Uncaught TypeError: msg.text.join is not a function

I tried the solution here https://github.com/jupyter/atom-notebook/issues/67
(remove the curly bracket)
and it turned out like this ⬇
Atom: 1.40.1 x64
Electron: 3.1.10
OS: Mac OS X 10.14.6
Thrown From: jupyter-notebook package 0.0.10
Stack Trace
Uncaught TypeError: msg.text.join is not a function
At /Users/euniceng/.atom/packages/jupyter-notebook/lib/display-area.js:68

TypeError: msg.text.join is not a function
    at DisplayArea.makeMimeBundle (/packages/jupyter-notebook/lib/display-area.js:68:39)
    at /packages/jupyter-notebook/lib/display-area.js:49:31
    at Array.map (<anonymous>)
    at DisplayArea.transformMimeBundle (/packages/jupyter-notebook/lib/display-area.js:48:55)
    at DisplayArea.componentWillMount (/packages/jupyter-notebook/lib/display-area.js:29:10)
    at ReactCompositeComponentWrapper.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactCompositeComponent.js:210:12)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactDOMComponent.mountChildren (/packages/jupyter-notebook/node_modules/react/lib/ReactMultiChild.js:241:44)
    at ReactDOMComponent._createContentMarkup (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:591:32)
    at ReactDOMComponent.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:479:29)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactDOMComponent.mountChildren (/packages/jupyter-notebook/node_modules/react/lib/ReactMultiChild.js:241:44)
    at ReactDOMComponent._createContentMarkup (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:591:32)
    at ReactDOMComponent.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:479:29)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactCompositeComponentWrapper.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactCompositeComponent.js:225:34)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactDOMComponent.mountChildren (/packages/jupyter-notebook/node_modules/react/lib/ReactMultiChild.js:241:44)
    at ReactDOMComponent._createContentMarkup (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:591:32)
    at ReactDOMComponent.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:479:29)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactDOMComponent.mountChildren (/packages/jupyter-notebook/node_modules/react/lib/ReactMultiChild.js:241:44)
    at ReactDOMComponent._createContentMarkup (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:591:32)
    at ReactDOMComponent.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:479:29)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactDOMComponent.mountChildren (/packages/jupyter-notebook/node_modules/react/lib/ReactMultiChild.js:241:44)
    at ReactDOMComponent._createContentMarkup (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:591:32)
    at ReactDOMComponent.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:479:29)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactCompositeComponentWrapper.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactCompositeComponent.js:225:34)

Commands

Non-Core Packages
atom-runner 2.7.1
Hydrogen 2.13.1
ide-json 0.2.1
jupyter-notebook 0.0.10
script 3.18.1

I tried the solution here #67
(remove the curly bracket)
and it turned out like this
Atom: 1.40.1 x64
Electron: 3.1.10
OS: Mac OS X 10.14.6
Thrown From: jupyter-notebook package 0.0.10
Stack Trace
Uncaught TypeError: msg.text.join is not a function
At /Users/euniceng/.atom/packages/jupyter-notebook/lib/display-area.js:68

TypeError: msg.text.join is not a function
    at DisplayArea.makeMimeBundle (/packages/jupyter-notebook/lib/display-area.js:68:39)
    at /packages/jupyter-notebook/lib/display-area.js:49:31
    at Array.map (<anonymous>)
    at DisplayArea.transformMimeBundle (/packages/jupyter-notebook/lib/display-area.js:48:55)
    at DisplayArea.componentWillMount (/packages/jupyter-notebook/lib/display-area.js:29:10)
    at ReactCompositeComponentWrapper.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactCompositeComponent.js:210:12)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactDOMComponent.mountChildren (/packages/jupyter-notebook/node_modules/react/lib/ReactMultiChild.js:241:44)
    at ReactDOMComponent._createContentMarkup (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:591:32)
    at ReactDOMComponent.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:479:29)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactDOMComponent.mountChildren (/packages/jupyter-notebook/node_modules/react/lib/ReactMultiChild.js:241:44)
    at ReactDOMComponent._createContentMarkup (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:591:32)
    at ReactDOMComponent.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:479:29)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactCompositeComponentWrapper.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactCompositeComponent.js:225:34)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactDOMComponent.mountChildren (/packages/jupyter-notebook/node_modules/react/lib/ReactMultiChild.js:241:44)
    at ReactDOMComponent._createContentMarkup (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:591:32)
    at ReactDOMComponent.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:479:29)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactDOMComponent.mountChildren (/packages/jupyter-notebook/node_modules/react/lib/ReactMultiChild.js:241:44)
    at ReactDOMComponent._createContentMarkup (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:591:32)
    at ReactDOMComponent.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:479:29)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactDOMComponent.mountChildren (/packages/jupyter-notebook/node_modules/react/lib/ReactMultiChild.js:241:44)
    at ReactDOMComponent._createContentMarkup (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:591:32)
    at ReactDOMComponent.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactDOMComponent.js:479:29)
    at Object.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactReconciler.js:37:35)
    at ReactCompositeComponentWrapper.mountComponent (/packages/jupyter-notebook/node_modules/react/lib/ReactCompositeComponent.js:225:34)

Commands
Non-Core Packages
atom-runner 2.7.1
Hydrogen 2.13.1
ide-json 0.2.1
jupyter-notebook 0.0.10
script 3.18.1

change this
bundle = {'text/plain': msg.text.join('')};
into this
bundle = {'jupyter/stream': msg};


[core] Optizime IN filter pushdown to snapshot/tag/schema system tables

Purpose

Linked issue: close #xxx

Currently IN filter cannot pushdown to snapshot/tag/schema system tables and IN would tramsform to OR(contians all Equal LeafPredicate), if user query with IN filter would cost more unnessary IO in a large number of snapshots/tag/schema;
TagTable predicate specified as LeafPredicate which cannot resolve other kind of Predicate, this pr had improved it.
Add APIs for get snapshots/tags/schemas which get multiple numbers for a list argument.

such like sql: select snapshot_id, schema_id, commit_user from T$snapshots where snapshot_id in (1, 3);
before the pr would query all snapshots files firstly, then filter with 1 and 3;
after the pr  would query only snapshots file with 1 and 3, not query all snapshots file, which can reduce unnessary IO.
note: if filter contains other fields would handle regress as before( like: select snapshot_id, schema_id, commit_user from T$snapshots where snapshot_id in (1, 3) or/and commit_user='xxx'; ), just work only snapshot_id IN filter.
Tests

API and Format

Documentation

@wwj6591812 Thanks review，had addressed.

+1

+1


Velocity Calculation fails for Hexagonal ThreeRollPass

Because of dependency of usable cross section area inside the algorithm, the algorithm fails for flat grooves.

already fixed


Broken links in docs

https://medium.com/@kelvinfichter/whats-a-sparse-merkle-tree-acda70aeb837 404

Temporarily network issue


Add mod file

Added a mod file to prepare for support of Modules.  @iafan you will need to tag the repo as I don't have permissions to do this.  This is for #7

@iafan gentle ping. Can we have this mearged please?

@iafan gentle ping. Can we have this mearged please?


fixate v1.14.6

Fixates the version, marks as release, sets the year of release.
Blocked until we make final decisions on all open PRs under the 1.14.6 milestone.

Everything is in, so 1.14.6 is good to go.

Built here on MacOS 12.4 M1 (under Rosetta of course / unfortuantely ) just for a bit of posterity, and looks gtg. much excite.

Ajs

Ajs


Fix invalid XML error

I had trouble installing this plugin with ionic cli, as the XML had an invalid character.
$ ionic plugin add --save cordova-plugin-nativeaudio
Fetching plugin "cordova-plugin-nativeaudio" via npm

Error: Invalid character in entity name
Line: 8
Column: 54
Char:

& by itself is not valid in XML and must be escaped by using &.
I fixed this issue and now I can install the plugin via a git URL.

hey guys, doesn't make sense to create new PRs again and again if there is already one, see #94, #109
@gligoran it's worth to look around in existing PRs and issues before creating a new PR

Oh, right, I forgot to check other PRs. Sorry. But I would urge @floatinghotpot to fix this XML problem as soon as possible.


[Blaze] Detected multiple package definitions

Hi,
vite-bundler: 2.0.0-beta.12
meteor-vite: 1.10.2
meteor: 3 beta 6
Creating the new issue about multiple package to avoid polluting the other one.
I added useraccounts:core in my project and to try to use https://github.com/meteor-vue/blaze-integration/issues/16 to use blaze template with Vue3.
When I try to use it with:
<template>
  <v-blaze template="atForm" :data="{ state: 'changePwd' }" />
</template>

<script setup>
  import VBlaze from '../../components/Generic/vBlaze.ts';
</script>

<style></style>

I have the following error message:
Server side:

Client side:

When running meteor lint, I have this error also:
[meteor-vite: stubs] Could not load meteor/blaze (imported by imports/ui/components/Generic/vBlaze.ts): The "path" argument must be of type string. Received undefined

Hey there 👋
I'll try to have a closer look at this in the next couple of days. In the meantime, would you be able to set up a repository reproducing the error there? 🙏

Hi,
Yes, i will try to have a repository that reproduce the issue

Here the repo:
https://github.com/harry-73/blaze-vue3-meteor

I am having this issue in #151

Hey there 👋
I'll try to have a closer look at this in the next couple of days. In the meantime, would you be able to set up a repository reproducing the error there? 🙏

Hi,
Did you see something with the repository?
Thanks.


Azur - admin console -> conversion of diksha tpd and etb api to emission is not working

Tring to change diksha tpd and etb from api to emission
Issue: alert is showing error

Defect is working now due to admin console api issue is not worked earlier

Issue is fixed


Fixed Portal URL

Portal was missing subdomain causing failed login

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

File
Status
Preview URL
Details

defender/threat-intelligence/searching-and-pivoting.md
:bulb:Suggestion

Details

defender/threat-intelligence/searching-and-pivoting.md

Line 2, Column 1: [Suggestion: manager-missing - See documentation] Missing required attribute: 'manager'. Add a valid Microsoft alias for the author's manager.

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

@DulceMontemayor Please merge this PR. Thanks

Learn Build status updates of commit 009344e:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


SEO URLs for Headless Sales Channel

Acceptance criteria:

URLs for headless sales channel are being recognized by the page resolver as well as storefront does
navigation endpoint contains SEO URLs instead of technical ones

we'll discuss it further on Monday

the SEO URLs have been implemented and work great!


Trigger message

@Ghostvv and myself discussed a way to allow form slots to be filled from the intent of the trigger message here
Proposed changes:

added trigger_message attribute to form event
added a from_trigger_intent slot mapping function

Status (please check what you already did):

[ ] made PR ready for code review
[x] added some tests for the functionality
[ ] updated the documentation
[x] updated the changelog

Respective changes in rasa_core can be found here

I'll review this by the end of this week.

@smn-snkl did you have a chance yet to look at this? 🙂

