Alternatives

This template seems abandoned, any suggestions on what to use instead of it?

Nope. I keep making similarish Haskell projects, but haven't figured out a good workflow for keeping this up-to-date.


Speculative PR for deep generics

I have the need for a deep generic representation of a nested ADT.
This representation is composed of HLists of base elements. e.g.
case class Address(number: Int, street: String)
case class Person(name: String, address: Address)
the[DeepGeneric[Person]]
//Repr is (String :: HNil) :: ((Int :: HNil) :: (String :: HNil) :: HNil) :: HNil

Is this idea, or a similar one, useful in shapeless itself?
EDIT
The representation for DeepGeneric[Person] should actually be
String :: (Int :: String :: HNil) :: HNil

Current coverage is 81.16% (diff: 0.00%)

Merging #669 into master will decrease coverage by 0.39%

@@             master       #669   diff @@
==========================================
  Files            69         70     +1
  Lines          2641       2654    +13
  Methods        2375       2389    +14
  Messages          0          0
  Branches         92         91     -1
==========================================
  Hits           2154       2154
- Misses          487        500    +13
  Partials          0          0

Powered by Codecov. Last update fcc15a6...c240b19

Sorry it's taken me so long to get to this ... I'm catching up with things after the break.
shapeless has followed the Haskell generics literature (Scrap Your Boilerplate and GHC Generics in particular) in taking a "one layer at a time" approach to generic representations. In these approaches the deep structure is captured by a traversal, which manifests itself as the kind of inductive traversals you see in examples of type class derivation using shapeless. But there are other points in the design space which are very much worth exploring.
I'm a little reluctant to include this in shapeless core just yet, but I would be keen to include it as an example, especially if you're able to extend it to cover things which have a Coproduct generic representation.

Thanks for the feedback, I also think this is more appropriate as an example.  There's already a DeepHLister which is fairly similar.  I'll expand this to include Coproduct, and clean it up a bit.

Thank you!

Apologies for not paying closer attention ... is there anything I can do to help move this along?

Apologies for the late update - I've made several attempts at this, but am still perplexed.  I'm going to close this PR, as I think that any solution would be too convoluted to make sense as an example.
I'll repoen it if and when I can get the code to work well.

If you push to the PR we could maybe give you some advice?


How to resolve Micro Frontend Shell app throwing 'not a known element' error for child Micro app?

I have all the appropriate modules imported in both the Shell(parent) app and Micro(child) app yet I get the error; specifically in my case 'mat-chip-list' is not a known element only when I launch the Shell(parent) app.
Is there a configuration I must have in my: webpack.config.js or nx.json or project.json or angular.json?

Hi,
hm, I guess you need to share Angular Material and all the used secondary entry points via all webpack.config-s (the one of the shell and the one of the micro frontend). Also, you need to import the Modules everywhere you need this shared mat-chip.list.


Rule to enforce semicolons after bound class methods

Bug Report

TSLint version: 5.7.0
TypeScript version: 2.4.2
Running TSLint via: CLI

TypeScript code being linted
This example may arguably be a bit too simple, but I've got real code like this.
class MyClass {
    	private myFunc =
    	    	    	([param1, param2, param3]) => param1 && && param2 && !param3;
        private myVar = 'test';
}

with tslint.json configuration:
{
        "semicolon": [
            true,
           "always"
        ]
}

