Content based file watching

Describe the bug
I have a rule that applies format to some files. ibazel catches this as a change and gets stuck in a loop ad-infinitum.
It would be nice if ibazel had the option to check for the file hash opposed to just triggering off timestamp.
Reproduction instructions
genrule(
    name = "generated-code-i-want-in-source",
    outs = [
        "result.code",
    ],
    cmd = ("PREFIX=/ " +
           " $(location //:generate)" +
           " && cp result/result.code $(@D)"
    local = True,
    tools = [":generate"],
)

Expected behavior
Not to get stuck in a loop
Actual behavior
INFO: Elapsed time: 9.686s, Critical Path: 9.49s
INFO: 7 processes: 1 internal, 6 local.
INFO: Build completed successfully, 7 total actions
iBazel [2:14PM]: Starting...
iBazel [2:14PM]: Changed: "result.code". Rebuilding...

Version (please complete the following information):

OS: nixos
iBazel - Version 0.25.3

Build label: 6.5.0- (@non-git)
Build target: bazel-out/k8-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Tue Jan 1 00:00:00 1980 (315532800)
Build timestamp: 315532800
Build timestamp as int: 315532800

Actually, it's OK. This works fine
ibazel -debounce 15s //:whatever

Nope, nvm. It starts the program and then kills it after 15s


Comment tables and fields when creating migrations

Now with Rails 5 we can add comments on tables and their fields.
These comments are important so everyone can understand what information the table holds and what each field represents.
This can be done like this:
# frozen_string_literal: true

class ExampleTable < ActiveRecord::Migration[5.0]
  def change
    create_table :example_table, comment: 'The is an example table for this suggestion' do |t|
      t.references :example_reference, index: false, foreign_key: true, comment: 'A reference example'

      t.integer :example_field, comment: 'The is an example field for this table'

      t.timestamps null: false
    end
  end
end

Good approach. It helps a lot the newcomers . Just let's make sure to keep a Ubiquitous Language,  this way the knowledge about another Geek process can be used to understand the code nuances

Good approach. It helps a lot the newcomers . Just let's make sure to keep a Ubiquitous Language, this way the knowledge about another Geek process can be used to understand the code nuances

I mean... if something is called Customer Ongoing by the CS team, then the table/fields related to it must have the comment mentioning the Customer Onging proccess.

These comments appear in Metabase too

Great proposal!
A securty reminder from PostgreQSL docs:

This is a great idea, we just need to be careful not to make comments that we consider anti-pattern in our code.
For example, this comment is valid since it adds rich info:
t.string :phone_number, comment: 'The phone number including country and area code'

While this one shouldn't be (we can document this in our styleguide), since it's obvious:
t.string :name, comment: 'The name'

@renanrcp let's update the styleguide =)


how i create [toc] menu.  showdown-toc can`t  use

i want to create toc menu. #422 showdown-toc requires jQuery, it cant`t use. what should I do。thank

You can make an extension.
Also, if you're willing to wait for version 2.0, creating a TOC will be trivial, sicne showdown will have a proper parser that outputs an abstract node tree that represents the document tree (and you can grab all the headings to create a TOC).

I will create a showdown-toc-meta extension.


💡[Feature]: ADD LSTM Model in [Prediction Models/Anemia Prediction/Anemia_prediction.ipynb]

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Implement an LSTM model to improve anemia prediction by capturing sequential dependencies in pixel and Hb data, and compare its performance with existing models (Logistic Regression, Decision Tree, and Gradient Boosting).
Use Case
Adding the LSTM model will enhance the project by leveraging sequential data patterns, potentially improving prediction accuracy for anemia detection. It will also provide a deeper comparison between traditional machine learning models and deep learning approaches, offering insights into which method is best suited for this dataset.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

please checkout the pin issue


Not working on new chrome ios

Hey, just found this a few days and think it's great and solves a very annoying problem. However it seems to not be working on the newly updated google chrome V69.0.3497.105 for ios

Hi,
Thank you for using this lib and thanks for reporting this issue.
I can effectively reproduce this behavior on chrome V69.0.3497.105 for ios & firefox…
It's ok with Safari, Chrome & Firefox for android…
I'll try to fix that tomorrow

Awesome, I can confirm the same behavior. Thanks for the quick response and turnaround!

@nikse In fact it's working.
In those browsers the vh unit reevaluate on scroll:

so the initial 100vh are matching the visible content
so the lib doesn't see any size difference
so it returns a no-needed

I've

detailed the readme about this.
updated the demo to see better what's going on.

Is this ok for you?

Ah, interesting yeah that explains it. Though, I will say this is still undesirable behavior from the browser. I'm wondering if an event or anything is fired once the address bar is removed/added and the vh could be set to the max of either of those or if you can think of any other alternative for the current ios chrome/firefox behavior

I don't know about such events.
I think it's more a bug than a real feature. They should align with all the other behavior.
Still if you want to override that you should be able to to do something like that:
vhCheck({
  bind: false,
  redefineVh: true,
})

.my-div {
  height: calc(var(--vh, 1vh) * 100)
}

--vh will be defined once at load time and will not reevaluate on scroll

thanks!


Syncing failing for activities without a description as of v0.2.4

The changes made in #18 created a bug where syncing fails if there's no description in the activity at all. Whoops.

Resolved by #20


allow custom error responses to be generated

By defining a new config value that flask_pydantic looks for
(FLASK_PYDANTIC_VALIDATION_ERROR_RAISE), we can support raising an
exception when we have a validation error. If that is set and the
exception is raised, by default, Flask will respond with a 500 error.
However, by coupling that feature with Flask.register_error_handler,
the user can catch the thrown exception and return whatever custom error
response the user wishes. Fixes https://github.com/bauerji/flask-pydantic/issues/45.

@bauerji is there something else you are looking for on this?

Thank you @jcreekmore, released in version 0.11.0


Support for creating vertical slides

Based on Stefan Eike's idea when the DITA Map contains more than one level of topicrefs, the second level topic refs can appear as vertical slides.
A couple questions:

Should we add a parameter to control this behavior?
What happens to third, fourth,.... level topicrefs?

Should we add a parameter to control this behavior?
This makes sense.

What happens to third, fourth,.... level topicrefs?
I prefer to handle them as second level topic. Other ideas?

{quote}I prefer to handle them as second level topic. Other ideas?{quote}
Probably this would be the only possible option, Reveal JS does not seem to handle the case when in a vertical set of slides you create another section containing another vertical set of slides.

To explain the problem roughly:
Reveal awaits is this structure

Single Horizontal Slide

Vertical Slide 1

Vertical Slide 2

But what we usually generate is:

Single Horizontal Slide

Vertical Slide 1

Vertical Slide 2

So, what the transformation does:
If the first level topic has children, inject a closing tag

Single Horizontal Slide

Vertical Slide 1

Vertical Slide 2

If the second level is the first child, inject an opening tag:

Single Horizontal Slide

Vertical Slide 1

Vertical Slide 2

Because you cannot inject either opening or closing tags with XSLT, you have to inject plain text.

I tried to find a solution without injecting tags as plain text, please see pull request.


Facing Issues with starting ViroSample from ViroMedia"Getting Started" page

[x] Review the documentation: https://docs.viromedia.com/
[x] Search for existing issues: https://github.com/viromedia/viro
[x] Use the latest ViroReact release: https://docs.viromedia.com/docs/releases

Environment
Please provide the following information about your environment:

Development OS: Windows
Device OS & Version: IOS 11.4.1
Version: ViroReact version "2.10.0", React Native version "^0.57.0"
Device(s): IPhone 8

Description
Describe your issue in detail. Include screenshots if needed. If this is a regression, let us know.
Hello everyone, sorry if this is a minor issue but I'm facing some issues with the "Getting Started" for ViroReact. I've followed all the steps specified for windows to create the ViroSample but I'm unable to start the project and view it via the Viro Media App on my iPhone. Thank you for your help
The following are the errors I'm facing:
PS E:\ReactNativeProjects\ViroSample> npm start

<EMAIL_ADDRESS>start E:\ReactNativeProjects\ViroSample
node node_modules/react-native/local-cli/cli.js start

┌──────────────────────────────────────────────────────────────────────────────┐
│                                                                              │
│  Running Metro Bundler on port 8081.                                         │
│                                                                              │
│  Keep Metro running while developing on any JS projects. Feel free to        │
│  close this tab and run your own Metro instance if you prefer.               │
│                                                                              │
│  https://github.com/facebook/react-native                                    │
│                                                                              │
└──────────────────────────────────────────────────────────────────────────────┘
Looking for JS files in
E:\ReactNativeProjects\ViroSample
Loading dependency graph, done.
error: bundling failed: Error: Cannot find module '@babel/plugin-external-helpers'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.Module._load (internal/modules/cjs/loader.js:507:25)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:20:18)
at Object. (E:\ReactNativeProjects\ViroSample\node_modules\metro\src\reactNativeTransformer.js:15:31)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Module._compile (E:\ReactNativeProjects\ViroSample\node_modules\pirates\lib\index.js:83:24)
at Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Object.newLoader [as .js] (E:\ReactNativeProjects\ViroSample\node_modules\pirates\lib\index.js:88:7)
BUNDLE  [ios, dev] ./index.js ░░░░░░░░░░░░░░░░ 0.0% (0/1)::ffff:<IP_ADDRESS> - - [20/Sep/2018:07:24:55 +0000] "GET /index.bundle?platform=ios&dev=true HTTP/1.1" 200 - "-" "ViroMediaApp/1 CFNetwork/902.2 Darwin/17.7.0"
BUNDLE  [ios, dev] ./index.js ░░░░░░░░░░░░░░░░ 0.0% (0/3)
The errors I see on my phone:
Failed to load bundle(http://<IP_ADDRESS>:8081/index.bundle?platform=ios&dev=true) with error:(E:\ReactNativeProjects\ViroSample\node_modules\react-native\Libraries\react-native\react-native-implementation.js: Cannot find module '@babel/plugin-external-helpers' (null))
void google::protobuf::internal::arena_delete_objectvr::internal::widgets::video::SphericalMetadata(void*)
RCTCxxBridge.mm:420
void google::protobuf::internal::arena_delete_objectvr::internal::widgets::video::SphericalMetadata(void*)
void google::protobuf::internal::arena_delete_objectvr::internal::widgets::video::SphericalMetadata(void*)
void google::protobuf::internal::arena_delete_objectvr::internal::widgets::video::SphericalMetadata(void*)
void google::protobuf::internal::arena_delete_objectvr::internal::widgets::video::SphericalMetadata(void*)
void google::protobuf::internal::arena_delete_objectvr::internal::widgets::video::SphericalMetadata(void*)

<redacted
<redacted
<redacted
<redacted
<redacted
<redacted
<redacted
<redacted
<redacted
<redacted
<redacted
<redacted
<redacted
<redacted
<redacted

_pthread_wqthread
start_wqthread
Reproducible Demo
Let us know how to reproduce the issue. Include a code sample, screen capture, video recording. The more information you provide, the better we can support you.
I followed the steps exactly from this page:
https://docs.viromedia.com/docs/quick-start-windows

Sorry for the issue, just realised that the react native version of 0.57 is not supported by ViroReact yet


[FAQ] Why should i train 'romp' by myself?

I am missing an notice about the purpose of training romp by myself.
For example: Are there any benefits of usage, if i train it again by myself instead of using the attached dataset?
Would be great to get some guidelines about this question.

I am missing an notice about the purpose of training romp by myself. For example: Are there any benefits of usage, if i train it again by myself instead of using the attached dataset?
Would be great to get some guidelines about this question.

Hi, what do you mean by 'train it again by myself instead of using the attached dataset' ? I think training romp is served for 3 purposes:

To reproduce the results in the paper and to better understand the paper.
Serve as an instructio/hint to re-implement some useful plugins or some of your own work based on romp.
If you mean to train romp on your own dataset instead of the dataset mentioned in the paper. Modifying the existing ones would be a great start.

@ZhengdiYu Please create an PR, if possible :)