@tmbo sorry for the delay, I'm a bit head under water right now as I have a deadline approaching by the beginning of next week. I could try to allocate it before if it's high priority for you, otherwise I'd finish it right after.

No worries and thanks for the heads up 🙂 no need to rush this! The reason I was asking is that we want to restructure the code a bit and we want merge most of the prs in the near future.

Sorry, closed by accident


Added merge_sync and sync_vars

Allows for syncing dasks together, removing terms equivalent modulo
variables. Fixes #37.
This provides two functions: sync_vars and merge_sync:

sync_vars takes two dasks, and returns a dict mapping keys in dask2 to equivalent keys in dask1.
merge_sync takes two dasks, calls sync_vars, and then merges the two dasks, applying the substitutions to each task.

If a term doesn't support ==, it is skipped over.
Example:
>>> dsk1 = {'a': 1, 'b': (add, 'a', 10), 'c': (mul, 'b', 5)}
>>> dsk2 = {'x': 1, 'y': (add, 'x', 10), 'z': (mul, 'y', 2)}
>>> sync_vars(dsk1, dsk2)
{'x': 'a', 'y': 'b'}
>>> merge_sync(dsk1, dsk2)
{'a': 1, 'b': (add, 'a', 10), 'c': (mul, 'b', 5), 'z': (mul, 'b', 2)}

This won't work for dasks that have matching keys (i.e. both dasks have key 'a'). I'm not sure how best to handle that. I see two solutions to this:

We create a new unique key for name conflicts. However, this will cause issues if that key is a desired result, as it won't be in the dask anymore. One solution would be to return a mapping of old names in dask2 to their new names in the merged dask. Note that this may be necessary even without name conflicts if any keys are replaced. Example:

>>> dsk1 = {'a': 1}
>>> dsk2 = {'a': 2}
>>> new_dsk, mapping = merge_sync(dsk1, dsk2)
>>> new_dsk
{'a': 1, 'gensym_1': 2}
>>> mapping
{'a': 'gensym_1'}

Erroring on name conflicts if the corresponding values aren't equivalent. Example:

>>> dsk1 = {'a': 1}
>>> dsk2 = {'a': 2}
>>> merge_sync(dsk1, dsk2)
ValueError("Conflicting keys in dsk1 and dsk2")
>>> merge_sync(dsk1, dsk1)
{'a': 1}

Thoughts?

>>> dsk1 = {'a': 1, 'b': (add, 'a', 10), 'c': (mul, 'b', 5)}
>>> dsk2 = {'x': 1, 'y': (add, 'x', 10), 'z': (mul, 'y', 2)}
>>> sync_vars(dsk1, dsk2)
{'x': 'a', 'y': 'b'}

How would this handle redundancy within a dask?, e.g {'a': 1, 'b': 1, ...}

As you point out it might be important to respect the names of a certain set of output keys.  It might make sense to take these as another input.

How would this handle redundancy within a dask?, e.g {'a': 1, 'b': 1, ...}

Right now it just finds the first valid match. The order of what's checked has to do with the ordering of dsk1.keys(), so it's random. I'm not sure if dealing with such cases is in the scope of this function - a good way to avoid this would be to trim duplicates from dsk1 before calling. Terms in dsk2 will always match to the same value in dsk1, so there's maybe no need to deduplicate dsk2 (it won't remove duplicate terms that don't match something in dsk1 though).

It might make sense to take these as another input.

So have an optional arg no_rename (or some other name) that takes a list of variables in dsk2 that can't be renamed? What happens in a case of conflict? Error?
Right now I'm treating dsk1 as concrete and only changing dsk2. If we can change keys in both dasks, then as long as the same variable name in each dask isn't requested there would always be one variable that could be renamed. However, I'm not sure how this would work with the sync_vars function.
I guess the question is, what is the intended scope of these functions?

A separate pass of de-duplication sounds like a good solution to redundancy within one graph.
Thinking more about this problem maybe we don't need to keep the output keys the same.  Maybe we just change the keys sent to get functions as we change them in dsk2.

I guess the question is, what is the intended scope of these functions?

That's a great question.  At the moment I'm considering the case where we accumulate dask computations from previous runs and reuse them in future runs.  Ideally this benefits from overlap between multiple similar queries.  I was fooling around with this idea in https://github.com/ContinuumIO/dask/pull/36 but it hasn't gone anywhere yet.
Consider the following example:
x = da.from_array(x, blockshape=(1000,))

y = x[:5000].sum().compute()
z = x[:6000].sum().compute()

Most of the work for z is already done when we compute y if we hold on to the right intermediate results (another problem entirely.)  The shared structure in these graphs is the same except for the names.  The goal is to identify and unite these cases.  Presumably we have one large dask graph that contains everything we've seen so far (the dealiasing and merger of many dask graphs) and every time we compute something we merge it into this graph and then compute against a shared cache with values keyed by the keys within this graph.
Within this context we probably only want to change dsk2 (the smaller graph).

Maybe we just change the keys sent to get functions as we change them in dsk2.

So something like the following?
>>> sub_dict, key_lookup = sync_vars(dsk1, dsk2, result_keys)
>>> new_dsk, key_lookup = merge_sync(dsk1, dsk2, result_keys)

Where result_keys is a list of keys that we may request from dsk2, and key_lookup is a dict mapping the old result_keys to their (potentially) new values. I'm unsure if the change to sync_vars is needed, but the change for merge_sync sounds good to me. I feel that sync_vars should probably just create mappings between equivalent keys in dsk2 and dsk1 without considering name conflicts.

At the moment I'm considering the case where we accumulate dask computations from previous runs and reuse them in future runs.

Interesting idea. I was playing with using it for pre-optimizing dasks before execution (no need to compute the same thing twice). If we store results in an ever size increasing dask, a permanent dep_dict data structure would make merging new dasks much faster, as we'd no longer have to preprocess dask1 each time. The current functions don't support this (preprocessing is contained in sync_vars), but they could be refactored to work nicely in such situations.

(aside, because this is interesting)

The goal is to identify and unite these cases.

This sounds like a pretty difficult problem to solve, as matching sub problems is semantic rather than syntactic. Assuming the task for the example you gave is:
(sum, (getitem, 'x', (0, 1, 6000)))    # I think that's how slice tuples work?

Certainly, one could search for this exact query to see if it's already been computed (syntactic matching), but other equivalent terms are:
(sum, (getitem, 'x', (6000, -1, 0)))
(add, (sum, 'x', (0, 1, 3000)), (sum, 'x', (3000, 1, 6000)))

These don't match the query term, but by meaning they're the same. And then you have subproblems like:
(sum, (getitem, 'x', (3000, 1, 6000)))
(sum, (getitem, 'x', (2000, 1, 4000)))

Because they overlap, you'd have to have some metric to determine which already solved solution should be used to reduce computation time. And if they didn't overlap, then there'd  be a way to use both of them. I'm seeing a lot of special case code coming from this.
It would be really cool to get this working, but it sounds like a pretty difficult problem to solve if we're going to add knowledge about how some tasks can be sub-problems for other tasks without having them actually composed of those other tasks.

Fortunately the blocking into blocks of size 1000 saves us here.
Sorry for the fast example without context.
In [1]: import numpy as np

In [2]: import dask.array as da

In [3]: x = np.arange(10000)

In [4]: x = da.from_array(x, blockshape=(1000,))

In [6]: y = x[:6000].sum()

In [7]: da.optimize(y.dask, y._keys())
Out[7]:
{'x_1': array([   0,    1,    2, ..., 9997, 9998, 9999]),
 ('x_6', 0): (<functools.partial at 0x7faa6477e940>,
  (<function operator.getitem>, 'x_1', (slice(0, 1000, None),))),
 ('x_6', 1): (<functools.partial at 0x7faa6477e940>,
  (<function operator.getitem>, 'x_1', (slice(1000, 2000, None),))),
 ('x_6', 2): (<functools.partial at 0x7faa6477e940>,
  (<function operator.getitem>, 'x_1', (slice(2000, 3000, None),))),
 ('x_6', 3): (<functools.partial at 0x7faa6477e940>,
  (<function operator.getitem>, 'x_1', (slice(3000, 4000, None),))),
 ('x_6', 4): (<functools.partial at 0x7faa6477e940>,
  (<function operator.getitem>, 'x_1', (slice(4000, 5000, None),))),
 ('x_6', 5): (<functools.partial at 0x7faa6477e940>,
  (<function operator.getitem>, 'x_1', (slice(5000, 6000, None),))),
 ('x_7',): (<toolz.functoolz.Compose at 0x7faa646c8be8>,
  [('x_6', 0), ('x_6', 1), ('x_6', 2), ('x_6', 3), ('x_6', 4), ('x_6', 5)])}

In [8]: y = x[:5000].sum()

In [9]: da.optimize(y.dask, y._keys())
Out[9]:
{'x_1': array([   0,    1,    2, ..., 9997, 9998, 9999]),
 ('x_10',): (<toolz.functoolz.Compose at 0x7faa646c8c58>,
  [('x_9', 0), ('x_9', 1), ('x_9', 2), ('x_9', 3), ('x_9', 4)]),
 ('x_9', 0): (<functools.partial at 0x7faa646cfa48>,
  (<function operator.getitem>, 'x_1', (slice(0, 1000, None),))),
 ('x_9', 1): (<functools.partial at 0x7faa646cfa48>,
  (<function operator.getitem>, 'x_1', (slice(1000, 2000, None),))),
 ('x_9', 2): (<functools.partial at 0x7faa646cfa48>,
  (<function operator.getitem>, 'x_1', (slice(2000, 3000, None),))),
 ('x_9', 3): (<functools.partial at 0x7faa646cfa48>,
  (<function operator.getitem>, 'x_1', (slice(3000, 4000, None),))),
 ('x_9', 4): (<functools.partial at 0x7faa646cfa48>,
  (<function operator.getitem>, 'x_1', (slice(4000, 5000, None),)))}

Ahhh, that'll make things easier. Not sure if it would be worth it memory-wise, but you could probably come up with some heuristic for cacheing only the queries that are directly related to the underlying datasets (in this case, the sum of each block), as those are the expensive computations.
Anyway, after some more thought, I think that sync_vars should stay the same, but the behavior of merge_sync should be changed to the following:
def merge_sync(dsk1, dsk2):
    """Merge two dasks together, combining equivalent terms.

    Parameters
    ----------
    dsk1, dsk2 : dasks

    Returns
    -------
    new_dsk : the merged dask
    key_map : a mapping between key names in `dsk2`, and key names in `new_dsk`"""

This will merge the dasks, and return the dict from sync_vars, updated with any renames due to name conflicts.

I suspect the first heuristic will be to look at three things for each key/task pair

The duration of computation (this took 200ms to compute)
The size of the results in bytes
How frequently this key gets requested

And then some sort of priority queue that takes the "best" keys based on some function over those things.

This seems fine to me, but I haven't taken a very in depth look.  @eriknw might find this interesting but he might be busy.
Honestly we should probably have an actual problem before we go too much more deeply in this direction.  The use case I had of slowly increasing datasets dired up a bit.  it would be a fun thing to resurrect though.  It's a novel direction for computation.


