Release version based on typescript-eslint 8.0.0 beta

Since typescript-eslint throws peer-dependency errors unless one uses the 8.0.0 beta it would be great to get a (pre-)release of eslint-stylistic that uses that version: https://typescript-eslint.io/blog/announcing-typescript-eslint-v8-beta
I'm running into peer dependency issues in the neostandard config where I use the 8.0.0 beta but eslint stylistic pulls in the 7.x version

I don't think we should bump to a pre-release in our dependencies now, as not every user wants to opt-in for the beta versions, and we shouldn't enforce them.
I would wait until they do stable releases. For now you can always use your local package resolutions/overrides to ensure you have a single version of ts-eslint packages.

@antfu The problem is that those of us who are relying on ESLint 9 currently gets lots of unmet peer dependency when using @stylistic: https://github.com/neostandard/neostandard/issues/35
Would it be possible to move to a peer dependency setup where @stylistic accepts both 7.x and 8.0.0 prereleases

Our solution was to simply remove stylistic TS rules for now and only have stylistic rules for JS

@antfu The problem is that those of us who are relying on ESLint 9 currently gets lots of unmet peer dependency when using @stylistic: neostandard/neostandard#35

It's more than just unmet dependencies message, TS code is not properly handled at all: formatting is incorrect, rules needing types checking misbehave, ... Having the two different major typescript-eslint version installed result in global linter misbehavior, including plugins using typescript-eslint API.

Just mention again you can override your local version with your package manager:

https://pnpm.io/package_json#pnpmoverrides
https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/

Just mention again you can override your local version with your package manager:

https://pnpm.io/package_json#pnpmoverrides
https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/

It's not an acceptable solution for an all-in-one dep targeting at enforcing standard coding style in TS, JS, ... code base to require package manager tuning to work properly on TS code base. Since at some point in time, eslint-stylistic will support typescript-eslint 8, I guess the neostandard maintainers have decided to wait for it before reintegrating TS code base formatting.

It's not we are requiring you to do it - it's the fact that typescript-eslint v8 is just not out yet. It's not practical for a stable package to ship a beta dependencies, if you decided to use the beta anyway, you take care the logicisic. Otherwise you might wait, we will bump the deps as soon as the ts-eslint v8 stable comes out.

It's fine.
But given the outcomes with two different major typescript-eslint version installed:

a big fat warning should be issued in that case about misbehavior => typescript-eslint upstream bug report
eslint-stylistic can consider shipping alpha releases with typescript-eslint 8 support only in order to allow its support stabilization. That version will be a breaking change and it looks like to be not trivial.

It feels wrong that my JavaScript project using stylistic has anything do to with TypeScript versioning.

It's because of "@typescript-eslint/utils": "^7.12.0" dep in several sub-packages package.json. I have no clue on its requirement since I do not know the code base. But I agree: a formatting only eslint plugin should not rely on typescript-eslint plugin to format TS files.
Maybe:

Untangle typescript-eslint requirement in existing rules when possible: split rules needing it from rules not
Detect if typescript-eslint is installed with a supported version as external dep and then enable optional rules requiring it

it's not practical for a stable package to ship a beta dependencies

What I was asking for is to make a pre-release of your own rather than wait for typescript-eslint 8.x to ship.
That way you will help out validate the new version, ensure no regressions remains in the stable version etc.
On top of that the typescript-eslint 8.x version is special, as unlike ESLint 9 the typescript-eslint crew decided to remove all style rules in 8.x, not just have them deprecated, leaving users of style rules with little way to test out the typescript-eslint 8.x release unless eslint-stylistic helps out.

I see. I am convinced. We will do beta releases with ts-eslint v8 then


Finish killing multiple parameter lists

Final installment in the series after https://github.com/apple/swift/pull/18128.
In a few places I had to hack things up a bit because the multiple parameter list and uncurry level terminology is so ingrained, in particular in CSDiag. We can clean this up later.
Fixes https://bugs.swift.org/browse/SR-5832.

@swift-ci Please test

@swift-ci Please test source compatibility

Build failed
Swift Test OS X Platform
Git Sha - 90cd772228932e0f8387c3bfcbacdb034fd87142

https://github.com/apple/swift-lldb/pull/787
@swift-ci Please test


Bought your app today on App Store

Would love the ability to show/hide the toolbar... I find it quite distracting since I know markdown and don't use the toolbar buttons for formatting etc. Any chance we can get an update with the ability to turn it off?

Click the separator line between the toolbar and the main content to toggle the toolbar. Let me know if it works for you.

Hey look at that - it works! I'm very happy. Did I miss that somewhere in the instructions? Now all I need is for math formulae, flow charts, sequence diagrams and Gantt charts to be able to render in my Gitlab and Github READMEs!
I love MDP and will leaving a glowing review for you in the App store.

Unfortunately GitHub Flavored Markdown doesn't support "math formulae, flow charts, sequence diagrams and Gantt charts". So GitHub READMEs cannot render them.
An alternative way is to export your markdown file as HTML and publish the HTML to GitHub Pages.

Excellent idea - thanks.


Create vm

I am getting a compile error in CreateVMWizardModel.java on line 144. Am I missing something? Here's the error:
Error:(144, 64) java: CreateVMWizardModel.java:144: type javax.swing.JList does not take parameters

I think it might help if we added the publish date along with the image label in the images list. For example instead of just CoreOS Alpha, we could show CoreOS Alpha - 13-1-2015.

Should we make the default VM size as Small (1 cores, 1792 MB)?

Should we add an option to specify an SSH key for Linux VMs?

When you create a new cloud service, we should select that new service in the drop down after the service is created. Also, should we default to creating a new cloud service instead of selecting one?

The default endpoints for a Linux VM shouldn't be PowerShell and RDP.

Got this error when I created a storage account in the flow:

We seem to have multiple instances of drop downs which need a sentinel "Create" item artificially inserted into the list (the cloud service drop down and storage drop down are examples). I am wondering if it'll make sense to make a reusable component that has built-in support for such an item and use that everywhere we need it instead of implementing it afresh each time.

After creating a Linux VM I wasn't able to SSH into the VM though I created the end point for SSH. Maybe we're missing some configuration while sending the create VM request?

@avranju: About the compile errors you are having, I couldn't reproduce the issue. I will remove the generic parameters that seem useless anyway, to see if that helps.

@avranju: About the names of the VM Images, I will add the publish date.

@avranju: About adding a SSH key to VM creation, Visual Studio does not have Linux support, and we are are designing the UI to mimic the wizard in VS. What we thought it would be the best is to allow to create a initial login by SSH with user/password, and if the user wants to add a certificate, he can do it later. I will add the SSL port as a default endpoint on linux VMs. By the way, we detected an issue with SSH logins, I already fixed it.

@avranju: about selecting the new cloud service once created, I will add the functionality.

@BeatriceOltean Do you want to comment on adding support for SSH keys while creating Linux VMs? Visual Studio is Windows only so it may make sense for them to de-prioritize support for Linux VMs in their tooling. Our tooling though will be available on non-Windows platforms. So it might make sense to add this capability.

Linux VMs are offered in Azure so developers should be able to have this capability.

@avranju: about the error in the flow, I couldn't reproduce the error.


Windows intel prosessor

Is there an installer for intel processors? When I was on a win 7notebook with a intel processor it gave the download file of keybase_setup_AMD64.msi. When running it it gives the error the this package will not work on this processor. Is there a seperate build for intel? I did install it on another notebook with an intel chip.

Does the notebook you're having trouble with have a 32-bit or 64-bit CPU?
You can find instructions on how to find this information here:
https://support.microsoft.com/en-us/help/827218/how-to-determine-whether-a-computer-is-running-a-32-bit-version-or-64


CONFIG_PWR_CTRL_ENABLED with BJT instead of a MOSFET

Can the circuit for CONFIG_PWR_CTRL_ENABLED be modified to use a BJT instead of a MOSFET? If yes how would the circuit look like?

Yes, you can use PNP bipolar transistor. More info here (as a note for gpu attribute). On my setups I tested both types of transistors: MOSFET and PNP and both variants worked fine.


Feat/one box test env

PR-Codex overview
This PR focuses on updating the Dockerfile and CI workflows.
Detailed summary:

Removed installation of arlocal package from Dockerfile
Added artifacts directory to hardhat.config.ts
Updated CI workflow to only run Hardhat compile and test commands in metadata directory
Added echo commands to CI workflow to display root directory and metadata directory
Copied db3 binary to Docker directory in CI workflow

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Codecov Report

Merging #516 (23b3b1f) into main (926b782) will increase coverage by 0.02%.
The diff coverage is 35.29%.

:exclamation: Current head 23b3b1f differs from pull request most recent head 0a52f2c. Consider uploading reports for the commit 0a52f2c to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #516      +/-   ##
==========================================
+ Coverage   60.40%   60.42%   +0.02%
==========================================
  Files          71       71
  Lines       14046    14050       +4
  Branches       60       60
==========================================
+ Hits         8484     8490       +6
+ Misses       5562     5560       -2

Flag
Coverage Δ

