yarn start internal error

I'm trying to run cal with docker and I get the following error:
+ yarn start
Internal Error: @calcom/skiff@workspace:packages/app-store/skiff: This package doesn't seem to be present in your lockfile; run "yarn install" to update the lockfile
    at P0.getCandidates (/calcom/.yarn/releases/yarn-3.4.1.cjs:435:5145)
    at yf.getCandidates (/calcom/.yarn/releases/yarn-3.4.1.cjs:391:1264)
    at /calcom/.yarn/releases/yarn-3.4.1.cjs:439:7693
    at of (/calcom/.yarn/releases/yarn-3.4.1.cjs:390:11070)
    at ge (/calcom/.yarn/releases/yarn-3.4.1.cjs:439:7673)
    at async Promise.allSettled (index 44)
    at async $s (/calcom/.yarn/releases/yarn-3.4.1.cjs:390:10398)
    at async /calcom/.yarn/releases/yarn-3.4.1.cjs:439:8205
    at async ti.startProgressPromise (/calcom/.yarn/releases/yarn-3.4.1.cjs:390:47579)
    at async je.resolveEverything (/calcom/.yarn/releases/yarn-3.4.1.cjs:439:6233)

I just attempted to upgrade from v3.0.10 → v3.1.1 and experienced this same error on container initialization.
Workaround: Downgrade to v.3.1.0
In your calcom/docker code (basically the code from this repo), you will see there is a docker-compose.yml file. That file has the image definition. That file is version controlled, so don't touch it.
What you can do is use Docker Compose Overrides to override the image definition.
What you need to do

Create a docker-compose.override.yml file in the root of the Git source folder
Paste in the contents below
Attempt to bring your containers up again

docker-compose.override.yml:
# This file overrrides what is provided by Cal (or Calendoso)
version: '3.8'
services:
  calcom:
    image: calcom.docker.scarf.sh/calcom/cal.com:v3.1.0

🚨👉 This essentially sets the image to always be at v3.1.0. In the future, you will just need to update the file above to what version you want to use, but at least you'll explicit control over what version you want to run.

can you check again with :main?
:v3.1.2 will be available in about 20mins also for testing

It's fixed with v3.1.2 👍
I saw 3.1.3 is out, but I was able to get it up and running with 3.1.2 without the error reported by @mohammadrezza

Thanks for the testing!


Implement autograd.

NOTE: Can only be worked on after issue #62 is completed and closed.
Autograd is a feature which lets us backpropagate gradients by automatically computing the gradients on a Tensor.
Such features come in very handy when implementing deep neural networks.
You can use the following resource to implement autograd -<EMAIL_ADDRESS>

I am willing to work on this. @rohansingh9001 please assign this to me if possible.


Add ConfigNoticeInternalServerError

if true, NoticeError for http status >= 500

Fiber doesn't return errors for all statuses, so this provides the option of noticing http errors with status >= 500.
This approach could be generalized to ConfigNoticeHttpError(statusThreshold), in which the statusThreshold is the code above which NoticeError is triggered.

Hi there! Thank you for your contribution. I do some research about it and I think this here is what I found.
app.Get("/give-me-error", func(ctx *fiber.Ctx) error {
	err := customErr{Message: "wrong request", Code: 4329}
	ctx.Status(http.StatusBadRequest).JSON(err)
	return err
})
app.Get("/give-me-just-error", func(ctx *fiber.Ctx) error {
	err := customErr{Message: "wrong request", Code: 4329}
	ctx.Status(http.StatusBadRequest).JSON(err)
	return nil
})

And here is the result. Don't tackle with the counts.

I suppose this line ensures NewRelic gets the response status code. Here is some kind of proof I guess.

Apparently, the NewRelic agent itself has some rules about it. Maybe take a look at here.
This is what I found. Maybe I'm missing something but I'm waiting for your response.

Closing due to lack of response


add on_conflict for upsert

Requested feature
We need to use "on_conflict" parameter for upsert.
Like this: https://postgrest.org/en/v10.0/api.html?highlight=merge#on-conflict
Proposal

Use specific annotation in Criteria
Use specific annotation in Repository

Create @OnConflict annotation that allow to be in the both with prior Criteria > Repository


Suppports show views statement

What type of enhancement is this?
API improvement
What does the enhancement do?
Part of #3729
After  #4086, we can create a view and then find all the views by using the show full tables command in CLI. Below is an example:
mysql> create view test as select * from numbers limit 10;
Query OK, 0 rows affected (0.03 sec)

mysql> select * from test;
+--------+
| number |
+--------+
|      0 |
|      1 |
|      2 |
|      3 |
|      4 |
|      5 |
|      6 |
|      7 |
|      8 |
|      9 |
+--------+
10 rows in set (0.03 sec)

mysql> show full tables;
+---------+-----------------+
| Tables  | Table_type      |
+---------+-----------------+
| numbers | LOCAL TEMPORARY |
| test    | VIEW            |
+---------+-----------------+
2 rows in set (0.03 sec)

If GreptimeDB could support a statement like show views, which only queries views from information_schema.tables, I think it would be great:
mysql > show views;
+---------+
| Views  |
+---------+
| test    |
+---------+

Implementation challenges
Please make a note of the following details:

Implement the 'show views' parser and add the 'ShowViews' statement.

https://github.com/GreptimeTeam/greptimedb/blob/main/src/sql/src/parsers/show_parser.rs
https://github.com/GreptimeTeam/greptimedb/blob/main/src/sql/src/statements/show.rs

Implement the 'show_views' for 'StatementExecutor', similar to 'show_tables':

https://github.com/GreptimeTeam/greptimedb/blob/da0c8402619134d455242bd5c16e16a3b3955994/src/operator/src/statement/show.rs#L52

The actual task is performed in 'sql.rs':

https://github.com/GreptimeTeam/greptimedb/blob/da0c8402619134d455242bd5c16e16a3b3955994/src/query/src/sql.rs#L457

The developer can refer to 'show_tables' in 'sql.rs' and add a filter 'TABLE_TYPE = 'VIEW''.

Adds unit tests and sqlness tests https://github.com/GreptimeTeam/greptimedb/tree/main/tests/cases/standalone/common/show

May depends on https://github.com/GreptimeTeam/greptimedb/issues/4339
But querying from tables could work.

@lyang24 Thanks a lot.


Javascript/flow checker fails silently if flow-bin version is below 0.34

Summary
screencast reproducing the bug
Steps to reproduce:

Install flow-bin 0.33

$ yarn global add<EMAIL_ADDRESS>...
$ flow version
Flow, a static type checker for JavaScript, version 0.33.0

Open any .js file with flow errors
Expect: errors in location window
Got:

no errors reported
got the message: syntastic: 0.214280: CacheErrors: Checker javascript/flow is not available

(bonus)

update flow-bin

$ yarn global add<EMAIL_ADDRESS>...
$ flow version
Flow, a static type checker for JavaScript, version 0.34.0

Open the same .js file
Got some errors reported

Possible Root of the Evil
https://github.com/vim-syntastic/syntastic/blob/master/syntax_checkers/javascript/flow.vim#L28
Versions
Vim Version
:ver
NVIM 0.2.0-dev
Build type: RelWithDebInfo
Compilation: /usr/bin/x86_64-linux-gnu-gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-securit
y -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unu
sed-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINC
LUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -D_GNU_SOURCE -I/build/neovim-38GZXR/neovim-0.1.7ubuntu1+git20
1701281330+3091+23~ubuntu16.04.1/build/config -I/build/neovim-38GZXR/neovim-0.1.7ubuntu1+git201701281330+3
091+23~ubuntu16.04.1/src -I/build/neovim-38GZXR/neovim-0.1.7ubuntu1+git201701281330+3091+23~ubuntu16.04.1/
.deps/usr/include -I/build/neovim-38GZXR/neovim-0.1.7ubuntu1+git201701281330+3091+23~ubuntu16.04.1/.deps/u
sr/include -I/build/neovim-38GZXR/neovim-0.1.7ubuntu1+git201701281330+3091+23~ubuntu16.04.1/.deps/usr/incl
ude -I/build/neovim-38GZXR/neovim-0.1.7ubuntu1+git201701281330+3091+23~ubuntu16.04.1/.deps/usr/include -I/
build/neovim-38GZXR/neovim-0.1.7ubuntu1+git201701281330+3091+23~ubuntu16.04.1/.deps/usr/include -I/build/n
eovim-38GZXR/neovim-0.1.7ubuntu1+git201701281330+3091+23~ubuntu16.04.1/.deps/usr/include -I/usr/include -I
/build/neovim-38GZXR/neovim-0.1.7ubuntu1+git201701281330+3091+23~ubuntu16.04.1/build/src/nvim/auto -I/buil
d/neovim-38GZXR/neovim-0.1.7ubuntu1+git201701281330+3091+23~ubuntu16.04.1/build/include
Compiled by root@lgw01-31

