Streaming Dockers aren’t playing nice (Plex, Emby, Jellyfin).

Ken,
I’m sure I’m a one off case issue. I’ve rebuilt and redesigned my setup since I first started this journey.  I’ve taken some of your influence (thank you) and some of my own direction. I’m currently running my OmniStream setup on a Debian VM on a Proxmox Host Cluster. You likely have much more experience with Proxmox than I have at this point. The issue I have is with the three media streamers mentioned above which is weird. My issue is that I have CEPHFS configured on my hosts and I have it kernel mounted to the Debian VM as my Media volume. I have that volume mounted the same way for all of the containers where I use it. All of the ‘ARR containers see it with no problem along with Calibre and another container I use. The three culprits go into a shutdown reboot loop after the scripts finish running. If I comment out the volume mount in the yaml and use the VARIABLE /Media volume, Emby and Jellyfin boot normally. Plex I haven’t nailed down to issues with the mount or the restore from backup yet. I can focus on it later - I use Emby primarily (less space overhead).  I’m trying to keep the kernel mount for better performance rather than try a ceph-fuse mount or SMB mount. Any ideas why those three are having issues and the other containers are not? I have one other thing to troubleshoot and hate to go that route but I can if need be because its time consuming. Like I said this is likely a single case use issue that others will never encounter. I’m just looking for direction. Thanks! @kelinger @TechPerplexed

So the troubleshooting I wanted to do was to ensure Debian 12 on my guest vm wasn't the issue. I stood up a Debian 11 box, threw a fresh install on it, and restored my backup. Same issue. On a positive note I was able to verify the issue is not with the cephfs mount. In the brief moments between restarting I was able to console into the container and the volume mount was there and accessible. I'm now troubleshooting my backup of the servers. I'm on different hardware and previously was using hw encoding whereas now I am not. Additionally the back up was from April prior to my rebuild efforts. I'm looking at vanilla installs and migrating my databases.

Unfortunately, I haven't really used Proxmox to do much more than host my systems and a few VMs.  Which is to say, it's a fairly simplistic setup.  I've found that, for replication, simply backing the LXC or VM up daily (to Google) and pulling it down to another Proxmox install if/when needed has suited my purposes.  Yeah, it's not a hot-standby or instant-failover configuration but it's also simple to manage.
I agree, though, that the problem is very unlikely the guest systems, whatever they are.  From the standpoint of Proxmox, its still the same CPU/Memory/etc. configuration and it shouldn't really care what's running.
Is it possible that mounting the media from the virtualized guest is being attempted before the guest is ready?

Solved this one. It was the health checks. Health checks are scripted to use MEDIA variable. I don’t use that variable because my files are local. REM’d them out for now. Any idea what I would need to use SS cmd instead of Netstat since its depreciated and not used on some containers. What I’ve tried for SS has not worked. It should just simply be SS -t -l -a -p. That gets me nowhere.

Problem found and worked around.


Add test for the qnn_add operator

The tests use fake quant approach so until the tf session, tensors remain in float32.
The test data has to be passed in uint8 because of how the tflite/tvm comparison works.
Abs tolerance up to 1 is allowed for the qnn results. For now input_stats are hardcoded
assuming the tests for the other qnn ops will pass the input data in the same range.

@FrozenGene @anijain2305 can you please review this patch

@inadob Thanks for improvement. Abs tolerance up to 1 doesn't make sense. I think it should be the problem I discuss with @anijain2305 : https://github.com/apache/incubator-tvm/pull/3900#discussion_r334324818. Better way should be we handle it in TFLite parser, then we could compare it with tflite elementwise, you don't need to set it  abs tolerance up to 1, it is too large. I could do it later. Or if you are interested, you could handle this issue, how about you?

If I understand tolerance correctly, I think atol of 1 is good for integers and current implementation. Let me know if I am wrong.
For integers, either you say match exactly, or if you want to have a tolerance, it can be minimum 1. There is nothing in between. Currently, as there is a difference between TFLite and TVM rounding, there is bound to be some differences and the minimum difference can be 1.
This PR makes a big jump in improving the testing infrastructure for TFLite quantized networks and enabling unittests. So, I think this is a very good addition. The atol is an artifact of implementation which we can solve separately.
@FrozenGene Will you be willing to create a separate RFC for implementing TFLite rounding in TVM? I don't think we should stall this PR.

If I understand tolerance correctly, I think atol of 1 is good for integers and current implementation. Let me know if I am wrong.
For integers, either you say match exactly, or if you want to have a tolerance, it can be minimum 1. There is nothing in between. Currently, as there is a difference between TFLite and TVM rounding, there is bound to be some differences and the minimum difference can be 1.
This PR makes a big jump in improving the testing infrastructure for TFLite quantized networks and enabling unittests. So, I think this is a very good addition. The atol is an artifact of implementation which we can solve separately.
@FrozenGene Will you be willing to create a separate RFC for implementing TFLite rounding in TVM? I don't think we should stall this PR.

@anijain2305  I only concerned we will let our wrong implementation off. For example, we implement one operator XXX, we follow the test infra setting abs tolerance be 1. However, our implementation of XXX is wrong and only different 1 between correct result. This is my real concern before, not pointing to this pr.
I would like to implement TFLite rounding next and wish we could change the tolerance after that. We could let this PR in firstly :-)

Thanks @inadob @anijain2305 @FrozenGene


cibuildwheel is now providing a dedicated Github Action

See here in action: https://cibuildwheel.readthedocs.io/en/stable/setup/#github-actions

Fixed as part of #63


Caching AutomationElement

I'm not fully sure what is caching feature for. Can I interact with cached elements? Or it's only for purpose of accessing element property value? In the wiki there is mentioned an example of cache usage with grids. But grids aren't static - most grids in my app are using paging and any scroll can load more data.
Could someone provide a real world example of cache usage?

Caching is rather specific. I have some information here: https://github.com/Roemer/FlaUI/wiki/Caching
Is that enough for your question? If not, what is missing?

Generally you can interact with cached element in case they are still the current control that is displayed. This is usually less of the case of caching.
The usual case is that you have a search field and a grid showing the found results.
You would use the search normally and then, as soon as the grid is loaded, load that grid including children with caching.
Then you could navigate thru the grid and all child elements inside the cache without needing to send IPCs (Inter Process Calls) for each request.
If you use paging, you can load each page into the cache when it is needed and if you reload more data with scrolling, you can load each chunk that is loaded with the cached mode.
Caching is very specific and there are tons of pitfalls when using it. So I suggest only getting deeper into it if you have performance issues with the UI tests.

I added some more information and another example to https://github.com/FlaUI/FlaUI/wiki/Caching. Hope this makes it more clear, otherwise re-open this issue.


Go get error

I am getting this error when trying to install. Please HELP !
go get: github.com/zerodha/gokiteconnect/v3@none updating to
<EMAIL_ADDRESS>parsing go.mod:
	module declares its path as: github.com/zerodhatech/gokiteconnect/v3
	        but was required as: github.com/zerodha/gokiteconnect/v3

OS: MacOS Big Sur (Version 11.4)
go version:  go1.16.4 darwin/amd64
Tried:
go clean -modcache
go mod edit -replace github.com/zerodhatech/gokiteconnect/v3=github.com/zerodha/gokiteconnect/v3

For now, could you please try
go get<EMAIL_ADDRESS>Or
go get github.com/zerodhatech/gokiteconnect/v3
I'll look into a fix for this in the meanwhile.
On Sat, Jun 12, 2021, 10:22 PM rachit srivastava @.***>
wrote:

I am getting this error when trying to install. Please HELP !
go get: @.*** updating to
@.***: parsing go.mod:
module declares its path as: github.com/zerodhatech/gokiteconnect/v3
but was required as: github.com/zerodha/gokiteconnect/v3
OS: MacOS Big Sur (Version 11.4)
go version: go1.16.4 darwin/amd64
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zerodha/gokiteconnect/issues/40, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHINZHR5NAHEJQP3ERUZ5LTSOGGPANCNFSM46S4VZRQ
.

Worked! Thanks

This should be resolved now via https://github.com/zerodha/gokiteconnect/releases/tag/v3.3.0


Should we re-implement voxelEngine in server from scratch without using voxeljs?

My vote at this point is no... but we might consider it for later?

Issue moved to UnboundVR/metavrse-server #20 via ZenHub.io


Changing "editor.lineHeight" to any value >= 0.5 squishes text

VSCode Version: Code 1.16.0 (787b31c0474e6165390b5a5989c9619e3e16f953, 2017-09-06T16:27:49.891Z)
OS Version: Windows_NT x64 10.0.15063

Steps to Reproduce:

Change "editor.lineHeight" to any value >= 0.5
Save settings

Reproduces without extensions: Yes
"editor.lineHeight": 0

"editor.lineHeight": 1

"editor.lineHeight": 1.5

This looks correct. The documentation for that setting says Use 0 to compute the lineHeight from the fontSize.
What else do you expect for a very small line height?

I was expecting the setting to work similarly to other editors, where my
preferred setting is usually 1.2. What values should I be using in Code if
I want to make the line height smaller than default?
On Fri, 8 Sep 2017 at 2.25, Rob Lourens<EMAIL_ADDRESS>wrote:

This looks correct. The documentation for that setting says Use 0 to
compute the lineHeight from the fontSize.
What else do you expect for a very small line height?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/33968#issuecomment-327954717,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMJCB993XG67AZHEdDyqrX60P_g1iXyLks5sgHuBgaJpZM4PQc1V
.

They must have a different definition of it. I think maybe it's on the same scale as font size. But you should just increase it until you find a comfortable value.

Seems markdown.preview.lineHeight and terminal.integrated.lineHeight both use relative values, only editor.lineHeight is absolute. It's a little bit inconsistent.

Okay, I got it now. I had to set it to 15 to get the result I was after. It might be a good idea to mention in the documentation what values the setting is expecting.

I see, the terminal value is like a multiplier. Maybe the editor.lineHeight description should have another sentence about how the value is used.

I suggest you make editor.lineHeight a multiplier to keep consistency with terminal.integrated.lineHeight and markdown.preview.lineHeight. Thanks 😄

