feat: reimplement date and rrules objects in typescript

Current implementation of RRuleDatTime and RRuleTimezone significantly decreased performance of the library. According to my research, it's better to manipulate simple data types on rust side, but more complex object manipulations should go to js.
This PR plan:

[x] Remove RRuleDatTime and RRuleTimezone from rust library
[x] Move rust code to lib folder
[x] Set up typescript compilation from src
[x] Create TypeScript wrappers around RRule and RRuleSet
[x] Make rrule.setUntil, rruleSet.between, rruleSet.all, rruleSet.addRdate, rruleSet.addExdate, rruleSet.constructor working with datetime represented as Integer
[x] Make rrule.setUntil respect time zone
[x] Implement DateTime in TypeScript (time can be UTC or NOT UTC)
[x] Make RRuleSet iterrable

@tomquist fyi

@lsndr I think it’s still important to be able to transfer a tuple of timestamp+timezone back and forth between the JS API and the library. This is important in some scenarios to pass timezone-related validations of the RRule library (e.g. when the library is validating the UNTIL timezone against the DTSTART timezone).

@tomquist yes, you are right. I plan to pass [number, string] array between js/rust

@tomquist you can already start reviewing it. The only thing left in this PR is to make RRuleSet iterable (the occurences method behavior).
Here are the new main conceptions of the PR:

RRule and RRuleSet are immutable now and fully moved to JS side. It makes data manipulation cheaper, since we don't need to talk to rust code everytime. Rust library only used in methods like all, between, parse and e.t.c.

Now it works with new DateTime object. This object represent either local time or utc time as said in rrule spec - I think it's the easiest way and most convenient way

@tomquist I think it's ready to be merged. Please let me know what you think

@tomquist merged this PR. I'll implement #147, write some basic e2e and then 2.0 can be released. I would say next week, probably end of next week it will be released.

Hi, is the v2.0 released? I just found this lib and its benchmark is mind-blowing.
Looking forward to use the DateTime since the current npm version does not have this class exported yet.
TIA.

@beeing, it will be released hopefully today. I just need to finish manual tests


The app won't launch anymore

Describe the bug
The app is launching but can't display any cluster: loading forever.
To Reproduce
Steps to reproduce the behavior:

Launch Kontena Lens (whether by CLI or UI)

Expected behavior
Accessing my Kubernetes clusters.
Environment (please complete the following information):

Lens Version: 3.6.4
OS: Ubuntu 20.04
Installation method (e.g. snap or AppImage in Linux): snap

Logs:
info: [IPC]: setup channel "cluster:activate"
info: [IPC]: setup channel "cluster:refresh"
info: [IPC]: setup channel "cluster:disconnect"
info: [IPC]: setup channel "cluster:install-feature"
info: [IPC]: setup channel "cluster:uninstall-feature"
info: [IPC]: setup channel "cluster:upgrade-feature"
info: 🚀 Starting Lens from "/home/prey/snap/kontena-lens/120/.config/Lens"
info: SNAP env is defined, updater is disabled
info: [STORE]: LOADED from /home/prey/snap/kontena-lens/120/.config/Lens/config.json
info: [STORE]: LOADED from /home/prey/snap/kontena-lens/120/.config/Lens/lens-cluster-store.json
info: [STORE]: LOADED from /home/prey/snap/kontena-lens/120/.config/Lens/lens-workspace-store.json
info: [CLUSTER-MANAGER]: init cluster {"id":"b058a8ee-479b-4ef3-bc4c-cbbe6451b403","name":"kubernetes-admin@cluster.local","initialized":false}
error: [CLUSTER]: init failed: TypeError [ERR_INVALID_ARG_TYPE]: The "url" argument must be of type string. Received type undefined {"id":"b058a8ee-479b-4ef3-bc4c-cbbe6451b403","error":{"code":"ERR_INVALID_ARG_TYPE"}}
info: [CLUSTER-MANAGER]: init cluster {"id":"5c3bb54a-faf1-4ca6-aadc-55e46174e6d6","name":"kubernetes-admin@cluster.local","initialized":false}
error: [CLUSTER]: init failed: TypeError [ERR_INVALID_ARG_TYPE]: The "url" argument must be of type string. Received type undefined {"id":"5c3bb54a-faf1-4ca6-aadc-55e46174e6d6","error":{"code":"ERR_INVALID_ARG_TYPE"}}
info: LensProxy server has started at http://localhost:42621
(node:843195) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'ensureServer' of undefined
    at be.handleRequest (/snap/kontena-lens/120/resources/app.asar/static/build/main.js:1:99537)
    at Server.<anonymous> (/snap/kontena-lens/120/resources/app.asar/static/build/main.js:1:97870)
    at Server.emit (events.js:223:5)
    at Server.emit (/snap/kontena-lens/120/resources/app.asar/node_modules/spdy/lib/spdy/server.js:245:40)
    at parserOnIncoming (_http_server.js:748:12)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:115:17)
    at socketOnData (_http_server.js:527:22)
    at Socket.emit (events.js:223:5)
    at Socket.Readable.read (_stream_readable.js:526:10)
    at Socket.read (net.js:614:39)
(node:843195) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:843195) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I think this is the same issue as reported here: https://github.com/lensapp/lens/issues/951

You're right.
I followed the instructions and modified the $HOME/snap/kontena-lens/current/.config/Lens/lens-cluster-store.json file and changed the path of kubeconfigs from "kubeConfigPath": "/home/<user>/snap/kontena-lens/116/..." to "kubeConfigPath": "/home/<user>/snap/kontena-lens/current/...".
Now the app is starting well. Thanks!
I don't know if the issue will appear again for the next update.

Duplicate of #951. Let's track the progress there.


Error Clean Up

Before starting with #293 I just wanted to make sure that everything that came with #289 was finalized. There were a couple NSErrors that still existed so I cleaned it up to remove all usages of NSError and replace them with MoyaError.
Changes:

Forward underlying errors when cast to MoyaError does not work
Fix MoyaResponse extensions that were still throwing an NSError instead of MoyaError
Change MoyaError to conform to Equatable in tests for cleaner syntax
Update reactive extension tests to use MoyaError instead of NSError
Update ReactiveCocoaMoyaProviderSpec tests to use the SignalProducer variant when possible.

Looks great! Thanks!

Current coverage is 68.30%

Merging #297 into master will decrease coverage by -2.81% as of 8d6158d

@@            master   #297   diff @@
=====================================
  Files           12     13     +1
  Stmts          509    549    +40
  Branches         0      0
  Methods
=====================================
+ Hit            362    375    +13
  Partial          0      0
- Missed         147    174    +27

Review entire Coverage Diff as of 8d6158d

Uncovered Suggestions

+8.93% via ...rkLoggerPlugin.swift#28...76
+2.92% via Source/Moya.swift#18...33
+1.64% via ...e/MoyaResponse.swift#33...41
See 7 more...

Powered by Codecov. Updated on successful CI builds.

I've opened a PR against this branch to try to resolve some of the code coverage issues: https://github.com/petester42/Moya/pull/1

Should be good to merge now. If anyone wants to look it over.

Just a thought, but does it make sense to implement Equatable in this way? The Swift docs declare this protocol as being for "value equality", which I feel this is not, as this expression could be true: .Underlying(x) == .Underlying(y) (where x != y). Seems to be typical convention to implement equality checking for associated value enum cases to compare the associated values, provided they're equatable (example: https://github.com/ReactiveCocoa/ReactiveCocoa/blob/fd64bf6ea7a83dec13fe42244db470fd9641a9a1/ReactiveCocoa/Swift/Event.swift#L94-L111), which I think MoyaResponse could conform to to make this work for this error type.
As for checking the case equality, that's still very much useful and necessary, in this case for the tests, but it felt more appropriate as a function on the enum IMO. May be confusing for users of Moya seeking true value equality checking on this type, which may have been the reason for @tomburns' initial reservation about implementing it this way.

Equality is just what we define to be equal. In this case since we are just using it for tests its simpler to just check the error type since in the tests that use it the response is going to be the same since it is hard coded. If we were going to make it public then ya I agree. @tomburns wanted it to be exhaustive and comparing the responses too without a default case is not fun.

Sure, just trying to stay aligned with observed language conventions 😊
From Swift Equatable docs:

Instances of conforming types can be compared for value equality using operators == and !=.

I think it's more responsible of us to not pollute the type with a non-conventional Equatable implementation just to be able to use == in a test rather than a (more appropriately named) function on the type. We don't need value equality for this type at this point, but we may in the future, or users of Moya may want to extend to implement it themselves, and would be stuck as the type already conforms with behavior they don't expect.

Merging #297 into master will increase coverage by +9.07% as of 20e82cf
😱

Do however agree with -1 on default cases in switches, and not comparing underlying values, but while it's internal to the framework it matters not to consumers of the API.

Well I didn't say anything needed changed with the switch statement or how it was implemented, just that this (again, perfectly valid) case comparison should change in no way other than taking it away from Equatable where it doesn't fit.
And it is public, unless you mean unreleased. It publicly conforms to Equatable, using up that conformity in a non-standard/sane way, which was my point. Again finding myself at a loss of understanding, so I'll ask more explicitly: why is it thought that two "same-operation" errors from two entirely different responses are "equal?" Or two completely different NSError objects in .Underlying(err)? I remain with my opinion on this, because IMO .Underlying(errorA) == .Underlying(errorB) evaluating true in any scenario other than where errorA == errorB seems lacking in sanity to me. As someone (also a user of Moya) who would potentially want equality checking with the behavior I describe, and would be forced to implement it OUTSIDE of Equatable.

Good points all round. I didn't think it would have caused such a big issue since that file is not even in Moya. Yes it is public but it is only part of the test target. I'll see what I can do about it later today.

Since the MoyaError Equatable method was only used by tests to compare the types of errors, I changed it to be a matcher for Nimble. Makes more sense since it's only for tests.
@JRHeaton want to review this and then merge?

changed it to be a matcher

Great idea! :100:

Looks damn good to me! We just need to resolve the merge conflicts.

Looks good once conflicts are fixed 👍

That should do it :smile:


Nuke: openpype expose knobs validator - OP-8166

Changelog Description
Port of https://github.com/ynput/OpenPype/pull/6213

I don't think this is needed in ayon-core.

I don't think this is needed in ayon-core. Settings overrides do not work the same way as in OpenPype.

So if an existing production is using ayon now without the Exposed Knobs setting, what would happen?

So if an existing production is using ayon now without the Exposed Knobs setting, what would happen?

In AYON you'll always get current settings model values. And if the settings model has the attribute, you'll get the value, in other words core version 1.1.1 will always get settings values compatible with model 1.1.1.
NOTE: That might not be true in case of addons which have settings in server_addons, because client code lives in core and does not have to be in sync on server with settings.

