Update failed： 504 Gateway Time-out 504 Gateway Time-out nginx/1.19.1

Error description:
Update failed： 504 Gateway Time-out 504 Gateway Time-out nginx/1.19.1
Steps to reproduce
While I am installing or updating the plug-in, it will be always failed.
Expected result
Plug-in installation or update successful.
Error result
Update failed： 504 Gateway Time-out 504 Gateway Time-out nginx/1.19.1
Comments
How to fix the problem?

This repo has no plugin.. does it? and if you are talking about the workpress.. it might has nothing to do with the proxy. Please open this issu in the wordpress repo.

Hi @evertramos - I know this is old, but I have a similar issue.  In my case, I have a site that sometimes takes a minute to respond when it is under heavy load.  And I would like Nginx to wait longer for it to load without returning 504.  How can I increase the timeout (time that Nginx will wait for the backend site)?

Hello @maltokyo you can add any nginx general settings to this path https://github.com/evertramos/docker-compose-letsencrypt-nginx-proxy-companion/tree/master/conf.d and algo set the any default proxy setting and site settings, please check:

https://github.com/nginx-proxy/nginx-proxy#custom-nginx-configuration
https://github.com/nginx-proxy/nginx-proxy#per-virtual_host

Thanks!!


Templates and revisions

Resources at the challenge level can be used as Templates for the content of new projects (screenshot 1)
In your project at a current event, you can see what role(s) are missing in your team (screenshot 2)
Progression through project stages is also now shown in the log, in a light blue box (screenshot 3)
The projects are now versioned, and can be reverted from the log tab - currently administrators only (screenshot 3)
It is somewhat easier to see at a glance what role(s) your team members have.
The "Connect" button is now also visible in the event page.
Editing and formatting of the new event recommendations screen.
Searching for projects, user profile, event buttons, log and tips UI tweaks.
After uploading a Data Package you see the events that were updated.

Screenshots

(1) New project screen, with a template selection menu.

(2) Project log, with stage progression ("Find" completed) and highlighting a new button to revert to a previous version.

(3) A list of roles which are still missing from the current project team.

Codecov Report

Merging #291 (29f853d) into main (ea47174) will decrease coverage by 0.10%.
The diff coverage is 27.27%.

@@            Coverage Diff             @@
##             main     #291      +/-   ##
==========================================
- Coverage   45.09%   44.98%   -0.11%
==========================================
  Files          30       30
  Lines        3371     3397      +26
==========================================
+ Hits         1520     1528       +8
- Misses       1851     1869      +18

Impacted Files
Coverage Δ

dribdat/aggregation.py
18.63% <ø> (ø)

dribdat/user/constants.py
35.13% <0.00%> (-0.65%)
:arrow_down:

dribdat/public/project.py
22.47% <15.78%> (-0.24%)
:arrow_down:

dribdat/user/models.py
57.91% <60.00%> (+0.06%)
: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 ea47174...29f853d. Read the comment docs.

The project template feature may render #283 unnecessary. It would still be interesting to "swap in" a tool in each stage. More practically, we should recommend one tool == one prototype.

Tested and merged.


mautrix-signal: 0.4.3 -> unstable-2023-12-30

Description of changes

mautrix-signal's latest released version v0.4.3 still uses the Python codebase
which is broken for new devices, see https://github.com/mautrix/signal/issues/388.
The new Go version fixes this by using the official libsignal as a library and
can be upgraded to directly from the Python version.
Fixes #248379.
If anyone wants to try this out in combination with https://github.com/NixOS/nixpkgs/pull/277368, I also created a combined branch of these changes based on nixos-23.11: github:niklaskorz/nixpkgs/nixos-23.11-mautrix-signal.
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.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.

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

Nice! Since I'm currently locked out of my bridge because of the 405 error, I'll happily test this soonish! :)

Bridge is working fine btw :+1:

I'm a bit unsure whether libsignal-ffi should be its own package or be part of the mautrix-signal package. Right now, this PR adds libsignal-ffi at version 0.36.1 while the latest version is 0.37.0. I tried running mautrix-signal with 0.37.0, but this leads to errors, so the version of libsignal-ffi must match unfortunately: https://github.com/mautrix/signal/issues/401

I'm a bit unsure whether libsignal-ffi should be its own package or be part of the mautrix-signal package

At the end of the day it's our job to provide a package set that works together, not a bunch of packages at the latest version (of course, that's not a hard rule, but something we should be keeping in mind generally).
My suggestion would be to still leave a warning in the libsignal-ffi nix expression, but as amintainer you should be pinged anyways on updates.
While you're at it, feel free to also add me to the list of maintainers for mautrix-signal :)

@Ma27 alright, done :)
@expipiplus1 any remarks from your side? do you still want to maintain the mautrix-signal package?


Change main to reference index.js to fix NPM installing

When I NPM installed this package, I was getting an error when trying to require or import it.
Turns out that main was pointing to a non-existant file.

I don't get any errors installing or requiring, nor Travis, not sure why though because this seems wrong. Anyway, thanks for spotting and fixing this. From what I've read it could even be removed because apparently index.js is the default if not specified.


Allow the scanning of QR codes for API key entry

The website will soon support QR codes for API keys, so the apps need to as well.

Completed for Android, iOS is in the pipeline.


remove HTTP2 package skeleton

Which problem is this PR solving?

Remove un-implemented HTTP2 package, will add it later once we start working on it.

Codecov Report

Merging #676 into master will decrease coverage by 1.73%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #676      +/-   ##
==========================================
- Coverage   91.56%   89.83%   -1.74%
==========================================
  Files         217      214       -3
  Lines       10186    10190       +4
  Branches      911      932      +21
==========================================
- Hits         9327     9154     -173
- Misses        859     1036     +177

Impacted Files
Coverage Δ

packages/opentelemetry-core/test/utils/url.test.ts
50% <0%> (-50%)
:arrow_down:

...pentelemetry-core/test/internal/validators.test.ts
50% <0%> (-50%)
:arrow_down:

...elemetry-core/test/trace/spancontext-utils.test.ts
55.55% <0%> (-44.45%)
:arrow_down:

...lemetry-core/test/trace/ProbabilitySampler.test.ts
56.52% <0%> (-43.48%)
:arrow_down:

...s/opentelemetry-core/test/trace/NoopTracer.test.ts
60% <0%> (-40%)
:arrow_down:

...s/opentelemetry-core/test/context/B3Format.test.ts
63.39% <0%> (-36.61%)
:arrow_down:

...ges/opentelemetry-core/test/trace/NoopSpan.test.ts
63.63% <0%> (-36.37%)
:arrow_down:

...s/opentelemetry-core/test/trace/tracestate.test.ts
65.06% <0%> (-34.94%)
:arrow_down:

...ntelemetry-core/test/trace/NoRecordingSpan.test.ts
71.42% <0%> (-28.58%)
:arrow_down:

...ackages/opentelemetry-core/src/platform/node/id.ts
71.42% <0%> (-28.58%)
:arrow_down:

... and 27 more


Don't touch files

Fixes #1540

Q
A

Bug fix?
Yes

New feature?
No

BC breaks?
Yes or No

Deprecations?
No

Fixed tickets
#1540

Removes the touch so that non-existing files are not created, possibly in an invalid format.

I'm afraid what this is breaking change. How can we figure this out?

I have the same feeling... this might be a breaking change... maybe this should be feature-flagged instead of beeing deleted, so you can opt-out from this touch call in your recipe.

I think we need to see history of this addition and why it was introduced in first place.

Yeah I was trying to, but at some time there was a large refactor so the history was hard to track down.
The symlink would still be created right? Just as a broken link, which (imho) is easier to notice then an empty file.

I think we need to see history of this addition and why it was introduced in first place.

Apparently it was introduced along with whole deploy:shared task in 2014:
https://github.com/deployphp/deployer/commit/339baedd143ac7f7b393c9fd43959b729d0d64f5#diff-17bfdc9b1a5d2375e8f0241c0bee0619R84

I guess we could also show a warning message when this doesn't exist, or fail.
But imho it seems to be more dangerous/unexpected to create an empty file, because some frameworks might check for the existence of a file and then require it or change behavior.

@gharlan your are right. Actually shared_dirs also created. What about them?
I think this is kind of breaking changes. I think to add this to v7 milestone.

So another use-case about this:
Magento has a 'maintenance' flag in 'var/.maintenance.flag'. If that exists, it's in maintenance mode, otherwise not. Currently you can't share that file, because if it doesn't exist you create it, so Magento thinks it's in maintenance mode..

Agree. Will be better to not create file. What about shared dirs?

If you ask me, I would answer; no shared directory creation and an showing an warning message is enough. Because this situation will only occurs when you bootstrap the project. In our situation the shared directories contains an .gitkeep file to prevent from not existing.

What about a flag to disable/enable this feature... and disabled by default, because otherwise it would be BC break

I think one more flag is redundant. Will merge in into v7 major release.


log4stach elastic search appender memory leak

Hey,
I'm facing major issue with my .Net process. At some random point the http appender stucks and the logs are stored in memory (stops sending to Elastic) until the process is killing the server.
Did you face this problem? I'm "shipping" around 1million logs per second.

I'm having a very similar issue.

Can you share your configuration?
I think you can work around this if you ok with loosing few log messages in case of overflow

