Form Proper Release Process

For a DevOps Engineer, I've done a pretty shitty job of managing releases of Ansible-NAS. Right now everything is on master and branches which is fine for those with Git skills, but merging updates into your own installation can be a ballache if not.
Ansible-NAS should have proper versioned releases with specific instructions of how to upgrade from one version to the next, with the specific changes required to your all.yml in release notes.
For those wanting to live on the edge or have the latest features, instructions should be provided how to run from the master branch.

hey @davestephens, so glad to see this project is still going strong!
i pretty much haven't touched my setup since September (issue #6 seems like so long ago!) but i'm wanting to update my installation to get all of the new good stuff you've incorporated since then
if you can give me some rough directions on how to proceed, i'm happy to try to contribute formal documentation on upgrading, etc?

Hey @chrisbutler - yeah, still cracking on!
Assuming you've not messed with the playbook, it should just be a case of pulling the latest from master, then merging changes from all.yml.dist into your own all.yml.
From release to release, I want to document the changes and new features/apps, and the relevant parameters required to be added to your own all.yml.  For the more controversial changes (for example I've just changed the default Docker storage driver from zfs to overlay2) I want to add the reasoning behind them so at least people have some insight into my thinking rather than just assuming I'm losing the plot :-)

A script to inject new/delta/missing pieces into all.yml from the current cloned copy of all.yml.dist would be highly appreciated! :)
(Should be a separate enhancement request but...) a simple upgrade.sh script or such that implements step no. 9 of the install (Run the playbook - something like ansible-playbook -i inventory nas.yml -b -K should do you nicely.) would be nice. After looking that command up on the website x amount of times, I finally made one. :)


SCM should be tagged on each build

Neat solution is not possible without JENKINS-28335
Currently having some problems integrating credentials

Fixed on v0.2 development branch


Diffenrent size of stage1.pth

excuse me, would you like to solve my confusion that the stage1.pth download from the Onedrive is 74.23M. However, the one that i train by myself base on THU2.0 is 37M. And both them are work. So would you explain the reason of the difference?
Thank you!

I have also been confused about it, a possible reason is that I trained the uploaded model with mixed precision.

I have also been confused about it, a possible reason is that I trained the uploaded model with mixed precision.

Thanks for your reply. I use both the download ckpt and the one trained by my self of stage1 to train stage2 on thu2.0 by "python train_stage2.py", the metric that i got is far higer than the score in Table1 in arxiv preprint. Is there anything that i operate or understand incorrectly?

In our paper, we evaluate PSNR, SSIM and LPIPS in foreground regions determined by the GT bbox of humans. However, during the training process, we directly evaluate them on whole images for ease of quantization. The background pixels make the PSNR higher than that reported in our paper.

In our paper, we evaluate PSNR, SSIM and LPIPS in foreground regions determined by the GT bbox of humans. However, during the training process, we directly evaluate them on whole images for ease of quantization. The background pixels make the PSNR higher than that reported in our paper.

Thanks for your reply! Would you plan to release the related evaluate code on PSNR, SSIM and LPIPS? Since i did not find it in the present released code.

Our evaluation code is based on IQA-PyTorch. I will release the related scripts and update the evaluation guidelines soon. However, since conducting evaluation on either whole images or foreground regions is a common practice, a fair comparison on all compared methods is sufficient for your research.

Our evaluation code is based on IQA-PyTorch. I will release the related scripts and update the evaluation guidelines soon. However, since conducting evaluation on either whole images or foreground regions is a common practice, a fair comparison on all compared methods is sufficient for your research.

Thank you for your patient response!


Update not called on physics system when changed.

The physics is a system. Which unfortunately does not fire update when it is changed.
https://aframe.io/docs/0.5.0/core/systems.html
It would be great if it was a component instead so that it could be updated dynamically.

Yeah, it's been an issue. The helpful thing about systems is that they're guaranteed to init() first and tick() last, which i'm taking advantage of. I'm hoping https://github.com/aframevr/aframe/issues/2071 will be fixed in 0.6.0, in which case systems will have the same update support as components.

Closing this here but 0.6.0 milestones should have it covered: https://github.com/aframevr/aframe/milestone/5


Add ODH support in ODS_CI tests

Allow ODS_CI to run test-suits on ODH codebase

changes look good to me, but please ensure that the latest changes works well with rhoai nightlies , odh nightlies and ODH.

I had tested these changes on my local system for RHOAI and ODH operator. How could I verify them for rhoai nightlies , odh nightlies?

@vaibhavjainwiz do you have permissions to merge this yourself? usually it's best when PR author clicks the merge for themselves

Tested in jenkins at https://red.ht/4aGEIzg, feel free to run again with more tests to be better assured this works

@vaibhavjainwiz current code will break ODh-nightly installation. If we want to merge this pr i would suggest to bring back the condition of odh-nightly as earlier. or if we want to use olminstall we still need condition for that  until the operator name is not consistence between odh-nightly and upstream ODH


Add Mermaid Zenuml Support

Describe the solution you'd like
Mermaid can render sequence diagrams with ZenUML.

https://mermaid.js.org/syntax/zenuml.html

It is possible to register the ZenUML renderer for Mermaid via './setup/mermaid.ts'.


list-prs-for-branch should exclude "reverse" pull requests

Description
By "reverse" pull requests I mean merging upstream into forks. Nobody is interested in them.

Also I feel list-prs-for-branch probably needs to be shown on more pages (currently it's only isRepoCommitList). I almost forgot it until this issue.
Screenshot
No response
Example URL
https://github.com/refined-github/refined-github/commits/hotfix

Is this as easy by filtering by user/repo? Or is there some field in the API call to do the same? I'd prefer the latter

I'm confused. We're already specifically asking the API for PRs open on the current repo. Why is that PR appearing here?
https://github.com/refined-github/refined-github/blob/dbb4cf8d6503ccfbdad00d13054aff8e15f3b7cd/source/features/list-prs-for-file.tsx#L69-L73

Can you create a permanent repro on the sandbox?

Can't repro


Lazy Loading Swiper Jumps

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 6.3.5

Platform/Target and Browser Versions: osx firefox 83.0

Live Link or JSFiddle/Codepen or website with isssue: https://stackblitz.com/edit/lazy-loading-swiper-bug?file=index.js

What you did
Create a swiper with lazy loading. Offset of the images is wrong, unless I resize the window when everything is loaded. ( The same appears when adding a video to a slide).
Expected Behavior
Correct Image offset, also with { centeredSlides: true }
Actual Behavior
offset is wrong

From example, it looks like this solves it for you, right?

          lazyImageReady: function() {
            console.log("lazy image ready");
            this.updateSlides();
            this.slideTo(this.activeIndex, 0, false);
          }

unfortunately not. see a video here: https://nx5024.your-storageshare.de/s/YXW3p79HsHnJr4T

@niklasp
https://skr.sh/v50bBm7aAsu?a
Am I testing it wrong?

try:
        on: {
          lazyImageReady: (swiper) => {swiper.update()}
        }

https://stackblitz.com/edit/lazy-loading-swiper-bug-cpdyap?file=index.html

@vltansky that last line of code fixed it for me. But i think the lazy loading feature needs more attention, as that somehow seems to me like a hack as it probably should be part of lazy loading, shouldn't it?

Yeah, I think so too.
@nolimits4web take a look on this. Is just adding swiper.update() just before emitting lazyImageReady a good solution?

Solution proposed by @vltansky is not a hack and should be used in this case (when images define slides sizes):
        on: {
          lazyImageReady: (swiper) => {swiper.update()}
        }


Avoid recompilation

This PR adds a keyword argument use_distributed which can be disabled to disable parallel processing. Instead, everything will be executed in the same process which avoids recompiling for each process. This can be more quick in systems with few threads such as GitHub Runners depending on the workload.
Also, rename run_notebook to run_notebook! because it mutates the first argument.

0a21852 manages to avoid recompilation completely. All tutorials are evaluated in the same process

I've tested this on TuringGLM's tutorial building. Everything appears to be fine


feat(doc): add a simple readme to help new user get start

Hey @metrue
Thank you for your PR. I'll merge it!


[SPARK-39472][SQL][TEST] Refactor InMemoryTableCatalog classes hierarchy

What changes were proposed in this pull request?

This PR proposes to change the test classes *InMemoryTableCatalog hierarchy and unify the class name style.
In detail, this PR renames InMemoryCatalog to InMemoryFunctionCatalog to unify the name style, changes OneTableCatalog from extends InMemoryCatalog to BasicInMemoryTableCatalog to minimize the functionality.
Why are the changes needed?

before
BasicInMemoryTableCatalog (org.apache.spark.sql.connector.catalog)
  - InMemoryTableCatalog (org.apache.spark.sql.connector.catalog)
    - StagingInMemoryTableCatalog (org.apache.spark.sql.connector.catalog)
    - InMemoryPartitionTableCatalog (org.apache.spark.sql.connector.catalog)
    - InMemoryCatalog (org.apache.spark.sql.connector.catalog)
      - OneTableCatalog (org.apache.spark.sql.execution)
    - InMemoryStreamTableCatalog (org.apache.spark.sql.streaming.test)
    - InMemoryRowLevelOperationTableCatalog (org.apache.spark.sql.connector.catalog)
    - <anonymous> in getAnalyzer() in TableLookupCacheSuite (org.apache.spark.sql.catalyst.analysis)
  - TestLocalScanCatalog (org.apache.spark.sql.connector)
  - V1ReadFallbackCatalog (org.apache.spark.sql.connector)

after
BasicInMemoryTableCatalog (org.apache.spark.sql.connector.catalog)
  - InMemoryTableCatalog (org.apache.spark.sql.connector.catalog)
    - StagingInMemoryTableCatalog (org.apache.spark.sql.connector.catalog)
    - InMemoryPartitionTableCatalog (org.apache.spark.sql.connector.catalog)
    - InMemoryFunctionCatalog (org.apache.spark.sql.connector.catalog)
    - InMemoryStreamTableCatalog (org.apache.spark.sql.streaming.test)
    - InMemoryRowLevelOperationTableCatalog (org.apache.spark.sql.connector.catalog)
    - <anonymous> in getAnalyzer() in TableLookupCacheSuite (org.apache.spark.sql.catalyst.analysis)
  - TestLocalScanCatalog (org.apache.spark.sql.connector)
  - OneTableCatalog (org.apache.spark.sql.execution)
  - V1ReadFallbackCatalog (org.apache.spark.sql.connector)

Does this PR introduce any user-facing change?

No.
How was this patch tested?

Existing UT.

cc @sunchao would you please take a look if you have time?

Can one of the admins verify this patch?


Major fixes

Thanks !

Few more minor PRs would be coming soon. Needed this for a project. Thank you 👍

Awesome :) i will put docker compose on in today with complete how to as well 👍


