I've installed both .NET x64 and x86 and it still gives me the error "To run this application, you must install .NET Core."

same

nevermind i didnt dowloand .net core 3.1 https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-3.1.421-windows-x64-installer

for me too

Download this and install it
https://download.visualstudio.microsoft.com/download/pr/c6eac4d8-45f2-442d-a43d-79b30249cef8/35ffdb7ea4dc51f11705732a3a1d1d4c/dotnet-sdk-3.1.423-win-x64.exe

Ive installed everything the people here have listed but it still doesn't work :/

same issue as you. really need it for a virtual concert. damn :(

I also have the same issue, it atill ays download .Net Core :[ and I've treid downloading different versions too

I have the same issue, maybe it has something to do with the windows version? I used to have this tool on an older computer (windows 10) and it worked perfectly, I have tried with two different windows 11 computers and they also display this error message even if .NET Core 3.1 is installed.

I have the same issue, maybe it has something to do with the windows version? I used to have this tool on an older computer (windows 10) and it worked perfectly, I have tried with two different windows 11 computers and they also display this error message even if .NET Core 3.1 is installed.

I fixed this awhile ago, its the x64 / x86 version you use. If you have a 64 bit system, use x64, otherwise use x86.


Failed to mount component: template or render function not defined.

Version
3.0.1
Reproduction link
https://github.com/aeolusheath/vue-router-project
Steps to reproduce
router/index.js config like this :
import Vue from 'vue'
import Router from 'vue-router'

Vue.use(Router)

export default new Router({
  routes: [
    {
      path: '/',
      name: 'HelloWorld',
      component: require('../components/HelloWorld.vue')
    },
    {
      path: '/test',
      name: 'Test',
      component: require('../components/Test.vue')
    }
  ]
})

What is expected?
work right...no warn or error:
 Failed to mount component: template or render function not defined.

route can work right, and is there some way to avoid to import first and use it in router config.
I just wanna do it like before. straightly use component: require('xxxxx')
What is actually happening?
I update webpack and vue-router to newest version, but actually before I use 1.X.X of webpack and<EMAIL_ADDRESS>and they work fine

add .default  to require('xxx.vue') or import('xxx.vue')  it will work right
import Vue from 'vue'
import Router from 'vue-router'

Vue.use(Router)

export default new Router({
  routes: [
    {
      path: '/',
      name: 'HelloWorld',
      component: require('../components/HelloWorld.vue')
    },
    {
      path: '/test',
      name: 'Test',
      component: require('../components/Test.vue')
    }
  ]
})

maybe it's caused by babel version update.

I had the same problem and I fixed my global components like this:
Vue.component('notifications', require('./components/ChatNotifications.vue').default);
However, on my new remote server  this does not work. I get error:
Unknown custom element: <notifications> - did you register the component correctly?
On my previous server and on my local develepment it works. This does not work either:
import notifications from './components/ChatNotifications.vue';
as far as I can tell my gulp and webpack versions are the same on all servers. What might be wrong here?

Okay turns out that this works:
import notifications from './components/ChatNotifications.vue'
as long as I remember to register my components within my app
var app = new Vue({     el: '#app',     components: {         notifications     },
So clearly it is time for that Bourbon!

look at this vue-loader release log
vue-loader- 13.0.0 will set the vue component as a esModule by default。 Before 13.0.0 vue-loader set the vue component as CommonJsModule

You can use dynamic import() as an alternative solution
import Vue from 'vue'
import Router from 'vue-router'

Vue.use(Router)

export default new Router({
  routes: [
    {
      path: '/',
      name: 'HelloWorld',
      component: () => import('../components/HelloWorld.vue')
    },
    {
      path: '/test',
      name: 'Test',
      component: () => import('../components/Test.vue')
    }
  ]
})

it help full to me:component: require('../components/HelloWorld.vue').default
buti can not understood why we write .default at the end

@dhruvinprajapati
watch detail in   realease-log

In my case, i was using the same route name twice in multiple places, after removing the duplicate ones, this problem resolved.

Me pasó lo mismo, solucioné ésto cambiando la forma en cómo registraba mis componentes:
Antes:
Vue.component('pedidos', require('./components/Pedidos.vue').default);
Después:
import pedidos from './components/Pedidos.vue';
const app = new Vue({
    el: '#app',
    components: {
        pedidos,
    }
});

Sin embargo, no sé exactamente qué causó el error que se aparecía. Si alguien logra encontrar a fondo la causa del error, agradecería bastante que lo compartiera

same problem，.default works for me，and when i change require to import,it fixed too
import member from '../components/member.vue'
const routes = [{
  path: '/',
  component: member,
}]

Me pasó lo mismo, solucioné ésto cambiando la forma en cómo registraba mis componentes:
Antes:
Vue.component('pedidos', require('./components/Pedidos.vue'));
Después:
import pedidos from './components/Pedidos.vue';
const app = new Vue({
    el: '#app',
    components: {
        pedidos,
    }
});

Sin embargo, no sé exactamente qué causó el error que se aparecía. Si alguien logra encontrar a fondo la causa del error, agradecería bastante que lo compartiera

Tal vez era por la version de Vue (Tu código me ayudó bastante)

FWIW I spent half the day troubleshooting this for a customer today. Discovered that they had created a Vue CLI project in their existing app and then removed the Vue CLI app code. So none of the above would have worked. I only came upon the reference when reading the lock file. I deleted the package-lock.json file and then ran npm install which recreated a new lock file and everything was back to normal.


hyperparameter tuning

hey sir thanks for your helpful documentation
I have a question and i was wondering if yo could answer
have you tried hyperparameter tuning like bayesian optimization  and why you havent used this in your project
thanks

hey sir thanks for your helpful documentation
I have a question and i was wondering if yo could answer
have you tried hyperparameter tuning like bayesian optimization and why you havent used this in your project
thanks

I tried Grid Search and Random Search. What I didn't do in this paper is: tuning the parameters along the way, I only used the in-sample data from 2009-2015 to tune the parameters once, so there is some alpha decay here. Ideally, you should tune the parameters every quarter when you retrain your model.
Numerous hyperparameters – e.g. the learning rate, total_timesteps – influence the learning process and are usually determined by testing some variations.


RegexpTagger fails to handle exception.

There is a bug in the RegexpTagger. It fails to handle exception in case of missing tag or regular expression.
    def __init__(self, regexps, backoff=None):
        """ """
        super().__init__(backoff)
        try:
            self._regexps = [
                (
                    re.compile(regexp),
                    tag,
                )
                for regexp, tag in regexps
            ]
        except Exception as e:
            raise Exception(
                "Invalid RegexpTagger regexp:", str(e), "regexp:", regexp, "tag:", tag
            ) from e

The problem that both regexp and tag are not defined anywhere in the class, which is weird because it implies that the user should be notified with the missing tag or regular expression which is missing!.
The possible solutions from POV are:

Simply remove the regexp and tag variables from the exception messae.
Check for the length of each tuple in the list and throw exception if length of one tuple is not two.

Maybe the Exception should be more meaningful like, "RegexpTagger expects tuple of size two(regexp, tag).

I think it is useful to catch regexp compilation errors and report them in this way. I think the situation you describe can only happen if an empty list of regexps is passed to the initialiser.
We do not systematically check the type or internal structure arguments passed to NLTK functions.

I completely agree, but it is irrelevant to use un-defined variables. Also there is different cases where this behaviour can happens. For example, regexps = [(r'^-?[0-]', 'CD'), (r'(The|the|A|a|An|an)$', 'AT'), (r'.*able$',)], where the list contains a tuple that does not have a corresponding tag or vice versa.


badge doesn't increment

I used the react-chat-widget to create a chatbot.
When the bot replies to the user I want to increment the badge's value. I created a global var that increments when the bot answers and get back to zero when the user write his input. the I pass it to the badge as the following
  render() {     return (<Widget       badge={}       handleNewUserMessage={this.handleNewUserMessage}       profileAvatar={profileAvatar}       subtitle=""       title="Chatbot"     />     );
but it seems not be working.
So I am wondering how it does work and how can I resolve my issue

You need to pass number in badge
for example
badge='4'
here your working code
render() { return (<Widget badge=4 handleNewUserMessage={this.handleNewUserMessage} profileAvatar={profileAvatar} subtitle="" title="Chatbot" /> );

You need to count the messages on the addResponseMessage that updates your badge. Maybe push the messages into an array and get the length of the array and use that to update the badge.

the standart addResponseMessage method set a number to badge count, when widget is in minimized state.
but, when use the renderCustomComponent method does not set a number for the badge count.

I agree with @kartikmaan. This could use a more clear way to be done. Either exposing the current count so we can pass a new value to increment it, or a method to increment the value by a given number. As it stands now the only accurate way I could come up with:

Set bool stating away on minimize or instantiated without opening.
Set a counter that keeps track of event counts until app is opened.
On open set bool to false and clear count


Question/Doc request: smaller level of composition?

First: thanks to all contributers for this generator. I've been using it for quite some time now and it is still my favorite boilerplate for react development.
I see why support for various technologies got dropped and am trying to understand the ways to "composite own features into the generator". I was looking at the yeoman docs and the implementation in generator-react-webpack-alt. If I am not wrong this way of composition simply means writing your own generator and referencing base generators, which seems great for adding a reasonably large feature set (but also introduces all the restrictions of a single inheritance strategy).
So I am wondering if there are smaller levels of composition or more accurately simpler ways of integrating custom features into the existing generator. E.g. if I want to provide templates for flux things without maintaining a completely different generator or if I want to provide some flags that could alter existing templates similar to the way it is now supported with the --stateless option on the component template. I guess something like a "plugin-system" that
a) does not have to live in this codebase
b) can be simply activated on my behalf
I note that the yeoman docs on composition mention some new ways so that an "end user may also initiate the composition". This seems to be WIP and there isn't much information about what it is (and what not) right now. As I didn't find more information about it I just know that it sounds like it could address that concern. :)
TLDR;
Do you know about other ways to integrate own things into an existing generator and if so, do you think it's worthwhile to add some documentation about it (could also be a Github wiki here)? Or maybe I am making it much too complicated and just don't know a common best practice to do this.

@sthzg: First thank you for your last contributions. I enjoy them very much. I think I am able to elaborate how this whole thing came to life and why it is done the way it is currently. Maybe this will answer some questions.
As I was starting out with React and Webpack, there where simply not that much useable projects to get you going. The one project that I found and that was worth a deeper look was generator-react-webpack, in this time in its 1.x release. Like you, I really liked the way it worked and I also liked the whole Flux-Implementation-Stuff that was in there. It just made it very easy to get started.
Because of those reasons, I used it some time and finally got to the conclusion that there where some features missing. However, @newtriks, the original author of the software (and still the current project maintainer) was very busy with other things and could not put as much time in the generator as he wanted.
Then came some updates for Flux implementations that could just not be tracked fast enough. It was also heavy to support all those flux frameworks, because no one knew them all. You cant be expert for everything, even if you try as hard as you can. That was the moment when we choose to strip the generator down to its bare bones. I still thank @newtriks that he gave me this chance, as I was not that active in the node community before filing my first PRs in here.
We initially tried to just revert the changes, but much of the older generator code was not that easy to maintain anymore. We knew the people would still love to use those flux implementations.
When I thought about how to we could to it, I also stumbled above the yeoman doc link you stated above. So I decided to break the generator down and use the afromentioned composition feature for those flux implementations.
When version 2.0 was ready, I directly started with the -alt version. There I found out that it works a bit different than what I expected it to work. Like you, I thought I could just add the -alt features more or less "on top" of the current generator. As yeoman is file based, this simply does not work. The composition feature is, as far as I understand it (and I found nothing on the web stating otherwise) not meant to enhance a given generator with features, but just to use the features of a given generator to enhance YOUR newly build generator.
That is also the reason you got the component subgenerator in generator-react-webpack-alt. It is just not possible to export the original interface without adding a (nearly) empty generator that composes the build in react-webpack function :(.
This means you always seem to need a small amount of boilerplate code. It also means that when I would choose to add a new subgenerator to generator-react-webpack, ALL generators using it as a base should also include this one. If you are not, you would have a system that works like this:
# The first steps are identical:
npm install -g yo
npm install -g generator-react-webpack
npm install -g generator-react-webpack-alt

cd /somewhere

# Version one: Using the current interface (speek, how it IS):
yo react-webpack-alt
yo react-webpack-alt:component newcomponent
yo react-wbpack-alt:component newstate --stateless
yo react-webpack-alt:store mystore

# How it would be otherwise:
yo react-webpack
yo react-webpack:component newcomponent
yo react-webpack:component newstate --stateless
yo react-webpack-alt:store mystore

I honestly just dont know if the second version (without the composition feature) would not be too difficult to use. Therefore, I opted to go the more "expensive" way to compose the interface of react-webpack.
I would also love to have it the different way around, but just dont see a possibility with the current yeoman system. As the yeoman authors have stated in the documentation, the composition feature is still in early stages. So maybe one time it will be possible to enhance a generator with plugins in a "valid" way.
Hope this helps,
Chris

Thanks for your reply! Makes perfect sense. Like you said there are quite a few flux-implementations, all of them moving constantly and on top of it Facebook's Relay project that also influences the role of flux. Not to mention the choice of developing with or without flow. So yes, supporting that all in one monolithic generator wouldn't be possible.
I continued searching a bit for the second approach briefly mentioned in the Yeoman docs (end user initiating composition) but still haven't found something. I upped the question on SO, maybe somebody will clarify there (also, a first read through the yeoman code also didn't reveal something, but I need to take a closer look).
Until there is something more generic I thought about another approach to provide custom subgenerators for an existing project. The basic idea is to provide a small command line script that can be added to the npm run scripts. It would accept two arguments,

the URL to a ZIP containing a subgenerator
the name of the generator that this should be added to

The script simply downloads the zip, expands the relevant parts and injects it into the existing generator. To provide production-grade quality of such a tool involves quite a few aspects (like providing update/uninstall commands and a version check that can warn users when an update of the generator targets a later version of React as the subgenerator states to be compatible with).
If that sounds interesting I've started a repository where I am trying to come up with some proof-of-concept code. Not sure if it will work out though. ;-). Would be interested in your opinion on that approach (the code itself is purely prototyping code, doesn't guard against anything yet).

@weblogixx if you are okay with it I vote for closing this as an issue, as there are not any actions implied and the initial question is answered. As also the devs from Yeoman have clarified that the "user initiated composition" is a planned feature (and nothing related to it is included in the code by now) there doesn't seem to be an official and elegant way to compose on a smaller scale.

@sthzg: I am watching your growing repo. Seems nice so far. But yes, I really would like to wait for something "official" from the Yeoman-guys before implementing something like this. I will keep an eye on it (and on your repo, too).


Bug Fixed: Siren Not Stopping

Now, siren button works whether user switch to different activity or minimize the app or even close the app.
How:

Used Singleton Class - 'MyMediaPlayer' to achieve the functionality.
Only one instance of this class leads to create only one instance of 'MediaPlayer'.

Made two commits:
As in first commit, forgot to remove gson library dependency added by me.
In second commit, removed it.

Made two commits:
As in first commit, forgot to remove gson library dependency added by me.
In second commit, removed it.

Great work @codeDamon 🚀

Great work @codeDamon 🚀

Great work @codeDamon rocket

Thanks :)

Great work @codeDamon rocket

Thanks :)


