Error on pip install

First of all, thank you for this port. Turf is a simple great package for geo processing.
I get the following when I try to install:
pip install --no-cache-dir pyturf
Collecting pyturf
  Downloading pyturf-0.6.0.tar.gz (36 kB)
    ERROR: Command errored out with exit status 1:
     command: /usr/local/miniconda3/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/jb/pflpzw4d0h75qsrd23z_t_0r0000gn/T/pip-install-kn0lrqax/pyturf_4a70855c9ede4d46befbd00fa835dc51/setup.py'"'"'; __file__='"'"'/private/var/folders/jb/pflpzw4d0h75qsrd23z_t_0r0000gn/T/pip-install-kn0lrqax/pyturf_4a70855c9ede4d46befbd00fa835dc51/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /private/var/folders/jb/pflpzw4d0h75qsrd23z_t_0r0000gn/T/pip-pip-egg-info-85im_2as
         cwd: /private/var/folders/jb/pflpzw4d0h75qsrd23z_t_0r0000gn/T/pip-install-kn0lrqax/pyturf_4a70855c9ede4d46befbd00fa835dc51/
    Complete output (34 lines):
    Traceback (most recent call last):
      File "/private/var/folders/jb/pflpzw4d0h75qsrd23z_t_0r0000gn/T/pip-install-kn0lrqax/pyturf_4a70855c9ede4d46befbd00fa835dc51/setup.py", line 8, in <module>
        __version__ = os.environ["GITHUB_REF"].split("/")[-1]
      File "/usr/local/miniconda3/lib/python3.7/os.py", line 678, in __getitem__
        raise KeyError(key) from None
    KeyError: 'GITHUB_REF'

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/private/var/folders/jb/pflpzw4d0h75qsrd23z_t_0r0000gn/T/pip-install-kn0lrqax/pyturf_4a70855c9ede4d46befbd00fa835dc51/setup.py", line 11, in <module>
        from turf.version import __version__
      File "/private/var/folders/jb/pflpzw4d0h75qsrd23z_t_0r0000gn/T/pip-install-kn0lrqax/pyturf_4a70855c9ede4d46befbd00fa835dc51/turf/__init__.py", line 6, in <module>
        from turf.boolean_disjoint import boolean_disjoint
      File "/private/var/folders/jb/pflpzw4d0h75qsrd23z_t_0r0000gn/T/pip-install-kn0lrqax/pyturf_4a70855c9ede4d46befbd00fa835dc51/turf/boolean_disjoint/__init__.py", line 1, in <module>
        from turf.boolean_disjoint._boolean_disjoint import boolean_disjoint
      File "/private/var/folders/jb/pflpzw4d0h75qsrd23z_t_0r0000gn/T/pip-install-kn0lrqax/pyturf_4a70855c9ede4d46befbd00fa835dc51/turf/boolean_disjoint/_boolean_disjoint.py", line 18, in <module>
        from turf.line_intersect import line_intersect
      File "/private/var/folders/jb/pflpzw4d0h75qsrd23z_t_0r0000gn/T/pip-install-kn0lrqax/pyturf_4a70855c9ede4d46befbd00fa835dc51/turf/line_intersect/__init__.py", line 1, in <module>
        from turf.line_intersect._line_intersect import line_intersect
      File "/private/var/folders/jb/pflpzw4d0h75qsrd23z_t_0r0000gn/T/pip-install-kn0lrqax/pyturf_4a70855c9ede4d46befbd00fa835dc51/turf/line_intersect/_line_intersect.py", line 4, in <module>
        from rtree import index
      File "/usr/local/miniconda3/lib/python3.7/site-packages/rtree/__init__.py", line 9, in <module>
        from .index import Rtree, Index  # noqa
      File "/usr/local/miniconda3/lib/python3.7/site-packages/rtree/index.py", line 6, in <module>
        from . import core
      File "/usr/local/miniconda3/lib/python3.7/site-packages/rtree/core.py", line 77, in <module>
        rt.Error_GetLastErrorNum.restype = ctypes.c_int
      File "/usr/local/miniconda3/lib/python3.7/ctypes/__init__.py", line 369, in __getattr__
        func = self.__getitem__(name)
      File "/usr/local/miniconda3/lib/python3.7/ctypes/__init__.py", line 374, in __getitem__
        func = self._FuncPtr((name_or_ordinal, self))
    AttributeError: dlsym(RTLD_DEFAULT, Error_GetLastErrorNum): symbol not found
    ----------------------------------------
WARNING: Discarding https://files.pythonhosted.org/packages/cc/78/aed4022347342291bb38561ebc7dfc1468f1b625970387a3aacc23734f31/pyturf-0.6.0.tar.gz#sha256=23b3ff2e42105da357416a4c2e92c3573d609d6c91351171612bfed180c49a00 (from https://pypi.org/simple/pyturf/) (requires-python:>=3.5). Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
  Downloading pyturf-0.5.0.tar.gz (26 kB)
Requirement already satisfied: numpy in /usr/local/miniconda3/lib/python3.7/site-packages (from pyturf) (1.19.5)
Building wheels for collected packages: pyturf
  Building wheel for pyturf (setup.py) ... done
  Created wheel for pyturf: filename=pyturf-0.5.0-py3-none-any.whl size=39727 sha256=ff99edb80862be517897f0cc87e0e36cb932f724245c1db932cd8c5e75114b88
  Stored in directory: /private/var/folders/jb/pflpzw4d0h75qsrd23z_t_0r0000gn/T/pip-ephem-wheel-cache-xkq8xcsk/wheels/d6/6a/2f/86f0c8ed86354a669c0b26944fd744b5f5e4fa0af134312c56
Successfully built pyturf
Installing collected packages: pyturf
Successfully installed pyturf-0.5.0

On another environment, it installed OK but I had to install required packages (numpy and rtree) manually before pip could go through.
Best regards
Pierre

Thanks, I will have a look.

Thanks, I will have a look.