Parse lockfile for expanded revision when toml has shortrev

https://github.com/pingcap/talent-plan/blob/dbd711344ff455f2d7942a494a0b97d0a6a6943c/rust/projects/project-4/Cargo.lock
^ The cargo.toml only stores the short rev (8cc906b) which Nix chokes on. The full revision is available in the lock file, we could grab it from there.

Fixed in #87


Moveable DirectionalLights

What problem does this solve or what need does it fill?
DirectionalLight shadow casting is tied to the world origin.
If you move a camera too far away from the origin, shadows disappear.
What solution would you like?
Allow the Transform component of any entity with a DirectionalLight to apply to its shadow casting.
Then, users could update the transform as the camera moves around the world.
What alternative(s) have you considered?
You might be able to update the frustrum of the DirectionalLight manually, but I was unable to get this to work.

An alternative solution is proposed in #3629

I implemented updating the projection based on the camera position here: https://github.com/superdump/bevy/commit/688b265380ef3620a6fcf852de2a76b5fe639ca7 it basically ensures the view frustum is covered but quality is poor because there’s too little shadow map resolution close to the camera and too much far away. So I wanted to instead get cascade shadow maps working.

You might be able to update the frustrum of the DirectionalLight manually, but I was unable to get this to work.

In case anyone wanted to try this approach, I experimented with this a bit. The DirectionalLight transform's translation seems to have no effect, but the rotation does. Once you have your rotation set for the angle of shadows, you just need to update the "box" in DirectionalLight's shadow_projection to cover where you're looking.
This might be tricky depending on what you're trying to do, but in my game I have a car heading in the positive x-axis direction, so I added a system that updates the directional light so that its shadow_projection.left is the car's X coordinate + 100.0 and the shadow_projection.right is the car's X coordinate - 100.0.
Here's a picture of it at the origin and then after driving to 2,544 X


Just a question about this framework

Hi, great work on this light framework! I am learning how to build a framework myself and found this very useful!
From the routing.py, I found following import:
from .app_types import ASGIApp, EventHandler, Receive, Scope, Send
from .config import settings
from .errors import HTTPError
from .redirection import Redirect
from .urlparse import Parser
from .views import View
from .websockets import WebSocket, WebSocketView

May I ask what are these import that start with "." ?
Thanks!

Hi, thanks for your kind words!
Those dots indicate imports relative to the package of the current Python module. To learn more about absolute vs. relative imports, I recommend this Real Python article: https://realpython.com/absolute-vs-relative-python-imports/

Hi Thanks for the link!
Never thought use . to import the file in the same directory.
Thanks!


When no p2p packet are available return -1 when calling getAvailableP2PPacketSize

Steam allow to send packet of size 0, currently the fact that this is returning 0 when no packet is available prevent handling such packet.
Most likely sending a 0 length packet is due to an error, but instead of crashing, currently the network code stop receiving packet (since we nee to check if packet_size > 0 to process the next packet)
NOTE:

This is a breaking change, I don't know how those are handled in the project.

Hey there!  I don't know this is particularly breaking; I think our examples would need a really minor adjustment.  Anyone using this older, deprecated Networking class may have to adjust but not sure if that would really have any effect for them.  Do you have any examples of 0-size packets?  I can't find any data about this anywhere; I'd presume there would be nothing if it was 0.

I'll provide a repro


Update README.md

Clarify the meaning of later.

Thank you. You are correct that it might have needed some clarification, but you where completely wrong with your fix... Have updated the text to hopefully be clearer.


[feat request]: add types

Thanks for this awesome wrapper project!
Right now, types are not loaded in the IDE,
so adding types would be nice!

Going to check this, thanks for reporting it

This is in v0.0.6, thanks to @franky47
@shunkakinoki let me know if isn't working, here works as expected

Working perfectly!!! Thanks for the fix!!! Love the lib!!!


Enhance scheduling capabilities for a group of pods

What would you like to be added:
Add a field like ScheduleMode. For scheduling a set of pods we may need more strict control. When deploying a distributed inference service, a set of pods, that is, a head plus several workers should be scheduled to neighboring nodes to reduce the communication cost between them.
Why is this needed:
There are many types of resources in a k8s cluster, and if the scheduling to nodes is constrained only by requests field, it is possible that the final distributed inference may not be too good.
An example is that a group of pods should be dispatched to nodes that have a special way of connecting to them, such as nvlink. Another example is that nodes in a cluster (a non-standard k8s cluster) may be across data centers, and a group of pods should be dispatched into the same data center.
Completion requirements:
I'm not sure about the eventual changes for the api, just an enhancement request. I'm also not sure if such a requirement is a reasonable enhancement request, and I'd be happy to contribute if it is.
This enhancement requires the following artifacts:

[ ] Design doc
[ ] API change
[ ] Docs update

The artifacts should be linked in subsequent comments.

@googs1025

An example is that a group of pods should be dispatched to nodes that have a special way of connecting to them, such as nvlink. Another example is that nodes in a cluster (a non-standard k8s cluster) may be across data centers, and a group of pods should be dispatched into the same data center.

In this scenario, each set of pods uses the same template, so the entire lws corresponding pods will be dispatched to the same data center. However, due to the fact that gpu is distributed in different data centers, so different groups of pods under lws should be scheduled to different data centers. So I think affinity or selector can't fulfill such requirement.

@googs1025

An example is that a group of pods should be dispatched to nodes that have a special way of connecting to them, such as nvlink. Another example is that nodes in a cluster (a non-standard k8s cluster) may be across data centers, and a group of pods should be dispatched into the same data center.

In this scenario, each set of pods uses the same template, so the entire lws corresponding pods will be dispatched to the same data center. However, due to the fact that gpu is distributed in different data centers, so different groups of pods under lws should be scheduled to different data centers. So I think affinity or selector can't fulfill such requirement.

Do different data centers signify the same cluster, or are they assigned to different clusters? If they are within the same cluster, it might still be feasible to utilize node selectors or affinity methods. However, if they are distributed across different clusters, there might be concerns regarding communication overhead.

If they are within the same cluster, it might still be feasible to utilize node selectors or affinity methods.

They belong to the same cluster, but how to schedule lws different groups of pods to multiple datacenters and each group of pods in the same datacenter by using affinity? I can't figure out a way to do this.

So, if I understand correctly, you want to schedule multiple pods under the workerTemplate to nodes in different data centers, is that correct? I cannot determine whether it is possible to achieve the desired functionality using node selectors or affinity. Additionally, I cannot assess whether it is a reasonable design to have scheduling decisions for the higher-level workload.

