Scenario graphic needs updating to match new scenario

Contact Details
<EMAIL_ADDRESS>What happened?
Exercise : 03 Lab Scenario
Description of issue:
This lab was significantly changed, but the graphic in the scenario was not updated. The Task 1 graphic looks OK, but the Task 2 graphic shows adding a role to a user instead of creating the Cloud Shell storage account.
Lab
Lab 07 Exercise 03 Create a Scheduled Query
Relevant screenshots
paste here 😉
Do you want to help us? 👏

[ ] Create a Pull Requestt by following this project's Contribution Guide

Follow-up note: There is a new Exercise 4 for Path 7 -- but the graphics have the lab and exercise number listed at the top, so all exercises after 4 have the wrong exercise number in the title on the graphic.

These will take a little while.

I updated all the lab scenario diagrams.

Fixed for next week.


Handle truncated ACKs properly

Should already work.
Truncated ACKs will be removed from the protocol with QUIC version 34.


[network] fix small issue with network rpc fuzzer

Sampling a new self-peer-id every fuzzer iteration causes metrics to
blow up after ~ 200,000 iters.

After this fix, the fuzzer runs pretty much indefinitely. I got up to
at least 16,000,000 iters locally with constant memory.

INFO: Seed:<PHONE_NUMBER>
190    INITED cov: 611 ft: 611 corp: 1/1b exec/s: 0 rss: 143Mb
8388608        pulse  cov: 612 ft: 613 corp: 3/555b lim: 4096 exec/s: 4459 rss: 1077Mb
16777216       pulse  cov: 612 ft: 613 corp: 3/555b lim: 4096 exec/s: 4464 rss: 1078Mb

/land

@sausagee do we need to cherry-pick this so we can fuzz it?


Fix vspk-go defaults for TCA

Breaks VSPK-GO because scope is not present in TCA (anymore)

Asking for a review to @little-dude just to be sure, but don't think that should be a problem :)


Cannot parse "11030938062" as an int value during NIC attach parse_response

Describe the bug
When running a reconfigure to add another NIC to a virtual machine, the following error occurs.  This happens in the OpenNebula vCenter driver paired with vCenter 8.0 U2.
Cannot attach NIC to VM: InvalidRequest:
Cannot parse "11030938062" as an int value
while parsing serialized value of type int
at line 1, column 405
while parsing property "key" of static type int
while parsing serialized DataObject of type vim.vm.device.VirtualVmxnet3
at line 1, column 371
while parsing property "device" of static type VirtualDevice
while parsing serialized DataObject of type vim.vm.device.VirtualDeviceSpec
at line 1, column 296
while parsing property "deviceChange" of static type ArrayOfVirtualDeviceConfigSpec
while parsing serialized DataObject of type vim.vm.ConfigSpec
at line 1, column 254
while parsing call information for method ReconfigVM_Task
at line 1, column 177
while parsing SOAP body
at line 1, column 167
while parsing SOAP envelope
at line 1, column 0
while parsing HTTP request for method reconfigure
on object of type vim.VirtualMachine
at line 1, column 0.

/usr/share/one/gems-dist/gems/rbvmomi2-3.7.0/lib/rbvmomi/connection.rb:64:in `parse_response'
/usr/share/one/gems-dist/gems/rbvmomi2-3.7.0/lib/rbvmomi/connection.rb:93:in `call'
/usr/share/one/gems-dist/gems/rbvmomi2-3.7.0/lib/rbvmomi/basic_types.rb:256:in `_call'
/usr/share/one/gems-dist/gems/rbvmomi2-3.7.0/lib/rbvmomi/basic_types.rb:77:in `block (2 levels) in init'
/usr/lib/one/ruby/vcenter_driver/virtual_machine.rb:2232:in `attach_nic'
/var/lib/one/remotes/vmm/vcenter/attach_nic:73:in `'"

To Reproduce
Steps to reproduce the behavior:

Import vCenter 8.0 U2 resources to OpenNebula
Create/Import a Virtual Machine
Try to attach a NIC to a virtual machine through OpenNebula

Expected behavior
A NIC should be attached without error
Platform:

OS: Any ( mainly testing with Ubuntu/Alma )
RbVmomi Version: rbvmomi2-3.7.0
Ruby Version: 3.0.2 ( also happens in 2.5.9 )

Additional context
For extra context, the function which builds and attaches the NIC can be found here in the OpenNebula project's vcenter library files: https://github.com/OpenNebula/one/blob/master/src/vmm_mad/remotes/lib/vcenter_driver/virtual_machine.rb#L1902
I also work on the OpenNebula project so I can provide other information if necessary. This is a very similar error that we're seeing when trying to run the old rbvmomi

Thanks @onenhansen I'll try to reproduce this on my side.  Could you re-run your reproducer but with SOAP debug enabled?  You can either run with the RBVMOMI_DEBUG=1 environment variable or pass the debug: true option to RbVmomi::VIM.connect().  This will print the raw XML to stderr.

Hi @agrare thanks for looking into this.
I've rerun this with the debug enabled in the connect method.  All of the previous requests go through properly, it gets the VM information right before this and appears to look good.  It definitely looks like it's related to the key value being interpreted as a string. Perhaps it is only a 32-bit integer and this is too large for it.
Thu Nov  9 17:31:00 2023 [Z0][VMM][I]: Request:
Thu Nov  9 17:31:00 2023 [Z0][VMM][I]:
<env:Envelope
	xmlns:xsd="http://www.w3.org/2001/XMLSchema"
	xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<env:Body>
		<ReconfigVM_Task
			xmlns="urn:vim25">
			<_this type="VirtualMachine">vm-109</_this>
			<spec xsi:type="VirtualMachineConfigSpec">
				<deviceChange xsi:type="VirtualDeviceConfigSpec">
					<operation>add</operation>
					<device xsi:type="VirtualVmxnet3">
						<key>11093059964</key>
						<deviceInfo xsi:type="Description">
							net2
							VM Network
						</deviceInfo>
						<backing xsi:type="VirtualEthernetCardNetworkBackingInfo">
							<deviceName>VM Network</deviceName>
							<network type="Network">network-16</network>
						</backing>
						<unitNumber>8</unitNumber>
						<addressType>manual</addressType>
						<macAddress>02:00:29:9e:bb:fa</macAddress>
					</device>
				</deviceChange>
			</spec>
		</ReconfigVM_Task>
	</env:Body>
</env:Envelope>
Thu Nov  9 17:31:00 2023 [Z0][VMM][I]:
Thu Nov  9 17:31:00 2023 [Z0][VMM][I]: Response (in 0.003 s)
Thu Nov  9 17:31:00 2023 [Z0][VMM][I]: <?xml version="1.0" encoding="UTF-8"?>
Thu Nov  9 17:31:00 2023 [Z0][VMM][I]: <soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Thu Nov  9 17:31:00 2023 [Z0][VMM][I]: <soapenv:Body>
Thu Nov  9 17:31:00 2023 [Z0][VMM][I]: <soapenv:Fault><faultcode>ServerFaultCode</faultcode><faultstring>
Thu Nov  9 17:31:00 2023 [Z0][VMM][I]: Cannot parse "11093059964" as an int value
Thu Nov  9 17:31:00 2023 [Z0][VMM][I]:
Thu Nov  9 17:31:00 2023 [Z0][VMM][I]: while parsing serialized value of type int
Thu Nov  9 17:31:00 2023 [Z0][VMM][I]: at line 1, column 406
...
same as above past here

Since I wasn't involved in writing this driver I've been reading through our code to see if the key is being generated as a number higher than a 32-bit integer.
Let me know about any further information, I'll try to trace this a bit better in the next couple days.

Interesting so I see you're using a timestamp for the temp key https://github.com/OpenNebula/one/blame/master/src/vmm_mad/remotes/lib/vcenter_driver/virtual_machine.rb#L2031
The usual "best practice" from my experience with VM reconfigure is to use e.g. -100 for the first new device, -101 for the second etc...
If you replace that timestamp with -100 does the reconfigure work?

🤦 Yep, you are right. I missed where it was generating the timestamp for the key. Gotta love problems from code written 2 years ago. I'm unsure why we haven't encountered this issue before now though.
We will change this code to generate a proper key going forward.
Thank you for your assistance @agrare , I'll close this issue since it doesn't exist in the rbvmomi2 repo.

Awesome!  Glad you were able to get it working


[SPARK-42388][SQL] Avoid parquet footer reads twice in vectorized reader

What changes were proposed in this pull request?
Parquet footer metadata is now always read twice in vectorized parquet reader.
When the NameNode is under high pressure, it will cost time to read twice. Actually we can avoid reading the footer twice by reading all row groups in advance and filter row groups according to filters that require push down (no need to read the footer metadata again the second time).
Why are the changes needed?
Reduce the reading of footer in vectorized parquet reader
Does this PR introduce any user-facing change?
no
How was this patch tested?
existing tests

Please ignore my PR. There is something wrong..

@MaxGekk could you help review my PR, thanks!

@MaxGekk @gengliangwang If you have time, please take a look, thanks

cc @sunchao , too.

