simulate pedestrians in igibson2.1.0

For simulating pedestrians with ORCA,  I refer to this file:
https://github.com/StanfordVL/iGibson/blob/cvpr21_challenge/gibson2/tasks/social_nav_random_task.py.
but the simulator became very slow: self.simulator_step()

and some attribute in cvpr21_challenge is not available in new version of igibson.
Is there any demo of social_nav_random_task available in new version?

and when I try to use the above SocialNavRandomTask to test the env_int_example.py, I get the error:
Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

while, I have solve all the above problems by debugging.
there is still one problem in the social_nav_random_task when load_obstacles:
yaw = obj.bbox_orientation_rpy[2]
rot_mat = np.array([
[np.cos(-yaw), -np.sin(-yaw)],
[np.sin(-yaw), np.cos(-yaw)],
])
initial_bbox = initial_bbox.dot(rot_mat)
initial_bbox = initial_bbox + obj.bbox_pos[:2]
it seems that the obj has no attribute of bbox_orientation_rpy and bbox_pos which means the orientation and position of the bounding box.


process.exit() just after logging, doesn't log to the files.

Please tell us about your environment:

winston version?

[ ] winston@2
[x] winston@3

node -v outputs: v11.13.0
Operating System?  WSL
Language?  ES6/7

What is the problem?
Here is how to reproduce the problem.
const logger = winston.createLogger({
  transports: [
    new winston.transports.File({ filename: "src/logs/access.log", level: "info" }),
    new winston.transports.File({ filename: "src/logs/errors.log", level: "error" })
  ],
  format: winston.format.combine(
    winston.format.timestamp({
      format: "YYYY-MM-DD HH:mm:ss"
    }),
    winston.format.errors({ stack: true }),
    winston.format.splat(),
    winston.format.json()
  )
});

  logger.add(
    new winston.transports.Console({
      format: winston.format.combine(winston.format.colorize(), winston.format.simple())
    })
  );

  logger.info({
    level: "info",
    message: "Incoming Request"
  });
process.exit()

The outcome is, it logs to the console, but doesn't log to the files because it takes some time to log to files.
So the solution can be making the logger.log function async
Or
Can someone suggest a workaround?
What do you expect to happen instead?
It should log to all the three transports, console and 2 files.