NOTE: That might not be true in case of addons which have settings in server_addons, because client code lives in core and does not have to be in sync on server with settings.

So we do have to merge this PR?
Dont mind whether we do or not, just need a decision. If its a problem, then its a quick and easy fix later.

Dont mind whether we do or not, just need a decision. If its a problem, then its a quick and easy fix later.

Huge sorry, I just realized the change is in nuke and not in core settings. Yes we should merge this.


Setup hot-reload for Electron main process

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Run the desktop dev app.
Make changes in desktop/main.js

Expected Result:
The Electron app should hot-reload
Actual Result:
In order for your changes to take effect you must stop the Electron app and restart it.
Workaround:
Stop and restart the desktop app.
Platform:

Desktop App

Version Number: 1.1.41-6
Reproducible in staging?: n/a
Reproducible in production?:  n/a
View all open jobs on GitHub

Triggered auto assignment to @bfitzexpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Triggered auto assignment to @CortneyOfstad (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

@CortneyOfstad Unassigned you because this does not need triage.

I'll sign on as the CME. cc @kidroca

I am handling Desktop App size update as part of my hourly tracked work:

https://github.com/Expensify/App/issues/6927

The ticket is related in that I had to disable hot-reload for main.js in favor of the changes that reduce Desktop size
I can research for a way to bring hot-reload back

@kidroca do you want me to assign this to you and let you work on it on an hourly basis?

Yes 👍

Upwork job created + offer sent. Switching to weekly.

@bfitzexpensify Since @kidroca works on an hourly basis we won't need a specific upwork job for this, so I went ahead and unassigned you here.

Closed the Upwork job

The way to go seems to be to use electron-webpack - it supports hot reload for the main (desktop) code and the renderer (App) code https://webpack.electron.build/development#hot-module-replacement. I don't expect big changes to switch to electron-webpack since we already use webpack
electron-webpack still allows us to override the underlying webpack config similar to how we change the webpack config for storybook

Okay, that approach is fine with me 👍

Update
I've tried electron-webpack and it seems it won't be able to fit the project without too many changes
(We'll have to override almost everything including providing custom webpack configs for renderer and main)
What I've missed the first time is this comment: https://github.com/sindresorhus/electron-reloader/issues/15#issuecomment-764557661 suggesting to replace electron-reloader with electronmon
electronmon is similar to nodemon and allows us to restart electron when we have ./desktop changes
Keeping everything the same with our configs/setup and just change the npm run desktop command we use for dev

Hmmm .... will electronmon work with our setup where Electron's main process is compiled via webpack? I would think we'd need to recompile the webpack bundle for the main process, then restart electron. Curious how that will work.

I would think we'd need to recompile the webpack bundle for the main process, then restart electron.

For local development desktop/main.js is not bundled through Webpack
https://github.com/Expensify/App/blob/2fd3df03a6f40e5dedbae5be60793fc5cf67fb07/desktop/start.js#L21
Any changes to desktop/main.js would have to restart Electron, there doesn't seem to be a way around that, but it also seems to be the case from when we used electron-reloader - any change to main would have to restart Electron
(Changes to stuff used by the "renderer" will not restart Electron, they will just refresh the window like on web)
I've checked out older code where we used electron-reloader and it looks like that's what it does but for some reason for me it just kills the Desktop app when I make changes to desktop/main.js and doesn't start it again (maybe because I'm on a M1?)

I've tried electronmon with no configuration and though it did refresh on main.js changes, the changes weren't getting applied and I still had to restart electron manually
I think what was going on is that electronmon picked up the changes as renderer changes and just refreshed the window whereas it should have relaunched the electron process
renderer changes are picked up by Webpack's dev server and a refresh is triggered anyway (neither electronmon or electron-reloader is needed for this), so where just trying to find a way to reboot on main changes
I'll give this another go

electron-reloader does the same thing (restarts the electron process on main changes), but for some reason it never worked for me and now it doesn't work with webpack either

Not particularly urgent. Webpack upgrade PR is here.

Oh, I think that we can just close this since it's done and @kidroca just bills us hourly


feat(settings): add milestone pinning

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #10

PR #11   👈

This stack of pull requests is managed by Graphite.

Merge activity

Jan 1, 3:43 AM: @ToastedDev started a stack merge that includes this pull request via Graphite.


higher_percentile error with small datasets

I have been running into an error when using the conformal predictive system. When I try to obtain the prediction intervals using an higher percentile >90, I get an index error (refer to traceback below). Since the intervals compute with a maximum value of 90, could the error be an issue caused by a small dataset size of 144 train, 48 cal and 49 test samples (I have tried this with a larger dataset and the intervals compute with an higher_percentile>90 as expected)?  Assuming dataset size is the issue, is there a way to make this work for small datasets?
File C:\WINDOWS\System32\erty\lib\site-packages\crepes\base.py:457, in ConformalPredictiveSystem.predict(self, y_hat, sigmas, bins, y, lower_percentiles, higher_percentiles, y_min, y_max, return_cpds, cpds_by_bins)
450             for b in range(len(bin_values)):
451                 higher_indexes = [
452                     int(np.ceil(higher_percentile/100
453                                 * (len(bin_alphas[b])+1)))-1
454                     for higher_percentile in higher_percentiles]
455                 result[bin_indexes[b],
456                        no_prec_result_cols:no_prec_result_cols
--> 457                        + len(higher_indexes)] = cpds[b]
458                            [:,higher_indexes]
459 if y_max < np.inf:
460     result[:,no_prec_result_cols:no_prec_result_cols
461            + len(higher_percentiles)]
462            [result[:,no_prec_result_cols:no_prec_result_cols
463                    + len(higher_percentiles)]>y_max] = y_max
IndexError: index 10 is out of bounds for axis 1 with size 10

Hi,
Thanks for your question! Your issue is related to #1, i.e., lack of informative error messages, which in your case should have explained that the number of calibration instances is not sufficient to extract the requested percentile. This may appear surprising since you are using 48 calibration instances, which should be more than enough to extract the 90th percentile (actually it should suffice with just 9 instances); however, from the (cryptic) error message, it seems that you are using a Mondrian approach, which requires a sufficient number of instances in each category (bin). As an alternative to increasing the number of calibration instances, you may consider reducing the number of categories, or even skip the Mondrian approach (not using bins at all).
Best regards,
Henrik

Hi,
Thanks again for pointing this out; this is now handled by issuing a warning in the new release (0.2.0)


Keras fails to run on this simplest 3-column dataset!!

z=f(x,y)=x+y
There are 3 columns in the dataset with x running from 1 to 1040 and y running from 1040 to 1. The value of z is a constant 1041. Deep learning with Keras doesn't work on this simplest possible dataset. It always returns zero accuracy and zero prediction. Why?
deep-learning-with-plus.zip

Definition of accuracy is exactly match, but your network provide a float number. Therefore, it almost impossible to get a accuracy larger than 0.
Data is not normalized, which is not good for deep learning.

Even if I ran with Normalized data, mterics=['mae'] etc.
but still the prediction is always zero.
Venkat
On Sat, Apr 15, 2017 at 11:03 AM, Joel<EMAIL_ADDRESS>wrote:

Definition of accuracy is exactly match, but your network provide a
float number. Therefore, it almost impossible to get a accuracy larger than

Data is not normalized, which is not good for deep learning.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/6260#issuecomment-294273717,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHvqxb_mm5jXBBmh9557joZRvjkiTn5ks5rwFbFgaJpZM4M-QMz
.

X = dataset[:,0:2] / 1041
Y = dataset[:,2] / 1041
print(numpy.round(predictions * 1041))
# acc: 100.00%

cmd.txt
I still get 0% and 0.0 prediction
deep-learning-plus.zip

Is it running fine in your version of keras?

Keras 2.0.3.

You didn't normalize Y.
Normalizer is normalizing over feature dim, which is not suitable here.

In the new dataset Y=1.0 not 1401, so it is normailzed but I am not
getting anything different.
Where you able to successfully run the code?
If you have a revised dataset and code that works, then can you send it to
me?
Venkat
On Sat, Apr 15, 2017 at 12:23 PM, Joel<EMAIL_ADDRESS>wrote:

Keras 2.0.3.

You didn't normalize Y.
Normalizer is normalizing over feature dim, which is not suitable
here.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/6260#issuecomment-294276503,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHvq1u85bCCrNqoBAyZD-54p4JdSIMQks5rwGmEgaJpZM4M-QMz
.

Just change 3 line as I mention above:
from keras.models import Sequential
from keras.layers import Dense, Activation
from sklearn.preprocessing import Normalizer
import numpy
# fix random seed for reproducibility
seed = 10
numpy.random.seed(seed)
# load division dataset
dataset = numpy.loadtxt("plus.csv", delimiter=",")
# split into input (X) and output (Y) variables
X = dataset[:,0:2] / 1041
#print(X)
Y = dataset[:,2] / 1041
#print(Y)
# create model
model = Sequential([
                  Dense(10, input_dim=2, init='uniform', activation='relu'),
 #                 Dense(2, init='uniform', activation='relu'),
                  Dense(1, init='uniform', activation='relu'),
             ])
# Compile model
model.compile(loss='mse', optimizer='adam', metrics=['accuracy'], vebose=1)
# Fit the model
model.fit(X, Y, nb_epoch=100, batch_size=100)
# evaluate the model
scores = model.evaluate(X, Y)
print("%s: %.2f%%" % (model.metrics_names[1], scores[1]*100))
# calculate predictions
predictions = model.predict(X)
# round predictions
print(numpy.round(predictions * 1041))

Oops!
I just switched the backend to Theano and it works like magic, so it is a
bug in Tensorflow after all!!
Theano also reported a syntax error "vebose=2" which should be "verbose"
but in case "verbose" option is not allowed in compile function, but only
in the model fitting function.
I any case changing that also didn't fix the Tensorflow bug ;)
but Theano works just as it should.
On Sat, Apr 15, 2017 at 12:43 PM, Joel<EMAIL_ADDRESS>wrote:

Just change 3 line as I mention above:
from keras.models import Sequentialfrom keras.layers import Dense, Activationfrom sklearn.preprocessing import Normalizerimport numpy# fix random seed for reproducibility
seed = 10
numpy.random.seed(seed)# load division dataset
dataset = numpy.loadtxt("plus.csv", delimiter=",")# split into input (X) and output (Y) variables
X = dataset[:,0:2] / 1041#print(X)
Y = dataset[:,2] / 1041#print(Y)# create model
model = Sequential([
Dense(10, input_dim=2, init='uniform', activation='relu'),
Dense(2, init='uniform', activation='relu'),
              Dense(1, init='uniform', activation='relu'),
         ])# Compile model

model.compile(loss='mse', optimizer='adam', metrics=['accuracy'], vebose=1)# Fit the model
model.fit(X, Y, nb_epoch=100, batch_size=100)# evaluate the model
scores = model.evaluate(X, Y)print("%s: %.2f%%" % (model.metrics_names[1], scores[1]*100))# calculate predictions
predictions = model.predict(X)# round predictionsprint(numpy.round(predictions * 1041))
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/6260#issuecomment-294277198,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHvqxV92NSinnmaNZNDfky7jjKyCBAJks5rwG4ngaJpZM4M-QMz
.

Actually I use tensorflow backend, so I don't think it's a tf bug.

Then it must be a bug in the version I am using which might have been fixed
later.
I use an official docker image that has tensorflow version 0.12.1.
If its not a bug in tensorflow, what we will it be?
On Sat, Apr 15, 2017 at 2:59 PM, Joel<EMAIL_ADDRESS>wrote:

Actually I use tensorflow backend, so I don't think it's a tf bug.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/6260#issuecomment-294282481,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHvq_WI9tfJpstJIKKGKaoHpsDnjpiWks5rwI3wgaJpZM4M-QMz
.

As I said before, accuracy is not used in that way. No matter accuracy is 0% or 100%, it's expected. All you can do is inference offline, round it and calculate accuracy in a correct way.

You missed the point completely!!
I have been using this docker instance with Tensorflow for running other
datasets and problems fairly successfully.
Tensorflow did not run at all for me for this problem with all the
predictions staying zero even if we use metric='['mae']" or anything else.
Theano worked fine for the same problem, why?
Anyway, I am at present trying to create a fairly simple unary and binary
algebraic functions to see how good deep learning is at predicting them.
Strangely I find that it s struggling, despite all the hype that it can
approximate any continuous function etc ;)
On Sat, Apr 15, 2017 at 4:27 PM, Joel<EMAIL_ADDRESS>wrote:

As I said before, accuracy is not used in that way. No matter accuracy is
0% or 100%, it's expected. All you can do is inference offline, round it
and calculate accuracy in a correct way.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/6260#issuecomment-294286069,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHvqxhhsXR1BPsedlxgeyaa9TVo2RXHks5rwKKygaJpZM4M-QMz
.


In search of an operator for inconsistent JSON format. Does it exist?

I am searching for an operator to help me concisely parse a JSON format that comes in two variants. Is this currently possible? If not, is it possible to define such an operator?
Sample JSON
{
  "name_tag": "Brian"
}

{
  "name-tag": "Brian"
}

Models
struct User {
    let nameTag: String
}

Ideally, I would write:
extension User: Decodable {
    static func decode(_ j: JSON) -> Decoded<User> {
        return curry(self.init)
            <^> j <| "name-tag" <?OPERATOR?> "name_tag"
    }
}

Argo Version
4.1.1
Dependency Manager
Carthage

This may work:
(j <| "name-tag") <|> (j <| "name_tag")
I'm not sure whether the parentheses are necessary.

I tried to add that but couldn't get it to compile without expression complexity errors. Hmm.

In that case move the curried initializer to a separate value.

Or since you only have one value there you don't need the curried initializer at all.

I'm fascinated by the frequency with which you (@btc) are running into these compiler complexity errors. I'm really sorry about that.
@jshier is correct, the operator you are looking for is <|> (alternatively, using the .or(_:) instance method on Decoded), and I'd write it the way he did.
I'd definitely try saving the curried function off to an intermediate constant first, but if that doesn't work, you could also try saving the result of this decoding operation off to an intermediate constant:
extension User: Decodable {
  static func decode(_ j: JSON) -> Decoded<User> {
    let tag: Decoded<String> = (j <| "name-tag") <|> (j <| "name_tag")

    return curry(self.init)
      <^> tag
  }
}

Also:
func eitherO(_ j: JSON, _ field: String, _ alt: String) -> Decoded<String> {
    return  j <|? field <|> j <|? alt
}


Vehicle type split change/update

We still have the electric vehicle share etc. from the 2010 ETP. need a good update!
See 3_SHA_TypeSplit_Vehicles_V2.3.xlsx

Figure 5.3 in "Energy Technology Perspectives 2017" report shows the global market penetration of different powertrains (2015-2060) under different scenarios.  Accordingly, pp 223-226 mention a couple of numbers (e.g., "By 2020, 2.3% of all PLDVs on the road have ultra-low or zero-emission powertrains of three types: 0.9% PHEVs, 1.3% battery-electric vehicles (BEVs) and 0.05% fuel cell electric vehicles (FCEVs).") that may be useful for intra-/extrapolate market evolution.
Ideally, we may obtain the complete dataset behind Fig.5.3 from IEA with the help from Eric.

Great idea, Qingshi! Would you be so kind to ask him?

Great idea, Qingshi! Would you be so kind to ask him?

Sure, will do. Will cc you and Stefan on this.

The figures and underlying data can be found here https://www.iea.org/reports/energy-technology-perspectives-2017

I back-calculated the inflow from the stock figures and converted to %, the result is now part of the RECC database. May swith from linear to spline interpolation as current result shows small discontinuities.


Run - Support URLs

Summary of the new feature/enhancement
The run command would be truly ubiquitous if it translated URLs to an action to open the user's default browser.
'www.microsoft.com' should navigate to https://www.microsoft.com.   Entries which start with www denote a url.  Assume navigation with the https protocol.

in theory, this should be an easy fix, yes, 100% as run prompt can do this.
"> www.microsoft.com" does this but that is going through the shell plugin.  if we detect www. http or https as a lead, route thorugh like the shell plugin

