[CLI] Downloading a reference artifact from S3 fails with an error 404.

Description
I'm trying to follow the guide on https://docs.wandb.ai/guides/artifacts/references.
But I'm getting an error:

ClientError: An error occurred (404) when calling the HeadObject operation: Not Found

Wandb features
What lines of wandb code are you using?
import wandb
run = wandb.init()
artifact = run.use_artifact('kostas1984/py-vision-src_research_nbs_wanb_test/wand_dataset_test:v2', type='dataset')
artifact_dir = artifact.download()

How to reproduce

Follow guide on  https://docs.wandb.ai/guides/artifacts/references.
Create a few different versions on s3
Try to download an artifact

Environment

OS: Windows
Environment: Jupyter Lab
Python Version: 3.8.0

Full Log
Finishing last run (ID:35vjzym2) before initializing another...

Waiting for W&B process to finish, PID 21448... (success).
Synced 5 W&B file(s), 0 media file(s), 0 artifact file(s) and 1 other file(s)
Synced spring-universe-14: https://wandb.ai/kostas1984/py-vision-src_research_nbs_wanb_test/runs/35vjzym2
Find logs at: .\wandb\run-20211101_172631-35vjzym2\logs
Successfully finished last run (ID:35vjzym2). Initializing new run:
Syncing run morning-fire-15 to Weights & Biases (docs).
---------------------------------------------------------------------------
ClientError                               Traceback (most recent call last)
<ipython-input-7-bffb22ca41a4> in <module>
      2 run = wandb.init()
      3 artifact = run.use_artifact('kostas1984/py-vision-src_research_nbs_wanb_test/wand_dataset_test:v2', type='dataset')
----> 4 artifact_dir = artifact.download()

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\apis\public.py in download(self, root, recursive)
   3670
   3671         pool = multiprocessing.dummy.Pool(32)
-> 3672         pool.map(partial(self._download_file, root=dirpath), manifest.entries)
   3673         if recursive:
   3674             pool.map(lambda artifact: artifact.download(), self._dependent_artifacts)

C:\Python\Python38\lib\multiprocessing\pool.py in map(self, func, iterable, chunksize)
    362         in a list that is returned.
    363         '''
--> 364         return self._map_async(func, iterable, mapstar, chunksize).get()
    365
    366     def starmap(self, func, iterable, chunksize=None):

C:\Python\Python38\lib\multiprocessing\pool.py in get(self, timeout)
    766             return self._value
    767         else:
--> 768             raise self._value
    769
    770     def _set(self, i, obj):

C:\Python\Python38\lib\multiprocessing\pool.py in worker(inqueue, outqueue, initializer, initargs, maxtasks, wrap_exception)
    123         job, i, func, args, kwds = task
    124         try:
--> 125             result = (True, func(*args, **kwds))
    126         except Exception as e:
    127             if wrap_exception and func is not _helper_reraises_exception:

C:\Python\Python38\lib\multiprocessing\pool.py in mapstar(args)
     46
     47 def mapstar(args):
---> 48     return list(map(*args))
     49
     50 def starmapstar(args):

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\apis\public.py in _download_file(self, name, root)
   3760     def _download_file(self, name, root):
   3761         # download file into cache and copy to target dir
-> 3762         return self.get_path(name).download(root)
   3763
   3764     def _default_root(self, include_version=True):

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\apis\public.py in download(self, root)
   3182         manifest = self._parent_artifact._load_manifest()
   3183         if self.entry.ref is not None:
-> 3184             cache_path = manifest.storage_policy.load_reference(
   3185                 self._parent_artifact,
   3186                 self.name,

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\sdk\wandb_artifacts.py in load_reference(self, artifact, name, manifest_entry, local)
    914         local: bool = False,
    915     ) -> str:
--> 916         return self._handler.load_path(artifact, manifest_entry, local)
    917
    918     def _file_url(

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\sdk\wandb_artifacts.py in load_path(self, artifact, manifest_entry, local)
   1066                 'No storage handler registered for scheme "%s"' % str(url.scheme)
   1067             )
-> 1068         return self._handlers[str(url.scheme)].load_path(
   1069             artifact, manifest_entry, local=local
   1070         )

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\sdk\wandb_artifacts.py in load_path(self, artifact, manifest_entry, local)
   1342             # and fallback to listing all versions if we don't have a match.
   1343             obj = self._s3.Object(bucket, key)
-> 1344             etag = self._etag_from_obj(obj)
   1345             if etag != manifest_entry.digest:
   1346                 if self.versioning_enabled(bucket):

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\sdk\wandb_artifacts.py in _etag_from_obj(obj)
   1473     def _etag_from_obj(obj: "boto3.s3.Object") -> str:
   1474         etag: str
-> 1475         etag = obj.e_tag[1:-1]  # escape leading and trailing quote
   1476         return etag
   1477

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\boto3\resources\factory.py in property_loader(self)
    337             if self.meta.data is None:
    338                 if hasattr(self, 'load'):
--> 339                     self.load()
    340                 else:
    341                     raise ResourceLoadException(

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\boto3\resources\factory.py in do_action(self, *args, **kwargs)
    503             # instance via ``self``.
    504             def do_action(self, *args, **kwargs):
--> 505                 response = action(self, *args, **kwargs)
    506                 self.meta.data = response
    507             # Create the docstring for the load/reload mehtods.

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\boto3\resources\action.py in __call__(self, parent, *args, **kwargs)
     81                      operation_name, params)
     82
---> 83         response = getattr(parent.meta.client, operation_name)(*args, **params)
     84
     85         logger.debug('Response: %r', response)

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\botocore\client.py in _api_call(self, *args, **kwargs)
    384                     "%s() only accepts keyword arguments." % py_operation_name)
    385             # The "self" in this scope is referring to the BaseClient.
--> 386             return self._make_api_call(operation_name, kwargs)
    387
    388         _api_call.__name__ = str(py_operation_name)

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\botocore\client.py in _make_api_call(self, operation_name, api_params)
    703             error_code = parsed_response.get("Error", {}).get("Code")
    704             error_class = self.exceptions.from_code(error_code)
--> 705             raise error_class(parsed_response, operation_name)
    706         else:
    707             return parsed_response

ClientError: An error occurred (404) when calling the HeadObject operation: Not Found

Any suggestions?
Many thanks,
Kostas

Hey @cyberkostas1984 when using reference artifacts we can't guarantee that they won't be deleted.  Are you sure the object still exists in your bucket?  If you confirm the object exists, then it's likely an issue with credentials in your environment.  Make sure you can use the aws cli to list or access the bucket from the same environment you run the script in.

hey @vanpelt ,
Thanks for your response.
AWS CLI is configured I think fine, and I can list all objects successfully.

AWS CLI is setup on Commnad prompt and Poweshell that jupyter uses.
Is there anything else that I can check?
Thanks,
Kostas

We capture the version of the object by default with S3.  Do you know if you have versioning enabled and perhaps deleted an older version of the file?  Are you able to see exactly which file we're unable to download?

Hi,
I tried working on a new bucket that has versioning enabled from the start (as on the original bucket it was enabled afterwards, because I thought it was optional to have enabled), but still I'm getting the same error.
This is what I'm running:

And these are the logs:
---------------------------------------------------------------------------
ClientError                               Traceback (most recent call last)
<ipython-input-4-b4ed4fc67fc2> in <module>
      1 run = wandb.init()
      2 artifact = run.use_artifact("wandb_versioning_v3:latest", type="dataset")
----> 3 artifact.download()
      4 run.use_artifact(artifact)

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\apis\public.py in download(self, root, recursive)
   3670
   3671         pool = multiprocessing.dummy.Pool(32)
-> 3672         pool.map(partial(self._download_file, root=dirpath), manifest.entries)
   3673         if recursive:
   3674             pool.map(lambda artifact: artifact.download(), self._dependent_artifacts)

C:\Python\Python38\lib\multiprocessing\pool.py in map(self, func, iterable, chunksize)
    362         in a list that is returned.
    363         '''
--> 364         return self._map_async(func, iterable, mapstar, chunksize).get()
    365
    366     def starmap(self, func, iterable, chunksize=None):

C:\Python\Python38\lib\multiprocessing\pool.py in get(self, timeout)
    766             return self._value
    767         else:
--> 768             raise self._value
    769
    770     def _set(self, i, obj):

C:\Python\Python38\lib\multiprocessing\pool.py in worker(inqueue, outqueue, initializer, initargs, maxtasks, wrap_exception)
    123         job, i, func, args, kwds = task
    124         try:
--> 125             result = (True, func(*args, **kwds))
    126         except Exception as e:
    127             if wrap_exception and func is not _helper_reraises_exception:

C:\Python\Python38\lib\multiprocessing\pool.py in mapstar(args)
     46
     47 def mapstar(args):
---> 48     return list(map(*args))
     49
     50 def starmapstar(args):

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\apis\public.py in _download_file(self, name, root)
   3760     def _download_file(self, name, root):
   3761         # download file into cache and copy to target dir
-> 3762         return self.get_path(name).download(root)
   3763
   3764     def _default_root(self, include_version=True):

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\apis\public.py in download(self, root)
   3182         manifest = self._parent_artifact._load_manifest()
   3183         if self.entry.ref is not None:
-> 3184             cache_path = manifest.storage_policy.load_reference(
   3185                 self._parent_artifact,
   3186                 self.name,

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\sdk\wandb_artifacts.py in load_reference(self, artifact, name, manifest_entry, local)
    914         local: bool = False,
    915     ) -> str:
--> 916         return self._handler.load_path(artifact, manifest_entry, local)
    917
    918     def _file_url(

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\sdk\wandb_artifacts.py in load_path(self, artifact, manifest_entry, local)
   1066                 'No storage handler registered for scheme "%s"' % str(url.scheme)
   1067             )
