Nunjucks or mustache templates?

Is there a way to use Nunjucks or Mustache for templates instead of Hyperscript? It may be much easier than trying to get rid of the warnings about arrays being flattened. Thanks

if your main issue is the warnings, you can silence them as shown in the docs [1], they're just performance suggestions and will not cause any app errors (or even impact perf that significantly).
as for whether you can use Nunjucks or Mustache, you would have to provide a compiler layer that would translate them into hyperscript. this would be possible if your mustache or nunjucks parser exposes the AST and/or API to do this translation. you can also take a look at a simple JSX adapter in https://github.com/leeoniya/domvm/issues/179
generally, domvm's hyperscript api provides a richer featureset than can be exposed in more restricted templating languages.
[1] https://github.com/leeoniya/domvm#devmode

Thanks @leeoniya, I will try out one of the micro builds then. About it's usage, I just replace the instances of arrays with el() declarations?

i think the example given is pretty clear. you can provide children as additional arguments without having to wrap them in an array,


Added ArrayPointer pattern

Added an ArrayPointer pattern. This is a lighter-weight alternative to the FFISlice pattern which allows expression of a pointer to an array of a type. This allows backends to generate more relevant bindings. Crucially, it forces the C# backend to declare the parameter as an IntPtr rather than a ref T (which makes little sense for an array of values).

On mobile right now, but quick cpomment: the api looks unsound as you can pass in len that mismatches the ffi array. At very least that method would have to be unsafe.

Alright, I just had another look, some more comments in random order

ArrayPointer should probably be #[repr(transparent)] if it only wraps a single pointer
as_slice is definitely unsound, as you can easily pass in u64::MAX and have instant UB
If I understand you correctly the main reason you'd want ArrayPointer is so C# can generate another pointer type. As ArrayPointer probably can't be made "safe and sound" (it'd have to be unsafe as on its own it can't guarantee correctness of the resulting slice), so I'm wondering if it would rather make sense to somehow hint to the C# backend that it should generate bindings differently for a raw pointer type, instead of adding a type pattern that only seems to be useful in C# (I'm not aware of any other language FFI system that'd make any such distinction as C#). Haven't thought this last point through though.

I won't argue that it's not unsafe, however, it's exactly equivalent to using the current FFISlice type, but just by passing the length as a parameter value rather than as a struct member:

I'd say there is a small difference :

You are correct that the general premise is that "people call in correctly". So we assume, say, FFISlice contains a valid (pointer, len), and in Rust we safely convert that to a slice.
The unsoundness in ArrayPointer however can be caused "purely in Rust". The problem is that even if people call in correctly (i.e., we already have a valid ArrayPointer type) you can still trigger UB in Rust by passing in the wrong value when invoking as_slice().

There's a bit more written in the FAQ.

I just copied the implementation from here, so surely this would also need to be marked unsafe?

See above. I admit there is a bit of a 'philosophical' argument around soundness boundaries across FFI (e.g., one could make the argument that any incoming FFI call should always be treated as maximally unsound, but then you'd also have to consider RwLocking things, doing pointer alignment checks, and more), but IIRC the consensus was that "expecting people to call in properly" is ok.
In that model though each FFISlice is self-contained and sound, so it's permissible to produce a slice without going through unsafe.

No problem with marking the as_slice function as unsafe

I still think if the main purpose of ArrayPointer is to govern C# codegen, some other construct might be a better solution (not saying it is, just how I understand the PR so far).

The unsoundness in ArrayPointer however can be caused "purely in Rust". The problem is that even if people call in correctly (i.e., we already have a valid ArrayPointer type) you can still trigger UB in Rust by passing in the wrong value when invoking as_slice().

Ok I see the distinction, I mistakenly thought that the FFISlice fields were public in rust.

I still think if the main purpose of ArrayPointer is to govern C# codegen, some other construct might be a better solution (not saying it is, just how I understand the PR so far).

I considered something like a ffi_hint as you suggested, however my reasoning for the pattern approach was:

It's a pre-existing concept within the library (rather than adding a whole new type).
It provides additional context on what the author intends the pointer to do, which is otherwise opaque to the library (ie, the backends have no way of knowing if a pointer represents an array, a single value, an optional value, etc.). Even if the only current use for this is solving the C# codegen issue, IMO having more context is beneficial.

Ah, just saw you pushed an update.
I'd still prefer to first explore other avenues to get the C# backend to emit the right binding.
My issue with going that route is that it seems to have little benefit over using raw pointer types from a Rust or any-other-language perspective.
In Rust you'd still have to call unsafe { array_pointer.as_slice(len) }, which is more-or-less slice::from_raw_parts() just with another name. The "return empty slice" part is convenient, but that could be a simple call (either in your crate, or even
interoptopus) which comes with much less "machinery".
In other languages (C, Python) that concept wouldn't translate to anything else than a fallback, and in C# it really only seems to affect IntPtr or not (again, please tell me if I'm missing something).
On the other hand, I think a hint system to tweak FFI generation is needed and came up a few times in our own bindings.
That said, I'm not strictly arguing that FFI hints are the problem to this particular issue; an even simpler alternatives could be just using *const c_void on Rust and ensure / guarantee that this always translate to IntPtr (semi-related ping @dennisradell since IIRC you had issues IntPtr vs ref too).

I considered something like a ffi_hint as you suggested, however my reasoning for the pattern approach was:

It's a pre-existing concept within the library (rather than adding a whole new type).

I don't quite understand, isn't ArrayPointer a whole new type / pattern added?

It provides additional context on what the author intends the pointer to do, which is otherwise opaque to the library (ie, the backends have no way of knowing if a pointer represents an array, a single value, an optional value, etc.).  Even if the only current use for this is solving the C# codegen issue, IMO having more context is beneficial.

Yes, and I'd totally agree that in many cases this is the right approach. It's just that this particular pattern, IMO, "doesn't carry it's weight" with respect to the user-code saved, safety gains, or general applicability.
(I might even change my opinion on this later on if more benefits became visible, just right now I don't see them).

In Rust you'd still have to call unsafe { array_pointer.as_slice(len) }, which is more-or-less slice::from_raw_parts() just with another name. The "return empty slice" part is convenient, but that could be a simple call (either in your crate, or even
interoptopus) which comes with much less "machinery".

TBH I only added this method as a convenience so entirely happy to lose it if you feel it's unnecessary. It was not the purpose behind the pattern.

I don't quite understand, isn't ArrayPointer a whole new type / pattern added?

It's a new type but the idea of patterns is not a new concept for the library and was considerably simpler to implement than adding a new ffi_hint type would have been. Also being a pattern means that a user familiar with the concept of patterns can make some assumptions about how it will work.

It's just that this particular pattern, IMO, "doesn't carry it's weight" with respect to the user-code saved, safety gains, or general applicability.

My general philosophy is that it's preferable to give automated systems the correct information to allow them to make the right decisions rather than explicitly tell them what result you want. Of course, this is a very idealistic view and requires much pragmatism in it's application, but to explain in more depth my thought process regarding this feature:
What I want on the surface is for the library to generate an IntPtr parameter rather than a ref object parameter, but the reason I want this is because the pointer represents an array, not a single object, and a ref object parameter makes no sense for an array. By using a raw pointer in the rust function signature, it is impossible for the library to know what I intend, so we have to give it that information somehow.
If we simply 'override' what the library would usually do by telling it explicitly what result we want in C# specifically, via something like ffi_hint, then we are solving the surface problem, but next time the a feature is added to the library in which specific code generation behaviour needs to be decided on the basis of whether a pointer represents an array or not, we're going to run into the same problem, and more ffi_hint attributes will be needed. However if we provide a mechanism to resolve the core ambiguity, the library will have the information to make the right decision in future scenarios yet unknown to us now.
I'm not necessarily suggesting that the pattern approach I've employed here is the best way of conveying this information, it might be better done by some variety of attribute, however rather than simply correcting the C# output, I feel that it is far more useful to indicate the purpose of the pointer parameter as that ambiguity is the root of the problem.