rust
60.42% <35.29%> (+0.02%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/node/src/indexer_impl.rs
0.00% <ø> (ø)

src/node/src/mutation_utils.rs
29.44% <0.00%> (-0.37%)
:arrow_down:

src/node/src/storage_node_light_impl.rs
0.00% <0.00%> (ø)

src/storage/src/ar_fs.rs
0.00% <0.00%> (ø)

src/storage/src/meta_store_client.rs
16.43% <ø> (ø)

src/storage/src/mutation_store.rs
68.59% <100.00%> (+0.30%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[RFC] Initial integration of libct into libcontainer

Hi All,
I'm integrating libct with libcontainer. I would like to share with you
this early draft to gather your opinions and advices.
This patch adds new factory and container classes to create and manage
containers via LibCT. This version is based on Michael's version of
libcontainer, where is a new api is used.  It has minimal functionality
just to show you how it looks like.
The current version of the abstract interface is a bit different. It
doesn't affect the idea of this patch. I will update the patch as soon
as libcontainer starts using the new interface.
LibCT is a library for creating and managing containers. It has ability
to add different backends. Currently it has only a native backend, which
is the same what libcontainer has now. We are developing a backend for
OpenVZ and PCS.
Notes:
The dockerinit process isn't required for libct. If I understand
correctly, dockerinit is used, because in golang code we should make
os.exec() immediately after os.clone().
If you want to play with this code, you can clone
https://github.com/avagin/libcontainer/commits/devel-new
Cc: Michael Crosby<EMAIL_ADDRESS>Cc: Victor Marmol<EMAIL_ADDRESS>Cc: Pavel Emelyanov<EMAIL_ADDRESS>

https://github.com/docker/libcontainer/pull/434


fix koa error handling and refactor http service

Coverage increased (+1.6%) to 86.207% when pulling e650e3d3a397a5f6800e32ae649b84ec4d522218 on fix/koa-error-handling into da689ca177464465e8ba257971b1d1f7a47ea615 on master.


Add faq for minikube users to embed their certs

We should put on a faq page that if someone is using minikube that we recommend that they embed their certificates. Most of the examples will only include the kubeconfig but by default minikube puts the certs in a separate file.
They should run minikube config set embed-certs true (from v0.29) so that minikube puts the certs in the config file. Otherwise you will get ugly error messages about being unable to connect.
err: couldn't get kubernetes client: couldn't build kubernetes config: invalid configuration:
[unable to read client-cert /Users/carolynvs/.minikube/client.crt for minikube due to open /Users/carolynvs/.minikube/client.crt:
no such file or directory, unable to read client-key /Users/carolynvs/.minikube/client.key for minikube due to open /Users/carolynvs/.minikube/client.key:
no such file or directory, unable to read certificate-authority /Users/carolynvs/.minikube/ca.crt for minikube due to open /Users/carolynvs/.minikube/ca.crt:
no such file or directory]

See the Doc Contributing Guide for help on how to preview your changes.

Hi! I can work on this 😄


BibTeX import: preamble with def create problems

Hello,
I have observed the following problems with bibtex Files involving preamble commands
involving defs:
If I try to import a file with a preamble commands containing a complicated
def command (being the result of an old bibtex export from mathematical reviews),
see the file problem-preamble.txt renamed to to problem-preamble.bib, the import stops with
the typical zotereo error message (see Error reports  5WM42JHA, HH4U5U9P, DBTTYV3U).
This still holds, if the bibtex file is changed and the defined command is not used in the following
entry.
If I import a file with a preamble command with a simple def command, see the file
problem-preamble-okay.txt renamed to problem-preamble-okay.bib, then the import works,
but I am not sure if is correct that the defined command in authors is completely ignored during the import.

:robot: bleep bloop; this is your friendly neighborhood build bot announcing test build 4267 (undefined).

Can you try 4267? It should fix the error, and I've added problem-preamble.txt as a test case to prevent regressions. The reference will require fixing after import; BBTs parser is not a full LaTeX processor (that'd be pretty crazy to even try), so the \def in the preamble will be ignored, and the name will come out as [Franc] [Jan], not [Franců] [Jan] (although \r u should import correctly I think).

:robot: bleep bloop; this is your friendly neighborhood build bot announcing test build 4270 ("Merge branch '723' into 732").

Really could use confirmation on this.

Will check tomorrow on my PC. Sorry for the delayed response.
Am 17. September 2017 20:55:56 MESZ schrieb retorquere<EMAIL_ADDRESS>
Really could use confirmation on this.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/retorquere/zotero-better-bibtex/issues/732#issuecomment-330072046

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

I have tried to test build 4267, but it seems that the link points to an invalid file. I could not load this file
with only 127K as app to zotereo.
I have tested now build 4270 and could import both files for the  problem-preamble.bib file there is
an additional entry in the literature list which contains the informations:

Import errors found:  Parse error: found "1", expected "}" <<
I think that this is a almost the solution for the really complicated macro situation.
Thank you.

But I am thinking about how to deal with  LaTeX/TeX macros in BBT. I agree to your point
of view that trying to build a full LaTeX parser is out of question.
But, I am thinking on those commands BBT can not deal with. Maybe BBT could mark somehow
that some fixing is required, for example by marking the overall entry with some tag/some note or
inserting it into some new subcollection "Entries needing fixing"
and by replacing the complicated command by

"UNEXPANDED_MACRO["copy of complicated"]"<< in the resulting entry, e.g
replaceing "\ocirc{u}" by  "UNEXPANDED_MACRO[\ocirc{u}]" in my example.  Should I open a new issue for this discussion, or has this already been discussed before?

Sorry, I closed the issue accidentally.

Yeah sorry about that link, the build process only retains the last 6 builds, so if you don't grab them promptly they get removed as I push out newer builds. I can always produce a new build, no problem.
No need to open a new issue -- I've added a feature request for the parser so I can mark references appropriately, but I wouldn't expect too much -- bib(la)tex import is always going to have problems with anything but very straightforward references.
Thanks for the confirmation, I'll fold this into a new release.


6.x compatibility thread

Hi,
I'm trying to build some graphs but appears this error:

Branch 6.x
Regards

Hi @OriolOMM thanks for the report!
I only tested the plugin on 5.x so we need to patch this for 6.x to import the kibana tables handler most likely. Could you provide the full kibana logs for this crash?

@OriolOMM I patched the 6.x branch, could you kindly try again running from sources? Thanks!

Hi @lmangani thanks for your fast patch. But for me is still failing :(
Here you can see the logs that appear when I press the play button:
`
Mar 14 09:38:36 adm-elk-client01 kibana: {"type":"response","@timestamp":"2018-03-14T09:38:36Z","tags":[],"pid":25267,"method":"get","statusCode":304,"req":{"url":"/ui/favicons/favicon-32x32.png","method":"get","headers":{"connection":"upgrade","host":"<IP_ADDRESS>","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36","accept":"image/webp,image/apng,image/,/;q=0.8","referer":"http://<IP_ADDRESS>/app/kibana","accept-encoding":"gzip, deflate","accept-language":"es-ES,es;q=0.9,ca;q=0.8,en-GB;q=0.7,en;q=0.6","if-none-match":""8e183c2e644fb050707d89402e1f7a120a95e4d2"","if-modified-since":"Fri, 16 Feb 2018 19:20:58 GMT"},"remoteAddress":"<IP_ADDRESS>","userAgent":"<IP_ADDRESS>","referer":"http://<IP_ADDRESS>/app/kibana"},"res":{"statusCode":304,"responseTime":7,"contentLength":9},"message":"GET /ui/favicons/favicon-32x32.png 304 7ms - 9.0B"}
Mar 14 09:38:37 adm-elk-client01 kibana: {"type":"response","@timestamp":"2018-03-14T09:38:37Z","tags":[],"pid":25267,"method":"get","statusCode":304,"req":{"url":"/ui/favicons/favicon-16x16.png","method":"get","headers":{"connection":"upgrade","host":"<IP_ADDRESS>","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36","accept":"image/webp,image/apng,image/,/;q=0.8","referer":"http://<IP_ADDRESS>/app/kibana","accept-encoding":"gzip, deflate","accept-language":"es-ES,es;q=0.9,ca;q=0.8,en-GB;q=0.7,en;q=0.6","if-none-match":""13b869be5df4bdc56920edc16a28e67a7c08203b"","if-modified-since":"Fri, 16 Feb 2018 19:20:58 GMT"},"remoteAddress":"<IP_ADDRESS>","userAgent":"<IP_ADDRESS>","referer":"http://<IP_ADDRESS>/app/kibana"},"res":{"statusCode":304,"responseTime":10,"contentLength":9},"message":"GET /ui/favicons/favicon-16x16.png 304 10ms - 9.0B"}
Mar 14 09:38:37 adm-elk-client01 kibana: {"type":"response","@timestamp":"2018-03-14T09:38:37Z","tags":[],"pid":25267,"method":"post","statusCode":200,"req":{"url":"/elasticsearch/_msearch","method":"post","headers":{"connection":"upgrade","host":"<IP_ADDRESS>","content-length":"449","accept":"application/json, text/plain, /","origin":"http://<IP_ADDRESS>","kbn-version":"6.2.2","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36","content-type":"application/x-ndjson","referer":"http://<IP_ADDRESS>/app/kibana","accept-encoding":"gzip, deflate","accept-language":"es-ES,es;q=0.9,ca;q=0.8,en-GB;q=0.7,en;q=0.6"},"remoteAddress":"<IP_ADDRESS>","userAgent":"<IP_ADDRESS>","referer":"http://<IP_ADDRESS>/app/kibana"},"res":{"statusCode":200,"responseTime":37,"contentLength":9},"message":"POST /elasticsearch/_msearch 200 37ms - 9.0B"}
thanks`

Thanks @OriolOMM I now found the core issue, some code needs to change to match 6.x internal revolutions - will release some patches this week to address it.

Thanks @lmangani!

Hi @lmangani
Though we have kbn_network integrated in our stack, considering other rich features of kibana_graph, we are eagerly waiting for the fix of this issue. Are you planning to release any new patch for 6.x in near future?

Hi @nsahaytech @OriolOMM absolutely yes, and apologies for not being able to fix this yet but as soon as time allows (or a contributor walks in) it'll definitely be addressed for 6.x and higher!

Update for those interested - We now have a partially working version on 6.2 with some bugs and quirks, and hopefully should have a stable release in the coming weeks. If anyone is familiar with 6.x and basic development and feels like contributing, please stand up ;)

Hi @lmangani. I installed kibana_graph for 6.2.4 of ELK. But it does not work even for a single node. Could you please help?

Great News - we finally found the core issue being the default responseHandler in 6.2+ a fix should follow up soon!

Is it possible to get a release for 6.2.3?

Hi, Thanks. Now it seems to work a little for two nodes. But for a chain of 4 nodes it gets stuck.

@vi9dgupta could you share the console errors?

@lmangani can u share project link of Kiban-graph for 6.3.2 or 6.X version?

@ashutoshningot everything available is already on github

Can you provide direct link for 6.3.2 as i tried with all possible tags/branch of this project but din't work for mi.

Please provide fix for kibana 6.7.0 version. The kibana itself does not boot up on changing the version name in package.json.


igv 2.3.97

Thank you, but please fill in the pull request template next time.

Will do. Thanks for merging. I used hub pull-request to open the PR, and it ignored .github/PULL_REQUEST_TEMPLATE.md for some reason.


Fix issue where methods that return int 0 do not have message body

Added a case in server2.js to show the error case:
1b97be94898c55300244f36966c87d32b7634635
To see the error use the following command:
dbus-send --print-reply --type=method_call --dest='some.name' '/com/github/sidorares/1' com.example.service.getint int32:0
You will see nothing in the body of the reply.  However, if you change the parameter to a non-zero value like 'int32:999', then there is a body in the reply.
This commit fixes the bug:
5337dad3800699ceec75245e96c469fbf5ee1636
It would be great to get this rolled into the npm release quickly.

Something strange with this PR - can you double check it and put only your commit into PR?

5337dad3800699ceec75245e96c469fbf5ee1636 lgtm

I'm not sure what is wrong with it.  It's a very simple change though, could you just apply it yourself?

I can cherry pick it from your repo, not a problem

Thank you!  Do you think it could be released soon?

eta +7 hours, sorry, too busy with other things

Excellent, thank you again.

Re-did PR, so closing this one.


Timesheet - 01/05/2021 - Bucky Roberts

Task 1
Recorded, edited, and uploaded 5 Docker tutorials.
Proof of Work

https://www.youtube.com/watch?v=yKUuCtSLwEM

Time Spent
5.5 hours

Total Time Spent
5.5 hours
Account Number
a37e2836805975f334108b55523634c995bd2a4db610062f404510617e83126f

Approved

Approved


Add free, automated flake8 testing to all new code submissions

Flake8 tests can help to find Python syntax errors, undefined names, and other code quality issues.  Travis CI is a framework for running flake8 and other tests which is free for open source projects like this one.  The owner of the this repo would need to go to https://travis-ci.org/profile and flip the repository switch on to enable free automated flake8 testing of each pull request.

@cclauss thanks for this, the code quality of all the library might actually benefit from this!
@paragbaxi i am not the repo owner, can you please flip the switch? i think we need to merge this first though

Flipped on.

Output: https://travis-ci.org/paragbaxi/qualysapi/builds/353182845?utm_source=github_status&utm_medium=notification


[FLINK-30896][table] Reduce usage of CatalogViewImpl in table-planner

What is the purpose of the change
CatalogViewImpl is deprecated and it is suggested to use CatalogView in comments.
The PR replaces CatalogViewImpl usages in table-planner with CatalogView.
In fact most of the work has been already done within https://issues.apache.org/jira/browse/FLINK-21801
And this PR does replacement for probably missing
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no )
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no )
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Sorry, seems I missed your comment.
Thanks for taking a look.