soc: nrf53: Add enabling of LFXO pins (XL1 and XL2)

Add a Kconfig option (enabled by default) the enables the low-frequency
oscillator (LFXO) functionality on the XL1 and XL2 pins in the nRF53
SoC initialization routine. This cannot be done in the clock control
driver, as it was done so far, because that won't work in a setup where
the application core image does not use the system clock at all.
Fixes #29762.

I've run a quick test and I have not seen any improvement. When I have an emtpy app in Application core, the program in the Net core spinlocks waiting for LF oscillator during initialization procedure.

@hubertmis your "empty app" still runs through the Application core initialization, right?

I've run a quick test and I have not seen any improvement. When I have an emtpy app in Application core, the program in the Net core spinlocks waiting for LF oscillator during initialization procedure.

@hubertmis The problem is in this empty_app itself. See https://github.com/nrfconnect/sdk-nrf/blob/2291ddb833869ba15f2705da7e6c13851440ad68/samples/nrf5340/empty_app_core/src/main.c#L56-L65.  It reconfigures all the pins so that they are assigned to the Network core. But XL1/XL2 should stay configured with the value Peripheral for the LFXO to work. Try commenting out the lines mentioned above, or just use uint32_t i = 2; as the initialization of the first loop there.

I've run a quick test and I have not seen any improvement. When I have an emtpy app in Application core, the program in the Net core spinlocks waiting for LF oscillator during initialization procedure.

@hubertmis The problem is in this empty_app_core sample itself. See https://github.com/nrfconnect/sdk-nrf/blob/2291ddb833869ba15f2705da7e6c13851440ad68/samples/nrf5340/empty_app_core/src/main.c#L56-L65. It reconfigures all the pins so that they are assigned to the Network core. But XL1/XL2 should stay configured with the value Peripheral for the LFXO to work. Try commenting out the lines mentioned above, or just use uint32_t i = 2; as the initialization of the first loop there.

Agree, this should do it. Let's wait for @hubertmis to try and  confirm the fix.


feat: indexedDB support

Implemented indexedDB support for the persisted store. This allows data to persist in indexedDB instead of sessionStorage or localStorage, useful for larger datasets.
Key changes include:

Localforage is now used for a consistent API
All operations are now asynchronous due to localforage being asynchronous
As localforage does not support sessionStorage, the default sessionStorage is used (no problems are caused)