I have the same issue. MacOs M1
Collecting pyturf==0.6.2
  Using cached pyturf-0.6.2.tar.gz (36 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [25 lines of output]
      Traceback (most recent call last):
        File "/private/var/folders/_w/m38196x96cs9ptvv1j0srlp80000gp/T/pip-install-2p137s4u/pyturf_a220078a7cba4d4cbda8a548c661cb04/setup.py", line 8, in <module>
          __version__ = os.environ["GITHUB_REF"].split("/")[-1]
        File<EMAIL_ADDRESS>line 680, in __getitem__
          raise KeyError(key) from None
      KeyError: 'GITHUB_REF'

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/private/var/folders/_w/m38196x96cs9ptvv1j0srlp80000gp/T/pip-install-2p137s4u/pyturf_a220078a7cba4d4cbda8a548c661cb04/setup.py", line 11, in <module>
          from turf.version import __version__
        File "/private/var/folders/_w/m38196x96cs9ptvv1j0srlp80000gp/T/pip-install-2p137s4u/pyturf_a220078a7cba4d4cbda8a548c661cb04/turf/__init__.py", line 6, in <module>
          from turf.boolean_disjoint import boolean_disjoint
        File "/private/var/folders/_w/m38196x96cs9ptvv1j0srlp80000gp/T/pip-install-2p137s4u/pyturf_a220078a7cba4d4cbda8a548c661cb04/turf/boolean_disjoint/__init__.py", line 1, in <module>
          from turf.boolean_disjoint._boolean_disjoint import boolean_disjoint
        File "/private/var/folders/_w/m38196x96cs9ptvv1j0srlp80000gp/T/pip-install-2p137s4u/pyturf_a220078a7cba4d4cbda8a548c661cb04/turf/boolean_disjoint/_boolean_disjoint.py", line 18, in <module>
          from turf.line_intersect import line_intersect
        File "/private/var/folders/_w/m38196x96cs9ptvv1j0srlp80000gp/T/pip-install-2p137s4u/pyturf_a220078a7cba4d4cbda8a548c661cb04/turf/line_intersect/__init__.py", line 1, in <module>
          from turf.line_intersect._line_intersect import line_intersect
        File "/private/var/folders/_w/m38196x96cs9ptvv1j0srlp80000gp/T/pip-install-2p137s4u/pyturf_a220078a7cba4d4cbda8a548c661cb04/turf/line_intersect/_line_intersect.py", line 4, in <module>
          from rtree import index
      ModuleNotFoundError: No module named 'rtree'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.

If I add GITHUB_REF I get another error
export GITHUB_REF=refs/heads/main

pip install pyturf==0.6.2

Collecting pyturf==0.6.2
  Using cached pyturf-0.6.2.tar.gz (36 kB)
  Preparing metadata (setup.py) ... done
  WARNING: Requested pyturf==0.6.2 from https://files.pythonhosted.org/packages/7d/25/c591c0ed4f958e8c1ac3b1fd1a94f311f48b54ba869632ee0ea5cac8bbaa/pyturf-0.6.2.tar.gz, but installing version main
Discarding https://files.pythonhosted.org/packages/7d/25/c591c0ed4f958e8c1ac3b1fd1a94f311f48b54ba869632ee0ea5cac8bbaa/pyturf-0.6.2.tar.gz (from https://pypi.org/simple/pyturf/) (requires-python:>=3.5): Requested pyturf==0.6.2 from https://files.pythonhosted.org/packages/7d/25/c591c0ed4f958e8c1ac3b1fd1a94f311f48b54ba869632ee0ea5cac8bbaa/pyturf-0.6.2.tar.gz has inconsistent version: expected '0.6.2', but metadata has 'main'
ERROR: Could not find a version that satisfies the requirement pyturf==0.6.2 (from versions: 0.1, 0.2, 0.3.5, 0.4.0, 0.4.1, 0.4.6, 0.4.7, 0.4.10, 0.4.12, 0.5.0, 0.6.0, 0.6.2)
ERROR: No matching distribution found for pyturf==0.6.2

Thank you. I will have a look.

@baditaflorin @devleaks
as a quick ugly fix - if you enter
pip install rtree

it will be possible to install pyturf with e.g.:
pip install pyturf==0.6.2


ng-build --prod failed with error

Hi,
I tried to build project in production mode by ng build --prod and getting the following error
ERROR in Unexpected module 'NvD3Module in F:/Development/TestDashboardApps/node_modules/ng2-nvd3/build/lib/ng2-nvd3.module.d.ts' declared by the module  ....Please add a @Pipe/@Directive/@Component annotation.
It would be very helpful to solve this issue. Thanks.

Try upgrading your project angular/cli version to the latest.
Check this issue of mine: https://github.com/krispo/ng2-nvd3/issues/107

thanks. its working


Unable to install Tomcat 9 - "Package 'tomcat9' has no installation candidate" || Ubuntu 24.04 LTS

I'm trying to install Tomcat 9 on my Ubuntu system using `*
sudo apt-get install tomcat9
but I keep running into the following error:
monirul@nitacl-Veriton-Series:~$ sudo apt-get install tomcat9
Reading package lists...
Done
Building dependency tree...
Done
Reading state information...
Done
Package tomcat9 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'tomcat9' has no installation candidate

Here's what I've tried so far:
sudo apt update Searching for alternative package names (e.g., tomcat9.0, tomcat-9) using apt-cache search tomcat

System Information: Ubuntu version: 24.04 LTS Noble Numbat
Architecture: LAMP
Could anyone please point me in the right direction? Is there a specific repository I need to enable or a different approach to installing Tomcat 9?
Thanks in advance for your help!****

This repo is for the Docker image for tomcat so this would be out of scope but my guess is that there are no pre-built packages in that OS for the architecture you are in.


HttpRequestData always returns 200 as status code

I have created a function that returns an error using the following code:
[<Function("myfunc")>]
let run ([<HttpTrigger(AuthorizationLevel.Function, "get")>]req: HttpRequestData) =
    async {
        let response = req.CreateResponse(HttpStatusCode.BadRequest)
        do! response.WriteAsJsonAsync("error message")
        return response
    } |> Async.StartAsTask

The message gets propagated correctly and the function returns "error message", but the status code returned is 200 instead of 400
.NET 5.0.300
Core Tools Version:       3.0.3568 Commit hash: e30a0ede85fd498199c28ad699ab2548593f759b  (64-bit)
Function Runtime Version: 3.0.15828.0

Context: https://github.com/UnoSD/UnoCash.Fable/blob/net5-azure-function/UnoCash.Api/GetExpenses.fs
I also tried getting rid of the Task<HttpResponseData> with .Result to make sure it wasn't an unwrapping issue, same results.
Thank you.

The WriteAsJsonAsync method sets the status code to 200. This is already submitted as issue # 344
https://github.com/Azure/azure-functions-dotnet-worker/issues/344

@stagep Thank you for the confirmation, I can close this issue then and follow the other.


#239 PsLinkedin passes the request parameters to the URI.

For task #239, removing the parameters in Href object and append them in RequestBody

@davvd , please review.


update logic for actants deletion

if deleting A: search all S, if the id isnt in data.actants[].actant or in S.data.props[].origin. If it is, then delete the whole object in which the id resides.

Deletion of used entities should not be allowed. Please refer to https://github.com/DISSINET/InkVisitor/issues/364.


Breaking API changes for 1.0

Naming

“Stateless Stores” are now called reducers. (https://github.com/gaearon/redux/issues/137#issuecomment-114178411)
The “Redux instance” is now called “The Store”. (https://github.com/gaearon/redux/issues/137#issuecomment-113252359)
The dispatcher is removed completely. (https://github.com/gaearon/redux/pull/166#issue-90113962)

API changes

composeStores is now composeReducers.
createDispatcher is gone.
createRedux is now createStore.
<Provider> now accepts store prop instead of redux.
The new createStore signature is createStore(reducer: Function | Object, initialState: any, middlewares: Array | ({ getState, dispatch }) => Array).
If the first argument to createStore is an object, composeReducers is automatically applied to it.
The “smart” middleware signature changed. It now accepts an object instead of a single getState function. The dispatch function lets you “recurse” the middleware chain and is useful for async: #113 (comment).

Correctness changes

The dispatch provided by the default thunk middleware now walks the whole middleware chain.
It is enforced now that raw Actions at the end of the middleware chain have to be plain objects.
Nested dispatches are now handled gracefully. (#110, #119)

Internal changes

The object in React context is renamed from redux to store.
Some tests are rewritten for clarity, focus and edge cases.
Redux in examples is now aliased to the source code for easier work on master.

This PR supersedes #166, #119, and #120, and brings us much closer to 1.0 (#164).
The missing pieces for 1.0 are more strict composeReducers (#193), new docs (#140), and a more convenient action creator binding API (#86), if we are certain that we need it.

Released on NPM as 1.0.0-alpha.

:tada: :)

Yay! Looks good!
I've been wondering if composeReducers() is really the best name for that function. The name is very generic, whereas its implementation is very specific.
Consider another common way of composing reducers, which is to apply each one of them in sequence:
(...reducers) => (prevState, action) =>
  reducers.reduce(
    (state, r) => r(state, action),
    prevState
  );

This could also be named composeReducers(). (I'd actually argue this is better fit for the name.)
Maybe we should think of a more specific name? Don't have any suggestions right now, but I wonder what everyone else's thoughts are.

@acdlite Any precedents in other libraries' APIs?

@gaearon one step forward, great work! :+1:

I've been wondering if composeReducers() is really the best name for that function.
Maybe we should think of a more specific name? Don't have any suggestions right now, but I wonder what everyone else's thoughts are.

combineReducers() maybe?

I like combine.

:+1: for combineReducers().
I think we should remove middleware as a parameter createRedux(). Because they have the potential to be async, middleware needs to be applied before being passed to higher-order stores like createDebuggerRedux(): https://github.com/gaearon/redux/pull/166#issuecomment-114222798
Instead, I think the API for middleware should be something like applyMiddleware() from that comment.

Oh, you're right!

@acdlite Please do!

@gaearon Hmm, just realized... we can't keep thunkMiddleware() as a default if we move middleware out of createStore().
Also, should applyMiddleware() be composable using compose()? E.g.
const store = compose(
  applyMiddleware(t => [ thunkMiddleware(t), promiseMiddleware ]),
  debugger,
  createStore
)(reducer, intialState)

or should it be applied to the store after it's created? E.g.
const store = applyMiddleware(
  t => [ thunkMiddleware(t), promiseMiddleware ],
  debugger(createStore)(reducer, initialState)
)

The second version looks nicer and is less likely to confuse people, but the first version is more flexible and "correct" since it has the same interface as debugger.

(Hahaha I guess calling it debugger isn't an option :D)

Submitted a PR to this branch to update middleware API https://github.com/gaearon/redux/pull/213

Like you said in your talk @gaearon, it often takes months to think about something and only a short time to code it once you've established a good mental model.
I think redux can benefit greatly from established backend mental models - specifically "event sourcing". @vladap Already hinted at the similarities in https://github.com/gaearon/redux/pull/140#issuecomment-115157831
Event sourcing has similar goals to redux:

By keeping a log of every event it's easy to "time travel" and evaluate the complete application state at different times.
In the event of a bug you can simply change the code, replay all your events and arrive at a consistent state
It separates writes from reads which reduces complexity. Instead of a component mutating state directly, it triggers an event (a write) which trickles down the system and eventually updates the state for future reads.

There are important architectural details which should be kept in mind with a event sourced system. One of the most important being the separation of commands / events. Commands are requests for state to be mutated. Depending on business logic these command requests can be denied. Events on the other hand can be thought of as approved commands and are written in the past tense to make this clear.
In my understanding of Redux these two concepts map nicely to actionCreators and actions. actionCreators receive commands, it might reject these commands silently, or it could create several events based on this command such as: ADD_TODO_REQUESTED, ADD_TODO_FAILED, ADD_TODO_SUCCEEDED.
Reducers take these events and synchronously modify the state of the application accordingly.
Do you think @vladap and I's analogy to event sourcing is valid for reflux? Would it help to use the command/event analogy? Since "event" is close to browser events, "facts" might be a better fit.

Separation of commands and events is something @glenjamin has been doing in fluctuations:
var interceptor = fluctuations.createInterceptor({
    FETCH_MESSAGE: function(emit, payload) {
        emit("FETCH_MESSAGE_BEGIN");
        setTimeout(function() {
            emit("CHANGE_MESSAGE", { value: "whatever" });
        }, 2000);
    }
});

I have no opinion on this yet. I'd probably stay with the current middleware approach for now, and see if something interceptor-like appears in the community.

Thanks I had a look at fluctuations...
Middleware is a powerful concept since it allows you to create a chain of transformers on an event instead of sticking to a single function.
I'm not sure I completely understand the current middleware proposal. I read about

"dispatch-level "middleware" and store-level "middleware"

from https://github.com/gaearon/redux/pull/166#issuecomment-114217907
Can I think of these two middleware stacks as command-middleware and fact-middleware?
Using these terms has some advantages over redux inventing it's own... it becomes more apparent that the command-middleware has to come before the fact-middleware. It also becomes more obvious that you should store a stream of facts for your time machine and throw away all commands. If you only traverse facts you solve the problems with async dependencies as mentioned in https://github.com/gaearon/redux/issues/113#issuecomment-114210769 since the async commands are already resolved to synchronous facts.
Or am I misunderstanding the current architecture?

+1. IMO this naming would add clarity, provided that it's accurate.

@skaapgif I feel like those terms are too limited. What we're calling "higher-order stores" right now is not just about intercepting "commands" — the uses cases are far more general. It's much the same concept as higher-order components in React. Yes, you can use them to intercept actions, and that will probably be the most common use case. However, you can also use them to do things like add the transducer protocol to a store, like so: https://github.com/acdlite/redux-transducers.
The best API is often no API. The current proposals for middleware and higher-order stores have the tremendous benefit is that they receive no special treatment by the core API — they're just wrappers around dispatch() and createStore(), respectively. You can even use them today, before 1.0 is released. That's a huge win for extensibility and rapid innovation. We should favor patterns and conventions over rigid, privileged APIs.
See a fuller explanation of higher-order stores here.

Thanks for the links @acdlite, I didn't notice the improve-docs branch, I'll have a read through it to make sure my understanding is correct.

So am I correct in saying there's no such thing as dispatch-level "middleware" and store-level "middleware"... just middleware? Middleware always wraps dispatch() and higher-order stores are stores which have middleware applied to them?
The difference between commands and facts then are the input and output of a single dispatch function or a middleware chain wrapping the dispatch function. Commands go into this chain and facts come out. These fact(s) are then "reduced" into new state change(s).

@skaapgif I think the soft consensus is that when we say "middleware" in Redux, we're talking specifically about a function that wraps or proxies dispatch(). Higher-order stores often employ middleware, but they are a superset, because they also have the ability to proxy or amend other parts of the Redux interface. applyMiddleware() is a good example because it shows the relationship between the two concepts — it is a higher-order store that implements middleware.

For clarification, here's an example how to do "new" middleware:
export default function actionDebugMiddleware(next) {
  return (action) => {
    console.info(action.type, action);
    next(action);
  };
}

@grrowl It will actually be this in 1.0, because the outer function receives ({ dispatch, getState }):
export default function actionDebugMiddleware() {
  return next => action => {
    console.info(action.type, action);
    next(action);
  };
}

Bizarre, that's what I had originally, but next was being filled with the action, with action undefined. On npm 1.0.0-alpha. I'll dig deeper

Oh that hasn't been merged yet :) Should have clarified. https://github.com/gaearon/redux/issues/213

@grrowl Merged now (but not released yet).

The main difference in command sourcing and event sourcing is how parts of the system are coupled. Event sourced system is highly de-coupled while command sourced system is coupled. I will try to show it on a contrived example.
ActionCreator buys pizzas. Each pizza comes with coffee and cola. There are 3 reducers, one counts bought pizzas, one counts coffees and one counts colas.
Now what action you should dispatch when AC finishes buying pizzas?
You can dispatch BUY_PIZZA but then you get a semantic problem that reducers were told to perform BUY_PIZZA action but they do something else. It is like you would tell me to buy pizza but actually wanted me to count them.
Or you want to dispatch actions describing what they should do. But which one? Each is doing something else. If you choose to dispatch all of them INC_PIZZA, INC_COFFEE, INC_COLA, it requires that AC knows what each reducer is doing. Even more worse is that if you want to add another reducer which would do something else when pizza is bought you are breaking Single Responsibility Principle, because by adding reducer you have to update ActionCreator as well if it requires new action!
Or you can invent some action covering all cases, you will probably end up with something generic non-descriptive like DO_WHATEVER_YOU_WANT.
With event sourced mental model AC writes facts and doesn't care at all what happens next. AC simply log PIZZA_BOUGHT. First reducer sees PIZZA_BOUGHT and thinks, when pizza is bought I'm responsible to increase pizza count. Next one inc coffee and the next inc cola. Everything is correct and it makes sense even under semantic lenses.
And you can add how many new reducers you want doing whatever you wish when pizza is bought. You don't need to touch AC. You do so only to extend its logging capability when your reducers need more facts.
Our teams writing transactional systems know nothing what our analytics team does. Command sourced mentality wouldn't work at all here. They just log what they did and sometimes we tell them to log some more.
Webapp components are very close to each other and they are developed by a single team/person so it is possible to get away with command sourced mentality. Game engines are (were) doing it for years (game replays). I still believe that thinking event sourced, understanding that past never changes but anybody can come and make a new decision/processing based on facts in the past is a good model to think in.

My current thinking is that action creators act like commands, and actions act like events.
The redux approach to storage and replay seems closest to event sourcing to me.
The experiments with APIs I'm doing in fluctuations are largely aimed at solving two problems:

reducing flux boilerplate
connecting action creators to a dispatcher without using singletons

Those damned ActionCreators. There is bindActionCreators() but dispatch(action) on a component level. We know that we actually dispatch (or something like that) actionCreator.
But isn't it confusing for somebody new this ActionCreator vs Action "fight"?
I'm fine with dispatch(action) and would like to have bindActions but it is not technically correct, at least not for async code. It works when there is 1:1 relation between AC and A, then AC can be seen as a hidden mediator between views and stores. It stops to work when AC starts to be more complex having quite a bit of logic and generates additional actions.
Saying that I'm binding AC and dispatching AC feels bad.

@vladap No we do not dispatch an action creator, since what we do is this: dispatch(actionCreator()). We are dispatching the result of an action creator, which is an action.

We are dispatching the result of an action creator, which is an action.

This is right.
See also https://github.com/gaearon/redux/blob/improve-docs/docs/types-and-terminology.md (work in progress).

Thanks for clarifying. The problem is then somewhere between my chair and keyboard :)

The version currently in this branch is likely to become the 1.0 release candidate.
If you wanna play with it ahead of the release, please do!

dat switch to 1.0.0-rc :+1:

1.0 RC release notes: https://github.com/gaearon/redux/releases/tag/v1.0.0-rc

How to bindActionCreators right now? I don't get it :sos:

Looks like it's impossible in decorator.
Is that means I should use Connect component every time I need bindActionCreators?

@gaearon What if change select signature to select(state: mixed, dispatch: Function): mixed ?

Found #86
Sorry for noise :smile:

@vslinko Here's the @connect API I have in mind: https://github.com/gaearon/react-redux/issues/1#issuecomment-120729921. Please let me know if you see ways to make it better (in that thread).

I don't know if anyone  would find this useful, but here is the gist I use for setting up my store with the new API. gist

Wow - I remember when this library was just a pseudo-code! I took a 2 month hiatus and now it's grown into something incredible :smirk:. TWO MONTHS!!! (I apologize if this is off topic).
Smart/Dumb components was excellent article - but Rich Hickey's talks have had profound influences on myself:
Simplicity Matters --- reducers --- transducers, to name a few.
But the most powerful feature of redux - what I never expected - was the ecosystem. Projects that encourage plugins and have a minimal core-api seem to dominate the npm world: express/connect gulp, grunt, etc.  - never imagined it would be used for flux-esc architecture
IMO simplify the core API as much as possible (like react-DND) - and encourage the plugin the ecosystem. I want to help contribute :)  -- (after I grok the concepts fully)

2.5 (insanely hectic for you)months from "Initial Commit" to "1.0" is kind of crazy... Nice work :)


declare and define does not work at the top of a block without curly braces

Summary:
Declare and define does not work at the top of a block without curly braces.
Description:
There is a parser error if you attempt to declare and define does not work at the top of a block without curly braces.
Reproducible Steps:
Parse this
functions {
  real foo() {
    if (1)
      real this_does_not_parse = 0;
    return 0;
  }
}

Current Output:
SYNTAX ERROR, MESSAGE(S) FROM PARSER:

Unknown variable: real
variable "real" does not exist.
  error in 'model_parser' at line 4, column 11
  -------------------------------------------------
     2:   real foo() {
     3:     if (1)
     4:       real this_does_not_parse = 0;
                  ^
     5:     return 0;
  -------------------------------------------------

Expected Output:
Nothing
Additional Information:
None
Current Version:
v2.18.0

a combined variable declaration and definition is considered to be a variable definition; it is not a statement.
the body of a for loop can be either a single statement or a sequence of statements.
a sequence of statements consists of:

'{'
zero or more variable declarations
zero or more statements
'}'

the parser is doing the right thing here; agreed, the error message could be better.

What we want to do is replace this issue with a feature request to turn variable declarations so that local variable declarations may be interleaved.  It's awkward with the implicit block-variable/statement split in the blocks with statements---the statements start after the last declaration.

Why would we want this to parse? Is there any reason to declare a local variable and never use it?
I agree that mixing variable declarations and statements is useful, but that seems like a different issue.

Hmm. OK. So maybe the grammar (and stanc3) should be changed then?


Updated Upgrade Instructions

Streamlined update process for newer users like myself.  Now includes exact instructions for downloading latest release or using git.

Great work, thanks!


feat: migrate the codePlugin from @vuepress/markdown to plugin-shiki

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

[ ] Read the Contributing Guidelines.
[ ] Provide a description in this PR that addresses what the PR is solving. If this PR is going to solve an existing issue, please reference the issue (e.g. close #123).

What is the purpose of this pull request?

[ ] Bug fix
[ ] New feature
[ ] Other

Description

see https://github.com/vuepress/core/issues/1550
Screenshots

Before
After

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 49.759%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
681

Relevant Lines:
1238

💛  - Coveralls

Also check0#135

Also check #135

It appears that the current shikiSetup() has already implemented the same functionality.

Same here. UT or E2E is required

Same here. UT or E2E is required

Added test cases identical to the codePlugin in @vuepress/core.

@meteorlxy @Mister-Hope Cc, this PR is ready.


Update Composer dependencies (2022-05-18-00-03)

Visual regression test passed!
View the visual regression test report


CORS error when fetch image from S3

*note: ImageDisplay is my custom image display
I faced this issue while working in my own project although in S3 i set Accpet-Control-Allow-Origin to '*' (image 3). I found out that if i write a fetch method to that s3 url its still face the same error but when i set mode: 'no-cors' it success. Anyone can explain why for me :( is there any way to work around or to set no-cors mode to reac-doc-viewer?
This is my first time submit an issue so plz appologize for any mistakes, thank you guys a lot.

 That config simply allows the request to go through, but you'll still see the error (which is actually a warning).

I've experienced a similar issue on a different project. By performing a fetch from your client, from your DocViewer, you are doing a cross-origin call. This is typically against common practice because of the potential security vulnerabilities that are invited.
However, if you have the correct controls in place, this can be perfectly legitimate. If your scenario was anything like mine, the fetch was perfectly fine, but the errors in the console are more so an FYI, "Be advised...", type of thing.
Check out the MDN Fetch resource.

Adding prefetchMethod="GET" resolved the CORS issue for me.

I'm experiencing this too.
I have a valid URL from AWS S3, which fetches fine when pasted in the browser.
But when Doc Viewer tries to make the request, it fails on CORS and no file is shown (infinite loading).
I tried the above of adding prefetchMethod="GET", it did not resolve the issue.

hi guys, sorry for late reply, i have solved it by remove region prefix in s3 presigned URL, maybe u can try

I'm experiencing this too. I have a valid URL from AWS S3, which fetches fine when pasted in the browser.
But when Doc Viewer tries to make the request, it fails on CORS and no file is shown (infinite loading). I tried the above of adding prefetchMethod="GET", it did not resolve the issue.

Have you managed to resolve this issue? I have the same one

anybody got the solution? same url works if img tag i use

I'm experiencing this too. I have a valid URL from AWS S3, which fetches fine when pasted in the browser.
But when Doc Viewer tries to make the request, it fails on CORS and no file is shown (infinite loading). I tried the above of adding prefetchMethod="GET", it did not resolve the issue.

Have you managed to resolve this issue? I have the same one @BenElferink

Nope, still unresolved.

I'm experiencing this too. I have a valid URL from AWS S3, which fetches fine when pasted in the browser.
But when Doc Viewer tries to make the request, it fails on CORS and no file is shown (infinite loading). I tried the above of adding prefetchMethod="GET", it did not resolve the issue.

Have you managed to resolve this issue? I have the same one @BenElferink

Nope, still unresolved.

i exposed a new api from my server and it worked, but still signed urls not working
`
@ApiBearerAuth()
@Get("/docs/preview")
async getEnquiryDoc(@Query('key') key: string, @Res() res: any): Promise {
try {
const s3Object = await this.s3Servcice.getObject(key);
// Determine the content type based on the file extension or your specific logic
const contentType = 'application/octet-stream';
  res.setHeader('Content-Disposition', `attachment; filename=${key}`);
  res.setHeader('Content-Type', contentType);
  res.setHeader('Content-Length', s3Object.length);
  res.send(s3Object);

} catch (err) {
  throw err;
}

}
/**

Get an S3 object based on the provided key.
@param {string} key The object key (filename) in the S3 bucket.
@returns {Promise} The content of the S3 object as a Buffer.
*/
async getObject(key: string): Promise {
const params = ({
Bucket: this.bucketName,
Key: key,
});

const response = await this.s3.getObject(params).promise();
return response.Body as Buffer;

}
`


change name of this repository

Some people, including myself, feel that this repository/package name is not ideal and that we should change it, see: https://github.com/ros2/c_utilities/issues/13#issuecomment-293560955 (and perhaps other conversations). If you disagree please chime in here.
When/if we select a new name, we should act quickly to update all instances to minimize impact on git history and cross-references. Also, we should update this package to use the full package name in the manual namespacing throughout.
I talked with @Karsten1987 offline about this and I came up with two criteria which could improve the name of this package:

A shorter name

since this is package contains C code, its functions and types need to be manually namespaced by prefixing them with the package name
@dirk-thomas pointed out that some shortcuts have been taken, using utitlities_ instead of the full c_utilities_ for example

I agree with him, that using the exact package name in the namespace is a very useful convention

a shorter name will keep it convenient and prevent the desire for shortcuts like these

A name with some reference to our project or organization

My concern is that c_utilities_ and especially utilities_ is not a very unique name
a unique name helps avoid symbol collisions and makes it more obvious that some part of the code is part of our project

for example, others thought we were adding an external dep: https://github.com/ros2/rmw/pull/100#issuecomment-293644996
Other examples of this are apr (Apache Portable Runtime) and glib GLib which is part of Gnome.

both are widely reused despite containing a reference to a project or organization in the name

Based on these goals I just threw out some alternatives, but I'm not really attached to any of them so please others chime in with options:

osrfcutils OSRF C Utilities

could be extended for other languages, e.g. for C++ as osrfcpputils

osrfcu OSRF C Utilities

could be extended for other languages, e.g. for C++ as osrfcppu

osrflibc OSRF Library for C

could be extended for other languages, e.g. for C++ as osrflibcpp

libosrfc Library used at OSRF for C

could be extended for other languages, e.g. for C++ as libosrfcpp
library names could be modified so that they come out as libosrfc.ext rather than liblibosrfc.ext

osrfc OSRF C utilities library

could be extended for other languages, e.g. for C++ as osrfcpp
library names would naturally be libosrfc.ext

rcutils ROS C Utilities

could be extended for other languages, e.g. for C++ as rcpputils

There were some others, but I didn't really like them or they collided with existing things, for example anything containing roslib might be confused with:
https://github.com/ros/ros/tree/lunar-devel/core/roslib
Or that ros2* sounds like you're converting to something from ros, or anything containing comm and not knowing if that's short for "common" or "communication".
My personal favorite atm is probably osrfc or libosrfc, as I think utils or utilities is a bit redundant or catch all, sort of like misc or common. To me leaving off words like that implies the same thing. I also think that they're pretty unlikely to collide with anything else and are relatively short.

I personally don't like the idea of having osrf in the name. Just imagine if that package would have been created a few years ago - different company name. They same might be the case in the future.
Therefore I am in favor of rcutils. It encode the important pieces imo: ROS, C, utils. And leaves room for similar packages for different languages.
Regarding the content I just want to mention that I think we need to be careful what to put inside that package. While we mainly want to avoid duplication we should be very careful not to put too many things into that package. It should aim to provide "utilities" which makes downstream code easier / less verbose (that is what e.g. apr and glib are about). But we should try to avoid providing crucial concepts which are then becoming must haves in downstream code. (I know this sounds fuzzy and is difficult to describe but I wanted to mention it anyway.)

I'd personally suggest something more like: roscutils.  It's a little longer, but then it is very clear that this is for ROS.

👍  rcutils

:+1: to rcutils as well, or something equivalently ROS-y. I agree with avoiding osrf in the namespace. I am constantly haunted by the hlr namespace in our Rethink code. Organization names change from time to time, but the project-code tends to live on :)

I'd take the other side and say that this is not ROS specific. We are using it to support the development of ROS2.0 but it certainly could be reused outside of ROS. It's true that it likely won't reach the scope of osrf_pycommon.
Following the goal of making downstream code less verbose, and following the examples of apr and glib I'd suggest shortening it to rcu This would come from it's core purpose as ROS C Utilities however like apr it can have a life of it's own if others want to pick it up. It's also short so usages are clear. And it's matches nicely with rmw and rcl for length making readability easier too.

Well put, Tully. Changing my +1 to rcu.

Thanks for all the feedback so far everyone.

@clalancette

I'd personally suggest something more like: roscutils. It's a little longer, but then it is very clear that this is for ROS.

The preference seems to be for rcutils do you feel strongly about ros versus just r for the suffix, or are you okay with the shorter hand?

@tfoote

It's true that it likely won't reach the scope of osrf_pycommon.

For me, osrf_pycommon came in under different constraints, because it was being used by catkin and ament, so there wasn't a clear "default" user, so the organization made the most sense at the time. To be honest, I'm not 100% happy with the name of that thing either, but it's the best I could come up with at the time. Also I consider osrf_pycommon to be "an OSRF common python library", not "the OSRF common python library", so if another project at OSRF needed common Python stuff they could make another library, but the hope is that they wouldn't need to do so. I feel the same about this package, it certainly won't be the only utilities library in ROS at some point given the breadth of people adding stuff to the ecosystem, but is a utility package used by ROS.
I understand the arguments against an institution name, but I guess I just don't mind if the company name changes or something like that in the future. It's part of the history regardless of the name and is in the copyright, etc. It's still unique and wouldn't be too hard for someone to figure out why osrf is in the name. That being said, I like the concise nature of the rc* names, and I'm perfectly fine with that.

I'd suggest shortening it to rcu

I like the shorter name, but my only hesitation is that rcl* stands for ROS Client Library, whereas this would be rcu ROS C Utilities, so the c stands for different things in each name, which might be confusing. I don't think that mix up would cause an issue, but maybe just misconceptions. I don't feel strongly about it, but that's why I didn't suggest it earlier.

:+1: for rcutils. agreed with the potential confusion of rcu that @wjwwood highlighted in his previous comment

Ok, I've added a summary of the preferences (ranked choice where implied) to the original post:
https://github.com/ros2/c_utilities/issues/17#issue-221713329
If you'd like to add your preference or update it please comment and I'll do it. If you want to edit the post yourself, you can but make sure to refresh right before editing to avoid overwriting each other.
Please register your opinion by end of day Saturday, so I can start to put the change in motion after that.

"I'd suggest shortening it to rcu"
I like the shorter name, but my only hesitation is that rcl* stands for ROS Client Library, whereas this would be rcu ROS C Utilities, so the c stands for different things in each name, which might be confusing. I don't think that mix up would cause an issue, but maybe just misconceptions.

I think the c in rcu is can be interpreted interchangeably between "client" and "c-language" in this context. All ros2 language clients that depend on on the rcl will depend on this c-library as well, making rcu quite fitting.

Looks like there is a slight preference for rcu. I'll go forward with that.

tl;dr we'll use rcutils unless another issue comes up.
@clalancette thanks for that insight. I searched for "rcu" library, but I missed uruc amongst the credit unions and university websites. Given that I, I'll retract my support for rcu but what I support instead doesn't matter I think, because no matter what I believe rcutils wins. Luckily I had not started because my other prs that need to be merged first took longer to clean up than I had hoped yesterday.

I'll leave this open until the repository is renamed and the ros2.repos file is update.


Update the Implementation Guide for v2.0.0

Is your feature request related to a problem? Please describe.
The IG needs to be updated before we can assign a tech writer.
Close this issue once you've updated the IG in workdocs to include any information that users need to know about changes listed in CHANGELOG.md.

done


timecode option for drawtext not working as expected.

Describe the bug
Attempting to use the 'timecode' or 'timestamp' option of the drawtext filter does not seem to work. ffmpeg WASM indicates the following errors:
[fferr] [drawtext @ 0x32c7540] Invalid 0xRRGGBB[AA] color string: '07'
[fferr] [drawtext @ 0x32c7540] Unable to parse option value "07" as color
[fferr] [Parsed_drawtext_0 @ 0x1a6e7c0] Both text and text file provided. Please provide only one
[fferr] [AVFilterGraph @ 0x32c9440] Error initializing filter 'drawtext' with args 'timecode=17:02:25:07:fontfile=font.ttf:r=24000/1001:fontcolor=white:fontsize=36:x=(w-tw)/2:y=h/2-18'

It does not like the "drawtext=timecode=17:02:25:07" as input for the filter. Note that is seems to be interpreting the 'frames' position of ":07" as a color (??). I suspect there's some issue with parsing the drawfilter argument that relates to the colons not being handled correctly
I have tried passing all of the following:
timecode='17\:02\:25\:07'
timecode=17\:02\:25\:07
timecode=\"17\:02\:25\:07\"
timecode='17:02:25:07'
timecode=17:02:25:07
timecode=\"17:02:25:07\"

Without any luck. On the command line, escaping the Colons is required, so I assume it is necessary on the WASM as well. All variants give the same error above.
if I change it to:
drawtext=timecode='0':

instead, I get:
 [fferr] [Parsed_drawtext_0 @ 0x3335c80] Unable to parse timecode, syntax: hh:mm:ss[:;.]ff
instead of the error above.
If I modify the input timecode string to timecode='17\:02\:25\;07' I no longer get the invalid color string error, but I still get the Both text and text file provided. Please provide only one error. Removing the trailing ";07" entirely also give the Both Provided error.
To me it appears there might be two bugs that are related. One for parsing the Frames with Colon option and another related to the WASM seeming to think both 'text' and a 'text file' are being passed to the timecode filter.
To Reproduce
    // font.ttf, test.mp3 and background.png are correctly loaded into the ffmpeg FS at time of run.
    await ffmpeg.run(
      '-loop', '1',
      '-r', '24000/1001',
      '-i', 'background.png',
      '-i', 'test.mp3',
      '-vf',
      "drawtext=timecode='17\:02\:25\:07':fontfile=font.ttf:r=24000/1001:fontcolor=white:fontsize=36:x=(w-tw)/2:y=h/2-18," +
      "drawtext=text='23.976 fps':fontfile=font.ttf:r=24000/1001:fontcolor=white:fontsize=20:x=(w-tw)/2:y=h/2+20,format=yuv420p",
      '-r', '24000/1001',
      '-b:v', '150000',
      '-c:v', 'libx264',
      '-c:a', 'aac',
      '-b:a', '128k',
      '-shortest', 'out.mp4');

Expected behavior
I would expect the timecode to be burned onto the PNG background file and run continuously throughout rendered file. The same command run on the ffmpeg cli works correctly.
If I remove the 'timecode' filter and run only the static drawtext=text filter, it works as expected.
Screenshots
Successful render from cli look like this and what I would expect from the timecode filter:

If I run just the static 'drawtext=text='23.976_fps' filter without the timecode filter, the WASM renders the file as follows (which is expected, but without the desired timecode).

Desktop (please complete the following information):

OS: Mac OS Catalina for Dev Machine
Browser: Chrome v103

Additional context
Using React 17.x and
    "@ffmpeg/core": "^0.10.0",
    "@ffmpeg/ffmpeg": "^0.10.1",

On the CLI I can run the equivalent and it works:
ffmpeg -loop 1 -r 24000/1001 -i 'background.png' -i 'test.mp3' -vf "drawtext=timecode='17\:02\:25\:00' :fontfile=font.ttf:r=24000/1001:fontcolor=white:fontsize=36:x=(w-tw)/2:y=h/2-18:box=1: boxcolor=black@1.0:boxborderw=4,drawtext=text='23.976 fps':fontfile=font.ttf:r=24000/1001:fontcolor=white:fontsize=20:x=(w-tw)/2:y=h/2+20, format=yuv420p" -r 24000/1001 -b:v 150000 -c:v libx264 -c:a aac -b:a 128k -shortest out_bwf.mp4

in my case ,
this code work
const param = "drawtext=text=\'test\':timecode=\'09:57:00:00\':rate=30:fontfile=arial.ttf:fontsize=24:x=(w-text_w)/10:y=text_h+10";


deploy

You can merge from master to production directly without my approval as long as the all the checks pass!!! Remember to do merge instead of squash & merge.


Unable to call asynchronous functions repeatedly

Hi, I'm trying to run some redis commands at some intervals
var j = schedule.scheduleJob(rule, test(function(reply) {
  console.log(reply);
}));

function test(callback) {
  client.get('mykey', function (err, reply) {
    callback(reply);
  });
}

However, it executes successfully once and then subsequently execution resulted in error:
Cannot read property 'execute' of undefined

What am I doing wrong? Please advise.

@gnoymmij The second parameter of the scheduleJob function should be a function. Try with this instead:
var j = schedule.scheduleJob({ second: 0 }, function() {
    test(function(reply) {
        console.log(reply);
    });
});

@santigimeno Nothing happens when I do it this way... I verified this by trying to delete a key rather than getting a key from redis.

@gnoymmij Take into account that I'm scheduling the job to be executed every minute (every time the second = 0)
For example this test is working correctly for me and writes hello every minute.
var j = schedule.scheduleJob({ second: 0 }, function() {
	test(function(reply) {
		console.log(reply);
	});
});

function test(cb) {
	setTimeout(function() {
		cb('hello');
    }, 100);
}

@santigimeno I tried your example and it works. But when I change the test function to:
function test(cb) {
  client.get('mykey', function(err, reply) {
    console.log('did this print?');
    cb(reply);
  }
}

Nothing seems to be executing, not even the console.log statement within the test function...

@gnoymmij It looks like a problem inside your function, not in node-schedule

@santigimeno I managed to make it work. I had to move the redis commands out to another file and export the function as a module.
Thanks for the help.

I get this error
Cannot read property 'execute' of undefined
when I try to run
schedule.scheduleJob('*/5 * * * * *', UpdateTiles("5sec"));
as opposed to
schedule.scheduleJob('*/5 * * * * *', Update5Sec);
function Update5Sec() {
UpdateTiles("5sec");
}

which works perfectly

@hydrix9 Did you manage to fix it?


Basic example not working on raspberry pi pico

I'm new to micropython and hope this is not an obvious error on my part. I've been trying to get the minimal example to work with the Raspberry Pi Pico but I get the following error message:
Traceback (most recent call last):   File "<stdin>", line 9, in <module>   File "mpr121.py", line 79, in __init__   File "mpr121.py", line 96, in reset   File "mpr121.py", line 84, in _register8 OSError: [Errno 5] EIO
The slightly altered example code I'm using looks like this:
from machine import I2C, Pin
import mpr121
import time

i2c = I2C(0, scl=Pin(9), sda=Pin(8), freq=100000)

time.sleep_ms(100)

mpr = mpr121.MPR121(i2c, 0x5A)

while True:
	print(mpr.touched())
	time.sleep_ms(100)

Could this issue be caused by the driver?

Caused by broken jumper wire


ENH: Jacobian memoization for multivariate minimization

The second commit fixes the current situation in which the objective function is evaluated twice when it also returns the jacobian in TNC and L-BFGS-B. See this discussion.
The last one introduces support for this behavior (i.e. fun(x, *args) -> f, fprime) in minimize thus making it available for all solvers.

I'm quite new to these memoization techniques so any comment very welcome.

Ok, this gets +1 from me. I don't see obvious problems in merging this.


Fix GH-201: Multiple @RequestPart not Working

Summary of changes follows:

Delegate ALL requestBody encoding where Content-Type is multipart/form-data to the SpringFormEncoder.
Introduce RequestPartParameterProcessor to deal with @RequestPart annotations, adds parameters to MethodMetadata.formParams().
Wrap HttpMessageConversionException in EncodeException.
Add tests to verify expected behaviour.

However there still exists a gap in functionality where any user defined pojo will be serialized as a Map<String,String>, as there is currently no way for SpringFormEncoder to know about the Content-Type of the individual parts beyond MultipartFile, boxed primitive types (which are treated as text/plain) and other built-in types inherited from FormEncoder.

@aaronjwhiteside Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@aaronjwhiteside Thank you for signing the Contributor License Agreement!


Windows ce app container edits

Docs Build status updates of commit 2243a85:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/windows-ce-app-container.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit e539d7b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/windows-ce-app-container.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Updated

Docs Build status updates of commit e539d7b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/windows-ce-app-container.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 36a4e3c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/windows-ce-app-container.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Update mutations.md - add retry context and include retry delay info

I had to look up another doc  to find this, having this here would help others in the future

please refer to the api docs to see all possible options
https://tanstack.com/query/v5/docs/framework/react/reference/useMutation


drivers: can_mcux_flexscan: fix syntax errors

A stray backslash prevented a macro from being defined, and a device pointer lacked the required const qualifier.
Relates to #31733 but doesn't fix it.

I guess we will take  #31885 instead.


chore: replace deprecated endpoints for vespa feeding and documentation

What

Replace the custom vespa cloud endpoints with the generated ones.

Why

The custom endpoints are deprecated and will be removed in the future.

Additional Info
Related PRs:

https://github.com/vespa-engine/documentation/pull/3327

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

what is the status here / should we keep or merge?

Keep, it will need to happen, but I've been busy with other things. 😊


feat: new web interface styling

Description
New theme with side menu using Material UI
Motivation and Context
Restyling components with a new look & feel
How Has This Been Tested?
Manually

I'm adding a new pr - just ignore this one


laravel/laravel release way behind master?

Result is considerable difference in using composer (current release) vs laravel/installer (master) (per laravel documentation) in the project scaffolding app/, config/ files etc.  Confusing for new laravel/php developers (aka me).

Sorry if this isn't clear.  Maybe this is more detailed:
http://laravel.io/bin/bE9JN

the installed app is the same as laravel/laravel?

Did I invoke composer incorrectly? The laravel documentation shows two methods of creating a new project. Those two methods produce different results. As in the scaffolding code is different. Is that intentional?


add(templates): next-enterprise

Name
Link

Next.js enterprise
https://github.com/Blazity/next-enterprise

An enterprise-grade Next.js boilerplate for high-performance, maintainable apps. Packed with features like Tailwind CSS, TypeScript, ESLint, Prettier, testing tools, and more to accelerate your development.

[x] My item is in the right category
[x] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[x] My item is awesome
[x] My item is in line with the Tailwind brand usage guidelines
[x] I have read and followed the contribution guidelines

This just has Tailwind added into it and isn't a tailwind specific thing. We've got enough boilerplates that ALSO include Tailwind as a feature. The point of this list is to be awesome things FOR Tailwind.


Update pom versions to SNAPSHOT version

Codecov Report

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

@@           Coverage Diff           @@
##           master     #378   +/-   ##
=======================================
  Coverage   82.75%   82.75%
=======================================
  Files          28       28
  Lines         725      725
  Branches       53       53
=======================================
  Hits          600      600
  Misses         86       86
  Partials       39       39

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 a88aa27...e9641e6. Read the comment docs.


pipenv with pixi (on Windows)

I have been given a project that uses pipenv, and I'm developing on Windows, so I was wondering about using pixi to do installation of both pipenv as a global tool and the installation of Python for the virtual environment.
So far I have:

pixi global install pipenv - Fine 👍
pixi global install "python=3.8.3" -e python3-8-3 --with pip --expose python3-8-3=python - Seems fine 👍 Note pip is explicitly included
pipenv install --python C:\...\.pixi\env\python3-8-3\python.exe - (as in https://pipenv.pypa.io/en/latest/advanced.html#pipenv-and-other-python-distributions) Creates the required virtual environment using this version of Python, but can't install pypi packages there due to ssl issues:

WARNING:pipenv.patched.pip._internal.models.search_scope:pip is configured with locations that require TLS/SSL, however
the ssl module in Python is not available.

In the python3-8-3 global environment, it has the following packages installed.
>pixi global list -e python3-8-3
The python3-8-3 environment has 12 packages:
Package          Version       Build               Size
ca-certificates  2024.8.30     h56e8100_0          155.1 KiB
libsqlite        3.47.2        h67fdade_0          870.4 KiB
openssl          1.1.1w        hcfcfb64_0          5 MiB
pip              24.3.1        pyh8b19718_0        1.2 MiB
python           3.8.3         cpython_h5fd99cc_0  18.9 MiB
setuptools       75.3.0        pyhd8ed1ab_0        761.3 KiB
sqlite           3.47.2        h2466b09_0          894.4 KiB
ucrt             10.0.22621.0  h57928b3_1          546.6 KiB
vc               14.3          ha32ba9b_23         17.1 KiB
vc14_runtime     14.42.34433   he29a5d6_23         736.6 KiB
vs2015_runtime   14.42.34433   hdffcdeb_23         17.2 KiB
wheel            0.45.1        pyhd8ed1ab_0        61.5 KiB
Package          Version       Build               Size

Exposes:
python3-8-3 -> python
Channels:
https://prefix.dev/conda-forge

Any suggestions?
All of the following commands work correctly (no errors), so ssl does appear to be available in all of the relevant environments.

C:\...\.pixi\envs\python3-8-3\python.exe -c "import ssl"
C:\...\.pixi\envs\pipenv\python.exe -c "import ssl"

The pipenv environment has the following packages installed, which includes openssl, so that should be OK too :shrug:.
>pixi global list -e pipenv
The pipenv environment has 26 packages:
Package          Version       Build               Size
bzip2            1.0.8         h2466b09_7          53.6 KiB
ca-certificates  2024.8.30     h56e8100_0          155.1 KiB
certifi          2024.8.30     pyhd8ed1ab_0        159.9 KiB
distlib          0.3.9         pyhd8ed1ab_1        267.7 KiB
filelock         3.16.1        pyhd8ed1ab_1        17 KiB
libexpat         2.6.4         he0c23c2_0          135.8 KiB
libffi           3.4.2         h8ffe710_5          41.1 KiB
liblzma          5.6.3         h2466b09_1          101.9 KiB
libmpdec         4.0.0         h2466b09_0          86.6 KiB
libsqlite        3.47.2        h67fdade_0          870.4 KiB
libzlib          1.3.1         h2466b09_2          54.2 KiB
openssl          3.4.0         h2466b09_0          8.1 MiB
packaging        24.2          pyhd8ed1ab_2        58.8 KiB
pip              24.3.1        pyh145f28c_0        1.2 MiB
pipenv           2024.4.0      pyhd8ed1ab_0        2 MiB
platformdirs     4.3.6         pyhd8ed1ab_1        20 KiB
python           3.13.1        h071d269_102_cp313  16 MiB
python_abi       3.13          5_cp313             6.6 KiB
setuptools       75.6.0        pyhff2d567_1        756.1 KiB
tk               8.6.13        h5226925_1          3.3 MiB
tzdata           2024b         hc8b5060_0          119.5 KiB
ucrt             10.0.22621.0  h57928b3_1          546.6 KiB
vc               14.3          ha32ba9b_23         17.1 KiB
vc14_runtime     14.42.34433   he29a5d6_23         736.6 KiB
virtualenv       20.28.0       pyhd8ed1ab_0        3.2 MiB
vs2015_runtime   14.42.34433   hdffcdeb_23         17.2 KiB
Package          Version       Build               Size

Exposes:
pipenv-resolver, pipenv
Channels:
https://prefix.dev/conda-forge

conda create -n python3-8-3 "python=3.8.3" installs the same conda packages as above, and has the same errors, so maybe it's an effect of the pixi global install. I am able to pip install packages into that conda environment, so I don't think it's a firewall issue.

I suspect it's either a pipenv issue, or a pixi global install pipenv issue.

On my Linux machine, the described commands work just fine.
I wonder if that problem is Windows related.

Since pipenv also fails with conda, I will go ahead and close this issue.
Thanks for the report @jamesmyatt!
If the pipenv developers have ideas on how to improve this situation, we are happy to help.


Tooltips

FYI, here's a live using this feature: http://gcmd.arcticlcc.org/ (expand a tree a couple levels to see the tooltips). The tooltips are implemented as badges. If there's a chance if this being merged, I'll clean it up and add docs...

@bagesh2003 Changed "showTips" to "showTip"


Function "read_raw_edf"  have some channels which dosen't apear in version 0.23.0

I used args "exclude"  to get the specific channel data before version 0.23.0.
Since it's much faster than read all data and pick channel data.
But when I upgrade mne to 0.24.0 , it would have bug .
There have some channels that dosent apear in version 0.23.0.
It will appear this warning , and I cannot read them in raw edf data.
RuntimeWarning: Channel names are not unique, found duplicates for: {'Impedance', 'Rate', 'Sum', 'Pressure', 'Fast', '(Imp)', 'Leg'}. Applying running numbers for duplicates.
And this is my function  to get specific channel data in 0.23.0.
def get_channel_name(edfname): ## Read  edf channel name
    with open(edfname,'r') as f:
        _ = f.read(96+120+36)
        channel_num = int(f.read(4))
        return  [f.read(16).strip() for i in range(channel_num )]

def get_channel_data(edfname,need_channels):
    ch_names = get_channel_name(edfname)
    exclude_channels = ['' if the_ch in need_channels else the_ch  for the_ch in ch_names ]
    data = mne.io.read_raw_edf(edfname,exclude=channel_list,verbose=False)
    return data.get_data() , data.info['sfreq'] , data.ch_names

Function "get_channel_name" is copy from function "_read_edf_header" in version 0.23.0.

I would not recommend copying and using internal code with all these magic numbers (96+120+36), this is very brittle and likely to break anytime. In addition, you are opening the file in text mode instead of binary (should be 'rb').
In any case, this still works for me in 0.24. However, a better approach is to first load the data with preload=False. This won't load the data, but you will get the header information, including channel names. You can then use raw["ch_names"] to

either construct the exclude argument and then load the data again with preload=True or
drop channels you do not need with raw.drop_channels() and then load the data with raw.load_data().

@cbrnr  Thanks for reply this issue.
I would try to use new method you provide to get the specfic channels data.
Because of the channels I need have different frequence so I use exclude .
And I found out why I received a warning about duplicate channel names.
In function "_read_edf_header" in v0.24.0
        ch_names = []
        ch_types = []
        for ch_idx, this_label in enumerate(ch_labels):
            # if no channel type, then we will default to eeg
            ch_type = None
            ch_name = this_label

            # space is found, so the prefix is the channel type. 'Annotations'
            # is also a keyword we search for
            if (this_label.count(' ') == 1) and \
                    ('Annotations' not in this_label):
                ch_type, ch_name = this_label.split(' ')

                # channel types should be upper case for easy comparison
                ch_type = ch_type.upper()

It would split channels name by space and cause some channels have the same name.
Maybe the EDF files I owned is not in typical format....
My channel names contain a lot of spaces.
Anyway, thank you for answering my question.

Glad I could help and that you could solve your issue! EDF channel names are poorly specified, and you are correct that from 0.24 we now detect if they contain spaces. We use this information to deduce channel types, which works for common cases such as "EEG Fz". Apparently, this should only be the case if we detect known prefixes.
Could you please post the channel names you have in (one of) your files? If these are unique, the warning about duplicate names should not appear, but if it does this might indicate that we're not doing the correct thing. Thanks!

My channels contains :
E1 ,
E1 Impedance,
O1 ,
O1 Impedance
Then the channles "Impedance" would be duplicated.
But I think this is my own file format problem.
I even need to write another header reader to solve this problem because It have some channel names longer than 16.

Thanks @0220220313! I think at least partly MNE-Python is doing the wrong thing here, there shouldn't be any duplicate channels names because these are unknown prefixes. Could you share one of your files so that I can reproduce the problem? If you have some channel names that are too long this would be a separate issue.

I am glad to help you.
Here is the example EDF .
example.zip
Some of the origin channel names in UI of my device are longer then 16 , they would be wrote only 16  chars in edf.
Since the final char of channel name would be drop by function "_read_edf_header " , if the channel name lenth is 16 chars.
I need to wite another function to read channel names.
Therefore, I think there is something wrong with my device when exporting EDF files.

Thanks! You are correct that EDF channel labels are 16 characters at most. If you have longer labels originally, then yes, I think you should try to shorten the names if possible so that nothing is lost when you export to EDF.
However, the first few channel labels in your example file are:
1
1 Impedance
1-2
1-2 (Imp)
1-F
2
2 Impedance

MNE-Python reads these as:
1
Impedance-0
1-2
(Imp)-0
1-F
2
Impedance-1

So even though unknown prefixes should be ignored, they are actually removed. It seems like labels are split on the first space character, and the first part (the prefix) gets removed no matter what. That's why suddenly there are duplicates, which should not happen (Impedance-0 and Impedance-1 should be 1 Impedance and 2 Impedance).
I will take a look and try to fix this.

Thanks,hope this problem can be resolved smoothly.

@0220220313 FYI a fix is ready in #10058 (also ping @adam2392 if you are interested).


Add GPS Attribute to sensor

Example in lovelace UI to show the car, in this case a Zoe, on the map.
type: map
default_zoom: 13
entities:
  - entity: sensor.zoe
hours_to_show: 24

Hi @myhrmans
Thanks for the PR, but I think some of this is already available in the develop branch.
Can you please review your PR accordingly?

Hi,
If you rebase the patch against the develop branch, you'll find that only the Readme update becomes relevant.

Hi @epenet
I see. Missed the development branch when I did the commit.
One note:
I think the Map Card in Home Assistant needs the attributes without "location_" before lng and lat.
Not sure about this tho.
I'll remove this PR since it's not relevant anymore.


Fix build on macOS runner which is apparently arm now

@dotnet/silk-dotnet anyone can review this one

The new job is failing because we weren't building the whole sln before, fixed on my branch :/ recommend merge with this failing for now


jpg and png image not upload but show message (File Uploaded Successfully)

everything is done, file work 100%, not show error

Can you find uploaded file on the server side, or can you provide broken image path?

I have the same problem on Ubuntu 16 with php 7 and nginx
On local server(xampp) image upload, but on production(ubuntu) server file manager do not upload image and response uploaded successfully. File upload, problem just with image.
I can not find uploaded file on the server. Also on Linux i have this message  laravel-filemanager::lfm.message-extension_not_found

+1 Same thing happening here.

@DeehSlash you may try to install php-gd or php-magick

@FreedomKnight Thanks. After install php-gd everything work


Most fields

We could tune results by having multiple fields with different analyzers and rank on most of them as described here.
For instance, we could have the following:

Original, unchanged field
Stemmed field (refs #82)
Field with synonyms (refs #96)

This needs reindexing.

https://www.elastic.co/blog/multi-field-search-just-got-better


refactor: How Sveltekit routing and client deals with IPC and websockets

It's possible that there's a much smoother way to open up a ws thread to Pieces API
See:
https://github.com/suhaildawood/SvelteKit-integrated-WebSocket
https://github.com/ubermanu/sveltekit-websocket
This is going to be harder to test as we'll get rate-limited in no time.

I don't think this is a risk anymore. We've added some client-side checks to make sure any websocket thread is only spawned when the browser window is present.
I think that should be all that's needed right now as we're using (at most) one class that creates one thread. We could revisit this it ever grows into something complex down the line.


[Website] 404 on  Component's playground sample images

The dropbox content cannot be found, displaying this. Thought you'd like to add fresh ones to make it look better!

Hey, I want to work on this.
Can you share the new avatar URLs ?

Feel free to pick whatever you like and add it to the www/images folder in the documentation :)

Is this issue still available?
I would love to try fixing it.

#1823 is available to fix or it is already fixed?


Double-clicking identifier will select $

Godot version
bc2445d
System information
W10
Issue description
3.x

4.0

Steps to reproduce

Add some node path using $
Double click it

Minimal reproduction project
No response

This may be done by design, but I'm not 100% sure. The list of non-word characters used for word breaking is now configurable in the Editor Settings.

This may be done by design, but I'm not 100% sure. The list of non-word characters used for word breaking is now configurable in the Editor Settings.

Then the defaults should be changed probably.

Then the defaults should be changed probably.

To me both behaviors make sense here. If you want to replace the node name not selecting $ is useful, but if you want to copy/move the actual "reference to a node" which $Test is, it's convenient that it's fully selected.
This might also have been done by design for the $ operator specifically, as this behavior doesn't reproduce in a string:

CC @Paulb23 @bruvzg @vnen

The newly added % syntax doesn't have this issue, creating an inconsistency.

Fixed by https://github.com/godotengine/godot/pull/93656


Can't send custom Payload other than APS

Please add a provisioning to send a custom payload along with APS key.

Hi!
I'm not really sure what you mean, can you elaborate?

I can send a payload like

{
"aps":
{
"alert":"Testing.. (59)",
"badge":10,
"category":"MAIL",
"content-available":1,
"mutable-content":1,
"sound":"default"
}
}

but not like  with a additional payload than APS

{
"aps":
{
"alert":"Testing.. (59)",
"badge":10,
"category":"MAIL",
"content-available":1,
"mutable-content":1,
"sound":"default"
};
"addInfo":
{
"threadId":"0"
}
}

Your JSON is malformed. The same problem as in your ticket you created in NWPuser
https://github.com/noodlewerk/NWPusher/issues/52
{
  "aps": {
    "alert": "Testing.. (70)",
    "badge": 10,
    "category": "MAIL",
    "content-available": 1,
    "mutable-content": 1,
    "sound": "default"
  },
  "addInfo": {
    "testKey": "TestValue"
  }
}

Tanks for helping out @JanC :)


Remove “awaiting confirmations” that are older than 5 days.

Tech questions from Chris to himself:

Can this be done when the sheet is opened?
Is it possible to set the “Status” in the master client sheet to “Reassigned”?

The "Availability Raw" sheet keeps this data, so no need to keep it in two places.

Closed wrong issue

Shouldn't be needed when https://github.com/usdigitalresponse/npi-lawyer-client-matching/issues/10 is fixed.


Hints containing modifier do not trigger

Describe the bug
When defining a hint with a key combination containing a modifier, for example
<C-W>, it will not trigger.
Config options
Consider the following hint:
hints = {
    ['<C-W>[hjkl]'] = {
        message = function(keys)
            return 'Use <A-' .. keys:sub(7) .. '> instead of ' .. keys
        end,
        length = 2,
    },
}

Expected behavior
When typing <C-W>h, the hint "Use  instead of h" should be shown.
Screenshots
N/A
Additional context
N/A

3 problems:

- is a magic characters so you need to escape it. (see Programming in Lua)
The length is the length of the final matched string, so it should be 6.
key:sub(6) should be key:sub(7) to get the final character of the string.

["<C%-W>[hjkl]"] = {
   message = function(keys)
      return "Use <A-" .. keys:sub(6) .. "> instead of " .. keys
   end,
   length = 6,
},

This should work.

Btw, I am really happy to know that there are people using the custom hint configuration!
Please consider sharing your custom hints in the discussion. I am curious about what other people have created!

3. key:sub(6) should be key:sub(7) to get the final character of the string.

<C-W>h
123456 <<<

Nope, it is really 6. Thanks for helping, though. It works now!
Also, thank you so much for adding all of the builtin hints. They are really
useful and must've taken a long time to come up with and write.


Separate the definition of a concrete index from the profile

Background: Orthogonal features live in different documents
A general principle within the collection of Solid specs is to describe orthogonal concerns in different documents.
For instance, WAC is defined in a separate document of itself.
Observation: Profiles and indexes seem orthogonal
The current Solid WebID Profile defines a specific kind of index, namely the type index.
Whereas indexes are important and crucial, it seems that they are an orthogonal concern:
indexes exist independently of profiles.
Furthermore, I expect different kinds of indexes to be defined in the near future,
whereas we probably want to strive for a profile document with a long lifetime.
Hence, I am making the following proposal for type indexes.
Proposal: move type indexes into a separate document
Required steps:

Create a separate specification document for the type index (or indexes in general)
Explain in the profile document that profiles MAY (or SHOULD, or MUST) contain an index.

Link here to the type index specification

Happy to help realize this proposal via a PR. However, I first wanted to start the discussion on this.

I don't have an objection to doing it this way. @timea-solid - thoughts?

@RubenVerborgh we discussed it over at the meeting and we have some further questions:

what kind of indexes do you think of? Is it going in the direction of automatically generated indexes for search purposes?
spec structure-wise - how would this separation looks like? What version would it have?

@timbl mentioned the phrase "Instance Discovery".  This suggests to me a way to distinguish which parts go in which spec.  The WebID Profile spec covers discovery of the typeIndex documents.  The Type Index spec covers discovery of the type registration instances which are found in the type index documents.  We would not need much overlap - a sentence or two can describe how to find the type index documents and generally what they contain and leave all the rest to the type index spec.

Hey @timea-solid!

we discussed it over at the meeting and we have some further questions:

Thanks a lot! I'll write some proposed answers below.

what kind of indexes do you think of?

There can be many different indexes for different purposes.
These are a couple of concrete examples:

subject indexes
property indexes
shape indexes
full-text indexes
cross-Pod indexes
…

Type indexes cover the specific case where the predicate is rdf:type. And that's an interesting case, but there are many more ways that we'll see in the future.

Is it going in the direction of automatically generated indexes

Presumably this is about whether the server, client, or an agent maintains the indexes. I'd say this is an orthogonal question, in the sense that all options are possible for each index. So it is up the specifications of those indexes to define that (or leave it open so multiple options are possible).

for search purposes?

There are many purposes; search is just one of them.
For instance, even though the type index has been designed for discovery, we are using it for query optimization as well. And more purposes can be imagined.

spec structure-wise - how would this separation looks like?

I'd imagine:

one spec detailing the type index

which is independent of the profile spec

one spec detailing expectations for a profile document

which includes a type index, so the profile spec links to the type index

So that matches with what @jeff-zucker wrote above. (Thanks, Jeff!)

What version would it have?

They can be independently versioned.

Thanks @RubenVerborgh for filling the gaps.
I had a good hunch of the type of indexes you had in mind.
In general, the team is for your proposal. The only remaining question is: is now the time for it?

Thanks, @timea-solid!

is now the time for it?

Well, given that the profile spec seems about to be published, I think it's best that it is directly published in an appropriate manner, so with orthogonal concerns separated.
Note that my proposal is currently only this separation, such that future extensions to indexes are possible. I am not proposing for these future extensions to happen now.
If this separation is accepted, I'm happy to help realize it.

Besides the consideration to separate the documents:
@RubenVerborgh (as well as anyone else that's interested), I can only encourage you to consider committing to a specific role for the new document, i.e., primarily as an editor and/or author.

If the team accepts to proceed, I'm happy to perform the split and act as a temporary editor.

@RubenVerborgh, can you keep us posted as to where (and/or when) we can contribute more to the new index doc? Thanks!

@woutermont the new home of the Type Index is: https://github.com/solid/type-indexes Feel free to open discussions or git issues on the new repo.


See screen sizes in piwik backend

I think it would be useful to see the screen size of the tracked devices in the piwik backend. Currently there is only one screen size called "unknown".

That is an easy thing to implement. In this document the res parameter is described as: The resolution of the device the visitor is using, eg 1280x1024.
I think it is save to say that that the resolution of a device never changes so we don't need to save the resolution for every event, but rather send it along. I think the best thing would be to have them as properties of the Event struct but don't implement them with the need to set it externally. Something like let screenSize = Device.makeCurrentDevice().screenSize. The other thing then would be to encode the size in the Events queryItems which encodes an event into an array of URLQueryItem.

Assign this to me. I'll try working on it over the week.

There is no need to assign issues. I am looking forward to you pull request. If you want to bounce ideas back and fourth just let me know.

Can you let me know how to test the app, I pulled upstream from develop.
The build succeeds, but the tests dont work. Do I need to change targets in
project settings? How do I know if I add a parameter to to the Event struct
is reflecting while creating the url for the server.
Thanks.
On Mon, Jun 5, 2017 at 11:57 AM, Cornelius Horstmann <
<EMAIL_ADDRESS>wrote:

There is no need to assign issues. I am looking forward to you pull
request. If you want to bounce ideas back and fourth just let me know.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/piwik/piwik-sdk-ios/issues/149#issuecomment-306113395,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGg5M4QxVwoaB6RBb-XlMcM-sfg9JyfOks5sA5-2gaJpZM4NpCUf
.

Got my tests to run. Had an issue with pods. Made change in Tests. A file was using Tracker instead of PiwikTracker. Tests ran successfully. Still can run the Example.

Hi @akshaykolte thank you for your PR. I just checked about the Example application. There is the same issue like in the Tests. It's a merge issue. The example application should work, if you edit the OptOutViewController.swift and replace all Tracker with PiwikTracker. Sorry for that!


Extending ApproximateQuantiles functionality to deal with non-uniform weights.

Extending functionality of ApproximateQuantiles PTransform to calculate quantiles of a data stream with custom weights. In case of weighted quantiles, input PCollection is expected to contain tuples of elements with their weight.
Also adding add_inputs function to the corresponding CombineFn for efficient processing of batched inputs.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @chrisgorgo

Friendly ping @pabloem

Ah yes, I had started doing the review. I'll wrap it up today.

Great, thanks!

the precommit tsts are currently broken on mainline, but also I think there's some docs issues in your pr. You can run tox -e py38-docs to run the docs tests

Was just looking for a way to do that, thanks a lot!

there's a strange 3-canceled message. I believe this is a bug wiith our test infra. I'll rerun the tests. this LGTM.

retest this please

Run Python PreCommit

thanks @iindyk

Thanks for the review @pabloem


Native Editor - variable explorer functional test

Not validated. Looks like the variable explorer tests are failing on our flake build runs:
https://dev.azure.com/ms/vscode-python/_build/results?buildId=39756

Looks like the timing for waiting for the variable explorer on the native editor is inconsistent. I think we likely need a better way to tell when the variable explorer is finished. Maybe a message.

The test 'Variable explorer - Loading (native)' fails on Windows.

What does it do?

The loading one is still flakey as it requires us to 'not' wait until all variables are ready

You can see it passes most of the time on the nightly flakey runs.

I see but it fails consistently in my machine. If there is no solution for that test in particular maybe we can leave only that one with the flakey tests?

Or we can just look into making that test less flakey. Can you log a separate issue for that?

Sure.
Validated.


CI broken by change "Make ECMASCRIPT_NEXT the default language out"

Our CI test for integration with npm has been broken since http://go/gh/google/closure-compiler/commit/ac3e3303617e23aed24eb7574e1d140565aa079a
I suspect I just need to find the right place to change the tests to explicitly request ES5 output.

Will be fixed by https://github.com/google/closure-compiler-npm/pull/221

Fixed by the submitted PR


Can the repo support roi feature extraction

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps you followed while encountering the bug
Expected behavior
A clear and concise description of what you expected to happen.
Thanks for your work! The repo now support extract video feature from a video or a set of frames
It will be better if it supports the ROI feature extraction part.
Screenshots/Code Output
If applicable, add screenshots or code output to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Ubuntu 16.04]
Python Version
PyTorch version

Additional context
Add any other context about the problem here.

Hello,
Thank you for using the framework and the suggestion. Could you elaborate on that? As far as I know, the Slowfast model does not make use of separate ROIs.

Hi,
When training on the AVA dataset, the SlowFast model using ROI feature to classify actions. The related code is in the slowfast/model/head_helper.py   ResNetRoiHead class
`    def forward(self, inputs, bboxes):
assert (
len(inputs) == self.num_pathways
), "Input tensor does not contain {} pathway".format(self.num_pathways)
pool_out = []
for pathway in range(self.num_pathways):
t_pool = getattr(self, "s{}_tpool".format(pathway))
out = t_pool(inputs[pathway])
assert out.shape[2] == 1
out = torch.squeeze(out, 2)
        roi_align = getattr(self, "s{}_roi".format(pathway))
        out = roi_align(out, bboxes)

        s_pool = getattr(self, "s{}_spool".format(pathway))
        pool_out.append(s_pool(out))

    # B C H W.
    x = torch.cat(pool_out, 1)

    # Perform dropout.
    if hasattr(self, "dropout"):
        x = self.dropout(x)

    x = x.view(x.shape[0], -1)
    x = self.projection(x)
    x = self.act(x)
    return x`

Here  out = roi_align(out, bboxes) is the ROI feature in a set of frames, right?
It will be great if the toolbox support object detect and feature extractract, such as person detect and person feature extract in a video or a set of frames.

Unfortunately, I do not have the bandwidth to work on this at the moment. So closing this issue for now.


Upgrade validator major version

Just ensure we're using the latest validator package version.
No breaking changes as far as I know.

Thanks for this. I'm going to include part of this PR but release this as a major release update. The reason being is we're jumping two versions of validator 7.0.0 > 9.4.0 and there may be breaking changes within validator itself for the users of mongoose-validator (i.e. a validator being removed). I have looked through the validator release history but can't find a list of what has changed (without going through the hundreds of commits in the history).

New 2.0.0 release includes update to latest version. Thanks.


Rename "data management" tool in Data Exploration to Cell sets and Metadata

Description
I was looking at Data Exploration and trying to talk to someone about this "data management" tool. Because it has the same name as the data management module, it is ambiguous to talk about it. I talked to Vicky and she suggested to change it to "Cell sets and Metadata" instead.
Details
URL to issue
N/A
Link to staging deployment URL (or set N/A)
https://ui-ivababukova-ui682.scp-staging.biomage.net/
Links to any PRs or resources related to this PR
N/A
Integration test branch
master

Merge checklist
Your changes will be ready for merging after all of the steps below have been completed.

Code updates
Have best practices and ongoing refactors being observed in this PR

[ ] Migrated any selector / reducer used to the new format.

Manual/unit testing

[ ] Tested changes using InfraMock locally or no tests required for change, e.g. Kubernetes chart updates.
[ ] Validated that current unit tests for code work as expected and are sufficient for code coverage or no unit tests required for change, e.g. documentation update.
[ ] Unit tests written or no unit tests required for change, e.g. documentation update.

Integration testing
You must check the box below to run integration tests on the latest commit on your PR branch.
Integration tests have to pass before the PR can be merged. Without checking the box, your PR
will not pass the required status checks for merging.

[ ] Started end-to-end tests on the latest commit.

Documentation updates

[ ] Relevant Github READMEs updated or no GitHub README updates required.
[ ] Relevant Wiki pages created/updated or no Wiki updates required.

Optional

[ ] Staging environment is unstaged before merging.
[ ] Photo of a cute animal attached to this PR.

Why 'Cell sets and Metadata' and not 'Cell Sets and Metadata'?

Why 'Cell sets and Metadata' and not 'Cell Sets and Metadata'?

We have "Custom cell sets" for scratchpad and also these

So I don't think this is wrong necessarily.

Won't "Cell sets and Metadata" right over "Cell sets" and "Metadata" feel a little redundant?
What about perhaps calling it "Cell sets personalization" or something like that?

Won't "Cell sets and Metadata" right over "Cell sets" and "Metadata" feel a little redundant?
What about perhaps calling it "Cell sets management" or something like that?

Good point. But if I call them "Cell sets management", then that makes "metadata" feel out of place


Mobs wont spawn in certain worlds even when its true

so basically there is something wrong with some of my worlds, in certain worlds, creeper eggs don't work, some spawners wont work either. I checked my config and it says for all worlds that its true but it still wont work please help me.

check if you are using latest version of multiverse. https://dev.bukkit.org/projects/multiverse-core
Most likely is a separate plugin or your server/spigot configs causing this issue. Try removing all plugins other than mv to test as well.

Possibly related to #2401
Closing this due to inactivity. If you are still having issues, do create a new issue and follow the new issue template or ask in our discord https://discord.gg/NZtfKky


Closing discovery item fails with AttributeError: 'Http' object has no attribute 'http'

The following line fails, looking at httplib2 shouldn't this be self._http.close() instead?
https://github.com/googleapis/google-api-python-client/blob/2d076b87cff4029a243357dad19564767bbf8751/googleapiclient/discovery.py#L1335

Hey @ghaithbilbeisi, could you show more of the stack trace?
From discussion in #1047 it looks like the issue is the low version of httplib2. I also see that this wouldn't work correctly if you were passing in your own httplib2 object (in that case it should just be self._http.close()).

Hi @busunkim96 , I get this when running my unittest with the following:
def test_build_drive(self):
    creds = utils.authenticate('client_id.json')
    drive = utils.build_drive(creds)
    self.assertIsNotNone(drive)
    if drive:
        drive.close()

Using the following authenticate and build_drive methods:
def authenticate(secret):
    """ Returns an oauth credentials object using the given secret, or stored credentials if available. """
    SCOPES = 'https://www.googleapis.com/auth/drive.readonly'
    store = file.Storage('storage.json')
    creds = store.get()

    if not creds or creds.invalid:
        flow = client.flow_from_clientsecrets(secret, SCOPES)
        creds = tools.run_flow(flow, store)

    return creds

def build_drive(creds):
    try:
        drive = discovery.build('drive', 'v3', credentials=creds)#http=creds.authorize(Http()))
    except:
        drive = None
    return drive

Running this with google-api-python-client 1.12.3, httplib2 0.18.1, and python 3.8.3 gives the following error:
Traceback (most recent call last):
  File "token_test.py", line 16, in test_build_drive
    drive.close()
  File "/Users/ghaithbilbeisi/miniconda3/lib/python3.8/site-packages/googleapiclient/discovery.py", line 1335, in close
    self._http.http.close()
AttributeError: 'Http' object has no attribute 'http'

I think the proper fix for this is to add close to AuthorizedHttp. Opened https://github.com/googleapis/google-auth-library-python-httplib2/pull/14

I'm going to close off this issue as google-auth-httplib2 0.1.0  was released on Monday with the fix from https://github.com/googleapis/google-auth-library-python-httplib2/pull/14 . If you're still having trouble after updating google-auth-httplib2, please re-open this issue with more information.

This simple code still raises the same error with latest packages (google-auth-httplib2 0.1.0, httplib2 0.19.0, google-api-python-client 2.0.2).
from googleapiclient.discovery import build

yt = build("youtube", "v3", developerKey="MY_KEY")
yt.close()

Traceback (most recent call last):
  File "test_code.py", line 4, in <module>
    yt.close()
  File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/googleapiclient/discovery.py", line 1364, in close
    self._http.http.close()
AttributeError: 'Http' object has no attribute 'http'

Process finished with exit code 1

I think https://github.com/googleapis/google-api-python-client/pull/1231/ will (finally) fix this. I'll circle back to it next week. Thanks for the report @solzard!

@busunkim96 actually #1231 did not fixed the issue since I am still having it:
Traceback (most recent call last):
  File "./src/sheet2xls.py", line 20, in <module>
    sheet = sheet_obj.get(sheet_id)
  File "/home/runner/.local/lib/python3.8/site-packages/gsheets/api.py", line 141, in get
    return self[id***
  File "/home/runner/.local/lib/python3.8/site-packages/gsheets/api.py", line 121, in __getitem__
    response = backend.spreadsheet(self._sheets, id)
  File "/home/runner/.local/lib/python3.8/site-packages/gsheets/tools.py", line 39, in __get__
    result = instance.__dict__[self.__name__*** = self.fget(instance)
  File "/home/runner/.local/lib/python3.8/site-packages/gsheets/api.py", line 69, in _sheets
    return backend.build_service('sheets', credentials=self._creds,
  File "/home/runner/.local/lib/python3.8/site-packages/gsheets/backend.py", line 34, in build_service
    return apiclient.discovery.build(**kwargs)
  File "/home/runner/.local/lib/python3.8/site-packages/googleapiclient/_helpers.py", line 134, in positional_wrapper
    return wrapped(*args, **kwargs)
  File "/home/runner/.local/lib/python3.8/site-packages/googleapiclient/discovery.py", line 324, in build
    discovery_http.close()
AttributeError: 'Http' object has no attribute 'close'
##[error***Process completed with exit code 1.

from pip list:
google-api-core          1.26.3
google-api-python-client 2.1.0
google-auth              1.28.0
google-auth-httplib2     0.1.0
googleapis-common-protos 1.53.0
httplib2                 0.19.1

@niva83 I'm not able to reproduce the error you're seeing. Could you share the bit of your code that calls discovery.build?
from googleapiclient import discovery

service = discovery.build("cloudasset", "v1")

service.close()

The stack trace seems to suggest it's failing on closing discovery_http, which is just a plain httplib2 object rather than one from google_auth_httplib2. https://github.com/googleapis/google-api-python-client/blob/a5d20813e8d7589b0cec030c149748e53ea555a5/googleapiclient/discovery.py#L324
Could you try this code to see if you can close a plain httplib2.Http instance? If this doesn't work, the version of httplib2 you have installed may be too old.
import httplib2

http = httplib2.Http()

http.close()

@busunkim96 thanks, I will test this week and let you know how it goes.

Hi @niva83 , I'm going to close this off as guidance has been provided in https://github.com/googleapis/google-api-python-client/issues/1046#issuecomment-815016260. If you're still having trouble, please re-open it with more information.


chore: upgrade reqwest to 0.9.5

Proposed changes
This PR upgrades reqwest dependency.
Types of changes

[x] Build (changes that affect the build system)

Checklist

[x] I have read the CONTRIBUTING documentation
[x] Lint and unit tests pass locally with my changes

https://github.com/ArkEcosystem/rust-client/pull/14