BTW, do we plan to remove the CatalogViewImpl after all the module do not rely on this ?

I would vote for this, however before doing this I would double check it in ML


Add Disney+ ESPN "curated" content

Got an email this morning from Mickey that said, in part:

Sure enough, there is a tile...

... and what appears to be a limited subsection of upcoming ESPN+ events...

As such, would it be possible to have a Disney+/ESPN Tile integration? Not having a subscription to ESPN+, it would only need to be these events added to the schedule.
Thanks!

I'll look at this


Refactor optimizations and multi calculated dims

changelog:

Consistent use of const for functions
Refactor most ofEach() to use array.reduce()
Refactor if/else blocks as ternaries
Add support for multiple calculated dimensions
Add example for multiple calculated dimensions

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Jim Rapp seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix register page for mobile view

Describe the bug

Font size and spacing have been modified and exceed screen width.

To Reproduce

Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

A clear and concise description of what you expected to happen.

Possible solution

Describe the solution you thought of.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.You can also mention your system environment in which you are running it.

Please assign me this issue under gssoc

It's working fine


Maui - iOS push notification cannot be set up -  Could not find a part of the path (Path too long)

Using the Xamarin.Firebase.iOS.CloudMessaging nuget in .NET Maui.
Android works fine, but in iOS we get this error. I believe it is because the file path is too long - however I have set the system settings to enable long paths and still get this exception.
**An error occurred while trying to deploy the app 'SamplePush.app'. Details: Could not find a part of the path
'C:\Users\username\AppData\Local\MyTempFiles\Xamarin\HotRestart\Signing\SamplePush.app\out\Payload\SamplePush.app\SamplePush.content\Firebase.CloudMessaging.resources\FirebaseMessaging.xcframework\ios-arm64\FirebaseMessaging.framework\Headers\FirebaseMessaging-umbrella.h'.**
I changed my temp file location to be shorter C:\tmp but still get the following:
**An error occurred while trying to deploy the app 'SamplePush.app'. Details: Could not find a part of the path
'C:\Tmp\Xamarin\HotRestart\Signing\SamplePush.app\out\Payload\SamplePush.app\SamplePush.content\Firebase.Core.resources\GoogleUtilitiesComponents.xcframework\ios-arm64_x86_64-simulator\GoogleUtilitiesComponents.framework\Headers\GoogleUtilitiesComponents-umbrella.h'**

Yeah , i found this problem too T^T
i use window 11 home , visual studio 22
my project is c# .net 7 maui
i use Firebase
and
it's call  xamarin.firebase.ios.CloudFireStore and BOOM  Long Path error
i try to set in regedit, gpedit.msc
it's not happen T^T
so sad brother

Try clearing your local nuget cache and run a nuget restore from the command line (not using Visual Studio).

Hi, I could manage the problem and now I can compile the iOS .Net 8 Maui App with Pulgin.Firtebase. I used "dotnet restore" to get the nuget package. But now I'd like to publish the app and I can't create an archive with the Archive Manager from Visual Studio 2022, because the path is too long! The zip file can be craeted, but the Unzip task crashes. The path, where the zip file is created is:
C:\Users\Marian.GRZESIK\AppData\Local\Xamarin\iOS\Archives\2024-01-05
When I try to unzip the file in c:\tmp, than it works.
Is it possible to shorten the paths? It worked well in Xamarin.Forms, but in .Net Maui it doesn't.

In the past, .NET iOS binding libraries were packed into .dll files. This led to naturally shorter file paths (e.g. /lib/xamarinios10/Firebase.Core.dll)
Apple has shifted to using XCFrameworks as the standard binary packaging format. This leads to naturally longer file paths (e.g /lib/net6-ios15.4/FIrebase.Core.resources/GoogleUtilitiesComponents.xcframework/ios-arm64/GoogleUtilitiesComponents.framework/Headers/GoogleUtilitiesComponents-umbrella.h)
Visual Studio (Windows) is fundamentally incapable of dealing with longer file paths like this. See:
https://github.com/NuGet/docs.microsoft.com-nuget/issues/2323
The punchline is that Visual Studio (Windows) is simply no longer a reliably viable tool for building or archiving iOS apps (MAUI or otherwise).

I fixed this by changing the nuget package location to a path that’s shorter than the default path. I did this by adding the following configuration to my NuGet.Config.
<config>     <add key="globalPackagesFolder" value="D:\nuget" />   </config>

I tried the short path in Nuget. I can compile iOS, but I could it also before. The problem is still the Package Manager in Visual Studio 2022, which can't create the package because of too long path. It can't Unzip the package. I changed the tmp path in windows to a very short one and the location of the archive, but the path ist still too long.
In Android I had to delete temporary iOS as the target framework, because otherwise it crashes with the same problem, because of iOS and too long path. It's strange. Without iOS I can build the package for the store.

I think the really well solution were the support of long path in Visual Studio 2022. It's awkward, that it can cope with long path till today.
PS. I had the same problem with an another Nuget Package -> Scandit for .Net Maui. The developer changed the names to much shorten ones, and now it works without any problem.

The developer changed the names to much shorten ones, and now it works without any problem.

You cannot simply change names in an XCFramework. They need to match the module names.

I fixed this by changing the nuget package location to a path that’s shorter than the default path. I did this by adding the following configuration to my NuGet.Config.
<config> <add key="globalPackagesFolder" value="D:\nuget" /> </config>

That's a workaround - not a fix ;) . A fix would prevent the problem from happening in the first place!

I fixed this by changing the nuget package location to a path that’s shorter than the default path. I did this by adding the following configuration to my NuGet.Config.
<config> <add key="globalPackagesFolder" value="D:\nuget" /> </config>

That's a workaround - not a fix ;) . A fix would prevent the problem from happening in the first place!

i try this but
C:\nuget  is ok
but my main project is
C:\XXXXXXX\XXXXXXXX\XXXXXXXXX\bin\debug...................................   it's still too long T^T
C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(4911,5)
: warning MSB3026: Could not copy
"C:\Nuget\xamarin.firebase.ios.cloudfirestore\<IP_ADDRESS>\lib\net6.0-ios15.4\Firebase.CloudFirestore.resources\grpc.xcframework\ios-arm64_x86_64-simulator\grpc.framework\PrivateHeaders\src\core\ext\filters\workarounds\workaround_cronet_compression_filter.h"
to
"bin\Debug\net7.0-ios\iossimulator-x64\Firebase.CloudFirestore.resources\grpc.xcframework\ios-arm64_x86_64-simulator\grpc.framework\PrivateHeaders\src\core\ext\filters\workarounds\workaround_cronet_compression_filter.h".
Beginning retry 2 in 1000ms. Could not find a part of the path
'bin\Debug\net7.0-ios\iossimulator-x64\Firebase.CloudFirestore.resources\grpc.xcframework\ios-arm64_x86_64-simulator\grpc.framework\PrivateHeaders\src\core\ext\filters\workarounds\workaround_cronet_compression_filter.h'.

For anyone who have still problem with long paths (size bigger than 260 characters).

Check if problematic paths do contains your project name. If yes you can try to rename it.
If bin or obj files are problem you can try to set them in properties of your project under Build configuration
Check if problematic path contains C:\Users\YourProfileName\AppData\Local\Temp... at the beginning, if yes there is DIRTY option to rename ENVIROMENTAL VARIABLE TEMP and TMP to something like C:\Test , BUT I needed to do RESTART of PC in order to stop copying into AppData\Local\Temp\Xamarin\ .... this will save you certain amount of characters

Combination of following might help you.
Hope it helps.


[Feature Request] Add Intel WiFi Driver Instructions

Now that AirPortItlwm exists here You should add instructions for users who do not wish to use Broadcom WiFi cards. It is in Beta and the according to FAQ the WiFi speeds are not the same as Broadcom ATM but will suit people who have so far been relying on USB WiFi Dongles. Awesome work on this so far!

I can add instructions in the Readme file, but the related kexts will not be merged into the warehouse


Refactor Cesium3DTilesStyle so that its always synchronous, add fromUrl

Fixes https://github.com/CesiumGS/cesium/issues/10345
This refactors Cesium3DTilesStyle so we can treat the object as completely synchronous, and removes the need for ready and readyPromise properties, which become deprecated. It also removes the string and Resource types from the constructor, again, deprecating them. Instead, this adds a fromUrl static function to asynchronously create a new style from a url.
This also allows us to clean up many of our specs, as we no longer need to wait on the style's readyPromise to be fulfilled.
TODO:

[ ] Create remove in issue

@ebogo1 Could you please review?

Thanks @ggetz - just a typo in CHANGES.md and a small conflict with main but otherwise I think this is good to go :+1:

Thanks again @ebogo1, fixed!


Syncing a large Dictionary with MultiplayerSynchronizer causes MTU limit error

Tested versions
Reproducible in - v4.2.stable.mono.official [46dc27791] and v4.1.1.stable.mono.official [bd6af8e0e]
System information
Godot v4.2.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1080 (NVIDIA; <IP_ADDRESS>58) - Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz (8 Threads)
Issue description
When using a MultiplayerSynchronizer node to sync a Dictionary (Vector2i, int) of a size some value larger than 64 I receive the following error.
E 0:00:06:0503   _send_sync: Node states bigger than MTU will not be sent (2568 > 1350): /root/Lobby
  <C++ Error>    Condition "size > sync_mtu" is true. Continuing.
  <C++ Source>   modules/multiplayer/scene_replication_interface.cpp:833 @ _send_sync()

The only mention of MTU limits in the documentation suggests high-level multiplayer intends to avoid the end user being concerned with the concept. A blog post from 2016 suggests the user should not have to deal with MTU limits manually.
https://docs.godotengine.org/en/stable/tutorials/networking/high_level_multiplayer.html#high-level-vs-low-level-api
https://godotengine.org/article/godots-new-high-level-networking-preview/
Steps to reproduce
Create an exported dictionary on a node and add ~128 elements to it. Add a MultiplayerSynchronizer and add the Dictionary to the synchronizers properties. The error occurs when replicate is set to Always but not On Change.
In the MRP I use the following code to populate the dictionary.
@export var coordinate_dictionary : Dictionary

# Called when the node enters the scene tree for the first time.
func _ready():
	coordinate_dictionary = {}
	if !multiplayer.is_server():
		return
	for i in 128:
		coordinate_dictionary[Vector2i(i,i)] = i