Dependency updates

Someone forgot to change the spring boot version on the last update 😉 also some other stuff, with the new jupiter version the setup and tearDown methods must not be private anymore.

Someone forgot to change the spring boot version on the last update 😉 also some other stuff, with the new jupiter version the setup and tearDown methods must not be private anymore.

@hedgehog1833
What do you mean by that? Do you have to adjust it in 2 places?


Update Harmonie config and SVG

Thanks for maintaining a dedicated faucet for the Substrate ecosystem.
As we are actually using an old faucet backend forked from the polkadot one, we would like to move to this faucet.
This PR is just some fix and adjustment for our testnet so we can start working with the application.

Thank you @SailorSnoW for the pull request. The changes are now live on the production.

@SailorSnoW May I know if the Harmonie testnet has a JSON RPC? We prefer it over websocket RPC for the frontier-based EVM chains/environments.
Suggestion: Please add your chain to the ethereum-lists repo, so it can be accessed from the chainlist.org

Look like the the testnet's JSON RPC and websocket RPC are same. Switched to JSON RPC.
The faucet is ready to use now for the Harmonie testnet.
Please refill the faucet by sending the test tokens to this address: 0xFe50094e366802c9d0aa0b47fC19B275e92F0b7F
@SailorSnoW

Our users are encountering this following error after we published the news on the discord: "Exceeded API limit for Harmonie Testnet".
Is that normal for the API rate-limit to be this strict ?

Our users are encountering this following error after we published the news on the discord: "Exceeded API limit for Harmonie Testnet".
Is that normal for the API rate-limit to be this strict ?

Yes, there is a generic rate limiting. One can request only once in 24 hours for each address.
Do your users need to request more than once in a day for any specific application? If so, we can implement a custom rate limiting.

Haa thanks for the confirmation, wasn't sure it was a per-address rate limit.
No it's okay like this then, I think one request per day is just enough to limit it right.

Cool, thanks for the confirmation.

@SailorSnoW if you prefer redirecting your users to the Harmonie's dedicated page on the faucet, you can use this link:
https://substratefaucet.xyz/allfeat-testnet

Perfect thanks, was searching if a feature like that has been implemented, so cool :)


Enhancement: Time Picker

I'm excited there is a date picker now! Would it be possible to also get the time options bound to the underlying control?

At the moment, you cannot use options to the underlying control of the date picker.
It seems the Datepick are using flatpickr as calendar logic and I have been looking into it.
Flatpickr does have an option to change date picker to time picker by using two boolean values and a date format. See here for what I am talking about: link
so in theory, it should be easy to implement Flatpickr options. The Flatpickr options
it would be nice if date picker could look something like this:
            @*Enable time on an normal AM/PM calendar*@
            <MatDatePicker EnableTime="true"></MatDatePicker>

            @*Enable time on an calendar with 24 hours option*@
            <MatDatePicker EnableTime="true" Enable24Hr="true"></MatDatePicker>

            @*Enable time picker with AM/PM*@
            <MatDatePicker NoCalendar="true" EnableTime="true"></MatDatePicker>

and the date picker code is using an object that contains all the options that could send to the javascript behind the date picker instead of using a DateTime value that is sending back.
export function init(ref, cmp, options) {
    //console.log('options', options)

  ref.$flatpickr = flatpickr(ref, {
      defaultDate: options.Value,
      enableTime: options.EnableTime,
      dateFormat: options.DateFormat,
      noCalendar: options.NoCalendar,
      time_24hr: options.Enable24Hr,
    // wrap: true,
    // allowInput: true,
    // clickOpens: false,
    onChange: function (value) {
      // console.log(value);
      cmp.invokeMethodAsync('MatDatePickerOnChangeHandler', value);
    }
  });

  ref.$iconRef = iconRef;

  // ref.addEventListener('focus', (i) => {
  //
  //   ref.$flatpickr.close();
  // });
}

I haven't managed to get it to work on my machine yet, but the concept is there.
But I am not sure if we can extend the date picker by making a new class called 'BaseMatTimePicker' and let it inherited from the BaseMatDatePicker than improve the date picker with options.

Enable time picker without Calendar, no longer works in version 2.0.0. (it disables everything) Is there some solution?

@antonianikolova Have you found a solution or have been informed of a solution? I've just implemented the standard MatDatePicker while I wait.

Hi, I also have a requirement to bind to a TimeSpan value for selecting a time only, would be great to have a time picker.

+1 for a time picker. It doesn't even be integrated with the date picker.

Also really need the time picker

I did realize that you can take the Mattextfield and put the type as time and convert the string to a time span and add it to a datetime


Remove control characters from file names found in OS X

I was instructed to send you guys a bug report by the backblaze b2 team.
I do a sync  with rclone to b2 and get some api errors, and some IO errors as if backblaze pods cannot be read. I can't quite reproduce the issue often as after about 10 retries it works. Here is my log attached. I know this is not much help but i'm using the current version of rclone on mac os el capitan  64 bit.
outputbooks.log.zip

Your files seem to have a carriage return on the end of them which is really odd!
All the failing files are called Icon^M.  Here is an explanation of what those are: http://superuser.com/questions/298785/icon-file-on-os-x-desktop/298798
Backblaze (nor any other cloud provider) don't let you store a file with a control character in which is why they don't upload and why so many errors.
I think if it wasn't for those files then your sync would be working quite well.  There are always a few errors with cloud storage systems, but rclone will retry the sync and get there in the end.
So I think what I should do is substitute control characters (0x00-0x1F and 0x7F) in local.go cleanRemote (perhaps to %XX) this will make the sync complete properly.  Note that it won't back up the contents of the Icon files though as these are stored in the resource fork and rclone only copies the data fork.
I'll post a beta for you to try in due course here.

Thanks. I know I didn't put any ctrl chars in my files. How odd. The icon files I'm not worried about, I don't think it will hurt my books and crud (tech term)  if the icon files are not there.
Thanks.

...in the mean time you could add --exclude 'Icon?' to your command line to not sync those files.

I've fixed that in: http://beta.rclone.org/v1.33-71-ga02edb9/ (uploaded in 15 mins)
I decided to ignore the files with control characters in which seems perfect for this use case.

Thanks. I and hopefully others will test it now. The files with control chars like the ones that are braking won't hurt anything if they are gone from a back up will they? I'm thinking no.
I'll post results here.

Sorry to comment so quickly. I'm getting a file not found error in safari when I try and dl. My wget yields this.
--2016-10-18 09:41:13--  http://beta.rclone.org/v1.33-71-ga02edb9/
Resolving beta.rclone.org... <IP_ADDRESS>
Connecting to beta.rclone.org|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 404 NOT FOUND
2016-10-18 09:41:13 ERROR 404: NOT FOUND.
Thanks.

It has appeared now. Sometimes Travis takes a bit longer her than 15 minutes.

The files with control chars weren't being backed up before. Those Icon files are the only examples I've found.


Service Request by Nick Bove - User log in issue

[x] Problem FULLY RESOLVED and Issue is Closed
[ ] Post-Service Request Survey was sent to User

Use comments feature (below) to document:

A clear and concise description of the solution.

A clear and concise description of any alternative solutions or features you've considered.

Any additional context, such as screenshots about the problem.

Program Manager Putnam County Login Issue: "For some reason when I enter the username/password and click login, the boxes turn yellow (login info remains) and nothing happens. I tried refreshing the page, etc. and still not working. I’m not sure what to think."

@NBOVE1
I suggest deleting this individual's user name via "Users". I would delete them from the list, then save and exit the Tracker. Then log back in and add the individual.
Then log out and back in, this time testing the username and new password.
If all is good, ask them to do the same.
If you have a problem, add Jeff to this issue and comment to him about the problem.
THANKS

Thank you David. This has appeared to work. I've requested that Kristin try it on her end:

@NBOVE1  If Program Manager Putnam County can log in without difficulty now, then we can close this issue.

@dlounsbu Sure, I'll close this out as soon as the PM confirms that she can access the tracker.


npm package giving error

inside the npm package src/node/index.js file very first line requires the fs npm package but fs package not exists.
can you please tell me about this require('fs').

This is the standard node fs module: https://nodejs.org/api/fs.html#fs_file_system

node
> require('ifsc').validate('HDFC0000001')
true

Error on my side:
ERROR  Failed to compile with 1 errors11:56:49 AM

This dependency was not found:

* fs in ./~/ifsc/src/node/index.js

To install it, you can run: npm install --save fs

But I have installed fs npm package, here is my package.json dependencies:
  "dependencies": {
    "babel-plugin-transform-runtime": "^6.23.0",
    "chart.js": "^2.7.1",
    "datatables.net": "^1.10.16",
    "datatables.net-dt": "^1.10.16",
    "fs": "0.0.1-security",
    "ifsc": "^1.0.11",
    "select2": "^4.0.5",
    "vue-chartjs": "^2.8.7",
    "vue-good-table": "^1.16.0",
    "vue-search-select": "^2.4.0",
    "vue-strap": "^1.1.40",
    "vue-template-compiler": "^2.5.7",
    "vuejs-datepicker": "git+https://github.com/paaysay/vuejs-datepicker.git"
  }

Please remove the fs package from your npm setup and try again. The fs module is part of node and is not required to be installed.
The package seems to be all fine: https://runkit.com/embed/hyy84qcdmjkl

Thanks @captn3m0
Even I install fs package or remove from my package.json, in both cases error occurred.

Are you using it with webpack? This package works with node.

Yes, I am using this with webpack, is it possible or not with webpack?

This is a Node.JS only package as of now, since the package does offline validation over a 300kb file, which you don't want to load over a web browser.
Instead, just make a AJAX request to https://ifsc.razorpay.com/{IFSC} to validate a IFSC code for a much faster method.

Same Error not able to find fs module
even i have installed it globally on my system.
Kindly assist  waiting for your reply.


[BUG] Received fatal alert: certificate_unknown