More specific changes are listed in each commit.
PS: All operations are asynchronous, and a type warning is not provided as the methods of the persisted store do not return.

Thanks @intercepted16!
I'm not totally sure, as it it contains breaking changes. It would mean all user's of this package would need to upgrade, even if they don't use Indexed DB.
For now, I don't think it's a good time to add it. Maybe it can be considered as part of the change to Runes API. (since that will require breaking changes anyways)
P.S. Would prefer if larger changes start as discussions, because I feel bad to turn away someone's effort

My 2 cents:  This brings an extra package.  This increases bundle sizes for people that don't used indexed DB.  I would vote against this even for the runes version.  Perhaps it could be created as a separate package.  I don't think there's enough justification to force asynchronous API's that 90+% of people won't need.

@webJose I would just like to add that localforage is actually quite lightweight; it is only 8.8kb when gzipped. However, I do agree with the forced asynchronous API's.

The less packages your application uses, the better in terms of maintenance.  Packages become obsolete, so yoiu have to keep on updating things.  Packages might also provide a surface for attacks.  If you bring a package to your application that you don't need, you might end up getting extra work to clean up a CVD about it.  What for?  Nothing.  Your app is not needing it.  You are just doomed to maintain it because it comes with another package that you do use.  It is good to apply the Single Responsibility Principle to packages.

@joshnuss If I modify it to use a synchronous API without localforage or an external library, would the PR be accepted?

@intercepted16 My understanding is that the IndexDB API is inherently asynchronous.
An alternative approach is having different function for each storage method.
// old-style of import would be deprecated
import { persisted } from 'svelte-persisted-store'

// instead there would be separate functions for localStorage, sessionStorage and IndexDB
import { persisted } from 'svelte-persisted-store/local-storage'
import { persisted } from 'svelte-persisted-store/session-storage'
import { persisted } from 'svelte-persisted-store/index-db'

Then the IndexDB version would have slightly different signature (async) and slightly different implementation (no need for serialization with indexdb)

@joshnuss Sorry, I made an error in my comment. I will try to implement your suggestion.

Before you implement, let me ask for feedback from a few folks
@bertmad3400 @webJose @niemyjski any thoughts on this proposed change?

Hello.  Strictly speaking, if the feature can be tree-shaken, theoretically it would not affect bundle sizes.  Using different functions as @joshnuss suggested would be the right move in the tree-shakable direction.
Still, the feature is so unique that I don't think it should be covered by this package, at least not as it is today.  I don't think many people need to store a lot of data in the browser.  This is, in my opinion, an edge-case feature.
A bold suggestion would be to break everything and re-think this package thinking plug-ins:  Make this package provide the reactive parts, but don't provide storage of any kind.  Instead, users of the package would have to install another package that would add the storage part.  Therefore, users will be able to use the same "front" logic of this package with any storage they like.
Examples:

WebJose needs session storage.  WebJose therefore installs svelte-persisted-store and svelte-persisted-store-session.
Joshnuss needs indexedDB storage.  Joshnuss therefore installs svete-persisted-store and svelte-persisted-store-indexedDB.

Etc.  A system where one package provides reactivity (the Svelte part), and another package provides the storage.  Too radical?  Perhaps.  Still, strictly speaking such system satisfies my requirements of not increasing bundle sizes and not changing the interface.
On the other hand, indexedDB has asynchronous API.  Forcing the API to synchronous is something I don't like.  In the plug-in system I would then standardize all storage API to be aysnchronous.  This is the downside I see.
So, practical terms:  Joshnuss' suggestion seems to be the more likely one for me.

So I have a couple of thoughts:

This project really needs a formatter. Shouldn't be a big change, but makes diffs like these much, much more readable.
Personally I could definitely see the use of an indexedDB option. The storage limits on localStorage means that there are some cases where that isn't viable.
The breaking API change, by requiring everything to be async would for me (had I been the library maintainer) be a deal breaker as well. For this problem I could see two potential solutions:

Implement this as an option param (so besides localStorage and session, the storage type could be indexedDB) along with some complex types, which would modify return types of the store based on the set storage type option param. This has the advantage of making this minimally invasive to the user, but would probably massively complicate the codebase.
Implement this as a second store. I think this is the most viable option, though it would probably require some refactoring work of the existing code-base.

If we are to include indexedb as an option here (and I really think we should consider that), I would love to see a draft of implementing the required interaction with indexedDB natively. I too don't like the idea of relying on localforage for this functionality, and I have a hunch that while indexedDB surely is more complicated than the localStorage API, I wouldn't believe it would be too terribly difficult.

@joshnuss I was thinking, and index.ts could still export a persisted function, but it returns one of the storage types, and it would only have to be awaited if the user chose indexedDB.
Eg:
// an indexeddb class could be implemented manually here
...

// types could be implemented here
...

export function persisted<T>(options: PersistedOptions): DynamicType<T> =  {
let storage: Storage | indexedDB
  switch (options.storage) {
    case StorageType.Session:
      return sessionStorage;

    case StorageType.Local:
      return localStorage;

    case StorageType.IndexedDB:
        return new IndexedDB()

    default:
      throw new Error('Invalid storage type');
  }
}

// in this example, it is not a store.
const localStore = persisted({storage: 'local'})
localStore.getItem('a')

const sessionStore = persisted({storage: 'session'})
sessionStore.getItem('b')

const indexedDBStore = persisted({storage: 'indexedDB'})
await indexedDBStore.getItem('c')

@webJose @bertmad3400 I have implemented @joshnuss's solution of three functions; localState, indexedDBState and sessionState in a new pull request: #273


Added notice about XQuartz on OSX

Why do you need XQuartz?

While i was trying to install the dependencies via Homebrew, i got informed by my terminal that i have to install this.

Were you installing wine?

I already had wine installed. But it´s not the problem. While installing the dependencies via Homebrew i got noticed about XQuartz..

I still don't think this is necessary, even though it's not a big deal...
One last question: when you were told to install XQuartz, did that notice also tell you how to install it (i.e. the exact command to run)?


Fix two wrong urls.

Coverage remained the same at 19.392% when pulling a50ff0b472630de82035c9179d1aaba1efea911d on doc/publish into 56c11d40207dcec15fbae8aaa0741842ad096950 on master.

@michaelsembwever Done.


How would one inspect the contents of the cache?

The Dictionary list of Keys is not exposed in the MemoryCache class like it was in previous implementations (I believe this currently tracked in the _entries variable).  I understand, the argument is that the list could be stale or even go stale as you iterate through it (I still think the benefit outweighs the known risk).
My issue is, how would someone inspect the contents of the cache in a diagnostics scenario?  It seems like an awful lot of overhead to implement a cache manager of what might be there when the underlying Dictionary of keys could just be exposed like in past implementations (yes, it could be gone even during the iterating loop but it could also be gone at any request even if I'm tracking it).  In the past this was blocking and not recommended for production environments (from MS documentation) but there are reasonable environments where you may want to do this (and the information is valuable when it's needed).
As reference, the Count property exposes the underlying dictionaries count with the comment "Gets the count of the current entries for diagnostic purposes".
I was able to fork the project, expose the keys and replace that assembly via a custom nuget feed.  Is it possible to inspect the cache without an intervention like this?

I don't think exposing the keys is the right default, because of the risks. Folks will just use it without knowing the risks.
If you really want to do this, I think instead of forking the code and exposing it in your fork, I recommend writing a wrapper which basically saves and deletes the keys in Set and Remove operations after calling our cache's respective methods.

There are lots of useful things that people could misuse.
Is this not something that could be explained briefly in the XML comment that Intellisense would then render?  E.g. "Returns dictionary enumerator used to iterate through keys in the cache.  This is a blocking call with the keys as of a point in time.".  That makes it's behavior clear and allows me to accept the now known risk.
Writing a wrapping manager is ok for when I add something into the cache via code but there are other entry points into the cache like the cache tag helper or even third party controls that may have a behavior that's out of my control.  With no way to inspect it's full contents easily it's incredibly difficult identify an issue like that.

Inviting @lodejard to chime in too.
cc @Eilon

My philosophical view is that it's definitely a wrong API to have. This type of cache is deliberately unpredictable so listing keys is not logical.
But the diagnostics scenario is definitely interesting. Would it make more sense to just have some diagnostics feed of data from the cache system? Then anyone wishing to introspect into the cache could go through some different API? You could even maybe get other information about hits/missed/size/etc.?