I still feel having to prepend www before address is kind of repetitive. Identifying the postfix such as .com/.in will be more feasible approach I feel. In that case unless I have completed typing the full address search can be treaded as text and when a .domain identified can be redirected to browser.
At the same time it will be great help for developers if you can support IP's as well. I often have to type quickly visit few ip's but all I have to do is open browser and type-in. ( I know It's not a generally used feature but for developers or network admins a great +)

How about a prefix like the shell plugin and it would just use your default browser to run the url or search if it is not a valid url?
E.g. !microsoft would return a search in you default search engine on you default browser for Microsoft and microsoft.com would take you straight to microsoft.com. This way one does not have to prefix the url with www and one does not have to make a list of all top-level domains and one does not have to open the browser first.

IMO that becomes an expectancy from users to know about "!" prepend. I feel It should be more natural like, if I type "Google" It means either I want to see a program named "Google " or search the term "Google" on whatever default search engine on default browser I have.
I don't think Indexing some popular domains would be a problem or maybe just Identifying something. something maybe a URL and then showing an option in suggestion pane to open URL.

I would be interested in this PR, a global design for this would be a seperate plugin whith no activated hotkey and the query would be parsed in the following way.

Quickly parse it as a valid url / ip with/without port/schema (e.g. scheme://(host|ip):port where scheme/port are optional and default to HTTPS (on default port)
If it's a valid Url, try to DNS lookup it (via https://docs.microsoft.com/en-us/dotnet/api/system.net.dns.gethostaddresses?view=netcore-3.1#System_Net_Dns_GetHostAddresses_System_String_)
If both are valid, return it otherwise return "null" which would prevent it from returning any results.

Regarding the result list, it should open the default browser (no way to override this) with the url and for the icon it would be easiest to take one of the Fluent Icons in dark/light mode.
Any other suggestions/ideas before implementing this?

@royvou +1 for IP
Just asking, by DNS lookup means, do the user needs to be connected to the internet? What about the local sites on dev machines? How that will be handled?
Hope to see it soon!

Lots of substantial conversation here. The original ask is to just pass search text to the browser and let it handle the workflow.  The browser handles URL parsing, DNS, and best effort matches to domain names. So much effort exists within browsers to interpret intent that I don't think we need to overthink design on this one.

Sounds great! I'll create a PR today or tomorrow.

With no offence to anyone, may be the substantial conversation was because of title (Support URL [not text 😅😅]).
Furthermore, if that's the case then, how would we know what possible valid Inputs (URL/IP's) can be passed to the browser and what values can not be?
Like if I enter "www.google.com" then It means, I want to open URL google.com and if I just enter "google" I want to search term google with whatever default search engine.
May be if that the case this issue https://github.com/microsoft/PowerToys/issues/3245 addresses the ask and can be marked as duplicate.

The PR has been created at #5160, unit tests exists to show parsing behaviour, see here (False/null results will not show up in PT Run)
I think #3245 should not impact this PR, but this would be a related feature!

*Ideas for the URL plugin"

Having a Tooltip for showing urls completely which are to long for result list width.

If we are able to get the path of the default browser in real-time, we could show it's icon in front of the result and the sub lable "Open webpage in browser name" in the result.

Maybe a setting that defines the browser to be used would be interesting.
Have no use case in mind at the moment.

why would a url you're typing in be too long?

why would a url you're typing in be too long?

Maybe while copy and past.
But it was only a thought of mine.

@htcfreek, then you know what the item is, no?  start menu / run prompt do not do that behavior

Another update but missing this crucial feature! The only think that is holding me back from completely switching to powertoys as my fool time tool.. 😅😅

Another update but missing this crucial feature! The only think that is holding me back from completely switching to powertoys as my full time tool.. 😅😅

@shirkerohit, small team, we improved a lot in 0.20 and targeted at improving results and UX performance. We removed some UX thread blocking issues and figured out how in .21 we can even improve more.  We also drastically increased our local build time which means we can iterate quicker.
@royvou is helping out and helping add support for this.  It is really shaping up and why open source is great, if something is important to you, help fix it.

@crutkas Thanks for you all efforts but I wasn't complaining but just mentioning ✌.
Yes, I do agree with your opinion over open source but I am less into .net / MS dev world and would love to contribute in any way possible in near future.

large sum of the code base is C++ as well @shirkerohit

Ok will check what I can I support with! 👍

Fix added in 0.21.1, please go to https://github.com/microsoft/PowerToys/releases to upgrade


Compilation Instructions?

Very cool presentation at GRcon17!
Would it be possible to get some basic instructions on how to compile and set up your Android app?

Unfortunately we can't distribute any of the Android app that goes along
with our project, since it's the property of the group funding our
research. The only code available is for the custom gnuradio blocks used in
the direction of arrival analysis.
Sam
On Dec 7, 2017 7:43 PM, "rtlsdrblog"<EMAIL_ADDRESS>wrote:

Very cool presentation at GRcon17!
Would it be possible to get some basic instructions on how to compile and
set up your Android app?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/samwhiting/gnuradio-doa/issues/1, or mute the thread
https://github.com/notifications/unsubscribe-auth/AWSUzRcWIXfclUFxzpsBnbQSjRWBJ2bqks5s-KJJgaJpZM4Q6gYl
.


flowchart renders as code

Firstly, this is a nice app, thanks for creating it.
My issue is that the example flowchart doesn't render when I copy paste it into my document. It also doesn't work when I create a new document and paste it there.
```flow
st=>start: Start
e=>end
op=>operation: My Operation
cond=>condition: Yes or No?

st->op->cond
cond(yes)->e
cond(no)->op
```.

The period at the end is because I don't know how to escape '```' to demonstrate I'm just copying the flowchart.
Version  5.7.1

StackEdit v5 now uses the Mermaid syntax for charts and diagrams.
Example:
```mermaid
sequenceDiagram
Alice ->> Bob: Hello Bob, how are you?
Bob-->>John: How about you John?
Bob--x Alice: I am good thanks!
Bob-x John: I am good thanks!
Note right of John: Bob thinks a long
long time, so long
that the text does
not fit on a row.

Bob-->Alice: Checking with John...
Alice->John: Yes... John, how are you?
```


Pass through ICache-related parameters in compliance test

The RISC-V compliance toplevel needs to pass through the instruction
cache-related parameters, which are set by the ibex configuration
script.

This unbreaks CI (I didn't see that there are checks missing when merging https://github.com/lowRISC/ibex/pull/1140).


[OmniConfig] Boolean values with default=true don't work correctly in CLI options

Boolean config values get mapped to the store_true argparse action, which works fine if the default value is false but doesn't work if the default is true since there's no way to set them to false via CLI args. We should special-case this and map them to the 'BooleanOptionalAction' instead, (I think?) which adds two options to the CLI, one to enable and one to disable the value.

Fixed in https://github.com/grahamtt/prosper-shared/commit/d379a62b1e9827be46a53338f82ad17c57bcee53


Feature request : format Value before apply validation

Formatter
It would be nice to have a formatter for any property like upper-case , lower-case or custom format
{
    type: String,
    formater : 'lower-case'
    enum: ["day", "month", "year"]
}

or something like that
{
    type: String,
    formater: function(data, schema) {
           return data.toLowerCase();
     },
    enum: ["day", "month", "year"]
}

I agree. I would, though, call it transform instead, and make it a generic validator for all types. I will look into it.

After thinking a little more about this, I actually think the custom validator should become a hook. I think I'll rethink it as something like this.
{
    type: String,
    on: {
        pre: function(data, schema) {
            // Pre validation
        },
        post: function(data, schema) {
            // Post validation
        }
    }
}


Create Rock-Paper-Scissors-Game.js

What a great code :smile: !
Just a little tip, its good to always put a description on your PRs to make more understandable.
Thank you for contributing! :rocket:


Add tls support

Upstream PR at https://github.com/github/gh-ost/pull/705
Description
This PR adds initial support for enforcing TLS/SSL connections for the databases involved in the schema changes. In this initial pass, a gh-ost user can enforce ssl be used for connections using the --ssl flag on the command line. If the user wishes to enforce checking validity of the database's certificate, the user can also specify a CA certificate in pem format with the --ssl-ca option.
Adding these two options is sufficient for our use case right now in connecting to AWS RDS instances. While there are plenty more options that can be specified by the native mysql client regarding ssl, this can provide a good starting point for other work by those with more complex needs.
Testing
We tested this updated code against an Aurora2 cluster running a MySQL 5.7 compatible engine.

For testing we added a user to the mysql cluster with REQUIRE SSL set.
We then attempted to run an alter table command using gh-ost against the cluster, but without the new ssl options enabled. As expected we received an access denied when attempting to connect with gh-ost.
We then attempted the same alter table command using all the same options, except also adding on the new --ssl flag, along with specifying the --ssl-ca certificate for AWS RDS. The job executed flawlessly.

RM +1 dependencies won't be scanned for this repo. this is a temporary fork/fix for tls, once the PR into the original fork is merged that will be used again.

Don't merge this yet @brandonbodnar-wk because once https://github.com/Workiva/gh-ost/pull/3 is merged the builds will pass on this.

RM +1


⚠ Processors has degraded performance

In 74266f6, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 778 ms

Resolved: Processors performance has improved in 5d681dd.


Click on a category then sort it by a view(top, best...) impossible

This is on the roadmap, also I think there's probably an issue for that already. So closing it for now :)


Why "cc_ros_library" will generate .so and .a at the same time? And how can I choose one to pack?

Hi Milan
This project is very nice and useful for ROS + bazel user.
But when I  try to use it and learn it, I didn't get why "cc_ros_library" will generate .so and .a at the same time? And how can I choose one to pack?
Would you please give me a help on this?
Thanks

Hi, cc_ros_library is a macro that wraps Bazel's native cc_library. When you build a library, then it creates .so and .a indeed; one typically doesn't build libs, but build executables and runs tests. But, when you build an executable then it doesn't build libraries, but links object files directly into an executable.

And how can I choose one to pack?

Can you elaborate on this one, please?


Expose Observable.of as a standalone function

Currently one has to import import 'rxjs/add/observable/fromArray'; in order to get Observable.of which is pretty confusing. Can we make it so that import 'rxjs/add/observable/of'; works?

My assumption's https://github.com/ReactiveX/RxJS/pull/922#issuecomment-162967611 was intention for this which was not landed yet -

if we just rename observable/fromArray to observable/of, I think I'm okay just leaving these things out for now

Will update once @blesh confirms my understanding's correct.

I see. Thanks for the quick response.

I think we can reasonably add an add/observable/of file, actually.

I read that those are generated from here but I don't get exactly what to do to make it generate an add/observable/of file. Or should I just create it manually?

@cburgdorf you could create it manually, I believe, since there are no name conflicts. Just add a comment to the top of the file to indicate it was manually created (since the others have the same for auto created)

Ok, guess this should do it https://github.com/ReactiveX/RxJS/pull/1197
I have some problems with the build since I don't have a proper Java environment. It's currently untested.

fromArray is deprecated in RxJS 4. Couldn't we just rename fromArray to of?


docs: add range query align to docs

What's Changed in this PR
Add range query align to and Interval docs
merge after https://github.com/GreptimeTeam/greptimedb/pull/2842
Checklist

[x] Please ensure that the content in summary.yml matches the current document structure when you changed the document structure.
[x] This change requires follow-up update in localized docs.

The keyword Calander with time_zone might confuse users, please wait for further API discussion.


Design System Storybook: Banner

Summary
Two variations of a banner  built from figma - one for editor, one for dashboard
Relevant Technical Choices
Includes only the presentational aspect of the banner and forwards the banner ref to manipulate the functionality however is necessary.
Used css grid to maintain dimensions and minimize checks for where to put elements since banners look different in each version.
To-do
User-facing changes
None, storybook only
Testing Instructions
See banner in storybook (designsystem/components/banner).

default is set with all the knobs so you can see things change
the editor and dashboard varieties should follow the designs in figma. Background urls will come from components, these don't match the specs.

Addresses #5214

For a single line content and title banner I think we should make sure they have the same vertical alignment

For a single line content and title banner I think we should make sure they have the same vertical alignment

@carlos-kelly - totally get that this could look a little odd, however there's actually extra space on the banner text. I've highlighted the two elements in figma:

@samitron7 do you want these to line up?

Yes, for single line text, please vertically align. Also the spacing between the text box should be 32. We're using a 8px grid system so round the number so they are divisible by 8 whenever you catch odd numbers.

@carlos-kelly - alignment is updated if you want to see! Thanks for flagging that.

@BrittanyIRL In Storybook, the first and last banners in screenshot are not responsive:

@samitron7 - thanks! Added a bug ticket, i'll fix this today and maybe later this week we can discuss breakpoints? https://github.com/google/web-stories-wp/issues/5495

I've had a look and the banners are now responsive. Closing the ticket.

I've had a look and the banners are now responsive. Closing the ticket.


Roll Flutter Engine from 2a6e1002eba6 to cafafa141a59 (2 revisions)

https://github.com/flutter/engine/compare/2a6e1002eba6...cafafa141a59
2022-10-17<EMAIL_ADDRESS>Revert "Build Web SDK in wasm build tree (#36520)" (flutter/engine#36805)
2022-10-17<EMAIL_ADDRESS>Roll Skia from 455c212410c3 to 7919bb8a3bfa (5 revisions) (flutter/engine#36802)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Improve Share Speed and Add Shared Indicator in Breadcrumb Area

When I click on 'Create/Update Link,' it takes a too much amount of time (sometimes 30 min and more) to share the document on the web and display the share address and sometimes its not displaying the shared address even after too much time. Could you make this process faster, similar to the sharing feature in Capacities or Notion? In those apps, the document is instantly shared on the web, and a secret share link is provided almost immediately.
Please take a look at the Capacities sharing feature—it is very user-friendly and efficient. I would be grateful if we could have a similar experience in SiYuan.
https://github.com/user-attachments/assets/a4951b99-8dd5-4aa3-af8a-741f0fe86f4b
Once the content has been shared in Capacities, the user can see a beautiful shared indicator in the breadcrumb area. I would love to see a similar feature in SiYuan so that we can easily know which documents have been shared and which have not.

Last but not least, please change the icon to the one shown in the image below. It looks better, in my opinion.

This is the current icon which doesn't looks good to me.

Thank you for considering this improvement!

The upload is slow, mainly because the connection to the server (the default is <IP_ADDRESS>) is slow. I guess your client is not in China, but the server is in China, and I don't have servers in other countries, so the sharing is very slow. You can consider using docker to build your own server.

Thanks, your icon suggestion is very good, I will update the image in the next version.

分享页面多了以后  占用资源 公共部分的js有好多  可以压缩空间俺  有没有办法压缩呢  比如公共空间提取出来

分享页面多了以后 占用资源 公共部分的js有好多 可以压缩空间俺 有没有办法压缩呢 比如公共空间提取出来

如果你是为了节省硬盘空间，快速的方法，可以参考find 资源目录 -name 'resources.zip' | xargs -n1  /usr/bin/rm搜索资源目录的压缩包并删除。我这边六百多个压缩包，占用了7.7G。如果纯粹为了提取公共文件，那么需要修改程序了。

When I click on 'Create/Update Link,' it takes a too much amount of time (sometimes 30 min and more) to share the document on the web and display the share address and sometimes its not displaying the shared address even after too much time. Could you make this process faster, similar to the sharing feature in Capacities or Notion? In those apps, the document is instantly shared on the web, and a secret share link is provided almost immediately.
Please take a look at the Capacities sharing feature—it is very user-friendly and efficient. I would be grateful if we could have a similar experience in SiYuan.
Centered.Document.View.Web.Sharing.Issue.12978.siyuan-note-siyuan.mp4
Once the content has been shared in Capacities, the user can see a beautiful shared indicator in the breadcrumb area. I would love to see a similar feature in SiYuan so that we can easily know which documents have been shared and which have not.

Last but not least, please change the icon to the one shown in the image below. It looks better, in my opinion.

This is the current icon which doesn't looks good to me.

Thank you for considering this improvement!

In the latest version (v2.3.1), a new server address (including https) is used, which will improve the user experience.


INotifyRead Don't work with MultiRecordEngine?

INotifyRead Don't work with MultiRecordEngine?

Hi friend, some answer about it?

I don't know exactly what your situation is. Could you provide more details?
I ran into a scenario where it appeared INotifyRead wasn't working with a MultiRecordEngine. I had three types being passed in, and only the second implemented INotifyRead. Apparently, the flag that determines if read/write events should be fired only uses the first type passed into the MultiRecordEngine. I rearranged the types so the INotifyRead type was first. Then I started getting errors that my other two did not implement INotifyRead. The workaround was to implement INotifyRead on all of my types.
Suggestion:
Please update the MultiRecordEngine so it dynamically checks for the INotifyRead/INotifyWrite interfaces on every type. This should not be an all-or-nothing solution.

Has any progress been made on this issue? I'm still facing it today.

This is same as #401.


shouldAddBreadcrumb doesn't skip breadcrumb

node: v9.6.1
@sentry/electron: 0.5.4

I init sentry as
init({
  dsn: RAVEN_DSN,
  enableJavaScript: true,
  enableNative: true,
  maxBreadcrumbs: 10,
  shouldAddBreadcrumb(crumb) {
    return false;
  }
}

With this configuration, the captured crash does have 10 breadscrumbs. If I change 10 to 20, it will have 20. It means maxBreadcrumbs works.
Problem here is I return false in shouldAddBreadcrumb, according to document, shouldAddBreadcrumb is A callback allowing to skip breadcrumbs.. I return false should ask sentry to ignore all breadscrumbs. But in fact crash report still have all manual and automatic breadcrumbs.

Just realised it do filter breadscrumbs.
But the captured crash report  brings breadcrumbs logged long time ago.


mac-10 devicelab error: "iPhone 11 is not available because it is unpaired Pair with the device in the Xcode Devices Window, and respond to any pairing prompts on the device."

https://ci.chromium.org/ui/p/flutter/builders/staging/Mac_ios platform_views_scroll_perf_bottom_ad_banner__timeline_summary/76/infra
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8742729113299342273/+/u/Prepare_iOS_device/Dismiss_iOS_dialogs/Run_app_to_dismiss_dialogs/stdout
 	Ineligible destinations for the "infra-dialog" scheme:
 		{ platform:iOS, arch:arm64e, id:00008030-000E4C9E226B402E, name:iPhone 11, error:iPhone 11 is not available because it is unpaired Pair with the device in the Xcode Devices Window, and respond to any pairing prompts on the device. }

@kentnguyen99 can you take a look?

mac-23 is hitting the same:
https://ci.chromium.org/ui/p/flutter/builders/staging/Mac_ios platform_views_scroll_perf_bottom_ad_banner__timeline_summary/2/infra

@jmagman Can you give another try?  It should be working now.

@kentnguyen99 also seeing on mac-26, could you check that one as well?

mac-26 is good now. Can you check again from your end?

I see mac-10 again?
https://ci.chromium.org/ui/p/flutter/builders/staging/Mac_ios platform_views_scroll_perf_bottom_ad_banner__timeline_summary/92/infra
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8742678619901646033/+/u/Prepare_iOS_device/Dismiss_iOS_dialogs/Run_app_to_dismiss_dialogs/stdout

Mac-10's phone is back online, it needs to hit "Trust" on the phone.

Thank you!


feat: Implement eth_getTransactionReceipt method

Description
Inputs are the same for both starknet and eth calls
https://github.com/keep-starknet-strange/rosettanet/blob/main/rpc-call-examples/eth_getTransactionReceipt.hurl
https://github.com/keep-starknet-strange/rosettanet/blob/main/rpc-call-examples/starknet_getTransactionReceipt.hurl
Get the starknet receipt result and format it into Ethereum format.
Please discuss if non-matching properties exist.
Requirements

Unit tests have to be implemented.
Do not change the existing type structure
Tests must have non exist transaction results as well.

Completion Time
The issue is assumed to be completed in 5 days. If you need more time, please also specify that.

@ermvrs what's your vision for these fields?

cumulativeGasUsed, gasUsed - one can only get the paid fee from starknet
logs - starknet events?
logsBloom - hardcoded 0?
status - it probably could also be hardcoded?

cumulativeGasUsed, gasUsed : We can use paid fee
logs - SN Events if possible
logsBloom - hardcoded 0
status - Accepted on l2, l1 etc. starknet statuses but with hex (0x1,0x2...)

I would like to be assigned to this issue.

Assigned

I'm just going to put this here for future reference.
starknet_getTransactionReceipt JSON RPC method can either return a transaction receipt or a pending transaction receipt.
TransactionReceipt: https://github.com/xJonathanLEI/starknet-rs/blob/6cadb198644cf5e942187896c2e6bb3ecc9edc6e/starknet-core/src/types/mod.rs#L262
PendingTransactionReceipt: https://github.com/xJonathanLEI/starknet-rs/blob/6cadb198644cf5e942187896c2e6bb3ecc9edc6e/starknet-core/src/types/mod.rs#L277

Properties of the result of starknet_getTransactionReceipt method:

transaction_hash
actual_fee
messages_sent
events
execution_resources
execution_result
contract_address (only DEPLOY and DEPLOY_ACCOUNT )
finality_status (only non-pending)
block_hash (only non-pending)
block_number (only non-pending)
message_hash (only L1_HANDLER)

cumulativeGasUsed, gasUsed : We can use paid fee logs - SN Events if possible logsBloom - hardcoded 0 status - Accepted on l2, l1 etc. starknet statuses but with hex (0x1,0x2...)

If I'm not mistaken status property of eth_getTransactionReceipt method is supposed to be either 0x0 or 0x1 after the Byzantium hard fork.
I doubt that being non-compatible is okay here.
What do you think?

We don't need to support all properties, just possible ones. You can pass compatible values if there is no way to format starknet output.

@berzanorg maybe it's a good idea to create a (draft) PR so that is easier for @ermvrs and others to follow and give review


Update google cloud dependencies on merlin sdk

What this PR does / why we need it:

Current merlin sdk has tight contraint on their dependency version, it might cause conflict with other dependencies that are used alongside merlin-sdk. This PR relax the dependency in merlin sdk
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

Checklist

[ ] Added unit test, integration, and/or e2e tests
[ ] Tested locally
[ ] Updated documentation
[ ] Update Swagger spec if the PR introduce API changes
[ ] Regenerated Golang and Python client if the PR introduce API changes

Do we see any risk of breaking existing batch model?
Do we need to regenerate the proto definition for batch predictor? I remember you need to regenerate it in https://github.com/gojek/merlin/pull/47

Do we see any risk of breaking existing batch model?

There is a risk if user use older version of grpcio e.g 1.2.2, to solve this user needs to pin older merlin-sdk version (not the latest version)

Do we need to regenerate the proto definition for batch predictor? I remember you need to regenerate it in #47
I think we can regenerate the proto with the same risk like the first point. I don't regenerate the proto because currently it didn't block anything

There is a risk if user use older version of grpcio e.g 1.2.2, to solve this user needs to pin older merlin-sdk version (not the latest version)

Pin merlin-sdk? Isn't it embedded in the batch predictor image? Is it better if they update their dependency?

I don't regenerate the proto because currently it didn't block anything

I see, I think we don't need to regenerate since it's forward compatible correct?

Pin merlin-sdk? Isn't it embedded in the batch predictor image? Is it better if they update their dependency?

Yes, it is better for them to update the dependency. If user hesitant to update their dependency they can pin merlin-sdk version on their conda yaml


Support for whitelist and blacklist at the same time?

Hi, is it possible to have a whitelist and a blacklist at the same time? For example, imagine I have multiple rules in my blacklist such as "procrastination", "wasting.*time", "filter.*this", "block.*this", etc. because I want to prevent myself from searching those things. However, sometimes there might be exceptions, for example, imagine I want to read a Wikipedia article about procrastination. In that case it would be OK to let me access the page because Wikipedia is a safe website. Therefore, it would be great to have the feature of defining both a blacklist and a whitelist of regexes, so that if a search matches a blacklist regex then block the page UNLESS it also matches a whitelist regex. Maybe instead of "white-list" a better name would be "exceptions-list".

@eryw, any updates on this by any chance?

@eryw, any updates on this so far by any chance?

i'll send you 100 Euros if you implement this (BlackList + ExceptionList). No kidding, this extension is GREAT by its very simplicity, but w/o this feature it's useless if you really want to block extensively. I've been checking lots of site blockers, none of the ones i could find seem to have this option, so i had to decide for which one to make my pledge. And your extension came on top should you implement this.


Update notes to reflect service being available in all prisons in England and Wales

Should not be merged/deployed until all prisons join the service


Fix/demoing storybook build

Storybook builds were taking incredibly long and perceptible to crashing because it ran out of memory.
After a lot of investigation it turned out to be a simple problem with a glob pattern for copying the custom-elements.json file, which was recursing into node_modules directories. Because rollup-plugin-cpy is using a deprecated API, I took the opportunity to replace it with a simpler version.
Besides this I made some more optimization, running the bundle and build for one config. This way the previous could be garbage collected if builds take really long.
Finally I suppressed some other warnings during the build to make the output cleaner. These are warnings we can do anything about when using storybook.

@Westbrook this is probably the proper fix for the issues you were seeing as well

Great to hear :) we can make it even faster if we allow dropping the IE11 build (if you dont need to support IE11)


[feat] Silent (or quieter) Windows updater

Describe the problem
The Windows updater currently just re-runs the installer at update time, which gets the job done, but the UX could be better if it was more hands-off.
Describe the solution you'd like
The MSI installers support a few flags to make the installation less interactive. There's a fully silent mode where it shows nothing onscreen, and a passive mode where it only shows a progress bar. Chatting with Fabian in Discord it seems like the "passive" mode might be a good middle ground - an automatic installation, but with some feedback so the user knows what's going on.
Alternatives considered
No response
Additional context
I'd be happy to take a stab at implementing it - just grepping around for msiexec I see it's referenced in core/tauri/src/updater/core.rs and also tauri/tooling/bundler/src/bundle/windows/templates/update-task.xml. I think this would only require changing the /qb+ to /passive in those two spots.

Really good idea, I don't like how agressive the update process is with the installer popping up all the time.


Generate listers and routes when actually needed and don't 'cache' them

This refactors the setListeners method out of the cache. Unless I'm misreading things, it didn't actually do anything useful other than obstructing the code-path regarding when and how often listeners are computed. If I'm not missing something, this shouldn't change anything in behavior.
/assign @jmprusi @davidor

/lgtm

/retest


keybase: 5.9.1 -> 5.9.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/keybase/client/releases.
meta.description for keybase is: "The Keybase official command-line utility and service"
meta.homepage for keybase is: "https://www.keybase.io/"
meta.changelog for keybase is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/h4nsc5x2m8r8jpx0gdl1q7s6yzqg76ra-keybase-5.9.3/bin/keybase had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/h4nsc5x2m8r8jpx0gdl1q7s6yzqg76ra-keybase-5.9.3/bin/kbnm had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 5.9.3 with grep in /nix/store/h4nsc5x2m8r8jpx0gdl1q7s6yzqg76ra-keybase-5.9.3
found 5.9.3 in filename of file in /nix/store/h4nsc5x2m8r8jpx0gdl1q7s6yzqg76ra-keybase-5.9.3

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

4 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
kbfs
keybase

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/h4nsc5x2m8r8jpx0gdl1q7s6yzqg76ra-keybase-5.9.3 \
  --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 keybase https://github.com/r-ryantm/nixpkgs/archive/66172fd25299c12ce9fd6da6bbcb80f58dd95bd7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/h4nsc5x2m8r8jpx0gdl1q7s6yzqg76ra-keybase-5.9.3
ls -la /nix/store/h4nsc5x2m8r8jpx0gdl1q7s6yzqg76ra-keybase-5.9.3/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

2 packages built:

kbfs
keybase

Maintainer pings
cc @avaq @carlsverre @np @rvolosatovs @Br1ght0ne @kf5grd @kalbasit for testing.

@GrahamcOfBorg eval


Request: Make another module for Android

Seems all the difference from making it running is:
LazySodiumJava lazySodium = new LazySodiumJava(new SodiumJava());

which will be replaced to :
LazySodiumAndroid lazySodium = new LazySodiumAndroid(new SodiumAndroid());

Perhaps you could make an interface for its usages, and wrap it from outside.
According to the usage, the interface should have the functions cryptoPwHash, cryptoSecretStreamInitPull, and cryptoSecretStreamPull .
So, there would be a main library module that has nothing that's related to LazySodiumJava and nothing that's related to LazySodiumAndroid. Instead, it would use your own interface LazySodiumInterface (or whatever name you wish, I'm bad with names), and there would be 2 tiny sample modules in the project. One for Java that provides the implementation via LazySodiumJava, and another for Android that provides the implementation via LazySodiumAndroid.
If you want, a working sample on Android is attached here, with minimal change to the UnApkm file:
ApkmTest.zip
If you do this, I suggest to also add annotations of @WorkerThread, @AnyThread, and @UiThread for the functions, based on the thread that it's supposed to run on.  However it's a conscious decision on my part to keep this a simple desktop command line program (with it being possible to easily port to android if necessary) - purely because I feel like I shouldn't be encouraging the use of this format and this is just a tool to convert these into a more standard open format that everyone else uses.
Please feel free to fork it into an android version if you really want to make a new APKMirror Installer app, but one exists already...

It doesn't have to be an APKMirror installer, and even if it will, it can be much better than what we have now.

Can I fork and make a pull request, and then you could just make a new module for PC ?
Sadly I have no idea how to test on PC via Android Studio. I think something is wrong on my Java environment, as I couldn't even make a Hell-world PC app on IntelliJ, no matter how much time and effort I've put into it.
I don't know why it is this way. Back in the Eclipse days, sure it was a bit complex, but I always succeeded making Java PC apps work fine.


syntax error  in source db name using copy to another server

Hi. I would like to copy db from one server to another and I am following this article using T-SQL
CREATE DATABASE db_copy AS COPY OF db.etl-jobs; and  Azure Data Studio and  SQL SMS complains with
"Incorrect syntax near '-'."
How I could copy db with when in name '-'?

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

ID: 9e8abfde-2523-5c70-bb95-b10101a726ff
Version Independent ID: 3b8152d2-b49e-df4b-0f05-3ec52aa5bb71
Content: CREATE DATABASE (Transact-SQL) - SQL Server
Content Source: docs/t-sql/statements/create-database-transact-sql.md
Product: sql
Technology: t-sql
GitHub Login: @CarlRabeler
Microsoft Alias: carlrab

@Rutikhal -- thank you for your question.  Please try enclosing the hyphenated name in [square brackets]:
CREATE DATABASE db_copy AS COPY OF db.[etl-jobs];
I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.

Thanks. Yes, now it works.

@Rutikhal -- you're welcome, and glad we could help.


Odyssey scraper AttributeError: NoneType object has no attribute 'click'

Traceback (most recent call last):
File "odyssey_indexer.py", line 209, in
main(place_id, year)
File "odyssey_indexer.py", line 123, in main
results = site.search(search_terms=batch, case_details=False)
File "/home/stanford/.pyenv/versions/3.7.6/lib/python3.7/site-packages/court_scraper/platforms/odyssey_site/site.py", line 33, in search
portal_page.go_to_smart_search()
File "/home/stanford/.pyenv/versions/3.7.6/lib/python3.7/site-packages/court_scraper/platforms/odyssey_site/pages/portal.py", line 20, in go_to_smart_search
self._click_port_button('smart_search')
File "/home/stanford/.pyenv/versions/3.7.6/lib/python3.7/site-packages/court_scraper/platforms/odyssey_site/pages/portal.py", line 36, in _click_port_button
button.click()
AttributeError: 'NoneType' object has no attribute 'click'

@zstumgoren This error occurred after my indexer script had run through 685 case numbers. I tried to recreate this by just running the case numbers after 685 but the error did not return...


Adding new Management addresses

@pvbchak : Thanks for your contribution! The author, @ccompy, has been notified to review your proposed change.

#sign-off


Sensors config not accepted

I am running the script and get the following output:

python3 app.py
Running with sensors config:
{}
nct6793-isa-0290 at ISA adapter
acpitz-acpi-0 at ACPI interface
coretemp-isa-0000 at ISA adapter
MQTT client connected with code 0
nct6793-isa-0290 at ISA adapter
acpitz-acpi-0 at ACPI interface
coretemp-isa-0000 at ISA adapter

MQTT is connected, I also send a test message. But the sensors config is probably not accepted. I made a file and called it Sensors. I took the sensor name from the output (see above), as I do not know what to use here. It has this content:
{
  "<coretemp-isa-0000>": {
    "features": {
      "<coretemp-isa-0000>": {
        "label": "Test",
        "mqtt": "coretemp-isa-0000"
      }
    }
  }
}

Here is my filestructure:
SensorsReport$ ls -lh
insgesamt 43K
-rw-rw-r-- 1 simon simon 2,5K Apr 16 12:58 app.py
-rw-rw-r-- 1 simon simon  299 Apr 15 09:49 docker-compose.yml
-rw-rw-r-- 1 simon simon  306 Apr 15 09:49 Dockerfile
-rw-rw-r-- 1 simon simon   32 Apr 15 09:49 dotenv.template
-rw-rw-r-- 1 simon simon 1,1K Apr 15 09:49 LICENSE
-rw-rw-r-- 1 simon simon 1,3K Apr 16 12:54 mqtt.py
drwxrwxr-x 2 simon simon    4 Apr 16 12:54 __pycache__
-rw-rw-r-- 1 simon simon  740 Apr 15 09:49 README.md
-rw-rw-r-- 1 simon simon   33 Apr 15 09:49 requirements.txt
-rw-rw-r-- 1 simon simon  159 Apr 16 13:11 SENSORS
-rw-rw-r-- 1 simon simon  135 Apr 15 09:49 util.py

I am just running the python scripts, no container. I adapted the mqtt.config so I do not use env variables, but direclty wrote the configuration in the files.

I made assumptions about understanding of the syntax in my example, which I hopefully fixed in #2.
Please try the following configuration:
{
  "coretemp-isa-0000": {
    "features": {
      "coretemp-isa-0000": {
        "label": "Test",
        "mqtt": "coretemp-isa-0000"
      }
    }
  }
}

Can you please check your "feature" entry? For me, this is temp one and I have written my configuration like this:
{
  "coretemp-isa-0000": {
    "features": {
      "temp1": {
        "label": "CPU Package",
        "mqtt": "CPU/Package"
      }
    }
  }
}

I am just running the python scripts, no container.
For a controlled environment I propose you use the docker image (see additions to README on how to run from the pre-built image) and create a .env file from the dotenv.template.

I adapted the mqtt.config so I do not use env variables, but direclty wrote the configuration in the files.
The application is expecting the sensors configuration in an environment variable. If you want to load from a file, changes to the source code are needed. Naming the file SENSORS will not make it available in the environment.


[3.x] Fix move_and_collide causing sliding on slopes

Make sure the direction of the motion is preserved in move_and_collide, unless the depth is higher than the margin, which means the body needs depenetration in any direction.
Credits to @fabriceci for investigating move and slide issues and helping with extensive testing.
3.x backport of #49901 (see more details there).

Converted to draft because on second thought, this could be too big of a change to be backported to 3.x. Once move_and_slide is more stable on 4.0 we can re-assess this PR and decide how much can be backported without too much risk.

Closing in favor of #50495, which also includes more recent fixes.


[Storage] Fixed bug were BlobBaseClient.Exists() did not function correctly for blobs encrypted with CPK

Resolves https://github.com/Azure/azure-sdk-for-net/issues/20361

LGTM.
There's bunch of changes in the PR that don't seem to be related to the bug. Could you please remove them from PR?

I am unable to.  They are because I re-generated from swagger, which includes version level worm.  Not that basically nothing changed in sdk/storage/Azure.Storage.Blobs/api/Azure.Storage.Blobs.netstandard2.0.cs

LGTM.
There's bunch of changes in the PR that don't seem to be related to the bug. Could you please remove them from PR?

I am unable to. They are because I re-generated from swagger, which includes version level worm. Note that basically nothing changed in sdk/storage/Azure.Storage.Blobs/api/Azure.Storage.Blobs.netstandard2.0.cs

To take new error code I suppose.

LGTM.
There's bunch of changes in the PR that don't seem to be related to the bug. Could you please remove them from PR?

I am unable to. They are because I re-generated from swagger, which includes version level worm. Note that basically nothing changed in sdk/storage/Azure.Storage.Blobs/api/Azure.Storage.Blobs.netstandard2.0.cs

To take new error code I suppose.

Ya I wasn't happy with all the changes when I regenerated, either.  Sorry about that :(


feat: option to hide cross section background in 3D slice views

Summary
This PR introduces a new global setting to optionally hide the background of 3D cross-sections in Neuroglancer. When activated, this setting allows users to view 3D slice projections without the background color, offering a less obstructed view of the data while still keeping the slice views in 3D on. Open to thoughts and suggestions on the functionality and implementation!
Default (background visible):

New Option (background hidden):

Motivation
When displaying slice views in 3D, the background of 2D cross-sections can sometimes appear prominently, especially when the user is zoomed out. This view can be useful but may also limit visibility of the 3D content itself. This feature provides the flexibility to hide the background in 3D, to improve visibility without turning off the section rendering completely. 2D cross-section views remain unaffected.
User interaction
In neuroglancer, this setting is available in the same panel where users toggle 3D view sections. It can also be enabled or disabled with the global "t" keybind (representing "Transparent"), selected to avoid overlap with existing shortcuts. Very open to suggestions on the keybind.
Implementation
The primary change is to the SliceViewRenderHelper class, and specifically the constructor and shader. The shader becomes a context and parameter dependent shader instead of a fixed shader. This allows the shader to change based on whether the user controlled setting is toggled on or off (the parameter to the memoized shader getter), and whether the render helper is for a cross-section view or projection view (the context).
When the hide setting is on, and the rendering is for a projection view, if the alpha of the sampled cross-section texture is 0 in the fragment shader, instead of picking up the background color, the fragment is discarded.
Oblique slicing example
For clarity, here is an example with oblique slicing and a red projection background to illustrate the effects of this new setting.

I put together this example showing how the shader can be additionally modified to make zero values (which in the fib25 dataset always indicate out-of-bounds) transparent, which in combination with this PR leads to a nicer visual effect:
Example
It may be reasonable to just enable this behavior all the time, rather than add an option for it.  I can't really think of a situation where displaying the out-of-bounds background is useful.
As a caveat, though, I will say that in general I find it not to be particularly useful to display the cross sections in the 3d views in actual usage --- mostly I have found the cross section display in the 3d view to be useful for screenshots, videos, and for demonstrating oblique slicing.  Others that actually rely on cross section display in the 3d view for interactive use may have a better idea as to whether this change would be undesirable in some cases.

I've reversed the flag in this PR. So this means the default would be to hide areas of the cross section that are transparent in 3D.
It means that previous neuroglancer links would have this new behaviour to hide transparent pieces of the cross sections in 3D by default, but that the previous behaviour can be restored and saved in the state if desired

Setting back to ready for review after fixing some issues in this PR with the most recent merge of changes from master branch


flag: Unexpected print result from flag.PrintDefaults() with grave accent mark (`).

