[Wave Collect] [Workflows] Fix disabling Delayed Submission in NewDot turns off Scheduled Submit instead of setting Instant Submit

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/42685
PROPOSAL:
Tests

[x] Verify that no errors appear in the JS console

Create new workspace in NewDot
Disable Delayed Submission
Workspace has Scheduled Submit enabled and 'Instantly' selected, on OldDot

https://github.com/Expensify/App/assets/21549771/fbc23ccc-3cb7-4fd6-9b1b-a90791918215
Offline tests

NA
QA Steps

[x] Verify that no errors appear in the JS console
Same as in tests

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/21549771/fbc23ccc-3cb7-4fd6-9b1b-a90791918215

MacOS: Desktop

So the autoreporting will never be turned off right?

Yes the PR is done now so I think we can proceed with the review here @parasharrajat

Lucien is ooo so I have updated it, can you please review @parasharrajat ?

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/rlinoz in version: 1.4.85-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/rlinoz in version: 1.4.85-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/rlinoz in version: 1.4.85-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.4.85-7 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Prerequisites

[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.

Criteria

[X] Reasonably well-known and widely used (e.g. if it's a GitHub project, it should have at least 100 stars and/or 50 forks)
[X] English interface (or at least English documentation)
[X] Latest stable version
[X] Full version (i.e. not a trial version)
[X] Fairly standard install (e.g. uses a version-specific download URL, no elaborate pre/post install scripts)

Name
gitu
Description
A TUI Git client inspired by Magit
Homepage
https://github.com/altsem/gitu
Download Link(s)
https://github.com/altsem/gitu/releases/download/v0.19.2/gitu-v0.19.2-x86_64-pc-windows-msvc.zip
Some Indication of Popularity/Repute
1500 ⭐
82 forks

Added in https://github.com/ScoopInstaller/Extras/pull/13175

Looks like it could be promoted into Main since completely fits criteria.

It only has 82 forks instead of 150. Not sure how important that is?

You are right, my mistake.
Еhen leaving it in Extras.


Add parameter selection for specialty plots

Adds error message to plot and filters the metadata from the streams.
@birdage @DanielJMaher please review

@birdage Your call on merge.

@birdage How much do we want to leave in for you to clean when you get your hands in here?

@Bobfrat nj! Could we remove the large comment section here https://github.com/Bobfrat/ooi-ui/blob/plotting_updates/ooiui/static/js/views/common/SVGView.js#L140 as well pls :smile:

@birdage I couldnt update all of the this.$el.find( instances you pointed out, but i did where I could.

@Bobfrat thats perfect, i guessed you wouldn't be able to do them all

@birdage this one should be ready

:+1: will merge in a sec


[Feature request] Why torch.no_grad on CLIPVisionTower Foward

feature
In llava/model/multimodal_encoder/clip_encoder.py line 39, the forward pass of the vision encoder has torch.no_grad decorator. I am trying to do some input optimization, and I think this is stopping gradients from being back propped to the input image. Is there a reason for this no_grad? Would it be ok to remove it? (I am happy to make a PR if so :) )
Thanks in advance for any help with this!

Hi @LukeBailey181
Thanks for the feedback and for your interest in our project. You are right that this torch.no_grad is preventing you from doing input optimization. This maybe one of the overally cautious decorator I have used, to make sure that the vision encoder is not modified during pretraining/instruction tuning. Since we have vision_encoder.requires_grad_(False), this shall be fine.
It would be great if you can help create a PR about this, and we just want to make sure that (1) vision encoder is not modified in any way that we do not want; (2) the gradients do not backward through the vision encoder unnecessarily (for most of the use cases, including the standard pretraining and instruction tuning), unless we need that like you are doing input optimization.
Thank you!

how to optimize the vision encoder? which code should i modify?


Fix <0.12 Node support when used as a module

Support for Node versions <0.12 was fixed in e6c5a6ae0557fb718b8f2fefb17091b9db411a93, but that was only for when using Lebab in the command line.
This fix adds the same polyfill when Lebab is required as a module.

Thanks!


Check answers shouldn't show contact details when no details changed

Fix the check answers so that it doesn't show the contact details part of the table when it's just a case of not changing any details.

added cert no of 6 and then a code to look out for it and hide the unnecessary content


Bug: Issue in calculation of MI of unselected features with the previously selected feature in S

Can you please try the latest version of the code and report back if you still encounter the bug? Thanks!

I had tested the code changes and it worked fine for me.
Thanks,
Swapnil

Can you please try the latest version of the code and report back if you still encounter the bug? Thanks!

I tried, but the error was same.

Can you please try the latest version of the code and report back if you still encounter the bug? Thanks!

I applied the last version, the error is All-NaN slice encountered
S, F = self._add_remove(S, F, bn.nanargmax(xy_MI))
ValueError: All-NaN slice encountered


Run Report not fully rendering when phone screen is off

Summary:
Run Report details not fully rendering when phone screen is off
Steps to reproduce:

Start a game
Turn off phone screen/multitask
Complete the run
Run Report map shows up, but run details (e.g. pace, distance) do not

Expected behavior:
Run details should show up on run report
Additional notes:
Tested with apk on phone

Might be a dark mode issue:

After starting run, enable dark mode
When run report loaded, it'll run the dark mode state (all text white, blends into white background) and appears to be blank


Human friendly elapsed time in log

This pull request will convert elapsed time from seconds to minutes and seconds if it's more than 60 seconds, convert it to hours, minutes and seconds if it's more than 3600 seconds to contribute for more human readable output.

Vagrant chef-zero provisioner's elapsed time got longer ( https://github.com/mitchellh/vagrant/issues/5972 ) and that led to this PR.
That said,
Chef Client failed. 9 resources updated in 40 minutes 35 seconds

would be more human friendly than
Chef Client failed. 9 resources updated in 2435.332318955 seconds

I like this change.  I would suggest keeping elapsed_time as a function that returns end_time - start_time and moving the pretty printing into pretty_elapsed_time.  That'll be friendlier to formatters that might be subclasses of this and future users of this class.

@stevendanna pretty_elapsed_time was created and formatting was moved over there.

:+1: here

cc @chef/client-maintainers

@chef/client-maintainers @sethvargo @stevendanna Removed Timecop dependency and rebased on top of 3770ec1025fd09d3a3bb393ad955ee2985252a67

:+1:

:+1:

Rebased on top of 1ef5f566480ba84091a12f2b6c5e85f44af54a5b


IsFiles decorator issue

When your dto have IsFiles decorator and some Transform decorator at the same time, then Transform decorator's callback will call as much times as files was attached to the request.
I guess this is a bug and unexpected behavior

closed as refined in PR #41


Item tooltip with duplicate enchantments crashes client

Playing on Minecraft 1.20.1 using Forge 47.2.0 and Apotheosis 7.3.0
crash-2024-02-13_17.29.27-client.txt
Steps to Reproduce:

Run this command.


add ability to filter the kingdom list to the hearted items

this will be completed by the #25 task


[AIRFLOW-118] use targetPartitionSize as the default partition spec

https://issues.apache.org/jira/browse/AIRFLOW-118

The change is backward-compatible in cases where the num_shards is already set and that setting is still honored. But for cases where num_shards is not set, the default behavior will be using targetPartitionSize with the default parameter coming from http://druid.io/docs/latest/ingestion/batch-ingestion.html
@aoen @mistercrunch

@aoen fixed your comments, would you take another look?

LGTM, merging to master


scenario parameter

for the enable-rpimage there is a scenario switch.  The documentation doesn't specify the possible values for this parameter, can this become a parameter set and the documentation be updated for that parameter?  I'm happy to do a pull request, but I'm not sure what the parameter is used for, I am guessing it is for (Failover and Test, Failover and recover, etc...)

I can't remember if that was returned from the query and what are the possible results. Unfortunately, we no longer have RecoverPoint in our environment so I am no longer able to maintain this project. I hope you are able to use it as a good starting point for managing your RP environment.


Broken link: README.md introduction link broken

Reference: https://github.com/themesberg/flowbite-vue/blob/main/README.md?plain=1#L52.
The link when clicked, takes you to a 404 not found page.
Should link to: https://flowbite.com/docs/getting-started/introduction/.
Let me know if you want me to make a PR for this.

Thank you, fixed


thoughts on leveraging self-links with this release?

(forgive me, I haven't done much research into the viability of this, I'm part asking and part getting thoughts out)
any thoughts on a way to modify the docker job to provide self-referential links so docker image on separate docker/* deployment instances could pass address references to one another as peers?
... I guess this wouldn't really work since links only work in rendered template jobs, not as accessible values in job properties (e.g. the recipe: key), but I'll postulate this regardless
background
I'm curious about using a BOSH-orchestrated deployment of docker-splunk Heavy Forwarders for syslog and http endpoint collection. I'm running a dedicated k8s cluster for it right now, but I'm interested in moving it to being BOSH-managed to keep it in line with my standard BOSH deployment suite.
If the splunk images can be passed the addresses of their peers, they can work in a cluster. I might be able to finagle them talking to each other using links similar to how the minio-boshrelease has all the instances link to one another
thoughts welcome, i'll probably experiment with this over the next few weeks or months just to see what options there are. Thanks for any time. We can close this out whenever 👍

I'm curious to see where your experiments lead.  Cross-node communication was not an original design goal of this BOSH release, but it's a desirable one nonetheless.
I'm curious about your aversion to using a dedicated Kubernetes cluster.  I've been mostly going the opposite direction, where I want BOSH to only deploy Kubernetes and then migrate more of my BOSH-bound stuff to Kubernetes.

I had some old code lying around in a working copy that I never properly branchified.  One of these days I'll get better at git.
I pushed the WIP commit to the linky-linky branch, here: https://github.com/jhunt/containers-boshrelease/tree/linky-linky
The idea was that BOSH operators could build more complicated stuff by using the containers link, cross-job to at least facilitate discovery of IP address (or BOSH DNS names).  I haven't played with it on anything more advanced than a single VM type linking to its other instance group instances (see manifests/redis-cluster)
I'd love to use that branch as a staging area for this type of work, if you're still interested in the functionality @aegershman

I am, I can't get to it anytime obviously soon unfortunately, but can we leave this open for a few weeks and if I get some time I'll try to see what can be done with this? This could be really valuable.
I like this idea, if I'm understanding correctly the only thing is getting the content of that file which contains the values of the links on disk fed into params which are expecting those values "up front" and spoonfed into it rather than reading them from a file on disk... which I guess is a big "only thing", tbh.
There might be a way to interpolate those values into the rendering of a docker-compose.yml by introducing another small layer of interpolation, e.g. when / after docker-compose is rendered, another step could replace any (user-supplied) identifiers such as LINKY_LINKS with a corresponding value which comes from the 'real' <% link("...").ips => erb interpolation... you know what I mean?
I have some ideas; they might turn out to be total trash, but it might work. Let me goof on this just a bit a little later?

Take all the time you need.  I'd be curious what your concrete use case is; maybe I could find some time to hack on that solution for a bit, as well.
Keep me posted.

TL,DR; I don't think there's a rock-solid concrete use-case
So, my original thought on this was to introduce a hodge-podge interpolation step to the docker-compose template would be. Basically in the docker-compose.yml, in fields where you'd want to pass the addresses of all the other nodes in the deployment, you'd reference it as something like ${LINK_INSTANCES_ADDRESSES}.
And then right before the docker-compose.yml is actually used, a shell script would interpolate the docker-compose with those common values which you have access to through bosh erb. For example, ${LINK_INSTANCES_ADDRESSES} would be...
# I'm sure there's a more succinct way to do this
LINK_INSTANCES_ADDRESSES=<%= link("containers").instances.map { |i| "#{i.address}"}.join(",") %>

and then if your docker-compose.yml had ${LINK_INSTANCES_ADDRESSES} referenced in it, it'd be replaced with the value of q-xyz.q123.bosh,q-abc.q123.bosh,q-zzz.q123.bosh, and passed to the docker container as such. You definitely wouldn't have access to bosh erb's full range of templating and values, but perhaps some common attributes.
That's the idea, but to be honest I'm not jazzed about it or if it'd legitimately offer value that'd be used. My use case of having the splunk container image orchestrated together in a cluster is likely an edge-case, and honestly, it works fine as a cluster of standalone images operating independently. I think at a certain point of complexity and reliance, it's better to commit to operating a dedicated boshrelease for <whatever thing>-- or, like, working out an actual k8s strategy alongside bosh.
I'll go ahead and close this out; thanks for your time && for letting me talk out the idea and thought process 👍we can definitely reopen it to reconsider or talk it through more


Usage statistics download issue

On the Usage Statistics page, clicking the "Download all" button for "No. plans by template" doesn't download a file. In Chrome, an error page pops up: "dmptool.org is currently unable to handle this request.
HTTP ERROR 500".
The other download buttons work as expected.

Clicking "Download Monthly Usage" button at the top of the page also results in the same error.

Related to https://github.com/DMPRoadmap/roadmap/pull/2866
Fix for this will be released this Thursday. Apologies for the delay @wdahdul


Barriers doesn't block other tokens that are more than 1 cells away

For tokens besides barriers, the block work, but not for farther ones.

Fixed on 6c4c129.


centralize md instance as part of the normalized configuration

A bit of refactoring before addressing #92, and maybe reviving #702.

As I was working on #92 (now with PR #1037) I wanted to pass down an additional option to markdown ("cleanUrls"). I saw that we were creating a new instance of md for each page, with a root option that wasn't used at all, and a path option that was redundant (it could be read from the context). We were also calling markdownIt — the new option that adds custom plugins — once per page. All this seemed non-optimal on principle, and I didn't want to add another option on top without cleaning this up.
The optional md is there for some of the unit tests, I can give them a custom md instead to avoid hiding a bug.
Creating a new instance of md is fast, so this did not translate into visible gains in execution time.


Keystore finalization

Draft EIP 2333 has been started to be implemented by teams.
When should EIP 2333 status be moved to Last Call (then Accepted and Finalized)?
https://github.com/ethereum/EIPs/issues/2337#issuecomment-624384934 should also be answered.
IANAC (I'm not a cryptographer) and for above issue, what is the impact of sticking with draft0 vs draft2 (or a future draft if this same function is updated)?
Since EIP 2333 has a dependency on a draft IETF standard as mentioned in above comment, are there other precautions that implementers and users of such keystores should be aware of?

It would be nice to have a pass on 2333, 2334, 2335, 2386 and define a standard on-disk layout for wallets (I have a file somewhere around to do this) so that keys are truly interchangeable between clients.  Happy to be involved in this effort.

/cc @CarlBeek

We considered reusing our KeyStore implementation from the Nimbus Ethereum 1.0 codebase, but minor differences in the standards made this difficult. Bringing the requirements of Eth1 into the picture and considering a possible upgrade path that unifies the standards may be beneficial.

Should one of the EIPS also include this suggestion https://github.com/prysmaticlabs/prysm/issues/6078 ?

@ethers That's an implementation detail and shouldn't be part of an EIP.
EIP 2680 is up and provides a layout format.  Comments welcome.

2333 was updated https://github.com/ethereum/EIPs/issues/2337#issuecomment-646646620 so I'll close this.


Merge RetroLab with the JupyterLab Simple Interface?

Problem
The Simple Interface in JupyterLab has been around for a while, and was improved for the 3.0 release:

RetroLab was developed a couple of weeks before the 3.0 release, back in December 2020. The goal was to develop a notebook UI that looks like the classic notebook, but made with JupyterLab components. The main motivation was this issue: https://github.com/jupyterlab/jupyterlab/issues/8450
However as RetroLab matures and starts looking more and more like the classic notebook, we should consider merging the two efforts to offer a consistent frontend to the users.
Here is a screenshot comparing RetroLab to the Classic Notebook:

Proposed Solution
If we want to unify the Simple Interface and RetroLab, and eventually offer RetroLab as part of the JupyterLab main package, we should consider a few UI, UX and technical details.
Left, right and botton areas
For now RetroLab does not expose any left, right, or bottom area. This is on purpose, to keep the interface as simple as possible.
However the Simple Interface still gives access to these areas. Which can be convenient for example for the Table of Contents or the Debugger.
Ideally RetroLab should keep good defaults: as simple as possible by default. These areas can exist, but should be hidden by default. More advanced users can toggle them on if they want to.
RetroShell vs LabShell
This is slightly similar to the previous point. For now RetroLab uses a custom shell:
https://github.com/jupyterlab/retrolab/blob/1f86be020c17bc0e75e10074f6316f4ee313b287/packages/application/src/shell.ts#L35-L191
And a custom app:
https://github.com/jupyterlab/retrolab/blob/1f86be020c17bc0e75e10074f6316f4ee313b287/packages/application/src/app.ts#L21-L145
RetroLab already supports the prebuilt JupyterLab extensions: https://github.com/jupyterlab/retrolab#support-for-prebuilt-extensions-. Most of them work just fine. However if for example a third-party extension adds a widget to the left area, nothing happens in RetroLab.
Maybe we should look into using the same shell and app for both lab and retro? This would have the advantage of better compatibility with third-party extensions that expect some areas or component to be available.
Open in a new browser tab
It should be possible to open the notebooks, terminals and the file browser in different browser tabs.
Also this sounds like a minor detail, but there should still not be any splash screen in Retro / Simple Interface. A splash screen indicates this is a heavier app while in RetroLab we only expect to be browsing a "normal" web page.
Seamless switch between JupyterLab and RetroLab / Simple Interface
RetroLab ships with a prebuilt lab extension by default, which adds buttons to the notebook to easily switch between JupyterLab, RetroLab and the Classic Notebook.
In RetroLab:

In JupyterLab:

These are simple buttons, but they already let users easily switch between interfaces with a single click. We should iterate on that idea: https://github.com/jupyterlab/retrolab/issues/256
More generic way of opening JupyterLab widgets in new browser tabs?
This might be more of a long term experiment. It would be interesting to be able to open arbitrary widgets in new browser tabs. Taking the inspiration from the current RetroLab, but with more widgets than just the notebook, console, terminal and file editor.
Writing this here as something to keep in mind while we iterate on the other items.
Additional context
There have been a lot of discussions in https://github.com/jupyterlab/jupyterlab/issues/9869
Although RetroLab already looks and feels a lot like the classic notebook, a few concerns have also been expressed in https://github.com/jupyter/notebook/issues/6210.

Closing as the JEP proposing to make Notebook v7 based on the current RetroLab has now been merged: https://github.com/jupyter/enhancement-proposals/pull/79
Check out the full description of the JEP to learn more: https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html
Thanks all!


Change default value for Visible Layer in canvas item

Since tree chain is taken into account for the test of visible layer, changed the value to all layer active by default.
Fixes #93316

Bugsquad edit, see also: https://github.com/godotengine/godot/pull/93512

Changing the default value of an exposed property breaks compatibility, this also creates an inconsistency with VisualInstance3D which also only has visibility on the first layer, I'd say both or neither should be changed

Inconsistency with VisualInstance3D already exist as the behavior is not inherit in 3D (I updated the repro project to show the point)
Do you think the feature is usefull in the current state ? (For example you have to check the whole inheritance chain to make sure to enable layer manually for each, and imagne that for dynamically instanciated node)
Since this feature has been introduced fairly recently i think it should be done now.

Since this feature has been introduced fairly recently i think it should be done now.

Fairly recently? How do you mean? It was introduced in 4.0

Marked as an enhancement as there's noting broken here, just possibly less useful than it could be, the system is fully usable if you configure it as you need to, this might just make it a bit easier to do so, though I'm not convinced it does that either

I think your solution introduce much more work and a totally new behavior, it will never be done (and i think should never be done).
I guess we will see if someone really using the feature will comment (but i doubt anyone will find that due to the new classification).
My guess is that currently people are getting around this using RemoteTransform2D or other solution to synchronize node without parenting them (Because prior to that feature that's how people were doing)
So once again .... this will disappear because of hypothetical compatibility issue ... :confused:

it will never be done

What are you basing this on?

@AThousandShips I will get back to working on my actual project, i'm fine maintaining my own branch for change like that. But i'm a bit tired of proposal being rejected by user that never using them and in the name hypotetical solution that are not implemented (If you think the solution is better and could be done easily, i think you should make another PR).
I think having a Node looking upward in the arborescence to check if the propagation of an value is done is pretty unique in the design of the engine, but again my main work is as a user (not as a maintener) so maybe you're right.

But i'm a bit tired of proposal being rejected by user that never using them and in the name hypotetical solution that are not implemented

I'm sorry you've had that experience, but please don't apply it here to a change that breaks compatibility, and part of the process of development is discussing the benefits and drawbacks of specific solutions, I think it's more productive to approach problems with an open mind and avoid responding to suggestions with bitterness or dismissiveness based on such, when they're made in a constructive way

There, PR open, please see if this is useful for you as an alternative, it's pretty simple and gives a clear error message:

https://github.com/godotengine/godot/pull/93351

Gonna be honest, I relate to the issue at hand very much. It's a shame this can't be done right now, but it should be done somehow.
Also the existing documentation really needs to highlight this behavior, as it can be seen as an oddity.

Also the existing documentation really needs to highlight this behavior, as it can be seen as an oddity.

If does?

A Viewport will render a CanvasItem if it and all its parents share a layer with the Viewport's canvas cull mask.

Or should it be a Note?

I'm aware it does, but "and all its parents" is a very casual mention, and with no concrete example (unlike CollisionObject2D's collision_layer's description) it can be hard to wrap your head around it. Plus, Viewport's canvas_cull_mask is not linked properly.

Other solution has been explored but no proper fix has emerged. Could this be considered for 4.3 release (for the compatibility needs to be with a major release and mentioned in changelog)

This is for 4.4 at the earliest, if the compatibility breakage is accepted for a minor release

This is for 4.4 at the earliest, if the compatibility breakage is accepted for a minor release

That's why i was not very pleased by the change to dicussion/enhancement (as it was previously a bug fix for #93512 , i think making it eligible to 4.3). Statement is that the Visibility Feature is not easily usable in the current state (and not matching behavior with the 3D version)

It being called a bug doesn't automatically make it acceptable to do compatibility breakage, it should be avoided in favour of changes not breaking compatibility, which for this there are alternatives that don't
But regardless it won't be in 4.3, as we're very late in the release cycle for such a drastic change

For a complete solution I'd say to have a three stage improvement:

First add a node warning to help diagnose this problem, this doesn't make it easier to work with in a nested hierarchy though
Add support for inheriting the layers to simplify the workflow
And finally at some future point (consider) changing the default value to create a more useful starting point

Ok i'll give up on that and will just maintain my own branch with that simple fix on the side.
Again, please consider listening to people using the real feature for making priority.
#93512 should be in Draft state IMO because it's not adressing the issue at the moment (Uploaded a test project to prove that in the PR discussion)
As stated in previous discussion the no-inheritance idea looks a bit complex and maybe not the greatest idea due to Y-Sorting.
The solution proposed in #93512 implies maintaining 2 behavior, as stated in the PR i think it's also a bad idea for maintenance reason (change to Y-Sorting for example would be a big problem).
For those reason i think the simplest solution to fix the problem without impacting other project is this one.
For the compatibility, as i mentionned earlier i think this is a false problem. Since this issue has never been mentionned earlier i think nobody is using this (or if people are using they already manually setted most of the value so the change on default value will not be a problem).
For the "controversy", i don't think that anyone using this feature has raised a flag here so the only controversy is on the engine developer side.

We are just asking for patience. Godot 4.3 is already way overdue, and is currently at a stage where we only focus on release blocking bugs. Release blocking bugs are typically regressions which would break 4.2 projects when migrating to 4.3.
This isn't the case for the issue you want to address, which exists in 4.2.stable and likely earlier versions too. I understand you want it fixed sooner than later, but we have limited resources and we need to be able to prioritize different things at different stages of development.
Once 4.3 is released, we can look deeper into this issue and whether the proposed solution is good. Until then, you and anyone interested can indeed use this solution in your own fork.

The other linked PR is related because it is part of a broader discussion and different approaches, it doesn't mean it is a replacement for this, or anything else than that it's related, what's the problem with it being referenced? Just leave it be

The other linked PR is related because it is part of a broader discussion and different approaches, it doesn't mean it is a replacement for this, or anything else than that it's related, what's the problem with it being referenced? Just leave it be

Please stay respectfull, i'm trying to sell this solution (because it's the one actually solving an issue in my dev process) so new people coming here understand that the other PR is not solving the issue. (Because i was confused myself reading the other PR as i told in the censored message)


Novels in source "FastNovel" doesn't show any chapters

Steps to reproduce
Open FastNovel
Select a novel (Favourited or not Favourited)
Expected behavior
When opening a source, in this case "FastNovel" and selecting the novel you want whether or not you have it Favourited in the library it should show the content of the novel aka chapters.
Actual behavior
When opening source, "FastNovel" and selecting the novel you want whether or not you have it Favourited in the library it doesn't show any chapters and when you try to update the library it doesn't update anything of the source "FastNovel"
LNReader version
1.1.17
Android version
Android 9
Device
Resmi Y2 (S2)
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with a source, I should be opening an issue in the sources repository.
[X] I have updated the app to version 1.1.17.
[X] I will fill out all of the requested information in this form.

Write it in the source section https://github.com/lnreader/lnreader-sources/issues/new/choose

If this is an issue with a source, I should be opening an issue in the sources repository.


introduce aframe deploy command: deploying project to static CDN

added aframe deploy, using IPFS, in PR #45


Node crashes due to pure virtual method being called

Description
Caught signal 11 (SIGSEGV) Stack Trace:  pure virtual method called terminate called without an active exception Caught signal 6 (SIGABRT)
Environment
Docker image
Node version
docker-pullable://gcr.io/jovial-meridian-249123/taraxa-node-develop@sha256:fbf392ebfe2e538c8c033f0c9d247dec470eadc912bcf73cf96384095dd969b9

docker images --format '{{.ID}}' 'taraxa/taraxa-node:latest'

Operating System details.
CPU, memory, disk details.
NOTE: In many cases log files are also useful to include. Since these files may be large, a Taraxa developer may request them later. These files may include public addresses that you're participating with. If that is a concern please be sure to scrub that data.
Steps to reproduce

Run node for a while
Wait for crash :-)

Needs testing, but should be fixed in #729 due to a pure virtual method being called inside of a destructor within taraxa-aleth


npm warnings

You might want to upgrade package.json to get rid of these:
npm WARN deprecated<EMAIL_ADDRESS>Babel 5 is no longer being maintained. Upgrade to Babel 6.
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>(when installing skeleton-es2016)

I'm closing this because we are aware of the issue and have publicly blogged about the problem. This relates to the fact that Babel's sloppy move from v5 to v6 broke a ton of tooling and even removed features from the language. We are waiting for them to fix all the issues before we update.

@fractalf you get the fsevents warnings because fsevents is supported only on OS X.


Live Stitch

Hello thanks for this nice project
Is it possible to use ashlar to live stitch when acquisiton frames while scanning the tissue ?

Not as currently designed -- the current architecture assumes all of the tiles are available up front. You could probably use some of the building blocks in utils.py to implement live stitching, but it would be very dependent on your specific experimental setup.


feat: overlays

This is going to change with rc0 - but it will just be moving it into a the single config, lets hold until rc0 update is done


The speed of Dataloader when using DeepSpeed

System Info
{
    "communication_data_type": "fp32",
    "bf16": {
        "enabled": true
    },
    "fp16": {
        "enabled": false,
        "auto_cast": true,
        "loss_scale": 0.0,
        "initial_scale_power": 32,
        "loss_scale_window": 1000,
        "hysteresis": 2,
        "min_loss_scale": 1
    },
    "zero_optimization": {
        "stage": 2,
        "allgather_partitions": true,
        "allgather_bucket_size": 5e8,
        "overlap_comm": false,
        "reduce_scatter": true,
        "reduce_bucket_size": "auto",
        "contiguous_gradients": true,
        "offload_optimizer": {
            "device": "none"
        },
        "offload_param": {
            "device": "none"
        }
    },
    "gradient_accumulation_steps": 1,
    "gradient_clipping": "auto",
    "train_batch_size": 64,
    "train_micro_batch_size_per_gpu": 32,
    "steps_per_print": 2000
}

Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[X] My own task or dataset (give details below)

Reproduction
When I run the code with DeepSpeed as follow, although GPU memory consumption decreases, loading 64 data samples takes around 7 seconds, whereas without DeepSpeed, loading 64 data samples takes less than 3 seconds.
deepspeed_plugin = DeepSpeedPlugin(zero_stage=2, gradient_accumulation_steps=config.training.gradient_accumulation_steps)
accelerator = Accelerator(
        gradient_accumulation_steps=config.training.gradient_accumulation_steps,
        mixed_precision=config.training.mixed_precision,
        log_with="wandb",
        deepspeed_plugin=deepspeed_plugin,
        logging_dir=config.experiment.logging_dir,
        split_batches=True,  # It's important to set this to True when using webdataset to get the right number of steps for lr scheduling. If set to False, the number of steps will be devide by the number of processes assuming batches are multiplied by the number of processes
    )
train_dataloader = CC3mDataLoader(train_dataset, batch_size=total_batch_size_without_accum, shuffle=shuffle)
model, optimizer, train_dataloader, lr_scheduler = accelerator.prepare(model, optimizer, train_dataloader, lr_scheduler)```

### Expected behavior

How can I reduce the data loading time while loading the same number of data samples when using DeepSpeed?

Hello, does this happen with Multi GPU DDP too? Want to confirm if you are comparing single GPU training with Multi GPU DeepSpeed training.


Improve mbio viz refactor implementation

Addresses #1164 and #1163.
Things done up to this point:

plugins, as applicable, create a default configuration within the plugin.
type guards have been added to remove all @ts-ignore statements
unnecessary comments, console logs, and imports have been removed
made adjustments to remove React or MUI warnings from console (however, a pesky React key warning remains in StartPage)

Apologies in advance that this became a bit of a behemoth of a PR.


Pluggable: BasePrice and QuotePrice can be less than zero

In this commit we introduced a validation check on the Price domain https://github.com/tdex-network/tdex-daemon/commit/ebfe465a1c8b5f111385a7383d55f475e94f6a35#diff-4d41ed4b84fbbf1a8d096677eb4767a6976b057cfa37f81e89111b502a488390R126-R131 that is conceptually wrong: the prices can def be less than zero

We should check instead they are at least one satoshi tho

Closed by #457.


fixes schema merge behavior

Description

defines schemas, tables and column merge behavior
add case insensitive naming convention to weaviate
does not add default hints to columns

@sh-rp fixed the debug prints and merging


Registry objects not removed from S3 on deletion

Bug description 🐞
I have created several test modules on the Terrakube Registry and later deleted them. After deletion, the objects for the deleted module persist in our S3 bucket that Terrakube uses for storage.
If a module is completely removed from Terrakube, it seems like it should also be removed completely from S3 or whatever backend storage is being used.
Steps to reproduce
Create module in Registry in Terrakube.
Delete module through UI
Look in storage - the module objects still exist.
Expected behavior
Objects in storage should get deleted when a module is deleted in Terrakube
Example repository
No response
Anything else?
No response

Partially fixed by
https://github.com/AzBuilder/terrakube/pull/538
Azure/GCP will be added later


Bug Report

This one have no use AO

This one use KinoObscurance

This one use Screen Space Ambient Obscurance
Thank you for your codes they are so much helpfull  to improve every frame effect beautfull and quickly. But steel have some problems.
My hari shader uses Dithered Alpha and Deferred Renderging and receve Light Attenuation, maybe because of the shadow or other something.

Thanks for reporting! Would you mind providing me a minimum project that can reproduce this issue? I'd like to check the details.

@keijiro Thanks your help, I'll letter to your Gmail, named (Hair KinoObscurance).
Thanks again.

Thanks for providing the project! I looked into it, and found that the hair shader doesn't provide information that is needed to render depth normals texture.
It seems you're using ShaderForge. Please read the following issue report. This explains what's happening in your project.
https://shaderforge.userecho.com/topics/896-proper-depth-depth-normal-rendering/
I fixed the issue by adding few lines to the shader and tweaking the settings a little bit. I'll send you the fixed project later.

Very kind of you, those days I have so many works to complet. Sorry for reply so later.
Yes the shader is use ShaderForge created. I have no idea how to remove the problem. Thank you for your help heartfeltly.
Good luck always with you.
PS: Waiting for your projects.

@johnartune I've sent the project to you on 4th Nov. Check your inbox, or spam filter :)


[BUG??] FIRAnalyticsVersionMismatch

Hi, its me again. All is working perfect, i only have a incompatibility between your plugin and other plugin.
Describe the bug
I added your plugin which is working incredibly good in iOS & Android. My problem now is that i've also a Firebase plugin. Using both plugins, give me a crash only on iOS, and it's because both uses FIRAnalytics but with different versions.
To Reproduce
Steps to reproduce the behavior:

Add your plugin.
Add Firebase Plugin.
Compile on iOS.
See error

I'm just wondering if there's some file where i can change the number of version or something like that. I open many files on both plugins, but i dont found anything. I find GoogleAppMeasurement folders, but i cant change version, or maybe i dont know where or with which software.
Here it's the exact line of error:
*** Terminating app due to uncaught exception 'FIRAnalyticsVersionMismatch', reason: 'Google Analytics for Firebase version (70100000) does not match with Google App Measurement (80901000) version. Please update.'
Thank you!

Hi, hmmm, instead of using the https://github.com/Poing-Studios/godot-admob-ios/releases/tag/v2.0.4 "googlemobileadssdkios.zip" that we provide, try to use Cocoapods
This should work: https://cocoapods.org/pods/Google-Mobile-Ads-SDK
I never tried to use the Firebase Plugin, can you give me details which plugin is it? The link of repository
A sample project would be great

Thank you gumaciel.
I have chosen to download from windows the latest version of Admob SDK, as you said.
I see that your plugin allows you to insert the SDK manually, which makes it dynamic. The other plugin (Firebase) doesn't seem to allow dynamically configuring the SDK, as apparently a part of it has files packed by the programmer.
I see that your plugin works correctly, so there is not much I can tell you. It's something related to another plugin so I'm going to put my focus on seeing what I can do there, although I don't think much more than what the plugin itself allows me.
I leave you the Firebase plugin, in case someone asks about this at least you know where the problem can come from. I appreciate the help provided. The topic can be closed.
https://github.com/DrMoriarty/godot-firebase-analytics


Removed unused functions

Proposed change
This PR removes the unused entry parameter from the async_setup_entry function in the Abode integration. This change improves code maintainability by addressing the python:S1172 issue flagged by code analysis tools and removes unnecessary elements from the function signature.
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Deprecation (breaking change to happen in the future)
[ ] Breaking change (fix/feature causing existing functionality to break)
[x] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the [development checklist][dev-checklist]
[x] I have followed the [perfect PR recommendations][perfect-pr]
[x] The code has been formatted using Ruff (ruff format homeassistant tests)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for [www.home-assistant.io][docs-repository]

Respected Professor
Thank you for your detailed feedback on my pull request. I would like to address your concerns and provide additional context regarding the scope and challenges faced during this submission.
Regarding the Scope of the PR:
The PR aimed to address six cases of unused parameters across various functions, primarily in the Abode integration. The changes targeted a specific issue flagged by SonarQube (python:S1172), identifying unused parameters like entry, perm_lookup, and config in functions such as async_setup_entry and lookup_all. My intention was to improve maintainability and clarity by removing these redundant parameters.
However, I recognize that including changes across six different files in a single PR can dilute its focus, making it harder to review and increasing the likelihood of unintended inclusions. While all the changes aligned with the overarching goal of addressing unused parameters, they spanned multiple contexts, which I now understand is less than ideal for collaborative workflows.
Challenges Encountered
When preparing the PR, I intended to address only the specific unused parameters in each function. However, while pushing the changes, I inadvertently included other changes that were not initially part of the plan. This resulted in a broader impact on the codebase than anticipated. While the issue did not add unrelated functionality, it created confusion about the PR's intended scope.
Additionally, some challenges arose from CI/CD checks, where several steps, including ruff-format and pylint, flagged issues that required resolution. These challenges delayed the process and emphasized the need to better validate my changes before submission.
Regarding Focus on Specific Files:
Despite affecting six files, my primary focus remained consistent: addressing unused parameters to improve maintainability.
The changes were applied to the following files in the Abode integration:
Abode Camera Devices: Removed the unused entry parameter.
Abode Binary Sensor Devices: Removed the unused entry parameter.
Abode Alarm Control Panel Device: Removed the unused entry parameter.
Abode Cover Devices: Removed the unused entry parameter.
Permission Lookup (lookup_all): Removed the unused perm_lookup parameter.
Abode System Setup: Removed the unused config parameter.
These files reflect the targeted scope described in my refactoring report. The changes aimed to address the same issue across different functions but, due to their spread across multiple files, inadvertently created the perception of a broader focus.
Thank you for your feedback, which has been invaluable in improving my approach to code contributions. I appreciate the opportunity to learn from this experience and refine my skills in maintaining focus and clarity in collaborative development projects.
Best regards,
Hari Veera Mani Kumar Vallu

This is the new PR link which I have updated the new file
https://github.com/PA2558-SEMP/home-assistant-core/pull/142


Track Paper builds

Is your feature request related to a problem? Please describe.
Right now the current image for 1.14.2 contains paper build v58, while the current build is v68
Describe the solution you'd like
Ideally, TravisCI could publish updated builds as they're available (or perhaps just republish frequently/daily)
It would be too much to ask for you to do this manually, but 1.14.2 is evolving quickly and bug and performance fixes are being released often, and it would be nice to stay up-to-date.

It might be a better idea to simply bundle paperclip.jar instead of the patched jar.
Paperclip was designed to re-download and reapply patches automatically as they become available.

While I like the idea of paperclip in general, I don't want to use it here, as the docker image should have a fixed version and shouldn't apply manual patches of an unknown state when running.

So no plan to keep the discrete versions updated?
PaperMC 1.14.2 is on build v96.
Unless there have been changes, the docker build is still v58...

The current latest 1.14.2 build should be based on #95 (https://papermc.io/ci/job/Paper-1.14/95/).
As this seems to very important for you, I would offer you Daily builds. The versions themselves are still fixed but once per day there is a build that builds with the "latest" docker tag and will always use the latest successful build. Would that be suitable for you?

I'm fine with fixed version numbers, as long as those version numbers are kept up to date with paper builds.
For instance, I'll keep using felixklauke/paperspigot:1.14.2 for now, but would like to make sure that it gets the bugfixes from paper as they are released, so I can occasionally re-pull the image and make sure my users get those bugfixes.
(Personally, this is a problem with the way Paper is set-up, and that it's tracking multiple upstream projects and API versions, which makes things confusing...)

If it helps, here's my usage scenario:

My users like/prefer 1.14.2, and want to keep up-to-date with the latest minecraft features as much as possible.
As a server operator, I want to make sure that the latest bugfixes are applied to that version to give them the best experience.

I will likely update to 1.14.3/1.15/etc shortly after they become available (I will test the server with a copy of the map in a sandbox environment for a few days, to make sure there are no show-stopping issues)
I understand some servers stay on a particular version for years, but I have a rather fickle audience who immediately demand releases as soon as mojang announces them (ha), but I quite enjoy exploring new game features myself, so I'll take the occasional instability as a reasonable trade-off.

I do want to thank you for accepting my input as well! It's been wonderful to see some of my ideas implemented.
If you'd rather not go in this direction, I'm happy to maintain my own branch as well, so let me know!

Hm, I'm still unsure how to handle this. With the todays Update for 1.14.3 (From build #108 at paper) I added the "latest build". that will build the latest version of 1.14. I will setup nightly builds for this. I will update this latest to 1.15, 1.16 as soon as it comes out.

The tags 1.13-latest (etc) is exactly what I'm looking for.
Adding 1.14-latest would be perfect (I expect the stand-alone latest version will track 1.15 when it's released)
I'm going to consider this resolved.

@t3rminus I came up with a completely new solutions. The old versions were still hard coded and hard to overview. But paper offers an API (https://papermc.io/api/v1/paper/${PAPER_VERSION}/latest/download) to download and track latest versions! Therefor I removed the "-latest" for now images and replaced them with the current versions. I will still come up with a new "Bleeding Edge" solution soon.


Typo in metaprogramming.html page

Hello,
There seems to be a typo in the  metaprogramming page.

In the sentence:
"You can a access a objects metaClass or set your own MetaClass implementation for changing the default interception mechanism."
probably the part: "You can a access a objects metaClass" should be replaced by: "You can access an object's metaClass".
Best regards,
Ivaylo

Thanks for reporting. :)
Fixed in: https://github.com/apache/groovy/commit/fa790d1aadb78290b906c930d2bdeaa039dc33f0
Website will be update with the next groovy release.
Cheers,
Pascal

Hey, Pascal
Great to hear.
Thank you!
Best regards,
Ivaylo


Avoid existing package name

Another ontopy package already exists: https://pypi.org/project/ontopy/

renamed to Ontolearn


Cannot assign keys for "Dota 2 Respawn" lighting

"Assign Keys" button changes to "Stop Assign", but no assigning can occur. "Stop Assign" also does nothing.
Can remove and move up/down normally, just can't assign different keys (or re-assign once removed except by creating a new respawn layer).
Loving the program, thanks heaps for your work, keep it up! 👍
Edit: Freestyle doesn't work either 😢

Fixed. The issue will automatically close when it's released in a new update.


Updates COS assets to support model training

Model label file name is specific to imagenet dataset. This PR is to generalize asset names to accommodate training changes.
To do after approval:

[x] Update COS prod
[x] Update readme link

@MLnick @bdwyer2
Moved asset to prod and updated readme.
Will merge the changes if it looks good

LGTM


Update clock to match canonical-data

There were some changes to the structure of canonical-data. The tests themselves are identical, so the version for the exercise remains unchanged.

Failure is due to outdated canonical-data in phone-number and unrelated to this change.


Setting up a NeoPixel Ring

Hi, I have setup the sorter by myself but for the final finishing I am trying to setup the NeoPixel ring. Just wanted to ask did you directly used the NeoPixel with the Pi or used it with the external power source as the LED's a trying heavy load of current. Also, did you use the GPIO 18 or any (PWM pin) as well for the setup.

Hi,
The NeoPixels must use an external 5v power source, as they draw too much power to for the Pi. Make sure to use a common ground between the power supply for the neopixels and the power supply for the Pi. This guide describes how the wiring should be set up: https://learn.adafruit.com/neopixels-on-raspberry-pi/raspberry-pi-wiring#using-external-power-source-without-level-shifting-3005993-11
We do use pin d18 as described in that guide as well under the 'Python usage' section. NeoPixels must be connected to pins D10, D12, D18 or D21 to work.


Metric exports failed while prometheus is up

Bug Report
We are experiencing metric data lost with Prometheus. It seems that after couple of days Prometheus stops scraping from our exporters. Service not fails, and able to access the exporters (testing it by running curl http://<remote_host>:<port>/metrics - data is accessible using curl) but no data is returned.
We are running on Azure cloud and we are using static config and azure_sd config for scraping.
Prometheus runs on a virtual machine using binaries, not as docker.

System information:
Linux 4.13.0-1011-azure x86_64

Prometheus version:
prometheus, version 2.2.1 (branch: HEAD, revision:  bc6058c81272a8d938c05e75607371284236aadc)
build user:       root@149e5b3f0829
build date:       20180314-14:15:45
go version:       go1.10

Alertmanager version:

alertmanager, version 0.14.0 (branch: HEAD, revision: 30af4d051b37ce817ea7e35b56c57a0e2ec9dbb0)
build user:       root@37b6a49ebba9
build date:       20180213-08:16:42
go version:       go1.9.2

Prometheus configuration file:

global:
  scrape_interval: "15s"

  external_labels:
    monitor: "alertmanager"

rule_files:
  - alerts/*.rules
  - recordings/*.rules

scrape_configs:
  - job_name: 'prometheus'
    scrape_interval: 5s

    static_configs:
      - targets: ['localhost:9090']

  - job_name: 'kafka-brokers'
    scrape_interval: 30s

    static_configs:
      - targets: ['prod-kafka-001:7071', 'prod-kafka-002:7071', 'prod-kafka-003:7071', 'prod-kafka-004:7071', 'prod-kafka-005:7071', 'prod-kafka-006:7071']

  - job_name: 'redis'
    scrape_interval: 30s

    static_configs:
      - targets: ['redis1-prod:9121']
        labels:
          name: redis1-prod

  - job_name: 'kafka-offsets'
    scrape_interval: 30s

    static_configs:
      - targets: ['prod-kafka-001:9308', 'prod-kafka-002:9308', 'prod-kafka-003:9308', 'prod-kafka-004:9308', 'prod-kafka-005:9308', 'prod-kafka-006:9308']

  - job_name: 'nodes'
    scrape_interval: 30s

    azure_sd_configs:
    - subscription_id: ""
      tenant_id: ""
      client_id: ""
      client_secret: ""

      refresh_interval: 120s
      port: 9100

    relabel_configs:
    - action: "keep"
      regex: "prod"
      source_labels: ["__meta_azure_machine_tag_env"]
    - source_labels: ["__meta_azure_machine_name"]
      target_label: "name"
    - source_labels: ["__meta_azure_machine_tag_role"]
      target_label: "role"

  - job_name: 'traffic-stream'
    scrape_interval: 30s

    static_configs:
      - targets: ['generalservices2-prod:5001']
        labels:
          name: generalservices2-prod

  - job_name: 'elasticsearch-nodes'
    scrape_interval: 30s

    azure_sd_configs:
    - subscription_id: ""
      tenant_id: ""
      client_id: ""
      client_secret: ""

      refresh_interval: 120s
      port: 9108

    relabel_configs:
    - action: "keep"
      regex: "prod"
      source_labels: ["__meta_azure_machine_tag_env"]
    - action: "keep"
      regex: "elasticsearch-(.+)"
      source_labels: ["__meta_azure_machine_tag_role"]
    - source_labels: ["__meta_azure_machine_name"]
      target_label: "name"
    - source_labels: ["__meta_azure_machine_tag_role"]
      target_label: "role"
    - source_labels: ["__meta_azure_machine_tag_cluster"]
      target_label: "cluster"
    - source_labels: ["__meta_azure_machine_tag_type"]
      target_label: "cluster_type"

alerting:
  alertmanagers:
  - static_configs:
    - targets: ['localhost:9093']

Alertmanager configuration file:

global:
  resolve_timeout: 5m

  # The smarthost and SMTP sender used for mail notifications
  smtp_smarthost: 'smtp-relay.gmail.com:25'
  smtp_from<EMAIL_ADDRESS>
  # The API URL to use for Slack notifications
  slack_api_url: ''

templates:
 - '/etc/alertmanager/templates/*.tmpl'

route:
  group_by: ['alertname', 'role']
  receiver: 'incidents'
  group_interval: 5m

  routes:
  - match:
      action: 'pagerduty'
    group_wait: 10s
    receiver: 'pagerduty'

receivers:
- name: 'incidents'
  email_configs:
  - send_resolved: true
    to<EMAIL_ADDRESS>  slack_configs:
  - send_resolved: true
    channel: '#incidents'
    title: '{{ template "custom_title" . }}'
    text: '{{ template "custom_slack_message" . }}'

- name: 'pagerduty'
  pagerduty_configs:
  - service_key: ''

Logs:

Can you share a screenshot of the target status page?

I've restarted the server so it might not help, but, see attached

To debug an issue like this we need information from the broken process, as there's little left lying around after a restart. If it happens again let us know.
The expanded view on the targets page is what's of interest, in particular when the last scrape was.

I will share it with you once it will happen again. Thank you

We went through this issue during our bugscrub and decided to close this as fixed. We haven't seen anything like this in a while and we probably fixed it in the meantime. Please reopen if you still see it.


Bump senzing from 3.2.0 to 3.3.0

See https://github.com/Senzing/senzingapi-runtime/issues/31

Pull requests:

https://github.com/Senzing/stream-logger/pull/102


Fix Nan in Blade Stiffened Shell Constitutive Model

Getting nans in the bucklingEnvelopeFailureSens while running the Mach wing in Funtofem
N1 << N1crit leads to root becomes 0 due to machine precision. Add small tolerance to prevent divide by zero.

@A-CGray - I made the changes you requested


Support generic method syntax in dart2js

The dart2js compiler should support declaration of type parameters in function and method declarations, and it should support provision of type arguments in message sends. The type parameter declaration grammar should be identical to the grammar of type parameter declarations on classes, and the type argument grammar should be identical to the grammar of type arguments passed to constructors on new expressions.

https://codereview.chromium.org/1723443003/ provides support for this, when the flag '--enable-generic-methods' is specified. Missing: The specified type parameters are ignored and hence all usages of the type parameters will cause an 'unknown type' warning or possibly a different warning because the same name is declared also in an enclosing scope and the usage is incorrect for that declaration.

https://codereview.chromium.org/1942763002/ adds support (still behind a flag as mentioned, but it has been renamed to '--generic-method-syntax') for passing method/function type variables into the resolution phase, and making them appear to be the type dynamic. This means that a wide range of usages of the type parameters are now accepted silently (but not type checked: bounds are ignored).

As of 9bf3b95cc5f4677269830054fb5c12b64f1e7f21, the generic method syntax feature is enabled by default. The option --generic-method-syntax is accepted and ignored.


card component

a simple card component for the adopt page. design is in the design folder

hey could i work on this i will follow
the card design pls

i will aslo follow the code of context
pls

i am soory for what i have done before pls take me back in :(

pls pls bro :( i am crying becase what i have done pls pls forgive me

I want to work on this, please assign it to me @AnandDhakane01

hey i am done working on this

hey i am done with it i will make a pr now


mesosphere/chronos image immediately stops after starting running under Marathon

The process starts but then gets killed immediately. Lots of messages in syslog like this:
chronos[1097]: 2016-08-18 14:26:00,599:1097(0x7f650c5c6700):ZOO_INFO@check_events@1728: initiated connection to server [52.90.xx.xx:2181]
It looks like it cannot connect to zookeeper - even though marathon and the mesos-slaves are able to connect without issue.
This is my marathon config:
{
  "id": "/chronos",
  "cmd": null,
  "cpus": 0.5,
  "mem": 128,
  "disk": 0,
  "instances": 1,
  "acceptedResourceRoles": [
    "*"
  ],
  "container": {
    "type": "DOCKER",
    "docker": {
      "image": "mesosphere/chronos",
      "network": "BRIDGE",
      "forcePullImage": true,
      "portMappings": [
        {
          "containerPort": 4400,
          "hostPort": 0,
          "servicePort": 31000,
          "protocol":"tcp"
        }
      ]
    }
  },
  "env": {
  },
  "shell":false,
  "ports": [
    "4400"
  ],
  "args": [
    "/usr/bin/chronos",
    "--master",
    "zk://server1.xx.com:2181,server2.xx.com:2181,server3.xx.com:2181/mesos",
    "--zk_hosts",
    "server1.xx.com:2181,server2.xx.com:2181,server3.xx.com:2181",
    "--cluster_name",
    "mesos-swarm-qa",
    "--http_port",
    "4400",
    "--zk_path",
    "/chronos"
  ]
}

@ChienHuey, this worked for me: https://github.com/mesos/chronos/issues/291#issuecomment-351970105


Discovery performance

Feature scope
Taps (catalog, state, stream maps, tests, etc.)
Description
This is for now a catch-all issue to investigate discovery performance, specific to SQL taps and how the SDK can help speed it up.

https://github.com/MeltanoLabs/tap-snowflake/issues/35
https://github.com/MeltanoLabs/tap-snowflake/issues/23
https://github.com/MeltanoLabs/tap-postgres/issues/284
https://github.com/MeltanoLabs/tap-bigquery/issues/15

A good reference implementation came up in https://github.com/MeltanoLabs/tap-postgres/pull/528.


⚠ File access has degraded performance

In 3c32107, File access (https://fyle.uk/file/fish) experienced degraded performance:

HTTP code: 200
Response time: 6944 ms

Resolved: File access performance has improved in 3af7fde after 8 minutes.


Target groups

Switches from one set of backends per service to a target groups based model
Allows weighting of traffic to target groups' backends
Normalises the API paths to register services, target groups and backends
Enforce PEP8 compliance with Flake8 (extended max line length to 120)

It's a pretty big commit but it LGTM, go forth and merge!


Add decl bindings for simple let statements [phab:D958]

Created by djrenren at 2016-07-11 21:37:03:
This commit adds the createion of variable nodes for local let
bindings

djrenren wrote at 2016-07-11 21:40:29:

Added a comment and renamed local_decl_vname

zarko commented inline (context lost during migration) at 2016-07-11 21:52:49:
How are crate_ids generated?

djrenren commented inline (context lost during migration) at 2016-07-11 23:07:05:
That's an excellent question... it's probably generated based on order :/ so I can totally just do a lookup and get the crate name. but honestly the corpus should probably be the difference there, not the sig... will post a revision. local variables will always have a crate_id that is equal to zero. So for now we can ignore it but I'll leave a note. This would make the vname schema for variables look like:
{
    "signature": "variable:123456"
    "corpus": "somecrate"
    "language": "rust"
}

does that sound good?

djrenren wrote at 2016-07-11 23:18:04:

Remove CrateNum from sig for variables

zarko commented inline (context lost during migration) at 2016-07-11 23:58:37:
nit: you indented this in the other test; choose one style for consistency.

zarko commented inline (context lost during migration) at 2016-07-11 23:58:37:
Is there a way to do this that doesn't involve string comparison? Do the HIR objects you have available to you have some flag that shows whether they are implicit code?

zarko commented inline (context lost during migration) at 2016-07-11 23:58:37:
Is there prominent documentation somewhere that says that bad things will happen if crates are not given globally unique corpora? I think this is one of your core assumptions about the way the indexer is invoked.

djrenren commented inline (context lost during migration) at 2016-07-12 00:21:38:
Well I'd written out a really long explanation of why we can't but then I found a very counterintuitive but correct way of doing this from clippy. On it.

djrenren commented inline (context lost during migration) at 2016-07-12 00:21:38:
So currently, yes. In the future I'd like to ingest some sort of config file. that aides in the construction of VNames. Corpus has really evolved into a VName generator rather than a node emitter (as I originally had it). So it would make sense to merge that logic in there. So I could put up a big scary warning but for now, since I'm not doing anything cross-crate nothing is broken per-se and it's very possible that that restriction isn't a hard one.

djrenren wrote at 2016-07-12 00:42:09:

Check for desugaring w/o string comparison

zarko wrote at 2016-07-12 00:59:53:
In a future diff you might consider indexing implicit declarations; LGTM (but please make sure to document the corpus precondition).

zarko accepted this revision at 2016-07-12 00:59:53

djrenren closed via commit 1bb8857bf1522ea6d6f1be638c2f319b84700f8e at 2016-07-12 01:01:17


Sharepoint doesnt show files on others sites rather than root

Hey @KevinTCoughlin, I have an issue that I guess it's related to this one.
When using the root company folder as endpointHint hint for Sharepoint (i.e https://test.sharepoint.com/Shared Documents/) users will not be able to see files on other /sites/ even when they have access and can see the sites on the left view (see picture).

This issue doesn't happen when setting endpointHint to any other site (even those where the user is not a member).
I am opening the picker similar to:
``  OneDrive.open({
clientId: clientID,
action: 'query',
advanced: {
accessToken: accessToken,
endpointHint: "https://test.sharepoint.com/Shared Documents/",
},
multiSelect: true,
success: onSuccess,
error: onError,
cancel: onCancel,  });
}
Originally posted by @ldcm3 in https://github.com/OneDrive/onedrive-api-docs/issue_comments#issuecomment-456458137

Any news here?

Any news here?

The endpointHint of https://test.sharepoint.com/Shared%20Documents/ seems correct given my testing against our own tenants and the Picker SDK documentation at https://docs.microsoft.com/en-us/onedrive/developer/controls/file-pickers/js-v72/open-file?view=odsp-graph-online#advanced-options.
Can you share any non-security sensitive attributes of the response to help us debug?
cc: @ThomasMichon for any insight re: the above.

quick check: Since Files.Read.All is not a default permission on registered apps, was this selected as a scope on your Azure Portal app registration settings as well?

Hi guys, thank you for the reply.

was this selected as a scope on your Azure Portal app registration settings as well?

Yes. I also tried with Sites.Read.All and did not work

Can you share any non-security sensitive attributes of the response to help us debug?

I hope this can help you. This is was tested using our dummy implementation on: https://github.com/jokr/taaskly/blob/msft/static/js/msftpicker.js

@ldcm3, I tested setting the endpointHint to a valid "Shared Documents" URL against a few SharePoint test tenants and the Picker worked as expected. I was able to view and select files in the "Shared Documents" document library as well as other site document libraries I had access to.
Here was my configuration:
var options = {
	clientId: '00000000-0000-0000-0000-000000000000',
	action: 'query',
	multiSelect: false,
	advanced: {
		endpointHint: 'https://<tenant>.sharepoint.com/Shared%20Documents/'
	},
	success: (files) => console.log('success', files),
	cancel: (err) => console.log('cancel', err),
	error: (err) => console.log('err', err)
};

OneDrive.open(options);

I could view / select files in the shared documents list as well as navigate to other site lists.
Have you tried omitting the accessToken parameter? One idea is that the accessToken is invalid for the site(s) you are trying to access.
Have you ensured that the decoded accessToken maps to the correct tenant resource via http://jwt.ms/?

Hey @KevinTCoughlin, I just tried again with the exactly same config you used (omitting accessToken) and same thing happens..
It doesn't seems to be a problem with permissions, since if I click on the "Go to the list" button it takes me to the site view (even I cannot pick files from there):

Please let me know how I can give you more info, thanks again!

As I said before, it is weird since the issue doesn't happen when setting endpointHint to any other site rather than the "default"   'https://.sharepoint.com/Shared%20Documents/'

As I said before, it is weird since the issue doesn't happen when setting endpointHint to any other site rather than the "default" 'https://tenant.sharepoint.com/Shared Documents/'

I set it to the "default" in my configuration and it worked i.e. https://.sharepoint.com/Shared%20Documents/.
Hence my confusion in trying to repro.

We are definitely sending requests and getting back a 404 when accessing other sites.
So we can't debug the error code on our side.
Can I get you a fiddler trace or a way to get a correlation id so you can trace the request on your side?

We are definitely sending requests and getting back a 404 when accessing other sites.
So we can't debug the error code on our side.
Can I get you a fiddler trace or a way to get a correlation id so you can trace the request on your side?

Fiddler traces would be great. Please send them to my work e-mail (I'm on the same thread you are). The traces should give us the correlation ID and additional information to debug.
I see both a 403 and a `404 in the screenshot attached in https://github.com/OneDrive/onedrive-api-docs/issues/985#issuecomment-469608533.

So this is what we get on that 403:
{"error":{"code":"-2130575251, Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"The security validation for this page is invalid and might be corrupted. Please use your web browser's Back button to try your operation again."}}}
From a quick search it looks like we are missing some RequestDigest field.
Not sure how to solve that since we the frame relies on cookie authentication as you said.

This should now be resolved as the fix was released to production earlier this week. The issue was in how the hosted Picker page resolved cross-site SharePoint URLs.
Please create a new issue if anyone is still blocked with new debug information. I'm going to have the bot soft-close meanwhile.
cc: @aditima @ThomasMichon


JSP highlighting

(Original issue 184 created by mgood on 2007-01-11T21:10:46+00:00)
Pygments could offer highlighting for JSP templates.
See also: http://trac.edgewall.org/ticket/4523

(Original issue was assigned to gbrandl)
(Original issue 184 last updated on 2007-01-11T21:15:35+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by gbrandl on 2007-01-11T21:15:18+00:00)
Yep, indeed. Added to TODO file.


Change mapping grammar to refer to options consistently

We currently have (for example):  OccurrenceTime[date] maps to start[x].Date
I would prefer it to be:  OccurrenceTime[date] maps to start[Date]  -- without the [x]. That would simplify the mapping grammar.

 Change mapping grammar to refer to options consistently

Added this suggestion to https://jira.mitre.org/browse/SHRO-545.


Update raw_info to use oauth2/@me path

I've just tried to use the omniauth-discord gem in a new Rails project of mine but I kept running into "Unauthorized" errors. Checking the Discord OAuth2 docs, the URL to grab details of the currently authenticated user is at oauth2/@me, so this PR fixes this.

Apologies, turns out I didn't supply the identify scope


Node.js  Community Committee Meeting 2020-10-15

Time
UTC Thu 15-Oct-2020 16:00 (04:00 PM):

Timezone
Date/Time

US / Pacific
Thu 15-Oct-2020 09:00 (09:00 AM)

US / Mountain
Thu 15-Oct-2020 10:00 (10:00 AM)

US / Central
Thu 15-Oct-2020 11:00 (11:00 AM)

US / Eastern
Thu 15-Oct-2020 12:00 (12:00 PM)

EU / Western
Thu 15-Oct-2020 17:00 (05:00 PM)

EU / Central
Thu 15-Oct-2020 18:00 (06:00 PM)

EU / Eastern
Thu 15-Oct-2020 19:00 (07:00 PM)

Moscow
Thu 15-Oct-2020 19:00 (07:00 PM)

Chennai
Thu 15-Oct-2020 21:30 (09:30 PM)

Hangzhou
Fri 16-Oct-2020 00:00 (12:00 AM)

Tokyo
Fri 16-Oct-2020 01:00 (01:00 AM)

Sydney
Fri 16-Oct-2020 03:00 (03:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community Committee+Meeting+2020-10-15&iso=20201015T1600
or https://www.wolframalpha.com/input/?i=04PM+UTC%2C+Oct+15%2C+2020+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1vdL_YjT0rMSkc99Lv5o5eXUzlAg_8wRc-P1IgEbDQJ4/edit

Agenda
Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/TSC

feat(charter): introduce emergency and async votes #919

Invited

CommComm Members: @nodejs/community-committee

Observers/Guests
Feel free to follow along on the YouTube live stream, or attend meeting as a guest
by calling in to Zoom, using the links below. If you will be attending as a guest,
please comment on this issue to let us know you'll be joining.
Notes
The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

Link for participants: https://zoom.us/j/523381536
For those who just want to watch: https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ

Invitees
Please use the following emoji reactions in this post to indicate your
availability.

:+1: - Attending
:-1: - Not attending
:confused: - Not sure yet

Probably won't be able to make it due to a meeting time conflict.

updated the agenda to remove an old issue that was resolved last time.


Airlock - Add get reviews endpoint

Description
As a TRE Developer
I want to add the GET reviews endpoint
So that users can ask for the given reviews and see why a request was denied/approved
Acceptance criteria

[ ] add missing endpoint
[ ] all reviews / steps of a given requests are returned
[ ] only for authorized roles
[ ] ...

Suggestion that this endpoint return all airlock requests "I" have access to - either waiting for my review OR requests I've submitted - is that the plan?

It might make sense to merge the objects in the response of requests, so that the reviews are part of a request (
Potentially not for a list, but for a GET)
See also https://github.com/microsoft/AzureTRE/issues/2271
@tamirkamara  to provide more details


Clear presence when housekeeping process

What this PR does / why we need it?
This PR addresses the absence of presence clearing logic in document detach during client deactivation for Housekeeping compared to document detach by the SDK. By implementing server-side presence clearance, this PR ensures that presence is correctly handled during the housekeeping process.
Any background context you want to provide?
The changes include:

Performing document detach with client deactivation and updating the SyncedSeq solely through the database -> making an API call similar to the SDK's document detach
This change allows presence to be cleared through client.detach() during deactivation and detach processes, simplifying the process and omitting the need for updating SyncedSeq separately.
In case of deactivation failure, some documents may not detach completely, but another deactivation attempt is possible.
Consideration for clustering and sharding per document
Taking into account document structures sharded across clusters by keys, the update allows one server to act as a client while multiple servers can perform detach operations.

What are the relevant tickets?

Fixes #602
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Additional documentation:

Checklist:

[x] Added relevant tests or not required
[x] Didn't break anything

Summary by CodeRabbit
Summary by CodeRabbit

New Features

Introduced methods for simulating document attachment and client activation, enhancing server-side operations.
Added functionality for converting internal documents to public documents, improving document management.
Enhanced client connection capabilities, allowing for improved document and client interaction.
Implemented configuration options for dynamic gateway service referencing in Kubernetes.
Added command-line flags for backend gateway address configuration, increasing server flexibility.

Bug Fixes

Improved error handling for detach requests to ensure system integrity in case of failures.
Enhanced logic for client deactivation, ensuring the most up-to-date client state is utilized.

Chores

Streamlined methods for client deactivation, simplifying document status management during operations.
Expanded configuration options in the Helm chart for better service adaptability.
Added new constants and configuration fields to improve server setup and management.

@hackerwins
The answer to question B is:
During the deactivate process, the VerifyAccess() was performed, and a test case that failed was found during this process, such as authorization webhook test.
For the remaining questions, I look forward to hearing ideas from others.

@hackerwins I think current approach is fare enough because we need to go through yorkie-gateway to delegate the operation. I'm wondering what will happen when detach is not performed on other documents that user was attached, and then deactivation occurs?

@krapie Could you please explain in more detail what you are curious about?
Are you referring to a situation where document detach fails and only client deactivate occured during the process of client deactivation, specifically clients.deactivate()?

I have identified an issue related to Authorization as pointed out by @hackerwins . Specifically, the issues are as follows:

For clients with a token value, the verifyAccess process is required during deactivate or detach.

When receiving a deactivate or detach request from an external source, the client's token value is passed along with the request.
However, in cases where a client is temporarily created during the server (Housekeeping) process, there is no way to know this token value.

To address this issue, I'm considering the following two actions:

Issuing a Server-Specific Token:
We plan to generate a shared token for all servers, allowing us to skip the verifyAccess step for server-specific tokens. We are considering methods such as injecting this token through the defaultFlag or a DevOps manifest.

Defining a systemService:
Currently, only rpcService and adminService are defined. We propose defining a new systemService to separate the logic for inter-server communication from existing services.

Given the additional work required, I will mark this PR as a draft.
And of course, any feedback or comments are welcome!

@raararaara My apologizes, I was asking the wrong question.

This PR continues in #1036.


Numba v0.46.0 issue when executing umap

Traceback (most recent call last):
  File "C:\Users\CrystalChutki\Desktop\Zlab\Enhancer_clustering_exercise\enhancer_clustering_analysis.py", line 24, in <module>
    umap_data = reducer.fit_transform(scaled_m.T)
  File "C:\Python27\lib\site-packages\umap\umap_.py", line 1598, in fit_transform
    self.fit(X, y)
  File "C:\Python27\lib\site-packages\umap\umap_.py", line 1417, in fit
    self.verbose,
  File "C:\Python27\lib\site-packages\umap\umap_.py", line 478, in fuzzy_simplicial_set
    knn_indices, knn_dists, sigmas, rhos
  File "C:\Python27\lib\site-packages\numba\dispatcher.py", line 420, in _compile_for_args
    raise e
UnsupportedParforsError: Failed in nopython mode pipeline (step: nopython mode backend)
The 'parallel' target is not currently supported on Windows operating systems when using Python 2.7, or on 32 bit hardware.
[1] During: lowering "id=0[LoopNest(index_variable = parfor_index.26, range = (0, $0.13, 1))]{362: <ir.Block at C:\Python27\lib\site-packages\umap\umap_.py (330)>}Var(parfor_index.26, C:\Python27\lib\site-packages\umap\umap_.py (330))" at C:\Python27\lib\site-packages\umap\umap_.py (330)
-------------------------------------------------------------------------------
This should not have happened, a problem has occurred in Numba's internals.
You are currently using Numba version 0.46.0.

Please report the error message and traceback, along with a minimal reproducer
at: https://github.com/numba/numba/issues/new

@shuo-shan thanks for reporting this, I have fixed up the formatting to use markdown. Feel free to checkout the following guid about Github markdown:
https://help.github.com/en/github/writing-on-github

Taking a closer look at the error message, it appears you are using an unsupported platform or python version:
�[1m�[1mThe 'parallel' target is not currently supported on Windows operating systems when using Python 2.7, or on 32 bit hardware.�[0m

Can you confirm?
If so, @lmcinnes - it might be worth disabling the parallel target in such cases?

Thank you @esc! Yes I was running it on Python2.7 using 64bit hardware. I will try running my code again using Python3.x and keep you posted on whether this error show up again.

@shuo-shan if that is an option, great!

@esc I used Python3.7.4 and it worked. Thank you for the help!

@shuo-shan thanks for reporting back. Will close this issue now.


Implement the personal api

Fixes #215.

This is enough to work with browser-solidity and soltest (of solidity).

Any chance I can get some added tests for these methods?

@axic Sorry for such the long wait on this. I've added it to the release branch of trufflesuite/ganache-core. Will go out with the next release of the TestRPC.


Middleman-blog pagination not working with v4

Let me know if I should file middleman-blog issues over in that repo - I'm starting here because it hasn't changed so I'm assuming the problem is on the middleman-core side.
I've noticed with the code in master that my blog no longer has pagination working for it. For example, the 2006 archive page shows 14 articles and no second page, even though my blog is configured to paginate (and there's a default page size of 10):

activate :blog do |blog|
  blog.prefix = "blog"
  blog.taglink = "category/:tag.html"
  blog.layout = "article"
  blog.summary_separator = /<!--more-->/
  blog.summary_length = nil

  blog.tag_template = "blog/tag.html"
  blog.calendar_template = "blog/calendar.html"
  blog.paginate = true
end

Hmm, deeper pages are still being generated, though. I wonder if I need to update my pagination partial, too. Here it is now:
.paginate.btn-toolbar
  .btn-group
    - if defined?(prev_page) && prev_page
      = link_to '◀ Previous Page', prev_page, :class => 'archives btn btn-default'

    - if defined?(next_page) && next_page
      = link_to 'Next Page ►', next_page, :class => 'archives btn btn-default'

Are prev_page and next_page not defined as locals anymore?

Pagination tests are currently broken on blog, so that may be it

:+1: This and the performance stuff is the only thing left as regressions for my blogs. :tada:

Excellent. I think the perf stuff can be solved by a bit more caching... which introduces its own complexity, but that's life.

Hmm, I pulled the latest from master, and now I'm getting 10 articles per page, and multiple pages are generated, but prev_page and next_page still aren't showing up as locals.

At the time of rendering (when Sitemap::Resource#render is called), the locals seem correct:
PATH: blog/index.html
["paginate",
 "page_number",
 "num_pages",
 "per_page",
 "page_start",
 "page_end",
 "next_page",
 "prev_page",
 "page_articles",
 "articles",
 "blog_controller",
 :rack,
 :current_path]

But when I print out methods from my template, it's not there.
There is an instance variable called @locs that contains my locals though. Is that how it's supposed to work now?

This really should be getting caught by the tests around this: https://github.com/middleman/middleman-blog/blob/master/fixtures/paginate-app/source/index.html.erb#L13-L14

A pertinent detail I missed - my pagination stuff is happening in a partial.

Whoa, partials weren't getting their parent locals. Nasty. Resolved.

I'm doing some issue-gardening 🌿🌷🌾 and came across this issue.
@bhollis Sorry that this has lingered for quite a while! Did the commit by @tdreyno work? If so, can this be closed?

This is similar I think to my reference
https://github.com/middleman/middleman-blog/issues/320


How to get cublas handle to run cublas function?

I write a custom op using cublas function cublasCgetrfBatched and cublasCgetriBatched, the functions use cublas handle as a input param, however the cublasCreate(&handle); cost nearly 100ms.
I think the TF has already integrate CUBLAS module, cublasCreate(&handle) muse have been invoked in the init process, then how to get the handle? An example may be the best!

Perhaps you may find this page useful
Also see cublas examples

@ymodak Thanks! But my question is how the get the cublas handle from TF, I know the the usage of cublas and have run the custom op using cublas already, but the handle need be created with cublasCreate(&handle), if run the op multi-times, then the handle is created multi-times, that's unreasonable. However I can't save the handle in an op and reuse it, as it is a global variable.
It seems that TF using steam_executor to wrap gpu device, maybe cublas handle has already created in the TF init process, and may get it from some TF C++ API.

As of today cublas handle is for Tensorflow internal use only. It's not exposed to the public C++ API. See tensorflow/stream_executor/cuda/cuda_blas.h that no getters are there for getting the handle blas_.
I don't know much about TF custom ops, but I'd expect somewhere in the executor to have a place for users to keep a handle there.

@timshen91 Very useful info! Is there any sample code that use stream executor to do BLAS ops with cuBLAS. If I modify the src code to export a getter of blas_ and use it in some custom op, will it affect releasing resource?

@7oud For your own debugging and understanding, it's probably fine to add a getter for blas_.
For a real solution, I suggest you to:

Find a way to transport arbitrary data from your application to the execution of your custom op
Create your permanent BLAS handle before executing the graph, and expose it to the custom op executor
In the custom op executor, use the permanent BLAS handle you created.

Unfortunately I don't know TF enough to tell you where those places are in code.

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


"SSL certificate manager" link in System > Settings > Administration points to nothing.

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
This link:

Points to a 404

When it should points to

To Reproduce
Steps to reproduce the behavior:

Go to System > Settings > Administration
Click on SSL certificate manager
See error

Expected behavior
Should take user to Trust >Certificates instead
Environment
OPNsense 24.7.2 (amd64).

@tanpro260196 thanks, fixed in https://github.com/opnsense/core/commit/f2603ca7101f8fb02dba37b3b14ff561964fcbc3


Example files naming and Xcode Project

exercism/xruby#102
"The only restriction is that the example file needs to have /[Ee]xample/ in the name" - @kytrinyx
I want to understand why the test files can be different names but the examples files names need to be "/[Ee]xample/ ". In an xcode project I can't have the same filename for different files in the same project because the project wont compile. Having all the problems in one project would allow faster updates of language changes ( 1.x to 1.x+ ) and in the future Travis integration.
http://docs.travis-ci.com/user/osx-ci-environment/
http://docs.travis-ci.com/user/languages/objective-c/

https://github.com/exercism/exercism.io/issues/316

Maybe it was a little late last night for me.  Would these be  valid "example" file names?
BobExample.swift
LeapExample.swift
etc

@masters3d, this is a great idea. Being able to name the tests BobTest.swift, the example BobExample.swift and the user's solution Bob.swift would really simplify things. It would not only make it easier to maintain the problem sets, but it would streamline the user's process. Instead of creating a new project for each exercise, they could just use the same project and add new exercises as they go.
If the restriction is that the examples must have /[Ee]xample/ in them, then BobExample.swift should work. That regex isn't anchored, so it should be okay. Let's get confirmation from @kytrinyx, then rename the existing example files.

@masters3d Yepp, BobExample.swift and LeapExample.swift are fine.
Would this structure the repo differently?

no, only the example.swift in each problem folder would be renamed as above.

Thank you! renaming done.


Adding text to existing template

Hi, i am currently working on a freelance project what i am asked to do is copy data from one CV and paste it into a new .docx template having headings like
Languages:
Experience:
Now what i am trying to is read the template file and then add Language info after the Languages word. maybe a run or a paragraph. I found  a insert_before function but not a paragraph. I can't find a way out. Also there is no function in Python-docx that does it. I found some articles mentioning addnext but i am not able to find it in Python-docx

Please ask support questions on StackOverflow using the "python-docx" tag. This issues
list is for suspected bugs and new feature requests.

@scanny just did
kindly check it out: https://stackoverflow.com/questions/61056479/add-after-paragraph-in-python-docx


'default' is not exported by node_modules/vanilla-modal/dist/index.js under rollup.js

import VanillaModal from 'vanilla-modal';
gives me
🚨   'default' is not exported by node_modules/vanilla-modal/dist/index.js
https://github.com/rollup/rollup/wiki/Troubleshooting#name-is-not-exported-by-module
precompiled/javascript/modules/pages/checkout.js (1:7)
1: import VanillaModal from 'vanilla-modal';
          ^
2:
3: var Checkout = function Checkout() {

under rollup.js v0.40.2 and using the "es2015" preset

However import VanillaModal from 'vanilla-modal/index.js'; does work!

Sorry for my tardiness in getting around to this - glad you worked it out @michaelburtonray!


Write tests

After #6 and #7, we can focus on writing some tests. I'd keep it fairly simple and basically only test that the bindings themselves work, i.e. calling each function and making sure the basic objects exist in the response. We can just use unittest for this, e.g. like here: https://github.com/gis-ops/pyvalhalla/blob/master/test/test_utrecht.py. We'll also want to test any abstractions we add in #7

this has landed with #9


Please review documentation and give feedback

Please review the documentation I have started at:
https://github.com/kai-koch/node-mysql/wiki
This is only a draft and consists mainly of the readme.md broken down into an sections sorted by (subjective) importance.
For the examples given I increased indentation from 2 to 4 spaces, because it is more readable IMO .
If the draft meets your approval I would like to continue working on:

more in depth examples from practical use-cases
in the API section, I would like to add descriptions like on php.net for methods and objects the end-user has to deal with

Please give feedback and, of course, suggestions on how to improve the structure of this draft.

I'm going through old issues in preparation for a major release. I'm going to close this as clean up, as I think perhaps this was already completed, but at least the link no longer works 😂


docs: improve the description of the Sunday Cycle calculation

This PR is based on this comment in #586.

looks like you need a little rebase

@tukusejssirs needs another rebase after the dependency updates, i'll turn on automerge so it merges once you rebase and the CI builds


Update Link to ExoPlayer in MediaElement.md

The link to the ExoPlayer Documentation was according to the content of its page out of date and developer.android.com was recommended instead.
Here is the message that is shown for the current link:

@jfversluis I think this is a good addition and fine to merge. Can you press the magic button please?