-> 1068         return self._handlers[str(url.scheme)].load_path(
   1069             artifact, manifest_entry, local=local
   1070         )

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\sdk\wandb_artifacts.py in load_path(self, artifact, manifest_entry, local)
   1342             # and fallback to listing all versions if we don't have a match.
   1343             obj = self._s3.Object(bucket, key)
-> 1344             etag = self._etag_from_obj(obj)
   1345             if etag != manifest_entry.digest:
   1346                 if self.versioning_enabled(bucket):

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\wandb\sdk\wandb_artifacts.py in _etag_from_obj(obj)
   1473     def _etag_from_obj(obj: "boto3.s3.Object") -> str:
   1474         etag: str
-> 1475         etag = obj.e_tag[1:-1]  # escape leading and trailing quote
   1476         return etag
   1477

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\boto3\resources\factory.py in property_loader(self)
    337             if self.meta.data is None:
    338                 if hasattr(self, 'load'):
--> 339                     self.load()
    340                 else:
    341                     raise ResourceLoadException(

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\boto3\resources\factory.py in do_action(self, *args, **kwargs)
    503             # instance via ``self``.
    504             def do_action(self, *args, **kwargs):
--> 505                 response = action(self, *args, **kwargs)
    506                 self.meta.data = response
    507             # Create the docstring for the load/reload mehtods.

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\boto3\resources\action.py in __call__(self, parent, *args, **kwargs)
     81                      operation_name, params)
     82
---> 83         response = getattr(parent.meta.client, operation_name)(*args, **params)
     84
     85         logger.debug('Response: %r', response)

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\botocore\client.py in _api_call(self, *args, **kwargs)
    384                     "%s() only accepts keyword arguments." % py_operation_name)
    385             # The "self" in this scope is referring to the BaseClient.
--> 386             return self._make_api_call(operation_name, kwargs)
    387
    388         _api_call.__name__ = str(py_operation_name)

~\Documents\cyberhawk_local\github\private\py-vision\.venv\lib\site-packages\botocore\client.py in _make_api_call(self, operation_name, api_params)
    703             error_code = parsed_response.get("Error", {}).get("Code")
    704             error_class = self.exceptions.from_code(error_code)
--> 705             raise error_class(parsed_response, operation_name)
    706         else:
    707             return parsed_response

ClientError: An error occurred (404) when calling the HeadObject operation: Not Found

These are the artifacts on Wandb:

Am I correct to understand that these artifacts, can only be used through your API for training?
Is it possible to download a specific version of the dataset and use it on another ML library ie pure Pytorch?
Thanks

@cyberkostas1984 the '' in the reference url seems like a smoking gun.  In your object store is the object within a sub folder named "dataset_test" or are they literally files named "dataset_test\20210920...".  Seems like the folder seperator in windows vs unix / cloud storage could be causing the problem.
When you're using reference artifacts you can download them independent of the wandb library.  Simply use boto3 or any other library to pull down data from your bucket.  Behind the scenes wandb is just making requests to the s3 api for reference artifacts using boto, the source code is available in this repo.  The advantage of downloading with the wandb library is we capture the specific version of a file in your bucket so when you goto download an historic file it will use the old version if it had since been overwritten in your bucket.

hey @vanpelt , thanks for pointing that out.
In the end running the code from an ubuntu instance, and having a new clean s3 bucket with versioning from the start, managed to resolve all the issues :).
Thanks again for your help 👍
Cheers


Refactor check server using helper functions

todo -- sagemaker refactor

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#958  👈
#949
#948
#947
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @carolineechen and the rest of your teammates on  Graphite


imported 'enumValues' get prefixed when put in input fields

Describe the bug
When I set typePrefix(ex. 'I'), enums(ex. 'MyEnum') registered as 'enumValues' in codegen.yml are imported in generated file without the prefix (-> 'MyEnum').
If I put those enum types in input fields, then those get prefixed in input fields when generated(ex. myEnum: IMyEnum). In this case, the enum type name 'IMyEnum' in generated input fields is different with the enum type name 'Enum', so the enum type evokes Not Found Error.
If you'd like to fix this issue, it helps for you to look packages/plugins/other/visitor-plugin-common/src/variables-to-object.ts I guess.
(+ enumPrefix: false is not a solution for this problem, it throws another error..)
To Reproduce

codegen.yml

overwrite: true
    schema: 'typedefs/**/*.graphql'
    documents: null
    generates:
      src/generated/graphql.ts:
        config:
          typesPrefix: I
          namingConvention:
            enumValues: change-case#constantCase
          enumValues:
            MyEnum: ../types#MyEnum
          mappers:
           ...(skip)...
        plugins:
          - 'typescript'
          - 'typescript-resolvers'

example.graphql

Please ignore why I put the enum in login input. It's just for an example :)

Bad situation

type Mutation {
  # situation 1
  login(
    username: String!,
    password: String!,
    myEnum: MyEnum
  ): LoginPayload
}

Good situation

input LoginInput {
  username: String!
  password: String!
  myEnum: MyEnum
}

type Mutation {
 # situation 2
  login(input: LoginInput): LoginPayload
}

generated/graphql.ts

Bad situation

import { MyEnum } from '../types';

export type IMutationLoginArgs = {
  username: Scalars['String']
  password: Scalars['String']
  myEnum?: Maybe<IMyEnum> // 'Cannot find name IMyEnum' !!!
}

Good situation

import { MyEnum } from '../types';

export type ILoginInput = {
   __typename?: 'LoginInput',
  username: Scalars['String'],
  password: Scalars['String'],
  myEnum?: Maybe<MyEnum>,
};

Expected behavior
when I put enum registered as enumValues in codegen.yml in input fields, I expected the type name doesn't get prefixed in generated code.
Environment:

OS: MAC
NodeJS: v12.10.0
package.json

"@graphql-codegen/cli": "^1.8.3",
"@graphql-codegen/typescript": "^1.8.3",
"@graphql-codegen/typescript-resolvers": "^1.8.3",
"typescript": "^3.7.2"

@roseline124 I think I managed to fix that in this PR: https://github.com/dotansimha/graphql-code-generator/pull/3015

Fixed in 1.9.0

Thanks!! :)


💄 Mobile/API | Add "Others" filter to the Networking page

Cc: @matt-goldman @zacharykeeping @Anton-Polkanov

Hi @tkapa
Pain

Blocked by: #739
The user currently doesn't have a way to see any community members that they have scanned or are yet to meet.
Suggested Solution

Add the "Others" Filter to the Networking page, and display External Scanned users to the "Friends" filter.
Tasks

[ ] Investigate
[ ] Add API Endpoints if Required
[ ] Implement UI

Acceptance Criteria

[ ] Meets Definition of Done - {{ LINK }}
[ ] User can see any non-SSW people that they have and have not scanned in the Networking page

More Information

Screenshots

Thanks!

Note that #739 is completed so this is not blocked by that now.
@bettybondoc I seem to recall we had a chat about this - did we agree on an approach here? This is regarding showing everyone in the app (not just SSW peeps).

@matt-goldman-ssw
I think we agreed to have 3 tabs:

Following (people we have scanned)
Followers (people who scanned us)
To Meet (people whom we haven't scanned yet and haven't been scanned by us)

And then use the green QR code icon to show that we have scanned them

Thanks @bettybondoc. I wasn't sure what we were doing with non-SSW folks. I can see that now under "to meet" we have only SSWers, but for the other 2 you can see SSWers plus externals that have scanned you or you have scanned. That's what we agreed right? Otherwise the "to meet" tab will have too many people.

@matt-goldman-ssw
Yes - only showing SSWers under "To Meet"
I think we also discussed additional features that could enhance the UX if we decide to show everyone. Otherwise, it may result in an endless scroll of users with accounts.
Here are some potential features to improve the UX and make "To Meet" more intuitive:

Check-in: Display only those currently checked in at the conference under "To Meet". This way users won't have to look for missing people.
Search: Add a search function within each tab ("Following," "Followers," and "To Meet") to help manage longer lists. This search should be placed strategically to avoid users mistaking it for a global search.
Hide Inactive Accounts: Reduce clutter by hiding accounts that haven't been active for a specific period (e.g., 2 months)


License

I'd like to use this project for my game, but it's missing a license. Could you add an MIT or some other free software license?

Oh wow, surprised I missed this. Just added.


Option to create dump on test failure

Summary
It would be useful to be able to automatically create a dump on failed test/assertion. This is especially interesting when the issue is quite randomic and we are not having enough info to try to replicate the issue.
This should not be the default configuration but more an option that can be enabled. We could consider having some specific filter flag too to avoid launching the debugger on any failed test but rather on a list of tests.
cc @MarcoRossignoli @nohwnd
This relates to #2033 and could be handy for CI where launching debugger would be pointless.

FYI, there are also some options in vstest to collect addtional information in case of test hangups:
https://github.com/microsoft/vstest/blob/main/docs/RFCs/0028-BlameCollector-Hang-Detection.md
But I can imagine that creating a crashdump on an (assertion) failure needs to be done in mstest related code (instead of in vstest)

Hi @japj,
Thanks! We are aware of the crash dump and hang dump features of VSTest but as you pointed out this is a different suggestion that would create a dump on assertion failure and not test hang or test app crash.


Sortier ran on code base

Added sortier to npm dev dependencies
Added sortier run script in package.json
Ran the npm run sortier script

never mind.. too many file changes for 1 MR


Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.

When using the devtool extension I get this error in my browser console. Goes away when disabled.
Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.

@bay-jacewhitten have you managed to solve this?

I know longer use the extension. I was not able to successfully quiet this
error.
On Fri, May 12, 2023 at 12:43 AM shakazullu94 @.***>
wrote:

@bay-jacewhitten https://github.com/bay-jacewhitten have you managed to
solve this?
—
Reply to this email directly, view it on GitHub
https://github.com/growthbook/devtools/issues/3#issuecomment-1545319697,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS356OA7VIQS6DYCPS2XMRDXFXS3PANCNFSM6AAAAAAQZ6A5MA
.
You are receiving this because you were mentioned.Message ID:
@.***>