@sunchao Thank you for your reply! Yes, I also noticed this, just before is for minimal changes.
In the original implementation:
The first footerFileMetaData use SKIP_ROW_GROUPS option (SkipMetadataFilter, return meta without rowGroup);
The second footerFileMetaData use RangeMetadataFilter(return meta with rowGroup info).
Actually the second footerFileMetaData contains all information used in the first footerFileMetaData(the detail implementation difference can see ParquetMetadataConverter#readParquetMetadata)
So when in case that we need filter pushdown and also enableVectorizedReader, we can only create one ParquetFileReader and read parquet footer only once. Other situations can also be optimized to read footer.
This needs to modify some more codes, do you think it is suitable?

@yabola yes, we'll need to use RangeMetadataFilter (i.e.: HadoopReadOptions.builder().withRange()) when we initially read the footer. This is possible since in places like ParquetFileFormat we already have a PartitionedFile which is just a segment in a Parquet file with a start and length.
The only problem is we need new non-deprecated API from parquet-mr to support this use case. Personally I think we can just use the deprecated API for now, and replace it after a new Parquet version is released.

@sunchao Sorry, it might be a mistake. We should read schema in footer meta first to get which filters need to be pushed down. After that we set pushdown info codes  and read filtered RowGroups.
So I think it might have to read footer twice if having filters. But we can read footer once when no filter is needed pushdown.
I think It will be useful when scanning joined tables (filter condition is only on the other side of the join table and filter is none in the joined table).  It can avoid reading much footer when there are many  joined tables.

@sunchao Hi~ Could you take a look at this PR?  I think it will be useful when there are joined tables and filter conditions are on few tables.

Sorry, it might be necessary to read footer twice if having filters. We should read schema in footer meta first to get which filters need to be pushed down. After that we set pushdown info ((https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetFileFormat.scala#L261) and read filtered RowGroups with the filter configuration.

Hmm why? when we read the footer for the first time, the result already contain all the row groups. We just need to pass these to ParquetFileReader, which will apply the filters we pushed down on these row groups and return a list of filtered ones. See here.

Merged to master, thanks!

@sunchao Thank you for your detailed review!

@yabola @sunchao  Could you share any benchmark numbers for the second optimisation of reading all row groups for each task? My concern is that it could be suboptimal in performance when you have, let's say, 100 row groups in a file, you create 100 tasks for each row group but then you read the full footer with all of the row groups for every task just to process one row group.

@sadikovi Thanks for your advice. I would do an experiment in the scenario you describe. But my understanding is that reading RowGroup meta (not data) should be indispensable, otherwise RowGroup cannot be filtered? I will follow up to confirm your concerns.

Yea @yabola is correct, if we have 100 row groups in a file and there are 100 tasks to read them, each task will only be assigned a range (e.g., a single row group) in the file to read, so it won't read metadata for all the row groups in the file.

@sadikovi I have tested the scenario as you said. The smaller the row group size (footer size will be larger), the higher the PR benefits.
Environment:  parquet.block.size=10240 (10kb),  file size is 253.6 MB( one file has  about 25000 row groups), and I wrote 24 files.
Before this PR:

After this PR:

Hi, @yabola and @sunchao .
SPARK-48950 seems to report a correctness issue about this. When you have some time, could you check it, please?

@dongjoon-hyun I will look into this issue later.


az ssh config --file crashes if given filename with no /

Extension name (the extension in question)
The az ssh extension
Description of issue (in as much detail as possible)
Attempting to run,
» az ssh config -f foo -g test -n test-new-aad-ext

Results in the following crash:
CLIInternalError: The command failed with an unexpected error. Here is the traceback:
[Errno 2] No such file or directory: ''
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.16.0/libexec/lib/python3.8/site-packages/knack/cli.py", line 215, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.16.0/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 654, in execute
    raise ex
  File "/usr/local/Cellar/azure-cli/2.16.0/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 717, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/local/Cellar/azure-cli/2.16.0/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 710, in _run_job
    six.reraise(*sys.exc_info())
  File "/usr/local/Cellar/azure-cli/2.16.0/libexec/lib/python3.8/site-packages/six.py", line 703, in reraise
    raise value
  File "/usr/local/Cellar/azure-cli/2.16.0/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 688, in _run_job
    result = cmd_copy(params)
  File "/usr/local/Cellar/azure-cli/2.16.0/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 325, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/Cellar/azure-cli/2.16.0/libexec/lib/python3.8/site-packages/azure/cli/core/__init__.py", line 784, in default_command_handler
    return op(**command_args)
  File "/Users/roy/.azure/cliextensions/ssh/azext_ssh/custom.py", line 28, in ssh_config
    _do_ssh_op(cmd, resource_group_name, vm_name, ssh_ip, public_key_file, private_key_file, use_private_ip, op_call)
  File "/Users/roy/.azure/cliextensions/ssh/azext_ssh/custom.py", line 49, in _do_ssh_op
    op_call(ssh_ip, username, cert_file, private_key_file)
  File "/Users/roy/.azure/cliextensions/ssh/azext_ssh/ssh_utils.py", line 54, in write_ssh_config
    file_utils.make_dirs_for_file(config_path)
  File "/Users/roy/.azure/cliextensions/ssh/azext_ssh/file_utils.py", line 12, in make_dirs_for_file
    mkdir_p(os.path.dirname(file_path))
  File "/Users/roy/.azure/cliextensions/ssh/azext_ssh/file_utils.py", line 17, in mkdir_p
    os.makedirs(path)
  File<EMAIL_ADDRESS>line 223, in makedirs
    mkdir(name, mode)
FileNotFoundError: [Errno 2] No such file or directory: ''
To open an issue, please run: 'az feedback'

This is because write_ssh_config attempts to make any non-existing directories: https://github.com/Azure/azure-cli-extensions/blob/568b8a889d99c3d1ff8ea67a9ce2925ccb8aeaf1/src/ssh/azext_ssh/ssh_utils.py#L52-L54
Which calls this:
https://github.com/Azure/azure-cli-extensions/blob/568b8a889d99c3d1ff8ea67a9ce2925ccb8aeaf1/src/ssh/azext_ssh/file_utils.py#L10-L12
The immediate problem is that, for foo, os.path.dirname returns '' ; it then tries to create this directory, which of course fails.
While that's the immediate cause, I would really not expect this utility to be creating directories like that. It's only being asked to emit the config to the path that I've specified. If a directory in that path doesn't exist, just error out & tell me. Worse, if I typo, it will created the typo'd directory. The examples in the docs for this flag also use ~/.ssh, which needs to have strict permissions on it, which this would ignore. It's better to just to what was asked (emit the config) & not try to correct for mistakes here.

VM SSH

Fixed in #3698

closing as it is called out as fixed.


Add Squirrel installertype

Description of the new feature/enhancement
This installertype is popular with many electron apps, including discord and authy. Using the "squirrel" installer type would automatically add the silent switches for installation like nullsoft and innosetup do.

Proposed technical implementation details (optional)

This topic brings me a lot of sadness as someone that worked with MANY of different installer engines.
From client-side installation, management Squirrel was by far, the best, most predictable and easiest to parse and work with.
@superusercode, as you mentioned a lot of electron app, used Squirrel for their installers, but that is something that getting less and less common and most are moving to NSIS, which, unfortunately, one of the worst installer engines as far as parsing/and predictability.
what is the point of all this, well, I just wanted to say how much I love squirrel. and more people should be using it. also, it makes total sense to get added to WinGet.

This could be grouped with #360

The big problem with Squirrel installers is that only user installs are supported. Machine wide installations are not.
Admins using winget would be very surprised if after installing an app it was only installed on their account.
I don't see how Squirrel installers can be supported in winget.

By the way, what should be the correct flags to add in a squirrel installer when adding to winget-pkgs?


Structs not supported?

I am trying to use ADO.NET to query a table whose schema contains:
column_name: code
column_type: STRUCT(coding STRUCT(code VARCHAR, display VARCHAR, "system" VARCHAR)[], sof_codes VARCHAR[], "text" VARCHAR)
I've tried every reasonable variation of select statement that should work to extract columns out of that struct, e.g.
SELECT code.coding.code FROM ...
SELECT code.* FROM ...

The data types in question for these columns are 24 and 25, which are not supported.
This exception gets raised:
https://github.com/Giorgi/DuckDB.NET/blob/58a3bc90e5446ddfca998da5817ed115170fa202/DuckDB.NET.Data/DuckDBDataReader.cs#L122
These schemas come from parquet files, if that matters.

No, structs and lists aren't supported currently.

Would you entertain a PR for it?

now that data chunks are implemented. any chance we get struct support?

Allow setting naming convention for member names (camel case, pascal case, snake case).
Allow custom naming convention for member names.
Use expression trees to set properties
Cache struct information for better performance

Structs are now working in the develop branch.

For now, I won't implement any naming customization.

Struct support is now live on NuGet

Thanks Giorgi.  This is really great.


how to find build_utils ?

how to find build_utils ?

Sorry for my late reply, you can find build_utils directory from this page: https://github.com/WZMIAOMIAO/deep-learning-for-image-processing/tree/master/pytorch_object_detection/yolov3_spp. Hope it can solve your question.


[Hub Generated] Review request for Microsoft.HybridCompute to add version preview/2021-12-10-preview

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[x] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

/azp run unifiedPipeline

Hi @qiaozha, for the cross version breaking change. Rule 1029: I had the same issue when I published the last preview API, we had an agreement with the last reviewer this is not a breaking change. For the Rule 1011, we made a mistake in the previous API and we wanted to fix it.

For the incomingconnections.ports property under the new agentConfiguration structure, right now, it is read-only.
However, in the future, we would like to support our agent being configured remotely via ARM, which would make it necessary to remove the read-only.
I believe it is a breaking change to change a property from read-only to not read-only
How would you advise us to approach this?

For the incomingconnections.ports property under the new agentConfiguration structure, right now, it is read-only. However, in the future, we would like to support our agent being configured remotely via ARM, which would make it necessary to remove the read-only. I believe it is a breaking change to change a property from read-only to not read-only What's the best approach for this?

@mentat9

For the incomingconnections.ports property under the new agentConfiguration structure, right now, it is read-only. However, in the future, we would like to support our agent being configured remotely via ARM, which would make it necessary to remove the read-only. I believe it is a breaking change to change a property from read-only to not read-only What's the best approach for this?

@mentat9

That isn't a REST breaking change, AFAICT. @qiaozha, @jsntcy would that break any SDKs?

@mentat9 Can you review the PR again? Thanks

@mentat9 Can you review the PR again? Thanks

Hi @dorothyhu: this week's oncall is @j5lim. He will review your update if his queue isn't too full. Otherwise, I will be oncall next week and will do it then.

@ArcturusZhang Could you take a look at this go SDK generation failure ?


Watch mode unresponsive to monorepo dependency changes

Describe the bug
I'm attempting to use Vitest in a monorepo, and noticed there are issues getting vitest to re-run tests in watch mode when in-repo dependencies change. I've identified a few specific limitations (if these should be split out into separate issues, let me know):

**/dist/** needs to be excluded from watchExclude. This is fine, however I'd expect the default behavior to be smart enough to handle a monorepo where packages are built separately and imported into the package being tested
deps.inline has to be set to true for changes to be picked up. Again, this is a reasonable workaround, but since vite "just works" for HMR and watch mode to work correctly, I wouldn't expect it to be necessary for vitest.
When rebuilding the dependency with Vite, tests are not rerun - even though if I manually change the file in dist, they are. Additionally, building with Vite then trying to change the file in dist (without restarting the test watcher) also does not cause a test rerun. I tried tweaking the chokidar options via vite's server.watch parameter (namely awaitWriteFinish and atomic) as that seemed like it could affect this, but there was no change in behavior.

Reproduction
Reproduce via https://stackblitz.com/edit/vitest-dev-vitest-fttlzd (ensure you have two terminals available). Stop any watch processes and reset file states between tests.

Run turbo run --cwd packages/packageb build:watch in one terminal
Change packages/packagea/src/lib.ts
Run turbo run --cwd packages/packagea build in the other terminal
Note packages/packageb/dist/index.js is updated accordingly

Run turbo run --cwd packages/packageb test in one terminal
Change packages/packagea/dist/src/lib.ts
Note the test watcher updates accordingly

Run turbo run --cwd packages/packageb test in one terminal
Change packages/packagea/src/lib.ts
Run turbo run --cwd packages/packagea build in the other terminal
Note the test watcher does not update

Comment out deps: { inline: true }, (and/or watchExclude: [],) in packages/packageb/vite.config.ts
Run turbo run --cwd packages/packageb test in one terminal
Change packages/packagea/dist/src/lib.ts
Note the test watcher does not update

Also note that if you run test 3 then 2 without stopping the test watcher, 2 will also fail to update.
System Info
System:
  OS: Linux 5.0 undefined
  CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Memory: 0 Bytes / 0 Bytes
  Shell: 1.0 - /bin/jsh
Binaries:
  Node: 16.14.2 - /usr/local/bin/node
  Yarn: 1.22.19 - /usr/local/bin/yarn
  npm: 7.17.0 - /usr/local/bin/npm
npmPackages:
  vite: 4.0.2 => 4.0.2
  vitest: 0.26.0 => 0.26.0

### Used Package Manager

npm

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitest-dev/vitest/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitest.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/vitest-dev/vitest/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitest-dev/vitest/discussions) or join our [Discord Chat Server](https://chat.vitest.dev).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

Just realized that vite's build watch uses rollup's watch mode, not the vite dev server which vitest uses. I changed packageb to be a web app that the vitest dev server can serve, and confirmed that rebuilding the dependency as in case 1 (using vitest instead of vitest build --watch) caused a proper reload: https://stackblitz.com/edit/vitest-dev-vitest-nhye4s

This should be fixed in 0.31.2.

Thanks for the update @sheremet-va - could you point me to the commit/PR in that release that resolves this (since my related PR is still open)?

#3446

The issue is not fully resolved yet. I was able to remove the deps inline, but watchExclude still needs to be cleared (as mentioned earlier, easy to work around) and tests to not rerun on a dependency vite build

Updated Stackblitz: https://stackblitz.com/edit/vitest-dev-vitest-g1bmwe

watchExclude still needs to be cleared (as mentioned earlier, easy to work around)

This is expected behavior.

tests to not rerun on a dependency vite build (which is what my PR addresses)

I left comments in PR.

Thanks - I'll revisit the PR once I have some available cycles

This is expected behavior.

On the other hand, it should also be removed from exclude at this point. We are moving away from treating named folders differently.

I'm not sure what the situation is right now, but vitest does not respond to rebuilds in the case of a workspace package being rebuilt. I think, ideally, there would be a way to just have vitest directly access the source of the workspace package instead of needing to look at the built package at all.

Just FYI I haven't dived into the full detail here (was snooping through existing issues to get help on something else!) but using an alias might be helpful here, that's how we got coverage working in our monorepo with vitest - https://github.com/vitest-dev/vitest/issues/5218#issuecomment-1952174964

@ahayes91 thanks for the suggestion!
It seems like it should work, but it is now just a bit more doubling up of code, and not having a single source of truth...


How can I use the methods in the "schemaHelper" object to correctly convert the data in "json.blobs"?

At present, I am converting the data into base64 characters, but this data should be an svg path, how can I convert it into a correct svg path?

"schemaHelper", the object provides some methods, but I don't know how to use them correctly.

@whxcode I'm not entirely sure to be honest. I haven't tried working with the image data directly yet.
I can give it a try when I have a moment later this week or next week (a bit packed with tasks)

@whxcode I'm not entirely sure to be honest. I haven't tried working with the image data directly yet.
I can give it a try when I have a moment later this week or next week (a bit packed with tasks)

Well, thank you.

@whxcode did you end up figure it out?


Unify 3rd party connection to the cart

Issue Name
Unify 3rd party connection to the cart
Summary
The idea here is to have a standard scenario for events which can be attached to the scicat cart.
There should be a configuration file which specifies what actions are available.
All actions will be added to the jobs table in the mongo database, which is where all information about the files/datasets involved is stored.
When the button is clicked, one of 3 things will happen,

A rabbitMQ message is sent out to a specified Queue with the jobID as a parameter
The button redirects to a specified URL with the jobID as a parameter
Nothing, this is for systems that like to poll, for example an archiver which only runs at midnight or something.

When the 3rd part tool updates things, it should update the status as it is doing things.

Cart actions should be defined in configuration.
The entry defining each actions should be an array with multiple instances of the following json entry:
 {
  id: '<action_unique_identifier>',
  machine_name: '<action_unique_name>',
  common_name: '<user_friendly_name>',
  icon: '<icon_file_path>',
  type: '<type_of_the_action>',
  <action_specific_keys> : '<action_specific_values>'
 }

If we would like to define the following actions:

Archive: submit a message to rabbitmq server rabbit.our.institution on topic archive
Retrieve: submit a message to rabbitmq server rabbit.our.institution on topic retrieve
Get Notebook: redirect user to external microservice with URL notebook.our.institution that prepopulate a jupyter notebook and push it to the user machine using http download
Analyze: just create a job with the analysis request. An external service will query at scheduled time for this jobs to start the analysis on an external infrastructure

In order to define such actions, the backend configuration file should contains the following section:
cart_actions : [
 {
  id: 'a5f43a5e-26e3-11ee-870c-3b096f8c3106',
  machine_name: 'archive_job_1',
  common_name: 'Archive',
  icon: 'icons/archive.png',
  type: 'rabbitmq',
  server: 'rabbit.our.institution',
  topic: 'archive',
 },
 {
  id: '02999218-26e4-11ee-8bef-7324e23d8360',
  machine_name: 'retrieve_job_1',
  common_name: 'Retrieve',
  icon: 'icons/retrieve.png',
  type: 'rabbitmq',
  server: 'rabbit.our.institution',
  topic: 'retrieve',
 },
 {
  id: '15ea1338-26e4-11ee-a932-d77973d535cb',
  machine_name: 'jupyter_job_1',
  common_name: 'Get Notebook',
  icon: 'icons/notebook.png',
  type: 'redirect',
  server: 'notebook.our.institution',
 },
 {
  id: '15ea1338-26e4-11ee-a932-d77973d535cb',
  machine_name: 'analysis_job_1',
  common_name: 'Run analysis',
  icon: 'icons/analysis.png',
  type: 'no_action',
  parameter_1: 'value_1',
  ...
 }
]

After meeting with @bolmsten, we should introduce the concept of action which can be performed on cart or datasets.
Action can trigger job creation or call an external URL.
More details coming

Also this requires more effort, so I am assigning it to its own release.

Super seeded by issues #635


Meeting Minutes from 7/7 and markdown checking automation

There are still files that need to be cleaned up in the markdown format; but, this is the start of that process to get them format corrected.


RWX Native support

hey,
Are there plans to support Read-Write-Many (RWX) natively in CSTOR or in JIVA ?
there's a blog post on how to enable RWX by leveraging NFS on top of OpenEBS
https://blog.openebs.io/setting-up-persistent-volumes-in-rwx-mode-using-openebs-142632244cb2
but this solution is very cumbersome

requires much more complicated configuration and setup
requires an additional provisioner
requires extra disk space
performance degradation is unclear

thanks

Reopening this issue with additional requirement:
Current RWX solution (here) is based on the Kubernetes nfs-provisioner
We need a solution that provides:

Standard Docker images with debugging tools
More than one provisioner instance - maybe through an Operator (Single provisioner is a point of failure)
Running NFS on LocalPV
Metrics exporter (adding Prometheus exporter for NFS-Ganesha as an option)

Reopening this issue

OpenEBS has started to support NFS natively via the Dynamic NFS provisioner. For trying it out and providing feedback please visit - https://github.com/openebs/dynamic-nfs-provisioner


How can we get com.mongodb.client.MongoClient?

com.mongodb.MongoClient = new Fongo(mongoURI).getMongo();
This was our old code.
Since now many methods are deprecated for com.mongodb.MongoClient, we are moving to com.mongodb.client.MongoClient.So, is there a way to get com.mongodb.client.MongoClient with Fongo now?

Any updates on this ?

Any updates on this?


Missing header

In following example:
package main

import (
	"github.com/gin-gonic/gin"
	"github.com/long2ice/swagin"
	"github.com/long2ice/swagin/router"
	"github.com/long2ice/swagin/swagger"
)

func main() {
	app := swagin.New(swagger.New("SwaGin", "Swagger + Gin = SwaGin", "0.1.0"))
	app.GET("/", test)
	if err := app.Run(); err != nil {
		panic(err)
	}
}

var test = router.New(
	&Test{},
	router.Summary("Test query"),
	router.Description("Test query model"),
)

type Test struct{
	Authorization string `header:"authorization" binding:"required" json:"authorization" default:"authorization"`
	Token string `header:"token" binding:"required" json:"token" default:"token"`
}

func (t *Test) Handler(ctx *gin.Context) {
	println(">>>>>>>>>> authorization:", t.Authorization)
	println(">>>>>>>>>> token:", t.Token)
}

I require two headers in request (Token and Authorization). They are both listed in documentation (at URL /docs) and I can set them to perform request. But validation fails for header Authorization which is missing, while Token is sent and received. Furthermore, in CURL example request Authorization header is missing while Token is set.
In my opinion, both headers should be sent. Why is Authorization missing?
This seems to be a collision with authorization bechanism in SwaGin, as it works fine with other headers.

Latest code is ok


Added support for user/command specific defaults

Also added tests

Is this cookbook no longer maintained?

Hello,
Thank you for taking the time to open this pull request, and for the comprehensive test coverage added too! I wanted to offer my thoughts on this PR.
This cookbook is maintained.
However I don't think we need to add every possible configuration scenario to the default sudoers file. This leads to attribute sprawl that makes it difficult to follow what is going on for future maintainers. As you're now aware there is additional testing required to ensure everything works - and we need to make sure those things don't get broken in the future. It can also lead to confusion for new users. They may ask questions like "what is this attribute? Do I need to set this? What does it do?" and then they find themselves reading man pages and blog posts about features. sudo itself has an includedir directive so users can drop off sudo configuration into /etc/sudoers.d (default included directory). The sudo resource in this cookbook can be used for that, or if it doesn't support desired options, a template resource will work just fine.

Thanks for the reply.
If you think that adding more default attributes is sprawl, I accept that and will use templates instead.
I just tested and Defaults is respected when used in included files.


TypeError

What I did just install this library.
And I am getting TypeError as:-

Version:-

Please Help!!!
Thanks in advance!!!

I'm wondering if it's an issue with the latest version of React Native.  It works for me in a project that is on 59.9, but my new project using 62.0 gets a similar TypeError: Cannot read property 'style' of undefined

React Native 0.62 removed propTypes. You need to remove the line:
itemTextStyle: Text.propTypes.style,

React Native 0.62 removed propTypes. You need to remove the line:
itemTextStyle: Text.propTypes.style,

can you help me finding path for this ?
I mean folder structure where I can find this line.
Thanks for your help.

React Native 0.62 removed propTypes. You need to remove the line:
itemTextStyle: Text.propTypes.style,

I did remove this line from
node_module/react-native-material-dropdown/src/component/index.js
line 136
but this not working too.
I even tried after removing itemTextStyle from line 582 and 633, but it does not work again.
What should I do now?

Try removing any occurrence of Text.propTypes.style. I was using this library in an old component that wasn't in production anymore, so I just removed the library.

React Native 0.62 removed propTypes. You need to remove the line:
itemTextStyle: Text.propTypes.style,

I did remove this line from
node_module/react-native-material-dropdown/src/component/index.js
line 136
but this not working too.
I even tried after removing itemTextStyle from line 582 and 633, but it does not work again.
What should I do now?

just found out that another library that is used in react-native-material-dropdown also use those deprecated props: it's react-native-material-textfield

i also have the same issue and have tried with above solution but still not working.

Its working fine in version 0.61.5 but this issue is in 0.62.0

Try removing any occurrence of Text.propTypes.style. I was using this library in an old component that wasn't in production anymore, so I just removed the library.

I did search all the Text.propTypes.style and remove that but still does not work.
I think this issue is with version 0.62.0 because it is working fine in version 0.61.5

@Shahanshah87  i have the same issue it is working fine in 0.61.5 version but not in 0.62 and not any updated of this library. i think, i have to leave using this library.

@Shahanshah87 i have the same issue it is working fine in 0.61.5 version but not in 0.62 and not any updated of this library. i think, i have to leave using this library.
You can use my fork
https://github.com/OrLevy23/react-native-material-dropdown

OrLevy23's fork doesn't show layout for me right, so i've prepared my own fork off latest 0.11.1:
npm i https://github.com/noway/react-native-material-dropdown

This error also occurs in 0.61.5 ....

OrLevy23's fork doesn't show layout for me right, so i've prepared my own fork off latest 0.11.1:
npm i https://github.com/noway/react-native-material-dropdown

This is working fine.
Thanks @noway for this.

    npm i https://github.com/noway/react-native-material-dropdown

This is working fine, thank you @noway

OrLevy23's fork doesn't show layout for me right, so i've prepared my own fork off latest 0.11.1:
npm i https://github.com/noway/react-native-material-dropdown

after entering npm i https://github.com/noway/react-native-material-dropdown in command prompt it is giving errors.

The below worked for me, got the answer from the link:
Afifa Khan, Stack Overflow

Commenting itemTextStyle: Text.propTypes.style in
..\node_modules\react-native-material-dropdown\src\components\dropdown file.

And remove Animated in Animated.Text.propTypes.style in

affix/index
helper/index
label/index

of react-native-material-textfield.

And added import { Animated, Text} from 'react-native'; in each of above three files.

The below worked for me, got the answer from the link:
Afifa Khan, Stack Overflow

Commenting itemTextStyle: Text.propTypes.style in
..\node_modules\react-native-material-dropdown\src\components\dropdown file.

And remove Animated in Animated.Text.propTypes.style in

affix/index
helper/index
label/index

of react-native-material-textfield.

And added import { Animated, Text} from 'react-native'; in each of above three files.

This Worked for me, on a project using RN 0.62. Thank you @pschorey

OrLevy23's fork doesn't show layout for me right, so i've prepared my own fork off latest 0.11.1:
npm i https://github.com/noway/react-native-material-dropdown

Working
thanks

I've solved it by these steps..

Remove installed package react-native-material-dropdown
yarn remove react-native-material-dropdown

Install new packages react-native-material-dropdown-v2 and react-native-paper.
yarn add react-native-material-dropdown-v2 react-native-paper

Swap react-native-material-dropdown used to react-native-material-dropdown-v2 in your code
e.g.
import { Dropdown } from 'react-native-material-dropdown' to import { Dropdown } from 'react-native-material-dropdown-v2'

3. import { Dropdown } from 'react-native-material-dropdown-v2'

its work for me, thanks

OrLevy23's fork doesn't show layout for me right, so i've prepared my own fork off latest 0.11.1:
npm i https://github.com/noway/react-native-material-dropdown

thanks, it's solved for me

npm i https://github.com/noway/react-native-material-dropdown don't work now :( RN 0.69.3.


Merge SparkExtension class into repo

SparkExtension is used for showing user SQL queries.

@weiqingy I don't see the codes where you merged, or are you going to merge this?

@jerryshao  Sorry for the late reply. I donot know why I didn't get any github notification.
I have submitted a PR(https://github.com/hortonworks-spark/spark-atlas-connector/pull/10) for this.

This is merged at https://github.com/hortonworks-spark/spark-atlas-connector/commit/36ec1994bc2ed6b87dee69bd9f1ad27c126d4d35


Add ability to enter buffer distance using text input

Currently, the only way to define the buffer distance is by using the buffer slider.  Consider adding a text box that allows users to define the buffer distance with text input.  Could be helpful to helping indicate more exact buffer distances.

We will only be making bug fixes at this time.  No action required.


OSError: lib/libth_transformer.so: cannot open shared object file: No such file or directory

I am facing this weird issue where torch is not able to detect libth_transformer.so file. I am able to successfully build it can see the libth_transformer.so file in build/lib folder, but I'm not sure why torch.classes.load_library is not detecting it. I am running bart translate_example.py. I have tried multiple times and have provide both relative and absolute path, still nothing.
Env: pytorch - 1.13.0, cuda version - 11.8, RTX 3080 Ti
I have tried it on the g5 instances (A10) of AWS too which still gives me the same error. I have also tried giving it all +rwx permissions too. Am I missing something?? Same happens while running T5 as well
OSError: /workspace/FasterTransformer/build/lib/libth_transfomer.so: cannot open shared object file: No such file or directory
Can anyone please help, Been stuck at it for a long time

I noticed that there seems to be a spelling mistake in your argument. It should be libth_transformer.so instead of libth_transfomer.so.


Docs: missing props tables

Regarding: 706

All props have been verified as showing up appropriately except for the following components:
Breakpoints Container
Container
Dropzone
Header
Line Chart
List


script to run program at a given time

Description
I have used the library Datetime of python to schedule the running of scripts.
dependencies:
install DateTime library of python by command
pip install DateTime
Fixes #(251)
#251 fixed
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change

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

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows [README.md)
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

Update README file

I have updated readme file .It was sent empty by mistake. Please review it.

Update README file

I have updated readme file .It was sent empty by mistake. Please review it.


Fixed permission-denied-error on unix systems in LoadosophiaUploader

When a plugin is used to run on multiple environments, it is sometimes preferable that the storeDir is set to the system's default temp directory. I tried out not to set storeDir at all, but then i got a "premission denied" error because the code tries to set an trailing slash to an empty string resulting in "/" which is then passed to File.createTempFile("Loadosophia_", ".jtl", new File("/")); which results in an temp-file in the root directory. If run with unprivileged user, it will fail to create that file.
Why is it necessary to set storeDir? Why don't you use the system's temp folder in all cases?

Changelog record is missing, according to http://jmeter-plugins.org/wiki/DeveloperGuide/

Setting store dir is important. For example, some systems have very limited temporary directory space, so they will need a way to change the place to store intermediary data.

Oh, sorry, I should have better first read the DevGuide :-) It's done now.

Thanks!


chore: replace custom cache step with config

The actions/setup-python@v2 and higher included a built-in cache
restore and post-run save step, meaning we can now retire our custom
steps for the configuration we want and gain some speed here.
Refs: actions/setup-python#266
Refs: https://github.com/actions/setup-python#caching-packages-dependencies
The actions/setup/node@v2 introduced support for configuring cache for
npm.
Since we use defaults, no changes are necessary other than setting the
installer type.
Refs: https://github.com/actions/setup-node/pull/272
Signed-off-by: Mike Fiedler<EMAIL_ADDRESS>

This does not impair existing caching behaviors, as the main addition is the post-action cache save, which due to the structure of the CI jobs, will collide on save - first one wins. Example: https://github.com/pypa/warehouse/runs/6850862495?check_suite_focus=true#step:16:3
I'm thinking about a general refactor of the steps here - and introducing a step-based workflow that runs the Dependencies job first - which should set up the cache for all other steps, and thus speed everything up a bit - saving ~1.5 minutes on every python-based step.
Should I attempt that in this scope as well, or save for another refactor?

Should I attempt that in this scope as well, or save for another refactor?

Upon further testing, looks like the downloads are cached, which is fine. Both node_modules and the python environments are not cached/restored between each step, so there won't be much savings anyhow - we can live with the current change of cache/restore of the download dependencies and take a little bit of time savings.


Link Water Features description to Example

Link https://spatial-information-qld.github.io/address-model/model.html#_water_based_addressing to https://github.com/Spatial-Information-QLD/feature-names-tests/tree/main/tests/017

Much updated for Issue #15 so resolved.


Text in docs do not match the code examples

File: engine/reference/commandline/login.md
The text says "For example, to use 'docker-credential-osxkeychain'" but the example code block does not contain this text.
The same issues exists with multiple examples and code blocks at that page - or it is not clear enough what you want to tell us ;)

Thanks for sharing the issue. The preceding sentence describes why the prefix is missing in the code block.
The value of the config property should be the suffix of the program to use (i.e. everything after docker-credential-).


Forwardport a few things from 3.1

@intellectronica cleared to land?

Coverage increased (+0.02%) to 90.139% when pulling bd9ed62286faf8bd0fa68a353898dd0db5ac2c8c on yakky:merge/3.1_151015 into 6ed7d819f8a236d3e3ca1cede974aef4fa719f89 on divio:develop.


TypeError: Object function createApplication() has no method 'createServer'

Stack trace:
01:45:50 web.1     | TypeError: Object function createApplication() {
01:45:50 web.1     |   var app = connect();
01:45:50 web.1     |   utils.merge(app, proto);
01:45:50 web.1     |   app.request = { __proto__: req };
01:45:50 web.1     |   app.response = { __proto__: res };
01:45:50 web.1     |   app.init();
01:45:50 web.1     |   return app;
01:45:50 web.1     | } has no method 'createServer'

Using Node.js 0.6.0, npm from git, express from git.
<EMAIL_ADDRESS>./node_modules/express
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
Happens on:
Express    = require "express"
Express.createServer()

master is 3.x you probably want the 2.x branch


Backport fix for docker stats in 1.10.3

Cherry-picks the fix from upstream https://github.com/docker/docker/commit/faf2b6f7aaca7f9ef400e227921b8125590fc9e5
Fixes https://github.com/coreos/bugs/issues/1526 for 1.10.3.

No longer shipping 1.10.3. Thank you for the 1.11 patch as well.


Disabled TextField InputDecoration errorText allocates space but is not shown

Steps to Reproduce

Create a TextField that has enabled: false and has decoration: InputDecoration().

Code of the sample app:

import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) => MaterialApp(
        title: 'Flutter Demo',
        home: MyHomePage(),
      );
}

class MyHomePage extends StatelessWidget {
  @override
  Widget build(BuildContext context) => Scaffold(
        body: Center(
          child: Padding(
            padding: EdgeInsets.all(16),
            child: Column(mainAxisAlignment: MainAxisAlignment.center, children: [
              Container(
                color: Colors.green.withOpacity(0.4),
                child: TextField(
                  enabled: false,
                  decoration: InputDecoration(
                    hintText: 'hintText',
                  ),
                ),
              ),
              SizedBox(height: 8),
              Container(
                color: Colors.orange.withOpacity(0.4),
                child: TextField(
                  enabled: false,
                  decoration: InputDecoration(hintText: 'hintText', errorText: 'Error text'),
                ),
              ),
              SizedBox(height: 8),
              Container(
                color: Colors.red.withOpacity(0.4),
                child: TextField(
                  decoration: InputDecoration(hintText: 'hintText', errorText: 'Error text'),
                ),
              ),
            ]),
          ),
        ), // This trailing comma makes auto-formatting nicer for build methods.
      );
}

Expected results:
To my mind, TextField should not allocate the space if it is disabled or it should still display the errorText;
Actual results:
At the moment it allocates the space but does not show the error itself;
Example image:

Issue replicable on latest stable. Tested on Android 8.1.0.
If the textfield is disabled that has errorText, the space is rendered even though the text is not, similar to an enabled textfield minus the error text.

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.0, on Mac OS X 10.15.4 19E2269, locale en-IN)
    • Flutter version 1.22.0 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision d408d302e2 (7 days ago), 2020-09-29 11:49:17 -0700
    • Engine revision 5babba6c4d
    • Dart version 2.10.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.49.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.11.0

[✓] Connected device (1 available)
    • SM A260G (mobile) • 5200763ebcfa861f • android-arm • Android 8.1.0 (API
      27)

• No issues found!

The issue is still reproducible as of the latest stable 3.3 and the master 3.6channel, The error text take space when the error is not present.

code sample
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) => MaterialApp(
        title: 'Flutter Demo',
        home: MyHomePage(),
      );
}

class MyHomePage extends StatelessWidget {
  @override
  Widget build(BuildContext context) => Scaffold(
        body: Center(
          child: Padding(
            padding: EdgeInsets.all(16),
            child: Column(mainAxisAlignment: MainAxisAlignment.center, children: [
              Container(
                color: Colors.green.withOpacity(0.4),
                child: const TextField(
                  enabled: false,
                  decoration: InputDecoration(
                    hintText: 'hintText',
                  ),
                ),
              ),
            const   SizedBox(height: 8),
              Container(
                color: Colors.orange.withOpacity(0.4),
                child:const  TextField(
                  enabled: false,
                  decoration: InputDecoration(hintText: 'hintText', errorText: 'Error text'),
                ),
              ),
             const  SizedBox(height: 8),
              Container(
                color: Colors.red.withOpacity(0.4),
                child: const TextField(
                  decoration: InputDecoration(hintText: 'hintText', errorText: 'Error text'),
                ),
              ),
            ]),
          ),
        ),

      );
}

flutter doctor -v (mac)
[✓] Flutter (Channel master, 3.6.0-6.0.pre.33, on macOS 12.6 21G115 darwin-arm64,
    locale en-IN)
    • Flutter version 3.6.0-6.0.pre.33 on channel master at
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision a9858ec524 (72 minutes ago), 2022-11-21 10:58:11 -0500
    • Engine revision 46a6b54295
    • Dart version 2.19.0 (build 2.19.0-406.0.dev)
    • DevTools version 2.19.0
    • If those were intentional, you can disregard the above warnings; however it is
      recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.70.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.53.20221101

[✓] Connected device (3 available)
    • iPhone 12 Pro (mobile) • 026D5789-9E78-4AD5-B1B2-3F8D4E7F65E4 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64
      • macOS 12.6 21G115 darwin-arm64
    • Chrome (web)           • chrome                               • web-javascript
      • Google Chrome 107.0.5304.110

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel stable, 3.3.9, on macOS 12.6 21G115 darwin-arm, locale en-IN)
    • Flutter version 3.3.9 on channel stable at /Users/mahesh/Development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b8f7f1f986 (24 hours ago), 2022-11-23 06:43:51 +0900
    • Engine revision 8f2221fbef
    • Dart version 2.18.5
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.70.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.53.20221101

[✓] Connected device (3 available)
    • iPhone 12 Pro (mobile) • 026D5789-9E78-4AD5-B1B2-3F8D4E7F65E4 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 12.6 21G115 darwin-arm
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 107.0.5304.110

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

what is the update in this issue???


add an ability to add custom supported chords

e. g. I want the lib to support chord A2 or A4 which are shorthands for Asus2 and Asus4

How would you configure such support? Provide a list of aliases?
Transposer.withAliases([{'A2':'Asus2'}, {'A4':'Asus4'}]).transpose(


Add global flow types to eslint globals

Added a subset of the global flow types from the fbjs eslint config to remove the no-undef errors for flow types as well as a few missing browser globals that were used in the codebase.
I also added a .eslintrc file to Examples to allow using alert there without warnings.

cc @satya164

Nice thanks!
@facebook-github-bot shipit


requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Python: 3.10.9
Sellix: sellix-python-sdk  1.0.5
replaced <YOUR_API_KEY> and <MERCHANT_NAME> with my own.
encounter this issue:
requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
from sellix import Sellix

# pass <MERCHANT_NAME> only if you need to be authenticated as an additional store

client = Sellix("<YOUR_API_KEY>", "<MERCHANT_NAME>")

try:
    products = client.get_products()
except Sellix.SellixException as e:
    print(e)

aslo ImportError: cannot import name 'Sellix' from partially initialized module 'sellix' (most likely due to a circular import)


Yearly

Hello,
I would like to know if there is a possibility to have only months by years?
Thank you for your reply.

This isn't a view that full-calendar provides at the moment.
See there docs for available views


Refactor retry logic for deployment key

Sometimes, a build might be triggered before the repository is registered, which mean a deployment key was added. For these reason we have a retry logic here https://github.com/taubyte/tau/blob/main/protocols/monkey/job.go#L88. Frankly, this code does not look good.
I suggest moving the check for deployment key to https://github.com/taubyte/tau/blob/main/protocols/monkey/job.go#L41, and use a helper function that will retry for a number of times till we get repo with a deployment key.

How much Attempts and Delay do we need?

You can have the retry and wait as global variables
In L41 we fetch repo info. we should re-try there if no key is found. then move on with the logic.
Re-fetching in L81 is not necessary

Hi @samyfodil , I would like to contribute to it and I have created a reusable Retry method. Is it too complex? Maybe I can simplify and only have it specific for deployment key. And for reading maxRetries & waitBeforeRetry how can we read from global variable os.GetEnv() || default or keep it in Monkey struct? Can you please guide me?
I have created a draft PR.


Rate limit ProcessOutputToLogStream

Sometimes, our sub-processes (such as Mesos), can get in a really tight loop and produce an overwhelming amount of output that overwhelms Jenkins and inhibits the test tear-down code from running.
Looking at a few of such cases, it seems obvious that we can effectively limit it via our ProcessOutputToLogStream logger class.
JIRA Issues: MARATHON-7809

@jeschkies My hypothesis was that when the Jenkins build jobs get stuck, it is not a deadlock, but it is too much logging overwhelming the Jenkins agent. This is corroborated by the fact that when the "logsplosion" happens, seconds worth of logs can take up to 1GB. I suspect, that at some point, the logsplosion starts to eat in to the JVMs ability to schedule threads effectively, cancel, and tear down.
At any rate, it seems that my hypothesis has been confirmed. https://jenkins.mesosphere.com/service/jenkins/job/marathon-pipelines/job/PR-5620/10/console was a stuck build. SystemResourceIntegrationTest-MesosMaster-32839 went in to the frenzy. After we suppressed 7,492,039 log lines over 5 minutes, the Mesos Master process was finally killed, as designed, when the test timed out.
Of course, it's always possible that there are other causes for jenkins builds getting stuck. All of the issues I've seen, recently, are from when the Mesos Master gets into a tight logging loop. Evidence confirms that that case is solved by this patch.

After we suppressed 7,492,039 log lines over 5 minutes, the Mesos Master process was finally killed, as designed, when the test timed out.

but this should not happen right? Why is the master not stopping? To me that's a bug.

Yes, it is not the core issue. The test times out and fails. This at least keeps Jenkins from crapping out.

I hope that this PR will also solve the issue (with some additional perks): https://github.com/mesosphere/marathon/pull/5633
by simply pumping stdout in the file - stderr alone is very few lines and would (in theory) never be able to break jenkins agent.
However I can see both approaches coexist - we should make sure however that maxLinesPerPeriod is high enough (1k is enough?) and is never seen during normal test runtime.

And since we already have Guava in dependencies - shouldn't we just take it?
import com.google.common.util.concurrent.RateLimiter

val rateLimiter: RateLimiter = RateLimiter.create(1000.0);
if (rateLimiter.tryAcquire()){
  ...
}


I WANT THE TEAM CALLED TEAM NAME 🎉

Optional extended description was on holiday.

:boom: THIS SOUNDS BRILLIANT


Unchecked lines should remain unchecked when zooming out

What did you do?

Visit /graph
Enter a query of the form 100 * (count by(job, namespace, service) (up == 0) / count by(job, namespace, service) (up)) > 10
See a couple of lines that correspond to that query (?)
In the "legend rickshaw_legend", click the action (✔) for all but one of them
See that only one line remains
Click the "glyphicon glyphicon-plus" to change the zoom

What did you expect to see?

Any line that I'd unchecked should remain unchecked.
The line I didn't uncheck should remain checked.
Lines that were not in the limited scope could appear checked since they had no reason not to.
If I had zoomed in and lost a line and then later zoomed out and regained a line, I'd expect it to remain hidden.

What did you see instead? Under which circumstances?
All of the lines were visible
Environment

System information:

Linux 4.19.112+ x86_64

Prometheus version:

prometheus, version 2.18.1 (branch: HEAD, revision: ecee9c8abfd118f139014cb1b174b08db3f342cf)
  build user:       root@2117a9e64a7e
  build date:       20200507-16:51:47
  go version:       go1.14.2

Alertmanager version:

Prometheus configuration file:

Alertmanager configuration file:

Logs:

Changing the zoom changes the query, so possibly alter query results, so that would be difficult to put in place. Grafana does this (retain selected legend when time changes) and I quite do not like it.
Note that you can deselect just one in one click by clicking directly on the 'V'.
cc @juliusv WDYT?

The problem is that I need to de-select all but one. Having to do that repeatedly is painful.

Then you can click on the text of that one.

Hello from the Bug Scrub!
Sounds like this issue is for the old UI, so let's close it. New UI(s) might still have this UX, so if anyone feels strong about it, feel free to add another issue and tag @juliusv for the decision making. Thanks!


Fix repo urls

Resolve #595 and add tests :smile_cat:
Let's get this in #610

Current coverage is 99.65%

Merging #655 into master will not affect coverage as of b19471c

@@            master    #655   diff @@
======================================
  Files           13      13
  Stmts          577     577
  Branches         0       0
  Methods          0       0
======================================
  Hit            575     575
  Partial          0       0
  Missed           2       2

Review entire Coverage Diff as of b19471c

Uncovered Suggestions

+0.35% via ...ookiecutter/utils.py#27...28

Powered by Codecov. Updated on successful CI builds.

@michaeljoseph :cookie:


Composer version constraints are incompatible with the current release of Laravel Homestead

I've just installed the most recent release of Laravel Homestead. The default packages installed with Composer on the current release of the Homestead box prevent the installation of forge-cli.
After Homestead's installation completes, the global package list is as follows (via composer global show):
vagrant@homestead:~
▶ composer global show
Changed current directory to /home/vagrant/.composer
doctrine/inflector               1.3.1              Common String Manipulations with regard to casing and singular/plural rules.
guzzlehttp/guzzle                6.5.2              Guzzle is a PHP HTTP client library
guzzlehttp/promises              v1.3.1             Guzzle promises library
guzzlehttp/psr7                  1.6.1              PSR-7 message implementation that also provides common utility methods
hirak/prestissimo                0.3.10             composer parallel install plugin
illuminate/contracts             v7.2.2             The Illuminate Contracts package.
illuminate/filesystem            v7.2.2             The Illuminate Filesystem package.
illuminate/support               v7.2.2             The Illuminate Support package.
laravel/envoy                    v2.0.1             Elegant SSH tasks for PHP.
laravel/installer                v3.0.1             Laravel application installer.
laravel/lumen-installer          v1.1.1             Lumen application installer.
laravel/spark-installer          dev-master 4c8dcd2 Command line installer for Laravel Spark.
nesbot/carbon                    2.31.0             An API extension for DateTime that supports 281 different languages.
psr/container                    1.0.0              Common Container Interface (PHP FIG PSR-11)
psr/http-message                 1.0.1              Common interface for HTTP messages
psr/simple-cache                 1.0.1              Common interfaces for simple caching
ralouphie/getallheaders          3.0.3              A polyfill for getallheaders.
slince/composer-registry-manager 2.3.0              Composer mirrors manager
symfony/console                  v5.0.5             Symfony Console Component
symfony/filesystem               v5.0.7             Symfony Filesystem Component
symfony/finder                   v5.0.5             Symfony Finder Component
symfony/polyfill-ctype           v1.15.0            Symfony polyfill for ctype functions
symfony/polyfill-mbstring        v1.14.0            Symfony polyfill for the Mbstring extension
symfony/polyfill-php73           v1.14.0            Symfony polyfill backporting some PHP 7.3+ features to lower PHP versions
symfony/process                  v5.0.5             Symfony Process Component
symfony/service-contracts        v2.0.1             Generic abstractions related to writing services
symfony/translation              v5.0.5             Symfony Translation Component
symfony/translation-contracts    v2.0.1             Generic abstractions related to translation
voku/portable-ascii              1.4.10             Portable ASCII library - performance optimized (ascii) string functions for php.

Trying to install this package with the command composer global require "sven/forge-cli" results in the following errors:
vagrant@homestead:~
▶ composer global require "sven/forge-cli"
Changed current directory to /home/vagrant/.composer
    1/5:        http://repo.packagist.org/p/provider-2020-04$83eb96e62de97b80ce3a7f173873660ec6f9db32c5357bc653cec40330640d62.json
    2/5:        http://repo.packagist.org/p/provider-latest$9047db88536a2f7e003a5eafcdf648f6b0c7274403182dcf31c0956a0a8be997.json
    3/5:        http://repo.packagist.org/p/provider-2017$9721b1ccb84023cd86e0d0c90ce50a3cb8f7595cf190d9c8505ca36009b1888c.json
    4/5:        http://repo.packagist.org/p/provider-2019-10$6dc0b4e5c117252c845145a27465cb969db3796f5202e616995aab830281bde9.json
    5/5:        http://repo.packagist.org/p/provider-2020-01$93d844837a76def4c4cf524c204c223b61861818f731b88a80597785bb795a9c.json
    Finished: success: 5, skipped: 0, failure: 0, total: 5
Using version ^0.4.0 for sven/forge-cli
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for sven/forge-cli ^0.4.0 -> satisfiable by sven/forge-cli[v0.4.0].
    - Conclusion: remove symfony/console v5.0.5
    - Conclusion: don't install symfony/console v5.0.5
    - sven/forge-cli v0.4.0 requires symfony/console ^4.0 || ^3.0 -> satisfiable by symfony/console[v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.17, v3.3.18, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.10, v3.4.11, v3.4.12, v3.4.13, v3.4.14, v3.4.15, v3.4.16, v3.4.17, v3.4.18, v3.4.19, v3.4.2, v3.4.20, v3.4.21, v3.4.22, v3.4.23, v3.4.24, v3.4.25, v3.4.26, v3.4.27, v3.4.28, v3.4.29, v3.4.3, v3.4.30, v3.4.31, v3.4.32, v3.4.33, v3.4.34, v3.4.35, v3.4.36, v3.4.37, v3.4.38, v3.4.39, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9, v4.0.0, v4.0.1, v4.0.10, v4.0.11, v4.0.12, v4.0.13, v4.0.14, v4.0.15, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9, v4.1.0, v4.1.1, v4.1.10, v4.1.11, v4.1.12, v4.1.2, v4.1.3, v4.1.4, v4.1.5, v4.1.6, v4.1.7, v4.1.8, v4.1.9, v4.2.0, v4.2.1, v4.2.10, v4.2.11, v4.2.12, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9, v4.3.0, v4.3.1, v4.3.10, v4.3.11, v4.3.2, v4.3.3, v4.3.4, v4.3.5, v4.3.6, v4.3.7, v4.3.8, v4.3.9, v4.4.0, v4.4.1, v4.4.2, v4.4.3, v4.4.4, v4.4.5, v4.4.6, v4.4.7].
    - Can only install one of: symfony/console[v4.3.0, v5.0.5].
    - Can only install one of: symfony/console[v4.3.1, v5.0.5].
    - Can only install one of: symfony/console[v4.3.10, v5.0.5].
    - Can only install one of: symfony/console[v4.3.11, v5.0.5].
    - Can only install one of: symfony/console[v4.3.2, v5.0.5].
    - Can only install one of: symfony/console[v4.3.3, v5.0.5].
    - Can only install one of: symfony/console[v4.3.4, v5.0.5].
    - Can only install one of: symfony/console[v4.3.5, v5.0.5].
    - Can only install one of: symfony/console[v4.3.6, v5.0.5].
    - Can only install one of: symfony/console[v4.3.7, v5.0.5].
    - Can only install one of: symfony/console[v4.3.8, v5.0.5].
    - Can only install one of: symfony/console[v4.3.9, v5.0.5].
    - Can only install one of: symfony/console[v4.4.0, v5.0.5].
    - Can only install one of: symfony/console[v4.4.1, v5.0.5].
    - Can only install one of: symfony/console[v4.4.2, v5.0.5].
    - Can only install one of: symfony/console[v4.4.3, v5.0.5].
    - Can only install one of: symfony/console[v4.4.4, v5.0.5].
    - Can only install one of: symfony/console[v4.4.5, v5.0.5].
    - Can only install one of: symfony/console[v4.4.6, v5.0.5].
    - Can only install one of: symfony/console[v4.4.7, v5.0.5].
    - Can only install one of: symfony/console[v3.0.0, v5.0.5].
    - Can only install one of: symfony/console[v3.0.1, v5.0.5].
    - Can only install one of: symfony/console[v3.0.2, v5.0.5].
    - Can only install one of: symfony/console[v3.0.3, v5.0.5].
    - Can only install one of: symfony/console[v3.0.4, v5.0.5].
    - Can only install one of: symfony/console[v3.0.5, v5.0.5].
    - Can only install one of: symfony/console[v3.0.6, v5.0.5].
    - Can only install one of: symfony/console[v3.0.7, v5.0.5].
    - Can only install one of: symfony/console[v3.0.8, v5.0.5].
    - Can only install one of: symfony/console[v3.0.9, v5.0.5].
    - Can only install one of: symfony/console[v3.1.0, v5.0.5].
    - Can only install one of: symfony/console[v3.1.1, v5.0.5].
    - Can only install one of: symfony/console[v3.1.10, v5.0.5].
    - Can only install one of: symfony/console[v3.1.2, v5.0.5].
    - Can only install one of: symfony/console[v3.1.3, v5.0.5].
    - Can only install one of: symfony/console[v3.1.4, v5.0.5].
    - Can only install one of: symfony/console[v3.1.5, v5.0.5].
    - Can only install one of: symfony/console[v3.1.6, v5.0.5].
    - Can only install one of: symfony/console[v3.1.7, v5.0.5].
    - Can only install one of: symfony/console[v3.1.8, v5.0.5].
    - Can only install one of: symfony/console[v3.1.9, v5.0.5].
    - Can only install one of: symfony/console[v3.2.0, v5.0.5].
    - Can only install one of: symfony/console[v3.2.1, v5.0.5].
    - Can only install one of: symfony/console[v3.2.10, v5.0.5].
    - Can only install one of: symfony/console[v3.2.11, v5.0.5].
    - Can only install one of: symfony/console[v3.2.12, v5.0.5].
    - Can only install one of: symfony/console[v3.2.13, v5.0.5].
    - Can only install one of: symfony/console[v3.2.14, v5.0.5].
    - Can only install one of: symfony/console[v3.2.2, v5.0.5].
    - Can only install one of: symfony/console[v3.2.3, v5.0.5].
    - Can only install one of: symfony/console[v3.2.4, v5.0.5].
    - Can only install one of: symfony/console[v3.2.5, v5.0.5].
    - Can only install one of: symfony/console[v3.2.6, v5.0.5].
    - Can only install one of: symfony/console[v3.2.7, v5.0.5].
    - Can only install one of: symfony/console[v3.2.8, v5.0.5].
    - Can only install one of: symfony/console[v3.2.9, v5.0.5].
    - Can only install one of: symfony/console[v3.3.0, v5.0.5].
    - Can only install one of: symfony/console[v3.3.1, v5.0.5].
    - Can only install one of: symfony/console[v3.3.10, v5.0.5].
    - Can only install one of: symfony/console[v3.3.11, v5.0.5].
    - Can only install one of: symfony/console[v3.3.12, v5.0.5].
    - Can only install one of: symfony/console[v3.3.13, v5.0.5].
    - Can only install one of: symfony/console[v3.3.14, v5.0.5].
    - Can only install one of: symfony/console[v3.3.15, v5.0.5].
    - Can only install one of: symfony/console[v3.3.16, v5.0.5].
    - Can only install one of: symfony/console[v3.3.17, v5.0.5].
    - Can only install one of: symfony/console[v3.3.18, v5.0.5].
    - Can only install one of: symfony/console[v3.3.2, v5.0.5].
    - Can only install one of: symfony/console[v3.3.3, v5.0.5].
    - Can only install one of: symfony/console[v3.3.4, v5.0.5].
    - Can only install one of: symfony/console[v3.3.5, v5.0.5].
    - Can only install one of: symfony/console[v3.3.6, v5.0.5].
    - Can only install one of: symfony/console[v3.3.7, v5.0.5].
    - Can only install one of: symfony/console[v3.3.8, v5.0.5].
    - Can only install one of: symfony/console[v3.3.9, v5.0.5].
    - Can only install one of: symfony/console[v3.4.0, v5.0.5].
    - Can only install one of: symfony/console[v3.4.1, v5.0.5].
    - Can only install one of: symfony/console[v3.4.10, v5.0.5].
    - Can only install one of: symfony/console[v3.4.11, v5.0.5].
    - Can only install one of: symfony/console[v3.4.12, v5.0.5].
    - Can only install one of: symfony/console[v3.4.13, v5.0.5].
    - Can only install one of: symfony/console[v3.4.14, v5.0.5].
    - Can only install one of: symfony/console[v3.4.15, v5.0.5].
    - Can only install one of: symfony/console[v3.4.16, v5.0.5].
    - Can only install one of: symfony/console[v3.4.17, v5.0.5].
    - Can only install one of: symfony/console[v3.4.18, v5.0.5].
    - Can only install one of: symfony/console[v3.4.19, v5.0.5].
    - Can only install one of: symfony/console[v3.4.2, v5.0.5].
    - Can only install one of: symfony/console[v3.4.20, v5.0.5].
    - Can only install one of: symfony/console[v3.4.21, v5.0.5].
    - Can only install one of: symfony/console[v3.4.22, v5.0.5].
    - Can only install one of: symfony/console[v3.4.23, v5.0.5].
    - Can only install one of: symfony/console[v3.4.24, v5.0.5].
    - Can only install one of: symfony/console[v3.4.25, v5.0.5].
    - Can only install one of: symfony/console[v3.4.26, v5.0.5].
    - Can only install one of: symfony/console[v3.4.27, v5.0.5].
    - Can only install one of: symfony/console[v3.4.28, v5.0.5].
    - Can only install one of: symfony/console[v3.4.29, v5.0.5].
    - Can only install one of: symfony/console[v3.4.3, v5.0.5].
    - Can only install one of: symfony/console[v3.4.30, v5.0.5].
    - Can only install one of: symfony/console[v3.4.31, v5.0.5].
    - Can only install one of: symfony/console[v3.4.32, v5.0.5].
    - Can only install one of: symfony/console[v3.4.33, v5.0.5].
    - Can only install one of: symfony/console[v3.4.34, v5.0.5].
    - Can only install one of: symfony/console[v3.4.35, v5.0.5].
    - Can only install one of: symfony/console[v3.4.36, v5.0.5].
    - Can only install one of: symfony/console[v3.4.37, v5.0.5].
    - Can only install one of: symfony/console[v3.4.38, v5.0.5].
    - Can only install one of: symfony/console[v3.4.39, v5.0.5].
    - Can only install one of: symfony/console[v3.4.4, v5.0.5].
    - Can only install one of: symfony/console[v3.4.5, v5.0.5].
    - Can only install one of: symfony/console[v3.4.6, v5.0.5].
    - Can only install one of: symfony/console[v3.4.7, v5.0.5].
    - Can only install one of: symfony/console[v3.4.8, v5.0.5].
    - Can only install one of: symfony/console[v3.4.9, v5.0.5].
    - Can only install one of: symfony/console[v4.0.0, v5.0.5].
    - Can only install one of: symfony/console[v4.0.1, v5.0.5].
    - Can only install one of: symfony/console[v4.0.10, v5.0.5].
    - Can only install one of: symfony/console[v4.0.11, v5.0.5].
    - Can only install one of: symfony/console[v4.0.12, v5.0.5].
    - Can only install one of: symfony/console[v4.0.13, v5.0.5].
    - Can only install one of: symfony/console[v4.0.14, v5.0.5].
    - Can only install one of: symfony/console[v4.0.15, v5.0.5].
    - Can only install one of: symfony/console[v4.0.2, v5.0.5].
    - Can only install one of: symfony/console[v4.0.3, v5.0.5].
    - Can only install one of: symfony/console[v4.0.4, v5.0.5].
    - Can only install one of: symfony/console[v4.0.5, v5.0.5].
    - Can only install one of: symfony/console[v4.0.6, v5.0.5].
    - Can only install one of: symfony/console[v4.0.7, v5.0.5].
    - Can only install one of: symfony/console[v4.0.8, v5.0.5].
    - Can only install one of: symfony/console[v4.0.9, v5.0.5].
    - Can only install one of: symfony/console[v4.1.0, v5.0.5].
    - Can only install one of: symfony/console[v4.1.1, v5.0.5].
    - Can only install one of: symfony/console[v4.1.10, v5.0.5].
    - Can only install one of: symfony/console[v4.1.11, v5.0.5].
    - Can only install one of: symfony/console[v4.1.12, v5.0.5].
    - Can only install one of: symfony/console[v4.1.2, v5.0.5].
    - Can only install one of: symfony/console[v4.1.3, v5.0.5].
    - Can only install one of: symfony/console[v4.1.4, v5.0.5].
    - Can only install one of: symfony/console[v4.1.5, v5.0.5].
    - Can only install one of: symfony/console[v4.1.6, v5.0.5].
    - Can only install one of: symfony/console[v4.1.7, v5.0.5].
    - Can only install one of: symfony/console[v4.1.8, v5.0.5].
    - Can only install one of: symfony/console[v4.1.9, v5.0.5].
    - Can only install one of: symfony/console[v4.2.0, v5.0.5].
    - Can only install one of: symfony/console[v4.2.1, v5.0.5].
    - Can only install one of: symfony/console[v4.2.10, v5.0.5].
    - Can only install one of: symfony/console[v4.2.11, v5.0.5].
    - Can only install one of: symfony/console[v4.2.12, v5.0.5].
    - Can only install one of: symfony/console[v4.2.2, v5.0.5].
    - Can only install one of: symfony/console[v4.2.3, v5.0.5].
    - Can only install one of: symfony/console[v4.2.4, v5.0.5].
    - Can only install one of: symfony/console[v4.2.5, v5.0.5].
    - Can only install one of: symfony/console[v4.2.6, v5.0.5].
    - Can only install one of: symfony/console[v4.2.7, v5.0.5].
    - Can only install one of: symfony/console[v4.2.8, v5.0.5].
    - Can only install one of: symfony/console[v4.2.9, v5.0.5].
    - Installation request for symfony/console (locked at v5.0.5) -> satisfiable by symfony/console[v5.0.5].

Installation failed, reverting ./composer.json to its original content.
✘ 2

Pull request #41 fixes this issue.

Fixed in #41. Thanks again @JackWH!


Add WiFi Reset Option

Although I don't expect it to get much use, it would be nice to expose the WiFi reset functionality from within Fermentrack for ESP-based controllers. I'm thinking add a switch to the "uninstall" screen for valid WiFi controllers that can be toggled to optionally reset everything at the same time as the device is uninstalled.

This is now in dev and should be pushed to master shortly


[ENH] docs (sphinx + readthedocs)

Implemented proper docs :scroll: :tada:
Main points:

Built with Sphinx.
Hosted in readthedocs: https://baikal.readthedocs.io/en/latest/
Uses Sphinx Material theme

Other changes:

Fixed several docstring issues.
Fixed typos in the user guide.
README.md now only has a brief introduction. The rest was moved to docs/src.

Codecov Report

Merging #29 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #29   +/-   ##
=======================================
  Coverage   99.87%   99.87%
=======================================
  Files          13       13
  Lines         812      812
  Branches      138      138
=======================================
  Hits          811      811
  Partials        1        1

Impacted Files
Coverage Δ

baikal/steps/expression.py
100% <ø> (ø)
:arrow_up:

baikal/plot.py
100% <ø> (ø)
:arrow_up:

baikal/_core/model.py
99.61% <ø> (ø)
:arrow_up:

baikal/sklearn.py
100% <ø> (ø)
:arrow_up:

baikal/_core/step.py
100% <ø> (ø)
:arrow_up:

baikal/steps/merge.py
100% <ø> (ø)
:arrow_up:

baikal/steps/factory.py
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


qt5.qtdatavis3d: init module

Description of changes
New module.
Things done

Built on platform(s)

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

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

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

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

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

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

libsForQt5.qt5.qtdatavis3d
libsForQt5.qt5.qtdatavis3d.bin
libsForQt5.qt5.qtdatavis3d.dev

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2121

Is this actually used by anything?

I locally packaged (and plan to upstream) nitrokey-app2 (the new rewrite in python). For this, I had to package PyQt5-stubs which has a ton of dependencies, among which is python3Packages.pyqtdatavisualization, which needs qt5.qtdatavis3d.
Instead of creating a MR for qt5.qtdatavis3d, python3Packages.{pyqtchart, pyqt3d, pyqtdatavisualization}, fixes to pyqt5 (fix QtConnectivity, add QtSerialPort, add QtDesigner), PyQt5-stubs, nitrokey-app2, I chose to create separate PRs. My plan would be this PR (qt5.qtdatavis3d), then another one for all the pyqt changes, then nitrokey-app2.

All right, just making sure.


INI config validation/check

It would be great to be able to check if a parameter does or does not exists. And if it does, being able to check that its value is correct.
If it's helpful here are Go projects for working with INI files:

https://github.com/go-ini/ini
https://github.com/alyu/configparser

And just fyi, here is how Salt does their YAML for INIs: https://docs.saltstack.com/en/latest/ref/states/all/salt.states.ini_manage.html

I think this is too specific, and there is a never ending set of config file formats out there to support. I would see if you can accomplish this with command instead combined with a simple script or command to extract parameters.
I'm following the 80/20 rule when it comes to adding functionality to goss, only tests that are pretty standard OS feature that would see wide use are built-in.


Do not print "Done!" after deployment phase; use only success/failure (binary)

Currently, we print "Done!" in most (but not all) cases after the code completes its "deployment" (phase/code).
However, If deployment fails, we still display "Done!" (in my case for "Deploying action HelloWorld/greeting ..." when the Deployment file had an invalid namespace).  The code should not display this as it implies successful completion to the user.  Also, this "Done!" was done after the actual "status" message which was confusing.
In fact, IMO the code should not print "Done!" at all, but stick to a binary success/failure paradigm.

For Blueprints work this would be very helpful, when my wskdeploy action runs on OW it's hard to handle the case where a trigger wasn't deployed if it existed already, as the overall result from wskdeploy is still "Done!..."

No longer applicable. Prints "Success: Deployment completed successfully." on successful deployment only:
	if err := deployer.deployAssets(); err != nil {
		wskprint.PrintOpenWhiskError(wski18n.T(wski18n.ID_MSG_DEPLOYMENT_FAILED))
		return err
	}

	wskprint.PrintOpenWhiskSuccess(wski18n.T(wski18n.T(wski18n.ID_MSG_DEPLOYMENT_SUCCEEDED)))


Update test fixtures

Recapturing fixtures to account for the new CPE enhancements that are causing failures in acceptance tests for https://github.com/anchore/grype-db/pull/67

Superseded by #69


[Help] How to cope with encrypted Authenticator?

I can not open because Google Authenticator is encrypted. I never includes "passphrase" but to open it must use a passphrase. Currently sya'm very need open Authenticator, because my account on some websites are protected Google Authenticator. how do I open it? please help me
!
untitled

Maybe your chrome account is encrypted.
Maybe there is no solution.
You must always have at least one or two backups of your secrets.


Udayton lessons contributions

There were over 100 local changes to Lessons that the University of Dayton has made over the years. I've narrowed them down to just the ones that were the most relevant to the community. Many changes relied on each other which made this difficult to share via separate pull requests for each feature.
I'm working now to create JIRA(s) for each improvement/bugfix, and I can rework these commits however we feel would be best.
This is just the initial migration of all the work. I still need to test these features in Sakai 21 and spend time cleaning up the code / making improvements, but I wanted to create the pull request now so others can take a look.

This work has been split into four pull requests. #8477 #8478 #8479 #8480
The LTI Tool icon work does not yet have a pull request.


About NVS metrics calculation

I have a simple question that I still haven't figured out so far. When calculating metrics like PSNR, do you directly use the image output from the model to compare with the ground truth GSO images, or first go through the reconstruction process and render images from the reconstructed object and then compare with the ground truth?

Hi, I use the generated views to calculate the PSNR instead of the rendering views.

Thanks, get it.😊

btw, regarding the input images, when evaluating metrics, do we directly use the first image i.e. "eval_samples/chicken-gt/000.jpg" as inputs?

Yes, we use the first image as condition.


Add a sanity check when building the image URL from multiple strings

Signed-off-by: Nico Schieder<EMAIL_ADDRESS>

/lgtm


Improvements to ceylon sh script

See individual commits. They’re loosely grouped by severity; if you want, you can exclude some.
I can’t find anything else I want to improve. The ls and expr stuff at the beginning looks scary, but apparently there’s just no good portable (POSIX) way to resolve a symlink. (readlink, realpath and stat are all non-portable.)

No no, you're not getting of that light. If you would have said "no", okay, but you said "I'm very confident" which is the same as saying "yes", the timing doesn't matter ;)

Btw I might have another change coming in very soon.


DETR VEA uses output of first layer of transformer decoder?

In https://github.com/tonyzhaozh/act/blob/694c606940fc16289bafbd4c5d2c70bc27a98207/detr/models/detr_vae.py#L131 and https://github.com/tonyzhaozh/act/blob/694c606940fc16289bafbd4c5d2c70bc27a98207/detr/models/detr_vae.py#L136 you index the output of the transformer with [0]. Does this not take the output of the first layer of the transformer decoder, instead of the last layer? And is this behaviour expected?

Agree. I removed subsequent layers and it had no effect on training.

@CarlDegio hello,I changed 0 to -1 and used the output of the last layer, but there is no obvious difference in the effect. May I ask that your experiment is effective?

I did not try the effect of multi-layer decoder. I just removed the decoder forward propagation that was not used in the original code to speed up the training.


config.omnibus.install_url = '/some/path/on/the/host' doesn't work on windows

Looks like on windows the download is initialized with WebClient, and the ?v breaks when attempting to 'download' from local path.
Vagrantfile:
    config.omnibus.chef_version = '12.0.3'
    config.omnibus.install_url = 'c:\\parent_binaries\\chef_client\\'
    config.vm.guest = :windows #needed for vagrant omnibus to work (1.4.1 has a bug https://github.com/chef/vagrant-omnibus/issues/90)
    config.vm.communicator = "winrm"

Error:
powershell -command "(New-Object System.Net.WebClient).DownloadFile('c:\parent_binaries\chef_client\?v=%version%', '%dest%')"

Gets translated to:
(New-Object System.Net.WebClient).DownloadFile('c:\parent_binaries\chef_client\?v=12.0.3', 'C:\Users\vagrant\chef-client-12.0.3-1.windows.msi')

PS C:\Users\vagrant> (New-Object System.Net.WebClient).DownloadFile('c:\parent_binaries\chef_client\?v=12.0.3', 'C:\User
s\vagrant\chef-client-12.0.3-1.windows.msi')
Exception calling "DownloadFile" with "2" argument(s): "Illegal characters in path."
At line:1 char:47
+ (New-Object System.Net.WebClient).DownloadFile <<<< ('c:\parent_binaries\chef_client\?v=12.0.3', 'C:\Users\vagrant\ch
ef-client-12.0.3-1.windows.msi')
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : DotNetMethodException

I am not sure if there is a simple syntax change that would allow both. Paging @smurawski

After looking at the code in more details, if I understood it correctly, it doesn't look like Windows supports custom installer script.
if windows_guest? generate file, otherwise use custom one

I am not familiar with Vagrants internals, so I don't know if Vagrant::Util::Downloader works on windows. But it would be nice if a custom installer could be defined for windows as well.

testing the following syntax
if(test-path $url\chef-client*%version%-1.windows.msi){copy $url\chef-client*%version%-1.windows.msi %dest%}else{"(New-Object System.Net.WebClient).DownloadFile('c:\parent_binaries\chef_client\?v=%version%', '%dest%')"}

pull request here:
https://github.com/chef/vagrant-omnibus/pull/111


Optionally Enable/Disable count queries for paging requests

When paging using this library a count query is made to get the total number of items that matches a query.
This could be costly in larger datasets.
I propose two ways to disable paging:

[ ] global setting on RepositoryOptions to turn this on/off
[ ] overload on the page methods themselves that default to false making this opt-in to avoid running up a large unexpected bill.

Thanks @robertbennett1998 this was closed as part of the PR #213