Inference on a single unlabeled .ply file

Hello! Thank you so much for this project!
I managed to go through the model retraining and evaluation (using the notebook demo). Presently however, I am trying to see the output of inference on a single unlabeled .ply file.
May you kindly advise on how this can be achieved? I tried to look into the docs and some issues, and it seems to me that the only way is through creating custom dataset files (Maybe I am misunderstanding or missing something).
Thank you very much in advance!

Hello @faridht,
Normally you should be able to find what you need for running the inference on a cloud in notebooks/demo.ipynb. This notebook shows how to run a forward pass on a NAG and visualize it with our tool.
Yet, since preparing a NAG for inference requires some preprocessing, you indeed should implement dedicated classes inheriting from BaseDataset and BaseDatamodule for your new data. If you have only one cloud tile in your dataset, this may sound overkill, but this is the cleanest, foolproof way of accessing all the features of this codebase.
Then, you would want to use the predict() logic.
A workaround would be that you manually instantiate and run the series of Transform for processing your raw data into a proper NAG for inference, and then run a forward pass on the model. These would be the ones you would otherwise find in your dataset's config file:

pre_transform
val_transform
on_device_val_transform

If you are familiar enough with the project and hydra in particular, you definitely can try this strategy ! However, I will not dedicate much time further helping with this approach, since we do not officially support it and I foresee doing so would open the door to a whole world of new issues :sweat_smile:


zabbix: update source url

Motivation for this change
Looks like I goofed up on https://github.com/NixOS/nixpkgs/pull/87179 :disappointed:
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 87776 1

Thanks @bhipple!


Doesn't work

iex(1)> [info] GET /pl
[info] Sent 500 in 36ms
[error] #PID<0.500.0> running Front.Endpoint terminated
Server: localhost:4010 (http)
Request: GET /pl
** (exit) an exception was raised:
    ** (FunctionClauseError) no function clause matching in Front.HomeController.init/1
        (front) web/controllers/home_controller.ex:2: Front.HomeController.init([action: :index, locale: "pl"])
        (front) web/router.ex:1: anonymous fn/1 in Front.Router.match_route/4
        (front) lib/phoenix/router.ex:261: Front.Router.dispatch/2
        (front) web/router.ex:1: Front.Router.do_call/2
        (front) lib/front/endpoint.ex:1: Front.Endpoint.phoenix_pipeline/1
        (front) lib/plug/debugger.ex:123: Front.Endpoint."call (overridable 3)"/2
        (front) lib/front/endpoint.ex:1: Front.Endpoint.call/2
        (plug) lib/plug/adapters/cowboy/handler.ex:15: Plug.Adapters.Cowboy.Handler.upgrade/4
        (cowboy) src/cowboy_protocol.erl:442: :cowboy_protocol.execute/4

  defp deps do
    [{:phoenix, "~> 1.2.1"},
     {:phoenix_pubsub, "~> 1.0"},
     {:postgrex, ">= 0.0.0"},
     {:phoenix_html, "~> 2.6"},
     {:phoenix_live_reload, "~> 1.0", only: :dev},
     {:gettext, "~> 0.11"},
     {:cowboy, "~> 1.0"},
     {:polygot, "~> 0.1.0"}]
  end

config :polygot,
  locales: %{
    "en" => %{ path_prefix: "en" },
    "pl" => %{ path_prefix: "pl" }
  },
  gettext_module: Front.Gettext,
  gettext_domain: "default"

  def router do
    quote do
      use Phoenix.Router

      import Polygot
    end
  end

localize get "/", HomeController, :index

$ mix phoenix.routes
 home_path  GET  /en Front.HomeController [action: :index, locale: "en"]
 home_path  GET  /pl Front.HomeController [action: :index, locale: "pl"]

  pipeline :browser do
    plug :accepts, ["html"]
    plug :fetch_session
    plug :fetch_flash
    plug :protect_from_forgery
    plug :put_secure_browser_headers
    plug Polygot.Plug
  end

Also Route helpers doesn't work, because it cannot find Polygot.Helpers.  Maybe on hex.pm there is older version of your library?

Hey @Harry27PL,
thanks for the reporting issue, there was a step missing in the readme, here it is:
https://github.com/boudra/polygot#controller
And I put up this fix for the helpers issue c01b52b473422db99d091b09486644fe2b18b3ba
please upgrade to the latest and let me know! thanks!

Now it works! Thanks


review: sample_bernoulli_rational

Closes #2068

#2112  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Shoeboxam and the rest of your teammates on  Graphite


inconsistent calculation of metrics

data: 20170307_issue1193/
The two following commands should give the same results, but they don't:
sct_extract_metric -i 001E_datapet_1mm.nii.gz -f PAM50_levels_BIN_T11-T12.nii.gz -method bin

--> 0, PAM50_levels_BIN_T11-T12.nii.gz [2299.0]:    1.14379832948 +/- 0.782535141076
sct_extract_metric -i 001E_datapet_1mm.nii.gz -f label/template -l 3 -vert 18:19 -method bin

--> 3, spinal cord [2328.0]:    1.13402642788 +/- 0.782505806446

This difference might me due to few voxels of a slice in-between T10 and T11 that are included in your mask but that belong to a slice in majority at T10. The vertebral level selection in sct_extract_metric is performed slice-wise because it cannot be voxel-wise (e.g., when the registration of the vertebral labeling is not perfect, voxels outside the cord would be included in the estimation).

ok i understand. But this is a problem, because ideally atlas-voxels should be selected on the basis of their inclusion in vertebral levels specified by the user. I.e., the result of extract metric should not be affected by the orthogonality of the cord to the slice. Since we have all the info, we should be able to address it properly. I think it's only a matter of computing a mask based on the vertebral_level, and then using this mask to keep only specific voxels in the atlas.

The problem comes from the partial voluming labels: using a binary mask (here, the mask computed based on the selected vertebral levels) removes all the interest of the partial voluming atlas. Moreover, in case of misregistration of the vertebral labeling (which is often the case because it is binary), we would remove lots of "relevant" metric voxels. The question is how to choose the voxels which belong to a specific level (in case of partial voluming labels or misregistration of the vertebral labeling).
I've just though about a solution:
The problem actually comes from the original definition of the vertebral levels in the template space, which is only in the cord. If the vertebral levels were defined in the template space in the entire slice (in the template space), i.e. one vertebral level value for the whole slice (not only in the cord), the problem would be fixed. The warping of the vertebral labeling file would define the voxels to select for a specific level, even in case of misregistration.

agreed-- let's leave it for futur dev with medium priority.


Release proposal: v1.24.1

I'm aiming to cut a new release later this week. If there are any objections, please raise them here.

No objections. Are there any open PRs you plan to merge before release?

I haven't gone through the list of open PRs to see what's ready to land, but I will before cutting the release. Are there any particular PRs that you think should make it in?

libuv in Node CI: https://ci.nodejs.org/view/libuv/job/libuv-in-node/72/
The only failure (test.sequential/test-debugger-debug-brk on CentOS6) appears to be https://github.com/nodejs/node/issues/18435.


Browser support ?

Hi,
What about the browser support ? Is that designed to work under IE7/8/9 right now or later may be ?
Thanks a lot !

Please add all browser support lists.
Because this code just using clean property and -webkit property.
Old moz and opera don't support clean animation tags!


Difference behaviour between WsiDicomFileSource and WsiDicomWebSource

Hi,
First of all, thank you very much for providing this great library.
I noticed a difference in the handling of the same DICOM file provided by WsiDicomFileSource and WsiDicomWebSource through a DICOMWeb interface.
The WsiDicomFileSource filters the DICOM levels for matching tile_size and UIDs:
https://github.com/imi-bigpicture/wsidicom/blob/b0d097c97140ba595529d60de43c472ffc5c6d6b/wsidicom/file/wsidicom_file_source.py#L274
This filtering is not done in WsiDicomWebSource:
https://github.com/imi-bigpicture/wsidicom/blob/b0d097c97140ba595529d60de43c472ffc5c6d6b/wsidicom/web/wsidicom_web_source.py#L58
This discrepancy can lead to DICOMs that can be opened via file but not via the web interface. I wanted to ask if this was intended.
Regarding the same topic of opening images via file or DCMWeb:
https://github.com/imi-bigpicture/wsidicom/blob/b0d097c97140ba595529d60de43c472ffc5c6d6b/wsidicom/web/wsidicom_web_source.py#L102
If the DICOMWeb server does not support JPEG2000, for example, as a transfer syntax and throws an exception (requests.exceptions.HTTPError: 400 Client Error: BAD REQUEST for url: Google DICOM Archive), the code only catches 406 exceptions.
https://github.com/imi-bigpicture/wsidicom/blob/b0d097c97140ba595529d60de43c472ffc5c6d6b/wsidicom/web/wsidicom_web_client.py#L218
With kind regards,
Christian Marzahl

Hi @ChristianMarzahl
Thanks for the feedback and sorry for the late response.
Limiting WsiDicom to only handle pyramid levels of same tile size was an early design decision. I'm not sure if it is still needed, if it with some effort the restriction could be removed, or how common it is with DICOM WSI-files with non-uniform tile size. Handling WSIs with non-uniform tile size differently when opened by DICOM Web was not intended.
I can try to create some test files with non-uniform tile size, but it would also be helpful to know where the library fails when you open your example as DICOM Web.
For the second issue, my interpretation of the standard is that the server should respond with 406 (Not Acceptable) when the requested transfer syntax is not accepted. Does the more generic 400 (Bad Request) response from Google DICOM Archive give a clear status reason that can be used to check if the error is due to the requested transfer syntax?

I played around a bit with disabling the tile size check together with a slide with levels with tile sizes of 200, 300, and 400 pixels. read_region() works as expected but it gets a bit weird when using get_tile() as (of coarse) the tiles will be of different size.
In the images that you have encountered, what levels are of different tile size? Is relaxation to allow different tile sizes a wanted feature or is it better to drop them (and implement the same checks for the DICOM web source)?

@ChristianMarzahl
I have started working on this in this branch.

Config strict_tile_size_check can be set to False to allow opening wsis with different tile size. The default is True
Change to WsiDicomWebSource so that level instances are filtered by tile size if strict_tile_size_check is True.

Please try this on your problematic WSI.
Also please provide the HTTP error message for Google DICOM archive on unsupported transfer syntax.

Dear @erikogabrielsson,
Thank you very much for looking into it.
I hope to spend some time on it this week to answer your questions.
Best,
Christian


Minor typo in documentation for Send POI: snedpoi => sendpoi

Hi,
a really minor typo: POST /webapi/v1/user/vehicles/:VIN/snedpoi
should be: POST /webapi/v1/user/vehicles/:VIN/sendpoi
Thanks,
Dietmar

Good spot! Please sned a pull request ☺


Cannot resolve binary for Adoptium OpenJDK 17.0.9+9 for Windows

