TabbarController support

Thanks for making this awesome tool!
I use it in a tab bar controller app.  Unfortunately when the console is shown the tab bar gets another empty tab added for the console. Probably this window.rootViewController?.addChild(consoleViewController) is the problem.
Any idea on how to fix this?

Fixed it temporarily by removing it from the tab bar and adding it as a child viewController to the first controller from the tab bar.


Create @shopify/logger

Problem Summary
Logging is an important tool in a developer’s arsenal. It can be used to debug applications both in development and production to better diagnose problems. It can be used, along with statistical analysis, to gain insight into the activity of even the most complex distributed systems.
As Shopify becomes increasingly distributed and complex, it will become imperative that logging is something that we do right.
We eventually want to build a great experience with a nice API, filtering, and a slick UI. By getting the API right and creating a nice separation of concerns, we allow for ease of continuous improvement for things like filtering, etc.
In development, for web application, there are concerns around simultaneous, asynchronous requests. We want immediate feedback, but, when many requests are happening at the same time, the UI is hard to get right.
In production web applications, stdout is our interface into splunk (via fluentd). We want our logs to have context about our application, and perhaps we want to aggregate these logs, so that we send only a single JSON payload to splunk per request.
For CLI applications, we’d like to avoid duplicating work in creating a nice UI for logging. It would be nice if our logger was not specifically tied to server applications.
Proposed Solution

Logging is split into 2 stages:

Logging (API emits intermediate data)
Formatting (converts intermediate data into desired format)

We use JSON as the intermediate logging format (pino / bunyan / bole)
The core logging API will stay as close as possible to https://console.spec.whatwg.org

If API exists, we’ll use it:

.time, .timeEnd

If API doesn’t exist, we’ll use idiomatic naming:

.tag, .tagEnd

Buffering for production is handled by @shopify/koa-logger

Why?

By splitting logging into 2 stages, we conceptually decouple the concept of an API from the concept of a logging UI. This allows us to focus on perfecting the 2 independently of each other.
By logging to a JSON format, we can easily create aggregation or filtering logic that gets applied before the logs get formatted. Again, we can do all of this independently of the logger API mechanism.
By staying close to the console specification for our API, we reduce friction for new developers into our code base. We also defer to the W3C arguments or differences of opinion for how things like tagging, grouping, or timing should be done. Sometimes it’s nice to have a decision made for you in a consistent way, even if it’s not your favorite outcome.

References
Inspiration was taken from many sources, but the primary influences were:
http://getpino.io/#/
https://github.com/klauscfhq/signale
https://console.spec.whatwg.org/

On separation of logging and formatting
There are several possible solutions here:

piping the output of a script to a formatting script
outputting the logs to a custom stream
the logger exposes an observable stream, and the formatter can listen and attach itself to this stream
same as above, but using an event-driven approach, rather than observables
the formatter exposes a function to receive input, and the logger gets passed a formatter on initialization

Using I/O streams seems overly complex for this scenario., whether in the code or via an OS pipe. Since we'll need our production logging in koa to accumulate logs into a single JSON object per request, I think it makes sense for a Formatter to be an object that can maintain state. Furthermore, I feel that the formatter should be passed into the Logger in order to reduce glue code.

Here's what I'm thinking, as of right now, for a basic console formatter:

The color schema is inspired by https://github.com/klauscfhq/signale, and the timestamps are similar to https://github.com/visionmedia/debug, but using https://github.com/sindresorhus/pretty-ms

With Error payloads, we could produce something like like this:

I'm not a fan of this error log, the more I look at it. I'd like to find something a bit cleaner.

I like this UI a lot better:


How do I get the metadata of each instance

I have two instances， instance A1，instanceA2,they point to the same service s1。
I configured metadata in A1，version=v1
I configured metadata in A2，version=v2
when i   execute  discoveryClient.getInstances(name)，I can only get the metadata of S1,such like 'version/region',I can't get this data.
How can I solve this problem
yaml Examples
apiVersion: v1
kind: Service
metadata:
name: discovery-springcloud-example-c
labels:
app: discovery-springcloud-example-c
service: discovery-springcloud-example-c
spec:
ports:

port: 8080
name: http
selector:
app: discovery-springcloud-example-c

apiVersion: apps/v1
kind: Deployment
metadata:
name: discovery-springcloud-example-a-v1
labels:
app: discovery-springcloud-example-a
version: v1
spec:
replicas: 1
selector:
matchLabels:
app: discovery-springcloud-example-a
template:
metadata:
labels:
app: discovery-springcloud-example-a
group: example-service-group
version: v1
region: common
env: env1
zone: zone1

apiVersion: apps/v1
kind: Deployment
metadata:
name: discovery-springcloud-example-a-v2
labels:
app: discovery-springcloud-example-a
version: v1
spec:
replicas: 1
selector:
matchLabels:
app: discovery-springcloud-example-a
template:
metadata:
labels:
app: discovery-springcloud-example-a
group: example-service-group
version: v1
region: common
env: env1
zone: zone1
spec:
***

Are you saying you can only get the metadata from the service and not from the individual pods?

Are you saying you can only get the metadata from the service and not from the individual pods?

Are you saying you can only get the metadata from the service and not from the individual pods?

Thanks for your response.
Just as you described it. i want to get metadata from the individual pods
just like eureka
instance A
eureka.instance.metadataMap.group=example-service-group
eureka.instance.metadataMap.version=1.0
instance B
eureka.instance.metadataMap.group=example-service-group
eureka.instance.metadataMap.version=1.1
When I call discoveryClient.getInstances(name) , The metadata for each instance is unique,For example, version is configured above
I want this result, what should I do

Are you saying you can only get the metadata from the service and not from the individual pods?

Thanks for your response.
Just as you described it. i want to get metadata from the individual pods
just like eureka
instance A
eureka.instance.metadataMap.group=example-service-group
eureka.instance.metadataMap.version=1.0
instance B
eureka.instance.metadataMap.group=example-service-group
eureka.instance.metadataMap.version=1.1
When I call discoveryClient.getInstances(name) , The metadata for each instance is unique,For example, version is configured above
I want this result, what should I do

Right now we just retrieve the metadata for the service not the individual pods.
If you could get the metadata for the pods how would you use that information?

Right now we just retrieve the metadata for the service not the individual pods.
If you could get the metadata for the pods how would you use that information?

Right now we just retrieve the metadata for the service not the individual pods.
If you could get the metadata for the pods how would you use that information?

Thanks for your response.
We expect to get the POD metadata for instance filtering,and we use metadata for grayscale publication.
At Eureka, Consul, we have implemented the corresponding functionality.But on the sck, we met resistance.
We tried to do this by modifying a lot of the source code,this may conflict with the sck's escalation.
So, can you help us solve it at the sck level.

Right now we just retrieve the metadata for the service not the individual pods.
If you could get the metadata for the pods how would you use that information?

Thanks for your response.
We expect to get the POD metadata for instance filtering,and we use metadata for grayscale publication.
At Eureka, Consul, we have implemented the corresponding functionality.But on the sck, we met resistance.
We tried to do this by modifying a lot of the source code,this may conflict with the sck's escalation.
So, can you help us solve it at the sck level.

We expect to get the POD metadata for instance filtering,and we use metadata for grayscale publication.

If requests are being handled by the service in Kubernetes how would you target a specific pod if you had the metadata?

We expect to get the POD metadata for instance filtering,and we use metadata for grayscale publication.

If requests are being handled by the service in Kubernetes how would you target a specific pod if you had the metadata?

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Window title garbled

At least in the Mate DE, the non-ASCII characters in the title of Lagrange's window are garbled - UTF-8 is displayed as a sequence of Latin-1 characters.

The window title is set using SDL_SetWindowTitle() where the title string is in UTF-8. What happens after that depends on SDL's internals and the window system. I would therefore consider this mostly an SDL bug.
I could add a build option (off by default) to force the window title to 7-bit ASCII?

It seems SDL is lagging behind the modern toolkits. I managed to work it around by changing X locale settings.


fix Typed property must not be accessed before initialization error in UpdateRequest class with 7.4+

Since PHP 7.4 introduces type-hinting for properties, it is particularly important to provide valid values for all properties, so that all properties have values that match their declared types.
A property that has never been assigned doesn't have a null value, but it is on an undefined state, which will never match any declared type. undefined !== null.
so we can not check the status of a property in this way:
!$this->update

That's correct. Thanks!


missing Mastodon client configuration!

Not sure whats going on with this one, when i go to run the script it just exits with that error. I have that area of the config file filled out fully.

When i was commenting out twitter i accidentally caught the first bracket as well. now the script runs and doesn't show any error but its also not posting anything from Tumblr as i setup. any way to get a more verbose output and figure out what might be going on on that front?

Just to be sure it was doing anything i at least did some snooping with tcpdump. I can see the bot call out to the tumblr pages ive setup so its at least trying. Cant figure out why its not actually posting anything to the mastodon instance though.

Hmm, I'll have to take a look. I haven't been using Tumblr functionality myself so maybe the API changed since I added it in.

Hey thanks for the quick reply, Starting to think its just something else about my setup. Twitter api got approved and that does not appear to be working either i randomly got it to finally post a single post from one of the tumblrs and then never again. only the RSS seems to work and i cant figure out why. Here is my config for reference
 :twitter {:access-keys
           {:consumer_key "keyhere"
            :consumer_secret "keyhere"
            :access_token_key "keyhere"
            :access_token_secret "keyhere"}
           ;; optional, defaults to false
           :include-replies? false
           ;; optional, defaults to false
           :include-rts? false
           ;; accounts you wish to mirror
           :accounts ["zedrinbot"]}
;;  add Tumblr config to mirror Tumblr accounts
 :tumblr {:access-keys
          {:consumer_key "keyhere"
           :consumer_secret "keyhere"
           :token "keyhere"
           :token_secret "keyhere"}
          ;; optional limit for number of posts to retrieve, default: 5
          :limit 1000
          :accounts ["cyberpunky.tumblr.com" "scipunk.tumblr.com"]}