@ZhengdiYu Please create an PR, if possible :)

Do you mean that you need a pull request to add he information into README?

@ZhengdiYu Why not? :)

OK I will do that recently, but I have to work for now. Your profile picture is so cute, I like it.

@ZhengdiYu

OK I will do that recently, [..]

ping

Your profile picture is so cute, I like it.

Thank you^^
It was one of my first exercises: https://www.deviantart.com/suk0m8u/art/Renshuu2-818674802


Cluster-autoscaler: timing in scale down fix

cc: @fgrzadkowski @piosz @jszczepkowski

LGTM

Can you please expand PR to actually explain what you're fixing. I'm reading this PR and I don't understand why you're changing it...


[Idea] with blocks instead of defer

Maybe instead of using defer statements we can use with blocks:
struct A{
    a: i32,
}

fn new_a(): A*{
    ...
}

method A::close(){
    ...
}

fn main(){
    with let foo: A* = new_a(){
        ...
    }
}

Which essentially means:
struct A{
    a: i32,
}

fn new_a(): A*{
    ...
}

method A::close(){
    ...
}

fn main(){
    let foo: A* = new_a();
    ...
    foo::close();
}

I've considered this, but I'm not really sure how much I like the proposed idea. The problem for me is really that this forces everything to be indented one level, which I'm not a fan of. So, if I were to open 3 files at once, I would have 3 nested with blocks and code keeps moving to the right.
If you have any ideas on how we can avoid this, maybe there's another variation of this idea we can add.

Instead of doing nested blocks we can do something like this:
with let a = ..., let b = ... {
    ...
}

Instead of doing nested blocks we can do something like this:

Sounds reasonable. I have nothing against this, but I would prefer if we had these alongside defer instead of replacing it.

Okay

We can implement those as syntatic sugar to defer basically. Does defer support multiple defers per block?

We can implement those as syntatic sugar to defer basically. Does defer support multiple defers per block?

Yep, you can have multiple defers in a block.


Can’t build on an airplane

Problem
If an http dependency doesn’t have a tag/commit specified, but it’s already cloned locally, just use the existing repo instead of failing with a network error?
Steps
No response
Possible Solution(s)
No response
Notes
No response
Version
No response

Hi!
Have you tried running with --offline flag?
E.g.
scarb --offline build

or
SCARB_OFFLINE=true scarb build

Currently, scarb tries to fetch the latest available revision of the dependency which will check after introduction of lockfiles tracked by https://github.com/software-mansion/scarb/issues/126


Changed code to compare the trimmed button text to the I10n version of app.save. This makes this feature I10n compatible.

Github Issue (if applicable): #589
Trello Link (if applicable):
Forum Link (if applicable):
https://forum.youneedabudget.com/discussion/52962/pop-up-calculator#latest
Explanation of Bugfix/Feature/Enhancement:
Changed code to compare the trimmed button text to the I10n version of app.save. This makes this feature I10n compatible.
Recommended Release Notes:

Thank you!


CARLA 0.9.7 does not generate a python library on Windows 10

Hi,
Running make PythonAPI claims to complete successfully with following output.
-[BuildPythonAPI]: Carla lib for python has been successfully installed in "C:/path/to/Workspace/Cpp/carla/PythonAPI\carladist"!

At first sight, the mixed usage of path separators looks suspicious. However, even if I ignore the forward slashes (i.e., /) by replacing them with backwards slash (i.e.,), there is no carladist in that path.
As user, I would expect there is an actual output in the highlighted path given with the build output.
Test environment
Windows 10 1909
Visual Studio 2017
Unreal Engine 4.22.3
Python 3.7.4.final.0
GNU Make 4.2.1
cmake version 3.12.18081601-MSVC_2
carla 0.9.7 (b9fbbf7fd03ee2a4f3a7baf4343a28381cfe81ef)

same problem and i have some link error
but finally output successful
-[BuildPythonAPI]: Carla lib for python has been successfully installed in "D:/project/carla/PythonAPI\carladist"
checking and it's nothing generated
lease\source/libcarla\libcarla.cp38-win32.exp
libcarla.obj : error LNK2001: 无法解析的外部符号 __imp_PyBool_FromLong
libboost_python38-vc141-mt-x64-1_69.lib(class.obj) : error LNK2001: 无法解析的外部符号 __imp_PyBool_FromLong
libcarla.obj : error LNK2001: 无法解析的外部符号 __imp_PySlice_Type
libboost_python38-vc141-mt-x64-1_69.lib(function_doc_signature.obj) : error LNK2001: 无法解析的外部符号 __imp_PyErr_Occurred
libboost_python38-vc141-mt-x64-1_69.lib(stl_iterator.obj) : error LNK2001: 无法解析的外部符号 __imp_PyErr_Occurred
libboost_python38-vc141-mt-x64-1_69.lib(enum.obj) : error LNK2001: 无法解析的外部符号 __imp_PyErr_Occurred
libboost_python38-vc141-mt-x64-1_69.lib(pickle_support.obj) : error LNK2001: 无法解析的外部符号 __imp_PyErr_Occurred
libboost_python38-vc141-mt-x64-1_69.lib(str.obj) : error LNK2001: 无法解析的外部符号 __imp_PyErr_Occurred
libcarla.obj : error LNK2001: 无法解析的外部符号 __imp_PyErr_Occurred
libboost_python38-vc141-mt-x64-1_69.lib(builtin_converters.obj) : error LNK2001: 无法解析的外部符号 __imp_PyErr_Occurred
libboost_python38-vc141-mt-x64-1_69.lib(list.obj) : error LNK2001: 无法解析的外部符号 __imp_PyErr_Occurred
libboost_python38-vc141-mt-x64-1_69.lib(function.obj) : error LNK2001: 无法解析的外部符号 __imp_PyErr_Occurred
libcarla.obj : error LNK2001: 无法解析的外部符号 __imp_PyEval_SaveThread
libboost_python38-vc141-mt-x64-1_69.lib(pickle_support.obj) : error LNK2001: 无法解析的外部符号 __imp_PyExc_RuntimeError
libcarla.obj : error LNK2001: 无法解析的外部符号 __imp_PyExc_RuntimeError
libboost_python38-vc141-mt-x64-1_69.lib(errors.obj) : error LNK2001: 无法解析的外部符号 __imp_PyExc_RuntimeError
libboost_python38-vc141-mt-x64-1_69.lib(class.obj) : error LNK2001: 无法解析的外部符号 __imp_PyExc_RuntimeError
libboost_python38-vc141-mt-x64-1_69.lib(function.obj) : error LNK2001: 无法解析的外部符号 __imp_PyExc_RuntimeError
libcarla.obj : error LNK2001: 无法解析的外部符号 __imp_PyLong_FromLong
libboost_python38-vc141-mt-x64-1_69.lib(enum.obj) : error LNK2001: 无法解析的外部符号 __imp_PyLong_FromLong
libboost_python38-vc141-mt-x64-1_69.lib(function_doc_signature.obj) : error LNK2001: 无法解析的外部符号 __imp_PyLong_FromLong