It looks like sometimes there can be issues with the creation of binaries on Adoptium's side and then some binaries can be produced that live in a directory with another version number appended, the file name still carrying the original version.
See https://github.com/adoptium/adoptium-support/issues/994

Fixed via 553927b0ad55783397b3f029e91a4dfe6794170d


Retire headers.go

Closes #274
Discussion is in the referenced issue.

For contributor use:

[X] Targeted PR against master branch
[X] Linked to GitHub issue with discussion and accepted design OR link to spec that describes this work
[X] Code follows the standards mentioned here
[ ] Updated relevant documentation
[X] Re-reviewed Files changed in the GitHub PR explorer
[ ] Added appropriate labels

I messed up the branch when rebasing I guess, fixing

I think you might need to rebase it to the top of master.

@janezpodhostnik I think somehow GitHub showing wrong diff. ( I rebased once again )

ok seems I managed to fix the problem somehow, I think can be merged.


Access to the path 'FSharp.ProjectTemplate' is denied.

Description
Got error when execute build.cmd on a new project.
Repro steps
Please provide the steps required to reproduce the problem

Open Visual Studio Code.

Open an empty folder.

Press Ctrl + Shift + p. Input "F#: New Project(ProjectScaffold).

Execute builld.cmd after Project created.

In the cmd window. Input necessary information when the script asked.

Expected behavior
The build.cmd executed without errors.
Actual behavior
Errors:
FsiEvaluationException:
Error: System.IO.IOException: Access to the path 'FSharp.ProjectTemplate' is denied.
at System.IO.DirectoryInfo.MoveTo(String destDirName)
at FSI_0005.Init.clo@167-5.Invoke(DirectoryInfo d) in D:\Repo\TMobileBill\init.fsx:line 167
at FSI_0005.Init.clo@158-2.Invoke(DirectoryInfo pd) in D:\Repo\TMobileBill\init.fsx:line 167
at Microsoft.FSharp.Primitives.Basics.List.iter[T](FSharpFunc2 f, FSharpList1 x)
at Microsoft.FSharp.Collections.ListModule.Iterate[T](FSharpFunc2 action, FSharpList1 list)
at <StartupCode$FSI_0005>.$FSI_0005_Init$fsx.main@() in D:\Repo\TMobileBill\init.fsx:line 158
Stopped due to error
Known workarounds
Please provide a description of any known workarounds.
Related information

Operating system: Windows 10
Branch
.NET Runtime, CoreCLR or Mono Version
Performance information, links to performance testing scripts

I experience the same problem.

Ok I've been able to reproduce this problem and have also got a workaround.
Effectively, if you run this while the "project" is open in Visual Studio Code, the latter locks 'FSharp.ProjectTemplate', hence why you get the error.
The workaround is to close Visual Studio Code and then run "build.cmd"

Closing. The path gets renamed during the init build.


Weird behavior when resizing

