How to render the template only if a sub-property of state is updated?

I am trying to update a template using a sub-property of another state.
"use strict";

const render = hyperHTML.bind(document.querySelector("root"));
const render2 = hyperHTML.bind(document.querySelector("root2"));
const render3 = hyperHTML.bind(document.querySelector("root3"));

// The usual state
const state = Introspected({
    catalogName: "Default Catalog",
    items: ["item1", "item2"]
}, s => {
    render`
${s.catalogName}

${s.items.map(item => `<li> ${item} </li>`)}

    `;
});

// Add another rendering to the same state
Introspected.observe(state, s => {
    render2`
Another ${s.catalogName}

${s.items.map(item => `<li> ${item} </li>`)}

    `;
});

setTimeout(() => {
    state.catalogName = "Default Catalog Updated"; // updating only root1, root2
}, 1000);

// Trying to add another rendering to a partial state,
// intending to update the template only if state.items change
Introspected.observe(state.items, s => {
    render3`
Other Catalog

${s.items.map(item => `<li> ${item} </li>`)}

    `;
});

setTimeout(() => {
    state.items.push("item3"); // updating root1, root2 and root3
}, 1000);

Live demo: https://plnkr.co/edit/IjZF042kY84L3fOGASe3?p=preview

The error is expected.
How to render root3 only if a sub-property of state is updated?

this ticket title is confusing, there's no JSON involved in here. Can you please edit it?

How to render root3 only if a sub-property of state is updated?

You keep ignoring the path variable.
The introspected is the state, and indeed you receive the state in the callback, not its items so ... stick with it.
Introspected.observe(state, (s, path) => {
    if (path[0] === 'items') {
      render3`
Other Catalog

${s.items.map(item => `<li> ${item} </li>`)}

      `;
    }
});

You are basically observing changes and acting only if anything inside the items property was changed, ignoring any other update outside such property.
You can easily automate this pattern, or propose an utility to do that.
I might consider simply accepting an intermediate path while observing.
// API example
Introspected.observe(state[, path?], callback);

// your case
Introspected.observe(state, ['items'], s => render`${s.items}`);

My concern about using path is the isolation of the component.
I am not convinced path resolves it.
That Introspected.observe is inside another component, different from the component, owner of the original state.
I would like it worked Introspected.observe(subState) and subState is the subset of the original state passed to the component.
Something like
// this is done in component 1
const subState = Introspected(state, ['items']);
...
// this is in component 2, receiving subState from component 1
Introspected.observe(subState, callback);

If items is updated, component1 and component2 are updated.

the problem is that if you change the subState in component 2, you want state in component 1 to be notified too.
Only way to go is to make subState trigger 2 callbacks, one before without being notified, and one for itself, branching out from the loop.
This might cause backfiring issues, in case the root component changes subState when it triggers ... hence my initial decision to have one source of truth on the root.
I'll think about it though, I see value in having this behavior too. I just want to avoid blowing too much the lib or its complexity for simpler use cases where you don't share a state between different components.

On a second thought and reading your last notes, I think the status quo (and using the path) is enough.
I would return again on these thoughts, when I completed the migration wit more insights.

I just want to avoid blowing too much the lib or its complexity for simpler use cases where you don't share a state between different components.

Totally agreed.

although ... there are still few stars and you are the most active user here, testing for real this project.
I am thinking to do a massive refactoring of this library in order to support subPath notifications.
At the end of the day, it is what I would expect too, passing through Introspected.observe(introspected.any.subPath, callback)
This lib is full of Proxy magic, why not making it fully wicked at this early stage?
Let's see how it goes.


LibPCRE crash with Invalid mem access on .match

In the wafalyzer shard we saw a crash when match is been feed image data.
To fix it we changed the code to use matches?
For us it fixed the issue but I guess this might blow in other peoples face, so maybe there is something deeper which needs to be done in STD lib level.
The full issue is here: https://github.com/NeuraLegion/wafalyzer/pull/6#issue-1079604779

Would you mind putting together a reproducible example?
The only significant difference between #matches? and #match is that the latter passes a pointer to assign capture values. Not sure if that could make a difference other than triggering different behaviour in the lib. So my guess would be rather a bug in libpcre than Crystal's bindings.

Might be completely unrelated, but I got a crash (out-of-bounds memory access) inside the match function from libpcre when running WebAssembly Crystal specifically in the mobile version of Chrome. I didn't investigate further, but most likely libpcre is invoking some C undefined behavior.


Dumping from a 3DS

Is it possible to dump the DSi NAND from a 3DS? I tried to launch the dumper with TWMenu++ in DSi mode but the message "This isn't a DSi!" is displayed.