I think that this is a known issue, therefore there are no compiled versions greater than 0.9.5. for Windows.
I'm personally stuck with these errors:
Creating library build\temp.win-amd64-3.6\Release\source/libcarla\libcarla.cp36-win_amd64.lib and object build\temp.win-amd64-3.6\Release\source/libcarla\libcarla.cp36-win_amd64.exp
libpng.lib(pngwrite.obj) : error LNK2001: unresolved external symbol deflate
libpng.lib(pngwutil.obj) : error LNK2001: unresolved external symbol deflate
libpng.lib(pngwrite.obj) : error LNK2001: unresolved external symbol deflateEnd
libpng.lib(png.obj) : error LNK2001: unresolved external symbol inflateReset
libpng.lib(pngrutil.obj) : error LNK2001: unresolved external symbol inflateReset
libpng.lib(png.obj) : error LNK2001: unresolved external symbol crc32
libpng.lib(pngread.obj) : error LNK2001: unresolved external symbol inflate
libpng.lib(pngrutil.obj) : error LNK2001: unresolved external symbol inflate
libpng.lib(pngread.obj) : error LNK2001: unresolved external symbol inflateEnd
libpng.lib(pngread.obj) : error LNK2001: unresolved external symbol inflateInit_
libpng.lib(pngwutil.obj) : error LNK2001: unresolved external symbol deflateReset
libpng.lib(pngwutil.obj) : error LNK2001: unresolved external symbol deflateInit2_
build\lib.win-amd64-3.6\carla\libcarla.cp36-win_amd64.pyd : fatal error LNK1120: 9 unresolved externals
error: command 'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\HostX86\x64\link.exe' failed with exit status 1120
-[BuildPythonAPI]: Carla lib for python has been successfully installed in "D:/carla/PythonAPI\carladist"!

There is a workaround for this problem - run PythonAPI 0.9.7 compiled for linux in WSL

The message is definitely confusing, because the .egg file is saved to carla/PythonAPI/carla/dist. It's a fairly innocuous error in the build python API batch script. Thanks for posting this, I also had issues with PythonAPI building on windows (though I was able to resolve my problems). I will be submitting a PR soon to resolve some problems I discovered while looking into this issue.

I can't say for sure that #2348 will fix all of the issues mentioned by users here but I hope it will help. I encountered many issues when I upgraded an earlier version where I had an installed PythonAPI. In the past I had used make clean but I didn't know that it wasn't working. With the change, make clean should remove any intermediate files messing with your build. make PythonAPI has always worked fine for me. I am using Win10 Pro x64, UE4.22.3, VS2017 w/ Native Tools x64 Prompt, python 3.6, Make for Windows 3.81


Remove unused params in msal-common

Remove unused params in msal-common.
Enable "noUnusedParameters" in tsconfig.json.

Codecov Report

Merging #6122 (91cafe4) into dev (81d34b4) will decrease coverage by 1.66%.
The diff coverage is 96.63%.

Flag
Coverage Δ

msal-angular
96.73% <96.63%> (+0.22%)
:arrow_up:

msal-browser
?

msal-common
83.23% <ø> (-1.31%)
:arrow_down:

msal-core
?

msal-node
79.73% <ø> (-3.66%)
:arrow_down:

msal-node-extensions
?

msal-react
94.24% <ø> (-0.45%)
:arrow_down:

node-token-validation
?

Impacted Files
Coverage Δ

lib/msal-common/src/account/AuthToken.ts
100.00% <ø> (ø)

lib/msal-common/src/account/CcsCredential.ts
100.00% <ø> (ø)

lib/msal-common/src/account/ClientInfo.ts
100.00% <ø> (ø)

lib/msal-common/src/authority/Authority.ts
90.87% <ø> (+2.98%)
:arrow_up:

lib/msal-common/src/authority/AuthorityFactory.ts
100.00% <ø> (+11.11%)
:arrow_up:

lib/msal-common/src/authority/AuthorityMetadata.ts
100.00% <ø> (ø)

lib/msal-common/src/authority/AuthorityOptions.ts
100.00% <ø> (ø)

lib/msal-common/src/authority/AuthorityType.ts
100.00% <ø> (ø)

lib/msal-angular/src/msal.guard.ts
90.78% <90.78%> (+0.64%)
:arrow_up:

lib/msal-angular/src/msal.navigation.client.ts
93.33% <92.85%> (+0.47%)
:arrow_up:

... and 7 more

... and 215 files with indirect coverage changes


Website tell us how  to improve link is borken

Clicking the link in the image returns a 404 error, can this be fixed or removed please

B O R K E N


Part Review feature: Show position + Axis alignment

Similarly to BFC and Harlequin modes, it would be nice to see  how sub models are placed and aligned in the Part Viewer.
Suggested by philo here: https://forums.ldraw.org/thread-23540-page-10.html

Done in latest push to master: See sample_part.htm for how to add axes helper when analyzing a part.


chore: update multi-parser to last version

Description
This PR updates @smoya/multi-parser to last version (4.0.0).

/rtm

@smoya not so fast 😄 tests are failing

@smoya not so fast 😄 tests are failing

Fixed now!

/rtm


Rust binding for Tensorflow Lite

Is there any kind of plan to create Tensorflow Lite bindings for Rust? It would be convenient for projects that only need the model execution layer, without having to import the rest of the project.

Here's What I have got from the documentation of tflite, TensorFlow Lite bindings for the Rust programming language have not been officially released by the TensorFlow team yet. However, there are some third-party libraries that provide TensorFlow Lite bindings for Rust.
But here are some of the third party stuff, if you want to try:

the Tensorflow Rust crate is a set of Rust language bindings for TensorFlow. It provides a high-level API for loading and running TensorFlow models, as well as a lower-level API for building custom TensorFlow ops using Rust code.

Another example is tflite-rust is a rust wrapper for TensorFlow Lite C API, which is developed by the community.

Hi @DURGESH716!
About the status of the third party libraries, I have to mention that they are not following a development speed to be used in production. Being some of these libraries abandoned in time.
Regarding the issue of using some constructions with TensorFlow Custom Ops, yes, it could be considered, but would it be a serious and competitive solution against Tensorflow Lite? It would be necessary to get some comparative metrics for it.
The reason for opening this issue is more to follow up this feature on the TensorFlow Lite library and to show the interest of the community to develop it.

@mohantym
could you please look at this issue?

Hi @Neirth,
Thanks for raising this issue. Are you aware of the migration to LiteRT? This transition is aimed at enhancing our project's capabilities and providing improved support and focus for our users. As we believe this issue is still relevant to LiteRT we are moving your issue there. Please follow progress here.
Let us know if you have any questions. Thanks.


Printing results

Can you please provide a hook for how to print repl results? Pretty-printing is by default defined for most standard library types,  as well as case classes and case objects. For other types not supported, it falls back to using toString says the doc. That's all undesirable for me.
I've gone to great lengths not to let toString infect everything in my library.  But Ammonite doesn't have to be as hostile to decent printing. I have a method like
object psp { def show[A: Show](x: A): String = implicitly[Show[A]] show x }

If there were some way to get the ammonite repl to use it on all results it would be hugely helpful.

You provide an implicit PPrinter[T] to tell it how to pprint something, and it should do it (modulo bugs). PPrinter[T] is separate from PPrint[T] to try and make the contravariant typeclasses work (seems to...)
This is describe too-briefly in http://lihaoyi.github.io/Ammonite/#Ammonite-PPrint. Could definitely use more prose.

I haven't been able to make it work for long enough to try much out.
@ implicit def implicitPPrint[A](implicit z: Show[A]): PPrint[A] = null
Compilation Failed
Main.scala:69: '}' expected but identifier found.
  +:$,
    ^
@

I guess I'm skeptical that, assuming other things worked, that if I had an implicit Show[String] which always prints "bippy" and I gave the literal String "foo" then I would see res0: bippy. But that's what I am after.

(Make the above PPrinter, obviously not going to save the day.)

Same error as https://github.com/lihaoyi/Ammonite/issues/36, possibly just fixed by @lihaoyi

I'm running against 47a361eee6, so guessing not fixed.

yeah imports are borked and being tracked here https://github.com/lihaoyi/Ammonite/issues/36.
Hopefully after playing whack-a-mole and adding a few more unit tests for all these failing cases it should be in reasonable shape.

Oh, when you say just you really mean "just".

A few minutes ago, yeah :-)

note that not all tests pass yet, but it should put it in a slightly better state. I'll come back and make it better after I'm done writing puppet scripts for $$$ at work

Update: it's not fixed :-|

By the way, if you want to improve on the scala repl this is the hard way to do it. Trying to elicit expected behavior wrt implicits and user-given imports in a repl setting via a rat's nest of generated strings is never going to work right. You have to manage the namespace directly.

@paulp I don't understand. I am managing the namespace directly, and have a Map[String, ImportData] of where the various things I'm importing come from. Do you think I should dive deeper into the compiler internals and munge the data-structures myself?

@lihaoyi Yes, that's what I mean. Here are some excerpts from mine.
class Analyzer(val global: outer.type) extends typechecker.Analyzer {
  def filteredRootContext(unit: ScalpelUnit, tree: Tree = EmptyTree): Context = rootContext(unit, tree)
  override def newNamer(context: Context): ScalpelNamer = new ScalpelNamer(context)
  override def newTyper(context: Context): ScalpelTyper = new ScalpelTyper(context)

  class ScalpelTyper(context: Context) extends Typer(context) {
    override def typed1(tree: Tree, mode: Mode, pt: Type): Tree = {
      super.typed1(tree, mode, pt)
    }
    override def typed(tree: Tree, mode: Mode, pt: Type): Tree = {
      strace(s"typed($tree, $mode, $pt)")

      tree match {
        case Ident(name) =>
        strace(s"typed($tree, $mode, $pt)")
        bindings get name.swap foreach { fullType =>
          val ref = atPos(tree.pos)(fullType.fullNameSelection)
          strace(s"Inserting $ref for $name")
          return super.typed(ref, mode, pt)
        }
        case _           =>
      }
      super.typed(tree, mode, pt)
    }
  }
  override def findMacroClassLoader(): ClassLoader = new AbstractFileClassLoader(outdir, super.findMacroClassLoader)
}

trait Bindings[K, V] {
  def prev: Bindings[K, V]       // the bindings which preceded these - collisions are shadowed
  def defined: Set[K]            // keys defined directly in this instance
  def imported: Set[K]           // keys directly imported by this instance
  def apply(key: K): V           // if defined or imported in this instance, the value, otherwise consult prev
  def keys: Set[K]               // directly defined/imported keys plus all keys of prev
  def contains(key: K): Boolean  // if the key is defined/imported here or in prev
}