Minimal reproduction project (MRP)
DictSizeTestPong.zip
The MRP adds a simple test to the pong demo project found here:
https://github.com/godotengine/godot-demo-projects/tree/master/networking/multiplayer_pong

Not a bug, just use set_max_sync_packet_size
	ClassDB::bind_method(D_METHOD("set_max_sync_packet_size", "size"), &SceneMultiplayer::set_max_sync_packet_size);

And change for the value you want.

Thank you, it looks like that would solve the issue for my case. However, the documentation for max_sync_packet_size says

Maximum size of each synchronization packet. Higher values increase the chance of receiving full updates in a single frame, but also the chance of packet loss. See MultiplayerSynchronizer.

This doesn't suggest that a smaller value will result in an error as it does. If I can get any kind of confirmation that this is intended behavior I'll close the issue and consider making an improvement proposal and an issue for the docs.

This is intended, you should avoid sending large data packets and I don't think what you're trying to do here is supported, synchronisation should be used for properties that needs that kind of updates, not complex large data structures, they should be sent by other means such as rpc calls


[FEAT] : improve the seo by adding the meta elements

Currently the Draw it out website lacks important meta elements so will affect seo problem

by adding the meta tag like description, keywords, author using the meta tags to improve the seo problem

@0xabdul Do you want to work on the issue?

Sorry, for 2 PRs. I forgot to change my main branch and what had to be 2 separate PRs came to same branch

@0xabdul Do you want to work on the issue?

yes i work

@0xabdul Best of Luck!


Added ID to EventTraceAttributes

cc @ian-mi
Signed-off-by: Francesco Guardiani<EMAIL_ADDRESS>

Why this change?

To align to this https://github.com/knative/eventing/blob/master/pkg/tracing/transformers.go#L57
Also it seems useful as attribute


ViewComponent

https://zenn.dev/cobachie/articles/tried-view-component

partial
https://qiita.com/shizuma/items/1c655dadd2e04b3990a8


cannot run solve_captchas.py

I have 23 accounts that need manual captcha solving, but can't get solve_captchas.py to run (traceback below).  I also can't access the manager at <IP_ADDRESS>:5002 (I got the impression from reading documentation that I may be able to solve them manually from there?).

added chromedriver location to PATH and updated google chrome. all working now. thanks


Error in godoc -html

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
Go 1.9
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
Windows 10 amd64
What did you do?
run "godoc -html :8000" and open the browser to localhost:8000.
What did you expect to see?
The usual welcome page.
What did you see instead?
There is an error message displayed on the welcome page
"template: main:6:10: executing "main" at <$.GoogleCN>: can't evaluate field GoogleCN in type godoc.Page"
and the welcome page has no content.

Nevermind. It is fixed by updating godoc.

fyi
$ godoc -http=":6060"
2018/04/02 20:13:51 executing template doc/root.html: template: main:6:10: executing "main" at <$.GoogleCN>: can't evaluate field GoogleCN in type godoc.Page
2018/04/02 20:13:53 executing template doc/root.html: template: main:6:10: executing "main" at <$.GoogleCN>: can't evaluate field GoogleCN in type godoc.Page
^C
[mh-cbon@pc4 src] $ go version
go version go1.10 linux/amd64

hello, still having the same issue on go 1.11 on a 64 bi linux lubuntu 16.04

This issue is closed. If you are still seeing issues, please open a new issue instead. Thanks.


merge deepGet and deepSet to get and set

In NestedTypes, model.get( 'attr' ) and model.set( 'attr', value ) are slower than accessing attribute through native property, and in general doesn't make any sense.
However, with new NestedTypes architecture we can add support for deep references directly to .get and .set functions, and it won't affect the performance of the native props.
Additional benefit would be that proxied underscore collections functions accepting attributes will work with deep references.

Using get and set with attr names is important for us because the name of properties change after code uglifier.

It depends on the options you pass. As far as I understand, with --mangle option it will screw up only local variables. Otherwise, latest NestedTypes version from 'develop' branch wouldn't work.

And need to add warning about this issue to documentation. Recent 'NestedTypes' most likely won't work at all if you will uglify everything aggressively.

Google closure compiler ADVANCED_OPTIMIZATIONS is my headache in these days.

Won't be fixed. Let's leave it as it is for now.


feature-login-registration-app

created engine.driver.py to encapsulate the process of file to video and vice versa.

implemented login and registration under ip:port/account/{login, logout, register}

PLEASE NOTE TO MERGE #38  BEFORE!


Could max value/caps of slider be a bit more forgiving?

Problem now is that sometimes somebody (read: @AlexanderWirtz) wants to put more than is permitted in a (scaled) scenario, but the max value of the slider does not permit that.
Could we allow the user to input any value in the text field of the slider, and, when it is larger than the current max of the slider, it should set the max of the slider to that value.
Of course, this does not apply to percentage sliders :grinning:
cc @ChaelKruip @jorisberkhout

Of course, this does not apply to percentage sliders

Do you mean the percentage sliders that form a slider-group and need to add up to 100%? We also have % sliders that can be outside the 0-100 range:

I believe that is what @dennisschoenmakers is referring too. I mostly want to recreate the current power production park in the northeast of Groningen province. I am not allowed to build all the coal plants they actually have, though.

Do you mean the percentage sliders that form a slider-group and need to add up to 100%?

Yes, I do. You don't want to upset them. :smile:

We also have % sliders that can be outside the 0-100 range:

It would be nice if they would also be flexible, you never know. We could then also restrict the max a bit more for normal users and allow elasticity whenever an expert needs it.

While I don't see any obvious technical reason preventing this, I would estimate this has moderate impact.

Our slider library enforces that values are valid (within the minimum and maximum).
ETEngine asserts that values are valid.

I think the behaviour of the slider could be a bit weird in the event you choose a larger- or smaller-than-permitted value: if the max value is 20, and you enter a custom value of 200 then touch the slider, it's going to jump back to 20.
My suggestion:

Add a new option to the settings menu allowing you to enter "exceptional" values. This is optional – and I'm not 100% sure about it – but I expect that it is useful to retain protection against wrong values for most users.

Allow entry of values into the text field which exceed the minima or maxima.

Extend the range of the slider to include the new value. In the above example, the slider's maximum value would be changed to 200 for that scenario.

This does still mean removing the validation from ETEngine, which is a pity, but I don't think that's a huge loss. We could likely keep validation for inputs whose unit is %, and those belonging to a share group.

@antw I like all of your suggestions!


SQL PRAGMA Error

Currently logged into are.nci.org.au but same error/issue happens via PBS submitted job. I have tested on all available conda environments and same error happens. (Things were working fine earlier in the day ... it seems like some update must have happened).
Here is sequence of commands issued that reproduce the error:
import cosima_cookbook   as cc
session = cc.database.create_session()
which results in

OperationalError                          Traceback (most recent call last)
File /g/data/hh5/public/apps/miniconda3/envs/analysis3-22.07/lib/python3.9/site-packages/sqlalchemy/engine/base.py:1900, in Connection._execute_context(self, dialect, constructor, statement, parameters, execution_options, *args, **kw)
1899     if not evt_handled:
-> 1900         self.dialect.do_execute(
1901             cursor, statement, parameters, context
1902         )
1904 if self._has_events or self.engine._has_events:
File /g/data/hh5/public/apps/miniconda3/envs/analysis3-22.07/lib/python3.9/site-packages/sqlalchemy/engine/default.py:736, in DefaultDialect.do_execute(self, cursor, statement, parameters, context)
735 def do_execute(self, cursor, statement, parameters, context=None):
--> 736     cursor.execute(statement, parameters)
OperationalError: attempt to write a readonly database
The above exception was the direct cause of the following exception:
OperationalError                          Traceback (most recent call last)
Cell In[2], line 1
----> 1 session = cc.database.create_session()
2 cc.querying.getvar(expt='01deg_jra55v140_iaf', variable='u', session=session, n=1)
File /g/data/hh5/public/apps/miniconda3/envs/analysis3-22.07/lib/python3.9/site-packages/cosima_cookbook/database.py:543, in create_session(db, debug, timeout)
541 # if database version is 0, we've created it anew
542 conn = engine.connect()
--> 543 ver = conn.execute("PRAGMA user_version").fetchone()[0]
544 if ver == 0:
545     # seems we can't use usual SQL parameter strings, so we'll just format the version in...
546     conn.execute("PRAGMA user_version={}".format(DB_VERSION))
File /g/data/hh5/public/apps/miniconda3/envs/analysis3-22.07/lib/python3.9/site-packages/sqlalchemy/engine/base.py:1365, in Connection.execute(self, statement, *multiparams, **params)
1356 if isinstance(statement, util.string_types):
1357     util.warn_deprecated_20(
1358         "Passing a string to Connection.execute() is "
1359         "deprecated and will be removed in version 2.0.  Use the "
(...)
1362         "driver-level SQL string."
1363     )
-> 1365     return self._exec_driver_sql(
1366         statement,
1367         multiparams,
1368         params,
1369         _EMPTY_EXECUTION_OPTS,
1370         future=False,
1371     )
1373 try:
1374     meth = statement._execute_on_connection
File /g/data/hh5/public/apps/miniconda3/envs/analysis3-22.07/lib/python3.9/site-packages/sqlalchemy/engine/base.py:1669, in Connection._exec_driver_sql(self, statement, multiparams, params, execution_options, future)
1659         (
1660             statement,
1661             distilled_params,
(...)
1665             statement, distilled_parameters, execution_options
1666         )
1668 dialect = self.dialect
-> 1669 ret = self._execute_context(
1670     dialect,
1671     dialect.execution_ctx_cls._init_statement,
1672     statement,
1673     distilled_parameters,
1674     execution_options,
1675     statement,
1676     distilled_parameters,
1677 )
1679 if not future:
1680     if self._has_events or self.engine._has_events:
File /g/data/hh5/public/apps/miniconda3/envs/analysis3-22.07/lib/python3.9/site-packages/sqlalchemy/engine/base.py:1943, in Connection._execute_context(self, dialect, constructor, statement, parameters, execution_options, *args, **kw)
1940             branched.close()
1942 except BaseException as e:
-> 1943     self._handle_dbapi_exception(
1944         e, statement, parameters, cursor, context
1945     )
1947 return result
File /g/data/hh5/public/apps/miniconda3/envs/analysis3-22.07/lib/python3.9/site-packages/sqlalchemy/engine/base.py:2124, in Connection.handle_dbapi_exception(self, e, statement, parameters, cursor, context)
2122     util.raise(newraise, with_traceback=exc_info[2], from_=e)
2123 elif should_wrap:
-> 2124     util.raise_(
2125         sqlalchemy_exception, with_traceback=exc_info[2], from_=e
2126     )
2127 else:
2128     util.raise_(exc_info[1], with_traceback=exc_info[2])
File /g/data/hh5/public/apps/miniconda3/envs/analysis3-22.07/lib/python3.9/site-packages/sqlalchemy/util/compat.py:210, in raise_(failed resolving arguments)
207     exception.cause = replace_context
209 try:
--> 210     raise exception
211 finally:
212     # credit to
213     # https://cosmicpercolator.com/2016/01/13/exception-leaks-in-python-2-and-3/
214     # as the traceback object creates a cycle
215     del exception, replace_context, from_, with_traceback
File /g/data/hh5/public/apps/miniconda3/envs/analysis3-22.07/lib/python3.9/site-packages/sqlalchemy/engine/base.py:1900, in Connection._execute_context(self, dialect, constructor, statement, parameters, execution_options, *args, **kw)
1898                 break
1899     if not evt_handled:
-> 1900         self.dialect.do_execute(
1901             cursor, statement, parameters, context
1902         )
1904 if self._has_events or self.engine._has_events:
1905     self.dispatch.after_cursor_execute(
1906         self,
1907         cursor,
(...)
1911         context.executemany,
1912     )
File /g/data/hh5/public/apps/miniconda3/envs/analysis3-22.07/lib/python3.9/site-packages/sqlalchemy/engine/default.py:736, in DefaultDialect.do_execute(self, cursor, statement, parameters, context)
735 def do_execute(self, cursor, statement, parameters, context=None):
--> 736     cursor.execute(statement, parameters)
OperationalError: (sqlite3.OperationalError) attempt to write a readonly database
[SQL: PRAGMA user_version]
(Background on this error at: https://sqlalche.me/e/14/e3q8)

@dpath2o Thanks for the report. This is a known issue that happens once in a while. The most recent update (from last night) should work fine. Could you have try?

Thanks Micael. Indeed it is working again. My apologies for bothering you.

No bother at all! I needed a reminder to implement a fix to this issue ;)