Actual behavior
The error I get is Unnecessary semicolon for myFunc, but it does not feel natural at all to to remove the semicolon from there.
And if I make use of the relaxing option "ignore-bound-class-methods", then there is no more enforced consistency, i.e. either way is allowed.
Expected behavior
I expect my TSLint configuration to be consistent at all times. If I look at an assignment, I expect a semicolon after it, no matter if it's a variable assignment or a function assignment. Otherwise it's still not consistent.
(I would also argue that the syntax for bound class methods is terrible, because it shouldn't look like an assignment at all, but I cannot help that, they chose so. If it looks like an assignment, then it also looks weird without a semicolon.)
So this issue goes one step further from https://github.com/palantir/tslint/issues/1476, because I would like the ability to require semicolons after whatever assignment I do, for consistency.
Update: Without the semicolon in myFunc, IntelliJ IDEA will warn that the statement is unterminated. So it looks to me that TSLint and IDEA disagree.
Additional info
The rule does not complain, if I don't break the line:
private myFunc =  ([param1, param2, param3]) => param1 && && param2 && !param3;

Also, I expect a semicolon here, but there is no error message:
    private myFunc2 = (myParam: boolean): boolean => {
        return true;
    }

I agree, that it's not consistent to simply ignore bound class methods (only when they span multiple lines).
We could add another option for that. But then they are likely to conflict.
I'm leaning more towards making "ignore-bound-class-methods" ignore that this is a bound class method and lint it like everything else. Technically a breaking change.
Thoughts @adidahiya?

To put it simply: I'm asking for a change that:

if it looks like an assignment => then semicolon it.
if it looks like a regular function definition => then don't semicolon it.

Why? Because we're spending too much time on the special cases with not much benefit, we're arguing too much about how to make things more complex, and I don't want to confuse my developers,

bottom line: I think banning semicolons on bound class methods by default was a mistake. we should align with prettier and enforce them by default. I agree with @rkrisztian's last comment (https://github.com/palantir/tslint/issues/3216#issuecomment-329025052).
however, this would be a breaking change. so despite the inevitable conflict across rule options, I would like to add this as a new rule option ("strict-bound-class-methods" perhaps) which we can make the default in 6.0.

By the way, the arrow function way of defining bound class methods is actually an assignment by definition: https://github.com/Microsoft/TypeScript/issues/16732
Thus, it counts as a field assignment, thus I don't really understand why most people don't add the semicolon.
Thus, I'm also wondering about member-ordering. Let's say you have:
export class TestService {
  test1 = () => { }
  test2: number;
}

Then if I set the rule:
        "member-ordering": [
            true,
            {
                "order": [
                    "static-field",
                    "instance-field",
                    "constructor",
                    "static-method",
                    "instance-method"
                ]
            }
        ],

Then the code above should be valid, because I declare only fields. TSLint thinks differently though:
ERROR: /home/rkrisztian/projects/testProject/src/app/test.service.ts[6, 2]: Declaration of instance field not allowed after declaration of instance method. Instead, this should come at the beginning of the class/interface.

Note: a decorator would handle the problem more nicely, but the TypeScript guys don't want to add to add such (e.g. a @bound annotation), because they don't do anything that can be done with a library. So now I'm also thinking, either we have proper rule for semicolons, or we ban such usage of arrow functions in favor of a decorator. (After all, some people think the arrow function way can be too cryptic, even if just using a lambda function property is so simple compared to using decorators.)

Thanks!


Using application certificates for mitmproxy error 403

Problem Description
I'am checking IOT device websocket data stream to Cloud and get 403 error doing this mitmproxy.
Steps to reproduce the behavior:

IOT application has 3 pem files: cacert.pem, newcert.pem, newkey.pem
launch mitmproxy --mode transparent --showhost --ssl-insecure --cert *=/tmp/ssl/cert.pem
(cert.pem has both newcert.pem and newkey.pem inside)
Error:

Server Error

403 - Forbidden: Access is denied.
You do not have permission to view this directory or page using the credentials that you supplied.
System Information
Mitmproxy: 5.0.1
Python:    3.6.8
OpenSSL:   OpenSSL 1.1.1  11 Sep 2018
Platform:  Linux-4.18.0-25-generic-x86_64-with-Ubuntu-18.10-cosmic

Not sure, could be that your device is using client certificates. We're generally happy to help out, but can I please ask you to use StackOverflow for all support and how-to questions? You can post the link to your question here so that people can follow up.
Thanks!


Error creating application autoscaling target for managing lambda provisioned concurrency

Hi,
I tried create application auto scaling policy for provisioned concurrency based on this doc:
https://docs.aws.amazon.com/autoscaling/application/userguide/application-auto-scaling-target-tracking.html
Based this I have written pulumi script, but I faced this error, after executing script:
error: Error creating application autoscaling target: ValidationException: Unsupported service namespace, resource type or scalable dimension

My code something like this :
          appautoscaling.Target(
                'some_name,
                service_namespace="lambda",
                resource_id=f'function:some_lambda.name:some_lambda.version',
                min_capacity=1,
                max_capacity=10,
                scalable_dimension="lambda:function:ProvisionedConcurrency"
            )

Through cli I can create that target and then policy.
What is wrong or pulumi doesn't support this now ?
Thanks.

Hi @Ilchuk-Mihail
Apologies for the issue you are facing here - please can you tell me what version of pulumi-aws you are using for this?
Paul

Hi @Ilchuk-Mihail
Another question on this, is the version being set as $LATEST?

I added publish=True parameter in lambda Function constructor, so it will create a new version for each update, and I used this version.
Also I tried to use alias for Lambda, but got the same error.
I used these versions:
pulumi  1.6.1
pulumi-aws 1.14.1

Connected with: https://github.com/pulumi/examples/issues/491

@Ilchuk-Mihail Here is a TypeScript example which works for me:
const resourceId = pulumi.interpolate`function:${lambda.name}:${lambda.version}`;
const target = new aws.appautoscaling.Target("target", {
    resourceId,
    serviceNamespace: "lambda",
    scalableDimension: "lambda:function:ProvisionedConcurrency",
    minCapacity: 1,
    maxCapacity: 10,
});

I'm not fluent with python, but I suspect your resource_id is not built correctly?

Hi @Ilchuk-Mihail
Please can you let me know if you still need help with this issue.
Thanks
Paul

I am going to close this out as we haven't heard anything back on the issue - if you still have issues, please let us know
Paul


Function returned by Microsoft.FSharp.Reflection.FSharpValue.PreComputeUnionConstructor throwing FatalExecutionEngineError when invoked

The function returned by Microsoft.FSharp.Reflection.FSharpValue.PreComputeUnionConstructor is throwing the following error very occasionally when used to create a value of type float option via reflection.

FatalExecutionEngineError occurred
Message: Managed Debugging Assistant 'FatalExecutionEngineError' has detected a problem in 'C:\dev\vs2015\src\repro\bin\Debug\repro.exe'.
Additional information: The runtime has encountered a fatal error. The address of the error was at 0xf582d7f4, on thread 0xdaa0. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.

This seems to have started happening after I installed VS2015, however targeting earlier versions of either FSharp.Core or the .NET runtime makes no difference.  I've also tried setting <useLegacyJit enabled="1"/> in the app.config due to the known bug in RyuJIT (http://nickcraver.com/blog/2015/07/27/why-you-should-wait-on-dotnet-46/), however this also makes no difference.  I've only tried this on Windows 7, so I don't know if it's OS specific.  It happens in both Debug and Release build.
I've managed to create a reproduction of the error. Compile and run the project linked to below with the conditional compilation symbol 'BUG' defined, and it should fail with the above error.  Then compile and run without 'BUG' defined to replace the use of FSharpValue.PreComputeUnionConstructor with equivalent non reflection based code, and the program will complete without error.
The project can be downloaded from here: https://www.dropbox.com/l/BXokpag4b4pFtBzeTJpion   Note that it's a 20Mb file as it contains 2 embedded data files which contain serialised arrays that trigger the error.

This bug repros even with
Complus_useLegacyJIT=1    ; use legacy Jit64
complus_zapDisable=1       ; don’t load ngen images, instead jit
The point of failure (or call stack) is the same even against RyuJIT.
  That is, the problem goes away by adding the following to the app.config file:
  <runtime>
    <gcServer enabled="true" />
  </runtime>

This might seem like a bit of an esoteric bug, but it is happening to me quite frequently at the moment whenever I try and process large amounts of data with F#.
I only found this workaround because I was getting absolutely terrible workstation GC performance since updating to VS2105. Things that used to take seconds now take many minutes, as is being reported by others:
http://blogs.microsoft.co.il/dorony/2015/08/08/beware-of-net-4-6-workstation-gc/
http://stackoverflow.com/questions/31747992/garbage-collection-and-parallel-foreach-issue-after-vs2015-upgrade

For the performance issue, please see my blog entry: http://blogs.msdn.com/b/maoni/archive/2015/08/12/gen2-free-list-changes-in-clr-4-6-gc.aspx. You could use Server GC for now (or continue to use it if it works well for you) and try the fix when it's available (should be very soon).

That's great news, thanks Maoni!  What about the original error? From sivarv's stack trace above, it seems like the exception is actually thrown inside the GC.  I presume you are on the GC team at MS, perhaps you could help give this issue a little oxygen?

I am trying to repro your original issue (without success so far).
The issue looks like typical managed heap corruption from the callstack (which is typically not GC problem). I am working with Siva to get my hands on repro environment (+ I am running it in parallel on my machine in a loop) -- once I have a repro somewhere, I plan to try GCStress (or iDNA tracing) to get something actionable.

@karelz Any progress on this issue?

I routed it for further investigation last week (sorry I didn't have time to dig deeper myself earlier).
It is most likely a bug in Runtime. We have some partial results (component likely to blame), but not final results yet. I'll keep you posted.

I looked at this today. And indeed this is a bug in GC. Thanks for discovering it!
You are hitting an extreme case (as in the survivors in your case were the smallest objects possible that were all separated from each other by objects that died) and my calculation was a tiny off which showed up in this extreme case. I will fix this ASAP. I'll need to check with our release folks when/how it will be shipped (that part is out of my control).
Thanks again for finding this. I will make sure this case is covered in our test suite.

No worries, thanks for the prompt attention, I hope a fix can be released soon!

Maoni, I'm pretty sure I need this GC fix too.  I can reproduce an ExecutionEngineException in a multi-threaded unit test running in vstest.executionengine.exe (from a command line call to vstest.console.exe).  It's all managed code on my end, and this test has worked for years in VS 2012 and 2013.  But now with .NET 4.6 and VS 2015, the same unit test will fail about half the time.
I used DebugDiag to create a full dump whenever ntdll!NtTerminateProcess was called in vstest.executionengine.exe, and the call stack matched the important parts above (where things go wrong in clr!WKS::gc_heap::compact_plug).  Looking at things in WinDbg, there doesn't appear to be any heap corruption.  It appears to match this GC bug most closely except I end up with an ExecutionEngineException.
I'd appreciate it if you could post here (or on your blog) any release date info and other details so I could track this.  I'm also anxiously awaiting the perf fix you blogged about last month.
Thanks!
ntdll!NtTerminateProcess
ntdll!RtlExitUserProcess+0x5b
kernel32!ExitProcessImplementation+0xa
mscoreei!RuntimeDesc::ShutdownAllActiveRuntimes+0x26c
mscoreei!CLRRuntimeHostInternalImpl::ShutdownAllRuntimesThenExit+0x14
clr!EEPolicy::ExitProcessViaShim+0x69
clr!SafeExitProcess+0x9d
clr!EEPolicy::HandleFatalError+0x123
clr!CLRVectoredExceptionHandlerPhase3+0x305292
clr!CLRVectoredExceptionHandlerPhase2+0x2d
clr!CLRVectoredExceptionHandler+0x94
clr!CLRVectoredExceptionHandlerShim+0x89
ntdll!RtlpCallVectoredHandlers+0x113
ntdll!RtlDispatchException+0x6e
ntdll!KiUserExceptionDispatch+0x3a
clr!WKS::gc_heap::compact_plug+0xb7
clr!WKS::gc_heap::compact_in_brick+0x6a
clr!WKS::gc_heap::compact_in_brick+0x98
clr!WKS::gc_heap::compact_phase+0x1c5
clr!WKS::gc_heap::plan_phase+0xc32
clr!WKS::gc_heap::gc1+0x9d
clr!WKS::gc_heap::garbage_collect+0x264
clr!WKS::GCHeap::GarbageCollectGeneration+0x13a
clr!WKS::gc_heap::allocate_more_space+0x1c5
clr!JIT_New+0x38c

@bmenees, thank you for reporting this. I would really love to get the fix out to you guys ASAP but unfortunately that part is out of my control. I am sure our servicing engineers are working as fast as they can in order to get fixes out but it takes time to go through the normal hotfix process. I have asked our release manager Lee to comment. I'll check again to see if he could comment soon.

@bmenees Why do you think you are hitting exactly the same bug as the original report? The callstack is pretty generic and does not identify root cause, just a symptom, so it is not sufficient for confirming if your problem is a dupe or not.

@karelz It's an educated guess based on working with .NET since 2002 using a mix of managed and unmanaged code.  I've run into ExecutionEngineExceptions in the past, and usually they were due to heap corruption issues in my (team's) unmanaged code.  But  once I was affected by an ExecutionEngineException that was due to a bug in the CLR.
I have a lot of experience analyzing user dumps in WinDbg and looking at valid and corrupt unmanaged heaps as well as the GC data.  I'm also familiar with what this particular unit test is doing and the huge amount of pressure it puts on the GC.  Everything I see in the behavior of this test now, both interactively and in the user dump, points to a GC bug and not heap corruption.
I also know it does not happen when I run it on a machine with .NET 4.5.2.  It only happens on machines with .NET 4.6.  Also, the performance of this unit test bombs when it runs on .NET 4.6.  And when I run the same code in a process where I've forced server GC usage, it runs fine.  And the RyuJit flags have no effect on this test.  So all signs, including the call stack and my Magic 8 Ball, point me to this thread.
On Monday, I'll try to open an MSDN Support incident to escalate this to someone at Microsoft so they can take an official look at it.  But that's usually a long and involved process that takes me multiple days to get to the right escalation engineer, and then it takes many more days of corresponding about repros, generating the right dumps, handling dump uploads with matching binaries, etc.  It was much nicer to end my work week with some hope that the lead developer on the GC has already found and fixed the perf and crash bugs in .NET 4.6 that are affecting me.  :-)

@bmenees It's always good to see someone educated about heap corruptions and GC. Sadly it's quite rare.
I believe in your experience and that your issue is likely a GC bug. The question remaining is: Is it the same as the one reproed on this thread. Would it be possible to provide a repro for us to verify on our private bits with a fix?
If you go through support and it is indeed a GC issue, it will end up on our plate eventually anyway ... consider this as a short cut :)

Hey folks,
Thanks for the report and additional feedback. Maoni has put together a fix for this and it will be making it's way through testing and the rest of the servicing machinery. We just missed the fix window for October so this will release in mid November.

@karelz Can you email me privately at my work address? Username: bmenees at my company's domain (equinoxis.com).  I've got a relatively small repro now (in a C# console app) that I can zip up and send you.  But due to a licensed data file that the test reads through, the zip is about 15MB, and I can't publicly attach it here.  And thanks for the shortcut.  :-)

Hi all, any info on the progress of the release of the fix for this?

Hey folks,
By way of background, hotfixes for the Framework can include changes from any of the different teams which contribute to the Framework. In the case of the November release, a problem was found with an unrelated fix leading to the entire set of fixes being delayed until around the 2nd week of December.

@leecow, is this fix in .NET 4.6.1 (since it was released on November 30)?


RTS awning no longer available since last commit

[x] I have read the Readme, including the Advanced section regarding debugging.

Describe the bug
RTS awning no longer available since commit 02adec972ec6778d0151402eaf11b82e1594b3eb
To Reproduce
I manually install my custom_components through git, I just updated (git pull) and after a restart, I got error logs
Expected behavior
Obviously to have the entity available and be able to control the awning.
Screenshots

Environment (please complete the following information):

Hub: TaHoma
ha-tahoma version: 3.18.0 (15078) | 2021.1.4-20
Home Assistant version: 2021.5.1
Platform: cover

Device: (if your problem is related to a specific device)

Model: UpDownHorizontalAwning
Type: rts:HorizontalAwningRTSComponent

Additional context
Log:
2021-05-09 13:17:28 ERROR (MainThread) [homeassistant.components.cover] Error adding entities for domain cover with platform tahoma
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 364, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 558, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 581, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 334, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 368, in _async_write_ha_state
    state = self._stringify_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 340, in _stringify_state
    state = self.state
  File "/usr/src/homeassistant/homeassistant/components/cover/__init__.py", line 192, in state
    closed = self.is_closed
  File "/config/custom_components/tahoma/cover.py", line 223, in is_closed
    if self.current_cover_position is not None:
  File "/config/custom_components/tahoma/cover.py", line 158, in current_cover_position
    position = 100 - self.select_state(
TypeError: unsupported operand type(s) for -: 'int' and 'NoneType'

When I checkout<PHONE_NUMBER>448c54397d07ff93eec69d4c1cb572, it works fine
git checkout<PHONE_NUMBER>448c54397d07ff93eec69d4c1cb572
dcrestart homeassistant

Results into:

Sorry, for this. And thx for this issue nicely described. Can you please try https://github.com/iMicknl/ha-tahoma/pull/440/commits?

Thx for this issue nicely reported. Can you please try https://github.com/iMicknl/ha-tahoma/pull/440/commits?

It's no longer unavailable so that is good. But the awning takes now 10-30 seconds to respond from the HA UI, Also the UI remains like this:

From https://www.tahomalink.com it reacts quite quickly.
No weird errors in the log, but haven't enabled any extra logging for this component.

Hmm, after a bit more trying it looks like the stop button is not stopping the awning but queueing the action. I remember this was also the case in early versions of this component

Thx for this issue nicely reported. Can you please try https://github.com/iMicknl/ha-tahoma/pull/440/commits?

It's no longer unavailable so that is good. But the awning takes now 10-30 seconds to respond from the HA UI, Also the UI remains like this:

From https://www.tahomalink.com it reacts quite quickly.
No weird errors in the log, but haven't enabled any extra logging for this component.

It was the case with the latest version?

I just did a bit more testing.
When the awning is open and when I press the go-up button in HA, it will close.
When I press the stop button (in HA) while closing, nothing happens and it continues to close. Once fully closed it will open again stop will also go to the prefix location and it looks like that is happening.
When I press the open button and a few seconds later the close button, it won't stop and close.
Not sure if the context is correct, but open is blocking the sun and close is not blocking the sun/retracted.

Beside the stop button, #440 Seems t work

@golles There is a typo in your comment?
In the linked PR I didn't touch the Stop button.
Can you compare with the latest available version (not master branch)?

Sorry to be a bit annoying, but all works fine till https://github.com/iMicknl/ha-tahoma/commit/02adec972ec6778d0151402eaf11b82e1594b3eb, like mentioned in the description.

@golles if only the Stop button does that work, can you please open a new issue?

Yep, will do that


Gamm multihop

I've added the multi-hop functionality as well as some test code. However, I've only added one case for the multi-hop test that succeeds. Let's take a look initially and revise later as needed.
I also think it'd be good to add more test codes on a separate branch.

I've also removed the max spot price functionality as I added the multi-hop functionality for now.
Let's discuss whether this feature is necessary and if it is I can add it back in.

#33

A. Adding CLI tests would be great
B. Writing shell scripts on README to try it out in real mode is 👍.


Explore UI is not showing correct count and pagination v/s API results

Affected module
Does it impact the UI, backend or Ingestion Framework?
UI
Describe the bug
During searching for specific table, found that API results return 4 but Explore UI shows 41 as count and multiple pagination.
To Reproduce
Screenshots or steps to reproduce
Attached is screenshot & API calls file

omd_api_calls.txt
file
Expected behavior
Explore UI count should match with API calls result
Version:

OS: [e.g. iOS]  Kubernates POD through Helm chart version 1.2.7( https://artifacthub.io/packages/helm/open-metadata/openmetadata/1.2.7)
OpenMetadata version: [e.g. 0.8] 1.2.4
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.

we need more details here. What version of OpenSearch or ElasticSearch and are they using multi-node cluster etc..

Hi @harshach , We are using elasticsearch:8.7.1 and not using multi node cluster

This is fixed in 1.3.0


Restore storybook for PR review and version publish

What it solves
Storybook automatic build was lost because it wasn't migrated from Travis. In this PR we restore automated builds on each PR and also the action to create the production build each time we create a new release to be published in https://components.gnosis-safe.io
It also includes some dependency bump and optimization

Two of the files do not have a new line at the end of the file: :
.github/workflows/deploy-storybook.yml
scripts/github/prepare_production_deployment.sh

Keep in mind that In this PR, The Textfield component is Broken:
https://pr168--safereactcomponents.review.gnosisdev.com/?path=/docs/inputs-textfield--simple-text-field


feat: add Autofocus info to Position object

This PR adds an hardware autofocus device argument to the Position object.
Example of use in https://github.com/pymmcore-plus/pymmcore-plus/pull/199 and https://github.com/pymmcore-plus/pymmcore-widgets/pull/147.

as discussed, perhaps a top level AutoFocusPlan on the sequence itself is a good idea here:
class AutoFocusPlan(UseqModel):
    device_name: str
    af_motor_position: float = 0
    axes: Tuple[str, ...] = Field(default_factory=tuple)


any hints about android?

couldn't find anything on google. how can I make this work with Android?

not support for android.

Android is not supported, but if you need it, a PR is welcome to implement it!

Any chance of android capabilities getting developed? (what's a PR?) (lol)

https://help.github.com/articles/using-pull-requests/


Some log output is falsely written to stderr

[!NOTE]
Related: #1193

Describe the bug
Some outputs that aren't actually indicating any issues are written to stderr when they should be written to stdout.
https://github.com/Redocly/redocly-cli/blob/eb827254637d3d17a30b2285fad7d37fb5a3318b/packages/cli/src/commands/build-docs/utils.ts#L63
https://github.com/Redocly/redocly-cli/blob/eb827254637d3d17a30b2285fad7d37fb5a3318b/packages/cli/src/commands/build-docs/utils.ts#L40
To Reproduce
Command
redocly build-docs openapi.yaml --output output.html > stdout.log 2> stderr.log

stdout.log

🎉 bundled successfully in: tmp.html (177 KiB) [⏱ 3ms]

stderr.log
Found redocly.yaml and using theme.openapi options
Prerendering docs

Expected behavior
Only logs indicating problems or critical warning should be printed to stderr.
Alternatively, such outputs should either be suppressed by default and only show up when using verbose flags -vv or there should be a flag to manually suppress such messages with a --silent or --quiet flag.
Redocly Version(s)
$ redocly --version
1.2.0

Node.js Version(s)
$ node --version
v16.20.2

Additional context
I'm running redocly as a subtask in my sbt build process. Because I pass the redocly output to my own logger, it gets picked up the same way as actual errors would.

Thanks for reporting!
@lornajane I remember we already discussed sorting out the stdout/stderr outputs. Here's the corresponding issue for the bundle command. Do we maybe want to consolidate all the related issues?

Yes, I think there's a few things going on in the different commands. Thanks @hertg for sharing this, I think it's appropriate to output additional information to stderr, and you should find that the exit codes are the best way to tell if something succeeded. That said, the option to silence non-error output is reasonable and I'm adding that to our list of features to consider.

@lornajane you should find that the exit codes are the best way to tell if something succeeded.

I thought about checking the exit code and only pass on the output from stderr if it was non-zero... But I can give you an example where that doesn't work: If I have an error in the redocly.yaml , it prints a useful error message to stderr that I definitely want to pass on, but the process exits successfully.
That's an error I got recently. Despite this error, the build-docs command completed with exit code 0.
stdout

🎉 bundled successfully in: tmp.html (96 KiB) [⏱ 3ms].

stderr
[1] :21:25 at #/theme/openapi/theme/typography/fontWeightBold

Expected type `string` but got `integer`.

19 | typography:
20 |   fontFamily: Inter,Roboto,sans-serif
21 |   fontWeightBold: 700
   |                   ^^^
22 |   headings:
23 |     fontFamily: Inter,Roboto,sans-serif

Error was generated by the configuration spec rule.

❌ Your config has 1 error.

I think it's appropriate to output additional information to stderr,

For what reason? I can see the argument to print diagnostic information to stderr if it is "unintended" output that you don't want to print to stdout, "unintended" in the sense that the user "didn't ask for it", so you don't want to clutter stdout with diagnostics. But I'd argue that printing diagnostic information the user didn't ask for is better left behind a verbose flag, making the user ask for it, and then it can be printed to stdout. Of course, that comes down to personal preference, just wanted to give an alternative viewpoint. :)

@hertg Oh, that's interesting. The reason it exits with 0 is that the error is in the config (and not in the API description itself), and we treat config errors separately. However, it should be a warning, not an error. For instance, the lint command produces a warning on the same config (again, it is not counted in the overall stats, which is expected).

@tatomyr I have no issues with it exiting successfully when there are config errors :) My point is that because of this mix of diagnostics and warnings/errors in stderr, I'm forced to always pass on what redocly prints to stderr, because there is no way for me to know whether it contains just diagnostics or actual warnings / errors. And I obviously want to pass them on as errors to our logs, because I want actual errors to show up as such, including config errors.
Right now, I have to communicate to the developers that the redocly errors in their logs can almost always be ignored, because they're just diagnostics. But I don't really like conditioning engineers to ignore error messages :stuck_out_tongue:
Although I'd prefer it not to print diagnostics to stderr by default, If there was an opt-in flag that I can set which has the effect that diagnostics are no longer printed to stderr, my needs would already be satisfied.

@hertg I see your point, but I'm referring to the actual bug you've accidentally helped to find.
Regarding your case, if you want to know if there are warnings/errors, you may tweak the rules' severity in a separate config and run the command against it (see here). If there are any, it will exit with 1. I understand that it won't work for config errors though. So it might be a good idea to introduce a flag or a config option that will force failing on config errors. I hope this makes sense.

The extra content in stderr is useful feedback for humans using the CLI at a command prompt, but you should be safely able to ignore it if there's a success response code! I agree with @tatomyr, an error from linting the configuration is still an error and should return the appropriate status code.

I'm having the same issue.
With the following areas:

Bundling
Linting
Documentation
A new update is available

I've managed to handle the incorrect behaviour in code however my logs contain the errors.
Within my Nuke build Errors & Warnings, you can see the compilation of these errors. This is outside of each individual step spitting out the same errors.
[ERR] BundleOASpecificatio:     ╔══════════════════════════════════════════════════════╗ [ERR] BundleOASpecificatio:     ║                                                      ║ [ERR] BundleOASpecificatio:     ║  A new version of Redocly CLI (1.2.0) is available.  ║ [ERR] BundleOASpecificatio:     ║  Update now: npm i -g @redocly/cli@latest.         ║ [ERR] BundleOASpecificatio:     ║  Changelog: https://redocly.com/docs/cli/changelog/  ║ [ERR] BundleOASpecificatio:     ║                                                      ║ [ERR] BundleOASpecificatio:     ╚══════════════════════════════════════════════════════╝ [ERR] BundleOASpecificatio:   bundling C:\Dev\GitlabRepos\Hydra\DeveloperPlatform\specifications\Auth/auth-api-spec.yaml... [ERR] BundleOASpecificatio: 📦 Created a bundle for C:\Dev\GitlabRepos\Hydra\DeveloperPlatform\specifications\Auth/auth-api-spec.yaml at C:\Dev\GitlabRepos\Hydra\DeveloperPlatform\output\specifications\auth\auth-api-spec-bundled.yaml 20ms. [ERR] LintOASpecifications:     ╔══════════════════════════════════════════════════════╗ [ERR] LintOASpecifications:     ║                                                      ║ [ERR] LintOASpecifications:     ║  A new version of Redocly CLI (1.2.0) is available.  ║ [ERR] LintOASpecifications:     ║  Update now: npm i -g @redocly/cli@latest.         ║ [ERR] LintOASpecifications:     ║  Changelog: https://redocly.com/docs/cli/changelog/  ║ [ERR] LintOASpecifications:     ║                                                      ║ [ERR] LintOASpecifications:     ╚══════════════════════════════════════════════════════╝ [ERR] LintOASpecifications:   validating C:\Dev\GitlabRepos\Hydra\DeveloperPlatform\output\specifications\Auth\auth-api-spec-bundled.yaml... [ERR] LintOASpecifications: C:\Dev\GitlabRepos\Hydra\DeveloperPlatform\output\specifications\Auth\auth-api-spec-bundled.yaml: validated in 21ms [ERR] LintOASpecifications: Woohoo! Your OpenAPI definition is valid. 🎉 [ERR] LintOASpecifications: 2 problems are explicitly ignored. [ERR] LintOASpecifications: [ERR] GenerateDocumentatio:     ╔══════════════════════════════════════════════════════╗ [ERR] GenerateDocumentatio:     ║                                                      ║ [ERR] GenerateDocumentatio:     ║  A new version of Redocly CLI (1.2.0) is available.  ║ [ERR] GenerateDocumentatio:     ║  Update now: npm i -g @redocly/cli@latest.         ║ [ERR] GenerateDocumentatio:     ║  Changelog: https://redocly.com/docs/cli/changelog/  ║ [ERR] GenerateDocumentatio:     ║                                                      ║ [ERR] GenerateDocumentatio:     ╚══════════════════════════════════════════════════════╝ [ERR] GenerateDocumentatio:   Found undefined and using theme.openapi options [ERR] GenerateDocumentatio: Prerendering docs

If I have an error in the redocly.yaml , it prints a useful error message to stderr that I definitely want to pass on, but the process exits successfully.
That's an error I got recently. Despite this error, the build-docs command completed with exit code 0.

@hertg in Redocly CLI v1.3.0 (the current latest version) we've changed the default severity level for config linting to warning and added the --lint-config option, so you may change it to error. And now the CLI will exit on config errors. I hope this solves your issue at least partially.

@sheldonreddy the current behaviour (outputting additional details to stderr) is designed specifically and likely will not be changed in the near term. Please describe your use case so we can better understand your need in the stderr output.

I think that the root cause of the original issue was corrected by the move to handle invalid configuration correctly. This means that the situation where a successful exit code is reported despite errors during processing.
We use stderr to output information about a command, to keep that diagnostic information separate from the command output. From this discussion, it seems that we should offer a way to suppress this, so I have opened #1335 as a feature request. Please check that issue meets your expectations, and feel free to follow there for updates. I'll close this issue as I think the original report was addressed.


Prune directxman12 from OWNERS, etc

Since I'm no longer working on metrics, I figured it's time to remove
myself from a bunch of these so I don't block reviews, etc by accident.

/hold
till we get @s-urbaniak listed

/close

FWIW, I'm not working on metrics anymore either :/


Issue with UI not resetting after clicking "Parse Logs" button.

Issue with UI not resetting after clicking "Parse Logs" button. and no combat entity is selected. The different controls like the DataGrid and plots aren't resetting.
Found this in 1.1.0.

This has being addressed in 1.1.1.

This bug has been fixed. Closing.


Migrating to shared feathers-service-tests suite

This uses the shared test suite at https://github.com/feathersjs/feathers-service-tests. It looks like two tests are failing. @ekryski or @marshallswain maybe you can have a look?

Specifically $select and $not. I think $select just has the wrong format (it is tested against an array now) and it looks like NeDB doesn't support $not (which is odd because it is in the documentation).

I can take a look this afternoon most likely. I passed out early last night so I'll be hammering pretty hard on Feathers today. :sleeping:

Ok should be fixed now. I had to update the tests for $not and submit a PR for feathers-knex.

So the tests for $not were actually what $ne is supposed to do. This one should be good to go now except for the updated documentation that I am currently working on.


Problem with "vagrant up"

C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/guests/linux/cap/mount_virtualbox_shared_folder.rb:64:in `mount_virtualbox_shared_folder': undefined method `+' for nil:NilClass (NoMethodError)
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/capability_host.rb:111:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/capability_host.rb:111:in `capability'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/guest.rb:43:in `capability'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/synced_folder.rb:51:in `block in enable'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/synced_folder.rb:35:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/synced_folder.rb:35:in `enable'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/synced_folders.rb:93:in `block in call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/synced_folders.rb:90:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/synced_folders.rb:90:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/synced_folders/nfs/action_cleanup.rb:19:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/prepare_nfs_valid_ids.rb:12:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:49:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/env_set.rb:19:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/provision.rb:80:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:15:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/set_name.rb:50:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/call.rb:53:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/call.rb:53:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/call.rb:53:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/box_check_outdated.rb:78:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/match_mac_address.rb:19:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/discard_state.rb:15:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/import.rb:44:in `clone'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/import.rb:11:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/prepare_clone_snapshot.rb:32:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/prepare_clone.rb:15:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/import_master.rb:36:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/customize.rb:40:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/call.rb:53:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builtin/call.rb:53:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/machine.rb:225:in `action_raw'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/machine.rb:200:in `block in action'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:567:in `lock'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/machine.rb:186:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/machine.rb:186:in `action'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

Closing this as a duplicate of #912.


[Improvement] It's unnecessary to use ConcurrentHashMap for "partitionToBlockIds" in RssShuffleWriter

Code of Conduct

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

Search before asking

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

What would you like to be improved?
For RssShuffleWriter, each task has unique instance of RssShuffleWriter. Thus, there is only one thread access its field, "partitionToBlockIds". It's inappropriate to use ConcurrentHashMap and ConcurrentHashSet like below.
`
this.partitionToBlockIds = Maps.newConcurrentMap();
partitionToBlockIds.putIfAbsent(partitionId, Sets.newConcurrentHashSet());
`
How should we improve?
We can just use simple HashMap and HashSet which avoid unnecessary locks.
Are you willing to submit PR?

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

Will it bring too much cost?

Will it bring too much cost?

I cannot tell how much cost it is. But you can imagine we need to get lock first before each map operation in each shuffle write partition. And it's counter-intuitive to use lock whilst it's unnecessary. We should avoid lock as much as possible.

If there is no thread conflicts, the clock operation only cost ns.

If there is no thread conflicts, the clock operation only cost ns.

maybe. There is other potential side-effect, like flushing CPU buffer to memory due to lock involved. So, it's better to avoid lock.

I'm in favor of this. The following code path doesn't need a ConcurrentHashMap as well.
https://github.com/apache/incubator-uniffle/blob/ddf83843a9fbce8155d159815c351b16eb5a9704/client/src/main/java/org/apache/uniffle/client/impl/ShuffleWriteClientImpl.java#L476

I just re-checked the code. It's different case since the shuffleWriteClientImpl instance is created in RssshuffleManager and shared by different threads. So, it's reasonable to use concurrenthashmp here.

The groupedPartitions is a local variable, it will never be used across threads?

correct. let me fix it along with RssShuffleWriter.


Support runnables in macros

fixes  #4771

Yeah, I do think we should move as far as possible of ast and into hir
acros the board
On Monday, 18 January 2021, Edwin Cheng<EMAIL_ADDRESS>wrote:

@edwin0cheng commented on this pull request.
In crates/ide/src/runnables.rs
https://github.com/rust-analyzer/rust-analyzer/pull/7321#discussion_r559761879
:

@@ -96,9 +96,7 @@ impl Runnable {
pub(crate) fn runnables(db: &RootDatabase, file_id: FileId) -> Vec {
let sema = Semantics::new(db);
let source_file = sema.parse(file_id);

source_file

   .syntax()

   .descendants()

sema.descendants_with_macros(source_file.syntax().clone())

I thought about it, but the original implementation find all functions and
module in all scopes. Of course I can find it recursively, but it will be
little bit complicated.
But I am okay for both approaches if you prefer.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rust-analyzer/rust-analyzer/pull/7321#discussion_r559761879,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANB3MZZZX22URAPUIOYKALS2SDXTANCNFSM4WHHCYZQ
.

Yeah, I do think we should move as far as possible of ast and into hir
acros the board
On Monday, 18 January 2021, Edwin Cheng<EMAIL_ADDRESS>wrote:

@edwin0cheng commented on this pull request.
In crates/ide/src/runnables.rs
https://github.com/rust-analyzer/rust-analyzer/pull/7321#discussion_r559761879
:

@@ -96,9 +96,7 @@ impl Runnable {
pub(crate) fn runnables(db: &RootDatabase, file_id: FileId) -> Vec {
let sema = Semantics::new(db);
let source_file = sema.parse(file_id);

source_file

   .syntax()

   .descendants()

sema.descendants_with_macros(source_file.syntax().clone())

I thought about it, but the original implementation find all functions and
module in all scopes. Of course I can find it recursively, but it will be
little bit complicated.
But I am okay for both approaches if you prefer.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rust-analyzer/rust-analyzer/pull/7321#discussion_r559761879,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANB3MZZZX22URAPUIOYKALS2SDXTANCNFSM4WHHCYZQ
.

Fixed.

Yeah, I do think we should move as far as possible of ast and into hir
acros the board

I get what you meant now, it is because hir has already expanded all macros such that we don't need to expand anymore.
Cool !

Fixed.

Yeah, I do think we should move as far as possible of ast and into hir
acros the board

I get what you meant now, it is because hir has already expanded all macros such that we don't need to expand anymore.
Cool !

bors r+

bors r+


data table not in readme?

Interested in using the data table but it's not listed in the readme

Was told to use https://github.com/bvaughn/react-virtualized


Use fallback if urls are not found

What problem are we solving?
https://github.com/chrislusf/seaweedfs/issues/3310
Normally resolve urls at the moment of leader change
How are we solving the problem?
Normally resolve urls at the moment of leader change
https://github.com/chrislusf/seaweedfs/issues/3310
Checks

[ok ] I have added unit tests if possible.
[ok] I will add related wiki document changes and link to this PR after merging.

I did some tests on our server. If the master leader was killed, Slave needed 5-15 seconds to became leader.
So  in this situation whether 2.55 seconds seems to be a little short?


Install a CMake config file with the library

I had to split this PR into two commits:

Change the CMakeLists.txt to install a CMake config file
Fix errors when building the unit tests caused by the fact that not all flags are global anymore

All the tests passed: cd build_ && ctest --output-on-failure. I also tried linking against LibCDS from a CMake-based project I have (the one I want to use LibCDS from), and everything seemed to work just fine. Compiler flags and linker flags were propagated properly to my library. All I had to do in my own CMakeLists.txt was (after installing LibCDS and placing its path in CMAKE_PREFIX_PATH):
find_package(LibCDS)
add_library(mylib INTERFACE)
target_link_libraries(mylib INTERFACE LibCDS::cds)

This closes #80.

Great work, Lois! All tests are done without my intervention - just merge and build.
Thank you very much!


Bot Image reposting

Guys this would be moderately entertaining.
When someone replies to an image with the command and specifies a date afterwards, the bot will repost the image at the specified date. alternatively instead of the parameter being a date it could also be a specified amount of time.
we could also have a second parameter for channels but I think that might cause too many problems
I don't think this would be too complicated so I could probably do it myself.

The bot has a database container attached to it, ive not yet poked around but i bet you could implement this using the database for persistant storage :3
as im working on code cleanup for the subteams cog im noticing a bunch of stuff got changed with the way cogs and cog loading works :/ so maybe wait till i iron it all back out.
Whats this for though?~ xD

There's at least 1 practical use for this that I can think of.
it could be used to repost important info at a time when we need it. For example: during a comp
But mostly people will probably use it to  do stupid stuff like make the bot post images at unusual times of the day
also we can probably have the command also do the same thing for text too. Don't really know why I specified just images earlier
Casey pointed out to me that the tetris toaster discord bot has commands that work in a similar way so I can look at them for a rough concept


Supplementary?

Hi, thanks for your contribution. When will you release the supplementary refered in the paper?

Thanks for your interest. The supplementary is now available at google drive.


I can't typing  only lowercase 'i' in my wsl2 + ubuntu environment. How can i fix  it?

Version
10.0.19042.867
WSL Version

[ ] WSL 2
[X] WSL 1

Kernel Version
5.4.72
Distro Version
Ubuntu 16.04
Other Software
No response
Repro Steps
don't needed
Expected Behavior
don't know
Actual Behavior
nothing
Diagnostic Logs
don't needed

only lowercase type 'i' don't work in wsl2

Closing as this is not helpful for giving context as to what is happening and how to investigate. Highly likely that this is not even related to WSL


Unable to access files on S3 with tf.io.gfile.GFile

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock
example script provided in TensorFlow): yes
OS Platform and Distribution (e.g.,
Linux Ubuntu 16.04): MacOS Mojave
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if
the issue happens on mobile device:
TensorFlow installed from (source or
binary): - TensorFlow version (use command below): 2.0.0
Python version: - Bazel
version (if compiling from source):
GCC/Compiler version (if compiling from
source):
CUDA/cuDNN version: - GPU model and memory:

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with: 1. TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)" 2. TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Describe the current behavior
Executing the following code:
with tf.io.gfile.GFile("s3://path/to/my/file", mode="r") as f:
    data = f.read()

results in the following error message:
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
  File "/Users/neelabh/opt/anaconda3/envs/tftrt/lib/python3.6/site-packages/tensorflow_core/python/lib/io/file_io.py", line 124, in read
    length = self.size() - self.tell()
  File "/Users/neelabh/opt/anaconda3/envs/tftrt/lib/python3.6/site-packages/tensorflow_core/python/lib/io/file_io.py", line 102, in size
    return stat(self.__name).length
  File "/Users/neelabh/opt/anaconda3/envs/tftrt/lib/python3.6/site-packages/tensorflow_core/python/lib/io/file_io.py", line 727, in stat
    return stat_v2(filename)
  File "/Users/neelabh/opt/anaconda3/envs/tftrt/lib/python3.6/site-packages/tensorflow_core/python/lib/io/file_io.py", line 744, in stat_v2
    pywrap_tensorflow.Stat(compat.as_bytes(path), file_statistics)
tensorflow.python.framework.errors_impl.NotFoundError: Object s3://[REDACTED]/train.txt does not exist

Describe the expected behavior
The contents of the file should be written to variable data
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
This points to a public s3 file, but still fails:
https://colab.research.google.com/drive/1VSlfzRPdFNSGGI8wd6RdhH9uFj7fkaFG
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
2020-03-30 23:22:36.465054: I tensorflow/core/platform/s3/aws_logging.cc:54] Initializing config loader against fileName /Users/neelabh//.aws/config and using profilePrefix = 1
2020-03-30 23:22:36.465103: I tensorflow/core/platform/s3/aws_logging.cc:54] Initializing config loader against fileName /Users/neelabh//.aws/credentials and using profilePrefix = 0
2020-03-30 23:22:36.465129: I tensorflow/core/platform/s3/aws_logging.cc:54] Setting provider to read credentials from /Users/neelabh//.aws/credentials for credentials file and /Users/neelabh//.aws/config for the config file , for use with profile default
2020-03-30 23:22:36.465207: I tensorflow/core/platform/s3/aws_logging.cc:54] Creating AWSHttpResourceClient with max connections2 and scheme http
2020-03-30 23:22:36.465336: I tensorflow/core/platform/s3/aws_logging.cc:54] Initializing CurlHandleContainer with size 2
2020-03-30 23:22:36.465391: I tensorflow/core/platform/s3/aws_logging.cc:54] Creating Instance with default EC2MetadataClient and refresh rate 300000
2020-03-30 23:22:36.465427: I tensorflow/core/platform/s3/aws_logging.cc:54] Added EC2 metadata service credentials provider to the provider chain.
2020-03-30 23:22:36.465682: I tensorflow/core/platform/s3/aws_logging.cc:54] Successfully reloaded configuration.
2020-03-30 23:22:36.465889: I tensorflow/core/platform/s3/aws_logging.cc:54] Initializing CurlHandleContainer with size 25
2020-03-30 23:22:36.466559: I tensorflow/core/platform/s3/aws_logging.cc:54] Pool grown by 2
2020-03-30 23:22:36.466586: I tensorflow/core/platform/s3/aws_logging.cc:54] Connection has been released. Continuing.
2020-03-30 23:22:37.536377: E tensorflow/core/platform/s3/aws_logging.cc:60] HTTP response code: 301
Exception name:
Error message: No response body.
7 response headers:
content-type : application/xml
date : Mon, 30 Mar 2020 17:52:37 GMT
server : AmazonS3
transfer-encoding : chunked
x-amz-bucket-region : eu-north-1
x-amz-id-2 : 021phnKX0e6e9R+N9sMrXZHViGoHdzJrTT5rnyHyWsP8d9ErkPMZT02RbTZcjVeCVrI/3hDkWk8=
x-amz-request-id : 7DAC97A633CA370B
2020-03-30 23:22:37.536443: W tensorflow/core/platform/s3/aws_logging.cc:57] If the signature check failed. This could be because of a time skew. Attempting to adjust the signer.
2020-03-30 23:22:37.536681: I tensorflow/core/platform/s3/aws_logging.cc:54] Connection has been released. Continuing.
2020-03-30 23:22:37.818954: W tensorflow/core/platform/s3/aws_logging.cc:57] Encountered Unknown AWSError 'PermanentRedirect': The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
2020-03-30 23:22:37.819073: E tensorflow/core/platform/s3/aws_logging.cc:60] HTTP response code: 301
Exception name: PermanentRedirect
Error message: Unable to parse ExceptionName: PermanentRedirect Message: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
7 response headers:
content-type : application/xml
date : Mon, 30 Mar 2020 17:52:37 GMT
server : AmazonS3
transfer-encoding : chunked
x-amz-bucket-region : eu-north-1
x-amz-id-2 : ob9TL15Q4Y7/idUzUTWvurB3Z4nxfVYRV2V+9ly88HrVGuHytuZA1U02rhcL0vFUpv83vUxeO9o=
x-amz-request-id : 51E3695245C81463
2020-03-30 23:22:37.819138: W tensorflow/core/platform/s3/aws_logging.cc:57] If the signature check failed. This could be because of a time skew. Attempting to adjust the signer.
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
  File "/Users/neelabh/opt/anaconda3/envs/tftrt/lib/python3.6/site-packages/tensorflow_core/python/lib/io/file_io.py", line 124, in read
    length = self.size() - self.tell()
  File "/Users/neelabh/opt/anaconda3/envs/tftrt/lib/python3.6/site-packages/tensorflow_core/python/lib/io/file_io.py", line 102, in size
    return stat(self.__name).length
  File "/Users/neelabh/opt/anaconda3/envs/tftrt/lib/python3.6/site-packages/tensorflow_core/python/lib/io/file_io.py", line 727, in stat
    return stat_v2(filename)
  File "/Users/neelabh/opt/anaconda3/envs/tftrt/lib/python3.6/site-packages/tensorflow_core/python/lib/io/file_io.py", line 744, in stat_v2
    pywrap_tensorflow.Stat(compat.as_bytes(path), file_statistics)