@luangong unfortunately it is too late to do that, as we probably have by now very many users that have customized it using the current behaviour.
Since more than 5 years, the editor.lineHeight is the value, in CSS pixels of the amount of space used for lines vertically.
I am sorry it is not a multiplier as you were expecting.
We can improve the documentation, but this is one of those things that is too late to change.

Is it possible to add another setting called editor.lineHeightUnit and default it to px? The value of editor.lineHeightUnit can be px, em, cm, etc.

@luangong yes, anything is possible. If that would reduce confusion or increase it, is hard to tell.

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!


View::PLACEHOLDER_* hack

What steps will reproduce the problem?
The framework level does not cover placeholder protection.
If, for example, I have an HTML content input form, then the placeholder can be inserted in it, in this case the rendered result will be wrong and it will require find a long time for developers to find out why the page design has crashed.
https://github.com/yiisoft/view/blob/4e39cf8a18b148a28e1d585fa29e46f6f9464b3d/src/View/WebView.php#L69-L80
What is the expected result?
placeholder protection is automatic or provide helper for protection.
What do you get instead?
placeholder is injectable.
I suggests
Instead of constants, it should be a variable that always contains a random string.
$placeholderbodybegin = '<![CDATA[YII-BLOCK-BODY-BEGIN-'.$uniqueRandomHash.']]>';

Q
A

Version
3.0.x-dev

PHP version
-

Operating system
-

It is unlikely that someone will use <![CDATA[YII-BLOCK-BODY-BEGIN]]> in HTML. Never happened to anyone, I think. At least it was never reported to issue tracker of Yii 2.

In my opinion, minimal work to improve, so it is irrelevant to ignore.

Generating unique placeholder means that we have to store it somewhere. That's introducing more state thus making everything a bit more complicated and potentially hurting performance / memory usage a tiny bit. Current solution is acceptable trade-off that caused no problems in 10 years.
@yiisoft/core-developers, @yiisoft/reviewers need more opinions.

I'm for fixing it. We don't need to generate and store hash - it could be set explicitly in component configuration, with md5(__DIR__) as a fallback.

    public function endPage($ajaxMode = false): void
    {
        $this->eventDispatcher->dispatch(new PageEnd($this->getViewFile()));

        $content = ob_get_clean();

        echo strtr($content, [
            self::PH_HEAD => $this->renderHeadHtml(),
            self::PH_BODY_BEGIN => $this->renderBodyBeginHtml(),
            self::PH_BODY_END => $this->renderBodyEndHtml($ajaxMode),
        ]);

        $this->clear();
    }

Will the potential problem be fixed by the fact that we will search and replace self :: PH_BODY_END from the end?
It can also work faster on large pages.

@rob006 wouldn't it be the same thing then? A magic value that, when met in the content will break rendering?

@rob006 wouldn't it be the same thing then? A magic value that, when met in the content will break rendering?

It is much less likely that it would happen, since it is no longer hardcoded value publicly known and identical in every Yii app. It will be basically impossible to exploit for example in comments system or have a conflict by creating some Yii guide where you need to mention this magic string.

no longer hardcoded value

So you still want to generate / store it?

So you still want to generate / store it?

If by "store it" you mean add property for it, which could be configured in app config - then yes, I want to store it. Default value could be generated based on app directory, but I'm fine with leaving it empty by default.

Got it. Yes. That would work.

But, I think, it's better to automatically generate / store this "salt" instead of allowing to change it.

You should be able to set it manually - it may be important in tests and cache context, where value should predictable and the same on multiple servers. It is similar story as for Request::$cookieValidationKey in Yii 2.

So you still want to generate / store it?

Not require store it. You must define a protected method, overwrite it for tests, and generate it for each instance.
class View {
  private string $placeholderSalt;

  protected function getPlaceholderSalt(): string {
    if($this->placeholderSalt === null) {
       $this->placegolderSalt = md5(microtime(true).mt_rand(1,1000000));
    }
    return $this->placeholderSalt;
  }
}

@kamarton AFAIK this salt should be shared between requests in order to cache work correctly.

this salt should be shared between requests in order to cache work correctly.

you're right.
Don't forget to change this too:
https://github.com/yiisoft/view/blob/fa61d35f016038d9ad12c8d80994413596fed1c2/src/View/View.php#L462

It is similar story as for Request::$cookieValidationKey in Yii 2.

Must be resolved if key value changes, do not use cache value otherwise placeholders will be output.


Generic class consumer leads to error with JSON / XML

If I have this class:
public class Request<TQuery, TQueryType> : CorrelatedBy<Guid>
        where TQuery : IQuery<TQueryType>
    {
        public TQuery Query { get; private set; }

        public Guid CorrelationId { get; private set; }

        public Request(TQuery query)
            : this(query, CombGuid.Generate())
        {
        }

        public Request(TQuery query, Guid correlationId)
        {
            this.Query = query;
            this.CorrelationId = correlationId;
        }
    }

And this Consumer:
public class RequestHandler : Consumes<Request<GetDataQuery, DataResult>>.Context
        where TQuery : IQuery<TResult>
    {
        private readonly IQueryHandler<TQuery, TResult> queryHandler;

        public RequestHandler(IQueryHandler<TQuery, TResult> queryHandler)
        {
            this.queryHandler = queryHandler;
        }

        public void Consume(IConsumeContext<Request<TQuery, TResult>> message)
        {
            message.Respond(
                new Response<TResult>(
                    this.queryHandler.Handle(message.Message.Query),
                    message.Message.CorrelationId));
        }
    }

And I publish a
new Request<GetDataQuery, DataResult>()

The message fails to get delivered when using the Json / XML formatter

What's happens when you can the consumer from public void Consume(IConsumeContext<Request<TQuery, TResult>> message) to public void Consume(IConsumeContext<Request<GetDataQuery, DataResult>> message)?
Also, how is the message published? Actually, I would start first with the how the message is published, make sure the compiler knows the type.

I've written this short program to demonstrate what I mean:
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace MassTransitProblemsDemo
{
    using System.Runtime.Serialization;

    using Magnum;

    using MassTransit;
    using MassTransit.Serialization;

    using Newtonsoft.Json;

    [Serializable]
    public class Animal
    {
        public string Name { get; set; }
    }

    [Serializable]
    public class Cat : Animal
    {
        public bool UsesCatLitter { get; set; }
    }

    [Serializable]
    public class Dog : Animal
    {
        public int NumberOfBarksPerMinute { get; set; }
    }

    [Serializable]
    public class Vet
    {
        public Animal TopAnimal { get; set; }

        public List<Animal> Animals { get; set; }
    }

    [Serializable]
    public class GetVet
    {
        public int Id { get; set; }
    }

    public class Request<TQuery, TQueryType> : CorrelatedBy<Guid>
        where TQueryType : Vet
    {
        public TQuery Query { get; private set; }

        public Guid CorrelationId { get; private set; }

        public Request(TQuery query)
            : this(query, CombGuid.Generate())
        {
        }

        public Request(TQuery query, Guid correlationId)
        {
            this.Query = query;
            this.CorrelationId = correlationId;
        }
    }

    public class RequestHandler : Consumes<Request<GetVet, Vet>>.Context
    {
        public void Consume(IConsumeContext<Request<GetVet, Vet>> message)
        {
            message.Respond(new Vet
            {
                TopAnimal = new Dog { Name = "Rolf", NumberOfBarksPerMinute = 3 },
                Animals =
                new List<Animal>
                              {
                                  new Cat { Name = "Mittens", UsesCatLitter = true },
                                  new Dog { Name = "Harvy", NumberOfBarksPerMinute = 1 }
                              }
            });
        }
    }

    class Program
    {
        static void Main(string[] args)
        {
            Bus.Initialize(sbc =>
            {
                sbc.UseRabbitMq();
                sbc.ReceiveFrom("rabbitmq://localhost/TestModule");

                sbc.Subscribe(configurator =>
                    {
                        configurator.Consumer<RequestHandler>();
                    });
            });

            Bus.Instance.PublishRequest(
                new Request<GetVet, Vet>(new GetVet { Id = 1 }),
                 x => x.Handle<Vet>(
                     vet =>
                     {
                         Console.WriteLine(vet.TopAnimal.GetType().ToString());
                         vet.Animals.ForEach(animal => Console.WriteLine(animal.GetType().ToString()));
                     }));

            Bus.Instance.Dispose();

            Console.ReadKey();
        }
    }

}

I get this error on the bus:

================================================================================
2015-06-05 16:02:00:621: Message published

Node:         rabbit@WS183
Connection:   [::1]:63554 -> [::1]:5672
Virtual host: /
User:         guest
Channel:      1
Exchange:     MassTransitProblemsDemo:Request--GetVet::Vet--
Routing keys: [<<>>]
Properties:   [{<<"message_id">>,longstr,
                <<"eb390000-73de-1803-bad2-08d26daf53a9">>},
               {<<"delivery_mode">>,signedint,2},
               {<<"headers">>,table,
                [{<<"Content-Type">>,longstr,
                  <<"application/vnd.masstransit+json">>}]}]
Payload:
{
  "requestId": "eb390000-73de-1803-f2d6-08d26daf53a8",
  "destinationAddress": "rabbitmq://localhost/MassTransitProblemsDemo:Request--GetVet::Vet--",
  "faultAddress": "rabbitmq://localhost/TestModule",
  "headers": {},
  "message": {
    "query": {
      "id": 1
    },
    "correlationId": "3e82d591-de1f-4957-bb89-a4ae01083925"
  },
  "messageType": [
    "urn:message:MassTransitProblemsDemo:Request[[MassTransitProblemsDemo:GetVet],[MassTransitProblemsDemo:Vet]]"
  ],
  "responseAddress": "rabbitmq://localhost/TestModule",
  "sourceAddress": "rabbitmq://localhost/TestModule"
}

================================================================================
2015-06-05 16:02:00:622: Message received