Expected Behavior
When resizing a page where charts are put into cols, I expect them to keep a minimal size and not grow as much as they can
Current Behavior
When you have 2 charts in separate cols and you shrink the window. The two charts expand full width.
I tried to fiddle with responsive: true, maintainAspectRatio and Divs but to no avail (https://github.com/chartjs/Chart.js/blob/master/docs/general/responsive.md#important-note)
Try resizing the page on this fiddle (growing will work but shrinking will make the two charts take full width) in chrome
https://jsfiddle.net/cthumerelle/z1gL7ywa/9/

You can set overflow: hidden in .col, to overcome the fact that chart sometimes grows just slightly too large.

That's working like a charm :)
https://jsfiddle.net/cthumerelle/z1gL7ywa/17/


Error spotted

This line of code looks wrong. (https://github.com/stevenpjg/ddpg-aigym/blob/master/critic_net.py#L84)
It should have critic model predicting not actor model.

Fixed! Possibly a typo, however this method was an inactive one in the code.


suitesparse -> libsuitesparse, typo fixes

test gpkit please

test models please

test models please

So you are replacing ipywidgets with jupyer? Should I do the same in all the tests scripts so they match your install instructions?

test models please

Jupyter now installs ipywidgets!

Ok, you should fix the typo of 'pip install jupyer' to 'pip install jupyter'
So if the install instructions now suggest using jupyter, we should update all the testing scripts to install that instead of just installing ipywidgets. Correct?

We don't currently test anything with ipywidgets, though, right? And it's the thing we acually import.

Installing jupyter can take some time (if you don't have libzmq installed it compiles it), so maybe we could do that just for gpkit_Install?

test models please

test models please

@whoburg, ready for review (it's just docs fixes, so I'll merge it now to avoid confusing anyone with bad installation instructions...)


Improperly formatted package.json

With the most recent updates the package.json generated by the version executor are missing the tailing new line making them fail the nx format:check.
It would be great if the files could be formatted via nx devkit prior to being written.
Example:
import { formatFiles } from '@nrwl/devkit';
import { flushChanges, FsTree } from '@nrwl/tao/src/shared/tree';

const tree = new FsTree(root, false);
tree.writeFile('package.json', somePackageUpdate);
await formatFiles(tree);
flushChanges(context.root, tree.listChanges());

Same case with CHANGELOG.md.
Currently working around this by formatting in a pre-commit hook.


Generator Sound repeating

After I turn on a DR Generator in the latest version of Deep Resonance, the sound it makes when it starts up keeps on playing, even when I manually turn it off. It can be fixed by exiting the world, but it happens again when I turn my generator back on.

Probably caused by Botania:
https://github.com/williewillus/Botania/issues/458

I am willing to follow up on this, even though the version I am using is on 1.8.9 and likely not the latest.
I have been experiencing this bug as well. The sound of a running generator just stays there. The way my generator is toggled is by a RFTools Logic Gate and is likely toggled a few times in a minute.
I don't have Botania in the modpack.


Parallel steps are not properly chained to parent & children steps

Parallel steps are not properly chained to parent & children steps

Problem isolated, I'm working on it.


Make timestamp of tool release history more readable

Currently, we have a format of timestamp which is difficult to read.
Task is to format the timestamp.
How to get to the bug:-
After opening the tool

Go to Help
Click on Tool releases
You can view that timestamp are not in proper format.

Completed on commit number :- f34f40c2d05d01810ce35acef77fed0f1dcf485f and fcd32b7cf7c8e04c6042975e980900c4bf0d7f83


Implemented Basic API for Public Project Names

Fixes #
Describe the changes you have made in this PR -
added a 'api/v0/projects' route to act as API Endpoints returning data about Public Projects in JSON API Spec
Screenshots of the changes (If any) -
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Coverage decreased (-1.5%) to 82.737% when pulling 34dc3bbd0cac8d6e84507baa9192db4d88351a5e on UltimateGamer07:api_demo into 89970529e97561132c2fd98bffee6d65ea4f6aff on CircuitVerse:master.

This has to be for your personal project. Currently not required here. @tachyons this can be closed.


iot_model dashboard – switching from metrics back to dashboard creates an error

This is kind of an odd bug since it's not exactly easy to reproduce, but I have steps:

run rill init-example in a new directory
make a dashboard for the IOT example
go to metrics page
switch from metrics to dashboard
click on a filter

https://user-images.githubusercontent.com/95735/200750199-5319d865-b8a8-43c1-af94-79bd592666ed.mp4
I get the following error in the console:
Error: Parser Error: syntax error at or near "AND"
LINE 3:       WHERE  AND "event_datetime" >= TIMESTAMP '2020-07-12T00:01:34.000Z' AND "event_datetime" <= TIMESTAMP '2020-07-20T00:03:37.000Z'
      GROUP BY "light"
      ORDER BY measure_0 desc NULLS LAST
      LIMIT 250
    ...
                     ^
    at DuckDBClient.request (/Users/hamiltonulmer/Code/rill/rill-developer/web-local/src/common/database-service/DuckDBClient.ts:175:13)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at DuckDBClient.execute (/Users/hamiltonulmer/Code/rill/rill-developer/web-local/src/common/database-service/DuckDBClient.ts:55:20)
    at DatabaseService.dispatch (/Users/hamiltonulmer/Code/rill/rill-developer/web-local/src/common/database-service/DatabaseService.ts:78:12)
    at ActionQueueOrchestrator.run (/Users/hamiltonulmer/Code/rill/rill-developer/web-local/src/common/priority-action-queue/ActionQueueOrchestrator.ts:30:24)

Began debugging but didn't quite get far enough. The culprit appears to be how we're handling WHERE clause templating here: https://github.com/rilldata/rill-developer/blob/main/web-local/src/common/database-service/utils.ts


[Enhancement]: Support for Claude 3.5 Sonnet 2024-10-22

Before Requesting

[X] I have searched the existing issues, and there is no existing issue for my feature request

What feature do you want?
Allow users to add new models on their own when they are available, or
add support for Claude 3.5 Sonnet 2024-10-22

The model selection field is a text field, you can type whatever model name you want.

Starting from 0.34.3, we will use -latest variant in the list when possible.


The dev server uses mime type "video/mp2t"

Describe the bug
When getting .ts files from the vite server, they are delivered with the wrong mime type.
Expected would be Content-Type: text/javascript but instead we get Content-Type: video/mp2t.
Reproduction
A simple minimal vite project, with a .ts file to be transpiled, should be enough. See the curl call below for reproducing it.
System Info

vite version: 2.1.2
Operating System: MacOS Big Sur
Node version: v14.15.4
Package manager (npm/yarn/pnpm) and version:
npm: 6.14.10

Logs (Optional if provided reproduction)
Example curl command:
curl http://localhost:4000/src/hello.ts -I
HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Content-Length: 49
Content-Type: video/mp2t
Last-Modified: Mon, 22 Mar 2021 09:22:14 GMT
ETag: W/"49-1616404934238"
Cache-Control: no-cache
Date: Mon, 22 Mar 2021 09:23:10 GMT
Connection: keep-alive
Keep-Alive: timeout=5

Possible cause of the bug
Looks like vite uses the module sirv under the hood to serve the files. Sirv uses the mime which makes from file extension to Content-Type. Looks like mime maps .ts to video/mp2t.

For those seeking to fix this: it is notable that .ts has always been a valid MPEG Transport Stream video format and even predates TypeScript by 17 years, which is why it maps to video/mp2t pretty much everywhere.
It is technically possible to detect an MPEG transport stream by the fact that it has an ASCII capital G every 188 bytes. In our case this a flawed heuristic because it uses a common keyboard character, and it is technically possible that you happen to have a valid TypeScript file with a capital G every 188 bytes starting from the 0th byte:
G();
function G() { console.log('Valid TypeScript'); }

Yes, this is a contrived example, but it runs.
Despite this fact, it is most likely that most people using the Vite server are serving TypeScript instead of MPEG transport streams. Since MPEG is the outlier case here, it is in my opinion fine for Vite to temporarily override all .ts MIME types to text/javascript, and we can raise a separate issue for the MPEG video MIME type, which is a much more complex use case to support.

Related:

https://github.com/jshttp/mime-db/issues/148

I'm running into this in production with audio-worklets. import processorUrl from "../worklets/audio-processor.ts?url"; works great in dev but throws "DOMException: The user aborted a request." in production. Seems like the behavior is inconsistent.
On a side note, it would be nice to have a "*?worklet" hook that registers the module automatically. Maybe by extracting the name from the registerProcessor call in the worklet itself?

@kgullion could you open a new issue with a minimal reproduction linking to this one so we can properly track your issue? Thanks!


tinyfecvpn doesn't work !

i managed to get 2 ubuntu server with public ip
what i did
run  server on ubuntu 1
tinyvpn -s -l<IP_ADDRESS>:4096 -f20:10 -k "passwd" --sub-net <IP_ADDRESS>
run client on my home (ubuntu 2)
./tinyvpn -c -r serverip:4096 -f20:10 -k "passwd" --sub-net <IP_ADDRESS>
tunnels have no packets movement but i can ping <IP_ADDRESS> from client side
am i missing something ?

there wasn't packets movments because i didn't redirect traffic to tunnels


refactor: text inside swap confirmation modal

Refactor Request
Describe the Refactor Request
The texts inside nftTokenCard overflows to the outside. This behavior reduces the appeal of the protocol and should be addressed.
Describe the Proposed Solution
Definition of Done:

[ ] Refactor the overflow of the text inside the NFT token card slot to appear within the container.

Related Code
ConfirmSwapModal.tsx
Related Context

Hey @heronlancellot What do you think about using "[tokenId]" or "[amount]" as a prefix for the Token Name when handling the approvals?
[#71] Frame LayerZero NFT Sepolia
[#23] Dogie - ERC721
[5e9] StreaXToken
Maybe we could have more clearance about the token Id and amount being traded.

Hey @heronlancellot What do you think about using "[tokenId]" or "[amount]" as a prefix for the Token Name when handling the approvals?
[#71] Frame LayerZero NFT Sepolia [#23] Dogie - ERC721 [5e9] StreaXToken
Maybe we could have more clearance about the token Id and amount being traded.

Perfect ! Great idea, let's do it


Document CoC process more clearly

Thanks @SomtochiAma for the find!
It's sort of documented in https://github.com/fluxcd/community/blob/main/GOVERNANCE.md#code-of-conduct already, but this way it's even clearer which process to follow.

As this is not a governance change per-se but just a piece of process documentation I'm merging it now.


how to set Ignoreview on reside menu drawer layout

You have described ignore view to avoid conflict with swipe gesture with viewpager or any other gesture. That's i got it. But I have added  a viewpager in drawer menu layout and applied ignore view as you described. But its not working. How can I solve it ? Please help me out.

@demo-Ashif any solution?

I got no solution. :( btw I didn't get your point . Can you describe please?

@demo-Ashif if i set the ignoreview on my mapfragment , it works.. but also it modify the others fragments.
and maybe is something in my code , because the views on my mapview still are functional in the other fragments (i dont know why)
sorry about my english , its not my native lenguaje


Architecture rewrite

Currently the way things work is:

Container is created for a project
Container has a bindmount for the project directory
'init' process for container is sleep infinity
Commands execute via docker exec api

Some problems that arise from this approach:

Containers hang around indefinitely, although that shouldn't much impact performance
The bind mounts have passthrough to the host, which means attacker controlled data is in the project's directory. Not a direct bypass, but definitely a security smell

A new approach should strive to resolve the above issues, as well as:

Consider a future where controlled sharing across containers (both within and across a project) may be desirable
Aim for an idiomatic approach
Consider implications for non-Linux platforms

Currently there's a Build and Publish container, the idea being that they each have their own needs. I think this can actually be generalized to a sort of RW^X model.
For example, Build has execution rights so we want to minimize its read/write permissions (especially around access to sensitive areas of the file system, environment variables, crates.io tokens, source code, etc).
Publish, on the other hand, may have read/write capabilities (signing keys, crates.io token) but no execute (we don't run build scripts, etc).
This means that cargo-sandbox publish should be safe even though we share a cache across these two systems. But only if we're very careful to ensure that there's no execution in the cargo publish.

It's also probably fine to say that "cargo publish is an advanced case and cargo-sandbox's attempt to isolate the api key is best-effort, ultimately it's the rest of the host we want to protect".

There should be a "priming" step, ie: cargo --version, which will have read/write access to the cargo bin/ directory.


Interpolation issues with suferplots

There is a problem with the plot output for the Canning at ELL with the 28/10/2019 data showing a white band in the DO plot where it should be orange.
canning_2019-10-29_surfer.pdf

Issue is probably related to nearby site driving the very low (out of range) value at ELL. Possible solutions include giving users more freedom in assignment of interpolation method.
Will look at adding this functionality in next development cycle.
@SamRobinson113 can you please add the raw data file so that this can be recreated and tested later on. Thnx

20191029coEXO3.xlsx
20191029cEXO3.xlsx

Two issues here.
White band/blob created by error in colour ramps where values were outside of available colours, which has now been fixed.
Interpolations are harder to work with. Kriging produces sub-optimal results. No easy way to incorporate changes in anistropy without doing a proper step by step modelling which is outside the scope of these visualisations without overcomplication.
Have rolled out a new feature whereby the river bottom is adjusted to bottom values in data. This has had the effect of removing some of those erroneous interpolations below measured values.


[Book] Stone parameters

Add a documentation page that describes how to create a parameter file for the Stone prover depending on the program and what is the format of that file.
Path to your markdown file: docs/pages/usage/parameters.md
References:

https://github.com/starkware-libs/stone-prover?tab=readme-ov-file#configuration-for-other-input-sizes
https://blog.lambdaclass.com/overview-of-the-stone-prover/
https://www.starknet.io/blog/diving-into-the-code-of-stone-prover-video/

Hi @dmirgaleev ,Please let me work on this when od hack starts.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
i am a blockchain developer , this would be my first time contributing to this ecosystem .can i be assigned to this issue ,i am avaliable to work
How I plan on tackling this issue
To approch the problem i will create a documentation page:

Research: Review the provided references to understand how to create a parameter file for the Stone prover.
Write Documentation:
-*Introduction: Briefly explain the purpose of the parameter file in the Stone prover.

Format: Describe the required format of the parameter file, including key sections and examples.
Creation Steps: Provide clear steps to create the parameter file based on the program:

Identify program-specific requirements.
Outline necessary parameters and their formats.
Example content for a parameter file.

Markdown Formatting: Use headers, lists, and code blocks to enhance clarity.
Save the File: Name the file docs/pages/usage/parameters.md and integrate it into the documentation structure.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hi, I'm Alvaro Lazarus a passionate blockchain developer with a good amount of experience on this ecosystem, I love working on clean documentations which makes me confident I can complete this issue, I haven't worked with Stone Packaging before but would love for this to be my first contribution to the project.
How I plan on tackling this issue
To address the issue, I will introduce the Stone prover and highlight the importance of parameter files. I’ll outline key fields such as input parameters, program type, and constraints, and provide a sample configuration in the required format (JSON or YAML). Key sections will include arguments and optional parameters, along with steps for validating the parameter file before use. Finally, I will create structured documentation with headers and code blocks, saving it as docs/pages/usage/parameters.md for integration into the overall documentation.
Best regards,
Lazarus

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
hello i am a frontend developer and a technical writer
please can i work on this issue :)
i would love to be a contributor on this repo
How I plan on tackling this issue
this will be my first time ccontributing to this repo

Hello @LazarusAA! Welcome aboard! Please don't hesitate to join our Telegram group https://t.me/baking_bad_odhack to ask questions and share your progress!  Happy hacking!

Thanks for the warm welcome @dmirgaleev! I'll work on the issue ASAP.

Hey @LazarusAA! Do you have any progress so far?

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I'm a CS major with experience in technical writing and documentation. I've produced and enhanced complex system documentation for a number of open-source projects. I have experience with zero-knowledge proofs and cryptographic protocols, which is helpful in comprehending and elucidating the Stone prover. I'm skilled with Markdown and have arranged technical data in an understandable way in the past.
How I plan on tackling this issue
I would start by carefully reading the included references to obtain a solid understanding of the Stone prover and its settings before creating the documentation page for Stone parameters. The Markdown file should be organised with sections explaining the function of parameter files, their format, and a detailed how-to for making them for various program kinds. I would describe each component, provide examples of parameter files for typical use scenarios, and go over how various parameters impact prover performance. In addition, I would discuss best practices and possible problems for choosing parameters. I would illustrate ideas throughout the document with simple language, brief bits of code, and maybe illustrations.

Friendly heads up that you have till Sunday (October 6) to push final PR. @akintewe

alright got it

hello @dmirgaleev can i take on this issue :)

hello @dmirgaleev kindly assign ETA: 48 hours max

Hello @dmirgaleev, may I give this a try?

I’m still very much interested on this if it’s still open for contribution @dmirgaleev 🙃

Hello @dmirgaleev! As a previous contributor to this project I would love to help with this task., I will start by creating the Markdown file: I'll add a new file parameters.md inside the docs/pages/usage/ directory and continue from there by researching how to create a parameter file and the format of the file. I'm ready to work :)

Sure! You can continue working on it:)

Hey @evgongora ! Can I reassign?


Networks of specific provisions

For specific provisions that we mention, e.g., racial exclusions, introductory section, oath taking, we might want a network diagram of section to section borrowings.

Did we decide against this, @kfunk074? If not, which provisions do you want to do?

Hold off till I get Part 2 better organized.


update go version to fix goreleaser

Thanks for taking care of this @geseq!
I know it’s only release and test actions, but can this somehow break backward compatibility for those who are using Tengo from 1.16 codebase?

It probably won’t work with 1.16 if someone upgraded to recent versions due to the math constants but 1.17 would be fine.
1.16 is fairly old and has been end of life for a fairly long time now so I’m not really sure it’s worth worrying about.

Got it. Should we just start a new major version v3 and change the minimum supported version to Go 1.18?

I don’t mind either way. Historically we’ve just maintained compatibility with the last 3 major versions of Go.
Personally to me v3 seems a bit of an overkill since the changes are mostly bug fixes and library expansions and not really major changes to tengo itself

Makes sense!


ISPN-11205 Server DataSources

https://issues.redhat.com/browse/ISPN-11205
A note about the test:
I had to implement a socket proxy to ensure that the database appears on a fixed port (testcontainers doesn't allow pinning a port). The proxy is opened on a known port (which is what the server points to) and forwards traffic to the database container port.

Rebased and ready to go

Test Result (50 failures / +1)

The ldap tests don't seem to like Datasources

Thanks @tristantarrant


Allow to specify a level to log

Limits the number of messages being sent to graylog.

mweibel, after reviewing the changes you made, I noted a couple of things that could bring confusion.
First, in the README, the modifications you made do not state that the new option will prevent sending messages with certain log levels, I believe this is crucial since this will change the behavior of how the plugin sends the GELF payload.
Second, I don't think line 39 in /index.js file on the register function should be there, since the level is already set to an int when the gelfFactory returns the GELF payload to be sent.
Until you can come up with a solution for these 2 points, mainly the first point I mentioned, this PR will be on hold since it will change behavior.
Please let me know your thoughts and suggestions, I would love to hear them.
Let me know if you have any questions and I'll be glad to answer them.

Thanks for reviewing.

First, in the README, the modifications you made do not state that the new option will prevent sending messages with certain log levels, I believe this is crucial since this will change the behavior of how the plugin sends the GELF payload.

Do you have a preference for how to describe that? In all other logging libs it's usually clear when you specify a log level that it'll only write logs of equal or higher importance.

Second, I don't think line 39 in /index.js file on the register function should be there, since the level is already set to an int when the gelfFactory returns the GELF payload to be sent.

What we give to the config options object is a string representation of the level. What we need later on in order to compare the levels is the integer representation of it in order to be able to check if the log to be sent should be written or not. That's why this is there.

On the documentation part, just make it clear that adding the additional log level option will block certain logs to be sent, I really want the docs to be understood even by the most junior devs.
On the parse function, you got me thinking, the plugin is really small and it could live on the index.js file, however I just don't like the idea of exposing the parsing function to the index, maybe we could figure out how to make this functionality happen but without throwing stuff to the index. I'm open to suggestions here, unfortunately I did not had the time to think of a solution for this, I would love if you could come up with something simple, even if it means adding more stuff to other parts of the plugin.
Let me know your thoughts on this.

I fixed the README.
I don't see how we could make this work in a different way. It's the most simple option given the current structure of the plugin.
The easiest way to make all of this even simpler is by adding a dependency to node-graylog2 and basicly just invoking this dependency. Obviously this introduces complexity in the sense of a dependency but on the other hand lots of things are cared for.
If that's something you'd be open to I'd be willing to make such a PR, but separate from the other two open right now.

node-graylog2 was the reason I wrote this plugin, so no thanks, I wont be adding node-graylog2 as a dependency to this project.
I'll try to think of something tonight, thanks for the fix on the readme :)

node-graylog2 was the reason I wrote this plugin, so no thanks, I wont be adding node-graylog2 as a dependency to this project

Could you elaborate on this?

I'll try to think of something tonight, thanks for the fix on the readme :)

You repeatadly said you don't have much time to maintain this repo. I totally understand this and know how it is as I have several open source packages as well. However I wonder why you insist to change the way this is implemented so much. Seems like a minor isssue to me.

It is a minor issue indeed, don't get me wrong. The thing is I just think this is not a good solution in terms of organization, nothing big at all.
I'll merge both requests today as I have some spare time (finally).
I think I can merge them now and come back at them and refactor if I find it's needed in the future.
Anyways thanks a lot for the help, really appreciate it.


fix(extension): fix extension nls config bug

Types

[x] 🐛 Bug Fixes

#2529 这个PR还是有bug，有两行写入languagePackJson的代码被误删除了，setupExtensionNLSConfig这个方法在activate的时候必须放在后面执行，否则不会生效，修改后已经验证没有问题了，帮忙Review后合并到2.24分支吧

Background or solution

🤖 Generated by Copilot at 767e0d0

Comment out the call to setupExtensionNLSConfig in the activate method of the ExtensionServiceImpl class to avoid overwriting the language pack settings by the plugins (link)
Add the logic to write the language pack settings to the languagepack.json file in the extension folder using the fileService methods in the ExtensionServiceClientImpl class (link)

Changelog

🤖 Generated by Copilot at 767e0d0
Commented out a method call in extension.service.ts and added logic to write language pack settings to languagepack.json in extension.service.client.ts. These changes fix the issue of incorrect language pack settings when loading extensions.

/publish

/publish

@shilin8805 这里 publish 没用，你基于 opensumi/core checkout 一个分支出来提交吧


Trace

--- 24 de jul. de 2022 02:35:53
--- IP (rmnet_data0) 2804:214:8488:9607:908d:586a:c689:279f
--- IP (rmnet_data0) <IP_ADDRESS>
--- IP (rmnet_data1) 2804:214:81a8:a5d7:1:2:6630:71ae
--- Connection: LTE
Trace to AlisaBelisa
Unable to resolve host "AlisaBelisa": No address associated with hostname


On reload on date year search page, date search selection breaks

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

Action Performed:

Open the app
Open settings
Open profile
Open personal details
Open Date of birth
Click on year to open date search page
Reload the app
Search anything and select any value and observe that app does not change the date value to that new field
Go back and reopen date search page and observe selection is still not working, it only works after reloading the app

Expected Result:
App should change year value on selection of year after reload on year search page
Actual Result:
App does not change the year value on selecting new value after reload on year search page
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number:  v1.3.13-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/d25f56a2-24aa-4a31-beab-20b2ad641b5a
https://github.com/Expensify/App/assets/43996225/f46ec84a-4590-4048-b092-3080fd83c2d0
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683797476601219
View all open jobs on GitHub

Reproduced this error, but I think we're going to be updating our date picker soon. Posted here in Slack to verify: https://expensify.slack.com/archives/C049HHMV9SM/p1684020899747059?thread_ts=1682973360.930769&cid=C049HHMV9SM

I can take this on since I have helped to implement this component and Going to ask Callstack to look into the proposal from @hoangzinh

Okay sounds good, should I add the external or internal label, or leave it unlabeled for now while you check with Callstack?

@thesahindia assigning @ArekChr to help out with the review and testing of this one as he has created the component.
@hoangzinh Can you please start a PR?

thanks!

@mountiny will you be the only reviewer on this PR? Just want to make sure there shouldn't also be a C+ reviewer.

Sent an offer to @dhanashree-sawant in Upwork.
@ArekChr is with CallStack so will be paid outside of Upwork.
@hoangzinh will you be paid through Upwork?

@sakluger noting this should be eligible for the bonus as I have been busy with manual requests but this was ready to merge  in time

@dhanashree-sawant I sent the payment, you're all set!
Thanks for the confirmation @hoangzinh, I sent the offer.
@mountiny sounds good on the bonus. 👍

I'm also going to move this to Weekly since there's nothing to update here until after it's deployed.

@mountiny @hoangzinh @ArekChr could you please help complete the BugZero checklist so that I can finish sending out payments? Thanks!

Thanks @hoangzinh! All paid so we can close this one out.


docker-compose_nlu_1 crashes (sometimes with 137 code)

Hi.
I can't even try the quick start solution, after jetty starts it crashes in less than 5 minutes. I never got to a point where I can send a request.
Initially I thought that 137 is exit code for Out of memory killer, but service-postgres-small is behaving in the exact same way. I even tried to spin up a 64 GB RAM VM in cloud but the behavior is the same.
Here is the last thing I see in logs before it restarts:
nlu_1  | [INFO] jetty-9.4.4.v20170414
nlu_1  | [INFO] Scanning elapsed time=38595ms
nlu_1  | [INFO] DefaultSessionIdManager workerName=node0
nlu_1  | [INFO] No SessionScavenger set, using defaults
nlu_1  | [INFO] Scavenging every 600000ms
nlu_1  | 2019-04-03 11:28:22,221 [main] INFO  service.web.ServiceContext:33  - Initializing the Entity Linking Manager
nlu_1  | 2019-04-03 11:28:22,246 [main] INFO  entitylinking.config.ConfigUtils:65  - Configuration 'aida_20180120_b3_de_en_v18_db' [set by environment AIDA_CONF].
docker-compose_nlu_1 exited with code 137
nlu_1  | [INFO] Scanning for projects...

The last line is new contaner
As I said, docker-compose_nlu_1 exited with code 137 message is intermittent. I sometimes get it, sometimes I don't.
I'm running Windows 10 if that's somehow important, which shouldn't be.

I have never seen this issue before, sorry.
What you can do is try to start jetty outside of Docker, as described here: https://github.com/ambiverse-nlu/ambiverse-nlu#alternative-ways-to-run
This should be easier to debug - let us know if you run into further issues!

I'm facing the same issue. After doing a git clone and docker-compose -f docker-compose/service-postgres-small.yml up on MacOS with 16G memory, docker-compose gets stuck a loop where docker-compose_nlu_1 stops with exit code 137.
The following log repeats itself in a loop:
...
nlu_1  | [INFO] No SessionScavenger set, using defaults
nlu_1  | [INFO] Scavenging every 660000ms
nlu_1  | 2019-04-24 12:13:46,174 [main] INFO  service.web.ServiceContext:33  - Initializing the Entity Linking Manager
nlu_1  | 2019-04-24 12:13:46,205 [main] INFO  entitylinking.config.ConfigUtils:65  - Configuration 'aida_20180120_b3_de_en_v18_db' [set by environment AIDA_CONF].
docker-compose_nlu_1 exited with code 137
nlu_1  | [INFO] Scanning for projects...
nlu_1  | [INFO] Inspecting build with total of 1 modules...
nlu_1  | [INFO] Installing Nexus Staging features:
nlu_1  | [INFO]   ... total of 1 executions of maven-deploy-plugin replaced with nexus-staging-maven-plugin
nlu_1  | [INFO]
nlu_1  | [INFO] ------------------------------------------------------------------------
nlu_1  | [INFO] Building AmbiverseNLU 1.1.1-SNAPSHOT
nlu_1  | [INFO] ------------------------------------------------------------------------
nlu_1  | [INFO]
nlu_1  | [INFO] >>> jetty-maven-plugin:9.4.4.v20170414:run (default-cli) > test-compile @ ambiversenlu >>>
nlu_1  | [INFO]
nlu_1  | [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ ambiversenlu ---
nlu_1  | [INFO] Using 'UTF-8' encoding to copy filtered resources.
nlu_1  | [INFO] Copying 43 resources
nlu_1  | [INFO] Copying 74 resources
nlu_1  | [INFO]
nlu_1  | [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ ambiversenlu ---
nlu_1  | [INFO] Nothing to compile - all classes are up to date
nlu_1  | [INFO]
nlu_1  | [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ ambiversenlu ---
nlu_1  | [INFO] Using 'UTF-8' encoding to copy filtered resources.
nlu_1  | [INFO] Copying 53 resources
nlu_1  | [INFO]
nlu_1  | [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ ambiversenlu ---
nlu_1  | [INFO] Nothing to compile - all classes are up to date
nlu_1  | [INFO]
nlu_1  | [INFO] <<< jetty-maven-plugin:9.4.4.v20170414:run (default-cli) < test-compile @ ambiversenlu <<<
nlu_1  | [INFO]
nlu_1  | [INFO]
nlu_1  | [INFO] --- jetty-maven-plugin:9.4.4.v20170414:run (default-cli) @ ambiversenlu ---
nlu_1  | [INFO] Logging initialized @6547ms to org.eclipse.jetty.util.log.Slf4jLog
nlu_1  | [INFO] Configuring Jetty for project: AmbiverseNLU
nlu_1  | [INFO] Webapp source directory = /ambiverse-nlu/src/main/java/de/mpg/mpi_inf/ambiversenlu/nlu/entitylinking/service/web
nlu_1  | [INFO] Reload Mechanic: automatic
nlu_1  | [INFO] Classes = /ambiverse-nlu/target/classes
nlu_1  | [INFO] Context path = /
nlu_1  | [INFO] Tmp directory = /ambiverse-nlu/target/tmp
nlu_1  | [INFO] Web defaults = org/eclipse/jetty/webapp/webdefault.xml
nlu_1  | [INFO] Web overrides =  none
nlu_1  | [INFO] web.xml file = /ambiverse-nlu/src/main/java/de/mpg/mpi_inf/ambiversenlu/nlu/entitylinking/service/web/webapp/WEB-INF/web.xml
nlu_1  | [INFO] Webapp directory = /ambiverse-nlu/src/main/java/de/mpg/mpi_inf/ambiversenlu/nlu/entitylinking/service/web
nlu_1  | [INFO] jetty-9.4.4.v20170414
nlu_1  | [INFO] Scanning elapsed time=26193ms
nlu_1  | [INFO] DefaultSessionIdManager workerName=node0
nlu_1  | [INFO] No SessionScavenger set, using defaults
nlu_1  | [INFO] Scavenging every 660000ms
nlu_1  | 2019-04-24 12:14:37,556 [main] INFO  service.web.ServiceContext:33  - Initializing the Entity Linking Manager
nlu_1  | 2019-04-24 12:14:37,578 [main] INFO  entitylinking.config.ConfigUtils:65  - Configuration 'aida_20180120_b3_de_en_v18_db' [set by environment AIDA_CONF].
docker-compose_nlu_1 exited with code 137

Any advice for getting the small version running?

As mentioned in the code above, you can try running jetty outside of Docker, as described here: https://github.com/ambiverse-nlu/ambiverse-nlu#alternative-ways-to-run - this should allow you to debug the reason for failure.

It seems MacOS's memory limit was the issue. See https://www.petefreitag.com/item/848.cfm

Interesting, this never happened to me - thanks for investigating and reporting back!


[MRG] Ensure git submodules are updated and initialized

This is a continuation of #540. See that PR for details. That PR by @alimanfoo was only missing a test so this is my attempt at adding one.
Some things to note:

Should I merge or rebase upstream or leave this branch where it is?
I'm not a pytest fixture expert, but I don't think there was a cleaner way of doing what I needed to do to create the git repositories. I separated out the functionality of repo_with_content so I could reuse them in my new fixture.
After creating the fixture, I then realized there was no builtin way to get the submodule's SHA without running some commands with subprocess. It made the git unit tests uglier, but I wasn't sure what else to do.
As part of point 2 above, I changed the functionality of adding content to a test repository to use append so theoretically someone could call the same method multiple times to create multiple commits.

I think this tests what it needs to test, but may not be how the maintainers want this structured. Let me know what you want changed. Git tests pass locally.

This looks good to me. Maybe the tests could be even nicer but this is definitely better than the current state and not obviously unmaintainable/total mess so I'd merge it. You can always come back and make a second PR to clean up or refactor the tests.

Should I merge or rebase upstream or leave this branch where it is?

I'd rebase after #640 is merged which will fix the docs failure (I think).

Ok I rebased with master. I also made it so the submodule repository has two commits, but the parent repository wants the submodule at commit 1. This makes sure that our operations don't accidentally update the commit the submodule is at.

Merging! Thanks for picking this up and contributing the test.


Not All React's Hooks Are Implemented

Not all of React's builtin hooks have been implemented. If you have a pressing need for a missing hook leave a comment here.

[x] use_state
[x] use_effect
[x] use_context
[x] use_reducer
[x] use_callback
[x] use_memo
[x] use_ref
[x] use_debug_value

@rmorshea Which hooks are still under development?

I think the only one not implemented at this point is useContext.

This is done now!


Update TargetVersion of a Issue

I'm trying to update an issue, but the changes don't apply in server side:
RedmineManager redmine = RedmineManagerFactory.createWithUserAuth(REDMINE_URI, REDMINE_USERNAME, REDMINE_PASSWORD);
Issue issue = redmine.getIssueManager().getIssueById(id, new Include[]{Include.attachments, Include.journals});
Version version = redmine.getProjectManager().getVersionById(9);
issue.setTargetVersion(version);
redmine.getIssueManager().update(issue);
The lib version is: redmine-java-api-2.2.0
tks

I brought back test for updating targetVersion in Issues
this test was marked "ignored" for a while
because Redmine did not support some functionality
around versions in REST API.
I verified this test works fine with Redmine 3.2.3
see the referenced commit with sample test code


Closing KeyboardDatePicker on Selection

I am trying to close the date picker once I have selected a date, I was not able to find any props for this, a prop CloseOnSelection would help people very much I guess, although I need urgent help rightnow for a live project, any help ??

Please submit support requests and questions to StackOverflow using the tag material-ui. StackOverflow is better suited for this kind of support. The issue tracker is for bug reports and feature discussions. See also our CONTRIBUTING guidelines.

Also linking #1651 as related.

hey @oliviertassinari thank you for your help, it helped although I on my first glance in the docs couldn't find the autoOk prop clear enough, therefore I thought this can be a feature, that is why I opened this issue.
Thanks for the help, should I make a PR for this in the docs to make this clear?
Thank you again so so much, this library is a gem.

Thanks for proposing your help but at this point, it's unclear which solution we will go for.


Documentation for s in UnivariateSpline is confusing

From the docs:

w : (N,) array_like, optional
Weights for spline fitting. Must be positive. If None (default), weights are all equal.

s : float or None, optional
Positive smoothing factor used to choose the number of knots. Number of knots will be increased until the smoothing condition is satisfied:
If None (default), s = len(w) which should be a good value if 1/w[i] is an estimate of the standard deviation of y[i]. If 0, spline will interpolate through all data points.

I interpret that to mean that if w is not specified, then s=0 should be the same as s=None but that does not seem to be the case.

I read this as s = nobs = len(data) in this case
implied weights if w is not specified are w = np.ones(len(data))
guessing based on part of docs in description

@josef-pkf how do you think s will differ when you set it to None vs 0 when w=None?

TBH I fail to read it as s=0 is equivalent to s=None. It is definitely not the same. Compare the plot at
http://docs.scipy.org/doc/scipy-0.15.1/reference/generated/scipy.interpolate.UnivariateSpline.html
(s=None, default) to http://docs.scipy.org/doc/scipy-0.15.1/reference/generated/scipy.interpolate.InterpolatedUnivariateSpline.html#scipy.interpolate.InterpolatedUnivariateSpline --- here s=0.

I know they are not the same. My question is what is actually happening.

The missing piece of documentation is maybe that UnivariateSpline does not do interpolation, it does fitting unless you force interpolation by using s=0.
Regarding what is actually happening, uhm well, here are Fortan level docs: https://github.com/scipy/scipy/blob/master/scipy/interpolate/fitpack/curfit.f#L141
Maybe some of this information could/should be added to python level docs.

if w is None and s is None: s = number_of_observations is my interpretation of the docstring (which sounds too large to me)

My question is what is actually happening.

This has already been answered in this thread, but I agree that the interface is confusing. You might think if you don't want weights or smoothing then you just don't provide w or s, but in fact this will use default (equal) weights and default (nonzero) smoothing. So if you want to disable smoothing then you have to set it to zero explicitly.

correction: s=len(x) is not too large because s is sum of squares and not mean.
From the docstring this would mean it's designed for standardized variables where variance (ss / nobs) is one

but I thought/think s is residual sum of squares not sum of squares of y.

@cancan101 viewing this as a documentation issue, what would you suggest to add/remove/improve?
I don't think we should change the behavior of the UnivariateSpline (as, erm, quirky it is)

Perhaps mention that s=0 results in an interpolating spline whereas the default of s=None yields a smoothing spline that uses all of the points?


🎮 Game Request
Basic description:
It is a simple game word guessing game where the has to guess the word by filling the blanks.User has to guess one letter at a time to fill in all the blanks and user can make only 5 wrong attempts.That'why !(not)more than 5 :).
How to play:
Simply users have to guess the name of animals.On screen they are able to see three things,that help them to guess the name and continue in the game. 1.Number of letters. 2.Number of guesses remaining,it is shown by the blocks.every time user make a mistake it increase the a block in structure.once the structure touches the base ,the game is over. 3.Also If users don't want to contiue with the same word,they can go to new word also.
Screenshots:

Point down the features
Game points:
The game consist of three parts:
1.How to play section: It helps users to understand about the game and rules they have to follow.
2.New Game section : To enter in to the game.
3.Dark and light mode section : Users can toggle their screen between light and dark mode as per their requirement.
Link: https://susanstorm.github.io/Not-morethan5/
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @SusanStorm !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @SusanStorm ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Custom food items

Gonna work on this tonight

this is basically done, as in i added 2 food items and not sure what to add.


Support for JSON Feed

There's this newfangled thing called JSON Feed that may or may not be worth supporting. So far, I've only seen it used on n-gate.com.

I was having a few blogs today on HN and saw it in the source.

Not sure how useful this is, given that I have never encountered a site that was exclusively syndicated over JSON Feed but not Atom or RSS.

Not sure how useful this is, given that I have never encountered a site that was exclusively syndicated over JSON Feed but not Atom or RSS.

That might be the case, however if people took that stance on every new standard we'd have nothing new. JSON Feed has a fairly well written specification, and is starting to become more popular.


When will you start creating content that is useful?

You explain in the typeof documentation about GetType, but you say almost nothing about the subject at hand, why is that?
Here is a peace of useful info from you know where(just a taste):
"All are different.
typeof takes a type name (which you specify at compile time).
GetType gets the runtime type of an instance.
is returns true if an instance is in the inheritance tree.
...etc."
And this is across the board so often.

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

ID: 8e46579c-383b-1049-fee9-59c27328f7ba
Version Independent ID: e9a776dd-e2b4-a2b2-6db4-4de7a4a0baeb
Content: typeof (C# Reference)
Content Source: docs/csharp/language-reference/keywords/typeof.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

What is missing in this document that you need @VProfirov ?

Closing due to the lack of response. Please let us know if you can share more information about what you'd like to see on this page.


Upgrade to netcoreapp2.1

This resolves issues debugging when using types that are available only in 2.1 runtime. Regardless of this change, CLI will be on 2.1 so this change should be safe.

Note this does not move our DLLs to netstandard2.1, just our entry-point.


Differences to keycloak-config-cli

Hello,
I just discovered this project.
Currently I am using keycloak-config-cli to have configuration-as-code for Keycloak.
Now, I have some of questions:

what are the differences/advantages of using your tool compared to the tool I mentioned? One difference is the configuration format (YAML vs JSON). Are there other differences/advantages?
looking at the source code of your tool, it uses the Keycloak Admin REST API, with a client that you have implemented. Why not use the existing Keycloak Admin REST API Java SDK?

Please note that this are just questions, and no criticism. More tools are always good, and of course you are free to build your own tool. :)
Regards!

Hey @skhro87 I don't know the tool you mentioned and can't detail the differences between the two :/
I have implemented my own api because the original Java SDK is really hard to use in my eyes :)

Alright @klg71 , that answers my questions!
Thank you! :)


Warning: Nashorn engine is planned to be removed from a future JDK release

It seems likely that Norconex/collector-http uses (directly or indirectly) the Nashorn engine. This leads to the warning message given in the log of this issue.
It's by using

tagger class="com.norconex.importer.handler.tagger.impl.ScriptTagger">

that I get this warning.
Is there a way to stop using Nashorn and adopt an alternative instead?

I would not worry as there is no tight-coupling.  Nashorn is not referenced explicitly.  The tagger refers to the JavaScript engine by the engine name "JavaScript", which is by default the one shipped with your JVM.  Ideally, "JavaScript" will remain available under that engine name in future JVM releases, even if the actual implementation changes. Worst case you just have to specify the new name, but keep your script. In the end, if you stick to ECMAScript basics, you should be fine with any implementation.
You can also add your own scripting engine.  A quick tip: if you put an invalid engine name, like engineName="IamBad", then you will get an error and the tagger should list available engines in your JVM.  That is a way to know what you have installed or available to you.

To silence these warnings, add:

-Dnashorn.args=--no-deprecation-warning


Update Client tool to support custom TEE pubkey and KBS certificate

Added optional parameters for importing custom TEE public key.
Added optional parameters for provide custom KBS Root certificate.
Provided SDK format for Client Tool.

These enhancements will make the Client tool easier to use

The PR looks good to me. Do we want to wait for https://github.com/confidential-containers/guest-components/pull/273 to be merged or you'd like this to go in sooner?

The PR looks good to me. Do we want to wait for confidential-containers/guest-components#273 to be merged or you'd like this to go in sooner?

@sameo We can wait for https://github.com/confidential-containers/guest-components/pull/273 to be merged. This is definitely after the release of v0.7.0, we don't plan to add this PR's feature in v0.7.0.

The PR looks good to me. Do we want to wait for confidential-containers/guest-components#273 to be merged or you'd like this to go in sooner?

@sameo We can wait for confidential-containers/guest-components#273 to be merged. This is definitely after the release of v0.7.0, we don't plan to add this PR's feature in v0.7.0.

Ok, so maybe we should tag this PR as a draft, or WIP, so that we don't merge it before the guest components PR is merged as well?


Basic CI implementation (https://github.com/kubernetes-sigs/cluster-api-provider-kubemark/issues/26)

What this PR does / why we need it:
Basic CI implementation (https://github.com/kubernetes-sigs/cluster-api-provider-kubemark/issues/26)
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #26
Special notes for your reviewer:
Release notes:

NONE

this looks cool @apoorva-jn , are you going to add some docs on how to operate the ci tests?

this looks cool @apoorva-jn , are you going to add some docs on how to operate the ci tests?

Sure, I will do.

/easycla

@elmiko:  please take another look when have a chance.

thanks for adding the instructions @apoorva-jn , i'd like to try this out tomorrow, but otherwise it's looking good to me.

should the Release notes: on this PR be blank? or say NONE?
@elmiko wdyt?

should the Release notes: on this PR be blank? or say NONE? @elmiko wdyt?

i think "None" or "N/A" is a good option

@elmiko - regarding capi version, I have a PR ready to go right after Apoorva's to upgrade to CAPI v1.0 (or at this point even 1.2), I will do it as part of issue https://github.com/kubernetes-sigs/cluster-api-provider-kubemark/issues/10
for the sake of this PR and your test please make sure that you run against cluster-api v0.4 (v1alpha4)
would that be okay?

@elmiko - regarding capi version, I have a PR ready to go right after Apoorva's to upgrade to CAPI v1.0 (or at this point even 1.2), I will do it as part of issue #10

++

for the sake of this PR and your test please make sure that you run against cluster-api v0.4 (v1alpha4)
would that be okay?

yeah, sounds good. i will try another test with the versions we have specified.

@apoorva-jn - there seems to be an issue that we don't actually test the current code with this process:
looking at Makefile, I see that we indeed build kubemark controller from code:
.docker-build-capk:
 	@make -C $(ROOT_DIR) release-manifests
 	@make -C $(ROOT_DIR) docker-build REGISTRY=$(DEV_REGISTRY)

but the fact that you then point to this image quay.io/elmiko/kubemark subsequently, negates the image built earlier
instead, we should modify to something like this:
.docker-build-capk:
 	@make -C $(ROOT_DIR) release-manifests
 	@make -C $(ROOT_DIR) docker-build REGISTRY=$(DEV_REGISTRY) && \
 		make -C $(ROOT_DIR) docker-push REGISTRY=$(DEV_REGISTRY)

and point to kubemark image at $(DEV_REGISTRY)

/lgtm

thanks for the updates @apoorva-jn , i will give this another test on monday.

@elmiko : Did you get a chance to test this?

after talking with @apoorva-jn on slack, i got this working. the last piece i needed was to export KIND_CLUSTER_IMAGE=docker.io/kindest/node:v1.21.10. i think we should pin that version in the hack/test/Makefile as a variable that can be overridden. that way we at least have the working defaults in place.
Tenant cluster is ready!

You can access tenant cluster with the above kubeconfig. (It also can be found in '/tmp/km.kubeconfig')

For CNI, you may apply calico with 'kubectl --kubeconfig /tmp/km.kubeconfig apply -f https://docs.projectcalico.org/v3.20/manifests/calico.yaml'

/lgtm

@elmiko : It works for me.

`NAMESPACE                           NAME                                                             READY   STATUS    RESTARTS   AGE
capd-system                         capd-controller-manager-766c69b845-pbmw7                         1/1     Running   0          3m41s
capi-kubeadm-bootstrap-system       capi-kubeadm-bootstrap-controller-manager-5997bbf6b8-27d6s       1/1     Running   0          3m43s
capi-kubeadm-control-plane-system   capi-kubeadm-control-plane-controller-manager-6f6bc6fd9c-hgfnp   1/1     Running   0          3m42s
capi-system                         capi-controller-manager-584b949db5-vzlb4                         1/1     Running   0          3m44s
capk-system                         capk-controller-manager-67fcd6665b-tf48l                         2/2     Running   0          3m38s
cert-manager                        cert-manager-667d895889-7sq9h                                    1/1     Running   0          3m55s
cert-manager                        cert-manager-cainjector-679f86cb46-lknhj                         1/1     Running   0          3m55s
cert-manager                        cert-manager-webhook-7d6784f6bf-nrhnx                            1/1     Running   0          3m55s
default                             km-wl-kubemark-md-0-5wc59                                        1/1     Running   0          2m53s
default                             km-wl-kubemark-md-0-fl4kz                                        1/1     Running   0          2m53s
default                             km-wl-kubemark-md-0-klgl2                                        1/1     Running   0          2m53s
default                             km-wl-kubemark-md-0-wz5tb                                        1/1     Running   0          2m53s
kube-system                         coredns-558bd4d5db-2cg6r                                         1/1     Running   0          8m32s
kube-system                         coredns-558bd4d5db-mwdhz                                         1/1     Running   0          8m32s
kube-system                         etcd-kind-control-plane                                          1/1     Running   0          8m49s
kube-system                         kindnet-lv4k9                                                    1/1     Running   0          8m33s
kube-system                         kube-apiserver-kind-control-plane                                1/1     Running   0          8m48s
kube-system                         kube-controller-manager-kind-control-plane                       1/1     Running   0          8m49s
kube-system                         kube-proxy-6v27c                                                 1/1     Running   0          8m33s
kube-system                         kube-scheduler-kind-control-plane                                1/1     Running   0          8m49s
local-path-storage                  local-path-provisioner-74567d47b4-rhkpr                          1/1     Running   0          8m32s

`

` NAME                        STATUS   ROLES                  AGE   VERSION
km-cp-control-plane-svlbp   Ready    control-plane,master   62s   v1.21.1
km-wl-kubemark-md-0-5wc59   Ready    <none>                 46s   v1.21.1
km-wl-kubemark-md-0-fl4kz   Ready    <none>                 46s   v1.21.1
km-wl-kubemark-md-0-klgl2   Ready    <none>                 47s   v1.21.1
km-wl-kubemark-md-0-wz5tb   Ready    <none>                 47s   v1.21.1 `

thanks @apoorva-jn , it's probably just my test setup then. i think we'll need to be aware of this as we start to use the testing script, but i'm good to approve.
thanks again for all the hard work on this =)
/approve

@apoorva-jn , i just noticed that you printed the results in the management cluster. would you mind adding the CNI to the workload cluster and then printing the output of kubectl get pods -A


Package as PyPi

This issue is just to elaborate the idea on packaging symupy as a standard python package

The package has been adapted to be distributed via pipy.  It has not been published since

[ ] Integrate and distribute binaries (simulator)
[ ] Adapt testing to the distributed binaries
[ ] Publish package on pypi first version

The package is available via pip install symupy. It is important do remember the checks in the following steps:

Before publishing: run tests in folder tests in dev
Increase the versioning in symupy/__init__.py
Commit changes in __init__.py
Be sure to merge everything to master commit as :label: bump 0.0.1 ➡ 0.0.2
Add changes to CHANGELOG.md
Create redistributables + binaries via python3 setup.py sdist bdist_wheel
Test the proper installation via pip install -e symupy  or pip install -e . if you are inside the folder
Check that the distribution is properly working twine check dist/*
Upload to test pypi via

python3 -m twine upload --repository-url https://test.pypi.org/legacy/ dist/* or
twine upload --repository-url https://test.pypi.org/legacy/ dist/*

Check the proper installation:

conda create -n test python=3.7 pip
pip install -i https://test.pypi.org/simple/ symupy

Upload to pypi via

python3 -m twine upload dist/* or
twine upload dist/*

Check the proper installation:

conda create -n test2 python=3.7 pip
pip install symupy

Last version of the package is available here


Perform storage stress test via fio

I would like to perform storage stress test using fio on AUT via litmus experiments

Thanks for the experiment @gpsingh-1991!

fixed via https://github.com/litmuschaos/litmus-go/pull/383


Fix URL to the Pile

Reported in the forums: https://discuss.huggingface.co/t/chapter-5-questions/11744/28?u=lewtun
TODO:

[ ] Export notebooks after this is merged

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


WIP: Add initial code for IRv2 decoder.

The changes in this PR are only to facilitate discussions. The original IR decoder was modified directly for the ease of prototyping and to show the differences between the two decoders. (Maybe we would end up with only one decoder depending on our discussion results.)
Description

Validation performed

@LinZhihao-723 / @kirkrodrigues
In addition to the inline questions, could you help me with below queries?

Shall we plan for two decoder classes or a single one for IRv1 and IRv2?

If we're to have two classes

Shall we release the classes as separate binaries?

Note there could be size overhead in the binaries.
That likely means we need to differentiate IRv2 from IRv1 in the Log Viewer. Not sure about how yet.

If we wish to maintain a single class

Do we plan to have the KeyValuePair as a new encoding type? That way it can be passed as a template variable to classes.
How do we differentiate IRv2 from IRv1 though? Do we check the version number from the file? (I got a bit confused by the clp-core code as it seems the "beta" version is referring to IRv2 while IRv1 is the regular version. Could you confirm?)

I think there have been different iterations of this discussion though I'm not sure about the latest conclusion: What're the official names for IRv1 and IRv2?

How should we name the class / classes?

@LinZhihao-723 / @kirkrodrigues In addition to the inline questions, could you help me with below queries?

Shall we plan for two decoder classes or a single one for IRv1 and IRv2?

If we're to have two classes

Shall we release the classes as separate binaries?

Note there could be size overhead in the binaries.
That likely means we need to differentiate IRv2 from IRv1 in the Log Viewer. Not sure about how yet.

If we wish to maintain a single class

Do we plan to have the KeyValuePair as a new encoding type? That way it can be passed as a template variable to classes.
How do we differentiate IRv2 from IRv1 though? Do we check the version number from the file? (I got a bit confused by the clp-core code as it seems the "beta" version is referring to IRv2 while IRv1 is the regular version. Could you confirm?)

I think there have been different iterations of this discussion though I'm not sure about the latest conclusion: What're the official names for IRv1 and IRv2?

How should we name the class / classes?

In my opinion we should maintain two classes for now before we have full supports of IR v2, including: (1) backward compatibility with IR v1; (2) metadata kv-pair supports. That's also why the version number for v2 is still marked as "beta". But due to my limited understanding of the new log viewer, I actually don't know the implications/overheads of the two alternatives you proposed. We can schedule an offline meeting if you want.
There's no special name for IR v1. For IR v2, I think a more formal name we used in our core PRs is "key-value pair IR format"

Shall we plan for two decoder classes or a single one for IRv1 and IRv2?

We should plan for one stream reader (a.k.a. decoder / deserializer) class by the time we start using this in production. Before now and then, we can do whatever is simplest.

If we're to have two classes, shall we release the classes as separate binaries?

Do we need to? The way I see it, the two readers are part of the same IR library, so it feels easier to keep them in one binary.

Note there could be size overhead in the binaries.

I guess it's still smaller than the IR streams we end up decoding?

That likely means we need to differentiate IRv2 from IRv1 in the Log Viewer. Not sure about how yet.

Right, this is another reason to go with one binary.

If we wish to maintain a single class, do we plan to have the KeyValuePair as a new encoding type? That way it can be passed as a template variable to classes.

The production release plan is that the KV-pair IR format will support deserializing IR v1 streams and expose them with the same API as KV-pair IR streams. So hopefully we can move away from all the different template specializations.

How do we differentiate IRv2 from IRv1 though? Do we check the version number from the file? (I got a bit confused by the clp-core code as it seems the "beta" version is referring to IRv2 while IRv1 is the regular version. Could you confirm?)

In my mind, the production release will use a different version number to differentiate the two.

I think there have been different iterations of this discussion though I'm not sure about the latest conclusion: What're the official names for IRv1 and IRv2?

As Zhihao said above.

How should we name the class / classes?

IRStreamReader and KVPairIRStreamReader? I think reader is more appropriate than decoder / deserializer since these classes really do both. Hopefully we don't have to keep these names for long.

@kirkrodrigues Thanks for completing the responses. I'll stick with one binary and redesign the interfaces with one stream reader pictured.
I also shortly discussed offline with Zhihao yesterday, and we have these items opened for discussions (@LinZhihao-723 please correct me if I'm wrong):

Currently we need to select a correct deserializer depending on the IR file version, but there is no existing code in clp-core that can directly differentiate an IRv1 stream from an IRv2 one. We explored below options:

Assign a different magic number to IRv2 files.
decode_preamble(reader) in C++ code and read the version out, although that would consume bytes from the reader, and directly reusing the reader for deserializer creation would cause protocol failures. We can make a copy before passing it to decode_preamble though.
Since the metadata is stored as a JSON in the preamble, "peeking" into the first few bytes in JS code to decode the version out before calling into C++ code is a possible option.

KV-pair IR format will support deserializing IR v1 streams and expose them with the same API as KV-pair IR streams

Do we have a timeline for this to be ready?

The PR is not ready for review yet as I'm still cleaning up the log level filtering code for IRv2.

This prototype is for reference only and not meant to be merged.

Closing this since all features prototyped in this PR has been checked in.


Bumps node version

Travis was complaining that the version of node set in .travis.yml was too low for one of the npm packages. this bumps node to v12.13.0

Travis is passing again, I’ll merge this


Add an 'update-button-on' attribute to update the button text when an expression changes.

See advanced static example for reason/usage.

Thank you for open PR, Would you please add an unit test spec for this new feature? you can add into test/spec/, a new file is OK.
Note that current karma-jasmine version is 0.1.5

Is there any reason this hasn't been merged? I'm going to be forking to integrate this request for my own project. I need this so I can update the names of the selected values when the user changes their language.

The feature of this PR has already implemented by another PR #131


p2p: session.getRangeByHeight should change condition check from == to >= given that the number of headers being appended is more than 1 at a time

https://github.com/celestiaorg/go-header/blob/18f0eb1c5d3aeab6476123da0dad57e82c067984/p2p/session.go#L117
should be changed to >= from == given that right above you added what could be more than just 1 header.
Kindly cc-ing @Wondertan @walldiss

Hey, thanks for pointing that out!
I totally agree - adding a check to ensure from < to will help prevent any range mix-ups and make the code more robust.


BSO Agility

So this one was interesting. In BSO levels can go up to 120, a great feature absolutely. Although with Agility, it can be quite detrimental the higher level you are, due to the rate of obtaining marks of grace becoming slowed, at increments of being 10 levels higher than the course requirement.
The rank 1 agility man Illusion, informed me he stopped doing agility because his rate of marks was so low, it wasn't worth it to him anymore. He is but a simple man, who provided thousands of free marks of grace for the people who needed a set of full graceful.
If it's possible to cap the mark loss at level 99, I'm sure it would make him, an extremely happy boy. I told him I'd make this apparent on GitHub and get some attention for him.

This was fixed.


Add a dependency to pom file to fix compilation

Add a dependency to pom file to fix compilation. I included an exclusion to the dependency, as was done in https://github.com/data-integrations/dynamic-partitioner/pull/1.
Compilation was broken in https://github.com/data-integrations/google-cloud/pull/64 (I'm not sure how the changes in that PR was compiling), but without this change, I get:
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /Users/alianwar/src/google-cloud/src/main/java/co/cask/gcp/common/RecordFilterOutputFormat.java:[34,32] package org.apache.orc.mapreduce does not exist
[ERROR] /Users/alianwar/src/google-cloud/src/main/java/co/cask/gcp/common/StructuredToOrcTransformer.java:[33,22] package org.apache.orc does not exist
[ERROR] /Users/alianwar/src/google-cloud/src/main/java/co/cask/gcp/common/StructuredToOrcTransformer.java:[34,29] package org.apache.orc.mapred does not exist
[ERROR] /Users/alianwar/src/google-cloud/src/main/java/co/cask/gcp/common/StructuredToOrcTransformer.java:[47,83] cannot find symbol
  symbol: class OrcStruct
[ERROR] /Users/alianwar/src/google-cloud/src/main/java/co/cask/gcp/common/StructuredToOrcTransformer.java:[50,29] cannot find symbol
  symbol:   class TypeDescription
  location: class co.cask.gcp.common.StructuredToOrcTransformer
[ERROR] /Users/alianwar/src/google-cloud/src/main/java/co/cask/gcp/common/StructuredToOrcTransformer.java:[53,10] cannot find symbol
  symbol:   class OrcStruct
  location: class co.cask.gcp.common.StructuredToOrcTransformer
[ERROR] /Users/alianwar/src/google-cloud/src/main/java/co/cask/gcp/common/StructuredToOrcTransformer.java:[70,11] cannot find symbol
  symbol:   class OrcStruct
  location: class co.cask.gcp.common.StructuredToOrcTransformer
[INFO] 7 errors
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:11 min
[INFO] Finished at: 2018-11-08T14:09:12-08:00
[INFO] ------------------------------------------------------------------------

Compilation now passes:


Cannot open assembly 'Support/...' on macOS

On macOS I get a following error while starting the VSCode with Omnisharp:
VSCode:
Version: 1.53.0
Commit: 8490d3dde47c57ba65ec40dd192d014fd2113496
Date: 2021-02-03T16:01:04.046Z
Electron: 11.2.1
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.6.0

Log:
Starting OmniSharp server at 2/5/2021, 8:34:05 AM
    Target: /Users/xxxx/Documents/Projects/xxxx/xxxx/xxxx/xxxx.sln

OmniSharp server started.
    Path: /Users/xxxx/Library/Application Support/CodeDotNet/ms-dotnettools.csharp-1.23.9/.omnisharp/1.37.6/run
    PID: 7470

Cannot open assembly 'Support/CodeDotNet/ms-dotnettools.csharp-1.23.9/.omnisharp/1.37.6/etc/config': No such file or directory.
[ERROR] Error: OmniSharp server load timed out. Use the 'omnisharp.projectLoadTimeout' setting to override the default delay (one minute).

This is not a default path for the extension

/Users/xxxx/Library/Application Support/CodeDotNet/ms-dotnettools.csharp-1.23.9/

how did you install this?
The reason why it fails, is the space in the folder name. It shouldn't fail on a space, but nevertheless, by default the extension gets installed under ~/.vscode/extensions

My bad, wrong arguments (should be swapped):
/usr/local/bin/code --user-data-dir="$HOME/.vscode-dotnet" --extensions-dir="$HOME/Library/Application Support/CodeDotNet" "$@"
nevertheless like you said, it should not crash on space in the path


Add max-pixels parameter for images

Closes #137
Let's hope I didn't do anything too crazy this time!
a1e24ed pulls out code common to types that can have values in the parameters column as we had discussed in a prior PR.
Instead of passing on the max-pixels value in parameters I went straight to adding it to the bind dictionary.
One thing that confuses me is that in the happy case test the order of the bind attributes isn't what I expected: https://github.com/XLSForm/pyxform/compare/master...lognaturel:pyxform-137?expand=1#diff-86152448d7cce73f07b4cd294f930633R14. In fact, when I set debug=True, orx:max-pixel comes before type to give <bind nodeset="/data/my_image" orx:max-pixels="640" type="binary"/>. I don't think this is a symptom of a deeper problem but would be good to get a double check.
The very astute will notice an unrelated change at https://github.com/XLSForm/pyxform/compare/master...lognaturel:pyxform-137?expand=1#diff-b29aeb282b118614b8333cdfc19f700dL859. I noticed that it wasn't used so I snuck that in as part of the extraction.

Thanks! I looked at the new tests (only) in order to not overstep my boundaries. They look great to me.


*added the "queue" param to "execute_job", "main_work_horse" and "per…

*added the "queue" param to "execute_job", "main_work_horse" and "perform_job"
*added " queue.enqueue_dependents(job, pipeline=pipeline)", accordingly was made in the "rq" module

+1 for merging this


Update authoring.md

Added method type and updated final URL according to new language Service endpoint

@jboback
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Allow concise ArrowFunctionExpression (named-functions-in-promises)

In relation to #63, this is the change I'm proposing to support binding context using arrow functions while still maintaining while still maintaining testability.
Here's the example for reference:
export default Component.extend({
  actions: {
    updateUser(user) {
      user.save()
        .then(user => this._reloadUser(user))
        .then(() => this._notifyAboutSuccess())
        .catch(err => this._notifyAboutFailure(err));
        //  As opposed to:
        // .then(this._reloadUser.bind(this))
        // .then(this._notifyAboutSuccess.bind(this))
        // .catch(this._notifyAboutFailure.bind(this));
    },
  },

  // ... Imagine there's a lot of other functions here ...

  _reloadUser(user) {
    return user.reload();
  },
  _notifyAboutSuccess() { /* ... */ },
  _notifyAboutFailure(err) { /* ... */ },
});

Note: This change explicitly allows the concise version of an ArrowFunctionExpression and does not allow arrow functions with explicit () => { /* function bodies */ }. In addition, it checks to ensure that the expression body is a CallExpression to ensure the logic is not happening in the arrow function itself.
Fixes #63

Made the allowable case even more stringent by ensuring that the CallExpression is calling a method on the parent:
// GOOD
user.save()
  .then(() => this._reloadUser(user))
  .catch(err => this._notifyAboutFailure(err))

// BAD
user.save()
  .then(() => user.reload())
  .catch(err => this._notifyAboutFailure(err))

While I'm not sure if this is being to strict, I think erring on the side of being more strict is better. This additional check enforces that your promise handler is defined on the parent itself and not calling out to another object.

@bardzusny I've updated this PR to:

No longer require that the call is being made on a method of this

The rule still enforces that the body of the arrow expression is a CallExpression

Make allowConciseArrow a optional configuration (default: false)

I'm happy to change the name/format of this option.

Document it

@michalsnik Updated to address comments! Thanks for reviewing :)


Uncaught Exception: The Internet connection appears to be offline.: (null)

An uncaught exception was reported.
Info:
OS: darwin
Arch: x64
GPMDP Version: 3.0.0
Time: Mon Mar 07 2016 13:14:16 GMT 0200 (SAST)
Error:
The Internet connection appears to be offline.: (null)
Error: The Internet connection appears to be offline.: (null)
    at Error (native)

This issue was created automatically inside the uncaughtException handler

I also got this right now.
It could be misleading to a user. Is it possible to not show the snackbar for this particularly error?

Yeah, that's been fixed in maste

:+1:


Updated js-yaml to 3.13.1 in package-lock.json

Updated js-yaml to 3.13.1 in package-lock.json as per security alert

Coverage remained the same at 81.284% when pulling dc45673b57ecbfa51b0a000eba31020af90acada on js-yaml-upgrade-vuln into 2c66079533ac6ba6b49661b70eb4b751b4e0bbf7 on master.

Thx for providing the PR.
This has been resolved by upgrading nyc - closing.


CTRL+R doesn't refresh the page but opens the rename title menu

CTRL+R doesn't refresh the page but opens the rename title menu, I don't like that. R alone also opens the rename menu, so I guess one could filter for the CTRL+R shortcut.

Windows?

Windows/Chrome

Ah my mistake. It's fine on OS X. Are there other problematic hotkeys on windows used by Lychee? What would be a cross-platform modifier? Shift?

It's the only hotkey I noticed so far. Btw. Shift+CTRL+R seems to work.

This is maybe an issue of it's own: I think it's strange that you can select images by holding and dragging middle or right mouse button, holding left mouse button should be enough. As far as I know most browsers have the option to scroll through pages by holding and dragging the middle mouse button, so it's a problem that you select images while you try to scroll.

Could you take a look at the v3.0 branch? The issue should be fixed (but I'm not sure anymore :d). Let me know if it's working.


Implement To-dos

Hi @SchluneggerDaniel,
here's a WIP PR for said changes so we can keep code and discussions in a single place.

[x] The current trial needs to stop as soon as the subject makes an error when reproducing the sequence. (d2e17d8)
[ ] The predefined sequence should just start with one color/tone and after correct reproduction by the subject, increase by +1 color/tone.
[ ] Reaction times should be recorded (for the whole sequence only)

Re 2: That shouldn't be too much work, but how should the response data look like then? Currently, it contains a flat array of button presses. Should we just add sub_sequence_length (or the like) to each recorded button press to indicate the length of the sub sequence that the recorded button belongs to?
Re 3: By that you mean the current delta_time field for each button click should be fully replaced by one joint response time per trial, or would you like to keep the per-button timings too?

@SchluneggerDaniel Are you still interested in (3) or (2) then?


Differentiate between per-PR failures vs nightly smoke test runs

I'd suggest making the display more tabular, like in the attached image.

One row per project
Columns for the types of runs (make the nightly tests the first column, since that's what we generally care most about)
Have a catch-call column at the end for any additional builds you're tracking
Optionally put projects with any failing builds at the top of the table?

Slightly nicer image, based on prototyping work in the delucchi/jinja branch.

Adding a reference to #14 which added this in, and perhaps #5 can shuffle things so that this table view becomes the main/only view of the dashboard

Closed by https://github.com/lincc-frameworks/lf-workflow-dash/pull/17


Content should not be tampered with

What I do
Checking file hash before/after being inserted to gopass
What I expect
I expect the file to be the same.
So the hash are equals
What I have
The hash are actually differents
$ gopass bintest < before.txt
$ gopass bintest > after.txt
$ md5sum before.txt after.txt
db81a851af569aef93d40c18fb78da3f  before.txt
3b96771673ab6a08085bd21f3609a36b  after.txt

My understanding
Changing stored content are not the behavior one would expect from a vault :confused:
I understand gopass helps securely share text files accross multiple platforms and may require text files translation (like we have for ftp file transfert modes).
Sharing binary files requires using specific gopass binary
My analysis
I have digged into this default text-mode behavior and realized the OS-specific line ending characters are not translated (which is what is being expected here as for ftp once again...)
The behavior seems to just to add a \n character at the very end of every files.
Following bash script test most binary/text X cr/lf combinations : https://gist.github.com/frntn/ae015b997a8255e3c99b3989d8b89af7

Hmmmm... I tried to play with the binary subcommand and have to admit I am very confused.
I first insert a binary file, using the binary mode.
$ echo -n $'\x01\x63\x61\x74' > before.bin
$ gopass binary cat perso/bintest/cr.bin < before_cr.bin

When I try to retrieve its content I get the base64 encoded version of the original content :
$ gopass perso/bintest/cr.bin
AWMNYQ10DQ==
$ gopass perso/bintest/cr.bin | base64 -d | od -c
0000000 001   c  \r   a  \r   t  \r
0000007

Actually reading/copying/moving actions to binary files require the use of binary subcommand :
$ gopass binary cat perso/bintest/cr.bin | od -c
0000000 001   c  \r   a  \r   t  \r  \n
0000010

Deleting seems to have a bug :
$ gopass perso/bintest
perso/bintest
└── cr.bin (binary)
$ gopass rm perso/bintest/cr.bin
Error: Entry is not in the password store

I have found the following workaround

$ gopass rm perso/bintest/cr.bin.b64

Which I understand shows some reserved filename extensions with some weird side effects :

$ echo "ascii content" | gopass insert perso/bintest/readme.txt
$ gopass perso/bintest
perso/bintest
└── readme.txt
$ echo "ascii content" | gopass insert perso/bintest/readme.txt.b64
$ gopass perso/bintest
Failed to add file perso/bintest/readme.txt to tree: File readme.txt exists
perso/bintest
└── readme.txt (binary)

Thank you very much for your analysis! The bash script is very helpful :100:
There seems to be at least one bug and several usability issues. I'll try to split these so we can track them one by one.

Right now we expect any content inserted into a secret to be unaltered when retrieving it.
This includes anything, even line breaks.
We should implement proper unit/integration tests to ensure this status quo.
There is but one exception we should consider: If the secret does not contain a final newline IMHO we should add this final newline when printing to stdout!
Any discussion if and how we should handle text files (line breaks) across different platforms should be kept in #348, please.

If when printing to stdout means when attached to a TTY
If I redirect stdout to file or a pipe the final newline should not be inserted.
Do you agree ?

Yes, exactly.
I propose we check if the secret has a trailing newline already. If it has OR if output is being redirected somewhere (pipe, file, ...) we do nothing.
If output if going to a terminal AND there is no trailing newline we should append a final newline to avoid messing up the terminal.


faq

being worked on, results tracked by Nyan

Awesome.

:-O

@dukedorje @harlantwood any quick comments? I'm undecided if it is worth pushing out or waiting until we have the deploy next week and then doing a v. 2

Thanks for posted updates @fractastical. Let me know if need changes.


Install IREE nightly

Closes #58

It feels like we need a simple solution to this that works consistently.  This should at least solve the problem of running this notebook, but it's probably still too much juggling for the end user to do.
We'll soon be publishing torch-mlir nightlies to PyPI, but I'm not sure that'll solve the issue, since iree doesn't publish nightlies to pypi and incompatibilities between the two seem to happen regularly.

It feels like we need a simple solution to this that works consistently. This should at least solve the problem of running this notebook, but it's probably still too much juggling for the end user to do.
We'll soon be publishing torch-mlir nightlies to PyPI, but I'm not sure that'll solve the issue, since iree doesn't publish nightlies to pypi and incompatibilities between the two seem to happen regularly.

Ultimately, we either accept nightly instability and align on joint released/pinned versions for interop, or we rebase on a strable ir for interchange.