You should be able to wait for the "finish" event, and exit then. See this section in the README: (https://github.com/winstonjs/winston#awaiting-logs-to-be-written-in-winston)
However, this behavior seems to be broken atm, at least for File transports - they don't flush on end: #1504

tldr: replace process.exit(1) with process.exitCode = 1;
After wasting a couple of hours I hope this will help someone else.


FEAT:  Auto Populate Time Zone on windows platforms

Issue:  Time Zone needs to be manually configured via /config/config.php on WIndows Platforms.
Suggestion:  Develop method by which Logarr can autoconfigure the localized DTG data.
Resolution:  TBD

Nah.


Map-clearing compiler optimization

What version of Go are you using (go version)?

$ go version
go1.18.1 darwin/arm64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/loganmallory/Library/Caches/go-build"
GOENV="/Users/loganmallory/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/loganmallory/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/loganmallory/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/homebrew/Cellar/go/1.18.1/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/homebrew/Cellar/go/1.18.1/libexec/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.18.1"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/loganmallory/code/mandark/core/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/54/hqns0t411d73n4r2df8tbp0r0000gn/T/go-build2870026131=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
Looking at this issue #20138 and this code merge https://go-review.googlesource.com/c/go/+/110055/  , it seems like the compiler should automatically detect map clears of the form:
for k := range m {
    delete(m, k)
}

and replace the loop with an optimized map clear.
However, when I benchmarked the following code, it appears that only the first case is optimized while the others are much slower:
var n = 4096

// 1 - simple case
// works as expected, compiler optimizes map clear ... 2us per clear
func Benchmark_1(b *testing.B) {
	m := make(map[int]int, n)

	b.ResetTimer()
	for i := 0; i < b.N; i++ {
		//fill up the map 50%
		b.StopTimer()
		for j := 0; j < n/2; j++ {
			m[j] = i
		}
		b.StartTimer()

		//clear the map
		for k := range m {
			delete(m, k)
		}
	}
}

// 2 - function clears the map
// compiler does not optimize map clear ... 50us per clear
func clearMap(m map[int]int) {
	for k := range m {
		delete(m, k)
	}
}
func Benchmark_2(b *testing.B) {
	m := make(map[int]int, n)

	b.ResetTimer()
	for i := 0; i < b.N; i++ {
		//fill up the map 50%
		b.StopTimer()
		for j := 0; j < n/2; j++ {
			m[j] = i
		}
		b.StartTimer()

		//clear the map
		clearMap(m)
	}
}

// 3 - map is held in a struct
// compiler does not optimize map clear ... 50us per clear
type Wrapper struct {
	m map[int]int
}
func (w *Wrapper) clearMap() {
	for k := range w.m {
		delete(w.m, k)
	}
}
func Benchmark_3(b *testing.B) {
	w := &Wrapper{m: make(map[int]int, n)}

	b.ResetTimer()
	for i := 0; i < b.N; i++ {
		//fill up the map 50%
		b.StopTimer()
		for j := 0; j < n/2; j++ {
			w.m[j] = i
		}
		b.StartTimer()

		//clear the map
		w.clearMap()
	}
}

I also tried to explore this in Godbolt but I'm not too familiar with Go bytecode:
1 - Simple case: https://godbolt.org/z/98oYGGrWf
2 - Map passed to clearing function: https://godbolt.org/z/xabq3czj8
3 - Map wrapped in struct: https://godbolt.org/z/63Wa48M4h
What did you expect to see?
I expected that the map clears in cases 2 and 3 (50us per map clear) would be optimized by the compiler just like in case 1 (2us per map clear)
What did you see instead?
The map clears in cases 2 and 3 do not seem to be optimized, they take 50us per map clear while case 1 takes 2us per map clear

I believe this is a dup of #53157.


Error during certificate export

I am using Lemur 0.2.1. When I try to export certificate using gui following error is returned by Lemur server :
2016-01-18 10:18:53,794 ERROR: Internal Error [in /usr/local/lib/python2.7/dist-packages/Flask_RESTful-0.3.3-py2.7.egg/flask_restful/__init__.py:299]
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1475, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1461, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/usr/local/lib/python2.7/dist-packages/Flask_RESTful-0.3.3-py2.7.egg/flask_restful/__init__.py", line 462, in wrapper
    resp = resource(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/views.py", line 84, in view
    return self.dispatch_request(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/Flask_RESTful-0.3.3-py2.7.egg/flask_restful/__init__.py", line 572, in dispatch_request
    resp = meth(*args, **kwargs)
  File "/usr/local/src/lemur/lemur/auth/service.py", line 121, in decorated_function
    return f(*args, **kwargs)
  File "/usr/local/src/lemur/lemur/certificates/views.py", line 855, in post
    extension, passphrase, data = service.export(cert, args['export']['plugin'])
  File "/usr/local/src/lemur/lemur/certificates/service.py", line 91, in export
    return plugin.export(cert.body, cert.chain, cert.private_key, export_plugin['pluginOptions'])
  File "/usr/local/src/lemur/lemur/plugins/lemur_openssl/plugin.py", line 122, in export
    create_pkcs12(body, output_tmp, key, alias, passphrase)
  File "/usr/local/src/lemur/lemur/plugins/lemur_openssl/plugin.py", line 47, in create_pkcs12
    f.write(key)
TypeError: expected a character buffer object

PKCS requires a private key to export, are you sure you have one available to lemur? This should probably be a robust error message.


GO:1990877   Lst4-Lst7 complex term name update

GO:1990877   Lst4-Lst7 complex
Definition (GO:1990877 GONUTS page)
A heterodimeric complex that functions as a GTPase-Activating Protein (GAP) Complex for members of the Rag family of GTPases. In the budding yeast, this complex contains Lst4 and Lst7, while the orthologous mammalian complex contains Follicular (FLCN) and either follicular interaction protein 1 (FNIP1) or FNIP2. PMID:24095279 PMID:26387955
Please could we update these labels from related to exact. These are alternative names for the human complex
FLCN-FNIP2 complex	related
FLCN-FNIP1 complex	related
FNIP-Folliculin RagC/D GAP complex	related
could we make
FNIP-Folliculin RagC/D GAP complex the primary name (more species neutral)
also add
exact "BFC complex" (the pombe name). I will provide PMID for this shortly, it isn't available yet.
thanks
Val

Reference for BFC complex: PMID:34805795


Fixed EIP681 and EIP67, added and improved a lot of ERCs

fixed EIP681 and EIP67
improved ERСs: 20, 721
added ERCs: 165, 777, 820, 1400 (and 1410, 1594, 1644, 1643 as for separate token), 888, 1633, 721x, 1155, 1376

This closes #111 , #110 , #109 , #108 , #107 , #98 , #82 , #81


Consider removing the "LApp Browser" button

Feature Request
On the bolt card wallet screen, the "LApp Browser" button looks like it is not needed.
All other functions on the screen have a purpose (Bolt Card balance, details & transactions).
On my phone it brings up a browser on a default search page (i.e. not useful).
On BlueWallet, the button only exists for Lightning wallets and not for Bitcoin wallets.
I suggest we remove the button as it will make the screen simpler and give a cleaner design.

removed


Using DocumenterVitePress as new documentation site

See #60.
Also, remember that we can't merge before https://github.com/LuxDL/DocumenterVitepress.jl/pull/38 is fixed. It will add documentation versioning, which is a required feature for me.
To do:

[ ] Add the home page (see docs/src/.vitepress/theme/index.ts + https://github.com/LuxDL/DocumenterVitepress.jl/blob/master/docs/src/index.md)
[ ] Add a favicon + logo (track here: #70 ), see: https://github.com/LuxDL/DocumenterVitepress.jl/tree/master/docs/src/assets

To run it locally, cd into docs, and run:
npm i

It will install all dependencies found in the package.json file.
Then open a julia instance in the docs folder, activate the environment and run:
include("make.jl")

And in another terminal, run:
npm run docs:dev

Then you'll have a site that is served locally.

The website is here: https://virtualplantlab.github.io/PlantSimEngine.jl/previews/PR69.
Although it builds fine locally, the build on GA is faulty and needs to be checked.

If you're not deploying a custom theme via the Vitepress files, you can remove them + the package.json!

Thank you for the review @asinghvi17! The website builds nicely locally, but it's not building properly on github pages, do you have any idea why?


Need help creating a compound partition key

I want to do this
CREATE TABLE pushes (
  owner_id int,
  push_month int,
  pushed_at timestamp,
  values map<text, text>,
  PRIMARY KEY ((owner_id, push_month), pushed_at)
) WITH CLUSTERING ORDER BY (pushed_at DESC);

but am having issues creating the compound partition key (owner_id, push_month), here's what I have- currently only owner_id is the partition key. I don't want to use belongs_to because Owner is actually a postgres ActiveRecord model.
class Push
  include Cequel::Record
  key :owner_id, :int
  key :push_month, :int
  key :pushed_at, :timestamp, order: :desc, index: true
  map :values, :text, :text
...

Can anyone help? Thanks

By default only the first key is added to the partition key, but you can override this behavior with the :partition option:
key :owner_id, :int
  key :push_month, :int, partition: true
  key :pushed_at, :timestamp, order: :desc, index: true
  map :values, :text, :text

Feel free to reopen if that doesn't clear things up!


Access admin page for moderation

As an admin I want to access admin page, so that I can moderate the cafes on the map/list.
Mockups:

Acceptance Criteria:

GIVEN admin user is successfully logged in to the system, WHEN he clicks on "Admin" button, THEN system shall navigate him to the admin page.

The admin page shall contain the following tabs at the top of the screen:
a. Users
b. Places

When admin clicks on a tab, system shall navigate him to it.

Out of scope:
list of places and users are out of scope of this story

Not relevant.


Feat: Add groups for LSP semantic tokens

I'm not sure what I am doing here, but my Lua code was getting white, so I linked some highlight groups to Treesitter ones.

It'll probably be better to change the notation to<EMAIL_ADDRESS>= { ... }

TODO: use the other syntax and add all these tokens https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_semanticTokens

Thanks for the PR!
What do you mean it was "getting white"?  Was everything completely white, or just some highlights white?

It seems like these tokens are new, tokyonight added them recently.

This PR seems to be the culprit.

It would have been really nice if all of the Neovim colorschemes were just forks of some core repository, and then just override colors as the developers see fit...

I am going to leave this open until there is a confirmation (from either you or me) that this groups are correct.  I suspect they are, I just don't have the time now to double-check.

This PR seems to be the culprit.

According to the docs we can simply disable all tokens, but I thought it would be useful to have easy access to this variables. Just in case anyone needs it:
for _, group in ipairs(vim.fn.getcompletion("@lsp", "highlight")) do
  vim.api.nvim_set_hl(0, group, {})
end

I am going to leave this open until there is a confirmation (from either you or me) that these groups are correct. I suspect they are, I just don't have the time now to double-check.

Following that script provided by neovim team, the following seems to be "official" groups, but I guess things may change until a stable release:

@lsp.type.class
@lsp.type.decorator
@lsp.type.enum
@lsp.type.enumMember
@lsp.type.function
@lsp.type.interface
@lsp.type.macro
@lsp.type.method
@lsp.type.namespace
@lsp.type.parameter
@lsp.type.property
@lsp.type.struct
@lsp.type.type
@lsp.type.typeParameter
@lsp.type.variable

The docs also say that many groups are linked by default to other highlight groups:

@lsp.type.class         Structure
@lsp.type.decorator     Function
@lsp.type.enum          Structure
@lsp.type.enumMember    Constant
@lsp.type.function      Function
@lsp.type.interface     Structure
@lsp.type.macro         Macro
@lsp.type.method        Function
@lsp.type.namespace     Structure
@lsp.type.parameter     Identifier
@lsp.type.property      Identifier
@lsp.type.struct        Structure
@lsp.type.type          Type
@lsp.type.typeParameter TypeDef
@lsp.type.variable      Identifier

I think we can drop the other notation from this PR, keep folke's changes and add the other possible tokens commented out as an "easy access" for future improvements. What do you think @AlexvZyl?

Yes, I agree with you.  You mind doing that?

Sure, I'll get this done later today or tomorrow.

Beautiful, thanks for the work!

There is a much easier way to disable semantic tokens:

I've read somewhere that it is a 'chosen' way to do that instead of messing with highlight groups.

If you can find this source you are more than welcome to open a PR.  We are currently not doing that since we are basically doing what Folke is doing over at tokyonight.


Fix erroneous messages about invalid package paths in html imports

fixes https://github.com/dart-lang/polymer-dart/issues/72

:+1:


Create issue templates

Issue templates help standardizes the process of understanding the contributor/end-user situation and helps priorize work.
Add issue templates for bug reports and feature requests.

/close


Create LICENSE

The license file itself is fine of course (although it uses different brackets in the appendix from the plain text version at apache.org [1]  for some reason, its identical otherwise).
But as the appendix says, all copyrighted files should also include a copyright notice. The appendix has more details regarding the form of the copyright notice.
[1] https://www.apache.org/licenses/LICENSE-2.0.txt

Added the header to the python files. All good ?

Looks good. Interesting choice to use string literals instead of comments, but that doesn't really matter I think.


Inline spread without type condition on non-null type gives an error

If you make an untyped spread on a non-null type, GraphiQL gives you a warning:

Here's a reproduction of the bug:
http://graphql.org/swapi-graphql/?query={
  allFilms(first%3A 1) {
    pageInfo {
      ... {
        hasNextPage
      }
    }
  }
}&operationName=null
But I think this is OK, here's the spec:

If the TypeCondition is omitted, an inline fragment is considered to be of the same type as the enclosing context.

https://facebook.github.io/graphql/#sec-Inline-Fragments
Is this error correct? Should the server accept this query, or should it be rejected?
cc @willianvdv who identified this

Whoa, great catch! I'm not sure why this code returns a non-null version of the parent type instead of the same parent type  - cc @leebyron for this. I think this is a bug.
Also, this probably belongs in graphql-js - would it be okay if we move this issue there? Also would be super grateful if we can get a PR for the fix.

@rmosolgo can you confirm this behavior is fixed in 0.17.0? we have https://graphiql-test.netlify.com if you'd like to give it a whirl. see if it's been fixed in graphql-js already?

It looks like this has been fixed in the last 2 years 🎉 The example link above no longer demonstrates the error:


Knausj generic terminal establishment

solves #505

Looks great, once you think it's ready we will merge it

I think there are some things left to do, like deciding wether terminal_list_all & co should be defined in the terminal specific file or in generic_terminal.py.
One question about the existing terminals: should they all be first transitioned to the new "architecture" or should this be done in later PRs?

Generally, things should work -- so the existing terminals should be migrated where it's reasonable. This does introduce some commands that will not work for e.g. gnome-terminal and guake as-is. I personally can live with this though.
I'm firmly on the fence re: "terminal_list_all & co should be defined in the terminal specific". I'm fine with the current approach, but we could have a generic_unix_shell tag for these super common implementation for terminals to opt into, as fidget suggested.


Adds snapshot testing functionality to plot_gate_map() and plot_coupling_map().

Summary
Added parameter filename to plot_gate_map() and plot_coupling_map(). Added functions for testing plot_gate_map() and plot_coupling_map().
Details and comments
Results for snapshot testing of plot_coupling_map() seem to be fine. But, there is some with plot_gate_map().

 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.


feat: add ability to manually select custom cooldown deposits

Added entry fee fallback in useIsCustomCooldownDeposit hook
Added ability to manually set deposits with custom cooldown in vault config

closed in favour of https://github.com/dhedge/ui-kit/pull/107


fix(ts/analyzer): Use empty tuple type for rest pattern with tuple initializer

Description:
Related issue:

Closes https://github.com/dudykr/stc/issues/186.

It seems this PR doesn't fix the #186 issue, the type of a1 is still recognized as string[]


rmf docker img

~ in testing ~
rmf docker image
This introduces a CI to build a rmf docker image and push it to this current github registry. Apart from easing the steps for external user to try out rmf (without installation), this will soon be handy for further (nightly) e2e test.
How to use it
docker pull docker.pkg.github.com/open-rmf/rmf/rmf_demos:latest
docker tag docker.pkg.github.com/open-rmf/rmf/rmf_demos:latest rmf:latest
docker run -it --network host rmf:latest bash -c "ros2 launch rmf_demos office.launch.xml headless:=1"

an example for rocker is also mentioned on the readme.
Signed-off-by: youliang<EMAIL_ADDRESS>

sorry i took so long to review this! Things seem to be working pretty well, which is great! I'm not sure but I get this error in the stdout logs for rocker:
[api_server-11] OSError: [Errno 98] Address already in use

In addition, it seems the navigation graph and map doesn't appear. I'd probably want to try this on a more serious device ( currently using my laptop ) and determine if its hardware specific on my end.

Thanks for trying. In this case, is the bare headless docker running fine? How about dispatching tasks via CLI? Iam currently able to run it on my graphic card-less laptop. You can also try  rocker --nvidia --x11 if required.

bare headless is working pretty well as far as I can tell. Docker is amazing. Still no luck with rocker though, so I think i'll try on a different device.
What would be great is if there was a sort of configuration to disable all simulation aspects of a demo. This would immediately make the docker useful with real life deployments. As a docker image purely based on rmf_demos, this may be hard to do as you need to edit some files. But this is probably out of the scope of this PR.
I'm wondering what you think of providing rocker option if it doesn't seem to work consistently, as it might cause confusion, but otherwise I think its awesome!

to follow up, on another machine, the command rocker --x11 --network host rmf:latest "ros2 launch rmf_demos office.launch.xml" seems to give OpenGL context errors:
[rviz2-7] [ERROR] [1618281511.068124643] [rviz2]: Failed to create an OpenGL context. BadValue (integer parameter out of range for operation)
[rviz2-7] [ERROR] [1618281511.068154663] [rviz2]: RenderingAPIException: Unable to create a suitable GLXContext in GLXContext::GLXContext at /tmp/binarydeb/ros-foxy-rviz-ogre-vendor-8.2.1
/obj-x86_64-linux-gnu/ogre-v1.12.1-prefix/src/ogre-v1.12.1/RenderSystems/GLSupport/src/GLX/OgreGLXContext.cpp (line 60)
[rviz2-7] [ERROR] [1618281511.068203894] [rviz2]: rviz::RenderSystem: error creating render window: RenderingAPIException: Unable to create a suitable GLXContext in GLXContext::GLXContext
 at /tmp/binarydeb/ros-foxy-rviz-ogre-vendor-8.2.1/obj-x86_64-linux-gnu/ogre-v1.12.1-prefix/src/ogre-v1.12.1/RenderSystems/GLSupport/src/GLX/OgreGLXContext.cpp (line 60)
[rviz2-7] [ERROR] [1618281511.072526635] [rviz2]: Failed to create an OpenGL context. BadValue (integer parameter out of range for operation)
[rviz2-7] [ERROR] [1618281511.072580846] [rviz2]: RenderingAPIException: Unable to create a suitable GLXContext in GLXContext::GLXContext at /tmp/binarydeb/ros-foxy-rviz-ogre-vendor-8.2.1
/obj-x86_64-linux-gnu/ogre-v1.12.1-prefix/src/ogre-v1.12.1/RenderSystems/GLSupport/src/GLX/OgreGLXContext.cpp (line 60)
[rviz2-7] [ERROR] [1618281511.072626796] [rviz2]: rviz::RenderSystem: error creating render window: RenderingAPIException: Unable to create a suitable GLXContext in GLXContext::GLXContext
 at /tmp/binarydeb/ros-foxy-rviz-ogre-vendor-8.2.1/obj-x86_64-linux-gnu/ogre-v1.12.1-prefix/src/ogre-v1.12.1/RenderSystems/GLSupport/src/GLX/OgreGLXContext.cpp (line 60)
[rviz2-7] [ERROR] [1618281511.076584875] [rviz2]: Failed to create an OpenGL context. BadValue (integer parameter out of range for operation)
[rviz2-7] [ERROR] [1618281511.076606055] [rviz2]: RenderingAPIException: Unable to create a suitable GLXContext in GLXContext::GLXContext at /tmp/binarydeb/ros-foxy-rviz-ogre-vendor-8.2.1
/obj-x86_64-linux-gnu/ogre-v1.12.1-prefix/src/ogre-v1.12.1/RenderSystems/GLSupport/src/GLX/OgreGLXContext.cpp (line 60)

What would be great is if there was a sort of configuration to disable all simulation aspects of a demo. This would immediately make the docker useful with real life deployments. As a docker image purely based on rmf_demos, this may be hard to do as you need to edit some files. But this is probably out of the scope of this PR.

Agree. Users can run custom config or launch files by mounting volume to host -v. It will be nice to have a bare and light docker image without rmf_demos, with this we can have multi stage build.
Yeap, the run with rocker feature seems inconsistent for now. I have updated to doc and specify it as "Experimental". We will soon need more testing to solve all these "graphical" issues on various machines.


Fix ServingRuntime args

Description

we test this multi-node feature with this template and found some small issues. This pr fix this.
Note)  this PR template was working with old vllm image.
How Has This Been Tested?

Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

for reference, https://github.com/vllm-project/vllm/issues/8735


Add executor_path and applications_path to spark config

TL;DR
nit: Add executor_path and applications_path to spark config
people may want to change python and application path in the driver and worker node when they use custom spark image.
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
^^^
Tracking Issue
https://github.com/flyteorg/flyte/issues/
Follow-up issue
NA

cc @peridotml


Poor T1 MNI normalization

Dear fmriprep experts, we recently encountered an issue with our T1 skull stripping using fMRIprep. Part of dura mater was included in the brain mask leading to very poor EPI-T1 registration.
The command used is as follows
antsBrainExtraction.sh -a /data/sub-22146/anat/sub-22146_T1w.nii.gz -m /work/fmriprep_wf/single_subject_22146_wf/anat_preproc_wf/skullstrip_ants_wf/t1_skull_strip/T_template0_BrainCerebellumProbabilityMask.nii.gz -e /niworkflows_data/ants_oasis_template_ras/T_template0.nii.gz -d 3 -f /niworkflows_data/ants_oasis_template_ras/T_template0_BrainCerebellumRegistrationMask.nii.gz -s nii.gz -k 1 -o highres001_ -q 1 -u 1

Using NKI template did not resolve the issue of skull stripping, below is the skull stripped image
antsBrainExtraction.sh -a /data/sub-22146/anat/sub-22146_T1w.nii.gz -m /work/fmriprep_wf/single_subject_22146_wf/anat_preproc_wf/skullstrip_ants_wf/t1_skull_strip/tpl-NKI_res-01_class-brainmask_probtissue.nii.gz -e /templateflow/tpl-NKI/tpl-NKI_res-01_T1w.nii.gz -d 3 -f /templateflow/tpl-NKI/tpl-NKI_res-01_label-BrainCerebellumExtraction_roi.nii.gz -s nii.gz -k 1 -o highres001_ -q 1 -u 1

I wonder if there is a solution to this.
Thank you!
Oliver

Thanks for this report. A couple things:

I think you should definitely report this upstream to ANTs. If they can help figure out how to better support cases like this, we can either incorporate their updated parameters or, if a code change is necessary, we can update to a new version of ANTs when it's available.
I notice the FAST tissue segmentation is much better than the skull stripping. Did you also run FreeSurfer? I believe @oesteban added some brainmask refinement using FreeSurfer tissue segmentation for cases like this.

This could definitely be caused by the mask refinement

@effigies Thanks for the advice. I will report it to ANTs. I did not run FreeSurfer and I am running fmriprep again with FreeSurfer. Will let you know if that improves the outcome.

If you did not run FreeSurfer then please scratch this https://github.com/poldracklab/smriprep/issues/55#issuecomment-465786192

@oliver-xie could you share this T1w privately?

@oesteban I have shared the T1w images through google drive to your Stanford email address. I also checked with ANTs developers and was told to use another template.
Thanks for your help!

Thanks, yes, I received the link. Which template did the ANTs devs recommend you?

They did not recommend a specific template. Just told me to try another template.


quic: add Private Key Provider support

Commit Message: quic: add Private Key Provider support
Additional Description:
This PR adds private key provider support to the QUIC over TLS 1.3
Risk Level: low
Testing: unittest and integration test
Docs Changes: api
Release Notes: new feature
Platform Specific Features: n/a

cc @danzh2010 @ggreenway @yanavlasov

/retest

/assign @danzh2010

/wait

This looks like it might conflict a bit with #32260 (which is almost finished)

This looks like it might conflict a bit with #32260 (which is almost finished)

thanks! I will take a look at.


explore sidebar title should left align with file icon

When there is only Folders section in explore sidebar, title should left align with file icon.

We do actually align the items in the explorer with the title:

It seems your file theme is disabling the tree chevrons, which is why it's not aligned


Fix paintScreen for IDE 1.6.10 and add combo display/clear functions

Main commits:

Applied the paintScreen() fix from V1.1.1 which fixes the screen corruption problem with Arduino IDE 1.6.10

Added core function paintScreenAndClearImage(), used by new function displayAndClear(). Many sketches call display() and then use clear() before rendering the next frame. Providing a function to do both saves these sketches a function call. Mainly though, because the buffer bytes are cleared while waiting for them to shifted out to the display, it doesn't take any more time than just calling display(). You save the extra time that a separate clear() call would take.
This was proposed in issue #89, which could be closed if this PR is applied.

Minor commits:

For function fillScreen(), changed the default value for the color argument from WHITE to BLACK. I think clearing the screen buffer to black (all zeros) will likely be the most common use of fillScreen(). This won't affect any existing code since nothing is currently calling fillScreen() with a default.

Removed the unnecessary use of the this-> pointer in function drawBitmap(). It's not used anywhere else. The library coding style should be consistent.

There may be a cleaner way to execute the clears and draws and for the default value of function calls, specifically fillScreen() in this case, is possible. I assume a call with on, not off. Pushing the commit. Thanks MLXXXp.


No Picture returned from the Camera Plugin

On all platforms, when launching the camera app via the camera plugin, a user is able to take a picture using the camera plugin but the picture is unaccessible to the app. This relates to the same origin policy error where we are attempting to access the file uri where the picture lives from a different origin.

Closing since we haven't seen very much activity on this issue. Feel free to reopen.

I'm not sure if what I'm experiencing is related to this or not...
I'm using the PG Developer app to test my app before jumping through the hoops of compiling it on its own. In both Android and iOS I'm able to choose photos from the camera roll and view them in my app.
Then I would like to upload them to my server. On Android this is working as expected. On iOS it appears that nothing is sent.
Via console.log I can see that the file uri (on ios) is file:///var/mobile/Containers/Data/Application/2D778ACD-42EA-43AE-A644-FAB48855DB19/tmp/cdv_photo_003.jpg
Here's my upload code:
var FT = new FileTransfer();
var uploadOptions = new FileUploadOptions();
var uploadPath = api.baseurl + '/photos.json';

uploadOptions.fileKey = 'photo';
uploadOptions.fileName = 'photo.jpg';
uploadOptions.chunkedMode = false;
uploadOptions.params = {
	deviceId: app.info.device_id
	,latitude: lat
	,longitude: lng
	,caption: caption
};

var win = function(resp){ //resp is a FileUploadResult
	console.log(resp);
	$.mobile.loading('hide');
	return successCB(resp);
};
var lose = function(err){
	console.error(err);
	$.mobile.loading('hide');
	ui.fail_handler(err, 'photo upload');
	return failCB(err);
};

try {
	$.mobile.loading('show',{
		text: "Uploading photo, please wait...",
		textVisible: true,
		theme: "a"
	});
	FT.upload(fileURI, encodeURI(uploadPath), win, lose, uploadOptions);
}catch(e){
	ui.fail_handler(e, 'calling FT.upload');
}

If this is a known issue with the PGD app, and given that it works on Android, if I can expect it to work on iOS once compiled to my own app, then I can live with that. Is that the case?

Hi @atuttle
I don't believe this is a known issue within the PhoneGap Developer App. It should work once you switch over to your own compiled app. However I would look at the server logs first to see at least the app had tried to upload the image.
If you can see maybe a 404 or at least any status code that indicated that the app tried to reach the server, that'd be a good place to start. Otherwise, if there is no indication then we can dig into this issue further.

Thinking it might be the size of the uploaded file I tried uploading a screen shot of my iPod instead of a photo, but the same thing happens.
I can see that the request from iOS is sent to my server, but the server is complaining that the file field from the upload is missing/blank; which is a bit odd as I can see it listed as a field when debugging and it has a nonzero length... What baffles me is that it's the same code running on both iOS and Android, and it works fine from Android. This leads me to believe it's not the server-side code but something with the app / permissions to send the file, maybe?

To follow up, after I started building my app on its own, the problem went away. I don't know what plugins the phonegap developer app has installed, but I'm making use of FileTransfer and the File plugin. I could see how not having one or both of those could be problematic. At any rate, I'm on my feet. Thanks for your attention! 👍

Hi @atuttle
Well, glad to hear it's working for you!


Support OAS 3.1 in type extensions

What/Why/How?
Plugin type extensions are the only remaining place that doesn't support
OpenAPI 3.1.0 documents.
Reference
Fixes #314
Testing
I've parametrized the existing type extensions test. The fact that the test
adds webhook support (something OAS 3.1 has explicit support for now) may be
slightly silly, but the test is no less valid for it.
Check yourself

[X] Code is linted
[ ] Tested with redoc/reference-docs/workflows

(I don't think this is applicable here)

[X] All new/updated code is covered with tests

Thanks, @mjpieters 👏


Added some guides

Added a few simple explanations of some topics that aren't really explained.
Currently added:

transforms
scenes

I can't believe I missed replying on this thread :D
There's going to be a post about the roadmap + guides stuff, as mentioned here which will affect the timing of guides (i.e guides being made right before a large scale refactor in the code is going to be wasteful :))


[Experiment] Use incremental vacuum to speed up delete?

Description
Background
In SQLite, data is stored in pages. When data is deleted, the pages which store that data are marked as free in the "freelist", which can be reused when new data is added. This means that no actual delete happens on disk.
In the past, we found that the database size increased a lot in long term use, and deleting data doesn't free up disk space. auto_vacuum = FULL was added to solve this issue.
auto_vacuum
According to the SQLite documentation, when auto_vacuum is set to full, on every transaction freelist pages are moved to the end of the file and truncated. If you think about it, this is terrible for our use case, since all our heartbeat data is inserted interleaved:
Heartbeat table
--------------------------------------------Time------------------------------------------->
|monitor1|monitor2|monitor3||monitor1|monitor2|monitor3||monitor1|monitor2|monitor3|monito..
--------------------------------------------Time------------------------------------------->

If monitor 1 is deleted, essentially all the pages in table needs to be shifted to reclaim the free space:
Heartbeat table
--------------------------------------------Time------------------------------------------->
|--------|monitor2|monitor3||--------|monitor2|monitor3||--------|monitor2|monitor3|-----..
--------------------------------------------Time------------------------------------------->
vacuum ->
--------------------------------------------Time------------------------------------------->
|monitor2|monitor3|monitor2||monitor3|monitor2|monitor3|..
--------------------------------------------Time------------------------------------------->

If auto_vacuum is set to incremental, this behavior is disabled, and we can run a separate command incremental_vacuum to free up a limited number of pages.
Nightly cleanup
Currently the server deletes heartbeat data older than the retention period every night. I think theoretically auto_vacuum = FULL also has no use here. Assuming the monitor config is not changed, the server will produce the same amount of data each day. If we cleanup the database every night, all the freelist pages can be reused the next day. The database size should not increase past the size of the data retention period. There is indeed one caveat, if the retention period is decreased, the database size will not decrease correspondingly. But maybe trigger a vacuum on changing of retention period can be a solution?
Experiment
However, I have not researched enough to see if this is actually happening on delete, or if the alignment situation in the heartbeat table is such that the all the pages are moved like that on delete, or it just leads to more fragmentation. I also don't have a big enough database to test this on, and my 4MB database showed no noticeable improvement.
Anyone who is interested can test this PR to see if delete is faster. I have added a logging function to time how long the delete takes. It's set at the INFO level so it might not show up by default.

Sounds interesting. I will test it later. Added it to the 1.22.0 milestone first.

Currently testing the experimental fix. 'Will report no later than this Friday on how it is going.
Instructions how I applied it on the Uptime-Kuma container for who may be interested:

Download the raw server/database.js & server/server.js files on your hostwget https://github.com/chakflying/uptime-kuma/raw/experiment/incremental-vacuum/server/database.js --output-document=server/database.js
wget https://github.com/chakflying/uptime-kuma/raw/experiment/incremental-vacuum/server/server.js --output-document=server/server.js

Mount it to your container with destination path being /app/server/database.js & /app/server/server.js respectively (make sure it has read+write permissions)
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data -v <PREVIOUSLY_DOWNLOADED_FILES_DIR>/server/database.js:/app/server/database.js -v <PREVIOUSLY_DOWNLOADED_FILES_DIR>/server/database.js:/app/server/server.js --name uptime-kuma louislam/uptime-kuma:1

Docker Compose file example:
services:
  uptime-kuma:
    [...]
    volumes:
      - uptime-kuma:/app/data:rw
      - <PREVIOUSLY_DOWNLOADED_FILES_DIR>/server/database.js:/app/server/database.js:rw
      - <PREVIOUSLY_DOWNLOADED_FILES_DIR>/server/database.js:/app/server/server.js
    [...]

Reporting back (late, but still)!
It did seem to have accelerated my Uptime Kuma installation but all slowdowns/locks up still seem to exist. They just happen later unfortunately.
It still gets locked up easily when, for example, refreshing the page while it is pulling data for each monitor. Aka, when the monitors list has part of them still saying « N/A » as their uptime percentage. If authentication is disabled, the authentication login page will be seen for a moment before getting redirected properly and being greeted with an empty list until the service catches up or is restarted.
I still consider it as an improvement as it has prevented my Uptime Kuma instance to be so locked up that it couldn't do its monitoring pings to Healthchecks.io (DMS to check if it's dead) in a timely manner.

@chakflying could you add PRAGMA optimize; as part of the nightly cleanup?

@chakflying I might have missed it but you're never invoking PRAGMA incremental_vacuum; ?

The missing executions of optimize and vacuum would also explain the slowdowns observed by @campfred. The database slowly gets more fragmented and the query planer has to work with outdated statistics on top of that.

@louislam: Any news after testing?

@louislam: Any news after testing?

I didn't see any negative effects, so I will keep this.

Our uptime-kuma instance with ~80 monitors and 365 days of history feels a lot snappier now. sqlite db size for reference: 4800MB


Importing tab sessions overwrites (wipes) previous sessions saved

Hello,
I'm glad I just started to use your extension. Because otherwise I would've been VERY sad to loose all my saved tab sessions. Which I did, but they weren't many yet.
I basically had three sessions saved and then went on to import a JSON file from my other browser which had other sessions instead. The result was that I ended up ONLY with the newly imported sessions and my saved sessions were gone! :(
I hope you can find the problem and fix it since it could be VERY devastating to loose a lot of research time...
Thank you very much and good luck with your project! :D

Hi, sorry about this. I have a commit pushed to master that fixes this, and will publish soon after some testing.

Fixed in 2.9.1


[ENHANCEMENT] #299 Changing 'ctrl+c', 'ctrl+x', and 'ctrl+v' action at the workspace

when 'ctrl+c', 'ctrl+x', and 'ctrl+v' is pressed sequentially at the workspace, plz make a new file in the manner of duplicating.
Signed-off-by: Minsung Jin<EMAIL_ADDRESS>

제발 commit amend를 사용해서 commit을 합쳐주세요!
그리고 action이 어떻게 바뀌었는지 써주세요.

I agree with @wcho.
I can't assume what is changed from the commit messages.

Fix incorrect behavior of copy/paste/move?
Add copy/paste/move feature?
Change 'ctrl+c' binding from copy to another opertaion?

several existing commit about a JShint unifies into a single commit.


beingLookedAtByLocalPlayer() is nil

After #3012, clients occasionally error with attempt to call upvalue 'beingLookedAtByLocalPlayer' (a nil value) under various circumstances.
A few stack traces:
1.  BeingLookedAtByLocalPlayer - addons/wire/lua/entities/base_wire_entity.lua:233
 2.  DoNormalDraw - addons/wire/lua/entities/base_wire_entity.lua:252
  3.  unknown - addons/wire/lua/entities/gmod_wire_button.lua:22

1.  BeingLookedAtByLocalPlayer - addons/wire/lua/entities/base_wire_entity.lua:233
 2.  DoNormalDraw - addons/wire/lua/entities/base_wire_entity.lua:252
  3.  Draw - addons/wire/lua/entities/base_wire_entity.lua:22
   4.  DrawTranslucent - gamemodes/base/entities/entities/base_anim.lua:49
    5.  unknown - addons/wire/lua/entities/gmod_wire_lamp.lua:21

1.  BeingLookedAtByLocalPlayer - addons/wire/lua/entities/base_wire_entity.lua:233
 2.  DoNormalDraw - addons/wire/lua/entities/base_wire_entity.lua:252
  3.  unknown - addons/wire/lua/entities/base_wire_entity.lua:22

All of which end up here.

I believe Initialize gets overwritten by multiple entities without calling BaseClass.Initialize so this value never gets initialized.

Can we just revert that dumb local. I'm not a fan of it.

No no no we can save it #3046


Kiwix.WikiMed.Electron v2.2.90-E

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

This updates v2.2.9-E to v2.2.90-E because 2.2.9 was not being picked up as the latest version.

This is indeed a duplicate package. Unfortunately, my numbering scheme works like this: v2.2.0-E -> v2.2.6-E -> v2.2.62-E -> v2.2.9-E, but winget things 2.2.62 is the latest package. Therefore I have updated the numbering to v2.2.90-E, but the package is the same. Generating a new 1.6GB package just for this minor numbering change would be very wasteful (of time, of energy, of resources).

This is indeed a duplicate package. Unfortunately, my numbering scheme works like this: v2.2.0-E -> v2.2.6-E -> v2.2.62-E -> v2.2.9-E, but winget thinks 2.2.62 is the latest package (see microsoft/winget-cli#2829). Therefore I have updated the numbering to v2.2.90-E, but the package is the same. Generating a new 1.6GB package just for this minor numbering change would be very wasteful (of time, of energy, of resources).

You should be able to use AppsAndFeatures entries to work around this, but you will need to add it for all versions for the mapping to work properly. You will need to add this section in each *.installer.yaml manifest
AppsAndFeaturesEntries:
- DisplayVersion: <displayversion>

Then just use these package versions and display versions (from your example)

Package Version
	Display Version

 <IP_ADDRESS>
	 v2.2.0-E

 <IP_ADDRESS>
	v2.2.6-E

 <IP_ADDRESS>
	 v2.2.62-E

 <IP_ADDRESS>
	v2.2.9-E

@Trenly I think that now I'm aware of this issue, i.e. that winget uses strict numerical numbering and not alphabetic sorting, or the latest manifest, to determine latest, it might just be easier if I deleted the v2.2.9-E manifest, and leave only v2.2.90-E, so as not to complicate things. Do I just submit a separate PR removing a manifest version?

@Trenly I think that now I'm aware of this issue, i.e. that winget uses strict numerical numbering and not alphabetic sorting, or the latest manifest, to determine latest, it might just be easier if I deleted the v2.2.9-E manifest, and leave only v2.2.90-E, so as not to complicate things. Do I just submit a separate PR removing a manifest version?

That would work

@Trenly I've made a PR to remove the prior duplicate: https://github.com/microsoft/winget-pkgs/pull/93347.


Update README.md for changing session's TTL range

max TTL changed to 86400s from 3600s from https://github.com/hashicorp/consul/pull/1412

Awesome, thanks for the fix!


Possible violation of copyright

Hi,
I strongly believe your GitHub profile violates copyright, particularly regarding the animation about frog guys 🐸
You'd better change your profile picture or Grandpa Mang-Tae would get you soon.
Good luck. Please do not make me say "I told you".

LGTM :+1:


Move forked header CSS to theme

@stvstnfrd matching theme changes to move forked SASS

matches https://github.com/Stanford-Online/edx-platform/pull/770


Initial commit for kubefed operator installation docs

added /docs dir
added initial installation md doc
added /docs/images dir (to be populated)

@abrennan89 QE approved.

/lgtm


ImportError: No module named MalmoPython

I have tried to build tutorial_1.py . But I got this error message.
I use Linux Mint. How can I find MalmoPython module?
Thanks!

@ayyucedemirbas  It should be in your python examples folder, then from there you should be able to add it to your users paths.

If there is no MalmoPython.so in your Python_examples folder then it would indicate that you've downloaded the source, rather than installing a pre-built release. If you downloaded the source, you'll also need to build it - see the docs for details.

Hello!
Thanks for your replies.
https://github.com/Microsoft/malmo => I downloaded this as a .zip file
https://github.com/Microsoft/malmo/releases => And I downloaded Malmo-0.18.0-Linux-Debian-8.6-64bit.zip
I followed the instructions at install_linux.md
I copied /Desktop/Malmo-0.18.0-Linux-Debian-8.6-64bit/Python_Examples MalmopPython.so to Desktop/malmo-master/Malmo/samples/Python_examples
And I tried to build tutorial_1.py
But I got this error message "ImportError: libboost_chrono.so.1.55.0: cannot open shared object file: No such file or directory "
What's the reason of that?
Thank you so much!

I am facing a similar issue on Ubuntu 16.04, the error for me is
ImportError: libboost_date_time.so.1.61.0: cannot open shared object file: No such file or directory
I see a solution suggested here but involves building from source. Is there any way to get the pre-compiled binaries working?

@avisingh599 the problem is that the pre-compiled binaries were built against a different version of boost to the one on your machine. We've been looking at ways to make this simpler (see #392) but there's no easy fix from our end. On your machine, you have essentially two options - either upgrade (or downgrade) your boost to match the version we built against, or build Malmo yourself against your boost installation.
I'd recommend the second option - building Malmo is very simple on Linux - just follow the instructions here - https://github.com/Microsoft/malmo/blob/master/doc/build_linux.md - it shouldn't take long at all.
The issue you mentioned - #179 - is specifically for older OSs like Debian 7 and Ubuntu 12, where it is necessary to build boost. You shouldn't need to worry about that for Ubuntu 16.04.

Yep, I ultimately ended up building Malmo from source.

Great, I shall close this issue then, and if @ayyucedemirbas is still having problems that aren't captured elsewhere we can open a new issue for that.


[Migrated] Community fork time?

Originally from: https://github.com/Miserlou/Zappa/issues/2173 by MerreM
Context
It's been 4 months since this has seen any activity from a maintainer AFAIK, and I have multiple projects that depend on this.
I don't know about other users, but I think I'm getting to the point where I'd rather we made a community fork than just wait for the docs to come up again/some of the issues be resolved.
I say we, as I've never run an open source project and frankly don't have a clue what I'd be doing with it, but I can probably make some time to help out.
Expected Behavior
The project should be maintained, docs should be available some communication between users and maintainers would also be good. AFAIK The slack is down, the blog is down and the project is increasingly "rotting on the vine".
Actual Behavior
It's been dead since for ~ 4 months.
Possible Fix
Members of the community make a fork - organise and get to work.

zappa was migrated to the community managed zappa/Zappa repository in 2021.
closing.


Inventory Click Context Bug

The output of /version on my server is: This server is running Paper version git-Paper-126 (MC: 1.15.2) (Implementing API version 1.15.2-R0.1-SNAPSHOT)
The output of /version denizen on my server is: Denizen version 1.1.3-SNAPSHOT (build 4639-DEV)
(If relevant) A link to a paste of a script demonstrating the issue:
https://one.denizenscript.com/paste/66241
https://one.denizenscript.com/paste/66242
The issue is:
Essentially I'm using a dynamic inventory for NPC quests but something is wrong in Denizen's core or something because as I've tried in NPCDebugEvents when I click in the inventory of which <context.inventory> is only meant to reference the top one the unique identifier is different to the clicked inventory context so trying to compare <context.inventory> & <context.clicked_inventory>` is how I check that the player is only clicking in the top inventory. Opened again as I would like you to point out what is wrong with the script as you're clearly clouded by your own poor judgement and bias: http://prntscr.com/rimdg6

This is continued spam. As was stated in your previous issue https://github.com/DenizenScript/Denizen/issues/2170#issuecomment-600833489 continued posting of issues will result in a report to GitHub staff.


App crashes when pinging users with '@'

The Android app crashes when I try to ping a user in a message with '@'. More specifically, it crashes when typing the first letter after the '@'.

@Sam1301 this seems likely to be a bug one can fix relatively quickly...

@derAnfaenger thanks for reporting this! I couldn't reproduce this error. Can you provide with more details as to when this error occurs? When I tried to click on a user, the app didn't crash.

@Sam1301
This happens for the production build on my phone, version 1.1.0

Open the app.
Tap the pen icon in the lower left corner.
Tap the message box (where it says "Tap on a message to compose reply").
Enter '@', followed by some letter.
The app should crash.

Thanks @derAnfaenger  for reporting this bug. Submitted a pr for the same :+1:


M.2 - Link Sharing

"Link Sharing - The dapp shall allow the sharing of the signing link by: email, Matrix, Whatsapp, and Telegram."

done.


notebooks.zip file generated in Makefile does not include data subdirectory

The notebooks.zip file generated in
https://github.com/UCL-RITS/doctoral-programming-intro/blob/ab0e1a71d48e436c50167bce82db25a51f5d31d4/Makefile#L27-L28
which is generated to as part of the site_build.yml workflow to build the associated web pages (and linked to from there) does not include the 01-beginners/data subdirectory or the files within it, preventing easily running the associated exemplar notebook without separately downloading the data.

Semi-related: make clean also removes the directory (not sure if intentionally or not).


Implement Worker metadata caching

What changes are proposed in this pull request?
A temporary solution for metadata caching on worker
Why are the changes needed?
reduce the api call to ufs
Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including
add properties

alluxio-bot, merge this please.


Make clear that "psql" should not be used

In passing, improve formatting and whitespace.

Thanks for the review.
I have pushed a few trivial modifications, but after looking at the big picture, it seems that you are taking objection to practically everything in that page.
So perhaps it would be best to remove the whole thing and assume that Linux users who try to access Babelfish are just a lunatic fringe one should not specifically cater for. Because that is the audience for whom this page was written.
I am not qualified to write about accessing Babelfish on the command line on Windows, since I don't do Windows, and anyway that is probably going to be an even smaller minority than the Linux users who want to do that...

Perhaps this pull request should simply be closed. It seems like it is pretty unclear if there should be documentation for the command line at all, so it might be best to remove the whole page.
I see no way forward here.


Android from console missing .env

Hi,
I already did all the setup and linking of the react-native-config. However I cannot find the variables I defined in my .env when I run the project using react-native run-android.
If I print the config object I'm seeing this:
{"FLAVOR":"","DEBUG":true,"VERSION_CODE":1,"BUILD_TYPE":"debug","APPLICATION_ID":"myappid","VERSION_NAME":"0.1.0"}
and none of my defined variables are shown.
In the logs I'm seeing
************************** *** Missing .env file **** **************************
When I run the project from Android Studio it works fine,  and all the variables are filled.
I'm using react-native 0.54.2 and react-native-config 0.11.5.
iOS works fine.
I would really appreciate the help with this.
Thanks!

Hey I was able to fix it by opening the project in Android Studio, cleaning and build!
Thanks!

you need to add defaultEnvFile property
check here https://stackoverflow.com/questions/49140463/missing-env-files-when-i-use-react-native-config-for-android/60299691#60299691


e2e: fix error handling for goerr113 linter

goerr113 is a golang linter to check the errors handling
expressions. It warns about using wrapped static errors in
place of dynamic at multiple places. Issue reported: err113:
do not define dynamic errors, use wrapped static errors instead
So, err113 reports every == and != comparison for exact error type
variables except comparison to nil and io.EOF.
Also, any call of errors.New() and fmt.Errorf() methods are reported
except the calls used to initialise package-level variables and the
fmt.Errorf() calls wrapping the other errors.
Updates: #1227
Signed-off-by: Yati Padia<EMAIL_ADDRESS>

Using Verbs in place of gerunds looks cleaner IMO. Thoughts?

Yes True. Thanks for the suggestion.

@Madhu-1 @nixpanic would like to get a review from you guys on this PR. Do comment your suggestions. If this is fine with you all, I will follow the same in other files and make the changes.

As suggested by @Madhu-1  keeping this at hold for sometimes. It's gonna be lots of changes if we go to resolve the go-linter error in all the e2e files. So Currently, looking for the way to enable goerr113 in only internal files and disable in e2e to avoid these changes.
We can also create static errors for all the errors in one file and use it in all the places.
What's your thought in this @nixpanic @Yuggupta27 .

So Currently, looking for the way to enable goerr113 in only internal files and disable in e2e to avoid these changes.

The latest version of golangci-lint provides an option to have the following config
issues:
  # Excluding configuration per-path, per-linter, per-text and per-source
  exclude-rules:
    # Exclude known linters from partially hard-vendored code,
    # which is impossible to exclude via "nolint" comments.
    - path: e2e/
      text: "e2e"
      linters:
        - goerr113

refernce: https://golangci-lint.run/usage/configuration/#config-file

So Currently, looking for the way to enable goerr113 in only internal files and disable in e2e to avoid these changes.

The latest version of golangci-lint provides an option to have the following config
issues:
  # Excluding configuration per-path, per-linter, per-text and per-source
  exclude-rules:
    # Exclude known linters from partially hard-vendored code,
    # which is impossible to exclude via "nolint" comments.
    - path: e2e/
      text: "e2e"
      linters:
        - goerr113

refernce: https://golangci-lint.run/usage/configuration/#config-file

Thanks @Rakshith-R for the reference.

As suggested by @Madhu-1 keeping this at hold for sometimes. It's gonna be lots of changes if we go to resolve the go-linter error in all the e2e files. So Currently, looking for the way to enable goerr113 in only internal files and disable in e2e to avoid these changes.
We can also create static errors for all the errors in one file and use it in all the places.
What's your thought in this @nixpanic @Yuggupta27 .

Sure, I'm fine with resolving goerr13 warnings only of internal code for now. Just make sure that the issue is open so that TODO for doing the same for e2e is tracked.

Creating a error.go file per package, and place all the static errors (not new error types) in there is probably helpful. It will make it easier to re-use errors and prevents duplication. When you do this, please move existing errors from other files into the error.go file too.
Addressing the linter partially (for internal/) and enforcing it is definitely a good step. Make sure to add a
# TODO: enable linter for all code, see ceph/ceph-csi#1227

comment in the section where it gets excluded. We should still fix the issues later, as all code in the repository should be of equal high qualify.
Also, send lots of small PRs that are quick to get merged. That way you reduce the chance that you need to manually rebase and repost when other changes get included.

Creating a error.go file per package, and place all the static errors (not new error types) in there is probably helpful. It will make it easier to re-use errors and prevents duplication. When you do this, please move existing errors from other files into the error.go file too.
Addressing the linter partially (for internal/) and enforcing it is definitely a good step. Make sure to add a
# TODO: enable linter for all code, see ceph/ceph-csi#1227

comment in the section where it gets excluded. We should still fix the issues later, as all code in the repository should be of equal high qualify.
Also, send lots of small PRs that are quick to get merged. That way you reduce the chance that you need to manually rebase and repost when other changes get included.

sure @nixpanic . Thanks for your suggestion

@nixpanic and @Madhu-1 would like to get your reviews on this PR so that I can proceed with other files. Please ignore the ci error and merge conflicts. I will resolve them after we finalize the way for this. IMO, creating types for the errors and using it where ever needed, is better.
Creating static errors(as suggested by @nixpanic ) doesn't seem feasible to me, mentioned the reason above.
I can move ahead with this, if you guys are fine with it orelse suggestions are most welcomed.

@nixpanic and @Madhu-1 would like to get your reviews on this PR so that I can proceed with other files. Please ignore the ci error and merge conflicts. I will resolve them after we finalize the way for this. IMO, creating types for the errors and using it where ever needed, is better. Creating static errors(as suggested by @nixpanic ) doesn't seem feasible to me, mentioned the reason above. I can move ahead with this, if you guys are fine with it orelse suggestions are most welcomed.

For me this looks like an extra overhead. am fine not fixing this linter in code base.

@nixpanic and @Madhu-1 would like to get your reviews on this PR so that I can proceed with other files. Please ignore the ci error and merge conflicts. I will resolve them after we finalize the way for this. IMO, creating types for the errors and using it where ever needed, is better. Creating static errors(as suggested by @nixpanic ) doesn't seem feasible to me, mentioned the reason above. I can move ahead with this, if you guys are fine with it orelse suggestions are most welcomed.

For me this looks like an extra overhead. am fine not fixing this linter in code base.

In that case, I would remove the TODO from the linter and close the issue https://github.com/ceph/ceph-csi/issues/1227 with the explanation.

In that case, I would remove the TODO from the linter and close the issue #1227 with the explanation.

Instead of removing the TODO comment, leave a shirt description with link to the issue that has the explanation.
We might be able to do better when we introduce new errors.

Closing this PR: https://github.com/ceph/ceph-csi/issues/1227#issuecomment-1068957831


Sign in page has a lot of design issue. It must be designed through Figma [GSSoC'23]

Describe the bug
Th Sign in page looks very basic and unprofessional. I can redesign the page through figma and recode it.
To Reproduce
Steps to reproduce the behavior:

Go to Sign in page
See error

Expected behavior
Screenshots
Sign in page:

Desktop (please complete the following information):

OS: [e.g. iOS] Windows 11
Browser [e.g. chrome, safari] Chrome
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Please assign me this issue under GSSoC'23

Please assign me this issue under GSSoC'23


Filter out reads marked as contaminants?

Hello,
Is it possible to use the contamination flag to filter the reads marked as contaminants by chopper?
Thank you

If I understand your question correctly then yes, but you must use -c it with a reference genome of the expected contaminants, e.g. the lambda DNA used as control in ONT preps.


fix handling of array of non-primitive types

This is necessary to correctly handle arrays of non-primitive types which are covered by the new tests in ros2/system_tests#15.
This depends on PR ros2/rosidl_dds#23 which extends the introspection interface.

+1. I'll have to rebase my change set, but that's fine.

+1

+1


Question: Does ArchiveBox still crash if alot of stuff is saved? Saw video form 3 years ago.

Hello I was looking up more info on ArchiveBox as a alternative to wallabag because I cannot get it working but the only video I could find was from 3 years ago and in one part of the video Nick says that ArchiveBox could crash the computer because I guess there was alot of stuff saved? Has that been fixed yet?
If there is a certain amount of saved data that crashes the computer still? Is this a resource heavy program?

What video? url plz

https://youtu.be/7eoz_EU6-wQ?t=1243
Sorry I forgot to add that to the post and I love your hair.

oh yeah that's ancient, I fixed that problem long ago. that was before we even used a database, it was just text files. It can handle 100k+ URLs now but haven't tested too much higher than that yet.
and thanks!


Unable to run ./flow.tcl

Description
While running ./flow.tcl, the following error is displayed.
Environment
--
>>make survey || python3 ./env.py issue-survey
python3 ./env.py issue-survey
Kernel: Linux v5.13.0-40-generic
Distribution: ubuntu 20.04
Python: v3.8.10 (OK)
Container Engine: UNKNOWN vUNKNOWN (UNSUPPORTED)
OpenLane Git Version: 30f87f541d4e338b6793e46032350f26f64d8791
pip: INSTALLED
pip:venv: INSTALLED
---
>>docker --version
Docker version 20.10.0, build 7287ab3

PDK Version Verification Status: OK
Reproduction
Run ./flow.tcl
Expected Behaviour
Run normally
Logs
>> ./flow.tcl
can't find package json
    while executing
"package require json"
    (file "/home/saji/projects/OpenLane/scripts/tcl_commands/all.tcl" line 15)
    invoked from within
"source /home/saji/projects/OpenLane/scripts/tcl_commands/all.tcl"
    ("package ifneeded openlane 0.9" script)
    invoked from within
"package require openlane"
    (file "./flow.tcl" line 26)

Previous error
make test ran succesfully. However the docker repository needed to be hard coded in Makefile to pull it as it was empty (efabless/openlane:latest)

@saji87
Can you please list the commands used before running ./flow.tcl?
Seems you're not given -design <Design_Name>
Make sure followed below steps or follow it, it will resolve your issue.
cd OpenLane
make mount
./flow.tcl -design spm

My issue seems to be error in OPENLANE_IMAGE_NAME in Makefile. Somehow its empty.
ifeq ($(OPENLANE_IMAGE_NAME),)
OPENLANE_DOCKER_TAG ?= $(shell $(PYTHON_BIN) ./dependencies/get_tag.py)
ifneq ($(OPENLANE_DOCKER_TAG),)
export OPENLANE_IMAGE_NAME ?= efabless/openlane:$(OPENLANE_DOCKER_TAG)
endif
endif
`
After hardcoding it to efabless/openlane the run is succesful
[SUCCESS]: Flow complete. [INFO]: Note that the following warnings have been generated: ..............................
May I ask what THREADS ?= 1  stands for in Makefile

Can you display?
which python3

/usr/bin/python3

You need to do following command before make mount:
OPENLANE_IMAGE_NAME=efabless/openlane:current make mount

Make sure pyhton3 default points to python3.8

>>make survey || python3 ./env.py issue-survey python3 ./env.py issue-survey Kernel: Linux v5.13.0-40-generic Distribution: ubuntu 20.04 Python: v3.8.10 (OK)

@saji87
If your issue got fixed, you may close this issue.


"Cannot read property 'Ua' of undefined" in v2.0.23

When upgrading (yarn remove xcomponent && yarn add xcomponent) from 2.0.22 to 2.0.23, I'm getting the following error in my browser console:
Cannot read property 'Ua' of undefined

When trying to figure out why this is happening I built the dist files from the repo (as of 7f83bf2) and copied into my node_modules. Interesting enough, everything is then working fine. Which leads me to believe that the dist folder on npm is not up to speed, could this be correct?
Building this way:
git clone ...
npm install
./node_modules/.bin/gulp build
cp dist/xcomponent.js xxx/node_modules/xcomponent/dist

I can produce same error in 2.0.23

Demo Site is throwing the same error.

Fixed. Thanks for the heads up. I had uglify prop-mangling enabled on my local when I merged and built the latest PR. Gotta add something to my publish script to prevent any un-staged changes making it into /dist. Sorry all!

fix is working. thanks for the prompt response !


hcm: adding a knob for setting scheme

Adding the option to
Risk Level: low (config guarded code)
Testing: unit testing
Docs Changes: n/a
Release Notes: inline
Part of #14587
Fixes #17105

@phlax added the new config here and confirmed it no longer redirects

@alyssawilk i picked the changes in this pr, built envoy with it and tested with the default config
not sure if this pr is still wip, but using the built envoy i got three different results

segfault - i think in Envoy::Http::HeaderString::setCopy()
400 bad response and some wierdly mangled headers 'x-forwarded-proto', '�oV��o'
worked perfectly

i have log traces from each of the outcomes if its helpful
worth mentioning is that whichever of the outcomes occurred the server continued with that until being restarted - ie if it worked once it continued working perfectly. It never gets the redirects problem. This is unlike envoy main in which you start the server and sometimes it works and sometimes it redirects - restarting has no effect
fwiw i tested out updating the default config to point to google and that also got spun out on redirects, so its not just the envoyproxy site i think
im wondering more generally - if this used to work without having to set anything extra - and that was the "default" demo config - can we make it work that way again - at least initially ?

so the default demo config had a listener which was listening in the clear, and then forwarding that content over TLS. Envoy proxy expects TLS traffic and now can detect (via x-forwarded-proto) that the request was sent in cleartext and is so not actually secure. The new default behavior is closing a fairly serious security loophole.  We could address by either having Envoy proxy allow http traffic, or making sure our example uses TLS rather than sending https urls in the clear :-)

ill test this with #17200 now...

worked perfectly every time! great, thanks

@phlax I'm going to merge as-is - lmk if you want a follow up with general docs clean up


quic: do not hard code "h3" APLN in EnvoyQuicProofSource

QUICHE interfaces in quic::ProofSource doesn't pass around ALPN negotiated by BoringSsl, but Envoy filter chain retrieval uses ALPN as part of the query. Right now, we hard-code h3 as the ALPN when we construct a ConnectionSocket for server session, but we should make the negotiated APLN available from QUICHE, and use it in Envoy glue code.

I'm not surprised that quic::ProofSource doesn't have the ALPN, but I'm slightly surprised that it might need it. Can you say more about why we need ALPN from ProofSource as opposed to from, say, quic::QuicSession?

EnvoyQuicProofSource does filter chain retrieval in order to get certs or private key to sign. And the FilterChainManager needs ALPN as part of the query. We might not have to expose ALPN directly in ProofSource, but something that can expose ALPN, i.e. QuicSession or a context object.

need a non-stable label


Unset OpenAI Key Error

          Can you change the error to be like?

! start with a bang

If this is not set or is an empty string then the OpenAI API will throw an error by default anyway, should I still implement null and throw our own error?

It would provide clarity to our early users if we explain how to enable this feature. Basically it should say something like
"You must configure the openai-api-key property in the bot configuration in order to use AI powered features."
Originally posted by @pavlovcik in https://github.com/ubiquity/ubiquibot/pull/748#discussion_r1326295811

@keyrxng this is for you

/start

/start

@already done just as part of /ask, will cherry pick now that /ask has been merged

@already done just as part of /ask, will cherry pick now that /ask has been merged

My bad, I didn't see any PR referenced by you so thought it was up for grabs.
thanks for telling I'll pick something else!

/stop

already done just as part of /ask, will cherry pick now that /ask has been merged

My bad, I didn't see any PR referenced by you so thought it was up for grabs. thanks for telling I'll pick something else!

that's my mistake should have noted this my bad dude

/ask

/start


Automatic pull request for presentation presentation-reflex-practical-functional-reactive-programming-frp-in-haskell.md

Created via the Hask Anything web interface. If this contains copyrighted material, please ask the author if we are allowed to replicate it here with attribution.

@m0rphism Your branch is still using the old circle.yml file, so it's still failing. Is there a way to fast-forward your branch so it includes the new file? Weird that it doesn't use mine :/


Update chrono to pass audit

Update chrono dependency and reduce its features to pass audit.
cargo audit
    Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
      Loaded 433 security advisories (from /home/balrog/.cargo/advisory-db)
    Updating crates.io index
    Scanning Cargo.lock for vulnerabilities (55 crate dependencies)

Fix https://github.com/mattnenterprise/rust-ftp/issues/108


Does glaredb have plans to support fully distributed execution?

It's interesting to know your plans for distributed execution like arrow-ballista

We do have plans to support distributed execution, but we're still in the planning phases of that.
As a side note, we do have a form of distributed execution by way of hybrid execution: https://docs.glaredb.com/glaredb/hybrid-execution/. The aim here being able to pool the resources of your Cloud deployment and laptop when executing queries.

We do have plans to support distributed execution, but we're still in the planning phases of that.
As a side note, we do have a form of distributed execution by way of hybrid execution: https://docs.glaredb.com/glaredb/hybrid-execution/. The aim here being able to pool the resources of your Cloud deployment and laptop when executing queries.

Cool, looking forward to see the design and roadmap.

We're tracking the work associated with this epic in #1867, and I think the answer is very firmly "yes".
I'm going to go ahead and close this, but feel free to reach out with more questions in the future.


Support yarn 1

Codecov Report

Merging #10 (b2ecbab) into main (c44dd07) will increase coverage by 4.40%.
The diff coverage is 96.00%.

@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
+ Coverage   83.14%   87.55%   +4.40%
==========================================
  Files          15       15
  Lines         712      731      +19
==========================================
+ Hits          592      640      +48
+ Misses        120       91      -29

Impacted Files
Coverage Δ

src/lib.sh
96.11% <95.91%> (+0.58%)
:arrow_up:

src/dev/lint.sh
100.00% <100.00%> (+100.00%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c44dd07...b2ecbab. Read the comment docs.


Work directly with or autoimport OpenAPI V3 spec files

I can import my openapi.yaml file as a new collection in bruno. But, that's it.
If I generate a new OpenAPI spec file using swagger I have to remove and add the collection again.

Am I doing something wrong?
If not, are there any plans to use OpenAPI spec files directly? Or maybe have some kind of auto import?

@sanjai0py @helloanoop This is pretty big, if you ask me, feature currently missing from Bruno.
What is the way to go when working with OpenApi specs that change over time?

IMO Bruno CLI should evolve to give us an option to import/update collections based on an OpenAPI spec.
In Postman, you can import your OpenApi spec, which then generates your collections.
If you update the spec, you can then update the collections.
Our use case is that our CI pipelines generates our OpenApi specs from our code. It would then be useful if the CLI could updates our Bruno collections automatically with the newly generated OpenApi.

I would like to use something like this:
bru import --collection {collection_path} --spec-file ./openapi.json

Where bruno update exiting collection and keeps envs, scripts, tests etc. But idk how to handle base_url env in this case for example. Maybe bruno should be smart about it, and compare path endings?

I'm currently developing an application based on OpenAPI specs that are still in development as well, I'm really mising the option to update the collection based on the new specs. A start could even be throwing away / regenerating the actual request files but keeping everything else e.g. environment configurations.


subfinder: 2.5.7 -> 2.5.8

Diff: https://github.com/projectdiscovery/subfinder/compare/v2.5.7...v2.5.8
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.


clear joystick state on disconnection

Previously, the joystick helper methods (e.g is_joy_button_pressed()) returned out-dated values when called after the device has been (unexpectedly) disconnected, leading to undesired behaviour.
Well, one could connect on the joy_connection_changed signal and stop input polling if necessary, but we shouldn't expect this. And the joystick state should be clean anyway when there's no device.

I'd tag this as "bug" instead of "enhancement" ^^

Not that it changes much ;)


Improve MDL thin-film support

push down the thin film parameters to the nodes that can use them, i.e., dielectric, conductor and generalized schlick

removed additional inputs, that transport thin film parameters, from the public material interface by making them non-editable

make sure thin_film will not result in undefined behavior when passing zeros as parameters (0 thickness disables thin_film but 0 ior is invalid)

Vertical Layering, push base deeper than one level, needs review, contains TODOs for mix, add, and multiply (If not 100% sure this is correct, we can drop that commit and postpone.

Hello! I'm seeing a regression when I use these changes with my MaterialX/MDL-based renderer:

Before
After

I've prepared a glTF+mtlx version of this asset in hope that it can be reproduced with the MDL SDK DXR example:
maneki_gltf.zip

I can reproduce it. And it showed another problem as well:
When reading the the normal texture, the output is color and connecting that to a float3 in MDL requires and explicit type construction (because color could be spectral).
But I'm a bit surprised about the missing gold here. I'll investigate and keep you posted.

Looking into the regression and it revealed an MDL bug which will be fixed with MDL 1.8. Meanwhile, I added a workaround to detect the problematic case and handle it correctly.

If we want the vec3 version of USDUVTexture how about we bring it up in the MTLX/USD channel and see what folks have to say.
IMO, it's an implementation variant and not a spec change but would need to discuss as it still produces 2 implementation signature variants for USD to consume.

@jstone-lucasfilm and @kwokcb is there something outstanding for this PR? I believe the type of the usd texture return rgb is a different topic discussed in https://github.com/AcademySoftwareFoundation/MaterialX/issues/1038

@krohmerNV As long as the original regression noted by @pablode has been addressed, I'm not aware of any outstanding issues, and I'll plan to take a closer look at these changes soon.


Can we introduce tags on the Tracer interface?

Some of my users want to define tags that should apply to all spans coming from a service, like the git commit SHA. However, depending on the framework used to build the service, the tracer is sometimes initialized on their behalf elsewhere, so that they can only get a reference to opentracing.Tracer, not to a concrete implementation.
cc @bensigelman @dkuebric

Why would you want to redundantly tag spans?  I guess having it at the tracer level would allow the tracer to abstract it out and manage that themselves, but my first thought for something like git commit is have the instrumentation report it (and other service-level info) in top-level span for the service.

@dkuebric it would be up to the tracer how to use tracer-level tags, it can attach them to all spans or to the first span in the process. It can also do various optimizations with those and send them out of process only once per whole batch of spans.  Basically I would expect the same level of support for tracer tags as for span tags, i.e. - no guarantees, but if the tracer does choose to persist those tags then the traces can be found by the tag value.

@yurishkuro on the one hand I think this is a fine idea, but on the other I don't see why it needs to be a part of the OpenTracing spec yet... any Tracer implementation is welcome to take a set of tags to apply to all spans it creates, and that can be done cleanly at Tracer init time. If that pattern is particularly valuable, we can upgrade the concept to the OpenTracing layer and/or provide a Tracer adapter that defers all real work to some wrapped Tracer but interposes on StartSpan with the provided tags.

:+1:

@bensigelman the problem is that the end user code has no way to give the Tracer a custom set of tags. If the code explicitly instantiates the Tracer implementation, then yes it can use a private API to pass any custom tags, but in many cases the tracer is instantiated by some common framework that the service is using, and the only way the service can get access to the tracer is via something like opentracing.GlobalTracer().

@yurishkuro ah, I didn't read the issue carefully enough (you were clear about init time, I just didn't parse it correctly). Hm... It feels like an encapsulation failure to have some process subcomponent deciding which tags should apply to all spans in that process, esp if that subcomponent isn't important enough to have a say in process-level initialization. For spans originating in the subcomponent, something like the Tracer wrapper I proposed above would work well. If it's truly important for the tags to apply to all Spans started by the Tracer... then there's a problem. I'd be curious to talk through the specifics in more detail over VC if that works...

We didn't find this to be a problem in real use cases, so closing.


gradle_6: mark very insecure

Every Gradle before v7 (including our beloved gradle_6) is vulnerable to a number of vulnerabiliites:

CVE-2021-29429, affecting confidentiality
CVE-2021-29427, affecting confidentiality and can lead to dependency poisoning
CVE-2021-29428, a privilege escalation involving the temp dir
CVE-2021-32751, arbitrary code execution

To mark the package insecure, I had to add a meta attribute that is merged into the existing meta produced by the package. Eval succeeds (fails with insecure warning) when I tested this.
Let me know if the messages in knownVulnerabilities are too verbose.
cc the following maintainers, whose packages would fail to build after the package is marked insecure:

armitage, @emilytrau
shattered-pixel-dungeon, unmaintained
jd-gui, @thoughtpolice

Closes #132127, #147881, #124636, #124635

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

I'm wondering if we should remove this package after the feature freeze.


Emojis on dark mode look wrong.

Preflight Checklist

[x ] I agree to follow the Code of Conduct that this project adheres to.
[x ] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
Emojis looks weird in dark mode.
To Reproduce
Steps to reproduce the behavior:

Add an emoji of the type on the canvas
Go to 'appearance'
Click on 'dark'

Expected behavior
I would think that the emojis would be the same as I selected or copied but it shows incorrect colors.
Screenshots

draw.io version (In the Help->About menu of the draw.io editor):

draw.io version [21.6.7]

Desktop (please complete the following information):

OS: [Windows 11]
Browser [Brave]

Additional context
They look ok in light mode, but I guess emojis should not change despite style mode selected.

Also, saving the file breaks the emoji. when you reload or open a file (I've tried XML as .drawio in github and desktop), it doesn't shows anymore. Both in web and desktop app.

Where does this emoji window come from in the first post?

Where does this emoji window come from in the first post?

From windows, "Win + . " launchs the emoji keyboard, but it's not really important, you can copy the emoji from another place and the results are the same. I just used like that to make it fit in a smaller screenshot.

#3701 I think is related to this. I'll close this issue and follow that discussion.


how to use relative path,

the following is my code:
Asset.fromModule(require('../../../assets/big_buck_bunny.mp4')).uri
but can't run.
so , how to use local assets file

Hello, I have used the following to read the local asset file:
const file = Asset.fromModule(require("../docs/myfile.pdf")); file.downloadAsync().then((doc) => {         setState({  localFilePath: doc.localUri }); })


Server request content streams

Handler that adds streaming requests support as proposed in #137.
This handler only creates streams when strictly necessary. Besides that, it allows the user to not consume the entire request before sending out a response.
In terms of performance it is roughly equal to that of non-streaming for small <=6KB requests. For larger requests it tends to be faster than non-streaming for larger request bodies. These observations are only based on my machine and ran with the HelloWorldAdvanced example app.
Lastly, it also fixes a bug currently in the main branch where subsequent responses were causing Netty to throw exceptions because of LAST_EMPTY_CONTENT not being written correctly.

Lastly, it also fixes a bug currently in the main branch where subsequent responses were causing Netty to throw exceptions because of LAST_EMPTY_CONTENT not being written correctly.
I am moving this to separate PR as this is a blocker to run benchmarks @DJLemkes

Let me know what you think. More then happy to make changes if required :).

This is great @DJLemkes! Will have look at it.

@tusharmath sorry to tag you again :). I can do another rebase when you're ready to review. And again, happy to make changes. Would it help if I added a description of my benchmark setup (used go-wrk to POST request bodies as well).

@DJLemkes Update: I am still doing some POCs on how to incorporate streaming capabilities to ZIO Http without compromising on performance. Thought I should post it here to keep you also updated :)

Will get this out soon. We have a design that is promising and reasonably performant.

Will get this out soon. We have a design that is promising and reasonably performant.


Fix typo in test

Fixes a minor typo in test/request/ip.js (remoteAddress instead of removeAddress).

+1


GitHub Actions test: Which file contains the test results?

build/hello-world/junit-report-hello-world.xml
build/leap/junit-report-leap.xml

Test results: https://github.com/exercism/free-pascal/pull/21/checks?check_run_id=23603820352

Arrgghh

Ready for review.  Please Squash and merge.
Test results: https://github.com/exercism/free-pascal/pull/21/checks?check_run_id=23603820352

@ErikSchierboom I think this is ready to be merged if you agree.

@cclauss Thanks for the work, but before I can review this, could you please explain to me why this change is neccessary?

The idea was to run the tests on every pull request (continuous integration) and also to generate a graphical dashboard to tests passed/failed... https://github.com/exercism/free-pascal/pull/21/checks?check_run_id=23603820352

The idea was to run the tests on every pull request (continuous integration) and also to generate a graphical dashboard of the tests passed/failed... https://github.com/exercism/free-pascal/pull/21/checks?check_run_id=23603820352

But did it not work before? In this CI run from November 2023 it perfectly generates the same output: https://github.com/exercism/free-pascal/runs/18703399543
Did something change in the dorny test reporter that it suddendly stopped working, or...?

Tested it and the not-working of publishing test results was intruced by you in this commit: https://github.com/exercism/free-pascal/commit/f478c00734199818cb94a0d5dd0352711e13e27c
I think it is a better approach to revert or otherwise restore the previous behaviour, than adding a second workflow and hardcoding testresult files inside the workflow.
Will work on a different approach that dosnt need to include all test paths hardcoded inside the workflow.

Closing in favor of #22 which looks like a more sane approach.

#22

MUCH better!  Thanks much @Mai-Lapyst
https://github.com/exercism/free-pascal/pull/21/checks?check_run_id=23713501927

MUCH better! Thanks much @Mai-Lapyst

Thanks to for spotting this issue in the first place :)


[Bug] Unable to edit bridge on mobile

Works great on desktop but on mobile it doesn't resize quite right so the edit is off to the right unable to be seen.
Pixel 7 using Chrome

I see that it's not really responsive, but for me it's still possible. I can simply scroll to the right.

Interesting. Mine doesn't let me scroll so the edit and the right column of the entity list is off screen.
Definitely not a big deal though.
For a brief moment the QR code is above the bridge details and you can see the edit but then the QR moves to the right and pushes it off screen.

My phone also doesn't let me scroll to the right. I'll record a screen recording and attach it here in a moment.


Broken Drop down in Simulator

Describe the bug
The drop down menus in the navbar on the simulator window appears when the cursor is hovered on a particular section. But it does not go back when the pointer is removed from the section heading.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://circuitverse.org/simulator'
Hover on any section heading
Remove the pointer from the heading
See error

Expected behavior
The drop down for the sections should go back to its original state after the pointer has been removed fromo the section heading.
Screenshots

(The pointer/cursor had been removed from the Tools heading at this point.)

@aayush-05, I would like to fix this issue. So can I work on it?

Hey @ac030540 !
I am not a contributer to this project as of now.
You can ask @satu0king or @ankitkataria , if they can assign this issue to you.

Hey @ac030540 !
I am not a contributer to this project as of now.
You can ask @satu0king or @ankitkataria , if they can assign this issue to you.

Okay. Thanks.

@satu0king , I would like to fix this issue. So can I work on it?

@satu0king , I would like to fix this issue. So can I work on it?

@ankitkataria ?

Personally I prefer the way it is right now. It's pretty similar to the Google Docs menubar. @satu0king what do you think?

Then we can make it more uniform like the Google Docs menubar, like since the menu closes back only when the heading is clicked upon. It should open only on clicking of the heading, not when hovered.


python36Packages.pyRFC3339: 0.2 -> 1.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.6-pyrfc3339/versions.
meta.description for python36Packages.pyRFC3339 is: '"Generate and parse RFC 3339 timestamps"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.1 with grep in /nix/store/vphk7gvv27sh09v2bwwsg60bk956w86w-python3.6-pyRFC3339-1.1

directory tree listing: https://gist.github.com/43503ddb005724ccce41f8cba7d01ece

du listing: https://gist.github.com/e4951eb3f14bcc07273d293955765fb5

Outpath report (click to expand)

Outpath difference report
23 total rebuild paths
6 package rebuilds
6 x86_64-linux rebuilds
6 i686-linux rebuilds
5 x86_64-darwin rebuilds
6 aarch64-linux rebuilds
First ten rebuilds by attrpath
certbot
python27Packages.acme
python27Packages.pyRFC3339
python36Packages.acme
python36Packages.pyRFC3339
simp_le

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vphk7gvv27sh09v2bwwsg60bk956w86w-python3.6-pyRFC3339-1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A python36Packages.pyRFC3339 https://github.com/r-ryantm/nixpkgs/archive/05d5474e6d908871295713b17a48a340ac30e032.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vphk7gvv27sh09v2bwwsg60bk956w86w-python3.6-pyRFC3339-1.1
ls -la /nix/store/vphk7gvv27sh09v2bwwsg60bk956w86w-python3.6-pyRFC3339-1.1/bin

Success on x86_64-darwin (full log)
Attempted: python36Packages.pyRFC3339
Partial log (click to expand)
/nix/store/zx08zp64vl52jnvwgy485wx6l4q842zh-python3.6-nose-1.3.7/lib/python3.6/site-packages/nose/config.py:264: RuntimeWarning: Option 'cover-html-dir' in config file 'setup.cfg' ignored: excluded by runtime environment
  warn(msg, RuntimeWarning)
/nix/store/zx08zp64vl52jnvwgy485wx6l4q842zh-python3.6-nose-1.3.7/lib/python3.6/site-packages/nose/config.py:264: RuntimeWarning: Option 'with-doctest' in config file 'setup.cfg' ignored: excluded by runtime environment
  warn(msg, RuntimeWarning)

----------------------------------------------------------------------
Ran 0 tests in 0.008s

OK
/nix/store/ds4pvxhlcw64d4p4j7zb3pc7vpjvwqd6-python3.6-pyRFC3339-1.1

Success on x86_64-linux (full log)
Attempted: python36Packages.pyRFC3339
Partial log (click to expand)
/nix/store/khj4yg8583s59wyg1vijj005qvaqiqnk-python3.6-nose-1.3.7/lib/python3.6/site-packages/nose/config.py:264: RuntimeWarning: Option 'cover-html-dir' in config file 'setup.cfg' ignored: excluded by runtime environment
  warn(msg, RuntimeWarning)
/nix/store/khj4yg8583s59wyg1vijj005qvaqiqnk-python3.6-nose-1.3.7/lib/python3.6/site-packages/nose/config.py:264: RuntimeWarning: Option 'with-doctest' in config file 'setup.cfg' ignored: excluded by runtime environment
  warn(msg, RuntimeWarning)

----------------------------------------------------------------------
Ran 0 tests in 0.006s

OK
/nix/store/vphk7gvv27sh09v2bwwsg60bk956w86w-python3.6-pyRFC3339-1.1

Success on aarch64-linux (full log)
Attempted: python36Packages.pyRFC3339
Partial log (click to expand)
/nix/store/99b2qc8sqvq9snqssyinkmjx090k2za2-python3.6-nose-1.3.7/lib/python3.6/site-packages/nose/config.py:264: RuntimeWarning: Option 'cover-html-dir' in config file 'setup.cfg' ignored: excluded by runtime environment
  warn(msg, RuntimeWarning)
/nix/store/99b2qc8sqvq9snqssyinkmjx090k2za2-python3.6-nose-1.3.7/lib/python3.6/site-packages/nose/config.py:264: RuntimeWarning: Option 'with-doctest' in config file 'setup.cfg' ignored: excluded by runtime environment
  warn(msg, RuntimeWarning)

----------------------------------------------------------------------
Ran 0 tests in 0.011s

OK
/nix/store/kz00m8wkbqjz7555m1h9fiqzbivb3pja-python3.6-pyRFC3339-1.1


⚠ Exoticaz has degraded performance

In 45c0838, Exoticaz ($EZ) experienced degraded performance:

HTTP code: 200
Response time: 1859 ms

Resolved: Exoticaz performance has improved in a4d8266 after 9 minutes.


Page template system

The page template system (usingPageProcessors) doesnt really feel intuitive to me right now. Open for suggestions on how to improve stuff.

Done, thanks to jinja