x/pkgsite: f for search doesn't work in Firefox for net/http page

What is the URL of the page with the issue?
https://pkg.go.dev/net/http
What is your user agent?
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:85.0) Gecko/20100101 Firefox/85.0
Screenshot
Looks just like the regular page on https://pkg.go.dev/net/http, but with a slightly greyed background. The same greying you get when you search with f, except that the actual search dialog does not appear.
What did you do?

Navigated to https://pkg.go.dev/net/http
Pressed f on my keyboard

What did you expect to see?
The "Jump to" dialog.
What did you see instead?
No dialog. Just modal greying of the page background and inability to interact with it.

Duplicate of #44077


[AKS] dashboard role for k8s dashboard and k8s dashboard URL

Problem:
For existing K8s, Such as AKS env k8s need RBAC role binding then could access api-server.
paictl k8s dahsboard also should define general
Dependency:
paictl & k8s dashboard
Reference Solution & Plan:
refer branch yanjga/aks-test
Dev plan

yanjie will create a pai/aks branch as master branch for receive all aks related pr. https://github.com/Microsoft/pai/tree/pai/aks
some knowledge could refer yanjga/aks-test driver related change
feature dev folk & submit pr to pai/aks branch
If all tests passed, then cherry pick pai/aks pr to master branch.

hi @wangcan0329 & @ydye  , For this issue's proposal,If there is a better way, let's discuss it together.
 :
Co-design with other services.

Could create the role binding during the service start. Use or not control  by a flag in service configuration about RBAC enable or not.
For k8s dashboard role binding,
method1: if i make a folder k8s-dashboard and only container start / stop to create binding or not. Do you think this way is ok? [This is more in line with microservices]
method2: is make this scripts to cluster configuration https://github.com/Microsoft/pai/tree/master/src/cluster-configuration/deploy.
@ydye For k8s dashboard role binding scripits in which position, do you have any comments?
https://github.com/Microsoft/pai/tree/master/src

@fanyangCS  and @sterowang ,  for rbac role proposal, pls review. context is at above.
This will affect some PR, if you agree, I will follow this role allocation.

Reference:

https://kubernetes.io/docs/reference/access-authn-authz/rbac/#default-roles-and-role-bindings

@ydye For k8s dashboard role binding. Propose to make the scripts at this folder and expose related config to user. Pls review if this is ok.
reason:
Since we did not maintain the kubernete dashboard in the service (pai/src) folder. We'd better treat this rolebinding as a cluster-configuration type and under (cluster-configuration folder). For other services like prometheus and watchdog, will set the create account and role binding at prometheus's deploy folder start.sh and stop.sh to keep the microservice relatively independent.

For code change and implement rbac role proposal:
0 k8s configuration.yaml new configuration items:
service account name etc.
token paths
1 change at src/xxservice folder
note: k8s dashboard don't have service folder suggest to make it at
2 start.sh
create serviceaccount
create rolebinding
deploy pod with this service account
3 stop.sh
delete serviceaccount
delete rolebinding

For k8s dashboard url on existing AKS which deployed not on existing machine list, proposal:
Pending: this will wait hao's new deployment process then do this feature.
(1)For deployment scripts:
will add a node ip only contains k8s dashboard label (which not affect other deployment as not label as pai-worker), this only used for paiobject model
https://github.com/Microsoft/pai/blob/2c08713a45457821543b2cd4c990b222ad367c71/deployment/clusterObjectModel/mainParser/kubernetes.py#L62
(2)For need add auto scripts:
to auto detect k8s dashboard pods ip then add a ip at cluster-configuration.

For this problem current status:
This problem could define as for existing k8s, the k8s dashboard may be deployed on different server use different ip then previous's PAI assumption. So make this ip  configurable.
This config will also as a service deployment input config in the future. @hao1939


Detour obstacle, circle with parameters of position and radius

Hello! I have a question...
I need to build a path by implementing an obstacle detour. But the requirement is as follows: there are the coordinates of the point and the radius of the circle. It is required to build a path around the circle.
"Sample_TempObstacles" as an example can not be used in my case.
Need to make an upgrade to "dtNavMeshQuery :: findStraightPath" to exclude the circle from consideration. I understand correctly? Any ideas or suggestions?

Other question: whether it is possible to calculate a way in a detour of the agent (without usage addObstacles) if that is in one point motionlessly?

Mikko has blogged about a potential implementation of this before: http://digestingduck.blogspot.dk/2011/02/very-temporary-obstacle-avoidance.html
http://digestingduck.blogspot.dk/2011/02/very-temporary-obstacle-avoidance-pt-2.html
However, the implementation with temporary obstacles is much simpler to use and works much better in practice. It will be hard to adapt findStraightPath to take into account both the polygons and additional circular obstacles.

I already tried to use addObstacle, I need it for the server. Tested on a large number of starts adding / removing obstacles - too long miscalculation.
Well ok .. I'll find more options.


Threadpool documentation

This addresses #235
Let me know if this is along the lines of what you were looking for. I made an assumption that rayon::join called inside of ThreadPool's spawn methods will also execute inside of the ThreadPool context, like install. If this isn't the case, I'll alter the second example and amend this commit. The example for spawn_future_async is based on code from your test cases.

I'm not quite sure why the docs are failing to compile, if someone could point out how to fix that I can amend the commit.
---- src/thread_pool/mod.rs - thread_pool::ThreadPool (line 28) stdout ----
	error[E0463]: can't find crate for `rayon`
 --> <anon>:2:4
  |
2 |    extern crate rayon;
  |    ^^^^^^^^^^^^^^^^^^^ can't find crate
error: aborting due to previous error

It's a little funny because of the way we expose rayon-core.  You can follow this example.

Lovely. I have an example of spawn_future_async, which of course uses futures. Is there a way to get that to work also?

Ah - not easily since that's behind an unstable feature flag.  Probably the best thing is to move that conditional example onto spawn_future_async itself.

I don't believe the # use rayon_core as rayon; is working properly either. In particular, in the example I
use rayon::{ThreadPool, Configuration}; and it doesn't appear to like that.

@leshow this looks like great work, thanks. I have one question: I have this PR that renames the various "async" methods (#313) that I had hoped to land soon. Would you mind updating the docs to reflect the new naming conventions?

@nikomatsakis Absolutely, I'll have a look at #313  and rename them appropriately.
I added the initial preamble because I thought it would be nice to have a simple example at the top of ThreadPool so users of rayon would know how things fit together. If it makes more sense to move everything to their corresponding methods I will do that.

I'm having trouble with the imports for example code still.
# use rayon_core as rayon;
use rayon::{Configuration, ThreadPool};

does not work, I have to use rayon_core:{Configuration, ThreadPool} so that it can find ThreadPool.
Additionally, I can't get extern crate futures recognized.

@leshow

I'm having trouble with the imports for example code still.

Huh, curious. My guess is that it has to do with exactly how rustdoc generates the code. I'm actually a bit surprised that my initial hack worked, now that I think about it, but it must be that the use winds up generated (in my code) at the root module, but not in your examples.

Ah, well, I guess I'm using things like rayon::scope in an expression context, where the paths are relative, but you are trying to do use rayon::, where the paths are absolute. Hence the difference. It seems like we should either give up and just do use rayon_core, or else hide the use statements altogether.

Or use explicit rayon::ThreadPool and rayon::Configuration in expressions here too.

After amending my commit about 20 different times trying different combinations of imports, I can across this:
https://github.com/rust-lang/cargo/issues/960
To use something like extern crate futures I need to include a fn main() declaration and either hide it with # or have it part of the example. So that's the futures issue taken care of.
Unfortunately on the nightly+unstable build, # use rayon_core as rayon says that rayon_core can't be found.

@leshow

To use something like extern crate futures I need to include a fn main() declaration and either hide it with # or have it part of the example. So that's the futures issue taken care of.

Ah yes good catch.

Unfortunately on the nightly+unstable build, # use rayon_core as rayon says that rayon_core can't be found.

Grr. Try adding extern crate rayon_core as rayon maybe, instead of the use?

Ha! That did it! thanks @nikomatsakis

Thanks, I've made those changes. I also amended the text for links to use the same wording that's ubiquitous throughout the docs already.

Nice :)


New Version 1.1

<?xml version="1.1" encoding="utf-8"?>
<configuration>
  <packageSources>
    <!--To inherit the global NuGet package sources remove the <clear/> line below -->
<add key="dotnet-core" value="https://www.myget.org/F/dotnet-core/api/v3/index.json" />
<add key="api.nuget.org" value="https://api.nuget.org/v3/index.json" />
    </packageSources>
</configuration>

Closin as this author has been spamming this repo. @jskeet has reported the author to github.


refactor: equals avoids null

Happy Hacktoberfest!
This refactor checks that any combination of String literals is on the left side of an equals() comparison to prevent null pointer exceptions.
:beers: Cheers,
Kyle

@zieka we appreciate the attempt, but for context what you have fixed is not production code and used for testing only. our hacktoberfest process is documented here: https://github.com/karatelabs/karate/wiki/Hacktoberfest


Simplify the IntlStream class

Remove some unnecessary use of dynamic. This class was written to operate over List instances, but the use case for a List contents is only a small bit of the functionality. The functionality used over a List content is non-overlapping with the subset of functionality use for String content.

Add a private extension method idexesWhere on List within the library that used the findIndexes method. Specialize to List with a indexed for loop instead of using the iterable approach.
Make The contents field a String and remove all conditional branches handling List instances.
Remove unused findIndex and findIndexes methods.
Make peek and rest concretely return String instead of dynamic.
Make the arguments to nextInteger positional and required since they are always passed and this is package private.
Add a TODO about merging with StringIterator. The two classes have overlapping functionality, but different enough APIs that it will be a noisier cleanup.
Make the setter for the index property private.