Describe the bug
Hello,
I am configuring opensearch to use letsencrypt certificate, everything was working fine but today i did helm delete/install, and i got that issue:
[2024-05-21T10:08:17,407][WARN ][o.o.h.AbstractHttpServerTransport] [opensearch-cluster-master-0] caught exception while handling client http traffic, closing connection Netty4HttpChannel{localAddress=/<IP_ADDRESS>:9200, remoteAddress=/<IP_ADDRESS>:34368} io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown
configurations:
``
opensearch.yml: |
    cluster.name: opensearch-cluster

    # Bind to all interfaces because we don't know what IP address Docker will assign to us.
    network.host: <IP_ADDRESS>

    # Setting network.host to a non-loopback address enables the annoying bootstrap checks. "Single-node" mode disables them again.
    # Implicitly done if ".singleNode" is set to "true".
    # discovery.type: single-node

    # Start OpenSearch Security Demo Configuration
    # WARNING: revise all the lines below before you go into production
    plugins:
      security:
        nodes_dn:
            - 'CN=opensearch.lab.mycompany.eu'
        ssl:
          transport:
            pemcert_filepath: certs/tls.crt
            pemkey_filepath:  certs/tls.key
            pemtrustedcas_filepath: certs/tls.crt
            enforce_hostname_verification: false
          http:
            enabled: true
            pemcert_filepath: certs/tls.crt
            pemkey_filepath: certs/tls.key
            pemtrustedcas_filepath: certs/tls.crt
        allow_unsafe_democertificates: true
        allow_default_init_securityindex: true
        authcz:
          admin_dn:
            - 'CN=opensearch.lab.mycompany.eu'
        audit.type: internal_opensearch
        enable_snapshot_restore_privilege: true
        check_snapshot_restore_write_privileges: true
        restapi:
          roles_enabled: ["all_access", "security_rest_api_access"]
        system_indices:
          enabled: true
          indices:
            [
              ".opendistro-alerting-config",
              ".opendistro-alerting-alert*",
              ".opendistro-anomaly-results*",
              ".opendistro-anomaly-detector*",
              ".opendistro-anomaly-checkpoints",
              ".opendistro-anomaly-detection-state",
              ".opendistro-reports-*",
              ".opendistro-notifications-*",
              ".opendistro-notebooks",
              ".opendistro-asynchronous-search-response*",
            ]
    ######## End OpenSearch Security Demo Configuration ########
 extraEnvs:
    - name: DISABLE_INSTALL_DEMO_CONFIG
      value: "true"

 extraVolumes:
   - name: opensearch-certs
     secret:
       secretName: tls-for-opensearch

   - name: opensearch-root-certs
     secret:
       secretName: root-ca

extraVolumeMounts:
   - name: opensearch-certs
     mountPath: /usr/share/opensearch/config/certs
     readOnly: true

   - name: opensearch-root-certs
     mountPath: /usr/share/opensearch/config/root

  securityConfig:
     enabled: true
     internalUsersSecret: internalusers-secret

    `

Related component
Plugins
Expected behavior
Opensearch up with letsencrypt certificate

Hi @sfisli,
Did you go through the forum posts for related failure queries?
https://forum.opensearch.org/search?q=Received fatal alert%3A certificate_unknown order%3Alatest


continuserv: Server to live serve local updates to the spec

The go isn't wonderful, but I hacked this together for my own benefit, and figure other people may want to use it

Install instructions would be great (e.g. min Go version and basic install steps) to include in a README in the continuserv directory. FWIW, I had to go get to get fsnotify then go run main.go.
It also didn't seem to pick up changes in the /specification folder when I tried - though it did on the YAML schemas in /api. The directories used to generate the spec are:
/api
/event-schemas
/scripts (specifically the .css files)
/specification
/templating

If you could watch these directories that would encompass any and all changes to the spec, not just YAML stuff.

Added README.
I also added a logging line, so that it will log when it detects an update. It should be finding any changes in the git repo, and I certainly could trigger rebuilds with changes to /specification - if you can reproduce with the logging, let me know :)

LGTM


Enforce Canonical Base64 encoding.

There's an apparent problem with RFC 4648.  There are three places base 64 representation may contain string variation:

Padding
Alphabet (URI unsafe or URI safe)
Canonical encoding (various characters can encode to the same byte string, but there is only one canonical decoding)

What is "canonical encoding"?  From the last three characters of the example tmb, "cLj8vs...XNuhOk", the values hOk and hOl may both decode to the same byte value (in Hex, 84E9) even though they are different UTF-8 values.  (Example decoding hOk and hOl.)  The canonical encoding is hOk
The RFC specifically addresses 1 and 2, but not really 3.
RFC 4648 advises to reject non-alphabet characters, which can include padding.  I agree with this advice:

Implementations MUST reject the encoded data if it contains
characters outside the base alphabet when interpreting base-encoded
data, unless the specification referring to this document explicitly
states otherwise. [...]  Furthermore, such specifications MAY ignore the pad
character, "=", treating it as non-alphabet data[.]

I don't see the RFC really address the to the third concern.
Behavior
Obviously non-"strict"/non-canonical base 64 encoding is incorrect, and any encoder producing non-strict encoding should be fixed.   However the question is what should Coze specify regarding non-strict encoding/decoding?  Both Go and Javascript are permissive when decoding and do not throw errors.
Ultimately, the concern is different base 64 encoders/decoders may have different behavior.  Ideally, Coze should specify the appropriate behavior for Coze.  Section 3.5 mentions non-canonical encoding in the context of unpadded data and this issues is unrelated to padding (hOk= and hOl=, both padded, have the same issue as unpadded strings).
The concern is that if a Coze implementation used string comparison instead of byte comparison, this could result implementations disagreeing about valid messages.  For example, with a non-strict tmb encoded string, if a Coze implementation checks tmb before cryptographic verification, it may check this based on the string value or the byte value, and comparing the string value or the byte value will result in different behavior.
Another note for any Coze restriction on encoding: JSON is base 64 unaware, any sort of Coze specified enforcement of base 64 encoding can only be applied to Coze known fields with type b64ut, and cannot be applied generally to any b64ut value.
Solutions
There appears to be only two options to handle this:

Be permissive on inbound encoding, force strict outbound encoding.
Force strict encoding and decoding.  (This can only be done when type is known to be b64ut.)

2 is more conservative, but may require unnecessary checks that don't really add value.  1 has the potential to be more compatible if assuming that systems can decode permissively (other programming language's base 64 libraries decode permissively), which may be a bad assumption.
Regardless, I believe that 1 is the correct behavior here.  Even if languages/system do no error on non-canonical encoding, implementing an encoding error can be implemented by re-encoding the decoded data and comparing strings.
Security Considerations
This base 64 decoding bug doesn't appear to be a structural/architectural/security concern since Coze uses the UTF-8 encoding of the string for signing and verification, however it is a interesting problem that should be known when working with RFC base 64.  Concerning specifically replay attacks, signatures are still not malleable as payloads are UTF-8 encoded and the signing operation is not base 64 aware.
If Coze used the base 64 representation directly, this would be a security concern and could result in reply attacks.
Notes
It should be obvious, but this situation also applies to the URI unsafe alphabet and messages with base 64 padding, which all are interpreted as the same bytes.  (My conversion tool only has "base64 as an input and not the various permutations since all variations can be known (or is irrelevant) and results in the sames decoded binary payload.
RFC 4648
I currently have errata open on one of the relevant sections.
I'm going to implement a non-canonical encoding check on Go and JS Coze.
See also the Go base64 package.
Go's base64 ignores carriage return and new line, so it is malleable, but JSON unmarshal does not, making Go Coze non-malleable.  https://go.dev/play/p/X0J74F0zWVf  See also the new line test in base64_test.go

Go has an issue for this that is currently frozen (and I might re-open if this doesn't ping 'em)
https://github.com/golang/go/issues/15656

Fixed by 98e7068.
Coze JS has an issue for this.

Also just discovered a 2022 paper on the issue: https://dl.acm.org/doi/10.1145/3488932.3527284


Can't connect consumer to Kafka with SSL

Here's my consumer. Whenever I try to connect, I get NoKafkaConnectionError: Kafka server has closed connection. I am using the same credentials on my ruby producer, and it connects properly. Guessing I am doing something wrong.
const ROOT_PATH               = path.resolve(__dirname);
const KAFKA_TOPIC             = 'foo';
const KAFKA_CLIENT_CERT       = fs.readFileSync(path.join(ROOT_PATH, 'keys', 'service.cert')).toString('utf-8');
const KAFKA_CLIENT_CERT_KEY   = fs.readFileSync(path.join(ROOT_PATH, 'keys', 'service.key')).toString('utf-8');
const KAFKA_SERVER_CERT       = fs.readFileSync(path.join(ROOT_PATH, 'keys', 'ca.pem')).toString('utf-8');
const KAFKA_BROKERS           = ["kafka://******:20310"];
const KAFKA_CLIENT            = "js-test-client";

const consumer = new Kafka.SimpleConsumer({
  connectionString: KAFKA_BROKERS.join(','),
  idleTimeout: 250,
  clientId: KAFKA_CLIENT,
  ssl: {
    cert: KAFKA_CLIENT_CERT,
    key:  KAFKA_CLIENT_CERT_KEY,
    ca:   KAFKA_SERVER_CERT,
  }
});

I tried reducing the issue down. This test case connects to my server:
const socket = tls.connect(20310, '*******', {
  cert: KAFKA_CLIENT_CERT,
  key:  KAFKA_CLIENT_CERT_KEY,
  ca:   KAFKA_SERVER_CERT,
  rejectUnauthorized: false
}, function() {
  console.log('connected');
});

socket.on('end', function () {
  console.log('Kafka server has closed connection');
});
socket.on('error', function (err) {
  console.log(err.toString());
});
socket.on('data', function(data){
  console.log(data);
});

Well, nevermind. I had 2.x installed. Sorry!


Add filmweb_watchlist input plugin

Motivation for changes:
I want to be able to use my filmweb watch list as an input for Flexget.
Requirements
pip install pyfilmweb==<IP_ADDRESS>

Config usage if relevant (new plugin or updated schema):
tasks:
  populate-movie-list:
    filmweb_watchlist:
      login: 'username/email'
      password: 'password'
      min_star: 5
    accept_all: yes

Log and/or tests output (preferably both):
2017-12-08 16:38 VERBOSE  filmweb_watchlist populate-movie-list Retrieving filmweb watch list for user: user
2017-12-08 16:38 VERBOSE  filmweb_watchlist populate-movie-list Logging as user
2017-12-08 16:38 VERBOSE  filmweb_watchlist populate-movie-list Filmweb list contains 385 items
2017-12-08 16:38 VERBOSE  details       populate-movie-list Produced 3 entries.
2017-12-08 16:38 VERBOSE  task          populate-movie-list ACCEPTED: `Movie #1 (2017)` by accept_all plugin
2017-12-08 16:38 VERBOSE  task          populate-movie-list ACCEPTED: `Movie #2 (2017)` by accept_all plugin
2017-12-08 16:38 VERBOSE  task          populate-movie-list ACCEPTED: `Movie #3 (2017)` by accept_all plugin
2017-12-08 16:38 VERBOSE  details       populate-movie-list Summary - Accepted: 3 (Rejected: 0 Undecided: 0 Failed: 0)

To Do:

Fix crash one some movies in Python2 due to bug in library that I am using: https://github.com/lopezloo/pyfilmweb/issues/2
Supports only film types of items on filmweb watchlist. Might add series handling in future.

Any plans on merging?

Is there anything I can do to make this go into develop?  @cvium @liiight


"Add ML-Based Recommendations for Related Products Based on User Selections"

