text:
allow method chaining

Personally, I'd like to chain my settings, so instead of this:

// init SecureHeaders
$headers = new SecureHeaders;

$headers->auto();
$headers->hsts();
$headers->csp([
    'default-src' => [
        'none'
    ],
    'script-src' => [
        'self'
    ],
    'style-src' => [
        'self',
        'https://fonts.googleapis.com'
    ],
    'img-src' => [
        'https://www.gravatar.com'
    ]
]);
$headers->apply();

I could do

// init SecureHeaders
$headers = new SecureHeaders;

$headers
    ->auto()
    ->hsts()
    ->csp([
        'default-src' => [
            'none'
        ],
        'script-src' => [
            'self'
        ],
        'style-src' => [
            'self',
            'https://fonts.googleapis.com'
        ],
        'img-src' => [
            'https://www.gravatar.com'
        ]
    ])
    ->apply();

Would you not find it confusing when using methods that cannot return the current instance?
E.g. https://github.com/aidantwoods/SecureHeaders/wiki/cspNonce

Also just as a btw, no need to call ->auto if you're not passing it any arguments :)
See: https://github.com/aidantwoods/SecureHeaders/wiki/auto

[...] If unconfigured, the default setting is SecureHeaders::AUTO_ALL.

No, I wouldn't as soon as it's clear that this is a getter, so I would call it getCspNonce(...$args) instead.
In fact, I'm that used to it, and my first tries were to do that, and it failed. :/

No, I wouldn't as soon as it's clear that this is a getter, so I would call it getCspNonce(...$args) instead.

Hmm... it's not a "pure" getter though (as-in: it has side effects). It'll generate and insert the nonce into the CSP, then return the nonce so you can use it (or if one was previously generated it'll just return it). I built it like that so you don't have to care whether one already existed right when you need it.
I mention that, because I'm not sure if it would be misleading to prefix it with get since it causes changes? (And it isn't really a getter – just happens to return a value, and sometimes get one).
In general I'm not opposed to method chaining though, just don't want to end up causing confusing by partially adding it 😜 (i.e. is unpredictable usability worse than not having it?)

Well, then I leave the choice up to you, since you are the maintainer. :P
It's good to say no. :D

I think it'll have to be a no for now. I may revisit in future though.

As an aside: just some thoughts on method chaining, having a think about it ;p
There appear to be two design patterns that use it:

Where you deliberately act on very different objects returned in a "flow" like way, e.g.$boo = $App->getConfig()->getId('Foo\Bar\Baz')->getValue();

For configuration, saving typing the original object multiple times$FooBar
    ->loadConfig($Config)
    ->loadExtensions($Extensions)
    ->run();

For the former, it relies on you knowing what is returned, and makes a nice way of using what was returned easily.
For the latter, the actual method itself returning the instance seems a bit useless as actual information (unless dealing with immutable objects – where it in-fact returns a new instance. But that's really just the former case – since the method was designed with returning something in mind anyway).
So I wonder whether for the latter case, it would almost be better to implement that kind of method chaining as a language feature (instead of doing it via a return statement that doesn't have anything to do with the method's role).
E.g. an &> operator, like -> but meaning something like "call foo and bar on this object".
So instead of the author of the object implementing support for you to do this (on methods that would otherwise have no reason to return anything). Or you could even use it on things that do return things (if you don't care about what's returned).
I.e. write this (knowing that it would work: because language feature).
$Baz
  &>foo()
  &>bar();

Practically, I guess it could act to call the method like -> would do, but ignore any return statement and pass on the object on the LHS. That way it would be clear when you're acting on the same object from a readers point of view too.
E.g. it would allow you to write:
$headers
    &>hsts()
    &>csp([
        'default-src' => [
            'none'
        ],
        'script-src' => [
            'self'
        ],
        'style-src' => [
            'self',
            'https://fonts.googleapis.com'
        ],
        'img-src' => [
            'https://www.gravatar.com'
        ]
    ])
    &>apply();

without the underlying library actually changing any code.
Let me know if that doesn't sound too insane – could perhaps send a message round on PHP internals to see if an RFC for something like this would be worth doing.

Okay. I'm fine with this, even though I'd like to be able to chain methods. :)

Interesting discussion here. 😄
I wish I would have seen this a bit earlier. To be honest, I think it's not the best style to have this method behave the way it does. The mix of setting and getting stuff might seem comfortable, but is hard to predict (the side effect determined by another flag on the class makes matters even worse).
Can you provide an example where the consumer of this library would not be aware of having added a nonce already, and would thus need protection from doing so? IMO, that is something consumers should have to take care of on their own.
Since the SecureHeaders class is mostly about configuration now, having it return itself (or even a new instance, thus becoming immutable) on these setter methods would be very nice.

I can definely agree with it not being terribly nice :p
Perhaps this should be split into seperate methods to generate + add, and then subsequently get the nonce?

@jens1o

Please write an RFC, that's a pretty good idea and it really cleans up the code!

I did send something round on internals, appears to have been missed/not replied to anyway – though feel free to reply to try get some discussion going 😉
https://externals.io/message/100007
PHP rules say I can ask for RFC writing permissions if feedback is not negative, pretty sure no feedback meets that criteria, right? ;p

Hmm, is it just me or can't the public reply to it?

Link is to a read only mirror of the mailing list (not really another good way to show it). I can probably forward you the original email, I think you'd need to subscribe to reply to the internals list though – not personally a fan of the whole mailing list setup for any discussion :p

authors: aidantwoods franzliedke jens1o

repo: aidantwoods/SecureHeaders


text:
obsidian端会导致metadata里的别名跑到正文里。

已经排查所有插件和主题，只有装了obsidian-bridge会出来这样的情况。不知道它和什么插件冲突还是其他什么的原因就不知道了。关闭bridge就不会出现别名乱跑的现象。

具体怎么操作的可以录个屏吗，我看看能不能复现

没有怎么操作呀，只要装了bridge后，凡是装之前有别名的文档都会出现别名跑下面来的情况。装了之后才增加别名的，重启后也会别名跑下面去。

确实会出现这样的情况，打开 Marginnoge companion 插件后输入一级标题，别名会在它下面再次出现，当关闭插件后不会出现这种情况。

source: gharchive/issue

authors: Miaoyifei-mz aidenlx xfxme

repo: aidenlx/marginnote-companion

license: MIT

license_type: permissive

license_source: github-api


text:
bug: React.memo works incorrectly

Describe the bug
Hey. I'm trying to test the compatibility layer with react. I came across a bug when using the memo function. This function is not properly passing props. I think the point is that memo function is implemented by passing props through Object.values(props) which produces an array instead of an object. As a result, the memoizable component receives an array of arguments as input, instead of a single props argument.
To Reproduce
Wrap any component in memo and pass some props to it.
Expected behavior
Props must be passed as a single argument.

fixed in v2

authors: aidenybai atellmer

repo: aidenybai/million


text:
Update Genetic Algorithm implementation in AIMA4e

Currently, GeneticAlgorithm.java does not follow the pseudo code of 4th edition.
@samagra14  I would like to work on this issue. May I proceed?

Hi @jsuyash1514 The code in pseudocode is of an older version of genetic algo. Things keep changing in the fourth edition. I will update the pseudocode soon. After that you may proceed.

Okay, @samagra14.
Should I close #452 for now?

repo: aimacode/aima-java

license: mit

license_source: bigquery


text:
pipelines with numbers

#The following script makes pipelines with numbers sometimes.
from golem.core.optimisers.genetic.operators.mutation import Mutation
from golem.core.optimisers.genetic.gp_params import GPAlgorithmParameters
from golem.core.optimisers.optimization_parameters import GraphRequirements
from golem.core.optimisers.optimizer import GraphGenerationParams, AlgorithmParameters
gr = GraphRequirements()
gap = GPAlgorithmParameters()
ggp = GraphGenerationParams()
m = Mutation(parameters = gap,    requirements= gr,  graph_generation_params = ggp)
#model - a fitted ts-forecasting model
#take some individual
ind = model.history.individuals[-2][0]
#mutation
x = m._mutation(ind)
x

Думаю, что проблема в том, что в примере используются сущности из голема, а надо из федота. Например, как в этом (https://github.com/aimclub/FEDOT/blob/master/test/unit/optimizer/gp_operators/test_mutation.py#L41) тесте

Спасибо, теперь все работает)

repo: aimclub/FEDOT


text:
State has no primary constructor , App crashing

Hi, I am facing the "State has no primary constructor" crash issue on Release Build. and we initialized all state properly but crashing for some user.  i am using mvrx 1.2.1
Fatal Exception: java.lang.RuntimeException: Unable to start activity ComponentInfo{MainActivity}: java.lang.IllegalStateException: HomeScreenActivityState has no primary constructor!        at android.app.ActivityThread.performLaunchActivity + 2447(ActivityThread.java:2447)        at android.app.ActivityThread.handleLaunchActivity + 2509(ActivityThread.java:2509)        at android.app.ActivityThread.access$900 + 175(ActivityThread.java:175)        at android.app.ActivityThread$H.handleMessage + 1382(ActivityThread.java:1382)        at android.os.Handler.dispatchMessage + 102(Handler.java:102)        at android.os.Looper.loop + 135(Looper.java:135)        at android.app.ActivityThread.main + 5425(ActivityThread.java:5425)        at java.lang.reflect.Method.invoke(Method.java)        at java.lang.reflect.Method.invoke + 372(Method.java:372)        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run + 928(ZygoteInit.java:928)        at com.android.internal.os.ZygoteInit.main + 723(ZygoteInit.java:723)

The cause of this issue seems to be this line in PersistState.kt
KClass.primaryConstructor property does not work well with proguard. I faced this issue in my own library as well, but was able to work around it by doing: klass.constructors.first(). Not sure if this is the best solution though.

Hi, something new about the solution?

Is there any update about this issue?
I'm facing exactly the same problem, occur in version mvrx 1.3.0 also

authors: Sroobik balrampandey19 haroldadmin herisulistiyanto

repo: airbnb/MvRx


text:
remove value tuple's key to reduce shuffle size

The value tuple of reduceByKey has part (x._1._1) which is same to the key of reduceByKey. Thus, that part can be removed to reduce shuffle size.

Good catch, thanks for the optimization

source: gharchive/pull-request

authors: CanoeFZH hectorgon

repo: airbnb/aerosolve


text:
REST API client

Hello
Is it possible to use a REST API as a source for the widget?
Thank you

What kind of REST service are you envisioning? The "Queryable" interface we use for Druid and SqlAlchemy sources is fairly complex and the service would have to implement it.

Do you know what a GUI is?
On Apr 3, 2016 8:44 AM, "hugo-pires" notifications@github.com wrote:

Hello
Is it possible to use a REST API as a source for the widget?
Thank you
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/airbnb/caravel/issues/245

I guess so. Could it help to answer my question?

So the answer is: it's possible and you'd have to implement the Queryable interface in models.py, it's not trivial though.

authors: hugo-pires mistercrunch tiffyangel89

repo: airbnb/caravel


text:
Missing ability to have multiple info pannels

react-dates@21.8.2
In my use case, I need to have both a left pannel, and a bottom pannel in Pickers.
The problem is there is only one prop renderCalendarInfo for rendering, and another prop calendarInfoPosition to choose where to display the component.
I would need to have more rendering props, eg:

renderCalendarTopInfo
renderCalendarBeforeInfo
renderCalendarAfterInfo
renderCalendarInfoBottom

Another (more generic) way of solving this would be to have kind of renderPicker prop that would allow the developper to render the picker's component inside a container.
This would allow full rendering control, with this kind of usage :
<DateRangePicker
  {...props}
  renderPicker={({ picker }) => {
    return (
      <>
        <myLeftPannel />
        <div>
          <myTopPanel />
          {picker}
          <myBottomPanel />
        </div>
        <myRightPannel />
      </>
    );
  }}
/>

repo: airbnb/react-dates


text:
Hover on a day on Firefox doesn't add classes to the day

When I hover on the calendar on firefox nothing happens. After debugging a little bit, I think there is a bug in the isTouchDevice function.
ontouchstart is defined in firefox, but it has a null value.

Since the onDayMouseEnter and onDayMouseLeave will return if this.isTouchDevice, the hover logic doesn't get applied on Firefox.

Which version of Firefox is this happening in? In my v53, it's undefined.

v53.0.2 (64-bit) in macOS sierra

I just realized what the problem was. Somehow I had the dom.w3c_touch_events.enabled property set to 1 in the browser. I didn't remember enabling it. I'm sorry about having created the issue.


text:
Keyboard Accessibility

This PR is currently somewhat of a mess. I need to decide whether or not I'm happy with this structure (also this will break the SDP right now), but this code adds basic keyboard accessibility to react-dates.

[ ] Fix issue where you navigate from April 2017 to May 2017 with keyboard with outside days enabled
[X] second param in onNextMonthClick/onPrevMonthClick???
[x] Update SingleDatePicker
[ ] if a CalendarDay has been blurred in the DOM, (ie going to the prev month/next month buttons) but the month transition doesn't trigger a different focusedDate... then the day doesn't get updates and therefore doesn't get refocused. :/

Coverage decreased (-10.5%) to 76.349% when pulling ee36ce84dda0476cb06ee7814347ed83d8350dd7 on maja-a11y-work into 04d08d4e32c458e4c86d2eb353a2cccd84c7a1ce on master.

Hi @backwardok @wyattdanger @ljharb @lencioni! I still need to write tests, but I'd love to get some feedback before I do. Would y'all be able to take a look at this PR? I am pushing real hard to get it in this week.
This is the MVP. I think there will likely be some polish work that still needs to be done.

@airbnb/webinfra @backwardok @ljharb I split out some of the work and broke up the PR into two commits (one for the breaking name change and one for all the a11y work). Would appreciate another set of eyes.
Once again, I still have to write tests! but that is incoming.

is the DayPickerRangeController supposed to work with keyboard in the storybook?

Looks like the Keyboard Shortcuts view could use some love in vertical orientation

@majapw I love this PR!!
Can I ask a slightly unrelated question?   What were you using to test the accessibility?  What is the black box showing the text?