I would welcome an alternative API route, that would alleviate my issues.  That data would be incredibly useful in debugging and fine tuning (and getting additional data like size is more than we've had in the past).  Knowing hits and misses or even the life of some objects and be useful in finding misuses of the cache.
Would you see the separate API including the keys (or at least where the objects originated from)?  More from the perspective of the key name can be helpful identifying information if it has been meaningfully named.

Something like DiagnosticsSource? https://github.com/aspnet/Caching/issues/129

@Tratcher not like it, but exactly it :smile:

Yeah, https://github.com/aspnet/Caching/issues/129 seems to be the right way for diagnostics. @blakepell Would the general proposal outlined there would be helpful to you?

@muratg - Yes, very much so.  #129 as it reads would cover want I wanted to address (and more).

Cool, tagged you in that issue so that you're notified when the issue changes.  Closing this one.


Closing expanded view with [x] stays in "Expand" tab

Describe the bug
Dismissing expanded view does not retain tab selection.
To Reproduce

Go to Graph Explorer
Run a query that has a response body (GET /me should work in sandbox)
Click on "Expand"
Dismiss the expanded view by clicking on [x]
Response pane stays with a focus on Expand "tab" without any content being shown as if there is no response.

Expected behavior
I think whichever tab is chosen in the expanded view should stay selected when the expanded view is dismissed.
A nice-to-have would be to always remember the selected tab, e.g. expanding "code snippets" tab defaults into "response preview" being selected in the expanded view.
Screenshots
Before expansion:

Expanded view:

After expanded view is dismissed:

Thanks for quick turnaround on this @Onokaev! Really appreciate it!


Interaction when in spectator mode

As spectator mode is meant for… spectating. A physics entity should only react to the player if they're any gamemode except spectator.

Fixed: https://github.com/LazuriteMC/Rayon/commit/08ecd02ef7f3676d810fe6c675b9a0b3cf6776f6


Make portRe constant

When running unfurl format %r.%t on a long list of urls, the function extractFromDomain() will be called separately for each one of the urls, multiple times.
This causes the same regex to be compiled multiple times:
	portRe := regexp.MustCompile(`(?m):\d+$`)

Instead, portRe should be a constant. I changed the regexp to be constant and tested it on a list of 1.1 Million urls. I got the following results:
Old: 0m35.384s
New: 0m21.374s

Hi @tomnomnom,
Did you have the time to review this?


Bubbles sizes are stable (GatsbyJS in production mode )

Hi,
Gatsby development mode works fine but in production mode, bubbles stay solid. There is no overriding css. Can't figure out why.
Demo

Comment out API calls & add your companies array.

Or just create a new gatsby application and install React-Bubble-UI in it.
Thanks in advance

Resolved. Was Not related with React-Bubble-UI.


Manual: $ is used instead of # for commands that must be run as root

Issue description
This part of the manual says:
WarningThese commands must be executed as root, so you should either run them from a root shell or by prefixing them with sudo -i.
and yet the commands are prefixed with a $ (without a sudo -i) instead of a #, eg.
$ nixos-rebuild switch
$ nixos-rebuild boot
I figure I must be missing something, hence why this isn't a pull request.

The NixOS manual does not follow that convention, but uses $ consistently throughout. I'm unsure whether using the # convention was ever considered.

I've recently into NixOS and coming from Archlinux, I was slightly confused by the manual as to which commands require root and which commands can be invoked by normal users. The ArchWiki differentiates pretty consistently between # (run command as root) and $ (run command as normal user), which makes things easier.
Here is an excerpt from the wiki editing guidelines which I find sensible:

When using inline code […], no prompt symbol is to be represented, but any notes about permissions must be added explicitly to the surrounding text.
When using block code […], use $ as a prompt for regular user commands; use # as a prompt for root commands.

Note: Because # is also used to denote comments in text files, you should always make sure to avoid ambiguities, usually by explicitly writing to run the command or edit a text file.

The sentence introducing a command block should usually end with :.
Unless really necessary, prefer using:

# command

instead of writing:
$ sudo command

Do not use the root prompt and the sudo command together, like in:

# sudo command

The only exception is when sudo is used with the -u flag: in this case the prompt can match the others of the same code block, or default to $.

- Do not add comments in the same box of a command, for example:

# pacman -S foo  #Install package foo

Do not assume the user uses sudo or other privilege escalation utilities (e.g. gksu, kdesu).

I don't know if there are explicit style guidelines for the NixOS manual, but if the above rules are acceptable, I can try to work on a PR based on them.

@wlhlm adding a brief section near the beginning that establishes notation sounds like a good idea. For now, I think it suffices to introduce $ and # as short-hands for user/root. It's diomatic and I think it's a clear improvement over the visually noisy warning boxes used currently. (Also: the more policy you want to add, the more we'd need to talk about it before implementing it, I think ... starting small is probably a smart move)

PR in #15589.

This can be closed now that #15589 got merged.


SOLID POD: Create a UI for editing/revoking permission

Revisit this issue after the permission UI in solidpod is done.

Done as part of https://github.com/anusii/solidpod/issues/140


feat: migrate to new auth method

For access to the File API:

Use authorization header is provided (it's provided when the adapter is called from the chat bot),
Otherwise, fallback to the base64 encoding of images (to allow usage of the adapter via api)

/deploy-review

/deploy-review

/deploy-review

/deploy-review


Adding an optional name parameter in Parameter.serialize in order to make warnings more helpful

Description
I added an optional name Parameter in https://github.com/voyages-sncf-technologies/luigi/blob/master/luigi/parameter.py#L247 in order to improve warnings.
I also passed this new parameter in many place where Parameter.serialize is invoked (not all, only when possible).
Finally I updated existing tests and added new ones.
Motivation and Context
When this name parameter is passed to Parameter.serialize, warnings raised will now include the parameter name, helping to diagnose the issue.
This is especially helpful in https://github.com/spotify/luigi/blob/master/luigi/task.py#L473 this is called to validate luigi.cfg.
Have you tested this? If so, how?
I have included unit tests and I used the patched version in our own luigi pipelines.

Just to clarify, I added a different way of solving this, because I think this is a great idea, and I could have used it myself many times. But I think this implementation could be better, and that in the long run it saves time for everyone: Users, you (the contributor) and me (the maintainer).

Alright, this is a good suggestion as it will reduce the impact of this change.
However IHMO adding a new function slightly adds in complexity.
I'll update this PR tomorrow.

New version pushed. It is definitively cleaner I think.

Tested with:
tox -e py34-nonhdfs --run-command "python test/runtests.py -v test/task_test.py"

Can you fix the flake issue please? Then I think we can merge. :)

Done


Use Renovate instead of Dependabot

My initial motivation was that Renovate handles gradle version updates as well as dependency updates, which would make our gradle version update automation unnecessary (which is not working well anyways because the PRs it opens aren't triggering CI actions without closing/re-opening the PR).
But also, I tried Renovate out on my fork of this repo, and it found several gradle dependency updates that dependabot wasn't finding: https://github.com/trask/opentelemetry-java-examples/issues/11
A few other OpenTelemetry repos are using Renovate already, so it wouldn't require any new approvals (just need to ask TC to enable it on this repository).

this is done, thx @jack-berg!


feat(macOS): deterministically snapshot NSViews on any device

Deterministically snapshot NSViews on any device
Summary
This PR builds upon #412 but maintains compatibility with existing API-behaviour.  Additionally to fixing backingScaleFactor issues, it also fixes the color space issues discussed in #477. Therefore all relevant rendering parameters can be set in a deterministic way allowing macOS snapshot test to run on any device including CI.
In Detail
As far as I can tell from experimenting, the rendering of NSView is determined by its .size, .appearance .window.backingScaleFactor, and window.colorSpace. This PR tackles the later two and adds a GenericWindow subclass of NSWindow which can be configured with a specific backingScaleFactor and colorSpace. The .image snapshot strategy on NSView is extended to allow the caller to optionally set a specific NSAppearance and to render the view in a GenericWindow. This window can be configure to use CI compatible values (eg. backingScaleFactor: 1.0 and colorSpace: .genericRGB). There is even a handy preconfigured static instance GenericWindow.ci.
Added Tests
Two tests are added to showcase the CI-compatibility. These are the CI-compatible version of pre-existing macOS NSView tests:

testNSViewCICompatible
testNSViewWithLayerCICompatible

For passing tests see https://github.com/tillhainbach/swift-snapshot-testing/pull/3
Caveats/Gotchas
The current implementation for .image for NSView has side-effect on the view which are not undone. This means that the calling order for .image and .recursiveDescription strategy matters. I added a note to the doc comment.
Minor Fixes along the way
I noticed some test failures on my local machine that where:

related to light/dark mode setting on test machine. I refactor the failing tests to explicitly use .aqua (light mode) appearance (the one used for provided target snapshot)
related to number formatting using localised formatting (decimal separator in my case). I changed the number formatter to use the a . as the decimal separator.

Other
This PR adds an additional step to the GitHub actions which uploads any failing snapshot artefacts. This is great for debugging failures on CI.
Related PRs and Issues

closes #412
fixes issues with #477. Supporting SwiftUI, however, could be simplified to just pullback to NSView.
closes #428
closes #313
closes #305

PS: I left the WIP and intermediate commits to improve comprehensibility for review but will squash them once this PR is approved to reduce the noise.

What's the state of this? Is there any plan to getting this merged? Looks like there's no SwiftUI support on macOS yet. With Apple getting serious with SwiftUI on macOS now with Ventura (the new Settings app was written with SwiftUI it looks like), I'd love to see proper support for SwiftUI in this lib as well. Are there any blockers right now?

Are there any plans to get this merged?
For anyone finding and needing this before it is merged, I created a branch in fork which basically combines this PR as well as #477: https://github.com/Obbut/swift-snapshot-testing/tree/updated-swiftui-macos

If the comments from @stephencelis are blocking to get this merged, I'd be happy to create a new PR with that feedback implemented

If the comments from @stephencelis are blocking to get this merged, I'd be happy to create a new PR with that feedback implemented

Would be great if you can take over. I was wanting to address this but I can't find the time since I haven't been working on anything swift related 🥲.

@Obbut Did you ever get the time to look at this? These look like great changes


dyld: Library not loaded: @rpath/Alamofire.framework/Versions/A/Alamofire

I can not set framework to Target Dependencies, no Embedded framework to add.
Enviroment Xcode7. swift 2.0
pod file
source 'https://github.com/CocoaPods/Specs.git'
platform :osx, '10.10'
use_frameworks!

pod 'Alamofire', :git => 'https://github.com/Alamofire/Alamofire.git', :branch => 'swift-2.0'

error
dyld: Library not loaded: @rpath/Alamofire.framework/Versions/A/Alamofire
  Referenced from: /....../
  Reason: image not found

Seems like this is most likely an issue with CocoaPods at the moment. Please check out this issue for more information.


Build Optimizer breaks on gsap dependency

Bug Report or Feature Request (mark with an x)
- [ x ] bug report -> please search issues before submitting
- [  ] feature request

Command (mark with an x)
- [ ] new
- [ x ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions
Angular CLI: 6.1.2
Node: 8.9.4
OS: darwin x64
Angular: 6.1.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
Package                           Version

@angular-devkit/architect         0.6.8
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core              0.0.29
@angular-devkit/schematics        0.7.2
@angular/cli                      6.1.2
@ngtools/webpack                  6.0.8
@schematics/angular               0.7.2
@schematics/update                0.7.2
rxjs                              6.2.2
typescript                        2.9.2
webpack                           4.8.3
macOs High Sierra 10.13.2
Repro steps

ng serve --prod

https://github.com/lichunbin814/ngcli6WithGsapBuildError
The log given by the failure
Uncaught TypeError: Cannot set property '_autoActivated' of undefined
    at Object.zUnb (main.67da554f7ccc2d4026c6.js:1)
    at p (runtime.a66f828dca56eeb90e02.js:1)
    at Object.3 (main.67da554f7ccc2d4026c6.js:1)
    at p (runtime.a66f828dca56eeb90e02.js:1)
    at n (runtime.a66f828dca56eeb90e02.js:1)
    at Array.e [as push] (runtime.a66f828dca56eeb90e02.js:1)
    at main.67da554f7ccc2d4026c6.js:1

Desired functionality
exclude some node_module when I use buildOptimizer flag ,keep other files can be optimizations
Mention any other details that might be useful
it works on buildOptimizer:false

We currently do not have such functionality.

Do I have another solution to keep buildOptimzer:true ?

I have exactly the same issue !
Are there any news?

This would be a great feature to have, as buildOptimizer breaks one of my dependencies and I end up having to copy it to resources/ and include it via index.html, which is pretty ugly.

This just sounds like a bug in build optimizer. It should generally be safe to run on a library, so if it is breaking gsap, then we should look into why and fix that.

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.


TypeError encountered while using graphback generate command.

While using graphback to generate schema and resolvers for the below graphql file:
type Task {
  id: ID!
  version: Int
  title: String!
  description: String!
  status: TaskStatus
}

enum TaskStatus {
  OPEN
  ASSIGNED
  COMPLETE
}

type Query {
  allTasks(first: Int, after: String): [Task],
  getTask(id: ID!): Task
}

type Mutation {
  createTask(title: String!, description: String!, status: TaskStatus): Task
  updateTask(id: ID!, title: String, description: String, version: Int!, status: TaskStatus): Task
  deleteTask(id: ID!): ID
}

I encountered the error: TypeError: Cannot read property 'forEach' of undefined.
@wtrocki Can you please help me out?

Graphback currently does not support enum, hence the issue. Will be adding it for version 0.6.0 roadmap

Yeah just read issue #188 .

@Lavanyagaur22 I just hit the same. @Lavanyagaur22 you can fix it by PR against that branch to replace that with strings and other required changes you want to introduce.

Closing this. Issue #191 is tracking it


AxesSubplot issue

I am using basemap via conda environment. When i want to do a simple plot like:
from mpl_toolkits.basemap import Basemap
import matplotlib.pyplot as plt
import numpy as np

my_map = Basemap(projection='ortho', lat_0=50, lon_0=-100,
              resolution='l', area_thresh=1000.0)

my_map.drawcoastlines()
plt.show()

It throws the error
AttributeError: 'AxesSubplot' object has no attribute 'get_axis_bgcolor'
I've read in previous posts that this issue was well known and fixed, but i cannot make it work.
What could I do?
(to install basemap i've followed these instructions here )

I believe you are getting a really outdated basemap from defaults. Try the conda-forge version:
$ conda install --channel conda-forge basemap basemap-data-hires

note that in conda-forge the high resolution data is a separate package, if you don't need it you can install a the slimmer version with just conda install --channel conda-forge basemap.

That was the problem! Thank you very much. I was using version 1.0.7


Screen sharing plugin not downloading on Ubuntu 15.10

When making a call from version 1.1.0 on Ubuntu 15.10, we attempted to download the screen sharing plugin. When clicking screen share, the dialogue appears containing a 'download plugin' button. Clicking on the button yields no result, and we cannot see the console to troubleshoot this issue further.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/31518001-screen-sharing-plugin-not-downloading-on-ubuntu-15-10?utm_campaign=plugin&utm_content=tracker%2F19476668&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F19476668&utm_medium=issues&utm_source=github).

We don't have support for screen sharing in Electron yet.

Duplicated of https://github.com/RocketChat/Rocket.Chat.Electron/issues/65


A simple refactoring removing an unnecessary variable

A simple refactoring.
This refactoring is based on similar code fragments in this repository, as described below.
https://github.com/alibaba/druid/blob/b73e55f4983ef4f0ae933770bb7fcbe95f7210c2/src/main/java/com/alibaba/druid/sql/ast/statement/SQLUpdateStatement.java#L249-L255
https://github.com/alibaba/druid/blob/b73e55f4983ef4f0ae933770bb7fcbe95f7210c2/src/main/java/com/alibaba/druid/sql/ast/statement/SQLDeleteStatement.java#L258-L264
Masayuki, Yoshiki, and Shinji

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

代码冲突太大，以后再优化代码细节。


Fix session test

Questions
Answers

Description?
The core PHP session test of PrestaShop checks if the sessions directory is writable, which does not always work as expected. Combined with an open_basedir configured without the session.save_path, PHP sessions are still working as intended, but the test_sessions function fails. In such a case, the One Click Upgrade module will fail checking its prerequisites in an attempt to make an upgrade. This fixes the issue on all old cores, because it implements the check inside the module.

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes https://github.com/PrestaShop/PrestaShop/issues/30658

Sponsor company

How to test?

Original solution provided by @alexandre-profileo in https://github.com/PrestaShop/PrestaShop/pull/31053, which fixes the issue in the core itself.

I tested it on our server with Plesk, having the same issue, and the issue is successfully solved. ✅

Test on Plesk install having the same issue.
Before

After
✅ No error

thanks @Hlavtox


Undeploy should not affect the state of referenced applications

Currently, during undeployment, the app is "fully stopped" including stopping all applications referenced by the app being undeployed.  Undeployment should not affect the state of other BizTalk applications.  The controlbiztalkapp NAnt task should accept a comma-separated combination of enum flags for the app start and stop options.
This work item was migrated from CodePlex
CodePlex work item ID: '3212'
Assigned to: 'tfabraham'
Vote count: '0'

[UnknownUser@10/8/2008]
Resolved with changeset 16202.

[UnknownUser@2/21/2013]

[UnknownUser@5/16/2013]


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

README.md

docs(README): update from template

Codecov Report

Merging #481 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #481   +/-   ##
=======================================
  Coverage   95.12%   95.12%
=======================================
  Files           1        1
  Lines          41       41
=======================================
  Hits           39       39
  Misses          2        2

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 3bf2a0e...1f60b19. Read the comment docs.

Coverage remained the same at 90.909% when pulling 1f60b1902d279958f7c23a17c66ba081443c900b on template-sync-1 into 3bf2a0ee3f5f35ea593453edfda1abdb9869a382 on master.


[Feature] Leverage the Geolocation API

Prerequisites

[ ] Designs for where / how this button should exists, and what the tooltip should look like

User Story
As a user
I want to allow RBB to use my IP location
So I can view businesses near me
Acceptance Criteria

[ ] Leverage the Geolocation API in order to prompt user allowing RBB to get their location
[ ] Use geolocation data to set the default search results based on that data
[ ] There is a button near the filters that will trigger the Geolocation API functionality asking for user location.
[ ] There is a tooltip that appears when hovering the button, which explains why we are getting your location
[ ] Results that are shown are accurate based on the user's location

Describe the solution you'd like
We need to add a button within the filters that will trigger the Geolocation API to get the users location, and update the search results based on that location.
We will need to be sure that the Geolocation data that is passed to the API is a latitude and longitude.

Looking good to me, I don't think I have much more to add. Just needs designs and I recon this can get started asap :)

if (navigator.geolocation) {
navigator.geolocation.getCurrentPosition(function(position) {/* do something */})
}

Hi, can I be assigned to this task?

@sonAndrew - apologies for the delay! Thanks for picking this up!


Handle batchable lists of length 0

TL;DR
Batchable lists of length 0 should produce empty lists
Type

[ ] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/flyteorg/flyte/issues/
Follow-up issue
NA
OR
https://github.com/flyteorg/flyte/issues/

This python 3.11 on windows failure is not related. Will investigate separately.


Is there currently a way to define how images are presented in zgui?

Hi!
Currently I am trying to implement zooming into a project that draws textures using zgui.
However, when zooming, textures become very blurry.

Is there a way to, either when drawing using zgui.image() or draw_list.addImage(), use point scaling when drawing the images to keep crisp pixels?
Thanks for any info!

Hi,
Using nearest filtering is actually not supported in imgui, see here: https://github.com/ocornut/imgui/issues/5118
"At a high level there are two strategies:
A) Use ImGuiDrawList::AddCallback to insert a callback to change the texture filtering to nearest neighbor, draw your image, and then call AddCallback(ImDrawCallback_ResetRenderState) to reset the state.
B) Use ImGuiDrawList::AddCallback to manually draw your image with nearest neighbor. (Being sure not to affect global state or use ImDrawCallback_ResetRenderState again to reset it.)"
We will need to expose ImGuiDrawList::AddCallback and then you would have to draw your image with nearest filtering manually.
As an alternative, you could draw those images yourself (not using zgui but just wgpu) onto zgui window.
What do you think?

Yeah, that's pretty much the same conclusion I came to last night. I looked at drawing the images outside of zgui, but I feel like it would end up being a mess trying to clip the image to the child window for the canvas with scroll bars and all of that, and that keeping the image rendering within zgui would be best.
I'll look at exposing ImGuiDrawList::AddCallback and try to get it working in my project and then I'll get you a PR.
Thanks!

You will need to bind your custom rendering pipeline and sampler with nearest filtering and the issue a draw call.

Would it be any simpler for me to somehow just render all zgui as nearest neighbor through zgpu? I'm a bit confused that I didn't run into this issue on the previous iteration of Pixi, I suppose upaya renders all imgui stuff with nearest neighbor...

Try to change filtering method here:
https://github.com/michal-z/zig-gamedev/blob/main/libs/zgui/libs/imgui/imgui_impl_wgpu.cpp#L534

This works!

This also affect text rendering, right? Does it look nice?

For me, it looks great, but I'm using a "pixely" font, so I would honestly prefer this font be nearest neighbor as well.

Looks very nice indeed! I think we should have an option to switch between samplers.

I'm not sure how to accomplish that without editing imgui_impl_wgpu.cpp, would you like me to still look into the callback route? Or do you have an idea to provide that option?

I will think about it some more - the simplest solution would be to provide an option in zgui.backend.init(). I will solve this issue next week.

@foxnne I've added zgui.backend.initWithConfig() which lets you select nearest texture filtering mode. Please take a look at gui_test_wgpu demo how to use it.

Fantastic, thank you so much for adding this!

@foxnne Can we close this issue?

Oh, my bad, closing!


custom dbus name for StatusNotifierWatcher

This is for flatpak packaging. If we own org.kde.StatusNotifierItem-2-1, it will be tricky: it's not guaranteed that my app will have PID 2.
As workarounds from chromium, instead we register a existing dbus name we are using, and everything works fine.

To address this, just use the default bus name we were given on
initially connecting to the bus.  This violates the spec, but there's
actually no consequence for doing this.

I have problems with flatpak too and probably related to this.
I don't have any problem when I add "--socket=session-bus" to finish-args. But flathub doesn't like "I can talk anything" permission.
When I removed "--socket=session-bus" and only "--talk-name=org.kde.StatusNotifierWatcher" left, I got D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (org.freedesktop.DBus.Error.ServiceUnknown)

I have problems with flatpak too and probably related to this.
I don't have any problem when I add "--socket=session-bus" to finish-args. But flathub doesn't like "I can talk anything" permission.
When I removed "--socket=session-bus" and only "--talk-name=org.kde.StatusNotifierWatcher" left, I got D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (org.freedesktop.DBus.Error.ServiceUnknown)

did you try https://github.com/waylyrics/ksni/tree/feat-custom-dbus-name

0.2.2 update and run_without_dbus_name() solved my problem.


bugfix: fix can't set quota with ".*"

Ⅰ. Describe what this PR did
fix can't set quota with ".*", and haven't set quota id.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews
Signed-off-by: Rudy Zhang<EMAIL_ADDRESS>

Just confirm，do we need to update the related documentation https://github.com/alibaba/pouch/blob/master/docs/features/pouch_with_diskquota.md ? @rudyfly @fuweid


Update locality-and-replication-zones.md

There's no node in the tutorial with port 54942 making the query fail
cockroach sql --insecure --host=<IP_ADDRESS>:54942 --execute="SHOW RANGES FROM TABLE intro.mytable;" --execute="SHOW RANGES FROM TABLE startrek.episodes;" --execute="SHOW RANGES FROM TABLE startrek.quotes;"
Error: cannot dial server.
Is the server running?
If the server is running, check --host client-side and --advertise server-side.

dial tcp <IP_ADDRESS>:54942: connect: connection refused
Failed running "sql"

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/3b88d5340fe8c7f1eb8e0feb8e2a49ebf689fc11/
Edited pages:

v19.2/training/locality-and-replication-zones.md

Identical fix has already been pushed to master.

(change came in on PR 6233)


DeepMimic.py creates a window which is soon disappears

After I run python DeepMimic.py --arg_file args/run_humanoid3d_spinkick_args.txt, it first prints this warning messages:
C:\Users\KozinV\Anaconda3\envs\DeepMimicEnv\lib\site-packages\tensorflow\python\framework\dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.                                                                                _np_qint8 = np.dtype([("qint8", np.int8, 1)])                                                                         C:\Users\KozinV\Anaconda3\envs\DeepMimicEnv\lib\site-packages\tensorflow\python\framework\dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.                                                                                _np_quint8 = np.dtype([("quint8", np.uint8, 1)])                                                                      C:\Users\KozinV\Anaconda3\envs\DeepMimicEnv\lib\site-packages\tensorflow\python\framework\dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.                                                                                _np_qint16 = np.dtype([("qint16", np.int16, 1)])                                                                      C:\Users\KozinV\Anaconda3\envs\DeepMimicEnv\lib\site-packages\tensorflow\python\framework\dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.                                                                                _np_quint16 = np.dtype([("quint16", np.uint16, 1)])                                                                   C:\Users\KozinV\Anaconda3\envs\DeepMimicEnv\lib\site-packages\tensorflow\python\framework\dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.                                                                                _np_qint32 = np.dtype([("qint32", np.int32, 1)])                                                                      C:\Users\KozinV\Anaconda3\envs\DeepMimicEnv\lib\site-packages\tensorflow\python\framework\dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.                                                                                np_resource = np.dtype([("resource", np.ubyte, 1)])                                                                   C:\Users\KozinV\Anaconda3\envs\DeepMimicEnv\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:541: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.                                                                                _np_qint8 = np.dtype([("qint8", np.int8, 1)])                                                                         C:\Users\KozinV\Anaconda3\envs\DeepMimicEnv\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:542: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.                                                                                _np_quint8 = np.dtype([("quint8", np.uint8, 1)])                                                                      C:\Users\KozinV\Anaconda3\envs\DeepMimicEnv\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:543: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.                                                                                _np_qint16 = np.dtype([("qint16", np.int16, 1)])                                                                      C:\Users\KozinV\Anaconda3\envs\DeepMimicEnv\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:544: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.                                                                                _np_quint16 = np.dtype([("quint16", np.uint16, 1)])                                                                   C:\Users\KozinV\Anaconda3\envs\DeepMimicEnv\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:545: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.                                                                                _np_qint32 = np.dtype([("qint32", np.int32, 1)])                                                                      C:\Users\KozinV\Anaconda3\envs\DeepMimicEnv\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:550: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.                                                                                np_resource = np.dtype([("resource", np.ubyte, 1)])                                                                   WARNING: Logging before flag parsing goes to stderr.                                                                    W0821 16:30:38.340782  5840 lazy_loader.py:50]                                                                          The TensorFlow contrib module will not be included in TensorFlow 2.0.                                                   For more information, please see:                                                                                * https://github.com/tensorflow/community/blob/master/rfcs/20180907-contrib-sunset.md                                   * https://github.com/tensorflow/addons                                                                                * https://github.com/tensorflow/io (for I/O related ops)                                                              If you depend on functionality not listed there, please file an issue.                                                                                Renderer: Intel(R) UHD Graphics 630                                                                                OpenGL version supported 3.2.0 - Build <IP_ADDRESS>11                                                                   Compiling shader: data/shaders/Mesh_VS.glsl                                                                             Compiling shader: data/shaders/VertColor_PS.glsl                                                                        Compiling shader: data/shaders/FullScreenQuad_VS.glsl                                                                   Compiling shader: data/shaders/DownSample_PS.glsl                                                                       Compiling shader: data/shaders/Mesh_VS.glsl                                                                             Compiling shader: data/shaders/DownSample_PS.glsl
then it opens the window for half a second