trait FullTypes {
  val global: Global

  import global._, definitions._
  private[this] var currentBindings: ReBindings = NoBindings
  def isBound(name: nm.Name)                        = bindings contains name
  def lookup(name: nm.Name)                         = bindings(name)
  def bindings                                      = currentBindings
  def applyBindings(f: ReBindings => ReBindings)    = currentBindings = f(currentBindings)
  def retainBindings(p: nm.Name => Boolean): Unit   = currentBindings = currentBindings filterKeys p
  def addBindings(bs: ReMap): Unit                  = currentBindings = currentBindings ++ bs
  def setBindings(bs: ReBindings): Unit             = currentBindings = bs
  def importAllFrom(name: String): Unit             = wrap(importAllFrom(staticTerm(name)))
  def importAllFrom(tpe: FullType): Unit            = addBindings(tpe.membersMap)
  def bindOne(name: nm.Name, value: FullType): Unit = addBindings(Map(name -> value))

  type ReBindings = Bindings[nm.Name, FullType]
  type ReMap      = Map[nm.Name, FullType]
  def NoBindings: ReBindings = Bindings.empty

  ...
}

What it all leads to is taking the parse tree and attaching symbols to identifiers directly, based on the bindings you are tracking yourself. Then you hand that tree off to typer to let it go the rest of the way.

@paulp Seems plausible. I don't know how well it'd actually work in practice: it seems pretty complicated, but stitching strings is starting to get complicated too. Likely I will keep this stuff in mind as I keep playing whack-a-mole with the string splicer, and if the string splicing gets too annoying then I'll try your approach

This works now
@ class C
defined class C
@ implicit def pprint = ammonite.pprint.PPrinter[C]((t, c) => Iterator("INSTANCE OF CLASS C"))
defined function pprint
@ new C
res2: cmd0.C = INSTANCE OF CLASS C

https://github.com/lihaoyi/Ammonite/blob/master/repl/src/test/scala/ammonite/repl/AdvancedTests.scala#L171-L182

Yes, it is pretty complicated, because the compiler is nothing but complicated. You haven't gotten to the real complications in in string land yet. Do you know why the repl creates all those nested objects? Do you intend to duplicate that approach?

I know why the REPL creates nested objects, and I think I can avoid doing that. The main distinction is that I expand out imports into their individual names and the nsc.interpreter doesn't. Thus I can avoid relying on the depth of an import to impose ordering, and can emulate import-shadowing manually by adding and removing imports at the correct time.
It's not 100% accurate yet (e.g. it doesn't distinguish the type namespace from the term namespace) but it's pretty darn close. If you can elaborate on what test cases w.r.t. implicits would fail, we may be able to fix them, or we may decide that some of the semantics are just broken (e.g. Scala's ambiguous-import errors) and document/wontfix them rather than trying to emulate.

 You will never make it work well this way. I won't need to elaborate because you will discover it for yourself.

I await my enlightenment then ^_^


Add w3schools effective go tutorial

What does this PR do?
Add resource
For resources
Description
w3schools effective go tutorial
Why is this valuable (or not)?
effective go tutorial. Have followed this personally.
How do we know it's really free?
Have used it personally.
For book lists, is it a book? For course lists, is it a course? etc.
It's a tutorial in website.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

listing is already in interactive tutorials.


Add drop-down to select custom auto-mark color

Add to @FNF
EDEN Editor setup that will allow the selection of a custom color to mark a certain object

maybe in the future but not needed at current


Coinbase Pro passphrase regex fix

Description
The passphrase regex in api.py should be the same as in coinbase_pro_parser.py
Type of change
Please make your selection.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] This change requires a new dependency
[ ] Code Maintainability / comments
[ ] Code Refactoring / future-proofing

How Has This Been Tested?
The regex has been tested (and is the same as in coinbase_pro_parser.py)
Checklist:

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

Changed the PR target to "beta" for testing. This will be included in the next release.


Maximum limit of 254 Wireguard clients

I have configured a PiVPN server with Wireguard. The network range I use is pivpnNET=<IP_ADDRESS> and subnetClass=22.
I have reached the client with IP <IP_ADDRESS>. From this point on I can't create any more clients. I have been looking at the makeCONF.sh script and I have seen that it checks the last octet of the clients file.
Is there any way I can continue using clients using the network <IP_ADDRESS>? If I change the network in setupVars.conf I understand that I will still get the same thing, since it checks only the last octet of that file.

Yeah this is something that should be changed. In the meanwhile you can edit /etc/wireguard/wg0.conf

And what do I get by editing that? The script to generate new users will still not work.

You are right, actually. Are you asking for a feature to change the subnet to a bigger one, or use a bigger subnet for everyone?

Currently my network is as follows:
Network: <IP_ADDRESS>/22
HostMin:	<IP_ADDRESS>
HostMax:	<IP_ADDRESS>
Broadcast: <IP_ADDRESS>
Hosts/Net: 1022
The script started assigning IPs for clients from <IP_ADDRESS> to <IP_ADDRESS>. The script should still be able to assign IPs, the next one would be the <IP_ADDRESS>

Have you found a solution? Tell me what you can do.

Pre-archive closing, more information here


⚠ Bofrost.fr has degraded performance

In 7fdcc84, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1559 ms

Resolved: Bofrost.fr performance has improved in 003c0a3 after 18 minutes.


Hard-coded 2 pixel border in GTK gVim

The current GTK gVim has hard-coded 2 pixel border around main window content:

The border value is hard-coded here.
Settings gui.border_width to 0
gui.border_width = 0;

and rebuilding gVim completely eliminates the unnecessary border.
Ideally the border width value should be configurable, but at very least it should be set to 0 (like in Windows version of gVim, for example).

Ideally the border width value should be configurable, but at very least it should be set to 0 (like in Windows version of gVim, for example).