tensorflow.python.framework.errors_impl.NotFoundError: Object s3://[REDACTED]/train.txt does not exist

There seems to be a failure before
Exception name: PermanentRedirect
Error message: Unable to parse ExceptionName: PermanentRedirect Message: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.

Can you also try with TF 2.1? tf-nightly? To bisect where the error comes from.

Here is what I did:
I ran the following code in a tensorflow/tensorflow:nightly container. TF version was 2.2.0-dev20200402
tf.io.gfile.stat("s3://neelabh-test-public-bucket/train.txt")
`
``

This produced the following error:

Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/lib/io/file_io.py", line 761, in stat_v2
return _pywrap_file_io.Stat(path)
tensorflow.python.framework.errors_impl.NotFoundError: Object s3://neelabh-test-public-bucket/train.txt does not exist

Now, when I install `boto3` in the same container and use `s3.Object().get()` I am able to download the file.  Also works with wget and the HTTP link to the file.

@nihil0
Is this still an issue?.
Please close this thread if the issue was resolved. Thanks!

Same problem here. Both these API calls (tf.io.gfile.stat or file_io.stat) fail with NotFoundError: Object s3:// <bucket_name>/<path/to/file> does not exist. But if I use boto3 I can download the files without any issue.
# Alternative to reproduce the error
from tensorflow.python.lib.io import file_io
print(file_io.stat('s3://<bucket_name>/<path/to/file>'))

Any news on this? I'm running into a similar issue with tf 2.2 and s3 on ec2.

I'm investigating this and similar issues

For my part it was an SSL problem whenever  I ran TensorFlow on an ec2 instance (curl 77 errors in the logs), I temporarily fixed it by setting S3_VERIFY_SSL=0.

I fixed this issue by adding AWS_REGION and S3_ENDPOINT environment variables. For example:
import os
os.environ['AWS_REGION'] = 'us-west-1'
os.environ['S3_ENDPOINT'] = 'https://s3-us-west-1.amazonaws.com'

@nihil0
Is this still an issue, can you please check on nightly and move this to closed status if resolved.

hi @Saduf2019 do you mind referencing the commit that is meant to fix this?

I have tested on the nightly build, and this problem still persists. The solution of @Abhipray does work: However I'd like to note that

download performance is really poor (100mb files takes over a minute on a connection that should be 10x faster)
no progress bar works with this

For my part it was an SSL problem whenever I ran TensorFlow on an ec2 instance (curl 77 errors in the logs), I temporarily fixed it by setting S3_VERIFY_SSL=0.

Not fixed in my case.
_tensorflow.python.framework.errors_impl.UnknownError: {{function_node wrapped__ReadFile_device/job:localhost/replica:0/task:0/device:CPU:0}} : curlCode: 77, Problem with the SSL CA cert (path? access rights?) [Op:ReadFile]

I am also getting curlCode: 77, Problem with the SSL CA cert (path? access rights?)


ResourceLink component

Description
Changes proposed in this pull request:

Add ResourceLink component
Fix little Luigi initialisation error

Related issue(s)
Closes #1561

/retest

/retest

/retest

/test pre-busola-integration-test-k3s-cluster

/retest


Dark mode option not working in Windows

I tried to change dark mode, but it shows an error.

Hey! We've tried to replicate this issue but we have no problem changing the theme...

@aguilaair I uploaded my screen recording.
https://user-images.githubusercontent.com/45334931/114602907-c0587100-9cb4-11eb-9716-ec8eecad6caf.mp4

@aguilaair I'm Using Flutter v1.12.13+hotfix.8, so I could not run this project now.

Ok, that's fine, let me see if I can send you over something to search for the error

Hey, this will probably change nothing, but have you tried running it as an admin?

@aguilaair I think that is it, I had mentioned in the settings, but its saving the fvm settings and it can't, You need admin in order to be able to manage the versions, and globals

Another option is to just turn own developer mode on windows

@msarkrish please let me know once you try the suggestion above

@aguilaair @leoafarias I run the sidekick as administrator but still same exception showing.

I think I know what the issue is, will push a fix on the next release

Need sidekick release for this fix @leoafarias

Hey, in the meantime here's a build:
Release.zip

@leoafarias @aguilaair  Sidekick 0.0.1 also have this problem and advanced mode enable disable problem

Ok, @leoafarias mind reopening this issue until it is IDd an fixed?

The issue should not have been closed, I added closes instead of fixes on the merge comment so it closed automatically

Issue should be fixed on 0.0.3


Azure Cognitive Search

Is there plans to integrate Azure Cognitive Search as vector store?

+1 to the question, found that this PR may be the starting point?

Tested part of PR2396 manually and the basics worked.
Could not figure out a way to use filters, when usint a {} empty reference I could reproduce the following, hope it helps
Error "searchRequest.filter with value "[object Object]" must be of type string." occurred in serializing the payload - undefined
```