, immediately closes the window and finally finishes running without any errors.
I expected that this window will not disappear and will show me a spinkicking humanoid.
My system is Windows 10, I built Bullet 2.87 and DeepMimicCore with VS2017 using NuGet packages "nupengl.core.<IP_ADDRESS>" and "glew.<IP_ADDRESS>".
Would be wonderful to know what is this problem about.

I had the exact issue. After digging into it I isolated the problem and found that attempting to instantiate variable of type cRenderState would crash the program. Issue was that glGenVertexArrays function was not correctly initialised, so it was a null pointer. After googling around, I found that adding the line 'glewExperimental = GL_TRUE;' before glewInit() solves this problem, but not sure with what consequences. Anyway, in DrawUtil.cpp, my cDrawUtil::InitDrawUtil() function looks like this:
`void cDrawUtil::InitDrawUtil()
{
glewExperimental = GL_TRUE;
glewInit();
const GLubyte* renderer = glGetString(GL_RENDERER); // get renderer string
const GLubyte* version = glGetString(GL_VERSION); // version as a string
printf("Renderer: %s\n", renderer);
printf("OpenGL version supported %s\n", version);
    ....

`
and it works for me now.

I also have that problem.... And i found the console window went wrong around this
"_DeepMimicCore.cDeepMimicCore_Reshape(self, w, h)", which is located in the deepmimiccore.py.
And i'm just a beginner and have no idea what went wrong. Does any body can help me :)