This is still an issue, and quite annoying. It takes about 4 seconds after loading of the page to appear. It's definitely related to this extension, because it does not appear when extension is disabled.

I believe this has been fixed - please update to version 0.3.2 of the chrome extension if you haven't already.


XUnit tabs not clickable

Using version 1.4.23.HOTFIX1, The tabs under XUnit widget that show different tests and their status are apparently not clickable (in both Chrome and FF). I expect them to link to appropriate sections in the report.

Try 1.4.24.RC3
It was fixed there.


Wave not show wave effect on first time when attached in Fragment

When Fragment was created I injected some logic to overall view that not include waveview,
I wonder why wave is not working, but when I drag notification bar down and push it up and look up WaveView in app. The wave was worked right.
What was something that I had wrong.
PS. I try to use
waveView.invalidate();
waveView.postInvalidate();
waveView.postInvalidate(5000);
It seems not working.

I sovled it by this code .
In Wave.java , add this code .
   @Override     protected void onLayout(boolean changed, int left, int top, int right, int bottom) {         super.onLayout(changed, left, top, right, bottom);         startWave();     }

Worked for me


Debug

var_dump($myVar); works but Atomik::debug($myVar); does not ouput anything
am i doing someting wrong ?
im using the default settings from composer create-project atomik/skeleton .

turns out you need to use
$this->debug($myVar, $force = true)
you should update your documentation


connect-livereload listed as a devdependency but used in production

index.js requires connect-livereload, but as this module is listed as a devdependency, it is not available in production.
We should either do a conditional require, or move the module to the regular dependency list.

It is only used for dev, we just need to figure out how to not activate this in index.js when deploying.


Missing: added two projects from 2022 with full marks

The projects were added to the 2022 list, briefly comparing the quality of the README.md presents in the various repositories. The https://github.com/laughinginloud/ing-sw-2022-manfredi-martelli-meneghin project was favoured as it contains a wiki section and screenshots of the game, on top of being well organised.
If the order was already decided based on other criteria, please review this PR, modifying the order of projects as you prefer.

I just noticed that the project https://github.com/laughinginloud/ing-sw-2022-manfredi-martelli-meneghin was already present in the README.md, but it was erroneously put in the "other" category while it is a 30L project. So the correct name for this PR is "EVALUATION" and "MISSING", as the second project I added was not present before.

Mmm where have I seen those icons in the "Before playing" section 🤨?
Anyhow the order does not matter and does not reflect the actual quality of the projects.

Hahahaha good projects (and good icons), deserve to be carried on 😄
Hopefully these projects will help current and future students to develop their project and also correctly document them.
Thanks for the merge! To the next one!


Create cmd entry points

Create cmd entry points for ygg create & ygg remove (one app at a time only?)

Added in 2.0.0-alpha.4


[Reorganization Proposal 1] Move traits into blocking/nonblocking modules

As discussed in our weekly meeting.
I chose nonblocking as module name because nb could be misunderstood as a re-exported nb crate.
An alternative is #279

r? @therealprof
(rust-highfive has picked a reviewer for you, use r? to override)

Any objections or can we merge this @rust-embedded/hal ?
This PR is a bit of a gatekeeper for any other changes because of the file shuffling.

parallel futures module seems reasonable and i don't have strong opinions for / against, lgtm

Alright, can I get an actual approval here @rust-embedded/hal?


summit_xl_sim: 1.0.0-0 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository summit_xl_sim to 1.0.0-0:

upstream repository: https://github.com/RobotnikAutomation/summit_xl_sim.git
release repository: https://github.com/RobotnikAutomation/summit_xl_sim-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.21
previous version for package: null

Since this pr changes the file in the same location as the other pr you need to rebase this to resolve conflicts.


CLI output for example equation doesn't render

In the 0.10.1 CLI, I ran npx katex -i C:/Tools/Katex-1.txt -o C:/Tools/Katex-out.html
Where Katex-1.txt contains the example equation from the docs: c = \\pm\\sqrt{a^2 + b^2}
I've tried rendering the resulting HTML in browsers directly, and on CodePen, but it's broken in all cases. The CodePen, with the full HTML syntax that KaTeX created is here.
Pasting the contents of katex.css into CodePen's CSS box slightly improved the situation, but as you can see below, the equation is still broken across three lines, and it's displaying the letters pm instead of the plus-minus sign.

Browsers are Edge 18, Firefox 65, and Chrome 72, all on Windows 10. The rendering is the same in all three browsers.
How does the CLI output normally work? Does it require katex.css? The font code seems to use relative paths. Is this a font problem? How would we normally configure the fonts?

There is no need to escape backslash in the CLI (unless needed by the shell you're using): c = \pm\sqrt{a^2 + b^2}.

Thanks! That fixed it. I didn't catch the escaping. Thanks again.


Please add expected network bandwidth

The "Size table definitions" section of the page even defines the "expected network bandwidth" column, but the column is not present.
I opened #19981 for this over a year ago and it was closed without an answer.

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

ID: 3d9f65d0-2ef2-bc61-a57d-7607421d3e8a
Version Independent ID: e5413b4b-bfe6-1e7c-ea31-5ea302d63ae9
Content: Azure Windows VM sizes - HPC - Azure Windows Virtual Machines
Content Source: articles/virtual-machines/windows/sizes-hpc.md
Service: virtual-machines-windows
GitHub Login: @vermagit
Microsoft Alias: amverma

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
CC: @MicahMcKittrick-MSFT

Thanks for the feedback. I'll reconsider adding the expected network bandwidth (for Ethernet, not InfiniBand) for the SKUs. The implications of adding that 'expectation' are that the observed performance from the workload depends on a lot of other factors as outlined in the section.
@cynthn

We are working on consistency across all our sizing docs. This is in the backlog.
#please-close


ARROW-14552: [C++][Gandiva] Implement Quarter Function Alias

Added Alias for the extract quarter a the gandiva

Moved to #12875


Allow panels to be used for unauthenticated users.

The only thing stopping a Panel from being used as a public Panel without user authentication is the user-menu being required in the top bar. This adds an auth check to only render the user-menu component when a user is authenticated.
I saw your comment that Panels aren't meant to be used for unauthenticated users, however I think this small change as well as the user removing the Authenticate middleware will allow the panel to be used for unauthenticated users. This will make the panels much more flexible and allow them to be used to build application experiences for unauthenticated users. My use case is to build a docs panel to ship as a plugin in a package.

[x] Changes have been thoroughly tested to not break existing functionality.
[ ] New functionality has been documented or existing documentation has been updated to reflect changes.
[ ] Visual changes are explained in the PR description using a screenshot/recording of before and after.

I like the idea of using Filament Panels for anything, so thumbs up from me:)


Create synchrotron-soleil

Add Synchrotron SOLEIL (synchrotron-soleil.fr)

@Aven678 First stage of verification passed, official domain for Synchrotron SOLEIL is synchrotron-soleil.fr as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@Aven678 I am sorry, this domain seems to represent a research center, not a specific single university or a college.
If you are a student there please enroll to GitHub Student Developer Program at https://education.github.com/discount_requests/application. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).
If employees of this Center need JetBrains tools, please let them know that they can request their licenses with 50% academic discount at<EMAIL_ADDRESS>I have to close this request without merging.
Thank you for your understanding!


Error deployment azure function

Hi,
since 1.66 version is not posible to deploy an azure function app. When I downgrade to 1.61 then is posible.
Thanks.

/duplicate


[Automation] Code update enhancement

Suggestions from @geissonator
1 . we should try to power off the system prior to update/ Since we don't know what the state other folks left it.
2.  Show user the success if it tries to update the system and found a same driver is installed. right now it fails which kinds of sends a wrong message that code update has failed. Will see what appropriate message and skipping we need to do at this front..

Code under review


etcd disaster recovery fails on a 8 host setup because of network partitioning

Rancher versions:
rancher/server:Upgrade from v1.6.6 to v1.6.7-rc1
**Docker version: (docker version,docker info preferred)**1.12.6
**Operating system and kernel: (cat /etc/os-release, uname -r preferred)**Ubuntu
**Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)**DO
**Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)**Single node
**Environment Template: (Cattle/Kubernetes/Swarm/Mesos)**Kubernetes
Steps to Reproduce:

Create a 8 host Kubernetes setup with etcd scale of 3 on v1.6.6
Create pods/rcs/services
Upgrade rancher to v1.6.7-rc1
Upgrade Network services, IPsec and Kubernetes stacks
Power down two hosts
etcd cluster is unhealthy
Perform disaster recovery by issuing the command "disaster" on the etcd which is the sole survivor. This is the etcd which is in running state

Results:
After disaster recovery, kubectl does not list any of the resources. The data is lost.
Kubernetes dashboard fails to launch with the error "Service unavailable"

Rootcause: https://github.com/rancher/rancher/issues/9418

The disaster recovery process itself wasn't designed to withstand a permanent network partition. When this happens, metadata is unreachable and cattle deletes/creates the container once the healthcheck initializing timeout (2 minutes) is reached. At this point, the other (new) members contain the lowest create index and assume the leadership role. One of those new members bootstraps a fresh cluster only if the DR container hasn't completed its objective.
The result is either complete data loss, or a split brain scenario where 2 different clusters are competing within the same service. Both are very bad scenarios.