Original DSi and 3DS DSi mode nands have different crypto, hence the refusal of the app to attempt to dump it.
You may use Godmode9 to do things with your DSi nand on 3DS (TWL Nand as it's officially called). There generally isn't any good reason to do that though.

OK I see.
In fact I would like to (legally) obtain a DSi NAND from my 3DS without having to buy a DSi for melonDS.
So I guess that's out of scope for this tool?

A DSi nand from 3DS is also fundamentally different from a stock DSi nand. It lacks tickets, system titles and files, etc, that melonDS would need to run. Even if it could dump that nand, it would be useless.

Oh OK, thanks for the clarification!


Suggest UI.Metrics and more UIElement methods to Warzone devs

Since it is the easiest to get debug info about font size, position etc. on the Website, the Mod library has been primarily made for the Website Version of Warzone.
For example, width of a char, spaces between two Elements in a HorizontalLayoutGroup, extra space needed for every Element down the UI hierarchy chain, etc. are easily to get via the Website with inspect Element. Unfortunately, the same cannot be said about the Standalone and Mobile Client. I'm therefore suggesting following (client only) UI APIs:

UI.Metrics.GetTextWidth(text): Takes a string as the argument and returns the width of text in pixels as a number. Depends on the   client type (website, standaloneclient, ...)  and the current font used. Suggested Resources:

https://docs.unity3d.com/ScriptReference/Font.GetCharacterInfo.html
https://stackoverflow.com/questions/118241/calculate-text-width-with-javascript/21015393#21015393

UI.Metrics.GetHorizontalGapSize: Constant number, the gap Size between 2 Elements in a HorizontalLayoutGroup. Will depend on the the client type (website, standaloneclient, ...) the game is being played on
UI.Metrics.GetVerticalGapSize: Constant number, the gap size between 2 Elements in a VerticalLayoutGroup. Will depend on the the client type the game is being played on
UI.Metrics.ExtraSpacePerChildLevel: Constant number. Every child of a parent gets moved left further (left: CSS-property) depending how deep down it is the ancestor tree. This constant reflects that

Definition of a [UIElement]:
Everything that can have a size, which can for example be set via [UIElement].SetPreferredWidth, for example a HorizontalLayoutGroup or Label.
API suggestions:

[UIElement].GetCurrentWidth(): Returns a number of how much width the element currently uses in pixels
[UIElement].GetAvailableWidth(): Returns a number of the max width the element can expand into in pixels
[UIElement].GetAvailableWidthLeft(): Returns a number of how much space there's left it still can expand into in pixels. Basically GetAvailableWidth() - GetCurrentWidth()
[UIElement].GetCurrentHeight(): Returns a number of how much height the element currently uses in pixels
[UIElement].GetAvailableHeight(): Returns a number of the max height the element can expand into in pixels
[UIElement].GetAvailableHeightLeft(): Returns a number of how much space there's left it still can expand into in pixels. Basically GetAvailableHeight() - GetCurrentHeight()
If any of the above cannot be calculated for whatever reason, it should return -1

appendum: There should also be a
[UIElement].GetAncestorCount()

I would like to see methods like GetDialogHeight and GetDialogWidth that would return the size of the dialog.
Using the setMaxSize function sets the window IF the given sizes fit on the device. This would at least allow us to create fixed menu's

appendum: There should also be a [UIElement].GetAncestorCount()
In theory this is already possible. I've written a small UI package, that keeps track of each element created. You can easily track how many children / ancestors an element using something like this

Created suggestion in uservoice forum:
https://warlight.uservoice.com/forums/77051-warzone-features/suggestions/48249116--modding-ui-metrics-and-more-uielement-methods


Include a Changelog Link, within the F-Droid App', on Info' Page.  Not Present, as of: 1.8.1.

NetInfo has been added to F-Droid without our permission and conscent. Google Play is the only supported distribution channel, and it has a changelog:
https://play.google.com/store/apps/details?id=com.ultrafunk.network_info

Sad.  Well then it doesn't seem to be truly FOSS (Free & Open Source Software).
Google has "remote kill switch", and other proprietary "remedies".   Via that, Google could uninstall it, withOUT my consent.  But I've done so, as you only want Google to have control.

Sad. Well then it doesn't seem to be truly FOSS (Free & Open Source Software).

If you want a changelog link within the F-Droid App: Please feel free to contribute the code to this project or make an F-Droid specific fork with any changes you think are needed.

https://f-droid.org/manual/html_node/Changelog.html#Changelog


Drawer

### Tasks
- [ ] Get Feedback
- [ ] Review site doc examples and desciptions
- [ ] Implement desktop support
- [ ] Move Drawer to core
- [ ] Transition needs standardising to ease in out with perceptible token (plus updating in characteristic spec)
- [ ] Update with Salt Scrim
- [ ] Update with secondary drawer examples in site
- [ ] Review Figma component to align wihn

Changes from UITK Drawer

Ensure that site docs/migration guide give recommendation to use Border Layout, rather than Drawer, when teams require equivalent of UITK Inlaid Drawer. Salt Drawer will only overlay.
Salt's Drawer is always modal (needs capturing in docs). A docked behaviour would be created by AD teams by using a panel and styles to expand and collapse a non-modal surface.
Custom Close Button label example not required.

Figma
Salt Drawer spec is here.
Salt Drawer component is released.

Things to discuss from KO

Should the Drawer fill the entire application or just a container/region - Yes. In order to satisfy the Data Grid requirement of having a drawer within the area of the grid.

30/1 Takeaway post catch up with @bhoppers2008

remove min height/min width for all positions
default primary & default secondary example to have no content
add one more example showcasing optional close button (total to 6 examples altogether)
improve example for bottom drawer: use Salt Cards and layouts
improve examples for left and right drawer: @bhoppers2008  to share mock ups by mid morning Wednesday
update docs to include recommendation for users to set drawer width

https://www.saltdesignsystem.com/salt/components/drawer/examples


Deploy confluent on kubernetes to AWS

Aug 2:
Looking at confluent on kubernetes, which should be easier because of operator (easier to deploy)

Confluent is deployed on Kubernetes. @Moro-Code has access. Still trying to figure out how to deploy the neo4j sink plugin.

Kubernetes deploy currently requires US-East, not able to us Canada servers yet.
To Backlog


Given "type T = ?{…}" how can I get "type U = {…}", i.e., "type U = T \setminus null \setminus undefined"?

Relay generates nice Flow types for me like
type T = {| user: ?{ firstName: string } |};

.
I'd like to be able to say a component accepts { firstName: string } without hard-coding the firstName: string in. I can use type U = $PropertyType<T, "user"> to dynamically get type U = ?{ firstName: string }, but would like another operator to let me require that the object is not null or undefined? Is there anything like this? It looks like $Diff<A, B> almost does this, but only works when A and B are both Objects.

$NonMaybeType<$PropertyType<T,"user">> should give you what you want.

Perfect!

i used this until i've heard about $NonMaybeType :smiley_cat: :
type _Definitely<T, U: ?T> = T;
type Definitely<T> = _Definitely<*, T>;

type T = {| user: ?{ firstName: string } |};
type U = Definitely<$PropertyType<T, 'user'>>;

({ firstName: 'foo' }: U);

Should I add that to https://flow.org/en/docs/types/utilities/ or is it documented somewhere else?

This is now documented.


Adds rough provenance replay

Goals:

replay something
don't worry about early-versions missing output names yet
don't worry about disconnected DiGraphs yet

Process:

[x] Take a provdag and print an ordered list of commands
[x] As above, but print an ordered list of usage examples
[x] Take a provdag and choice of interface driver, print an ordered list of rendered usage examples
[x] As above, but pipe rendering into a text file
[x] Deal with imports
[x] Deal with metadata
[x] Deal with no-provenance nodes
[x] tests

Under initial play testing, nx.topological_sort() seems to be iterating over the sets produced by topological_generations, so we get all imports at the top with either function, and would only get value out of topological generations if we wanted to apply some in-generation ordering of our own. This is probably better done with lexicographical_topological_sort(), which gives us more power to resolve ambiguity at the cost of complexity. That's out of scope for this PR.

Based on this and this, I think I can rely on Usage drivers tracking unique usage variable names, and so enabling me to chain a single huge usage example out of a basic analysis, where each usage output name's value (e.g. the ints_d in use.UsageOutputNames(concatenated_ints='ints_d') will persist and remain available to the following action.
We still need to make sure that these names are unique in the namespace, but that's less awful than having to build factories for each example, or something awfulawfulawful.

closes #33


Add hu (Hungarian - magyar) locale

Does another file need updating to enable Hungarian?
Thank you

@joeattardi does another file need updating to enable Hungarian? Thank you

@joeattardi can you please merge this? If not, please advise what else is required to merge. If not required, please advise so this can be deleted. Thank you

The ellipsis changes don't seem necessary here, the … character isn't widely used, at least not in English. I am happy to merge the hu language pack but please revert the ellipsis changes.

Mozilla (eg Firefox and Thunderbird) use 1-character ellipses.
https://transvision.mozfr.org/?recherche=Browse…&repo=all_projects&sourcelocale=en-US&locale=en-GB&search_type=strings&entire_string=entire_string

@joeattardi thank you for your comment. As you requested, ellipses should be now 3-character dots. Can you please now merge? Thank you

Ellipses have been reverted to 3-character ellipses (except for Hungarian) at https://github.com/joeattardi/picmo/pull/282/files.
Do you also require Hungarian to have a 3-character ellipsis to enable merging?
Thank you

Thank you @joeattardi

@joeattardi please advise if there are any new translations required in the future. Thank you


Add unit tests

Consider using the mock webserver from OkHttp
https://github.com/square/okhttp/tree/master/mockwebserver
Anything missing would be useful additions to that library


Improve github-actions to run job only if its target changed

As we have already done in Gitlab-CI:

run frontend job only if frontend files have changed,
run backend job only if backend files have changed.

Done in https://github.com/probabl-ai/skore/pull/349 and https://github.com/probabl-ai/skore/pull/402 .


android the app closes and 'TurboStarter' could not be found

hello, with ios it works perfect, but with android it doesn't, the app closes and i get this error: 2022-04-29 14:50:50.271 28083-28131/com.example.reactnativeturbostarter E/ReactNativeJS: Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'TurboStarter' could not be found. Verify that a module by this name is registered in the native binary., js engine: hermes
This my system information:
System:
OS: macOS 12.3.1
CPU: (4) x64 Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz
Memory: 600.11 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 17.8.0 - /usr/local/bin/node
Yarn: 1.22.18 - /usr/local/bin/yarn
npm: 8.5.5 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8309675
Xcode: 13.3/13E113 - /usr/bin/xcodebuild
Languages:
Java: <IP_ADDRESS> - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.68.1 => 0.68.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Originally posted by @direstrepo24 in https://github.com/talknagish/react-native-turbo-starter/issues/27#issuecomment-1112749365

Hi @direstrepo24! Thanks for the issue. I will look into it whenever I get a chance


unknown comand

./linWinPwn.sh -t <IP_ADDRESS>
Unknown option: -t

Thanks for creating the Issue. Fixed with the new commit


Add crashing test case when using dry wet in mixer

Possibly related to https://github.com/AudioKit/AudioKit/issues/2377
Few things I noticed:

Using Mixer instead of DryWetMixer doesn't crash
Using only one BitCrusher (or any effect) in chain doesn't crash
Adding mixer inputs after engine.output assignment still crashes

Interesting, I think this is probably an issue in AudioKit's connection mechanism, but only rears its ugly head here.  @wtholliday What do you think?


fix: update tab instead of creating a new one during HTTP recovery

Fixes #873

The changes caused some tests to fail, and I'm not sure my javascript skills are good enough to figure out how to fix them properly without just deleting them.
  419 passing (2s)
  1 pending
  7 failing

  1) requestHandler.onCompleted:
       with recoverFailedHttpRequests=true
         should redirect to default subdomain gateway on broken subdomain gateway request:
     AssertionError: tabs.create should be called with default subdomain gateway URL: expected false to be truthy
      at Context.<anonymous> (test/functional/lib/ipfs-request-gateway-recover.test.js:57:14)

  2) requestHandler.onCompleted:
       with recoverFailedHttpRequests=true
         should recover from unreachable third party public gateway by reopening on the public gateway:
     AssertionError: tabs.create should be called with IPFS default public gateway URL: expected false to be truthy
      at Context.<anonymous> (test/functional/lib/ipfs-request-gateway-recover.test.js:92:14)

  3) requestHandler.onErrorOccurred:
       with recoverFailedHttpRequests=true
         should redirect to default subdomain gateway on failed subdomain gateway request:
     AssertionError: tabs.create should be called with default subdomain gateway URL: expected false to be truthy
      at Context.<anonymous> (test/functional/lib/ipfs-request-gateway-recover.test.js:156:14)

  4) requestHandler.onErrorOccurred:
       with recoverFailedHttpRequests=true
         should recover from unreachable third party public gateway by reopening on the public gateway:
     AssertionError: tabs.create should be called with IPFS default public gateway URL: expected false to be truthy
      at Context.<anonymous> (test/functional/lib/ipfs-request-gateway-recover.test.js:182:14)

  5) requestHandler.onErrorOccurred:
       with recoverFailedHttpRequests=true
         should recover from unreachable HTTP server by reopening DNSLink on the active gateway:
     AssertionError: tabs.create should be called with DNSLink on local gateway URL: expected false to be truthy
      at Context.<anonymous> (test/functional/lib/ipfs-request-gateway-recover.test.js:191:14)

  6) requestHandler.onErrorOccurred:
       with recoverFailedHttpRequests=true
         should recover from failed DNS for .eth opening it on EthDNS gateway at .eth.link:
     AssertionError: tabs.create should be called with ENS resource on local gateway URL: expected false to be truthy
      at Context.<anonymous> (test/functional/lib/ipfs-request-gateway-recover.test.js:202:14)

  7) modifyRequest processing
       a failed main_frame request to /ipns/ipfs.io/blog
         should be updated to /ipns/blog.ipfs.io:
     AssertionError: expected false to be truthy
      at Context.<anonymous> (test/functional/lib/ipfs-request-workarounds.test.js:194:14)