Optional features included (+) or not (-): +acl   +iconv    +jemalloc +tui
For differences from Vim, see :help vim-differences

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Syntastic Version
Syntastic version: 3.8.0-21 (Vim 704, Neovim, Linux)
Info for filetype: javascript
Global mode: active
Filetype javascript is active
The current file will be checked automatically
syntastic: 975.810029: system: command run in 0.181361s
syntastic: 976.044979: system: command run in 0.230846s
Available checkers: eslint standard
Currently enabled checkers: -
syntastic: 976.046169: &shell = '/usr/bin/fish', &shellcmdflag = '-c', &shellpipe = '2>&1| tee', &shellquo
te = '', &shellredir = '>%s 2>&1', &shelltemp = 1, &shellxquote = '', &autochdir = 0, &shellxescape = ''

According to the search for usage of syntastic#util#versionIsAtLeast method, this is a common pattern to ignore checkers based on some minimal version.
So, this is a feature, but not a bug?
As for me, I expect some message explaining about flow-bin version below 0.34 is not suitable for Syntastic. This is at least not obvious :)

The root of all evil is you not reading the manual.  What you were supposed to do was:

read :h syntastic-javascript-flow; there, you'd find that:

Syntastic requires "Flow" version 0.34.0 or later.

install flow version 0.34.0 or later
run :SyntasticInfo javascript, and make sure flow is marked as available
add flow to g:syntastic_javascript_checkers.

As for me, I expect some message explaining about flow-bin version below 0.34 is not suitable for Syntastic. This is at least not obvious :)

That would be possible if syntastic tried to autodetect flow for you.  This is not how syntastic works.  Read the archives if you're curious to find out why autodetection doesn't make sense. shrug

@lcd047, first of all, sorry if my messages are looking bully or somewhat. I haven't done that deliberately :slightly_smiling_face:
I agree with you about reading the docs. Surely this is true - at least for the first-time set up. When I was setting up this initially, I read the docs and easily succeed thankful to them.
My current story is about mystic break of the flow checker. So, the story is the following.

I've had the flow checker working:

let g:syntastic_javascript_eslint_exec = 'eslint'
let g:syntastic_javascript_flow_exec = 'flow'
let g:syntastic_javascript_checkers = ['eslint', 'flow']

Then eventually, it has stopped working
The way I have been searching for the reason:

check flow starts from the shell
check .vimrc settings
let g:syntastic_debug = 1, got the message ...Checker javascript/flow is not available
google syntastic Checker is not available
finally, looked at the /syntax_checkers/javascript/flow.vim and have found the answer

The questions:

How often a user supposed reading the docs? (I'm really not sure about this)
What is the best way to be in touch with the breaking changes in Syntastic? (The changelog or anything else)

I've tried googling syntastic autodetection, syntastic autodetect and haven't succeed. Could you please give me a hint where can I read about this?

Re: breaking changes.  I do try to keep incompatible changes to a minimum.  I also try to document them to Changelog.  However, both are best effort attempts, not guarantees.  And people already grumble all day long about me rejecting changes to default options for this very reason.
If you want to minimise the effects of my fumbling to your workflow you get the choice between (1) installing only released versions of syntastic, or (2) following development and subscribing to this issue tracker.
If you install only releases, you'd only need to check your favourite checkers still work only when a new release comes out, which is about once a year or so.
On the other hand, if you subscribe to this issue tracker you can see all changes as they happen.  In particular, changing the minimum version requirement for flow happened in #1954, two weeks ago.  You can also find there the reason for the change, and the history behind it.
Re: autodetection.  Validating a checker for use with syntastic can be slow.  Running rubocop --version used to take ~5 seconds on some systems.  No idea if that's still the case, but you don't want to wait that long when you run checks for the first time in a session, particularly if you don't care about rubocop.  Also some checkers conflict with each other (f.i. GCC and AVR-GCC).  There is no set of options that works well for everybody, which is why you're supposed to configure the list of checkers explicitly.  Not doing so will cost you time.


hi I saw there is a problem in stacked line chart if there are nagitive an positive numbers they dont stack is there away to stack them togther?

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce

Context

Environment

Chart.js version:
Browser name and version:
Link to your project:

Please ask questions on StackOverflow: https://stackoverflow.com/questions/tagged/chart.js


Clarify paragraph introducing grid systems

Main reason for the PR is the first sentence: At first read, I thought "not an option" meant that they may not be used. Other slight language tweaks while I was at it. Thanks for creating this!

Thank you very much!


discard import-export from s-f on ios

import-export module is skipped in -sys crate, it should be discarded too from the "rusty" crate to build on ios.
As far as I can tell, without this change, current top of tree does not crosscompile to ios.

Oops! SecImportExport.h does appear in the iOS SDK, so I think we'll actually want to remove the #[cfg(target_os = "macos")] from the module in the sys crate.

Ah, but it doesn't include the stuff we're using.

This should un-break the build. Thanks!

It looks like we now ship iOS toolchains - I'll update the Travis configuration to at least build for iOS.

great news, thank a lot :)


[ACPROX] : (JS-0263) Detected the use of process.exit()

Description
The process.exit() method in Node.js is used to immediately stop the Node.js process and exit. This is a dangerous operation because it can occur in any method at any point in time, potentially stopping a Node.js application completely when an error occurs. For example:
Occurrences
There is 1 occurrence of this issue in ACPROX.
See all occurrences on DeepSource → app.deepsource.com/gh/dswan36/acprox/issue/JS-0263/occurrences/

Bad Practice
process.exit(1);
process.exit(0);

Recommended
Process.exit();
var exit = process.exit;


ENHANCEMENT location data endpoint not tied to Locator page in SiteTree

can you expand on this a bit? not sure which milestone this would go against

Moving to 3 milestone, this would be an endpoint like FoxyStripe where it's more of a custom route in cases of using SS only to manage the records.


Better exception prompt for ExistingVersionError

Sometimes I mistake to push samge gem with same version twice, and I got
Internal Server Error
 in the console.
Maybe we can improve it and prompt cli a better message.
Tell me if I can help~

@42thcoder Thank you very much for your report!
This report is a duplicate of #99. Can we close this issue?


Segmentation fault (core dumped) when running test.py

Hi,
when i input "python3 test.py", I got an error. I have modified cfg['parallel'] = False.
[root@localhost lib]# python3 test.py
........
g++ -pthread -shared -B /root/miniconda3/compiler_compat -L/root/miniconda3/lib -Wl,-rpath=/root/miniconda3/lib -Wl,--no-as-needed -Wl,--sysroot=/ /tmp/tmpn14w7ygm/home/sly/minionn/lib/minionnMath.o /tmp/tmpn14w7ygm/home/sly/minionn/lib/minionnCrypto.o /tmp/tmpn14w7ygm/home/sly/minionn/lib/minionnABY.o /tmp/tmpn14w7ygm/home/sly/minionn/lib/.rendered.minionn.o -lseal bin/libaby.a -lssl -lcrypto -lgmp -lgmpxx -lpthread -o /tmp/tmpn14w7ygm/minionn.cpython-37m-x86_64-linux-gnu.so
copying /tmp/tmpn14w7ygm/minionn.cpython-37m-x86_64-linux-gnu.so -> /home/sly/minionn/lib
Segmentation fault (core dumped)
What's going on? Thanks!

That is a little bit tricky, I don't know what is going on there. Maybe try to test SEAL and ABY independently. E.g. take some elements out of the minionn.cpp and only test minionnMath for example. If that works, add minionnCrypto etc.
That way you at least see if the error is with Python, C++, SEAL, or ABY (or anything else).

Hi,
when i input "python3 test.py", There is an error.
[root@localhost lib]# python3 test.py
g++ -pthread -shared -B /root/miniconda3/compiler_compat -L/root/miniconda3/lib -Wl,-rpath=/root/miniconda3/lib -Wl,--no-as-needed -Wl,--sysroot=/ /tmp/tmpyjs5w9nr/home/sly/lib/lib/minionnMath.o /tmp/tmpyjs5w9nr/home/sly/lib/lib/minionnCrypto.o /tmp/tmpyjs5w9nr/home/sly/lib/lib/minionnABY.o /tmp/tmpyjs5w9nr/home/sly/lib/lib/.rendered.minionn.o -lseal bin/libaby.a -lssl -lcrypto -lgmp -lgmpxx -lpthread -o /tmp/tmpyjs5w9nr/minionn.cpython-37m-x86_64-linux-gnu.so -shared
copying /tmp/tmpyjs5w9nr/minionn.cpython-37m-x86_64-linux-gnu.so -> /home/sly/lib/lib
Traceback (most recent call last):
File "test.py", line 15, in
m = cppimport.imp("minionn")
File "/root/miniconda3/lib/python3.7/site-packages/cppimport/importer.py", line 84, in imp
return imp_from_filepath(filepath, fullname)
File "/root/miniconda3/lib/python3.7/site-packages/cppimport/importer.py", line 78, in imp_from_filepath
load_module(module_data)
File "/root/miniconda3/lib/python3.7/site-packages/cppimport/importer.py", line 41, in load_module
_load_module(module_data)
File "/root/miniconda3/lib/python3.7/site-packages/cppimport/importer.py", line 34, in _load_module
module_data['module'] = importlib.import_module(module_data['fullname'])
File "/root/miniconda3/lib/python3.7/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1006, in _gcd_import
File "", line 983, in _find_and_load
File "", line 967, in _find_and_load_unlocked
File "", line 670, in _load_unlocked
File "", line 583, in module_from_spec
File "", line 1043, in create_module
File "", line 219, in _call_with_frames_removed
ImportError: /home/sly/lib/lib/minionn.cpython-37m-x86_64-linux-gnu.so: undefined symbol: EVP_CIPHER_CTX_init
What's going on? I have installed libssl libcrypto, Thanks!