Since the root cause is networking related  (#9418) and a fix has been put in place to address, can you please re-test to see if you hit this when testing #9418.

Tested using v1.6.7-rc7 with the latest fixes in rancher/net:v0.11.7. Disaster recovery cases succeeded and there was no data loss after recovery.


feat: support serialize and deserialize in PipelineHandler

Description
support serialize and deserialize in PipelineHandler
Modules

[ ] UI
[ ] Controller
[ ] Agent
[x] Client
[x] Python-SDK
[ ] Others

Checklist

[x] run code format and lint check
[x] add unit test
[ ] add necessary doc

#611


electrode schemas

@aeidi89 mentioned this (possibly interesting): https://www.biorxiv.org/content/10.1101/447995v1.full.pdf

seems like this paper is looking exclusively at how to track and analyze electrodes in slice histology
this might be approach-wise closer to tracks of biopsies

Nonetheless good to keep in mind. And of potential interest for the image service I guess.
Please see the next comment for the schema approach I could imagine to capture types/structures of electrophysiology electrodes.

Let me start with a couple of definitions / assumptions:

an electrode is considered to be a physical element (shaft, disk) that has at least one recording point/surface
a) an electrode should have an identifier
the recording point/surface of an electrode is called electrodeContact
an electrodeContact is defined by it's identifier, central coordinate point (coordinate) and shape
a) a coordinate of an electrodeContact is typically captured in a file
an electrode can be used independently as single electrode or be part of an electrodeArray
a) a multiple contact electrode should define it's inter-contact-distance
an electrodeArray is defined by wiring multiple electrodes together into one hardware system
a) an electrodeArray should have an identifier
b) an electrodeArray should define it's inter-electrode-distance

Now let me summarize the basic outline of electrode schemas based on these definitions / assumptions:

coordinate.schema.json
1.1) coordinate [expects: array of three number-items]
1.2) coordinateSpace [expects: object, ref to coordinateSpace.schema.json]

electrodeContact.schema.json
2.1) identifier [expects: string]
2.2) coordinate [expects: object, ref to coordinate.schema.json]
2.3) definedIn [expects: object, ref to fileInstance.schema.json]
2.4) type [expects: object, ref to electrodeContactType.schema.json]
2.5) relatedRecordings  [expects: object, ref to fileInstance.schema.json]
2.6) relatedStimulations  [expects: object, ref to fileInstance.schema.json]

electrode.schema.json
3.1) identifier [expects: string]
3.2) electrodeContact(s) [expects: array of objects, min: 1, ref to electrodeContact.schema.json]
3.3) interContactDistance [expects: number+unit]
3.4) type [expects: object, ref to electrodeType.schema.json]

electrodeArray.schema.json
4.1) identifier [expects: string]
4.2) electrode(s) [expects: array of objects, min: 1, ref to electrode.schema.json]
4.3) interElectrodeDistance [expects: number+unit]
4.4) type [expects: object, ref to electrodeArrayType.schema.json]

electrodeContactType.schema.json (this is not yet well defined)
5.1) semanticShape [expects: enum ("tip", "disk", "ring")]
5.2) numericShape [expects: enum of objects (tipShape.schema, diskShape.schema, ringShape.schema)]

electrodeType.schema.json (this is not yet well defined)
6.1) recordingType [expects: enum ("intracellular", "extracellular", "patch")]
6.2) semanticShape [expects: enum ("shaft", "disk")]
6.3) numericShape [expects: enum of objects (shaftShape.schema, diskShape.schema)]
6.4) manufacturer [expects: string]

electrodeArrayType.schema.json (this is not yet well defined)
7.1) type [expects: enum ("2D-electrode-array", "3D-electrode-array", "EEG-cap", "ECoG-array")]
7.2) manufacturer [expects: string]

@blixilla & @GMattheisen : what do you think about the suggested schemas as a start point?
[please make direct references to the schemas/properties you want to discuss by using the numbers in the lists]

@lzehl I think this is a good starting point. I think it makes sense to have this hierarchy with electrodeArray/electrodes/electrodeContacts.
I tried to play around and apply it to a rat use-case, the one with an EEG array (these are epidural electrodes, more precisely surgical implantation of a chronic array of 17 stainless steel electrodes covering most of the cortical areas of a rat brain);

and then some questions arose:
In general, would you say SANDS is intended to contain metadata necessary for visualization in the atlas viewer, or should it also contain other interesting metadata for the user (e.g. 6.4 manufacturer). What is covered by openMINDS? What is covered in your schemas, @GMattheisen?
2.3: would this be an image or imaging volume?
3.3: is this essential positioning information? if all the coordinates is already defined - will this be calculated automatically? do you perhaps have an example? :)
4.3: same comment as above + is this supposed full coordinate lists for electrodes within an array? How easy would it be to provide, and with what precision?
5.1: just curious, in what case would 'ring' apply? :)
5.2 and 6.3: is this physical dimensions of electrodes/electrodeContacts? Do these schema files exist somewhere? What kind of information do they contain?
6.1: What would it be for an intrusive epidural EEG electrode?
7.1: For this example we need an option appropriate for an array of intrusive EEG electrodes. EEG cap would maybe not fit that well, what do you think?
I hope these questions made sense, otherwise I would be happy to get a more thorough explanation of how this schemas would be used.

7.2, 6.4 Manufacturer (datatype: str) You may also want to allow for distributions. I have encountered numerous datasets where they array is a custom build and it is good to link out to the paper, pdf, or the like for a description.
We also discussed the possibility of a flag as a property of electrodecontactschema (2). I have seen data where channels are dropped or tagged if they recording quality is low or the recording lost before the end of the experiment. If the data user wanted to pull just the good recordings for analysis work/visualization, adding a tag would make for a great filter.

@blixilla thanks a lot for your comments. Here my feedback:
"In general, would you say SANDS is intended to contain metadata necessary for visualization in the atlas viewer, or should it also contain other interesting metadata for the user (e.g. 6.4 manufacturer). What is covered by openMINDS? What is covered in your schemas, @GMattheisen?"

for now SANDS should focus on how to provide metadata necessary for the atlas viewer
SANDS schemas should on the long run be extended with in-depth metadata that are of interest (so, for now, we could leave out manufacturer in 6 "electrodeType" & 7 "electrodeArrayType")
so far purchasable hardware devices are not captured as schemas in openMINDS (6 & 7 are a workaround for this)

a general schema for hardware devices could be interesting, possible properties (example: Utah Array):

manufacturer (Blackrock Microsystems)
name (Utah Array)
description (xxx)
connector (Cereport)
type (microelectrode array)
array (link to electrodeArray schema)

@GMattheisen: is any of this already captured in one of the in-depth schemas? maybe in neuroshapes?
2.3: would this be an image or imaging volume?

electrodeContact would be defined by a coordinate not an image
therefore the fileInstance would most likely point to a CSV, TSV, JSON, that stored that coordinate point, example:

tabular file with contact ID, x, y, z, unit as header

3.3: is this essential positioning information? if all the coordinates is already defined - will this be calculated automatically? do you perhaps have an example? :)

this is a good question, because in case we are in the native coordinateSpace of the electrode (meaning patient space) this could indeed be calculated
we could get coordinates of electrodeContacts that are alread transformed into a common space, here the calculation of the inter-contact-distance will be most likely erroneous, because usually the spatial relation between contacts gets lost in the transformation process
therefore I thought it might be good capturing it in any case
we could leave it out for now, because I'm not sure if it helps the visualization

4.3: same comment as above + is this supposed full coordinate lists for electrodes within an array? How easy would it be to provide, and with what precision?

see above (should be the same)

5.1: just curious, in what case would 'ring' apply? :)

out of my head I have two examples:

deep brain stimulation (DBS) electrode (one shaft-electrode with typically 3-4 contact rings)
stereotactic EEG electrode (one shaft-electrode with typically 10 - 20 contact rings)

5.2 and 6.3: is this physical dimensions of electrodes/electrodeContacts? Do these schema files exist somewhere? What kind of information do they contain?

yes, it would be the physical dimension of an  electrode/electrodeContact
no, these schemas do not yet exist (@GMattheisen: or do you have them in the in-depth metadata defined somewhere?
I would imagine something simple for each semantic shape, such as:

tipShape.schema properties:

length (value+unit)
diameterTip (value+unit)
diameterBase (value+unit)

diskShape.schema properties:

diameterMax (value+unit)
diameterMin (value+unit)
height (value+unit) [might be, in principle, 0 in some cases]

ringShape.schema properties:

diameterMax (value+unit)
diameterMin (value+unit)
width (value+unit)

shaftShape.schema properties:

length (value+unit)
diameterTip (value+unit)
diameterBase (value+unit)

6.1: What would it be for an intrusive epidural EEG electrode?

should be extracellular (as far as I know there is no further distinction of extracellular, except for the type of the recorded signal, e.g. MUA, LFP, EEG)

7.1: For this example we need an option appropriate for an array of intrusive EEG electrodes. EEG cap would maybe not fit that well, what do you think?

yes, the list I posted might need more extensions, although we need to be careful with the definitions

ECoG array would possibly fit your needs already

question is if we should specify the overall location of the electrodes somewhere (e.g., epidural, subdural, intracranial, extracranial, etc.)

@lzehl Sounds good to focus on viewer integration 👍 Thanks for all the thorough explanations :)
a few comments:
2.3: Ah, of course. For many of the rodent cases there are only very few coordinate pairs, so I was thinking we would write them directly in the JSON. Yes, I was thinking that the fileInstance could be directed to an annotated image.
3.3 and 4.3: I see, yes, I guess we can leave it out for now.
5.1: thanks :)
5.2 and 6.3: Sounds good.
6.1: yes, makes sense.
7.1: yes, could be nice to discuss this detail in a later meeting.
and lastly: Have you tried to set up an example JSON for a (real) human case, yet? Would it be possible to do this at this point, do you think?

:slightly_smiling_face: you're welcome!
for 2.3: I was originally thinking that electrode coordinates should be always saved in a separate file, but I agree that this might be inconvenient in some cases. So linking to an image as source as well could simplify this. On the other hand we need to rethink this a bit what it means for the rest of the model... specifically the annotation.schema.json and the image.schema.json. I think in such cases where the coordinate comes from an annotated image it should be covered as annotation.
for 7.1: I would say let's start with the easy cases and then gradually extent the list.
To lastly: I suggest that I write down the code for these schemas and then get in touch with you for creating examples early next week?

Cool, that sounds like a good plan :)

Decisions made for the electrode schemas (present: @UlrikeS91 ,  @aeidi89 , @blixilla , @lzehl ):