----------------------------------------|----------|----------|----------|----------|-------------------|
File                                    |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
----------------------------------------|----------|----------|----------|----------|-------------------|
All files                               |    61.29 |    57.17 |       59 |    62.74 |                   |
 lib                                    |    59.53 |    55.52 |    56.94 |    61.06 |                   |
  context-menus.js                      |    58.24 |     7.69 |    42.86 |    60.47 |... 71,173,174,177 |
  copier.js                             |     9.38 |        0 |    14.29 |     9.38 |... 59,61,68,69,70 |
  dir-view.js                           |      100 |       50 |      100 |      100 |             10,33 |
  dnslink.js                            |    68.81 |    66.67 |    81.25 |    73.27 |... 56,159,161,167 |
  http-proxy.js                         |    25.81 |     6.25 |    33.33 |    24.14 |... 8,92,96,97,101 |
  inspector.js                          |       50 |      100 |       50 |       50 |    10,11,12,13,14 |
  ipfs-companion.js                     |    27.88 |     8.05 |    15.38 |    29.38 |... 55,759,776,777 |
  ipfs-import.js                        |    21.43 |        0 |    22.22 |    21.31 |... 09,110,111,112 |
  ipfs-path.js                          |     92.5 |    80.67 |      100 |    94.41 |... 25,250,310,359 |
  ipfs-protocol.js                      |    86.67 |     62.5 |      100 |    86.21 |       20,21,37,49 |
  ipfs-request.js                       |    87.88 |    84.41 |     93.1 |    90.95 |... 15,416,420,422 |
  mime-sniff.js                         |       80 |       60 |      100 |    92.31 |                33 |
  notifier.js                           |    27.27 |        0 |    33.33 |    27.27 |... 12,14,15,20,22 |
  on-installed.js                       |    55.56 |        0 |       50 |    55.56 |         8,9,17,18 |
  options.js                            |    91.43 |    77.55 |      100 |    91.18 |... 63,172,173,182 |
  precache.js                           |       30 |     8.33 |    30.77 |    32.14 |... 03,104,105,109 |
  runtime-checks.js                     |    93.33 |    96.43 |      100 |    93.33 |                16 |
  state.js                              |    94.74 |     62.5 |       80 |    94.29 |             50,53 |
 lib/ipfs-client                        |     61.7 |    52.63 |    43.75 |    63.04 |                   |
  embedded.js                           |    29.03 |        0 |        0 |       30 |... 37,44,45,47,48 |
  external.js                           |      100 |      100 |      100 |      100 |                   |
  index.js                              |       72 |    55.56 |    71.43 |    73.47 |... 62,64,65,66,89 |
 lib/ipfs-client/embedded-chromesockets |    29.61 |        0 |        0 |    30.41 |                   |
  config.js                             |    20.75 |        0 |        0 |    21.57 |... 56,159,161,162 |
  index.js                              |    21.57 |        0 |        0 |       22 |... 85,86,87,89,92 |
  libp2p-bundle.js                      |    34.48 |        0 |        0 |    34.48 |... 01,102,104,106 |
  libp2p.js                             |    68.42 |      100 |        0 |    72.22 |    24,25,26,32,87 |
 lib/ipfs-proxy                         |     76.7 |    74.85 |    74.12 |    78.48 |                   |
  access-control.js                     |    98.08 |    96.08 |      100 |      100 |            62,173 |
  enable-command.js                     |      100 |    90.91 |      100 |      100 |             24,48 |
  index.js                              |    43.18 |        0 |    15.38 |     47.5 |... 57,58,61,64,68 |
  pre-acl.js                            |       96 |    88.89 |      100 |      100 |             27,49 |
  pre-command.js                        |     91.3 |       75 |      100 |    95.24 |                21 |
  pre-mfs-scope.js                      |    97.01 |    92.59 |      100 |    96.72 |            72,121 |
  request-access.js                     |    12.28 |        0 |     8.33 |    13.73 |... 06,108,111,113 |
 pages/proxy-access-dialog              |    71.43 |       50 |       50 |    90.91 |                   |
  page.js                               |    71.43 |       50 |       50 |    90.91 |                54 |
 pages/proxy-acl                        |    93.48 |       90 |    88.89 |      100 |                   |
  page.js                               |     87.5 |    93.33 |    81.82 |      100 |                38 |
  store.js                              |      100 |       80 |      100 |      100 |                 3 |
 popup                                  |      100 |    57.14 |      100 |      100 |                   |
  logo.js                               |      100 |    57.14 |      100 |      100 |          6,7,8,13 |
----------------------------------------|----------|----------|----------|----------|-------------------|

@lidel To check changes on tests I just do npm run dev-build and then npm test right? I'm still getting the same test failures after I changed them all.

@abueide ah, I believe you need to remove all occurrences of , openerTabId: 20   in ipfs-request-gateway-recover.test.js (tabs.update is called without it).
That should fix remaining tests :)


Missing attributes

Maybe setting attributes to resources should have a failsafe/fallback to log warnings instead. Right now this is very susceptible to break whenever there is any change on the resources' attributes via the hetzner team. Being always up to date is not going to be maintainable in the long run.
I will try to look into it a bit, but this might be very easy for you to do already. Any thoughts?

I added setting attributes on the fly in v1.5.4. It logs a warning when it happens for the first time as well.


Update youtube-downloader extension

Description
Removed empty dropdown items caused by duplicate values
Screencast
Before and after

Also in my opinion Raycast should automatically remove duplicate dropdwon options isntead of making their title emtpy, it's not the first time i see empty dropdown items because their value is duplicate

Thanks for the update 🔥
@vimtor can you check this?


alert user if empty-can subtraction results in too many negative values

Got this error message (this bug was found by @jniedziela) in a DOS extraction run:
    440         # import pickle as pkl
    441         # pkl.dump((E,g,beta,dE), open('mp.forward.phonon.gamma0-debug.pkl', 'w'))
--> 442         raise RuntimeError("integrated dos should be 1, got %s instead" % (dos_integrated,))
    443     # compute function to integrate
    444     with np.errstate(invalid='ignore'):

RuntimeError: integrated dos should be 1, got nan instead

It turns out that after MT subtraction the I(Q,E) contains quite a bit negative values and it causes the calculation to fail.

should we just print a warning and set all negative values to zero?
or should we stop?
or provide user options to proceed or not?

Only put out a warning. Blindly setting all negative values to zero is problematic because users won't know he is actually over-subtracting. Simply throwing an exception might not be a good idea because sometimes it may be OK to have some negative values at some places due to statistical fluctuations.


Full Throttle - All-American Racing (USA).sfc glitchy line down the bottom of the screen when you choose the water craft

This sometimes happens in bsnes as well (with both PPU cores) but never seems to happen in Mesen. The glitchy line occurs because the game disables forced blanking for a single line in a single frame.
The game is doing some really strange things with HDMA during this screen transition. The glitch is possibly caused by not handling that correctly, or it could be a timing issue since it doesn't always occur.


Fixing issue where network couldn't be picked in dappbrowser

Reproducible:

Enable a lot of networks in settings.
Pick one of those (not ethereum main net) in the dapp browser
Go back to settings and disable all the networks except main net
Go to dapp browser and see that no network is selected.

Fix: If the network was deselected and is no longer in the enabled filters then revert network to main net.

User chooses a network for dappbrowser.
Subsequently, user disables that network in the wallet.
Dappbrowser can't use that network as it's been told not to use that network.

With your solution, dappbrowser continues to use the network after the user has instructed not to use that network.
Imagine this scenario:
user is using an xDai dapp, but wants to ensure, for whatever reason that the wallet won't use xDai, so they switch that network off.
Dappbrowser was previously set to xDai, and unless we do something will still be switched to xDai.
This is quite clearly NOT what was intended as xDai network was switched off.

@hboon how does iOS handle such situation? Might need some align-up here.

iOS falls back to mainnet (actually this is wrong too because the behaviour is unpredictable if mainnet was disabled).
I think there isn't a risk in losing funds from sending the transaction to the wrong network since the chain ID is embedded, and most apps should/ought to check for it before even accepting the user. Maybe loss of gas?
So we have a few options here.

@hboon how does iOS handle such situation? Might need some align-up here.

iOS falls back to mainnet (actually this is wrong too because the behaviour is unpredictable if mainnet was disabled).
I think there isn't a risk in losing funds from sending the transaction to the wrong network since the chain ID is embedded, and most apps should/ought to check for it before even accepting the user. Maybe loss of gas?

User enters testnet and she sees her balance is Ξ300
User disables the testnet from the available networks
The user is taken to mainnet without telling the user, and the system shows a balance of Ξ250
The user sends Ξ100 to bob thinking she sent testnet Ether. Bob receives Ξ100 real ether.

You can see cryptography doesn't come to play in such a scenario. So why chain ID comes to this discussion?

4. The user sends Ξ100 to bob thinking she sent testnet Ether. Bob receives Ξ100 real ether.
You can see cryptography doesn't come to play and this is purely UX problem. So why chain ID comes to this discussion?