I'd be happy with some lost messages right now!
If there isn't a way / plan for a flush-on-payload-size limit feature, that'd be useful.  I'm using AWS OpenSearch and we're limited to 10Mb per message.  With the settings below as well as some application-level message size capping, we're regularly blowing past that.
<?xml version="1.0" encoding="utf-8"?>
<log4net>
	<root>
		<level value="ALL" />
		<appender-ref ref="elasticsearch" />
	</root>
	<appender name="elasticsearch" type="log4stash.ElasticSearchAppender, log4stash">
		<Server><!-- redacted --></Server>
		<Port>443</Port>
		<AllowSelfSignedServerCert>False</AllowSelfSignedServerCert>
		<Ssl>True</Ssl>
		<AuthenticationMethod>
			<Basic>
				<Username><!-- redacted --></Username>
				<Password><!-- redacted --></Password>
			</Basic>
		</AuthenticationMethod>

		<IndexName>%{environment}-%{application}-%{log.level}-%{+yyyy-MM-dd}</IndexName>
		<IndexType>_doc</IndexType>
		<IndexAsync>False</IndexAsync>

		<BulkSize>256</BulkSize><!-- we're getting lots of payload too large messages -->
		<BulkIdleTimeout>5000</BulkIdleTimeout>
		<DropEventsOverBulkLimit>False</DropEventsOverBulkLimit>
		<ElasticSearchTimeout>90000</ElasticSearchTimeout><!-- we're getting connection rejected a lot from the server; I'd like to increase BulkSize, but with the payload too large messages, I don't think I can right now -->

		<SerializeObjects>True</SerializeObjects>

		<FixedFields>Partial</FixedFields>

		<ElasticFilters>
			<Remove>
				<Key>log4net:HostName</Key>
			</Remove>
			<Remove>
				<Key>log4net:Identity</Key>
			</Remove>

			<Rename>
				<Key>AppDomain</Key>
				<RenameTo>application</RenameTo>
			</Rename>
			<Rename>
				<Key>HostName</Key>
				<RenameTo>host.name</RenameTo>
			</Rename>
			<Rename>
				<Key>Level</Key>
				<RenameTo>log.level</RenameTo>
			</Rename>
			<Rename>
				<Key>log4net:UserName</Key>
				<RenameTo>UserName</RenameTo>
			</Rename>
			<Rename>
				<Key>LoggerName</Key>
				<RenameTo>log.logger</RenameTo>
			</Rename>
			<Rename>
				<Key>Message</Key>
				<RenameTo>message.text</RenameTo>
			</Rename>
			<Rename>
				<Key>ThreadName</Key>
				<RenameTo>thread.name</RenameTo>
			</Rename>
			<Rename>
				<Key>UserName</Key>
				<RenameTo>server.user.name</RenameTo>
			</Rename>
		</ElasticFilters>
	</appender>
</log4net>

Hi,
We have a mechanism to drop events over the bulk limit, but you will have to play with it in order to achieve optimal solution.
Please read about DropEventsOverBulkLimit there: https://github.com/urielha/log4stash/issues/77#issuecomment-800988830
Basically you will have to set BulkIdleTimeout to a more smaller timeout (depends on your amount of log messages per seconds) and set DropEventsOverBulkLimit to true


Turned the check of the scroll at the bottom from

checking equal to checking a range to make it work with fractions.
For #6580

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[x] Title summarizes what is changing
[x] Has a news entry file (remember to thank yourself!)
[ ] Appropriate comments and documentation strings in the code
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated
[ ] Test plan is updated as appropriate
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed)
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #7255 into master will decrease coverage by 0.44%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #7255      +/-   ##
=========================================
- Coverage   58.55%   58.1%   -0.45%
=========================================
  Files         486     486
  Lines       21460   21460
  Branches     3463    3458       -5
=========================================
- Hits        12566   12470      -96
- Misses       8116    8205      +89
- Partials      778     785       +7

Impacted Files
Coverage Δ

src/client/testing/serviceRegistry.ts
48.64% <0%> (-46.85%)
:arrow_down:

src/client/testing/codeLenses/main.ts
44.44% <0%> (-33.34%)
:arrow_down:

...t/datascience/jupyter/jupyterDataRateLimitError.ts
66.66% <0%> (-33.34%)
:arrow_down:

src/client/formatters/serviceRegistry.ts
75% <0%> (-25%)
:arrow_down:

src/client/api.ts
62.5% <0%> (-25%)
:arrow_down:

src/client/common/utils/platform.ts
64.7% <0%> (-23.53%)
:arrow_down:

src/client/common/utils/icons.ts
83.33% <0%> (-16.67%)
:arrow_down:

src/client/datascience/cellFactory.ts
75.86% <0%> (-13.8%)
:arrow_down:

src/client/common/logger.ts
68.55% <0%> (-6.92%)
:arrow_down:

src/client/providers/providerUtilities.ts
83.33% <0%> (-5.56%)
:arrow_down:

... and 9 more

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 04200d9...b6a392f. Read the comment docs.

You'll have to merge this into the native editor changes. It's no longer in mainPanel.tsx, but in interactivePanel.tsx. I should have submitted the same changes though.

So when merging, make sure MainPanel.tsx goes away still.

I also think when you 'port' this to release, you'll have to make this change.
Actually maybe that would be better. Just do this change in the release branch. We don't need this in the main branch because I already applied the fix to the native editor bits.

I also think when you 'port' this to release, you'll have to make this change.
Actually maybe that would be better. Just do this change in the release branch. We don't need this in the main branch because I already applied the fix to the native editor bits.

I was doing the merge, but I still need to finish it to cherrypick into release right?

No I think you can just cancel this PR and just a regular PR (not a cherry-pick) into the release branch

In reply to: 528937409 [](ancestors = 528937409)

Where in the release branch, you just redo this change.

In reply to: 528937926 [](ancestors = 528937926,528937409)

So create a branch from master, and PR that to release, right?
The changes should be there.

No. Create a branch from release and create a PR from that to release.

In reply to: 528938420 [](ancestors = 528938420)


Error executing action run on resource 'execute[Install Weblogic]'

Trying to install weblogic 10.3.6 on ubuntu 14.04
I get the following error and then I see an endless loop
 * template[/var/chef/cache/silent.xml] action create (up to date)
  * remote_file[/var/chef/cache/wls_121200.jar] action create (up to date)
  * execute[Install Weblogic] action run
================================================================================
Error executing action `run` on resource 'execute[Install Weblogic]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '255'
---- Begin output of java -jar /var/chef/cache/wls_121200.jar -silent -responseFile /var/chef/cache/weblogic_install.rsp -Djava.security.egd=file:/dev/./urandom ----
STDOUT: Unable to instantiate GUI, defaulting to console mode.

<IP_ADDRESS> <---------------------------- BEA Wizard Framework --------------------------->
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS> [Exit][Previous][Next]>

I'm closing this issue in preference or the new cookbook.
If the new cookbook doesn't meet your needs feel free to give us some feed back as it takes a different stance to installing than this one.

Mind throwing us a link to the new cookbook?...

No problem, here is it:
https://github.com/universityofderby/chef-weblogic


Problem with connecting to Nvidia shield controller via bluetooth on Ubuntu

Does anyone know how to connect the Nvidia joystick to the Ubuntu Via Bluetooth?

I tried to use Blueman, it still does not work.

We did not have any problems connecting our Shield controllers on Ubuntu 16.04.
Here is what I see now on my Ubuntu 18.04:
[NEW] Device 00:04:4B:77:F1:6C NVIDIA Controller v01.04
[CHG] Device 00:04:4B:77:F1:6C Connected: yes
[NVIDIA Controller v01.04]#

Try connecting the controller using USB cable and see if it works.

Thank you so much for your prompt response. I just updated my system from 16.04 to 18.04. It could be able to connect right now. but it will automatically disconnect. Did you have ever meet this problem?


Types seem to be missing

https://circleci.com/gh/intuit/auto/6454?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
also the code on github is pretty out of date

It's outdated, because I think the last release was somewhere else :D :D
I'm finalizing some things, so I hope that soon everything will be okay for most of the packages. I'm super confused where is what, too :sob:

So yea, the typings are missing, right? Nothing has changed that significantly, so you can include them manually from those which are here.

Oh, wait. Why updating to a different than latest tag?
Oooh, looking on the npm page and versions tab I'm seeing that accidentally there was 4.1 on latest dist tag? If so, why the heck 3.2.3 stay as latest, currently?!
Anyway. I may suggest you try the alpha dist-tag which seems to be v4, which includes the TS.


Add a better injectModule method to WASM

This allows for strict privacy for WASM modules, which is important in an environment like the browser, where most of the time you're running code on someone else's computer. The idea for this method would be to write a wrapper module around some possibly security-sensitive functions that you pass from js, and then allow arbitrary code to access that module. For robot rumble (the successor to codingworkshops, the code learning platform), it might be used like:
// vm.injectModule(name, source, imports?, strict_private?)
vm.injectModule(
    "robots",
    `
__all__ = ["export"]
def export(...): runRobot(...)
# robot-rumble "stdlib" source code
`,
    { runRobot: () => { ... } },
    true,
);
// later
vm.exec(userCode);

We don't want user code arbitrarily calling the runRobot function, so we wrap it in a module that makes sure that it can't, and also (ideally) provides a nicer, more pythonic interface. The strict_private parameter enables that; it runs the source code provided in one namespace with the JS imports, and copies only the items exported in __all__ to a new namespace that is injected into sys.modules.

Hmm, just realized that it would be possible to access the globals by doing e.g. get_robot.__globals__['runRobot']. I might look into preventing that, though I don't know if it's that necessary; it's pretty obscure.