leave out manufacturer property for now (push it to in-depth part of the schemas)
do now go into detail about the Types (can be resolved/discussed also later and is not needed for a first working version of the schemas for atlas viewer purposes)
implement first version of schemas in elements asap (@lzehl)

Hi, nice progress on electrodes! I wonder if you have considered injection electrodes used for tract-tracing experiments? I guess all your already defined metadata will fit well and some additional ones specific for this type could be added, like electrode entry point, depth and injection volume ?

@Majpuc I think the injection volume would belong to the in-depth metadata. Depth seems like it belongs in SANDS, as this is definitely spatial information, but perhaps that information is already available in the coordinates, or can be calculated from the coordinates and the position of the cortical surface in the atlas?

Yes, a valid point. If both the coordinates of the entry point of the electrode and the contact point (the tip) are recorded, this can be calculated. Thanks!

@apdavison I agree with you on the injection volume. The depth however is is tricky to calculate at the moment. The way it is planned at the moment, we won't capture the entry point of the electrode, only the contact point of the tip in the brain. Given that electrodes can be inserted with an angle (on purpose or by accident), the distance to the cortex surface would only be an estimation of the depth. It will give some information, but I don't think it's as exact as @Majpuc is looking for, right?
@apdavison How important do you think this information is for ephy electrodes? Do you think it's crucial for a 1st version of the electrode schema or rather additional information that would be nice to have but isn't that crucial?
I think for injection electrodes this is very important, since injections tend to spread around the tip and along the entire tract of the electrode. For tract tracing experiments, this would be crucial information. Transfection could have taken place at any of those areas then which can have a big impact on the results/findings.
@lzehl Do we want to include an entry point coordinate already for ephy electrodes (e.g. as optional property)?

@UlrikeS91 Depth is critical, as it tells you which layer (and hence which possible cell types) you are recording/stimulating in. It is often measured precisely using histology, so probably it would be best to have a field for it even if it could in principle be calculated.

@UlrikeS91 Depth is critical, as it tells you which layer (and hence which possible cell types) you are recording/stimulating in. It is often measured precisely using histology, so probably it would be best to have a field for it even if it could in principle be calculated.

Thanks for the info, Andrew. I assume that Lyuba will respond herself later too, but if not, I'll point this out to her in our next meeting.

@Majpuc glad you like the basic layout of the electrode schemas :slightly_smiling_face: I would assume that capturing metadata for tract-tracing of injection electrodes would be an extension to the current set of schemas. I currently would aim for that tract-tracing as performed in the paper mentioned at the top of this issue, would be captured in the annotation.schema.json (which would need a revision then) or as it's own schema (e.g., tractTrace.schema.json) which could be attached to the electrode.schema.json. Or one could add indeed a schema for the injection point of the electrode (penetrationPoint.schema) and assume that the trace is the linear connection between the coordinate stated in the electrodeContact and the penetrationPoint.
Any preferences, feedback are appreciated for this :slightly_smiling_face:
@apdavison : what do you think? Would this be a simple extension to SANDS which would be compatible to the in-depth metadata?
@apdavison considering depth: I was thinking of defining shape schemas for electrodes and contacts which should then also include the length of an electrode (cf comments above). If you think this would be beneficial for SANDS, it would be great to get help / feedback here. I left it out for now, because it is not so relevant for the EBRAINS atlas viewer team (they currently mainly need the electrodeContact coordinate for the data that can define this, e.g. sEEG data).

@lzehl Thanks for considering this. I don't have any strong preference but it seems that having a (penetrationPoint.schema) might be useful for all electrodes. I'll let you decide :)

@lzehl I think we can close this issue, right?

Leave this one open for now. I want to hear back from @apdavison first and verify again if we have a good fit with in-depth extensions.

@lzehl I think we need to separate electrode and electrode-placement. The length of an electrode doesn't necessarily tell you the depth(s) of the recording point(s). For single electrodes and for small arrays such as tetrodes, the penetration depth is adjusted in order to find good cells, while for electrode arrays I guess the local curvature of the surface could affect the penetration depth of individual electrodes in the array (not sure if this latter point is significant).
Concerning good fit with in-depth extensions, don't worry too much about that, as we will revise the extensions to fit with whatever is decided for openMINDS core and SANDS.

@apdavison I agree with you. The implemented openMINDS_SANDS schemas focus now purely on the device (hierarchy) and an already identified coordinate point for the electrode contact. The process of getting to this coordinate point is not necessarily provided / described in openMINDS.
I think right now the openMINDS_SANDS schemas could be easily extended with more "pure" device information (length, shape, impedance, type, etc.). Some of those could be already optional properties in SANDS (maybe the ones that might be useful for visualization in the atlas viewer, or the general context [type, e.g. "linear electrode array"]) but I think most of it should/could be tier 3.
I'm closing this issue for now. We can get back to it in a new issue, if we need to further discuss extensions for the currently implemented electrode schemas in SANDS


Fixfix group_concat order bug and support more signatures.

Proposed changes
Issue Number: close #xxx
Problem summary
fix group_concat order bug and support more signatures.
now the function not only support varchar but also char, string.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[x] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[x] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 36.27 seconds
load time: 500 seconds
storage size:<PHONE_NUMBER>7 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230118155053_clickbench_pr_83583.html

duplicate with #16081


Training ResNet_50v1.5 on ImageNet