Oh right. Serves me right for multi-tasking.
I suppose the only way that makes sense is to prompt the user (by showing the selector) until a selection has been made then.

Accept that this solution isn't ideal - since it's very much an edge condition; it's probably acceptable to pop a 'choose new network for DappBrowser' dialog.
@colourfreak What do you think?

What could solve a problem is

adding network name to all action sheets https://zpl.io/VO4dq4j
add info in the top left corner about what network you are connected to https://zpl.io/Vq7LmA5

And if you do steps like James mentioned, simply don't change anything.

If you choose: 'keep connected' it does not deselect xdai and keep you connected to xDAI
If you choose: 'disconnect' it deselect xdai from Active Networks and changes to Ethereum Mainnet automatically.

If you choose: 'keep connected' it does not deselect xdai and keep you connected to xDAI
If you choose: 'disconnect' it deselect xdai from Active Networks and changes to Ethereum Mainnet automatically.

Yes, putting the dialog there seems the most logical place you'd expect to see it.

https://zpl.io/a7mv7zR
https://zpl.io/Vq7LmA5


Additional build commands if not using makefile

Thanks for the contribution @MartinW ! Can you please fill out the CLA form so we can review your PR?

Hey @MartinW we don't accept PRs into the master branch so please reopen this against develop. Also the instructions should still say how to build with the Makefile. The command make build run, builds and runs the application.


mouse input

Is there any chance you can give me some pointers on modifying this code to a mouse? I tried it without success. As a summary, I have done the following:

set class to 0x2580 in the server
match HID report format to that of HID mouse on both the server and client.

As for the rest, I followed all the steps in your tutorial and the application is able to run without crashing. The mouse cursor just doesn't respond. Is there anything I am missing?
Thanks for your help in advance.

I am by no means an expert at this stuff, but I am guessing that the payload for a  HID mouse event report  will be different from a keyboard one, so you'll need to consult the HID documentation to see how to build this,
Here are the HID specs: http://www.usb.org/developers/hidpage#HID_Usage
It also looks like adafruit have something you might be able to adapt:  https://learn.adafruit.com/introducing-bluefruit-ez-key-diy-bluetooth-hid-keyboard/sending-keys-via-serial


[Debugging] Add DebugDescriptionMacro experimental feature

This removes the leading underscore from the macro.

@swift-ci smoke test

@swift-ci test macOS

@swift-ci linux macOS

@swift-ci test linux

Does this need some handling of asserts vs. no asserts compiler?

@drodriguez I don't believe so

Thanks, I see the problem. Fix here https://github.com/apple/swift/pull/73097


In a configuration with multiple vitest.config.ts, Run Test returns the same result as the previous one.

Describe the bug
There is a monorepo project with multiple vitest.config.ts.
They are not configured in workspace.
.
├── a
│   ├── node_modules
│   ├── package.json
│   ├── package-lock.json
│   ├── src
│   │   ├── sum1.test.ts
│   │   └── sum1.ts
│   ├── tsconfig.json
│   └── vitest.config.ts
└── b
    ├── node_modules
    ├── package.json
    ├── package-lock.json
    ├── src
    │   ├── sum2.test.ts
    │   └── sum2.ts
    ├── tsconfig.json
    └── vitest.config.ts

In this state, if the following steps are taken, the test will not fail at 3.
It seems that the test is executed again in the state of 1.

Run tests with "Run Test".
Change the test code so that the test fails.
Re-run the test with "Run Test".

"Debug Test" instead of "Run Test" resulted in a run against the current code.

Other informations.

The same is true when run from Test Explorer.
No problem with npm run test.
If vitest.config.ts in one of the folders is deleted so that there is only one vitest.config.ts, this problem will not occur.

Reproduction
I have placed the reproduced code below.

https://github.com/onozaty/node-sandbox/tree/main/vitest-monorepo

Output
[INFO 3:34:09 AM] [v1.2.8] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 3:34:10 AM] [API] Running Vitest v2.1.0 (b/vitest.config.ts) with Node.js: /usr/local/bin/node
[INFO 3:34:10 AM] [API] Running Vitest v2.1.0 (a/vitest.config.ts) with Node.js: /usr/local/bin/node
[INFO 3:34:11 AM] [API] Vitest v2.1.0 (a/vitest.config.ts) process 3646 created
[INFO 3:34:11 AM] [API] Vitest v2.1.0 (b/vitest.config.ts) process 3645 created
[INFO 3:34:11 AM] [API] Collecting tests: a/src/sum1.test.ts
[3:34:11 AM] Not starting the runner because tests are being collected
[3:34:11 AM] There is no test run for "sum1.test.ts"
[3:34:11 AM] No test run to finish for /workspaces/node-sandbox/vitest-monorepo/a/src/sum1.test.ts
[INFO 3:34:23 AM] Running 1 file(s) with name pattern: ^\s?a tset 1$
[3:34:23 AM] The runner is starting because tests /workspaces/node-sandbox/vitest-monorepo/a/src/sum1.test.ts were started due to a file change
[3:34:23 AM] Enqueuing "a tset 1"
[3:34:23 AM] No task result for "a tset 1", assuming the test just started running
[3:34:23 AM] Marking "a tset 1" as passed
[3:34:23 AM] Ending test run a/src/sum1.test.ts
[INFO 3:34:28 AM] Running 1 file(s) with name pattern: ^\s?a tset 1$
[3:34:28 AM] The runner is starting because tests /workspaces/node-sandbox/vitest-monorepo/a/src/sum1.test.ts were started due to a file change
[3:34:28 AM] Enqueuing "a tset 1"
[3:34:29 AM] No task result for "a tset 1", assuming the test just started running
[3:34:29 AM] Marking "a tset 1" as passed
[3:34:29 AM] Ending test run a/src/sum1.test.ts
[INFO 3:34:32 AM] Running 1 file(s) with name pattern: ^\s?a tset 1$
[3:34:32 AM] The runner is starting because tests /workspaces/node-sandbox/vitest-monorepo/a/src/sum1.test.ts were started due to a file change
[3:34:32 AM] Enqueuing "a tset 1"
[3:34:32 AM] No task result for "a tset 1", assuming the test just started running
[3:34:32 AM] Marking "a tset 1" as passed
[3:34:32 AM] Ending test run a/src/sum1.test.ts
[INFO 3:34:35 AM] [DEBUG] Debugging started
[INFO 3:34:36 AM] Running 1 file(s) with name pattern: ^\s?a tset 1$
[3:34:36 AM] The runner is starting because tests /workspaces/node-sandbox/vitest-monorepo/a/src/sum1.test.ts were started due to a file change
[3:34:36 AM] Enqueuing "a tset 1"
[3:34:37 AM] No task result for "a tset 1", assuming the test just started running
[3:34:37 AM] No errors found for "sum1.test.ts"
[3:34:37 AM] Marking "a tset 1" as failed with 1 errors
[3:34:37 AM] No errors found for "sum1.test.ts"
[3:34:37 AM] Ending test run a/src/sum1.test.ts
[3:34:37 AM] Disposing test runner
[INFO 3:34:41 AM] Running 1 file(s) with name pattern: ^\s?a tset 1$
[3:34:41 AM] The runner is starting because tests /workspaces/node-sandbox/vitest-monorepo/a/src/sum1.test.ts were started due to a file change
[3:34:41 AM] Enqueuing "a tset 1"
[3:34:41 AM] No task result for "a tset 1", assuming the test just started running
[3:34:41 AM] Marking "a tset 1" as passed
[3:34:41 AM] Ending test run a/src/sum1.test.ts

Version
v1.2.8
Validations

[X] Check that you are using the latest version of the extension
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Fixed in https://github.com/vitest-dev/vscode/releases/tag/v1.2.9