I had the exact issue. After digging into it I isolated the problem and found that attempting to instantiate variable of type cRenderState would crash the program. Issue was that glGenVertexArrays function was not correctly initialised, so it was a null pointer. After googling around, I found that adding the line 'glewExperimental = GL_TRUE;' before glewInit() solves this problem, but not sure with what consequences. Anyway, in DrawUtil.cpp, my cDrawUtil::InitDrawUtil() function looks like this:
void cDrawUtil::InitDrawUtil()
{
	glewExperimental = GL_TRUE;   //New line
	glewInit();

	const GLubyte* renderer = glGetString(GL_RENDERER); // get renderer string
	const GLubyte* version = glGetString(GL_VERSION); // version as a string
	printf("Renderer: %s\n", renderer);
	printf("OpenGL version supported %s\n", version);
        ....

and it works for me now.

thank u sooooooooooooooooooooo much !!!!


How to disable packaging by default will have a *.css problem

My current configuration items are as follows

Do you mean that you want to inline the css content?

Yes, it seems that this will set the default style automatically. I need to remove these default CSS styles.

this option may be helpful: https://rsbuild.dev/guide/basic/css-usage#inline-css-files

did this problem get solved? if you have any questions, please let me know.

I'm sorry, I saw the reply again yesterday and went to try it, and it didn't fix the CSS issue introduced by default. Sorry I forgot to reply

Could you provide a minimal reproduction repository? I would like to understand your scenario better, as I'm not fully clear on the problem.

Could you provide a minimal reproduction repository? I would like to understand your scenario better, as I'm not fully clear on the problem.

https://github.com/h7ml/juejin-book-downloader
My repo is here, troublesome

But I'll add the css file
createShadowRootUI({
  styles: chrome.runtime.getURL('static/css/content-script.css'),
  render({ root }) {
    createRoot(root).render(<App />);
  },
});

The issue has not been resolved

because the modal is a portal element, it's created under document.body by default. createShadowRootUI.styles will be injected under the shadow root, and the styles are isolated.
so, you need to inject the style into the document.head directly, or set the container of the modal to the shadow DOM via props getContainer.

Thank you very much for your patience

const linkEl = document.createElement('link');
linkEl.rel = 'stylesheet';
linkEl.href = chrome.runtime.getURL('static/css/content-script.css');
document.head.appendChild(linkEl);

The above code can't be used directly in my juejin.tsx file, which will freeze the whole UI interface. I tried to use the CDN resource below and it also got stuck. I can't figure out the cause of the freeze at the moment.
const linkEl = document.createElement('link');
linkEl.rel = 'stylesheet';
linkEl.href = 'https://cdn.tailwindcss.com/3.4.5';
document.head.appendChild(linkEl);

make sure the snippet is executed ONCE. did you place it in a callback that may be executed multiple times

Yes. I'm sure he only inserted it once

could you push your changes to a new branch?

you can add some debugger instructions or alert() calls to block the JS thread, the MutationObserver callback is falling into a loop
https://cdn.tailwindcss.com/3.4.5 is a js file, please replace it with chrome.runtime.getURL('static/css/content-script.css')
make sure the css is accessible in web_accessible_resources

as I said, https://cdn.tailwindcss.com/ is NOT a css file, you need to replace it with chrome.runtime.getURL('static/css/content-script.css')

make sure the css is accessible in web_accessible_resources

make sure the css is accessible in web_accessible_resources

Yes, this can be ensured.

https://github.com/tmkx/webx-kit/blob/4634f9d433883c365f728ef206b9f9ec85940bb7/examples/react/src/manifest.ts#L18-L23

thank you for trying WebX-Kit. however, I will delete this issue due to potential copyright concerns.


[Typescript] Added TypeText declaration to the exports file

Closes #30851.

[x] I have followed (at least) the PR section of the contributing guide.

Thanks for your work! Could you also export TypeAction and TypeBackground for consistency?


formatting::source_lines context bug

Something like that?

yeah something like it; I don't think .nth(target_line) will work b/c we'll have already skipped skipped_lines, so target_line usize won't point to the correct line anymore. But I'll figure it out

Something like that?

yeah something like it; I don't think .nth(target_line) will work b/c we'll have already skipped skipped_lines, so target_line usize won't point to the correct line anymore. But I'll figure it out

The example was three different iterators, and then combining them together at the end.

The example was three different iterators, and then combining them together at the end.

f540c8a9


Errno::ENOENT

When I build Mixpanel via Rome, I get ENOENT.
The project in this directory is just a freshly-created Xcode template project.
Versions
Xcode Version 6.4 (6E35b)
OSX 10.10.4 (14E46)
Stack
   CocoaPods : 0.38.0
        Ruby : ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin14]
    RubyGems : 2.0.14
        Host : Mac OS X 10.10.4 (14E46)
       Xcode : 6.4 (6E35b)
         Git : git version 2.3.2 (Apple Git-55)