Alright, I added the concept of "incognito" mode (though it's not an actual compile::Mode), which means that functions defined in it cannot have their __globals__ accessed, and frames that originate from an incognito context disallow accessing f_globals and f_locals. There's probably a few things like that that I missed, but I think the basic concept is decent.

Because I didn't look into non-vm part of this project that much, I am confused about this a little. To make it clear, this is a extension feature (mostly) for wasm, right?
Basically, I don't like the idea that non-standard python feature slow down the standard features.
It seems this feature is only enabled when inject_modlue is called. So please review if this idea will work:

Define new objects SecureModule, SecureFrame and SecureCodeObject (or Incognito*)
Define traits of module, frame and code object. Because the mode is given to compiler, a single module will have only CodeObject or SecureCodeObject. So they probably perfectly exclude each other.
Turn some functions and struct into generic. Probably vm.run_code, PyFunction and module related things?
These things might be placed in wasm or vm by whether this feature is belong to rustpython or rustpython-wasm.

Note: Here "standard Python" means documented or CPython compatible.

I think that would be a better way of separating the concerns, but it might also be cumbersome to have to define CodeObject, Frame, and PyFunction twice. Making core functions/frame code generic might also increase the code size a ton. I think this is sort of about whether or not we should implement features that CPython doesn't have, so here's my take on that: as an alternative Python interpreter, we are in a unique situation where we can experiment with non-standard features that we consider useful, and see how they work/interact with the rest of the language, without having to go through a PEP process first. At least in this situation (e.g. arbitrary Python code running in the browser), a feature like this is definitely necessary, but CPython doesn't usually run in the browser. However, I'm sure there are other environments where Python code does need security like the security that this feature provides, so I think it would be interesting to try this and see where else it could be used.

Also, w.r.t. "only used from the rustpython-wasm module", I was thinking that it could also be enabled from a Python module by something like from __future__ import incognito_module or __incognito__ = true.

Basically, I don't like the idea that non-standard python feature slow down the standard features.

@coolreader18 can you give us some numbers on the performance impact this change has?

Alright, I had some trouble getting the benchmarks to work, but here's what I got:
On master:
running 3 tests
test bench_rustpy_mandelbrot    ... bench: 1,017,088,271 ns/iter (+/- 21,787,720)
test bench_rustpy_nbody         ... bench: 306,066,689 ns/iter (+/- 13,873,395)
test bench_rustpy_parse_to_ast  ... bench:  10,004,214 ns/iter (+/- 1,026,285) = 6 MB/s

test result: ok. 0 passed; 0 failed; 0 ignored; 3 measured; 4 filtered out

RustPython on  master [!] is 📦 v0.1.1 via 🐍 v3.8.1 via 🦀 v1.41.0 took 6m42s
❯

On this branch:

running 3 tests
test bench_rustpy_mandelbrot    ... bench: 1,028,623,787 ns/iter (+/- 51,170,076)
test bench_rustpy_nbody         ... bench: 305,318,476 ns/iter (+/- 30,826,374)
test bench_rustpy_parse_to_ast  ... bench:  10,042,795 ns/iter (+/- 689,063) = 6 MB/s

test result: ok. 0 passed; 0 failed; 0 ignored; 3 measured; 4 filtered out

RustPython on  coolreader18/wasm-inject-module [!] is 📦 v0.1.1 via 🐍 v3.8.1 via 🦀 v1.41.0 took 6m50s
❯

Basically very little difference; the difference between 2 benchmarks are within both the standard deviations given by the bencher.

I agree that this is a very small decrease in performance. What do you think @youknowone?
We should document features that are not part of CPython. Where do you think this should be documented? I mentioned it in #1192 but we never decided where.

To make things clear, I am not asking changes or trying to decline this PR by these comments. This is just my general preferences.
Before talking about performance, the performance itself doesn't justify the design. So this is a kind of negotiation of trade-off between performance and a new feature. It seems having multiple PyFunction is not a big deal. If generic has too much complexity for core python features, then still secure objects can take over the complexity part as an optional feature. I think struct SecureCodeObject(CodeObject) and similar secure frame is another option. it seems we don't need 2 versions of frame - we just need 2 versions of FrameRef.
Being included in rustpython core or wasm is subtle issue. How about this? wasm support is one of the major feature of RustPython but perfectly living out of rustpython core world. So no matter whatever things happen in there. I think any non-standard feature can be added in this way of extension. We just can keep the core for the best compatibility.
About the benchmark, the measured performance doesn't look meaningful. The benchmark should measure the cost of f_globals and f_locals. The benchmark code use them enough? I am doubtful in general sense of Python though I didn't look in the benchmark test code.
Still, if you guys think adding this feature in this way is better than other way, I think it is acceptable. Because usually I was concentrating on core features, I don't have any perspective of the big plans of the project. So I don't want to disturb to decide things we do out of the core language.

That makes a lot of sense; I think your idea of separate FrameRef payoad types is much more elegant than my solution, I just don't know if it's feasible with how the PyRef type works at the moment. Eventually I'd like to allow some sort of upcast operation on a PyObject that returns a reference to the payload type of its base class, but I'm still trying to figure out the best way to do that. That would be necessary to implement your solution, though, as FrameRefs stored in e.g. the vm.frames frame stack are just PyRefs and can be accessed from Python, so it wouldn't be possible to store multiple different Frame payloads in the frame stack without that upcast feature.

@youknowone would you be okay with this getting merged?

if everybody think this is the best for now, yes, I am ok

@palaviv what do you think of this?

Hi all,
I looked into this change a bit, and I cannot say I agree with it. Python is insecure by design, you can modify all kind of things. In my opinion, adding an incognito mode adds extra code which tries to protect global variables, but as you mentioned elsewhere, you could still circumvent this by accessing the globals in another obscure way. I think it would be best to stick to CPython behavior, which is insecure by design. Making python properly secure can probably be harder than you imagine at first.
I like the __future__ compilation part of the change, that would be good to merge, but I'm reluctant to merge the incognito mode. Also, I would like to be able to use the rustpython code as a library on embedded systems, and then I want the library to be as simple as possible, and not too tailered towards WASM / javascript.
Please do not be offended by this feedback, but this is my view on the project.

Would you be opposed to any attempt to sandbox RustPython? What about a wasm-only builtin module that has a function to wrap a callable into an opaque object?
@opaque_callable
def a(): pass

I think we do need some solution for sandboxing, since a lot of use cases for embedding a scripting language into a program involves running arbitrary code, and I think RustPython's simplistic nature lends itself well to embedding.

I'm not opposed to sandboxing rustpython as a whole. This is already possible by compiling rustpython as a wasm module, and by using the wasm import / export machinery to very tightly control what can be accessed by rustpython. In that sense, the sandboxing would take place by limiting the exposed modules, such as sys, os and the file and socket API's. Maybe we could add feature flags to choose which parts of the standard library you want to use?
My rationale is that we do not require any specific sandboxing features inside rustpython itself. Just treat all python scripts executing in rustpython as one big interconnected mass. If you want to isolate some of your python code, since it is safety related, the I would propose to fire up two rustpython VM's and link them using queues, or another interface. In this sense, you would have two isolated rustpython VM's. One with a few privileges, and a limited API to the second VM. The second VM would than contain the secure code, and have more access.
On top off that I think python is insecure by it's nature, which is also what makes it a great tinkering tool, so I think we should stick to that, and not try to build protection features in. Another reason for not wanting the protection features, is that it might sound like it's secure, but still there are loopholes to bypass this security. In this case it is better to have no security than apparent security.
I agree that rustpython lends itself very well for embedding, and I would like to keep this feature.

I'm merging this now, since it's basically just the __future__ syntax and the injectModule  method, no big changes like incognito.


It is unclear (also from pycldf implementation) whether metadatafree datasets may have additional columns

Followup on https://github.com/cldf/pycldf/issues/50 from the formal side:
The specs state that

A dataset can be CLDF conformant without providing a separate metadata description file. To do so, the dataset must follow the default specification for the appropriate module regarding

file names
CSV dialect
column names
exactly. Thus, rather than not having any metadata, the dataset does not specify any; and instead falls back to using the defaults, i.e. "free" as in "beer" not as in "gluten-free".

A close reading of that seems to imply that additional columns outside those defined in the corresponding module .json should not be permitted.
However, several other bits of the specs (including the Wordlists.md with its talk about optional columns) give me the impression that additional columns should be permitted, and cldf validate does not complain, either.

Agree. Would changing "column names" into "required column names" do?

I think I'd write it in there explicitly, like

The CSV file may contain additional columns not specified in the default module descriptions. CLDF tools may handle these columns as named columns of datatype string with no propertyURL, or they may ignore these columns, or expose them in some contexts but not in others.

@Anaphory I'll add the first part of your suggestion, but not the second, since I think when CLDF tools make use of any non-standard columns, they are off in non-CLDF territory and I wouldn't want to prescribe any behaviour there :)


fix(procedure): adapt MetricaEmpresa class to be compatible with proc…

…edure modification

Push successful with no conflicts.


attachment content for Office 365 "Send an email (V2)" disappears after saving the workflow

Describe the Bug with repro steps
in logic app standard new designer,
1- adding Send an email (V2) action and configure the attachment content

2- save workflow successfully.
3- close and open the workflow designer again
4- attachment content is empty

