python311Packages.robotframework-pythonlibcore: 4.2.0 -> 4.3.0

Description of changes
Diff: https://github.com/robotframework/PythonLibCore/compare/refs/tags/v4.2.0...v4.3.0
Changelog: https://github.com/robotframework/PythonLibCore/blob/refs/tags/v4.3.0/docs/PythonLibCore-4.3.0.rst

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 270473 run on x86_64-linux 1

12 packages built:

python310Packages.robotframework-pythonlibcore
python310Packages.robotframework-pythonlibcore.dist
python310Packages.robotframework-selenium2library
python310Packages.robotframework-selenium2library.dist
python310Packages.robotframework-seleniumlibrary
python310Packages.robotframework-seleniumlibrary.dist
python311Packages.robotframework-pythonlibcore
python311Packages.robotframework-pythonlibcore.dist
python311Packages.robotframework-selenium2library
python311Packages.robotframework-selenium2library.dist
python311Packages.robotframework-seleniumlibrary
python311Packages.robotframework-seleniumlibrary.dist


Testing in React.

I have made a lot of progress getting this library to work with React do to all the help I have received from the community. I plan on posting a working version of this implemented with my React App with a test to help future newcomers.
My Error is    1)  Uncaught error outside test suite:      Uncaught ReferenceError: Image is not defined       at getImageInfo (node_modules/openseadragon/src/imagetilesource.js:106:43)       at $.TileSource (node_modules/openseadragon/src/tilesource.js:187:14)       at new $.ImageTileSource (node_modules/openseadragon/src/imagetilesource.js:72:22)       at Timeout._onTimeout (node_modules/openseadragon/src/viewer.js:2304:32)
My simple test is
 <Viewer showNavigator imageUrl={'https://i.imgur.com/b4z9aNS.jpg'} />
);

describe.only('The Viewer should have a ', () => {
 it('should a have a class', () => {
   expect(wrapper.find(`.${styles.container}`).length).to.equal(1);
 });
});

Any ideas on why Image is undefined?

Looks like this is the line that's failing:
https://github.com/openseadragon/openseadragon/blob/master/src/imagetilesource.js#L106
That's just the standard Image class that's built in to the browser:
https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/Image
Are you running your test suite in a browser or a headless browser, or is it just running in Node? If the latter, I guess you need to mock Image or something.
I'm glad to hear the React project is going well! I look forward to seeing the result :)

I guess you'll have to mock as much of the Image class as you need (in this case its addEventListener method). This is part of the challenge of testing client-side code with server-side tests. Maybe your test suite has some facility for dealing with this sort of thing? It certainly seems like it'll come up in other contexts besides OSD.


net: Remove legacy TCP stack

Remove legacy TCP stack as it is replaced by the new TCP2 stack.
The TCP2 stack has been the default stack from 2.4 release.
Signed-off-by: Jukka Rissanen<EMAIL_ADDRESS>

@jukkar
I am not sure if it is a good idea to remove legacy TCP stack support because some TCP features or requirements are supported in legacy TCP stack but not in TCP2.
To my understanding, there is no clear plan to implement these features in TCP2.
Some developers might not switch to TCP2 due to above reason.

I am not sure if it is a good idea to remove legacy TCP stack support

I'd generally be concerned too with removing TCP1 so soon. Especially given that this PR removes tests, without adding replacement (or clearly explaining the situation in the commit message, like "tests/net/tcp/src/main.c is removed because there's tests/net/tcp/XXX/YYY which contains all the relevant testcases and fully supersedes it.")

I am not sure if it is a good idea to remove legacy TCP stack support because some TCP features or requirements are supported in legacy TCP stack but not in TCP2.
To my understanding, there is no clear plan to implement these features in TCP2.

Could you elaborate what features are not supported in TCP2? The plan is to remove TCP1 so there is definitely a clear incentive to add any missing support to TCP2.

this PR removes tests

Those tests only work with TCP1 thus so they are not usable after the TCP1 is removed.

Those tests only work with TCP1 thus so they are not usable after the TCP1 is removed.

Can you please add that info explicitly to the commit message? And an extra sentence elaborating why they work only with TCP1 would also helpful.

I am not sure if it is a good idea to remove legacy TCP stack support because some TCP features or requirements are supported in legacy TCP stack but not in TCP2.
To my understanding, there is no clear plan to implement these features in TCP2.

Could you elaborate what features are not supported in TCP2? The plan is to remove TCP1 so there is definitely a clear incentive to add any missing support to TCP2.

TCP2 does not support TCP window size update.
TCP2 does not send our MSS to peer : #30367 (TCP1 does not support either)
TCP2 does not implement TCP alive check mechanism. (TCP1 does not support either)
TCP2 is not stable enough. If you do TCP loop back burn-in test, the system will stop or even crash.
The throughput of TCP2 is even worse than TCP1.

TCP2 does not support TCP window size update.

I will investigate this, it is probably easy to implement to TCP2.

TCP2 does not send our MSS to peer : #30367 (TCP1 does not support either)

TCP2 does not implement TCP alive check mechanism. (TCP1 does not support either)

TCP2 is not stable enough. If you do TCP loop back burn-in test, the system will stop or even crash.

My experience has been different so far. TCP2 has been much more stable than TCP1, especially if you have limited number of net_buf's and net_pkt's and you run out of them. Note that you should use the very latest upstream for TCP2 as I fixed one memory leak last week.

The throughput of TCP2 is even worse than TCP1.

This is interesting, I would like to hear what kind of testing you are using for that.
I did a short test with both qemu_x86 and sam_e70_xplained boards:
sam_e70_xplained
First with TCP2
$ cd samples/net/sockets/dumb_http_server_mt
$ cmake -B build -DBOARD=sam_e70_xplained . -DCONFIG_LOG_BUFFER_SIZE=65536 -DCONFIG_LOG_STRDUP_BUF_COUNT=400 -DCONFIG_NET_PKT_RX_COUNT=100 -DCONFIG_NET_PKT_TX_COUNT=100 -DCONFIG_NET_BUF_RX_COUNT=400 -DCONFIG_NET_BUF_TX_COUNT=400 -DCONFIG_NET_MAX_CONN=64 -DCONFIG_NET_MAX_CONTEXTS=32 -DCONFIG_NET_SAMPLE_NUM_HANDLERS=8 -DCONFIG_NET_TCP1=n
$ make -C build -j 9 flash

Then in Linux side, I used wrk tool https://github.com/wg/wrk
$ wrk -d 5 -t 16 -c 1000 http://<IP_ADDRESS>:8080
Running 5s test @ http://<IP_ADDRESS>:8080
  16 threads and 1000 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     8.45ms   26.05ms 212.08ms   98.31%
    Req/Sec   184.78    133.27   363.00     50.00%
  356 requests in 5.10s, 763.54KB read
  Socket errors: connect 0, read 380, write 0, timeout 0
Requests/sec:     69.84
Transfer/sec:    149.78KB

Then with TCP1
$ cd samples/net/sockets/dumb_http_server_mt
$ cmake -B build -DBOARD=sam_e70_xplained . -DCONFIG_LOG_BUFFER_SIZE=65536 -DCONFIG_LOG_STRDUP_BUF_COUNT=400 -DCONFIG_NET_PKT_RX_COUNT=100 -DCONFIG_NET_PKT_TX_COUNT=100 -DCONFIG_NET_BUF_RX_COUNT=400 -DCONFIG_NET_BUF_TX_COUNT=400 -DCONFIG_NET_MAX_CONN=64 -DCONFIG_NET_MAX_CONTEXTS=32 -DCONFIG_NET_SAMPLE_NUM_HANDLERS=8 -DCONFIG_NET_TCP1=y
$ make -C build -j 9 flash

The results were much worse with TCP1
./wrk -d 5 -t 16 -c 1000 http://<IP_ADDRESS>:8080
Running 5s test @ http://<IP_ADDRESS>:8080
  16 threads and 1000 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    48.89ms  137.80ms 628.82ms   86.67%
    Req/Sec     5.58     11.38    50.00     88.46%
  45 requests in 5.10s, 94.04KB read
  Socket errors: connect 0, read 67, write 0, timeout 0
Requests/sec:      8.82
Transfer/sec:     18.44KB

The numbers are not very good for either of these examples but TCP2 was 8 times faster in this test.
qemu_x86
$ cmake -B build -DBOARD=qemu_x86 . -DOVERLAY_CONFIG=../echo_server/overlay-e1000.conf -DCONFIG_LOG_BUFFER_SIZE=65536 -DCONFIG_LOG_STRDUP_BUF_COUNT=400 -DCONFIG_NET_PKT_RX_COUNT=100 -DCONFIG_NET_PKT_TX_COUNT=100 -DCONFIG_NET_BUF_RX_COUNT=400 -DCONFIG_NET_BUF_TX_COUNT=400 -DCONFIG_NET_MAX_CONN=64 -DCONFIG_NET_MAX_CONTEXTS=64 -DCONFIG_NET_SAMPLE_NUM_HANDLERS=64 -DCONFIG_NET_TCP1=n

The TCP2 results:
$ wrk -d 5 -t 16 -c 1000 http://<IP_ADDRESS>:8080
Running 5s test @ http://<IP_ADDRESS>:8080
  16 threads and 1000 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency   134.43ms  277.62ms   1.42s    86.59%
    Req/Sec    13.94     31.32   130.00     90.91%
  99 requests in 5.04s, 224.38KB read
  Socket errors: connect 0, read 99, write 0, timeout 17
Requests/sec:     19.65
Transfer/sec:     44.53KB

and with TCP1:
wrk -d 5 -t 16 -c 1000 http://<IP_ADDRESS>:8080
Running 5s test @ http://<IP_ADDRESS>:8080
  16 threads and 1000 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency   483.17ms  238.02ms 625.42ms   66.67%
    Req/Sec     1.75      2.22     5.00     75.00%
  4 requests in 5.04s, 8.36KB read
  Socket errors: connect 0, read 4, write 0, timeout 1
Requests/sec:      0.79
Transfer/sec:      1.66KB

    The throughput of TCP2 is even worse than TCP1.

I can't ack that either. In my list, TCP2 has slight (15-20%) performance improvement over TCP1. I base my evaluation based on downloading large file from real-world Internet, the big_http_download sample.
The opposite direction (device->host) is also interesting, but there was no easily usable option to test that. I now see that dumb_http_server_mt has an option to serve 100K file, but that still too little to assess sustained throughput. And dumb_http_server_mt is not POSIX-compliant app, so there's always suspicion that "it uses dirty Zephyr API hacks to workaround network stack issues". dumb_http_server remains the baseline test for me, and it shows much more humble figures comparing to the "adhoc Zephyr API/MT" version. And IMHO, we should target "unadorned BSD sockets" for performance optimizations first thing (and judge results by it).