Description:
This PR transforms the search feature by implementing ML-based recommendations. Previously, search results only displayed items that matched the beginning letters of the query. Now, with ML integration, search results suggest related products based on user selection, item type, and category, creating a more personalized experience.
Highlights
Enhanced Search: Upgrades search from exact matches to ML-driven recommendations.
Relevant Suggestions: Provides related products to improve user engagement and discovery.
gssoc-ext, hacktoberfest-accepted, Level 3
Issue Reference: #137 opened by @Renukanarayan

This PR transforms the search feature by implementing ML-based recommendations. Previously, search results only displayed items that matched the beginning letters of the query. Now, with ML integration, search results suggest related products based on user selection, item type, and category, creating a more personalized experience.

How to run the recommendation search engine:
1.Navigate to recommendation_service
2.install needed libraries
Command:- pip install Flask flask-cors pandas scikit-learn
3. Run the file
Command:- python recommendation_service.py

@Renukanarayan  I'll review the code soon and let you know in few days

@Minav karia     Don't I have chance to be on leaderboard
On Sun, 10 Nov 2024, 3:55 pm Minav Karia, @.***> wrote:

@Renukanarayan https://github.com/Renukanarayan I'll review the code
soon and let you know in few days
—
Reply to this email directly, view it on GitHub
https://github.com/MinavKaria/Ratna-Supermarket/pull/199#issuecomment-2466676530,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BEXHTRBVQRTE3YYDK7KA52LZ74YDFAVCNFSM6AAAAABRPNQDJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWGY3TMNJTGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

As a part of GSSOC i have done my contribution.Could you confirm that am i eligible for certification

@Renukanarayan Sorry Contributor, We aren't using the python backend as of now, Thank you for your contribution. Feel free to open a new issue if you find any.

As of until,you used python right can I know what key changes made and other languages you get involved with

@Renukanarayan Hey contributor , currently the whole project is working on MERN stack , I'll contact you if we'll need any help in python development.

Ok, thanks for the update.
On Thu, 28 Nov 2024, 8:46 am Minav Karia, @.***> wrote:

@Renukanarayan https://github.com/Renukanarayan Hey contributor ,
currently the whole project is working on MERN stack , I'll contact you if
we'll need any help in python development.
—
Reply to this email directly, view it on GitHub
https://github.com/MinavKaria/Ratna-Supermarket/pull/199#issuecomment-2505185311,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BEXHTREY6T5X6HEMJLCWM7T2C2DKBAVCNFSM6AAAAABRPNQDJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBVGE4DKMZRGE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Buffer Request Pane

Would be nice to be able to scroll through previous requests, or support having multiple requests on-screen at once.
Useful when debugging something that sends multiple different payloads - can just point them all at httplab and understand the flow.

having an scroll seems great, but not sure about the UI, having multiple requests on-screen at once may be overkill, I'm thinking on a popup which displays them.
What do you mean with multiple different payloads?

For example an android library that sends 5-6 different http calls. I want to send them all to httplab and inspect them.

how would you correlate them? by souece host perhaps? or you dont need to
On Wed, Mar 1, 2017, 13:45 SikhNerd<EMAIL_ADDRESS>wrote:

For example an android library that sends 5-6 different http calls. I want
to send them all to httplab and inspect them.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/gchaincl/httplab/issues/6#issuecomment-283396568, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABOoebgZ3Z-Glv36S5Y4O24R9Zvg7bHaks5rhaC4gaJpZM4MPS_1
.

Don't particularly need to, because I'd review everything that was in httplab, or I'd only be sending the things I cared about, so I'd just page through all of them.

@SikhNerd mind to take a look at request-scroll branch, PgUp and PgDown will go back in time to inspect previous request

@gchaincl Tested and works as advertised, I really like how it behaves when I've scrolled to a particular request and new requests are still coming in 👍

Cool!, I'll merge it


Integrate MKLDNN Conv1d and support 3d layout

Description
This PR aims to integrate MKLDNN Conv1d and enable 3d layout for Conv and Activation.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] MKLDNN Conv1d
[x] MKLDNN 3d layout for Conv and Activation

@pengzhao-intel @TaoLv

@mxnet-label-bot add [MKLDNN, Operator, pr-awaiting-review]

@TaoLv address Tao's comments. These changes are already covered by test_operator:test_convolution_grouping and test_operator:test_activation. I check if they run into MKL-DNN kernel by checking the mkldnn_verbose.

Do we have unit test for 1D Convolution without grouping? Please also make sure that this change works well for quantized Convolution (which I think doesn't support 1D yet).

Address Tao's comments. I've skip conv1d convolution on both C level and Python level. @ZhennanQin Please help take a look. Maybe skip all non-4d data layout in quantization.py is not a good choice.

LGTM.

Seems there was problem with CI. Do you mind re-triggering it with an empty commit? @xinyu-intel
Ping @zheng-da for review. Thank you.

@pengzhao-intel Conv1d will fall back to native cpu implement.
100 iterations total time(ms) on Xeon Skylake 8180 1 socket:

shape
before opt
after opt
speedup

(1,256,200)
715.47
73.88
9.68x

(1,1024,512)
1970.15
101.06
19.49x

(64,1024,512)
131312.48
4196.24
31.29x

I've add 1d,3d,4d data shape to activation test. Regarding quantized conv, it will now return error when the data shape is 3d and users should exclude this layer:
  CHECK_EQ(param.full_conv_param.conv_param.kernel.ndim(), 2U)
      << "MKL-DNN only supports quantized conv2d.";

@zheng-da Please take a look. Thanks!

@xinyu-intel Thank you for the contribution. Now merging.

I noticed a very nice improvement with this change.
So, thank you.
Still, for my use-case: conv1d, small batch size, small channel dimension, long sequence length,
I don't see much improvement with more cores added to the computations.
The simplified snippet to reproduce (conv1d.py):
import mxnet as mx
from mxnet import gluon, nd

from mxnet import profiler
profiler.set_config(profile_all=True, aggregate_stats=True, filename='profile_output.json')

channels = 64

net = gluon.nn.Sequential()

conv = gluon.nn.Conv1D(channels, 4, padding=1)
act = gluon.nn.Activation('sigmoid')

for i in range(3):
    net.add(conv)
    net.add(act)

net.initialize()

data = nd.random.uniform(shape=(1, channels, 2**16))

# Warm-up
y = net(data)
nd.waitall()

profiler.set_state('run')
for i in range(10):
    y = net(data)
    nd.waitall()
profiler.set_state('stop')

print(profiler.dumps())

When run on a host with a lot of cores (AWS c4.8xlarge) results in:
$ OMP_NUM_THREADS=1 python conv1d.py | grep "Convolution\|Activation"
Activation                             60         244.8700           3.3960           9.7510           4.0812
Convolution                            60        1648.7010          24.9280          40.6520          27.4783
$ OMP_NUM_THREADS=2 python conv1d.py | grep "Convolution\|Activation"
Activation                             60         127.4460           1.6600           5.4070           2.1241
Convolution                            60         866.8680          12.6670          22.9810          14.4478
$ OMP_NUM_THREADS=4 python conv1d.py | grep "Convolution\|Activation"
Activation                             60          65.3190           0.8940           2.9280           1.0886
Convolution                            60         854.2900          12.6230          20.3230          14.2382

There is no improvement when number of threads is increased to 4, or more.
Playing more with this example, for higher 'channels' value, it starts to be a little better parallelizable.
So, it seems the parallelization is done only per a single sequence "point". Is it the case?
But, it seems quite natural to parallelize also along the sequence, especially when it is long - different threads doing a different part of the sequence.
Then, parallelization should scale linearly with number of threads.
Isn't it done like that?
Bartosz

Thanks @bputrycz really thanks for trying the new MKLDNN API and give us the very useful feedback.
Nice analysis and reproducible examples. I will contact Intel MKL-DNN team to see how to fix it.
In a short term, you can try to launch multiple instances (processor) and each one binds to 2/4 cores to get the max throughput in case this is the inference case.

@TaoLv is following this issue and will back to you with more details soon.

@bputrycz Cannot reproduce the problem. The code snippet you provided scales well on my machine:
$ OMP_NUM_THREADS=1 python conv1d.py | grep "Convolution\|Activation"
Activation                             60         183.5660           2.6600           6.1490           3.0594
Convolution                            60        1047.5291          14.2060          26.2510          17.4588
$
$ OMP_NUM_THREADS=2 python conv1d.py | grep "Convolution\|Activation"
Activation                             60         103.8990           1.4330           3.5280           1.7316
Convolution                            60         550.4830           7.5440          13.9890           9.1747
$
$ OMP_NUM_THREADS=4 python conv1d.py | grep "Convolution\|Activation"
Activation                             60          57.5180           0.7640           2.4380           0.9586
Convolution                            60         290.6110           3.8830           7.8330           4.8435
$
$ OMP_NUM_THREADS=8 python conv1d.py | grep "Convolution\|Activation"
Activation                             60          39.8030           0.4470           1.8200           0.6634
Convolution                            60         179.9880           2.2860           5.4140           2.9998

Have you ever tried the cpu affinity before run multi-thread case?
export KMP_AFFINITY=granularity=fine,compact

Ummm, just notice that you're using c4.8xlarge which I think have no AVX512. Will have another try and come back to you later.

Confirmed this problem exists on machine without AVX512 as threading optimization for 1D Convolution is made for AVX512 only. Would you mind having a try on AWS c5? @bputrycz

Yes. I confirm.
It scales much better on AWS c5.
Thank you very much.

Yes. I confirm.
It scales much better on AWS c5.
Thank you very much.

It's good to see the problem can be resolved on AWS c5.
Feel free to ping us if you have any questions or issues :)
We will document this behavior in MKLDNN README @xinyu-intel

@bputrycz Also feel free to let me know if the performance on c4 is critical for you.

@TaoLv Performance on c4 is not critical for me, as for now.


Add support for notifying testers in method upload_and_release

Hello. Method upload_and_release under the hood has notify_testers = false, so when using it, tests don't get emails about new release. Could you extend the contact of this method?

Released as version 2.0.2.


Binding shift doesn't work

bind <S-left> seek -5 doesn't work. I.e. Shift <- to seek backwards.
The debug-log doesn't show anything out of the ordinary.

@jottr, please try with the latest master commit. Major parts of the key binding system has been refactored to support key modifiers such as shift and alt. See the docs at
https://github.com/ambientsound/pms/blob/master/config.md#bind.
Unsure about specific key availability, YMMV and I'd appreciate to know what's working and what's not.

@jottr, have you had a chance to test these changes yet?

Closing this issue, feel free to reopen if you have any comments or further problems.


Service not showing up in drop-down box when accessing Release Planner app

Service is not showing up in the drop-down menu.  Since this is a new service, please see email that has been forwarded, message in engagement teams channel, and access service tree link for additional details.

Top level service for the products - https://microsoftservicetree.com/services/ae53b53f-9347-4198-b9b7-ff4b8228d6a7
All of the products dated for 2023 are in scope for APEX.

Replied in teams.


Replaced deprecated app.session_cookie_name with app.config["SESSION_COOKIE_NAME"].

@rayluo It seems this breaks for anyone who is using Flask < 2.3 ?