Another issue detected, the Dimensions is fixed for 1536. It would be nice to be optional to change so as to be used with another embedding.

Azure Cognitive Search its the most important integration for enterprise data use cases. How can i help here? All community flowise is waiting for this.
Thanks @ladrians


Cannot Login with AddApiKey (return 401 error)

What I want to do.
I am using WPF to create a desktop app.
Want to keep the app logged in after it is restarted.
However, when I set up auth using AddApiKey, it returns an error like the one shown in the attached image, and I am redirected to the login page.
This is part of the code I wrote.
Configuration config = new Configuration
{
    BasePath = "https://vrchat.com/api/1",
    UserAgent = "VRChatAPI/1.0",
};

config.AddApiKey("auth", "authcookie_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx");
config.AddApiKeyPrefix("auth", "Bearer");
config.AddApiKey("twoFactorAuth", "xxxxxxxxxxxxxxxxxxxxxxxxx.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx");

authApi = new AuthenticationApi(config);

try
{
    // トークンが有効か確認
    var currentUser = authApi.GetCurrentUser();
    if (currentUser != null)
    {
        // 認証成功、アプリケーションを通常通り続行
        MessageBox.Show($"Logged in as {currentUser.DisplayName}");
        return;
    }
}
catch (Exception ex)
{
    MessageBox.Show("Authentication check failed: " + ex.Message);
    Console.WriteLine("Authentication check failed: " + ex.Message);
}