Using grave accent mark (`) in descriptions to flags produces unexpected flag.PrintDefaults() results. In case of two grave accent marks used all between them are moved next to flag name to the previous row. The desired result is achieved using three grave accent marks in a row. Tested on 1.19 and 1.20.
Example:
desc := fmt.Sprintf("Place `foo` option, or maybe `bar`")
flag.StringVar(new(string), "missing", "something", desc)
desc = fmt.Sprintf("Place ```foo` option, or maybe `bar`")
flag.StringVar(new(string), "workaround", "something", desc)
flag.Parse()
flag.PrintDefaults()
// Result:
// -missing foo
//	Place foo option, or maybe `bar` (default "something")
// -workaround
//	Place `foo` option, or maybe `bar` (default "something")

AFAIK, this behavior is not documented.

AFAIK, this behavior is not documented.

https://pkg.go.dev/flag#PrintDefaults says:

The listed type … can be changed by placing a back-quoted name in the flag's usage string; the first such item in the message is taken to be a parameter name to show in the message and the back quotes are stripped from the message when displayed.

Ah, I didn't quite understood what back-quoted name was, but example makes it clair. I should have been more attentive. Thank you for your time and sorry! Closing issue.


"qemu: uncaught target signal 6 (Aborted) - core dumped" on m1 Mac

Not starting on an m1 Mac (core dump)
compreFace-core is producing following log:
[uWSGI] getting INI configuration from uwsgi.ini

*** Starting uWSGI 2.0.19 (64bit) on [Tue Dec  7 23:07:57 2021] ***

compiled with version: 10.2.1 20210110 on 20 October 2021 09:21:55

os: Linux-5.10.76-linuxkit #1 SMP PREEMPT Mon Nov 8 11:22:26 UTC 2021

nodename: b9d8893ef004

machine: x86_64

clock source: unix

detected number of CPU cores: 4

current working directory: /app/ml

detected binary path: /usr/local/bin/uwsgi

!!! no internal routing support, rebuild with pcre support !!!

setgid() to 33

setuid() to 33

your memory page size is 4096 bytes

detected max file descriptor number: 1048576

lock engine: pthread robust mutexes

!!! it looks like your kernel does not support pthread robust mutexes !!!

!!! falling back to standard pthread mutexes !!!

thunder lock: disabled (you can enable it with --thunder-lock)

uwsgi socket 0 bound to TCP address <IP_ADDRESS>:3000 fd 3

Python version: 3.7.12 (default, Sep 28 2021, 19:53:04)  [GCC 10.2.1 20210110]

Python main interpreter initialized at 0x4000130390

python threads support enabled

your server socket listen backlog is limited to 100 connections

your mercy for graceful operations on workers is 60 seconds

mapped 218712 bytes (213 KB) for 2 cores

*** Operational MODE: preforking ***

2021-12-07 23:08:01.358950: F tensorflow/core/platform/cpu_feature_guard.cc:37] The TensorFlow library was compiled to use AVX instructions, but these aren't available on your machine.

qemu: uncaught target signal 6 (Aborted) - core dumped

Steps to reproduce
(i) On an M1 Mac install Docker Desktop (apple silicon version).
(ii) Install CompreFace 0.6.1 and run it

M1 Mac works on ARM CPU and CompreFace doesn't support it.
As I know it can somehow emulate x86, but we don't have now contributors with M1 Mac to check why it doesn't work.
My guess - CompreFace also requires AVX, which is supported only by x86 CPU, and I don't know if Apple managed to emulate it.


Yandex maps scaling work incorrectly

Hello.
I opened the example of Yandex maps by downloading your repository.
And I noticed that Yandex maps work correctly on Google Chrome browser, but if I change this browser to Mozilla Firefox, Yandex maps work incorrectly. Please solve this issue.

Have you checked #293 ?

Yes I have, but his solution doesn't work. May be for me, I don't know.

Confirming the issue.
Known workaround: set map options zoomAnimation property to false.

@johnd0e your temp solution works, thank you. But is there any solid fix?

Sure. It's merged into master already.

@johnd0e but as you can see below it somehow does not work. I'm using right version I hope.

I'm using right version I hope.

Nope.
Right version is unreleased.
https://rawcdn.githack.com/shramov/leaflet-plugins/efd0a870496fa55fd51904fff781b6d214e09fa6/layer/tile/Yandex.js

I've just released v3.3.1 for that ;)


Dev: add support for configurable model options

This change adds support for configurable model options in the local configured LLM providers available behind cody.dev.models feature.
The CompletionsModelConfig type has been extended to include an options field, which allows users to specify additional settings for the model, such as temperature, max tokens, and whether to use streaming.
The changes have been implemented across the various LLM provider chat clients (Anthropic, GROQ, and Ollama) to handle the new configuration options.
Additionally, the getCompletionsModelConfig utility function has been updated to extract the options field from the model's client-side configuration.
Finally, the ChatModelProviderConfig interface in the VSCode extension has also been updated to include the options field, allowing users to configure these settings in the VSCode extension.
The CompletionsModelConfig and ChatModelProviderConfig interfaces have been updated to include the options field, which i've also made the required changes to existing code that uses these interfaces.
Test plan

This change only affects an internal feature that's hidden behind the 'cody.dev.models' setting.

Confirm ollama models are working
In your user settings,  add the cody.dev.models settings with the new "options" config:

	"cody.dev.models": [
		{
			"provider": "openaicompatible",
			"model": "gpt-4o-mini",
			"apiEndpoint": "https://api.openai.com/v1/chat/completions",
			"apiKey": "YOUR OPENAI API key",
			"options": {
				"stream": false
			}
		},
		{
			"provider": "openaicompatible",
			"model": "gpt-4o-latest",
			"tokens": 30000,
			"apiEndpoint": "https://api.openai.com/v1/chat/completions",
			"apiKey": "YOUR OPENAI API key",
			"options": {
				"stream": true
			}
		},
	],

Changelog

cody.dev.models now supports "options" parameter.

Wait ... this is kinda cool! Awesome change!


Update rebar.config

修改emqttc

change emqttc

Hi @Rokey1990, please submit an PR in emqttc project, Thanks.


Propose to delete Volume snapshots when deleting VM/Volume

Acceptance criteria:

When destroying a VM: add a checkbox "Delete snapshots?" ("Удалить снимки"?) to the dialog "Delete this VM's data drives?".
This checkbox should appear only when data drives have snapshots
When deleting a Volume: add a dialog "Delete this volume's snapshots?" ("Удалить снимки данного диска?") appearing after volume deleting has been approved by user.
This dialog should appear only when a volume has snapshots
Document this feature in "Custom features" local doc

Connected feature ID:

vm_destroy_datadrives_snap
storage_disk_delete_snap

Mockup

test on: http://cs-ui-ci.z1.netpoint-dc.com:8080/ksendart/871-delete-snapshots
to test:
vm_destroy
vm_expunge
storage_disk_delete
storage_disk_delete_snap
storage_snap_display
storage_snap_delete

vm_expunge
Got error for "Failed to detach a volume" when VM was expunged.
Steps:
Login and create new VM
For created VM on sidebar create new Volume to attach
Attach the Volume
Go to VMs and destroy VM, check Expunge

Expected result: disk is deleted
Actual result: error  "Failed to detach a volume"

pending
Count above Zero is shown. Please, see the attach. Appears in many scenarios: vm creation, vm destroying, disk deleting.
Steps:
Login and go to Storage
Create new, attach to VM
Make shap
Delete disk with shapshots
Expand the pending list
Close pending list

Expected result: no count value appears
Actual result: count value is above zero

pending
Snapshot created but throbber is never ending.
Steps:

Login and select any vm
Go to Storage and make 2 snapshots one by one for one disk
See the pending operations

Expected result: snapshot taken in pending
Actual result: never ending throbber appears

If creation snapshot is failed, on pending Failed to delete snapshot appears. Expected: Snapshot failed.
To reproduce  -  Go to Storage and make 2 snapshots one by one for one ROOT disk


WebGL issue on iOS9

I'm getting an issue with a three.dart (WebGL) app when running on iOS9 (Safari). It seems fine on everything else including iOS8.
The error in console is:
[Error] Uncaught Error: Error: receiver.getParameter is not a function. (In 'receiver.getParameter(pname)', 'receiver.getParameter' is undefined)
Stack Trace:
getParameter$1@http://www.autograph-maths.com/webversion-debug/autograph.html_bootstrap.dart.js:68983:37
getParameter$1$x@http://www.autograph-maths.com/webversion-debug/autograph.html_bootstrap.dart.js:108426:55
WebGLRenderer$10$alpha$antialias$canvas$context$depth$logarithmicDepthBuffer$precision$premultipliedAlpha$preserveDrawingBuffer$stencil@http://www.autograph-maths.com/webversion-debug/autograph.html_bootstrap.dart.js:102218:45
....

Also:
Error] Uncaught Error: Error: receiver.getExtension is not a function. (In 'receiver.getExtension($name)', 'receiver.getExtension' is undefined)
Stack Trace:
getExtension$1@http://www.autograph-maths.com/webversion-debug/autograph.html_bootstrap.dart.js:68980:37
getExtension$1$x@http://www.autograph-maths.com/webversion-debug/autograph.html_bootstrap.dart.js:108423:55
$get$1@http://www.autograph-maths.com/webversion-debug/autograph.html_bootstrap.dart.js:98514:43
WebGLRenderer$10$alpha$antialias$canvas$context$depth$logarithmicDepthBuffer$precision$premultipliedAlpha$preserveDrawingBuffer$stencil@http://www.autograph-maths.com/webversion-debug/autograph.html_bootstrap.dart.js:102227:31
....

A bit of debugging shows that receiver which is a WebGLRenderingContext doesn't have either getParameter or getExtension defined. Not sure where the problem lies since it only seems to occur in iOS9.

I think both of those should be there, according to https://www.khronos.org/registry/webgl/specs/latest/1.0/#5.14
There's some mention of a Safari bug with reference WebGLRenderingContext constants, but that doesn't seem like the same thing. If those are actually missing from the underlying JS object I'm not sure what we can do. Can you tell if they're just prefixed, or otherwise available?

After spending most of yesterday trying to debug this issue, I finally found it was related to the inclusion of webcomponents.js. This seems to contain wrappers for the canvas element and the webgl context which are causing issues on iOS9.
  (function(scope) {
    "use strict";
    var HTMLElement = scope.wrappers.HTMLElement;
    var mixin = scope.mixin;
    var registerWrapper = scope.registerWrapper;
    var unsafeUnwrap = scope.unsafeUnwrap;
    var wrap = scope.wrap;
    var OriginalHTMLCanvasElement = window.HTMLCanvasElement;
    function HTMLCanvasElement(node) {
      HTMLElement.call(this, node);
    }
    HTMLCanvasElement.prototype = Object.create(HTMLElement.prototype);
    mixin(HTMLCanvasElement.prototype, {
      getContext: function() {
        var context = unsafeUnwrap(this).getContext.apply(unsafeUnwrap(this), arguments);
        return context && wrap(context);
      }
    });
    registerWrapper(OriginalHTMLCanvasElement, HTMLCanvasElement, document.createElement("canvas"));
    scope.wrappers.HTMLCanvasElement = HTMLCanvasElement;
  })(window.ShadowDOMPolyfill);

For now, I have commented out this code and it seems to solve the issue for me. I don't really know what the purpose of the wrapper is and what consequences it is going to have commenting out the code. At the moment it seems fine.
I have also filed a bug report at: https://github.com/webcomponents/webcomponentsjs/issues/414

OK. There doesn't seem to be anything we should be doing at the Dart library level for that, so closing this. Feel free to re-open if you do see something.


Get the blockchain api working

[ ] Implement integration tests for src/utils/xrpl.test.ts. Integration tests mean that it is calling the actual xrpl blockchain to check if the code is running correctly. Note for now we only have unit test - keep them in separate sections using describe
[ ] Implement Minting integration test
[ ] Fix mintNft function
[ ] Implement a new function to get all our nfts for a users wallet address (could be just storing them in mongo db and retrieving them)
[ ] Research a way to get current users' addresses from UI - if there is an XRPL wallet we can use for that

All done


Fix Glottolog mapping; improve profile; regenerate CLDF

This PR:

Fixes Glottolog mapping by correcting mappings, replacing bookkeeping codes, splitting different languages that were mapped to the same glottocode (many thanks to @MacyL for her help in fixing the Hmong languages that were mapped to the same code!)
Fixes the orthographic profile, with some improvements and now achieving 100% coverage

Pinging @XachaB

Thanks ! So fast I didn't even have time to write an issue :)

The language mapping would benefit from revisions, including less conservative ones (I only touched those that were problematic), no doubt about that.
Nonetheless, considering that this mapping improves the one currently in master, I suppose I can merge it?

@tresoldi ok, go ahead and merge.


Dt fixes for ncs 1.3

I cherry-picked the devicetree changes and fixes that have been applied upstream since the latest mergeup.
DNM for now as I'm still waiting for https://github.com/zephyrproject-rtos/zephyr/pull/25556 to get merged so I can add it here.
Also DNM because this is on top of https://github.com/nrfconnect/sdk-zephyr/pull/302

@carlescufi  this is as discussed offline earlier this week.

All checks passed.
checkpatch (informational only, not a failure)
-:3639: WARNING:LONG_LINE_COMMENT: line over 80 characters
#3639: FILE: include/devicetree/fixed-partitions.h:46:
+ *     DT_NODE_BY_FIXED_PARTITION_LABEL(mcuboot) // node identifier for boot_partition

-:3640: WARNING:LONG_LINE_COMMENT: line over 80 characters
#3640: FILE: include/devicetree/fixed-partitions.h:47:
+ *     DT_NODE_BY_FIXED_PARTITION_LABEL(image_0) // node identifier for slot0_partition

-:4107: WARNING:LONG_LINE_COMMENT: line over 80 characters
#4107: FILE: include/devicetree/pwms.h:181:
+ *     DT_PWMS_CELL_BY_NAME(DT_NODELABEL(n), alpha, flags)   // PWM_POLARITY_NORMAL

-:4108: WARNING:LONG_LINE_COMMENT: line over 80 characters
#4108: FILE: include/devicetree/pwms.h:182:
+ *     DT_PWMS_CELL_BY_NAME(DT_NODELABEL(n), beta, flags)    // PWM_POLARITY_INVERTED

- total: 0 errors, 4 warnings, 4762 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

Your patch has style problems, please review.

NOTE: Ignored message types: AVOID_EXTERNS BRACES CONFIG_EXPERIMENTAL CONST_STRUCT DATE_TIME FILE_PATH_CHANGES MINMAX NETWORKING_BLOCK_COMMENT_STYLE PRINTK_WITHOUT_KERN_LEVEL SPDX_LICENSE_TAG SPLIT_STRING VOLATILE

NOTE: If any of the errors are false positives, please report
      them to the maintainers.

Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages.

Since #302 is blocked on CI and these really ought to go into 1.3, I'm going to push them into that PR.


create a docs folder with detailed info on each pipeline stage

Before 1.0-beta release:
A useful resource would be a centralized folder that contains multiple documents, one for each stage of the pipeline.

preprocess
segmentation
patch
VAE training and encoding
dimensionality reduction

For example, the dim_reduction module has the following usage:
config file
The configuration file now accepts a list of input, output full paths to directories. The file_name_prefixes is a list of string prefixes. The weights_dir is a single directory in which pca_model.pkl is written as a result of PCA fitting (fit_model = True). The conditions is a list of strings describing experimental conditions. This value is only used during plotting after fitting.
details
For fit_model: True:
loops over all directories listed in config's input_dirs
loops over all prefixes in config's file_name_prefixes
[aggregate all data]: searches for _latent_space_after.pkl files in the input dirs and concatenates them in a vector list for subsequent PCA fitting
Fitting will write a model pca_model.pkl to the config's weights_dir directory.
Fitting will write a figure PCA.png to the config's weights_dir directory
finally, will loop over all pairs of input_dirs and output_dirs in the config:
will run inference on all individual latent_space.pkl in input_dir folder, where suffix='after' hardcoded. And where the supplied model is the one generated from step 4 above.
output of each inference is _latent_space_after_PCAed.pkl and saved to each corresponding output_dir from 6
For fit_model: False:
loops over all pairs of directories listed in config's input_dirs / output_dirs
loops over all prefixes in config's file_name_prefixes
assumes the weights_dir supplied in the config is a directory, and looks for the pca_model.pkl file there.
runs inference on latent_space.pkl where suffix=after is hardcoded.
writes the transformed vectors to latent_space_PCAed.pkl in the corresponding output_dir directory


Responsive NavBar

Is your feature request related to a problem? Please describe.
Currently there is no any navbar in react webapp through which user can navigate into webpages.

Describe the solution you'd like
Make a clean and responsive NavBar.

Would like to work under this issue to start my contribution in GSSOC'2020. Kindly assign me this issue.
Thanku!

Please assign me this issue. I would like to work on it.

Can I be assigned to this issue? I am very interested!

I would love to work on this issue ...
Please Assign this to me

I would like to take the issue, can you assign me this?
And also please mention what all things are needed in nav-bar. Thank you!

I would like to work on this issue.. can you please assign it to me.

I would like to contribute to this issue as a part of GSSoC 2020. @jainpawan21

Would like to work under this issue to start my contribution in GSSOC'2020. Kindly assign me this issue.
Thanku!

Thanks for showing interest in this issue. @ayushi0014. I hope you will complete it by 4th march.

@jainpawan21  Can you assign me this issue?

I would like to work on this issue

@jainpawan21 @PragatiVerma18 I would like to take up this issue, can you please assign me?(gssoc20)

I would like to work on this issue too

@jainpawan21 I'll report you with the same by tomorrow evening.

@jainpawan21 @vinitshahdeo I have worked on given issue and have send my progress.

Please give me ahead instructions.

@ayushi0014 LGTM, assigning you this issue. Can you please change options in the navbar:

Home
Implementation
FAQs
Team
Contact

@vinitshahdeo Yes for sure!!

Good job @ayushi0014 :clap:
Please go ahead and make PR.

Is this issue still open @vinitshahdeo ?

Yes @shreyakapoor08 you can make your contribution.

@PragatiVerma18 @vinitshahdeo I would like to work on this issue.

The UI has changed. You can view the UI in here

Yes, but the UI wireframes are ready.


Fix reference when generating with ClusterIP

Fails to generate as the include was not changed to match the other types.

Thx for the PR :)
there was already a pending one #43 with the same fix tho