Using SGD to train ResNet
Implement cross-entropy Loss
Adding Transforms
Should reach the desired accuracy within 50 epochs in theory ( Implementation details - https://github.com/NVIDIA/DeepLearningExamples/tree/master/PyTorch/Classification/ConvNets/resnet50v1.5 )
SGD doesn't have weight decay???

Bounty locked, good luck!

If you set GPU=1 it should train on gpu

I'm using Ubuntu right now on an Intel i5

Do you have a dedicated gpu or are you just running off of the i5 igpu?

I do have a dedicated Nvidia GPU

You can try with CUDA=1 or TRITON=1 but I'm pretty sure triton is broke rn: #855

Training on a relatively smaller dataset with a batch size of 8 (due to memory constraints), should be reproducible by CUDA=1 python3 ./examples/mlperf/model_train.

No update in a week


[composer] sidebar tree is incomplete

See screenshot, after reloading this morning I lost all my content in composer and after a while some of it started to appear again (some spaces in shared spaces) but not all of them. I also see "personal space" header duplicated.

I think @wittjosiah fixed this

@zhenyasav please confirm that you can now load Composer again and everything looks ok!

closing this.


Missing attributes for Real Estate

When creating a new ad for the Real Estate section, many options are unaccounted for, including:

Appliances
Personal outdoor space
Building amenities
Utilities included
All virtual options

And likely others. Additionally, many of the ones that are accounted for haven't been assigned human-readable attribute names, resulting in blanks when generating an ad:
Choose most relevant category relating to "". [To skip, enter 'skip'] [To restart, enter 0]:
Both issues are easily fixed by adding the missing items to kijiji_categories_attrs.json.

Honestly, real estate should just use their own platform and stop putting junk on Kijiji...

Honestly, real estate should just use their own platform and stop putting junk on Kijiji...


Meteor 1.3 / Scss compiler error

Hi all,
I'm trying to use Motion UI with Meteor but it seems like there's an issue with the mixins.
Any idea? Thanks.
@import '{zurb:motion-ui}/src/motion-ui';
@include motion-ui-transitions;
@include motion-ui-animations;

=> Errors prevented startup:

   While processing files with fourseven:scss (for target web.browser):
   /client/main.scss: Scss compiler error: no mixin named motion-ui-transitions

   Backtrace:
   {}/client/main.scss:5

=> Your application has errors. Waiting for file change.

I had the same error. Solved it by doing this:

(this may be optional) :

npm install core-js
npm install
meteor npm install

meteor add zurb:motion-ui
meteor

I'm experiencing the same error. Tried @soriyath 's solution but without luck. Any other solutions? @nska02 did you get it to work?


[KYUUBI #2085] Add a labeler github action to triage PRs

Why are the changes needed?

to close #2085
How was this patch tested?
A series of local tests ran on my forked repo.

https://github.com/cfmcgrady/incubator-kyuubi/pull/8
https://github.com/cfmcgrady/incubator-kyuubi/pull/9
https://github.com/cfmcgrady/incubator-kyuubi/pull/10

Help check that these labels are set up reasonably. @yaooqinn @pan3793

thanks, merged to master


README ToC: add one

I want the README to stay easy to use, even as we add more to it.
I propose we add a Table of Contents, using some tool to keep it updated.
What do you say?

ToC
Shorter headings
more focused sections

Go ahead.

On 24 Nov 2016, at 18:05, Olle Jonsson<EMAIL_ADDRESS>wrote:
I want the README to stay easy to use, even as we add more to it.
I propose we add a Table of Contents, using some tool to keep it updated.
What do you say?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Example rendered output here:
https://github.com/olleolleolle/hutch/blob/86cd99e21502f6dee5cb60970b6fc9b9882338a1/README.md


fix:  restrict the module query being shown in Inputs autocomplete area

Description
restrict the module query being shown in Inputs autocomplete area
PR fixes following issue(s)
Fixes # (issue number)

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

Summary by CodeRabbit

New Features

Enhanced autocomplete capabilities within the code editor for a smoother user experience.

Refactor

Streamlined autocomplete logic for better maintainability and performance.

Style

Adjusted input text control to accommodate new autocomplete features.

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>


OpenTurbine-Specific Input Definition

Must work with WindIO format: https://windio.readthedocs.io/en/latest/
Will include how to discretize the turbine (defined in the WindIO file), and runtime parameters.

No progress to report.


OMIM 613735 mapping

Mondo term (ID and Label):
MONDO:0013396   chromosome 1p32-p31 deletion syndrome
Xref that should be fixed (ID and label):
https://omim.org/entry/613735
OMIM's preferred name for this is on MONDO:0100478 (brain malformations with or without urinary tract defects)
the "included' OMIM concept is CHROMOSOME 1p32-p31 DELETION SYNDROME
Your nano-attribution (ORCID)
If you don't have an ORCID, you can sign up for one here
Other comments:

Thanks @kanems
I changed the annotation to OMIM on MONDO:0013396 chromosome 1p32-p31 deletion syndrome, we are now using MONDO:includedEntryInOMIM on 'included' entries.
I added OMIM:613735 as an exact xref on brain malformations with or without urinary tract defects, this term was previously requested by ClinGen.


Modify Startup Output

Following discussion in issue #2458 I have implemented a change to how sites are output to this
Each port has been grouped.
Activating privacy features... done.

Serving HTTP on port:444
http://localhost:444

Serving HTTP on port:80
http://curlyparsley.kinchik.ie
http://
http://salmon.kinchik.ie
http://pepper.kinchik.ie
http://courgette.kinchik.ie
http://splitpeas.kinchik.ie/path
http://ripefig.kinchik.ie
http://<IP_ADDRESS>

Serving HTTPS on port:443
https://pie.kinchik.toflidium.com

Serving HTTP on port:2015
http://fig.kinchik.ie:2015

Serving HTTP on port:4467
http://localhost:4467

Serving HTTP on port:1667
http://<IP_ADDRESS>:1667
http://localhost:1667

When caddy is set to log to stdout you also still get the log entries.  I need some help to fix thils.
Activating privacy features... done.
Serving HTTP on port:1234
http://<IP_ADDRESS>:1234
2019/02/17 22:09:23 http://<IP_ADDRESS>:1234

Serving HTTP on port:1667
http://<IP_ADDRESS>:1667
2019/02/17 22:09:23 http://<IP_ADDRESS>:1667
http://localhost:1667
2019/02/17 22:09:23 http://localhost:1667

Serving HTTP on port:444
http://localhost:444
2019/02/17 22:09:23 http://localhost:444

Serving HTTP on port:80
http://curlyparsley.kinchik.ie
2019/02/17 22:09:23 http://curlyparsley.kinchik.ie
http://
2019/02/17 22:09:23 http://
http://salmon.kinchik.ie
2019/02/17 22:09:23 http://salmon.kinchik.ie
http://pepper.kinchik.ie
2019/02/17 22:09:23 http://pepper.kinchik.ie
http://courgette.kinchik.ie
2019/02/17 22:09:23 http://courgette.kinchik.ie
http://splitpeas.kinchik.ie/path
2019/02/17 22:09:23 http://splitpeas.kinchik.ie/path
http://ripefig.kinchik.ie
2019/02/17 22:09:23 http://ripefig.kinchik.ie
http://<IP_ADDRESS>
2019/02/17 22:09:23 http://<IP_ADDRESS>

Serving HTTPS on port:443
https://pie.kinchik.toflidium.com
2019/02/17 22:09:23 https://pie.kinchik.toflidium.com

Serving HTTP on port:2015
http://fig.kinchik.ie:2015
2019/02/17 22:09:23 http://fig.kinchik.ie:2015

Does anyone know how I get access to the logger struct from here https://github.com/mholt/caddy/blob/master/caddyhttp/httpserver/server.go#L519

I don't even know if you can figure out via the logging struct that it was set to stdout. Might need a way to make the logfile flag from run.go available to the OnStartupComplete function? Maybe put it next to caddy.Quiet in caddy.go?

Pushed an update which simplifies hugely.
Turns out that there is a call to OnStartupComplete for every Server (eg port) that is started, so all sites in each call are grouped anyway.  It does make trying to pull out the calls to log in a seperate block much more complicated.
I have made change as requested by @mholt, though code is now very different.
If @mholt or someone else could tell me how I can access the logger struct from this code, I would be able to read the Output value in that struct which will be set to 'stdout' and if it is I could simply not call log.Println

I think you might've misunderstood what @mholt said. He was saying this improved output makes sense for the stdout, but for the logged stuff, it should maybe stay the same (because it doesn't need to be grouped for user-friendliness as much in the actual logs)

No I understood what he meant, but the problem is the grouping happens at the moment we just dont hightlight it.
With this pr and caddy -log stdout you will get
Activating privacy features... done.

Serving HTTP on port 80
http://curlyparsley.kinchik.ie
2019/02/18 22:06:29 http://curlyparsley.kinchik.ie
http://
2019/02/18 22:06:29 http://
http://salmon.kinchik.ie
2019/02/18 22:06:29 http://salmon.kinchik.ie
http://pepper.kinchik.ie
2019/02/18 22:06:29 http://pepper.kinchik.ie
http://courgette.kinchik.ie
2019/02/18 22:06:29 http://courgette.kinchik.ie
http://splitpeas.kinchik.ie/path
2019/02/18 22:06:29 http://splitpeas.kinchik.ie/path
http://basil.kinchik.ie
2019/02/18 22:06:29 http://basil.kinchik.ie
http://walnutoil.kinchik.ie
2019/02/18 22:06:29 http://walnutoil.kinchik.ie
http://soup.kinchik.toflidium.com
2019/02/18 22:06:29 http://soup.kinchik.toflidium.com
http://chard.kinchik.ie
2019/02/18 22:06:29 http://chard.kinchik.ie
http://<IP_ADDRESS>
2019/02/18 22:06:29 http://<IP_ADDRESS>
http://onion.kinchik.ie
2019/02/18 22:06:29 http://onion.kinchik.ie
http://peas.kinchik.ie
2019/02/18 22:06:29 http://peas.kinchik.ie
http://ripefig.kinchik.ie
2019/02/18 22:06:29 http://ripefig.kinchik.ie
http://<IP_ADDRESS>
2019/02/18 22:06:29 http://<IP_ADDRESS>

Serving HTTPS on port 443
https://pie.kinchik.toflidium.com
2019/02/18 22:06:29 https://pie.kinchik.toflidium.com

Serving HTTP on port 2015
http://fig.kinchik.ie:2015
2019/02/18 22:06:29 http://fig.kinchik.ie:2015

with caddy -log c:\mylogfile.txt
Activating privacy features... done.

Serving HTTPS on port 443
https://pie.kinchik.toflidium.com

Serving HTTP on port 2015
http://fig.kinchik.ie:2015

Serving HTTP on port 80
http://curlyparsley.kinchik.ie
http://
http://salmon.kinchik.ie
http://pepper.kinchik.ie
http://courgette.kinchik.ie
http://splitpeas.kinchik.ie/path
http://basil.kinchik.ie
http://walnutoil.kinchik.ie
http://soup.kinchik.toflidium.com
http://chard.kinchik.ie
http://<IP_ADDRESS>
http://onion.kinchik.ie
http://peas.kinchik.ie
http://ripefig.kinchik.ie
http://<IP_ADDRESS>

and mylogfile.txt is
2019/02/18 22:07:42 https://pie.kinchik.toflidium.com
2019/02/18 22:07:42 http://fig.kinchik.ie:2015
2019/02/18 22:07:42 http://curlyparsley.kinchik.ie
2019/02/18 22:07:42 http://
2019/02/18 22:07:42 http://salmon.kinchik.ie
2019/02/18 22:07:42 http://pepper.kinchik.ie
2019/02/18 22:07:42 http://courgette.kinchik.ie
2019/02/18 22:07:42 http://splitpeas.kinchik.ie/path
2019/02/18 22:07:43 http://basil.kinchik.ie
2019/02/18 22:07:43 http://walnutoil.kinchik.ie
2019/02/18 22:07:43 http://soup.kinchik.toflidium.com
2019/02/18 22:07:43 http://chard.kinchik.ie
2019/02/18 22:07:43 http://<IP_ADDRESS>
2019/02/18 22:07:43 http://onion.kinchik.ie
2019/02/18 22:07:43 http://peas.kinchik.ie
2019/02/18 22:07:43 http://ripefig.kinchik.ie
2019/02/18 22:07:43 http://<IP_ADDRESS>

However to remove the log lines from in between the fmt lines when caddy -log stdout is non trival because of when OnStartupComplete is called.  However if i can get access to logger.Output I can check if we are wriing log to stdout and output less

Hugely simplified is right, 11 lines is very cool and the -log output being regular is great. It's a nice neat looking change.
Only thing left on the wishlist is the check for -log stdout, and maybe what @mholt said in his review:

Perhaps we should rethink how we log this instead. Maybe like what we had before, but instead, it'd look something like [INFO] Serving %s (site address)

Is that a change that merits being made right here or do we want to leave the log output alone entirely for the time being?

After suggestion about fixing #2473 I rearranged the code so that caddy.Quiet only surpresses the call to fmt.Println .  I kept the OutputSiteInfo function but use if for a different purpose.
The output is now like this, which I think is good.  I could go one step further and surpress calls to log.Println if log.Output == stdout if people think it is ok to add logDestination to caddy struct
Output
Activating privacy features... done.

Serving HTTP on port 80
http://curlyparsley.kinchik.ie
http://
http://salmon.kinchik.ie
http://pepper.kinchik.ie
http://courgette.kinchik.ie
http://splitpeas.kinchik.ie/path
http://basil.kinchik.ie
http://walnutoil.kinchik.ie
http://soup.kinchik.toflidium.com
http://chard.kinchik.ie
http://<IP_ADDRESS>
http://onion.kinchik.ie
http://peas.kinchik.ie
http://ripefig.kinchik.ie
http://<IP_ADDRESS>

2019/02/20 08:15:17 http://curlyparsley.kinchik.ie
2019/02/20 08:15:17 http://
2019/02/20 08:15:17 http://salmon.kinchik.ie
2019/02/20 08:15:17 http://pepper.kinchik.ie
2019/02/20 08:15:17 http://courgette.kinchik.ie
2019/02/20 08:15:17 http://splitpeas.kinchik.ie/path
2019/02/20 08:15:17 http://basil.kinchik.ie
2019/02/20 08:15:17 http://walnutoil.kinchik.ie
2019/02/20 08:15:17 http://soup.kinchik.toflidium.com
2019/02/20 08:15:17 http://chard.kinchik.ie
2019/02/20 08:15:17 http://<IP_ADDRESS>
2019/02/20 08:15:17 http://onion.kinchik.ie
2019/02/20 08:15:17 http://peas.kinchik.ie
2019/02/20 08:15:17 http://ripefig.kinchik.ie
2019/02/20 08:15:17 http://<IP_ADDRESS>

Serving HTTPS on port 443
https://pie.kinchik.toflidium.com

2019/02/20 08:15:17 https://pie.kinchik.toflidium.com

Serving HTTP on port 2015
http://fig.kinchik.ie:2015

2019/02/20 08:15:17 http://fig.kinchik.ie:2015

I don't see any reason we couldn't make the log destination part of the caddy struct so we can check it here, but I'd defer that to @mholt...

Added caddy.LogDestination so that log output is conditional.
Log output to file now
2019/02/21 21:04:05 [INFO] Serving https://pie.kinchik.toflidium.com
2019/02/21 21:04:05 [INFO] Serving http://fig.kinchik.ie:2015
2019/02/21 21:04:05 [INFO] Serving http://curlyparsley.kinchik.ie
2019/02/21 21:04:05 [INFO] Serving http://
2019/02/21 21:04:05 [INFO] Serving http://salmon.kinchik.ie
2019/02/21 21:04:05 [INFO] Serving http://pepper.kinchik.ie
2019/02/21 21:04:05 [INFO] Serving http://courgette.kinchik.ie
2019/02/21 21:04:05 [INFO] Serving http://splitpeas.kinchik.ie/path
2019/02/21 21:04:05 [INFO] Serving http://basil.kinchik.ie
2019/02/21 21:04:05 [INFO] Serving http://walnutoil.kinchik.ie
2019/02/21 21:04:05 [INFO] Serving http://soup.kinchik.toflidium.com
2019/02/21 21:04:05 [INFO] Serving http://chard.kinchik.ie
2019/02/21 21:04:05 [INFO] Serving http://<IP_ADDRESS>
2019/02/21 21:04:05 [INFO] Serving http://onion.kinchik.ie
2019/02/21 21:04:05 [INFO] Serving http://peas.kinchik.ie
2019/02/21 21:04:05 [INFO] Serving http://ripefig.kinchik.ie
2019/02/21 21:04:05 [INFO] Serving http://<IP_ADDRESS>

Log output is surpressed if set to stdout
I tried with grouping, could look like this.  Interested in what people think
''''
2019/02/21 21:02:46 [INFO] Serving HTTP on port 80
2019/02/21 21:02:46 [INFO] Serving http://curlyparsley.kinchik.ie
2019/02/21 21:02:46 [INFO] Serving http://
2019/02/21 21:02:46 [INFO] Serving http://salmon.kinchik.ie
2019/02/21 21:02:46 [INFO] Serving http://pepper.kinchik.ie
2019/02/21 21:02:46 [INFO] Serving http://courgette.kinchik.ie
2019/02/21 21:02:46 [INFO] Serving http://splitpeas.kinchik.ie/path
2019/02/21 21:02:46 [INFO] Serving http://basil.kinchik.ie
2019/02/21 21:02:46 [INFO] Serving http://walnutoil.kinchik.ie
2019/02/21 21:02:46 [INFO] Serving http://soup.kinchik.toflidium.com
2019/02/21 21:02:46 [INFO] Serving http://chard.kinchik.ie
2019/02/21 21:02:46 [INFO] Serving http://<IP_ADDRESS>
2019/02/21 21:02:46 [INFO] Serving http://onion.kinchik.ie
2019/02/21 21:02:46 [INFO] Serving http://peas.kinchik.ie
2019/02/21 21:02:46 [INFO] Serving http://ripefig.kinchik.ie
2019/02/21 21:02:46 [INFO] Serving http://<IP_ADDRESS>
2019/02/21 21:02:46 [INFO] Serving HTTPS on port 443
2019/02/21 21:02:46 [INFO] Serving https://pie.kinchik.toflidium.com
2019/02/21 21:02:46 [INFO] Serving HTTP on port 2015
2019/02/21 21:02:46 [INFO] Serving http://fig.kinchik.ie:2015

I have made those 2 updates now.

@mholt Sorry about that.  I just thought the comments had been dealt with.  I'll answer your comments inline.  We can rollback or I'll submit another PR

Looking at @mholt comments I think it best if this change goes back to formatting like this
Activating privacy features... done.

Serving HTTP on port 80
http://curlyparsley.kinchik.ie
http://
http://salmon.kinchik.ie
http://pepper.kinchik.ie
http://courgette.kinchik.ie
http://splitpeas.kinchik.ie/path
http://basil.kinchik.ie
http://walnutoil.kinchik.ie
http://soup.kinchik.toflidium.com
http://chard.kinchik.ie
http://<IP_ADDRESS>
http://onion.kinchik.ie
http://peas.kinchik.ie
http://ripefig.kinchik.ie
http://<IP_ADDRESS>

2019/02/20 08:15:17 http://curlyparsley.kinchik.ie
2019/02/20 08:15:17 http://
2019/02/20 08:15:17 http://salmon.kinchik.ie
2019/02/20 08:15:17 http://pepper.kinchik.ie
2019/02/20 08:15:17 http://courgette.kinchik.ie
2019/02/20 08:15:17 http://splitpeas.kinchik.ie/path
2019/02/20 08:15:17 http://basil.kinchik.ie
2019/02/20 08:15:17 http://walnutoil.kinchik.ie
2019/02/20 08:15:17 http://soup.kinchik.toflidium.com
2019/02/20 08:15:17 http://chard.kinchik.ie
2019/02/20 08:15:17 http://<IP_ADDRESS>
2019/02/20 08:15:17 http://onion.kinchik.ie
2019/02/20 08:15:17 http://peas.kinchik.ie
2019/02/20 08:15:17 http://ripefig.kinchik.ie
2019/02/20 08:15:17 http://<IP_ADDRESS>

Serving HTTPS on port 443
https://pie.kinchik.toflidium.com

2019/02/20 08:15:17 https://pie.kinchik.toflidium.com

Serving HTTP on port 2015
http://fig.kinchik.ie:2015

2019/02/20 08:15:17 http://fig.kinchik.ie:2015

This does not require caddy.LogDestination . I agree that the duplication is really not an issue.  We'll wait till Matt has finished his thesis to continue this PR


Sample data for dashboard APIs

Do you think it would be a good idea to add a second user petition? Definitely won't be the case for all users, but something that needs to be handled.

I also have a question related to the user having multiple petitions. In the current version, when you go to http://petitions.moveon.org/dashboard.html, one of your petitions is displayed, even if you have multiple. (there's also a dropdown to switch)
How do we decide which to display by default? Can we just use the first returned by /user/petitions?

Yes, they are sorted by timestamp (descending) so the most recent one will always be first.  I can add another petition or two, to demo multiple petitions in that list.
We debated whether to have an endpoint like, say, /user/petitions/latest.json that only gave you details on the latest petition, and then require frontend to do a second call to /user/petitions.json for the other petitions in the dropdown... but figured it's probably eaiser to just return a bunch and display the first (plus, the others can get cached by the client)
However I'm open to changing this around if something else is easier for you.


Adding rdbms-connect fails in Azure CLI version 2.54.0

Describe the bug
Adding the extension rdbms-connect fails in an Azure CLI task in a release pipeline.
Related command
az extension add --name rdbms-connect --version 1.0.3
Errors
2023-11-21T09:19:22.5964957Z ERROR: cli.azure.cli.core.azclierror: An error occurred. Pip failed with status code 1. Use --debug for more information.
2023-11-21T09:19:22.5966400Z ERROR: az_command_data_logger: An error occurred. Pip failed with status code 1. Use --debug for more information.

Issue script & Debug output
2023-11-21T09:19:22.5900051Z Building wheels for collected packages: setproctitle
2023-11-21T09:19:22.5900776Z   Created temporary directory: C:\Users\VssAdministrator\AppData\Local\Temp\pip-wheel-_r4cueft
2023-11-21T09:19:22.5901647Z   Destination directory: C:\Users\VssAdministrator\AppData\Local\Temp\pip-wheel-_r4cueft
2023-11-21T09:19:22.5902353Z   Building wheel for setproctitle (pyproject.toml): started
2023-11-21T09:19:22.5903296Z   Running command Building wheel for setproctitle (pyproject.toml)
2023-11-21T09:19:22.5903768Z   running bdist_wheel
2023-11-21T09:19:22.5904006Z   running build
2023-11-21T09:19:22.5904223Z   running build_ext
2023-11-21T09:19:22.5904452Z   building 'setproctitle' extension
2023-11-21T09:19:22.5904764Z   creating build
2023-11-21T09:19:22.5905017Z   creating build\temp.win-amd64-cpython-311
2023-11-21T09:19:22.5905430Z   creating build\temp.win-amd64-cpython-311\Release
2023-11-21T09:19:22.5905892Z   creating build\temp.win-amd64-cpython-311\Release\src
2023-11-21T09:19:22.5911710Z   "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -DSPT_VERSION=1.2.3 "-IC:\Program Files\Microsoft SDKs\Azure\CLI2\include" "-IC:\Program Files\Microsoft SDKs\Azure\CLI2\Include" "-IC:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\ATLMFC\include" "-IC:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\include" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\cppwinrt" /Tcsrc/setproctitle.c /Fobuild\temp.win-amd64-cpython-311\Release\src/setproctitle.obj
2023-11-21T09:19:22.5917701Z   setproctitle.c
2023-11-21T09:19:22.5918946Z   C:\Users\VssAdministrator\AppData\Local\Temp\pip-install-o4_pqwpi\setproctitle_cd0f4ebe1aef4cdebbbdcb122e6f9a65\src\spt_python.h(15): fatal error C1083: Cannot open include file: 'Python.h': No such file or directory
2023-11-21T09:19:22.5921023Z   error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Enterprise\\VC\\Tools\\MSVC\\14.29.30133\\bin\\HostX86\\x64\\cl.exe' failed with exit code 2
2023-11-21T09:19:22.5922050Z   error: subprocess-exited-with-error
2023-11-21T09:19:22.5922376Z
2023-11-21T09:19:22.5922740Z   Building wheel for setproctitle (pyproject.toml) did not run successfully.
2023-11-21T09:19:22.5923279Z   exit code: 1
2023-11-21T09:19:22.5923610Z
2023-11-21T09:19:22.5923789Z   See above for output.
2023-11-21T09:19:22.5924025Z
2023-11-21T09:19:22.5924431Z   note: This error originates from a subprocess, and is likely not a problem with pip.
2023-11-21T09:19:22.5926170Z   full command: 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe' 'C:\Program Files\Microsoft SDKs\Azure\CLI2\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py' build_wheel 'C:\Users\VSSADM~1\AppData\Local\Temp\tmphjkyy0yp'
2023-11-21T09:19:22.5927973Z   cwd: C:\Users\VssAdministrator\AppData\Local\Temp\pip-install-o4_pqwpi\setproctitle_cd0f4ebe1aef4cdebbbdcb122e6f9a65
2023-11-21T09:19:22.5928900Z   Building wheel for setproctitle (pyproject.toml): finished with status 'error'
2023-11-21T09:19:22.5929476Z   ERROR: Failed building wheel for setproctitle
2023-11-21T09:19:22.5929840Z Failed to build setproctitle
2023-11-21T09:19:22.5930443Z ERROR: Could not build wheels for setproctitle, which is required to install pyproject.toml-based projects
2023-11-21T09:19:22.5931106Z Exception information:
2023-11-21T09:19:22.5931342Z Traceback (most recent call last):
2023-11-21T09:19:22.5932137Z   File "C:\Program Files\Microsoft SDKs\Azure\CLI2\Lib\site-packages\pip\_internal\cli\base_command.py", line 180, in exc_logging_wrapper
2023-11-21T09:19:22.5932961Z     status = run_func(*args)
2023-11-21T09:19:22.5933234Z              ^^^^^^^^^^^^^^^
2023-11-21T09:19:22.5933910Z   File "C:\Program Files\Microsoft SDKs\Azure\CLI2\Lib\site-packages\pip\_internal\cli\req_command.py", line 245, in wrapper
2023-11-21T09:19:22.5934672Z     return func(self, options, args)
2023-11-21T09:19:22.5934971Z            ^^^^^^^^^^^^^^^^^^^^^^^^^
2023-11-21T09:19:22.5935651Z   File "C:\Program Files\Microsoft SDKs\Azure\CLI2\Lib\site-packages\pip\_internal\commands\install.py", line 429, in run
2023-11-21T09:19:22.5936387Z     raise InstallationError(
2023-11-21T09:19:22.5937270Z pip._internal.exceptions.InstallationError: Could not build wheels for setproctitle, which is required to install pyproject.toml-based projects
2023-11-21T09:19:22.5938365Z Removed build tracker: 'C:\\Users\\VssAdministrator\\AppData\\Local\\Temp\\pip-build-tracker-xumup4t6'
2023-11-21T09:19:22.5938838Z
2023-11-21T09:19:22.5940795Z DEBUG: cli.azure.cli.core.extension.operations: Command '['C:\\Program Files\\Microsoft SDKs\\Azure\\CLI2\\python.exe', '-m', 'pip', 'install', '--target', 'C:\\Program Files\\Common Files\\AzureCliExtensionDirectory\\rdbms-connect', 'C:\\Users\\VSSADM~1\\AppData\\Local\\Temp\\tmpe66gnbk1\\rdbms_connect-1.0.3-py2.py3-none-any.whl', '-vv', '--disable-pip-version-check', '--no-cache-dir']' returned non-zero exit status 1.
2023-11-21T09:19:22.5943550Z DEBUG: cli.azure.cli.core.extension.operations: Pip failed so deleting anything we might have installed at C:\Program Files\Common Files\AzureCliExtensionDirectory\rdbms-connect
2023-11-21T09:19:22.5944844Z DEBUG: cli.azure.cli.core.azclierror: Traceback (most recent call last):
2023-11-21T09:19:22.5945922Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
2023-11-21T09:19:22.5947273Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
2023-11-21T09:19:22.5950355Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
2023-11-21T09:19:22.5954470Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
2023-11-21T09:19:22.5956037Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
2023-11-21T09:19:22.5957467Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
2023-11-21T09:19:22.5959088Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/extension/custom.py", line 16, in add_extension_cmd
2023-11-21T09:19:22.5960673Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/extension/operations.py", line 344, in add_extension
2023-11-21T09:19:22.5962440Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/extension/operations.py", line 173, in _add_whl_ext
2023-11-21T09:19:22.5963739Z knack.util.CLIError: An error occurred. Pip failed with status code 1. Use --debug for more information.
2023-11-21T09:19:22.5964326Z
2023-11-21T09:19:22.5964957Z ERROR: cli.azure.cli.core.azclierror: An error occurred. Pip failed with status code 1. Use --debug for more information.
2023-11-21T09:19:22.5966400Z ERROR: az_command_data_logger: An error occurred. Pip failed with status code 1. Use --debug for more information.

Expected behavior
Extension should add without fail.
Environment Summary
azure-cli                         2.54.0
core                              2.54.0
telemetry                          1.1.0

Extensions:
azure-devops                      0.26.0

Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2

Additional context
The command ran fine with Azure CLI version 2.53.1. The error seems the simillar to those described here:
#25869
#25067
However the workarounds provided either don't work (install setuptools) or were already present (specify version of rdbms-connect). Our hotfix was to install a previous version of Azure CLI before running any commands: python -m pip install azure-cli==2.50.0 (trying to install version 2.53.1 returned an error message that the newest available version was 2.50.0 for some reason?).
This is not something we would like to have in our pipeline obviously, also it increases the time it takes to run the pipeline by around 5 minutes.

Thank you for opening this issue, we will look into it.

The bundled Python is bumped to 3.11 in 2.54.0.
rdbms-connect 1.0.3 requires setproctitle (~=1.2.2), which does not provide a wheel for python 3.11.
I think it update the dependency to setproctitle==1.3.3.
I can't find a workaround for this.
@alanenriqueo for awareness. rdbms-connect does not work on Windows.

The bundled Python is bumped to 3.11 in 2.54.0. rdbms-connect 1.0.3 requires setproctitle (~=1.2.2), which does not provide a wheel for python 3.11. I think it should update the dependency to setproctitle~=1.3.3.
I can't find a workaround for this.
@alanenriqueo for awareness. rdbms-connect does not work on Windows.

Fix for this https://github.com/Azure/azure-cli-extensions/pull/7138, is currently blocked due to https://github.com/dbcli/mycli/issues/1139.

@ambrahma Is this still blocked as noted above? I'm experiencing the same issue with Azure CLI 2.59.0 (on Windows).

@ambrahma Is this still blocked as noted above? I'm experiencing the same issue with Azure CLI 2.59.0 (on Windows). I'm not specifying a version in the command.

My PR to fix this has been checked-in https://github.com/Azure/azure-cli-extensions/pull/7138, and will be releases as part of upcoming milestone

The issue is present in:
azure-cli                         2.61.0
core                              2.61.0
telemetry                          1.1.0
Dependencies:
msal                              1.28.0
azure-mgmt-resource               23.1.1
on macos

I guess I'm facing a related problem. Windows 11, az 2.62.0
az extension add --name azure-devops
An error occurred. Pip failed with status code 1. Use --debug for more information.


Add monitored-entity reconciler to logmodule reconciler

Description
DAQ-1397
Both KubernetesClusterMEID and KubernetesClusterName are a hard requirement for the deployment of the standalone logmodule.
So we add the monitoredentities.Reconciler to the logmodule reconcile, the ensure that we have it available.

If we still don't have the KubernetesClusterMEID and KubernetesClusterName then we log it and then end the logmodule reconcile early.

should we error instead of log?

How can this be tested?
Deploy a dynakube with logModule.enable: true in 2 scenarios:

When there is an ME on your tenant => everything should deploy fine (daemonset appears)
When there is NO ME on your tenant => should see in the logs that something is not good (daemonset does NOT appear)

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 75.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 64.42%. Comparing base (d86bdc4) to head (d757b9a).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

pkg/controllers/dynakube/logmodule/reconciler.go
75.00%
1 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3932   +/-   ##
=======================================
  Coverage   64.42%   64.42%
=======================================
  Files         381      381
  Lines       20616    20623    +7
=======================================
+ Hits        13281    13286    +5
- Misses       6044     6045    +1
- Partials     1291     1292    +1

Flag
Coverage Δ

unittests
64.42% <75.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@aorcholski I didn't to reproduce that, I get:
{"level":"info","ts":"2024-10-17T07:29:46.687Z","logger":"logmodule-daemonset","msg":"the status of the DynaKube is missing information about the kubernetes monitored-entity, skipping logmodule deployment"}

But yes the Phase of the DynaKube is Running, but that was semi intended. My question of should we error instead of log? is related to that. Will try to see what happens if we just error.


Adding error messages to Mongodb when an error occurs

Short description outlining key changes/additions
Adding error messages to Mongodb when an error occurs in processing csv during ValidationScheduler
JIRA Ticket Number
IDVA5-1628
Type of change

[ ] Bug fix
[x] New feature
[ ] Breaking change
[ ] Infrastructure change

Pull request checklist

[x] I have added unit tests for new code that I have added
[x] I have added/updated functional tests where appropriate
[ ] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: No security warnings found

CI: No security warnings found


Can we have a flag to disable image

Thanks for an amazing package.
It would be great if we can have a flag that makes the preview image hide.
Thanks

Hi, thanks! Sorry for the late response, was on vacation. Released in v2.2.0. hideImage param.

Awesome great