@sontek Thanks! Hopefully this should land soon (I'm waiting on help from a copy person here at Airbnb).
That black box is voiceover on OSX. It's the default voiceover app. :)

Coverage decreased (-11.4%) to 71.875% when pulling a8e86c849af1936cfb430bf5ccbc94b6464fd67c on maja-a11y-work into 5ba9930b74d91bd9560e450574bfaea02cf5fda0 on master.

Coverage increased (+0.6%) to 83.912% when pulling 769f0497917d2e7452af55964aea658c051a319c on maja-a11y-work into 5ba9930b74d91bd9560e450574bfaea02cf5fda0 on master.

Coverage increased (+0.7%) to 84.023% when pulling 1ffcac04ae4516dd5eb05d7f9f4865b2dae77fc4 on maja-a11y-work into 5ba9930b74d91bd9560e450574bfaea02cf5fda0 on master.

Coverage increased (+0.8%) to 84.041% when pulling b000e3fb56978f07a5c2915e1eecd9927444c05d on maja-a11y-work into 5ba9930b74d91bd9560e450574bfaea02cf5fda0 on master.

Coverage increased (+0.8%) to 84.114% when pulling 9f56e07e25f723e416ac51f7ccd2382542d6dc73 on maja-a11y-work into 5ba9930b74d91bd9560e450574bfaea02cf5fda0 on master.

Coverage increased (+0.8%) to 84.114% when pulling 9f56e07e25f723e416ac51f7ccd2382542d6dc73 on maja-a11y-work into 5ba9930b74d91bd9560e450574bfaea02cf5fda0 on master.

Coverage increased (+0.4%) to 83.705% when pulling a5d7bbbdd911d77e4fd48f61d27dd93a44ed870c on maja-a11y-work into 5ba9930b74d91bd9560e450574bfaea02cf5fda0 on master.

Coverage increased (+0.4%) to 83.705% when pulling a5d7bbbdd911d77e4fd48f61d27dd93a44ed870c on maja-a11y-work into 5ba9930b74d91bd9560e450574bfaea02cf5fda0 on master.

Hey @airbnb/webinfra, this PR is ready to go! Please take a look and give me your feedback!

Coverage increased (+0.5%) to 83.742% when pulling 780522ef29abd1788cfb6e3a65517ac134c5ac91 on maja-a11y-work into 5ba9930b74d91bd9560e450574bfaea02cf5fda0 on master.

authors: coveralls majapw sontek wyattdanger


text:
Remove v4 reference

Removing deprecated v4 reference.

Merged in https://github.com/airbrake/airbrake-docs/pull/87

repo: airbrake/airbrake-docs


text:
Can not use multiply gpus for bottom-up feature extraction

Hi, Thanks for authors great doker environment for bu feature extraction.
However, I find it cannot use the multiply GPUs by using CUDA_VISIBLE_DEVICES=0,1,2,3 in docker？
And I check the extract.py file, it seemed that it does not support the multiply gpu extracting?
Or am I missing anything?
Thanks~

Currently, the original CAFFE implementation (originated from Ross's py-faster-rcnn repo) could not do batch-wise inference. Because they kept the width-height ratio during inference.
A possible solution is to use detectron2/mmdetection as the backbone extractor. These libraries add the support of batch-wise inference.  However, I do find that D2's batch-wise mode would decrease the score of downstream tasks because the features and RoI's are not perfectly aligned.

Hi, Thanks for authors great doker environment for bu feature extraction.
However, I find it cannot use the multiply GPUs by using CUDA_VISIBLE_DEVICES=0,1,2,3 in docker？
And I check the extract.py file, it seemed that it does not support the multiply gpu extracting?
Or am I missing anything?
Thanks~

Hi @Wangt-CN, can you share me /workspace/features/extract_nlvr2_image.py? I follow this issue#79.

Hi, Thanks for authors great doker environment for bu feature extraction.
However, I find it cannot use the multiply GPUs by using CUDA_VISIBLE_DEVICES=0,1,2,3 in docker？
And I check the extract.py file, it seemed that it does not support the multiply gpu extracting?
Or am I missing anything?
Thanks~

Hi @Wangt-CN, can you share me /workspace/features/extract_nlvr2_image.py? I follow this issue#79.

Hi, Thanks for authors great doker environment for bu feature extraction.
However, I find it cannot use the multiply GPUs by using CUDA_VISIBLE_DEVICES=0,1,2,3 in docker？
And I check the extract.py file, it seemed that it does not support the multiply gpu extracting?
Or am I missing anything?
Thanks~

Hi @Wangt-CN ，I am also interested in installing Detectron (used by VisualBERT) or Detectron2.

Hi, Thanks for authors great doker environment for bu feature extraction.
However, I find it cannot use the multiply GPUs by using CUDA_VISIBLE_DEVICES=0,1,2,3 in docker？
And I check the extract.py file, it seemed that it does not support the multiply gpu extracting?
Or am I missing anything?
Thanks~

Hi @Wangt-CN ，I am also interested in installing Detectron (used by VisualBERT) or Detectron2.

Currently, the original CAFFE implementation (originated from Ross's py-faster-rcnn repo) could not do batch-wise inference. Because they kept the width-height ratio during inference.
A possible solution is to use detectron2/mmdetection as the backbone extractor. These libraries add the support of batch-wise inference. However, I do find that D2's batch-wise mode would decrease the score of downstream tasks because the features and RoI's are not perfectly aligned.

Hi @airsplay thanks! Seems results of these feature extraction tools are comparable and consequentially, other  feature extraction tools.
By the way, Any method no need of caffe/caffe2? although I personally can install caffe under this case of LXMERT.

Currently, the original CAFFE implementation (originated from Ross's py-faster-rcnn repo) could not do batch-wise inference. Because they kept the width-height ratio during inference.
A possible solution is to use detectron2/mmdetection as the backbone extractor. These libraries add the support of batch-wise inference. However, I do find that D2's batch-wise mode would decrease the score of downstream tasks because the features and RoI's are not perfectly aligned.

Hi @airsplay thanks! Seems results of these feature extraction tools are comparable and consequentially, other  feature extraction tools.
By the way, Any method no need of caffe/caffe2? although I personally can install caffe under this case of LXMERT.

Please refer to here. Thanks.

Please refer to here. Thanks.

Currently, the original CAFFE implementation (originated from Ross's py-faster-rcnn repo) could not do batch-wise inference. Because they kept the width-height ratio during inference.
A possible solution is to use detectron2/mmdetection as the backbone extractor. These libraries add the support of batch-wise inference. However, I do find that D2's batch-wise mode would decrease the score of downstream tasks because the features and RoI's are not perfectly aligned.

Also interested in batch-wise inference and extract_features.py is also doing inference for each image. I follow issue#7 in airsplay/py-bottom-up-attention as well.

Currently, the original CAFFE implementation (originated from Ross's py-faster-rcnn repo) could not do batch-wise inference. Because they kept the width-height ratio during inference.
A possible solution is to use detectron2/mmdetection as the backbone extractor. These libraries add the support of batch-wise inference. However, I do find that D2's batch-wise mode would decrease the score of downstream tasks because the features and RoI's are not perfectly aligned.

Also interested in batch-wise inference and extract_features.py is also doing inference for each image. I follow issue#7 in airsplay/py-bottom-up-attention as well.

authors: Wangt-CN airsplay yezhengli-Mr9

repo: airsplay/lxmert


text:
⚠ Turnos 24x7 has degraded performance

In 6b6153c, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 890 ms

Resolved: Turnos 24x7 performance has improved in b0b9d0f.

repo: aisa-status/status-upptime-dev


text:
When the wallet is not connected should give a clear messsage

done

repo: aisland-dao/docsig


text:
BUG: mkinstallp no longer gives correct sizes: Upsize template line

Looking at the archive - from before github days it appears a start was made to update the way the template-line "Upsize" was created.
It looks as if makebff.pl is still doing something - but not what is really needed.
Needs fixing! (So, now I'll look at how I would submit my own PR!)

Hmm. Open issue, but I had already done a branch and merged it.
Must check if it is already fixed.

repo: aixtools/buildaix


text:
Can the rolling.Apply support multidimensional?

Now rolling.apply can roll window at one-dimensional,will be able to support multidimensional in the future?Like that:

I find it will be finish in that "https://gist.github.com/seberg/3866040".

Hi @thouger, thanks for the link. My intention is that this library will only support 1D rolling windows, unlike the NumPy example. This is for a couple of reasons:

I want to be able to support arbitrary iterators (like generators), not just fixed-length containers such as arrays. Adding support for higher dimensions is possible in theory, but very difficult to get right in practice (NumPy's implementation is very impressive).
My focus for this library is on implementing computationally efficient algorithms over rolling windows and it's not clear to me how some algorithms could be extended to higher dimensions (operations over windows generated using as_strided are not efficient as values must be iterated over multiple times to perform the reduction on the window).

Hi @ajcr ,thanks for you answer,The reason that i want to add is because the "rolling" package is very overall package about 1D in pip.Because it can print the iterators result and it's a feature that numpy doesn't have(numpy only provide the result such as max,min when rolling window),so if the rolling package can print n-dimensional result when rolling window that will be even excellent.
I will continue to explore the rolling window n-dimensional method.

Thanks @thouger: I'll give your suggestion some more thought. It might be possible to find a solution.

authors: ajcr thouger

repo: ajcr/rolling


text:
Unable to build and run the examples

Also tried with flink 1.4.2

How did you try to build the project?
With a simple $ mvn clean install the project is built properly. Please ensure you have a proper maven installation.
And about to run the examples, you need to have a sample Mqtt Broker to run them, but with the samples and running this you should be able to run a sample program.
$ java -cp target/flink-connector-mqtt-0.1.jar com.iniesta.flink.connector.mqtt.MqttWordCount2Mqtt
USAGE:
MqttWordCount2Mqtt <hostname> <topic IN> <topic OUT>

Please feel free to modify and  customize for your needs.

Hi,
Maven 3.5.2 on Windows. With "mvn clean install" I'm getting:
C:\flink-connector-mqtt>mvn clean install
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Flink Connector for mqtt 0.1
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for org.apache.flink:flink-java:jar:1.3.2 is invalid, transitive dependencies (if any) will not be available, enable debug logging f
or more details
[WARNING] The POM for org.apache.flink:flink-streaming-java_2.10:jar:1.3.2 is invalid, transitive dependencies (if any) will not be available, enable
debug logging for more details
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ flink-connector-mqtt ---
[INFO] Deleting C:\flink-connector-mqtt\target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ flink-connector-mqtt ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ flink-connector-mqtt ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 10 source files to C:\flink-connector-mqtt\target\classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /C:/flink-connector-mqtt/src/main/java/com/iniesta/flink/connector/mqtt/MqttSink.java:[3,38] package org.apache.flink.configuration does not e
xist
[ERROR] /C:/flink-connector-mqtt/src/main/java/com/iniesta/flink/connector/mqtt/MqttSink.java:[9,8] cannot access org.apache.flink.api.common.function
s.Function
class file for org.apache.flink.api.common.functions.Function not found
[INFO] 2 errors
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.986 s
[INFO] Finished at: 2018-05-21T11:30:22+03:00
[INFO] Final Memory: 14M/46M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project flink-connector-mqtt: Compilati
on failure: Compilation failure:
[ERROR] /C:/flink-connector-mqtt/src/main/java/com/iniesta/flink/connector/mqtt/MqttSink.java:[3,38] package org.apache.flink.configuration does not e
xist
[ERROR] /C:/flink-connector-mqtt/src/main/java/com/iniesta/flink/connector/mqtt/MqttSink.java:[9,8] cannot access org.apache.flink.api.common.function
s.Function
[ERROR]   class file for org.apache.flink.api.common.functions.Function not found
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

authors: IshayLevy ajiniesta

repo: ajiniesta/flink-connector-mqtt


text:
🛑 NEW ZEALAND is down

In b86ca62, NEW ZEALAND (https://www.bricks4kidz.co.nz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NEW ZEALAND is back up in 00595aa.


text:
[Snyk] Upgrade @angular-devkit/build-angular from 0.1102.18 to 17.3.7

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade @angular-devkit/build-angular from 0.1102.18 to 17.3.7.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

⚠ Warning: This PR contains major version upgrade(s), and may be a breaking change.

The recommended version is 317 versions ahead of your current version.

The recommended version was released on 25 days ago.

Issues fixed by the recommended upgrade:

Issue
Score
Exploit Maturity

Regular Expression Denial of Service (ReDoS)SNYK-JS-TERSER-2806366
45
No Known Exploit

Incomplete List of Disallowed InputsSNYK-JS-BABELTRAVERSE-5962462
45
Proof of Concept

Uncontrolled resource consumptionSNYK-JS-BRACES-6838727
45
Proof of Concept

Uncontrolled resource consumptionSNYK-JS-BRACES-6838727
45
Proof of Concept

Improper Verification of Cryptographic SignatureSNYK-JS-BROWSERIFYSIGN-6037026
45
No Known Exploit

Inefficient Regular Expression ComplexitySNYK-JS-MICROMATCH-6838728
45
No Known Exploit

Improper Verification of Cryptographic SignatureSNYK-JS-NODEFORGE-2430339
45
No Known Exploit

Prototype PollutionSNYK-JS-UNSETVALUE-2400660
45
No Known Exploit

Path TraversalSNYK-JS-WEBPACKDEVMIDDLEWARE-6476555
45
Proof of Concept

Prototype PollutionSNYK-JS-LOADERUTILS-3043105
45
No Known Exploit

Inefficient Regular Expression ComplexitySNYK-JS-MICROMATCH-6838728
45
No Known Exploit

Open RedirectSNYK-JS-EXPRESS-6474509
45
No Known Exploit

Improper Input ValidationSNYK-JS-POSTCSS-5926692
45
No Known Exploit

Improper Input ValidationSNYK-JS-POSTCSS-5926692
45
No Known Exploit

Improper Input ValidationSNYK-JS-POSTCSS-5926692
45
No Known Exploit

Regular Expression Denial of Service (ReDoS)SNYK-JS-GLOBPARENT-1016905
45
Proof of Concept

Open RedirectSNYK-JS-NODEFORGE-2330875
45
Proof of Concept

Prototype PollutionSNYK-JS-NODEFORGE-2331908
45
No Known Exploit

Improper Verification of Cryptographic SignatureSNYK-JS-NODEFORGE-2430337
45
No Known Exploit

Improper Verification of Cryptographic SignatureSNYK-JS-NODEFORGE-2430341
45
No Known Exploit

Regular Expression Denial of Service (ReDoS)SNYK-JS-LOADERUTILS-3042992
45
No Known Exploit

Regular Expression Denial of Service (ReDoS)SNYK-JS-LOADERUTILS-3105943
45
No Known Exploit

Cross-site Scripting (XSS)SNYK-JS-SERIALIZEJAVASCRIPT-6147607
45
Proof of Concept

Cross-site Scripting (XSS)SNYK-JS-SERIALIZEJAVASCRIPT-6147607
45
Proof of Concept

Release notes

Package name: @angular-devkit/build-angular

17.3.7 - 2024-05-08
17.3.7 (2024-05-08)
@ angular-devkit/build-angular

Commit
Description

decode URL pathname decoding during SSG fetch

@ angular-devkit/schematics

Commit
Description

use web standard error check for Deno support

17.3.6 - 2024-04-25

17.3.5 - 2024-04-17

17.3.4 - 2024-04-11

17.3.3 - 2024-04-02

17.3.2 - 2024-03-25

17.3.1 - 2024-03-20

17.3.0 - 2024-03-13

17.3.0-rc.0 - 2024-03-06

17.2.3 - 2024-03-06

17.2.2 - 2024-02-28

17.2.1 - 2024-02-22

17.2.0 - 2024-02-14

17.2.0-rc.0 - 2024-02-08

17.2.0-next.1 - 2024-01-31

17.2.0-next.0 - 2024-01-25

17.1.4 - 2024-02-14

17.1.3 - 2024-02-08

17.1.2 - 2024-01-31

17.1.1 - 2024-01-24

17.1.0 - 2024-01-18

17.1.0-rc.1 - 2024-01-10

17.1.0-rc.0 - 2024-01-03

17.1.0-next.3 - 2023-12-22

17.1.0-next.2 - 2023-12-13

17.1.0-next.1 - 2023-12-06

17.1.0-next.0 - 2023-11-29

17.0.10 - 2024-01-10

17.0.9 - 2024-01-03

17.0.8 - 2023-12-21

17.0.7 - 2023-12-13

17.0.6 - 2023-12-06

17.0.5 - 2023-11-29

17.0.4 - 2023-11-29

17.0.3 - 2023-11-21

17.0.2 - 2023-11-20

17.0.1 - 2023-11-15

17.0.0 - 2023-11-08

17.0.0-rc.5 - 2023-11-07

17.0.0-rc.4 - 2023-11-07

17.0.0-rc.3 - 2023-11-01

17.0.0-rc.2 - 2023-10-26

17.0.0-rc.1 - 2023-10-25

17.0.0-rc.0 - 2023-10-19

17.0.0-next.9 - 2023-10-12

17.0.0-next.8 - 2023-10-11

17.0.0-next.7 - 2023-10-04

17.0.0-next.6 - 2023-09-27

17.0.0-next.5 - 2023-09-20

17.0.0-next.4 - 2023-09-13

17.0.0-next.3 - 2023-09-07

17.0.0-next.0 - 2023-08-30

16.2.14 - 2024-04-11

16.2.13 - 2024-03-25

16.2.12 - 2024-01-24

16.2.11 - 2023-12-21

16.2.10 - 2023-11-08

16.2.9 - 2023-11-01

16.2.8 - 2023-10-25

16.2.7 - 2023-10-19

16.2.6 - 2023-10-11

16.2.5 - 2023-10-04

16.2.4 - 2023-09-27

16.2.3 - 2023-09-20

16.2.2 - 2023-09-13

16.2.1 - 2023-08-30

16.2.0 - 2023-08-09

16.2.0-rc.1 - 2023-08-04

16.2.0-rc.0 - 2023-08-02

16.2.0-next.4 - 2023-07-26

16.2.0-next.3 - 2023-07-20

16.2.0-next.2 - 2023-07-13

16.2.0-next.1 - 2023-07-06

16.2.0-next.0 - 2023-06-28

16.1.8 - 2023-08-04

16.1.7 - 2023-08-02

16.1.6 - 2023-07-26

16.1.5 - 2023-07-20

16.1.4 - 2023-07-06

16.1.3 - 2023-06-29

16.1.2 - 2023-06-28

16.1.1 - 2023-06-22

16.1.0 - 2023-06-13

16.1.0-rc.0 - 2023-06-07

16.1.0-next.2 - 2023-06-01

16.1.0-next.1 - 2023-05-25

16.1.0-next.0 - 2023-05-17

16.0.6 - 2023-06-13

16.0.5 - 2023-06-07

16.0.4 - 2023-06-01

16.0.3 - 2023-05-25

16.0.2 - 2023-05-17

16.0.1 - 2023-05-10

16.0.0 - 2023-05-03

16.0.0-rc.4 - 2023-04-28

16.0.0-rc.3 - 2023-04-27

16.0.0-rc.2 - 2023-04-27

16.0.0-rc.1 - 2023-04-19

16.0.0-rc.0 - 2023-04-12

16.0.0-next.7 - 2023-04-06

16.0.0-next.6 - 2023-03-30

16.0.0-next.5 - 2023-03-22

16.0.0-next.4 - 2023-03-15

16.0.0-next.3 - 2023-03-09

16.0.0-next.2 - 2023-03-01

16.0.0-next.1 - 2023-02-23

16.0.0-next.0 - 2023-02-22

15.2.11 - 2024-03-25

15.2.10 - 2023-10-05

15.2.9 - 2023-06-28

15.2.8 - 2023-05-03

15.2.7 - 2023-04-26

15.2.6 - 2023-04-12

15.2.5 - 2023-04-05

15.2.4 - 2023-03-16

15.2.3 - 2023-03-15

15.2.2 - 2023-03-08

15.2.1 - 2023-03-01

15.2.0 - 2023-02-22

15.2.0-rc.0 - 2023-02-15

15.2.0-next.4 - 2023-02-08

15.2.0-next.3 - 2023-02-02

15.2.0-next.2 - 2023-01-25

15.2.0-next.1 - 2023-01-18

15.2.0-next.0 - 2023-01-12

15.1.6 - 2023-02-15

15.1.5 - 2023-02-08

15.1.4 - 2023-02-01

15.1.3 - 2023-01-25

15.1.2 - 2023-01-18

15.1.1 - 2023-01-12

15.1.0 - 2023-01-11

15.1.0-rc.0 - 2023-01-06

15.1.0-next.3 - 2022-12-15

15.1.0-next.2 - 2022-12-08

15.1.0-next.1 - 2022-11-30

15.1.0-next.0 - 2022-11-23

15.0.5 - 2023-01-06

15.0.4 - 2022-12-14

15.0.3 - 2022-12-07

15.0.2 - 2022-11-30

15.0.1 - 2022-11-23

15.0.0 - 2022-11-16

15.0.0-rc.5 - 2022-11-15

15.0.0-rc.4 - 2022-11-15

15.0.0-rc.3 - 2022-11-09

15.0.0-rc.2 - 2022-11-02

15.0.0-rc.1 - 2022-10-26

15.0.0-rc.0 - 2022-10-20

15.0.0-next.6 - 2022-10-14

15.0.0-next.5 - 2022-10-12

15.0.0-next.4 - 2022-10-06

15.0.0-next.3 - 2022-09-28

15.0.0-next.2 - 2022-09-21

15.0.0-next.1 - 2022-09-15

15.0.0-next.0 - 2022-09-08

14.2.13 - 2023-10-05

14.2.12 - 2023-06-28

14.2.11 - 2023-03-16

14.2.10 - 2022-11-17

14.2.9 - 2022-11-09

14.2.8 - 2022-11-02

14.2.7 - 2022-10-26

14.2.6 - 2022-10-12

14.2.5 - 2022-10-05

14.2.4 - 2022-09-28

14.2.3 - 2022-09-15

14.2.2 - 2022-09-08

14.2.1 - 2022-08-26

14.2.0 - 2022-08-25

14.2.0-rc.0 - 2022-08-17

14.2.0-next.2 - 2022-08-17

14.2.0-next.1 - 2022-08-11

14.2.0-next.0 - 2022-08-03

14.1.3 - 2022-08-17

14.1.2 - 2022-08-10

14.1.1 - 2022-08-03

14.1.0 - 2022-07-20

14.1.0-rc.3 - 2022-07-14

14.1.0-next.4 - 2022-07-06

14.1.0-next.3 - 2022-06-29

14.1.0-next.2 - 2022-06-23

14.1.0-next.1 - 2022-06-15

14.1.0-next.0 - 2022-06-09

14.0.7 - 2022-07-20

14.0.6 - 2022-07-13

14.0.5 - 2022-07-06

14.0.4 - 2022-06-29

14.0.3 - 2022-06-23

14.0.2 - 2022-06-15

14.0.1 - 2022-06-08

14.0.0 - 2022-06-02

14.0.0-rc.3 - 2022-05-31

14.0.0-rc.2 - 2022-05-25

14.0.0-rc.1 - 2022-05-18

14.0.0-rc.0 - 2022-05-11

14.0.0-next.13 - 2022-05-04

14.0.0-next.12 - 2022-04-27

14.0.0-next.11 - 2022-04-21

14.0.0-next.10 - 2022-04-21

14.0.0-next.9 - 2022-04-13

14.0.0-next.8 - 2022-04-06

14.0.0-next.7 - 2022-03-30

14.0.0-next.6 - 2022-03-16

14.0.0-next.5 - 2022-03-09

14.0.0-next.4 - 2022-03-03

14.0.0-next.3 - 2022-02-23

14.0.0-next.2 - 2022-02-18

14.0.0-next.1 - 2022-02-09

14.0.0-next.0 - 2022-02-02

13.3.11 - 2023-03-16

13.3.10 - 2022-11-17

13.3.9 - 2022-07-20

13.3.8 - 2022-06-15

13.3.7 - 2022-05-25

13.3.6 - 2022-05-18

13.3.5 - 2022-05-04

13.3.4 - 2022-04-27

13.3.3 - 2022-04-13

13.3.2 - 2022-04-06

13.3.1 - 2022-03-30

13.3.0 - 2022-03-16

13.2.6 - 2022-03-09

13.2.5 - 2022-02-23

13.2.4 - 2022-02-17

13.2.3 - 2022-02-09

13.2.2 - 2022-02-02

13.2.1 - 2022-01-31

13.2.0 - 2022-01-26

13.2.0-rc.1 - 2022-01-25

13.2.0-rc.0 - 2022-01-19

13.2.0-next.2 - 2022-01-12

13.2.0-next.1 - 2021-12-15

13.2.0-next.0 - 2021-12-09

13.1.4 - 2022-01-19

13.1.3 - 2022-01-12

13.1.2 - 2021-12-15

13.1.1 - 2021-12-10

13.1.0 - 2021-12-09

13.1.0-rc.0 - 2021-12-09

13.1.0-next.3 - 2021-12-02

13.1.0-next.2 - 2021-11-18

13.1.0-next.1 - 2021-11-11

13.1.0-next.0 - 2021-11-03

13.0.4 - 2021-12-01

13.0.3 - 2021-11-18

13.0.2 - 2021-11-11

13.0.1 - 2021-11-04

13.0.0 - 2021-11-03

13.0.0-rc.3 - 2021-11-02

13.0.0-rc.2 - 2021-10-27

13.0.0-rc.1 - 2021-10-21

13.0.0-rc.0 - 2021-10-14

13.0.0-next.9 - 2021-10-07

13.0.0-next.8 - 2021-10-05

13.0.0-next.7 - 2021-09-30

13.0.0-next.6 - 2021-09-22

13.0.0-next.5 - 2021-09-15

13.0.0-next.4 - 2021-09-08

13.0.0-next.3 - 2021-09-01

13.0.0-next.2 - 2021-08-26

13.0.0-next.1 - 2021-08-18

13.0.0-next.0 - 2021-08-11

12.2.18 - 2022-07-21

12.2.17 - 2022-03-31

12.2.16 - 2022-01-31

12.2.15 - 2022-01-12

12.2.14 - 2021-12-07

12.2.13 - 2021-11-03

12.2.12 - 2021-10-27

12.2.11 - 2021-10-20

12.2.10 - 2021-10-13

12.2.9 - 2021-10-07

12.2.8 - 2021-10-01

12.2.7 - 2021-09-23

12.2.6 - 2021-09-15

12.2.5 - 2021-09-08

12.2.4 - 2021-09-01

12.2.3 - 2021-08-26

12.2.2 - 2021-08-18

12.2.1 - 2021-08-11

12.2.0 - 2021-08-04

12.2.0-rc.0 - 2021-07-28

12.2.0-next.3 - 2021-07-21

12.2.0-next.2 - 2021-07-14

12.2.0-next.0 - 2021-06-25

12.1.4 - 2021-07-28

12.1.3 - 2021-07-21

12.1.2 - 2021-07-14

12.1.1 - 2021-07-01

12.1.0 - 2021-06-25

12.1.0-next.6 - 2021-06-17

12.1.0-next.5 - 2021-06-10

12.1.0-next.4 - 2021-06-02

12.1.0-next.3 - 2021-05-26

12.1.0-next.2 - 2021-05-19

12.0.5 - 2021-06-17

12.0.4 - 2021-06-10

12.0.3 - 2021-06-02

12.0.2 - 2021-05-26

12.0.1 - 2021-05-19

12.0.0 - 2021-05-12

12.0.0-rc.3 - 2021-05-11

12.0.0-rc.2 - 2021-05-06

12.0.0-rc.1 - 2021-04-28

12.0.0-rc.0 - 2021-04-21

12.0.0-next.9 - 2021-04-14

0.1200.0-next.8 - 2021-04-07

0.1200.0-next.7 - 2021-04-02

0.1200.0-next.6 - 2021-03-24

0.1200.0-next.5 - 2021-03-18

0.1200.0-next.4 - 2021-03-10

0.1200.0-next.3 - 2021-03-03

0.1200.0-next.2 - 2021-02-24

0.1200.0-next.1 - 2021-02-17

0.1200.0-next.0 - 2021-02-11

0.1102.19 - 2022-03-31

0.1102.18 - 2022-01-13

    from @angular-devkit/build-angular GitHub release notes

[!IMPORTANT]

Warning: This PR contains a major version upgrade, and may be a breaking change.
Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.
Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

🎉 Snyk hasn't found any issues so far.
✅ security/snyk check is completed. No issues were found. (View Details)

repo: akanchhaS/github-juice-shop-js


text:
Bundles don't work anymore in Meteor 1.8.2

When using nathantreid:static-assets, Meteor behaves fine in the development mode using meteor run.
During rollout into production a bundle is generated using meteor build direct from the repository clone. Opening the new application in the browser will throw a JavaScript error Uncaught Error: Cannot find module '…'
When generating the bundle a second time without modification of any of the files, it works. No JavaScript errors are shown in the browser.
See https://github.com/qnipp/meteor-double-build-bug to reproduce the bug.
The bug was observed on Linux, using Meteor 1.8.1 and Node version 8.15.1 (which is the corresponding Node version for this Meteor version).
On 1.8.2 and 1.9-beta.3, even a second build does not help, the error remains.
The bug is reported to Meteor as well: https://github.com/meteor/meteor/issues/10780

Using static assets from NPM packages works well with symbolic links, as explained in https://guide.meteor.com/using-npm-packages.html#npm-assets
Therefore, I've changed my application to do it as explained in the guide and removed this package.


text:
Prerequisite Steps:
1. Make sure your provider has community provider attributes and your contact details (email, website):
  Example:
  $ provider-services query provider get akash1<REDACTED> -o text
  ...
  attributes:
  ...
  - key: host
  value: akash
  - key: tier
  value: community
  info:
    email: "<your email>"
    website: "<your website>"

Ref documentation:.
2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)
host <anything>.ingress.<yourdomain>

Example:
$ host anything.ingress.akash.pro
anything.ingress.akash.pro is an alias for nodes.akash.pro.
nodes.akash.pro has address 65.108.6.185

More info on what DNS records should look like are available in the Akash Documentation here.

3. Please make sure your Akash provider doesn't block any Akash specific ports.

If you are using a firewall, please follow this doc:
https://akash.network/docs/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/#step-11---firewall-rule-review
If you are behind NAT, then you need to make sure these ports are open between your provider worker nodes and the internet.

Audit Steps:
1. Title the issue: " [Provider Audit]: Provider Address" (e.g. "[Provider Audit]: provider.europlots.com")
2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed.
3. If there are issues during the provider Audit, debug those issues, and Audit will be complete.
4. Audit Issue will be closed by core team member.
Leave contact information (optional)

Tyler Wellener
Discord: twell1
Contact email address: tyler@wellener.xyz

Hi @twellener,
Your provider has misconfigured attributes.
Current Attributes:
provider-services query provider get akash14f4jr40pvtvsa57u3arf3kexyrk87df5c72g3d -o text
attributes:

key: organization
value: GPU Base

key: arch
value: amd64

key: capabilities/gpu/vendor/nvidia/model/4090
value: "true"

key: capabilities/gpu/vendor/nvidia/model/rtx4090/interface/pcie
value: "true"

key: capabilities/gpu/vendor/nvidia/model/rtx4090/ram/24Gi/interface/pcie
value: "true"

key: capabilities/gpu/vendor/nvidia/model/rtx4090
value: "true"

key: capabilities/gpu/vendor/nvidia/model/rtx4090/ram.24Gi
value: "true"

key: Discord
value: twell1

key: Website
value: gpubase.xyz
host_uri: https://provider.gpubase.xyz:8443
info:
email: ""
website: ""
owner: akash14f4jr40pvtvsa57u3arf3kexyrk87df5c72g3d

key: capabilities/gpu/vendor/nvidia/model/rtx4090/ram.24Gi
value: "true"

This is a typo, the last dot should really be a /
Like this:

key: capabilities/gpu/vendor/nvidia/model/rtx4090/ram/24Gi
value: "true"

Second, the provider has missing attributes:

key: tier
value: community
key: host
value: akash

And third issue is that the provider is not responding on port 8444 / GRPC:
grpcurl -insecure provider.gpubase.xyz:8444 akash.provider.v1.ProviderRPC.GetStatus
Failed to dial target host "provider.gpubase.xyz:8444": context deadline exceeded
Please fix those issues and we can continue,
thank you!

Thanks @shimpa1. I've updated the misconfigured attributes. Please let me know if there's any other issues

@twellener
The contact information should be in the info section. Having a key value pair for that is optional.
As soon as this is updated, the provider will be ready to be signed.

Just updated this on the following page: https://console.akash.network/providers/akash14f4jr40pvtvsa57u3arf3kexyrk87df5c72g3d?network=mainnet
Thanks for your help

@twellener
there are now double attributes for website and email.
Please remove the ones in capital.
If your provider has persistent storage enabled then you also need this key:

key: feat-persistent-storage
value: true

If your provider does not have persistent storage enable then please remove attribute:

key: capabilities/storage/2/class
value: beta2

thank you,

Please do the following:
Log into the provider and edit the file ~/.praetor/provider.yaml
Add the lines:
email:           # set your email here
website:         # set your website (if you have)
Then do helm upgrade --install akash-provider akash/provider -n akash-services -f provider.yaml
This should do the update, I've tested it.
Once done please let me know.
thank you,

Hey @shimpa1 - thanks again for your help on this. Just updated the file and upgraded!

@andy108369 Provider akash14f4jr40pvtvsa57u3arf3kexyrk87df5c72g3d ready to be signed.

Signed!
https://www.mintscan.io/akash/txs/87732F97B3042B924B24D669F4D9CEEBD08CB414FBE41E88A9DE3D093B5ED1A2

repo: akash-network/community


text:
モデルファイルにバージョン番号を埋める？

META.json みたいなファイルをおいて、フォーマットバージョンをかいておくようにするみたいな。

{
  format_version: "1",
  version: "v0.4.0",
},

みたいな感じを想定。

repo: akaza-im/akaza


text:
Issue when trying to MAKE SETUP

When I try to 'make setup' it says :
ld: building for iOS Simulator, but linking in .tbd built for macOS/Mac Catalyst, file '/Library/Developer/CommandLineTools/SDKs/iPhoneSimulator.sdk/System/Library/Frameworks//Foundation.framework/Foundation.tbd' for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [build] Error 1
make: *** [all] Error 2

Please install Xcode.

I already have installed Xcode and the Command Lines + SDKs

What is the output of xcode-select -p on your machine?

/Library/Developer/CommandLineTools

sudo xcode-select -s /Applications/Xcode.app

authors: PoomSmart ltran-inc

repo: akemin-dayo/simject


text:
Glob characters cannot be escaped

Python's fnmatch and glob don't allow escaping glob characters with a backslash.
This is by design for Python (even if it's a weird design), but I don't think it's what most people expect from dpath, even if they see the reference to fnmatch:
>>> d = {'a': 23, '*': 42}
>>> dpath.util.get(d, '*')
ValueError: dpath.util.get() globs must match only one leaf : *
>>> dpath.util.search(d, '*')
{'a': 1, '*': 2}
>>> dpath.util.get(d, r'\*')
KeyError: '\\*'
>>> dpath.util.search(d, r'\*')
{}
>>> dpath.util.get(d, '[*]') # is anyone going to guess this?
42
>>> dpath.util.search(d, '[*]')
{'*': 42}

I've run into a similar issue in the past with many projects that want "globbing like the glob module but with backslash escapes". The simplest solution (but make sure to verify compatible licensing) is to fork fnmatch into your own code, and change this part of the translate function:
    if c == '*':

… to this:
    if c == '\\' and i < n:
        res = res + re.escape(pat[i])
        i = i+1
    elif c == '*':

However, that may not be all you need here.
I'm guessing (given the KeyError) that you have some code that checks for a wildcard and uses fnmatch if found but does a direct lookup if not. If so, your wildcard test has to change to understand backslashes (re.search on (?<!\\)[*?[]) and your direct-lookup has to manually unescape the same characters (re.sub on a similar pattern but that also handles ] and \\). Although once you're getting into manually unescaping, you may want to consider what you want to do with a backslash before any other character—leave it as a backslash, unicode-unescape it, raise an exception, …

Fixing this could also make it easy to provide an alternate fix for #30 by allowing users to backslash-escape the path separator character.

Another point: While glob characters can be escaped fnmatch-style by putting them inside a glob class, trying that for separators gives you something completely wrong and basically undebuggable:
>>> d = {'a': {'b': 1}, 'a/b': 2, 'a[/]b': 3}
>>> dpath.util.get(d, 'a[/]b')
KeyError: 'a[/]b'

Also, I'm not sure what happens if you put [**] in a pattern—that should do the same thing as [*], and match a single literal *, but I wouldn't be surprised if your existing code treated it as a recursive glob.

Your summary of the behavior of fnmatch/glob and our current use of it is correct. We haven't heard many users requesting the ability to escape glob characters, so we're not able to prioritize this currently.
For the 1.0 interface, check out the dpath.path module, the 'match' method. If you want to perform some amount of escaping on globs, this is where it would happen. I'd be happy to review a PR to that end.

Use [*][*] to escape **.

This can be fixed by using lists as paths instead of strings

Separator got you down? Use lists as paths
The default behavior in dpath is to assume that the path given is a string, which must be tokenized by splitting at the separator to yield a distinct set of path components against which dictionary keys can be individually glob tested. However, this presents a problem when you want to use paths that have a separator in their name; the tokenizer cannot properly understand what you mean by '/a/b/c' if it is possible for '/' to exist as a valid character in a key name.
To get around this, you can sidestep the whole "filesystem path" style, and abandon the separator entirely, by using lists as paths. All of the methods in dpath.util.* support the use of a list instead of a string as a path.

authors: abarnert akesterson calebcase

repo: akesterson/dpath-python


text:
Upstream ci is broken

I think this does it

oh whoops thanks!

authors: Dirbaio jacobrosenthal

repo: akiles/nrf-softdevice


text:
[QUESTION] Git-Plus doesn't work after update

I recently was using Git-Plus with no issues on a macOS Sierra 10.12.6. After I updated my git-plus to version 8.1.0 on Atom 1.28.2, git-plus does not work any more neither through the command palette or via keybindings. Now, I have to result to using the terminal in order to use Git which is not convenient. Please, help!

Same for me, but it typically is only on pushes.

I do have always pull before push set.
I keep getting error on
pull before push
fatal: Couldn't find remote ref origin
fatal: the remote end hung up unexpectedly
However running pull and push in terminal works fine.

Ok, I just turned off always pull with push and it started working again.
Then turned it back on and I get the error again.
So maybe my issue with something to do with pull with push.  I will create a separate issue.

authors: ggedde vikeinstein

repo: akonwi/git-plus


text:
Top tab bar still showing up, side tab bar not collapsing

Hey
Really nice work. .I am using Ubuntu 18.04 and I followed through all the steps and ended up with something like this. Along with the problems mentioned in the title(tried all the solutions provided by you), the UI doesn't quite look like yours
Also. I would like to know which dark mode theme you use in your setup.
Sorry for any silly questions, new to firefox.

Was able to fix this behaviour. It was my bad. Now the icons in the sidebar sticking to the left side .

What did you do to fix this issue?

@UnchartedSystems Looks like deepak used userChrome-static instead of userChrome-hover at first. Adding userChrome-hover correctly should fix it.


text:
fix donate.html dark theme

i also added linkedin icon at the bottom

Related Issue
Closes: #1356
Description
i added linkedin logo at the bottom. i also fixed the dark theme for donate.html + there was a text not visible in light mode. tweaked that!
Screenshots

Checklist

[x] My code adheres to the established style guidelines of the project.
[x] I have included comments in areas that may be difficult to understand.
[x] My changes have not introduced any new warnings.
[x] I have conducted a self-review of my code.

fetch and merge to resolve conflicts

please fetch and merge to resolve conflicts

#1789
i've submitted another pull request maam. kindly check


text:
clarify prop types

Make docs more explicit that backButtonImage and drawerImage are sources instead of strings.

@johnstonmatt Are you up to rebase on master?

@charpeni I gave it a try, does that look right?

Unfortunately, rebase wasn't right. I fixed it on your fork.
Here some documentation on Syncing a fork.
Thank you for your PR, it's greatly appreciated!

authors: charpeni johnstonmatt

repo: aksonov/react-native-router-flux


text:
fix(promotions): multiple stages can sync same argocd app

In the case that two stages are trying to sync the same ArgoCD app (such as an app of apps), there was an infinite cycle of the stages overwriting the kargo.akuity.io/freight-collection value in the ArgoCD operation state info.
In my case, this is an ArgoCD promotion mechanism with no source updates (just refreshing an app with gitops updates).
Promotions were never able to complete this way since they were always being requeued.
These changes explicitly prevent this infinite loop by adding stage metadata to the freight collection key.

@shmargum thanks for the PR.
I just wanted to respond that it might be a little bit before we get to looking at this. The issue isn't quite as simple as it may seem on the surface.
I think this may work for your use case, but in cases where the Argo CD App updates are actually mutating something or cases where the health checks on a Stage involve asserting that the App is synced to some specific, desired revision, I think this is going to not work.
In general, the notion of multiple Stages updating the same App is not something we anticipated, and tbh, I have my doubts that it's a generally advisable pattern. Stages are, roughly speaking, "environments" and it seems, at the very least, odd that two or more distinct environments would be managed by a single App.
At any rate, I'm not by any means dismissing this PR out of hand. As I said, I just wanted to respond sooner than later and let you know that this is going to require some careful thought on our part before we can commit to taking this.

Just want to give some more context about why I am doing this in the first place.
I'd like to keep all my state in git, and so ArgoCD source updates are out of the question.
This leaves umbrella helm chart as a documented approach for gitops style updates with noted drawbacks in #1610
We've taken another approach, where we publish helm charts as OCI artifacts, and use the image promotion process to promote the helm chart "image" as a value in git, which configure child apps.
This means that we are also doing 2 ArgoCD updates, first one for the parent app, then a refresh of the child app.
Currently, the parent app holds all the children apps for a service (environments).
I suppose I could work around this further by adding an intermediate level of parent app.  I think a similar approach would be needed for umbrella charts as well.

I'd like to keep all my state in git, and so ArgoCD source updates are out of the question.

Yep. That's ideal. Source updates are not real GitOps.

Currently, the parent app holds all the children apps for a service (environments).

If you're doing App of Apps, why is Kargo ever having to sync the parent app? I would imagine that the Apps managed by the parent App are fairly static in that their definitions must rarely change. Why doesn't each Stage just sync relevant children?
To be transparent, I don't completely understand the approach you've described, but the notions of multiple Stages all syncing the same App or any Stage syncing a parent in App of Apps still feels vaguely suspect.

Ok. I understand better what you are doing now. Thanks for explaining. 😄

The parent app which deploys the child apps sets the "target revision" of the child apps.

That is, for sure, a novel approach to mutating the target revisions whilst still being real GitOps.
What I am, perhaps, not understanding is why use that somewhat complex approach to begin with? Would not all your state still be in your repositories if the child apps all tracked the head of various branches and Kargo managed what's at the head of each branch?

In order to achieve both 2 and 3 we need the base helm chart and environment specific values to be independent (we can't bundle those with the base chart or else they would go through the promotion process)

I think you're going to love the upcoming release. We've been building toward doing things exactly like this without so much hassle. In a previous release, we added the possibility of Stages subscribing to Freight from multiple Warehouses. In v0.9.0, we're adding far more flexibility to the promotion processes. It's a bit reminiscent of GitHub Actions.
For your scenario, what you'll be able to do at each Stage is consume multiple pieces of Freight (i.e. artifacts not bundles together in one box) and describe much more explicitly how you would like to combine those artifacts.

I'm going to close this as I think we've established (through occurrences besides this one, as well) that multiple Stages attempting to manage a single Argo CD App is asking for trouble.
@shmargum, v0.9.0 has been released now, and I am hopeful that all its new flexibility makes workflows possible for you that won't require you to attempt managing one Application using multiple Stages.

While I still think it is a common pattern to have apps that manage other apps, I also agree that Kargo trying to manage a single app with multiple stages sounds like trouble.
I've actually just went ahead and created a separate parent app per actual app.
This does nearly double the number of ArgoCD Application objects, but hey, things work :)

@shmargum I will continue thinking about how to make this use case work.
I'm in complete agreement that it makes sense.

authors: krancour shmargum

repo: akuity/kargo


text:
无法登录: Unknown error occurred

⚠'tzlocal() does not support non-zoneinfo timezones like %s. \nPlease use a timezone in the form of Continent/City'
日志:

此错误来自自定义集成。

Logger: aiohttp.server
Source: custom_components/xiaomi_miot/config_flow.py:141
Integration: Xiaomi Miot Auto (documentation, issues)
First occurred: 11:34:56 (8 occurrences)
Last logged: 11:35:00

Error handling request
Traceback (most recent call last):
  File "/config/custom_components/xiaomi_miot/config_flow.py", line 110, in check_xiaomi_account
    mic = await MiotCloud.from_token(hass, user_input, login=False)
  File "/config/custom_components/xiaomi_miot/core/xiaomi_cloud.py", line 456, in from_token
    mic = MiotCloud(
  File "/config/custom_components/xiaomi_miot/core/xiaomi_cloud.py", line 33, in __init__
    super().__init__(username, password)
  File "/usr/local/lib/python3.9/site-packages/micloud/micloud.py", line 38, in __init__
    timezone = datetime.datetime.now(tzlocal.get_localzone()).strftime('%z')
  File "/usr/local/lib/python3.9/site-packages/tzlocal/unix.py", line 203, in get_localzone
    _cache_tz = _get_localzone()
  File "/usr/local/lib/python3.9/site-packages/tzlocal/unix.py", line 161, in _get_localzone
    tzenv = utils._tz_from_env()
  File "/usr/local/lib/python3.9/site-packages/tzlocal/utils.py", line 125, in _tz_from_env
    raise ZoneInfoNotFoundError(
tzlocal.utils.ZoneInfoNotFoundError: 'tzlocal() does not support non-zoneinfo timezones like %s. \nPlease use a timezone in the form of Continent/City'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 79, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 220, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 137, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 205, in post
    return await super().post(request, flow_id)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 62, in wrapper
    result = await method(view, request, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 109, in post
    result = await self._flow_mgr.async_configure(flow_id, data)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 260, in async_configure
    result = await self._async_handle_step(
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 335, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
  File "/config/custom_components/xiaomi_miot/config_flow.py", line 296, in async_step_cloud
    await check_xiaomi_account(self.hass, user_input, errors, renew_devices=True)
  File "/config/custom_components/xiaomi_miot/config_flow.py", line 141, in check_xiaomi_account
    _LOGGER.error('Setup xiaomi cloud for user: %s failed: %s', mic.username, exc)
AttributeError: 'NoneType' object has no attribute 'username'

https://github.com/al-one/hass-xiaomi-miot/issues/500#timezone

登录失败/没有实体等常见问题解决办法 #500 (comment)

THX!!!

authors: TPAXcc al-one

repo: al-one/hass-xiaomi-miot


text:
Help - how to properly use actions, zones and coordinates [ijai.vacuum.v10]

Hello! I'm not sure this is the correct place, but I've been trying to create zones and send my vacuum there to clean, and so far I wasn't successful.
This is my model: ijai.vacuum.v10 - https://home.miot-spec.com/spec?type=urn:miot-spec-v2:device:vacuum:0000A006:ijai-v10:1
This is the script I'm running. From my understanding, my model requires a zone to be set before I ask it to go there to clean it.
alias: "Vacuum: Clean Mapped Zone"
sequence:
  - service: xiaomi_miot.call_action
    data:
      entity_id: vacuum.ijai_v10_0930_robot_cleaner
      siid: 9
      aiid: 8
      throw: true
      params: x1, y1, x2, y2, x3, y3, x4, y4
  - service: xiaomi_miot.call_action
    data:
      entity_id: vacuum.ijai_v10_0930_robot_cleaner
      siid: 9
      aiid: 3
      throw: true
  - service: xiaomi_miot.call_action
    data:
      entity_id: vacuum.ijai_v10_0930_robot_cleaner
      siid: 10
      aiid: 12
      params:
        - param1?
        - param2?
      throw: true
mode: single

I have a few questions:

Is this the correct way to send my robot to clean, let's say, a zone with params x1, y1, x2, y2, x3, y3, x4, y4?

How do I determine x1, y1, x2, y2, x3, y3, x4, y4 zone? I tried using the Map Extractor plugin, but my model is not supported, so I'm using an image on lovelace-xiaomi-vacuum-map-card.

After you make the fist service call (siid 9, aiid 8), how does the API should respond? Mine usually respond with:

{'code': 0, 'out': [{'piid': 7, 'value': 1}, {'piid': 8, 'value': 0}, {'piid': 9, 'value': 0}]}

I imagine 1, 0 and 0 are the map-id, map-type and timestamp. But I don't know if 1, 0 and 0 means it's not working.

In the last service, what params should go there?

Here's my vevs logs:
530369328.txt
Thank you so much in advance!

I didn't find any "siid":9 in your logs, make sure you performed a zone cleanup in MiHome by vevs.

  function setArea(area) {
    var va = area.points[0].x + "," + area.points[0].y + ","
           + area.points[1].x + "," + area.points[1].y + ","
           + area.points[2].x + "," + area.points[2].y + ","
           + area.points[3].x + "," + area.points[3].y;
    var ssid = _SCNetEnum.default.NetServer.S9pointZone;
    var aiid = _SCNetEnum.default.S9PointZoneAction.S9A8_setArea;

    var values = [va];

    var params = _encapDo(ssid, aiid, values);
    var matches = /function\s*(\w*)/i.exec(arguments.callee.toString());
    _WLLog.default.log(_WLDateUtils.default.nowText() + " req:", matches[1], params);

    return new Promise(function (accept, reject) {
      _doCommon(params, matches[1], 1).then(function (res) {
        var model = _SCDevice.SCDevice.mapModel.getNewMapTimeStampResult(res);
        if (model == null) {
          reject(model);
        } else {
          _SCDevice.SCDevice.mapModel.refreshArea(area);
          _updateNewestMapStamp(model);
          accept(model);
        }
      }).catch(function (error) {
        reject(error);
      });
    });
  }

  function startAreaClean() {
    var ssid = _SCNetEnum.default.NetServer.S9pointZone;
    var aiid = _SCNetEnum.default.S9PointZoneAction.S9A3_startZoneClean;
    var params = _encapDo(ssid, aiid);
    var matches = /function\s*(\w*)/i.exec(arguments.callee.toString());
    _WLLog.default.log(_WLDateUtils.default.nowText() + " req:", matches[1], params);

    return new Promise(function (accept, reject) {
      _doCommon(params, matches[1], 1).then(function (model) {
        if (model.result) {
          clearFaultCodeBeforeMove();
        }
        accept(model);
      }).catch(function (error) {
        reject(error);
      });
    });
  }

Try:
alias: "Vacuum: Clean Mapped Zone"
mode: single
sequence:
  - service: xiaomi_miot.call_action
    data:
      entity_id: vacuum.ijai_v10_0930_robot_cleaner
      siid: 9
      aiid: 8
      params:
        - x1,y1,x2,y2,x3,y3,x4,y4
  - service: xiaomi_miot.call_action
    data:
      entity_id: vacuum.ijai_v10_0930_robot_cleaner
      siid: 9
      aiid: 3

Thanks for the reply! My MiHome app by vevs does not have a way to send my vacuum to clean a specific zone/room. Just to clean everything. I was hoping I could use the zone cleaning with HA, since the MiHome app does not support zones/rooms for my model.

I just tried the new script you suggested - I still get {'code': 0, 'out': []} as a response and nothing happens. I'm imagining it's because I don't know what params I should send.
Also, how am I supposed to use the JS script you sent? I see you're sending the area as a param.

These JS codes come from the plug-in source code of the device in MiHome, and I only use it as a reference to create the service yaml.
ijai.vacuum.v10.js

Besides checking veva logs for siid: 9, is there anything else O could try to check or create new zones?

It can also be found from the JS code, but it seems to have no effect.

authors: al-one paulakfleck


text:
Error in Evaluation mode when using .npy files

--- Logging error ---
Traceback (most recent call last):
File "/bask/projects/v/vjgo8416-ms-img-pc/marji/affinity-vae/run.py", line 664, in run
run_pipeline(data)
File "/bask/projects/v/vjgo8416-ms-img-pc/marji/affinity-vae/run.py", line 714, in run_pipeline
evaluate(
File "/bask/projects/v/vjgo8416-ms-img-pc/marji/affinity-vae/avae/evaluate.py", line 212, in evaluate
meta_df["image"] = meta_df["image"].apply(vis.merge)
File "/bask/homes/h/hdjd5168/vjgo8416-ms-img-pc/marji/env_merge_codebase/lib/python3.10/site-packages/pandas/core/series.py", line 4771, in apply
return SeriesApply(self, func, convert_dtype, args, kwargs).apply()
File "/bask/homes/h/hdjd5168/vjgo8416-ms-img-pc/marji/env_merge_codebase/lib/python3.10/site-packages/pandas/core/apply.py", line 1123, in apply
return self.apply_standard()
File "/bask/homes/h/hdjd5168/vjgo8416-ms-img-pc/marji/env_merge_codebase/lib/python3.10/site-packages/pandas/core/apply.py", line 1174, in apply_standard
mapped = lib.map_infer(
File "pandas/_libs/lib.pyx", line 2924, in pandas._libs.lib.map_infer
File "/bask/projects/v/vjgo8416-ms-img-pc/marji/affinity-vae/avae/vis.py", line 134, in merge
i = im.split("&")
AttributeError: 'NoneType' object has no attribute 'split'

can we separate the restart feature and evaluation feature from the dynamic plots?

Should be fixed in #208

authors: crangelsmith marjanfamili

repo: alan-turing-institute/affinity-vae


text:
Colab badge

Recently came across this project via https://x.com/tom_r_andersson/status/1849069927463809339. Thanks for creating this!
I've added a colab badge at the top of the README which links to https://colab.research.google.com/drive/1q1n7RGxEQJ_6z1DpBSg9FKF9bVQF-GRV?usp=sharing to make the demo more discoverable

Hey, thanks! This is a hacky colab I just threw together to demonstrate the upgraded forecasting features. Am a bit concerned about this detracting from the README quick start, the docs notebooks, and the DeepSensor Gallery. I wonder if there is a good middle ground, where the colab just runs the README quick start (rather than being something different and confusing), or if we link to the forecasting demo colab in the docs somewhere.

authors: raybellwaves tom-andersson

repo: alan-turing-institute/deepsensor


text:
Added meta-tuning example to docstring of ForecastingGridSearchCV

What does this implement/fix? Explain your changes.
Added meta-tuning example to docstring

yes, I made a smaller fh and I forgot the (...) in the output placeholder

repo: alan-turing-institute/sktime


text:
Change Language

So, I need the buttons (cancel and save) translated to ES or pt-BR. There's already any props or config to achieve that? Thank's for the attention.

I did change the locale, but nothing is working.

This is my code:   Future openDatePicker(BuildContext context) async {
if (!disabled) {
DateTime? picked = await showOmniDateTimePicker(
context: context,
initialDate: controller.value,
is24HourMode: true,
isShowSeconds: false,
minutesInterval: 1,
secondsInterval: 1,
borderRadius: const BorderRadius.all(Radius.circular(16)),
constraints: const BoxConstraints(
maxWidth: 350,
maxHeight: 650,
),
transitionBuilder: (context, anim1, anim2, child) {
return FadeTransition(
opacity: anim1.drive(
Tween(
begin: 0,
end: 1,
),
),
child: child,
);
},
transitionDuration: const Duration(milliseconds: 200),
barrierDismissible: true,
selectableDayPredicate: (dateTime) {
// Disable 25th Feb 2023
if (dateTime == DateTime(2023, 2, 25)) {
return false;
} else {
return true;
}
},
);
if (picked != null && picked != controller.value) {
controller.value = picked;
controller.update();
}
}
}

and this is my component code:
  Future<void> openDatePicker(BuildContext context) async {     if (!disabled) {       DateTime? picked = await showOmniDateTimePicker(                     context: context,                     initialDate: controller.value,                     is24HourMode: true,                     isShowSeconds: false,                     minutesInterval: 1,                     secondsInterval: 1,                     borderRadius: const BorderRadius.all(Radius.circular(16)),                     constraints: const BoxConstraints(                       maxWidth: 350,                       maxHeight: 650,                     ),                     transitionBuilder: (context, anim1, anim2, child) {                       return FadeTransition(                         opacity: anim1.drive(                           Tween(                             begin: 0,                             end: 1,                           ),                         ),                         child: child,                       );                     },                     transitionDuration: const Duration(milliseconds: 200),                     barrierDismissible: true,                     selectableDayPredicate: (dateTime) {                       // Disable 25th Feb 2023                       if (dateTime == DateTime(2023, 2, 25)) {                         return false;                       } else {                         return true;                       }                     },                   );       if (picked != null && picked != controller.value) {         controller.value = picked;         controller.update();       }     }   }

Did you find?

authors: Falchizao yunchiri

repo: alanchan-dev/OmniDateTimePicker


text:
Add some 404 tests

Add some 404 test, what check some bug what exists in npm version.

Oh no, tests test nothing!

I haven't written tests for all the failure cases yet, but would be glad to accept PRs!  We need tests for 201 and 304 reponses too.  Glad to offer help if you have any trouble with Chai/Nock.

authors: doublerebel kataev

repo: alanclarke/najax


text:
feat: allow task name editing for v0.4.x

Reference: https://github.com/alanvardy/tod/pull/245
Tests are missing, I just tested the feature with my account. I would like to have feedback on the code organization as I mainly focused on making things work (which was actually straightforward!). Should I add a method to projects for editing the tasks, instead of using request directly?

Also, bigger problem is on how to display the current content of the task. My idea was to print the current task name and make it editable from the user, but from a quick overview of the inquire lib it's not possible

Also, bigger problem is on how to display the current content of the task. My idea was to print the current task name and make it editable from the user, but from a quick overview of the inquire lib it's not possible

I haven't tried it but initial_value might be what you are looking for
https://docs.rs/inquire/0.6.2/inquire/struct.Text.html
If that doesn't work you could use the Editor option as it allows predefined text
https://docs.rs/inquire/0.6.2/inquire/struct.Editor.html

@BobToninho @titoOdUA I'm going to hold off merging my work for a couple of days or until this gets merged because some of my refactors will conflict with this.

Great! Will finish this in the following days

This is great, thank you!
I have PRs after this that will make it easy to test. Are you ready for me to merge?

So we'll add tests after those PRs? If yes, you can merge!

authors: BobToninho alanvardy

repo: alanvardy/tod


text:
failed to solve with frontend dockerfile.v0: failed to read dockerfile: open /var/lib/docker/tmp/buildkit-mount080660389/Dockerfile: no such file or directory

New issue popped up when tried to install through docker:
C:\Users\xxxx>docker build --tag albertbup/deep-belief-network:1.0.5 .
[+] Building 0.1s (2/2) FINISHED
=> [internal] load build definition from Dockerfile                                                               0.1s
=> => transferring dockerfile: 2B                                                                                0.0s
=> [internal] load .dockerignore                                                                                0.0s
=> => transferring context: 2B                                                                                0.0s
failed to solve with frontend dockerfile.v0: failed to read dockerfile: open /var/lib/docker/tmp/buildkit-mount080660389/Dockerfile: no such file or directory

did u fix it? having the same problem

authors: GinoToch sheldamohan

repo: albertbup/deep-belief-network


text:
Add Harbor support

Add support for VMWARE Harbor container registry as vulnerability provider

Included in v1.3.0 and onward

repo: alcideio/iskan


text:
[Feature Request]: TriviaQA for ReAct

Feature Description
Familiarize yourself with the repository and take a look at the ReAct repo, paper, and TriviaQA.
Currently, the ReAct implementation only has prompts for HotpotQA and FEVER.
Add relevant prompts and logic to the current ReAct implementation. You'll see that an agent's current structure is divided into cog/agent, cog/modules, and cog/functional/. This task will require you to make modifications in cog/prompts, but will also require you to test your code in all the other relevant modules cog/functional and cog/agent.
What to submit:

[ ] Set up your environment via the CONTRIBUTING.md
[ ] Make a Pull Request (PR)
[ ] Add the prompts for the specified benchmark
[ ] Write a short notebook tmp.ipynb in cog/agent showcasing the agent ran on a sample question from the benchmark

[ ] Add print statements for all calls to the LLM for easier debugging + I can easily verify the outputs

[ ] Include a thorough description of your changes within the PR
[ ] Request a review from @alckasoc

ReAct may not have been tested on this benchmark. If this is true, refer to other methods that have been tested on this benchmark. Check the project lifecycle document.
If there is any additional logic for testing ReAct on this benchmark, include these specifications in the PR description.
Feel free to ask me questions on Slack if you're confused! Good luck!

I am Jiaqi Wu, a first-year math-cs undergraduate at UCSD and interested in AI/ML. I will take this issue as my OA.

repo: alckasoc/discussion-agents


text:
Bump MSRV to 1.45.0

Closes #2

@tspiteri I had to fix some obscure issue that prevented compiling on 1.45.0 even (on 1.46.0 it worked), something either paste or rustc related. But anyways, because of that there will have to be a version bump (1.1.0), will publish shortly.
MSRV build will now also run on CI (and has already proven itself useful).

But anyways, because of that there will have to be a version bump (1.1.0), will publish shortly.

Isn't this just a documentation fix? I think 1.0.1 is enough, as you are not really adding new features to the library; the new features are in testing not in the library itself. And nothing that was working will stop working for any rustc version: for example for version 1.0.0 doesn't work either, so you're not really increasing the required version, you're just correcting the docs.

@tspiteri It would be documentation fix if I haven't had to fix some obscure macro scope bug which made it fail to compile on 1.45.0, but this way 1.0 only compiles on 1.46 whereas 1.1 also compiles on 1.45.

authors: aldanor tspiteri

repo: aldanor/fixed-macro


text:
Quick Form Update Removes Fields That Aren't Filled Out

I have some hidden fields that are filled in by the system after the user submit the form (e.g. ID field, URL slug field).
When the user uses the {{> quickForm type="update" }} form, any fields that aren't filled in get removed.  How can I prevent this from happening?
I've tried using a formToDoc hook, but it doesn't seem to fire.  I've also tried using docToForm before loading the form even though those fields aren't visible.

For future Googlers, the docs refer to autoForm on this page, but setArrayItems=true works for quickForm as well.

repo: aldeed/meteor-autoform


text:
Release 3.1.0

rename to aldryn-boilerplate-bootstrap3
update browser-sync to v2
update bootstrap settings file to full implementation

:+1:

LGTM

authors: FinalAngel sergii-kulakovskyi vxsx


text:
🛑 WBO is down

In dc17890, WBO (https://wbo.alefvanoon.xyz) was down:

HTTP code: 404
Response time: 5160 ms

Resolved: WBO is back up in a443f62.

repo: alefvanoon/Status


text:
Feature/allow session sub UUID

Merging in patch for skydio session truncation issue

Opened in error.  Will wait for feedback on issue 193


text:
Feature loadmore not work

Other features like reading and writing work as a charm. However with the button "Load 10 more", I cannot click and there is no option for me to load more than 10 items in a collection. Please check it. I am using Visual Studio Code for Windows 10.
Thanks a lot!

Yep, beautiful extension, but this feature is not working, while it is needed badly...

You can enable this by modifying package.json.
line 94
  {   "command": "firestore-explorer.showMoreItems",   "title": "Show More Items",   "enablement": "true"   }
and line 127
  {   "command": "firestore-explorer.showMoreItems",   "when": "true"   }

authors: MinhCuongIT Serzhmen kailash-shewtahul

repo: alesdi/firestore-explorer


text:
layers probably should have option to not auto-remove their source

See title; when using the new <Source /> element, you can get breaking behavior with <Layer /.
For example, if you have source A and layer A (layer A pointing to source A), and you remove Source A in your JSX right before layer A, an error will be thrown in componentWillUnmount which will also result in a failure to remove the click / mousemove listeners from the map.
should be easy to fix, if you have any suggestions on the approach other than a Layer parameter, feel free to share

idea -- if you use sourceId instead of passing a source object, don't remove source on unmount

pr up https://github.com/alex3165/react-mapbox-gl/pull/105 @alex3165 @philpl
layer / source component interaction is pretty broke without this, so lets converge on a solution sooner than later :)

Hey @z0d14c Thanks for the PR I have juste merged it, sorry for the delay I think we are not on the same timezone 😄


text:
map.getSource() returns undefined in onStyleLoad

I have a GEOJson <Source id="point"> with hardcoded data (ideally will come from some other source) and accompanying <Layer> component inside my <ReactMapboxGl>. I am trying to do some animation upon loading of the map. But map.getSource('point') inside onStyleLoad is returning undefined.
My current workaround right now is to add a setTimeout and everything works fine by then.
  onStyleLoad(map, e) {
    console.log(map.getSource('point'));   // this returns undefined
    setTimeout(_ => {
      console.log(map.getSource('point')); // this works
      // proceed to do other stuffs
    }, 1000);
  }

Here is my full code. Nothing really special. Initializing my variables and state in the constructor, rendering the map component.
import React, { Component } from 'react';
import ReactMapboxGl, { Layer, Source, Feature } from 'react-mapbox-gl';
import turf from '@turf/turf';

const MAPBOX_TOKEN = '<MAPBOX_TOKEN>';

class Map extends Component {
  constructor(props) {
    super(props);
    const path = turf.lineString([96.219456, 17.096823], [96.267761, 16.929063], [96.212375, 16.857859], [96.185887, 16.83685]);
    const point = turf.along(path, 0, 'miles');

    const pathSource = {
      type: 'geojson',
      data: path,
      maxzoom: 20
    };

    const pointSource = {
      type: 'geojson',
      data: point
    };

    this.state = {
      pathSource,
      pointSource,
      path,
      point
    };

    this.onStyleLoad = this.onStyleLoad.bind(this);
  }

  onStyleLoad(map, e) {
    console.log(map.getSource('point'));   // this returns undefined
    setTimeout(_ => {
      console.log(map.getSource('point')); // this works
      // proceed to do other stuffs
    }, 1000);
  }

  render() {
    <ReactMapboxGl
      style="mapbox://styles/mapbox/dark-v9"
      accessToken={MAPBOX_TOKEN}
      center={[96.1587996, 16.7849606]}
      minZoom={10}
      zoom={[13.86]}
      bearing={1}
      containerStyle={{
        height: '100vh',
        width: '100vh'
      }}
      onStyleLoad={this.onStyleLoad}
    >
      <Source id={point} geoJsonSource={this.state.pointSource} />
      <Layer
        id="pointLayer"
        sourceId="point"
        type="circle"
        layout={{
        }}
        paint={{
          'circle-radius': 4,
          'circle-color': '#ffffff'
        }}
      >
      </Layer>
    </ReactMapboxGl>
  }
}

I think maybe the map or the source layer is not fully loaded by the time onStyleLoad is fired. And is there a difference between on('style.load') and on('load'). I couldn't really find anything on the difference between the two in Mapbox GL docs. Should I be using on('load') here? Thanks!

Hey it is normal because the Source component is not mounted when the  onStyleLoad function is executed. I have just added a onSourceAdded props which receive the source as a first argument to the Source component, you can use it to get the source when it has been added to the map.

Ah … I see. onSourceAdded is just what I need. Thanks!
On Tue, 7 Mar 2017 at 17:40, Alexandre notifications@github.com wrote:
Hey it is normal because the Source component is not mounted when the
onStyleLoad function is executed. I have just added a onSourceAdded props
which receive the source as a first argument to the Source component, you
can use it to get the source when it has been added to the map.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alex3165/react-mapbox-gl/issues/145#issuecomment-284670855,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQJshDptnjlOXVd9F2M-Q87UoMKAC5Iks5rjSYmgaJpZM4MVLm7
.


text:
How can I install electron-vite 2.0.0. using @quick-start/electron?

Describe the bug
when I tried 'npm create @quick-start/electron' for starting new project, electron-vite version still 1.0.27.
How can I install electron-vite 2.0.0?
installed packages as follows.
"dependencies": {
"@electron-toolkit/preload": "^2.0.0",
"@electron-toolkit/utils": "^2.0.0",
"electron-updater": "^6.1.1"
},
"devDependencies": {
"@electron-toolkit/eslint-config-prettier": "^1.0.1",
"@electron-toolkit/eslint-config-ts": "^1.0.0",
"@electron-toolkit/tsconfig": "^1.0.1",
"@types/node": "^18.17.5",
"@types/react": "^18.2.20",
"@types/react-dom": "^18.2.7",
"@vitejs/plugin-react": "^4.0.4",
"electron": "^25.6.0",
"electron-builder": "^24.6.3",
"electron-vite": "^1.0.27",
"eslint": "^8.47.0",
"eslint-plugin-react": "^7.33.2",
"prettier": "^3.0.2",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"typescript": "^5.1.6",
"vite": "^4.4.9"
Used Scaffolding
create-electron
Used Package Manager
npm
Validations

[X] Follow the Code of Conduct.
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Thank you for your quick response.
It worked well.
Thanks again.


text:
Need Documentation!

[ ]

@sKarmony Please elaborate a bit on how to do so. Comment below a short description as to what you expect the end result to be,

I would like to suggest one thing in this documentation.
It would be better to add the names of all the skill templates present in the repository and the respective links in the readme file and the people who are adding their skills to this repo must update their skills in the readme file as well

I would like to suggest one thing in this documentation.
It would be better to add the names of all the skill templates present in the repository and the respective links in the readme file and the people who are adding their skills to this repo must update their skills in the readme file as well

@sumanthst24 that's a nice suggestion, it's better you make this up as a new issue and elaborate it there.

Is this community, Active ?? ... Because there was no update from the last 3 years

repo: alexa-dev-hub/alexa-skills