This PR is also now explicitly marked as "2.6.0", which alleviates concern of removing TCP1 too soon. And AFAIK, 2.6 is supposed to be an LTS release, so the desire to remove TCP1 before it is understood - to not maintain 2 stacks in the LTS.
Note that I personally still not going to approve this, unless my suggestions for elaborating the commit message (https://github.com/zephyrproject-rtos/zephyr/pull/31744#issuecomment-773186687) are addressed. But given the above circumstances with LTS, that won't preclude merging this, someone else will for sure approve, no matter how bad the commit message is ;-).

TCP2 does not support TCP window size update.
TCP2 does not send our MSS to peer : #30367 (TCP1 does not support either)

@kevin0402 See #32076, it has the TCP window size update and also sends our MSS to peer. Actually TCP1 supports sending MSS to peer already.
Please try and report if they do not work as expected.

Fixed merge conflict.


error messages do not provide details without additional effort.

What is the expected enhancement?
Currently, if a job fails out, one gets an exception like:
IBMQJobFailureError: 'Unable to retrieve result for job xxxx. Job has failed. Use job.error_message() to get more details.'
seeing the actual error (which presumably the user will want), requires the extra step described in the message, and at least on the IQX takes an additional 16 seconds to even fetch the error message.  This is really offputting compared to putting the error message in the exception string.
So the enhancement would be to put the error_message in the exception string.

I can second this as being a really useful addition.


fix: suppress debug logs when using -q

Describe the PR
Fixes an issue where certain debug logs were always directed to stderr, even if the -q flag was provided.
Relation issue
#1255
Additional context
This fix will be helpful for anyone who wants to suppress all debug output (e.g. when generating API docs as part of a git commit hook).
I took the path of least resistance here since I'm not sure on the development philosophy for this project. For example, I initialized the new Gen.debug field in the Build() method instead of the New() method. Happy to pass the debugger in as an arg to New() instead if that's preferred.
I did run the changes and they work as expected.

(Whoops, hadn't noticed this was already merged when I requested review 😄, thanks! )


Datagrid columns have minimum width

Select one ...  (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Expected behavior

It should be possible to fully control the width of datagrid columns, hence there should also not be a minimum width. There are situations in which a denser grid with small columns makes sense, e.g.:

Actual behavior

The width of datagrid columns can be set by using CSS. However, the minimum width of a datagrid column is currently 96px. I do not know if this is by design or not, however it should either be clearly documented or the constraint should be removed.
Reproduction of behavior

https://plnkr.co/UVREum

Create a datagrid column that is sized to 40px.
Observe that the column is still 96px wide.

Environment details

Clarity version: 0.10
Browser: all

Any workarounds possible to achieve this in the current version?

@Trojaan
If the goal is to have a non-sortable, non-filterable, tabular display of a fixed set of data (as in the OP example), you should just use a table.

I also need this.. there are some cols that contain for eg Qty or other small width (with no need to sort or filter), but I still want to use sort/filter for others cols and pagination for the set as a whole.
I toyed around with changing the min-width: 4rem to 3rem or 50px in the 4 spots in CSS and it seems to work but I see some artifacts as below that are "sort of" related to #2906 or #1725. Actually seems to be a combination of the column header length AND the page size ie data grid size.
Top pic shows wider datagrid where clicking on the header did not affect col header separator position adversely, next one shows  smaller grid but with end col selected, final pic shows same smaller grid but with same col header selected as original, but this time shows artefact - col separator pushed out to the right.
Would appreciate any suggestions with CSS to workaround these col header artifacts.
Loving your work though..

@Trojaan
If the goal is to have a non-sortable, non-filterable, tabular display of a fixed set of data (as in the OP example), you should just use a table.

@mathisscott - the main goal of using a UI Framework is uniform output - the 'just use a table' approach creates output that is not consistent with the datagrid style - you end up with 2 differently styled tables - that's an unfortunate stance to take for end users - couldn't it be prudent to check if those features are not leveraged within the clr-dg-column component and unset the min-width style?  or something along those lines instead of saying 'just use something else' outright  ...
@hippee-lee mentioned here that he had figured out why the .% style doesn't work - it would be great if this was resolved - at this point, I could not even get the .px style to work - html always shows width: 0px - datagrid width has become a frustrating thing to work around -
One thing I noticed is when you get the cursor change to <-||-> (if you were to resize the columns) & double-click, then all of the widths are calculated properly based on the cell data width ... perhaps the code within that double-click event should be used from the datagrid initialization/calculation code?  (in this case, there are 9 columns where they are auto-initialized to all be the exact same width (0px) despite some cell data being longer than others)

@bret-bailey

Our tables should have style parity with the datagrids. If that is not the case can you replicate the issue and submit a new ticket focused on that?
I know this is a problem for you and I'm really sorry that I don't have a satisfactory answer for you. I hope I can explain some of whats going on properly. Here goes - the datagrid layout is complex under the hood. In order to support the various combination of use cases we will likely stay with a flexbox layout and this is what I believe is causing the issue with % widths on columns and cells. To this point, I haven't found a way to support % widths + flex: 1 1 auto + user resized columns or declared widths on columns + the requirements for the last column1 + the use case when a user has resized a column`
In addition to the last point. Width are calculated buy putting only the columns, rows and cells into a container with native table element styles with display: table;     table-layout: auto; - this allows us to let the browser handle the sizing calculation ands provide auto sizing for any content given to columns and cells and then we can apply specific widths as we need to or not based on the combination of datagrid features in use at any given time
If you have any ideas or want to take a stab at coming up with a solution please let me know I'll be happy to support that as best I can. Right now this isn't one of the issues we can work on given some of the other priorities related to a11y and other larger feature tickets.

1: When all columns are resized or have a width set by the consumer then the last column cannot have a fixed width of any kind. It needs to flex to take up the remaining width of the table even when the width of the table overflows on the x axis.

Related to the comment about not getting a px width to work. Here is an example where I set the first colum to a 500px width: https://stackblitz.com/edit/gh-1405-px-width-column

The min-width on column is not a bug. This is expected behavior of Datagrid columns. Users could simply override the default min-width style as below:
<clr-dg-column [style.min-width.px]="anyPxValueYouWant"></clr-dg-column>

Maybe, this is a documentation issue.

@hippee-lee - thank you for the explanation - definitely can see how difficult a problem this really is to tackle - I'll give it some further thought & review the code to see if something pops out
https://gh-1405-px-width-column-ncmdfk.stackblitz.io
Here is an example of 'just a table' compared to the datagrid - without any style changes - they are noticeably different - specifically, header text alignment & dividers - our product uses the 'datagrid-compact' class, which only further separates the uniform ui differences
@Shijir - thanks for that suggestion - in order for that to work, you still need the width setting as well - so you end up with this:
<clr-dg-column [style.min-width.px]="pxValue" [style.width.px]="pxValue"></clr-dg-column>
However, it is noticeable that the columns no longer align with the cell values once you set the min-width below 96 - so I'm not certain that this is a viable work around
Oddly enough, despite the stackblitz working as expected with regards to setting the width and min-width - both values are still ignored within my application - very strange - something else must be affecting the width styles ...

I also have a pretty good use case where I need to only display status icons in a column but since there's a minimum width set to it, I can't set the width same as the icon.

As a workaround, override the css for the column with status icons.
Here is one way to do that with an Angular style binding but it could also be accomplished with css placed directly on the column.: https://stackblitz.com/edit/gh-1405-px-width-column-gjlaxw?file=src/app/app.component.html
Note: this approach needs the styles applied to with the column and the cell with the status icon in it.

There is a workaround available for this issue, and we recommend using it for Clarity Angular. As we build Clarity Core implementations, we expect that this issue won’t be an issue or will be configurable on the application side. To help us clean up our backlog, we are going to close this with a functional workaround available and suggest you follow updates for Clarity Core for enhancements that can support your use case with Clarity Core components.

There is a workaround available for this issue, and we recommend using it for Clarity Angular. As we build Clarity Core implementations, we expect that this issue won’t be an issue or will be configurable on the application side. To help us clean up our backlog, we are going to close this with a functional workaround available and suggest you follow updates for Clarity Core for enhancements that can support your use case with Clarity Core components.


Screening Plan Builder

Please name the task using the following information: Browser - Name. Give this issue a "FED" or "BED" label, alongside the "Bug" label.
Description
Current: Skill names have disappeared

Expected: Skill names should appear left of/above description

[ ] This bug requires a unit test.

Steps to Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Images
Place image attachments (wireframes, etc.) here.
Additional Context
Add any other context about the problem here.

Duplicate


Uncaught TypeError: useDragDropContext is not a function or its return value is not iterable

In newly created Solid.js application from template, installing the solid-dnd dependencies and copy-paste an example I have the next error within the white page:
create-pointer-sensor.js?v=88ebfb3e:4 Uncaught TypeError: useDragDropContext is not a function
 or its return value is not iterable
    at createPointerSensor (create-pointer-sensor.js?v=88ebfb3e:4:108)
    at DragDropSensors (drag-drop-sensors.jsx:3:5)
    at dev.js:515:12
    at untrack (dev.js:421:12)
    at Object.fn (dev.js:511:37)
    at runComputation (dev.js:691:22)
    at updateComputation (dev.js:676:3)
    at devComponent (dev.js:522:3)
    at createComponent (dev.js:1222:10)
    at get children [as children] (App.tsx:156:2)

App.tsx
import { Component, For } from "solid-js";

import {
	DragDropProvider,
	DragDropSensors,
	DragOverlay,
	createDraggable,
	DragEventHandler,
} from "@thisbeyond/solid-dnd";

const Draggable = (props) => {
const draggable = createDraggable(props.id);
  return (

      Draggable {props.id}

  );
};

export const DragMoveExample = () => {
  let transform = { x: 0, y: 0 };

  const onDragMove: DragEventHandler = ({ overlay }) => {
    if (overlay) {
      transform = { ...overlay.transform };
    }
  };

  const onDragEnd: DragEventHandler = ({ draggable }) => {
    const node = draggable.node;
    node.style.setProperty("top", node.offsetTop + transform.y + "px");
    node.style.setProperty("left", node.offsetLeft + transform.x + "px");
  };

  return (
    <DragDropProvider onDragMove={onDragMove} onDragEnd={onDragEnd}>
      <DragDropSensors />

        <Draggable id={1} />
        <Draggable id={2} />

      <DragOverlay>
        {(draggable) =>
Draggable {draggable.id}
}
      </DragOverlay>
    </DragDropProvider>
  );
};

const App: Component = () => {
  return (
      <>
        <DragMoveExample />

Hello tailwind!

    </>
  );
};

export default App;

package.json
{
  "name": "dnd",
  "version": "0.0.1",
  "description": "",
  "scripts": {
    "dev": "vite",
    "build": "vite build",
    "serve": "vite preview"
  },
  "license": "MIT",
  "devDependencies": {
    "autoprefixer": "^10.4.8",
    "postcss": "^8.4.16",
    "tailwindcss": "^3.1.8",
    "typescript": "^4.8.2",
    "vite": "^3.1.4",
    "vite-plugin-solid": "^2.3.9"
  },
  "dependencies": {
    "@thisbeyond/solid-dnd": "^0.7.1",
    "solid-js": "^1.5.7"
  }
}

Thank you in advance for any thought on this point.
Might be i'm doing something wrong, cause I just started to dig into solid ^^

Hmm. That's definitely unexpected. I'll try and take a look at the weekend.

Hello! Is this issue resolved? If yes, would like to know what happened? If no, I also need some help regarding the same issue.

I'll need an example repo of this happening in order to help more. Can you share a link to where this is occurring for you?

Hi! The same problem.
create-draggable.js?v=49d3789b:6 Uncaught (in promise) TypeError: useDragDropContext is not a function or its return value is not iterable
    at createDraggable (create-draggable.js?v=49d3789b:6:77)
    at _Hot$$Folder (Folder.jsx:8:20)
    at @solid-refresh:10:42
    at untrack (dev.js:421:12)
    at Object.fn (@solid-refresh:10:28)
    at runComputation (dev.js:691:22)
    at updateComputation (dev.js:676:3)
    at createMemo (dev.js:238:10)
    at hmrCompWrapper (@solid-refresh:7:20)
    at dev.js:515:12

Check your vite.config.ts contains the following:
optimizeDeps: {
  extensions: ["jsx"],
},

For example:
import { defineConfig } from 'vite';
import solidPlugin from 'vite-plugin-solid';

export default defineConfig({
  plugins: [solidPlugin()],
  server: {
    port: 3000,
  },
  build: {
    target: 'esnext',
  },
  optimizeDeps: {
    extensions: ["jsx"],
  },
});

My config:
import { defineConfig } from "vite"
import solidPlugin from "vite-plugin-solid"
const path = require("path")

export default defineConfig({
  plugins: [solidPlugin()],
  resolve: {
    alias: {
      "@": path.resolve(__dirname, "./src"),
    },
  },
  server: {
    port: 3000,
  },
  build: {
    target: "esnext",
  },
  optimizeDeps: {
    extensions: ["jsx"],
  },
})

It's doesn't help. The issue still not resolved. (

For reference, I tested by creating a new repo from the solid ts template, updated all dependencies to latest and installed solid-dnd. This worked for me 🤷♂
I'll need more info to help further:

What versions of solid, vite, vite-solid-plugin do you have?
What does your package.json look like?
Do you have a repo I can look at?

Perhaps, I found what’s wrong. If I import createDraggable and define  Draggable component directly in App.jsx everything works. But if make component in separate file I see the error on step const draggable = createDraggable()   Maybe I don't understand something fundamental in Solid

Are you using the needed .jsx (or .tsx for typescript) extension for that other file?

After a few hours of dancing it finally works ))) I made the new project and move all my components there step by step. So, I don't know what exactly was wrong but I'm sure optimizeDeps make sense, because without that option the error appears every time.

Good to hear!
Curious: do you still have that alias entry in your vite config? If not, perhaps that was causing an issue.

My vite config looks exactly like this
import { defineConfig } from "vite"
import solidPlugin from "vite-plugin-solid"
const path = require("path")

export default defineConfig({
  plugins: [solidPlugin()],
  resolve: {
    alias: {
      "@": path.resolve(__dirname, "./src"),
    },
  },
  server: {
    port: 3000,
  },
  build: {
    target: "esnext",
  },
  optimizeDeps: {
    extensions: ["jsx"],
  },
})

@martinpengellyphillips sorry for being out of touch.
You r right:
optimizeDeps: {
    extensions: ["jsx"],
  },

fixes this issue for me.  Thank you : 🙏

what this code does?
optimizeDeps: {
    extensions: ["jsx"],
  },

we need to delete node_modules folder and install packages again also to make it working.

I'm not able to use it too and no solution worked for me, except for this:
I basically switch the exports map putting "solid" as last entry 😄

There is also reproducible example in a PR for my project where I'm trying to update all dependencies (both solid and solid-dnd)
https://codesandbox.io/p/github/riccardoperra/codeimage/build/update-dependencies?workspace={"gitSidebarPanel":"PR","sidebarPanel":"GIT"}

I just ran into this error. Looks like the var useDragDropContext in dev.jsx is returning a null when attempting to useContext from Context generated higher up from Solid's direct createContext. I suspect it's due to my use in a condition render... will update here if I solve it.

@martinpengellyphillips , I ran into this issue an was able to drill down to see that useDragDropContext from dev.jsx was returning null. I was able to replicate it by commenting out the DragDropProvider and DragDropSensors from one of the Solid examples:
const DragDemo = () => {
  return (
    // <DragDropProvider>
    //   <DragDropSensors>
        <Sandbox />
    //   </DragDropSensors>
    // </DragDropProvider>
  );
};

I suspect the trouble in my actual codebase is due to putting the provider inside a conditional render or something. Going to try to start small and add to a working example until I break it, but hopefully this insight helps show what might be happening. Definitely a failure of the context not being available during the createXable function.

So in my case, I was making a wrapper for DND components and was using {children}. SolidJS expects you to return children as a function to comply with how it does reactivity ( https://www.solidjs.com/tutorial/props_children ). So after complying with the reactivity correctly, it all works just fine. Not sure if this was the case for others, but in my case it came down to bad reactivity.


"mystery cave chest" inaccessible?

I'm admittedly not too experienced with this game so I might just be missing something, but the completion log says that "mystery cave chest" has the Satchel and is accessible with Autumn, L2 Rang, and Magnets. I can't for the life of me find anything that would be a Mystery Cave with the tools given to me (including bombing multiple walls).

Sorry that the names in the log file are so unhelpful; they were originally written with terseness in mind (for use in the code) but should be revised to actually be understandable. That location is the cave blocked by mushrooms on the screen north of what's normally the mystery seed tree.

I probably would have made the connection if I had been able to get up there. Is the pathing assuming access to Mystery Tree without any way to burn down the trees on the east edge of Horon?

Yes, there are a few different ways to get to that area. You can burn the trees, traverse Natzu with an animal companion, swim down from Mt. Cucco, or exit Subrosia via the portal near the dance hall.

I'm locked at South Subrosia from having no Feather, locked at North Horon from having no Bracelet, and locked at East Horon from having no Satchel. The log thinks that Magnetic Gloves is the next key in the sequence, so I'm thinking the pathing erroneously thinks you can get from South Subrosia to North with them?

Can you post the log file?

oos-randomizer_log_2018-08-20_210357.txt


Kube-Prometheus rules version not matching with K8S1.15

I executed below command ..
jb install<EMAIL_ADDRESS>This downloads all the Kube-prometheus related jsonnet files.
I created a new jsonnet file to update a rule by importing  'kube-prometheus/kube-prometheus.libsonnet' .
But I finally find that the Prometheus-rules.yaml created , has rules which is from rules folder and not from rules1.14 folder.
We have Kubernetes 1.15 .And We use Kube-prometheus-stack.And it uses rules1.14 folder.
How to make jb install to download files that can generate rules1.14 ?

I have found jb install<EMAIL_ADDRESS>works for rules1.14.
I am not sure if this release 0.6 is fine with Kubernetes 1.15 version.Please confirm.

There is no tight dependency, but you should check https://github.com/prometheus-operator/kube-prometheus#compatibility

That is what confuses me.
rules 1.14 is for Kubernetes version >= 1.14.
But Kube-prometheus release 0.3 which is compatible with Kubernetes1.15  downloads rules and not rules1.14.
Only Kube-Prometheus 0.6 downloads rules1.14.  Thatswhy I am not sure if we need to download 0.3 or 0.6.
Please advice

Closing as k8s 1.15 and 1.14 reached EOL


Add support for insertions

https://varnomen.hgvs.org/recommendations/DNA/variant/insertion/
https://varnomen.hgvs.org/recommendations/protein/variant/insertion/

Only focused on simple insertions (i.e. format <positions_flanking>ins<inserted_nucleotides> such as NC_000023.10:g.32867861_32867862insT) for now to address MetaKB misses (#95).


Inline tags doesn't change icon

Hi, i am having some problems trying to define multiple points with different tags ex.
Venice airport tag:dep-plane
The point shows up on the map but the icon does'n change

I also would like to understand if i can define multiple points with different tags in the same note
Thanks

Turns out that the regex that matches inline tags (as opposed to note tags which uses the built-in Obsidian system) doesn't take into account the dash character.
I'll fix it, but in the meantime, take into account that alphanumeric characters and an underscore should work.

Fixed in 1.1.0.


fix expires when max age is 0

Coverage increased (+0.09%) to 85.571% when pulling bed58d466b3095f95f75e406b5f80005bd29bebe on fix/max-age-0 into 96c3e0ffa8df3e586873e833b927d66c8927898e on master.


RetryFunc added

This PR replaces MaxRetries constant with RetryFunc that dynamically decides if a retry should be performed, making it possible to use rate-limiting and various feedback loops set by client's owner.
No APIs are broken except the removal of DefaultMaxRetries constant. It is possible to bring it back, but it would make the code less transparent.
Similar change can be made to every version of the client.

It seems that SetMaxRetries sets the max total HTTP request number per one client request instead of number of retries (excluding original request).
I've preserved previous behaviour for now and updated the SetMaxRetries()'s comment, but it can be misleading.

Thanks for your contributions.
For elastic v3 (for ES 2.x) and v5 (for ES 5.x) I've already added retries and backoff, which seem to be a bit more enhanced than your solution. However, they are not backported to v2 (for ES 1.x).
Are you still on ES 1.x, or did you overlook the Wiki page?

@olivere Yep, I'm still on ES 1.x.

Can you check if the Retrier will also work for you? If so, I'd prefer backporting to have a consistent implementation across all versions. Or even better: Create a PR based on e.g. this commit for elastic.v3.

Aha! Didn't see docs about the Retrier. Thanks, that'll do; I'll backport it and create a new PR. 🙂

If CI is okay, I will push 2.0.58.
Thanks for your time working on the PR.


Doc running hooks async from hook chain

Mention https://medium.com/@mattchewone/feathersjs-background-hooks-e105bc82d84a

Isn't this just run parallel?

Yes, I added runParallel with Matt's approval.


firebase_app_check throws error

Bug report
Describe the bug
A clear and concise description of what the bug is.
After installing all the dependencies of flutter firebase i'm getting exception from firebase_app_check
Steps to reproduce
Steps to reproduce the behavior:

Go to 'pubysec.yaml and add dependecies.

Firebase

firebase_core: ^1.11.0
firebase_analytics: ^9.0.5
firebase_auth: ^3.3.5
firebase_messaging: ^11.2.5
firebase_crashlytics: ^2.4.5
firebase_app_check: ^0.0.6+6

initialize in main.dart
main() async {
WidgetsFlutterBinding.ensureInitialized();
await Firebase.initializeApp();
await FirebaseAppCheck.instance.activate();

add in build.gradle.
implementation 'com.google.firebase:firebase-appcheck-playintegrity:16.0.2'

run the app

See error or incorrect behavior

../../../development/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_app_check_platform_interface-0.0.4/lib/src/method_channel/utils/exception.dart:13:11: Error: Method not found: 'Error.throwWithStackTrace'.
Error.throwWithStackTrace(exception, stackTrace);
^^^^^^^^^^^^^^^^^^^
../../../development/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_app_check_platform_interface-0.0.4/lib/src/method_channel/utils/exception.dart:16:9: Error: Method not found: 'Error.throwWithStackTrace'.
Error.throwWithStackTrace(
^^^^^^^^^^^^^^^^^^^
../../../development/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_app_check_platform_interface-0.0.4/lib/src/method_channel/utils/exception.dart:11:7: Error: A non-null value must be returned since the return type 'Never' doesn't allow null.
Never convertPlatformException(Object exception, StackTrace stackTrace) {
[✓] Flutter (Channel stable, 2.5.0, on macOS 12.6 21G115 darwin-arm, locale en-IN)
• Flutter version 2.5.0 at /Users/gauravswarankar/development/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 4cc385b4b8 (1 year, 1 month ago), 2021-09-07 23:01:49 -0700
• Engine revision f0826da7ef
• Dart version 2.14.0

@Anonymousgaurav
You are on very old version of the framework along with plugins, so I recommend to upgrade all dependencies to latest and framework to latest stable, which should resolve the issue you are facing.
Closing for now. If, after upgrading, you see same behavior, write in comments and I'll reopen it.


Image clipping and combining support

We need support for image clipping and combining in the ResourceManager, to support the functionality here: http://www.qooxdoo.org/5.0.1/pages/development/image_clipping_and_combining.html

Given that the generator does image combining and clipping into the resource directory (and therefore the results would tend to be committed as part of the source), if the compiler took a different approach (ie fully automatic) can we avoid reimplementing the generator method?  EG the generator method is deprecated but still available for existing projects because the generator is available?
For image combining, it should be entirely automatic for the compiler to be able to add images into one big image and keep track of offsets; when the code refers to an image which has been copied into a combined image, the framework would be able to select the correct part with nothing more that the original image resource path.
Combining would be done based on rules which are provided in config.json and done on a path basis, for example:
    resources: [
      "$defaultIcons": {
        "filesize < 100": "inline",
        "imageWidth <= 50 && imageHeight <= 50": "combine"
      },
      "qx/decoration/Classic/**": {
        "filesize < 100": "inline",
        "filename.startsWith('qx/decoration/Classic/colorselector/')": "none",
        "imageWidth <= 50 && imageHeight <= 50": "combine"
      },
      "qx/decoration/Indigo/**": {
        "filesize < 100": "inline",
        "filename.startsWith('qx/decoration/Indigo/colorselector/')": "none",
        "imageWidth <= 50 && imageHeight <= 50": "combine"
      },
      "qx/decoration/icon/Oxygen/16/**": "$defaultIcons",
      "qx/decoration/icon/Oxygen/22/**": "$defaultIcons",
      "qx/decoration/icon/Oxygen/32/**": "$defaultIcons",
      "qx/decoration/icon/Oxygen/48/**": "$defaultIcons",
      "qx/decoration/icon/Oxygen/64/**": "$defaultIcons"
    ]

In this hypothetical example, the rules are mini expressions which are just javascript expressions; well defined variables exist such as filesize, imageWidth, imageHeight etc.  When a match is found for the path and for a rule, the mapped value can be either inline (to convert to base64 inline encoding), combine (to combine into a single file for the path), or none (to allow for exceptions to the rule.
The last few paths (beginning "qx/decoration/icon/Oxygen/...) don't have an object of rules, instead it has a string which is used to match against the list of paths - by specifying an impossible path like $defaultIcons this allows for simple reuse of rule sets between paths.
For image splitting, the same process should work but would use the original image and meta files to create virtual paths that use the original, pre-combined image.

Sounds great! I hope that most of what it takes to implement the image processing / CSS stuff is already available on NPM and you would only have to add glue code that uses the rule syntax above to the exeute the neccessary library API methods. one thing: maybe you might want to use "file.name" and "image.with" in the javascript expressions? I find that easier to remember than to have to think about "Was it fileName or filename vs. imagewidth or imageWidth??"

We are migrating our tool-stack from the old generator to the node-based compiler and everything works out quite well so far. The lack of the image combining feature though is posing quite a problem. Do you think it is going to be ported soon? If not, are there any alternatives that you can point us to for us to investigate?

Unfortunately this is something that keeps slipping due to other pressures and I don't have any time to look at implementing this soon enough for your needs.
However, if you have a lot of investment in split/combined images, and as the original generator based split/combine is based on imagemagick, it should be fairly straight forward to implement something yourself which batch splits/combines.
For splitting, you just have to output the portions of the image, for combining there needs to be a JSON structure output that can be incorporated into the resources.
If you can write something in node.js to do this, I can help you get it integrated into the compiler code?

I am unfortunately not familiar enough with node.js, so I toyed a bit with the "montage" command of ImageMagick and performed some XSLT wizardry on its HTML output. Everything is wrapped in an ANT build script.
My experimental setup results in the exact same content as what the Python tool-stack was generating, i.e. one big PNG in the resources folder, and an associated .meta file with JSON information for each named resource - see below example
[
  "waffle/icons/fatcow-16/accept.png": [ 16, 16, "png", "source/resource/quadro/combined/180/fatcow-16.png", 0, 0 ],
  "waffle/icons/fatcow-16/add.png": [ 16, 16, "png", "source/resource/quadro/combined/180/fatcow-16.png", -16, 0 ],
  ...
]

Do you think it is possible to integrate this information into the new ResourceManager without too much hassle from your side?

Could this be plugged into the compiler using a package that contains a compile.js that hooks into the compiler workflow and calls the ANT script?
https://qooxdoo.org/documentation/6.0/#/development/compiler/configuration/api?id=events-and-hook-methods
Then you simply need to make this package a dependency of your app to get image combining. This would be a quick-and-dirty way that doesn't require us to define any format or protocol at this point, but would make it possible for others to use it as well. This way we don't have to commit to any particular schema or implementation.

Also, @gnikolaidis can use what he has already written and the ANT dependency isn't a problem because it is a package and not a core component.

As long as the .meta file is properly read and used at runtime (I didn't have the time to test that), the current ANT-based setup is doing the job really well for us for now.
I have the feeling that it is not the compiler's job to perform the actual combining, as there are too many use cases and accommodating for everyone's needs will be a daunting task. It would be sufficient to write some documentation about the meta file, i.e. its format, its place in the directory structure, its use at runtime.
In the future, a solution like @cboulanger suggests is probably the way to go, as it separates concerns, doesn't add unnecessary dependencies, and fits well within the compiler's pluggable architecture.

Thanks to a dive into the compiler code, namely qx.tool.compiler.resources.Manager, and some luck, I managed to get image combining to work! In my .meta sample file above, I had to remove the "source/resource" prefixes from the composite image paths (position 3 of each array). Thinking again about it, it was an obvious mistake from my part- the platform runtime works with resource names instead of paths.
BUT I stumbled upon what I believe is a bug of the compiler: the first time I build the project with --clean, composite information ( the "composite", "x" and "y" keys of combined resources) is missing from resource-db.json. Invoking the compiler a second time, without --clean, makes them reappear.
# start with a clean build
> qx compile --target build --clean
> grep composite compiled/build/resource-db.json
# image combining information missing from resource-db.json
# invoking the compiler a second time, without --clean this time
> qx compile --target build
> grep composite compiled/build/resource-db.json
# image combining information found in resource-db.json, and properly working at runtime

This is 100% reproducible; the qx/decoration/... split PNGs of the stock themes display the same problem.

@gnikolaidis glad you've got a solution!
Please file an issue for the --clean bug

A gist for some basic horizontal image combining using the new tooling, inspired by comments above. https://gist.github.com/rad-pat/c568fa4467f85f56beb0a53bf71d9ec1


Iguana OS X dock icon is a bit large

@miketaz100
https://github.com/SuperNETorg/Iguana-application/issues/40

New Agama Wallet dock icon is smaller. If any other perfectionist request, please reopen this one again or make a new one.


Update workspace-data-exfiltration-protection.md

This constraint is no longer valid:
Metastore is disabled in Synapse workspaces that have Managed Virtual Network with data exfiltration protection enabled. You can't use Spark SQL in these workspaces.

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


Custom SSLContext Error - SNI and cert verify false support

I am trying to make HTTP2 request to a server(virtual hosted) which gives SSL certificates based on host header value(SNI).
# conn = hyper.HTTP20Connection('http2.akamai.com', port=443, ssl_context=context)
# conn.request('GET', '/path', headers={'Host': 'www.mywebsite.com'})

Hyper-h2 package for Python won't support SNI or disabling cert verification! https://hyper.readthedocs.io/en/latest/advanced.html#ssl-tls-certificate-verification
One way to disable certs verification is by having custom SSLContext, and stuck in protocol assertion error
Basic code to make HTTP2 call with custom SSLContext:
import ssl
import hyper

# Custom SSLCONTEXT for not verifying SSLCertificate and Hostname
# or need SSLCONTEXT for SNI support
context = ssl.SSLContext(ssl.PROTOCOL_SSLv23)
context.verify_mode = ssl.CERT_NONE
context.check_hostname = False
hyper.tls._context = context

conn = hyper.HTTP20Connection('http2.akamai.com', port=443, ssl_context=context)
conn.request('GET', '/')

print conn.get_response()

Error :
Traceback (most recent call last):
  File "ssl_custom.py", line 32, in <module>
    conn.request('GET', '/')
  File "/usr/local/lib/python2.7/site-packages/hyper/http20/connection.py", line 281, in request
    self.endheaders(message_body=body, final=True, stream_id=stream_id)
  File "/usr/local/lib/python2.7/site-packages/hyper/http20/connection.py", line 544, in endheaders
    self.connect()
  File "/usr/local/lib/python2.7/site-packages/hyper/http20/connection.py", line 373, in connect
    assert proto in H2_NPN_PROTOCOLS or proto == H2C_PROTOCOL
AssertionError

Stackoverflow link: https://stackoverflow.com/questions/45293922/hyper-http2-custom-sslcontext-error

If you are using a custom SSLContext you must set it up appropriately for HTTP/2. This involves setting some protocol negotiation parameters. You should begin by obtaining your SSLContext using this function, which you can then subsequently modify to suit your needs.

import ssl
import hyper
from hyper.tls import init_context

ssl_context = init_context()
ssl_context.check_hostname = False
ssl_context.verify_mode = ssl.CERT_NONE

conn = hyper.HTTP20Connection('http2.akamai.com', port=443, ssl_context=ssl_context)
conn.request('GET', '/')

print conn.get_response()

@Kostya Your example worked fine but below scenario still a problem.
ev-www.opentable.com.edgekey.net - server with virtual hosting servers based on "Host" header, I am still getting the error.
Also let me know how to update SNI
ssl_context = init_context()
ssl_context.check_hostname = False
ssl_context.verify_mode = ssl.CERT_OPTIONAL

headers={'Host': 'www.opentable.com'}
conn = hyper.HTTP20Connection('ev-www.opentable.com.edgekey.net', port=443, ssl_context=ssl_context)
conn.request('GET', '/washington-dc-restaurants', headers=headers)

print conn.get_response()


False positive on Structural Type

Shapeless does not use reflection or structural type but scalastyle complains that this line
https://github.com/milessabin/shapeless/blob/master/core/src/main/scala/shapeless/ops/hlists.scala#L777
uses structural typing.
Even though it is a structural type from a typechecking point of view, but it's completely erased at runtime, so there's no cost at all.

Just to clarify, I don't think there's any structural typing on that line at all, erased or otherwise. More generally, if you could try and detect type-lambdas and not report them as incurring runtime reflection overhead that would be great.

I'm not sure I can, actually. The StructuralTypeChecker detects Refinements, it is very simple.
I would have to understand this is a lot more depth to know how to fix this. Also, I'm not sure how much effort I want to put into this given that the Scala compiler also detects Structural types, and a lot better than Scalastyle.
My tendancy is to close this. Is this something you're really attached to?

The problem here is that the presence of a refinement doesn't imply that there will be any form of reflective structural access to value members at run time, so the error report is incorrect. All uses of type lambdas or the Aux pattern will be hit by this, which I think it quite unfortunate for such widely used idioms.
If you don't think it's worth fixing here then I suggest deprecating the feature in favour of scalac's checking.

Fixed this by a documentation change. If you don't think the current documentation is clear enough, please say so.


Trailing spaces following table header prevent single column tables from rendering

Description: If there is a trailing space following the header of a single column table, the table does not get rendered.  Multi column tables still render when there header has a trailing space.
Input:
| Single column |
|:-------|
|   Row one   |
|   Row two   |

Expected output:

Single column

Row one

Row two

Actual Output:
| Single column | |:-------| | Row one | | Row two |

Verified. The issue is not that serious and it should be an easy fix.

Should be fixed in v 1.7.6

As you know, ShowdownJS is a free library and it will remain free forever. However, maintaining and improving the library costs time and money. Currently, we're looking to improve showdown with automated tests in all browsers and a proper domain and webpage. 500$ should be enough to to keep showdown testing framework running for a year or two.

If you like our work and find our library useful, please donate through Pledgie or directly through paypal!! Your contribution will be greatly appreciated.


TD-788: Adds woody pool/connections metrics

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 90.124%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
4517

Relevant Lines:
5012

💛  - Coveralls


3DS Popup opening and closing immediately with failed authentication

General information

SDK version: 3.81.0
Environment: Production
Browser and OS: Chromium: 92.0.4515.159 on Mac OS 11.4

Issue description
Hi there,
We are experiencing a problem with one of our customers. When they try to process a payment we call verifyCard, then the 3DS popup from Cardinal shows blank for a second and closes resulting into an error for the payment.
The input to verifyCard:
{
      amount: 65.94,
      nonce: paymentMethod.nonce,
      bin: paymentMethod.details.bin,
      email: userDetails.email,
      billingAddress: {
          givenName: onlyEnglish(firstName(userDetails.name)),
          surname: onlyEnglish(lastName(userDetails.name)),
      },
      additionalInformation: {
          shippingGivenName: onlyEnglish(firstName(userDetails.name)),
          shippingSurname: onlyEnglish(lastName(userDetails.name)),
          acsWindowSize: "03",
      },

      challengeRequested: true,
      onLookupComplete: function (data: any, next: () => void) {
          next();
      },
  }

This is the response from the verifyCard:
{
    "nonce": "xxxxx-xxxxx-xxxxx-xxxx",
    "type": "CreditCard",
    "binData": {
        "prepaid": "No",
        "healthcare": "No",
        "debit": "No",
        "durbinRegulated": "No",
        "commercial": "No",
        "payroll": "No",
        "issuingBank": "xxxx",
        "countryOfIssuance": "xxx",
        "productId": "xxx"
    },
    "details": {
        "cardType": "MasterCard",
        "lastTwo": "xx",
        "lastFour": "xxxx",
        "bin": "xxxxxx",
        "cardholderName": null,
        "expirationYear": "xxxx",
        "expirationMonth": "xx"
    },
    "description": "xxxxxxx",
    "liabilityShifted": false,
    "liabilityShiftPossible": true,
    "threeDSecureInfo": {
        "liabilityShifted": false,
        "liabilityShiftPossible": true,
        "status": "challenge_required",
        "enrolled": "Y",
        "cavv": null,
        "xid": null,
        "acsTransactionId": "xxxxxxx",
        "dsTransactionId": "xxxxxx",
        "eciFlag": "00",
        "paresStatus": null,
        "threeDSecureAuthenticationId": "xxxxx",
        "threeDSecureServerTransactionId": "xxxxxxx",
        "threeDSecureVersion": "2.1.0",
        "lookup": {
            "transStatus": "C",
            "transStatusReason": null
        },
        "authentication": {
            "transStatus": null,
            "transStatusReason": null
        }
    },
    "rawCardinalSDKVerificationData": {
        "Validated": false,
        "ActionCode": "FAILURE",
        "ErrorNumber": 0,
        "ErrorDescription": "Success",
        "Payment": {
            "Type": "CCA",
            "ExtendedData": {
                "CAVV": "",
                "ECIFlag": "00",
                "ThreeDSVersion": "2.1.0",
                "PAResStatus": "N",
                "SignatureVerification": "Y"
            },
            "ProcessorTransactionId": "xxxxxx"
        }
    }
}

Video:
**
https://user-images.githubusercontent.com/6017552/130966680-a1b51f6e-3f41-476a-bc4f-2f84d75cb6fa.mov
**

Thank you for providing the detailed information, @ginovski. We are investigating it and hope to have an answer soon.

@kate-paypal Do you have any update on this one?

Thanks for reaching back out @ginovski. We are still taking a look at the possible cause of this issue. We may have to escalate this to Cardinal, our MPI provider. We have some additional follow up questions:
You said you are able to reproduce this on your end. When you reproduce it, does it happen every time? Sporadically? Are there any specific card brands that cause this issue? If you can reproduce this consistently, are there any other differences between when this happens and when it doesn't?

@ginovski do you still need help with this? If so, can you answer @jplukarski's questions?

Closing due to inactivity. Feel free to comment here if we should re-open it.


Problem with printing form view to PDF

If you go to the eyeball icon for a record and open it to preview and have it on form view, and then go to the windows bar File > Print > Save to PDF, you get only the first page of the form over and over and not the rest of the pages.  It seems to be fine if you File > Print > Save to PDF from the edit page for a record, it works fine.   I'm doing this in Firefox but the same thing happens in Chrome (just fewer pages of the same page)

Hmm, not sure if we ever set anything up for printing, but I'll take a further look


Allow sqlx dependency without runtime and TLS features.

Is your feature request related to a problem? Please describe.
I need to write an SDK crate that depends on sqlx and will be available to run on both actix and tokio runtimes. I really only need an access to the executor. It's not the first time of me facing this issue, however this time it's critical, I can't have any workarounds. Having to duplicate code this much is really frustrating. I don't see any reasons this crate cannot be runtime and TLS agnostic.
Describe the solution you'd like
Allow specifying a dependency on sqlx without specifying runtime and TLS.
Describe alternatives you've considered
I don't see any other adequate solutions.

This now works in 0.7.0


Add parse multiple empty newlines in message

Related to #30
Environment:
Asterisk 16.6.1 running on Ubuntu 18.04
Steps to reproduce:

Configure an AMI user in manager.conf with read = all and write = all
Listen to AMI events
Call an extension in the dialplan that triggers an AGI script that then uses the Dial application

Description:
Yesterday I ran into an issue causing the exception: Parse error, no colon in line "" found.
While connected to AMI telnet <IP_ADDRESS> 5038, I noticed the following Event output:
Event: DeviceStateChange
Privilege: call,all
Device: PJSIP/2101
State: RINGING

Event: TestEvent
Privilege: reporting,all
Type: StateChange
State: RINGING_INBAND
AppFile: channel.c
AppFunction: indicate_data_internal
AppLine: 4562
Channel: PJSIP/2102-00000046

Event: VarSet
Privilege: dialplan,all
Channel: PJSIP/2102-00000046
ChannelState: 6
ChannelStateDesc: Up
CallerIDNum: 2102
CallerIDName: Test 2102
ConnectedLineNum: 9999
ConnectedLineName: <unknown>
Language: en
AccountCode:
Context: demo
Exten: 9999
Priority: 5
Uniqueid:<PHONE_NUMBER>.531
Linkedid:<PHONE_NUMBER>.531
Variable: RINGTIME
Value: 0

There is an extra blank line after the TestEvent Event that gets passed to the parseMessage method as the first line of the next VarSet Event that throws an error because the line does not contain a colon.  I suspect the extra line is either coming from the end of the TestEvent or beginning of the VarSet Event in asterisk's code.
This change will remove any empty lines in a message before the lines are parsed.

I added a test based on a tweaked version of your old comment.  While testing I noticed the string "\r\n\r\n\r\n\r\n" was returning a Response object without any fields and added a check for that in the parser push method.
I have looked through the Asterisk source code to the best of my ability, but have little experience with C and can only guess one of the functions generating strings for AMI messages might be causing the extra newline in very specific situations.

@glet Thank you for keeping up with this and providing all the details in this high-quality PR! I can now see the problem and agree that your fix is a nice way to avoid this problem. I've just squashed your changes with #53 and slightly adjusted this to support the updated test suite and legacy PHP versions as per #51. Keep it up! :+1:

Thank you for your help and this project!


[Feature Request]: Nested Writes for relations

It would be a nice feature to be able to create or connect nested records in a single request.
For example, if I have the following migration:
CREATE TABLE "User" (
    "id" SERIAL NOT NULL,
    "email" TEXT NOT NULL,
    "name" TEXT,

    CONSTRAINT "User_pkey" PRIMARY KEY ("id")
);

-- CreateTable
CREATE TABLE "Post" (
    "id" SERIAL NOT NULL,
    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
    "title" TEXT NOT NULL,
    "content" TEXT,
    "published" BOOLEAN NOT NULL DEFAULT false,
    "viewCount" INTEGER NOT NULL DEFAULT 0,
    "authorId" INTEGER,

    CONSTRAINT "Post_pkey" PRIMARY KEY ("id")
);

-- CreateIndex
CREATE UNIQUE INDEX "User_email_key" ON "User"("email");

-- AddForeignKey
ALTER TABLE "Post" ADD CONSTRAINT "Post_authorId_fkey" FOREIGN KEY ("authorId") REFERENCES "User"("id") ON DELETE SET NULL ON UPDATE CASCADE;

It would be nice to be able to create/ update/ connect nested records, i.e:
mutation CREATE_USER {
	insertUser(inputs: {
		email: "...",
		name: "...",
		posts: { (possible operations =>) create/ connect/ connectOrCreate: [ { ...post properties here} ] }  }){
	}
}

The current workaround for this making 2 mutations to connect two records.

Indeed, this would be handy. It's kind of hard to do for save (given its upsert nature), however we can definitely do this for insert.


All future events are concidered as "next week events" in weekly newsletter.

Only the events that are during next week should be in that category. Change this to the web site as well as email.

This is work in progress in this branch fix-weekly-newsletter-calendar
Anyone feel free to take over if you want to finish the implementation 🙏


Error formatting issue

Description
There is small formatting issue in returned errors for initial registration if the name has already been registered i.e. when the error message is "o auth2 registration with this name already exists.". It's simple to work around but also very simple to correct in the api itself. Currently the error is returned labelled as "name" and its value is a string inside of an array.
Reproduction

Register a name with the api that has already been used:

$ curl -X POST -H "Content-Type: application/json" -d '{"name": "My already used name", "description": "To access CC Catalog API", "email"<EMAIL_ADDRESS>https://api.creativecommons.engineering/v1/auth_tokens/register

See error (see below in expectation).

Expectation
Currently the error returned is this:
  {     "name" : ["o auth2 registration with this name already exists."]   }
I would expect to see this, given that this is the error format used when requesting a token:
  {     "error" : "o auth2 registration with this name already exists."   }
Resolution

[ ] I would be interested in resolving this bug.

Shall I implement this issue .

Shall I implement this issue .

Hi, is there a timeline for copying this across to the live version? Reason I ask is I'm implementing a php means of searching CC, which I'll probably then release here on Github, but I don't want to release it until the live version is updated.  Thanks in advance.

Hi, is there a timeline for copying this across to the live version? Reason I ask is I'm implementing a php means of searching CC, which I'll probably then release here on Github, but I don't want to release it until the live version is updated.  Thanks in advance.

@Garrettlynch this issue was closed. No more changes are expected for this repo. See my previous comment.

@TimidRobot yes I understand the issue has been fixed in the repo and the issue is closed - many thanks for that. However, it seems to not have been implemented in the live version running at https://api.creativecommons.engineering/v1/. Do you know when this might happen? Thanks in advance.

@Garrettlynch this issue was closed. No more changes are expected for this repo. See my previous comment.

@TimidRobot yes I understand the issue has been fixed in the repo and the issue is closed - many thanks for that. However, it seems to not have been implemented in the live version running at https://api.creativecommons.engineering/v1/. Do you know when this might happen? Thanks in advance.


Tests: lib: gui: lvgl: test causes a Stack Overflow on stm32f746g_disco

Describe the bug
Tests/lib/gui/lvgl test does not run on stm32f746g_disco, & possibly other platforms as well, & causes a Stack Overflow. LittleFS appears to be the cause (as seen in the console output below).

target platform: tested on stm32f746g_disco
Attempted workaround: update LittleFS to 2.8.1 using PR 65414
Still don't know if it's a regression

To Reproduce
Steps to reproduce the behavior:

cd ~/zephyrproject/zephyr
west build -p always -b stm32f746g_disco tests/lib/gui/lvgl
west flash

Expected behavior
Random noise on the screen
Impact
Cannot run test
Logs and console output
I: Reading SFDP
I: qspi-nor-flash@0: SFDP v 1.5 AP ff with 2 PH
I: PH0: ff00 rev 1.5: 16 DW @ 30
I: Reading SFDP
I: qspi-nor-flash@0: 16 MiBy flash
I: PH1: ff03 rev 1.0: 2 DW @ 100
* Booting Zephyr OS build zephyr-v3.5.0-4181-g4204ca9bcb3f *
Running TESTSUITE lvgl_fs
===================================================================
I: LittleFS version 2.5, disk version 2.0
I: FS at qspi-nor-flash@0:0xa0000 is 3840 0x1000-byte blocks with 512 cycle
I: sizes: rd 16 ; pr 16 ; ca 64 ; la 32
E: * MPU FAULT *
E:   Stacking error (context area might be not valid)
E:   Data Access Violation
E:   MMFAR Address: 0x2001da38
E: r0/a1:  0x00000002  r1/a2:  0x2001da5c  r2/a3:  0x2001da5c
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x2001da70
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x2001da70
E: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
E: Current thread: 0x200146f0 (main)
E: Halting system

Environment:

OS: Linux
Toolchain: Zephyr SDK 0.16.3
Commit SHA: main branch, 4204ca9bcb3f675a0e63f647931ffe2c4b515729

Additional context
None for now

Do you have enough stack size? I had this on my Sam_e70 derived project, I put "CONFIG_MAIN_STACK_SIZE=8192" in the prj.conf to solve.

Do you have enough stack size? I had this on my Sam_e70 derived project, I put "CONFIG_MAIN_STACK_SIZE=8192" in the prj.conf to solve.

@simontheu No it does not solve the problem.

Check stacks. Maybe ISR stack. This ain't LittleFS. Play with all available stack settings and then narrow down.


Can it be used with Astro?

Can it be used with Astro and Tailwind?

Yes. It works with Astro. I'll see if I can find an example for you.

+1

I was playing with getting a very minimal example up just to get it to build. Hope this will get you started.
https://github.com/talves/astro-shadcn-ui-template/tree/main

Let me know if this is the wrong place to ask this. I'm having trouble with the Tooltip component. It works fine in development, but when I deploy to Vercel, the build fails.
I'm using Astro 2.3.1 and I've had no issues with the Dropdown, Command Bar, and Dialog components so far. Does anyone know if the problem is on my end or if it's an issue with Astro or the Tooltip component? Any help would be much appreciated!
Code

Let me know if this is the wrong place to ask this. I'm having trouble with the Tooltip component. It works fine in development, but when I deploy to Vercel, the build fails.
I'm using Astro 2.3.1 and I've had no issues with the Dropdown, Command Bar, and Dialog components so far. Does anyone know if the problem is on my end or if it's an issue with Astro or the Tooltip component? Any help would be much appreciated!
Code

I am getting these same displayName undefined errors on build.

@shadcn with the new CLI, do these steps still apply for Astro sites?

I was playing with getting a very minimal example up just to get it to build. Hope this will get you started.
https://github.com/talves/astro-shadcn-ui-template/tree/main
Note:  Understand that it has to be a static build using vite.ssr.noExternal for radix-ui. The astro.config.mjs config reflects this setup.

How do you use the buttonVariants?

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


Weather refactoring

Fixed openweathermap
Fixed darksky
Implemented forecast for both
added indoor values
documentation
...

Some things are still missing:

feels like temperature
openweathermap forecast for newer api keys (grouping 3h forecasts)
darksky unit handling
some more config options from the previous modules

But I would categorize those more as improvements.

The build on travis only failed for 50%. Nodejs can't handle class and in the other one the before hooks timed out as seen previously

SUPER AWESOME WORK! 🎉
If we can find a way to make travis happy, I can merge it, and then merge it into develop so we can shift the module as EXPERIMENTAL, which will hopefully increase traction in the development.
I'll be releasing the next MM version January 1st, so lets try to get it included in this version! :)

Warnings

:warning:

Please include an updated CHANGELOG.md file.This way we can keep track of all the contributions.

  Generated by :no_entry_sign: dangerJS

@MichMich I merged current develop branch (has an updated travis config) into the weather branch. It passed now.

Great work! Ill make sure to merge it into dev before releasing a new version.


Fix issue where if a last page < 50% width, pressing the back will…

… jump upto 150% of a slide, which is effectively two pages (due to rounding issue).
Hey, I've been using microfiche and came across an issue - let me explain. We have a navigation bar which is 800px wide, and each item is 200px wide, so we can have up to 4 per page. We had 13 items in our list, so there are 4 pages. When we used the 'next' and 'previous' buttons, using 'next' was fine, so we could go 1-2-3-4, but using previous went 4-2-1. This is due to a rounding issue where if you have less than 50% used on the last slide, the code will ignore that (round it off) and jump an entire page PLUS what is on that final semi-full page (so for us it was jumping 5 items and messing up our page counter - i notice that the max() function has already been fixed in the unreleased v1.8.1).
I was using V1.8.0 when I fixed this.
Thanks,
Alex

Great spot, thanks! Just verifying this doesn’t have any other ramifications.

Looks good :shipit: Thanks again!

This is now part https://github.com/withassociates/microfiche.js/releases/tag/v1.8.2


0x80131534 error at trying to clone repository from Arm system

Dev Home version
<IP_ADDRESS>
Windows build number
10.0.22621.0
Other software
No response
Steps to reproduce the bug

Open the Dev Home app on the device with an Arm processor (e.g. Surface Pro 9 or Parallels Desktop virtual machine on Apple M series)
Try to clone a GitHub repo using Dev Home, e.g. https://github.com/microsoft/vscode

Expected result
The repo is cloned (as it is on Intel PC)
Actual result
Error:
"Couldn't clone vscode 0x80131534"

Included System Information
No response
Included Extensions Information
No response

Closing as not repro.  We could clone with an ARM machine.  Please open if issue persists.


Update server.rb

According to https://pusher.com/docs/rest_api , status codes returned should be 200 on success, not 202

It used to return 200, but it was changed to return 202. See #161.
Would be great to check against a real pusher account to see the code is returning right now.

https://github.com/pusher/pusher-http-python/search?utf8=✓&q=200
https://github.com/pusher/pusher-http-python/search?utf8=✓&q=202&type=Code
https://github.com/pusher/pusher-http-python/issues/14
Sounds like 202 was the old value.
Whilst it will be nice to completely support the exact pusher implementation as it currently is, I think it is better to support the client library versions that work with slanger now.
Then for the rewrite, we'd probably want to match the pusher API.

Pusher's lib from pip requires status code 200 otherwise it raises an exception, so no longer does slanger support the client libraries out there right now.

+1 for python client

I'm not completely sure, but maybe there is a way to keep backward compatibility. Slanger has two different endpoints used for triggering events:
Official endpoint:
https://github.com/stevegraham/slanger/blob/master/lib/slanger/api/server.rb#L27
Legacy endpoint:
https://github.com/stevegraham/slanger/blob/master/lib/slanger/api/server.rb#L38
Old clients used to send requests to the legacy endpoint. If Slanger only changes the official endpoint in order to return 200 but keep legacy endpoint returning 202, new clients and old clients should work.
Again, I'm not completely sure about this, and maybe would be better to check against a real Pusher account with a new and an old python client to see returned status codes.

@Juanmcuello according to this I think you are right. For the new python push client , it always use the new api, but for the old api and 202 status code , it was before 1.0 release.  So for now it is important to change line 34 to use 200 status code; However for the legacy api (line 44), better to use 202 to make backward compatible but it is not important .

@Juanmcuello thanks for looking into this. The problem we really have here is a series of changes on the pusher API and corresponding pusher clients. Nearly all the issues we get on here are due to mismatch in client versions.
The slanger code base has got to the stage that we want to do a rewrite, then update the API to match the existing pusher API. Only at that point will we start considering incompatibility with the latest pusher API as being bugs in slanger.
If people used older pusher clients then most of the issues would go away. Or alternatively if we rewrote the codebase we would probably be more willing to support it.
As it is, I'm prepared to look at merging pull requests that address all issues related to all clients and have clearly thought through all implications.
But I'm not as likely to merge a fix for a specific new client with a potentially breaking change for the old clients that do work 100% with the old API.


Allow identifiers to be defined with a block

Now that ::association and ::field receive an optional block,
::identifier should receive it as well.
Since all three methods receive an optional block, the block extraction
mechanism was moved to AutoExtractor. Removing this mechanism from
each individual method made them very similar. ::association now uses
::field instead of directly adding the field to the current view.
Addresses #109

I've added documentation. Feel free to suggest better examples, I used the one I needed on my project, but it may be a bit weird.

LGTM!

We’ll hopefully get this out soon in the next release of Blueprinter, thanks for this!


Bump version to 3.0.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.87%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
350

Relevant Lines:
354

💛  - Coveralls


Fix adding annotations on top of boundary

Overview
Previously, the annotation clicks would be captured by the polygon. Now we mark it as not interactive if the user cannot write or if the shape is not in edit mode, which allows the clicks to pass through to the map, allowing Validators to add annotations within the boundary.
Also removes the Archived tab in the submissions list.
Closes #225
Closes #227
Demo
https://user-images.githubusercontent.com/1430060/205735421-07661311-2f7b-42ef-ab8a-99fee32d5484.mp4

Testing Instructions

Check out this branch and server
Go to http://localhost:4545/ and login as a Validator
Pick an In Review submission and go to the details and draw page
Try adding annotations

[x] Ensure you can add annotations both inside and outside the shape
[x] Ensure you can delete annotations both inside and outside the shape

With a sample annotation within and outside the boundary, mark that boundary as Needs Revisions
Logout and log back in as a Contributor
Pick the Needs Revisions submission and amend it

[x] Ensure you can access annotations within and without the shape
[x] Ensure you can edit the shape

Go to /submissions/

[ ] Ensure you don't see an Archived tab, or Active tab

Checklist

[ ] fixup! commits have been squashed
[x] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines
[ ] README.md updated if necessary to reflect the changes
[ ] CI passes after rebase

Thanks for reviewing! I just added 4477531 to remove the Archived tab. Feel free to take another cursory look. Else will merge soon.


POC: Dynamic height undo redo issue

Fixes issue where scroll height of container like widget's canvas was never resetting after we fixed the undo-redo issue
Fixes issue where undo after move/add/delete/cut/paste/resize of a widget was not working.

@marks0351 @rahulramesha Thanks for your inputs. I've noted the points down. We'll make sure to restore the fixes for issues before releasing this feature. I'm going to merge this in for now.


Masking of text input for phone number

When entering a phone number, I want the input to be masked as user types in.
TextInput:
  inputType: phone
  maskValue: true

https://github.com/EnsembleUI/ensemble/assets/491202/2281dc2a-b623-4e20-8334-bbc149ac10ac

This should be a generic input masking. The yaml should able to accept a mask, which will then auto-format the content as we type. e.g. phone number, social security, ...

@amin-nas @vusters  PR - #690


Ask  openai.GPT4o with a file request

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I'm trying to ask  openai.GPT4o to analyze a html document/ file and extract keywords but I cannot find how to attach the html document to the prompt request
Describe the solution you'd like
A clear and concise description of what you want to happen.
A File field on openai.ChatCompletionRequest
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I've added the html content itself in the prompt but it confuses chatGPT and returns gibberish responses. See the reduced code I've tried:
func main(){
   content,_ := ioutil.ReadFile("x.html")
   response, _ := fmt.Sprintf("analyze the html content below and return me 10 keywords: \n %s", content)
func chat(cx context.Context, text string) (string, error) {
	client := openai.NewClient(openAIKey)
	resp, err := client.CreateChatCompletion(
		cx,
		openai.ChatCompletionRequest{

			Temperature: 2,
			Model:       openai.GPT4o, //  openai.GPT3Dot5Turbo,
			//	FilePath:    "./x.html",
			Messages: []openai.ChatCompletionMessage{
				{
					Role:    openai.ChatMessageRoleUser,
					Content: text,
				},
			},
		},
	)

	if err != nil {
		return "", err

	}

	return resp.Choices[0].Message.Content, nil
}

There's nowhere in the API that allows generic file uploads. It's only text and images, within the prompt structure. In order to achieve the effect you want, you will have to either insert all the HTML as text as part of your prompt, or find a way to parse it to extract portions of the HTML (so you can save on tokens).

Also - your temperature is extremely high- which may explain some of the "gibberish". Start with 0.7 and maybe reduce/increase it incrementally.


Improve documentation on pyChapel return types

From the Misc. Page we can see that primitives can be returned from a Chapel routine into Python.  This isn't explicitly stated.  Is there a way to return non-primitives?  How would I return arrays or sparse arrays, for instance? What about JSON or blobs?
This could be useful for sending data back and forth.  I'm sure there are reasonable limits I don't understand.

Only certain types are supported across the Python-Chapel divide.  In the current implementation, we've had to explicitly mention certain types, so you won't see every type Chapel or Python could support.  While arrays can be passed to Chapel functions, they cannot currently be returned from them (but you will see modifications made to arrays you pass in to Chapel functions)

It is an action item to support arrays of more than just the one element type, to return them, and to support arbitrary structures defined within Chapel and Python

In the example below,  Chapel is modifying and np.ndarray.
@Chapel()
def quant(date=np.ndarray, bid=np.ndarray, ask=np.ndarray, voodoo=np.ndarray):
    """
    var future = 200;
    voodoo = ask-bid;
    for i in 1..future {
        voodoo += (ask-bid + ask-bid  + ask-bid + ask-bid
                   +ask-bid + ask-bid + ask-bid + ask-bid
                  ) / 8;
    }
    voodoo = voodoo / future;
    """
    return None

Is the Python view of the "voodoo" variable modified?

Also, I'm trying to send an array into a routine defined in an sfile.  I need an example of the syntax.  This failed:
  export
  proc flip_bit(v: [?D] int) {
    v[0] = -v[0];
    return v;
  }

with error
(pychapel) buddha314@notes:~/pychapel/tmp$ python call.py
/tmp/temp-lnjLSb.chpl:10: In function 'flip_bit':
/tmp/temp-lnjLSb.chpl:11: internal error: CAL0126 chpl Version 1.16.0 pre-release (c3663a54f0)

Internal errors indicate a bug in the Chapel compiler ("It's us, not you"),
and we're sorry for the hassle.  We would appreciate your reporting this bug --
please see http://chapel.cray.com/bugs.html for instructions.  In the meantime,
the filename + line number above may be useful in working around the issue.

g++: error: /tmp/tmpEB8cif.a: No such file or directory
Traceback (most recent call last):
  File "call.py", line 12, in <module>
    shout_out()
  File "/home/buddha314/.virtualenvs/pychapel/local/lib/python2.7/site-packages/pych/extern.py", line 212, in wrapped_f
    raise MaterializationError(self)
pych.exceptions.MaterializationError: Failed materializing ({'anames': [],
 'atypes': [],
 'bfile': None,
 'dec_fp': '/home/buddha314/pychapel/tmp/response.chpl',
 'dec_hs': '7ecfac2d168f3423f7104eeb38057ac3',
 'dec_ts':<PHONE_NUMBER>,
 'doc': None,
 'efunc': None,
 'ename': 'shout_out',
 'lib': 'sfile-chapel-7ecfac2d168f3423f7104eeb38057ac3-1501804367.so',
 'module_dirs': [],
 'pfunc': <function shout_out at 0x7fe326f428c0>,
 'pname': 'shout_out',
 'rtype': None,
 'sfile': '/home/buddha314/pychapel/tmp/response.chpl',
 'slang': 'chapel',
 'source': None}).

re: the voodoo variable - I believe Python will see any changes made to it, and since it is an argument to the function, will be able to work with the actual used after the call has completed.  But you should double check that to be certain.
Hmm, I don't think we have any tests of sending an array to a function defined in an sfile.  I suspect that the ?D domain is causing issues, since Chapel arguments to functions that Python calls must be fully concrete and ?D or no domain at all makes the argument generic.  That really shouldn't be an internal error (and is a problem on the Chapel side).  Perhaps try specifying the domain exactly for the call?

And if you wouldn't mind, please open an issue on the Chapel repository about exporting a function with a generic array argument causing an internal error instead of a user facing one :)

Maybe we will be able to resolve that when our separate compilation story gets implemented

Sorry, just saw this, should I still open that ticket?  I'm not sure I understand it, but I'm happy to parrot your words.

Thanks!

Do you have a basic example of sending an integer between python and chapel?  Something like
import os
from pych.extern import Chapel

currentloc = os.path.dirname(os.path.realpath(__file__))
@Chapel(sfile=os.path.join(currentloc + '/response.chpl'))
def flip_bit(v=int):
    return int

if __name__=="__main__":
    u = 71
    w = flip_bit(u)
    print(w)

And
module Response{
  export
  proc flip_bit(v: int) :int {
    v = -v;
    return v;
  }
}

This example isn't working, but I can't tell from the docs how to send in v
Thanks!

The interaction of these two files seems to work for me: python file and chapel file
I suspect the difference has something to do with wrapping your chapel code in a module, since you would normally need a use statement to access its contents (due to the name of the module being different from the name of the file - Chapel is case sensitive).  You could either remove the module declaration or make it lower case (i.e. module response)

Note that this might interplay with issue #10

Changing to lower case module response yields:
/tmp/temp-d4UnJ0.chpl:4: In function 'flip_bit':
/tmp/temp-d4UnJ0.chpl:5: error: illegal lvalue in assignment
g++: error: /tmp/tmpbUDg_C.a: No such file or directory
Traceback (most recent call last):
  File "call.py", line 15, in <module>
    w = flip_bit(u)
  File "/home/buddha314/.virtualenvs/pychapel/local/lib/python2.7/site-packages/pych/extern.py", line 212, in wrapped_f
    raise MaterializationError(self)
pych.exceptions.MaterializationError: Failed materializing ({'anames': ['v'],
 'atypes': [<type 'int'>],
 'bfile': None,
 'dec_fp': '/home/buddha314/pychapel/tmp/response.chpl',
 'dec_hs': '7ecfac2d168f3423f7104eeb38057ac3',
 'dec_ts':<PHONE_NUMBER>,
 'doc': None,
 'efunc': None,
 'ename': 'flip_bit',
 'lib': 'sfile-chapel-7ecfac2d168f3423f7104eeb38057ac3-1502208167.so',
 'module_dirs': [],
 'pfunc': <function flip_bit at 0x7fc042d4a938>,
 'pname': 'flip_bit',
 'rtype': <type 'int'>,
 'sfile': '/home/buddha314/pychapel/tmp/response.chpl',
 'slang': 'chapel',
 'source': None}).

Removing declaration of module so response.chpl is now
  export
  proc flip_bit(v: int) :int {
    v = -v;
    return v;
  }

Brings me this when I do python call.py
/tmp/temp-fb2D85.chpl:2: In function 'flip_bit':
/tmp/temp-fb2D85.chpl:3: error: illegal lvalue in assignment
g++: error: /tmp/tmpbJWVBW.a: No such file or directory
Traceback (most recent call last):
  File "call.py", line 15, in <module>
    w = flip_bit(u)
  File "/home/buddha314/.virtualenvs/pychapel/local/lib/python2.7/site-packages/pych/extern.py", line 212, in wrapped_f
    raise MaterializationError(self)
pych.exceptions.MaterializationError: Failed materializing ({'anames': ['v'],
 'atypes': [<type 'int'>],
 'bfile': None,
 'dec_fp': '/home/buddha314/pychapel/tmp/response.chpl',
 'dec_hs': '7ecfac2d168f3423f7104eeb38057ac3',
 'dec_ts':<PHONE_NUMBER>,
 'doc': None,
 'efunc': None,
 'ename': 'flip_bit',
 'lib': 'sfile-chapel-7ecfac2d168f3423f7104eeb38057ac3-1502208246.so',
 'module_dirs': [],
 'pfunc': <function flip_bit at 0x7f0a18ab0938>,
 'pname': 'flip_bit',
 'rtype': <type 'int'>,
 'sfile': '/home/buddha314/pychapel/tmp/response.chpl',
 'slang': 'chapel',
 'source': None}).

Oh, right.  That's because you're trying to assign to the argument, when the argument's default intent is const in (meaning it can't be overwritten).

Should we be having this conversation on stackoverflow?

Hey, that's fine with me!  Okay, I'll start one and post it here.  Good idea!

HIT IT!


Feed icon

Because RSS is all the rage.

I will be adding this in the next version.

Added Feed icon to v1.4.

thanks!


CompletionWindow NuGet 6.0.1

Hello,
I encountered a problem with your nuget package in version 6.0.1.
When I use that nuget package and try to fill the CompletionWindow with data and then calling the Show Method, the CompletionWindow is empty and the program crashes after another keypress. If I compile your GitHub files manually, the same code suddenly works and the CompletionWindow become filled.
Do you know about anything I could've done wrong?
I'm using VS2019 and I've included the package by the built in NuGet Package Manager
Kind regards

I just tried to reproduce the problem on my end using the 6.0.1 nuget package, however, I was not able to make it crash. See
codecompletionsample.zip for the code I used. If this does not solve your problem, please modify the sample so that it crashes on your machine and send it back to me. Thanks!


ubuntu 18.04 : 'xlocale.h' file not found

trying to build master
build fails with:
In file included from /.../workspace/carla/Util/Build/llvm-source/projects/libcxx/src/algorithm.cpp:11:
In file included from /.../workspace/carla/Util/Build/llvm-source/projects/libcxx/include/random:1646:
In file included from /.../workspace/carla/Util/Build/llvm-source/projects/libcxx/include/istream:163:
In file included from /.../workspace/carla/Util/Build/llvm-source/projects/libcxx/include/ostream:138:
In file included from /.../workspace/carla/Util/Build/llvm-source/projects/libcxx/include/ios:216:
/.../workspace/carla/Util/Build/llvm-source/projects/libcxx/include/__locale:39:11: fatal error:
      'xlocale.h' file not found
# include <xlocale.h>

see
https://sourceware.org/glibc/wiki/Release/2.26#Removal_of_.27xlocale.h.27

I compiled using the proposed workaround
ln -s /usr/include/locale.h /usr/include/xlocale.h

@maxlem thanks a lot, it solve my problem :)


fix loop

Coverage increased (+0.2%) to 66.22% when pulling 4372c21ec0e7b4a4dd3bd4d1cd6ad743b7387771 on bugfix/PN-288-fix-sms-loop-retry into ca2e72b6556dc09685af320a69a1da1be4b56357 on master.


Add "figs" and "img" folders

Thank you for your contributions, I truly value and appreciate each one. 👍🏼
I'm currently working on expanding the extension's capabilities to allow file uploads, not just direct image data (which would allow for way more flexibility).
I'm hoping to implement this improvement soon. However, some limitations with Chrome's extension framework present challenges that I'm actively working to overcome. 🤝 🙌🏼

I've finally figured it out! The solution was simply to listen to the paste event instead of the key-down event. Who would have thought? 🤦🏼 🤦🏼♂
Now, the feature works perfectly. You can upload images directly either by cropping or simply selecting files from your PC. It also supports multiple selections and conveniently uses the name and the paste event contains a File object with all the necessary information.
Once I've thoroughly tested it and ensured its reliability, I'll upload the new release.


Update docs with information on how to import robot accounts

Update docs with information on import procedure.
This fixes #309

hi @naitmare01 ,
thank you :)


QuEra backend

Suggest adding a note that pytket-braket is not supporting the QuEra backend

What goes wrong? Is it a bug that it doesn't work?

Does pytket-braket support the QuEra backend? (neutral atom-based QPU). I did not find mention of the QuEra backend here:
pytket/extensions/braket/backends/braket.py

Ah, this is not a gate-based device is it? If not then pytket can't support it. I would just change the documentation to make clear that we only support gate-model QPUs.


Suggestion to change the section about JavaScript

For https://github.com/grab/front-end-guide#new-age-javascript, can you mention using https://github.com/babel/babel-preset-env instead of "ES2015" by which you mean babel-preset-es2015? I would explain that as browsers natively support ES whatever babel can just compile what is necessary.
And regarding babel-preset-stage-0, I would recommend explaining what Stage 0 means if it's going to be mentioned at all (that it's not javascript and just proposals that might go away). If you need help with this, can check out http://babeljs.io/docs/plugins/#presets-stage-x-experimental-presets-, https://github.com/hzoo/role-of-babel-in-js, https://tc39.github.io/process-document/

Thanks for the suggestions @hzoo . Will get to it immediately.

I would recommend suggesting stage-3 for stability. Historically, stage-0 implementations have changed their implementations, async/await was a big one, where as a stage-3 is basically just awaiting implementation.
Although you could probably write a codemod  to change them nowadays.

Thanks for your comments @sidhuko , but the fact is that we were using preset-stage-0, and are in the process of changing to preset-env for our apps. I'll add in a note to inform about using stage-3 for stability.

Yeah Stage 0 is literally just someone's idea on the committee and could change at any point. Of course we have tests and will try to help migrate users when possible but we are just volunteers.

Thanks for everyone's comments. Fixed in 4571a88.


tf.reshape modify the value of tensor

when i reshape the samples, the value of it is modified, why?

Because all the time TF draws a sample from your distribution. Try:
with tf.Session() as sess:
  print sess.run([samples,ss])

instead


Changed default value for history.end_rip_after_already_seen

Category
This change is exactly one of the following (please change [ ] to [x]) to indicate which:

[X] a bug fix (Fix #...)

Description
The default value was -1 which caused ripme to end the rip if the user hadn't changed the default value
Testing
Required verification:

[X] I've verified that there are no regressions in mvn test (there are no new failures or errors).
[X] I've verified that this change works as intended.

[X] Downloads all relevant content.
[X] Downloads content from multiple pages (as necessary or appropriate).
[X] Saves content at reasonable file names (e.g. page titles or content IDs) to help easily browse downloaded content.

[X] I've verified that this change did not break existing functionality (especially in the Ripper I modified).

Optional but recommended:

[ ] I've added a unit test to cover my change.

Coverage increased (+0.04%) to 31.821% when pulling 34e27cd2facaba6016e228afc6e717e59d8fca6a on cyian-1756:lastseenfix into af2c5f3fe09e3446aae75047daa6232ff2e39f90 on RipMeApp:master.

Coverage increased (+0.04%) to 31.821% when pulling 34e27cd2facaba6016e228afc6e717e59d8fca6a on cyian-1756:lastseenfix into af2c5f3fe09e3446aae75047daa6232ff2e39f90 on RipMeApp:master.