Thanks for the detailed reply.
More on a side note, from a design paradigms perspective I think I mostly agree with your reasoning; (so far) I've probably just differed in what the underlying vs. surface problem is. Within this library I mostly look at things with a C-lens, and there a distinction between single-element and multi-element pointers doesn't really exist, so adding these types feel like fixing what could also be labeled "bad C# ergonomics" (w.r.t, declaring C# FFI interfaces and working with ref / IntPtr). So then fixing the actual problem in this particular case just telling the backend what you want (and a similar "what you want" machinery would be needed, say, to tell C# whether you want the helpers metioned in #27).
However since C#-like marshalling details (e.g., the question of #[In, out] and whether content behind pointers need to be copied back) I could see myself getting around having interoptopus::patterns::ptr with a number of types which, in a first iteration, would just fall back to regular Rust pointers (e.g., via .into()) and FFI pointers (via .fallback_type())
Names tbd:

A generic FFIPointer<T, SingleElementOrMultiple, RustRW, FFIRW> indicating how that pointer is being used (type T of target, single or multiple elements, and who reads and writes; bonus points if we can make T so that it also accepts and enum of type alternatives although I wouldn't know how to do that)
various aliases to common FFIPointer<A, B, C, D> combinations.

The generic FFIPointer would fallback to *T or *c_void in backends for now or could be used for other optimizations (e.g., deciding if an #[In, out] should be applied.

Have some time now to look at #71 so closing this PR.


Fix download method for items with multiple images

The Download method of Item does not implement carousel.

Just read that this is intentional. Working on a proper implementation (mine is WIP and dirty).

I opened a PR (#152)


fix broken release infrastructure

I've been trying to get the tag workflow to run for the last hour or so and it seems broken in several ways. Here's the most recent failure:
https://github.com/twisted/constantly/actions/runs/6679755558/job/18152162563
I'm just going to make a release manually now.

I see that PyPi is configuredf for ci.yml , while the current file is named ci.yaml
This was previously configured

I have reconfigured PyPI for ci.yaml
This is what is configured now

@adiroiban cool. do you want to try doing a no-op micro-version release just to see if this works?

I can try do a .dev0 release on https://test.pypi.org/ .... not sure how the versioner part works for testing :( ... but I will give it at try.


Change PATH in project and drivers folder

Change PATH in project where all drivers will be loaded from. Create a folder in git project where dataset will be stored. Add also some .md file to specify why the folder is there. Also change the PATH where screenshots will be saved (default - to project folder).

Done.


Coalesce interval implementations

After issue #1158 and PR #1227, we have two representations of intervals in Ehcache sharing a common XML base.  The implementations

org.ehcache.clustered.client.config.TimeoutDuration  (/ehcache:config/ehcache:service/tc:cluster/tc:read-timeout)
org.ehcache.expiry.Duration (/ehcache:config/ehcache:cache/ehcache:expiry/ehcache:tti and /ehcache:config/ehcache:cache/ehcache:expiry/ehcache:tti)

share the underlying schema type time-type.
XML parsing support for TimeoutDuration takes advantage a JAXB parser based on the XML module definition of time-type.
This issue suggests:

Coalescing the common interval specifications of TimeoutDuration and Duration into a new API module object -- possibly TimeSpan-- and deriving TimeoutDuration and Duration from that common object.
Provide a JAXB parsing routine (see org.ehcache.clustered.client.internal.config.xml.ClusteringServiceConfigurationParser#processGetTimeout) that can be used by modules using configurations based on extension XSDs.

Review comments on PR #1227 should be reviewed for context and additional details.

Issue #2196 removed TimeoutDuration, and Duration is now deprecated in favor of java.time.Duration.


double free

import magma as m

@m.circuit.sequential(async_reset=True)
class Counter1:
    def __init__(self):
        self.count : m.UInt[16] = m.uint(0, 16)

    def __call__(self, inc : m.Bit) -> m.UInt[16]:
        print(locals())
        plusone = self.count + 1
        if inc:
            self.count = plusone
        else:
            self.count = self.count

        O = self.count
        return O

m.compile("counter1", Counter1, output="coreir-verilog")

Results in a double-free in coreir.
/pycoreir/coreir-cpp/src/binary/coreir.cpp:188 Running Runningvpasses
/pycoreir/coreir-cpp/src/passes/transform/rungenerators.cpp:10 In Run Generators
/pycoreir/coreir-cpp/src/passes/transform/rungenerators.cpp:26 Done running generators
/pycoreir/coreir-cpp/src/binary/coreir.cpp:197 Running vpasses
/pycoreir/coreir-cpp/src/binary/coreir.cpp:238 Modified?: Yes
double free or corruption (fasttop)

Hmm this might be a pycoreir issue. Closing for now, will file a new issue when I get a better repro.

Can you check if it's happening when you convert the coreir json to verilog? If not, that might suggest it's an issue with the magma pycoreir backend

Also could check if it happens when just compiling to coreir (not coreir-verilog)

I recall having issues with double freeing when using pycoreir. Definitely reopen this as a CoreIR issue if you can reproduce it from the coreir binary.

@leonardt does not happen with "coreir", does happen with "coreir-verilog".


Remanent Outputs

Hi, i was wondering if this is a issue with Homeassistant or this plugin, but i use the GPIO to drive relays for my appliances (TV, Audio, PC etc.) and at each homeassistant restart (altered configuration.yaml needs the full restart) all pins will turn off.
Is there a possibility to make the gpio pins remanent?

It is not possible, the GPIOs are reset by the driver. If you need the pins to keep their state between restarts I highly suggest to use ESP based board with ESPHome/Tasmota or a Shelly device.


Reorganize into multiple projects

Splits the scalacheck.Arbitrary instances and the tests into their own sub-projects. Makes it easier to depend on the instances in other projects for tests.

Curious about the above but aside from that LGTM. Btw, I added this in the PathyGen in quasar recently:
https://github.com/jedesah/Quasar/commit/4331d65c1ff85f24c1bd75264822c9b5a8f3b2e4#diff-40e2ae56540e33fc9d065079bbe40c0f
Since you are publishing a new version, might be worth putting that in here if it's deemed generic enough. I think it's probably fairly generic especially if we make it more like a function that accepts an Arbitrary[String] as the segment generator.

I'd say we do a separate PR for the other change you referenced. Once you're happy with this PR I'm going to publish another release so we can depend on it in quasar. There's bound to be a bit of release churn while we sort this stuff out, which is also why we're still in 0.0.x.

It doesn't need to be in this PR, but it might make sense to open a quick new PR before you publish. My reasoning is that one of the main intents of this PR is to be able to use the Generators in Quasar and get rid of PathyGen in Quasar. However, without this we won't be able to delete PathyGen.


Remove hardcoded studyright start date and credit targets, replace with start date + 3y and start date + 4y

[x] proto C/C2
[x] proto G

closed in #1990 or #1991


When template folder contains both azuredeploy.json and mainTemplate.json Outputs-Must-Be-Present-In-Template-Parameters test should check both templates

For Azure Managed Application, the template folder contains both azuredeploy.json and mainTemplate.json. When running the test suite and pointing to the template folder, the Outputs-Must-Be-Present-In-Template-Parameters.test.ps1 seems to specifically look in the azuredeploy.json file for the outputs of the createUIDefinition.json instead of looking in the mainTemplate.json and reports that these parameters are not found.

Actually I think we need to fail the suite on this scenario...  At least as designed currently, there can only be one "entry" point to a deployment.  We determine that by the filename, so if in the folder hierarchy there are 2 "main templates" we need to throw our hands up.
In your scenario, which I assume is similar to this: https://github.com/Azure/azure-quickstart-templates/tree/master/101-managed-application-with-linked-templates you would have to test those folders independently, or somehow otherwise state your intent that you have 2 separate deployments and the files fit together in a particular way.
We could pair CUID with a colocated template, but that's not a requirement (except in cases of AMA).
Open to other ideas...

Thanks! I agree with your assessment and closing this none-issue.


ability to use numbers on scale options instead of line or dot

i was wondering if the ability to use a scale with numbers on it is available? the desired result is to make the gauge look like a speedometer. if this does not currently exist, what would i edit in the code? i was hoping that i could use the existing calculations for the lines but instead of using a line, just insert a number. thank you

i also need that, please let me know if you implementated that.


moveControllerPropsToOnInit should not move explicit constructor content

When the moveControllerPropsToOnInit option is enabled and a custom constructor is present at the same time, the entire content of the constructor is moved to onInit():
Input:
import Controller from "sap/ui/core/mvc/Controller"
/** @namespace example */
export default class AppController extends Controller {
  input = this.byId("input")
  constructor(id, opts) {
    logger.trace("before super")
    super(id, opts)
    logger.trace("after super")
  }
}

Output:
"use strict";

sap.ui.define(["sap/ui/core/mvc/Controller"], function (Controller) {
  /** @namespace example */
  var AppController = Controller.extend("example.AppController", {
    onInit: function onInit() {
      this.input = this.byId("input");
      logger.trace("before super");
      logger.trace("after super");

      if (typeof Controller.prototype.onInit === 'function') {
        Controller.prototype.onInit.apply(this, arguments);
      }
    }
  });
  return AppController;
});

While it's understandably necessary to move constructor content after super to where it is executed after the moved props have been initialized, statements that appear before super should remain in the constructor and run before the call to the super constructor.
An example where this is required is when trying to pass data from the HTML page through a component to the application's root view - i.e., I would like the transpiled code to look something like this:
UIComponent.extend("my.Component", {
  constructor: function(id, settings) {
    this._componentSettings = settings;
    UIComponent.apply(this, arguments);
  },
  createContent: function() {
    var settings = this._componentSettings;
    delete this._componentSettings;
    var rootView = this.getMetadata().getRootView();
    rootView.viewData = settings;
    return sap.ui.view(rootView);
  }
});

Fantastic work on the plugin, by the way. With this in an easy-to-use build pipeline I can finally ~force~ inspire my colleagues to learn modern JS! 😈

@Elberet .
I'm glad you like the plugin!
I'll have a look at that. I've never had a use for constructor in a controller before so I did not handle this situation.
Something you might already be aware of is that in ES2015 classes, you should not use this before super in the constructor, as according to the spec it will be null. Might be fine in UI5 though.
Also, are you using version 6.x or 7.x (release candidate)? They'd both have the same behaviour for this, but just curious.
Ryan

@Elberet Please give rc3 a try. This version has a breaking change in your favour, where moveControllerPropsToOnInit no longer causes constructor code to get moved to onInit.
I added a new option moveControllerConstructorToOnInit to enable the old behaviour.
I also remembered that you could put the following jsdoc on a constructor to keep it.
/**
 * @keep
 */
constructor() {}

That wouldn't be needed for you with the new default behaviour, but if you enabled moveControllerConstructorToOnInit to get the old behaviour, you could annotate an individual constructor.
I think this new default is the better approach anyways as that @keep was a bit of a hack.

Seems to work; statements before super appear in the constructor before the transpiled super call, everything else gets moved to the top of onInit() just below property initializers. 👍


timedatectl warning on WSL

On WSL (Windows Subsystem Linux), snikt script reports the following warning.
$ snikt.R --version
Failed to create bus connection: No such file or directory
Warning message:
In system("timedatectl", intern = TRUE) :
  running command 'timedatectl' had status 1
SNIKT 0.3.0

This warning does not affect the functioning of the program.

The issue was found as a problem with the timedatectl not properly configured under WSL. timedatectl is queried by the tidyverse for time zone which if not set generates a warning.
This can be resolved with specifying the time zone for R to use.
echo -e 'TZ="America/New_York"\n' >> ~/.Renviron


Implement class tree

It will be nice if class hierarchy will be represented as tree instead of simple list of all subclasses

I believe this has been implemented in #43.


net: mDNS name resolving issue between 2 Zephyr nodes

I'm trying to use mDNS between two Zephyr nodes. I only want to resolve IPv6 addresses and I want to use the default server [ff02::fb]:5353.
I call dns_resolve_init with the address to setup the resolving and then send queries using the same code than samples/net/dns_resolve.
The query is properly formatted and sent.
Frame 1955: 78 bytes on wire (624 bits), 78 bytes captured (624 bits) on interface 0
Raw packet data
Internet Protocol Version 6, Src: fe80::200:5eff:fe00:5303, Dst: ff02::fb
    0110 .... = Version: 6
    .... 0000 0000 .... .... .... .... .... = Traffic Class: 0x00 (DSCP: CS0, ECN: Not-ECT)
    .... .... .... 0000 0000 0000 0000 0000 = Flow Label: 0x00000
    Payload Length: 38
    Next Header: UDP (17)
    Hop Limit: 64
    Source: fe80::200:5eff:fe00:5303
    Destination: ff02::fb
    [Source SA MAC: IcannIan_00:53:03 (00:00:5e:00:53:03)]
User Datagram Protocol, Src Port: 51196, Dst Port: 5353
    Source Port: 51196
    Destination Port: 5353
    Length: 38
    Checksum: 0xe4e6 [unverified]
    [Checksum Status: Unverified]
    [Stream index: 16]
    [Timestamps]
Multicast Domain Name System (query)
    Transaction ID: 0x09fb
    Flags: 0x0100 Standard query
    Questions: 1
    Answer RRs: 0
    Authority RRs: 0
    Additional RRs: 0
    Queries
        zephyr.local: type AAAA, class IN, "QM" question
            Name: zephyr.local
            [Name Length: 12]
            [Label Count: 2]
            Type: AAAA (IPv6 Address) (28)
            .000 0000 0000 0001 = Class: IN (0x0001)
            0... .... .... .... = "QU" question: False

The responder properly receives the query and responds properly:
Frame 1956: 100 bytes on wire (800 bits), 100 bytes captured (800 bits) on interface 0
Raw packet data
Internet Protocol Version 6, Src: fe80::200:5eff:fe00:5382, Dst: ff02::fb
    0110 .... = Version: 6
    .... 0000 0000 .... .... .... .... .... = Traffic Class: 0x00 (DSCP: CS0, ECN: Not-ECT)
    .... .... .... 0000 0000 0000 0000 0000 = Flow Label: 0x00000
    Payload Length: 60
    Next Header: UDP (17)
    Hop Limit: 255
    Source: fe80::200:5eff:fe00:5382
    Destination: ff02::fb
    [Source SA MAC: IcannIan_00:53:82 (00:00:5e:00:53:82)]
User Datagram Protocol, Src Port: 5353, Dst Port: 5353
    Source Port: 5353
    Destination Port: 5353
    Length: 60
    Checksum: 0xeadd [unverified]
    [Checksum Status: Unverified]
    [Stream index: 17]
    [Timestamps]
Multicast Domain Name System (response)
    Transaction ID: 0x0000
    Flags: 0x8400 Standard query response, No error
    Questions: 0
    Answer RRs: 1
    Authority RRs: 0
    Additional RRs: 0
    Answers
        zephyr.local: type AAAA, class IN, cache flush, addr fe80::200:5eff:fe00:5382
    [Unsolicited: True]

The answer is received but dropped by the resolver.
[net/core] [DBG] net_rx: (0x20000ab8): Received pkt 0x20002720 len 100
[net/ipv6] [DBG] net_ipv6_process_pkt: (0x20000ab8): IPv6 packet len 100 received from fe80::200:5eff:fe00:5382 to ff02::fb
[net/conn] [DBG] net_conn_input: (0x20000ab8): Check UDP listener for pkt 0x20002720 src port 5353 dst port 5353 family 10 chksum 0xeadd len 60
[net/conn] [DBG] net_conn_input: (0x20000ab8): No match found.
[net/core] [DBG] processing_data: (0x20000ab8): Dropping pkt 0x20002720

This is because since the resolver sent the query using a local port it's listening on that port but the responder, correctly I might add (see RFC), responds with both ports at 5353 as expected.

@lbise Thanks for good analysis, saved me lot of time :+1:

@lbise If you have time, please test the fix proposal.

Hello @jukkar, thank you for the speedy patch.
Now the ports are correct, however I found 2 issues.
The response is received now, however the resolver cannot find the query ID in its list of queries because when answering the mDNS responder forces the query ID to 0
ID set to 0 in response here : https://github.com/zephyrproject-rtos/zephyr/blob/ae5db66b8cc4f39aa6e0c0748d339612414420c4/subsys/net/lib/dns/mdns_responder.c#L118
Which makes resolver fail here : https://github.com/zephyrproject-rtos/zephyr/blob/ae5db66b8cc4f39aa6e0c0748d339612414420c4/subsys/net/lib/dns/resolve.c#L374
The second issue is that now if you have responder AND resolver both enabled (which was my case), the answer doesn't even reach the resolver because the packet is routed to the responder since there are 2 listeners on the same port now. Sadly I'm not sure this is easily fixable but you know better.
     Context          Iface         Flags Local               Remote
[ 1] 0x20000538       0x20012140    6DU   [ff02::fb]:5353     [::]:0
[ 2] 0x200005ac       0x20012140    6DU   [::]:5353   [::]:0

     Handler    Callback      Proto   Local                   Remote
[ 1] 0x20000f70 0x0803bc7d    UDP     [ff02::fb]:5353 [::]:0
[ 2] 0x20000fac 0x0803bc7d    UDP     [::]:5353       [::]:0

@lbise Fixed the "DNS id 0" issue, also the mDNS response parsing did not work properly. Please test if it works for you now. The issue with having both mDNS resolver and responder enabled at the same time, needs to be handled separately.

The second issue is that now if you have responder AND resolver both enabled (which was my case), the answer doesn't even reach the resolver because the packet is routed to the responder since there are 2 listeners on the same port now. Sadly I'm not sure this is easily fixable but you know better.

@lbise See #18797 for support to have both mDNS responser and resolver enabled at the same time.


Occasionally a new line is created instead of sending a message if you use a colon to select emotes

Checklist

[X] I'm reporting a problem with Chatterino
[X] I've verified that I'm running the most recent nightly build or stable release
[X] I've looked for my problem on the wiki
[X] I've searched the issues and pull requests for similar looking reports

Describe your issue
Occasionally [Return] fails to send a message if you use a colon and select an emote from the drop-down list. Instead, [Return] moves the caret to the next line. It's not clear why this happens and how to get out of this mode.
How I reproduce this
Open a chat → Enter ":" and the beginning of an emote → Select an emote from the list → Press [Return] to send the message → A new line appears instead of sending the message.
This isn't always the case. There're times when everything is fine. Sometimes the sending is restored without rebooting the app. Nevertheless, this happens 10-20 times a day. Any idea why?
Screenshots
No response
OS and Chatterino Version
Chatterino 2.4.2 (commit c8204ef7) built with Qt 5.15.2 Running on macOS 13.2, kernel: 22.3.0

and how to get out of this mode.

try clicking the client next time it happens

@Felanbird In my case, it doesn't work. But I found that if I open the popup window with all the emotes, then sending messages will work as usual.

This problem no longer exists since v 2.4.3.


glance-registry is deprecated and removed in Cloud9 (SCRD-7639)

We have completed the deprecation of the glance-resitry in Cloud9
and removed support for deploying it, therefore we should only be
generating service component entries for it in Cloud8 deployments
and not in Cloud9.
(cherry picked from commit a2f04ed57607723a59eb8e281cc28d3f42018994)
Trying again in conjunction with splitting https://gerrit.suse.provo.cloud/5639 into two patches.

https://gerrit.suse.provo.cloud/5646 contains the new first phase of the ardana/ardana-input-model.git patch.

https://ci.suse.de/blue/organizations/jenkins/openstack-ardana/detail/openstack-ardana/3350/pipeline started using gerrit patch 5646 to verify that it will allow us to proceed with the proposed strategy of breaking the original gerrit patch 5639 up into two phases.

Testing again in https://ci.suse.de/blue/organizations/jenkins/openstack-ardana/detail/openstack-ardana/3400/pipeline/

https://ci.suse.de/job/openstack-ardana/3422/ started to verify the change, rebased to latest SUSE-Cloud/automation; previous test job (rebuild in https://ci.suse.de/blue/organizations/jenkins/openstack-ardana/detail/openstack-ardana/3400/pipeline/) succeeded in conjunction with gerrit patch 5646.


Update AutoRest C# version to 3.0.0-beta.20230609.1

Update AutoRest C# version to 3.0.0-beta.20230609.1

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

Didn't this just merge as another PR?

Yes. The azure-sdk-for-net has been updated since generate this PR. So we triggered another release pipeline and regen another upgrade PR.
Close this one.


Update prometheus adapter for reload

Use a singleton builder to ensure port is used correctly.
Do smart reloads, counter state is trashed only when a metric
is redefined.
Ensure that builder.Build() does not panic on metric redefinition.

Release note:

NONE

This change is

We can delete handlers when there are no requests using it.
The way to achieve what you are suggesting is

stop accepting new work, put old handler in a quiesce mode.
Close the handler after quiesce period / when no requests are using it.
Create the handler with new config, requests wait until this handler is created.

This effective puts connection creation on the request path, which is a bad idea.
The real issue here is that, we don't distinguish between connection state (adapter config) and rest of config. When we do that, the work of singleton is done by the connection state.

OK, you got me there. We can't introduce a hiccup where we hold off
requests until a new handler is fully operational. We therefore have to be
able to create a new handler while the old one still exists. And then you
hit the prometheus port problem this PR is trying to address. Given that,
I'll review the PR in more detail.
On Wed, Aug 30, 2017 at 4:36 PM, mandarjog<EMAIL_ADDRESS>wrote:

We can delete handlers when there are no requests using it.
The way to achieve what you are suggesting is

stop accepting new work, put old handler in a quiesce mode.
Close the handler after quiesce period / when no requests are using
it.
Create the handler with new config, requests wait until this
handler is created.

This effective puts connection creation on the request path, which is a
bad idea.
The real issue here is that, we don't distinguish between connection state
(adapter config) and rest of config. When we do that, the work of singleton
is done by the connection state.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/mixer/pull/1173#issuecomment-326148253, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVucHeHmMxP4eTi4OE0hrgw_Bdy3YqJ-ks5sdfIYgaJpZM4PIAbf
.

@mandarjog: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-presubmit.sh
43c7d88eaab6296b923c29ad1979d27114717635
link
/test mixer-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@mandarjog: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-presubmit.sh
1d30f366ab964fd561cf04c25a0af320e767aa90
link
/test mixer-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[Feature] Display mysqld version in motd on Ubuntu

i know sometime you just wanna get things done, but this formula was build to support redhat based distributions too. so i'd wish it keeps supporting redhat with all new features.


Demo is not working if I upgrade the versions of dependencies to the latest ones

https://codesandbox.io/s/graphql-field-arguments-coercion-usage-gjppl?file=/index.ts
Currently, the demo seems not working when I use the following lib versions. I see the visitFieldDefinition of FieldResoverWrapperVisitor is not executed. So the validation is not working.
"graphql-tools": "^6.0.12",
"apollo-server": "^2.15.1",
"graphql": "^15.2.0",

It's working fine for me: https://codesandbox.io/s/graphql-field-arguments-coercion-usage-cwvqn?file=/index.ts
I've used<EMAIL_ADDRESS>


DEV change breaks Storybook (DEV not defined)

🐛 Bug report
Current Behavior
__DEV__ is not defined when running storybook, thus breaking storybook.
This is a result of #1577 / #1594.
Expected behavior
Storybook should run and have access to __DEV__
Reproducible example
Clone repo
git checkout next
yarn
yarn start
yarn run storybook (separate terminal)
Storybook runs but cannot display anything and JS console full of errors about missing __DEV__ variable.
Suggested solution(s)
Super easy, barely an inconvenience:
// .storybook/webpack.config.js

const { TsConfigPathsPlugin } = require('awesome-typescript-loader');
+const webpack = require('webpack');

module.exports = async ({ config, mode }) => {
  config.module.rules.push({
    test: /\.tsx?$/,
    loader: 'awesome-typescript-loader',
    options: {
      configFileName: 'tsconfig.storybook.json',
    },
  });
  config.resolve.extensions = ['.ts', '.tsx', '.js', '.jsx'];
  config.resolve.plugins = [new TsConfigPathsPlugin({})];
+  config.plugins.push(
+    new webpack.DefinePlugin({
+      '__DEV__': process.env.NODE_ENV === 'development'
+    })
+  );

  return config;
};

Your environment

Software
Version(s)

Formik
next

React

TypeScript

Browser

npm/Yarn

Operating System

👋 😄 👍

weirdly enough, this still happens 👀

this was merged to v3 and not v2. Reopening until it lands in master.

@johnrom would you recommend using v3 in favor of v2 yet?

v3 is in active development at the moment, so I wouldn't recommend using it in Production.


Reduce versions to build on Netlify

During the build process, we build a complete website for each version which is 9.2 MB / version.
On Netlify, our deploy preview infrastructure, we have to upload every changed file. Each time we cut a new version or making multiple changes we're facing timeout errors from Netlify trying to upload megabytes of HTML files.
This script makes sure we're not deploying unnecessary versions on Netlify.
We only need 0.5 which is the first draft of each doc, and the recent ones.
🐎 Also, this would significantly decrease the time needed to build a deploy preview.
⚠ imagebackground and safeviewarea were missing in versioned_docs/version-0.5.

@charpeni mind addressing the feedback from @hramos?

I removed ImageBackground and SafeAreaView from version 0.5, and instead, I edited the script to keep version 0.46 (ImageBackground) and 0.50 (SafeAreaView).
So, from now, on Netlify we'll have version 0.5, 0.46, 0.50, and all versions from 0.56. That should save us some time on building deploy previews and should prevent the timeout issue with Netlify on cutting releases.
I'll monitor this on the next release and I'll remove the script if it didn't help as planned.
Note: Netlify is only used for deploy previews.


question about dataset download and format

I am unable to download the SatMTB dataset from BaiduYun. Could you please upload it to OneDrive or Google Drive instead?
Additionally, I am looking for the dataset format for SatVideoDT. I found a readme.txt file, but it does not specify the headers in the label files. Could you provide that information?
Thank you.

@maxbeyond I am working on uploading SatMTB to OneDrive, thanks for your patience.
Besides, I am not quite sure what 'headers' mean. If you mean the format of MOT labels, it would be <frame_id>, <obj_id>, <bbox_left>, <bbox_top>, <bbox_width>, <bbox_height>, , <object_category>, , which is the same as the common MOT dataset.


fatal error: Index out of range

When return from the SwipeMenuViewController to the previous location

same

@shenmiaoling
fix by add code to ContentScrollView, SwipeMenuView, TabView:
open override func didMoveToSuperview() {
super.didMoveToSuperview()
    if self.superview != nil {
        setup()
    }
}

Same error. SwipeMenuViewController (1.1.5), Xcode 8.2.1, Swift 3.0.2

same issue please help

Hi, @shenmiaoling @chsasaw @Mirach0rus @yashdishatechnology .
Maybe, It happens because the number of pages and the number of tabs do not match.
I resolved this problem for fatal error crush by released version 2.0.1 .
If the number of pages and the number of tabs do not match, it will be blank instead of fatal error crush. (Xcode9.0, Swift4.x)
Thank you for reporting :-)

If you want to use with Swift 3.x please fork this code and make such a fix.

before

extension TabView {
    var currentItem: TabItemView {
        return itemViews[currentIndex]
    }
    ...
}

after

extension TabView {
    var currentItem: TabItemView? {
        return currentIndex < itemViews.count ? itemViews[currentIndex] : nil
    }
    ...
}


Scrutinizer Auto-Fixes

@alphadevx requested this pull request.
It consists of patches automatically generated for this project on Scrutinizer:
https://scrutinizer-ci.com/g/alphadevx/alpha/

Changes Unknown when pulling 9a5a4146eda0bc9b9e5e35a8875a806bdb05370a on scrutinizer-patch-1 into ** on develop**.


Converted NewEmbeddedNATSServer to a variadic options based signature…

Converted NewEmbeddedNATSServer to a variadic one.
Will be a breaking change, but now the two key bits of functionality can be overridden.
Cheers,
D

Depends on the style you want. Same outcome, different approach.
I'll re-do it. Sigh.

I can do in the morning sigh

Le soupir.
I've added the builder pattern and an examples directory to show you how to use it. Variadic has gone and despite being more verbose, seems to make sense. Tested. Noice.
seufzen.

Fixed in separate PR, thanks though this spurred that approach!


Potential conflict usage of pkgs folder?

Hi, I noticed that all CUDA binaries were installed in ~/anaconda3/envs/XXX/pkgs folder. In a recent issue in another conda package (https://github.com/conda/conda-pack/issues/112#issuecomment-653697649), I noticed that if installed the package in the root environment, it might clobber the package cache directories ~/anaconda3/pkgs. Can this be confirmed? Thanks!

To clarify, I am not claiming that it would overwrite anything. But it is somewhat of a reserved space for conda to use, neither users nor package it should depend on its continued existence.

@AgrawalAmey @andersy005 @scopatz @xmnlab
Could we please revive this issue? Every time I install cudatoolkit-dev to a new environment, I am finding that my (not so bandwidth-limited) system is spending 5-15 min minutes on the following step:
downloading https://developer.download.nvidia.com/compute/cuda/11.7.0/local_installers/cuda_11.7.0_515.43.04_linux.run to $CONDA_PREFIX/pkgs/cudatoolkit-dev/cuda_11.7.0_515.43.04_linux.run
Because this file is (1) downloaded to $CONDA_PREFIX/pkgs and (2) subsequently deleted anyway, it isn't cached. Can we instead include it as part of the cudatoolkit-dev package on conda-forge? Then, it will be downloaded to the system pkgs directory and cached. We can allow it to persist until the user intentionally runs conda clean. I believe this is a more standard practice.
I really think this will make installing this package much more efficient. Thank you!

@apoorvkh afaik it can't be done because of legal issues. We can't redistribute nvidia binaries I think.

Unfortunate :( but understood. Thanks!
Alternative: just download it to the regular conda pkgs directory, where it will be cached?

The pkgs directory is indeed a cache. If I look at the post-install code it seems like it will not re-download unless the cache has been cleared.

maybe something that could be done:

check if the cuda file is already downloaded, if so, check if the sha is correct, and if so, skip the download step
otherwise, download the cuda file, and check the sha if it is correct, if not, remove the file and raise an error
ensure that conda clean removes the cuda download.

thoughts?

I like @xmnlab's solution! Just to be clear, I feel that the file should be saved to the general conda pkgs directory, not the environment-specific$CONDA_PREFIX/pkgs directory.
Regarding CI pipelines: I think Github Actions provides 14 GB storage to runners by default and, if this becomes a concern, larger configurations can be requested. The CUDA file is 3 GB, so the affected CI workflows are those that consume exactly 11-14 GB outside of this file.
I imagine this would affect a narrow population of workflows. If so, I think the most obvious solution is to request larger storage. If that is not preferable, the users can simply add a conda clean step right after building the environment.

Makes sense, @apoorvkh do you want to raise a PR for this?

Sure, I'll try to get something simple rolling in the next few days.

Just a note for posterity: I probably won't implement the fix we were discussing above. Instead, the nvidia/cuda package seems to be a suitable alternative (at least, for me). I think it distributes the CUDA binaries directly (circumventing the issue we are facing here), includes "dev" libraries (e.g. nvcc), and appears to be actively maintained. Thanks anyway for the previous discussion!


Huge differences in prediction between versions of Keras (1.2.2 & 2.0.4) - Possible bug?

Today I've ran into some very strange behavior of Keras. When I try to do a classification run on the iris-dataset with a simple model, keras version 1.2.2 gives me +- 95% accuracy, whereas a keras version of 2.2.4 predicts the same class for every training example (leading to an accuracy of +- 35%, as there are three types of iris). The only thing that makes my model predict +-95% accuracy is downgrading keras to a version below 2.0:
I think it is a problem with Keras, as I have tried the following things, all do not make a difference;

Switching activation function in the last layer (from Sigmoid to softmax).
Switching backend (Theano and Tensorflow both give roughly same performance).
Using a random seed.
Varying the number of neurons in the hidden layer (I only have 1 hidden layer in this simple model).
Switching loss-functions.

Dependencies to reproduce the problem:

numpy=1.16.4
pandas=0.25.0
sk-learn=0.21.2
theano=1.0.4
tensorflow=1.14.0

Below is my code; it's only a short script, and I've included the iris data so the problem should be easily reproduced.
import pandas as pd
from keras.models import Sequential
from keras.layers import Dense
from keras.wrappers.scikit_learn import KerasClassifier
from keras.utils import np_utils
from sklearn.model_selection import cross_val_score
from sklearn.model_selection import KFold
from sklearn.preprocessing import LabelEncoder

#Load data
data_frame = pd.read_csv("iris.csv", header=None)
data_set = data_frame.values
X = data_set[:, 0:4].astype(float)
Y = data_set[:, 4]

#Encode class values as integers
encoder = LabelEncoder()
encoder.fit(Y)
encoded_Y = encoder.transform(Y)

# convert integers to dummy variables (i.e. one hot encoded)
dummy_y = np_utils.to_categorical(encoded_Y)

def baseline_model():
    #Create & Compile model
    model = Sequential()
    model.add(Dense(8, input_dim=4, init='normal', activation='relu'))
    model.add(Dense(3, init='normal', activation='sigmoid'))
    model.compile(loss='categorical_crossentropy', optimizer='adam', metrics=['accuracy'])
    return model

#Create Wrapper For Neural Network Model For Use in scikit-learn
estimator = KerasClassifier(build_fn=baseline_model, nb_epoch=200, batch_size=5, verbose=0)

#Create kfolds-cross validation
kfold = KFold(n_splits=10, shuffle=True)

#Evaluate our model (Estimator) on dataset (X and dummy_y) using a 10-fold cross-validation procedure (kfold).
results = cross_val_score(estimator, X, dummy_y, cv=kfold)
print("Accuracy: {:2f}% ({:2f}%)".format(results.mean()*100, results.std()*100))

Rename this file to iris.csv and you're good to go
iris.txt

I've managed to isolate the issue, if you change nb epoch to epochs, the model predicts very good again, in keras 2 as well. I don't know if this is intended behavior or a bug.


test: fix suppressing vue experimental warning

Description
There was a code which intends to suppress the following message.
But it was not working.
This PR simply fixes this.

[@vue/ref-transform] Reactivity transform is an experimental feature.
Experimental features may change behavior between patch versions.
It is recommended to pin your vue dependencies to exact versions to avoid breakage.
You can follow the proposal's status at https://github.com/vuejs/rfcs/discussions/369.

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Thanks! 🙏


Add thread for PathoGFAIR preprint

Hi,
I hope everything is okay (my first try of the tool there)
Bérénice

Media bluesky and mastodon are disabled in plugins.yml. either you have to delete them from your post file or, we have to add the credentials first and enable them.

Is it normal that the graphical abstract does not render?

Right now Mastodon and Bluesky do not support markdown syntax (we only support images).
I will fix this to just ignore any markdown for these social media platforms.
So it is better right now to not use markdown syntax.

Is it normal that the graphical abstract does not render?

Good point!
So right now the images will be separated from the file and parsed just into the first post. But I am not sure why it is not working right now.

That looks good :)

How should we do then?
Should I remove all Markdown formatting then? It might be good to explain that in the README

How should we do then? Should I remove all Markdown formatting then? It might be good to explain that in the README

For now yes but I will fix this issue.
It is mentioned in the README file:

Note that some social media platforms do not support Markdown formatting, so use plain text only.

It is mentioned in the README file:

Note that some social media platforms do not support Markdown formatting, so use plain text only.

Sorry I missed that

It is mentioned in the README file:

Note that some social media platforms do not support Markdown formatting, so use plain text only.

Sorry I missed that

No worries!

Great.
Sorry about that. I will fix this as soon as possible to ignore the markdown on Mastodon and Bluesky.

You could also now bring the markdown syntax back if you want to since @arash77 has addressed this in #58, i.e. your post would now use the markdown on matrix but use plain text on mastodon. You don't have to, of course - also looks good without it.

Tbh I am lazy to put the Md syntax back 😅

I merged main into this branch, maybe we get LinkedIn working as well for this post already?

I merged main into this branch, maybe we get LinkedIn working as well for this post already?

LinkedIn works now?

It should yes. We need to add it to the metadata in your post I think.
ping @arash77

#65 should get merged before that.

Closed to get a cleaner PR that could be a good showcase to link to


Code execution output alignment issue

Hi,
I am trying to use this to print a Python snippet:
def print_box_with_rounded_corners(width, height):
    if width < 3 or height < 3:
        print("Width and height should be at least 3 to draw rounded corners.")
        return

    # Top rounded corners and top border
    print('╭' + '─' * (width - 2) + '╮')

    # Middle part
    for _ in range(height - 2):
        print('│' + ' ' * (width - 2) + '│')

    # Bottom rounded corners and bottom border
    print('╰' + '─' * (width - 2) + '╯')

# Set the dimensions of the box
box_width = 10
box_height = 5

# Print the box
print_box_with_rounded_corners(box_width, box_height)

However, it gave out:

Could you help take a look?

Thanks for the report! This is fixed in master now.


pylint workflow added

This PR adds github workflow for running pylint.

Success! This PR now passes. It's not end of the story, however. For the time being, there are two major holes one could drive a truck through:

tests and linter is running on station only (no server)
the pylint is told to pass if the score is at least 7.0 out of 10.0. This is pretty low.

Ok, this is now ready for review. This covers CI actions for station. The server is more complicated (due to a need for Postgres) and will be added in the future release.


Merge main to live 12/19/23

This pull request includes updates to improve the content and ownership of the project. The most important changes include updates to the seo-reference.md file, clarifying content related to meta titles and descriptions, and removing a user from the list of default owners in the CODEOWNERS file.
Content updates:

Contribute/content/seo-reference.md: Updated section titles, descriptions, and clarified content related to meta titles and descriptions. [1] [2] [3]
Contribute/content/index.md: Updated a sentence to include the missing word "to".

Ownership changes:

CODEOWNERS: Removed user @Jim-Parker from the list of default owners.

#sign-off


[Feature request] Define retry logic and expected application error handling behavior

Description:
Define when a pipeline component aborted early due to non-application induced failure, the retry logic by the pipeline scheduler. Can the applicaion logic assume exactly once or at least once to build in error handling?
Additional information:
[Miscellaneous information that will assist in solving the issue.]

This will be addressed via: https://github.com/opendatahub-io/data-science-pipelines-operator/issues/335

@rimolive will follow up on this with current retry state in v1

Migrated to Jira: https://issues.redhat.com/browse/RHOAIENG-1605


Feature: Sign Up Roadblocks - Tracking Issue

Type of feature
🍕 Feature
Current behavior
There are a lot of places we should encourage sign in
Suggested solution

[ ] Force login when someone paginates any data on repository or contributors tab
[ ] Replace the reports page login button (it's been removed).
[ ] Hide all insights except contributors on the dashboard - https://github.com/open-sauced/insights/issues/722

Code of Conduct

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

Contributing Docs

[ ] I agree to follow this project's Contribution Docs

Points of interest to force login:

Adding any filters (ie top 100 repos, most spammed, etc)
Under Repositories, wondering if it is possible to show the first 5 repos in the chart below and blur the rest- forcing folks to
login to view the repos

We should also force login when creating an insight page

@takanome-dev you shouldn't be on this page if you're not logged in. We have a bug that doesn't redirect you somewhere else on logout currently

Ah that's why. Hum, I will look into it 👍


Adding consumer batch-size matric to sarama

Problem Description
If I have to expose a consumer batch metric from sarama, is this -> https://github.com/Shopify/sarama/blob/master/consumer.go#L519-L545 right place to do it? parseRecords get batch as an argument, can I put len(batch) as consumer-batch-size in metric?
@dim @eapache

@varun06 sorry this isn't my code, but I assume it depends on the Consumer.Fetch settings in https://github.com/Shopify/sarama/blob/master/config.go#L244

Thanks. I shall keep looking.


Remove ASTScope starting DeclContext hack

ASTScope takes a SourceFile and a SourceLoc, and finds the innermost scope containing the SourceLoc.
It used to also take a DeclContext, and if the DeclContext didn't match the innermost scope's DeclContext, walk up to the parent scope. Let's remove this hack and have the callers do the right thing instead.

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please test source compatibility Release


(fix) attribute deletion causes repl to freeze

closes #496
This issue is due to the fact that the array of the diagnostics get's out of sync with the actual code for a brief moment. This usually it's not a huge problem because it get's recomputed moments later but it can be a problem when the error falls outside of the max length of source code.
To avoid this issue i've added a bundling promise inside the context that get's reassigned whenever a bundling process starts and resolved immediately after the new bundle has been assigned to the store. The diagnostic has also been transformed from an array that get's recalculated dynamically to an async function that awaits the bundling process. Finally instead of simply passing the diagnostics to neocodemirror we create a linter  extension passing the aforementioned async function. Codemirror will call and await this function at each modification.
A couple of points:

This means the diagnostics feel a bit more slow because it has to wait for the bundling to finish, however this is more correct since the diagnostics immediately reflect the actual source code.
This could also be "fixed" upstream in @PuruVJ @neocodemirror library, right now does work as intended but it uses setDiagnostics and it might be beneficial to use the linter extension instead to allow for async diagnostic calculation. So if @PuruVJ prefer to first upgrade @neocodemirror i can update this pr whenever he push a new release there.

I'll try to close and reopen to trigger the deploy on vercel

Ok apparently it doesn't work just by this...I'll try to close it and open a new one


Excessive GraphQL calls on server side rendering

Although we have set {ssr: false} to some query, it's still invoked in server-side rendering. This puts extra load to SSR server.

Logger added to BatchHttpLink:
fetch: (uri, options) => {
  console.log(
    'FETCH',
    options.body &&
      (JSON.parse(options.body) || []).map(
      ({ operationName }) => operationName
    )
  );
  return fetch(uri, options);
}

Related issue: apollographql/react-apollo#3130, apollographql/react-apollo#3500

I seem to have a similar issue when setting up Material UI SSR + next-i18nnext SSR. The way Apollo detects SSR seems to be broken in certain scenarios when playing too much with React SSR, it might change some internal state


Spyder 5.0.1 dev installation fails in Pycharm Debugger

Problem Description
I trying run Spyder from source code in a debugger, but I am unable to.   I am able however able to run it the "old fashioned way" by pressing the Run button instead of the Debug button.  I am using Pycharm as my IDE to run Spyder from source.
What steps reproduce the problem?

Checkout v5.0.1 from Spyder code repository
Run conda install -c spyder-ide/label/dev --file requirements/conda.txt
Use Pycharm Run function to run boostrap.py and verify that it runs successfully
Use Pycharm debugger to run bootstrap.py
Behold the error.

What is the expected output? What do you see instead?
When I press run I see this in my Pycharm console:
/Users/selah/opt/anaconda3/envs/spyder-dev/bin/python /Users/selah/Repos/spyder/bootstrap.py
Executing Spyder from source checkout
*. Patched sys.path with /Users/selah/Repos/spyder
*. Patched sys.path with /Users/selah/Repos/spyder/external-deps/spyder-kernels
*. Patched sys.path with /Users/selah/Repos/spyder/external-deps/qdarkstyle
*. Patched sys.path with /Users/selah/Repos/spyder/external-deps/python-language-server
*. Installing PyLS locally
*. Declaring completion providers
*. PyQt5 is detected, selecting
*. Imported Spyder 5.0.1 - Revision 1f54323e5, Branch: (HEAD detached at v5.0.1)
    [Python 3.7.7 64bits, Qt 5.9.6, PyQt5 5.9.2 on Darwin]
*. Running Spyder
Bootstrap completed in 00:00:04.7186
No QCoreApplication instance found. Application patches not applied. You have to call load_stylesheet function after instantiation of QApplication to take effect.

When I press debug I see this in my Pycharm console:
/Users/selah/opt/anaconda3/envs/spyder-dev/bin/python "/Applications/PyCharm CE.app/Contents/plugins/python-ce/helpers/pydev/pydevd.py" --multiproc --qt-support=auto --client <IP_ADDRESS> --port 55460 --file /Users/selah/Repos/spyder/bootstrap.py
pydev debugger: process 26557 is connecting

Connected to pydev debugger (build 202.6397.98)
Executing Spyder from source checkout
WARNING: 3rd party Python exception hook is active: '_fallback_excepthook'
*. Patched sys.path with /Users/selah/Repos/spyder
*. Patched sys.path with /Users/selah/Repos/spyder/external-deps/spyder-kernels
*. Patched sys.path with /Users/selah/Repos/spyder/external-deps/qdarkstyle
*. Patched sys.path with /Users/selah/Repos/spyder/external-deps/python-language-server
*. Installing PyLS locally
unknown option --port
usage: /Users/selah/opt/anaconda3/envs/spyder-dev/bin/python [option] ... [-c cmd | -m mod | file | -] [arg] ...
Try `python -h' for more information.
Traceback (most recent call last):
  File "/Users/selah/opt/anaconda3/envs/spyder-dev/lib/python3.7/subprocess.py", line 512, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/Users/selah/opt/anaconda3/envs/spyder-dev/bin/python', '-W', 'ignore', 'setup.py', 'develop', '--no-deps', '--install-dir', '/Users/selah/Repos/spyder/external-deps/python-language-server/.installation-dir']' returned non-zero exit status 2.
python-BaseException

Process finished with exit code 1

Versions

Spyder version: 5.0.1
Python version: 3.7.7
Operating System name/version: MacOS Mohave 10.14.6

Use Pycharm debugger to run bootstrap.py

Sorry but we don't give support to run our development version in ways that we don't endorse. In this case, no one of us use Pycharm, so we won't be able to help you with your problem.

Fair.  Is there a debugging setup that you do endorse?  I'd love to get this running so that I can make some code contributions of my own to the Spyder project.

Got it.  Thanks!

Great! Thanks for understanding.


Service does not start in Windows

The fix for #1 does not seem to work: in this run, the result is:
sc config MongoDB start= auto
[SC] ChangeServiceConfig SUCCESS
sc start MongoDB
[SC] StartService FAILED 1053:

The service did not respond to the start or control request in a timely fashion.

child_process.js:674
    throw err;
    ^

Error: Command failed: sc start MongoDB
    at checkExecSyncError (child_process.js:635:11)
    at execSync (child_process.js:671:15)
    at run (D:\a\_actions\ankane\setup-mongodb\v1\index.js:5:3)
    at Object.<anonymous> (D:\a\_actions\ankane\setup-mongodb\v1\index.js:36:3)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
    at internal/main/run_main_module.js:17:47 {
  status: 1053,
  signal: null,
  output: [ null, null, null ],
  pid: 7084,
  stdout: null,
  stderr: null
}

The original step is:
      - uses: ankane/setup-mongodb@v1
        with:
          mongodb-version: 5.0

I noticed that Windows is not included in the test matrix for this action, which prevented detecting this in CI.

Hey @MattiSG, are you seeing the same error on every run? windows-2019 and windows-2022 are both included in the test matrix and currently passing, so it may be an intermittent issue.

Thanks @ankane for your fast reply and for pointing out the tests!

are you seeing the same error on every run?

I just ran it repeatedly, and indeed only that first attempt failed.

it may be an intermittent issue

Indeed, this flakiness unfortunately seems to be systematic with that Windows service start. There does not seem to be a way to prevent this.

both included in the test matrix

Sorry for that, I had not read further than the os matrix and had missed the os / version combination!


Merged pull requests' branch should not be created when migrating from github

When migrating from github, a branch will be created when migrating a pull request.
But this could be done by only opened pull request and that will speed up the process of migrating.

closed by #7463


Improve the performance of rendering road labels for a zoom level by

modifying polygons in-place and batching the transformations.
This is a followup to @michaelkirk's idea in #740. Some efficient in-place way to batch together transformations would be cool, but in practice, this is the one case that's a noticeable perf impact. So I think the one-off code is well worth it.
I measured the improvement to be about 35%. One zoom level on a large map dropped from 0.4s to 0.26s.

Ahem, see 58068b0da0e689dc13cfaa399f4ce98b6b6eb180 for a vital bugfix. Math is hard on a train.

A couple weeks ago I made an experimental integration with the upcoming (unreleased) AffineOps trait in geo: https://github.com/a-b-street/abstreet/compare/master...michaelkirk:abstreet:mkirk/affine?expand=1
I wasn't super pumped about the API usage, so I haven't tried to upstream it, but FYI.

It's not a terrible API... I like the flexibility of transformation_mut and transformation for consuming / builder API style vs modifying in-place. I'll keep it in mind as more geom changes slowly trickle through.


Missing vendor files. on setup wizard

Expected behavior:
Setup wizard should complete
Actual behavior:
Setup wizard ends with the following error:
Missing vendor files.
Reproduce steps:
Run Setup.
Version:
v3
Additional Information:
Running ubuntu 18.04, php 7.2, mysql 5.7.
Also tried with php 7.4, 7.3 and ubuntu 16.04

Can you show us your setup.log?


Temperature feature

There is a nearly insignificant bug in CMD_ANALOG_VAL_RD. When reading the temperature from the LM75, on line 975 the code is:
spirez = i2c_rdata[0];
I think it should be:
spirez = i2c_rdata[1];

Actually, I think the code should look like this:
converted_val = (signed short int)i2c_rdata[0];
converted_val = converted_val << 8;
converted_val = converted_val | i2c_rdata[1];
converted_val = 5 * (converted_val >> 7);

Actually, I think the code should look like this: converted_val = (signed short int)i2c_rdata[0]; converted_val = converted_val << 8; converted_val = converted_val | i2c_rdata[1]; converted_val = 5 * (converted_val >> 7);

Fixed typo in main.c. This only affects 0.5 precision reading. Keeping same code to have it consistent with other projects.
Thanks @Merewether.


NTR: NuA4 histone acetyltransferase complex binding

Hi,
From annotation review ticket (co-localizes_with complex terms): geneontology/go-annotation#1940
I need a term to indicate 'NuA4 histone acetyltransferase complex binding' based on
PMID:15528408
(Acetylation by Tip60 is required for selective histone variant exchange at DNA lesions.)
Thanks,
Penelope

GO:0035267 NuA4 histone acetyltransferase complex

Added in:
https://github.com/geneontology/go-ontology/pull/16317


proxy_on_start is called on worker threads with a 0 configuration_size

Title: proxy_on_start is called on worker threads with a wrong configuration_size
Description:
proxy_on_start is called on the main thread + on every worker thread, however configuration_size parameter has a correct value only the first time (must be on main thread)
Repro steps:

Use a test Plugin that calls proxy_log as part of proxy_on_start, e.g.
#[no_mangle]
pub extern fn proxy_on_start(id: envoy::ContextId, config_len: envoy::Size) -> envoy::WasmResult {
   unsafe {
     match envoy::proxy_log(envoy::LOG_LEVEL_INFO, &format!("proxy_on_start( id={}, config_len={} )", id, config_len) ) {
         Ok(_) => envoy::WASM_RESULT_OK,
         Err(e) => e.raw_error(),
     }
   }
}

Configure Envoy to use that Plugin and try starting Envoy with different concurrency settings
./envoy-static --concurrency 1 -c examples/wasm/rust.envoy.yaml

[2020-01-05 23:38:32.067][1887264][info][wasm] [source/extensions/common/wasm/context.cc:1028] wasm log my_plugin_1 my_root_id: proxy_on_start( id=1, config_len=28 )
[2020-01-05 23:38:32.068][1887264][info][wasm] [source/extensions/common/wasm/context.cc:1028] wasm log my_plugin_1 my_root_id: proxy_on_start( id=1, config_len=0 )
[2020-01-05 23:38:32.083][1887448][info][wasm] [source/extensions/common/wasm/context.cc:1028] wasm log my_plugin_1 my_root_id: proxy_on_start( id=1, config_len=0 )

 ./envoy-static --concurrency 2 -c examples/wasm/rust.envoy.yaml

[2020-01-05 23:39:59.028][1888566][info][wasm] [source/extensions/common/wasm/context.cc:1028] wasm log my_plugin_1 my_root_id: proxy_on_start( id=1, config_len=28 )
[2020-01-05 23:39:59.029][1888566][info][wasm] [source/extensions/common/wasm/context.cc:1028] wasm log my_plugin_1 my_root_id: proxy_on_start( id=1, config_len=0 )
[2020-01-05 23:39:59.044][1888582][info][wasm] [source/extensions/common/wasm/context.cc:1028] wasm log my_plugin_1 my_root_id: proxy_on_start( id=1, config_len=0 )
[2020-01-05 23:39:59.044][1888583][info][wasm] [source/extensions/common/wasm/context.cc:1028] wasm log my_plugin_1 my_root_id: proxy_on_start( id=1, config_len=0 )

./envoy-static --concurrency 3 -c examples/wasm/rust.envoy.yaml

[2020-01-05 23:42:52.821][1890912][info][wasm] [source/extensions/common/wasm/context.cc:1028] wasm log my_plugin_1 my_root_id: proxy_on_start( id=1, config_len=28 )
[2020-01-05 23:42:52.822][1890912][info][wasm] [source/extensions/common/wasm/context.cc:1028] wasm log my_plugin_1 my_root_id: proxy_on_start( id=1, config_len=0 )
[2020-01-05 23:42:52.837][1890925][info][wasm] [source/extensions/common/wasm/context.cc:1028] wasm log my_plugin_1 my_root_id: proxy_on_start( id=1, config_len=0 )
[2020-01-05 23:42:52.838][1890927][info][wasm] [source/extensions/common/wasm/context.cc:1028] wasm log my_plugin_1 my_root_id: proxy_on_start( id=1, config_len=0 )
[2020-01-05 23:42:52.839][1890926][info][wasm] [source/extensions/common/wasm/context.cc:1028] wasm log my_plugin_1 my_root_id: proxy_on_start( id=1, config_len=0 )

Notice that proxy_on_start is called with a correct configuration_size only once

Config:
static_resources:
  listeners:
  - name: main
    address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 10000
    filter_chains:
    - filters:
      - name: envoy.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager
          stat_prefix: ingress_http
          codec_type: auto
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains:
              - "*"
              routes:
              - match:
                  prefix: "/"
                route:
                  cluster: web_service
          http_filters:
          - name: envoy.filters.http.wasm
            typed_config:
              "@type": type.googleapis.com/envoy.config.filter.http.wasm.v2.Wasm
              config:
                name: "my_plugin_1"
                root_id: "my_root_id"
                vm_config:
                  vm_id: "my_vm_id"
                  runtime: "envoy.wasm.runtime.wavm"
                  code:
                    local:
                      filename: "hello_world.wasm"
                  configuration: '{"type":"vm","version":"v1"}'
                configuration: '{"type":"plugin","version":"v1"}'
          - name: envoy.router
  - name: staticreply
    address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 8099
    filter_chains:
    - filters:
      - name: envoy.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager
          stat_prefix: ingress_http
          codec_type: auto
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains:
              - "*"
              routes:
              - match:
                  prefix: "/"
                direct_response:
                  status: 200
                  body:
                    inline_string: "example body\n"
          http_filters:
          - name: envoy.router

  clusters:
  - name: web_service
    connect_timeout: 0.25s
    type: static
    lb_policy: round_robin
    hosts:
    - socket_address:
        address: <IP_ADDRESS>
        port_value: 8099
admin:
  access_log_path: "/dev/null"
  address:
    socket_address:
      address: <IP_ADDRESS>
      port_value: 9901

@yskopets -
Just a heads up, although you're probably already aware... might save you some unsafe blocks... you can use log = "0.4.8" and then log::info!, log::debug! etc macros if you are using the wasm filter crate found in this repo, since its _start fn sets up the logger to hook into the host.
I have some early work over here for example -- https://github.com/envoyproxy/envoy-wasm/compare/master...nilslice:sm/testing
w/r/t the config size change on worker threads, could this be intentional to provide filter code a way to restrict needless re-configuration? I'm admittedly speaking a bit outside my depth of Envoy knowledge here, but it seems like the main thread would be able to read configs, then use some shared state to inform other workers about the config data if needed at start.
Do you know if the configuration data is available to filter functions like proxy_on_request_headers through a host function call? otherwise, it would make sense to require filter creators to store the config data somewhere. similarly, some mechanism to remove the configuration from some shared state if a filter is pulled from the chain when envoy.yaml is reloaded.

@nilslice
Hi! Thanks for the tip!
No, I'm not using Rust SDK from this repo.
I'm doing a sanity check for Envoy ABI and behaviour of proxy_on_start is not intuitive to me.
I see that static variables set when proxy_on_start was called on the main thread preserve their values on worker threads (probably, due to VM cloning).
It makes sense for caching vm configuration, but not for choosing unique values per VM.
Is memory cloning a mandatory part of VM cloning ?

@yskopets - that sounds interesting... looking at your project https://github.com/yskopets/envoy-wasm-rust-sdk. witx looks great, and your work on [https://github.com/yskopets/envoy-wasm-rust-sdk/blob/master/envoy-abi/v1alpha/witx/envoy_host.witx](this file) is super helpful.


[Extensibility Enhancement] Table "Transaction Mode", field Code - add TableRelation + ValidateTableRelation

Our customers requested a Lookup on field Code of DataItem "Transaction Mode" in report "Get Proposal Entries".
We provided this by adding the following to field Code:
field(2; "Code"; Code[20])
{
Caption = 'Code';
NotBlank = true;
TableRelation = "Transaction Mode".Code where("Account Type" = field("Account Type"));
ValidateTableRelation = false;
}
Trying to extend this, we ran into the issue that it's not possible to use property ValidateTableRelation on the TableExtension.
Besides that, it's not possible to add a coded Lookup to the TableExt.
Our request is if Microsoft could add these properties.

Thank you for reaching out. Your request could be reporting a suggestion for the AL compiler not related to the AL application extensibility. Please reach out to the relevant support channels:

For collaboration in preview or beta versions of AL Language in Visual Studio Code (aka ModernDev), use GitHub (https://github.com/microsoft/al).


anchor build failed.   with use of unstable library feature 'build_hasher_simple_hash_one'

here is my  tool-chain
anchor_version = "0.29.0" solana_version = "1.17.13"
i have change the solana_version  from 1.16.24  stable  to 1.17.13.    but it did't work

rustc version is  rustc 1.76.0-nightly

This happens because Solana's rustc is outdated(https://github.com/solana-labs/solana/issues/33504).
The easiest way to fix this is to downgrade ahash version to the latest compatible version by adding:
ahash = "=0.8.6"

to your dependency list in Cargo.toml.

Fixed in https://github.com/solana-labs/solana/pull/34636 and https://github.com/solana-labs/solana/pull/34650

still having hash error when building (anchor build)
[dependencies]
ahash = "=0.8.6"
error[E0658]: use of unstable library feature 'build_hasher_simple_hash_one'
--> src/random_state.rs:463:5
|
463 | /     fn hash_one<T: Hash>(&self, x: T) -> u64 {
464 | |         RandomState::hash_one(self, x)
465 | |     }
| |_____^
|
= note: see issue #86161 https://github.com/rust-lang/rust/issues/86161 for more information
= help: add #![feature(build_hasher_simple_hash_one)] to the crate attributes to enable
For more information about this error, try rustc --explain E0658.
error: could not compile ahash due to previous error

still having hash error when building (anchor build)
[dependencies] ahash = "=0.8.6"
error[E0658]: use of unstable library feature 'build_hasher_simple_hash_one' --> src/random_state.rs:463:5 | 463 | / fn hash_one<T: Hash>(&self, x: T) -> u64 { 464 | | RandomState::hash_one(self, x) 465 | | } | |_____^ | = note: see issue #86161 rust-lang/rust#86161 for more information = help: add #![feature(build_hasher_simple_hash_one)] to the crate attributes to enable
For more information about this error, try rustc --explain E0658. error: could not compile ahash due to previous error

Can you share a repo that shows this error so I can test it locally?

this my repo:
https://github.com/oWahyudi/staking_program
The codes can successfully compile using the cargo build command.
$>cargo build
warning: `staking_program` (lib) generated 9 warnings (1 duplicate) (run `cargo fix --lib -p staking_program` to apply 5 suggestions)
    Finished dev [unoptimized + debuginfo] target(s) in 0.11s

compilation error when compile using the anchor build command.
$>anchor build
error: package `solana-program v1.18.0` cannot be built because it requires rustc 1.72.0 or newer, while the currently active rustc version is 1.68.0-dev
Either upgrade to rustc 1.72.0 or newer, or use
cargo update -p<EMAIL_ADDRESS>--precise ver
where `ver` is the latest version of `solana-program` supporting rustc 1.68.0-dev

compilation error when compile using the anchor build command.
$>anchor build
error: package `solana-program v1.18.0` cannot be built because it requires rustc 1.72.0 or newer, while the currently active rustc version is 1.68.0-dev
Either upgrade to rustc 1.72.0 or newer, or use
cargo update -p<EMAIL_ADDRESS>--precise ver
where `ver` is the latest version of `solana-program` supporting rustc 1.68.0-dev

That error has nothing to do with this issue, run solana-install init 1.18.0 to fix it.


props.change(fieldName, newValue) doesn't work on array field

The use case is I want to change Field B's value when Field A's value gets changed. Both Field A and B holds a value of an object in an array.  Say, Field A's name is "person[0].id", Field B's name is "person[0].firstName". When "person[0].id" Field value is changed to 1, in the onChange handler I call props.change("person[0].firstName", "Sam")
What is the current behavior?
Current behavior is the "person[0].firstName" Field value is not changed to "Sam"
What is the expected behavior?
"person[0].firstName" Field value is changed to "Sam",
and { person: [ { id: 1, firstName:"Sam" } ] } should be in the values object
Sandbox Link

What's your environment?

Other information

Could you provide a sandbox reproduction of this issue?

Hi Daniel, somehow I have got it work now. It was probably my own bug. Sorry about that. This issue can be closed


Jayasri2111

The Readme file is currently lengthy and complex, making it challenging for newcomers to comprehend how to contribute effectively to the project.
To enhance accessibility and clarity, I propose relocating the Contributing section to the beginning of the Readme file and streamlining its content where feasible.
I kindly request assistance from anyone willing to dedicate time to address this issue and improve the project's accessibility for all contributors. Thank you!

I am Jayasri Rengachari Master Student in Computer Science from Northern Arizona University. I am super excited to contribute to this project and excited to work for the enhancement of this project.

@caiton1 review my issue


Getting inverse Depth Map as output

Even after changing post_process = False in test.py I am getting inverse depth map as an output while visualization

It shouldn't be the case. The output should be just the depth map.


Change the LaTeX logo

Edit: I just realized that in some instances, there is a very dark background for discord, which would make a transparent-background logo look bad as well. Is there a way to change the logo so the background of the image fills the frame?
The LaTeX logo has a white trim around it, which looks bad when viewing Discord using dark mode. Please change the file to one that has a transparent background, like this

Done


Refactor entity picker

Signed-off-by: Ilya Savich<EMAIL_ADDRESS>Hey, I just made a Pull Request!
Refactored EntityTagPicker to re-use functionality for all filters with multiple select
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Quick question: The EntityAutocompletePicker is just the extracted (and generalized?) implementation? Hard to see if something changed.
Also love the additional tests.

(just popping in to mention I'm off for the holidays and reviews might take a while longer)

I see some odd test failures, would you mind looking into them? Perhaps a rebase to make sure first, but then eg the lighthouse test might actually have been affected

@freben tried to rebase, error this appears, do you have any idea what to do with it ? seems some memory leak, maybe to increase limit for pipeline ?
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [process]. Use emitter.setMaxListeners() to increase limit

@freben Is there a plan to export EntityAutocompletePicker? So devs can re-use it for their own custom filters since the picker already encapsulate quite a lot of boilerplate code.


Admin SDK cannot authenticate when mocking Date global

Step 2: Describe your environment

Operating System version: Windows 10 Home
Firebase SDK version: "firebase": "^5.4.2",
"firebase-admin": "^5.12.0"
Library version: _____
Firebase Product: Admin SDK nodejs, firestore (auth, database, storage, etc)

Step 3: Describe the problem
I am running Jest unit tests on functions including Admin SDK calls. Admin SDK is initialized with a JSON service account key before tests are run
using npm install mockdate package, which allows you to override the global Date, subsequent admin sdk calls provide the error below.
I would appreciate getting an understanding as to if this is a bug or something I can circumvent.
Steps to reproduce:
MockDate.set(moment().add(1, 'hours').toISOString());
admin.firestore().collection('some collection').doc('some doc').get()

Relevant Errors:
 { Error: 16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
        at Object.<anonymous>.exports.createStatusError (...\node_modules\grpc\src\common.js:87:15)
        at ClientReadableStream._emitStatusIfDone (...\node_modules\grpc\src\client.js:235:26)
        at ClientReadableStream._receiveStatus (....\node_modules\grpc\src\client.js:213:8)
        at Object.onReceiveStatus (....\node_modules\grpc\src\client_interceptors.js:1256:15)
        at InterceptingListener.Object.<anonymous>.InterceptingListener._callNext (.....\node_modules\grpc\src\client_interceptors.js:564:42)
        at InterceptingListener.Object.<anonymous>.InterceptingListener.onReceiveStatus (....\node_modules\grpc\src\client_interceptors.js:614:8)
        at ....\node_modules\grpc\src\client_interceptors.js:1019:24
      code: 16,
      metadata: Metadata { _internal_repr: { 'www-authenticate': [Array] } },
      details: 'Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.' }

Google auth servers will not issue ID tokens when the client's clock is out of sync. This approach of testing does not sound correct. You probably need to mock out all RPC calls made by the SDKs during testing.


Using tokio tracing for log file

Which issue does this PR close?
Closes #122 .
Rationale for this change
Enable thread info and cut log file by day.
Now logs look like:
arrow-ballista % cat logs/scheduler_ballista_<IP_ADDRESS>_50050.2022-08-10
2022-08-10T07:28:45.457283Z  INFO main ThreadId(01) ballista_scheduler: Ballista v0.7.0 Scheduler listening on <IP_ADDRESS>:50050
2022-08-10T07:28:45.457489Z  INFO main ThreadId(01) ballista_scheduler: Starting Scheduler grpc server with task scheduling policy of PullStaged
2022-08-10T07:28:45.458130Z  INFO main ThreadId(01) ballista_scheduler::scheduler_server::query_stage_scheduler: Starting QueryStageScheduler
2022-08-10T07:28:45.458307Z  INFO tokio-runtime-worker ThreadId(17) ballista_core::event_loop: Starting the event loop query_stage
2022-08-10T07:29:46.156777Z  INFO main ThreadId(01) ballista_scheduler: Ballista v0.7.0 Scheduler listening on <IP_ADDRESS>:50050
2022-08-10T07:29:46.157159Z  INFO main ThreadId(01) ballista_scheduler: Starting Scheduler grpc server with task scheduling policy of PullStaged
2022-08-10T07:29:46.157729Z  INFO main ThreadId(01) ballista_scheduler::scheduler_server::query_stage_scheduler: Starting QueryStageScheduler
2022-08-10T07:29:46.157922Z  INFO tokio-runtime-worker ThreadId(15) ballista_core::event_loop: Starting the event loop query_stage
2022-08-10T07:30:09.766192Z  INFO main ThreadId(01) ballista_scheduler: Ballista v0.7.0 Scheduler listening on <IP_ADDRESS>:50050
2022-08-10T07:30:09.768707Z  INFO main ThreadId(01) ballista_scheduler: Starting Scheduler grpc server with task scheduling policy of PullStaged
2022-08-10T07:30:09.769133Z  INFO main ThreadId(01) ballista_scheduler::scheduler_server::query_stage_scheduler: Starting QueryStageScheduler
2022-08-10T07:30:09.769264Z  INFO tokio-runtime-worker ThreadId(09) ballista_core::event_loop: Starting the event loop query_stage

What changes are included in this PR?

Are there any user-facing changes?

related issue: https://github.com/apache/arrow-ballista/issues/85


The paper link maybe wrong?

The paper link in the README is VoxelMorph.

Yes, thanks for the heads-up. We had to put a placeholder while arXiv processed our submission.


pull request for e2e test at 12/25/2016 17:26:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[log] New, make action log configurable and generic

CATEGORY

[ ] Bug Fix
[X] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
Make event logger configurable and generic
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[x] Introduces new feature or API
[ ] Removes existing feature or API

I'm tempted in doing a bigger change. @mistercrunch what do you think about creating a new module with the following structure:
superset/
log/
init.py (AbstractActionLogger, DBActionLogger, log_this decorator)
models.py (Log)
views.py (LogModelView)

Codecov Report

Merging #7705 into master will increase coverage by 0.13%.
The diff coverage is 87.5%.

@@            Coverage Diff             @@
##           master    #7705      +/-   ##
==========================================
+ Coverage   65.64%   65.78%   +0.13%
==========================================
  Files         459      460       +1
  Lines       21909    21927      +18
  Branches     2408     2408
==========================================
+ Hits        14383    14425      +42
+ Misses       7405     7381      -24
  Partials      121      121

Impacted Files
Coverage Δ

superset/models/core.py
83.72% <100%> (+0.69%)
:arrow_up:

superset/utils/log.py
85.18% <85.18%> (ø)

superset/views/core.py
73.06% <0%> (+0.27%)
:arrow_up:

superset/db_engine_specs/postgres.py
95.45% <0%> (+22.72%)
:arrow_up:

superset/db_engine_specs/mysql.py
93.02% <0%> (+30.23%)
:arrow_up:

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 2a453e1...7a4c5c6. Read the comment docs.

@dpgaspar the structure looks ok to me as is, my original idea was to just made EVENT_LOGGER a simple function, but the abstraction you have is more modular I guess
It could be good to allow us to shut down the current Log model and ModelView, but these really don't hurt. Main goal here is a hook to allow for hijacking / rewiring these events.
Another PR could add decorate many more views with @logthis

Yes, I know it seems over the board this kind of abstraction, but ideally @log_this should go out of the Log Model class, since we are making it generic, so in the future AbstractEventLogger is a good place for the decorator.

Rats! :)

@dpgaspar the ASF license check is failing, you simply have to add a header to all new files

I think I've already done that, logs says:
Our attempt to download rat locally to /tmp/lib/apache-rat-0.13.jar failed. Please install rat manually.
ERROR: InvocationError for command /home/travis/build/apache/incubator-superset/scripts/check_license.sh (exited with code 255)

Mmmh.. trying to force rerun, let's see if that helps.

Ok, done


Garbled hover in .pre-commit-config.yaml

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
Garbled hover in .pre-commit-config.yaml
Environment
Zed: v0.77.3 (stable)
OS: macOS 13.2.1
Memory: 32 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

This will be fixed in a few releases!


virtualbox as the default provider

My assumption is most people don't have an openstack cluster at their disposal to work with, so why is it the default, we should order these by which is the most likely vagrant deployment platform first and so on... If it's openstack -> libvirt -> virtualbox then we can close here, just wanted to bring it into question.

i'll merge. but openstack should be below even libvirt.


Route::model('status', Status::class) explicit binding causes route not found for SPA route

Laravel Version: 8.40
PHP Version: 7.4.1
Database Driver & Version:

Description:
If I add Route::model('status', Status::class)  to RouteServiceProvide.php it results in the following query call select * from statuses where id = 200 limit 1  as well as not found returned when it should return app.blade.php, if I change Route::model('statuses', Status::class) it works normal.
Steps To Reproduce:
https://github.com/asolopovas/laravel-status-bug

Hey there,
Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to report back and I'll gladly help you out and re-open this issue.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!

It looks like a bug not support request


Left over artifacts after running tests

Specifically when running contrib/hadoop_test.py, it makes my_dir/my_file. It doesn't clean up properly after its done.

closing this issue.

[x] It has been inactive for +4 months.
[ ] It's not about luigi core, so not as many users are affected about this.
[ ] The change seems quite big, it's unlikely to be sporadically picked up.
[ ] The owner haven't responded or disappeared.
[ ] I don't understand what this issue is about.
[ ] There exists a reasonable workaround for this.
[x] We need to check if this hasn't been fixed by now (for old issues).
[ ] This is kind of by design and not a bug.
[ ] Resolving this would probably add a lot of complexity.

Every open issue adds some clutter, and we try to make the issues fewer and make it easier for new collaborators to find. Currently we try to close any issue that meets the first checkbox + one other.
Feel free to reopen this issue at any point if you have the intent to continue to work this (i.e. send a PR). :)

I think things have gotten slightly better here. Another current effort is to split this repo.


Fix attributes and fix topic creation in kafkacat

@bhardesty On the same token, would you mind doing a quick peer review here as well? I also updated the attributes to be more consistent. I did this once before be they keep diverging. And the attributes injection isn't working for me on the new repo, so I just did it manually for now. I'll be asking Pete. I also manually added the signup-link and samples-git-repo variables downstream so that they render in the CP. Thanks.

@bhardesty I wondered the same thing. The only reason I kept it as is, is that the pattern I/we have followed is "enter this command and replace the values accordingly", which in this case includes the topic. I'll think on this though when I do my final UI sanity check and see again in the larger context if it makes sense to call it out more explicitly as a step or if it's a given. Thanks.


LXD storage api: Implement changing properties of storage volumes

For each property we need to check whether it applies to the storage volume and whether it can be changed and if so implement changing it.

All changeable properties should be changeable now.


Next

Related Issues

closes #
Short Description and Why It's Useful

Screenshots of Visual Changes before/after (if There Are Any)

Which Environment This Relates To
Check your case. In case of any doubts please read about Release Cycle

[ ] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[ ] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[ ] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)
[ ] I've updated the Upgrade notes and Changelog on how to port existing Vue Storefront sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and Currently Important Rules Acceptance

[ ] I read and followed contribution rules

Pull Request Test Coverage Report for Build 463670372

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+5.07%) to 99.31%

Totals

Change from base Build 446785342:
5.07%

Covered Lines:
119

Relevant Lines:
120

💛  - Coveralls

Pull Request Test Coverage Report for Build 463670372

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+5.07%) to 99.31%

Totals

Change from base Build 446785342:
5.07%

Covered Lines:
119

Relevant Lines:
120

💛  - Coveralls

Pull Request Test Coverage Report for Build 463670372

0 of 6 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.3%) to 95.504%

Totals

Change from base Build 446785342:
1.3%

Covered Lines:
333

Relevant Lines:
341

💛  - Coveralls

Pull Request Test Coverage Report for Build 463670372

0 of 6 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.3%) to 95.504%

Totals

Change from base Build 446785342:
1.3%

Covered Lines:
333

Relevant Lines:
341

💛  - Coveralls

Pull Request Test Coverage Report for Build 463670372

6 of 6 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.3%) to 95.504%

Totals

Change from base Build 446785342:
1.3%

Covered Lines:
333

Relevant Lines:
341

💛  - Coveralls

Pull Request Test Coverage Report for Build 463670372

6 of 6 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.3%) to 95.504%

Totals

Change from base Build 446785342:
1.3%

Covered Lines:
333

Relevant Lines:
341

💛  - Coveralls


workflow v0.9.9 re-release!

Improvements

Optimize Dns Cache's searching speed and memory size
Optimize route manager and dns resolver
Increase server task's performance by reducing some atomic operations
Increase global performance by removing some singletons
Always use dns resolver as name service policy when redirecting
Add WFServer::get_listen_addr() for server started on a random port
Support kafka kip 329

Bug Fixes

Fix service governance's ref count bug
Fix mysql sequence id bug when retrying big request
Fix VNSWRR upstream bug
Fix dns client bug when host name has trailing dot
Fix URL parser fatal bug

We have to re-release this version because some bugs were found.


When upgrading a package, it is unlinked and never re-linked.

I have a few packages on my MacBook that I have set to "ensure => latest".  When any of them are upgraded, I see a notice about them being unlinked, but they are never relinked.  I have to manually run (or script via puppet) a "brew link" for the upgraded package.

Terribly sorry for the delay, I was not able to work on this these past few weeks.
I will be on it shortly.

Also noticing this. Trying to use the linkapps parameter as per the README, but I get the error Error: Invalid parameter linkapps on Package[vim]. I uncommented these lines from 3b9c4c2f27d54918aea70f6eac3df5c4dab1b393, but still no dice. Is there something else needed to declare this as a supported parameter? I'm finding the Puppet documentation on custom providers to be somewhat lacking.

It's been over a year since the previous response @gildas, how's it going?