(With the understanding that I don't know about Windows at all) Adding a small number of pixels to borders has been done customarily in GUI for UNIX-like systems for a long time to make the border visible or noticeable even if the given physical display is incapable in color.  I don't think setting gui.border_width to 0 is a decent UI design, considering such an important role border widths have long played..

@nuko8, I'm not sure I fully understand your argument.
Window border is something window manager should be dealing with, not the application itself.
If user decides to have no borders on a display incapable of colors - it is his/her choice, and applications shouldn't make any assumptions there.
Otherwise it will be a mess: Vim decides to have border of 2px, some other application decides to make its border 3px etc.
Even if there's a legitimate use case where having inner border could improve user experience on certain combinations of displays and WM, how common is this case?
I'd guess - not common at all. So why is the choice was made towards marginally improving UX in an uncommon case, while disrupting UI layout and breaking consistency for common cases?
Just for comparison, below is a screenshot from Windows gVim:

As you can see, the content fully occupies window and fits nicely without any unexpected padding and without wasting any pixels.
Ultimately, having inner border or not (as well as what width it should be) is a user's choice, that may depend on personal preference, window manager, display DPI etc.
Which is why I suggest that it should be configurable in gVim.
But if making it configurable is too difficult to implement, then I strongly believe that choice should be made towards consistency and most common use case, i.e. no forced padding that disrupts layout.

In my maximized gvim (on a 1280x1024px 16777216-color display, minus the window manager's toolbars at top, right and bottom edges) I hardly notice the 2px margin, I have to look very closely to see it. Could be because 2px on this monitor seems to be something like 0.5 mm (by eyeball estimate, no ruler). YMMV of course.
But the fact that it is there when I look for it tells me that gvim is not overshooting the monitor edges. :stuck_out_tongue:
Best regards,
Tony.

On Mon, Oct 29, 2018 at 11:10 PM ovk<EMAIL_ADDRESS>wrote:

@nuko8 https://github.com/nuko8, I'm not sure I fully understand your
argument.
Window border is something window manager should be dealing with, not the
application itself.

No.  It's an attribute of windows (as X resource).  See XCreateWindow(1)
and XCreateSimpleWindow(1).

If user decides to have no borders on a display incapable of colors - it
is his/her choice, and applications shouldn't make any assumptions there.

Seems like you are confusing the border width of each window with the one
added to application's largest window by the window manager.

Otherwise it will be a mess: Vim decides to have border of 2px, some other
application decides to make its border 3px etc.

Hmm, but it's you who is claiming that border widths should be configurable
so that they can have a value other than 2px.  What's wrong with 2px which
has been widely used by terminal emulators?  Sounds like you are saying
your proposal will cause a mess.

Even if there's a legitimate use case where having inner border could
improve user experience on certain combinations of displays and WM, how
common is this case?
I'd guess - not common at all. So why is the choice was made towards
marginally improving UX in an uncommon case, while disrupting UI layout and
breaking consistency for common cases?

Because "applications shouldn't make any assumptions there."  Talking about
"common" case is just making an assumption, isn't that?

Just for comparison, below is a screenshot from Windows gVim:
[image: vimw]
https://user-images.githubusercontent.com/693072/47655003-715d0680-db62-11e8-9587-95fc7b7e824c.png
As you can see, the content fully occupies window and fits nicely without
any unexpected padding and without wasting any pixels.

I already said, "I don't know about Windows."  I should have said that more
clearly: I don't want to comment on what others are doing and want to
follow the well-tested 2px tradition in order to avoid time-consuming,
unproductive re-verification.

Ultimately, having inner border or not (as well as what width it should
be) is a user's choice, that may depend on personal preference, window
manager, display DPI etc.
Which is why I suggest that it should be configurable in gVim.

Once everything being configurable was considered a good thing.  Later,
that was found a factor which made users confused and the resulting bloat
code could be an obstacle to implement new features.  Now, users'
productivity is more emphasized than configurability.

But if making it configurable is too difficult to implement, then I
strongly believe that choice should be made towards consistency and most
common use case, i.e. no forced padding that disrupts layout.

Actually, writing a patch for that is entry level. But let me emphasize
this again: Avoid making any assumption in the name of what is considered
common use cases.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vim/vim/issues/3575#issuecomment-433923653
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>For more options, visit https://groups.google.com/d/optout.

No.  It's an attribute of windows (as X resource).  See XCreateWindow(1) and XCreateSimpleWindow(1).
Seems like you are confusing the border width of each window with the one added to application's largest window by the window manager.

What I mean is that if user wants to have border/gaps - he can do so by relying on WM.
However, in the current situation if the user doesn't want any padding, he can only get rid of it by patching and recompiling gVim.

What's wrong with 2px which has been widely used by terminal emulators?

It's a magic number that adds non-removable visually distracting padding that is inconsistent across different gVim versions.
Why 2px, why not 5 or maybe 42? I feel like this "one size fits all" approach contradicts Vim's incredible customizability.

Sounds like you are saying your proposal will cause a mess.

No. I am saying that if every application developer will decide to go with with arbitrary chosen hard-coded paddings - then it will be a mess.
You can still have 2px as a default (to avoid disruptive upgrade), but having it configurable will give users freedom in having consistent look and feel.

Talking about "common" case is just making an assumption, isn't that?

Well I mentioned that this is my guess, but it is based on the current Linux distro usage statistics.
Besides, hard-coding padding is actually making a very opinionated assumption.

I already said, "I don't know about Windows." I should have said that more clearly: I don't want to comment on what others are doing

Fair enough. I just hope that other Vim developers (assuming you one of them) are more interested in gVim providing consistent UX between platforms.

Now, users' productivity is more emphasized than configurability.

You are generalizing users. The padding actually decreases my productivity because it is visually distracting (especially when switching between platforms).
It also makes gVim window to stand out of other apps (that I use) as none of them have similar paddings.

Windows version had also 2px borders. However they were removed by 7.4.930, because it didn't fit the recent Windows design.

AFAICT the similar 'guiheadroom' option does nothing, even if set on the command-line by gvim --cmd 'set ghr=0' or similar. What about a new 'guisideroom' option defaulting to 2 on Linux and to 0 on Windows for backward compatibility?

To be sure, @tonymec s proposal resolves this particular issue concerning the claimed "inconsistency," but is there anyone who can address another possible inconsistency due to that? : Vim on xterm has the 2px-width border, which can be seen even with that on terminals for macOS, Terminal.app and iTerm2, while that hypothetical Gvim with the proposed guisideroom option can have the 0px-width border.
Personally, I think any UI should follow a UI guideline written specifically for a specific platform or environment, if any, or, well-established, local conventions when such a guideline is unavailable or tells nothing about UI design issues at hand, so that the resulting UI design will give no surprise to people.
  Why should we, however, import that design into UNIX-like systems at the cost of inconsistency between Vim and Gvim on a single platform?

The 2 pixels space is needed to avoid that the text runs into the window border.  I don't think that adding yet-another-option for this is really useful, considering that most users are happy with how it is now.

Why should we, however, import that design into UNIX-like systems at the cost of the consistency between Vim and Gvim on a single platform?

Well, as per @tonymec suggestion there won't be any inconsistency unless user explicitly configures 'guisideroom' in a way that is inconsistent with user's terminal of choice.
Besides, while xterm does have 2px padding by default (which, by the way, is configurable with -b argument; running xterm -b 0 effectively disables padding) - the default Ubuntu terminal (gnome terminal), for example, doesn't have any padding.
P.S. Neovim doesn't suffer from this issue

Yet-another-option for this doesn't seem right IMO, but it should not be hard-coded in gvim.  This should be controlled by the style or theme, like the shape of the scrollbar buttons.  Can we not allow the windowing toolkit to make these decisions?  I may be showing my ignorance of GUI development here.

Hi, Is this still an open problem ?? In that case I suggest you that check your window's config in your distro if you keep using Linux.

@ivantux1, I don't think the issue have been addressed. I don't use Vim any more (switched to Neovim), but looking at the commit history for the gui_gtk_x11.c file I don't see anything that would've removed that arbitrary hardcoded border. I also just compiled Vim from the source and I indeed can see the 2px margin/border. In fact, you have it on your screenshot, it just doesn't look immediately apparent because all of your background is white.
Besides, the general hostility of the comments in this thread made me believe the border is here to stay.

Oooh, I understand the issue better, infact You did wanted to reduce to a absolute zero this margin, but If you really don't care anymore you may close this issue (for example, if I use Vim, I prefer use it in terminal absolutely) I don't feel uncomfortable graphically talking, and I hope don't be a rude person, I think is better collaborate cordially for experts and no-experts as me.

I think it's it up to Vim developers/contributors whether to close this issue or not.

I see, well, thank you

Let's close it for now. If GTK allows this to be configurable using some toolkit switch, a PR would be appreciated. For now, just leave gui.border_width = 2 as is.

I know the reporter explicitly states GTK, but since this has been closed, for those unaware: If you use Athena instead (probably also works with Motif), you can put
Vim.borderWidth: 0

in your ~/.Xresources file. Then merge the changes with xrdb ~/.Xresources and voila, margins no more.
Bear in mind that in Athena and Motif only bitmap fonts are allowed.


[SPARK-32719][PYTHON] Add Flake8 check missing imports

https://issues.apache.org/jira/browse/SPARK-32719

What changes were proposed in this pull request?

Add a check to detect missing imports. This makes sure that if we use a specific class, it should be explicitly imported (not using a wildcard).
Why are the changes needed?

To make sure that the quality of the Python code is up to standard.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing unit-tests and Flake8 static analysis

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Jenkins, add to whitelist.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/32591/
Test PASSed.

Test build #127966 has started for PR 29563 at commit bcdf4ea.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/32592/
Test PASSed.

Test build #127966 has finished for PR 29563 at commit bcdf4ea.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127966/
Test PASSed.

Test build #127993 has started for PR 29563 at commit f039f68.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/32619/
Test PASSed.

Test build #127993 has finished for PR 29563 at commit f039f68.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127993/
Test PASSed.

Test build #128021 has started for PR 29563 at commit 06480a7.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/32648/
Test PASSed.

Test build #128021 has finished for PR 29563 at commit 06480a7.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class PlanChangeLogger[TreeType <: TreeNode[_]] extends Logging
class AQEOptimizer(conf: SQLConf) extends RuleExecutor[LogicalPlan]

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128021/
Test PASSed.

Merged to master.

BTW, this is nice. Thanks for working on this!


Example at https://hono.dev/helpers/websocket#websocket-helper doesn't work with deno.

What version of Hono are you using?
2.0.2
What runtime/platform is your app running on?
Deno
What steps can reproduce the bug?
Just run the example code:
import { Hono } from<EMAIL_ADDRESS>import { upgradeWebSocket } from<EMAIL_ADDRESS>
const app = new Hono();

app.get(
  "/ws",
  upgradeWebSocket((c) => {
    return {
      onMessage(event, ws) {
        console.log(`Message from client: ${event.data}`);
        ws.send("Hello from server!");
      },
      onClose: () => {
        console.log("Connection closed");
      },
    };
  }),
);

Deno.serve(app.fetch);

And try to connect it in a browser console.
const socket = new WebSocket('ws://localhost:8000/')
What is the expected behavior?
I expect the client to connect to the server.
What do you see instead?
I get a ts error like this:
No overload matches this call.
  The last overload gave the following error.
    Argument of type 'string' is not assignable to parameter of type 'Handler<string, Env>'.

and when I try to connect to it I get a runtime error like this.
TypeError: Cannot read properties of undefined (reading 'Symbol(request)')
    at toInnerRequest (ext:deno_fetch/23_request.js:560:17)
    at Object.upgradeWebSocket (ext:deno_http/01_http.js:410:17)
    at https://deno.land/x/hono@v4.1.4/adapter/deno/websocket.ts:7:37
    at dispatch (https://deno.land/x/hono@v2.0.2/compose.ts:28:30)
    at https://deno.land/x/hono@v2.0.2/compose.ts:12:12
    at Hono.dispatch (https://deno.land/x/hono@v2.0.2/hono.ts:182:23)
    at fetch (https://deno.land/x/hono@v2.0.2/hono.ts:203:17)
    at ext:deno_http/00_serve.js:455:24
    at ext:deno_http/00_serve.js:689:29
    at eventLoopTick (ext:core/01_core.js:169:7)

Additional information
OS: Windows 11
Deno version:

deno 1.41.3 (release, x86_64-pc-windows-msvc)
v8 <IP_ADDRESS>
typescript 5.3.3

Hi @unworthyEnzyme
@nakasyou, Could you take a look at this issue?

Hi @unworthyEnzyme, thank you for writing Issue.
I couldn't reenactment this errors, I got an onerror on Browser. But I have an idea to resolve.
You tried this code:
const socket = new WebSocket('ws://localhost:8000/')

I think you may resolve it if you write code like this:
const socket = new WebSocket('ws://localhost:8000/ws')

Because route of WebSocket is /ws. onerror error is removed if I change my code.

Oh, I found the cause that seems to be. You use Hono v2.0.2.
WebSocket helper on Deno uses c.req.raw API, but v2.0.2 doesn't have c.req.raw API because c.req.raw has implemented since v3.
If we would like to resolve it, we should support v2 or write "WebSocket helper doesn't support Hono before v3" to docs.
Using different version same package is difficult when we use most package managers such as Bun and npm.
But when we use Deno, it is easy.

Hi @nakasyou.
Oh wow, I didn't realize v4.1.4 was out. When I click the vscode Update specifier to it's redirected specifier., it rewrites the version as 2.0.2. It doesn't do the same with the upgradeWebSocket import which is weird. I didn't even noticed the versions of the two imports was different. I wonder why this is the case.
For the solution I think adding a notice to the docs is sufficient since it is quite an old version.

Hi @unworthyEnzyme, thank you for your opinion.
Now, the docs includes warnings!
https://hono.dev/guides/middleware#built-in-middleware

A similar problem occurrs when using deno together with the SSE middleware.
The warning in https://hono.dev/docs/guides/middleware#built-in-middleware isn't very clear what to do in such a case. Is this considered a seperate bug?


Add image filename columns to CellProfiler presets

Description
This PR adds image table FileName columns to CellProfiler presets within CytoTable. Along the journey towards this work I found there was an unused fixture which also had a warning associated with it so I removed this.
Closes #251
References wayscience/cytodataframe#22
What is the nature of your change?

[ ] Bug fix (fixes an issue).
[x] Enhancement (adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] This change requires a documentation update.

Checklist
Please ensure that all boxes are checked before indicating that a pull request is ready for review.

[x] I have read the CONTRIBUTING.md guidelines.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] New and existing unit tests pass locally with my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have deleted all non-relevant text in this pull request template.

Thanks @gwaybio ! Merging this in.


Resources dropdown empty icon

There's a box within the Resources dropdown Documentation text that I think is meant to be the external link icon:

I tried this in Chrome Version 111.0.5563.147 and Edge Version 112.0.1722.39, but I do not see it in Firefox


Why the chinese in the editor is so ugly?

Vertion: latest release 1.13
Problem: Why the chinese in the editor is so ugly?

@Hapoa Sorry for the inconvenience. Could you mention the OS, on which you are seeing this issue?

@nethip Windows 10. (Actually, I encountered the problem last year in the old release version.)


feat(gql): add search resolver for pano

Implement a full text search solution for pano using https://www.prisma.io/docs/concepts/components/prisma-client/full-text-search#mysql
The query we want to implement:
query PanoSearch($searchQuery: String!) {
  pano {
    search(input: { query: $searchQuery }) {
      edges { cursor, node { id, title }}
      pageInfo { hasNextPage }
    }
  }
}

Types for that query:
# this is already defined in schema.graphql
query PanoQuery {
  # ... other queries
  # this depends on https://github.com/kamp-us/monorepo/pull/440 for SozlukTermConnection type
  # so we can create PanoPostConnection based on that
  search(input: PanoSearchInput): PanoPostConnection
}

input PanoSeachInput {
  query: String!
}

We will need to create a loader for this resolver, and use prisma for search over there.
Depends on #479

Duplicate of #657


404 on npm registry

Description
I have a 404 error when I want to pull the library from npm or yarn
Error log / Screenshot

This package is not currently available on the NPM registry.
You need to configure & use the Github registry or use direct git url in your package.json :
// package.json
...
"dependencies": {
"@lemonde/react-native-at-internet": "lemonde/react-native-at-internet#master",
}
....

And then npm update @lemonde/react-native-at-internet


Better documentation

The README.md is nice, but reading through it can be a bit cumbersome. Cabinet would be better served by a documentation website. #10 was the first step towards realizing this. Now we need to create and build the documentation.

#13 closes this for now...


cross references in multiple latexfiles

(This is my first attempt at any sort of pull request on github - let me know if there is more information needed)
I am building a Software Requirements Specification and Software Test Report in separate PDFs with the following in my conf.py:
latex_documents = [
  ('software_requirements_specification', 'SRS.tex', 'Software Requirements Specification',
   'myname', 'manual'),
  ('software_test_report', 'STR.tex', 'Software Test Report',
   'myname', 'manual')]

When rendering the individual .tex files, cross references from needs listed in STR.tex cannot be placed to their origin back in SRS.tex -- leading to a "Fatal - doctree not resolved" type of error.
With these changes, the following directives in the software_test_report.rst`  work as expected.  Namely, they create a list/table/link back to the need specified in the software_requirement_specification.  When rendering as an html, the list/table/link cross references work correctly.  When rending as latex, the list/table/link render as plain text (without the fatal error).

.. needtable::
   style: table

.. needlist::

see :need:`REQ_000`

Why are you closing this PR?
Got your problem solved?
BTW: Your first PR looked really promising  👍

Thank you for the encouragement!
This was a premature pull request. I found a few more use cases where a more general fix worked better.   I work on an off-network system, so I will eventually propose another pull request but its an awkward workflow for me...


Feature/title label default

Description
Fixes no title displaying on books that don't have a book cover image.
Trello card: https://trello.com/c/trrzdLO4/88-ui-tweaks
Type of change

[x] New feature (non-breaking change which adds functionality)

Change Status

[x] Complete, tested, ready to review and merge

How Has This Been Tested?

[x] Manually tested with simulator (iPhone 8)

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] There are no merge conflicts

 UI Tweaks


Make content-length header optional

We should still create SXG response for payloads missing content-length header.

LGTM, but requesting a small change to avoid using bail macro.

Thanks. I pushed new changes.


Undefined symbols for architecture x86_64

I am using the cocoapods objective c version in my project and linking gives me hundreds of errors. Such as:
Undefined symbols for architecture x86_64:
"realm::BpTreeBase::write_subtree(realm::Array const&, unsigned long, unsigned long, unsigned long, realm::BpTreeBase::SliceHandler&, realm::_impl::OutputStream&)", referenced from:
realm::BpTree<long long, false>::write(unsigned long, unsigned long, unsigned long, realm::_impl::OutputStream&) const in libRealm.a(RLMResults.o)
realm::BpTree<long long, false>::write(unsigned long, unsigned long, unsigned long, realm::_impl::OutputStream&) const in librealm.a(RLMResults.o)
realm::BpTree<long long, false>::write(unsigned long, unsigned long, unsigned long, realm::_impl::OutputStream&) const in libRealm.a(object_store.o)
osx 10.10, every other pod seems to work fine though. Any idea what linker option is missing? Thanks!

@ifeherva this can sometimes happen when downloading Realm has failed. Can you try running the following for me, and installing again? Thanks!
rm -rf ~/Library/Caches/CocoaPods
rm -rf Pods
pod install

I tried again on another computer where cocoapods were not even installed. The project is very simple, yet I get the same error.

How did you install Realm on the non-CocoaPods machine?

I mean everything was freshly installed so there was no need to wipe the cache from ~/Library. Even though I tried again and same result.

But did you also delete the Pods directory?

I'm getting the same error, I was just creating sample project to make a test on Realm for 10.10.
The project is just empty, just did a pod install. Also tried to remove everything link to cocoa pods and reinstall it.
Moreover, I'm already using in another project Realm with CocoaPods which is working well.
Podfile very simple:
source 'https://github.com/CocoaPods/Specs.git'
workspace './RealmTest.xcworkspace'
xcodeproj './RealmTest.xcodeproj'
inhibit_all_warnings!

platform :osx, '10.10'
pod 'Realm'

I can send the sample project if that can hep.

@tbaranes yes, a sample project that demonstrates the issue would be very helpful!

Just sent at<EMAIL_ADDRESS>Hope it helps

OK, figured this out. The issue is that the CocoaPods static library is named Realm, and Realm is also linking against a static library called realm -- thanks to running on case-insensitive file systems, there's no way to link them both. The immediate fix for you (if possible) is to add the use_frameworks! flag to the Podfile, and I'll pull together a PR here with a less hacky fix.

I'm getting again this error on OSX using CocoaPods, but this time using RealmSwift. Any issues about it?

@ifeherva this can sometimes happen when downloading Realm has failed. Can you try running the following for me, and installing again? Thanks!
rm -rf ~/Library/Caches/CocoaPods
rm -rf Pods
pod install

@ifeherva this can sometimes happen when downloading Realm has failed. Can you try running the following for me, and installing again? Thanks!
rm -rf ~/Library/Caches/CocoaPods
rm -rf Pods
pod install

saved my day :)

@ifeherva this can sometimes happen when downloading Realm has failed. Can you try running the following for me, and installing again? Thanks!
rm -rf ~/Library/Caches/CocoaPods
rm -rf Pods
pod install

saved my day :)

@ifeherva this can sometimes happen when downloading Realm has failed. Can you try running the following for me, and installing again? Thanks!
rm -rf ~/Library/Caches/CocoaPods
rm -rf Pods
pod install

saved my day :)

save my day :)

@ifeherva this can sometimes happen when downloading Realm has failed. Can you try running the following for me, and installing again? Thanks!
rm -rf ~/Library/Caches/CocoaPods
rm -rf Pods
pod install

saved my day! thank you very much, mate!


When installing Keptn, allow the user to specify a pre-defined domain or a wildcard DNS resolver, and add a warning

While it is already possible to specify a domain, e.g., keptn install ... --domain=my-server.some-company.net, it is currently not possible to pre-select a DNS wildcard resolver, such as nip.io or xip.io.
From a security and legal standpoint, end-users might not want to use nip.io and xip.io per default (which we currently do in Keptn), therefore specifying a custom domain upfront is good.
However, should customers still want to use nip.io/xip.io, we need to provide a warning (to be defined):

Warning: Using a DNS wildcard resolver is only recommended for demos and workshop-settings, definately NOT for production setups. By continuing you are using the selected service at your own risk. Find out more on https://keptn.sh/docs/wildcard-dns-resolver/.

Definition of Done

[ ] Page on keptn.sh/docs that provides more information about wildcard DNS resolvers and the risks behind them (IP spoofing, data is being sent to a third party which is GDPR relevant, ...)
[ ] If the --domain flag is not specified during installation, keptn install actively queries the user to provide a domain (DEFAULT), or to select a Wildcard DNS Resolver (pre-defined ones will be xip.io, nip.io, as well as "specify your own wildcard dns resolver"). Selecting a Wildcard DNS Resolver must print a warning message.
[ ] If the --domain option contains a wildcard dns resolver, the CLI needs to print a warning.
[ ] keptn configure domain provides the same mechanism as keptn install for specifying a domain
[ ] The Keptn installer image prints a warning in the logs if usage of a wildcard dns resolver (e.g., nip.io, xip.io) is detected.
[ ] Keptn Bridge provides a warning in the UI which can be dismissed if usage of a wildcard dns resolver (e.g., nip.io, xip.io) is detected.

Related to #1708

This might be obsolete with KEP 18.

With the implementation of KEP 18 and especially with my PR https://github.com/keptn/keptn/pull/2022, the user now has full control of using any domain or wilcard DNS resolver, etc. Therefore, I am closing this issue.


Add Sparkline Chart Directive

Adding directive for sparkline charts. Includes unit tests and ng-docs.

Dave, fixed your comments as well.

I will squash the commits when you agree the issues are all resolved

I will squash the commits when you agree the issues are all resolved

I'm good with your last push.


Crash when opening the app after using the proxy（problem with version 0.4.5 bug）

AndroidRuntime: FATAL EXCEPTION: OkHttp Dispatcher
kotlin.UninitializedPropertyAccessException: lateinit property abManager has not been initialized
at com.paypal.pyplcheckout.services.callbacks.BaseCallback.retryOnError(BaseCallback.kt:78)
at com.paypal.pyplcheckout.services.callbacks.BaseCallback.onFailure(BaseCallback.kt:40)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:525)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)

Hey @androidGithubRookie - This looks like a duplicate issue of https://github.com/paypal/android-checkout-sdk/issues/53. I'm going to close this out, but please follow the other issue that was created.


chore: update CODEOWNERS

@teppeis Could you review this?

Codecov Report

Merging #966 (732aded) into master (51ae07b) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##           master     #966   +/-   ##
=======================================
  Coverage   61.18%   61.18%
=======================================
  Files          27       27
  Lines        2785     2785
  Branches      200      200
=======================================
  Hits         1704     1704
  Misses       1081     1081

@koba04 thanks for


Bad results on the detectron2 example

Hello,
I have tired your detectron2 example on my video and i got very bad results, tracking is lost when even a minor occlusion happens, tried different detectron2 models but the results were consistently bad.
any parameters to optimize?

Hello sadimoodi! I don't know what may be causing your specific problem, but take into account that the distance function used in the detectron2 demo doesn't take into account the size of the objects or the resolution of your video, since it is just the unscaled distance between the centers. If your video has really high resolution, then the distance between objects can be large even for objects that appear to be close in the video. You can try re scaling the distance_function to take into account you video resolution and change the distance_threshold accordingly, or using a completely different distance_function.
If you think that your objects are getting deleted too fast, you can increase the hit_counter_max parameter so that the objects live longer without detections.
On another note, I do not know the quality of your detections. In case you do not have consistent detections (for example, if you are missing detections during really minor occlusions), try lowering the detection threshold of your detector and try lowering the detection_threshold argument you are currently using in the tracker (if you are using any non None value).
If you want to share your video with us so we can see it, it might be helpful in order to give you better advices.

@aguscas  How do you take into account the size of the objects or the resolution of the video in the distance function? is it just dividing the norm by the video resolution?  What would be the best strategy to incorporate this into the distance function and tracker?

account the size of the objects or the resolution of your video, since it is just the unscaled distance between the centers. If your video has really high resolution, then the distance between objects can be large even for objects that appear to be close in the video. You can try re scaling the distance_function to take into account you video resolution and change the distance_threshold accordingly


express.static - add support for cache-control: immutable

On static content with versioned URLs, add a flag to options on express.static that generates a cache-control header with immutable, e.g.:
Cache-Control: max-age=365000000, immutable
This reduces unnecessary requests in supporting clients.
This is supported by Firefox 49 and used by Facebook:
https://hacks.mozilla.org/2017/01/using-immutable-caching-to-speed-up-the-web/
https://bitsup.blogspot.co.uk/2016/05/cache-control-immutable.html
Supported in Chrome 54
https://bugs.chromium.org/p/chromium/issues/detail?id=611416
Webkit support seems to be added:
https://bugs.webkit.org/show_bug.cgi?id=167497

Sounds reasonable :) One point missed above is that Chrome does not support this, as you can read through in that Chromium issue (they implement something similar to cache-control: immutable using heuristics instead of looking at a header value at all).
Thinking how we could easily add this to our API, what about having it where if you set maxAge: Infinity it would add the immutable tag in addition to the 1 year age it does today?

Ok, I confess I didn't read all the comments.   The maxAge: Infinity suggestion sounds good.

This landed in the upstream send dependency, so will be part of the Express.js 4.16 release.


IE9 support

I understand that websockets are not supported in IE9, but is there a way to make ddp.js work on IE9?
I'm getting the error WebSocket is undefined. How does Meteor work on IE9 if websockets are unsupported?

Definitely! You just need sockjs-client:
const DDP = require("ddp.js");
const options = {
    endpoint: "http://localhost:3000/sockjs",
    SocketConstructor: SockJS
};
const ddp = new DDP(options);

Let me know.

Great!
Slightly more verbosely (and es6) just in case anyone else has this issue.
npm install -s sockjs-client
import DDP from "ddp.js";
import SockJS from 'sockjs-client'

const options = {
   endpoint: "http://localhost:3000/sockjs",
   SocketConstructor: SockJS
};
const ddp = new DDP(options);

Thanks a ton!


More verbose logging

Need to have more logging. In general, an exception should be handled and result in a descriptive stack trace dumped to the log file / console.

As of v1.0.1, the log output is much more descriptive. For example, invalid API keys and BaseURI values in the config file will yield detailed error messages stating exactly what to correct.


Appstudio update test-component-private-twnz

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-private-twnz-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
7 seconds
sast-snyk-check

✅ Succeeded
25 seconds
build-container

✅ Succeeded
12 seconds
clair-scan

✅ Succeeded
11 seconds
inspect-image

✅ Succeeded
15 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
5 seconds
show-summary

✅ Succeeded
6 seconds
show-sbom


WIP: feat(builder): add output.vendorEntry

PR Details

Original implemented in #1679
See https://github.com/modern-js-dev/modern.js/pull/1679#discussion_r966557589 for discussions before
Description

Related Issue

Motivation and Context

How Has This Been Tested

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project.
[ ] I have updated changeset
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This PR will be closed because it is outdated 😄


eglInitialize failed

Hello! I followed the guidance you provided in the README file to complete the environment setup. However, when I ran the command:
python train.py --data_dir ./data/nvidia/Balloon1 --model_config configs.dgmarbles_nvidia --load_checkpoint ./checkpoints/balloon1/Balloon1.ckpt --output ./out --only_render True
I encountered the following error:
Creating trajectory images
[Open3D INFO] EGL headless mode enabled.
🎥 Rendering 🎥 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0/192(0.0%) ? -:--:-- 0:00:00
FEngine (64 bits) created at 0x126a0c940 (threading is enabled)
eglInitialize failed
Segmentation fault (core dumped)
I tried disabling WandB, but it still didn't work. Have you encountered similar issues? Could you provide me with some guidance on possible solutions?

Hello, thanks for raising this issue! You are the second person to have run into a segmentation fault... I'm not sure how the last person fixed this. I'll spend the next couple days looking into this, because there clearly is an underlying issue with the environment setup.
Based on my intuition, a few possible reasons this could occur:

The CUDA version at /usr/local is different than your anaconda's CUDA version. Some packages (i.e. FRNN) refer to the base CUDA while others (i.e. torch packages) refer to the anaconda version.
PyTorch3D often causes issues. Are you installing it from source?
Verify that torch_scatter is installed correctly
Verify that open3d is installed correctly

Again though, I'll look into this over the next couple days and keep you posted!

Trying to reproduce it - what's your exact OS + CUDA version(s) + Nvidia card and driver? And do you just follow the setup.sh script as written?

Hello! Thank you very much for your response.
Regarding your first reply:
1.The CUDA version displayed in my /usr/local directory is 12.4. However, since the README mentions that FRNN depends on CUDA 11.7, and I don't have sudo permissions on the server, I have only configured CUDA 11.7 in my user directory. I am unsure if this could cause the conflict you mentioned.
2.After running the bash setup.sh ~/miniconda3 dgmarbles command, I have successfully downloaded PyTorch3D. To be sure, I also used git clone https://github.com/facebookresearch/pytorch3d.git to download their project and manually install it. From my experiments, this doesn't seem to be the source of the issue.
3 & 4. I believe that torch_scatter and open3d have been correctly installed.
(dgmarbles) wsq@zkyd:~/dynamic-gaussian-marbles$ pip show open3d
Name: open3d
Version: 0.18.0
Summary: Open3D: A Modern Library for 3D Data Processing.
Home-page: https://www.open3d.org
Author: Open3D Team
Author-email<EMAIL_ADDRESS>License: MIT
Location: /home/wsq/miniconda3/envs/dgmarbles/lib/python3.10/site-packages
Requires: addict, configargparse, dash, ipywidgets, matplotlib, nbformat, numpy, pandas, pillow, pyquaternion, pyyaml, scikit-learn, tqdm, werkzeug
Required-by: nerfstudio

(dgmarbles) wsq@zkyd:~/dynamic-gaussian-marbles$ pip show torch_scatter
Name: torch-scatter
Version: 2.1.2+pt20cu117
Summary: PyTorch Extension Library of Optimized Scatter Operations
Home-page: https://github.com/rusty1s/pytorch_scatter
Author: Matthias Fey
Author-email<EMAIL_ADDRESS>License:
Location: /home/wsq/miniconda3/envs/dgmarbles/lib/python3.10/site-packages
Requires:
Required-by:

Regarding your second reply:
OS: Ubuntu 20.04
CUDA Version: 12.4 (located in /usr/local/cuda), 11.7 (located in /home/.../cuda)
NVIDIA Card: NVIDIA GeForce RTX 4090
Driver Version: 550.100
Installation: I followed the setup.sh script as written without modifications.
Looking forward to your reply, and once again, thank you for your help!

Ok I was unable to reproduce the error, but I did get an environment working with CUDA 12. I just pushed the new setup_cuda12.sh, so give that a try and let me know if it works!

Hello, what's your gcc and g++ versions? Also, if you remove the --only_render True, does it begin training correctly? And if it begins training, are you able to visualize interactively via web viewer (if you're using a server, you can port forward to still visualize interactively - for instance for port 7007: ssh -L 7007:domain:7007 username@domain.

Hello, my gcc and g++ versions are:
(dgmarbles) (base) wsq@zkyd:~/dynamic-gaussian-marbles$ g++ --version
g++ (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

(dgmarbles) (base) wsq@zkyd:~/dynamic-gaussian-marbles$ gcc --version
gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

I removed the --only_render True parameter, and the training process was able to start normally.
Regarding what you mentioned about forwarding to the browser, I am a bit confused. First, I ran the command ssh -L 7007:domain:7007 username@domain in one terminal, and then in another terminal, I ran the command python train.py --data_dir ./data/nvidia/Balloon1 --model_config configs.dgmarbles_nvidia --load_path ./checkpoints/balloon1/Balloon1.ckpt --outdir ./out --only_render True. However, I still get an EGL initialization failure, and my webpage at http://localhost:7007/ shows the error: **This page isn’t working. localhost didn’t send any data. ERR_EMPTY_RESPONSE.**
Additionally, I’d like to add that after debugging, I found that the root cause of the EGL initialization failure comes from the following line in dynamic-gaussian-marbles/src/visualization/render_trajectories.py:
render = rendering.OffscreenRenderer(width=width, height=height)

Ok I went back through this and found the problem: it's the rendering of the Gaussian trajectories via Open3D. Check out this issue, which is identical: https://github.com/isl-org/Open3D/issues/5292. In short, your device does not have the appropriate EGL / OpenGL set up for Open3D's rendering. Unfortunately, fixing this will depend on your own device. However, a quick fix can be to turn off trajectory rendering by commenting out lines 186-188 in src/models/model.py.

Finally, this will only visualize until the error is thrown or the code exits. To indefinitely visualize interactively, please git pull to the to the tag v0.1 and pass in the argument --only_interactive_visualize True instead of --only_render True.


Document how the agent gracefully restarts

We are often asked how to restart the agent to pick up new configuration or how to shutdown agents without killing running tasks. This needs to be documented somewhere.

Relevant to https://github.com/buildkite/agent/issues/476

Also some description of what signals we handle and some nice descriptions like here: https://www.quora.com/What-is-the-difference-between-the-SIGINT-and-SIGTERM-signals-in-Linux-What’s-the-difference-between-the-SIGKILL-and-SIGSTOP-signals

This is the canonical documentation presently: https://github.com/buildkite/agent/blob/ce7280de5d8fc20850f899bd4a1b23e6ced995f2/agent/agent_pool.go#L81

Also, I just really like leaving comments on this issue.

@lox we have a small section on Signal Handling in the overview document of the Agent.
This section might be better with a little more context and in a different place - what do you think about an additional mention and a link to signal handling in the config doc and another in the buildkite-agent start doc? Otherwise I could just add a little more info to the current Signal Handling section so that the probable search terms like 'new config' or 'shutdown agents' will pop up in google with this section.

👋🏻 @lox! Given that the 'stop agent' button is (somewhat recently) graceful and has the option for force stopping (https://github.com/buildkite/buildkite/pull/3064), do we need more docs additions about stopping agents? Possibly just a mention in the signal handling section that they can be killed from the Agent UI?


[WinUI 2.6 Preview] Release mode crash caused by NavigationView ItemsRepeater

Describe the bug
After upgrading to the WinUI v2.6 preview, my UWP app crashes at runtime only when compiled in release mode. The crash is hard to debug this way, but I've attached the stack trace. The stack trace indicates the issue lies somewhere in NavigationView's ItemsRepeater FlowLayout.

Steps to reproduce the bug

Steps to reproduce the behavior:

Upgrade a UWP app with a WinUI NavigationView to v2.6-preview.
Build it for release mode
Observe crash at runtime

Expected behavior
ItemsRepeater shouldn't be problematic in the MUX NavigationView, and it should function without crashing just like it does when compiled for debug mode builds.
Version Info

NuGet package version: Microsoft.WinUI 2.6.0-prerelease.210405001

Windows app type:

UWP
Win32

Yes

Windows 10 version
Saw the problem?

Insider Build (21354)
Yes

October 2020 Update (19042)

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Additional context

StackTrace.txt
Removing the reference to our DataTemplateSelector from the markup produced the same crash.

@ranjeshj I think this needs to be fixed for 2.6.   @ojhad thoughts?

@chingucoding I think I remember you looking at flow layout in the past, does this ring any bells?

@duke7553 are you putting custom types into your navigationview items?

@StephenLPeters We're using a DataTemplateSelector (which it still crashes in release even when this isn't set).
We do have various custom types which act as the model for each item in their DataTemplate. One of them is LocationItem:
<DataTemplate x:Key="LocationNavItem" x:DataType="local2:LocationItem">
                <muxc:NavigationViewItem
                    AllowDrop="True"
                    BorderThickness="0.8"
                    CanDrag="False"
                    Content="{x:Bind Text}"
                    DataContext="{x:Bind}"
                    DragEnter="NavigationViewItem_DragEnter"
                    DragLeave="NavigationViewItem_DragLeave"
                    DragOver="NavigationViewLocationItem_DragOver"
                    DragStarting="NavigationViewItem_DragStarting"
                    Drop="NavigationViewLocationItem_Drop"
                    IsExpanded="{x:Bind IsExpanded, Mode=TwoWay}"
                    IsRightTapEnabled="True"
                    MenuItemsSource="{x:Bind ChildItems}"
                    RightTapped="NavigationViewLocationItem_RightTapped"
                    SelectsOnInvoked="{x:Bind SelectsOnInvoked}"
                    Tag="{x:Bind Path}"
                    ToolTipService.ToolTip="{x:Bind HoverDisplayText}">
                    <muxc:NavigationViewItem.Icon>
                        <muxc:ImageIcon Source="{x:Bind Icon}"/>
                    </muxc:NavigationViewItem.Icon>
                </muxc:NavigationViewItem>
            </DataTemplate>

Example codebehind:
public class LocationItem : ObservableObject, INavigationControlItem
    {
        private string path;
        public ObservableCollection<INavigationControlItem> ChildItems { get; set; }
        public FontFamily Font { get; set; } = new FontFamily("Segoe MDL2 Assets");
        public string HoverDisplayText { get; private set; }
        public SvgImageSource Icon { get; set; }

        public bool IsDefaultLocation { get; set; }

        public bool IsExpanded
        {
            get => App.AppSettings.Get(Text == "SidebarFavorites".GetLocalized(), $"section:{Text}");
            set
            {
                App.AppSettings.Set(value, $"section:{Text}");
                OnPropertyChanged(nameof(IsExpanded));
            }
        }

        public NavigationControlItemType ItemType => NavigationControlItemType.Location;

        public string Path
        {
            get => path;
            set
            {
                path = value;
                HoverDisplayText = Path.Contains("?") || Path.ToLower().StartsWith("shell:") || Path.ToLower().EndsWith(ShellLibraryItem.EXTENSION) || Path == "Home" ? Text : Path;
            }
        }

        public SectionType Section { get; set; }
        public bool SelectsOnInvoked { get; set; } = true;
        public string Text { get; set; }

        public int CompareTo(INavigationControlItem other) => Text.CompareTo(other.Text);
    }

Looking at the stacktrace, it seems that it crashes because measuring the NavigationViewItem objects fails. Flowlayout shows up because ItemsRepeater meaasures everything for layouting purposes, when it encounters an element that fails to measure properly, flowlayout would be the first to notice.

Hmm, not sure if I did everything correct but I wasn't able to repro this issue. @duke7553 if you have the time, it would be amazing if you create a repro app that can be used to dig into this.

@chingucoding I hate to give you an app which has unrelated code, but I can only reproduce this one in Files main branch which should reference the latest WinUI preview.
https://github.com/files-community/Files

After debugging it a bit, it seems like an issue with the Version 2 styles, more importantly probably with the NavigtaionViewItem(Base) one as those crash in MeasureOverride.

Thanks for the added information both of you!

Also, @StephenLPeters I am looking to this issue, feel free to assign this to me.
Also also, if we can't find a way to repro this in MUXC test app, is it still fine to create a PR?

I think we need to fix it. Not being able to repro in our app doesn't change that :)

@StephenLPeters Over at the files repo, we finally have a good fix for this: https://github.com/files-community/Files/pull/4606/
The only changes made are the removal of the corner radius setter which seemed to cause the issues on this. What are your thoughts on this? @ranjeshj FYI


SMILES import in standalone mode

Dear Ketcher team,
First, thanks a lot for putting together Ketcher. I do use it on our prediction server. One of the feature I couldn't get to working is importing molecule as a SMILES string. It says "Extended SMILES and opening of Daylight SMILES is not supported in standalone mode." Is there a way around this?
I would like to be able to load a molecule into Ketcher from a text input (if not directly pasted from clipboard by doing Ctrl+v).
Thank you,
Vishal

Dear @iwwwish ,
thank you for your interest in Ketcher.
Please provide an additional information:

which version of Ketcher do you use?
which mode of Ketcher is used? (from Ketcher v2.2.x two different modes are available: remote - Indigo Service is required, and standalone - it is based on WASM. For details you  can look at https://www.npmjs.com/package/ketcher-standalone).

Dear @AndreiMazol,
Thanks for your reply. I am using Ketcher 2.0 in standalone mode. Is there a reason why SMILES import is disabled? I would appreciate if you could suggest a way around this problem.
Thank you,
Vishal

Dear @iwwwish ,
Ketcher 2.0 does not support standalone mode (now it is called offline remote mode, sorry for confusion). Now you have 2 options to work with SMILES:

Deploy Indigo Service and provide api_path query parameter to Ketcher instance:  http://localhost:3000?api_path={link_to_indigo_REST-Service_here} (SMILES, CML, InchL, SMARTS require working Indigo Service)
Switch to Ketcher 2.2.x (standalone mode). Artifacts can be found here

Best regards,
Andrei