Welcome back, @fengsp !

@rayluo It seems this breaks for anyone who is using Flask < 2.3 ?

Not necessarily. Flask-session itself uses semantic versioning. We can have flask-session 0.4.x contain working with Flask < 2.3, and have flask-session 0.5+ using Flask >= 2.2.

@rayluo It seems this breaks for anyone who is using Flask < 2.3 ?

I do not think this is an issue.  When we have:

Flask-Session 0.4.x: install_requires: Flask >=0.8, <2.3
Flask-Session 0.5.0: install_requires: Flask >=2.2

People running Flask<2.3 can still use Flask-Session==0.4.x nicely.

Flask-Session 0.5.0 is now available.


Update repositories with approval rules

I've added the aproval rules to the stm32_sensor_module repo
We still need to add them to other repos in the project.


feat: get cutting edge github cards from our project to use in the LP home section

Using the GitHub cards in the home section is perfect for displaying what the app is about!

Do some polishing to the best cards you can find in our GitHub project and use them in the landing page to attract users so that they will know what this is about
Change these images that are very ugly into something beautiful like those strong pink images that are also in the Figma followed by the example below:
Change this:

To this:

Bumping this @andressa-cabral

closing this as duplicated


Move concepts to oeo-shared

Summary of the discussion
project
quantity value
technology
transformation
good
good role
study report
methodology
import
export
process attribute
organisation
funder
sponsor
still missing:
study
Type of change (CHANGELOG.md)
Added

Added a new class #

Updated

Updated a definition #

Removed

Removed a broken link #

Workflow checklist
Automation
Closes #
PR-Assignee

[ ] 🐙 Follow the Pull Request Workflow
[ ] 📝 Update the CHANGELOG.md
[ ] 📙 Add #'s to term tracker item

Reviewer

[ ] 🐙 Follow the Reviewer Guide
[ ] 🐙 Provided feedback and show sufficient appreciation for the work done

With study I had the problem that I couldn't find cannot find covers some 'analysis scope' axiom in omn file.
I can merge and improve earliest Friday late afternoon FYI

With study I had the problem that I couldn't find covers some 'analysis scope' axiom in file.

This axiom is currently implemented in oeo-model.

5a7b12f organisation 'has role' some 'organisation role' should stay in oeo-shared-axioms and can be deleted from oeo-shared.
seems to cause the problem

I don't think it makes sense to have organisation and organisation role in different modules, therefore I move it to oeo-shared too.


Fix for Neovim/Vim job control function

Am I mistaken or this replaces Vim support with Neovim support? there is no jobstart() function in Vim.