;; add RSS config to follow feeds
 :rss {"Hacker News" "https://hnrss.org/newest"
      "r/Clojure" "https://www.reddit.com/r/clojure/.rss"}
 :mastodon {:access_token "keyhere"
            :api_url "http://art.kitsuna.net/api/v1/"
            ;; optional boolean to mark content as sensitive
            :sensitive true
            ;; optional visibility flag: direct, private, unlisted, public
            ;; defaults to unlisted
            :visibility "public"
            ;; optional limit for the post length
            :max-post-length 300
            ;; optional flag specifying wether the name of the account
            ;; will be appended in the post, defaults to false
            :append-screen-name? false
            ;; optional signature for posts
            :signature "#mediabot"
            ;; optionally try to resolve URLs in posts to skip URL shorteners
            ;; defaults to false
            :resolve-urls? true
            ;; optional content filter regexes
            ;; any posts matching the regexes will be filtered out
            ;; :content-filters ["."]
            ;; optional keyword filter regexes
            ;; any posts not matching the regexes will be filtered out
            ;; :keyword-filters []
}}```

Oh, I think I know what might be happening here. The bot checks the timestamp on the last post from Mastodon, and then only posts things that are after that to avoid reposting old content. In case there aren't any posts, the time defaults to now. So, any older Tumbler/Twitter posts will get filtered out by that.

Perfect! that appears to have been it didn't realize it wouldn't back pull but it makes sense now that i think about it. Maybe just mention it in the readme to avoid more people like me :P Thanks for the help

Good idea, I'll add a note as it's not really obvious in retrospect. :)


Issue with long horizontal scroll

Hello!
When I was trying to use this component for a long horizontal scroll it didn't work.
I realized what's wrong with that. Look at this method:
handleChangePosition(vScrollbar, orientation){
        // Convert Percentage to Pixel
        let next = vScrollbar / 100 * this.scrollAreaHeight
        if( orientation == 'vertical' ) this.normalizeVertical(next)
        if( orientation == 'horizontal' ) this.normalizeHorizontal(next)
}

I think next variable should have condition either and also using different scrollArea values. At least it works for me.
handleChangePosition(vScrollbar, orientation){
        // Convert Percentage to Pixel
        let next = vScrollbar / 100 * (orientation == 'vertical' ? this.scrollAreaHeight : this.scrollAreaWidth)
        if( orientation == 'vertical' ) this.normalizeVertical(next)
        if( orientation == 'horizontal' ) this.normalizeHorizontal(next)
}

How to check issue?
Just try to create a wrapper div with any width but without height any limit so vertical scroll won't be showed. Then create a content div with 9000+ px width and try to render that.

Hey @pbelyaev, Thank you so much for giving me an issue and giving me its solution at the same time! thanks! :grin: :+1:


Remove outdated alert on PV expansion for encrypted PVs

This alert became obsolete since https://github.com/ceph/ceph-csi/pull/2258
Signed-off-by: Alfonso Martínez<EMAIL_ADDRESS>

/assign @bipuladh @SanjalKatiyar

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/approve

/cherry-pick release-4.12

/cherry-pick release-4.12-compatibility

/test odf-console-e2e-aws


Consider making least_busy a provider method

Combo provider / API request
What is the expected behavior?
Currently least_busy must be run by doing:
from qiskit import IBMQ
IBMQ.load_accounts()
from qiskit.providers.ibmq import least_busy
least_busy(IBMQ.backends())

However, it makes much more sense to have this as a provider method
IBMQ.backends.least_busy() #allow for simulator=False

In addition, internally this queries all backends that are loaded by the provider through individual API calls which is quite slow, averaging about 32 sec for me.  The API should really be tracking the least busy backend (I would be surprised if this is not already the case) so that a single API call can get the least busy backend that an user can access in a fast manner.

Stale issue, closing


feat(logging): custom logger

Logging middleware now can use a custom logger.

Codecov Report

Merging #72 (50498c1) into main (2fa36c1) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #72      +/-   ##
==========================================
+ Coverage   71.89%   71.95%   +0.06%
==========================================
  Files          18       18
  Lines         893      895       +2
==========================================
+ Hits          642      644       +2
  Misses        198      198
  Partials       53       53

Impacted Files
Coverage Δ

logging/logging.go
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[alert] Candidates for hardening

A couple of things to look into and see if it is worth hardening

the "clear" signal right now is not shadowed, which means it could potentially be glitched to skip all the escalation responses.  (@msfschaffner let me know if i misunderstood).

when in "terminal" state all the escalation requests are turned off. Does it make sense when in terminal to just fire all escalations? This is not really that important since the liklihood of glitching into Terminal is low due to sparse encoding and redundant counters.

Question - when escalation sender observes an error does it make sense to cycle back to idle, or should we progress to a state that would both request escalation forever and timeout on pings? The error observed might be a result of a glitch between escalation sender / receiver.  This is closely related to the alert clock/power boundary discussion.

a few questions and possibly hardening suggestions.

Sorry for not responding earlier to this:

let me do that right away (see #7996)

I thought about doing that, but didn't go through with that change so that SW still has the option to implement a protocol that does not reset after scrapping the life cycle state (which would not be possible if we were to assert all countermeasures in the terminal state). however, all countermeasures are asserted if the FSM is glitched into an invalid state
https://github.com/lowRISC/opentitan/blob/da8885eaf4ee34e63cdcaa06bc8f273e925fd60b/hw/ip/alert_handler/rtl/alert_handler_esc_timer.sv#L268-L274
however, one thing we could do is fire all escalation actions that have been programmed for the escalation protocol. e.g. if an escalation protocol has actions 0 and 1 configured, we just fire those two once we get into the terminal state.

yes we can do that. this is closely related to the corner case that @cindychip has found here https://github.com/lowRISC/opentitan/issues/7489.

Hey @tjaychen, WDYT regarding 2. above?

Sorry for not responding earlier to this:

[x]  1st point: let me do that right away (see [alert_handler] Make the CLR register shadowed #7996)

[x]  3rd point: yes we can do that. this is closely related to the corner case that @cindychip has found here [prim_esc_receiver] reserve ping corner case #7489.

[ ]  2nd point: I thought about doing that, but didn't go through with that change so that SW still has the option to implement a protocol that does not reset after scrapping the life cycle state (which would not be possible if we were to assert all countermeasures in the terminal state). all countermeasures are asserted if the FSM is glitched into an invalid state, though:
https://github.com/lowRISC/opentitan/blob/da8885eaf4ee34e63cdcaa06bc8f273e925fd60b/hw/ip/alert_handler/rtl/alert_handler_esc_timer.sv#L268-L274
one thing we could do is fire all escalation actions that have been programmed for the escalation protocol. e.g. if an escalation protocol has actions 0 and 1 configured, we just fire those two once we get into the terminal state.

ah yes! after reading your response, what you described is exactly what I had in mind.
However...do you think this is important to do?  This would only have value if an attacker were somehow able to glitch DIRECTLY to terminal_st while somehow skipping all the others (this should be REALLY hard).  This feels very defense in depth that could maybe be left as an enhancement for the future.

yeah, given that these escalation FSMs are sparsely encoded, I believe this should be really hard to do. I would make the decision dependent on how easy it is to adapt the DV side of things (@cindychip WDYT). if this is not straightforward to do, I would say we punt this for later. @cdgori let us know if you think otherwise.

I think it would be really hard to do reach that specific terminal state directly given all the other protection we have.  It'd be a nice enhancement, but if the DV impact is high I'm ok to punt it.
(I think it's important to do what you said about invalid states above though, since those can be much more easily reached.)

Ok in that case, let's punt 2.. The invalid state handling is already implemented in the current design.


Any way to achieve flex-grow: 1?

In CSS, I can fill a line by stretching some of items:

1

2

3

Is there any way to achieve this with FlexPanel?

The FlexPanel was moved to Avalonia.Labs.
There is no flex-grow, but it shouldn't be hard to implement.


feat: QOL Capabilities functions

Per: https://github.com/CosmWasm/wasmvm/pull/413
I have added some capability functions here instead of in wasmvm.
This way a chain like Juno can add wasmd.GetDefaultWasmCapabilities() for future upgrades without us forgetting to add the capabilities (that wasmd implement)

Thanks for your pr!
Alex is on holidays and will be back in 2 weeks and he can give a better feedback on this work.
Regarding your changes, I am not sure if "default cosmos capabilities" and "default wasm capabilities" names are a bit misleading.
Moreover don't you lose visibility on which capabilities you are actually importing, and don't you need to check anyway on every version upgrade that those functions haven't been modified and some capability was added/removed?

@pinosu
I agree default can be misleading. Will change that worder

Moreover don't you lose visibility on which capabilities you are actually importing

I just wanted to solve for new wasmvm/wasmd funcationality as it comes out. This way upgraded chains don't forget to add cosmwasm_1_# to their capabilities as we get more features.
That way as you upgrade to a future wasmvm 1.3 it would return capabilities cosmwasm_1_1, 1_2, and 1_3 automatically
This is all I was trying to solve for here as we forgot to add this during our testnet launch

Thank you @Reecepbcups !
I think the issue you want to solve makes sense, we just need to find the proper way to do it.
Let's continue this discussion when @alpe is back, he might have some good ideas about it.

Thanks for the PR! I do understand that new capabilities are easy to miss. Therefore I had highlighted this in the changelog.
Nevertheless I am very open to make this better.
With your solution, I have some concerns about the method names as well as the grouping. Let's spike some solutions that work nicely with git diff. I have opened https://github.com/CosmWasm/wasmd/issues/1341

Closing in favour of #1361 . Thanks for bringing attention to the problem! 🏅


[#2990] Raspbian support.

Problem
There was a need for paver.sh changes in python-packages for supporting Raspbian.
Solution
Port the changes from python-packages for supporting Raspbian.
Drive-by fix:

allow ./cache to be a symlink in .gitignore.

How to test
Please review changes.
Run the tests.
reviewer: @adiroiban

needs-review

Changes look good. Thanks
changes-approved


Should not convert negative integer in ruby array as erlang string

I use custom type for parsing ruby ast.
I found that negative integer array of ruby is encoded as erlang string of incorrect value.
def single_neg
  [-1]
end

def two_neg
  [-1,-2]
end

def single_pos
  [1]
end

def two_pos
  [1,2]
end

calling these functions generate incorrect value
1> {ok, R} = ruby:start().
{ok,<0.35.0>}
2> ruby:call(R, './int_ary.rb', single_neg, []).
"ÿ"
3> ruby:call(R, './int_ary.rb', two_neg, []).
"ÿþ"
4> ruby:call(R, './int_ary.rb', single_pos, []).
[1]
5> ruby:call(R, './int_ary.rb', two_pos, []).
[1,2]

the real problem is that it's not a char with proper value
6> Tn = ruby:call(R, './int_ary.rb', two_neg, []).
"ÿþ"
9> lists:nth(1,Tn).
255
10> lists:nth(2,Tn).
254

which should be -1 and -2, not 255 and 254.

Fixed


Month name and arrow doesn't show up

Hello everyone, I'm new here. I have some issues on month name and arrow to change between months on title bar doesn't show up.
Here is the code
 <vue-cal         :disable-views="['years', 'year', 'weeks', 'week']"         :time="false"         selected-date="2019-09-01"         xsmall         click-to-navigate         default-view="month"         events-on-month-view="short"/>

Looking forward for the solution
Thank you!!

Hi @yogaprasss, the markup is correct.
do you have any JavaScript error?
And more important, do you have vue 2.6+ And latest vue-cal (2.0+)?

Hi @antoniandre thank you for your reply
I just found out that my vue version is below 2.6 and my vue-cal version is below 2.0.
Unfortunately, for some reason, I just can't upgrade it to the latest version.
So I decided to make my version of that title bar.
Once again, thank you for your reply and have a good day :)

Ok good. Remember if you use vue-cal version 1.x you should refer to the v1 documentation (there's a link in the top bar of the v2 documentation)


Widget-related getAllWidgets endpoints causing errors

I suspect these endpoints are deprecated, as I can't find a reference to widgets in basyx-java-server-sdk.
There's some widget related endpoints and code in the aas-gui, which are causing some errors.
(In my use-case, also errors in CORS, and due to these errors, the UI seems to be reloading - each reload of the UI is for some reason, downloading approximately 8.2MB each time)
Is there a particular reason to keep them? If not, I could create a PR to remove them.
This is in AppNavigation and MainMenu, with references in a few places to widgets as a concept.
// Function to check if Widget API is available and set the Widget Feature Activation Status in the store
checkWidgetApi() {
    let WidgetApiURL = this.registryURL.split(':') as any;
    WidgetApiURL[2] = '4000';
    // join the array to a string
    WidgetApiURL = WidgetApiURL.join(':');
    // check if the Widget API is available
    let path = WidgetApiURL + '/api/getallwidgets';
    let context = 'trying to connect to Widget API';
    let disableMessage = true;
    // Send Request to get all Widgets
    this.getRequest(path, context, disableMessage).then((response: any) => {
        if (response.success) {
            this.navigationStore.dispatchWidgetApiURL(WidgetApiURL); // save the Widget API URL in the NavigationStore
            this.widgetsStore.dispatchWidgetFeatureActive(true); // set the Widget Feature Activation Status to true
        } else {
            this.navigationStore.dispatchWidgetApiURL(''); // clear the Widget API URL in the NavigationStore
            this.widgetsStore.dispatchWidgetFeatureActive(false); // set the Widget Feature Activation Status to false
        }
    });
},

Hello @abhishekmaha23, thank you for pointing this out. You are right this, feature is deprecated and will be replaced by a plugin for the Time Series Data Submodel Template in the next update.
You don't have to create a PR, I already removed this in my local branch. The original feature used its own backend for handling widgets. This component was not officially released on the BaSyx DockerHub but on my own DockerHub page instead.
Regarding the reload:
I never encountered this but the 8MB reload size makes sense because the AAS UI is a single-page application which loads all the necessary data in the beginning and then never has to request any resources regarding js, HTML or CSS from the server again.

Eagerly waiting for the next update. Let me know if you'd like me to close this issue.
I'm concurrently working on a Plugin for TimeSeries data visuals by embedding small Grafana dashboards. Will this still be compatible with the upcoming release (i.e. will the plugin structure change?). Also, is updating/editing the attributes of the Shells on the roadmap?
Regarding the reload, perhaps I'm reading it wrong! The UI loads quite quickly, but Chrome and other benchmarking tools showed the size of the page being downloaded to be pretty large.

I will release this feature at the end of January if everything goes as planned. You can keep the issue open, I will link it in my PR.
That sounds like a cool feature. If you want, we could exchange some ideas regarding time series data. The plugin mechanism is staying as it is and you won't encounter any problems with your plugin development.
Yes, updating/editing is also a planned feature for the future I would like to implement. I will start implementing this when the BaSyx Java Server SDK supports all necessary endpoints of the API spec to do that.
Reload speed is in general no problem. But it being a single-page application makes the initial page load a bit bigger as explained before. The benefit is, that every consecutive request is very small and the page never has to reload again.

Regarding the time-series data plugin, I'd like that!
Thanks for the (other) quick responses as well :)

I've made a very basic streaming plugin, that displays from a Grafana embed - https://github.com/abhishekmaha23/basyx-gui-timeseries-plugin
Another error with reloads:

I see that every plugin is throwing a 404 error while attempting to find the semantic ID of the plugin as a concept-description at the Basyx server, which is again causing a reload of the page (thus breaking the embedded Grafana, which shouldn't happen, but I probably didn't do a robust job :) )
I'm not able to identify if this is also Widget-related - could you perhaps check?

Additionally, hosting the HelloWorldPlugin.vue externally (through a ConfigMap in Kubernetes) causes an error here:
Line 24:
import SubmodelElementWrapper from '../components/UIComponents/SubmodelElementWrapper.vue';
should be:
import SubmodelElementWrapper from<EMAIL_ADDRESS>The minor change above makes it easier for deployment as a ConfigMap in Kubernetes and does not impact normal lcoal development or Docker deployment. Could you please update this? (It's too small a change for a PR)

Thats cool, I will take a look into that. Thank you for sharing this :)
You are right, the UI sends a request for every open SubmodelElement that has a semanticId to check if there is a related conceptDescription in the ConceptDescription Repository. It is totally normal, that there is not always a related CD present. Therefore the request will return a status 400. But this is definitely not reloading the UI. I already checked that. If you want we could have an online meeting to look at this together to find the problem you are encountering.
Thank you for pointing that out. You are totally right, the import is not ideal in the plugin. I will include that with the next update.


CLDC-1694 Fix issue with non-renewal lettings allowing 'renewal' for vacancy reason

Would it make sense to also write a test to check that no errors are seen when the letting is not a renewal but a different vacancy reason is chosen? Presumably that would be might be overkill?
As well as reviewing my code, I wouldn't mind feedback on my commit messages if they could be improved!

Would it make sense to also write a test to check that no errors are seen when the letting is not a renewal but a different vacancy reason is chosen?

You could do this, but I suspect it it is already tested implicitly elsewhere.


Call to undefined method Endroid\QrCode\QrCode::create()

It may be something very simple, but I've been busting my head and can't find the solution. I did the installation with composer, but it always gives me an error with the imported method. I have tried with the code as it appears here at the beginning and as it appears in the YT video. But the result is always the same.
Call to undefined method Endroid\QrCode\QrCode::create()
PHP Fatal error:  Uncaught Error: Class "Endroid\QrCode\Builder\Builder" not found in /...

Hi @musiquero what version do you have installed according to you composer.lock file? And if you go to the QrCode class can you find a create method or what do you see?

i experienced the same problem.
you can see in my screenshot that the PngWriter class is not read.

sorry if my language is not good. I used Google Translate and I hope you understand.
thanks.

Hi @hallosatria347 the same question for you: what version do you have installed according to your composer.lock file? Also you can check the vendor/endroid/qr-code folder and see if the class PngWriter exists in the Endroid\QrCode\Writer namespace. If so, your autoloading is broken.


Training going very slow

I am trying to train a model built with Keras's Sequential class. The training is very slow with 8000 secs per epoch, i.e 9.25 days for 100 epochs which I can't afford to wait.
Details about the model and data are as follows.

The model has 2 channels and each one has 4 CNN layers, 2 max-pooling layers and 3 dense layers.
Both the channels are independent in the initial layers and are combined only before the final dense layer.
The input size is (150000, 3, 224, 224) with 32 samples per gradient update. I have 2 different data for the 2 channels and therefore have a total of 2*150,000 images sent to the network in pairs, one for each channel.
I am using all relu activations but a softmax one in the last but one layer; optimizer is rmsprop and loss is categorical_crossentropy

Details about the setup is as follows.

Ubuntu - 14.04.3
GPU - Nvidia Tesla K40c(GK110BGL)/33Mhz/12GB
Cuda - 7.5
Python - 2.7.6
Keras backend - Theano

The code-piece where I train the model is given here.
h5fGlobal = h5py.File( 'global_data.h5', 'r')
h5fLocal = h5py.File( 'local_data.h5', 'r')
h5fLabel = h5py.File( 'label_data.h5', 'r')
label_data = h5fLabel['label_data'][:]
h5fLabel.close()
label_data = np_utils.to_categorical(label_data,2)
model.fit(X=[h5fGlobal['global_data'], h5fLocal['local_data']],
                  y=label_data, batch_size=32, nb_epoch=1,
                  callbacks=[], validation_split=0.0, validation_data=None,  shuffle="batch",show_accuracy=False,
                  class_weight=None, sample_weight=None)

I put the entire data into 8 global and 8 local files(the size of each file is 22GB) and run the fit function on each of these. The program loops through them for 100 epochs.
My ~.theanorc file is given below in case you wish to look at it.
[global]
floatX = float32
device=gpu0
exception_verbosity=high
optimizer_including=cudnn
mode=FAST_RUN
openmp=True

[blas]
ldflags = -L/usr/lib -lblas -llapack

[nvcc]
nvcc.fastmath=True
allow_gc=True

[cuda]
root = /usr/local/cuda-7.5/

[lib]
cnmem=0.85

[gcc]
cxxflags=-I /usr/local/cuda/include -L /usr/local/cuda/lib64

[scan]
allow_gc=True
allow_output_prealloc=True

Could you give me a clue why my training is so slow?

Could you give me a clue why my training is so slow?

Almost certainly because you don't have cuDNN installed (or otherwise it's not running).

I installed it quite sometime back. I can reinstall it though to be on a safer side (or verify if it is installed). But how do I check if it is running when I run my program? Can you help?

We just found out a way to check if cuDNN is running from
http://www.chioka.in/why-is-keras-running-so-slow/
We will let you know how it goes. Thank you!

I verified the installation of cuda and cuDNN and everything looks fine.
I tried on two different systems and it is taking around 7000-8000 seconds per epoch on both the systems. Can someone explain me how long would it generally take for network this deep(it has 2 columns) and data of size (150,000*2, 3, 224, 224 )(multiplied by 2 because I have 2 channels)? When I analyse the time, around 50%(a little more than 50%) is utilized in loading the files and a little less than 50% is utilized in training. (I just have 2 parts, load and train, no preprocessing as I preprocessed when I made the hdf5 files).
@fchollet Can you help me with this? I am precisely looking for a benchmark to compare my time-per-epoch with.
Thank you.

@fchollet @Vijetha1 I just ran into a similar problem and after running some tests I am pretty sure the issue is with how Keras loads samples from HDF5 datasets.
All of the indices passed to the HDF objects __getitem__ method use fancy indexing which is significantly slower than using a slice. The fancy indexing section of the h5py docs allude to this but I didn't appreciate how much of a performance bottleneck it was until I ran some benchmarks.
On my system using a relatively simple random dataset of shape (10000, 100), dtype float32, and no compression:

Load 1000 rows using a slice (e.g. X[0:1000]): 4.094ms average
Load 1000 rows using fancy indexing (e.g. X[np.arange(1000)]): 254.588ms average

A slow down by a factor of ~62x is pretty significant. Doubling the number of rows loaded to 2000 increases the performance discrepancy even more to a whopping ~118x slow down (870.254ms vs. 7.378ms). At 4000 rows it's a staggering ~176x slow down (2525.599ms vs. 14.369ms). Even on relatively small requests for 10 rows the slowdown is still ~9x.
I would argue that this is a pretty significant performance issue that should probably be fixed. If someone points me at where the fancy index is passed to the train/test data I can put together a pull request.

@easyas314159 any chance you were able to figure this out? i'm training with HDF files, and would happily take a 5x speedup!


python311Packages.uiprotect: 1.7.2 -> 4.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.uiprotect is: Python API for UniFi Protect (Unofficial
meta.homepage for python311Packages.uiprotect is: https://github.com/uilibs/uiprotect
meta.changelog for python311Packages.uiprotect is: https://github.com/uilibs/uiprotect/blob/refs/tags/v1.19.2/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.19.2 with grep in /nix/store/lm32m95k1c5g5gmrxsmg0cxdjyd949l5-python3.11-uiprotect-1.19.2
found 1.19.2 in filename of file in /nix/store/lm32m95k1c5g5gmrxsmg0cxdjyd949l5-python3.11-uiprotect-1.19.2

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

home-assistant-component-tests.unifiprotect
python311Packages.uiprotect
python312Packages.uiprotect

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lm32m95k1c5g5gmrxsmg0cxdjyd949l5-python3.11-uiprotect-1.19.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.uiprotect https://github.com/r-ryantm/nixpkgs/archive/346246cc48f278361fbb714cd1099af033fe7116.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/346246cc48f278361fbb714cd1099af033fe7116#python311Packages.uiprotect

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lm32m95k1c5g5gmrxsmg0cxdjyd949l5-python3.11-uiprotect-1.19.2
ls -la /nix/store/lm32m95k1c5g5gmrxsmg0cxdjyd949l5-python3.11-uiprotect-1.19.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.unifiprotect
python311Packages.uiprotect
python311Packages.uiprotect.dist
python312Packages.uiprotect
python312Packages.uiprotect.dist

Maintainer pings
cc @mweinelt for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.uiprotect is: Python API for UniFi Protect (Unofficial
meta.homepage for python311Packages.uiprotect is: https://github.com/uilibs/uiprotect
meta.changelog for python311Packages.uiprotect is: https://github.com/uilibs/uiprotect/blob/refs/tags/v4.1.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.1.0 with grep in /nix/store/qw630cza85igm0g5ailwlpwwanvis1fn-python3.11-uiprotect-4.1.0
found 4.1.0 in filename of file in /nix/store/qw630cza85igm0g5ailwlpwwanvis1fn-python3.11-uiprotect-4.1.0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

home-assistant-component-tests.unifiprotect
python311Packages.uiprotect
python312Packages.uiprotect

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qw630cza85igm0g5ailwlpwwanvis1fn-python3.11-uiprotect-4.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.uiprotect https://github.com/r-ryantm/nixpkgs/archive/7126da5cf22c074eb5501bcf9f451ba1e9decc9f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7126da5cf22c074eb5501bcf9f451ba1e9decc9f#python311Packages.uiprotect

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qw630cza85igm0g5ailwlpwwanvis1fn-python3.11-uiprotect-4.1.0
ls -la /nix/store/qw630cza85igm0g5ailwlpwwanvis1fn-python3.11-uiprotect-4.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.unifiprotect

4 packages built:

python311Packages.uiprotect
python311Packages.uiprotect.dist
python312Packages.uiprotect
python312Packages.uiprotect.dist

Maintainer pings
cc @mweinelt for testing.

I require 4.2.0


On latest release

We are seeing this error on the latest aurelia-orm, aurelia-api and aurelia-authentication packages.
system.js:4 Uncaught (in promise) Error: TypeError: (0 , _aureliaTemplating.customElement) is not a function
at Object.eval (http://localhost:9000/jspm_packages/npm/aurelia-orm@2.2.2/component/association-select.js:75:100)
Error loading<EMAIL_ADDRESS>

@RWOverdijk you need to publish 2.2.3 on npm. darn, that's why i ask if there is a hook

@devenson sorry. has nothing (not much) to to with our 'name change'. that's a stupid bug of mine and that npm seems to be behind. it's long fixed and published on github afaik

afaik fixed with https://github.com/SpoonX/aurelia-orm/commit/ae8a42d0367e9cd7610645dea07c510c4b408c72 and githiub relaase 2.2.3

@doktordirk - thanks. I'll check again when I have time to try the latest builds.

fixed: 2.2.3 is on npm


Add seldon to users

Signed-off-by: Clive Cox<EMAIL_ADDRESS>Checklist

[*] Commits are signed with Developer Certificate of Origin (DCO)

Adds Seldon to users of KEDA.

@cliveseldon We are looking for KEDA end-users who want to be interviewed by CNCF for our CNCF Graduation proposal.
Are you willing to share about your experiences on using KEDA? This can be anonymously if need be.
If so, feel free to fill in https://forms.gle/91dD4RVxifWsS2hc7


Can't connect to Wifi from Oxide

Describe the bug
I always have to connect to Wifi through Xochitl instead of in Oxide. Oxide's Wifi window scans correctly but doesn't let me connect, neither to eduroam nor to my iPhone's hotspot. These are networks I have saved on the device and can connect to using Xochitl.
Currently the way I get around this is by switching to Xochitl connecting to the network, then switching back to Oxide. After this, even after killing Xochitl, I am connected. Sometimes in Xochitl I have to forget the network and log in again, but that might be eduroam weirdness at play.
To Reproduce
Steps to reproduce the behavior:

In oxide, open the Wifi screen by tapping the Wifi icon
Click 'scan'. It should work fine and show networks, both new and remembered.
Click 'join' on one of them
Nothing happens

Expected behavior
The selected network should become connected and the Wifi icon should change to indicate a signal.
Version Information:

Device: reMarkable 2
OS: Version <IP_ADDRESS>2-patch_29.2-0gb7a518a
Version: oxide 2.3-3

Additional context
Logs:
tarnish_log.txt (around line 10171 has wifi stuff)
wpa_log.txt

btw, stamen half is the SSID of my iPhone's Wifi hotspot. If I'm not connected to that I usually connect to my college's eduroam network.

Do you know what authentication method it uses? Oxide has extremely rudimentary wireless handling and only really works with open networks or wpa.

@qubist have you had a chance to follow up on this? It's been quite a long while.

Closed due to lack of followup.


[Backport 2.x] Adding integ test for index close/open scenario

Adding integ test for index close/open scenario

Backport https://github.com/opensearch-project/k-NN/pull/693
Signed-off-by: Martin Gaievski<EMAIL_ADDRESS>(cherry picked from commit https://github.com/opensearch-project/k-NN/commit/54a433ee3681a2f48acee5c1aacf9a3058f85641)

Codecov Report

Merging #699 (931ff9b) into 2.x (2b12ea5) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                2.x     #699      +/-   ##
============================================
- Coverage     84.48%   84.46%   -0.03%
+ Complexity     1063     1062       -1
============================================
  Files           149      149
  Lines          4332     4332
  Branches        392      392
============================================
- Hits           3660     3659       -1
- Misses          492      493       +1
  Partials        180      180

Impacted Files
Coverage Δ

.../java/org/opensearch/knn/index/query/KNNQuery.java
77.77% <0.00%> (-5.56%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Android 4.1 crashes with this plugin and latest play services

Expected Behaviour
App executes normally without crashes.
Actual Behaviour
Push actually registers successfully and I get a token, but for some reason my app crashes in an unreleated part of my app. (Login) When the plugin is removed, and actually replaced with the deprecated version (com.phonegap.plugins.pushplugin) the app works normally with push notifications and all.
Reproduce Scenario (including but not limited to)
Run an app with this plugin (even without calling init() ) in a device with the specs below.
Steps to Reproduce
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
Android 4.1.2
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Samsung Galaxy s3 Mini. It works perfectly in an LG G3 stylus (android 5) and a Moto X play (Android 6)
Cordova CLI version and cordova platform version
cordova --version:       cli-5.2.0
cordova platform version android: cordova android 4.1.1

Plugin version
cordova plugin version | grep phonegap-plugin-push   # e.g. 1.5.3

Latest version.
Sample Push Data Payload
Sample Code that illustrates the problem
Logs taken while reproducing problem
Specific part of the log with the crash:
07-05 16:55:54.039: E/dalvikvm(5687): Class lookup Landroid/webkit/WebResourceResponse; attempted with exception pending
07-05 16:55:54.039: W/dalvikvm(5687): Pending exception is:
07-05 16:55:54.039: I/dalvikvm(5687): java.lang.NullPointerException:
07-05 16:55:54.039: I/dalvikvm(5687): 	at android.content.res.AssetManager.openAsset(Native Method)
07-05 16:55:54.039: I/dalvikvm(5687): 	at android.content.res.AssetManager.open(AssetManager.java:315)
07-05 16:55:54.039: I/dalvikvm(5687): 	at android.webkit.BrowserFrame.inputStreamForAndroidResource(BrowserFrame.java:860)

Full logcat:
https://gist.github.com/mlabarca/2fa8688c74e4b615793bd64c1d3836a9
Notes:
At first I though this was also related to https://github.com/phonegap/phonegap-plugin-push/issues/909, But play services in the device in question is at the most recent version (9.2.56). I also attempted re-applying
this  commit  in my fork : https://github.com/phonegap/phonegap-plugin-push/commit/2fecb9c8110644e8f279c40dc25d44039daf99aa to lock down the services requirement(both in plugin.xml and push.gradle) but that didn't work either. I'm starting to think this is a separate issue with something else bundled with this plugin.
I'm seeing this building with phonegap build and also in cli.

@mlabarca hey, I took a look at your stack trace:
07-05 16:55:54.039: I/dalvikvm(5687): java.lang.NullPointerException:
07-05 16:55:54.039: I/dalvikvm(5687): 	at android.content.res.AssetManager.openAsset(Native Method)
07-05 16:55:54.039: I/dalvikvm(5687): 	at android.content.res.AssetManager.open(AssetManager.java:315)
07-05 16:55:54.039: I/dalvikvm(5687): 	at android.webkit.BrowserFrame.inputStreamForAndroidResource(BrowserFrame.java:860)
07-05 16:55:54.039: I/dalvikvm(5687): 	at android.webkit.BrowserFrame.shouldInterceptRequest(BrowserFrame.java:951)
07-05 16:55:54.039: I/dalvikvm(5687): 	at android.webkit.JWebCoreJavaBridge.nativeServiceFuncPtrQueue(Native Method)
07-05 16:55:54.039: I/dalvikvm(5687): 	at android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:113)
07-05 16:55:54.039: I/dalvikvm(5687): 	at android.os.Handler.dispatchMessage(Handler.java:99)
07-05 16:55:54.039: I/dalvikvm(5687): 	at android.os.Looper.loop(Looper.java:137)
07-05 16:55:54.039: I/dalvikvm(5687): 	at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:1127)
07-05 16:55:54.039: I/dalvikvm(5687): 	at java.lang.Thread.run(Thread.java:856)

and nowhere in there does a part of the Push Plugin java code get executed. If you comment out the call to init and rebuild your app does it still crash?

Unfortunately, yeah. Even with init 'on' it registers without issues and i
see the token stored in device storage, problem comes after a login action
that is unrelated. It seems it's a problem with a dependency or something.
I'll recheck and try to build and run this tomorrow with much earlier
version (say, 1.5) to narrow it down more.
On Jul 5, 2016 8:32 PM, "Simon MacDonald"<EMAIL_ADDRESS>wrote:

@mlabarca https://github.com/mlabarca hey, I took a look at your stack
trace:
07-05 16:55:54.039: I/dalvikvm(5687): java.lang.NullPointerException:
07-05 16:55:54.039: I/dalvikvm(5687):   at android.content.res.AssetManager.openAsset(Native Method)
07-05 16:55:54.039: I/dalvikvm(5687):   at android.content.res.AssetManager.open(AssetManager.java:315)
07-05 16:55:54.039: I/dalvikvm(5687):   at android.webkit.BrowserFrame.inputStreamForAndroidResource(BrowserFrame.java:860)
07-05 16:55:54.039: I/dalvikvm(5687):   at android.webkit.BrowserFrame.shouldInterceptRequest(BrowserFrame.java:951)
07-05 16:55:54.039: I/dalvikvm(5687):   at android.webkit.JWebCoreJavaBridge.nativeServiceFuncPtrQueue(Native Method)
07-05 16:55:54.039: I/dalvikvm(5687):   at android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:113)
07-05 16:55:54.039: I/dalvikvm(5687):   at android.os.Handler.dispatchMessage(Handler.java:99)
07-05 16:55:54.039: I/dalvikvm(5687):   at android.os.Looper.loop(Looper.java:137)
07-05 16:55:54.039: I/dalvikvm(5687):   at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:1127)
07-05 16:55:54.039: I/dalvikvm(5687):   at java.lang.Thread.run(Thread.java:856)
and nowhere in there does a part of the Push Plugin java code get
executed. If you comment out the call to init and rebuild your app does
it still crash?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phonegap/phonegap-plugin-push/issues/1051#issuecomment-230641651,
or mute the thread
https://github.com/notifications/unsubscribe/AEYBvUiVPwYlnoo2gtGpstjCtuCpI4YEks5qSvd-gaJpZM4JFmC6
.

@mlabarca I think what you should concentrate on is looking for spots in your code that attempt to load files from the assets folder on Android. That is what the stack trace indicates to me.

@macdonst I thought the same at first, but it doesn't really explain why it works with more recent android devices and when removing the plugin.
Anyways, after spending some time trying out versions, no crashes occur in the device in question when using version 1.3.0; crash happens with plugin version 1.4.0 onwards. I'll take a look at the changelog and see what I can find.

@macdonst hmm Well from this commit https://github.com/phonegap/phonegap-plugin-push/commit/a69b59675c61436a2e46a91dc3ec0db4a948b142  version 1.4.0 changed a lot of stuff from the way dependencies are handled. Any ideas? are there other libraries that have to be installed in the device besides the latest play services version or something not being added properly by phonegap build?

@mlabarca first thing I'd do would be to delete your projects platforms/android directory then re-add the android platform cordova platform add android and see if you can reproduce it.
Can you send me what your init code looks like?

@macdonst Sorry for the delay.

This tests were done using phonegap build. If I understand pgb correctly anything on the platforms folder shouldn't affect it right? I did do one test locally, I did have to rebuild the android platform anyways since I had the old deprecated push plugin.

First, the init code itself:
    var initPush = function(){
      var androidParams = {senderID: zimplepr.config.pushNotification.android.senderID, clearBadge: true};
      var iosParams =  {'badge': 'true', 'sound': 'true', 'alert': 'true', clearBadge: true};
      return PushNotification.init({android: androidParams, ios: iosParams});
    };

and when is it called:
cordovaService.then(function () {
        var push = initPush();
        push.on('registration', function(notification) {
          var token = notification.registrationId;
          handleToken(token, platform) // stores device token on device to be sent later to our server
        });

        push.on('notification', function(data){
           // notification Callback
        });
}

and cordova service returns a promise that resolves when the device is ready like this:
function($window, $document, $q){

    var deferred = $q.defer(),
    var resolved = false,
    var promise =  deferred.promise;

    $document[0].addEventListener('deviceready', function(){
      resolved = true;
      deferred.resolve($window.cordova);
    }, false);

    return promise;
  });

This doesn't seem the issue to me since like I've said before, I get the token without problems and I haven't had any issues in recent versions and the app initializes. It's just on an unrelated login action after login credential are input by the user where I send the token to the server that the crash happens from version 1.4 onwards. Hope this helps at least :/

@mlabarca there is nothing in the code that you posted that has anything to do with loading anything from the assets folder so I feel as if the push plugin is not to blame here.
When you go to the login screen are you trying to load something from assets that a) does not exist or b) has a special character like : in it? Apparently having a : in the URL is a problem.
https://code.google.com/p/android/issues/detail?id=46721

@macdonst Something I've just noticed (not sure if it's related) comparing tokens with recent and old plugin versions. For the same phone in the old deprecated plugin I'm receiving a token like APA91bHiZJoSgvS2EJvoOCjl0UzGUBInV6OkDiGYtQ6vPCZnegyv.... but from this plugin in more recent phones i receive **chLNI95DAOo:**APA91bHiZJoSgvS2EJvoOCjl0UzGUBInV6OkDiGYt.... Isn't this something that happens when firing the plugin before a device ready event? notifications do work, though.

@mlabarca the old plugin used the gcm.jar to get the registration ID. This plugin uses updated libraries gcm and google instance ID. That is why the registration ID looks a bit different. You are getting it in the correct format.

Closing, inactivity

To anyone who is lost in a similar issue and uses angular, this was not a problem with the push plugin per se. GCM tokens can sometimes be in the form of '**chLNI95DAOo:**APA91bHiZJoS...'. This small colon that should be present seems to be generated in mostly android versions (Hence why it don't see the issue happen in android >4.4), when sent in an ajax request with the wrong encoding, crashed the app since it interpreted it as accessing a local non-existent template instead of the ajax request. Simply encoding that token with encodeURIcomponent in an $http interceptor and parsing it at the server fixed the issue. So sorry for the inconvenience 😞


Is it possible to restrict expression access to a given set of types and singletones?

Could you, please, provide an example of how one can limit and enforce that our expression only to be capable of calling methods of our class like to say Test, Math.* functions, create int/string types?

Inside an expression you can call any type that was previously referenced.
By default the following types are available:
https://github.com/davideicardi/DynamicExpresso#built-in-types-and-custom-types
You can add other types using Reference function. Or avoid loading default types using InterpreterOptions inside the Interpreter constructor.


feat: add exclude option

I create a new pull request about the exclude.
Could you please spent some times to review the code.
Waiting for your reply，thank you.

Does anyone review this request?
This new feature is important for me.

bump. would love to see this too

@endday Thank you for your Pull Request. Sorry for such a long delay in a response!
This is interesting. I figured that in whatever system you used this plugin in, that system would allow you to choose what file to run it on and what files to ignore. To me it seems like a bad pattern to make the plugins have their own way of ignoring files. If that was the case then all the plugin creators should come together and come up with some kind of standard option that everyone should add. See what I'm getting at? Most people use several PostCSS plugins with this plugin and it would be complicated if you had to learn each plugins system to ignore the correct files.
Can you help me understand why someone would need this?

We have multiple entries in our Webpack config, I only want to convert to rem in 1 of those entry points while leaving the other these as fixed pixels. I guess this could be done using multiple rules in the Webpack config, but then you have duplicate code sitting around

when my project need pxtorem, but some components libs should be excluded, the exclude option would be usefull.

I changed my mind. I want to include this. Would you like to resolve the conflicts or else I can take these changes and apply them to a new branch?
FYI, I just added eslint and prettier to the package so it is easier to get the formatting correct.

我太久没有看过这个项目了，所以代码都不太理解了，在解决冲突上花了比较久的时间。
这合并请求还有进展，让我十分惊喜，希望这个功能能给使用者带来方便。
————————————————————————————————————————————
I haven't seen this project for a long time, so I don't understand the code very much, and I spent a long time in resolving conflicts.
I am very surprised by the progress of this merge request. I hope this function will bring convenience to users.

Thanks!

This is published as 5.1.0


(node-redis) Error in declaration file when noImplicitAny is enabled

(node-redis) Please add var types/return types where appropriate, for users who have noImplicitAny enabled. :)

I think node_redis/node_redis.d.ts is old version of redis/redis.d.ts.
Please use the new version of redis definition(redis/redis.d.ts).
But I don't know why the old version is exists...


Restore standalone editor style

But apply it only on standalone editors
@kaisalmen it's a fix for https://github.com/TypeFox/monaco-languageclient/pull/600#issuecomment-1964017110
Removing it doesn't seem to be an issue on Linux but it is on Window

Works nicely. Thanks.

@CGNonofr unfortunately, the same problem happens when using the standalone DiffEditor.

@CGNonofr unfortunately, the same problem occurs when using the standalone DiffEditor.

Oh... can you please open another issue?


Reconcile healthchecks on host.activate

https://github.com/rancher/rancher/issues/8416
This fixes a bug that occurs if you take you environment down to zero
hosts by removin the hosts from your cloud provider and they go into a
disconnected state in Rancher. In that scenario, healthchecked
instances on the disconnected host would never get healthchecks
scheduled on the newly added hosts and thus would never get moved off
the disconnected host.
The process that we were previously keying off of
(networkserviceproviderinstancemap.create) is no longer executed. It
was executed to lanuch the network-agent container on the host, but
we've completely gone away from that model. We were previously using
that process because we needed the network-agent to be running in order
for that host to process healthchecks, but that is no longer necessary
because healthcheks are deployed in their own containers. The logic
later in this process that schedules the new healthchecks ensures that
the host will have a healthcheck container deployed to it, if it
doesn't already.

Potential hosts for the HCIHM are retrieved here:
https://github.com/rancher/cattle/blob/2e53df9ea42f7aa20b73c66097a9b4286844bf07/code/iaas/healthcheck/src/main/java/io/cattle/iaas/healthcheck/service/impl/HealthcheckServiceImpl.java#L261
...
https://github.com/rancher/cattle/blob/c28f841054eac49ae89562d4be4726a9024ce9cf/code/iaas/allocator/src/main/java/io/cattle/platform/allocator/dao/impl/AllocatorDaoImpl.java#L451-L466
Hosts that are active-ish with active (or reconnecting)

@ibuildthecloud you initially said you were not 100% convinced with this fix, but then added a test and and verified the functionality manually with hosts started from the UI (since the flow is different bc the host exists before the agent does) and you said it looked good.
Feel free to re-review, just giving you some context

I had a bug in the test, which I fixed


Implement multiprocessing speedup for suggest in absence of python-Levenshtein

NOTE: With the deprecation of the python-Levenshtein speedup for the suggest functionality (see #211 & #218), identifying other methods to increase performance is a priority. This multi-processing based approach is the best one I've thought of so far. If anyone has another suggestion, please open a new issue to discuss it.

Very early POC on suggest-multiproc branch.
Suggests some speedup possible, but not a slam-dunk whether it's worth it given the sub-2s processing times for most inventories. Properly exploiting difflib.SequenceMatcher's caching behavior may change this, however.
For comparison, python-Levenshtein is a better speedup for less internal complexity, and doesn't appear to benefit at all from multiproc.

API -- arg to Inventory.suggest(), likely
CLI -- new parameter for suggest subparser

If nproc == 1 then skip multiprocessing entirely
Probably need to check at sphobjinv import-time whether multiprocessing is available

Doing that in a way that doesn't further slow down the import time may be tricky

Per the difflib docs, implementing a bespoke scoring function directly with difflib.SequenceMatcher may allow significant speed gains, due to the ability to cache the suggest search term
For v2.3, perhaps keep the current single-process fuzzywuzzy method as the default, but implement with a feature flag to switch to the mp-accelerated version?
A naive, direct use of difflib.SequenceMatcher does not give good suggestions for some searches (e.g., "dataobj" in the sphobjinv inventory), compared to the default, WRatio-based partial-matcher in fuzzywuzzy

Going to want to port this fuzzywuzzy method directly into the codebase, adapted to allow for multiprocess, I think.

If I'm going to have to re-implement fuzzywuzzy's WRatio as part of this, I might as well do it in a way that exposes the internal weighting values inside WRatio, so that if someone wanted to they could adjust those values. Have to think about whether there's a way to do that ~cleanly in a plugin system, though...

Scorer should make its own internal decision about multi or not, but suggest should have an option to coerce single or nproc if user prefers, or if the multi-detector is making a bad determination.
The scorer should have a fully inspect able/introspectable API. Defined interface on how suggest will call it. Should be the most general, information rich inputs possible, which is probably the search term and the inventory itself!
Provide index and score flags, too? Threshold? I could see a scorer knowing enough about its own properties to be able to make a quick first pass and discard sufficiently poor matches. Might as well provide all the information possible. Have to set this up so that it's easy to add more information if something new comes up.

SuggestPayload object with Inventory and suggest parameters (index, score, thresh... others?) passed to scorer, along with an extra_kwargs dict of additional arguments that can adjust the scorer behavior.
Best practice... recommend that any scorer, builtin or plugged, define Enums for use as the keys in extra_kwargs?

Either way, keep the legacy scorer, available under the legacy id... and call the new one default, probably.

Sprinkling this in various issues: rapidfuzz as another fuzzywuzzy alternative.


Generics in implemented interfaces are not output

The following:

 * @implements {goog.Thenable<TYPE>}
 * @template TYPE,RESOLVER_CONTEXT
 */
goog.Promise = function(resolver, opt_context) {...}

outputs
class Promise < TYPE , RESOLVER_CONTEXT > implements Thenable {

But it should be Thenable<TYPE>.

Same for union types. For example
/**
 * Resolves this resolver with the specified value.
 * @type {function((TYPE|goog.Promise<TYPE>|Thenable)=)}
 */
goog.promise.Resolver.prototype.resolve;

Type disappears.


Config isn't honored/loaded + config parsing issues

Nixpkgs channel: Version 22.11
Description
When using the nixos module and generating a config at /etc/nvim/sysinit.lua I would expect the settings to be honored when I open nvim.
However no settings are loaded when I open nvim.
If I directly open nvim with the config file via nvim -u /etc/nvim/sysinit.lua I do get lua parsing errors.
The first error is:
Error detected while processing /etc/nvim/sysinit.lua:
E5113: Error while calling lua chunk: /etc/nvim/sysinit.lua:10: invalid value for option
stack traceback:
        [C]: in function '__newindex'
        /etc/nvim/sysinit.lua:10: in main chunk

which seems to relate to commit hash 4ddd3969
If you change L10 from vim.o[k] = v to vim.opt[k] = v we make it pass this error.
The next error once we reload nvim with the fixed config is:
Error detected while processing /tmp/sysinit.lua:
E5113: Error while calling lua chunk: /tmp/sysinit.lua:61: module 'lspconfig' not found:
        no field package.preload['lspconfig']
        no file '/nix/store/xnxyn0bp80pf2jk58a72za679ajlcp32-luajit-2.1.0-2022-10-04-env/share/lua/5.1/lspconfig.lua'
        no file '/nix/store/xnxyn0bp80pf2jk58a72za679ajlcp32-luajit-2.1.0-2022-10-04-env/share/lua/5.1/lspconfig/init.lua'
        no file '/nix/store/xnxyn0bp80pf2jk58a72za679ajlcp32-luajit-2.1.0-2022-10-04-env/lib/lua/5.1/lspconfig.so'
stack traceback:
        [C]: in function 'require'
        /tmp/sysinit.lua:61: in main chunk

Which I assume is from not having access to the set of
plugins, vim runtime, etc in some manner.
Config
{ pkgs, config, ... }:

{
  programs = {
    nixvim = {
      enable = true;
      viAlias = true;
      vimAlias = true;
      options = {
        mouse = "a";
        termguicolors = true;
        background = "dark";
        ignorecase = true;
        swapfile = false;
        showmatch = true;
        hlsearch = true;
        wildmode = [ "longest" "list" ];
        expandtab = true;
        tabstop = 4;
        shiftwidth = 4;
      };
      extraConfigVim = ''
        set completeopt=menuone,noinsert,noselect
        set shortmess+=c
        set whichwrap+=<,>,h,l,[,]
        au BufRead,BufNewFile *.md setlocal textwidth=80
        au BufRead,BufNewFile *.yaml setlocal textwidth=80 shiftwidth=2 cc=80
        au BufRead,BufNewFile *.yml setlocal textwidth=80 shiftwidth=2 cc=80
        au BufRead,BufNewFile *.sls setlocal textwidth=80 shiftwidth=2 cc=80
        au BufRead,BufNewFile *.sh setlocal textwidth=80 shiftwidth=2 cc=80
        au BufRead,BufNewFile *.nix setlocal textwidth=80 shiftwidth=2 cc=80
        au BufRead,BufNewFile *.js setlocal textwidth=80 shiftwidth=2 cc=80
        au BufRead,BufNewFile *.ts setlocal textwidth=80 shiftwidth=2 cc=80
        au BufRead,BufNewFile *.lua setlocal textwidth=80 shiftwidth=2 cc=80
        au BufRead,BufNewFile *.py setlocal textwidth=80 shiftwidth=4 cc=88
        au BufRead,BufNewFile *.rs setlocal textwidth=80 shiftwidth=4 cc=80
        au BufRead,BufNewFile *.c setlocal textwidth=80 shiftwidth=4 cc=80
        au BufRead,BufNewFile *.go setlocal textwidth=80 shiftwidth=4 cc=80
        au BufWrite *.rs :Autoformat
        au BufWrite *.nix :Autoformat
      '';
      plugins = {
        lsp = {
          enable = true;
          servers = {
            rnix-lsp = { enable = true; };
            rust-analyzer = { enable = true; };
          };
        };
      };
    };
  };
}

What Neovim version are you on? vim.o not working is odd

Version 0.7 I believe.

Okay I had a default nvim package in systemPackages overriding the nixvim package.
Removed that and rebuilt, now on nvim version 0.8.1 but still seeing the same issues as above.

Okay so seems to be mostly a red herring.
The issue with
Error detected while processing /etc/nvim/sysinit.lua:
E5113: Error while calling lua chunk: /etc/nvim/sysinit.lua:10: invalid value for option
stack traceback:
        [C]: in function '__newindex'
        /etc/nvim/sysinit.lua:10: in main chunk

was due to having improper options in my nix config.
The second error with not loading the LSP config also went away once fixed my vim config options and loaded the config via the -u param.
However this still doesn't answer the question as to why I can't load the config file located at /etc/nvim/sysinit.lua by default?
I can only assume it's not a default file search path for neovim?

One could make the patch to nixvim to always pass -u /etc/nvim/sysinit.lua to neovim?

From reading over the nvim source code, while we can check multiple dirs including /etc/nvim/ for vim configs I don't believe this holds for sysinit.lua. So this module may be broken.
A workaround seems to be to use wrapRc = true; for now however.

I'm assuming yes, unfortunately it doesn't seem to look at sysinit.lua by default (as far as I can tell, it does look at sysinit.vim)
I'd say the best course of action here would actually be to generate a sysinit.vim for this case. Short term though, don't see anything wrong with just making wrapRc = true.

So seems we should do a stub sysinit.vim and do a lua call to load the systinit.lua file then?
Or should we just revert to writing a vim file again?

I think that your problem is caused by the line wildmode = [ "longest" "list" ]; in the options.
Indeed, I had the same message when using programs.nixvim.options.completeopt = [ "menu" "menuone" "noselect" ];.
I have since then switched to programs.nixvim.options.completeopt = "menu,menuone,noselect"; and it works fine.

Yeah that was my issue wrt config parsing.
But not wrt the config being loaded or attempted to load afaic.
On Tue, Jan 17, 2023, 12:25 PM Gaétan Lepage @.***>
wrote:

I think that your problem is caused by the line wildmode = [ "longest"
"list" ]; in the options.
Indeed, I had the same message when using programs.nixvim.options.completeopt
= [ "menu" "menuone" "noselect" ];.
I have since then switched to programs.nixvim.options.completeopt =
"menu,menuone,noselect"; and it works fine.
—
Reply to this email directly, view it on GitHub
https://github.com/pta2002/nixvim/issues/105#issuecomment-1385771436,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHQRQNW4WQBNF4IRHOUT53WS3IXTANCNFSM6AAAAAATUMGJQY
.
You are receiving this because you authored the thread.Message ID:
@.***>

I think that your problem is caused by the line wildmode = [ "longest" "list" ]; in the options. Indeed, I had the same message when using programs.nixvim.options.completeopt = [ "menu" "menuone" "noselect" ];. I have since then switched to programs.nixvim.options.completeopt = "menu,menuone,noselect"; and it works fine.

hm that seems like a bug that needs to be fixed, but seems like it might be an upstream thing (because it doesn't work when setting it to an array)

Hasn't this gotten fixed by https://github.com/pta2002/nixvim/pull/167 ?


The first letter should be small in error of remote.go

- What I did
Fix the typo of the first letter in error
- How I did it
Modify the first letter capital to lowercase
Signed-off-by: YuPengZTE<EMAIL_ADDRESS>

Why should the first letter be lower case? Is the error message prefixed with other messages?

@dnephin afaik, it's convention to lowercase error messages (can't find a reference right now)

Reference here: https://github.com/golang/go/wiki/CodeReviewComments#error-strings

LGTM
win failure is unrelated


lv messages translation fix, update yii.php

lv messages translation fix

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

Fixed issues

Merged. Thanks!


runtime: pinner.Pin doesn't panic when it says it will in Go 1.21

The documentation for runtime.Pinner.Pin currently says:

The argument must be a pointer of any type or an unsafe.Pointer. It must be the result of calling new, taking the address of a composite literal, or taking the address of a local variable. If one of these conditions is not met, Pin will panic.

However, it does not always do so today.
A channel, map, or slice value can be constructed by calling make, which does not involve a call to new, nor a composite literal, nor the address of a local variable. Empirically, Pin does not panic when called on such an object (https://go.dev/play/p/q_iyNHJduRf).
	p := new(runtime.Pinner)
	c := make(chan struct{}, 1)
	p.Pin(reflect.ValueOf(c).UnsafePointer())

It isn't clear to me whether this is a mistake in the documentation (a valid case that was omitted from the doc comment), or a bug in the implementation (Pin failing to panic for an unsupported address).
At a higher level, it seems to me that it is basically always a mistake for a doc comment to state that something will panic for an unsupported input, since that makes it an incompatible change to ever add support for such an input. (It would be better for Pin not to promise anything about what happens for such an input, but to panic anyway as a debugging aid to the user.)

This was prompted by the desire to pin channel values in https://go.dev/cl/528796.
Note that channels are, to my knowledge, the only Go type that cannot be allocated by either calling new or taking the address of a composite literal or local variable (compare #28366).

It reads like an oversight in the documentation, though it is also unclear to me what C code would do with a pinned channel or map.

CC @mknyszek especially.

See #62356 and CL 527156，After  CL 527156, the documentation becomes:
The argument must be a pointer of any type or an unsafe.Pointer. It's safe to call Pin on non-Go pointers, in which case Pin will do nothing.

Huh! Yeah, it looks like this is probably fixed at head as a result of #62356. 🙃

In that case, I guess this is a bug affecting only Go 1.21. (Leaving open for the runtime folks to decide whether it's worth backporting some kind of fix for compatibility.)

We only usually backport fixes for regressions, so I'm inclined to leave this one be.
Pin will panic less in 1.22 than in 1.21, but that's not so bad. It isn't like Pin in 1.21 panics more than 1.20 (because Pin doesn't exist in 1.20).

Perhaps this is a go1.21 documention issue that should be written as
The argument must be a pointer of any type or an unsafe.Pointer.

See https://go.dev/wiki/MinorReleases, I think can repair go1.21 document.
I think the title of this issue is followed should by [1.21 backport] , don't have to open a new backport issue.

@bcmills Could you please add [1.21 backport] after the title of this issue?

Done.

Sorry for not replying here. @bcmills I think you're right that we shouldn't explicitly say anything panics necessarily as part of the API. We should just drop the problematic part of the documentation.
I do also think we should consider:

Adding a warning to the documentation that writing the code you wrote may not work correctly and is not supported.
Redirect users to runtime/cgo.Handle if the only reason they want to pin something is to pass it back to Go.
Explicitly allowing some common and fairly safe cases, like slices and strings. (Slices are especially egregious today, since you can just pass an interior pointer to the slice and that doesn't even need unsafe!)

I will file a proposal for the third bullet point.


fix(dynamic-links): prevent crash when annotation is null

Apparently the options are always empty https://github.com/firebase/firebase-ios-sdk/blob/136e71f7aa438236421307a69c01789855515464/FirebaseDynamicLinks/Sources/FIRDynamicLinks.m#L544

@triniwiz there is any chance to get a release with this fix today? we are blocked and not able to publish apps on iOS because of this

I'm facing a iOS device crash when I include the dynamic-links plugin, however this happens only the first time when the App is installed, subsequent re-opens don't cause a problem.
During compilation, I noticed the below error:
node_modules/@nativescript/firebase-dynamic-links/platforms/ios/src/TNSFirebaseDynamicLinksAppDelegate.swift:30:146: warning: expression implicitly coerced from 'Any?' to 'Any'
return application(app, open: url, sourceApplication: options[UIApplication.OpenURLOptionsKey.sourceApplication] as? String, annotation: options[UIApplication.OpenURLOptionsKey.annotation])
Environment setup:

Mac OS : 12.4
iPhone OS : 15.5
NativeScript : 8.2.3

I'm sure the crash is due to the plugin because I've experimented several times by including and excluding the package from the build.
Requesting some assistance on this. Btw, it works fine on Android.


Write the code generator and generated codes usage to README.md

Also, write comments to code files.


Fix Arm64 detection logic for devices

Description
Flutter tools assumes that all 64 bit ARM cpus are able to run 64 bit code.
There are manufacturers that use 64 bit ARM cpus while installing 32 bit Android OS on it.
Added code that looks at the OS for 32 or 64 bit arm so dev tools do not try to download
64 bit code to 32 bit Operating systems.
Tests
As far as tests, I have tested with my available android devices including Kindle Fire 8 and Motorola LG v30.
But this is device detection, so it requires physical devices more than I have available.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[ x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[ x] I signed the [CLA].
[ x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[?] I updated/added relevant documentation (doc comments with ///).
[?] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read [Handling breaking changes]). Replace this with a link to the e-mail where you asked for input on this proposed change.
[X ] No, this is not a breaking change.

I will get back to this very shortly.  I am just trying to get some other deadlines met in the meantime.

Closing due to lack of activity. I've filled https://github.com/flutter/flutter/issues/44999 to capture the issue here


Browser BackButton: View not reloaded, but URL changed

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[X ] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[X ] bug report
[ ] feature request
Current behavior:
I use DeepLinking. With ionic 3.7.1. the error of reloading the wrong SubTabs while loading Tabs-Page does not occur anymore. But now the browser back button does not work anymore. This means that when I click on back/forward button the url changes but the content stays the same.
Expected behavior:
Content should change according to Back-Button and reloaded URl.
Steps to reproduce:
ionic serve (project) - I can give private access but I can't publish repository if needed.
Related code:
 imports: [
    TagInputModule,
    FileUploadModule,
    IonicModule.forRoot(MyApp, {},
      {
      links: [

        { component : VerifyPage, name: 'verify', segment : 'verify/:id'},
        { component: TestPage, name: 'TestPage', segment: 'test' },
        { component: TestPage, name: 'TestPage', segment: 'test' },
        { component: KontaktPage, name: 'KontaktPage', segment: 'kontakt' },
        { component: ImpressumPage, name: 'ImpressumPage', segment: 'impressum' },
        { component: BewerbenPage, name: 'BewerbenPage', segment: 'bewerbenaa' },
        { component: MyJobsPage, name :'MyJobsPage', segment: 'myjobs'},
        { component: JobFormPage, name:'JobFormPage', segment:'jobform'},
        { component: TabsPage, name:'TabsPages', segment:'tabs'},
        { component: ProfilePage, name : 'ProfilePage', segment: 'profile' },

      ]
    }

  ),

...

    {
      provide: AuthHttp,
      useFactory: getAuthHttp,
      deps: [Http]
    },

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Your system information:

Cordova CLI: 6.5.0
Ionic Framework Version: 3.7.1
Ionic CLI Version: 2.2.3
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 2.1.4
ios-deploy version: Not installed
ios-sim version: Not installed
OS: OS X Yosemite
Node Version: v7.9.0
Xcode version: Xcode 6.4 Build version 6E35b

Hello! Thank you for opening an issue with us! Would you be able to provide a sample application via GitHub that demonstrates the issue you are having?
I have attempted to duplicate your issue using our sample "Conference App" https://github.com/ionic-team/ionic-conference-app but could not, even after changing ionic-angular from the nightly build it uses by default to the 3.7.1 release build.
Thanks for using Ionic!

HI kensodemann,
thanks for your reply.
I checked with the ConferenceApp and I could not find any reason for my app to cause this error compared to the ConferenceApp. Though my code is a bit different from it.
I invited you as a contributor to the app. I cant share it public since it is an enterprise project.
Thanks for having a look!

A live demo can be found here: http://cohooyo.com/#/tabs/bewerben/bewerben
If you click on Kontakt and Impressum on the left you should see the effect.

I have the problem too.

@AlessandroSchneiderSignUP Do you find something to solve it?

@AlessandroSchneiderSignUP - I have taken a look at your repo but have not found anything yet. I don't know when I will have time to take a closer look.
If you can duplicate this by taking one of our starters (probably sidemenu based on your app) and updating it until it demonstrates the issue that would be very helpful.

Hello @Lsy-kg
thanks for that tip @kensodemann
The reason was:
    { component: TabsPage, name:'TabsPages', segment:'tabs'},

had to be renamed to
{ component: TabsPage, name:'TabsPages', segment:'tabs-page'},

Hi there,
I just found out that this was exactly the opposing solution of the error  of "reloading the wrong SubTabs while loading Tabs-Page" mentioned by other devleopers here on GitHub where I was told to rename tabs-page to tabs.
Can you please have a look into that?
Thanks!!


Align IT translations #266

Codecov Report

Merging #270 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #270      +/-   ##
============================================
- Coverage     58.04%   58.01%   -0.03%
  Complexity     2725     2725
============================================
  Files           328      328
  Lines          6931     6931
============================================
- Hits           4023     4021       -2
- Misses         2908     2910       +2

Impacted Files
Coverage Δ
Complexity Δ

src/Helper/ImageHelper.php
78.26% <0%> (-8.7%)
15% <0%> (ø)

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 83b28e7...dc2fabe. Read the comment docs.


Add release notes for improving libreswan down time

Release notes for https://github.com/submariner-io/submariner/pull/2543

Redone as https://github.com/submariner-io/submariner-website/pull/987


First click on <Link> has no effect

Version
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>
Steps to reproduce

reload site
click on a <Link> → nothing happens
click again → works as expected

for some reason this only seems to occur in chrome – it works fine in safari and firefox.
it looks like this is due to event.defaultPrevented being true at https://github.com/ReactTraining/react-router/blob/master/packages/react-router-dom/modules/Link.js#L39
IIRC, this beviour was first observed after using the new react context API in our SPA, which broke ALL links, and then updating react-router-dom to the latest version.

things I tried in the meantime (that didn't change anything, unfortunately):

go back to the older version of react-router-dom I had used previously (4.2.2)
switch to the legacy context API

turns out it has to do with the latest version of howler.js, which must have gotten updated along with the router. — never mind!


Datastore.save does not return

Morphia version: 1.1.1
JDK version: Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Mongo version: 3.0.12
I have an issue where Datastore.save does not return for a certain object. Other, similar objects work perfectly fine.
There is no exception and nothing in the mongo logs. These are the last few corresponding lines from /var/log/mongodb/mongod.log
2016-05-12T16:09:57.280+0200 I NETWORK  [initandlisten] connection accepted from <IP_ADDRESS>:42429 #1 (1 connection now open)
2016-05-12T16:09:58.081+0200 I NETWORK  [initandlisten] connection accepted from <IP_ADDRESS>:42431 #2 (2 connections now open)
2016-05-12T16:09:58.104+0200 I NETWORK  [initandlisten] connection accepted from <IP_ADDRESS>:42432 #3 (3 connections now open)
2016-05-12T16:13:32.885+0200 I NETWORK  [initandlisten] connection accepted from <IP_ADDRESS>:42457 #4 (4 connections now open)

And this is the only corresponding log message of the application using morphia
[pool-1-thread-1] DEBUG org.mongodb.driver.protocol.insert - Inserting 1 documents into namespace dbname.statistics on connection [connectionId{localValue:2, serverValue:4}] to server localhost:27017

The class looks as follows
@Entity("statistics")
public class Statistics {

    @Id
    private ObjectId id;

    private int intA = 0;
    private int intB = 0;
    private int intC = 0;

    private Map<String, Integer> mapA = new HashMap<>(); //4751 entries in one case that fails
    private Map<String, Integer> mapB = new HashMap<>();

}

As I said, the bug only happens with certain objects of this class. Most work just fine. I figured out the following as well. It has to do with the map.
Statistics stats = new Statistics();
// ... stats is filled with data

ds.save(stats) // hangs

stats.mapA.clear()
ds.save(stats) // works  fine

This led me to the conclusion that there might be something in a string of the map that is not properly escaped or something. However, saving all content of the stats.mapA in seperate documents, e.g. with a test class works flawless.
@Entity("dbtest")
public class DbTest {
    @Id
    private ObjectId id;

    private String word;
}

stats.mapA.entrySet().forEach((entry) -> {
    ds.save(new DbTest(entry.getKey()));
});
// no problem

I'm a bit lost here with neither an exception nor something in a log file. I'm happy to do the debugging but some ideas where to start would be greatly appreciated.

I found the error. There was a leading $ sign in the key of the map. And since maps are treated like objects where the key is the field name this broke something. It is, however, very bad behavior to just fail, without anything that might give you a hint on what's wrong. This should throw an exception.

Can you post a test case to recreate it?  It might be a morphia or it might be a driver.  It could also be a "well, don't do that" but I'd like to see how you're getting there so I know if/where there's work to be done.

If I try to reproduce it standalone I get java.lang.IllegalArgumentException: Invalid BSON field name as you would expect. It has to be a logging issue. Ironically I do get the annoying cluster messages but not the exception. Will close this one and open another if I can't sort it out.

Sounds good.  Thanks.


feat(frontend): Pushdown condition above join to other side if all InputRefs are eq-condition columns

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
Pushdown join condition to other side if all InputRefs are eq-condition columns
Questions:

How to handle null_safe flag: we can apply the condition on nullsafe condition (NOT DISTINCT FROM) since the condition pushed down will filter out/not filter out rows with equal keys on both sides. This applies even if the condition is pushed from outer side to inner side. The only way that IS NOT DISTINCT FROM differs from = is that the former allows NULL = NULL, so we only need to care about how NULL is handled on both sides.
How to handle non-inner joins: we can only handle pushing down to an inner side. If the side is outer, we do not want to apply filter to it, since we do not want to filter a row which will be forwarded regardless of match on other side. Conversely, if filter originally from outer side filters row on outer side, then we will never forward a corresponding row on inner side, since we require match with outer side to forward.

TODO:

X Unit test
[X] More planner test (test more types of predicates, test non-inner joins?)

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)
Fix: https://github.com/risingwavelabs/risingwave/issues/6862

Seems this PR also caused during deterministic-simulation/fuzzing:
thread '<unnamed>' panicked at 'hash key should not be empty, use `Single` instead'

The PR LGTM. The optimization seems a subset of predicate move around. So do we need to implement it completely 🤔 @chenzl25?

Yes. Currently we can only push the predicate in a top-down way. In order to make it possible to move the predicates from one side of the join to the other side, I think we should implement predicate pulled up as well. We can use an optimizer rule to match a LogicalJoin and try to pull up its predicates and then distribute the inferred predicates to the join inputs.

Currently we can only push the predicate in a top-down way. In order to make it possible to move the predicates from one side of the join to the other side, I think we should implement predicate pulled up as well.

I believe we already do this for multiway inner joins. Not sure how applicable predicate pullup is for non-inner joins.

Currently we can only push the predicate in a top-down way. In order to make it possible to move the predicates from one side of the join to the other side, I think we should implement predicate pulled up as well.

I believe we already do this for multiway inner joins. Not sure how applicable predicate pullup is for non-inner joins.
The paper only mentions predicate pullup for: GroupBy, Select (Project) and Union/Intersection nodes.

For outer join, we can pull up the predicates from outer side and then push them down to the inner side (Both sides of full outer join are outer). All the predicate pullup logical just need to be sound but not complete.

Hello, I decided to define pure function as limited to a certain enum range of the proto. Secondly, I added planner tests. PTAL, thanks!

license-header-check  is not working and blocks many PRs to be merged after this one,
let's try to merge the next one first.


Reorganize and format code

Hi there,
I love the idea of the project and it is very interesting and definitely helps you on your daily shopping (and it surely can be expanded to other markets as well).
I've taken a look at the code and it can be improved in terms of readability and maintainability. I highly recommend creating new modules and adding docstrings everywhere. That will help you in further development and also will make other people understand the code easily. Finally, you could encapsulate all the project in a package so it can be distributed and managed effortless.
Anyway, the project looks nice the way it is right now. Congratulations for the result and the job done!

Thank you for the feedback.  I'm planning to keep chipping away at it, to
get it be more automated.  Basically the goal is to make it as simple as a
pip install, and then running a setup to set the needed variables.  I'll
probably start a new branch and begin working on that in the next couple of
days.  For now, I really just wanted to get the first round of code out
there, so people could use it if they like.  Knowing what I learned through
this process, I think there could be some really compelling use cases way
beyond what I wrote it for.
I'll definitely refactor and reorganize it as I go.  Most of my code to
date has been closed source.  So I cant say that I've had many people
actually read it before :)
On Fri, Dec 8, 2023 at 2:06 PM Alejandro González Momblán <
@.***> wrote:

Hi there,
I love the idea of the project and it is very interesting and definitely
helps you on your daily shopping (and it surely can be expanded to other
markets as well).
I've taken a look at the code and it can be improved in terms of
readability and maintainability. I highly recommend creating new modules
and adding docstrings everywhere. That will help you in further development
and also will make other people understand the code easily. Finally, you
could encapsulate all the project in a package so it can be distributed and
managed effortless.
Anyway, the project looks nice the way it is right now. Congratulations
for the result and the job done!
—
Reply to this email directly, view it on GitHub
https://github.com/huths0lo/SavonPython/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASZQAMBPQH4J3PCCJNJPEQLYIOFN3AVCNFSM6AAAAABANH6HG6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGAZTGMZWG43DQOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Wanted to post an update. I believe I can work through making it so one time passcodes are viable. I was going to use sqlite3, but I may press ahead and just use postgres. If I can do this, it would mean this tool could bolt in to any situation.

Wanted to post an update. I believe I can work through making it so one time passcodes are viable. I was going to use sqlite3, but I may press ahead and just use postgres. If I can do this, it would mean this tool could bolt in to any situation.

That's really nice, I hope you can make that happen!


install and configure Clowder VM on Nebula OpenStack

[ ] how to 'post' (upload, push) data?

rest api w/ username password using curl

[ ] mount terraref project directory on Clowder VM

how can multiple internal users write to disk? three separate processes, ea. must write to disk

NFS: easier if matching ids

Users:

ubuntu user
elastic search
mongo