[Doc improvement][What's new]

update what's new

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/whats-new.md
90
93
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


Auto attack error

After enter username in auto attack option
Then it's saw many error can you fixed then i gave you screenshots on my Instagram id name is smeet.thakar

Fatal error name='csrftoken', domain=None, path=None


Reduce image allocation2

This reduces the need to allocate an image for every tile rendered. Rather we re-use the same pixels and just clear them beforehand (which is cheaper than re-allocating). This is able to drop memory usage from the > 1.5 GB range to just 80 MB for one render at z19. For reference this same render used 700 MB before mapnik/node-mapnik@b7b1ec5. But I don't think the solution is to revert mapnik/node-mapnik@b7b1ec5 but rather just avoid as much allocation (which is what this pull does).

now at #69


Reset stake rate

As discussed on the dev calls this will lower or raise the stakerate on all existing primenodes to 100%
The keys are still grouped under their previous rates to insure proper handling of old blocks. To that end the conf files should not be changed from their existing rates. These will be forced to 100 by the code after the given date.
(we used timestamp over block number because timestamp allows us to set a time for mandatory wallet upgrades, all wallets agree on the time when verifying new blocks anyway).

We have another PR we'll be putting in for the stall issue. It should probably have priority over this.

Since this will be a mandatory wallet update the timestamp on this will likely need to be expanded before merging to give people time to upgrade.

I'd like to see it even less,  more like 50-75 percent. The less coins the better.

Please Talk here to help the community: http://talk.paycoin.com/discussion/539/pull-request-47-reset-stake-rate/p1

This update implements a protocol change to insure that only updated wallets are connected when the stakerate is updated.

LGTM

@HyperCommNet LGTY?


refactor the -cfg to be a pull-down lis

change the -cfg flag from checkbox to pull down list at fpga_mafia ./gui_build.py
make it to be as -top or -regress


Support time based ban (mute)

This would be for creators, deleted moderators, and global mods. Would be a param passed to the block API
https://github.com/lbryio/lbry-desktop/issues/6299

Mute is not a distinct action, but instead modifies blocks to be time based.


issue with the D435IF depth image

Hello, I have a D435IF cmera that is giving us a distorted depth image. we tried on-chip calibration and gold reset and tare calibration but this distortion has not been fixed to reach the second image, could you please let me know hat could be the issue ?

best regards

Hi @Nimaro76
If a gold reset did not correct the depth image then you could try another method of resetting the camera to its factory-new default calibration, using the RealSense Viewer with instructions at https://github.com/IntelRealSense/librealsense/issues/10182#issuecomment-1019854487
If that does not work then you can try resetting the Viewer to its default settings instead of the camera with instructions at the link below.
https://support.intelrealsense.com/hc/en-us/community/posts/360052013914/comments/1500000416522
I also note that you are using camera firmware driver 5.13,0.55 in your camera.  This firmware is designed for Viewer / SDK versions 2.50.0 and 2.51.1, and using it with 2.54.2 could cause errors.  For 2.54.2 it is recommended that the firmware is updated to <IP_ADDRESS>, as suggested by the 'Firmware Update Recommended' pop-up box in the top corner of your Viewer.

Hi @Nimaro76  Do you require further assistance with this case, please?  Thanks!

not for now, thank you.
best, Nima
On Wed, Apr 3, 2024 at 6:33 PM MartyG-RealSense @.***>
wrote:

Hi @Nimaro76 https://github.com/Nimaro76 Do you require further
assistance with this case, please? Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/12790#issuecomment-2035072016,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3JUXA77QSKTFCKAIH7R7LLY3QVO3AVCNFSM6AAAAABFFXCVRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVGA3TEMBRGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

You are very welcome.  As you do not require further assistance, I will close this case.  Thanks again!


Bump golangci-lint version

Hey @alexander-melentyev, can we please ignore this lint failure in the golangci config? Because there's an index check a few lines above the lint error.

Thanks for the contribution @alexander-melentyev ❤


Bug: Changing task order in "Tasks" view

Search first

[X] I searched and no similar issues were found

What Happened?
I'd like to be able to change the order of tasks in a given column:

This is obv low priority -- happy to submit a PR though if you can point me to the right place in the codebase. Thanks!
Reproduce the Bug
Use drag and drop to try and change the order
Screenshots
No response
Environment Information
No response
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.

[x] I'm willing to submit a PR (Thank you!)

May I ask what are you would like to use for sorting?

I think the default can be whatever, for example, whatever the default is now.
But then I think it'd be cool if one could move stuff around


Can we provide the username to ADFS via the SAML Auth Request?

Hi there
I found this request in the Azure Ad Issues https://github.com/MicrosoftDocs/azure-docs/issues/19654 and this part of the SAML Spec - https://www.oasis-open.org/committees/download.php/35711/sstc-saml-core-errata-2.0-wd-06-diff.pdf (See 3.4.1).
It implies that there is a way to tell ADFS via SAML that we would like to login as a particular subject.
Is this possible? What parameter should we set on the request to add this data to the SAML ?

Hi! Sorry about the delay. For future questions regarding the component, please email<EMAIL_ADDRESS>for faster response times.
I think I may have already answered your question (or your colleagues) via the help desk, but currently, this is not something we support (and for some reason discouraged by previous versions of the interoperability specification (https://saml2int.org/profile/current/#section82).
I don't believe that this is supported by ADFS either.

Thanks for the clear answer!


TDVT tests fail with "TableauException: FederatedSubtreeBuilder: Could not determine types for all columns in the relation"

About You:
Name: Christoph Pirkl
Company: Exasol
Your question:
The TDVT tests for our JDBC Exasol connector fail with the following error message in tdvt_log_combined.txt:
2023-12-11 07:55:34,544 Thread-[1] Running test:logical.calcs.exasol_jdbc
2023-12-11 07:55:34,553 Thread-[1]  calling C:\Program Files\Tableau\Tableau 2023.3\bin\tabquerytool.exe --query-file-list C:\Users\chp\AppData\Local\Temp\2\cca01878f059c4e8bf387d353dba092ed4fa2b543a98fa40ee74a993a3q6rpt0\logical_calcs_exasol_jdbc\tests.txt -d C:\Users\chp\git\tableau-connector\tdvt_jdbc\tds\cast_calcs.exasol_jdbc.tds --combined --schema TestV1 --password-file C:\Users\chp\git\tableau-connector\tdvt_jdbc\tds\exasol_jdbc.password --output-dir C:\Users\chp\AppData\Local\Temp\2\cca01878f059c4e8bf387d353dba092ed4fa2b543a98fa40ee74a993a3q6rpt0 -DLogDir=C:\Users\chp\AppData\Local\Temp\2\cca01878f059c4e8bf387d353dba092ed4fa2b543a98fa40ee74a993a3q6rpt0\logical_calcs_exasol_jdbc -DOverride=ProtocolServerNewLog -DConnectPluginsPath=..\src -DLogicalQueryRewriteDisable=Funcall:RewriteConstantFuncall -DInMemoryLogicalCacheDisable
2023-12-11 07:55:47,401 Thread-[1] CalledProcessError: Return code: 12 Attempting to run query...
TableauException: FederatedSubtreeBuilder: Could not determine types for all columns in the relation.
{"relation-conn":"leaf","relation-conn-class":"exasol_jdbc","relation-table":"[TESTV1].[Calcs]","unknown-type-columns":["[bool0_]","[bool1_]","[bool2_]","[bool3_]"]}

Error running query

2023-12-11 07:55:47,402 Thread-[1] Command line output:Attempting to run query...
TableauException: FederatedSubtreeBuilder: Could not determine types for all columns in the relation.
{"relation-conn":"leaf","relation-conn-class":"exasol_jdbc","relation-table":"[TESTV1].[Calcs]","unknown-type-columns":["[bool0_]","[bool1_]","[bool2_]","[bool3_]"]}

Error running query

2023-12-11 07:55:47,412
Finished tdvt suite [exasol_jdbc]: tested sql [False]: tested tuples [True]: tested error [False]: output dir [C:\Users\chp\AppData\Local\Temp\2\cca01878f059c4e8bf387d353dba092ed4fa2b543a98fa40ee74a993a3q6rpt0]: logical [True]: config file [logical.calcs.exasol_jdbc]: override [-DConnectPluginsPath=..\src]: tds [C:\Users\chp\git\tableau-connector\tdvt_jdbc\tds\cast_calcs.exasol_jdbc.tds]: thread [6]

In total 31 tests fail because of this:
Test Count: 949 tests
        Passed tests: 918
        Failed tests: 31
        Tests run: 949
        Disabled tests: 0
        Skipped tests: 0

How can I fix these errors?
TDVT version: 2.7.6
Tableau Desktop version: 2023.3

I hope it's okay to piggy-back on this issue since I am encountering the same error.
Here is my "About You":
Name: Michael Habiger
Company: Actian Corporation
TDVT version: 2.7.6
Excerpts from my tdvt_log_combined.txt
2023-12-12 15:58:48,798 Thread-[6]  calling C:\Program Files\Tableau\Tableau 2023.3\bin\tabquerytool.exe --expression-file-list C:\Users\mhabiger\AppData\Local\Temp\596bb5566baa2f9f2e3f0063660fdd831d866604cf06c81d59fe6d2e8b72202_\expression_lod_mahjdbc\tests.txt -d C:\Users\mhabiger\Data\work\tableau\dec12test\tabdsk-2023.3\wksp\tds\cast_calcs.mahjdbc.tds --combined --schema mhabiger --password-file C:\Users\mhabiger\Data\work\tableau\dec12test\tabdsk-2023.3\wksp\tds\mahjdbc.password --output-dir C:\Users\mhabiger\AppData\Local\Temp\596bb5566baa2f9f2e3f0063660fdd831d866604cf06c81d59fe6d2e8b72202_ -DLogDir=C:\Users\mhabiger\AppData\Local\Temp\596bb5566baa2f9f2e3f0063660fdd831d866604cf06c81d59fe6d2e8b72202_\expression_lod_mahjdbc -DOverride=ProtocolServerNewLog -DLogicalQueryRewriteDisable=Funcall:RewriteConstantFuncall -DInMemoryLogicalCacheDisable

.....

2023-12-12 15:59:05,126 Thread-[1] CalledProcessError: Return code: 12 Attempting to run query...
TableauException: FederatedSubtreeBuilder: Could not determine types for all columns in the relation.
{"relation-conn":"leaf","relation-conn-class":"actian_jdbc","relation-table":"[mhabiger].[Calcs]","unknown-type-columns":["[bool0_]","[bool1_]","[bool2_]","[bool3_]"]}

The error only occurs when using tabquerytool.exe from my Tableau Desktop version 2023.3. If I simply update the TAB_CLI_EXE_X64 path in the tdvt_override.ini to point to the tabquerytool.exe from my 2023.2 version, the error doesn't occur.
So it seems like a problem introduced in 2023.3.

Thank you both for reporting this. We will investigate.
Tracking: W-14659872

I believe this bug is fixed with the latest release of TDVT 2.13.4.
There was an associated test update to setup.BUGS.B59740.xml that was required by the platform with the release of 2023.3. The columns [bool<num>_] were updated to [bool<num>] in that file.

TDVT version 2.13.4 seems to have fixed the problem for us. Thank you!

You will nee a more recent version of Python for this release - 3.7.9 fails.


refactor nodes/workflows

refactored nodes/workflows to be consistent with the /workflows route
@RackHD/corecommitters @dalebremner @srinia6 @brianparry

*** BUILD #1356 ***
Test Name: test_node_workflows_get
Error Details: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 303, in test_node_workflows_get
    assert_raises(rest.ApiException, Api().nodes_get_workflow_by_id, 'fooey')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 183, in assert_raises
    fail("Expected an exception of type %s to be raised." % exception_type)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.

working on addressing the function test issues in another PR.  Travis had a time out, but worked locally so....
test this please

*** BUILD #1378 ***
Test Name: test_node_workflows_get
Error Details: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 303, in test_node_workflows_get
    assert_raises(rest.ApiException, Api().nodes_get_workflow_by_id, 'fooey')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 183, in assert_raises
    fail("Expected an exception of type %s to be raised." % exception_type)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.

*** BUILD #1380 ***
Test Name: test_node_workflows_get
Error Details: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 303, in test_node_workflows_get
    assert_raises(rest.ApiException, Api().nodes_get_workflow_by_id, 'fooey')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 183, in assert_raises
    fail("Expected an exception of type %s to be raised." % exception_type)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.

Functional test issues resolved in https://github.com/RackHD/RackHD/pull/260
Both of these PRs are dependent on each other.  In addition, pypi needs to be updated as well.
As far as the order for merging:
I believe PR should get merged, pypi should be updated, and then the functional test PR should get merged

@benbp addressed your comments.  Thanks for the tips about lodash! :)

*** BUILD #1403 ***
Test Name: test_node_workflows_get
Error Details: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 303, in test_node_workflows_get
    assert_raises(rest.ApiException, Api().nodes_get_workflow_by_id, 'fooey')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 183, in assert_raises
    fail("Expected an exception of type %s to be raised." % exception_type)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.

timeout error.
test this please

travis, test this please

+1

*** BUILD #1449 ***
Test Name: test_node_workflows_get
Error Details: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 303, in test_node_workflows_get
    assert_raises(rest.ApiException, Api().nodes_get_workflow_by_id, 'fooey')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 183, in assert_raises
    fail("Expected an exception of type %s to be raised." % exception_type)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.

@benbp @brianparry @zyoung51 @jlongever
updated query usage so we are now doing the query before passing it into the database.
passed all unit tests and functional tests locally.  Dependencies still remain on the Functional test PR ( https://github.com/RackHD/RackHD/pull/260 ) and on pypi being updated

👍  thanks @BillyAbildgaard !

@tannoa2 you gave a plus 1, but there were some changes to how we're doing queries now.  You might want to review again after my latest commit

*** BUILD #1453 ***
Test Name: test_node_workflows_get
Error Details: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 303, in test_node_workflows_get
    assert_raises(rest.ApiException, Api().nodes_get_workflow_by_id, 'fooey')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 183, in assert_raises
    fail("Expected an exception of type %s to be raised." % exception_type)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.

+1, looks good to me

*** BUILD #1455 ***
Test Name: test_node_workflows_get
Error Details: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 303, in test_node_workflows_get
    assert_raises(rest.ApiException, Api().nodes_get_workflow_by_id, 'fooey')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 183, in assert_raises
    fail("Expected an exception of type %s to be raised." % exception_type)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.

*** BUILD #1456 ***
Test Name: test_node_workflows_get
Error Details: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 303, in test_node_workflows_get
    assert_raises(rest.ApiException, Api().nodes_get_workflow_by_id, 'fooey')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 183, in assert_raises
    fail("Expected an exception of type %s to be raised." % exception_type)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.

*** BUILD #1457 ***
Test Name: test_node_workflows_get
Error Details: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 303, in test_node_workflows_get
    assert_raises(rest.ApiException, Api().nodes_get_workflow_by_id, 'fooey')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 183, in assert_raises
    fail("Expected an exception of type %s to be raised." % exception_type)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.

@brianparry I was just doing it that way in case we add more swagger query parameters in the future. That way they'll still get passed in once active is handled and removed from the query

@brianparry made the change you recommended

@BillyAbildgaard :+1: Thanks for making these changes.

*** BUILD #1496 ***
Test Name: test_node_workflows_get
Error Details: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 303, in test_node_workflows_get
    assert_raises(rest.ApiException, Api().nodes_get_workflow_by_id, 'fooey')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 183, in assert_raises
    fail("Expected an exception of type %s to be raised." % exception_type)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.

*** BUILD #1499 ***
Test Name: test_node_workflows_get
Error Details: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 303, in test_node_workflows_get
    assert_raises(rest.ApiException, Api().nodes_get_workflow_by_id, 'fooey')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 183, in assert_raises
    fail("Expected an exception of type %s to be raised." % exception_type)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: Expected an exception of type <class 'on_http_api2_0.rest.ApiException'> to be raised.


how can i get the cookies header string?

your framework is very good ,thanks
But I find that using function "CookieManager.get(url, (err, res) => { }"  i get the local cookie and it is in json format.
but i need the cookies header for another request ,it is like "aaa=xxxx;bbb=yyyy;ccc=zzzz",how can i get this ?

ok i know . i read your code (iOS) , i find i can use this function to get it ,and the string is in  header["Cookie"]
RCT_EXPORT_METHOD(getHeader:(NSURL *)url callback:(RCTResponseSenderBlock)callback) {
NSArray *cookies = [[NSHTTPCookieStorage sharedHTTPCookieStorage] cookiesForURL:url];
NSDictionary *header = [NSHTTPCookie requestHeaderFieldsWithCookies:cookies];
callback(@[[NSNull null], header]);
}

@rayshen Could you clarify the detail how can do that?

export const jsonToStringCookie = (cookieJson= {session: '"abc"'}) => {
  let cookieString= ''
  Object.keys(cookieJson).map((title, index) => {
    cookieString = cookieString + `${title} = ${cookieJson[title]};`
  })
  return cookieString;
}

I'm only thinking that way


Updating cli tool to use node balances instead of account balances

cli was using account balances, updated it to use node balance.

@pengying is going to resubmit internally first.


MarGo build failed

I'm filing this on the advice of the below output:
** 2017-10-17 09:14:44.383647 **:
GoSublime: | GoSublime error: MarGo build failed
|                > This is possibly a bug or miss-configuration of your environment.
|                > For more help, please file an issue with the following build output
|                > at: https://github.com/DisposaBoy/GoSublime/issues/new
|                > or alternatively, you may send an email to<EMAIL_ADDRESS>|                >
|                >
|                > cmd: `['C:\\Go\\bin\\go.exe', 'build', '-tags', '', '-v', '-o', 'gosublime.margo_r17.10.15-1_go1.9.exe', 'disposa.blue/cmd/margo']`
|                > stdout: `
|                >
|                > `
|                > stderr: `
|                > net
|                > disposa.blue/margo
|                > disposa.blue/something-borrowed/types
|                > disposa.blue/margo/meth/importpaths
|                > crypto/x509
|                > vendor/golang_org/x/net/proxy
|                > vendor/golang_org/x/net/lex/httplex
|                > net/textproto
|                > mime/multipart
|                > crypto/tls
|                > net/http/httptrace
|                > net/http
|                > net/http/pprof
|                > net/rpc
|                > disposa.blue/something-borrowed/gocode
|                > # disposa.blue/something-borrowed/gocode
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:13:5: Margo redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:15:5
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:15:6: MargoConfig redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:17:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:22:6: margoEnv redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:24:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:32:6: (*margoEnv).assign redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:34:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:43:6: margoState redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:45:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:54:6: MargoCandidate redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:56:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:60:23: newMargoState redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:62:23
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:72:6: (*margoState).Complete redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:74:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:90:6: (*margoState).updateConfig redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:92:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:96:9: (*margoState).updateConfig.func1 redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:98:9
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:96:9: too many errors
|                > `
|                > exception: `None`
|   install state: busy
| sublime.version: 3150
| sublime.channel: dev
|       about.ann: a17.10.15-1
|   about.version: r17.10.15-1
|         version: r17.10.15-1
|        platform: windows-x64
|            ~bin: ~\AppData\Roaming\Sublime Text 3\Packages\User\GoSublime\windows-x64\bin
|       margo.exe: ~bin\gosublime.margo_r17.10.15-1_go1.9.exe (missing)
|          go.exe: C:\Go\bin\go.exe (ok)
|      go.version: go1.9
|          GOROOT: C:\Go\
|          GOPATH: C:\GoWork
|           GOBIN: (not set) (should usually be `(not set)`)
|       set.shell: []
|       env.shell:
|       shell.cmd: ['C:\\Windows\\system32\\cmd.exe', '/C', '${CMD}']
--------------------------------

** 2017-10-17 09:14:44.386647 **:
GoSublime init r17.10.15-1 (3.610s)
|   install margo: cmd: `['C:\\Go\\bin\\go.exe', 'build', '-tags', '', '-v', '-o', 'gosublime.margo_r17.10.15-1_go1.9.exe', 'disposa.blue/cmd/margo']`
|                > stdout: `
|                >
|                > `
|                > stderr: `
|                > net
|                > disposa.blue/margo
|                > disposa.blue/something-borrowed/types
|                > disposa.blue/margo/meth/importpaths
|                > crypto/x509
|                > vendor/golang_org/x/net/proxy
|                > vendor/golang_org/x/net/lex/httplex
|                > net/textproto
|                > mime/multipart
|                > crypto/tls
|                > net/http/httptrace
|                > net/http
|                > net/http/pprof
|                > net/rpc
|                > disposa.blue/something-borrowed/gocode
|                > # disposa.blue/something-borrowed/gocode
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:13:5: Margo redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:15:5
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:15:6: MargoConfig redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:17:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:22:6: margoEnv redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:24:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:32:6: (*margoEnv).assign redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:34:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:43:6: margoState redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:45:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:54:6: MargoCandidate redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:56:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:60:23: newMargoState redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:62:23
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:72:6: (*margoState).Complete redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:74:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:90:6: (*margoState).updateConfig redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:92:6
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:96:9: (*margoState).updateConfig.func1 redeclared in this block
|                > 	previous declaration at ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\bridge._margo_.go:98:9
|                > ..\..\..\..\GoSublime\src\disposa.blue\something-borrowed\gocode\gosublime_gocode_bridge.go:96:9: too many errors
|                > `
|                > exception: `None`
|   install state: done
| sublime.version: 3150
| sublime.channel: dev
|       about.ann: a17.10.15-1
|   about.version: r17.10.15-1
|         version: r17.10.15-1
|        platform: windows-x64
|            ~bin: ~\AppData\Roaming\Sublime Text 3\Packages\User\GoSublime\windows-x64\bin
|       margo.exe: ~bin\gosublime.margo_r17.10.15-1_go1.9.exe (missing)
|          go.exe: C:\Go\bin\go.exe (ok)
|      go.version: go1.9
|          GOROOT: C:\Go\
|          GOPATH: C:\GoWork
|           GOBIN: (not set) (should usually be `(not set)`)
|       set.shell: []
|       env.shell:
|       shell.cmd: ['C:\\Windows\\system32\\cmd.exe', '/C', '${CMD}']

Actually - I resolved this by removing the package and then re-installing it. No idea why that should make a difference - but the error disappeared.


Queue manager

We should  configure  RSAT to enable running tasks on slurm.
This would be useful for different purposes :

Some command-line tools are computer-intensive, and the corresponding software has options to send the tasks to a job scheduler. I used different schedulers for this (PBS, torque, ... ?) but not yet slurm. It should be relatively easy to add a slurm configuration.

Currently the Web server treats requests in synchronous mode. It would be every useful to enable sending some computer-intensive analyses to the job scheduler. This will require some additional development.

The cluster options can be set with
perl perl-scripts/configure-rsat.pl

We will also need to adapt the Perl library in order to support slurm.


Add arguments

Added command arguments.
Now it is possible to pass the arguments to the commands.
For example: $ ./cli cmd arg1 arg2
P.S. arg1 and arg2 is command(cmd) arguments.

close #8


How to check for the length property with JsonLogic

Hi,
Sorry for coming back with another question please. My bad.
Here is my use case.
I have a JSON obejct. I am using json-logic-fs to apply the query formatted as jsonlogic against my object. So far it works with the text fields.
What I also want to do is filter out the items which dont have children items inside . For example please see the following json object
{
 "name" : "Category of the post",
"posts": [ {"id" : 1 , "title" : "my first post"}]
},
{
 "name" : "Another post category",
"posts": []
}

I have the current fields set up as such
const fields = [
  { name: 'name', label: 'Category Name' },
  {
    name: 'posts',
    label: 'Has posts',
    valueEditorType: 'checkbox',
  },
];

What I would really like to do is to generate a query that will filter out categories which do not have any post, i.e categories which have posts field length is 0, will be filtered out.
The existing default operators wont help, I presume as I cannot use them to check for the length of an array.
Is there a way I can create a length operator and use it to filter categories which have the posts length as 0.
Sorry for a lengthy question.
Thanks once again for your time and patience.
With Regards
Gagan

Is the length filter something that you want to be able to produce dynamically from the query builder, or something static that you would add to each JsonLogic filter unconditionally?
If it's static, you can register a custom operation with jsonLogic.add_operation and manipulate the JsonLogic object you get from formatQuery to use the custom operation.
If it's something you need to have as an operator in RQB, you'll still need to add the custom operation before you apply the JsonLogic filter, but you can also use the ruleProcessor option in formatQuery to produce the rule you need. If you need a specific example let me know, but the documentation page actually already has a good JsonLogic example.

@jakeboone02 an example would be nice , kind Sir. I appreciate all help .
Thanks,
Gagan

I think this does something like what you want: https://stackblitz.com/edit/github-2vj3ih-urvyv3?file=src/App.tsx
Check and uncheck the checkbox on the default "Has posts" rule to see how the data is filtered differently.

You are godsend.. Thanks a lot .. it worked perfectly. Thank you once again. Much much appreciated. This is the first time, I am seeing such kind of support from the author of a very popular component. thanks once again. ❤

I don't know about "very popular" but thank you for the kind words!


Migrate from webpack/jest/babel to vite/vitest

Description
Migrate to vite and vitest.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Dependency changes
[x] Code refactor / cleanup
[ ] Documentation or wording changes
[ ] Other

How should this be tested?
Please provide instructions so we can test. Please also list any relevant details for your test configuration.

[ ] Test A
[ ] Test B

Visual context
Please provide any relevant visual context for UI changes or additions. This could be static screenshots or a loom screencast.
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have requested at least 2 reviews (If the PR is significant enough, use best judgement here)
[ ] I have commented my code where relevant, particularly in hard-to-understand areas
[ ] If package-lock.json has changes, it was intentional.
[ ] The base of this PR is master if hotfix, develop if not

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1203456727694350

@agualis can you also add please some tool to analyse final bundle? may be https://www.npmjs.com/package/rollup-plugin-analyzer ?

@alter-eggo I did, check the Readme. You need to set up 2 env vars to run it locally.

@agualis The staking incentives accordian on pool pages doesn't work and the styling of accordions that appear on mobile on the swap page are broken (see image)

Replaced by #2683


BUG: Logout issue

Context
Working in two different Tabs logged in on the same instance, one tab in WP the other in Django.
Problem
If I logout from Django, the WP tabs properly show the logged out upper panel, but I can still uses WP admin tools (modify pages...) and I am still logged in WP.
Expect
When I logged out of Django I also get logged out of WP.

see #95


[Subtask] Connectors for Flink SQL Query Engine -> Iceberg

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the subtask
Add a doc of Flink SQL Query Engine for Iceberg.
Parent issue
https://github.com/apache/incubator-kyuubi/issues/3059
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

I would like to take this.


Ledger API response error on v2GetAccount

When I call the following method:
await formanceClient.ledger.v2GetAccount({
  address: 'creators:123_123_123:gross_earnings:pending',
  ledger,
})

the ledger returns with the following error:
{
  "errorCode": "NOT_FOUND",
  "errorMessage": "getting account: not found"
}

and the logs show the following warning
WARN: bun: 2024/07/15 09:56:38 query "(jsonb_array_length(account_address_array) = 5 and account_address_array @@ ('$[0] == \"creators\"')::jsonpath and account_address_array @@ ('$[1] == \"123_123_123\"')::jsonpath and account_address_array @@ ('$[2] == \"gross_earnings\"')::jsonpath and account_address_array @@ ('$[3] == \"pending\"')::jsonpath) or (jsonb_array_length(account_address_array) = 6 and account_address_array @@ ('$[0] == \"creators\"')::jsonpath and account_address_array @@ ('$[1] == \"123_123_123\"')::jsonpath and account_address_array @@ ('$[2] == \"gross_earnings\"')::jsonpath and account_address_array @@ ('$[3] == \"pending\"')::jsonpath) or (jsonb_array_length(account_address_array) = 7 and account_address_array @@ ('$[0] == \"creators\"')::jsonpath and account_address_array @@ ('$[1] == \"123_123_123\"')::jsonpath and account_address_array @@ ('$[2] == \"gross_earnings\"')::jsonpath and account_address_array @@ ('$[3] == \"pending\"')::jsonpath) or (jsonb_array_length(account_address_array) = 8 and account_address_array @@ ('$[0] == \"creators\"')::jsonpath and account_address_array @@ ('$[1] == \"123_123_123\"')::jsonpath and account_address_array @@ ('$[2] == \"gross_earnings\"')::jsonpath and account_address_array @@ ('$[3] == \"pending\"')::jsonpath) or (jsonb_array_length(account_address_array) = 9 and account_address_array @@ ('$[0] == \"creators\"')::jsonpath and account_address_array @@ ('$[1] == \"123_123_123\"')::jsonpath and account_address_array @@ ('$[2] == \"gross_earnings\"')::jsonpath and account_address_array @@ ('$[3] == \"pending\"')::jsonpath) or (jsonb_array_length(account_address_array) = 10 and account_address_array @@ ('$[0] == \"creators\"')::jsonpath and account_address_array @@ ('$[1] == \"123_123_123\"')::jsonpath and account_address_array @@ ('$[2] == \"gross_earnings\"')::jsonpath and account_address_array @@ ('$[3] == \"pending\"')::jsonpath)" has [] args, but no placeholders

It looks like the resolved URL is: /api/ledger/v2/ledger/accounts/creators%3A123_123_123%3Agross_earnings%3Apending
If I use postman, and include the account address with the colons unencoded (creators:123_123_123:gross_earnings:pending), then it works as expected. So the SDK is encoding the colon characters which appears to be breaking the endpoint.

Hello @WoodyWoodsta
We've just released a new version of the SDK that fixes this.
Regards

Thanks @flemzord 👍


Chip: Add active prop for toggle

Description

Added prop active to toggle active state

References: #1136
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update

How Has This Been Tested?

https://deploy-preview-2391--moduswebcomponents.netlify.app/
Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

@ElishaSamPeterPrabhu Can we get this updated to have a test to validates that the styles changed when active is true?

Added test case


Files added during Docker Build are User writeable

It seems that on some cases files which are added during build time are still writeable by the runtime user.
This should now be the case and instead only files in the persistent storage should be able to be written.

Is this still a feature request @Schnitzel?


Repo sync for protected CLA branch

The pull request is created from master637588551229780984 to master to fix git push error for protected CLA branch

@ghogen : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[SDPA-2718] Update docs / new-component / package-dependencies scripts.

JIRA issue: https://digital-engagement.atlassian.net/browse/SDPA-2718
Changed

Add scripts to root package.
Update scripts with 'yarn' naming and updated paths.
Replace 'file://' with version in ripple-ui-components/package.json.
Change 'new-package' naming to 'new-component' to match dir naming.
Add next steps prompt after new package is generated.
Get versions from package.json rather than lerna.json.
Update repository path on package.json template for new components.

Screenshots

Updated scripts to work with Storybook v5.

Updates to stories template
Updated URLs in package.json
Updated readme.MD storybook links to support multiple .storiesOf() functions with add.
Updated paths.


feat: permissions support

To be reviewed post #4
This PR adds support for operations on

Endpoint permissions
Entity permissions
Role operations corresponding to these identities.

Please take care of lint failures.


Translations

Currently arc.codes is probably one of the first markdown based serverless CMS systems. So it is pretty raw (and almost silly simple).
All the content is in https://github.com/arc-repos/arc.codes/tree/master/src/shared/en/aws. New translations should use their language code and in a new folder under shared. (Eg src/shared/pt-br, src/shared/es, src/shared/fr, etc)

Things we need to think about of the top of my head! I am in no way an i18n expert and def appreciate feedback for improving this.

I have three goals:

Supporting a new language should be as easy as writing markdown
The website content needs to be fully URL addressable by language so copy/paste always works
Everything remains completely backwards compatible

TODO

[ ] Add one new route get /:language/:section/:doc and make it smart enough to load the right thing from the right place at the right time ;)
[ ] Make a drop down for selecting a different language in the master layout https://github.com/arc-repos/arc.codes/blob/master/src/shared/render.js (which just redirects to the appropriate url)

(cc @ryanblock @kristoferjoseph @rdela and @GustMartins)

Just to throw a wrench into automation of i18n/translations 😉, I would say the design should allow for easily "flipping" to support languages written right to left. I would imagine you can do this with a separate or additional style sheet and when a RTL language is added there should somewhere to flag it as such.


Color Picker accessibility improvements

Context

Summary

Adds label to the swatches
Adds keyboard navigation

Relevant Technical Choices

To-do

User-facing changes

Testing Instructions

Open the color picker
Tab through all the fields and verify the focus outline is displayed correctly
Verify the swatches have aria-label
Verify arrow keys can be used to navigate in a color group (e.g. within the Default colors), and tab can be used to move between the color groups

[ ] This is a non-user-facing change and requires no QA

This PR can be tested by following these steps:

Checklist

[x] This PR addresses an existing issue and I have linked this PR to it in ZenHub
[ ] I have tested this code to the best of my abilities
[ ] I have verified accessibility to the best of my abilities (docs)
[ ] I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
[ ] This code is covered by automated tests (unit, integration, and/or e2e) to verify it works as intended (docs)
[ ] I have added documentation where necessary
[x] I have added a matching Type: XYZ label to the PR

Fixes #8657

I merged #8799, so now there are some conflicts, but should be trivial.


WFLY-10455 Update JPA documentation, remove references to older ORM versions

https://issues.jboss.org/browse/WFLY-10455
https://issues.jboss.org/browse/EAP7-999
First pass at JPA 2.2 doc update

@gbadner @simkam @gsmet could you please review this doc change pr?  Especially, the transformer section.  The .adoc file contain asciidoc.
I also removed a few incorrect debug log calls from the transformer.


Submit to pangeo-forge

Now that HDFReferenceRecipe is available in pangeo-forge, it should be possible to submit a new recipe repeating the work in this tutorial to https://github.com/pangeo-forge/staged-recipes
It would be nice to also do the NWM, but that would take some work on the recipe class to support the two-stage aggregation required by the large number of files.

What's the difference between https://github.compangeo-forge/staged-recipes and https://github.com/pangeo-forge/pangeo-forge-recipes?

pangeo-forge-recipes is the library containing the classes that get called during the run phase, when a dataset is processed.
staged-recipes is where individual datasets are defined via PRs (like in conda-forge), spawning one new repo per dataset. These recipes provide arguments to be passed to the classes in 1, in a yaml file and/or python code.

Think of it like fsspec-reference-maker's classes in 1., and each specific example that creates a JSON as 2.

Great. I want to work on getting the HRRR/GRIB2 stuff added as well. So if I understand it correctly, the GOES/NetCDF stuff will go in staged-recipes since you did the work of putting SingleHdf5ToZarr in pangeo-forge-recipes, while GRIB2 examples would require additions to both repos.

Yes, that's correct - the class currently in pangeo-forge-recipes only deals with HDF


Change import structure for ORTModel

With this PR, from optimum.onnxruntime import ORTModel imports from modeling_ort.py.
All examples use from optimum.onnxruntime.model import ORTModel so no need to modify them, and ORTModel was not used in the doc.
This is potentially breaking change.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Gently pinging @echarlaix, do we still need the previous ORTModel?

Merging as the failed tests are unrelated.


mouse over Ruvvi logo cursor is pointer but no link - nit

hovering the mouse at just the right spot just below the Ruuvi logo changes the cursor to 'pointer' . see attached

All of the logo should have the pointer cursor as it's a link that goes back to the dashboard.
It took me a while to figure out what's going on here. It's the new Mac feature "Live Text" where you can select text from an image!
Good find, but not much can be done about that.


Polyfill CSSStyleRule to include a styleMap property

See https://developer.mozilla.org/en-US/docs/Web/API/CSSStyleRule/styleMap

The styleMap read-only property of the CSSStyleRule interface returns a StylePropertyMap object which provides access to the rule's property-value pairs.

We have a StylePropertyMap. We need to update the polyfill to add styleMap to CSSStyleRule. Right now it's applied to the ancestor CSSRule.

Fixed in #33


Messages not updating after phone shuts off

Hello, i found a bug, everything works correctly but if meantime my phone battery dies, and i was chatting with customer, and that customer messages me while my phone is off, after i turn it on i recieve message in app, but on ticket system message is not updated. i have to ask him again.
I found solution i just
 "pm2 restart whaticket-backend" in terminal after turning my phone back on,
and customers messages appear in web.
But how i can make this automated? so after connection losts,and reconnects on reconnect it should automatically run  "pm2 restart whaticket-backend"

Can someone help me with this?, its really important if phone shuts off messages are not updated, i need it automatically, for busy company even 1 minute can mean alot, this doesnt happen if internet is lost and whatsapp still runs in app drawer, only when completley off


Improve error message when user have an outdated token

This is a bug report + feature request.
urcli crashes without a good error message if the token is outdated.
Which version of Node.js are you running (node -v)?
v6.10.2
Which version of urcli are you running (urcli -V)?
2.5.2
What behavior were you expecting to see?
My revenue summary.
What was the actual behavior?
The following error message:
19:03 $ urcli revenue 4
unhandled rejection: TypeError: this.reviews.forEach is not a function
    at Report.create (/home/gbra/npm/lib/node_modules/urcli/lib/commands/revenue.js:156:18)
    at /home/gbra/npm/lib/node_modules/urcli/lib/commands/revenue.js:243:14
    at next (native)
    at step (/home/gbra/npm/lib/node_modules/urcli/lib/commands/revenue.js:28:191)
    at /home/gbra/npm/lib/node_modules/urcli/lib/commands/revenue.js:28:361
    at process._tickCallback (internal/process/next_tick.js:109:7)

Describe the steps needed to reproduce the problem?

Let your token outdate
Run urcli revenue.
Get the error message.

What is your Operating System (e.g., Linux Ubuntu, MacOS, Windows)?

Fixing this in v3.

Fixed for the revenue command in the 63fa42c626dc3af9a94fdf276690090960d9b927 commit of the https://github.com/trolster/urcli/commits/next branch.