Node:         rabbit@WS183
Connection:   [::1]:63553 -> [::1]:5672
Virtual host: /
User:         guest
Channel:      2
Exchange:     MassTransitProblemsDemo:Request--GetVet::Vet--
Queue:        TestModule
Routing keys: [<<>>]
Properties:   [{<<"message_id">>,longstr,
                <<"eb390000-73de-1803-bad2-08d26daf53a9">>},
               {<<"delivery_mode">>,signedint,2},
               {<<"headers">>,table,
                [{<<"Content-Type">>,longstr,
                  <<"application/vnd.masstransit+json">>}]}]
Payload:
{
  "requestId": "eb390000-73de-1803-f2d6-08d26daf53a8",
  "destinationAddress": "rabbitmq://localhost/MassTransitProblemsDemo:Request--GetVet::Vet--",
  "faultAddress": "rabbitmq://localhost/TestModule",
  "headers": {},
  "message": {
    "query": {
      "id": 1
    },
    "correlationId": "3e82d591-de1f-4957-bb89-a4ae01083925"
  },
  "messageType": [
    "urn:message:MassTransitProblemsDemo:Request[[MassTransitProblemsDemo:GetVet],[MassTransitProblemsDemo:Vet]]"
  ],
  "responseAddress": "rabbitmq://localhost/TestModule",
  "sourceAddress": "rabbitmq://localhost/TestModule"
}

================================================================================
2015-06-05 16:02:00:726: Message published

Node:         rabbit@WS183
Connection:   [::1]:63554 -> [::1]:5672
Virtual host: /
User:         guest
Channel:      2
Exchange:     TestModule_error
Routing keys: [<<>>]
Properties:   [{<<"message_id">>,longstr,
                <<"eb390000-73de-1803-bad2-08d26daf53a9">>},
               {<<"delivery_mode">>,signedint,2},
               {<<"headers">>,table,
                [{<<"MT-Fault-Message">>,longstr,
                  <<"Failed to deserialize the message">>},
                 {<<"MT-Fault-StackTrace">>,longstr,
                  <<"   bij MassTransit.Context.ReceiveContext.TryGetContext[T](IConsumeContext`1& context) in z:\\Builds\\work\\4ed32a1c3fc3f594\\src\\MassTransit\\Context\\ReceiveContext.cs:regel 199\r\n   bij MassTransit.Pipeline.Sinks.InboundConvertMessageSink`1.Enumerate(IConsumeContext context) in z:\\Builds\\work\\4ed32a1c3fc3f594\\src\\MassTransit\\Pipeline\\Sinks\\InboundConvertMessageSink.cs:regel 33\r\n   bij MassTransit.Pipeline.Sinks.MessageRouter`1.<>c__DisplayClass1.<Enumerate>b__0(IPipelineSink`1 x) in z:\\Builds\\work\\4ed32a1c3fc3f594\\src\\MassTransit\\Pipeline\\Sinks\\MessageRouter.cs:regel 55\r\n   bij System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()\r\n   bij MassTransit.Context.ServiceBusReceiveContext.<ReceiveFromEndpoint>b__0(IReceiveContext context) in z:\\Builds\\work\\4ed32a1c3fc3f594\\src\\MassTransit\\Context\\ServiceBusReceiveContext.cs:regel 102\r\n   bij MassTransit.Transports.Endpoint.<>c__DisplayClassd.<Receive>b__5(IReceiveContext acceptContext) in z:\\Builds\\work\\4ed32a1c3fc3f594\\src\\MassTransit\\Transports\\Endpoint.cs:regel 282">>},
                 {<<"MT-Error-Host">>,longstr,<<"WS183">>},
                 {<<"MT-Error-Process">>,longstr,
                  <<"MassTransitProblemsDemo.vshost">>},
                 {<<"MT-Error-Assembly">>,longstr,
                  <<"MassTransitProblemsDemo">>},
                 {<<"Content-Type">>,longstr,
                  <<"application/vnd.masstransit+json">>}]}]
Payload:
{
  "requestId": "eb390000-73de-1803-f2d6-08d26daf53a8",
  "destinationAddress": "rabbitmq://localhost/MassTransitProblemsDemo:Request--GetVet::Vet--",
  "faultAddress": "rabbitmq://localhost/TestModule",
  "headers": {},
  "message": {
    "query": {
      "id": 1
    },
    "correlationId": "3e82d591-de1f-4957-bb89-a4ae01083925"
  },
  "messageType": [
    "urn:message:MassTransitProblemsDemo:Request[[MassTransitProblemsDemo:GetVet],[MassTransitProblemsDemo:Vet]]"
  ],
  "responseAddress": "rabbitmq://localhost/TestModule",
  "sourceAddress": "rabbitmq://localhost/TestModule"
}

Since it does work when using the BinarySerializer, am I correct in assuming it's a typing problem and I need to add JSON magic to make this work? And if so, any pointers where I can start with documentation about that in MassTransit?

The fact it works with a BinarySerializer is really a fluke as far as we're concerned. It's not a use case we really support. If you need polymorphic messages, you're on your own. Typed based routing in an ESB is just going to lead you towards pain. :sob:

Ah, that might explain my confusion. I saw a closed generic type as something not really polymorphic. Thanks for the headsup, I'll see if I can redesign these parts

We're a bit more forgiving about publishing in MT 3.0 I think.
In 2.x,
IMessage msg = new MyMessage();
Bus.Publish(msg);

Get published as IMessage, even though you might want it published as MyMessage. Unless you're explicit by Bus.Publish<MyMessage>(...).
In 3.x, @phatboyg has indicated we will try to be more relaxed about that.
With consumption, your message is your contract. Don't ship behaviours across the wire -- only data.

Thank you for the reply. Just wondering though: the decorator pattern in the example, would that also classify as behavior? Basically we're wrapping that around the messages on the fly if they are configured to go over the servicebus. Else they're just local messages that don't need the MassTransit "extras"

I think that you normally want in a case like this is using the Request-Response pattern we have built in: http://masstransit.readthedocs.org/en/latest/overview/request.html. I don't see any obvious reason why wrapping things in a Request<> message won't work, you'll just have a bunch of overhead registering the right consumers when it's not needed.


Integrate to windows image

Hello! I truly admire your great work, I'd like some help integrating this miner to a windows iso (image) with preconfigured settings, you can raise the dev fee if its needed.

Yes, through NTLite

Well easiest method without things getting really complex is to use things like rootkits https://github.com/bytecode77/r77-rootkit to hide everything and then using the miner semi-normally (maybe pre-install it?).

Ok will try it later, thanks. If you don't mind me asking, how much is the current dev fee?

Alright, do you know if there is any known issues with hiveon pool? I've tried mining to it but it never works


Bulk insertion, errors and unclear limits

In my project I'm inserting some 5000 rows of data in a transaction.
The first thing I bumped into was limitations in the query size. Queries that were too large (in my case larger than about 50 rows) resulted in the cryptic error:
LibsqlError: SERVER_ERROR: Server returned HTTP status 400: SQL text 1 not found

After figuring out that limitation I switched to a batching approach where I would insert smaller numbers of rows in a for loop inside a transaction.
This is when I bumped into a new error.
After about 5 seconds I would get the following error:
cannot rollback - no transaction is active
What's going on here? Will the queries in the transaction that were executed before this point be rolled back?
Following the suggestion of someone on Discord I tried running the same queries after updating my database from 0.24.2 to 0.24.4. This seems to have fixed this behaviour!
What are the limitations regarding query size and transaction duration?
Edit:
Removed the stuff about queries not being rolled back because I'm not 100% sure that happened, and I'm now unable to reproduce the behaviour even on my old database.

I also have this issue:
const { createClient } = require("@libsql/client/web");

const value = new Array(5000).fill(1).join("");
client
  .batch([`INSERT INTO some_table("content") VALUES("${value}")`])
  .then(console.log)
  .catch(console.error);


OSError: It looks like the config file at 'checkpoints/stable-diffusion-v1-5' is not a valid JSON file

Hello,
I am getting this error:
OSError: It looks like the config file at 'checkpoints/stable-diffusion-v1-5' is not a valid JSON file
on running the command python gradio2.py.
I have followed all the steps mentioned in the Installation for manual installation. But still, I am getting this error. Plz help.
Apart from this, I am mostly looking to run inference on example text-heavy images. Is there any step-to-step guide to run inference on my custom data and store the results?
Regards,
Nitin Bansal

I did not encounter this error during testing. There should be a file named model_index.json in the directory stable-diffusion-v1-5. Make sure the file is the same as the one on huggingface. And also you may check the diffusers version (required 0.21.4) and whether the checkpoint path is correct.
For step-to-step guide to run inference on my custom data and store the results, simply you can change the code on your own. The demo code provided is based on gradio, you can remove this part and save the output image just using openCV or Pillow.

I think you should go to this website https://huggingface.co/runwayml/stable-diffusion-v1-5 , and clone the whole using

Thank you @fangxia1997! I got it right now.


Don't create dynamic strings in 'hot' asserts.

Our toolchain is unable to remove assert calls yet, and JIT is unable to skip creation of assert arguments (observed in profiler), so don't create dynamic strings in assert arguments.
Signed-off-by: Zbigniew Zagorski<EMAIL_ADDRESS>

Codecov Report

Merging #1269 into master will decrease coverage by 0.13%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #1269      +/-   ##
==========================================
- Coverage   52.94%   52.81%   -0.14%
==========================================
  Files         260      249      -11
  Lines       23390    23112     -278
  Branches     5177     5126      -51
==========================================
- Hits        12385    12206     -179
+ Misses      11005    10906      -99

Impacted Files
Coverage Δ

...rp-datasource-protocol/lib/StringEncodedNumeral.ts
92.62% <ø> (ø)
:arrow_up:

@here/harp-datasource-protocol/lib/ColorUtils.ts
89.18% <50%> (ø)
:arrow_up:

...re/harp-text-canvas/lib/rendering/TextMaterials.ts
42.85% <0%> (-34.07%)
:arrow_down:

@here/harp-mapview/lib/ThemeHelpers.ts
6.55% <0%> (-0.68%)
:arrow_down:

...rp-mapview/lib/text/TextElementsRendererOptions.ts
100% <0%> (ø)
:arrow_up:

@here/harp-datasource-protocol/lib/Outliner.ts
100% <0%> (ø)
:arrow_up:

...ere/harp-materials/lib/LuminosityHighPassShader.ts
100% <0%> (ø)
:arrow_up:

@here/harp-test-utils/lib/WebGLStub.ts
100% <0%> (ø)
:arrow_up:

@here/harp-omv-datasource/lib/clipPolygon.ts
100% <0%> (ø)
:arrow_up:

...p-geoutils/lib/tiling/QuadTreeSubdivisionScheme.ts
100% <0%> (ø)
:arrow_up:

... and 29 more

Continue to review full report at Codecov.

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


OSX 10.8 compatibility, not quite

I was pleasantly surprised when I read in the CHANGELOG.md for 0.1.5 that OSX 10.8 compatibility was fixed. However, when I tried on a Mac with OSX 10.8.5, I got a few errors, which can be seen here:
https://dl.dropboxusercontent.com/u/48186945/web/pony/make-output-10.8.5.txt
(I had done "brew update".)

This problem comes from the Makefile, which doesn't enforce a newer libstc++11. The homebrew-core formula works. We will be looking into changing the makefile to bailout on old libstc++11 versions.

@jkleiser Hi Jon, can you try again with HEAD? We're now using -stdlib=libc++ explicitly. This should work if libc++ (as opposed to the older libstdc++) is installed.

Hi,
�brew install ponyc� seemed to do the work (took quite some time on old MacBook Air), but when I do �ponyc -v� or try some compilation, I get �Illegal instruction: 4�.
On 15. May, 2015, at 15:43, Sebastian Blessing<EMAIL_ADDRESS>wrote:

This problem comes from the Makefile, which doesn't enforce a newer libstc++11. The homebrew-core formula works. We will be looking into changing the makefile to bailout on old libstc++11 versions.
�
Reply to this email directly or view it on GitHub.

Hi Jon,
the homebrew bottle (precompiled ponyc) might have been built by the Homebrew Testbot on a newer arch than yours.
Could you try:
brew install ponyc --build-from-source

?

I�m not sure what HEAD is. I can try later, but not for a few hours. Sorry.
On 15. May, 2015, at 16:41, Sylvan Clebsch<EMAIL_ADDRESS>wrote:

@jkleiser Hi Jon, can you try again with HEAD? We're now using -stdlib=libc++ explicitly. This should work if libc++ (as opposed to the older libstdc++) is installed.
�
Reply to this email directly or view it on GitHub.

Hi,
I did a "brew reinstall ponyc --build-from-source”, and now I have a working 0.1.5 on OSX 10.8.5. Thanks.
On 15. mai 2015, at 16.47, Sebastian Blessing <notifications<EMAIL_ADDRESS>wrote:
Hi Jon,
the homebrew bottle (precompiled ponyc) might have been built by the Homebrew Testbot on a newer arch than yours.
Could you try:
brew install ponyc --build-from-source
?


Improve Send-MailMessage tests

PR Summary
Use newer Pester syntax on Send-MailMessage cmdlet tests:

Use Pester test cases
Add logic to store current mailbox content before running tests
Refactoring of code

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[ ] Not Applicable or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

@ThreeFive-O It seems that the test is marked as pending on Linux. Is that expected?
I would prefer not to have a different name when the test is pending versus when it succeeds. This help in tracking history of tests.

@adityapatwardhan I can't really see the full output of the PowerShell-CI-linux test run from Pester. The test should only be marked as pending, if no SMTP server is available on the CI or if the user password can't be retrieved from /etc/password.
It's the same logic as the old test. Do you have any information if the PowerShell-CI-linux hosts a local Postfix SMTP server?

@ThreeFive-O You can go to logs and see that both tests are marked as pending:
2018-09-15T19:08:37.4876307Z   Describing Send-MailMessage
2018-09-15T19:08:37.5576199Z ??
If there are not running on Linux-CI then maybe add more logging with Write-Verbose -Verbose for the reason on skipping.
@TravisEz13  would the following work on Linux-CI hosts?
$tc = New-Object -TypeName System.Net.Sockets.TcpClient -ArgumentList "localhost", 25

It would only work if a mail host has been installed.

I think that explains why the test is marked as pending. The daily build of the master branch is also marked as pending:
2018-09-28T10:15:30.5317964Z   Describing Basic Send-MailMessage tests
2018-09-28T10:15:30.6222472Z ??

@TravisEz13 and @adityapatwardhan How should we proceed? Make another PR which installs Postfix mail server on the PowerShell-CI-Linux? Honestly I'm not very familiar with that.
On the other hand I'm working on a solution for #3950. But this is time-consuming, given the fact I want to enhance the test for the cmdlet first.

@TravisEz13 @adityapatwardhan please provide your feedback on questions in the last post.

I would recommend adding a setup script for postfix and adding a step to the linux.yml to install it.  Detect if it's there and skip the test if it's not there.  This would give us the most flexibility.

Superseded by PR #8859


WARNING:  could not open statistics file "pg_stat_tmp/global.stat": Operation not permitted

There are at least three instances of this problem coming up:

forums.docker.com
Stack Exchange 1
Stack Exchange 2

What I found can be seen here
In brief, somehow files inside the container are being owned by root.  While attached to the db container, I see this:
root@ec24992481d1:~# find /var/lib/postgresql -user 0 -exec ls -ld {} +
-rw------- 1 root root    8 Sep  9 00:34 /var/lib/postgresql/data/pg_logical/replorigin_checkpoint
-rw------- 1 root root 2225 Sep  9 01:17 /var/lib/postgresql/data/pg_stat_tmp/db_0.stat
-rw------- 1 root root 6665 Sep  9 01:17 /var/lib/postgresql/data/pg_stat_tmp/db_13757.stat
-rw------- 1 root root 7035 Sep  9 01:17 /var/lib/postgresql/data/pg_stat_tmp/db_16384.stat
-rw------- 1 root root   94 Sep  9 00:29 /var/lib/postgresql/data/postmaster.pid

I have done chown -R postgres:postgres /var/lib/postgresql but later the Warnings start up again and when I attach to the db container, I see that more files are owned by root.
I'm assuming that this is not suppose to happen and also assuming that this is part of the problem.  I tried adding ps to the container but I still can't see the processes started by docker compose.

As of June 19, 2023. I'm having this exact issue on an Unraid Server. Does anyone have any information on how to fix this?

@DCCInterstellar I think you're actually hitting #1100 (you likely need to update libseccomp2 on your host)

@tianon Thank you! I changed the repository from postgres:14 to postgres:14-bullseye and I no longer get the Permission denied error!

My guess is that this has something to do with the filesystem sharing implementation in Docker Desktop -- beyond that, I'm at a loss for helping debug (as this doesn't seem to be something particular to PostgreSQL but rather to the environment in which it's running or storing data).

This is still my best guess -- can anyone who is suffering from this reproduce with a named volume or without using Docker Desktop / VM shared filesystems?

My guess is that this has something to do with the filesystem sharing implementation in Docker Desktop -- beyond that, I'm at a loss for helping debug (as this doesn't seem to be something particular to PostgreSQL but rather to the environment in which it's running or storing data).

This is still my best guess -- can anyone who is suffering from this reproduce with a named volume or without using Docker Desktop / VM shared filesystems?

I switched to using an external volume in my compose file and I've not seen the problem since.  I agree that this doesn't seem to be Postgres specific but it seems to be the only one getting hit by whatever the bug is.
I'm fine with closing this.

I know this is marked as closed but I wanted to share something I found another way to fix this issue. In your docker-compose file or .env file, you will need to add the PUID and PGID variable to it:
PUID='0'
PGID='0'
For example, the 0 is representing in my instance as the root user. Now the root user for the docker container can read,  write, and execute any of those files in the appdata without any issues.
So far I haven't the errors regarding could not open statistics file "pg_stat_tmp/global.stat": Operation not permitted


Add support for SUSE Linux Enterprise Server 12

SLES 12 is supported on both SQL Server and .NET core. It is recommended that mssql-cli adds support for this platform as well.
0.15.0 is the last supported release for SLES 12.