This higher-level workload don't need to make any scheduling decisions , it just needs to make sure the workers are scheduled in the same data center as the head. The head's scheduling is entirely decided by the scheduler.
One possible implementation could be to wait until the head is scheduled to a node, then retrieve a label from that node (this label's key is predefined on the lws yaml). Afterwards, the workers would add similar affinities, ensuring they get scheduled to similar nodes.

Thanks for bring this to the community, is this you need? https://github.com/kubernetes-sigs/lws/blob/main/docs/examples/sample/README.md#exclusive-placement

But this is exclusive, which means two groups can not be located at the same topology.

Thanks, that's what I'm looking for.

But this is exclusive, which means two groups can not be located at the same topology.

LeaderWorkerSet supports exclusive placement through pod affinity/anti-affinity where pods in the same group will be scheduled on the same accelerator island (such as a TPU slice or a GPU clique), but on different nodes. This ensures 1:1 LWS replica to accelerator island placement.

But I have a question, in the example, there are GPU and TPU accelerator islands. Does that mean I can only have two groups of pods? I feel like it should allow for multiple groups of pods within the same topology. Is it more reasonable to just ensure that the head and workers have the same topology key?

in the example, there are GPU and TPU accelerator islands. Does that mean I can only have two groups of pods?

Accelerator is only used for integrations with cloud providers, like TPU with google cloud.
So what you need is slightly different with exclusive placement. Do you have a real use case from your side?

My usage scenario is that there are many nodes in a k8s scenario, some of them are user's and some of them are cloud vendor's, to make it simple there are two datacenters, one for the user and one for the cloud provider. (This is not a standard k8s cluster, but I wonder if there is a need to schedule a group of pods to nodes of the same gpu type if there are many gpu resource types in a cluster)
I want to use lws to deploy inference services to the user's datacenter and the datacenter on the cloud. Although the network of datacenter on the cloud and the user's datacenter is interoperable, they are more expensive to communicate with and may require a public network, which is unstable.
So I want to make sure that a group of pods are dispatched to a single data center, so they can communicate easily. And multiple sets of pods are supported in one data center, and business peaks also require scaling.

Make sense to me as a group of Pods should be located at the same topology, and the group number should not be limited.
cc @ahg-g @liurupeng thoughts?

yes, we can support that by simply removing the exclusive anti-affinity term that is currently getting added. But we need to come up with a proper API first, similar to https://github.com/kubernetes-sigs/jobset/issues/75

@ahg-g  I would like to contribute to this feature. I can propose a KEP later. Is this good for you?

@vie-serendipity could you start the KEP so that we could start the review?

@liurupeng Okay, I will propose a KEP recently.

/subscribe

/remove-lifecycle stale


Compile failed!

I can't use this repo on vs2022,
it can compile but the generated library can't link, it seems like it's not ready yet!

Hi, you did not give lot of information. Anyway, do you compile correct files and defines ? See https://github.com/Lecrapouille/zipper/blob/16ebfebb25b1fc79f405d53326570fca2365d910/Makefile#L40

Hi,
Thank you. clearly I was missing them.

If it's working for you, would be nice to create a pull request since i'm not a windows user it's hard for me to give build system for other users.

@dangdkhanh I'm still interesting by your vs2022 build files, if you agree to share them :)


Fix mn typo

Broadcast time reported by tsanalyze command contains a typo in the minutes - mn instead of min.

Alright. Initially, it was not a typo, "mn" was intentional since it is a usual abbreviation for minute. However, according to Wikipedia, the SI symbol for minute is "min", not "mn". I respect that. I will merge it.

@lelegard as you mentioned that "mn" was not a typo, sorry for that, maybe I can change the commit message to be more appropriate in that sense, what do you think?

@lelegard as you mentioned that "mn" was not a typo, sorry for that, maybe I can change the commit message to be more appropriate in that sense, what do you think?

@rubenochiavone, don't worry about the message, only the code is important.
Merged.


[help] transfer settings to another computer

Hello wich files and where do i need to transfer to another computer? How to make it work with atom-sync ? thanks
os: Windows 10

ok im sorry didnt see the import export feature.
the file was project-viewer.json
case closed


commit 1

Added About us feature. Corrected as per our chat. working on Working days.
Francesca- Can you put About us link on Manager Homepage

There are still 2 controllers folders(Controllers and controller)


Issue-cf-flake

Overview

What is it?

[ ] Feature / enhancement
[ ] Bug
[ ] Docs / tests / types / typos

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Use cases and why

One use case

Another use case

Checklist:

[ ] My code follows the developer guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

I believe this is no longer needed


added the parser

would u plz try to fix the build errors?

Hi @seenureddy
Looks interesting!
I don't see where you're actually doing something with the backport of the LAXOptionParser.
If would be also great if you could provide a test so it's clear what you're trying to fix here.

Not sure about the state of this, but you could try rebasing it first.

I'm not sure what the correlation is between this PR and https://github.com/jazzband/django-configurations/issues/65#issuecomment-68948641.
Is this PR obsolete (and we can close it) or does it address a different topic?


Integrate llvm-project at 0c852dc88e9276b74532fd7d233dd23ec1bbed6f

Reset third_party/llvm-project: 0c852dc88e9276b74532fd7d233dd23ec1bbed6f (2023-05-09 07:42:20 +0000): [clang][dataflow][NFC] Remove SkipPast param from getValue(const ValueDecl &).
Reset third_party/mlir-hlo: 768b11e9baa9b2e8b153b84c6e2403b048935dfe (2023-05-09 08:24:44 -0700): [XLA:CPU Next] Outline reduce fusion clusters.

Update ops implementing the CallOpInterface.

I am surprised Mehdi's changes made it in to integrate so fast. Are we sure that is in?

Yeah, this is a fresh fresh llvm commit (from this morning). I checked and I can see the UB check that @okkwon listed in: https://discord.com/channels/689900678990135345/1080178290188374049/1105178214239830086

"Regressed Compilation Times" values are high, but look to be within the noise for those series.

"Regressed Compilation Times" values are high, but look to be within the noise for those series.

Yeah compilation time is not very stable now..


Discuss how to manage GA releases

Right now, Alloy is composed by a list of modules that have independent release cycles; for example, the UI module could be on version 1.0.4 and modeling module could be 1.0.6 .
There is no concept of GA release (ie, Alloy 1.0, which includes UI 1.0.4 and modeling 1.0.6) and we were debating whether it was something needed.
From a technical standpoint, there is no need for a GA release, and the absence of it allows modules (and teams) to have a leaner way to develop software (granted that code is constantly tested across all versions, see https://github.com/finos/alloy/issues/130).
We wanted to keep track of this discussion to understand what's the opinion of the rest of the team.

[As discussed on June 9 meeting] Assuming we don't insist on GA releases, next question would how do we brand releases -- i.e., how would we brand a release that is, say, Alloy 1.0.1, UI 1.03, and modeling 1.04. Key question is how do we brand new releases - suggestion is that we do roll-up releases vs headline releases.
Suggestion made to also make sure we have release notes to describe what is in a release.

I think that we're good for the go-live, yes (removed label)
But I'd like to discuss this before the next big release, as I believe that there should be a bit of strategy on how to cut general releases, regardless of the modular nature of the project.

@beekemarie @epsstan FYI this is what we discussed last week, let's use this issue to discuss next steps, starting from
https://legend.finos.org/docs/advanced/legend-docker-image

@agitana @maoo can we close this issue?

Yes, see https://legend.finos.org/releases


Difference between Sandbox Dashboard and API result

Hello,
I am facing a strange behavior : I have pushed several KYC documents to user (with several different status). They all appear correctly on the Sandbox Dashboard (and correctly attached to the user, but when I call GetKycDocuments() from the PHP SDk I don't receive the whole list. In fact 3 validated documents are not listed.
Did I miss something or is there a problem somewhere?
Also when grabing the LegalUser object the values for LegalRepresentativeProofOfIdentity, ProofOfRegistration and ShareholderDeclaration are null even if I have provided and validated them.
Thank you.

Hi @fleflochN
Indeed these parameters are inputs and not filled automatically.
Regards,
max


[focus] Change the namespace name.

As suggessed in #48 the fmk namespace should be named focus. But for compatibility issues, the Fmk namespace should also be created.

Changed with the module rewrite #22


Feature request - Foldable items

Good morning,
Is there the possibility of implementing an expandable folding function for the items?
For example I have the item "Test" and, by clicking on this, several items expand (Test 1, Test 2. Test 3, etc. ):

Test
-- Test 1
-- Test 2
-- Test 3

I think it would be very useful, for me but also for many other users who would like to have this functionality.
Thank you

Hi @Jonny-T-cyber,
Please, consult this discussion and my answer there. That would not be an easy task to do and it would require a lot of work and maintenance, but if you think that there are many users that would like to have that functionality try to revive this feature request. If it gets traction among the community members and it is not implemented in Home Assistant I would consider to implement it in this custom plugin.
Regards

Hi @Jonny-T-cyber,
Moving this to a discussion.


remote debugging isn't working

VSCode Version:1.4.0
OS Version:ubuntu 16.4

Steps to Reproduce:

run an app on debug more node --debug
try to connect to the remote server ip running the debugger
it will stop if you specified the --debug-brk option on the first line but once when you hit continue it no longer stops in the break points you specify in vscode

not: i havent tried using debugger keyword inside code since its already on the server its not the best way i think

@NikosEfthias please read the section "Remote Debugging Node.js" in https://code.visualstudio.com/docs/editor/debugging for learning how to map local and remote paths by using localRoot and remoteRootattributes. Without this, breakpoints won't work.

@NikosEfthias could you solve the issue by setting the localRoot and remoteRoot attributes?

hi sorry i didnt have time yet on weekend hopefully i will try

hi @weinand shoudl i pass a full remote path something like /home//

The output of the remote node.js is only available on the remote system. VS code has no access to it because VS Code did not launch the remote node.js.


That's fantastic, @tucotuco ! I can't believe how many typos, formatting errors, etc. that you found. They should have never been in the original document. It all looks good to me.

Yay!


Test scalability of hyperparameters setting

Linking this to task #77 for @5u6r054 to test at scale.
Since we currently don't know if the provided implementation can support more than 1 node, we want to scale testing of the implementation.
Action items:

[ ] Create a test that allows spinning up more nodes in the subnet (e.g. 1000 "fake" nodes)
[ ] Make sure that implementation is solid enough by running the test suite - otherwise create follow-up tasks

Out of scope for this week's planning. Would suggest to keep it on No Status

Since starting Q3, this enters the current scope. However, I think this is blocked by Docker images/Docker-compose to be able to have a testing environment.
I'm open to suggestions that tell other opinions but as of now I think it's:

Blocked by #85
Blocked by #109
[Maybe] Blocked by #111

Since starting Q3, this enters the current scope. However, I think this is blocked by Docker images/Docker-compose to be able to have a testing environment.
I'm open to suggestions that tell other opinions but as of now I think it's:

Blocked by Set up subtensor, miner (with masa protocol worker) and validator using docker compose #85
Blocked by ci: Container images release #109
[Maybe] Blocked by Github action to deploy devnet (opentensor subtensor instance with a subnet) #111

Might still be blocked, however the competition could prove to be such test of hyperparameters. Would require more info on what's the expected output of this task. Maybe it is enough with the competition and we just need to define the output of this task rather than the steps to complete it.
Think this still needs triage by the @masa-finance/subnet team as a whole

Since starting Q3, this enters the current scope. However, I think this is blocked by Docker images/Docker-compose to be able to have a testing environment.
I'm open to suggestions that tell other opinions but as of now I think it's:

Blocked by Set up subtensor, miner (with masa protocol worker) and validator using docker compose #85
Blocked by ci: Container images release #109
[Maybe] Blocked by Github action to deploy devnet (opentensor subtensor instance with a subnet) #111

Might still be blocked, however the competition could prove to be such test of hyperparameters. Would require more info on what's the expected output of this task. Maybe it is enough with the competition and we just need to define the output of this task rather than the steps to complete it.
Think this still needs triage by the @masa-finance/subnet team as a whole

+1
Suggest we close this since iteration over the subnet is being done on the fly by the needs of the environment. This might be already redundant or outdated by now

Obsolete now since we are on the mainnet already, and scaling works.


API access problem.

Which version are you using?
v0.21.6
Which operating system are you using?

[ ] Linux amd64 standard
[ ] Linux amd64 Docker
[ ] Linux arm64 standard
[ ] Linux arm64 Docker
[ ] Linux arm7 standard
[ ] Linux arm7 Docker
[ ] Linux arm6 standard
[ ] Linux arm6 Docker
[x] Windows amd64 standard
[ ] Windows amd64 Docker (WSL backend)
[ ] macOS amd64 standard
[ ] macOS amd64 Docker
[ ] Other (please describe)

Describe the issue
When i try to make the webserver get the api information it receives an error of CORS
"Access to XMLHttpRequest at 'http://localhost:9997/v1/paths/list' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource." I already tryed some ways to get around in the frontend but nothing.
Describe how to replicate the issue

It happens when i have the api on normal port 9997 and webserver on 3000 and if webserver sends a fetch to api receives that error but if i do CURL on console to the api it works as normal.
Did you attach the server logs?

"2023/03/31 15:35:50 DEB [API] [conn <IP_ADDRESS>] GET /v1/paths/list
2023/03/31 15:35:50 DEB [API] [conn <IP_ADDRESS>] [c->s] GET /v1/paths/list HTTP/1.1
Host: localhost:9997
Accept: application/json, text/plain, /
Accept-Encoding: gzip, deflate, br
Accept-Language: pt-PT,pt
Connection: keep-alive
Origin: http://localhost:3000
Referer: http://localhost:3000/
Sec-Ch-Ua: "Brave";v="111", "Not(A:Brand";v="8", "Chromium";v="111"
Sec-Ch-Ua-Mobile: ?0
Sec-Ch-Ua-Platform: "Windows"
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-site
Sec-Gpc: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
2023/03/31 15:35:50 DEB [API] [conn <IP_ADDRESS>] [s->c] HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Server: rtsp-simple-server
(body of 12 bytes)"
Did you attach a network dump?

no

port 3000? is that a nodejs application? You could have your node application proxy the api
https://dev.to/bornfightcompany/bypassing-cors-via-custom-proxy-backend-2po

Yes that must be the problem the link you sent is quite right. I will test when i can and thanks.


Available for mac?

How i can use this on mac? i did make install but command not found windscribe-proxy
I tried install it on ubuntu server, same problem.

Hello,
Installed binary should be in ~/go/bin/windscribe-proxy (where ~ denotes home directory).
Alternative option is to use binary downloaded from releases page (MacOS binaries are ones with darwin in their names).


Non-existing modules are not reported

Create a file with the following code:
\open ::Foo
Then the error that Foo does not exists is not reported.

[Loaded] ::Prelude
[Loaded] ::Test (../vclang-lib/lib/Test.vc@1492696857000)
[ERROR] ../vclang-lib/lib/Test.vc@1492696857000:1:1: Module not found: ::Foo
--- Checking ---
[✓] ::Test
--- Done ---

Looks like it is reported.
Currently, there is no way to influence the tick, since the tick indicates the result of typechecking definitions, which, in this case, clearly succeeded.


cover MQTT issue with configuration file and web ui controls.

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.27
Python release (python3 --version):
3.4.3+
Component/platform:
Cover MQTT
Description of problem:
Cover MQTT component does not accept service_open, service_close as indicated by docs.  Leaving these optional items off allows the component to load properly, but no controls are shown on web ui
Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:
Traceback (if applicable):
hartmms@yzf600:$ hass --script check_config
Testing configuration at /home/hartmms/.homeassistant
16-08-28 18:17:05 INFO (MainThread) [requests.packages.urllib3.connectionpool] Starting new HTTP connection (1): maps.googleapis.com
16-08-28 18:17:05 WARNING (MainThread) [homeassistant.config] Incomplete core config. Auto detected elevation: 411
16-08-28 18:17:06 ERROR (MainThread) [homeassistant.bootstrap] Invalid config for [cover.mqtt]: [service_open] is an invalid option for [cover.mqtt]. Check: cover.mqtt->service_open.
Failed config
  cover.mqtt:
    service_open: up
    name: Awning
    platform: mqtt
    state_topic: home/outdoor_blinds/awning/status
    service_closed: down
    qos: 1
    command_topic: home/outdoor_blinds/awning/set
    state_open: up
    state_closed: down

Additional info:

@turbokongen

Also, it would be great if the "stop" function was back.  I have Somfy roller shutters that have an "up", "down", and "my" button. I used the "stop" as a proxy for the "my" feature.  The my button either stops the blinds while in operation, or moves them to a preset location.
FYI - I wired up a spare Somfy remote to a Particle Photon wireless wifi that has an MQTT subscribed to the proper hass topic for contro/status.

This was a documentation error. It's been fixed now.
Please reopen if other issues.


WIP: add retry interceptor

@UDarya How do u think about 429 error code?
Please also check Retry-After header

@gokulchandra Probably u will have a moment to have a look at this PR


[WIP] No backspace key?

Seem it is not possible to delete code in the editor.
I will propose a fix, it is an opportunity for me to propose my first patch to the project 😄

The code editor is still nothing...

So do you have an idea where I could start to help you on the WIP branch?

Fixed this :3


Fix incorrect menu item title for starting streaming logs.

@leemcmullen : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good (text and alt text changes match the UI in the screenshot); merging. Thanks.


clear up gradle config

write a config.gradle to config all the gradle in the progject

Could I push it to dev branch?


Republish please.

Hi Raphael,
Thanks for merging my changesets. Glad to be away from maintaining my own local fork. If you could please run npm publish now that you have merged those changes.
G.
Edit: It might be a good idea to enable "issues" on this repository for non-code discussion.

Hi,
Didn't expect anyone would use this fork. Will publish the changes ASAP.

Republished

Unfortunately, the main branch is abandoned, your fork is the best alternative! If you abandon this one eventually I'll probably republish and try to maintain my own fork, at least until Material UI 1.0 is out. :)


This command only works in a clone of flowtype/flow-typed. It is a tool used to validate the library definitions flow-typed project.

I have been trying to enhance some of the type definitions but running on windows does not seem to be fully supported and I was not able to run the required unit tests.
I started by creating a run_def_tests.cmd version of run_def_tests.sh that looks like this:
cd definitions
call npm install
call npm test
cd ..\cli
call npm install
node dist\cli.js validate-defs
node dist\cli.js run-tests %*

and it seems to work but:

when running eslint npm/**/test* I get a large number of warning and an error:

D:\MyDev\doberkofler\flow-typed\definitions\npm\react-redux_v4.x.x\flow_v0.30.x-\test_Provider.js
  6:11  error  Parsing error: Unexpected token, expected ,

Is this expected?

Later when processing the script, I get the following error message:

D:\MyDev\doberkofler\flow-typed\cli>node dist\cli.js validate-defs
This command only works in a clone of flowtype/flow-typed. It is a tool used to validate the library definitions flow-typed project.

clearly I am working in a cloned repository and I have no idea what this is about?

More generally speaking, I'm surprised why there are so many open pull requests and was wondering, if this is just a backlog or something else?

This is probably because this detection method is a bit to naive.


[BUG] DCID's for genomes missing from search

Describe the bug
Missing results for ENCODE related searches.
@spiekos could you add some examples here that don't work?

Search on the dcid no longer works. This leads to no results being returned when you search for things like:
CHEMBL102202
TP63
ChemicalCompound
These previously would return the correct nodes under the old method in which the search operated only on the name property of entities.

@spiekos the old search functionality will be available again at datacommons.org/search_dc after our next push to prod. Sorry for the trouble!


Adding className prop and additional tests

This is a great wrapper package. I created this PR in order to allow users to append a className to the wrapping Input <div />. I explored the option of actually adding Wrapper to components, this would allow a user to use any component they liked as long as it was wrapped with React.forwardRef. I opted against making this change for this commit as I thought it could be confusing for a user who isn't aware of how forwardRef works, but perhaps in the future this could be added.
In addition to the className changes, I added a few more tests and a Loqate class to consume the responsibility of handling the URL construction to the already difficult to use Loqate API.
I think this is a great package, and would have saved me a lot of time early last year when we started using Loqate with React.

Thanks for the excellent PR. I have reviewd & merged it. Will release soon.


Add filter for time

TODO:

Allow exporting records for a particular time and date range

Here's an example implementation for filtering by start and end date in another very similar project (patterned after this one) that exports music player event data from Firebase:
https://github.com/CUTR-at-USF/muser-firebase-export/pull/13


14000571_ds- Tributary to Houston Tommy Creek

[ ] missing temp and cond data. Only turbidity on fiss site card. No other info available in 14000571_us. Leaving open in case #92 resolves this missing data.
[x] Turbidity missing. Added from fiss site card.
[x] total_cover set to moderate but fiss site card says trace. Photos suggest moderate is more appropriate. Leaving as moderate.
[x] instream_vegetation_type set to none but fiss site card says Vascular plants.
[x] clean up comments

added temp and cond from 14001106


@conda-forge-admin, please add bot automerge

Additional comment:
@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/de-jobsuche-feedstock#2.


updated v0.8.1

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

We released a version 1.0 so this will be the maintenance branch for version 0.8.x

@conda-forge-admin, please rerender


2 errors - not defined

4:8  error  'VueSocialSharing' is defined but never used  no-unused-vars
6:9  error  'SocialSharing' is not defined                no-undef

so tried this:
import VueSocialSharing from "vue-social-sharing";
Vue.use(VueSocialSharing);

but then this:
vue-social-sharing.js?bd8c:1 Uncaught TypeError: Cannot read property 'networks' of undefined
I guess there's an error after the update. Used it 2 weeks and was working perfectly.

Hello @bogdanfer, thank you for raising this issue.
I indeed failed the last beta build, it is now fixed.
It looks like you upgraded from vue-social-sharing v2 to v3 ? If that's the case take a look at the documentation as a lot of things have been changed between the two versions.


Clarify what "dimensions" are 🤔

I'm coming from Influx and learning about Prometheus.
At https://prometheus.io/docs/practices/naming/, I see

A metric name should represent the same logical thing-being-measured across all label dimensions.

then later

As a rule of thumb, either the sum() or the avg() over all dimensions of a given metric should be meaningful

I gather dimensions are points, i.e. float64 values? This is counter-intuitive, because when I think of "multiple dimensions", I think of separate concepts: height, width, length, weight etc. rather than values that change over time.

It's usually better to open support requests under discussions. That being said:
The dimensions are labels and their values. Every label is a new, orthogonal dimension, their values are the position alongside said dimension.

My request wasn't to clarify dimensions for me, but for new learners. Hence I think this clarification should be made in the documentation, rather than OOB in a support request.


[Feature Request]: standard error codes

Implementation ideas
Implementations should return standard error codes so that clients have a way to handle the error and retry if possible.
We can reuse JSONRPC error codes in the range --32000 to -32099 , clients should map their errors into the standard error codes for e.g.:

32001 - request timeout
32002 - mempool congested
32003 - insufficient fee
32003 - incorrect sequence / nonce
32004 - blob size too large

gRPC can reuse the JSONRPC error codes for simplicity.
Based on the error, the client can retry with a higher fee, different nonce or smaller blob.
Implementations should wrap their error with the corresponding typed error.
E.g.:
pkg someda

...
var (
	// Err32003 is returned when the blob transaction has insufficient fee
	Err32003 = errors.New("32003")
)
...

// Submit submits the Blobs to Data Availability layer.
func (c *SomeDA) Submit(ctx context.Context, blobs []da.Blob, gasPrice float64, ns da.Namespace) ([]da.ID, error) {
        ...
	height, err := c.Submit(ctx, blobs, gasPrice, ns)
	if err != nil {
		if errors.Is(err, ErrInsufficientFee) {
			return errors.Wrap(da.Err32003, err)
		}
		return nil, err
	}
        ...
}

@tuxcanfly when do we expect this error? 32002 - mempool congested?

@tuxcanfly when do we expect this error? 32002 - mempool congested?

When blob transactions are failing to be included in blocks due to mempool being full. It would signify two things:

this is a temporary error
it may be retried with a higher fee or higher priority fee when fee market is implemented

@tuxcanfly when do we expect this error? 32002 - mempool congested?

When blob transactions are failing to be included in blocks due to mempool being full. It would signify two things:

this is a temporary error
it may be retried with a higher fee or higher priority fee when fee market is implemented

is this different from 32001 - request timeout?

is this different from 32001 - request timeout?

Yes, it indicates a generic connection error and maybe retried without modifying the transaction.

@tuxcanfly I like this. What are your thoughts on introducing some kind of error for this use case (ie: blob not found) https://github.com/celestiaorg/celestia-node/issues/3292 (there's a lot of context in that thread, sorry)


Add -local flag to llms/hf_llm/convert.py for reading source HF models from filesystem.

This PR is to add a local flag (-l, --local) to convert.py to enable the reading of HF Models already on the filesystem during a conversion operation. Currently the script has to download the model weights from HF directly before beginning the conversion to MLX format.
Setting the --local flag disables uploads to huggingface during conversion as the hf_path argument would not specify the original model in the modelcard.

I consolidated the fetch_from_local and fech_from_hub functions into one. Though I kept the fetch_from_hub function name as-is. Let me know if you'd like to change that to just load_model or something more neutral as it is not technically fetching from the hub if local=True is passed.
I also removed all the code related to non-safetensors.

@awni , I think I've incorporated everything from your initial review. Please let me know if there is anything else for this PR.

Thanks a ton! I will check it shortly!


React App is not working in IE11 or below

Hello all, this may be very common issue and so many answers are available on internet for the same & I have tried most of them but nothing worked in my case I am posting a stack-overflow link for my question
https://stackoverflow.com/questions/59550650/my-react-app-is-not-rendering-in-internet-explorer-because-of-arrow-function

@peeyushsingla my issue is not resolved yet . can you please let me know what to do ?

Its hard to understand from the files, if I can reproduce may be I can check

BTW issue is also fixed in CRA release

Check this
https://stackoverflow.com/questions/60105051/react-ie11-support-easy-way-cra-3-x

Its hard to understand from the files, if I can reproduce may be I can check

My setup is with django+python+react as you can see in the upper layer there is django + python setup and a folder named react which contains react files

this is react files structure apart from this all the configuration files are attached in the question

add this to your package.json
 "resolutions": {
    "react-dev-utils/chalk/ansi-styles": "https://github.com/codercodingthecode/ansi-styles"
}

@peeyushsingla I have tried by creating simple new CRA app and tested it and it worked on IE :) , I think something is missing in my package.json/webpack.config/babelrc file can you please help me by finding it

Can you elaborate on the steps you took to make it work? I'm having the same issue and also created a test app but with no success. Here's the flow:

npx create-react-app test-app
cd test-app
npm i react-app-polyfill
add 'react-app-polyfill/ie11' and 'react-app-polyfill/stable' to line 1 & 2 of index.js
revert react-scripts to 3.2.0 in package.json
add "ie 11" to browserlists -> development in package.json
rm -rf node_modules/.cache/
npm run start

Runs fine in Chrome as expect with the spinning React icon, but only shows "You need to enable JavaScript to run this app. " on IE 11.

@peeyushsingla I have tried by creating simple new CRA app and tested it and it worked on IE :) , I think something is missing in my package.json/webpack.config/babelrc file can you please help me by finding it

Can you elaborate on the steps you took to make it work? I'm having the same issue and also created a test app but with no success. Here's the flow:

npx create-react-app test-app
cd test-app
npm i react-app-polyfill
add 'react-app-polyfill/ie11' and 'react-app-polyfill/stable' to line 1 & 2 of index.js
revert react-scripts to 3.2.0 in package.json
add "ie 11" to browserlists -> development in package.json
rm -rf node_modules/.cache/
npm run start

Runs fine in Chrome as expect with the spinning React icon, but only shows "You need to enable JavaScript to run this app. " on IE 11.

apart from step #5 I did the same and it is working for me may be you have to enable javascript for IE

"resolutions": {
"react-dev-utils/chalk/ansi-styles": "https://github.com/codercodingthecode/ansi-styles"
}

not worked :(

@scwong93 I guess you need to enable JS


MedicationAdministration should not override a value set as medicationUseStatus

Currently if MedicationAdministration does not have a medicationUseOccuranceDateTime, then the medicationUseStatus is overridden to unknown.  If the use status is provided, it should be retained.
medicationUseOccuranceDateTime will cause a MedicationStatement to be created and it defaults to "unknown" if a medicationUseStatus is not provided.   Thus a default is already accounted for.
Change code so if a medicationUseStatus is provided, it is retained.

@LisaWellman FYI.

Included in release 1.1.0 https://github.com/LinuxForHealth/CsvToFHIR/releases/tag/1.1.0


How to handle timeouts

Hi, I'm trying to send an http get or post request and then execute some code if the request timed out.
I'm not sure if I can define a timeout handler with this library. Anyone have any ideas?

Docs have an example on adding timeout handler.
https://github.com/daltoniam/SwiftHTTP#global-handlers

version 3.0.0
HTTP.globalRequest { req in     req.timeoutInterval = 5.0     return }
Get error: Cannot assign to property: 'req' is a 'let' constant
@daltoniam


[1pt] Switch badges for Rockets - Conditional components

Rockets that have already been reserved should show a "Reserved" badge and "Cancel reservation" button instead of the default "Reserve rocket" (as per design)
Use the React conditional rendering syntax:
{rocket.reserved && (
    // render Cancel Rocket button
)}

Hello @rachidelaid, kindly review:
https://github.com/fobadara/rocket-space-missions/pull/41


Remove f-string for < 3.5 support

Hello! For issue plotly/jupyterlab-dash#26
Format() method work out of the box with with Python 2.7, 3.2, 3.3, 3.4, and 3.5.

Sorry, about the delay in merging/releasing this fix.  Dash 1.0 just came out and JupyterLab 1.0 will be out in the next few days, so we'll try to do another release soon after.


Scrolling using vim-smoothie lags when lualine.nvim is enabled

nvim --version:

NVIM v0.5.0-dev+972-g84faeb07d
Build type: RelWithDebInfo
LuaJIT 2.0.5

latest versions of both plugins
terminal: kitty 0.19.3 (also occurs in xterm)

Scrolling using vim-smoothie while lualine.nvim is enabled produces lag, especially towards the end of the scrolling motion.  This does not occur while using vim-airline (though lualine.nvim is the first statusline plugin I've ever used, but I had to test with another one).

It is less noticeable using the default scroll speed (let g:smoothie_update_interval=10), but when using let g:smoothie_update_interval=5, a slower scroll speed it becomes immediately apparent. The last few last to-be-scrolled take a second to go by.

This does not happen on my system unless I set g:smoothie_update_interval=1, even on xterm.
Keep in my that vim-smoothie is really cpu heavy as shown below

But no lag happens when lualine.nvim is not installed so this is definitely an issue, I will try to resolve this asap.

Yeah the less delay between update the more lag there is, without lualine I can get a very smooth motion with it set to 5, with it not so much. I love the plugin, hope you get it resolved!

can you try setting up lualine this way?
require('lualine').sections = {
  lualine_a = { 'mode' },
  -- lualine_b = { 'branch' },
  lualine_c = { 'filename' },
  lualine_x = { 'encoding', 'fileformat', 'filetype' },
  lualine_y = { 'progress' },
  lualine_z = { 'location'  },
}

I think the branch function might be a problem

Using that I get this:

try this way
    local lualine = require('lualine')
    lualine.sections = {
      lualine_a = { 'mode' },
      -- lualine_b = { 'branch' },
      lualine_c = { 'filename' },
      lualine_x = { 'encoding', 'fileformat', 'filetype' },
      lualine_y = { 'progress' },
      lualine_z = { 'location'  },
    }
    lualine.status()

Yeah that works, it doesn't lag anymore!

Great! Thanks for pointing that out. I know why this is happening but I have a more universal fix in mind than just fixing the branch function.
Some functions like branch, fileformat should probably only run once per file, not on every update like this is happenig like now.
I will try to resolve this next friday. You can keep using lualine without the branch functionality for now or try creating a pr.

I'm not super familiar with the Lua API but why not make the calls async with vim.loop instead?

I'm not super familiar with the Lua API but why not make the calls async with vim.loop instead?

Yes function like branch have to be made async as well. Thanks for pointing vim.loop out, it looks like it could be an easy to implement solution.

could you confirm if https://github.com/hoob3rt/lualine.nvim/tree/async solves this issue?

could you confirm if https://github.com/hoob3rt/lualine.nvim/tree/async solves this issue?

yeah, seems to be fixed, nice.

yeah, seems to be fixed, nice.


aria-multiselectable=true reported as invalid on element with role=tablist

Tested on
Chrome 49.0.2623.110
Accessibility Developer Tools 2.10.9
[Severe] This element has an unsupported ARIA attribute (1)
See AX_ARIA_10 for more information.
<div id="accordion" class="panel-group " role="tablist" aria-multiselectable="true">
[...]

AX_ARIA_10 says that "Many ARIA attributes (states and properties) can only be used on elements with particular roles". According to W3: aria-multiselectable is used in roles: grid, listbox, tablist, tree.
Cheers, and thanks for this cool software.

Thanks.
Duplicate of #289


Enable provider config, update README

Following the Strapi 3.x documentation the extension should be activate in the ./extensions/upload/config/settings.json path.

Hello @MiguelSavignano, thanks for your PR, but I had work on a new release with full configurations options.
Feel free for any suggestion, I close your PR. Thanks !


What about switching Vulkan.dll to .NET Standard?

As far as I understand PCLs are dead. Is switching Vulkan.dll to .NET Standard a good idea?

It is good idea. There are some issues in Xamarin.Android and .NET standard right now though. Once they are fixed I am all for it.

@TillAlex I maintain some bindings here which support .NET Standard. They are very different in style from the bindings here, though -- closer to native Vulkan.

@mellinoe Is vk compatible with Xamarin?
@TillAlex Most of the actively maintained .NET Vulkan libraries support .NET Standard; vk is a great low-level implementation, I maintain SharpVk which is closer to VulkanSharp's API, and VulkanCore is a hand-coded binding specifically for .NET Core.

@FacticiusVir It should be compatible, yeah. But like @radekdoulik mentioned, there are some problems with Xamarin + .NET Standard at the moment.

Is any of those library tested with MoltenVK? I'm statically linking MoltenVK into my app. As I don't get dllmaps working I have to change the DllImports in code to make it working with VulkanSharp.

@TillAlex I've tested my library with MoltenVK, but not on mono/Xamarin. Only on .NET Core/macOS.


criterions of training and test are mixed up

https://github.com/LayneH/SAT-selective-cls/blob/dc5559358b6bf59e23ce988baa6b8430626c8822/train.py#L200-L201
It might be a mistake to use the same criterion in function train and function test, which mixes up histroy of predictions of the model on training set and that on test set .

Thank you for pointing it out.
This is indeed a bug in our code that we should not pass the SAT criterion to the test() function.
I have rerun the experiments after fixing this bug and found that the performance is slightly improved.

Could you push your updated code to this repository? I did not get better performances after I fixed the bug and reran the experiments.

Hi,
Please refer to the latest commit. The scripts should produce slightly (if noticeable) better results than the reported ones.

Hi,
I find that even though I use updated code, I can not reproduce the results on CIFAR10 as reported in your paper. My results are following:

coverage
mean
stantard devariance

100
6.008
0.138

95
3.724
0.028

90
2.064
0.045

85
1.187
0.031

80
0.656
0.002

75
0.406
0.051

70
0.298
0.055

As the table shows, the selective error rate for 95% coverage is 3.72%, which is far away from (3.37±0.05)%. Could you help me solve this problem?

I am sorry for not explaining mean and standard deviation in the last comment. In the table of the last comment, mean and standard deviation refer to mean of selective error rate and standard deviation of selective error rate respectively, which are calculated over 3 trials.

Hi,
It seems that most entries are pretty close to or better than the reported ones in the paper except the case of 95% coverage.
I have checked the experiment logs and found that some of the CIFAR10 experiments (but none of the experiments on other datasets) are based on an earlier implementation of SAT, which slightly differs from the current implementation in this line
# current implementation
soft_label[torch.arange(y.shape[0]), y] = prob[torch.arange(y.shape[0]), y]
# earlier implementation
soft_label[torch.arange(y.shape[0]), y] = 1

You can try this to see the performance.

Hi,
I reran the experiments and got results as following (with the earlier implementation of  SAT). mean and std dev refer to mean of selective error rate and standard deviation of selective error rate respectively in this table.
Test	mean	std dev
100	5.854	0.216
95	3.603	0.133
90	1.978	0.117
85	1.109	0.046
80	0.683	0.070
75	0.433	0.044
70	0.303	0.031

The performance is better than that of the current implementaton of SAT. But the selective error rate of coverage 95%, 3.603%, is still not so good as the reported one, (3.37±0.05)%, in your paper. Perhaps you had made a clerical mistake in your paper?

Interesting reproduction analysis, did this eventually get resolved?
Should one use the main branch for reproductions?

Interesting reproduction analysis, did this eventually get resolved? Should one use the main branch for reproductions?

No, I gave up. This repository does not provide the random seed manualSeed, making it challenging to reproduce the results.

Might I ask you if you know of any other selective classification methods that 'actually work'?
I was looking into self-adaptive training as well, which seems related.

As far as I know, Deep Ensemble [1] really works and might be the most powerful method. However, considering the heavy computational overhead of ensemble models, recent work in selective classification focuses on individual models. These models (e.g., [2][3]) exhibit marginal improvement from Softmax Response [4]. The advance in this line of work seems neither significant nor exciting. Nevertheless, my survey might be not comprehensive. A more comprehensive survey might be found in [5][6].
[1] Lakshminarayanan et al. Simple and Scalable Predictive Uncertainty Estimation using Deep Ensembles. In NIPS, 2017.
[2] Liu et al. Deep Gamblers: Learning to Abstain with Portfolio Theory. In NeurIPS, 2019.
[3] Feng et al. Towards Better Selective Classification. In ICLR, 2023.
[4] Geifman and El-Yaniv. Selective Classification for Deep Neural Networks. In NIPS, 2017.
[5] Gawlikowski et al. A Survey of Uncertainty in Deep Neural Networks. arXiv:2107.03342.
[6] Galil et al. What Can we Learn from The Selective Prediction and Uncertainty Estimation Performance Of 523 ImageNet Classifiers? In ICLR, 2023.


use preprocessor to map define'd constants/macros

as discussed here https://gitter.im/nimgen/Lobby?at=5bf638386621313894fbddac
links
https://stackoverflow.com/questions/2224334/gcc-dump-preprocessor-defines

I believe this is now implemented with -dD. We need to add tests though.

This seems as appropriate an issue thread as any to chime in, but I saw that I think you (shashlick?) in IRC a few days ago asked about cligen handling -I multiple times or probably similarly for -D.  No one seemed to answer you, and I suppose there's a chance you tried it and saw that it "just worked", but its CL usage is a little subtle.
An explicit = or : or long option param separation causes things to "reset" to the argument.  So, --defines=def0,def9 will clobber any existing seq with just ["def0", "def9"].  A short option (if you added short={ "defines": 'D', "includeDirs", 'I' } ) would let the CLI user say -Ddef1 -Ddef2 with the intended accumulating meaning. They can also use an explicit append mode via --defines+=def3 and even a prepend mode -I^=earlierpath.  I found it a little tricky balancing the "need to reset" with the principle of least surprise, and this is only really in the documentation for argcvt.  I could be convinced that maybe "reset and assign" should be spelled .= or something.  There's been talk of the need for a --help-syntax or something more to guide CL users.
If you hate this syntax, you can also override all of this default syntax by just by doing an import cligen, cligen/argcvt and, between that import and the dispatch.  defining your own version of proc argParse*[T](dst: var seq[T], ... .  It's only a 19 line proc in cligen/argcvt.nim, but you might also need to learn some more internals to do it.

@c-blake - thanks for chiming in. I wasn't able to since the += and ^= syntax isn't obvious and there weren't any examples either. I also just tried to see the argcvt docs and it doesn't seem to work. Says table not accessible.
That being said, @timotheecour has already migrated nimterop to use cligen. Here's the syntax so far:
Usage:
  main [required&optional-params]
  Options(opt-arg sep :|=|spc):
  -h, --help                                  write this help to stdout
  -m=, --mode=         string       "cpp"     language; see CompileMode
  -p, --past           bool         false     print AST output
  --pnim               bool         false     run preprocessor on header
  --pretty             bool         true      set pretty
  --preprocess         bool         false     print Nim output
  -d=, --defines=      ,SV[string]  EMPTY     definitions to pass to preprocessor
  -i=, --includeDirs=  ,SV[string]  EMPTY     include directory to pass to preprocessor
  -s=, --source=       string       REQUIRED  C/C++ source/header

Not sure what's wrong with the http://htmlpreview.github.io/?, but I also get that error a day later.  That file is just the output of nim doc argcvt.nim.  So, you can also just read the doc comments there.
Also, I don't think I was so clear...Had you tried just "-i dir1 -i dir2" (with no "=") then it would have appended rather than doing a clobbering assignment.  It only does the clobbering assignment with an explicit '=' (at least right now).  So, it seemed possible to me you might have discovered that subtle property by accident.  I don't think of += as very likely to be tried.  But, yeah, there should be example usage/--help-syntax.  parsopt3 is also quite a bit more flexible than the stdlib parseopts.

Not sure what's wrong with the http://htmlpreview.github.io/?, but I also get that error a day later.

not sure what you meant above but http://htmlpreview.github.io/?https://github.com/c-blake/cligen/blob/master/argcvt.html worked for me (link given at end of README in https://github.com/c-blake/cligen ; admittedly I'd prefer if that link appeared on top of README)

--help-syntax

=> moved that discussion to https://github.com/c-blake/cligen/issues/64

@genotrance

I believe this is now implemented with -dD. We need to add tests though.

is it, though? that's why I was trying to test with https://github.com/genotrance/nimterop/pull/17 but it fails

indeed, travis now passes! windows still fails though

This has been fixed.

@genotrance could we reopen?
constants works but not macros, see https://github.com/genotrance/nimterop/pull/30


Consider showing style tags in dev

I think that'd improve the dev experience when working locally. Right now the rules are inserted in a way that arent visible within dev tools.

Done


Plugin api

Almost all this was implemented on #11.
I just added a way to add new effects exposing a registerEffect method.

You can try this with power-effects package, is not yet published

see #264


liqoctl: generate random cluster name if none is provided

Description
Makes liqoctl install generate a random name if none is provided. It uses the same algorithm as Docker.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

[x] Unit
[x] E2E

/test

/test

/test

/merge


Elements for Microsoft Edge: Attach to a target command does nothing

I've been trying to figure out how to attach Elements to my running browser instance launched by Debugger for Edge.
The existing docs aren't helping and the "Elements for Microsoft Edge: Attach to a target" command does nothing except put up an unproductive edit field.  I expect that, according to the docs, it will put up a dropdown allowing me to select the browser instance to which to attach.

We have worked planned to make integration with the Debugger for Edge extension more seamless as right now (as you are finding out), it's a bit of a pain.
It should be possible though.
When you run the "Elements for Microsoft Edge: Attach to a target" command, the Elements extension will attempt to look for all targets using the settings specified for your current workspace. The fact that the dropdown is showing up blank suggests that Elements is using a different port to the one Debugger for Edge is using (so it can't find any targets).
Could you try the following:

Open VS Code settings (File ->Preferences -> Settings)
In the settings dialog, Expand Extensions
Under Extensions, Select Elements for Microsoft Edge
In the Elements settings, Find Port
Update the Port value to be 2015

I believe 2015 is the port that Debugger for Edge uses by default, if you have set a different port in your launch.json for the Debugger for Edge config, use that port number in the Elements settings above.
That should allow the Elements attach command to find the targets that the Debugger for Edge extension is using and so the dropdown will let you pick the right one.


BatchJob is a bad name

The name "BatchJob" suggests that it is associated with the batch system. This isn't the case. Possible alternatives include PersistentJob, StoredJob, JobStoreJob etc.

On 8/7 it was agreed that we use the name JobWrapper.

I see some places batchJob has been replaced with jobWrapper, but not everywhere (e.g. in the code).

I hope I caught them all in #218.


icon_color template does not work in 0.88

Checklist

[x ] I'm running the latest version of CustomUI (Update guide) or using a specific release that is not marked as "Broken".
[x ] I tried to force-refresh (Ctrl+Shift+R / Ctrl+F5) the browser
[x ] (Optional, but recommended) I'm using Chrome or tried to reproduce the feature on Chrome.

Browser + Version:
Chrome, Version 72.0.3626.109 (Official Build) (64-bit)

CustomUI version:
20190113
Home Assistant release (hass --version):
Hass.io 0.88.0
Problem-relevant customize.yaml entries:
sensor.indendoers:
  device_class: temperature
  templates:
    icon_color: 'if (state > 24) return ''rgb(223, 76, 0)''; if (state >= 21 ) return
      ''rgb(12, 135, 102)''; return ''rgb(214, 189, 29)'';'

This configuration works in 0.87, but after updating to 0.88 the custom colors does not work.
Possibly due to update on base card in 0.88.

Can confirm the same issue.

Same problem here as well.

Same as 169. I debugged it already. Hope Andrew will have time tout update it.

same issue on version 0.88.1.

It is working. To you all that have this problem, please see your logs. I had some other issues, and by resolving them, this started to work.

dito. homeassistant 0.88.1 using chrome

Same issue on version 0.88.1 using any browser.

same issue on version 0.88.1

same issue on version 0.88.1

In the mean time, someone found a solution using hs_color

This is rather surprising workaround, and as far as I can tell it uses HSV color space (but at least for me) ignores V component...

@rzolau
same for me, the V or B (or last integer) is ignored (makes no difference what i make that value)

This is rather surprising workaround, and as far as I can tell it uses HSV color space (but at least for me) ignores V component...

Same here. But then again, it IS called hs_color, so I guess it's not false advertising ;) Works as a workaround, but looking forward for the solution :)

I got color working again on my dashboard... via the hs_color workaround with the brightness too...
I used http://colorizer.org/ to convert the RGB into Hue, Saturation, and Brightness. Then I took the (Brightness#/100)*255 = The number you need to give Home Assitant using the separate brightness template.
Thanks to @WhistleMaster for putting the link here and to @arsaboo for showing his work on how to fix the brightness issue.
https://community.home-assistant.io/t/customui-discussion-thread/48694/25
input_boolean.home:
  templates:
    hs_color: 'if (state === ''on'') return [205,82]; else return [186,12];

      '
    brightness: 'if (state === ''on'') return 209; else return 147;

      '

hs_color works for me with the help of

I got color working again on my dashboard... via the hs_color workaround with the brightness too...
I used http://colorizer.org/ to convert the RGB into Hue, Saturation, and Brightness. Then I took the (Brightness#/100)*255 = The number you need to give Home Assitant using the separate brightness template.
Thanks to @WhistleMaster for putting the link here and to @arsaboo for showing his work on how to fix the brightness issue.
https://community.home-assistant.io/t/customui-discussion-thread/48694/25
input_boolean.home:
  templates:
    hs_color: 'if (state === ''on'') return [205,82]; else return [186,12];

      '
    brightness: 'if (state === ''on'') return 209; else return 147;

      '

How do you get the color white to work with hs_color?  I tried ever combination, but it defaults to blue icons.
              hs_color: >           if (entities['climate.pool_heater'].state ==='off') return [120,0];           if (entities['climate.pool_heater'].state ==='heat') return [50.3,79.2];         brightness:  >           if (entities['climate.pool_heater'].state ==='off') return 255;           if (entities['climate.pool_heater'].state ==='heat') return 250.92;

Fixed in 2019-03-24


ORC-597 row-level filtering benchmark

Extending orc benchmark to support row-level filtering using existing datasets

Hi, @pgaref . Could you resolve the conflicts?

Hi, @pgaref . Could you resolve the conflicts?

Hey @dongjoon-hyun just rebased with the latest master -- it should solve the conflicts

Eventually, this PR should be split into two PRs: (1) reader change, and (2) add benchmark code.

Extending orc benchmark to support row-level filtering using existing datasets

Hey @dongjoon-hyun -- The effort is already split in ORC-577 adding the reader functionality and ORC-597 extending the benchmarks  --  as I did not have permissions to create a branch upstream this PR also contains the Reader changes -- apologies for the mixup.

Hey @dongjoon-hyun @jcamachor  could you please take a look?
Now that ORC-577 is merged this could be pretty useful.
Thanks!

cc @omalley


cmd-ref: document new gc behavior

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.
Please chose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏
Fixes #1013

Question: do -a and -T keep also cached files referenced in the workspace regardless of whether you're currently checked out in a branch or tag? If so we should update those options to explain so, something like "in all Git branches/tags as well as the workspace".

@skshetry @jorgeorpinel what is the status of it? @skshetry is still assigned - are you going to move it forward?

@shcheklein Umm, yes. I'm trying to add --all-commits on this PR as well. I'll also have to address @jorgeorpinel reviews.

@skshetry sure! np. Just wanted to be sure that I don't block it like it happened last time.

@jorgeorpinel @skshetry ping! any progress on this?

@shcheklein, sorry, I couldn't get to the docs. I have adjusted it now and addressed most of the suggestions. :slightly_smiling_face:
Please take a look.

@skshetry @jorgeorpinel PTAL - https://dvc-landing-gc-flag-cha-stdoiq.herokuapp.com/doc/command-reference/gc - I've applied some edits to the doc

@jorgeorpinel @skshetry PTAL again.

@jorgeorpinel merging this, feel free to do changes on top of it!

Great 🎉  Just added a couple more changes in 0f10925e (part of #1072)


v0.9.0

feature: add pprof flag to disable running pprof server always
sync and ls uses a global queue with 100 workers to speedup process
file writeAt support
file truncate support
file & directory rename support
file & directory move support
allow pod to open if any file metadata gets corrupted
kv/present moved to kv/entry/present
running ci tests on windows
dfs server runs on windows now.
ws v2 login support
ws now uses dfs.API
pod/open-async api added
pods list, metadata and content encryption
swagger integration

7696298b999fcdce6a99e35884db682b12aa1315 also covers #281


Added .crunit suffix to Python language

see https://github.com/NiklasRosenstein/creator

It looks like you're the only user of this extension on GitHub: https://github.com/search?utf8=✓&q=extension%3Acrunit+NOT+sjfhdkfdgfndjg&type=Code&ref=searchresults :/
We try to only add new extensions/languages once they have some usage on GitHub. You can probably fix this using Linguist Overrides.

We try to only add new extensions/languages once they have some usage on GitHub.

:+1: - @NiklasRosenstein please take a look at the Linguist Overrides as @pchaigno suggests.


Tabbar component is not chanching my views and do not change the activated link

Hi,
I am new at Framework7 and VueJs and I am trying to create an app using PhoneGap. My main goal is to create an app for all mobile devices and have the same UX as native apps. So, I installed the default template that this module sugests. That was my starting point. I want to have an app with different views. Each view will have it's route tree. Each view is a tab so I add a toolbar to jump between the views. My app structure is this:
main.js
...

// Import Routes
import Routes from './routes.js'

// Import App Component
import App from './main.vue'

// Init F7 Vue Plugin
Vue.use(Framework7Vue)

// Init App
new Vue({
    el: '#app',
    template: '<app/>',
    // Init Framework7 by passing parameters here
    framework7: {
        root: '#app',
        /* Uncomment to enable Material theme: */
        material: true,
        routes: Routes
    },
    // Register App Component
    components: {
        app: App
    }
})

main.vue
<template>

		<f7-statusbar></f7-statusbar>

		<f7-views tabs toolbar-through>
			<f7-view id="tab1" route-tab-id="tab1" main tab has-tabbar active>
				<f7-pages></f7-pages>
			</f7-view>

			<f7-view id="tab2" route-tab-id="tab2" tab has-tabbar>
				<f7-pages></f7-pages>
			</f7-view>

			<f7-view id="tab3" route-tab-id="tab3" tab has-tabbar>
				<f7-pages></f7-pages>
			</f7-view>

			<f7-view id="tab4" route-tab-id="tab4" tab has-tabbar>
				<f7-pages></f7-pages>
			</f7-view>

			<f7-toolbar tabbar labels bottom>
				<f7-link iconF7="true" iconMaterial="room" tabLink="true" text="Perto" href="/" route-tab-link="#tab1" active></f7-link>
				<f7-link iconF7="true" iconMaterial="photo_camera" tabLink="true" text="Câmara" href="/tab-2/" route-tab-link="#tab2"></f7-link>
				<f7-link iconF7="true" iconMaterial="explore" tabLink="true" text="Rotas" href="/tab-3/" route-tab-link="#tab3"></f7-link>
				<f7-link iconF7="true" iconMaterial="local_mall" tabLink="true" text="Comprar" href="/tab-4/" route-tab-link="#tab4"></f7-link>

			</f7-toolbar>

		</f7-views>

</template>

route.js
export default [
    {
        path: '/',
        tabs: [
            {
                path: '/',
                tabId: 'tab1',
                component: require('./assets/vue/pages/about.vue')
            },
            {
                path: '/tab-2/',
                tabId: 'tab2',
                component: require('./assets/vue/pages/about.vue')
            },
            {
                path: '/tab-3/',
                tabId: 'tab3',
                component: require('./assets/vue/pages/about.vue')
            },
            {
                path: '/tab-4/',
                tabId: 'tab4',
                component: require('./assets/vue/pages/about.vue')
            },
        ]
    }
]

For now, I am setting all tabs to present the same page as an example.
With this, I am not able to change between views. No error is presented so is not a problem of using the components. I tried everything that the documentation says, but without success. Do you have some ideia about the problem? I really appreciate your help. Thank you.

Because Router is a View! So router (which is View) can't control other views. Use the following View declaration for each View https://github.com/nolimits4web/Framework7-Vue/blob/master/kitchen-sink/index.html#L40 (using url) property. And switch tabs without routes

@tmmsmoreira It's a bit late, but did you manage to make it work and how ?

No @amakh
I quit using Framework7 because I was not able to pass through this problem. I opted by Ionic.


Enable GPU Support

We need to enable GPU support in the Mesos framework so Scale will receive resource offers from GPU nodes.

We're punting on this for now.

What's the timeframe for adding GPU support? I see that this list https://github.com/ngageoint/scale/wiki/Priority-List has Mesos universal containerizer (first-class GPU support) listed as a Priority 2 but I'd like to know what that means in terms of time. Will we have to wait weeks? months? years?

It can be tough to estimate long term since our project tends to have shifting priorities, but as of right now I'd estimate that first-class GPU support is around 6 to 8 months away.
Note that this doesn't mean you can't run jobs that use GPUs, you will just have to work around some limitations, such as only being able to run one GPU job per node at a time (since Mesos isn't scheduling which GPUs are available to your job, your job just assumes it has use of all GPUs on the node). You will also have to set up your job and nodes with the correct CUDA libraries, see https://github.com/ngageoint/scale/wiki/Adding-NVIDIA-CUDA-support-to-your-Mesos-Docker-Containerizer

I'm interested in learning more about that "second class" option for running GPU jobs with Scale.
I have two agent nodes with GPUs but those nodes aren't listed on my Scale web interface
http://<MasterIP>/service/scale/#/nodes. You implied that GPU nodes should be available to Scale so I'm wondering if the problem is that when I built my DC/OS cluster I added GPU support by adding the following lines to my config.yaml:
enable_gpu_isolation: 'true'
gpus_are_scarce: 'true'

Do you think Scale will be able to see my GPU nodes if I reinstall my DC/OS cluster with gpus_are_scarce: 'false'?

gpus_are_scarce: 'false' is definitely a requirement for Scale to execute GPU algorithms on that node. Without this setting, Mesos will not give resource offers to Scale from nodes that contain GPUs. Regardless of this, you should have seen the nodes from the Nodes page in Scale - it is just a Scale view of the Mesos private agents. Are those nodes displaying as expected in the DCOS Nodes UI (https://my-dcos-admin.com/#/nodes)?

I'll go ahead and change the gpus_are_scarce parameter and rebuild my cluster.  One thing to note is that I have Scale v5.4.0 running on DCOS v 1.11.1. I heard that the next version of Scale will be compatible with DCOS v1.11.
I have 6 Agent Nodes, 1 is Public (no GPUs), 2 Private Nodes have GPUs. The remaining 3 Private Nodes are the ones that show up on Scale's web interface. The attached picture shows the web interfaces for DC/OS and Scale side by side.

Scale recognizes a Mesos private agent once it has first received resources for that agent from Mesos, so the gpus_are_scarce parameter is affecting those two private nodes. Switching it to false will allow Scale to receive resources from those nodes and it will therefore display them.
I'm not aware of anything in the next version of Scale specifically geared towards support of DC/OS 1.11. Scale 5.4.0 should work just fine with DC/OS 1.11. If you have seen any issues with Scale 5.4.0 and DC/OS 1.11, please let us know.

I'm following up to report that I successfully rebuilt my DC/OS cluster with gpus_are_scarce: 'false' and my new deployment of Scale can now see all my agent nodes with GPUs. Thank you for your help.

No problem. Let us know if you need anything else.

When we fully enable Scale to consume GPU offers we should consider the scarcity concerns in a manner similar to Marathon: https://mesosphere.github.io/marathon/docs/preferential-gpu-scheduling.html
This should be exposed as an environment on the Scale container so that the scheduler can make a proper determination when launching on how to schedule when GPU offers are encountered.

The following steps should be taken to test GPU support:

Update Scale to accept GPU resource offers here: https://github.com/ngageoint/scale/blob/1f46d70390273140a60c6a7cb791509131cd7c18/scale/scheduler/management/commands/scale_scheduler.py#L85
Apply configuration to Mesos GPU agents to ensure GPUs are available: https://github.com/ngageoint/scale/wiki/Adding-NVIDIA-CUDA-support-to-your-Mesos-Docker-Containerizer

Once that change has been made, GPU offers should be received by Scale. I’m not 100% sure that it will work because Scale uses the Docker containerizer which does not support GPU isolation (Mesos Containerizer does), but it’s worth a shot. All that will be needed then is a Scale job that requires the gpu resource.


msm + jsf + failover node = This XML file does not appear to have any style information associated with it

From<EMAIL_ADDRESS>on July 09, 2013 22:34:41
What steps will reproduce the problem?
1.- Install two tomcat instances in separate servers
2.- Configure LoadBalancing with mod_jk in other server (sticky sessions=true)
3.- Configure two memcached nodes with sticky=true
4.- start tomcat servers
5.- Launch web aplications
6.- Testing loadbalancing and session replication stopping one memcached node (the one is serving the aplication)
7.- trying to navigate to another page the Error is shown:
"This XML file does not appear to have any style information associated with it. The document tree is shown below."
8.-After a few seconds, I navigate to another page, and the page is rendered.

Is there a way to prevent this error?

extra configurations:

context.xml
<Manager className="de.javakaffee.web.msm.MemcachedBackupSessionManager"
sticky="true"
memcachedNodes="n1:<IP_ADDRESS>:11211,n2:<IP_ADDRESS>:11211"
failoverNodes="n2"
requestUriIgnorePattern="..(ico|png|gif|jpg|css|js)$"
transcoderFactoryClass="de.javakaffee.web.msm.JavaSerializationTranscoderFactory"
/>

I also got mapped in each application web.xml the following:
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>.xhtml</url-pattern>
<url-pattern>.jsf</url-pattern>
<url-pattern>.faces</url-pattern>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>

Original issue: http://code.google.com/p/memcached-session-manager/issues/detail?id=169

From martin.grotzke on July 19, 2013 03:03:12
Discussed here:
https://groups.google.com/d/msg/memcached-session-manager/r8A_V5I-e-E/Yhwj050WZiIJ

Closed due to inactivity / missing feedback on the mailing list.


Flashing white and blue lights from the Garmin after connecting

Hey Mholow,
One of my subs is having an issue where:
everything looks great for connections on the computer, bluetooth paired and connected, GSPro opens fine with the open API, then I open the gsp-r10 connect app, the app goes through its paces, it says connecting to R10 then next line says connected to launch monitor... so everything looks perfect on the computer end. The end result is the R10 flashing quickly white then blue followed by a pause, over and over is all the r10 will do.
Have you heard of any issues like this or can you think of anything that could be the issue?
Cheers,
Joe

As far as I understand when the computer makes the Bluetooth connection it puts the device in standby mode (white) but then if the device fails the Bluetooth handshake it will disconnect put itself back into pairing mode.  So what’s happening is probably that the computer has some success connecting but trouble keeping steady communication line open


[CP] Remove Picture/Scene toImageSync from 3.3 beta

issue_link
https://github.com/flutter/flutter/issues/108389
Commit Hash
N/A
Target
beta
pr_link
N/A
Impacted Users
Flutter Developers
Impact Description
Developers that attempt to use a new API that was not quite ready for 3.3 may experience native crashes.
Workaround
Don't use the new API
Risk
low
Test Coverage
yes
Validation Steps
This is a pure revert, so it is not really risky as long as existing tests pass

Diff is https://gist.github.com/jonahwilliams/dfb5ccc1d44affc0a013d879009fb849, but I guess rather than a CP this is really more of a PR against a release branch?

Looking at the conversation in https://github.com/flutter/flutter/issues/108389, I am going to go ahead and approve this revert.
I think this would require a revert on master followed by a CP of that revert into the beta branch.
CC: @CaseyHillers

From the release side, this sounds fine to me.
@jonahwilliams can you open a PR containing your proposed against the branch flutter-3.2-candidate.5?

https://github.com/flutter/engine/pull/34975

CP has landed in the candidate release branch.


Use get_account_reputation instead of look_up accounts for search autocomplete

Changes:

Use get_account_reputation instead of look_up accounts for autocomplete on search
Sort by user reputation

I think we are displaying too much users (in my opinion 5 would be enough) - we can load more to get better results, but limit it to 5 on UI.
https://busy-master-pr-1270.herokuapp.com/search?q=sekhmet
Now it's cumbersome if you want to search for something else than users.

Yes @Sekhmet . My meaning was to load more results from Steem API to get better quality but not showing more result on the UI.


ToC issue

When located at this url in the documentation:
https://docs.microsoft.com/en-us/azure/security/fundamentals/management-monitoring-overview?source=docs#feedback
and then clicking the marked entry in the ToC

it takes me to:
https://docs.microsoft.com/en-us/ which isn't really what I expected.

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

ID: cb7f41e4-36b4-82f0-32e9-3c05bdec1dcf
Version Independent ID: 856d1793-a232-cab5-6c2d-a9f2edcbde7a
Content: Management and monitoring security features - Microsoft Azure
Content Source: articles/security/fundamentals/management-monitoring-overview.md
Service: security
Sub-service: security-fundamentals
GitHub Login: @TerryLanfear
Microsoft Alias: terrylan

@pejuborg thanks for the feedback! I have assigned this issue to the content author to update as I don't have access to those links.

@pejuborg - Thank you for the feedback and sorry for the confusion. The Azure Log Integration content is archived because the feature was deprecated on 06/15/2019. You can view the Azure Log Integration content at https://docs.microsoft.com/previous-versions/azure/security/fundamentals/azure-log-integration-overview.
#please-close


image memory cache not working

When i use CachedMemoryImageProvider this error occurred

When i use isExists it show image is cached.

Output

Did it ever work?

"Thank you for reporting the issue. You can address it by using version cached_memory_image: ^1.5.0 and updating your code as follows in Dart:
CachedMemoryImageProvider(
   key,
   cached: CachedImage.readOnly,
)


Add doc for ConstructCell, improve doc Boxed, Enum

Related to the issue #932.
I'm not sure if types created with glib::Enum can be nullable...

I'm not sure if types created with glib::Enum can be nullable...

They can't, neither can flags :)


Add option to throw original error rather then timeout

Overview
This adds an optional parameter to throw the last thrown error from the retry loop in it's original state rather a timeout error instance. This prevents having to fork error handling modules to pluck the error out of the timeout error, and have it done at the source instead.

Thanks!

@demmer No worries, I'll be watching for that new release. :)

@dustinblackman Ha! Done :) I just pushed 0.9.0 after adding a workaround for phantomjs issues and adding a test for this option to keep the coverage at 100%.


SpeckleCircle needs X-axis and Y-axis properties for aligning planes

Expected Behaviour
Start point on a circle domain should be based on the plane the curve has been defined in
Actual Behaviour
When circles are created on twisted frames, before translation evalutation correctly picks up curve start, afterwards, the start point defaults to standard coordinates.

@secretlyagoblin as you suggest the circle schema (and arc by extension) seems to require some other property for better definition. I run into something similar while implementing arcs on the dynamo converter
Rather than 2 vectors I thought more of having the start point as property as such would be slightly lighter and easier to re-construct on the target platform(?)
@didimitrie

all the same to me! point + normal might be more useful for reducing error as they're further apart. Worth noting that Ellipse and Arc are derived from a xy axis.

More than happy to discuss these things! I've been running around in circles trying to fix these issues - pun intended.
SpeckleArcs do have a plane property, which basically includes X, Y and Z (normal) dirs. I know there have been problems (https://github.com/speckleworks/SpeckleRhino/issues/170, https://github.com/speckleworks/SpeckleCore/issues/68).
@alvpickmans: how are we doing for arcs from rhino/gh in dynamo at the moment? I remember I fixed this issue theoretically.
@secretlyagoblin: would the plane be ok for circles? I guess this would give you the control you need.
@all: the big fuckup previously with arcs and rhino was the domain and how it's specified. Adding  this to arcs resolved https://github.com/speckleworks/SpeckleRhino/issues/170, but not really sure what's our status on this one.

afaik although both Rhino and Dynamo have circle constructor based on Plane and Radius, Dynamo only uses the plane's origin as its centre building the curve from the positive vector from the origin parallel to XY plane (rigth side if counterclockwise), while Rhino from the circle's plane X axis (starting points in blue on pics below).
The same applies to arcs, so in Rhino the start point is on the plane's X axis and start angle 0 while in Dynamo can be any.
Quickly checking three.js api , it considers the starting point same as Dynamo. It would be good to know how other possible clients handle this (Unity, Blender...), and define SpeckleCircle/Arc schemas according to what would be easier to implement.

then ping @secretlyagoblin and  @cwmorse regarding unity circles and @tsvilans for blender circles.
It might also be the case that this level of control is not needed in Blender/Unity/Threejs, and we need to nail  it down for now Dynamo - Gh/Rh.
@alvpickmans, talk more irl tomorrow, but we can have start points added too to circles and arcs.

@didimitrie yep the plane should be fine, thanks! I'm using verbnurbs and it considers a circle to be a special case arc, which is probably a good way of thinking about it.
@alvpickmans that almost feels like bug on the part of Dynamo! I can't imagine that being preferred behaviour.

@secretlyagoblin I agree on treating circles as "closed arcs". I wouldn't say it is a bug, probably just a different interpretation of the geometry, just like nurbcurves are defined differently (great old post here).
In any case, there is no harm in asking Dynamo/Autodesk :)

I got in this when i reduced lines to a polyline with only two point coords in its array. Had to bring lines back because of public outcry.
So would keep arcs as arcs on the speckle side for now...

okay this is sorted now! I've remade a quick def to spin up some circles. will be closed soon...

Made it work in Dynamo as well! It was indeed a bug on its geometry library, but it is resolved until they release the fix with version 2.1.
This can be closed now.