Ruby lib dir : /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @ 5d6927ee9e98868c4e7919eca94440e7648d5f4e

Plugins
cocoapods-plugins : 0.4.2
cocoapods-rome    : 0.1.0
cocoapods-stats   : 0.5.3
cocoapods-trunk   : 0.6.1
cocoapods-try     : 0.4.5

Podfile
platform :ios, '8.2'
use_frameworks!

plugin 'cocoapods-rome'

pod 'Mixpanel'

Error
Errno::ENOENT - No such file or directory - /Users/drew/Code/Mixpanel-rome/build/Mixpanel/Mixpanel
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1552:in `stat'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1552:in `block in fu_each_src_dest'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1568:in `fu_each_src_dest0'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1550:in `fu_each_src_dest'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:508:in `mv'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-rome-0.1.0/lib/cocoapods-rome/post_install.rb:27:in `block (4 levels) in <top (required)>'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-rome-0.1.0/lib/cocoapods-rome/post_install.rb:22:in `each'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-rome-0.1.0/lib/cocoapods-rome/post_install.rb:22:in `block (3 levels) in <top (required)>'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-rome-0.1.0/lib/cocoapods-rome/post_install.rb:17:in `each'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-rome-0.1.0/lib/cocoapods-rome/post_install.rb:17:in `block (2 levels) in <top (required)>'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-rome-0.1.0/lib/cocoapods-rome/post_install.rb:15:in `chdir'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-rome-0.1.0/lib/cocoapods-rome/post_install.rb:15:in `block in <top (required)>'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/hooks_manager.rb:117:in `call'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/hooks_manager.rb:117:in `block (3 levels) in run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/user_interface.rb:140:in `message'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/hooks_manager.rb:111:in `block (2 levels) in run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/hooks_manager.rb:109:in `each'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/hooks_manager.rb:109:in `block in run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/user_interface.rb:140:in `message'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/hooks_manager.rb:108:in `run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/installer.rb:448:in `run_plugins_post_install_hooks'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/installer.rb:440:in `perform_post_install_actions'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/installer.rb:111:in `install!'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/command/project.rb:71:in `run_install_with_update'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/command/project.rb:101:in `run'
/Library/Ruby/Gems/2.0.0/gems/claide-0.9.1/lib/claide/command.rb:312:in `run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/lib/cocoapods/command.rb:48:in `run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.0/bin/pod:44:in `<top (required)>'
/usr/bin/pod:23:in `load'
/usr/bin/pod:23:in `<main>'

This was possibly caused by #10, but there's also now slightly better logging for the case where lipo fails. In any case, this works now with the new 0.2.0 version that was just released.


Add --component to build a single component.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
Got a bit tired of constantly commenting out components in the manifest while fixing individual components. You can now pass in --component and it will build just that component, skipping all the others. The build output also shows the last failure and gives a copy-paste to rebuild the last component that failed.
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I like the intent here but I think we need to clarify that this is to "Rebuild" a single component.  Right now build.sh scripts rely on their dependencies being built in-order before them and stored in maven local.  This was a trade-off that was made over each build script cloning and building their deps so that we can guarantee all components are built from the same unreleased version.

I like the intent here but I think we need to clarify that this is to "Rebuild" a single component. Right now build.sh scripts rely on their dependencies being built in-order before them and stored in maven local. This was a trade-off that was made over each build script cloning and building their deps so that we can guarantee all components are built from the same unreleased version.

Are you suggesting I adjust wording, or do you think more is needed, such as renaming the option?

I like the intent here but I think we need to clarify that this is to "Rebuild" a single component. Right now build.sh scripts rely on their dependencies being built in-order before them and stored in maven local. This was a trade-off that was made over each build script cloning and building their deps so that we can guarantee all components are built from the same unreleased version.

Are you suggesting I adjust wording, or do you think more is needed, such as renaming the option?

I am suggesting adjusting the wording in the README, the option name is ok.


Pin version of docker-py image

Parallel change to #1360, for the 1.0 branch.
The file has changed a lot (including its name) on master, so a merge of this change to master would be equivalent to re-implementing #1360.

This will still need to be merged into master, since master must always be
strictly ahead of 1.0. If you merge #1360 first then merging this will
simply entail throwing away any changes.


automatically ignore the controller or support @ignore

Following the Angular2 migration guidelines, I wrote this es6 code :
'use strict';

/**
 * @ngdoc directive
 * @memberof example.layout
 * @name layoutFooter
 * @description
 *  Global footer for the application
 */
angular.module('example.layout')
    .directive('layoutFooter', () => {

        /**
         * @namespace
         * @ignore
         */
        class LayoutFooter {

            constructor() {
                // TODO
            }
        }

        return {
            restrict: 'EA',
            scope: {},
            bindToController: {},
            controller: LayoutFooter,
            controllerAs: 'layoutFooter',
            templateUrl: 'layout/layout-footer_component.html'
        };
    });

For now, angular-jsdoc create a new page for the controller classe, with an undefined module. I tried everything, but nothing seems to work on this element.

I cannot answer this. angular-jsdoc follows JSDoc3 and I don't think JSDoc 3 understands ES6 syntax, AFAIK

Jsdoc 3 does support ES6 class : http://usejsdoc.org/howto-es2015-classes.html
https://github.com/jsdoc3/jsdoc/issues/555
But, even if my example is in ES6, if you write this with es5 (by simply using function instead of class), the problem is the same.

I can look into adding support for @ignore @noelmace

PR & Issues spring-cleaning: I no longer face the problem, and the discussion on this topic is no longer active, so I close this issue / PR. Feel free to reopen it if necessary.


Any example on creating custom grid content?

[X] Question
[ ] Bug
[ ] Improvement

So my question is if there is any demo where another react components are rendered inside the ReactGridLayout? Are there any open source codes out there I could look at?
I am stuck with this issue and cannot figure out what the proper way is to add components inside the grid and make them fit into their cell.
Thank you.

May I know how did you create Custom grid content ?


Correct installation test in appveyor

It turned out that the appveyor configuration we had didn't try installing, even though we wanted to...

+1

Merged.
I'd suggest you rebase #1758 on top of a fresh master.


Better Fluid Support!!!

Issue description:
First, I'm starting to use a lot of fluids and it's getting really old having to run all the way back to my stationary fluid monitor EVERY SINGLE TIME I want to know how much fluid I have in my system.  It's MOST DEFINITLY getting in the way of debugging my setups when something's going wrong (or even knowing that something's going wrong in the first place)!  Could you PLEASE implement a wireless fluid monitor?!?  Honestly, I've no idea why you don't have one already!
Second, your fluid monitor is great and all that, but besides being stationary, it's also completely inert.  Want a bucket of water, milk, or anything else?    Same goes for emptying a bucket as well!  The fluid monitor is, in my opinion, the least useful block in this mod because it does TOO LITTLE.  You can input and remove items from the regular item grid, would you PLEASE enable the fluid grid to do the same!!!
Third, if you're going to implement points one and two, then why not let the wireless fluid monitor empty and fill buckets as well.  And if you're going to do that, you might as well create a wireless bucket that can tap directly into the system (in addition to letting the wireless fluid monitor fill buckets, of course)!!!
Fourth, don't forget about bucketless fluid support!!!  In fact point three should solve this automatically, since if you implemented a wireless bucket and made it so that you could fill it, i.e. set it's fluid type, from the (wireless) fluid monitor, that would include otherwise bucketless fluids, giving you a bucket to use when setting fluid selection fields and solve the whole issue!!!  Or you could just use regular buckets filled from the (wireless) fluid monitor, if it's possible for you to provide support for buckets with fluid from other mods that don't provide buckets themselves.
If you feel that wireless buckets are too OP (though I'd have to ask WHY, since it just giving you the same access to your fluids that you already have with your items), you could still solve the bucketless fluid issue by creating a special 'dummy' RS bucket that can be set from the wireless fluid monitor (if you don't include wireless support...I'm going to get really grumpy and tired running back and forth constantly) that's just for setting fluid selection fields and can't actually place any fluids in the world itself.

Minecraft: 1.10.2
Forge:2185
Refined Storage: 1.2.12

After my lastest update to first post of this issue, I'm really wondering if I should I close my other thread on Bucketless Fluid Support...

You sound really rude.

Sorry, that was not my intention. Text is a poor medium for conveying emotion...  I will admit that the impetus for writing this post in the first place was frustration, which may have come across...poorly.  Do you want me to rewrite my first post (in the morning)?

Please do.

@7OOTnegaTerces While this is definitely more entertaining than a bug report I am guessing your Fluid Grid doesn't take too kindly to be called a USELESS STATIONARY MONITOR as mine gives me buckets of fluid for the asking. Perhaps you should try a different approach.
Here by accident but couldn't resist.

Could you PLEASE implement a wireless fluid monitor?!? Honestly, I've no idea why you don't have one already!

The 1.11 version will have a wireless fluid grid, in fact, it's already implemented and completed.

Second, your fluid monitor is great and all that, but besides being stationary, it's also completely inert. Want a bucket of water, milk, or anything else?

False.
https://refinedstorage.raoulvdberge.com/wiki/fluid-grid
"To insert a fluid, players can SHIFT click or just click in a filled fluid container."
"Players can extract the fluid by clicking on it. The Fluid Grid will then fill a bucket with the selected fluid."
"Refined Storage will first search an empty bucket from your storage system. If none is found, a bucket will be searched in your inventory."

Third, if you're going to implement points one and two, then why not let the wireless fluid monitor empty and fill buckets as well.

That already works in 1.11, as I said.

And if you're going to do that, you might as well create a wireless bucket that can tap directly into the system (in addition to letting the wireless fluid monitor fill buckets, of course)!!!

No!!!

Fourth, don't forget about bucketless fluid support!!!

I won't!!!

If you feel that wireless buckets are too OP (though I'd have to ask WHY, since it just giving you the same access to your fluids that you already have with your items), you could still solve the bucketless fluid issue by creating a special 'dummy' RS bucket that can be set from the wireless fluid monitor

Sorry, but this idea is dumb.
In conclusion: 85% / 90% of your issue report is fake news. Alternative facts. Literally Trump.


[bug] API sometimes responds with an empty response

Seems to be an issue with the cache.

Hi evilarceus!
I was coming to report this exact same issue. I haven't been able to identify a pattern, it's completely random. I can even loop 10 times in a php script for 10 albums and get 0, 3, 9, or 10 results. Kinda weird.
I'm not helping much, I haven't dig into the source code so far to try to understand the root cause. Compared to the previous API, I like how the results include much more parameters, it's very handy!

Was this the intermittent 500s? I was getting that too but haven't checked since Saturday.