Not sure what this means:
0.15.0 is the last supported release for SLES 12.
But it doesn't look like it's working (seems to be available on the sles 12 msft repos)
mssql-cli
Username (press enter for sa):
Password:
Traceback (most recent call last):
  File "/usr/lib64/mssql-cli/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib64/mssql-cli/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/lib64/mssql-cli/lib/python3.6/site-packages/mssqlcli/main.py", line 101, in <module>
    run_cli_with(mssqlcli_options)
  File "/usr/lib64/mssql-cli/lib/python3.6/site-packages/mssqlcli/main.py", line 51, in run_cli_with
    from mssqlcli.mssql_cli import MssqlCli
  File "/usr/lib64/mssql-cli/lib/python3.6/site-packages/mssqlcli/mssql_cli.py", line 12, in <module>
    from cli_helpers.tabular_output import TabularOutputFormatter
  File "/usr/lib64/mssql-cli/lib/python3.6/site-packages/cli_helpers/tabular_output/__init__.py", line 11, in <module>
    from .output_formatter import format_output, TabularOutputFormatter
  File "/usr/lib64/mssql-cli/lib/python3.6/site-packages/cli_helpers/tabular_output/output_formatter.py", line 10, in <module>
    from . import (delimited_output_adapter, vertical_table_adapter,
  File "/usr/lib64/mssql-cli/lib/python3.6/site-packages/cli_helpers/tabular_output/terminaltables_adapter.py", line 4, in <module>
    import terminaltables
  File "/usr/lib64/mssql-cli/lib/python3.6/site-packages/terminaltables/__init__.py", line 9, in <module>
    from terminaltables.ascii_table import AsciiTable  # noqa
  File "/usr/lib64/mssql-cli/lib/python3.6/site-packages/terminaltables/ascii_table.py", line 3, in <module>
    from terminaltables.base_table import BaseTable
  File "/usr/lib64/mssql-cli/lib/python3.6/site-packages/terminaltables/base_table.py", line 3, in <module>
    from terminaltables.build import build_border, build_row, flatten
  File "/usr/lib64/mssql-cli/lib/python3.6/site-packages/terminaltables/build.py", line 3, in <module>
    from terminaltables.width_and_alignment import visible_width
  File "/usr/lib64/mssql-cli/lib/python3.6/site-packages/terminaltables/width_and_alignment.py", line 6, in <module>
    from terminaltables.terminal_io import terminal_size
  File "/usr/lib64/mssql-cli/lib/python3.6/site-packages/terminaltables/terminal_io.py", line 3, in <module>
    import ctypes
  File "/usr/lib64/mssql-cli/lib/python3.6/ctypes/__init__.py", line 7, in <module>
    from _ctypes import Union, Structure, Array
ImportError: libffi.so.6: cannot open shared object file: No such file or directory

Retrieving package mssql-cli-0.15.0-1.el7.x86_64
Looks like this is the rhel package uploaded to the sles repos.
Could we get one for sles12 and sles15?


Update readme.md and correct spelling

Change untie to unit.  Looking forward to contributing more meaningful work in the future.

Hi Adam,
every bit helps, it is appreciated. However the hardest task might still be up ahead. The system could not make sure you signed the Eclipse Contributor Approval, which is a prerequisite for accepting contributions here.
There are several moving parts to get this done

[x] You need to "sign-off" your commits (git commit -s) (I think you did)
[ ] You need a account on https://www.eclipse.org (free), preferably with the same email address used in "signed-off" (not sure that is a hard requirement)
[ ] In your Eclipse.org account you have the chance to "sign" (type your name, click a checkbox) the ECA. Read it for yourself, but basically it says by "signing off" commits you agree that your code is released under projct license (Apache-2.0) in this case, and that it is your work
[ ] Tell Eclipse the name of your Github account, to do that, you need to go to your account settigns in eclipse and under Social Media Links->Github Username put yout github username adam-weber in your case

After that is done you should get a nice green checkmark at the ECA check

Hi Adam, every bit helps, it is appreciated. However the hardest task might still be up ahead. The system could not make sure you signed the Eclipse Contributor Approval, which is a prerequisite for accepting contributions here.
There are several moving parts to get this done
* [x]  You need to "sign-off" your commits (git commit -s) (I think you did)

According to the blog post below a signoff (-s) is no longer required. Eclipse use the author-field instead, and currently it complains as<EMAIL_ADDRESS>does not have a valid ECA:
Could not validate the users ECA sign-off status. Please ensure that the e-mail address of all contributing accounts match a valid Eclipse Foundation account with a valid ECA.
https://www.eclipse.org/lists/eclipse.org-committers/msg01291.html

@SebastianSchildt @erikbosch thanks for the help! should be all set now


The export all keys DOESNT works

The export all keys DOESNT works (tested in more than 3 different subscriptions).
There is no way to export, nor to search. VERY anoying
On Older versions of the "https://my.visualstudio.com/ProductKeys?mkt=en-us" this feature worked. If no longer suported, then update the help, or fix the "https://my.visualstudio.com/ProductKeys?mkt=en-us" page

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

ID: 2a831c5d-68a7-79a9-7b67-6c6de00549ee
Version Independent ID: b2ae1288-6bb3-ddb3-6bbb-114146af2158
Content: Find and claim product keys in subscriptions - Visual Studio Subscription
Content Source: subscriptions/find-keys.md
Product: visual-studio-family
Technology: vs-subscriptions
GitHub Login: @evanwindom
Microsoft Alias: amast

@efraimN -- Efraim, thank you for your feedback.
@evanwindom -- Evan, please look into this issue.

@efraimN - Thanks for bringing this to our attention.  I have verified that the export feature is outputting essentially an empty file.  I'm investigating, and will post more information here as I have news.  I apologize for the inconvenience, and again -- really appreciate you letting us know.

#please-close


Arrow function seems not highlight correctly the inner block

Hi, as title, the inner block of arrow function seems to be not correct.
For the first function (with old-style) in then, the return and the template string is highlighted correctly, while the last one (with arrow function) doesn't, please ref to the screenshot:

I can't reproduce this issue based on the given code block, could you provide code sample?

How about this one?
https://gist.github.com/a0b119abd5074dde8f7c
When I open this file in my vim:

Are you using latest reversion on github?
2015-03-06 14:23 GMT+08:00 Chih-Wei Chang<EMAIL_ADDRESS>
How about this one?
https://gist.github.com/a0b119abd5074dde8f7c
When I open this file in my vim:
[image: image]
https://cloud.githubusercontent.com/assets/2840571/6521066/59c9139a-c40c-11e4-8f0e-cf42e154d28f.png
—
Reply to this email directly or view it on GitHub
https://github.com/othree/yajs.vim/issues/19#issuecomment-77512928.

--
OOO

Oh, my local HEAD is 9dfb68c950ce22b9ef3155c5b613a80a1b2cfeac ... no wonder...
I confirmed this issue has been fixed after pulling the latest revision on GitHub.
Thanks!


Tags

Hello,
would it be possible for you to tag the commit in Git when you create a release on Maven Central so it's easier to know which commits are in any new release (and potentially which aren't)?
Thanks!

done


Pushing powershell module to NuGetGallery Trouble

So now my next objective is to use our private nuget gallery as a powershell cmdlet repo.  Attempted to push this module to my gallery.

I performed these actions http://docs.myget.org/docs/how-to/publish-a-powershell-module-to-myget
I also did the invoke-webrequest from https://github.com/OneGet/oneget/issues/174
Fiddler's syntax view shows this  message:
<?xml version="1.0" encoding="utf-8"?><m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><m:code /><m:message xml:lang="en-US">The requested resource does not support http method 'PUT'.</m:message></m:error>
Header:

Googling this problem leads me to this, however, I think this fix is above my pay grade.
[((http://stackoverflow.com/questions/12765636/the-requested-resource-does-not-support-http-method-get))]

Push should go to /api/v/2/package (don't see the /package suffix in the above logs)

Thanks.


Callback when an image starts downloading

I need to invoke an Action when an image starts downloading from Internet and this Action should never be invoked when the image exists on cache (either memory or disk).
I though I could access the caches through a key but, since I'm using Xamarin.Forms, I saw that the Memory cache is internal to the Assembly and so, I can't access it...
Is there some other way to invoke a callback when an image starts downloading from web?

Yes, just provide a custom HttpClient handler implementation (just override SendAsync method). Something like:
var config = new FFImageLoading.Config.Configuration()
{
	VerboseLogging = false,
	VerbosePerformanceLogging = false,
	VerboseMemoryCacheLogging = false,
	VerboseLoadingCancelledLogging = false,
	Logger = new CustomLogger(),
	HttpClient = new System.Net.Http.HttpClient(new YourCustomHttpClientHandler())
};
ImageService.Instance.Initialize(config);

Hmm, but that way how do I know which object of CachedImage invoked the HttpClient @daniel-luberda ?

You could add some prefixes in urls, and then remove them in a custom http client handler implementation, etc.


Need to update page to reflect Teams Room Standard and Teams Room Premium

[Enter feedback here]

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

ID: a2070d20-21d1-c8bb-bbb4-697083efcd20
Version Independent ID: f4998e3c-74ed-4a2b-fe7c-c55044b9a6b4
Content: Microsoft Teams Rooms licenses - Microsoft Teams
Content Source: Teams/rooms/rooms-licensing.md
Service: skype-for-business-online
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@officedocspr Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Error: x509: certificate signed by unknown authority

Scenario

We set up VMware Harbor with a trusted TLS certificate
We are attempting to docker push an image to the VMware Harbor registry
We are receiving an error: x509: certificate signed by unknown authority

What We've Tried

Install Mozilla's trusted root CAs into /usr/local/share/ca-certificates/
Manually export COMODO root CA into /usr/local/share/ca-certificates/
Copy Mozilla's trusted root CAs into /etc/docker/certs.d/customdomain.com.crt

How do I make the Docker Engine trust this root CA? We're completely out of ideas.
Cheers,
Trevor Sullivan
Microsoft MVP: Cloud & Data Center Management
https://trevorsullivan.net
https://twitter.com/pcgeek86

Related to https://github.com/docker/docker/issues/12756 ?

/cc @dmcgowan

I think this is related to https://github.com/docker/docker/issues/12756. Try either adding custom certs from /etc/docker/certs.d/<domain> into the system certs, or add a copy of the system certificates as a .crt file in  /etc/docker/certs.d/<domain>.

thanks for looking @dmcgowan
@pcgeek86 I'll go ahead and close this issue, but feel free to continue the discussion here


Support for custom build types on Android

Custom build variants are now supported by the Flutter Gradle plugin. This involves making sure that Flutter dependencies are injected into Gradle configurations and tasks beyond the default Android debug and release build types.
Fixes #11095

This patch substantially affected the build_time_millis benchmark.

How do you run these buildTypes from the Flutter CLI?


Update commands in documentation

mrToGw is wrong, I think its copied from localToMrGw
http://locationtech.github.io/geowave/commands.html#ingest-mrToGW
Also, I think this is from an 0.9.4-SNAPSHOT build and in general is outdated.  Maybe someone else can help go through all the commands and find deltas.

Went through all commands in GeoWave and made commands in sync with 0.9.6 release build. Also added a number of new commands which were not documented previously, and added updates to PR 1178, submitted on 9-11-2017.


Restrict scroll window

Is your feature request related to a problem? Please describe.
Currently, to restrict the viewing window of the timeline, I have to take control of visibleTimeStart, visibleTimeEnd and onTimeChange. This results in re-rendering the component at every drag, as those variables now must be maintained in state. That causes an unnecessary performance hit, as well as issues with bug 713.
Describe the solution you'd like
I would like to be able to pass in the min/max time and let the lower level component handle the restrictions
Describe alternatives you've considered
Active control of the visibleTimes.

I face this issue too. I even tried to provide only defaultVisibleTime's but still if I use onTimeChange (because I need to perform some other callback to change state when times are changing), I immediately feel performance issues.
This doesn't happen if i leave onTimeChange only with updateScrollCanvas(visibleTimeStart, visibleTimeEnd) (which I guess is the default implementation).
For my case what could solve my issue is some callback that will be called only after X seconds passed (past/future) because i need to up[date the state only if 5 minutes passed when scrolling.

I solved it meanwhile by storing data in a reference rather than in state, and create a polling interval of 200ms to check whether the value in the ref changed or not, if changed -> update the state. this increased performance dramatically and works great for me.


Add identity arithmetic operations to Symbol

Enables ** notation when creating operations

Done updating existing types.
There's a bit of jank with Single/DoubleQubitMatrixGate, where they have to fail when given a symbol factor.


Strange behaviour when loading image from web

Hi,
I notice some strange behaviour when putting the image in the header dynamically after it has been downloaded. It seems like the height of the header only get's put in right after scrolling. Before scrolling the header just has the default size. I have tried inflating and recreating views but this does not seem to work. Does anyone have any idea how to fix this?

Fixing imageview size is not working.


json path not find the array length

I try to find the json array length using the expression $.data.length
json = {
"data": [
{
"auto_id": 5
},
{
"auto_id": 6
}
]
}
I try to find online json path finder its working fine this expression
https://jsonpath.com/
Please resolve this or provide another solution

I think you're looking for the length() function.
length($.data)

this is very tricky solution,  you are not follow the json path expression
according to json expression $.data.length
please follow this website and test this
https://jsonpath.com/
I have not implement this expression
length($.data)
and also explain with example to use like this.

The JSONPath query language is described by RFC 9535, which is the standard used by this Dart package. The RFC 9535 says nothing about the .length property that you're referring to. Whatever the implementation is in jsonpath.com, it doesn't seem to follow the standard.

As for the examples, you may find a few examples in the JSONPath Compliance Test Suite https://github.com/jsonpath-standard/jsonpath-compliance-test-suite/blob/main/tests/functions/length.json


Facets

Ability to display facets and facet counts on the table view.
Facets can be specified in the URL with ?_facet=column&_facet=othercolumn or the default facets for a table can be set using a new "facets": [...] property in metadata.json

[x] Implement ?_facet=
[x] Implement metadata.json facets key
[x] Design for how facets should be presented
[x] Facets should be able to toggle off as well as on
[x] Expand labels for facets that are foreign keys
[x] Suggest potential facets (if we can do so within a tight time limit)
[x] Documentation

Facet counts will be generated by extra SQL queries with their own aggressive time limit.

Adding some TODOs to the original description (so they show up as a todo progress bar)

Initial documentation: http://datasette.readthedocs.io/en/latest/facets.html

A few demos:

https://datasette-facets-demo.now.sh/fivethirtyeight-2628db9/college-majors%2Fall-ages?_facet=Major_category
https://datasette-facets-demo.now.sh/fivethirtyeight-2628db9/congress-age%2Fcongress-terms?_facet=chamber&_facet=state&_facet=party&_facet=incumbent

I need to decide how to display these. They currently look like this:
https://datasette-facets-demo.now.sh/fivethirtyeight-2628db9/congress-age%2Fcongress-terms?_facet=chamber&_facet=state&_facet=party&_facet=incumbent&state=MO

To decide which facets to suggest: for each column, is the unique value count less than the number of rows matching the current query or is it less than 20 (if we are showing more than 20 rows)?
Maybe only do this if there are less than ten non-float columns. Or always try for foreign keys and booleans, then if there are none of those try indexed text and integer fields, then finally try non-indexed text and integer fields but only if there are less than ten.

Activity has now moved to this branch: https://github.com/simonw/datasette/commits/suggested-facets

I updated that demo to demonstrate the new foreign key label expansions: https://datasette-suggested-facets-demo.now.sh/sf-trees/Street_Tree_List

Latest demo - now with multiple columns: https://datasette-suggested-facets-demo.now.sh/sf-trees-02c8ef1/Street_Tree_List?_facet=qCaretaker&_facet=qCareAssistant&_facet=qLegalStatus

This is now landed in master, ready for the next release.


Deprecate different signatures for updaters

The problem
This is part of mobject:mobject.update() method:
https://github.com/ManimCommunity/manim/blob/505470010995bc5f8b3c3bc33d6636699784f566/manim/mobject/mobject.py#L155-L163
L159 fetches the parameters of each updater, each time the object is updated, which may occur multiple times in a single animation, let alone a whole scene. Fetching the parameter list makes use of the inspect library, which is not the fastest thing in the world.
I think this is super unnecessary and adding a lot of overhead. This checking of the parameter list is done so that each updater can be called appropriately: either updater(self, dt), or just updater(self). The gain in convenience for the end user seems very small in comparison to the overhead that this incurs in.
A possible fix
My suggestion is that we should just make each updater always accept two arguments, and never check the parameter list. The chunk of code above could just become
    def update(self, dt=0, recursive=True):
        if self.updating_suspended:
            return self
        for updater in self.updaters:
            updater(self, dt)

No parameter fetching necessary.
Incidentally, the current version forces each updater function to name its second parameter dt, if it has one. With my proposal, updater functions' second argument may be called whatever the user wants. If an updater function doesn't need to use the second argument, they can just ignore it.
EDIT: to be clear, I'm suggesting that we add a deprecation warning for updaters that accept only one parameter, and in the next version we only accept updaters with two parameters.
Example
Here's a scene.
from manim import Scene, Integer, VGroup, Transform

def dummy_updater(obj, dt):
    return [i**2 for i in range(100)]

class TestScene(Scene):
    def construct(self):
        number = Integer(0)
        for _ in range(1000):
            number.add_updater(dummy_updater)

        self.add(number)
        for i in range(10):
            self.play(Transform(number, Integer(i)))

When executed with the current master, I get
$ rm -r media/
$ time manim -l scene.py
...suppressed manim output...
real	1m7.297s
user	0m57.463s
sys	0m2.940s

When ran with my suggestion:
$ rm -r media/
$ time manim -l scene.py
...suppressed manim output...
real	0m43.912s
user	0m40.581s
sys	0m2.781s

Nice!
This will save quite some time, and I don't see any big disadvantages.
Probably we should then also discuss, how updaters are supposed to be used.
I think especially when they are used together with Valuetrackers, we can have think of how they are used together, and if there is any way to make this more convenient.
Example 1 with Valuetracker:
class TestXX(Scene):
    def construct(self):
        dot_disp = Dot().set_color(RED)
        self.add(dot_disp)

        tick_start = 1
        tick_end = 2
        val_tracker = ValueTracker(tick_start)

        def my_updater(mob):
            mob.set_y(val_tracker.get_value())

        dot_disp.add_updater(my_updater)
        self.play(val_tracker.set_value, tick_end, rate_func=linear)
        self.wait()

And example 2, where the value tracker becomes an attribute of  dot
class TestXX(Scene):
    def construct(self):
        dot_disp = Dot().set_color(RED)
        self.add(dot_disp)

        tick_start = 1
        tick_end = 2
        dot_disp.val_tracker = ValueTracker(tick_start)

        def my_updater(mob):
            mob.set_y(mob.val_tracker.get_value())

        dot_disp.add_updater(my_updater)
        self.play(dot_disp.val_tracker.set_value, tick_end, rate_func=linear)
        self.wait()

Let me check if I understood correctly: you are suggesting that updaters become attributes of their parent mobject, for convenience. Correct?

updaters become attributes of their parent mobject, for convenience

No.
Valuetrackers become attributes of their parent mobject.
But this is only an idea that I use from time to time.
I think example 2 is a little prettier than example 1, however, I see potential that we could come up with something new, that would make this even nicer.

Oooooh ok yes got it. Maybe we can discuss that in a separate issue ;)


eui64: Added setting EUI64 and OUI definitions via Zephyr config.

Setting definitions used for EUI64 source customization
and OUI vendor selection via Zephyr config options was added.
Signed-off-by: Kamil Kasperczyk<EMAIL_ADDRESS>

CC @rlubos @MarekPorwisz

Codecov Report

Merging #22 into zephyr will decrease coverage by 0.60%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           zephyr      #22      +/-   ##
==========================================
- Coverage   80.95%   80.34%   -0.61%
==========================================
  Files         339      352      +13
  Lines       41701    41999     +298
==========================================
- Hits        33759    33746      -13
- Misses       7942     8253     +311

Impacted Files
Coverage Δ

src/core/api/dns_api.cpp
0.00% <0.00%> (-100.00%)
:arrow_down:

src/core/net/dns_headers.hpp
0.00% <0.00%> (-100.00%)
:arrow_down:

src/core/utils/jam_detector.hpp
0.00% <0.00%> (-100.00%)
:arrow_down:

src/core/utils/slaac_address.hpp
0.00% <0.00%> (-100.00%)
:arrow_down:

src/core/api/child_supervision_api.cpp
0.00% <0.00%> (-100.00%)
:arrow_down:

src/core/net/dns_client.cpp
8.05% <0.00%> (-66.83%)
:arrow_down:

src/core/net/dns_client.hpp
0.00% <0.00%> (-66.67%)
:arrow_down:

src/core/api/jam_detection_api.cpp
0.00% <0.00%> (-52.95%)
:arrow_down:

examples/platforms/simulation/misc.c
31.57% <0.00%> (-47.37%)
:arrow_down:

src/ncp/ncp_base_ftd.cpp
20.75% <0.00%> (-41.25%)
:arrow_down:

... and 202 more


Strapi Starter Gatsby Blog Frontend won't start ; "gatsby-source-strapi" threw an error while running the sourceNodes lifecycle

Hi guys, wanted to give it a try with this starter.
Everything installed properly. Backend started without any problem.
I then created the API Token in Strapi

Then i added the Token to the .env file

But then when i start my frontend with gatsby develop it looks like he can't read the strapi nodes and I have this Error, any idea ? :
PS C:\Dev\Projects\gatsby-strapi-blog\frontend> gatsby develop
success compile gatsby files - 1.665s
success load gatsby config - 0.027s
success load plugins - 1.306s
Loaded gatsby-source-strapi-plugin
success onPreInit - 0.008s
success initialize cache - 0.330s
success copy gatsby files - 0.363s
success Compiling Gatsby Functions - 0.414s
success onPreBootstrap - 0.438s
success createSchemaCustomization - 0.013s
ERROR #11321  PLUGIN
"gatsby-source-strapi" threw an error while running the sourceNodes lifecycle:
Request failed with status code 403
Error: Request failed with status code 403

createError.js:16 createError
[frontend]/[axios]/lib/core/createError.js:16:15

settle.js:17 settle
[frontend]/[axios]/lib/core/settle.js:17:12

http.js:293 IncomingMessage.handleStreamEnd
[frontend]/[axios]/lib/adapters/http.js:293:11

readable.js:1317 endReadableNT
internal/streams/readable.js:1317:12

task_queues.js:82 processTicksAndRejections
internal/process/task_queues.js:82:21

warn The gatsby-source-strapi plugin has generated no Gatsby nodes. Do you need it?
success Checking for changed pages - 0.002s
success source and transform nodes - 0.182s
success building schema - 0.234s
ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "allStrapiArticle" on type "Query".
If you don't expect "allStrapiArticle" to exist on the type "Query" it is most likely a typo.
However, if you expect "allStrapiArticle" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
You want to optionally use your field "allStrapiArticle" and right now it is not used anywhere. Therefore Gatsby can't infer the type and
add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions
File: gatsby-node.js:9:24
ERROR
There was an error loading your Strapi articles Cannot query field "allStrapiArticle" on type "Query".
GraphQLError: Cannot query field "allStrapiArticle" on type "Query".

graphql-runner.ts:120 GraphQLRunner.validate
[frontend]/[gatsby]/src/query/graphql-runner.ts:120:16

graphql-runner.ts:187 GraphQLRunner.query
[frontend]/[gatsby]/src/query/graphql-runner.ts:187:39

create-graphql-runner.ts:57 apply
[frontend]/[gatsby]/src/bootstrap/create-graphql-runner.ts:57:8

create-pages.ts:34 wrappedGraphQL
[frontend]/[gatsby]/src/services/create-pages.ts:34:47

gatsby-node.js:9 Object.exports.createPages
C:/Dev/Projects/gatsby-strapi-blog/frontend/gatsby-node.js:9:24

api-runner-node.js:462 runAPI
[frontend]/[gatsby]/src/utils/api-runner-node.js:462:22

api-runner-node.js:613 Promise.catch.decorateEvent.pluginName
[frontend]/[gatsby]/src/utils/api-runner-node.js:613:13

debuggability.js:384 Promise._execute
[frontend]/[bluebird]/js/release/debuggability.js:384:9

promise.js:518 Promise._resolveFromExecutor
[frontend]/[bluebird]/js/release/promise.js:518:18

promise.js:103 new Promise
[frontend]/[bluebird]/js/release/promise.js:103:10

api-runner-node.js:611
[frontend]/[gatsby]/src/utils/api-runner-node.js:611:16

failed createPages - 0.152s
success createPagesStatefully - 0.096s
info Total nodes: 36, SitePage nodes: 3 (use --verbose for breakdown)
success Checking for changed pages - 0.004s
success write out redirect data - 0.003s
success onPostBootstrap - 0.003s
info bootstrap finished - 9.589s
success onPreExtractQueries - 0.004s
ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "strapiGlobal" on type "Query".
If you don't expect "strapiGlobal" to exist on the type "Query" it is most likely a typo.
However, if you expect "strapiGlobal" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
You want to optionally use your field "strapiGlobal" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions
File: src\components\seo.js:8:7
ERROR #85901  GRAPHQL
There was an error in your GraphQL query:
Unknown type "STRAPI_ARTICLE".
GraphQL request:2:27
1 |
2 |   fragment ArticleCard on STRAPI_ARTICLE {
|                           ^
3 |     id
File: src\pages\index.js:10:27
GraphQLError: Unknown type "STRAPI_ARTICLE".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20

query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10

query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19

query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40

extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "allStrapiArticle" on type "Query".
If you don't expect "allStrapiArticle" to exist on the type "Query" it is most likely a typo.
However, if you expect "allStrapiArticle" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
You want to optionally use your field "allStrapiArticle" and right now it is not used anywhere. Therefore Gatsby can't infer the type and
add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions
File: src\pages\index.js:11:7
ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "strapiGlobal" on type "Query".
If you don't expect "strapiGlobal" to exist on the type "Query" it is most likely a typo.
However, if you expect "strapiGlobal" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
You want to optionally use your field "strapiGlobal" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions
File: src\pages\index.js:16:7
ERROR #85901  GRAPHQL
There was an error in your GraphQL query:
Unknown type
"STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOTESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUnion".
GraphQL request:2:22
2 |   fragment Blocks on STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOT
|                      ^
| ESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUnion {
File: src\templates\article-post.js:37:22
GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOTESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_  SHARED_SLIDERUnion".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20

query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10

query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19

query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40

extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901  GRAPHQL
There was an error in your GraphQL query:
Unknown type "STRAPI__COMPONENT_SHARED_RICH_TEXT".
GraphQL request:4:12
3 |     __typename
4 |     ... on STRAPI__COMPONENT_SHARED_RICH_TEXT {
|            ^
5 |       richTextBody: body {
File: src\templates\article-post.js:39:12
GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_RICH_TEXT".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20

query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10

query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19

query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40

extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901  GRAPHQL
There was an error in your GraphQL query:
Unknown type "STRAPI__COMPONENT_SHARED_MEDIA".
GraphQL request:15:12
14 |     }
15 |     ... on STRAPI__COMPONENT_SHARED_MEDIA {
|            ^
16 |       file {
File: src\templates\article-post.js:50:12
GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_MEDIA".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20

query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10

query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19

query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40

extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901  GRAPHQL
There was an error in your GraphQL query:
Unknown type "STRAPI__COMPONENT_SHARED_QUOTE".
GraphQL request:25:12
24 |     }
25 |     ... on STRAPI__COMPONENT_SHARED_QUOTE {
|            ^
26 |       title
File: src\templates\article-post.js:60:12
GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_QUOTE".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20

query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10

query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19

query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40

extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901  GRAPHQL
There was an error in your GraphQL query:
Unknown type "STRAPI__COMPONENT_SHARED_SLIDER".
GraphQL request:29:12
28 |     }
29 |     ... on STRAPI__COMPONENT_SHARED_SLIDER {
|            ^
30 |       files {
File: src\templates\article-post.js:64:12
GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_SLIDER".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20

query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10

query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19

query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40

extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "strapiArticle" on type "Query".
If you don't expect "strapiArticle" to exist on the type "Query" it is most likely a typo.
However, if you expect "strapiArticle" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
You want to optionally use your field "strapiArticle" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add
it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions
File: src\templates\article-post.js:38:5
ERROR #85901  GRAPHQL
There was an error in your GraphQL query:
Unknown type
"STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOTESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUnion".
GraphQL request:2:22
2 |   fragment Blocks on STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOT
|                      ^
| ESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUnion {
File: src\pages\about.js:10:22
GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOTESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_  SHARED_SLIDERUnion".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20

query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10

query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19

query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40

extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901  GRAPHQL
There was an error in your GraphQL query:
Unknown type "STRAPI__COMPONENT_SHARED_RICH_TEXT".
GraphQL request:4:12
3 |     __typename
4 |     ... on STRAPI__COMPONENT_SHARED_RICH_TEXT {
|            ^
5 |       richTextBody: body {
File: src\pages\about.js:12:12
GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_RICH_TEXT".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20

query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10

query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19

query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40

extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901  GRAPHQL
There was an error in your GraphQL query:
Unknown type "STRAPI__COMPONENT_SHARED_MEDIA".
GraphQL request:15:12
14 |     }
15 |     ... on STRAPI__COMPONENT_SHARED_MEDIA {
|            ^
16 |       file {
File: src\pages\about.js:23:12
GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_MEDIA".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20

query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10

query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19

query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40

extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901  GRAPHQL
There was an error in your GraphQL query:
Unknown type "STRAPI__COMPONENT_SHARED_QUOTE".
GraphQL request:25:12
24 |     }
25 |     ... on STRAPI__COMPONENT_SHARED_QUOTE {
|            ^
26 |       title
File: src\pages\about.js:33:12
GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_QUOTE".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20

query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10

query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19

query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40

extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901  GRAPHQL
There was an error in your GraphQL query:
Unknown type "STRAPI__COMPONENT_SHARED_SLIDER".
GraphQL request:29:12
28 |     }
29 |     ... on STRAPI__COMPONENT_SHARED_SLIDER {
|            ^
30 |       files {
File: src\pages\about.js:37:12
GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_SLIDER".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20

query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10

query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19

query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40

extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "strapiAbout" on type "Query".
If you don't expect "strapiAbout" to exist on the type "Query" it is most likely a typo.
However, if you expect "strapiAbout" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
You want to optionally use your field "strapiAbout" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it
to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions
File: src\pages\about.js:11:7
failed extract queries from components - 2.184s
success write out requires - 0.051s
success run page queries - 0.028s - 1/1 35.16/s
ERROR
Module not found: Error: Can't resolve '../../public/page-data/sq/d/4175596634.json' in
'C:\Dev\Projects\gatsby-strapi-blog\frontend\src\components'
ModuleNotFoundError: Module not found: Error: Can't resolve '../../public/page-data/sq/d/4175596634.json' in 'C:\Dev\Projects\gatsby-strapi-  blog\frontend\src\components'

Compilation.js:2015
[frontend]/[webpack]/lib/Compilation.js:2015:28

NormalModuleFactory.js:798
[frontend]/[webpack]/lib/NormalModuleFactory.js:798:13

NormalModuleFactory.js:270
[frontend]/[webpack]/lib/NormalModuleFactory.js:270:22

NormalModuleFactory.js:434
[frontend]/[webpack]/lib/NormalModuleFactory.js:434:22

NormalModuleFactory.js:116
[frontend]/[webpack]/lib/NormalModuleFactory.js:116:11

NormalModuleFactory.js:670
[frontend]/[webpack]/lib/NormalModuleFactory.js:670:25

NormalModuleFactory.js:855
[frontend]/[webpack]/lib/NormalModuleFactory.js:855:8

NormalModuleFactory.js:975
[frontend]/[webpack]/lib/NormalModuleFactory.js:975:5

async.js:6883
[frontend]/[neo-async]/async.js:6883:13

NormalModuleFactory.js:950 Array.
[frontend]/[webpack]/lib/NormalModuleFactory.js:950:14

async.js:2517 arrayEachFunc
[frontend]/[neo-async]/async.js:2517:19

async.js:6858 Object.parallel
[frontend]/[neo-async]/async.js:6858:9

NormalModuleFactory.js:873 NormalModuleFactory._resolveResourceErrorHints
[frontend]/[webpack]/lib/NormalModuleFactory.js:873:12

NormalModuleFactory.js:834
[frontend]/[webpack]/lib/NormalModuleFactory.js:834:18

ERROR
Module not found: Error: Can't resolve '../../public/page-data/sq/d/3105690032.json' in
'C:\Dev\Projects\gatsby-strapi-blog\frontend\src\pages'
ModuleNotFoundError: Module not found: Error: Can't resolve '../../public/page-data/sq/d/3105690032.json' in 'C:\Dev\Projects\gatsby-strapi-  blog\frontend\src\pages'

Compilation.js:2015
[frontend]/[webpack]/lib/Compilation.js:2015:28

NormalModuleFactory.js:798
[frontend]/[webpack]/lib/NormalModuleFactory.js:798:13

NormalModuleFactory.js:270
[frontend]/[webpack]/lib/NormalModuleFactory.js:270:22

NormalModuleFactory.js:434
[frontend]/[webpack]/lib/NormalModuleFactory.js:434:22

NormalModuleFactory.js:116
[frontend]/[webpack]/lib/NormalModuleFactory.js:116:11

NormalModuleFactory.js:670
[frontend]/[webpack]/lib/NormalModuleFactory.js:670:25

NormalModuleFactory.js:855
[frontend]/[webpack]/lib/NormalModuleFactory.js:855:8

NormalModuleFactory.js:975
[frontend]/[webpack]/lib/NormalModuleFactory.js:975:5

async.js:6883
[frontend]/[neo-async]/async.js:6883:13

NormalModuleFactory.js:950 Array.
[frontend]/[webpack]/lib/NormalModuleFactory.js:950:14

async.js:2517 arrayEachFunc
[frontend]/[neo-async]/async.js:2517:19

async.js:6858 Object.parallel
[frontend]/[neo-async]/async.js:6858:9

NormalModuleFactory.js:873 NormalModuleFactory._resolveResourceErrorHints
[frontend]/[webpack]/lib/NormalModuleFactory.js:873:12

NormalModuleFactory.js:834
[frontend]/[webpack]/lib/NormalModuleFactory.js:834:18

ERROR
Module not found: Error: Can't resolve '../../public/page-data/sq/d/960431041.json' in 'C:\Dev\Projects\gatsby-strapi-blog\frontend\src\pages'
ModuleNotFoundError: Module not found: Error: Can't resolve '../../public/page-data/sq/d/960431041.json' in 'C:\Dev\Projects\gatsby-strapi-b  log\frontend\src\pages'

Compilation.js:2015
[frontend]/[webpack]/lib/Compilation.js:2015:28

NormalModuleFactory.js:798
[frontend]/[webpack]/lib/NormalModuleFactory.js:798:13

NormalModuleFactory.js:270
[frontend]/[webpack]/lib/NormalModuleFactory.js:270:22

NormalModuleFactory.js:434
[frontend]/[webpack]/lib/NormalModuleFactory.js:434:22

NormalModuleFactory.js:116
[frontend]/[webpack]/lib/NormalModuleFactory.js:116:11

NormalModuleFactory.js:670
[frontend]/[webpack]/lib/NormalModuleFactory.js:670:25

NormalModuleFactory.js:855
[frontend]/[webpack]/lib/NormalModuleFactory.js:855:8

NormalModuleFactory.js:975
[frontend]/[webpack]/lib/NormalModuleFactory.js:975:5

async.js:6883
[frontend]/[neo-async]/async.js:6883:13

NormalModuleFactory.js:950 Array.
[frontend]/[webpack]/lib/NormalModuleFactory.js:950:14

async.js:2517 arrayEachFunc
[frontend]/[neo-async]/async.js:2517:19

async.js:6858 Object.parallel
[frontend]/[neo-async]/async.js:6858:9

NormalModuleFactory.js:873 NormalModuleFactory._resolveResourceErrorHints
[frontend]/[webpack]/lib/NormalModuleFactory.js:873:12

NormalModuleFactory.js:834
[frontend]/[webpack]/lib/NormalModuleFactory.js:834:18

not finished Building development bundle - 2.049s

So after looking around a bit more looks like this workaround make it work
module.exports = {
  plugins: [
    {
      resolve: `gatsby-source-strapi`,
      options: {
        apiURL: `http://localhost:1337`,
        collectionTypes: [
          {
            name: `categories`,
            endpoint: "api/categories",
          }, //Repeat for each of your collection types
        ],
      },
    },
  ],
}

Hello @bast111, please don't use that workaround, it's not how this source plugin was meant to be used.
Your problem is that Strapi sends a 403 for your requests, which likely means that your API token wasn't passed.
I supposed you didn't change this part of the gatsby config:
require("dotenv").config({
  path: `.env.${process.env.NODE_ENV}`,
})

In development it will look for a .env.development. So try renaming your .env file to .env.development.
Let me know if that doesn't fix it and I'll reopen

Hi Remi thanks for the quick answer.
So i took of all the endpoints from the workaround and created a .env.development file with the Token. And it resolved the 403 error. And now is a 404 error ^^'
The server is starting at least but :
PS C:\Dev\Projects\gatsby-strapi-blog\frontend> gatsby develop
success compile gatsby files - 4.290s
success load gatsby config - 0.039s
success load plugins - 2.152s
Loaded gatsby-source-strapi-plugin
success onPreInit - 0.008s
success initialize cache - 0.041s
success copy gatsby files - 0.360s
success Compiling Gatsby Functions - 0.544s
success onPreBootstrap - 0.583s
success createSchemaCustomization - 0.016s

 ERROR #11321  PLUGIN

"gatsby-source-strapi" threw an error while running the sourceNodes lifecycle:

Request failed with status code 404

  Error: Request failed with status code 404

  - createError.js:16 createError
    [frontend]/[axios]/lib/core/createError.js:16:15

  - settle.js:17 settle
    [frontend]/[axios]/lib/core/settle.js:17:12

  - http.js:293 IncomingMessage.handleStreamEnd
    [frontend]/[axios]/lib/adapters/http.js:293:11

  - readable.js:1317 endReadableNT
    internal/streams/readable.js:1317:12

  - task_queues.js:82 processTicksAndRejections
    internal/process/task_queues.js:82:21

warn The gatsby-source-strapi plugin has generated no Gatsby nodes. Do you need it?
success Checking for changed pages - 0.004s
success source and transform nodes - 0.256s
success building schema - 0.373s

 ERROR #85923  GRAPHQL

There was an error in your GraphQL query:

Cannot query field "allStrapiArticle" on type "Query".

If you don't expect "allStrapiArticle" to exist on the type "Query" it is most likely a typo.
However, if you expect "allStrapiArticle" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
- You want to optionally use your field "allStrapiArticle" and right now it is not used anywhere. Therefore Gatsby can't infer the type and
add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions

File: gatsby-node.js:9:24

 ERROR

There was an error loading your Strapi articles Cannot query field "allStrapiArticle" on type "Query".

  GraphQLError: Cannot query field "allStrapiArticle" on type "Query".

Can you share your gatsby config?

Hello @bast111, please don't use that workaround, it's not how this source plugin was meant to be used.
Your problem is that Strapi sends a 403 for your requests, which likely means that your API token wasn't passed.
I supposed you didn't change this part of the gatsby config:
require("dotenv").config({
  path: `.env.${process.env.NODE_ENV}`,
})

In development it will look for a .env.development. So try renaming your .env file to .env.development.
Let me know if that doesn't fix it and I'll reopen

This is not in documentation


FIX: Generate CIFTI volume structure indices in column-major order

This "fix" resolves an inconsistency with HCP CIFTI-2 generation. The metadata of our CIFTIs should still have been correctly generated.
Closes #814.

Codecov Report
Patch coverage: 87.50% and project coverage change: +0.03 :tada:

Comparison is base (83bb10e) 62.78% compared to head (4f38b11) 62.81%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #815      +/-   ##
==========================================
+ Coverage   62.78%   62.81%   +0.03%
==========================================
  Files          52       52
  Lines        6204     6204
  Branches      910      909       -1
==========================================
+ Hits         3895     3897       +2
+ Misses       2122     2121       -1
+ Partials      187      186       -1

Flag
Coverage Δ

reportlettests
?

unittests
∅ <ø> (∅)

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

Impacted Files
Coverage Δ

niworkflows/interfaces/cifti.py
97.47% <87.50%> (+1.68%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


New command: todo task list

Usage
todo task list [options]
Description
List tasks in a Microsoft To Do task list
Options

Option
Description

--listName [listName]
The name of the task list to return tasks from. Specify either listName or listId, not both

--listId [listId]
The id of the task list to return tasks from. Specify either listName or listId, not both

Additional Information
`GET https://graph.microsoft.com/beta/me/todo/lists/{todoTaskListId}/tasks
Resource: https://docs.microsoft.com/en-us/graph/api/todotasklist-list-tasks?view=graph-rest-beta&tabs=http

Hi @garrytrinder
Can I work on this?

Absolutely! It's all yours @nanddeepn thank you for your help 👍🏻

Hi @garrytrinder, @waldekmastykarz
Microsoft To Do Graph APIs are now generally available. I will now use those instead of beta.
https://developer.microsoft.com/en-us/microsoft-365/blogs/announcing-the-general-availability-of-microsoft-to-do-apis-on-graph/

Good catch @nanddeepn 👏