Thank you, good to see this happening. I hope this is a step in the
direction of replacing it with regular collection operations.  That code
has always been a nagging pain in the back of my mind for ages. Like, it
uses the name Stream in part because it wasn't a conflict, Dart had nothing
named Stream at that time - pre-M1 release.
On Thu, Sep 22, 2022 at 4:38 PM Nate Bosch @.***> wrote:

Remove some unnecessary use of dynamic. This class was written to operate
over List instances, but the use case for a List contents is only a small
bit of the functionality. The functionality used over a List content is
non-overlapping with the subset of functionality use for String content.

Add a private extension method idexesWhere on List within the
library that used the findIndexes method. Specialize to List with a
indexed for loop instead of using the iterable approach.
Make The contents field a String and remove all conditional branches
handling List instances.
Remove unused findIndex and findIndexes methods.
Make peek and rest concretely return String instead of dynamic.
Make the arguments to nextInteger positional and required since they
are always passed and this is package private.
Add a TODO about merging with StringIterator. The two classes have
overlapping functionality, but different enough APIs that it will be a
noisier cleanup.
Make the setter for the index property private.

You can view, comment on, or merge this pull request online at:
https://github.com/dart-lang/intl/pull/494
Commit Summary

4dfdc1b
https://github.com/dart-lang/intl/pull/494/commits/4dfdc1bf322fab2933e1a928dd3da4dca785cbf7
Simplify the IntlStream class