5- by looking at browser trace, we can see the API call https://management.azure.com/subscriptions/99116a50-926e-44bb-b3f0-6691c02d05a1/resourceGroups/LARunHistory_RG/providers/Microsoft.Web/sites/ymsalehrunhistory/deployWorkflowArtifacts?api-version=2018-11-01
the payload was as below, it is clear that attachment content is empty, so it is UI issue
{
"files": {
"blob/workflow.json": {
"definition": {
"$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
"actions": {
"Read_blob_content": {
"type": "ServiceProvider",
"inputs": {
"parameters": {
"containerName": "files",
"blobName": "2019_CeratoK3_Manual.pdf",
"inferContentType": false
},
"serviceProviderConfiguration": {
"connectionName": "AzureBlob",
"operationId": "readBlob",
"serviceProviderId": "/serviceProviders/AzureBlob"
}
},
"runAfter": {}
},
"Send_an_email_(V2)": {
"type": "ApiConnection",
"inputs": {
"host": {
"connection": {
"referenceName": "office365-2"
}
},
"method": "post",
"body": {
"To"<EMAIL_ADDRESS>"Subject": "test",
"Body": "test",
"Attachments": [
{
"Name": "2019_CeratoK3_Manual.pdf",
"ContentBytes": ""
}
],
"Importance": "Normal"
},
"path": "/v2/Mail"
},
"runAfter": {
"Read_blob_content": [
"SUCCEEDED"
]
}
}
},
"contentVersion": "<IP_ADDRESS>",
"outputs": {},
"triggers": {
"When_a_blob_is_added_or_updated": {
"type": "ServiceProvider",
"inputs": {
"parameters": {
"path": "files/"
},
"serviceProviderConfiguration": {
"connectionName": "AzureBlob",
"operationId": "whenABlobIsAddedOrModified",
"serviceProviderId": "/serviceProviders/AzureBlob"
}
}
}
}
},
"kind": "Stateful"
},
"parameters.json": {
"ti": {
"type": "Int",
"value": 20
}
}
}
}
Note: I can edit successfully from code view
What type of Logic App Is this happening in?
Standard (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
No
Workflow JSON
{
    "files": {
        "blob/workflow.json": {
            "definition": {
                "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
                "actions": {
                    "Read_blob_content": {
                        "type": "ServiceProvider",
                        "inputs": {
                            "parameters": {
                                "containerName": "files",
                                "blobName": "2019_CeratoK3_Manual.pdf",
                                "inferContentType": false
                            },
                            "serviceProviderConfiguration": {
                                "connectionName": "AzureBlob",
                                "operationId": "readBlob",
                                "serviceProviderId": "/serviceProviders/AzureBlob"
                            }
                        },
                        "runAfter": {}
                    },
                    "Send_an_email_(V2)": {
                        "type": "ApiConnection",
                        "inputs": {
                            "host": {
                                "connection": {
                                    "referenceName": "office365-2"
                                }
                            },
                            "method": "post",
                            "body": {
                                "To"<EMAIL_ADDRESS>                                "Subject": "test",
                                "Body": "
test
",
                                "Attachments": [
                                    {
                                        "Name": "2019_CeratoK3_Manual.pdf",
                                        "ContentBytes": ""
                                    }
                                ],
                                "Importance": "Normal"
                            },
                            "path": "/v2/Mail"
                        },
                        "runAfter": {
                            "Read_blob_content": [
                                "SUCCEEDED"
                            ]
                        }
                    }
                },
                "contentVersion": "<IP_ADDRESS>",
                "outputs": {},
                "triggers": {
                    "When_a_blob_is_added_or_updated": {
                        "type": "ServiceProvider",
                        "inputs": {
                            "parameters": {
                                "path": "files/"
                            },
                            "serviceProviderConfiguration": {
                                "connectionName": "AzureBlob",
                                "operationId": "whenABlobIsAddedOrModified",
                                "serviceProviderId": "/serviceProviders/AzureBlob"
                            }
                        }
                    }
                }
            },
            "kind": "Stateful"
        },
        "parameters.json": {
            "ti": {
                "type": "Int",
                "value": 20
            }
        }
    }
}

Screenshots or Videos
No response
Browser
Edge
Additional context
No response

this should be fixed, however we'll still be missing 1 station before eod today, I'll run a hotfix for this in that missing station

the fix will go out EOD today

fix should now be in, closing - we can reopen if anyone is still facing the issue.


feat: use a Struct as a type

Currently, there is no way to nest a created Struct within another, with this PR, each Struct can have other structs be nested within.

@mergifyio update


footer: add mandoc version which was used for conversion

Turns out mandoc currently doesn’t have a version flag. I have posted a patch to the mandoc tech mailing list which adds such a flag, so that we can implement this feature with the next mandoc release.

mandoc upstream doesn’t want us to use version numbers.


Added Frame to each event record in the logs

Added checksum header and magic number footer to each record (bson) written to the logs.
Perf Test
Master (no frames)        33.74 ops/s stdev 2.17
Checksum CRC32          25.26 ops/s stdev 3.15
Checksum Adler32        25.27 ops/s stdev 2.60
Given no significant perf differnce, using CRC32 given testing from the Multimedia guru https://guru.multimedia.cx/crc32-vs-adler32/ which shows much better collision results for small messages.
There are probably a number of buffer type (and gc, other) optimisations that may be applied ...

 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.


noob question

hello, i am starting out with opengl and git.
i am familiar with glsl, but I am unsure how can I practice with code from your Chapter0 for example.
I do not want to rip stuff, but learn.
So can I for example copy mandelbrot1.html code into my site?
but what about .js sources?
could someone help me, I would be grateful!

All our code is available at interactivecomputergraphics.com http://interactivecomputergraphics.com/

Ed Angel
Founding Director, Art, Research, Technology and Science Laboratory (ARTS Lab)
Professor Emeritus of Computer Science, University of New Mexico
1017 Sierra Pinon
Santa Fe, NM 87501
505-984-0136 (home<EMAIL_ADDRESS><EMAIL_ADDRESS>505-453-4944 (cell) 				http://www.cs.unm.edu/~angel http://www.cs.unm.edu/~angel

On Feb 26, 2021, at 4:06 AM, josipDogan<EMAIL_ADDRESS>wrote:
hello, i am starting out with opengl and git.
i am familiar with glsl, but I am unsure how can I practice with code from your Chapter0 for example.
I do not want to rip stuff, but learn.
So can I for example copy mandelbrot1.html code into my site?
but what about .js sources?
could someone help me, I would be grateful!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/esangel/WebGL/issues/12, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB33BF2BQMTOU6BWAISUIH3TA56CXANCNFSM4YIHZ5MA.

thanks!


feat: add list utils

This adds functions to work with lists from bzlparty/lib_common as discussed in #495.
I removed the occurs functions, this is not needed because of the in-operator.
Please let me know if I should add more tests/documentation.
Type of change

New feature or functionality (change which adds functionality)

For changes visible to end-users

Relevant documentation has been updated

Test plan

New test cases added

@alexeagle thanks for taking the time to make some extra work
@kormide thanks for your review I really like your suggestions and will adopt them :heart:

Looks like this just needs a rebase to fix the test errors.


.env not found in current directory

I suggest to replace this line:
https://github.com/shroominic/codeinterpreter-api/blob/000213df1e28ec7efb27494280e5db12bc082dbf/codeinterpreterapi/config.py#L5
with
load_dotenv(dotenv_path="./.env")
so the .env file is located in the current directory of the Python script.
For instance:
 juanan@u033782  /opt/codeinterpreter-api-test  tree -a
.
├── .codebox
├── .env
└── get_btc.py

without that change, if we run the get_btc.py script we'll get this error:
File "/Users/juanan/.pyenv/versions/3.10.0/lib/python3.10/site-packages/codeinterpreterapi/session.py", line 54, in _llm
raise ValueError("OpenAI API key missing.")
ValueError: OpenAI API key missing.

With the suggested change, the .env file will be correctly located.

I am not sure if this is nessesary. I have the .env file in the same location as you and for me it works.
As far as I know dotenv is searching the entire directory tree from the current working directory down the folders for a .env file so by default it should find it.


[Week supervision] tooltip on "records with filters"

Discuss the necessity to explain better the info "Records with filters applied"

Can we close this @Amelie-V ?

yes


feat: worker convenience methods

This adds worker.evaluate and worker.evaluateHandle methods as a shortcut to their execution context equivalents. It also moves the worker tests into their own spec file, and makes the error messages a bit nicer when interacting with a closed worker (as opposed to a closed page).

@patrickhulce


Wrong delete call in coda-grib.c

Using
extern "C" int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  FuzzerTemporaryFile temp_file(data, size);

  coda_init();
  const char *product_class = NULL;
  const char *product_type = NULL;
  coda_format format;
  int version;
  coda_recognize_file(temp_file.filename(), NULL, &format, &product_class,
                      &product_type, &version);
  coda_done();
  return 0;
}

I got this crash:
0x0000555556534acf in __assert_fail (assertion=<optimized out>, file=<optimized out>, line=62,
    function=0x555555928ae0 <__PRETTY_FUNCTION__.coda_grib_type_delete> "void coda_grib_type_delete(coda_dynamic_type *)") at base/logging.cc:106
#8  0x0000555555cf2bfc in coda_grib_type_delete (type=0x604000002050) at third_party/stcorp_coda/libcoda/coda-grib-type.c:62
#9  0x0000555555ce8ef5 in read_grib1_message (product=0x607000000560, message=<optimized out>, file_offset=<optimized out>) at third_party/stcorp_coda/libcoda/coda-grib.c:1727
#10 0x0000555555cdc85e in coda_grib_reopen (product=<optimized out>) at third_party/stcorp_coda/libcoda/coda-grib.c:3103
#11 0x0000555555d10a77 in reopen_with_backend (product_file=0x10418, format=66584) at third_party/stcorp_coda/libcoda/coda-product.c:408
#12 0x0000555555d0e61e in open_file (filename=<optimized out>, product_file=<optimized out>, force_binary=<optimized out>) at third_party/stcorp_coda/libcoda/coda-product.c:550
#13 0x0000555555d0e09d in coda_recognize_file (filename=<optimized out>, file_size=<optimized out>, file_format=<optimized out>, product_class=<optimized out>,
    product_type=<optimized out>, version=<optimized out>) at third_party/stcorp_coda/libcoda/coda-product.c:594
#14 0x0000555555c68ced in LLVMFuzzerTestOneInput (data=<optimized out>, size=<optimized out>) at third_party/stcorp_coda/fuzz/coda_recognize_file_fuzzer.cc:16