Assuming that in Neovim the job feature is called the same, something like this:
  if has('job')
    " We can be a bit slow on big files, this should mask it.
    if has('nvim')
      " Neovim
      call jobstart(yaifa#magic(a:bufnr))
    else
      " Vim
      call job_start(yaifa#magic(a:bufnr))
    endif
  else
    call yaifa#magic(a:bufnr)
  endif

My bad. It seemed to work in both Vim and Neovim with this change but I'm not sure if it was using job control in Vim.
The current issue was that Neovim complained about no method named job_start.
I think the code in your reply is the correct fix for this.


Could not reach any registry endpoint

While I'm trying to pull from docker hub on a Raspberry Pi Zero I'm getting the follow message.
What could this be?
$docker pull alpine
Pulling repository alpine
docker 2016/02/29 15:33:02 Could not reach any registry endpoint

This is a question for the docker engine team.  I would first ask in #docker-dev and if there is a bug, create an issue in docker/docker.
If you can ping docker.io and curl https://registry-1.docker.io/v2/, then you will have eliminated network, dns and certificate problems.


Minimum deploy target

Hi, I was worrying if there's a way to use this calendar for lower versions of iOS such as 11.4 or at least 12 instead of 13 (even though the major part of iOS user are above 13, there are some still in 12.
Thanks beforehand.

Nope. iOS 13 > only. I wouldn’t worry about 12 by it’s like 6% of users on that


clear

With Django 1.8.1 and Python 3.4 I get the following error when starting an application:
from django.db.models.related import RelatedObject
ImportError: No module named 'django.db.models.related'

I encountered the same problem with django 1.8.2 and python 2.7.5.


Test including setters from Module

It's currently impossible to extract a setter into a module.

Here's how it works.
http://trailblazer.to/gems/reform/api.html#forms-in-modules
http://trailblazer.to/newsletter/2016-march.html


Master

I identified two more problems with pure pursuit:

the lap statistics crashed immediately because it didn't receive the second argument (number_laps),
the find_nearest_goal had an index error when the car was nearing the end of the lap.

The fixes to both bugs were really simple so here's the PR.

Changes made!


ioncube extensions

Hi
how to use ioncube extensions on macos x?

Sorry, I will not add that extension in this tap. Please reach out to ioncube for that.

Thank you for your answer .Where is the extension path to add ioncube?


set CSharp Controller Settings by json in NSwagStudio

As a developer
I want to be able to set CSharp Controller Settings by json in NSwagStudio
so that I am able to ensure my preferences are saved.

Which ones are missing?

I'm looking for the ability to upload the json representation of the CSharpController Settings on the NSwagStudio

You can save the config from NSwagStudio - it contains all the properties. But its not exactly the same as the settings class.


Kineticist Weapon Infusion roll options no longer work

Probably related to the recent change (the one that modified their domain) but both roll options are currently doing nothing.

The one that modified their domain?


Update "Data Sources" page in documentation

This PR updates the "Data Sources" page in the documentation (data.md).
As I don't have a met background, I thought it might be prudent for somebody with a met background to check my work. @nicholasloveday @BethEbert - if either or both of you are happy to take a look, that would be much appreciated.
You can see the updated Data Sources page here: https://scores.readthedocs.io/en/228-documentation-testing-branch/data.html
(quick note from Tennessee - the link above will also now show an alert that you may be reading an old version of the documentation. In this case, just close the box, ignore the message, and do the review on the linked version)
Changes made:

I added that scores is used with xarray and pandas, as that was not mentioned previously on this page.
I tried to retain the existing information, while improving clarity.
I added new headers and header levels, and reorganised some of the information
I made all existing URLs hyperlinks
I added some links
I updated some links that no longer worked, replaced one dataset link with a DOI (that resolves to the same page as the initial link), and replaced the link for WeatherBench to WeatherBench 2 (as far as I can tell, WeatherBench 2 still includes ERA 5 and supplants WeatherBench - but I didn't compare the two in detail, so I cannot guarantee this).
I modified the capitalisation of headers for improved consistency with the rest of the documentation.

I also have two questions that I have included as code comments (either see below or "Files changed")

I have read through it and think it's a good change, and I'm happy with the page as-is. Getting a few different perspectives on this one makes sense to me to make sure it can be easily understood be several people and also makes sense for those in the field.

Hi Steph and Tennessee,
I took the easy (for me) option and put some comments into the PDF version you sent before making changes. I think you may have fixed a few typos, but there are a few other comments to consider.
The data page is looking good!
Beth

From: Stephanie Chong @.>
Sent: Sunday, 16 June 2024 15:23
To: nci/scores @.>
Cc: Beth Ebert @.>; Mention @.>
Subject: Re: [nci/scores] Update "Data Sources" page in documentation (PR #544)
@Steph-Chong commented on this pull request.

In docs/data.mdhttps://github.com/nci/scores/pull/544#discussion_r1641616586:

+### Software for Accessing Data

Should WeatherBench 2 also be added to this section?
—
Reply to this email directly, view it on GitHubhttps://github.com/nci/scores/pull/544#pullrequestreview-2121091267, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGMQHAPBXXET7SACNC3RMATZHUOOJAVCNFSM6AAAAABJLPTMPKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCMRRGA4TCMRWG4.
You are receiving this because you were mentioned.Message ID: @.***>

Hi Steph and Tennessee, I took the easy (for me) option and put some comments into the PDF version you sent before making changes. I think you may have fixed a few typos, but there are a few other comments to consider. The data page is looking good! Beth

Thanks very much @BethEbert. Unfortunately neither Tennessee nor I can find the PDF you added comments to - so we can't see your feedback.
Tennessee suggested if you are happy to, you could either email him your feedback, or you could post your feedback as comments here on GitHub.
When I looked at the page again earlier today, as well as fixing a few typos, I reordered the sections (again) and also added a sentence in one section - so there were a few further changes I made earlier today.
This PDF shows the page in its current form:
Data Sources 16.6.24.pdf

Hi again Steph and Tennessee,
Not sure why the PDF attachment didn't come through. Here it is again - hopefully this time successful. Please don't feel obligated to use any of it.
Beth

From: Stephanie Chong<EMAIL_ADDRESS>Sent: Sunday, 16 June 2024 17:23
To: nci/scores<EMAIL_ADDRESS>Cc: Beth Ebert<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [nci/scores] Update "Data Sources" page in documentation (PR #544)
Hi Steph and Tennessee, I took the easy (for me) option and put some comments into the PDF version you sent before making changes. I think you may have fixed a few typos, but there are a few other comments to consider. The data page is looking good! Beth
Thanks very much @BethEberthttps://github.com/BethEbert. Unfortunately neither Tennessee nor I can find the PDF you added comments to - so we can't see your feedback.
Tennessee suggested if you are happy to, you could either email him your feedback, or you could post your feedback as comments here on GitHub.
When I looked at the page again earlier today, as well as fixing a few typos, I reordered the sections (again) and also added a sentence in one section - so there were a few further changes I made earlier today.
This PDF shows the page in its current form:
Data Sources 16.6.24.pdfhttps://github.com/user-attachments/files/15856499/Data.Sources.16.6.24.pdf

Reply to this email directly, view it on GitHubhttps://github.com/nci/scores/pull/544#issuecomment-2171124593, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGMQHAOUQWAKBDGLW62LGNLZHU4QBAVCNFSM6AAAAABJLPTMPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRGEZDINJZGM.
You are receiving this because you were mentioned.

Hi again Steph and Tennessee, Not sure why the PDF attachment didn't come through. Here it is again - hopefully this time successful. Please don't feel obligated to use any of it. Beth

Thanks for the helpful feedback Beth. When I get a moment, I will update the page to incorporate your feedback.

I have made further updates to:

Incorporate feedback from Beth
Change HDF5 link to their GitHub
Add WeatherBench 2 to the software packages section
Changed one "data set" to "dataset" for consistency with the rest of the page.

When I built it locally, it rendered correctly in readthedocs.
I intend to read through it again later, as I find I sometimes pick up missed typos etc. when I reread my work after a break. But if anyone is keen to merge it before then, please feel free to do a check for any missed typos etc. (And of course, if anyone notices any mistakes, please do point them out).

There are two areas where I would particularly appreciate feedback:

WeatherBench 2: as I don't have a background in this area, it would be much appreciated if someone could please double check what I have written is accurate and/or if there is anything else that should be mentioned in this section.

The "Point-Based Data" subsection: this is the only sub-section in the "Datasets" section that doesn't include a brief description of what point-based observations are. I am guessing point-based observations are exactly what they sound like (observations taken an specific locations), so perhaps an explanation is unnecessary. But I wanted to raise it, in case (a) it would be preferable to provide a one sentence description and (b) if so, it would be helpful if someone could suggest a suitable sentence (otherwise I can try and come up with one, and seek feedback).

There are two areas where I would particularly appreciate feedback:

WeatherBench 2: as I don't have a background in this area, it would be much appreciated if someone could please double check what I have written is accurate and/or if there is anything else that should be mentioned in this section.
The "Point-Based Data" subsection: doesn't include a brief description of what point-based observations are. (The other "Datasets" subsections provide a brief description of what type of data is included in the dataset). I am guessing point-based observations are exactly what they sound like (observations taken at specific locations), so perhaps an explanation is unnecessary. But I wanted to raise it, in case (a) it would be preferable to provide a one sentence description and (b) if so, it would be helpful if someone could suggest a suitable sentence (otherwise I can try and come up with one, and seek feedback).

I'm not even sure if weatherbench2 allows us to retrieve data from them. I'd just leave it off for now unless we definitely know that it allows us to retrieve data.
You can always say something like "point based observations (e.g., weather stations or buoys)"

There are two areas where I would particularly appreciate feedback:

WeatherBench 2: as I don't have a background in this area, it would be much appreciated if someone could please double check what I have written is accurate and/or if there is anything else that should be mentioned in this section.
The "Point-Based Data" subsection: doesn't include a brief description of what point-based observations are. (The other "Datasets" subsections provide a brief description of what type of data is included in the dataset). I am guessing point-based observations are exactly what they sound like (observations taken at specific locations), so perhaps an explanation is unnecessary. But I wanted to raise it, in case (a) it would be preferable to provide a one sentence description and (b) if so, it would be helpful if someone could suggest a suitable sentence (otherwise I can try and come up with one, and seek feedback).

1. I'm not even sure if weatherbench2 allows us to retrieve data from them. I'd just leave it off for now unless we definitely know that it allows us to retrieve data.

I was under the impression you could, but perhaps I misunderstood?
https://weatherbench2.readthedocs.io/en/latest/data-guide.html#ground-truth-datasets
https://console.cloud.google.com/storage/browser/weatherbench2
https://weatherbench2.readthedocs.io/en/latest/data-guide.html#forecast-datasets

2. You can always say something like "point based observations (e.g., weather stations or buoys)"

Thanks for this suggestion.
The existing sentence says: "Point-based observations are shared routinely between countries for the purposes of weather modelling."
So perhaps I could modify it to something along the lines of: "Point-based observations (e.g. from weather stations or buoys) are shared routinely between countries for the purposes of weather modelling"?

Re.  Just let me know once that is resolved so I can update (or not) accordingly.

So perhaps I could modify it to something along the lines of: "Point-based observations (e.g. from weather stations or buoys) are shared routinely between countries for the purposes of weather modelling"?

That sounds good.
And yes, you're right. It does look like weatherbench2 allows you to access data (I haven't tested it out yet). I'm happy with what you've written about weatherbench2

I have:

added some extra info re. point-based observations (thanks @nicholasloveday),
in the WeatherBench 2 section, added a link to the datasets page in their docs (to make it easier for people who want to quickly locate info regarding their included datasets),
made a minor edit to remove some repetition in one sentence.

I didn't notice any typos etc. (famous last words...), so if others are happy, I think this is ready now.


Add 01node operator

Name - 01node
Short Description - High Quality Institutional Blockchain Validation and Staking
Ethereum operator address - 0xfdB7787Cb7ed6E0A9b3e3821C5B2Ca4333A1E24b
Validator consensus address - 36D2AFCDFAB19C464D1EBD198A4565E2A525F841

I've registered here : https://holesky.etherscan.io/address/0xa02C55a6306c859517A064fb34d48DFB773A4a52
according to docs.


Add packages for 2024 UW NASA Hackweek

Updating the conda environment.yml file to include more packages as requested at https://github.com/CryoInTheCloud/hub-image/issues/118.
Newly added:

hydroeval=0.1.0
itables=2.14
jupyter-sshd-proxy=0.2.0
py-xgboost=2.1.1 (cpu)
~- pytorch=2.3.1 (cpu)~
stackstac=0.5.1

Extensions that are added back since they have new compatible releases:

jupyter-offlinenotebook=0.3.1

Upgraded:

code-server from 4.16.1 to 4.23.1
snowexsql from 0.4.1 to 0.5.0 (so that we can get geopandas 1.0, xref https://github.com/CryoInTheCloud/hub-image/pull/121#discussion_r1697925958)
icepyx from 1.1.0 to 1.2.0

/condalock

/condalock

/condalock

Will leave this up for another day in case there are any other late additions. @scottyhq, you probably have a better grasp of what's needed across the 3 Hackweek streams, so I'll let you merge this in once you're happy (and ping @tsnow03 to update the hub image afterwards).

/condalock


3rd-party controller notifications

I'm trying to setup notifications from tf-controller, so I followed what is mentioned here
I'm not sure if this falls here, or better on tf-controller... but my guess is that I'm just misconfiguring something
I have checked the resources and they seem to contain the correct patches:
kubectl -n flux-system describe crd alerts.notification.toolkit.fluxcd.io
...
                    Kind:
                      Description:  Kind of the referent
                      Enum:
                        Bucket
                        GitRepository
                        Kustomization
                        HelmRelease
                        HelmChart
                        HelmRepository
                        ImageRepository
                        ImagePolicy
                        ImageUpdateAutomation
                        OCIRepository
                        Terraform
...

kubectl -n flux-system describe crd receivers.notification.toolkit.fluxcd.io
...
                    Kind:
                      Description:  Kind of the referent
                      Enum:
                        Bucket
                        GitRepository
                        Kustomization
                        HelmRelease
                        HelmChart
                        HelmRepository
                        ImageRepository
                        ImagePolicy
                        ImageUpdateAutomation
                        OCIRepository
                        Terraform
                      Type:  string
...

kubectl -n flux-system describe clusterrole crd-controller-flux-system
Name:                               crd-controller-flux-system
Labels:                             app.kubernetes.io/instance=flux-system
                                    app.kubernetes.io/part-of=flux
                                    app.kubernetes.io/version=v0.34.0
                                    kustomize.toolkit.fluxcd.io/name=flux-system
                                    kustomize.toolkit.fluxcd.io/namespace=flux-system
Annotations:                        PolicyRule:
  Resources                         Non-Resource URLs  Resource Names  Verbs
  ---------                         -----------------  --------------  -----
...
  *.infra.contrib.fluxcd.io         []                 []              [*]
...

My Alert specification is the following
---
apiVersion: notification.toolkit.fluxcd.io/v1beta1
kind: Provider
metadata:
  name: slack
  namespace: flux-system
spec:
  type: slack
  channel: general
  secretRef:
    name: slack-url
---
apiVersion: notification.toolkit.fluxcd.io/v1beta1
kind: Alert
metadata:
  name: flux-cd
  namespace: flux-system
spec:
  summary: "Flux CD"
  providerRef:
    name: slack
  eventSeverity: error
  eventSources:
    - kind: GitRepository
      name: '*'
    - kind: Kustomization
      name: '*'
    - kind: Terraform
      name: '*'

It works fine for GitRepositiory resources, but for Terraform resource I get no notification at all, and I don't see anything in the notification-controller logs, not even a mention whether a rule was not satisfied
Is there anything else I'm missing on the setup?

It seems to be the correct configuration to me. I did try the similar setup and it worked.
Maybe you would try specifying apiVersion for your event source?
apiVersion: notification.toolkit.fluxcd.io/v1beta1
kind: Alert
metadata:
  name: terraform-slack
  namespace: default
spec:
  providerRef:
    name: slack
  eventSeverity: info
  eventSources:
    - apiVersion: infra.contrib.fluxcd.io/v1alpha1
      kind: Terraform
      name: '*'

Hey @chanwit Thanks for answering very quickly
I have tried adding the apiVersion, still no success:
The way I'm testing it is changing the Terraform path to an invalid path
Then I see it on the tf-controller logs:
{"level":"info","ts":"2023-01-17T19:18:09.392Z","msg":"clean up dir: ok","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"saas-github","namespace":"flux-system"},"namespace":"flux-system","name":"saas-github","reconcileID":"d0f5928b-2c40-4581-8553-345180873591"}
{"level":"error","ts":"2023-01-17T19:18:09.415Z","msg":"Reconciliation failed after 15.440494373s, next try in 2h0m0s","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"saas-github","namespace":"flux-system"},"namespace":"flux-system","name":"saas-github","reconcileID":"d0f5928b-2c40-4581-8553-345180873591","revision":"master/bfca0740f9f0f164f9cc7ab86a29b7cad7cbe65d","error":"rpc error: code = Unknown desc = terraform path not found: stat /tmp/flux-system-saas-github/terraform/xsaas/github: no such file or directory"}

Which is what I expected, however, the notification-controller doesn't seem aware of this error at all
Is there a way that I can maybe debug who should be sending the data to the notification-controller?

My next guess would be similar to your.
tf-controller needs the url of the notification controller and posts copies of events there.

Found the issue, I'm installing it manually using the manifest, not a helm chart
And it seems that the events-addr has only a default value when using the Helm Chart
So I had to manually add this to the list of arguments:
--events-addr=http://notification-controller.flux-system.svc.cluster.local.

I'm glad it worked for you now. Shall we close this issue?

ack. will address it.


Use StreamField to define form fields

Using a StreamField would allow for more flexibility and provide a more suitable interface for each respective field type.
Each field would be a block, which would also make it possible to add other kinds of content between fields (which has been a use case that has come up for us).

I'm closing this issue, because the project is now deprecated and we are not planning to add any new features. There are some related issues in the Wagtail itself:

https://github.com/wagtail/wagtail/issues/4485
https://github.com/wagtail/wagtail/issues/1564


ReserveCalifornia does not detect available campsites

Describe the bug
ReserveCalifornia shows 0 availability for me
Original Camply Command (with --debug)
$ camply --debug --provider ReserveCalifornia campsites --rec-area 726 --start-date 2024-04-29 --end-date 2024-04-30
[2024-04-25 08:45:29] CAMPLY   camply, the campsite finder ⛺
[2024-04-25 08:45:29] DEBUG    Setting up camply debugging
[2024-04-25 08:45:29] DEBUG    Camply Version: 0.32.2
[2024-04-25 08:45:29] DEBUG    Python Version: 3.10.12
[2024-04-25 08:45:29] DEBUG    Platform: linux
[2024-04-25 08:45:29] INFO     Using Camply Provider: "ReserveCalifornia"
[2024-04-25 08:45:29] INFO     1 booking nights selected for search, ranging from 2024-04-29 to 2024-04-29
[2024-04-25 08:45:29] INFO     Searching across 3 campgrounds
[2024-04-25 08:45:29] INFO         ⛰  Sunset SB (#726) - 🏕  Pines Hollow and Dunes Camp (Sites 38 – 90) (#734)
[2024-04-25 08:45:29] INFO         ⛰  Sunset SB (#726) - 🏕  Sunset Group Area (#735)
[2024-04-25 08:45:29] INFO         ⛰  Sunset SB (#726) - 🏕  South Camp (sites 1-37) (#737)
[2024-04-25 08:45:29] INFO     Searching Pines Hollow and Dunes Camp (Sites 38 – 90), Sunset SB (734) for availability: April, 2024
[2024-04-25 08:45:29] DEBUG    Starting new HTTPS connection (1): calirdr.usedirect.com:443
[2024-04-25 08:45:29] DEBUG    https://calirdr.usedirect.com:443 "POST /rdr/rdr/search/grid HTTP/1.1" 200 None
[2024-04-25 08:45:30] INFO             ❌       0 total sites found in month of April
[2024-04-25 08:45:30] INFO     Searching Sunset Group Area, Sunset SB (735) for availability: April, 2024
[2024-04-25 08:45:30] DEBUG    https://calirdr.usedirect.com:443 "POST /rdr/rdr/search/grid HTTP/1.1" 200 None
[2024-04-25 08:45:30] INFO             ❌       0 total sites found in month of April
[2024-04-25 08:45:30] INFO     Searching South Camp (sites 1-37), Sunset SB (737) for availability: April, 2024
[2024-04-25 08:45:31] DEBUG    https://calirdr.usedirect.com:443 "POST /rdr/rdr/search/grid HTTP/1.1" 200 None
[2024-04-25 08:45:31] INFO             ❌       0 total sites found in month of April
[2024-04-25 08:45:31] INFO     ❌ ❌ ❌ ❌ 0 Reservable Campsites Matching Search Preferences
[2024-04-25 08:45:31] CAMPLY   Exiting camply 👋
vasso@py:~$

Expected behavior
The Reserve California shows 44 available sites for the date/campground in question.
Console Output (with --debug)
$camply --version
camply, version 0.32.2

Additional context
< Add any other context about the problem here. >

Dang, confirmed this on my end as well. I will dig in to see what I can figure out here.

Turns out we were giving too early of a startDate for UseDirect.
Tested the following command on main vs the bugfix branch:
python -m camply \
  --debug \
  --provider ReserveCalifornia \
  campsites \
  --campground 737 \
  --start-date 2024-04-29 \
  --end-date 2024-04-30

❯ python -m camply --debug --provider ReserveCalifornia campsites --rec-area 726 --start-date 2024-04-29 --end-date 2024-04-30
[2024-04-25 18:42:42] CAMPLY   camply, the campsite finder ⛺
[2024-04-25 18:42:42] DEBUG    Setting up camply debugging
[2024-04-25 18:42:42] DEBUG    Camply Version: 0.32.2
[2024-04-25 18:42:42] DEBUG    Python Version: 3.11.8
[2024-04-25 18:42:42] DEBUG    Platform: darwin
[2024-04-25 18:42:42] INFO     Using Camply Provider: "ReserveCalifornia"
[2024-04-25 18:42:42] INFO     1 booking nights selected for search, ranging from 2024-04-29 to 2024-04-29
[2024-04-25 18:42:42] INFO     Searching across 3 campgrounds
[2024-04-25 18:42:42] INFO         ⛰  Sunset SB (#726) - 🏕  Pines Hollow and Dunes Camp (Sites 38 – 90) (#734)
[2024-04-25 18:42:42] INFO         ⛰  Sunset SB (#726) - 🏕  Sunset Group Area (#735)
[2024-04-25 18:42:42] INFO         ⛰  Sunset SB (#726) - 🏕  South Camp (sites 1-37) (#737)
[2024-04-25 18:42:42] INFO     Searching Pines Hollow and Dunes Camp (Sites 38 – 90), Sunset SB (734) for availability: April, 2024
[2024-04-25 18:42:42] DEBUG    Starting new HTTPS connection (1): calirdr.usedirect.com:443
[2024-04-25 18:42:42] DEBUG    https://calirdr.usedirect.com:443 "POST /rdr/rdr/search/grid HTTP/1.1" 200 None
[2024-04-25 18:42:42] INFO             ⛺      100 total sites found in month of April
[2024-04-25 18:42:42] INFO     Searching Sunset Group Area, Sunset SB (735) for availability: April, 2024
[2024-04-25 18:42:43] DEBUG    https://calirdr.usedirect.com:443 "POST /rdr/rdr/search/grid HTTP/1.1" 200 None
[2024-04-25 18:42:43] INFO             ⛺      3 total sites found in month of April
[2024-04-25 18:42:43] INFO     Searching South Camp (sites 1-37), Sunset SB (737) for availability: April, 2024
[2024-04-25 18:42:44] DEBUG    https://calirdr.usedirect.com:443 "POST /rdr/rdr/search/grid HTTP/1.1" 200 None
[2024-04-25 18:42:44] INFO             ⛺      37 total sites found in month of April
[2024-04-25 18:42:44] INFO     ⛺ ⛺ ⛺ ⛺ 42 Reservable Campsites Matching Search Preferences
[2024-04-25 18:42:44] INFO     📅 Mon, April 29 🏕  42 sites
[2024-04-25 18:42:44] INFO             ⛰  Sunset SB  🏕  Pines Hollow and Dunes Camp (Sites 38 – 90): ⛺ 34 sites
[2024-04-25 18:42:44] INFO                     🔗 https://www.reservecalifornia.com/Web/Default.aspx#!park/726/734 (1 night)
[2024-04-25 18:42:44] INFO             ⛰  Sunset SB  🏕  South Camp (sites 1-37): ⛺ 7 sites
[2024-04-25 18:42:44] INFO                     🔗 https://www.reservecalifornia.com/Web/Default.aspx#!park/726/737 (1 night)
[2024-04-25 18:42:44] INFO             ⛰  Sunset SB  🏕  Sunset Group Area: ⛺ 1 sites
[2024-04-25 18:42:44] INFO                     🔗 https://www.reservecalifornia.com/Web/Default.aspx#!park/726/735 (1 night)
[2024-04-25 18:42:44] CAMPLY   Exiting camply 👋

:tada: This issue has been resolved in version 0.32.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Newest version: It stopped working with delayed data

If the data for the ionic-modal-select is not populated right away, but is is populated later with an ajax call the modal is not showing anything.
This worked in an earlier build.

before the searchbar

@crissi  thanks for reporting.
can you provide a codepen or something tho show the issue?

http://codepen.io/anon/pen/qbqKLr?editors=101
The value that is set to start with is set, but it does not change if I set new content... Also tried to use angular.copy.

@crissi should be working now


Conda install that works

Pin to working version of conda

For https://github.com/quantopian/trading_calendars/issues/58


Support Indirect ISR handling through zero page pointer address

This PR is to allow for user programs to define their own interrupt handling.  The mod is quite simple.

create a new ISR_SERVICE routine that simply jumps to an address indexed by a hard coded zero page address.  $04 is used for this .
Initialise the $04 pointer to point at the original ISR routine.
Update the vector for IRQ to point at ISR_SERVICE instead of ISR
Add some documentation to Readme and an example of how to use it in examples/irq.asm

I have been working on getting some kind of sound out of the BE6502.  The using_rom_lib example includes a beep routine.  The example should still work if you don't have anything hooked up for making noise.
If you do happen to own a piezo buzzer - go ahead and hook it up to PA0 and you will get some beeps when you press the buttons.

This is such a good idea! I have been using the Sixty5o2-bootloader for some time now but found it frustrating to be directed to using the NMI in the code I upload (I modified the vector in bootloader.asm, in the same fashion you did, but for NMI so I wouldn't mess with the bootloader itself).  So I really like this PR!
I noticed one minor detail in the updated readme that I think is incorrect. See the line here: https://github.com/janroesner/sixty5o2/pull/11/commits/a77de400d065b5a27b27c14a78c8c339fff7b322#diff-1550ec65ac92f65817fc28928dfef526912b5f52356ff43651369bae92f56031R222 . It should read $05 in order to accommodate both high and low byte of the address if I understand your code correctly.

This is such a good idea! I have been using the Sixty5o2-bootloader for some time now but found it frustrating to be directed to using the NMI in the code I upload (I modified the vector in bootloader.asm, in the same fashion you did, but for NMI so I wouldn't mess with the bootloader itself). So I really like this PR!
It should read $05 in order to accommodate both high and low byte of the address if I understand your code correctly.

No, 6502 is little endian so addresses are read low byte first. The jump instruction at the IRQ vector in bootloader is an indirect zero page jump. You must point it at the LSB in zero page. I have committed a working example with this PR. Try it out.

On reset the bootloader stores its own interrupt address (i.e. the value of the label "ISR") in bytes $04 and $05. So my point was that the Readme also should mention that $05 is used by the bootloader internally. As I said, it is a minor detail but has the potential to be confusing if not mentioned.
By the way, I cloned it and gave it a try. It works like a charm!

Ah ok. I'll make the clarification and push a new commit.

@linuxplayground David, that's awesome. I always wanted to get that fixed. I think there is another way to solve it, and Ben's interrupt videos point to that ... but I'll check the PR on the weekend and merge it asap. Thanks a lot!


IntelliSense doesn't work

Importing the library in another project doesn't make IntelliSense work

My mistake. I didn't use it properly


[Question] OrderBy does not work with nullable navigation properties

OrderBy  works fine on non nullable navigation properties but if navigation property is nullable it doesn't work
System.Linq.Dynamic.Core.Parser.ExpressionParser.ParseArgumentList() in ExpressionParser.cs, line 1851
list = list.AsQueryable().OrderBy("site.title  asc" ).ToList();
site is nullable navigation property

Hello @khallid-itdevtech ,
Do you think you could provide a project sample with this issue?
It will help my developer investigate the issue more efficiently.
We already tried once but everything was working, so we might miss something.
We now always ask for a project sample even if the issue is easy to reproduce. As a free product, we must find some way to save time to offer an overall better experience for everyone and release fixes faster.
You can send it to<EMAIL_ADDRESS>if you need to keep the source private
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

I think the site is a nullable navigation property in this question. So you cannot use site.title asc because site is null.
The solution is to use the NullPropagating (np) function, so I think this code should solve the issue
list = list.AsQueryable().OrderBy("np(site.title) asc" ).ToList();

I was getting a different error when the site was null (Null reference exception which is was I'm expecting).
I guess we will see with his answer ;)

@StefH Thanks
list = list.AsQueryable().OrderBy("np(site.title) asc" ).ToList();
this works like charm.  👍


Dialog documentation should explain autofocus

Description
The dialog documentation doesn't mention autofocus. It seems to conflate autocomplete and autofocus, as well.
Browser/OS Environment
No response

Looks like it's just a typo, should be autofocus instead of autocomplete.
Do you mind sending a PR to update both the doc and the show() method's jsdoc?