File Changes
(2 files https://github.com/dart-lang/intl/pull/494/files)

M lib/src/intl/date_format_field.dart
https://github.com/dart-lang/intl/pull/494/files#diff-fd7b4a615b344dc4840c228593c961bef539a3458e6473fbca8cad2119fc2e8b
(20)
M lib/src/intl/intl_stream.dart
https://github.com/dart-lang/intl/pull/494/files#diff-d84e97243bc784d6b52c0f9cb40b841eba901b612942bcd3848c70aa3ac66289
(100)

Patch Links:

https://github.com/dart-lang/intl/pull/494.patch
https://github.com/dart-lang/intl/pull/494.diff

—
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/intl/pull/494, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2QU6H2EZ4J3JRDEXK4IBLV7S7UVANCNFSM6AAAAAAQTNFRZ4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Arabic (non-Latin) digits definitely happen. There should definitely be
tests that exercise that.
On Fri, Sep 23, 2022, 12:14 Nate Bosch @.***> wrote:

@.**** commented on this pull request.
In lib/src/intl/intl_stream.dart
https://github.com/dart-lang/intl/pull/494#discussion_r978844739:

 if (string == null || string.isEmpty) return null;

 read(string.length);

if (zeroDigit != null && zeroDigit != constants.asciiZeroCodeUnit) {

if (zeroDigit != constants.asciiZeroCodeUnit) {
// Trying to optimize this, as it might get called a lot.
var oldDigits = string.codeUnits;
var newDigits = List.filled(string.length, 0);

I'd like to refactor this to
  string = String.fromCharCodes(string.codeUnits
      .map((c) => c - zeroDigit + constants.asciiZeroCodeUnit));

And my initial naive benchmarks show it should be just as performant.
I know this is maybe out of scope for the review, I was just thinking as
the name of the PR is "Simplify the IntlStream class"...
Yeah, I'd break this one out into a separate change since the comment
calls out perf as a motivation for the current implementation, and I don't
know if we have benchmarks for it.
Are non-ASCII digits really happening often enough that it's worth
supporting?
I have no idea. Figuring out whether we can remove the support may be more
effort than retaining it.
—
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/intl/pull/494#discussion_r978844739, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2QU6E7OXJBGNKJFR7V3MTV7XJNBANCNFSM6AAAAAAQTNFRZ4
.
You are receiving this because you commented.Message ID:
@.***>


Bower.json harakiri

What does this PR do ?
Fixes the broken npm install_deps after I deleted bower.json and pushed it directly to 2.x.

How should this be manually tested?
Take a look at the travis log

OMG. Closing it and pointing to 2.x


configcenter bug for zookeeper

Environment

Dubbo version: 2.7.2
Operating System version:  window10 1903
Java version: jdk1.8

Steps to reproduce this issue

create app router in dubbo admin
request my url
no response the app router

Pls. provide [GitHub address] to reproduce this issue.
Expected Result
No response or listner for the app condition router
Actual Result
We add the app condition router, it should be invoke in routerChain.route,
The reason is ZookeeperDynamicConfiguration

rootPath = "/" + url.getParameter(CONFIG_NAMESPACE_KEY, DEFAULT_GROUP) + "/config";

Tips:
CONFIG_NAMESPACE_KEY = org.apache.dubbo.configcenter.Constants.CONFIG_NAMESPACE_KEY = config.namespace (dubbo-configcenter-api)

But the zookeeper config is dubbo.config-center.namespace = dubbo, If I change to my own config, em, dubbo.config-center.namespace = dev, It cannot work

2.7.3已修复

Fxied in 2.7.3, and will be released in few days.


[bug] [master] task can't use [out] type param

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
task can't use [out] type param.

sqlTask use prepareParamsMap to replace param.

prepareParamsMap uses varPool of parameters.

parameters's varPool uses taskInstance.taskParams

BUT prepareParamsMap is created earlier than assignment of taskInstance.taskParams.varpool.

So taskInstance.taskParams..varpool is always null when prepareParamsMap is created.
What you expected to happen
task can use [out] type param
How to reproduce
1.create a task with [out] type task
2.create a sql use it.
Anything else
none.
Version
dev
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @huangchenguang123  #11053 had fixed the out param pass, you can check it again in dev.

Hi @huangchenguang123 #11053 had fixed the out param pass, you can check it again in dev.

Thanks, this is also a way to solve the issue. I will close my issue and pr.

close by #11053


Question about Refreshing a Page

I have noticed that when I refresh a page using NavigationService.Refresh(), the OnNavigatedToAsync method is not called. After reading #1304, #1002 and #995, If I provide a parameter to NavigationService.Refresh(), the OnNavigatedToAsync is called but the NavigationMode parameter is New instead of Refresh. I think the OnNavigatedToAsync method must be called always on Refresh, regardless of whether a parameter is passed or not and the NavigationMode parameter must be set accordingly . As someone said, some developers may find annoying this behavior but I think it is the purpose of the NavigationMode parameter.
Or how can I get the OnNavigatedToAsync method being called with the NavigationMode parameter set in Refresh?

Well, here's the line that calls the navigation mode in 1.1.13: https://github.com/Windows-XAML/Template10/blob/version_1.1.13p/Template10 (Library)/Services/NavigationService/NavigationService.cs#L214
And, here's the line that calls the navigation mode in 1.1.12 https://github.com/Windows-XAML/Template10/blob/version_1.1.12_vs2017/Template10 (Library)/Services/NavigationService/NavigationService.cs#L180
I assume you are doing this in Template 10 version 1.1.12.
Well, are you using NavigationService.ResolveForPage() to create your page programmatically? Either way, if you are getting mode==New the view-model is there. So, that's not it.
When you refresh you get New instead of Refresh...
So I looked at the 1.1.12 Refresh() operation in the FrameFacade (which is where the logic resides in 1.1.12) and I saw this implementation: https://github.com/Windows-XAML/Template10/blob/version_1.1.12/Template10 (Library)/Services/NavigationService/FrameFacade.cs#L165
I see the problem. Instead of wrapping this operation in the NavigationOrchestrator of the NavigationService which would properly call the view-model methods, it ONLY gets and sets the navigation state string of the encapsulated string.
How is it possible that you are the first person to report this? This is not good and is a real problem. I can't think of an immediate workaround either. I will need to significantly change the Navigation logic to get that to work. I think a quick around would be for you to put something in a static field to check for Refresh like this.
But, then I think it is worth looking at 10.2 which implements the frame facade logic here: https://github.com/Windows-XAML/Template10/blob/version_1.1.13p/Template10 (Library)/Services/NavigationService/FrameFacade.cs#L134
You can see the logic has been removed and marked as obsolete (it is not simply removed so Template 10.1 developers will have a little internal guidance on how to use the changed API. The Refresh logic has been moved to the NavigationService (the only place that made sense for it) and implemented here: https://github.com/Windows-XAML/Template10/blob/version_1.1.13p/Template10 (Library)/Services/NavigationService/NavigationService.cs#L370
I guess I realized the problem you identify here while rewriting Template 10 for the Falls Creators Update.  The Refresh operation is now properly wrapped in the NavigationOrchestrator which is responsible for not just navigation but also managing the before and after events for view-models.
A hack of a workaround is all I can offer you with version 1.1.12
Maybe this:
static bool _refresh = false;
void MyMethod()
{
  _refresh = true;
  navigationService.Refresh();
}
void NavigatedTo()
{
  Try
  {
    if (_refresh)
    {
      // special logic
    }
    else
    {
      // normal logic
    }
  }
  Finally
  {
      _refresh = false;
  }
}

Hello,
I have the same issue with the NavigationService.Refresh(). I see that the issue has been opened for more than 6 months. Any updates on this issue?
Thanks


Solve race condition between AThousandShips and Akien

Solves race condition between AThousandShips and Akien.
Solves https://github.com/godotengine/godot/pull/83705.

Thanks!


Remove the unused isStream property on various Streams

This property was added all the way back in PR #542, but hasn't actually been relied upon ever since PR #692.
Note that there's a isStream() utility function which replaced the property years ago, hence the isStream property is now dead code.

/botio test

/botio-linux preview

Thank you for the cleanup!


revert: unnecessary changes

Description
Reverts two changes introduced in #4205 which aren't really necessary.
Changelog

readds name in docker-compose.yml
reverts changes from tsconfig.json, this is handled in #4255

ok seems like this doesn't work as easily as I thought it would, I'll come back to this some other time 👀


User Can Edit Button Now

Fixes Issue
Closes #issue_number

Changes proposed

Screenshots

Checklist

[ ] You've linked this PR to the correct issue.
[ ] You have checked that the code is working correctly.
[ ] You ⭐ the repository!

Note to reviewers

@Souravvmishra, Please review this PR #1922


Html image not working.

So basically, i put a file in pfps/1.jpg. I did res.sendFile(__dirname + 'pfps/1.jpg'), and that worked. But when i do
let path = (__dirname + 'pfps/1.jpg')
res.send(<img src=${path}>), it does not work. the image does not load.

Hi @F1R3L1GHT, I could not reproduce your issue, res.send() is working correctly.
I assume __dirname will not fit for sending public URI for image as it will return internal server path that won't fit for putting it in src attribute.


fix(userspace/libscap): fixed loading of ebpf probe with offline CPUs

What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area libscap-engine-bpf
Does this PR require a change in the driver versions?
NOPE
What this PR does / why we need it:
Revert a bug introduced in #374: use same code used by kmod engine to properly load all CPUs and online CPUs, to be later able to properly count online CPUs.
Which issue(s) this PR fixes:
Fixes #720
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

fix(libscap): fixed loading of ebpf probe with offline CPUs

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/cc @gnosek @Andreagit97

/milestone 0.10.0

The if after the for loop is still wrong https://github.com/falcosecurity/libs/pull/721/files#diff-12833abd4271488260dae0ba178c6ad3f0bc63642f793a20b06ab4eb10d02cf9R1565-R1568 and it is the original cause of the strange log in the Falco issue, we should print online_cpu not i :point_down:
	if(online_cpu != handle->m_dev_set.m_ndevs)
	{
		snprintf(handle->m_lasterr, SCAP_LASTERR_SIZE, "processors online: %d, expected: %d", online_cpu, handle->m_dev_set.m_ndevs);
		return SCAP_FAILURE;
	}

Great catch!

Fixed!

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: daebbeb87d639c7edac3be197313b9da9df85777

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Update and improve API documentation

A few parts of the API documentation was not clear enough.
Added extra details and examples.

@rerobika I've did a bit of update (around the jerry_string_to_char_buffer method)

Still LGTM.


FailureActions.AndPauseProcessing(TimeSpan) doesn't seem to be working correctly

FailureActions.AndPauseProcessing(TimeSpan) doesn't seem to be working correctly.
My setup looks like this
options.LocalQueueFor<ThisMeansTrouble>().Sequential();
options.OnException<Exception>()
    .Requeue().AndPauseProcessing(30.Seconds());

But my log output shows the message being reprocessed immediately before it's eventually dead-lettered:
16:25:36 fail: Repro.ThisMeansTrouble[105]
      Failed to process message Repro.ThisMeansTrouble#018e62e7-b65a-4853-b0f0-c46c04f5d457 from local://repro.thismeanstrouble/
      System.Exception: Exception of type 'System.Exception' was thrown.
         at Repro.UnreliableHandler.Handle(ThisMeansTrouble message) in /Users/robert.dusek/Desktop/Repro/UnreliableHandler.cs:line 9
         at Internal.Generated.WolverineHandlers.ThisMeansTroubleHandler986978479.HandleAsync(MessageContext context, CancellationToken cancellation)
         at Wolverine.Runtime.Handlers.Executor.ExecuteAsync(MessageContext context, CancellationToken cancellation)
16:25:36 info: Wolverine.Runtime.WolverineRuntime[0]
      Requeue for message 018e62e7-b65a-4853-b0f0-c46c04f5d457 of message type Repro.ThisMeansTrouble
16:25:36 fail: Repro.ThisMeansTrouble[105]
      Failed to process message Repro.ThisMeansTrouble#018e62e7-b65a-4853-b0f0-c46c04f5d457 from local://repro.thismeanstrouble/
      System.Exception: Exception of type 'System.Exception' was thrown.
         at Repro.UnreliableHandler.Handle(ThisMeansTrouble message) in /Users/robert.dusek/Desktop/Repro/UnreliableHandler.cs:line 9
         at Internal.Generated.WolverineHandlers.ThisMeansTroubleHandler986978479.HandleAsync(MessageContext context, CancellationToken cancellation)
         at Wolverine.Runtime.Handlers.Executor.ExecuteAsync(MessageContext context, CancellationToken cancellation)
16:25:36 fail: Wolverine.Runtime.RemoteInvocation.FailureAcknowledgementHandler[0]
      Received failure acknowledgement on reply for message 018e62e7-b65a-4853-b0f0-c46c04f5d457 from service Repro with message 'Moved message 018e62e7-b65a-4853-b0f0-c46c04f5d457 to the Error Queue.
      System.Exception: Exception of type 'System.Exception' was thrown.
         at Repro.UnreliableHandler.Handle(ThisMeansTrouble message) in /Users/robert.dusek/Desktop/Repro/UnreliableHandler.cs:line 9
         at Internal.Generated.WolverineHandlers.ThisMeansTroubleHandler986978479.HandleAsync(MessageContext context, CancellationToken cancellation)
         at Wolverine.Runtime.Handlers.Executor.ExecuteAsync(MessageContext context, CancellationToken cancellation)'
16:25:36 info: Wolverine.Transports.Local.DurableLocalQueue[0]
      Pausing message listening at local://repro.thismeanstrouble/
16:25:36 fail: Wolverine.Runtime.WolverineRuntime[108]
      Envelope Envelope #018e62e7-b65a-4853-b0f0-c46c04f5d457/CorrelationId=83bad262b7a9da89a6da85972c41672f (ThisMeansTrouble) from Repro to local://repro.thismeanstrouble/ was moved to the error queue
      System.Exception: Exception of type 'System.Exception' was thrown.
         at Repro.UnreliableHandler.Handle(ThisMeansTrouble message) in /Users/robert.dusek/Desktop/Repro/UnreliableHandler.cs:line 9
         at Internal.Generated.WolverineHandlers.ThisMeansTroubleHandler986978479.HandleAsync(MessageContext context, CancellationToken cancellation)
         at Wolverine.Runtime.Handlers.Executor.ExecuteAsync(MessageContext context, CancellationToken cancellation)

Wolverine 2.1.2 & Marten 7.4.0

Before we call this a bug, what's the full setup you have for error handling? The tests for this functionality are happily passing right now. Are you sure some other error policy isn't kicking in first?

There's no other error policies configured, here's my whole Wolverine setup:
builder.Host.UseWolverine(options =>
{
    options.LocalQueueFor<ThisMeansTrouble>().Sequential();
    options.OnException<Exception>()
        .Requeue().AndPauseProcessing(30.Seconds());

    options.Policies.AutoApplyTransactions();
    options.Policies.UseDurableLocalQueues();
    options.Policies.UseDurableOutboxOnAllSendingEndpoints();
});

There was a test for this using Rabbit MQ, but the mechanics are different for local queues. I've got a failing test now

Race condition. Should be pause, then requeue after the listener is paused.

Not just a race condition

Got it. Brought to light some other internal flaws too. Good times. Fix coming in 2.2.0.
@robertdusek Thanks for your patience with these things!

@jeremydmiller
Thanks for taking a look at this. Unfortunately I'm still seeing (different) errors after updating to Marten 7.6 and Wolverine 2.2.1.
I call the handler that throws:
16:51:45 fail: Repro.ThisMeansTrouble[105]
      Failed to process message Repro.ThisMeansTrouble#018ebfb2-1db5-4d6c-8536-a8e2dab1c872 from local://repro.thismeanstrouble/
      System.Exception: Exception of type 'System.Exception' was thrown.
         at Repro.UnreliableHandler.Handle(ThisMeansTrouble message, ILogger`1 logger) in /Users/robert.dusek/Desktop/Repro/UnreliableHandler.cs:line 10
         at Internal.Generated.WolverineHandlers.ThisMeansTroubleHandler986978479.HandleAsync(MessageContext context, CancellationToken cancellation)
         at Wolverine.Runtime.Handlers.Executor.ExecuteAsync(MessageContext context, CancellationToken cancellation) in /home/runner/work/wolverine/wolverine/src/Wolverine/Runtime/Handlers/Executor.cs:line 164

The queue is paused and the message is requeued, but Wolverine detects it as a duplicate message:
16:51:45 info: Wolverine.Transports.Local.DurableLocalQueue[0]
      Pausing message listening at local://repro.thismeanstrouble/
16:51:45 info: Wolverine.Runtime.WolverineRuntime[0]
      Requeue for message 018ebfb2-1db5-4d6c-8536-a8e2dab1c872 of message type Repro.ThisMeansTrouble
16:51:45 fail: Wolverine.Runtime.WorkerQueues.DurableReceiver[0]
      Duplicate incoming envelope detected
      Wolverine.Persistence.Durability.DuplicateIncomingEnvelopeException: Duplicate incoming envelope with message id 018ebfb2-1db5-4d6c-8536-a8e2dab1c872
         at Wolverine.RDBMS.MessageDatabase`1.StoreIncomingAsync(Envelope envelope) in /home/runner/work/wolverine/wolverine/src/Persistence/Wolverine.RDBMS/MessageDatabase.Incoming.cs:line 78
         at Wolverine.Runtime.WorkerQueues.DurableReceiver.receiveOneAsync(Envelope envelope) in /home/runner/work/wolverine/wolverine/src/Wolverine/Runtime/WorkerQueues/DurableReceiver.cs:line 275
16:51:45 fail: Wolverine.Runtime.WolverineRuntime[0]
      Error while trying to retry Envelope #018ebfb2-1db5-4d6c-8536-a8e2dab1c872/CorrelationId=2d1abc3e4cf7433cc9341846f4597ec4 (ThisMeansTrouble) from Repro to local://repro.thismeanstrouble/
      System.NullReferenceException: Object reference not set to an instance of an object.
         at Wolverine.Runtime.WorkerQueues.DurableReceiver.<>c.<.ctor>b__15_2(Envelope env, CancellationToken _) in /home/runner/work/wolverine/wolverine/src/Wolverine/Runtime/WorkerQueues/DurableReceiver.cs:line 73
         at Wolverine.Util.Dataflow.LambdaItemHandler`1.ExecuteAsync(T message, CancellationToken cancellation) in /home/runner/work/wolverine/wolverine/src/Wolverine/Util/Dataflow/RetryBlock.cs:line 23
         at Wolverine.Util.Dataflow.RetryBlock`1.PostAsync(T message) in /home/runner/work/wolverine/wolverine/src/Wolverine/Util/Dataflow/RetryBlock.cs:line 94

The queue is restarted and the message is reprocessed, the exception is thrown and the queue pauses again:
16:51:45 info: Wolverine.Runtime.Agents.NodeAgentController[0]
      Successfully started agent wolverinedb://default/ on Node 2
16:51:45 info: Wolverine.Runtime.WolverineRuntime[0]
      Successfully started agent wolverinedb://default/ on node 2
16:51:50 info: Wolverine.RDBMS.DurabilityAgent[0]
      Issuing a command to recover 1 incoming messages from the inbox to destination local://repro.thismeanstrouble/
16:51:50 warn: Repro.UnreliableHandler[0]
      Handler called
16:51:50 fail: Repro.ThisMeansTrouble[105]
      Failed to process message Repro.ThisMeansTrouble#018ebfb2-1db5-4d6c-8536-a8e2dab1c872 from local://repro.thismeanstrouble/
      System.Exception: Exception of type 'System.Exception' was thrown.
         at Repro.UnreliableHandler.Handle(ThisMeansTrouble message, ILogger`1 logger) in /Users/robert.dusek/Desktop/Repro/UnreliableHandler.cs:line 10
         at Internal.Generated.WolverineHandlers.ThisMeansTroubleHandler986978479.HandleAsync(MessageContext context, CancellationToken cancellation)
         at Wolverine.Runtime.Handlers.Executor.ExecuteAsync(MessageContext context, CancellationToken cancellation) in /home/runner/work/wolverine/wolverine/src/Wolverine/Runtime/Handlers/Executor.cs:line 164
16:51:50 info: Wolverine.Transports.Local.DurableLocalQueue[0]
      Pausing message listening at local://repro.thismeanstrouble/
16:51:50 info: Wolverine.Runtime.WolverineRuntime[0]
      Requeue for message 018ebfb2-1db5-4d6c-8536-a8e2dab1c872 of message type Repro.ThisMeansTrouble

Then immediately the following entries start to repeat:
16:51:50 fail: Wolverine.Runtime.WorkerQueues.DurableReceiver[0]
      Unexpected failure
      System.ArgumentOutOfRangeException: Erroneous persistence of an incoming envelope to 'any' node (Parameter 'Envelope')
         at Wolverine.RDBMS.MessageDatabase`1.StoreIncomingAsync(Envelope envelope) in /home/runner/work/wolverine/wolverine/src/Persistence/Wolverine.RDBMS/MessageDatabase.Incoming.cs:line 53
         at Wolverine.Runtime.WorkerQueues.DurableReceiver.receiveOneAsync(Envelope envelope) in /home/runner/work/wolverine/wolverine/src/Wolverine/Runtime/WorkerQueues/DurableReceiver.cs:line 275
         at Wolverine.Runtime.WorkerQueues.DurableReceiver.executeWithRetriesAsync(Func`1 action) in /home/runner/work/wolverine/wolverine/src/Wolverine/Runtime/WorkerQueues/DurableReceiver.cs:line 303
16:51:50 info: Wolverine.RDBMS.DurabilityAgent[206]
      Recovered 1 incoming envelopes from storage
16:51:50 info: Wolverine.RDBMS.DurabilityAgent[0]
      Successfully recovered 1 messages from the inbox for listener local://repro.thismeanstrouble/
16:51:50 fail: Wolverine.Runtime.WorkerQueues.DurableReceiver[0]
      Unexpected failure
      System.ArgumentOutOfRangeException: Erroneous persistence of an incoming envelope to 'any' node (Parameter 'Envelope')
         at Wolverine.RDBMS.MessageDatabase`1.StoreIncomingAsync(Envelope envelope) in /home/runner/work/wolverine/wolverine/src/Persistence/Wolverine.RDBMS/MessageDatabase.Incoming.cs:line 53
         at Wolverine.Runtime.WorkerQueues.DurableReceiver.receiveOneAsync(Envelope envelope) in /home/runner/work/wolverine/wolverine/src/Wolverine/Runtime/WorkerQueues/DurableReceiver.cs:line 275
         at Wolverine.Runtime.WorkerQueues.DurableReceiver.executeWithRetriesAsync(Func`1 action) in /home/runner/work/wolverine/wolverine/src/Wolverine/Runtime/WorkerQueues/DurableReceiver.cs:line 303
16:51:50 fail: Wolverine.Runtime.WorkerQueues.DurableReceiver[0]
      Unexpected failure
      System.ArgumentOutOfRangeException: Erroneous persistence of an incoming envelope to 'any' node (Parameter 'Envelope')
         at Wolverine.RDBMS.MessageDatabase`1.StoreIncomingAsync(Envelope envelope) in /home/runner/work/wolverine/wolverine/src/Persistence/Wolverine.RDBMS/MessageDatabase.Incoming.cs:line 53
         at Wolverine.Runtime.WorkerQueues.DurableReceiver.receiveOneAsync(Envelope envelope) in /home/runner/work/wolverine/wolverine/src/Wolverine/Runtime/WorkerQueues/DurableReceiver.cs:line 275
         at Wolverine.Runtime.WorkerQueues.DurableReceiver.executeWithRetriesAsync(Func`1 action) in /home/runner/work/wolverine/wolverine/src/Wolverine/Runtime/WorkerQueues/DurableReceiver.cs:line 303

Thanks again for all your help with this!

Hey guys, if you put a comment on a closed issue, there's a less than zero chance I'll ever see it. Open a new issue or reopen this one.


Can't view dataframe in data viewer while debugging "Cannot read properties of undefined (reading 'disposed')"

Applies To

[ ] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
When debugging a python file (OS : Windows, Environnement : Anaconda), right clicking on a numpy array or a pandas dataframe in the "variables" side panel offers the option to "view the value in the data viewer" (it might not be the exact words, my vscode install is configured in another language).
When I click on it, an error appears : "Cannot read properties of undefined (reading 'disposed')". And nothing else happens.
I tried with both the prerelease and commercial versions of Jupyter, to no avail.
In the Jupyter logs, "xxxx" is my Windows session username
Here is my lanch.json code for the debugging configuration I'm using :
{     "version": "0.2.0",     "configurations": [         {             "name": "Python : fichier actif",             "type": "python",             "request": "launch",             "program": "${file}",             "console": "integratedTerminal",             "justMyCode": false         }     ] }
VS Code Version
Version : 1.75.1 (user setup) Validation : 441438abd1ac652551dbe4d408dfcec8a499b8bf Date : 2023-02-08T21:32:34.589Z Electron : 19.1.9 Chromium : 102.0.5005.194 Node.js : 16.14.2 V8 : <IP_ADDRESS>-electron.0 Système d’exploitation : Windows_NT x64 10.0.19044 Sandboxé : No
Jupyter Extension Version
v2023.1.2010391206 AND v2023.2.1000461014
Jupyter logs
info 17:57:03.945: Found debugAdapterPython on Debug Configuration to use
info 17:57:04.764: Process Execution: > c:\Anaconda3\python.exe -c "import pandas;print(pandas.__version__)"
> c:\Anaconda3\python.exe -c "import pandas;print(pandas.__version__)"
error 17:57:05.365: [TypeError: Cannot read properties of undefined (reading 'disposed')
	at Zh (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:17:165040)
	at ef.getDataFrameInfo (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:17:165522)
	at async Fk.ensureInitialized (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:24:519924)
	at async Fk.getDataFrameInfo (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:24:518749)
	at async Ek.onVariablePanelShowDataViewerRequest (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:24:510752)
	at async s.h (d:\xxxx\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:96:108008)]
warn 17:57:05.366: DataScience Error [TypeError: Cannot read properties of undefined (reading 'disposed')
	at Zh (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:17:165040)
	at ef.getDataFrameInfo (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:17:165522)
	at async Fk.ensureInitialized (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:24:519924)
	at async Fk.getDataFrameInfo (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:24:518749)
	at async Ek.onVariablePanelShowDataViewerRequest (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:24:510752)
	at async s.h (d:\xxxx\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:96:108008)]

Coding Language and Runtime Version
Python 3.9.7
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
conda 4.10.3
Running Jupyter locally or remotely?
None

I think that callstack should be impossible. Annotating it with the real class names
safeExecuteSilently
	at Zh (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:17:165040)
PythonVariablesRequester#getDataFrameInfo
	at ef.getDataFrameInfo (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:17:165522)
JupyterVariableDataProvider#ensureInitialized
	at async Fk.ensureInitialized (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:24:519924)
at async Fk.getDataFrameInfo (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:24:518749)
at async Ek.onVariablePanelShowDataViewerRequest (d:\xxxx\.vscode\extensions\ms-toolsai.jupyter-2023.2.1000461014\out\extension.node.js:24:510752)
at async s.h (d:\xxxx\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:96:108008)]

JupyterVariableDataProvider calls into its variableManager here https://github.com/microsoft/vscode-jupyter/blob/48a9cbd766740772f4e2ee5446573a9466295b8a/src/webviews/extension-side/dataviewer/jupyterVariableDataProvider.ts#L170 and it got that with injection for @inject(IJupyterVariables) @named(Identifiers.ALL_VARIABLES)
The stack shows that it got to PythonVariablesRequester#getDataFrameInfo here https://github.com/microsoft/vscode-jupyter/blob/48a9cbd766740772f4e2ee5446573a9466295b8a/src/kernels/variables/pythonVariableRequester.ts#L75
But PythonVariablesRequester is not the type that should be injected for that interface, the registrations are set up here https://github.com/microsoft/vscode-jupyter/blob/48a9cbd766740772f4e2ee5446573a9466295b8a/src/kernels/serviceRegistry.node.ts#L119-L125

So the code should not call from JupyterVariableDataProvider to PythonVariablesRequester but somehow it did

it happens when debuggerVariables.active is false and kernelVariables are returned from the getter here. I got a repro by just commenting out the first return

I can't repro- if you could, it means that kernel was undefined at that point and I'm not sure why that would happen (or why debuggerVariables would say it's not active at this point)
But the interface clearly states that kernel can be undefined, and this case just isn't implemented in KernelVariables, so I'll fix that case and see if it helps the OP

I couldn't repro the original problem described, so I've optimistically marked it verified, but @sacha-hirsch please try out the latest prerelease and see if it's been fixed for you as well.

I have some news ! First, the bad one : with the newest release, the error message doesn't come up anymore... but nothing else happens. So this is still not resolved.
However, I noticed that this bug only happens when I have multiprocessing code running at some point earlier in the program (multiprocessing.Pool().map is called and resolved before the breakpoint where I'm peeking at the array) !
You can find attached two logs of the same program with the same breakpoint, one with multiprocessing enabled (the bug appears) and one with multiprocessing disabled (no bug, data viewer works perfectly).
The bug also disappears if the breakpoint is placed before the call of multiprocessing.Pool().map
So, I guess a better title for this issue is "dataviewer broken when multiprocessing is used earlier in the script"
I should have checked with somtehing closer to a minimal example before posting, sorry!
vscode_variable_peeking_bug_multiproc_enabled.txt
vscode_variable_peeking_no_bug_multiproc_disabled.txt

Thanks for the details, could you also include some sample code?

Here you go with a minimal example
Commenting line 14 will make the bug disappear
jupyter_bug_minimal_example.txt

I have the same problem too.
Only 20 rows of Pandas.Dataframe / the List can't display in Data Viewer.

Pay attention. I just find that the variables could view in Data Viewer if pool of mutliprocessing didn't shutdown.
Maybe it is a temporary solution.

I had the same problem, but, in my case multiprocessing was called by torch.utils.data.DataLoader. Setting num_workers=0 fixed it for me.

@leonmayer @bamurtaugh @hyepod @sacha-hirsch
I'm tryhing to replicate this issue with the code provided, unfortunately I cannot repro this.
Can someone please provide a simple sample to repro this issue.
When using the code provided by @sacha-hirsch it fails with the following error
  File "/Users/donjayamanne/.pyenv/versions/3.11.5/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/multiprocessing/queues.py", line 367, in get
    return _ForkingPickler.loads(res)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: Can't get attribute 'func' on <module '__main__' (built-in)>

Hello,
This is probably because my minimal code is not meant to be run in jupyter but as a classic python .py file.
This issue was probably categorized as "vscode-jupyter" because it deals with the dataviewer but it is first and foremost a python debugger issue, not a jupyter issue.
FYI I just restested the minimal code with python 3.11 and the last version of VScode, and the bug is still there. Calling the multiprocessing module somewhere in the code will break the debugger dataviewer for all the following code lines , even if meanwhile the multiprocessing call has been resolved.
Best of luck !

Hey @DonJayamanne, this issue might need further attention.
@sacha-hirsch, you can help us out by closing this issue if the problem no longer exists, or adding more information.