this is a error(ex.Message).

Environment:
Windows 11
Visual Studio 2022
net8.0

I believe that this issue is already fixed on main but is not released yet
Could you try building the dll from main and using that?

With the code from main, this works:
https://github.com/vrchatapi/vrchatapi-csharp/pull/20#issuecomment-2278460593

Thank you!
It's done.


feat/enh: Possibility to add self signed TLS Certs for the Ollama API

Validations

[X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that requests the same enhancement

Problem
Hello,
we would like to assign the Ollama Base API to a self signed HTTPS Address. (Because we want a encrypted communication between Continue and Ollama in our organisation)
Something like https://ai.example.test wich refers to the Ollama base Endpoint.
But after setting this route we get a cert error in VSCode (unable to verify first certificate):

In the Developer Console:

We can access the URL on the same server in the browser without getting any error.
Thank you!
Solution
No response

Any updates on that?
Has PR #1658 something to do with that?
There are multiple related Issues #889 #1474


fix(pcre2): add prefix path for additional archs

On debian arm64 path is /usr/lib/aarch64-linux-gnu, and looks like the autoconf script is not finding libraries there.
Signed-off-by: Felipe Zipitria<EMAIL_ADDRESS>

This is the build using docker buildx bake -f ./docker-bake.hcl --set nginx-alpine.platform=linux/arm64/v8 --progress plain nginx-alpine with the change:
11 123.5 configure: xml VERSION: 2.9.14
#11 123.6 configure: xml CFLAGS: -I/usr/include/libxml2 -DWITH_LIBXML2
#11 123.6 configure: xml LDADD: -lxml2 -L/lib -lz -llzma -lm
#11 123.6 checking if libxml2 is at least v2.6.29... yes, 2.9.14
#11 123.6 configure: using libxml2 v2.9.14
#11 123.6 checking for libpcre config script... /usr/bin/pcre-config
#11 123.7 configure: pcre VERSION: 8.45
#11 123.8 configure: pcre LDADD: -lpcre
#11 123.8 configure: pcre PCRE_LD_PATH: /-lpcre
#11 123.8 checking for PCRE JIT... yes
#11 125.0 configure: using pcre v8.45
#11 125.0 configure: PCRE2 support was marked as mandatory by the utilization of --with-pcre2=yes
#11 125.0 configure: Nothing about PCRE2 was informed during the configure phase. Trying to detect it on the platform...
#11 125.0 *** LOOKING AT PATH:  /usr/lib
#11 125.0 configure: PCRE2 library found at: /usr/lib//libpcre2-8.so
#11 125.0 *** LOOKING AT PATH:  /usr/local/lib
#11 125.0 configure: PCRE2 library found at: /usr/lib//libpcre2-8.so
#11 125.0 *** LOOKING AT PATH:  /usr/local/libpcre2-8
#11 125.0 configure: PCRE2 library found at: /usr/lib//libpcre2-8.so
#11 125.0 *** LOOKING AT PATH:  /usr/local/pcre2
#11 125.0 configure: PCRE2 library found at: /usr/lib//libpcre2-8.so
#11 125.0 *** LOOKING AT PATH:  /usr/local
#11 125.0 configure: PCRE2 library found at: /usr/lib//libpcre2-8.so
#11 125.0 *** LOOKING AT PATH:  /opt/libpcre2-8
#11 125.0 configure: PCRE2 library found at: /usr/lib//libpcre2-8.so
#11 125.0 *** LOOKING AT PATH:  /opt/pcre2
#11 125.0 configure: PCRE2 library found at: /usr/lib//libpcre2-8.so
#11 125.0 *** LOOKING AT PATH:  /opt
#11 125.0 configure: PCRE2 library found at: /usr/lib//libpcre2-8.so
#11 125.0 *** LOOKING AT PATH:  /usr
#11 125.0 configure: PCRE2 library found at: /usr/lib//libpcre2-8.so
#11 125.0 configure: PCRE2 headers found at: /usr/include
#11 125.0 *** LOOKING AT PATH:  /usr/lib64
#11 125.0 configure: PCRE2 library found at: /usr/lib//libpcre2-8.so
#11 125.0 configure: PCRE2 headers found at: /usr/include
#11 125.0 *** LOOKING AT PATH:  /opt/local
#11 125.0 configure: PCRE2 library found at: /usr/lib//libpcre2-8.so
#11 125.0 configure: PCRE2 headers found at: /usr/include
#11 125.0 *** LOOKING AT PATH:  yes
#11 125.0 configure: PCRE2 library found at: /usr/lib//libpcre2-8.so
#11 125.0 configure: PCRE2 headers found at: /usr/include
#11 125.1 configure: using PCRE2 v
#11 125.1 checking for stdio.h... yes
#11 125.5 checking for stdlib.h... yes

So the fix is making the build finding the correct libraries.


updated TweetEntitiesMention in models

Stream API returns mention text as 'username', not 'tag', as in hashtags, so the data model for mentions needs to be updated in order to gather mention data correctly.

Yes, you are right, Thanks a lot!


Revert "Support available((swift_attr("@Sendable")))"

Reverts apple/swift#40170
This broke the Windows build: https://ci-external.swift.org/job/swift-PR-windows/18665/console
The tests on the PR indicated that it was part of the change..  This should be easy to fix, there is a missing symbol (either a missing dependency or function).  However, given the imminent freeze, I'd like to get the tree green.

@swift-ci please smoke test

CC: @beccadax

Merging early to unblock CI.


auth-stuff: reduce clutter in pipeline defs

OPA doesn't need a studio for its tests
local-user-service doesn't need a studio for its tests, combine static and unit again.
installing the CLI opa in the Makefile is probably not needed
remove privileged: true from some deployment-service steps that don't need them

DC-oh-no!


As an organisation I can edit only my offer

 Issue by bakalaw
Wednesday Feb 24, 2016 at 12:40 GMT
Originally opened as https://github.com/stxnext-csr/volontulo/issues/470

AC -
Organisation has a list of its offers.
Organisation can edit only its offers.
The button "Edit" next to another organization's offers should be hidden
Currently editing other organization's is not possible even though the edit button is displayed. After clicking on it following error is displayed

 Comment by w1stler
Thursday Sep 15, 2016 at 18:25 GMT

Moving to Merged column: https://travis-ci.org/stxnext-csr/volontulo/builds/112117373

Done


'Go to definition' prefers root of repo, even if outside of project folder

Environment data

VS Code version: 1.27.2
Extension version (available under the Extensions sidebar): 2018.8.0
OS and version: Mac OS 10.13.6
Python version (& distribution if applicable, e.g. Anaconda): XXX
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Relevant/affected Python packages and their versions: Python 3.6

Actual behavior
"Go to definition" looks in the wrong path in the root of the repository, when its name matches the file in the currently opened folder.
This only happens, when the project is a subfolder of a repository. If the .git folder is removed, it works as expected.
Maybe this is related to issue 2555? Using the language server with "python.jediEnabled": false also avoids this problem.
Expected  behavior
Ignore files in the root of the repository, if outside of project (or reduce priority).
Steps to reproduce:
Given the following folders:
.git
project/
    .vscode/
        settings.json
    main.py
    utils.py
utils.py

Open the folder project/ in vscode
Open the file main.py
Use "Go to definition" on import utils

vscode jumps to /utils.py instead of project/utils.py, even though it is outside the project.
If the /.git folder is removed, it works as expected. Running python main.py works as expected in any case.
Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
##########Linting Output - pylint##########

--------------------------------------------------------------------
Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
(no output)

Thanks for the report @sebastian-b, and the details you've provided.

Using the language server with "python.jediEnabled": false also avoids this problem.

Is this workaround not a viable solution for you? Could you tell us why, if that is the case?
Otherwise, I believe this is more an issue with jedi than with the extension itself, but we should repro just in case we're doing something wonky here!

Is this workaround not a viable solution for you?

It is! I only saw the workaround after creating the ticket and since this setting was described as experimental, I left the ticket open.

Understood, thanks for letting us know.

I have verified that this does indeed happen when Jedi is enabled.
If I run the script I've created, it runs as expected (picks up the local utils version, not the one located at the workspace root).
Here's my layout:

${workspaceFolder}\utils.py:
def base_util():
    print("base")

def common():
    print("base-common")

${workspaceFolder}/project/utils.py:
def project_utils():
    pass

def common():
    print("project-common")

${workspaceFolder}/project/main.py:
import utils

utils.common()

From the terminal, if I run this I see:
dekeeler@dek-laptop-lnx:~/dev/github/d3r3kk/test/2585_jedi_navigation_oddity$ python3 project/main.py
project-common

But if I use Go to definition inside of main.py on the call to utils.common (line 3), I get taken to the ${workspaceFolder}/utils.py version of the function.

Files that we potentially need to diagnose:
pythonFiles/completion.py
src/client/providers/jediProxy.ts
Hypothesis: We are finding the definitions for both (all) functions/libs but are only using the first one found to jump to.

@d3r3kk I've found that currently, it is worse than that. Not sure if it should be reported as a separate issue.
If I have flask or tensorflow installed in the project's virtualenv which both have logging module inside their namespaces "Go to definition" on import logging will open flask/logging.py or tensorflow/logging.py instead of logging from the stdlib.

HI,
I managed to solve this issue by getting the latest jedi via pip and setting it's path in vscode settings:
"python.jediPath": "c:\\users\\<yourusername>\\appdata\\local\\programs\\python\\python37-32\\lib\\site-packages"

We have recently released a new and more performant language server called Pylance which likely solves these issues you are reporting.  You can download Pylance from the marketplace and install it alongside the core Python extension. Because our team's development efforts have shifted to support the new language server, we'd encourage you to try it out.

@luabud it's worth mentioning that Pylance is not Open Source. It is based on Pyright which is, though.

Fixed in Jedi behind LSP.


[GOBBLIN-1373] make HighLevelConsumer poll for records without waiting

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1373

Description

[x] Here are some details about my PR, including screenshots (if applicable):
HighLevelConsumer thread sleeps for 50ms after doing a poll. This significantly reduces its speed of consumption.
This PR will make the polling a continuous task to speed consumption up

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
trivial changes. tested with a manualjob run

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3215 (0bfd18c) into master (f4c7513) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

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

Codecov Report

Merging #3215 (0bfd18c) into master (f4c7513) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

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


Migrate to jQuery 3.0

http://blog.jquery.com/2015/07/13/jquery-3-0-and-jquery-compat-3-0-alpha-versions-released/:

the most important rule for moving to jQuery 3.0 is this: Don’t use a stylesheet to set the default of display: none and then try to use .show() – or any method that shows elements, such as .slideDown() and .fadeIn() – to make it visible.

If you need an element to be hidden by default, the best way is to add a class name like “hidden” to the element and define that class to be display: none in a stylesheet. Then you can add or remove that class using jQuery’s .addClass() and .removeClass() methods to control visibility.

Done (911eea0 and c9c2998)


layout issues with comments form

In Firefox, the comments form for an album is displayed on top of the album contents.
In Safari & Chrome, you cannot scroll down to the comments form. The page kind of jumps up and down.

In Piwigo core, albums don't have a comment feature. You must be using some plugin.

That is correct: https://piwigo.org/ext/extension_view.php?eid=512
And it works fine with other themes.
I was wrong about the browsers before. The behavior actually depends on the window width. If the window is wide enough (roughly 2500px) then everything is OK. When you start narrowing it down is when you get the the superimposing or jumping.


Add default headers implementation TargetType

Hi all,
public protocol TargetType {
    var headers: [String: String]? { get }
}

This's a very good addition to the framework. But I think that headers customisation can be a rare case. So I suggest adding default implementation for this.
What others think about it?

@larryonoff I believe one of Moya's design philosophies is to "favour explicitly-defined behaviour over default implementations.". Therefore, we're trying to avoid default behaviors.

@SD10 hah! thanks!
I see that sampleData usually Data()...


Split code into MVC

Start splitting up the code into MVC as it might become bigger and bigger
Solution:

implement the MVC patterns in python

Implemented


GNSS/GPS not working

Hello,
I bought a LILYGO T-SIM7670G-S3 ESP32-S3 4G LTE Wireless Cellular IOT Devices Low-power Long-range Communication with GPS TTGO Development Board from the Lilygo amazon store. I have tried various example codes to get the GPS to work but I can't seem to get it working. the unit is placed outside with the antenna pointing to the sky.
Which boards have GPS capability built in, as this is not clear in the main readme page

See FAQ  Second point

Explain how to perform "First, determine whether the purchased board model supports GPS function, regardless of whether the physical board contains a GPS antenna interface."
If a board is installed with a GPS antenna mount, sold with an antenna, and your own shop lists it as having GPS on amazon, it would be reasonable to assume this is a function. explain how i confirm i verify the board has the capability before i upload the NMEA bin

If the GPS antenna is included, it usually has GPS function. You can perform the second step to test whether there is NMEA message output.


Some Platforms are no longer working due to changes with Archive.org

Some platforms such as Playstation are no longer working, as files are locked and an account is now required to download them.

Thanks for the report, it's appreciated.
I've deliberately left out any "download all ROMs" options from ROMweasel to avoid unnecessary load on archive.org bandwidth and I'm quite sure we're not the cause for the lockdown. I'm also not willing to do what update_all MAME ROM downloader did, which was to upload a new dedicated repository to archive.org to circumvent the lock. Instead, I'll adopt the proper fix from update_all, which adds support for setting a login username and password for downloading from locked repositories.

Preliminary fix committed: https://github.com/Koston-0xDEADBEEF/MiSTer-ROMweasel/commit/24d295d170c662088ab12998e85da3e79f88f9dd
I'm closing this issue now, because my time/interest for maintaining this project is limited. Let me know if there's something fundamentally broken, besides not dealing properly with failures from attempting to use locked repos without login.


microk8s bin commands not available

Installed via
snap install microk8s --classic
with the following result
microk8s v1.12.0 from Canonical✓ installed
No obvious errors and kube appears to be running.
None of the microk8s binaries look to be automatically available on the path.
I've found them located under \snap\microk8s\current\
Aliasing also doesn't work presumably because the binaries aren't on the path to correctly.
Is this something I need to fix in the installation on my system or a bug with the snap package?
Thanks!
snap       2.35.2
snapd      2.35.2
series     16
linuxmint  18.1
kernel     4.4.0-53-generic

Hi @singram ,
All snap binaries should be available under /snap/bin/ and microk8s should not be an exception. Can you please make sure you have /snap/bin in your PATH?
Thank you for using microk8s.

Thanks for the assistance, appreciated.
PATH is now fixed and the issue is resolved.

Thanks for the assistance, appreciated.
PATH is now fixed and the issue is resolved.

Do you mind if you can share how did you fixed the issue?  Thanks in advance!

Came here looking for a solution to the same problem and couldn't find it, so wanted to include my solution for others to try in case they are in the same situation:
In the install steps, I did not set my PATH for snapd.
To add /snap/bin to your PATH, run export PATH="$PATH:/snap/bin",  and check that it's in your PATH with echo $PATH
For reference, I got my solution from this site.
Hope this helps somebody!


Writing Auto Test for changing Statuses Scenarios

[x] If Listing=Null stayed more than N days, automatically set it to "Listed"
[x] Edit Projects: won't affect Verification status - changes listing to "not reviewed" means listing=null
[x] Deactivating (Archiving): won't affect Verification status - won't affect listing status.
[ ] Activating (Unarchiving): won't affect Verification status - changes listing to "not reviewed"
[x] Cancelling (By admin): make it unverified & delisted.
[x] Verification approved: won't affect the listing status
[x] Verification removed: won't affect listing status.
[x] Delisting: won't affect the verification status,
[x] Listing: won't affect the verification status,

Hey team! Please add your planning poker estimate with ZenHub @mohammadranjbarz @CarlosQ96

I'll put 8, as I have to get familiar with certain testing tools first.

@WhyldWanderer  @MoeNick  I saw the code and I noticed the user can not active a deactivated/cancelled project, so this endpoint is useless, and I can't write test for this
** Activating (Unarchiving): won't affect Verification status - changes listing to "not reviewed"**
If it's a bug please tell me to fix that otherwise we can remove that from checklist

@WhyldWanderer @MoeNick I saw the code and I noticed the user can not active a deactivated/cancelled project, so this endpoint is useless, and I can't write test for this Activating (Unarchiving): won't affect Verification status - changes listing to "not reviewed" If it's a bug please tell me to fix that otherwise we can remove that from checklist

Sorry it was my mistake, the description of statuses was misleading, so I misunderstood

@MoeNick
I wrote a migration file to change description/name of statuses in this PR, and I wrote a table for that, you can see that here
https://github.com/Giveth/impact-graph/tree/f_343_write_tests_for_changing_statuses_scenarios#statuses

PR approved! All tests correlate the list.


Support skipLabels that contain forward slash

The skipLabels currently splits labels that contain / into multiple labels so skip/changelog becomes skip, changelog. This change fixes that so that a single skip/changelog (for example) label can be used.

Will merge and put this in the next release. Thinking a 3.5.0 since I don't see it as a patch but an improvement to support more label names


Included automation to build libtensorflow. ( fix on install protobuf )

Hi there @jkjung-avt , let me first thank you for providing the repo with out of the box clean installs. Kudos :100: :)
Opening this PR to check if you have interest in providing out of the box build scripts for libtensorflow ( and a quick fix on protobuf ). wdyt?

Thanks for submitting this patch.