Hi @shenliyan
I think you might need to update SEAL to the latest updated version.
Since when I ran this program, the problem is from the SEAL.

@shenliyan Hello, I have the same problem.
How did you solve it?

If you solve this, I am happy to accept pull requests. I am not actively supporting this code anymore but I am willing to put in some effort to keep the code usable.


fix: generate_starknet_os_resources python target fix

This change is

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

Comparison is base (d017ea6) 69.64% compared to head (ad6d375) 69.64%.

Additional details and impacted files
@@              Coverage Diff              @@
##           main-v0.13.1    #1541   +/-   ##
=============================================
  Coverage         69.64%   69.64%
=============================================
  Files                59       59
  Lines              8173     8173
  Branches           8173     8173
=============================================
  Hits               5692     5692
  Misses             2015     2015
  Partials            466      466

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

Python PR


Changes to SDFITS format

Resolve  #106

Hello @matteobachetti! Thanks for submitting the PR.

In the file srttools/converters/sdfits.py, following                are the PEP8 issues :

Line 482:29: E127 continuation line over-indented for visual indent


Adjust CLI logging level

By default the CLI shows a bunch of detailed errors:
./chain-bench scan --repository-url https://github.com/buildsec/frsca --access-token $GITHUB_TOKEN -o ./results
2022-06-17 09:10:07 INF 🚩 Fetch Starting
2022-06-17 09:10:08 ERR error in fetching organization hooks error="GET https://api.github.com/orgs/buildsec/hooks: 404 Not Found []"
2022-06-17 09:10:08 INF 🏢 Fetching Organization Settings Finished
2022-06-17 09:10:08 ERR error in fetching org packages error="GET https://api.github.com/orgs/buildsec/packages?package_type=npm&state=active: 403 You need at least read:packages scope to list packages. []"
2022-06-17 09:10:13 ERR error in fetching hooks data error="GET https://api.github.com/repos/buildsec/frsca/hooks: 404 Not Found []"
2022-06-17 09:10:13 INF 🛢 Fetching Repository Settings Finished
2022-06-17 09:10:13 ERR error in fetching branch protection error="GET https://api.github.com/repos/buildsec/frsca/branches/main/protection: 404 Not Found []"
2022-06-17 09:10:13 INF 🌱 Fetching Branch Protection Settings Finished
2022-06-17 09:10:13 INF 👫 Fetching Members Finished
2022-06-17 09:10:13 WRN file .github/workflows/ci.yaml not found
2022-06-17 09:10:14 WRN file dynamic/pages/pages-build-deployment not found
2022-06-17 09:10:14 INF 🔧 Fetching Pipelines Finished
2022-06-17 09:10:14 INF 🏁 Fetch succeeded

But these errors just clutter the output, and are not very useful unless debugging information is needed. These types of details should be displayed for debug or tracing log level.
As a user I should be able to adjust the log level from the CLI, for example by supplying -v flags (1 for info, 2 for debug, 3 for trace).

Something like this?
https://github.com/aquasecurity/chain-bench/blob/45436aeac3894dd20218f89c06e9fc8d16c21a1b/internal/commands/flags.go#L20-L22

@rgreinho Thanks again for your contributions!
So just to clarify, your suggestion is to remove the full error message from the printer when we get an error?

Thanks Remy! @rgreinho
I like the idea of using the verbosity flag to determine the log level, it doesn't have much use on its own anyway.
I'm also thinking to use the quiet flag as the opposite of verbose, to adjust the log level the other way.
Fix coming soon.


Menu Nav - Position Fixed on mobile

I think the menu nav should be fixed on mobile.
I changed a little the css to position absolute only in Desktop views, because it uses already the bootstrap class navbar-fixed-top.

This is more a design choice rather than a function that I want to add into the base theme.


Missing New-VSEC2VPCEndpointService in "VaporShell/Public/Resource Types"

This function is missing because it is missing from the us-east-1 cfn spec json file, so automation reliant on it being present there isn't including it.
I reference the issue here with the CloudFormation documentation folks: Missing AWS::EC2::VPCEndpointService ResourceType in CloudFormationResourceSpecification.json for Most Regions
The automation you are using should automatically fix this once they introduce it to the proper CFN spec files, but I'm not sure how long that will take. Thought I'd give a heads up since my tooling recently discovered it missing from the spec files.

Hey @ScriptAutomate - apologies on slowness in ack'ing this. I'm working on rolling your suggestions for the documentation updates in now, which includes parsing the other spec files outside of us-east-1's for any missing resources and properties, which should catch odd ones out like this. I appreciate digging into it and raising awareness! I'll close this out once the new version is pushed, should be today if time allows!

Got it sorted to do the initial pull on us-east-1, then check the remaining spec sheets for anything missing. Working well so far:

Had to make a few adjustments to the CFNHelp module gist you shared to integrate with the build process, but this is getting rolled out shortly. Snippet including the updated help content of Get-Help New-VSEC2VPCEndpointService -Full for reference:

Awesome! Looks like you're picking up stragglers just fine (including two new ones!), and the  expansion of the property descriptions looks great.
A side note, more related to the feature request of comment-base help doc expansion in #61 is that I noticed that the Description (and optionally, the Synopsis) is still the previous default. The CFNHelp comes up with additional values for those (though it looks like my poc parsing may have left in some open parentheses where it didn't need to):
PS > $HelpDocs = New-CFNHelpDoc
PS > $HelpDocs | Where-Object -Property FunctionName -like "New-VS*VPCEndpointService"                                                                                FunctionName : New-VSAWSEC2VPCEndpointService
FunctionName : New-VSAWSEC2VPCEndpointService
Description  : Specifies a VPC endpoint service configuration to
               which service consumers (AWS accounts, IAM users, and
               IAM roles can connect. Service consumers can create
               an interface VPC endpoint to connect to your service.
               To create an endpoint service configuration, you must
               first create a Network Load Balancer for your service.
Links        : {http://docs.aws.amazon.com/AWSCloudFormation/latest/U
               serGuide/aws-resource-ec2-vpcendpointservice.html}
Parameters   : {@{ParameterName=AcceptanceRequired;
               ParameterDescription=Indicates whether requests from
               service consumers to create an endpoint to your
               service must be accepted.},
               @{ParameterName=NetworkLoadBalancerArns;
               ParameterDescription=The Amazon Resource Names ARNs
               of one or more Network Load Balancers for your
               service.}}
Synopsis     : Specifies a VPC endpoint service configuration to
               which service consumers (AWS accounts, IAM users, and
               IAM roles can connect. Service consumers can create
               an interface VPC endpoint to connect to your service.

Ahhhhhhhhhh I completely missed that and it would be easy to add! Thank you for the reminder! I'll get it added in as well, easy add since I already have the info as noted :D

Testing the addition now, then pushing out 2.9.1 with the updated info.

Looking nice, pushing momentarily:

v2.9.1 pushed with the added help bits. Thanks again!
PS - You can see the updated functions in the ci folder of the repo: https://github.com/scrthq/VaporShell/tree/master/ci
They're called from the Convert-SpecToFunction function during the CI's Build stage

AWS::EC2::VPCEndpointService is now in the us-east-1 resource specification itself as well


V4.0.0 - MultiStorage upgrade!

Status
IN DEVELOPMENT
Breaking Changes
NO
Description-0
MultiStorage upgrade!

In-memory Temporal storage
File-per-Bloc storage, by Duplex of default cache and CellMultiplexer
All to single file storage, by Duplex of default cache and CellSinglet

AES Encryption

Use StringCell to save plain data
Use AESCell(BinaryCell) to save encrypted binary
Use AESCell(Base64Cell(StringCell)) to save encrypted base64 encoded text

Safe Mode!

Use safeSync to prevent data loss on switching multi-storage modes
Non-breaking upgrade from v3.1.0 to v4.0.0

Description-1
I have 2 branches on my repo.
break-test-v3 with hydrated bloc v3.1.0
break-test-v4 with hydrated bloc v4.0.0
It is used to ensure data compatibility between versions
Description-2
The Plan B is to comment out interface for AES encryption, and release it with v4.1.0.
The Plan A is not to comment out code and fix aes/plain compatibility in this release.
Description-3: Benchmark included!
$ cd benchmark
$ flutter run --release

Clear benefits of having different storages
Description-4
This is merge of mine v4.0.0 into your's v4.0.0

@orsenkucher I took a quick look over the changes and I am wondering based on the benchmarks which is the most performant solution so far? I personally think we should carefully select the default storage mechanism and bundle that with the package and move other HydratedStorage implementations to separate package(s). Let me know what you think 👍

@felangel
Currently single file storage is needed to be v3.1.0 compatible, but multi-file does significantly better writes and is magnitudes better for encrypted writes

@orsenkucher can we close this PR now that we've merged #52?

💯 Yes! @felangel


Documentation Error

At your website for this project: bkaradzic.github.io/bgfx
If your looking on how to open a window using the SDL library. What the example code does not tell you is that you also have to include the file SDL_syswm.h before bgfxplatform.h
It took me a bit to figure this out, and I found this out looking in the source code for a clue.Because on line 257 it says: If SDL_syswm.h is included before bgfxplatform.h we can enable SDL window If you don't do this then you get the following error when trying to call sdlSetWindow, namespace "bgfx" has no member "sdlSetWindow"
So it would be a good idea to edit the example code about opening a SDL window.

I moved initialization code inside SDL and GLFW, that way it's clear what's going on:
https://github.com/bkaradzic/bgfx/commit/939829f88c96f772b2af7b79c9c54cc05816940a


Change SIGINFO to SIGUSR1

SIGINFO only exists in newest version of python 2.7.11

Thanks Valentin,


Test for deploy hint in cairo 1

Codecov Report

Merging #544 (e19ef6c) into main (eedbc30) will decrease coverage by 0.10%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #544      +/-   ##
==========================================
- Coverage   90.87%   90.78%   -0.10%
==========================================
  Files          52       52
  Lines        9956     9966      +10
==========================================
  Hits         9048     9048
- Misses        908      918      +10

Impacted Files
Coverage Δ

.../business_logic/execution/execution_entry_point.rs
96.83% <ø> (ø)

...rc/core/syscalls/business_logic_syscall_handler.rs
55.16% <0.00%> (-0.50%)
:arrow_down:

src/core/syscalls/syscall_request.rs
69.51% <0.00%> (+0.42%)
:arrow_up:

... and 17 files with indirect coverage changes


[Resume] [Content] Create index.html

Content for the file is mentioned here, level 4 Збираємо website докупи
Pay attention to emoji

will be performed in Homepage project


@conda-forge-admin, please rerender

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

You can probably just rerun the circleci job for this, it appears to have been a temporary failure.

Nice catch. Done and relabled.


get_anndata is slow for large gene lists

Due to an issue with TileDB query conditions, var/obs queries with very large number of values used in an in expression will be very slow (time is roughly linear to the number of items in the list).
For example, if this query has a very large list of lung_genes, it will be very slow.
lung_genes = list(lung_var["feature_id"])
lung_adata = cell_census.get_anndata(
    census,
    organism="Homo sapiens",
    obs_query={"tissue_general": "lung", "is_primary_data": True},
    var_query={"feature_id": lung_genes},
)

This expands to a value_filter on the var DataFrame that looks like feature_id in ["gene1", "gene2", ..., "geneN"], which currently has performance roughly O(N), where N is the number of possible matches (right side of the in operator).
a MUCH faster alternative is to directly use the soma_joinids (coordinates) and skip the table scan.
The filter issue has been reported to TileDB. Still considering an appropriate work-around for the get_anndata API.  It may be helpful to expose the coords that the underlying experiment query supports.

Update:  ETA from TileDB for a fix to the underlying query condition is late Q1.

@bkmartinjr: This issue is now just waiting for the TileDB fix for the underlying query condition, right? Unless we want to add performance tests it seems this isn't actionable.  Close?

I don't think we should add any work-arounds.
I was leaving it open to track the issue on our side, as we don't have access to their tracking system. I didn't want to lose sight of our need for this to be fixed soon.  Do you have an alternative preference for tracking these types of dependencies?

I don't think we should add any work-arounds.
I was leaving it open to track the issue on our side, as we don't have access to their tracking system. I didn't want to lose sight of our need for this to be fixed soon. Do you have an alternative preference for tracking these types of dependencies?

Added a (new) blocked label for now.

Update: ETA from TileDB for a fix to the underlying query condition is late Q1. Tracking id 24310

@ebezzi to follow up with TileDB to understand if this is unblocked. In the future, we will request that TileDB open a corresponding github issue that can block issues like this one.

No need to ask - I already did two weeks ago :-).
The enhancement is slated for TileDB core v 2.16, which is imminent.  After that, it simply requires incorporation into tiledbsoma.

Update: verified that this is resolved by the tiledbsoma 1.5RC. Awaiting the actual 1.5 release, after which the cellxgene-census package will release with an updated dependency pin.


Fix minor format mistakes (and typo) in docs

Can one of the admins verify this patch?

Jenkins, test this please

Coverage decreased (-0.1%) to 81.883% when pulling da8033608c3f4f63c7f337adb010cbe490c0edde on kkaneda:kaneda/fix_minor_format_miss_in_doc into fe1cba2177e529fdf7f2995329f73886b4ecf2ae on bigdatagenomics:master.

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

Thank you for the contribution, @kkaneda!


menu typography

Can we change to all caps with spacing between letters?
also use + instead of & like this:
K I D S  +  S T U D E N T S

Yeah, I can increase the kerning.

I'll update #389 to use a + instead of an &.

I see + is already used instead of & in Kids + Students. So only changing to all caps is left?

Yes. And I would do it with css, instead of actually changing the text. Thanks!

Can I take this up ?

Sure.

@keelyjay I tried this out and it seems a little shouty...
Before:

After:


Use aframe instead of aframe-core

Since aframe-core is now deprecated/moved

Already on dev branch

ah, didn't see you had a dev branch. thanks, m8!


colon symbol vanishing from variable output

: colon is not shown in variables output:
$var = "ff:gg"
 => "ff:gg"
20:>> notify { $var: }
 => Puppet::Type::Notify {
  loglevel => notice,
   message => "ffgg",
      name => "ffgg",
     title => "ffgg",
  withpath => false
}

or:
$var_again = "ff\:gg"
notify { $var_again: }
 => Puppet::Type::Notify {
  loglevel => notice,
   message => "ff\\gg",
      name => "ff\\gg",
     title => "ff\\gg",
  withpath => false
}

That issue might be caused by this:
https://github.com/nwops/puppet-debugger/blob/master/lib/awesome_print/ext/awesome_puppet.rb#L57
I'll dig into this later.


DotNetCoreRestore: dotnet restore no longer supports globbing

As pointed here by @mmisztal1980, dotnet restore no longer supports globbing on the root parameter. The XML docs on DotNetCoreRestore are OK, but the example shows a string with a globbing pattern. I also came across this problem and an issue wasn't created yyet.
@patriksvensson suggested that the root parameter on DotNetCoreRestore could become a DirectoryPath. However, on dotnet restore it actually can be a list of project.json, global.json or root directory.

Is there any type on cake that can represent both files and directory paths?
Maybe we could have a params argument?

I believe the same applies to dotnet test

@andycmaj Is this related to your issue #985?


Add IPv6 wildcard for dualstack proxies and correct ipv6 wildcard

Please provide a description of this PR:
Fixes #46743. This PR also changes the ipv6 wildcard from ::/0 to ::. I'm not sure if this counts as a bug fix because I'm not sure how any ipv6 wildcard listeners ever worked. I'll let networking maintainers advise on whether or not this needs a release note.

@keithmattix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
964cd674659bfaa177b021584465649736c49003
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test release-notes

unit-tests-arm64_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test release-notes

unit-tests-arm64_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test unit-tests-arm64

unit-tests_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn Looks like WorkloadEntries shouldn't have clusterVIPs (which makes sense on the face of it). We also probably don't want clusterVIPs if endpoints are set?

not sure I am following why we are relating VIP (service) to endpoints
here? You definitely may be right, my knowledge is fuzzy here
On Thu, Aug 31, 2023, 3:30 PM Keith Mattix II @.***>
wrote:

@howardjohn https://github.com/howardjohn Looks like WorkloadEntries
shouldn't have clusterVIPs (which makes sense on the face of it). We also
probably don't want clusterVIPs if endpoints are set?
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/46795#issuecomment-1701865348, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXIIR2LPGY2IXZFFU73XYEGAXANCNFSM6AAAAAA4GT3F2Y
.
You are receiving this because you were mentioned.Message ID:
@.***>

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test release-notes

unit-tests-arm64_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test unit-tests-arm64

unit-tests_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test unit-tests

integ-pilot-multicluster_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Sorry I meant endpoints on the ServiceEntry resource; the clusterVIP addition is happening in the serviceentry -> model.Service conversion. I'm wondering if the test failures are just because I didn't update unit test structs or if something is actually broken (i.e. depending on now clusterVIP being set

Would appreciate @ramaraochavali @stevenctl and others' feedback on this

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test unit-tests-arm64

unit-tests_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test unit-tests

integ-pilot-multicluster_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test integ-pilot-multicluster

release-notes_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test unit-tests

integ-pilot-multicluster_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test integ-pilot-multicluster

release-notes_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test release-notes

integ-basic-arm64_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test integ-pilot-multicluster

release-notes_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test release-notes

integ-basic-arm64_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-basic-arm64

integ-ds_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ds

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test integ-pilot-multicluster

release-notes_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test release-notes

integ-basic-arm64_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-basic-arm64

integ-ds_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ds

integ-ipv6_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ipv6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test integ-pilot-multicluster

release-notes_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test release-notes

integ-basic-arm64_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-basic-arm64

integ-ds_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ds

integ-ipv6_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ipv6

integ-distroless_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-distroless

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test integ-pilot-multicluster

release-notes_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test release-notes

integ-basic-arm64_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-basic-arm64

integ-ds_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ds

integ-ipv6_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ipv6

integ-distroless_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-distroless

integ-ambient_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test integ-pilot-multicluster

release-notes_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test release-notes

integ-basic-arm64_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-basic-arm64

integ-ds_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ds

integ-ipv6_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ipv6

integ-distroless_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-distroless

integ-ambient_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test integ-pilot-multicluster

release-notes_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test release-notes

integ-basic-arm64_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-basic-arm64

integ-ds_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ds

integ-ipv6_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ipv6

integ-distroless_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-distroless

integ-ambient_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-istiodremote

integ-pilot_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test integ-pilot-multicluster

release-notes_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test release-notes

integ-basic-arm64_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-basic-arm64

integ-ds_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ds

integ-ipv6_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ipv6

integ-distroless_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-distroless

integ-ambient_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-istiodremote

integ-pilot_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot

integ-cni_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
f7a0ebd8f1864348696e08b315bf95ad7bdb0256
link
true
/test integ-pilot-multicluster

release-notes_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test release-notes

integ-basic-arm64_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-basic-arm64

integ-ds_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ds

integ-ipv6_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ipv6

integ-distroless_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-distroless

integ-ambient_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-istiodremote

integ-pilot_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot

integ-cni_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-cni

integ-pilot-istiodremote-mc_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test release-notes

integ-basic-arm64_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-basic-arm64

integ-ds_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ds

integ-ipv6_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ipv6

integ-distroless_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-distroless

integ-ambient_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-istiodremote

integ-pilot_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot

integ-cni_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-cni

integ-pilot-istiodremote-mc_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-basic-arm64

integ-ds_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ds

integ-ipv6_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ipv6

integ-distroless_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-distroless

integ-ambient_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-istiodremote

integ-pilot_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot

integ-cni_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-cni

integ-pilot-istiodremote-mc_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-multicluster

release-notes_istio
4d9d592cad8da058856b1d6d7cf3828881f77b7d
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-distroless

integ-pilot-istiodremote_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-istiodremote

integ-pilot_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot

integ-cni_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-cni

integ-pilot-istiodremote-mc_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
b8d57b737be7ed918aea691de550ac8813304ff3
link
true
/test integ-pilot-multicluster

release-notes_istio
4d9d592cad8da058856b1d6d7cf3828881f77b7d
link
true
/test release-notes

integ-ambient_istio
4d9d592cad8da058856b1d6d7cf3828881f77b7d
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
4d9d592cad8da058856b1d6d7cf3828881f77b7d
link
true
/test integ-ambient

release-notes_istio
1a5f169fd8d17f0d3cdde1848fab7b801c0afd24
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest release-notes_istio

@keithmattix: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test analyze-tests
/test bookinfo-build
/test gencheck
/test integ-ambient
/test integ-basic-arm64
/test integ-cni
/test integ-distroless
/test integ-ds
/test integ-helm
/test integ-ipv6
/test integ-operator-controller
/test integ-pilot
/test integ-pilot-istiodremote
/test integ-pilot-istiodremote-mc
/test integ-pilot-multicluster
/test integ-security
/test integ-security-istiodremote
/test integ-security-multicluster
/test integ-telemetry
/test integ-telemetry-istiodremote
/test integ-telemetry-mc
/test lint
/test release-notes
/test release-test
/test unit-tests
/test unit-tests-arm64

The following commands are available to trigger optional jobs:

/test benchmark
/test experimental-tracing
/test integ-assertion

Use /test all to run the following jobs that were automatically triggered:

analyze-tests_istio
gencheck_istio
integ-ambient_istio
integ-basic-arm64_istio
integ-cni_istio
integ-distroless_istio
integ-ds_istio
integ-helm_istio
integ-ipv6_istio
integ-operator-controller_istio
integ-pilot-istiodremote-mc_istio
integ-pilot-istiodremote_istio
integ-pilot-multicluster_istio
integ-pilot_istio
integ-security-istiodremote_istio
integ-security-multicluster_istio
integ-security_istio
integ-telemetry-istiodremote_istio
integ-telemetry-mc_istio
integ-telemetry_istio
lint_istio
release-notes_istio
release-test_istio
unit-tests-arm64_istio
unit-tests_istio

In response to this:

/retest release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/test release-notes_istio

@keithmattix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio
1a5f169fd8d17f0d3cdde1848fab7b801c0afd24
link
true
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@keithmattix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-distroless

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-distroless

integ-basic-arm64_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-distroless

integ-basic-arm64_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-distroless

integ-basic-arm64_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot-istiodremote

integ-cni_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-distroless

integ-basic-arm64_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot-istiodremote

integ-cni_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-cni

integ-pilot_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-distroless

integ-basic-arm64_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot-istiodremote

integ-cni_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-cni

integ-pilot_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-distroless

integ-basic-arm64_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot-istiodremote

integ-cni_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-cni

integ-pilot_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-security-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-distroless

integ-basic-arm64_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot-istiodremote

integ-cni_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-cni

integ-pilot_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-security-istiodremote

integ-security_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-distroless

integ-basic-arm64_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot-istiodremote

integ-cni_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-cni

integ-pilot_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-security-istiodremote

integ-security_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-security

integ-security-multicluster_istio
f78eea6e7e92d0a7d22c66ed56f9c36abf172f52
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

LGTM


Jupyter Plugin: Add resource limit spec to pipelines

Adds method for adding GPUs (resource_limits spec) to pipelines spawned by the jupyter extension

 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.

Closing for #9119


Bug: Method Spoofing Validation

Describe the bug
While attempting to send a PUT request to my RESTapi endpoint to update a record I found that if I also want to pass a file in my request I could not get "$this->validate($rules)" to work.
So after changing my request to $_POST and using method spoofing to change the request method to PUT still did not fix the issue.
CodeIgniter 4 version
v4.0.2
Affected module(s)
method withRequest
Expected behavior, and steps to reproduce if appropriate
the issue comes at line 322 of Validation.php file where
if (in_array($request->getMethod(), ['put', 'patch', 'delete'])) { 	$this->data = $request->getRawInput(); }
in case anyone attempts to pass $_FILES in the request $this->data will be empty.
Maybe a solution would be to change the if statement
if (in_array($request->getMethod(), ['put', 'patch', 'delete']) && $_SERVER['REQUEST_METHOD'] != 'POST')
So that if the initial request is POST then no reason to grab raw input.
Issue #880 seemed similar but not exactly.

Upload file muse use multipart/form-data, php just parse this in POST before CI,
If we want to parse the data again, we must implement the parser.
In my opinion. Files should not be uploaded in RESTful.

After doing some random tests, it appears that when using a $this->resource('controller') routing rule
`$routes->resource('photos');
// Equivalent to the following:
....
$routes->put('photos/(:segment)',      'Photos::update/$1');
....
@lonnieezell,  even though the rule is for PUT requests (based on docs), you still can make a POST request and theupdate` method works just fine and uploads the file, so maybe the documentation should be adjusted.

The biggest problem with this is that it assumes that a PUT request should operated just like a POST request. And they shouldn't. According to the spec a PUT request is to allow putting the body of the request at a specific location. So, it cannot accept multiple files. If an image would be sent via a PUT request, it should be only the data for the image.


Adobe apps paths have changed again

Dock needs updating

Bad:
"_CFURLString" = "file:///Applications/Adobe%20InDesign%20CC%202015/Adobe%20InDesign%20CC%202015.app";

Good:
"_CFURLString" = "file:///Applications/Adobe%20InDesign%20CC%202015/Adobe%20InDesign%20CC%202015.app/";


how to write a java code snippet

how to write a java code snippet like this format
if(cursor ==null) {
	Log.w(TAG,"....");
}else{
	while(cursor.moveToNext()){
		//do someting ....


fix localization demo launch file and tf_speed_control_node to use use_sim_time

Fix multi-floor localization demo launch file to use_sim_time parameter
Fix tf_speed_control_node to use use_sim_time parameter

This change has a small conflict with https://github.com/CMU-cabot/cabot-navigation/pull/103
To resolve the conflict, it is necessary to remove or comment out these lines
https://github.com/CMU-cabot/cabot-navigation/pull/104/files#diff-a2643cd185a851c155121f9e0dc48c2296fdb531e202ba4f00835a57e8007a32R227-R232

This looks similar to #114. Can we close this?

#114

My apologies, I should have closed this Pull Request before opening https://github.com/CMU-cabot/cabot-navigation/pull/114.


upgrade weirdly failed, and can't restart now

 $ edgedb server upgrade --nightly
The following commands will be run with elevated privileges using sudo:
    sudo apt-key add -
    sudo apt-get update
    sudo DEBIAN_FRONTEND=noninteractive _EDGEDB_INSTALL_SKIP_BOOTSTRAP=1 apt-get install -y edgedb-server-1-alpha8-dev5340
Depending on system settings sudo may now ask you for your password...
 Done
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://packages.edgedb.com/apt focal InRelease' doesn't support architecture 'i386'
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://packages.edgedb.com/apt focal.nightly InRelease' doesn't support architecture 'i386'
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  gconf-service gconf-service-backend gconf2-common libappindicator1 libaribb24-0 libbasicusageenvironment1 libc++1 libc++1-10
  libc++abi1-10 libcddb2 libdbusmenu-gtk4 libdvbpsi10 libebml4v5 libgconf-2-4 libgroupsock8 libixml10 liblirc-client0
  liblivemedia77 libmatroska6v5 libnfs13 libopenmpt-modplug1 libplacebo7 libprotobuf-lite17 libresid-builder0c2a libsdl-image1.2
  libsdl1.2debian libsidplay2 libspatialaudio0 libupnp13 libusageenvironment3 libva-wayland2 libxcb-xv0 vlc-bin vlc-data vlc-l10n
  vlc-plugin-base vlc-plugin-notify vlc-plugin-qt vlc-plugin-samba vlc-plugin-skins2 vlc-plugin-video-output
  vlc-plugin-video-splitter vlc-plugin-visualization
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libnss-systemd libpam-systemd libsystemd0 systemd systemd-sysv systemd-timesyncd
Suggested packages:
  systemd-container
The following NEW packages will be installed:
  edgedb-server-1-alpha8-dev5340
The following packages will be upgraded:
  libnss-systemd libpam-systemd libsystemd0 systemd systemd-sysv systemd-timesyncd
6 upgraded, 1 newly installed, 0 to remove and 108 not upgraded.
Need to get 24,7 MB of archives.
After this operation, 148 MB of additional disk space will be used.
Get:1 http://tr.archive.ubuntu.com/ubuntu focal-updates/main amd64 libnss-systemd amd64 245.4-4ubuntu3.4 [95,9 kB]
Get:2 http://tr.archive.ubuntu.com/ubuntu focal-updates/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.4 [28,1 kB]
Get:3 http://tr.archive.ubuntu.com/ubuntu focal-updates/main amd64 systemd-sysv amd64 245.4-4ubuntu3.4 [10,3 kB]
Get:4 http://tr.archive.ubuntu.com/ubuntu focal-updates/main amd64 libpam-systemd amd64 245.4-4ubuntu3.4 [186 kB]
Get:5 http://tr.archive.ubuntu.com/ubuntu focal-updates/main amd64 systemd amd64 245.4-4ubuntu3.4 [3.805 kB]
Get:6 https://packages.edgedb.com/apt focal.nightly/main amd64 edgedb-server-1-alpha8-dev5340 amd64 1.0a8.dev5340+g76e0688b-2021012101~focal.nightly [20,3 MB]
Get:7 http://tr.archive.ubuntu.com/ubuntu focal-updates/main amd64 libsystemd0 amd64 245.4-4ubuntu3.4 [273 kB]
Fetched 24,7 MB in 6s (4.038 kB/s)
(Reading database ... 280220 files and directories currently installed.)
Preparing to unpack .../0-libnss-systemd_245.4-4ubuntu3.4_amd64.deb ...
Unpacking libnss-systemd:amd64 (245.4-4ubuntu3.4) over (245.4-4ubuntu3.3) ...
Preparing to unpack .../1-systemd-timesyncd_245.4-4ubuntu3.4_amd64.deb ...
Unpacking systemd-timesyncd (245.4-4ubuntu3.4) over (245.4-4ubuntu3.3) ...
Preparing to unpack .../2-systemd-sysv_245.4-4ubuntu3.4_amd64.deb ...
Unpacking systemd-sysv (245.4-4ubuntu3.4) over (245.4-4ubuntu3.3) ...
Preparing to unpack .../3-libpam-systemd_245.4-4ubuntu3.4_amd64.deb ...
Unpacking libpam-systemd:amd64 (245.4-4ubuntu3.4) over (245.4-4ubuntu3.3) ...
Preparing to unpack .../4-systemd_245.4-4ubuntu3.4_amd64.deb ...
Unpacking systemd (245.4-4ubuntu3.4) over (245.4-4ubuntu3.3) ...
Preparing to unpack .../5-libsystemd0_245.4-4ubuntu3.4_amd64.deb ...
Unpacking libsystemd0:amd64 (245.4-4ubuntu3.4) over (245.4-4ubuntu3.3) ...
Setting up libsystemd0:amd64 (245.4-4ubuntu3.4) ...
Selecting previously unselected package edgedb-server-1-alpha8-dev5340.
(Reading database ... 280220 files and directories currently installed.)
Preparing to unpack .../edgedb-server-1-alpha8-dev5340_1.0a8.dev5340+g76e0688b-2021012101~focal.nightly_amd64.deb ...
Unpacking edgedb-server-1-alpha8-dev5340 (1.0a8.dev5340+g76e0688b-2021012101~focal.nightly) ...
Setting up edgedb-server-1-alpha8-dev5340 (1.0a8.dev5340+g76e0688b-2021012101~focal.nightly) ...
Setting up systemd (245.4-4ubuntu3.4) ...
Installing new version of config file /etc/dhcp/dhclient-enter-hooks.d/resolved ...
Setting up systemd-timesyncd (245.4-4ubuntu3.4) ...
Setting up systemd-sysv (245.4-4ubuntu3.4) ...
Setting up libnss-systemd:amd64 (245.4-4ubuntu3.4) ...
Setting up libpam-systemd:amd64 (245.4-4ubuntu3.4) ...
Processing triggers for libc-bin (2.31-0ubuntu9.1) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for dbus (1.12.16-2ubuntu2.1) ...
WARNING<PHONE_NUMBER>-01-21 21:26:48,635 py.warnings: /usr/lib/x86_64-linux-gnu/edgedb-server-1-alpha8-dev5340/lib/python3.8/site-packages/edb/server/main.py:606: DeprecationWarning: Option `--default-database-user` is deprecated. Role `edgedb` is always created and no role named after unix user is created any more.
  warnings.warn(

WARNING<PHONE_NUMBER>-01-21 21:26:48,636 py.warnings: /usr/lib/x86_64-linux-gnu/edgedb-server-1-alpha8-dev5340/lib/python3.8/site-packages/edb/server/main.py:621: DeprecationWarning: Option `--default-database` is deprecated. Database `edgedb` is always created and no database named after unix user is created any more.
  warnings.warn(

INFO<PHONE_NUMBER>-01-21 21:26:48,636 edb.server: EdgeDB server (1.0-alpha.8+dev.5340.g76e0688b) starting.
INFO<PHONE_NUMBER>-01-21 21:26:49,451 edb.server.pgcluster: Initializing database cluster in /home/isidentical/.local/share/edgedb/data/default
INFO<PHONE_NUMBER>-01-21 21:26:51,787 edb.server: Creating template database...
INFO<PHONE_NUMBER>-01-21 21:26:53,860 edb.server: Creating the necessary PostgreSQL extensions...
INFO<PHONE_NUMBER>-01-21 21:26:53,871 edb.server: Initializing the standard library...
INFO<PHONE_NUMBER>-01-21 21:26:58,203 edb.server: Creating database: __edgedbsys__
INFO<PHONE_NUMBER>-01-21 21:26:59,314 edb.server: Creating database: edgedb
INFO<PHONE_NUMBER>-01-21 21:26:59,884 edb.server: Restarting server to reload configuration...
INFO<PHONE_NUMBER>-01-21 21:27:01,490 edb.server: Serving on <IP_ADDRESS>:10700
INFO<PHONE_NUMBER>-01-21 21:27:01,490 edb.server: Serving on /run/user/1000/edgedb-default/.s.EDGEDB.10700
INFO<PHONE_NUMBER>-01-21 21:27:01,490 edb.server: Serving admin on /run/user/1000/edgedb-default/.s.EDGEDB.admin.10700
WARNING: unsolicited message LogMessage(LogMessage { severity: Notice, code:<PHONE_NUMBER>, text: "server restart is required for the configuration change to take effect", attributes: {} })
INFO<PHONE_NUMBER>-01-21 21:27:02,781 edb.server: Shutting down.
edgedb error: failed to restore "default": error applying init file "/home/isidentical/.local/share/edgedb/data/default.dump/init.edgeql": failed statement "CONFIGURE SYSTEM SET query_work_mem := \'\"6144kB\"\';": ERROR: InvalidValueError: invalid value for parameter "work_mem": ""6144kB""
(.venv) (Python 3.10.0a4+) [  9:27ÖS ]  [ isidentical@desktop:~ ]
 $ edgedb -Idefault
edgedb error: Connection refused (os error 111)
(.venv) (Python 3.10.0a4+) [  9:28ÖS ]  [ isidentical@desktop:~ ]
 $ edgedb server restart default
(.venv) (Python 3.10.0a4+) [  9:29ÖS ]  [ isidentical@desktop:~ ]
 $ edgedb -Idefault
edgedb error: ERROR: InternalServerError: relation "edgedbss.0f06fc00-3ce1-11eb-94c7-09385bb1572d_t" does not exist
  Hint: This is most likely a bug in EdgeDB. Please consider opening an issue ticket at https://github.com/edgedb/edgedb/issues/new?template=bug_report.md
  Server traceback:
      edb.errors.InternalServerError: relation "edgedbss.0f06fc00-3ce1-11eb-94c7-09385bb1572d_t" does not exist

The previous version was either an old alpha 8 or one of the latest alpha 7s, the OS is ubuntu 20.04.1. I can't also use that same command to try again:
 $ edgedb server upgrade --nightly
edgedb error: failed to read metadata /home/isidentical/.local/share/edgedb/data/default/metadata.json: No such file or directory (os error 2)

The previous version was either an old alpha 8 or one of the latest alpha 7s, the OS is ubuntu 20.04.1. I can't also use that same command to try again:
 $ edgedb server upgrade --nightly
edgedb error: failed to read metadata /home/isidentical/.local/share/edgedb/data/default/metadata.json: No such file or directory (os error 2)

This looks like #1533.  It's been fixed in master, although older versions are still affected.  I'll look into backporting the fix to a7

This looks like #1533.  It's been fixed in master, although older versions are still affected.  I'll look into backporting the fix to a7

This looks like #1533. It's been fixed in master, although older versions are still affected. I'll look into backporting the fix to a7

Is there a way to restore my DB to the previous state, or do I need to have a fresh start?

This looks like #1533. It's been fixed in master, although older versions are still affected. I'll look into backporting the fix to a7

Is there a way to restore my DB to the previous state, or do I need to have a fresh start?

@tailhook, any ideas no how to best recover a failed upgrade?

@tailhook, any ideas no how to best recover a failed upgrade?

This looks like #1533. It's been fixed in master, although older versions are still affected. I'll look into backporting the fix to a7

Is there a way to restore my DB to the previous state, or do I need to have a fresh start?

Sure, something like this:
edgedb server stop default
mv ~/.local/share/edgedb/default ~/.local/share/edgedb/default.new
mv ~/.local/share/edgedb/default.backup ~/.local/share/edgedb/default
edgedb server stop default

This looks like #1533. It's been fixed in master, although older versions are still affected. I'll look into backporting the fix to a7

Is there a way to restore my DB to the previous state, or do I need to have a fresh start?

Sure, something like this:
edgedb server stop default
mv ~/.local/share/edgedb/default ~/.local/share/edgedb/default.new
mv ~/.local/share/edgedb/default.backup ~/.local/share/edgedb/default
edgedb server stop default

To actually upgrade the instance you probably have to edit the dump at /home/isidentical/.local/share/edgedb/data/default.dump/init.edgeql and remove the query_work_mem line and load that dump to a newly created instance:
edgedb server init new
edgedb -Inew restore --all /home/isidentical/.local/share/edgedb/data/default.dump

To actually upgrade the instance you probably have to edit the dump at /home/isidentical/.local/share/edgedb/data/default.dump/init.edgeql and remove the query_work_mem line and load that dump to a newly created instance:
edgedb server init new
edgedb -Inew restore --all /home/isidentical/.local/share/edgedb/data/default.dump

Sure, something like this:

Can we make this happen automatically if upgrade fails?

Sure, something like this:

Can we make this happen automatically if upgrade fails?

Sure, something like this:

Thanks, restored successfully! Though upgrading failed (I also tried this after restarting, still same)
 $ edgedb -Idefault restore --all /home/isidentical/.local/share/edgedb/data/default.dump/ --allow-non-empty
WARNING: unsolicited message LogMessage(LogMessage { severity: Notice, code:<PHONE_NUMBER>, text: "server restart is required for the configuration change to take effect", attributes: {} })
WARNING: unsolicited message LogMessage(LogMessage { severity: Debug, code:<PHONE_NUMBER>, text: "received configuration reload request", attributes: {} })
WARNING: unsolicited message LogMessage(LogMessage { severity: Debug, code:<PHONE_NUMBER>, text: "received configuration reload request", attributes: {} })
edgedb error: restoring database "reiz_testing": Error initiating restore protocol: ERROR: SchemaError: ObjectType <QualName ast::AST> is already present in the schema <FlatSchema gen:1 at 0x7f3b96ee3490>

Sure, something like this:

Thanks, restored successfully! Though upgrading failed (I also tried this after restarting, still same)
 $ edgedb -Idefault restore --all /home/isidentical/.local/share/edgedb/data/default.dump/ --allow-non-empty
WARNING: unsolicited message LogMessage(LogMessage { severity: Notice, code:<PHONE_NUMBER>, text: "server restart is required for the configuration change to take effect", attributes: {} })
WARNING: unsolicited message LogMessage(LogMessage { severity: Debug, code:<PHONE_NUMBER>, text: "received configuration reload request", attributes: {} })
WARNING: unsolicited message LogMessage(LogMessage { severity: Debug, code:<PHONE_NUMBER>, text: "received configuration reload request", attributes: {} })
edgedb error: restoring database "reiz_testing": Error initiating restore protocol: ERROR: SchemaError: ObjectType <QualName ast::AST> is already present in the schema <FlatSchema gen:1 at 0x7f3b96ee3490>

Sure, something like this:

Thanks, restored successfully! Though upgrading failed (I also tried this after restarting, still same)
 $ edgedb -Idefault restore --all /home/isidentical/.local/share/edgedb/data/default.dump/ --allow-non-empty
WARNING: unsolicited message LogMessage(LogMessage { severity: Notice, code:<PHONE_NUMBER>, text: "server restart is required for the configuration change to take effect", attributes: {} })
WARNING: unsolicited message LogMessage(LogMessage { severity: Debug, code:<PHONE_NUMBER>, text: "received configuration reload request", attributes: {} })
WARNING: unsolicited message LogMessage(LogMessage { severity: Debug, code:<PHONE_NUMBER>, text: "received configuration reload request", attributes: {} })
edgedb error: restoring database "reiz_testing": Error initiating restore protocol: ERROR: SchemaError: ObjectType <QualName ast::AST> is already present in the schema <FlatSchema gen:1 at 0x7f3b96ee3490>

This error means you're restoring into a database that already contanins schema/data. Try restoring into a new one. Or you can drop and recreate default, but backup the dump before issuing edgedb destroy default.

Sure, something like this:

Thanks, restored successfully! Though upgrading failed (I also tried this after restarting, still same)
 $ edgedb -Idefault restore --all /home/isidentical/.local/share/edgedb/data/default.dump/ --allow-non-empty
WARNING: unsolicited message LogMessage(LogMessage { severity: Notice, code:<PHONE_NUMBER>, text: "server restart is required for the configuration change to take effect", attributes: {} })
WARNING: unsolicited message LogMessage(LogMessage { severity: Debug, code:<PHONE_NUMBER>, text: "received configuration reload request", attributes: {} })
WARNING: unsolicited message LogMessage(LogMessage { severity: Debug, code:<PHONE_NUMBER>, text: "received configuration reload request", attributes: {} })
edgedb error: restoring database "reiz_testing": Error initiating restore protocol: ERROR: SchemaError: ObjectType <QualName ast::AST> is already present in the schema <FlatSchema gen:1 at 0x7f3b96ee3490>

This error means you're restoring into a database that already contanins schema/data. Try restoring into a new one. Or you can drop and recreate default, but backup the dump before issuing edgedb destroy default.

Sure, something like this:

Can we make this happen automatically if upgrade fails?

We can, but the reasons of my hesitation:

We have to be careful when this happens, on certain error condition we shouldn't revert (e.g. probably if start fails rather then restore)
What if reverting of restore failed? The biggest issue here is that user can see failure of restoring instead of upgrade failure and this might make us harder to help. And also now directories are in unknown inconsistent state.

I'm thinking of something like edgedb server repair, which could solve these failures. We should have enough metadata to find out what's going on, but at least repair would not touch anything if state is unclear, and original failure is still there after upgrade.
Or just edgedb server revert which is able both: to repair the failed upgrade and to revert successful upgrade.

Sure, something like this:

Can we make this happen automatically if upgrade fails?

We can, but the reasons of my hesitation:

We have to be careful when this happens, on certain error condition we shouldn't revert (e.g. probably if start fails rather then restore)
What if reverting of restore failed? The biggest issue here is that user can see failure of restoring instead of upgrade failure and this might make us harder to help. And also now directories are in unknown inconsistent state.

I'm thinking of something like edgedb server repair, which could solve these failures. We should have enough metadata to find out what's going on, but at least repair would not touch anything if state is unclear, and original failure is still there after upgrade.
Or just edgedb server revert which is able both: to repair the failed upgrade and to revert successful upgrade.


Add zsh completion for 'docker node' commands

Ref. #23363
@vincentbernat
Signed-off-by: Steve Durrheimer<EMAIL_ADDRESS>

LGTM

LGTM 🐯

LGTM, thanks!


Going from tab through non-tabs back to different tab

Version

react-native-router-flux Latest
react-native v0.48.2

Expected behaviour
Go from a tab scene to a non-tab scene, another non-tab, back to a different tab with a smooth, single transition on the last step.
Actual behaviour
I can only navigate back safely by popping back to the tab, then to the second tab -- if I try to directly push to the second tab it goes but then does a reset to scene right afterwards(2 transitions and I'd rather not reset).
Steps to reproduce
<Scene>
     <Tabs key="company">
              <Scene key="tab1"/>
              <Scene key="tab2"/>
              <Scene key="tab3"/>
     </Tabs>
     <Scene key="A"/>
     <Scene key="B"/>
</Scene>

I want to go from tab1 -> A -> B -> tab2.
I have a feeling like it doesn't work to do this, which is fine, but then I need a way to either

Pop immediately back to tab1 without animations and then go to to tab2. Can't do this, can I?
or
Display a modal over the popping animation. Modal can't do this as far as I can tell.

I have a work-around so I'm going to close with it. Don't have time to solve this properly. Maybe I'll come back to it if people want.
Here's what I did. I'm still popping back to my tab scene, but you can trick lightbox into staying visible as you pop by doing this:
// display the modal
Actions.loadingModal()
// pop as much as needed to get back to tab scene (popTo doesn't work in this case for me)
Actions.pop()
Actions.pop()
// load the modal back immediately
Actions.loadingModal()
// close the popup by navigating to new tab
setTimeout(() =>{
     Actions.tab2()
}, 3000)

This works for me:
  popToRoot = state => {
    Actions.pop();
    if (state.routes) {
      return state.routes.every(popToRoot);
    }

    return true;
  }

popToRoot(Actions.state);
Actions.jump('tab2');


fix: update time-rs to pass build on rust 1.80 (fix #10406)

Ran cargo update time to bump time-rs to 0.3.36 in order to pass build with rust 1.80. See #10406

Clippy fix seems to be included here

The linked PR also updated the lockfile so this PR is no-op now, sorry x) Thanks for contributing though!


update my bio and links

update my bio and links

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

review/ @Pradumnasaraf

review/ @Pradumnasaraf

Hey, you need to ping any specific maintainers. Anyone can review and merge


Memory Leak

Hello!
I have question about realization: did you use some cashing or else?
I have notice that using your library request to translate will be faster if it was made by same translator object sometime and RAM on my PC decrease.
If you using some cashing can I to disable it?

There is no such caching feature built in, so posting your code will help figure out if this is actually a library issue.


Set HOST to HEROKU_APP_DEFAULT_DOMAIN_NAME

So that HOST includes the subdomain guid. Otherwise the talos manager web doens't work.

Thanks 👍


Foundation CSS interferes with Google Maps markers

I am using Foundation with Rails and displaying Google Maps using gmaps4rails. Normal map markers are unaffected, but when I create a dynamic marker and set it to draggable, Foundation scales the marker to approx. 50% of its width. The marker is created with
var marker = new google.maps.Marker({draggable: true});

Omitting the Foundation CSS from the asset manifest restores the marker look, as does setting draggable to false.
I tried to hunt down the CSS that would cause this, but failed. The marker element in the DOM is:
<img style="position: absolute; left: 0px; top: 0px; width: 20px;
 height: 34px; -moz-user-select: none; border: medium none;
 padding: 0px; margin: 0px;" src="http://maps.gstatic.com/mapfiles/markers/marker_sprite.png"
 usemap="#gmimap1">

Any help would be much appreciated!

Could you drop in more of the context around the marker (the markup I mean) - that or drop in the computed styles that Firebug / Chrome Inspector prints out? Not sure why Foundation would be shrinking the markers like that when the size styles are inline.

Found it. It's the following rule in the CSS reset section:
img, object, embed { max-width: 100%; }

Google Maps seems to use images in a rather creative way, and does not play well with this reset rule.

Looks like rule has caused problems for other projects as well:
https://github.com/murtaugh/HTML5-Reset/issues/7
However it's core to Foundation being responsive, and needs to stay in.
You should be able to override this property by setting max-width: none; for elements this cause problems for. Just note that those images will not scale for devices with smaller screens, but that is probably the effect that you want.

Yeah, got it fixed by overriding max-width. Marking this as closed if that's OK.

Yup, glad you we able to get it working.

thanks @ghost that was a good paste


Make tabs undraggable

Before submitting, please confirm you've

[x] read and understood our Contributing Guidelines
[x] completed Mattermost Contributor Agreement
[x] executed npm run lint:js for proper code formatting

Please provide the following information:
Summary
Make tabs undraggable.
This would block #478 in the future. But this is an easy workaround for now.
Issue link
#667
Test Cases

Add two servers at least.
Try to drag&drop a tab.
Anything should not happen.

Additional Notes
https://circleci.com/gh/yuya-oc/desktop/754#artifacts

@yuya-oc This one too! :)


Update meta.yaml for v0.1.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

The CI failures are being tracked in this issue https://github.com/conda-forge/status/issues/125


Semantics of Greater Than Challenge

Challenge Name
Comparison with the Greater Than Operator
Issue Description
Semantics of this challenge need to be amended. Would be better to say '100 or over'. This test only passes when you put val > 100 but I think it should only pass (assuming use of integers only) with 101.
Your Code

function testGreaterThan(val) {
  if (val > 100) {  // Change this line
    return "Over 100";
  }

  if (val > 10) {  // Change this line
    return "Over 10";
  }

  return "10 or Under";
}

// Change this value to test
testGreaterThan(10);

Ah, I suspect this is a bit of a challenge given the >= exercise which follows.

@cmhall42 thanks for the issue. Can you elaborate on why you want this change? I'm not understanding the issue. Which "test" are you referring to in "This test only passes..."?
I think the challenge is clear enough and uses the correct comparison operators. If 101 is passed into the function for this challenge, it should return Over 100. And as you mentioned, the next challenge uses ## or over to indicate the value passed in is equal to that number or greater.

Please provide clarification as requested


Upgrade cardano-node dependency

Update to cardano-node 8.2 and ghc 9.2.8.

@MaximilianAlgehed No idea what's going on with the aarch64-darwin build!

@zeme-wana any clue what's up here? Is this just a silly thing related to the latest github meltdown?

@sjoerdvisscher if you force push this branch that might re-trigger the build.

It's good now

It's good now @sjoerdvisscher

That's a relief! But I'm getting some errors while running tests in plutus-apps, so let's not merge this until I know if that's a bug here or in plutus-apps.

Gonna merge this


Adding path level tagging

Hi team,
Currently OAS supports tagging in API and operation level. This PR is to add tagging in path level also.
Related feature request related to this:
OAI#1367
Please review the PR and merge the same.
Thanks,
Mohammed

Hey @ymohdriz Thanks for the PR.  This is definitely an interesting addition that has a low impact on the spec.  However, we do have to consider the impact on tooling.  We would need to get feedback from folks who are producing documentation based on OpenAPI as to whether they have user requests for these features and whether they are prepared to do the work to incorporate this capability.
Also, this kind of change cannot go into a patch release, it would need to go into a 3.1 branch which I don't believe we have yet created because we are still working on what features will go into 3.1.
We will definitely consider this for inclusion and the more feedback we can get from tooling people on this, the easier it will be to make the call.

Hi @darrelmiller,
Thanks for the detailed response.
I would like to contribute to this project. But new PRs may turn into new features.
Can you please suggest some areas to work on?
Thanks,
Mohammed

Hey @darrelmiller,
What's the state? Are subtags considered to be a feature, because it would be great!
If it's possible, a push would be very helpful!

This PR cannot be accepted as-is, because a) it is targeted at v2.0 of the specification, which is published and will not change, b) it only updates the schema file, which is not the source-of-truth of the specification (the markdown documents are), c) as @darrelmiller says, this change (if accepted) would need to go into a minor release, such as v3.1.0
@emreakca if you need sub-tag grouping / a hierarchy of tags, it would probably be worth commenting on #1367 or #1507 as appropriate.

Closing, for the reasons given in https://github.com/OAI/OpenAPI-Specification/pull/1509#issuecomment-402967954