The assert is here:
void coda_grib_type_delete(coda_dynamic_type *type)
{
    assert(type != NULL);
    assert(type->backend == coda_backend_grib);  // <--- this assert was hit

Fixed by switching coda_grib_type_delete to coda_mem_type_delete lets the fuzzer poc run without crashing.
            /* data representation type is Latitude/Longitude Grid */
            gds = coda_mem_record_new((coda_type_record *)grib_type[grib1_grid], NULL);

            NV = buffer[3];
            gtype = grib_type[grib1_numberOfVerticalCoordinateValues];
            type = (coda_dynamic_type *)coda_mem_uint8_new((coda_type_number *)gtype, NULL, cproduct, NV);
            coda_mem_record_add_field(gds, "numberOfVerticalCoordinateValues", type, 0);

            PVL = buffer[4];

            gtype = grib_type[grib1_dataRepresentationType];
            type = (coda_dynamic_type *)coda_mem_uint8_new((coda_type_number *)gtype, NULL, cproduct, buffer[5]);
            coda_mem_record_add_field(gds, "dataRepresentationType", type, 0);

            if (read_bytes(product->raw_product, file_offset, 26, buffer) < 0)
            {
                coda_mem_type_delete((coda_dynamic_type *)gds);
                // coda_grib_type_delete((coda_dynamic_type *)gds);  <----- wrong type
                return -1;
            }

Fuzzer proof of concept (poc):
crash-65723607e49c0ccb8ac6e7790f748cf607880bc9.zip

The bug is in read_grib1_message()

This is indeed a bug. Thanks for finding it.
Luckily it is in a cleanup handler (when you have e.g. corrupt grib files), so users should generally not be impacted.
The correct fix is to use coda_dynamic_type_delete though.
Fixed in 836d1493d7b70451ae9239b78e07d767da1d3adc


Added Drawing Canvas

Issue Id you have worked upon - #283
Briefly explain your program logic - Made a plain canvas with functionality of change pen color, brush width and brush opacity and clearing the canvas.
Screenshots(Attach 2 screenshots of your own input and output) -

By raising this PR I affirm that -

[x] My code follows the guidelines of this project.

[x] I have performed a self-review of my own code.

[x] I have commented my code.

[x] My code gives the correct output.

[x] I affirm that I strictly follow contributing guidelines and code of conduct.

Hey 👋, may you also encourage us by clicking the star icon on the repository main page. ⭐


https browser and embedded device net::ERR_CERT_AUTHORITY_INVALID

We are sourceing pages in the browser using https. For that reason we need to use secure ws (wss). Our embedded devices are on a LAN (192.168.0.* ip addresses).
When the browser tries to connect a wss to the embedded device, we get the error net::ERR_CERT_AUTHORITY_INVALID
We are having trouble working out how to generate the embedded side certification  which allows the browser to connect using wss.
Is there a simple standard way to do this ?
Currently we have been trying to self sign certificates... however we aren't having much luck.

Modern browsers are making it near-impossible to use self-signed certificates, even for testing purposes.
Especially if you want any browser (not just one under your control) to access the service, you'd be better off using an authority like Let's Encrypt to generate "proper" certificates for your service.  In addition to being free, Let's Encrypt is widely recognized and offers many of ways to automate generating and renewing their certificates.


Move SupportsAdmissionControl methods to DeltaSourceBase

DeltaSourceBase is a SupportsAdmissionControl but all the methods are in DeltaSource (looks like a leftover after a code refactor?) They should be moved off of DeltaSource to DeltaSourceBase.
/cc @scottsand-db

@jaceklaskowski - this doesn't seem like a super critical refactor. The code wouldn't be that much simpler afterwards. We'd rather focus our review time on new features or bugs. If you feel passionately about this, feel free to make a PR though. But I think there's more interesting Delta stuff for you to work on :p See the good first issue and good medium issue labels.


Non-defined user?

sqlplus system/OraPasswd1@pdb1 = ORA-12154: TNS:could not resolve the connect identifier specified

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

ID: c3e91e0d-1797-abae-1941-29e91cc05b77
Version Independent ID: 7e55f1a5-54b2-cf04-af3a-813d2e855539
Content: Implement Oracle Golden Gate on an Azure Linux VM
Content Source: articles/virtual-machines/workloads/oracle/configure-oracle-golden-gate.md
Service: virtual-machines-linux
GitHub Login: @romitgirdhar
Microsoft Alias: rogirdh

Ah - this can be ignore - looks like there was  problem with the TNS Ora file.

We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


fs: don't use GENERIC_READ with CreateFile when obtaining file info

We don't really need this flag, because we don't do any actual reading
except reading metadata. But using GENERIC_READ on file opened in exclusive
mode, results in 'OSError: [WinError 6] The handle is invalid' being raised,
which is caused by the GetFileInformationByHandle returing 0. This bug
is pretty easy to reproduce by just opening a file in excel and then trying
to feed it to getfileinfo().
This patch drops GENERIC_READ and also provides a test.

Hmm, looks like appveyor's trigger broke when you've changed your nick on github.

Closing due to maintainer's inactivity.


Phone lib addon - parentheses

I wasn't able to find any issues around this, but wanted to know if there was ever any talk about adding more formatting options around a specific country code's formatting. For example, a US number looks like this currently:<PHONE_NUMBER> but it'd be great if there was an option to surround that text like so<PHONE_NUMBER>.

my version of the "crutch."
but delimiters does not support " " (there is a space) and 2 characters in a row ") " or ")-"
when 2 characters, then deletion <- occurs before the place ") " and further blocked, - you must manually rearrange the cursor
var phoneMask = {
            prefix: '+7 (',
            delimiters: [')', '-', '-'],
            blocks: [7, 3, 2, 2],
            uppercase: true
        };

if  could add 2 characters and a space character, you would get support for large data formats

My company is considering not using this library for phone masking because most of our customers require parentheses for their style guides... would love to not have to integrate with another lib for this one use case.
I'm willing to spend some time on a PR with some direction from maintainers if there is interest.

@zslabs Does this work for you?
https://jsfiddle.net/qnmds8dn/2/
new Cleave("input", {
	numericOnly: true,
	blocks: [0, 3, 3, 4],
  	delimiters: ['(', ') ', '-']
});

@nosir That actually works pretty well! I noticed that if I type a full number and attempt to backspace; it gets "stuck" before the  ) . Happening to you at all?

Until #348 is addressed, I'm adding an extra block and delimiter for the space. It's not the ideal aesthetic (since the space comes after the next number), but I found it more important to have the ability to backspace.
new Cleave(this.el, {
  numericOnly: true,
  blocks: [0, 3, 0, 3, 4],
  delimiters: ["(", ")", " ", "-"],
});

Ah cool, I shall add this to demo

Added @stephenjwatkins 's solution to the demo: https://jsfiddle.net/nosir/aLnhdf3z/

@nosir Any reason why this wouldn't work in a React app? My code looks like this but no blocks and delimiters updates.
<Cleave placeholder={this.props.placeholder}
className={this.props.className}
options={{
phone: true,
phoneRegionCode: 'US',
blocks:[0, 3, 0, 3, 4],
delimiters: ['(', ')', ' ', '-']
}}
/>

@Schw2iizer To use custom blocks or phone: true, you can only choose one option, they don't work together, by using phone: true, it resolves blocks automatically for you, and in that case, you can only define single delimiter.
TLDR;
either:
options={{
blocks:[0, 3, 0, 3, 4],
delimiters: ['(', ')', ' ', '-']
}}

or
options={{
phone: true,
phoneRegionCode: 'US',
delimiter: '-'
}}

@nosir That's great. Thank you for that info.

Confirmed that suggestion by @nosir works as of today. Thank you.


Enable FORWARDing to exposed network

Please review each commit separately. Each commit contains a self descriptive message helping to understand the introduced changes.
Non-backward compatible change: weave expose requires a running instance of weaver which makes not possible to run weave expose when weave has not been launched yet.
Fixes #2758

I fixed up the conflict (the other change was lint-driven) so it can be merged if tests still pass


fix: bump osv max concurrent requests

The current maxConcurrentRequests setting is insufficient for container scanning, where one scan may report more than a thousand vulnerabilities. Bump it up to 1000 to fix it.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 69.31%. Comparing base (a20e520) to head (77c1b15).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1290      +/-   ##
==========================================
+ Coverage   68.53%   69.31%   +0.78%
==========================================
  Files         175      175
  Lines       16804    13097    -3707
==========================================
- Hits        11516     9078    -2438
+ Misses       4661     3389    -1272
- Partials      627      630       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Trying to understand the impact on an end user in a bandwidth-challenged environment...
Does this result in up to 1,000 concurrent separate API requests for individual vulnerabilities?
Or a single batch query for up to 1,000 vulnerabilities?

Does this result in up to 1,000 concurrent separate API requests for individual vulnerabilities?
Or a single batch query for up to 1,000 vulnerabilities?

The former, 1000 concurrent separate API requests.

Does this result in up to 1,000 concurrent separate API requests for individual vulnerabilities? Or a single batch query for up to 1,000 vulnerabilities?

It's for the individual vulnerability queries.


recording fragment

I want to record videos to different files in one minute. Can I only stop record first and then start record.I use camera2

Record videos in chucks is not possible using MediaMuxer and it is the way used to record videos in this library so it is not possible currently.
The only way is strart and stop record as you described.
I recommend you record a video, and after record, cut this video using other library.

Thanks


What's the difference between coco network and other OSS blockchain technologies?

What unique features are we going to get using coco framework as opposed to using Quorum or Hyperledger Fabric both are aimed for private chain networks and the target audience is the enterprise.
So what am I missing here?
P.s I'm aware this is not an "issue" per se and more of a discussion. It's a relatively new technology and there aren't proper channels to discuss it yet (that I'm aware of) so I created this gitter room feel free to drop a line there.

The Coco white paper does a nice job of describing the differences without
going too deep. The shortest possible description (which will have flaws)
is that it can be seen as an abstraction and governance layer above a
network of heterogeneous nodes.
Quorum and Hyperledger fabric are each focused on their own block chain
technology.
A major caveat - I have only read the white paper and despite repeated
attempts to contact Microsoft have only got radio silence, so it might all
be complete vaporware.
I do recommend that you read the white paper though if you haven’t already.
It’s interesting.
On Sun, Mar 11, 2018 at 11:20 Ofir Green<EMAIL_ADDRESS>wrote:

What unique features are we going to get using coco framework as opposed
to using Quorum or Hyperledger Fabric both are aimed for private chain
networks and the target audience is the enterprise.
So what am I missing here?
P.s I'm aware this is not an "issue" per se and more of a discussion. It's
a relatively new technology and there aren't proper channels to discuss it
yet (that I'm aware of) so I created this gitter room
https://gitter.im/enterprise-blockchain/ feel free to drop a line there.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Azure/coco-framework/issues/15, or mute the thread
https://github.com/notifications/unsubscribe-auth/AQXtaAN01ijTY2VlXabIkeYDdoCw7lMJks5tdUCfgaJpZM4Slupt
.

--
Patrick Millar
email<EMAIL_ADDRESS>twitter: @patrickmi
mobile:<PHONE_NUMBER>

Coco has been released as CCF now: https://github.com/Microsoft/CCF
The repository contains links to the Technical Report and the project documentation, which should help answer your question.
Thank you for your patience!


Change relation for metabolism terms

This is actually multi-step

Define new relation in RO (cjm, DH, DOS)
clear TG queue and Freeze editing
Search and replace in editors file
Change TG template
Unfreeze

Reported by: cmungall
Original Ticket: geneontology/ontology-requests/10881

Fixed with ##16910


Any help needed on the DB side?

Hello, I have stumbled in your project and I think I may be able to help with the "Search-related issues" issue written on http://dev.gutenberg.org/help/new_website.html
Are you currently looking to rework some of the backend as well?

Apologies for the long delay. We had other priorities, and are now looking at search.
We are seeking to implement Solr+Lucene. We are also interested in addressing some of the long-standing anomalies in the current search method, which basically uses PostgreSQL (our back-end database).
If these might be of interest, please get in touch ("contact information" at www.gutenberg.org). Thanks and best regards.


Secure faucet pallet

#67

Should be working, needs docs possibly?

Should be working, needs docs possibly?


Slider handle position in not in correct

Hi, I am trying to build a slider component on https://message.dk/shop . We are setting the min and max value for the slider and the values seem to be updating correctly, at least when it comes to the numbers under the slider.
The issue is in the thumb in the slider. The position of it is completely off.
Looking into your demo I saw that transform: translate you are using is going to -1000% for the 0 position and mine goes up to 100%. As soon as I add one more 0 in dev tools, position is correct.
Also this only happens in production, development version uses the correct -1000% value.
Do you have any idea of why is there a difference in numbers?
Here are two screen shots of what happens before and after adding additional 0 to the calculation:

So, to answer my own question, the issue I found was the version of the package.
We used package.json setup like this: "@vueform/slider": "^2.0.3" and that was producing the issue in the build.
Instead, I have removed the cap to use exactly 2.0.3 and it works properly

Hi @wolfx1998, remove package-lock.json (yarn.lock) and node_modules then reinstall it. It should be fine - if not, let me know! Make sure that if you're using custom css update that one too to the latest.


JavaScript example fails: error TS2694: Namespace 'React' has no exported member 'SFC'.

Describe the bug
git clone \
  --depth 1  \
  --filter=blob:none  \
  --sparse \
  https://github.com/SAP-samples/cloud-sdk-js.git \
;
cd cloud-sdk-js
git sparse-checkout set samples/cf-sample-application

cd cloud-sdk-js/samples/cf-sample-application
npm install
npm run start:dev

../node_modules/@types/markdown-to-jsx/index.d.ts:21:13 - error TS2694: Namespace 'React' has no exported member 'SFC'.

[11:29:55] Starting compilation in watch mode...

../../../node_modules/@types/markdown-to-jsx/index.d.ts:21:13 - error TS2694: Namespace 'React' has no exported member 'SFC'.

21     | React.SFC<P>
               ~~~

../../../node_modules/@types/markdown-to-jsx/index.d.ts:23:66 - error TS2694: Namespace 'React' has no exported member 'SFC'.

23           component: string | React.ComponentClass<P, S> | React.SFC<P>;
                                                                    ~~~

../../../node_modules/@types/markdown-to-jsx/index.d.ts:74:21 - error TS2694: Namespace 'React' has no exported member 'SFC'.

74         type: React.SFC<P> | React.ComponentClass<P> | string,
                       ~~~

[11:30:00] Found 3 errors. Watching for file changes.

Used Versions:

node version via node -v v16.16.0
npm version via npm -v 8.18.0
SAP Cloud SDK version you used as dependency

Why following packages are required as production dependencies ?
    "rimraf": "3.0.2",
    "rxjs": "7.5.6",
    "webpack": "5.74.0"

Hey @bsrdjan, thanks for reaching out to us.
You are right, these dependencies shouldn't be production dependencies, we will improve that in the near future.
However we can't reproduce the compilation error you face, the cause is most likely a global dependency you installed, which is used instead of one of the local dependencies.


Number of GPUs for training

How many GPUs are used during training?
In the paper, it is mentioned a single V100 is used for implement, wondering the number of GPUs used for training.

8块 32G V100
FireWallDragonDarkFluid @.***> 于2023年7月1日周六 12:01写道：

How many GPUs are used during training?
In the paper, it is mentioned a single V100 is used for implement,
wondering the number of GPUs used for training.
—
Reply to this email directly, view it on GitHub
https://github.com/Li-Chongyi/Dehamer/issues/16, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIEVQEKYZUUAVCQIJN4VHWLXN6OJBANCNFSM6AAAAAAZ2RGBPQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Add alternative shortcut for Align Transform to View in the 3D editor

Follow-up to https://github.com/godotengine/godot/pull/93579.

The new shortcut is Ctrl + Alt + Numpad 0 and is the one listed in the 3D viewport's Perspective menu (since PopupMenu accelerators display the first shortcut only). This shortcut matches Blender and avoids conflicts with the GeForce Experience overlay, which defaults to Ctrl + Alt + M.
Ctrl + Alt + M is still defined as an alternative default, so that existing workflows are not impacted.

See https://github.com/godotengine/godot/issues/93668.

Thanks!


some error with proxy

When I try to use proxy I get this:
I'm sure that my proxies are working
` Traceback (most recent call last):
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpcore_exceptions.py", line 8, in map_exceptions
yield
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpcore\backends\sync.py", line 82, in connect_tcp
sock = socket.create_connection(
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\socket.py", line 843, in create_connection
raise err
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\socket.py", line 831, in create_connection
sock.connect(sa)
ConnectionRefusedError: [WinError 10061] Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpx_transports\default.py", line 60, in map_httpcore_exceptions
yield
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpx_transports\default.py", line 218, in handle_request
resp = self._pool.handle_request(req)
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpcore_sync\connection_pool.py", line 253, in handle_request
raise exc
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpcore_sync\connection_pool.py", line 237, in handle_request
response = connection.handle_request(request)
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpcore_sync\http_proxy.py", line 255, in handle_request
connect_response = self._connection.handle_request(
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpcore_sync\connection.py", line 86, in handle_request
raise exc
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpcore_sync\connection.py", line 63, in handle_request
stream = self._connect(request)
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpcore_sync\connection.py", line 111, in _connect
stream = self._network_backend.connect_tcp(**kwargs)
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpcore\backends\sync.py", line 82, in connect_tcp
sock = socket.create_connection(
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\contextlib.py", line 135, in exit
self.gen.throw(type, value, traceback)
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpcore_exceptions.py", line 12, in map_exceptions
raise to_exc(exc)
httpcore.ConnectError: [WinError 10061] Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\asus\Desktop\2\Discord-MultiToolPY-main\main.py", line 375, in
menu()
File "C:\Users\asus\Desktop\2\Discord-MultiToolPY-main\main.py", line 198, in menu
req1 = getInviteInfo(rawInvite)
File "C:\Users\asus\Desktop\2\Discord-MultiToolPY-main\utils.py", line 68, in getInviteInfo
res = client.get(f'https://discord.com/api/v9/invites/{rawInvite}?with_counts=true', headers={
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpx_client.py", line 1025, in get
return self.request(
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpx_client.py", line 802, in request
return self.send(request, auth=auth, follow_redirects=follow_redirects)
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpx_client.py", line 889, in send
response = self._send_handling_auth(
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpx_client.py", line 917, in _send_handling_auth
response = self._send_handling_redirects(
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpx_client.py", line 954, in _send_handling_redirects
response = self._send_single_request(request)
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpx_client.py", line 990, in _send_single_request
response = transport.handle_request(request)
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpx_transports\default.py", line 218, in handle_request
resp = self._pool.handle_request(req)
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\contextlib.py", line 135, in exit
self.gen.throw(type, value, traceback)
File "C:\Users\asus\AppData\Local\Programs\Python\Python39\lib\site-packages\httpx_transports\default.py", line 77, in map_httpcore_exceptions
raise mapped_exc(message) from exc
httpx.ConnectError: [WinError 10061] Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение
Process finished with exit code 1`

Can you tell me what protocol do your proxies use?

@shahzain345  http also I tried https

@shahzain345 I noticed that this problem is not present when using the SingleDM function but with Joiner Server it is not working

i am using python 3.9.8 also message me on guilded and I'll be happy to help you.


Update Test SDK version

This will reduce #6955 to a very small number of files.

Urgh - rerunning the diff-pr job doesn't work because it's still deeming it to not have the "allow breaking changes" label. Will close and reopen.


Write ORC from arrow recordbatches

Not a focus now, just raising issue here for tracking

Beginning work on this.
I'll be committing to the initial-write-support branch.
Will want to get a minimum end to end version before merging into main (so resultant PR might be big), supporting basic types like string/integer/float etc.

https://github.com/datafusion-contrib/datafusion-orc/pull/122
PR for initial support, without boolean and string (will be done subsequently since PR is already quite large)


Pipeline (#1)

add new source-build options for multi stage build

allow override of registries to avoid dockerhub rate limit

update tests to allow for override of docker hostname when building in non-kind cluster

remove docker ignore file, buildah and other container build tools don't like this format

add step to ensure csv for openshift-pipelines installed on OpenShift, or tekton-pipelines is installed on kube

add support for knative based restarting of pipeline

add onepipeline file for security scanning

add secrets baseline file

https://w3.ibm.com/w3publisher/detect-secrets/developer-tool

make integration tests work

performs additional cleanup for subsequent runs
blocks m4dapplication test from running when wkc connector is configured

need to adjust this such that it is configurable from pipeline

use fybrik-system until multi-tenancy is supported

Support tekton install via Kind with basic nfs install

cleanup for upstream effort

Co-authored-by: Nicholas Goracke<EMAIL_ADDRESS>Co-authored-by: Jonathan L Kaus<EMAIL_ADDRESS>Signed-off-by: Nicholas Goracke<EMAIL_ADDRESS>

@shlomitk1 I've removed files & references that are wkc related.  See my other comments/questions inline.

For .secrets.baseline, it's used for static code scanning to ensure we aren't including secrets in the code base (there is a step in the pipeline that checks this).
The tool that checks it, however, may not be widely available.  I'll remove it for now, and we can discuss as a part of a separate PR

@ronenkat anything else you'd like to see addressed for this?


Upgrade dependencies

Upgrade dependencies

Codecov Report

Merging #75 (40c91e9) into master (312952b) will decrease coverage by 1.02%.
The diff coverage is 2.72%.

:exclamation: Current head 40c91e9 differs from pull request most recent head c055ba2.

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


Remove section about coronavirus

Following chat with Mark (we're adding aliases to the relevant pattern, so people who search will still find it)

You can preview this change here:
Built with commit 23c3c2bc21503973f892d75a2a57ce96ba8e02bd
https://deploy-preview-1308--govuk-design-system-preview.netlify.app


Update minikube and kubernetes to latest versions

Current Behavior
These versions are highlighted in the readme as being used by the action currently:
          minikube version: 'v1.21.0'
          kubernetes version: 'v1.20.7'

Desired Behavior
The latest versions of these tools are:
          minikube version: 'v1.30.1'
          kubernetes version: 'v1.27.3'

Implementation

Use the latest versions in the action by default.
Update the scheduled tests to use the latest versions.

Acceptance Tests

New version of this GitHub Action is published to the marketplace.

Contributor Guides and Resources

📝 Meshery Adapters Spreadsheet
🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Hey @leecalcote, I want to work on this issue. Can you assign me?

Previous:

Latest:

Previous:
Latest:

If you allow me to go forward then I will raise a PR @leecalcote.

There you go @Debjyoti0404


allowing breakpoints everywhere triggers a breakpoint event

re #39553

have this config "debug.allowBreakpointsEverywhere": true
listen to breakpoint events and have already a few breakpoints
toggle the "debug.allowBreakpointsEverywhere" from true to false
two more breakpoint changes are fired

notice that those events are empty

@isidorn I can avoid sending out those empty events but why are you generating them in the first place?

Great catch.
I had a problem where on each file event I was checking what breakpoints I need to remove since the file might be deleted by a file event. And after figuring out no breakpoints need to be deleted I would still cal the remove method with an empty array which would generate an event.


cmd/go/internal/fsys: TestWalk fails on Plan 9

CL 262617 has a test which fails on Plan 9.
--- FAIL: TestWalk (0.06s)
    --- FAIL: TestWalk/no_overlay (0.01s)
        fsys_test.go:583: name of file #0 in walk, got "root", want "."
FAIL
FAIL	cmd/go/internal/fsys	0.780s

This appears to be due to a difference in the behavior of os.Lstat on Plan 9.
On other platforms, os.Lstat(".") empirically returns a FileInfo such that fi.Name() == ".", but on Plan 9 it seems to instead return the resolved name of the current working directory.
Is that difference intentional?

What does the program in https://play.golang.org/p/OHAkKG-4Tp- output when run on Plan 9?
(I can't run it myself due to #42117.)

Is that difference intentional?

It reflects the underlying semantics of Plan 9 file system.  Plan 9 doesn't have separate directories and inodes, or links - the filesystem is a tree, not an arbitrary graph. The directory entry contains the name of the file element, and that's what stat returns in the name field. No resolving needed.

What does the program in https://play.golang.org/p/OHAkKG-4Tp- output when run on Plan 9?

I copied it into /tmp, and did 'go run' from there. It outputs "tmp".

go doc os.FileInfo says that the Name field is "base name of the file".  On Plan 9 that's unambiguous because files have only one name.  (You can dynamically bind other names to it, but that's something else.)   On other systems with hard links, it can only give "a base name" because "the base name" doesn't seem to have a meaning.

Hmm. On other systems, there is one obvious base name to choose for ., which is the name given by calling filepath.Base on  the result of os.Getwd(). But they don't do that today. 😞
Given your argument above, I suppose that the Lstat behavior on Plan 9 is correct and it is the other platforms that are not quite right.

Given your argument above, I suppose that the Lstat behavior on Plan 9 is correct and it is the other platforms that are not quite right.

Hrm. The stat(1) command on Linux is consistent with Go's Stat and Lstat:
$ cd /tmp
/tmp$ stat . --format=%n
.

I guess this is just a plain old platform variation. 😞


KiCad 5 Simulator Fails to run

Issue description
The simulator is unable to run and when attempted it has a segmentation fault.
(ngspice is installed)
Steps to reproduce
Start kicad from terminal
Open Eeschema under tools select simulate.
It opens a kicad error window that says
"libngspice.so.0.0.0: cannot open shared
object file: No such file or directory"
Click okay then open Eeschema which has a Warning window open that says
"Missing ngspice shared library"
After clicking Ok it closes and the terminal only has Segmentation Fault showing after the call.

system: "x86_64-linux"
host os: Linux 5.1.6, NixOS, 19.03.172801.1a27474d474 (Koi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2.2
channels(root): "nixos-19.03.172801.1a27474d474"
channels(emmer): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

@berce

Did a bit of testing. If the wrapper adjusts the LD_LIBRARY_PATH to include libngspice, the SPICE GUI opens, but running a simulation immediately crashes kicad again:
`wrapProgram "$out/bin/kicad" "''${gappsWrapperArgs[@]}" --prefix LD_LIBRARY_PATH : "${libngspice}/lib"
There is nothing obvious I can find in the strace output, so I'm not sure what exactly is breaking there.

I'm using this overlay to get ngspice simulator working in kicad:
kicad.nix.txt
Which requires following patch to kicad:
kicad-ngspice.patch.txt
and using kicad-stable in environment.systemPackages list in my configuration.nix.
I am not sure if following two are required, but adding them for completeness (they enable open-mp):
ngspice.nix.txt
libngspice.nix.txt
With these overlays and  the patch to kicad, I'm able to use ngspice simulator in kicad (as well as seeing 3D models, but that might have been resolved in original kicad/default.nix file already). Maybe it's not ideal solution but it seems working fine.
Hope that helps.

I've got it working in #69584 now, only thing left is an aarch64 build issue.


update(README.md): add k8s-metacollector to the list of charts

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If this PR will release a new chart version please make sure to also uncomment the following line:

/kind chart-release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area falco-chart

/area falco-exporter-chart

/area falcosidekick-chart

/area event-generator-chart

/area k8s-metacollector

What this PR does / why we need it:
update(README.md): add k8s-metacollector to the list of charts
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Checklist

[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: alacuku
Once this PR has been reviewed and has the lgtm label, please assign cpanato for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: b183b0910328981dcfc45d0fb1f9639953278e25


Add support for intercepting routes

I have implemented in this PR the support for intercepted routes. The Router's href will be set to the same href as it would be set when the page is reloaded. So the Router has the same href "/blog/:author" in the /@modal/(.)blog/[author]/page.tsx and /blog/[author]/page.tsx pages.
I had to write quite complicated RegExps for this functionality. And there is also now some ordering dependancies between the piped functions in getRouteHref. For example, all group and parallel segments (expect default locale "/(en)/" group segment) have to be removed before intercepted segments can be removed properly.
Since now the default locale group segment "/(en)/" is not removed in the first removeGroupSegments call, it required it's own function to had it removed later in the pipe.
I will create a different pull request for the example update since it requires a new version of next-roots to be released.

I was still thinking about the generated route names in the getRoute file. Since intercepted (and also parallel) routes have the same href as the basic versions of the routes, should they have also the same name? For example these rewrites
{
  originPath<EMAIL_ADDRESS>  localizedPath<EMAIL_ADDRESS>},
{
  originPath: '/blog/[authorId]/[articleId]/page.ts',
  localizedPath: '/en/blog/[authorId]/[articleId]/page.ts',
},
{
  originPath: '/@modal/(.)blog/[authorId]/[articleId]/page.ts',
  localizedPath: '/en/@modal/(.)blog/[authorId]/[articleId]/page.ts',
},

Should those be transformed to the below routes?
{
  name: '/login',
  href: '/en/log-in',
},
{
  name: '/blog/[authorId]/[articleId]',
  href: '/en/blog/:authorId/:articleId',
},
{
  name: '/blog/[authorId]/[articleId]',
  href: '/en/blog/:authorId/:articleId',
},

In my opinion, if the route is grouped, parallel or intercepted, it should have the same name in the router's schema as if it was a basic route. That way for example router.getHref can be called only with "real" route names and not with something like /@modal/(.)blog/[authorId]/[articleId].
I will implement it the way I think it should work and you can comment when you have time if I thought this through correctly.


Give insight into pending timers for Angular2 applications

When waiting for page stability times out, it would be useful to have some sort of output to inspect for Angular2 apps, like we do for Angular.js 1.x.

Still want to do this, we're working on changes to the Testability API to support it.


Show conflicted files on pull request ui.

Currently when a PR is creating, it will return 500 if there are some conflicts. It's not very friendly UI.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/41873740-show-conflicted-files-on-pull-request-ui?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

If it displays a 500 error page it's a bug and not a feature :)


Why don't apple_sdk frameworks use __propagatedImpureHostDeps?

Some of the Apple frameworks we use (such as Security.framework and CoreFoundation.framework; I'm not sure what else is included here) require impurely linking against the system-provided version. This can be a problem when trying to build in the sandbox.
My local /etc/nix/nix.conf file was discovered to have extra-sandbox-paths = /System/Library/Frameworks /System/Library/PrivateFrameworks /usr/lib /private/tmp /private/var/tmp /usr/bin/env, I have no idea where this came from, but my laptop's version was missing that, and was subsequently unable to run nix-review on a PR because the build process invoked tools linking against Security.framework and CoreFoundation.framework.
In a quick experiment, __impureHostDeps looks like it can be used to declare that that we need access to these frameworks regardless of nix.conf (well, it looks like there's an undocumented setting that controls what prefixes you can use on entries in __impureHostDeps, but since it's undocumented, nobody should be changing the defaults). I tried with the following file:
{ pkgs ? import <nixpkgs> {}}:

pkgs.runCommandNoCC "foo" {
  __impureHostDeps = [
    "/System/Library/Frameworks/Security.framework/Versions/A/Security"
    "/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation"
  ];
} ''
  ${pkgs.cargo}/bin/cargo --version
''

This was built with nix-build --option sandbox true ./foo.nix (after having commented out the extra-sandbox-paths line in /etc/nix/nix.conf).
Without the __impureHostDeps this fails to invoke cargo, but with them it's able to invoke it just fine (note: it still fails because it didn't produce $out, but that's to be expected).
Given this, why don't our applicable apple_sdk frameworks (such as darwin.apple_sdk.frameworks.Security) declare __propagatedImpureHostDeps that include the applicable paths? That way I don't need to have extra-sandbox-paths defined.
One annoyance is the fact that __impureHostDeps apparently needs to reference files, it can't reference directories, but we only need access to the the library itself, not the rest of the framework, so that should be ok (and in 18 years Apple has never made use of the framework versioning feature so Versions/A should remain reliable).
I haven't actually tested __propagatedImpureHostDeps but from the name I have to assume it will work. We may need to do something silly though like have the framework itself include a separate propagatedTargetBuildInput that's a shim derivation that actually defines __propagatedImpureHostDeps.

Alternatively we could modify stdenv.__extraImpureHostDeps to just include the frameworks directly, but that will then add them to the __impureHostDeps of every single stdenv.mkDerivation even if they don't use the frameworks.

Also see https://github.com/NixOS/nix/issues/2732

I looked into this and the frameworks actually already have __propagatedImpureHostDeps defined, it's just that this doesn't propagate because they're not propagated dependencies.
My guess is the logic for propagating the __propagatedImpureHostDeps itself is wrong, though I'm having a hard time tracing through it because I don't have a good grasp on the various build input types.

It looks like __propagatedImpureHostDeps only comes from propagatedBuildInputs, but does not come from buildInputs. I'm inclined to think that __propagatedImpureHostDeps just doesn't fit well into the model here, because there's two different reasons for needing impure host deps:

The derivation is a binary tool and needs impure host deps to run, and therefore any build step that invokes it needs the impure host deps too.
The derivation is a library so anything that links to it needs impure host deps.

For the first, only the immediate consumer needs the __impureHostDeps. For the second, everything that uses this derivation, directly or indirectly, may need it.
We could just optimize for the second and live with the sandbox being overly relaxed by including __propagatedImpureHostDeps from all buildInputs. Alternatively we could define a second set of host deps that distinguishes between the two cases.
That said, __propagatedImpureHostDeps is used so rarely that I'm inclined to just go with the first approach. In fact, outside of frameworks, it seems the only paths that are added is /usr/lib/libobjc.dylib, /usr/lib/libobjc.A.dylib, and /usr/lib/libc.dylib, which is pretty tame.

Not only do we need to change how __propagatedImpureHostDeps works for libraries to propagate more than one level up, it also turns out that our propagation of impure host deps and sandbox profile was also just completely broken since it used lib.concatLists instead of lib.flatten.
Fixing the concatLists vs flatten causes e.g. cargo to sprout reasonable __impureHostDeps, but it won't fix nested cases (e.g. binary A requires library B which requires Security.framework). Changing propagation should fix it, but either way we can end up with some pretty large __impureHostDeps lists, and this will cause pretty much the entire world to be rebuilt on darwin.
Given all that, my proposed patch looks like
diff --git a/pkgs/stdenv/generic/make-derivation.nix b/pkgs/stdenv/generic/make-derivation.nix
index a11b280b047..f392f9dffa1 100644
--- a/pkgs/stdenv/generic/make-derivation.nix
+++ b/pkgs/stdenv/generic/make-derivation.nix
@@ -164,21 +164,25 @@ in rec {
         lib.concatMap (input: input.__propagatedSandboxProfile or [])
           (stdenv.extraNativeBuildInputs
            ++ stdenv.extraBuildInputs
-           ++ lib.concatLists dependencies);
+           ++ lib.flatten dependencies);

       computedPropagatedSandboxProfile =
         lib.concatMap (input: input.__propagatedSandboxProfile or [])
-          (lib.concatLists propagatedDependencies);
+          (lib.flatten propagatedDependencies);

       computedImpureHostDeps =
         lib.unique (lib.concatMap (input: input.__propagatedImpureHostDeps or [])
           (stdenv.extraNativeBuildInputs
            ++ stdenv.extraBuildInputs
-           ++ lib.concatLists dependencies));
+           ++ lib.flatten dependencies));

+      # Unlike other propagations, we may need impureHostDeps to be made available on all indirect
+      # dependents. In particular, if the current derivation is a library, anything that indirectly
+      # links to it will need these.
       computedPropagatedImpureHostDeps =
         lib.unique (lib.concatMap (input: input.__propagatedImpureHostDeps or [])
-          (lib.concatLists propagatedDependencies));
+          (lib.flatten propagatedDependencies
+          ++ lib.flatten dependencies));

       derivationArg =
         (removeAttrs attrs

This does unfortunately mean that e.g. any frameworks used by cargo will end up propagating into the impure host deps of every single rust package, but AFAICT the only way to fix that is to explicitly denote which derivations are libraries and which are build tools.

It occurs to me that I think buildInputs vs nativeBuildInputs is supposed to be the difference between libraries and binaries used in the build, but I don't know if this is used correctly often enough to rely on it. Still, we could try only propagating buildInputs upwards and see what happens.

Ok this is still hurting my head, but I'm pretty sure our propagation logic is still wrong. Instead of propagating from all inputs, we need to only propagate from some. Rather, all inputs should probably go into __impureHostDeps but only some inputs should go into __propgatedImpureHostDeps. In particular, anything that's a build tool doesn't need to be propagated further upwards.
But I still don't understand the various dependency types well enough to tease apart which ones get propagated upwards and which don't.

It looks like __propagatedImpureHostDeps only comes from propagatedBuildInputs, but does not come from buildInputs. I'm inclined to think that __propagatedImpureHostDeps just doesn't fit well into the model here, because there's two different reasons for needing impure host deps:

The derivation is a binary tool and needs impure host deps to run, and therefore any build step that invokes it needs the impure host deps too.
The derivation is a library so anything that links to it needs impure host deps.

So should it be enough to just change all the cases of "type 2" to put the frameworks into the propagatedBuildInputs instead of buildInputs? This would be better than breaking the convention for the meaning of propagated inputs.

The propagation as it's implemented currently is definitively wrong. And no, derivations should not be putting frameworks in propagatedBuildInputs, because a library depending on a framework should not make that framework available to any other derivations that depend on the library. That would be wrong.

@lilyball What you propose in https://github.com/NixOS/nixpkgs/issues/67166#issuecomment-541277824 will enable infinite propagation of __propagatedImpureHostDeps. We probably should rename it to something else to underline the seriousness of this setting and to let users know that this is not the standard "propagated" logic.
I also wonder what kind of constraints we should set to put some limits on this. The only thing that comes to mind should not propagate through nativeBuildInputs (I guess, it should not propagate with any build-host-target offset change).

@veprbl Yeah the infinite propagation is why I'm holding off on pushing this change through. I think not propagating on any build-host-target offset change makes sense, but I still don't understand that system well enough to be able to say definitively.

Nix 2.3.5 has largely obsoleted this by simply adding /System/Library/Frameworks and /System/Library/PrivateFrameworks to the default sandbox paths on macOS. The downside is this means all system frameworks are accessible without being declared as dependencies. So in the long run it would still be better to fix the frameworks to use __propagatedImpureHostDeps and remove them from the default sandbox paths.

I don't think propagating inputs implicitly is a good idea, especially for impurities like this.  Might as well remove it all in that case.

I’m not sure what you mean, remove what all?

I don't think propagating inputs implicitly is a good idea, especially for impurities like this.

This isn’t propagating the full input, it’s propagating just the impurity. And the reason is because the sandbox doesn’t care about whether dependencies are direct or indirect, it only cares that they’re accessed somehow, so without punching a large hole in the sandbox (like we just did for Nix 2.3.5) we need a way to tell the sandbox “/System/Library/Frameworks/CoreFoundation.framework needs to be accessible at runtime if darwin.apple_sdk.frameworks.CoreFoundation exists anywhere in the dependency tree”, and that seems to be precisely what __propagatedImpureHostDeps does.


release:v0.1.1

add examples for faceDetector and markerDetector
update README
rebuild code

 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.cxs seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


router props function is ignored

Environment

Operating System: Darwin
Node Version:     v14.19.1
Nuxt Version:     3.5.1
Nitro Version:    2.4.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      app, modules, htmlValidator, css, components, postcss, i18n, hooks
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
inside the pages:extend hook
pages.push({
	name: 'some-route',
	path: '/some-route',
	file: '~/some-pages/some-route.vue',
	props: () => ({ someProp: 'modified value' }),
})

page component
export default defineNuxtComponent({
  name: 'some-route',
  props: {
    someProp: {
      type: String,
      default: 'original value',
    },
  },
})

Describe the bug
the props function is ignored. The page component will not receive someProp with a different value than the default one
if props is declared like this, it works
pages.push({
	name: 'some-route',
	path: '/some-route',
	file: '~/some-pages/some-route.vue',
	props: { someProp: 'modified value' },
})

Additional context
this worked properly in nuxt v2
Logs
No response

You cannot pass non-serialisable values in pages:extend as they need to be included in the runtime build. For non-serialisable values, you can use app/router.options: https://nuxt.com/docs/guide/going-further/custom-routing#using-router-config.

but
Nuxt will not augment any new routes you return from the routes function with metadata defined in definePageMeta of the component you provide. If you want that to happen, you should use the pages:extend hook which is [called at build-time](https://nuxt.com/docs/api/advanced/hooks#nuxt-hooks-build-time).
so this will mean that i will not take advantage of the page meta..
so I guess I will have to wait for this to be added in nuxt, right?

You will receive the meta in the routes() function and can do what you want with it.

I found this issue when upgrading nuxt3 from nxut2, so the only way is to define it using useRoute()? Is using defineNuxtComponent({meta:{base:'/'}}) no longer effective?