Changed "create" to "manage"

A user must have Create, Edit, and Delete permissions to access Manage Soft Credits. This change clarifies this point.
Critical Changes
Changes
Issues Closed
Fixes #3790
New Metadata
Deleted Metadata

Thanks for making this change @sam-knox. Looks great. Merging.

**lurch: attach W-029670

Tracking W-029670


[Enhancement] Open Property pane only on toggle

Summary
Open property pane only via the widget toggle(widget name) instead of opening it up on clicking on the widget/ resizing/ dragging.
Motivation
Property pane often comes in the way when the user wants to just move around widgets or resize them or interact with them which ends up into a bad UX.
Additional Context
When a new widget is added property pane is shown.

@marks0351 @areyabhishek can we do this along with the enter / double click feature? I don't think we should ship this without an easy way to open it. It might negatively impact new users

@areyabhishek I agree with @Nikhil-Nandagopal. thoughts?

Sounds good.

BTW, what's the ETA of this feature?

@Nikhil-Nandagopal @areyabhishek This was suppose to come out last week. I have hit a road block on this wrt to checkbox and radio buttons of blueprint which simulate multiple clicks which I am trying to figure out why.


V10 API Example - Infinite loop ?

import ReactFlow, {
  applyNodeChanges,
  applyEdgeChanges
} from 'react-flow-renderer';

const initialNodes = [
  { id: '1', data: { label: 'Node 1' }, position: { x: 250, y: 0 } },
  { id: '2', data: { label: 'Node 2' }, position: { x: 150, y: 100 } }
];

const initialEdges = [
  { id: 'e1-2', source: '1', target: '2' }
];

const BasicFlow = () => {
  const [nodes, setNodes] = useState(initialNodes);
  const [edges, setEdges] = useState(initialEdges);

  const onNodesChange = useCallback((changes) => setNodes((ns) => applyNodeChanges(changes, ns)), []);
  const onEdgesChange = useCallback((changes) => setEdges((es) => applyEdgeChanges(changes, es)), []);

  return (
    <ReactFlow
      nodes={nodes}
      edges={edges}
      onNodesChange={onNodesChange}
      onEdgesChange={onEdgesChange}
    />
  );
};

export default BasicFlow;

Using:
<EMAIL_ADDRESS>It appears that once
nodeTypes = { { } }
is added to the API example that, there is a pretty serious loop occuring ? am I missing something.  applyNodeChanges is triggering onNodesChange which is then calling the callback and on and on etc.

Good point. I will add it to the docs. We are not memoizing node types anymore. If your node types were dynamic you had to use a hacky API to update them in v9. In v10 it behaves like all other props too. You need to take care that you don't create a new nodeTypes object on every render. If you use useMemo or define the nodeTypes outside of the component this issue shouldn't occur.

I was just playing with this building a sandbox and I discovered the issue with memo ... I think we are good

It's not dumb at all ;) Maybe it is a bad idea to change the API but I think it's more consistent and also clear what can be expected.

I totally agree with the decision, albeit a difficult one, to adjust the API. The project benefits from consistency, a straightforward API and configurability. A number of the other alternative projects out there have carried forward a great deal of legacy which has resulted in convoluted messy API's as well as hard to identify bugs.
I am glad I delayed implementing, the work we had done with 9 was easily adapted to 10 and 10 is so far stable enough i can complete our more in depth integration.
Is there any way / value in contributing examples.  I have an example using mui dropdowns (they use portals for the menu popup which requires keeping the scale in sync) on custom nodes, it's basically an extension of the dynamic render based on scale example already provided.

Thanks @moklick I did search the issues the day before this issue was created, that's a real coincidence :p Anyway, just wanted to say that memoizing outside the function worked. I see the PR description has also been updated, cheers!


Prost integration

Is it possible to use Prost as RDDLSimAgent? Is there any documentation on how to do this?

In principle, yes -- Thomas Keller had originally written RDDLSimAgent to allow use of PROST with pyRDDLGym, which was updated by Christian Muise and others in January 2023.  But we lack documentation and testing of RDDLSimAgent given all of the changes to pyRDDLGym since that time... it has been on our TODO list for a while now.  If you or someone else is willing to test this out and provide documentation, we would gladly welcome your contribution!
===
However, if you're willing to work with the version of pyRDDLGym from January 2023, Christian Muise has provided a dockerized integration of PROST and pyRDDLGym that you can find documented here:

Section 3.1 of PyRDDLGym tutorial documentation

"Probabilistic Planning" section of Christian Muise's excellent CISC-813 course on Automated Planning

Christian has provided further helpful comments on his CISC-813 content as follows:

The Dockerfile we use, which simply brings together both pyRDDLGym and the PROST planner in the same environment along with our scripts.

The command used to run the pyRDDLGym server.  The time parameter is not redirected to PROST, but rather passed on to the RDDLSimAgent (since all details of time limits in previous competitions were provided by the Competition Server to the Client agent) -- this line in RDDLSimAgent shows where the time parameter is used.

The bash script that ties things together. Lines 34 on show how (1) the pyrddl service is invoked; (2) PROST is fired up with the suggested settings (chosen for simplicity and not necessarily top performance); and (3) how the logging details are piped to a file.

Docker files and instructions have been added yesterday to pyrddlgym (per the pull request above).
Please find the instructions how to set up PROST: here
Please note, this is still beta and not extensively tested yet on various machines etc. If you are still in need of running prost, please feel free to give this a shot and let us know in case something is broken.


Windows service 'run_as_user' param does not work and clobbers existing permissions

The changes made in be28ba9 introduced support for running a windows service as a specific user by passing 'run_as_user' and 'run_as_password'.
I can't find any documentation of this feature other than the ticket which added it.
This feature first assigns the service to run as the specified user using the specified password.  This part works, although I needed to specify HOSTNAME/username, not just username.  You cannot specify the SID when using Win32::Service.configure.
The second part attempts to grant the user the right to log on as a service.  This part does not work.  First, the method it uses appears to require the SID of the user, but the code just passes the username.   I believe the correct fix is to look up the SID for the provided username and pass that:
wmic useraccount where name='USERNAME' get sid
A far worse issue is that it does not look up the existing permissions.  It just applies a permissions file.  This will completely clobber any existing users that have the right to logon as a service.  I believe it should pull the current list, then append the provided user as necessary.

I personally feel that this is two issues, one being the complete failure of "run_as_user" to work at all which I think is major - the functionality doesn't work at all and breaks the chef run.
The first issue is in my opinion a show-stopper.  What tadrinth failed to mention which I think is the key to getting this issue escalated, is that the chef-client run dies the moment the cookbook specifies run_as_user credentials.  This is more than not working as expected.  Tadrinth is also correct, documentations is not great here.  I was able to find doco but it doesn't specify that the server/domain name (or "." in place of server name) is required in front of the username to make the configuration for run_as_user take effect.
  Digging into the code, I find that in windows.rb on line ~244, an explicit "\" is inserted in front of the user name before it is added tot the text file being sent to scedit.exe - which ironically would work if there was no need to specify the server name and \ in front of the user name.  Removing these two slashes (technically \\ as they need to be escaped) will allow the chef-client run to successfully complete if you do correctly specify either "." or "SERVERNAME" or "DOMAINNAME" in front of the username.  This is a very simple fix and I hope someone can make this urgently to at least get chef-client to complete, and restore functionality for users only using a single service account to start service(s) on a server.
The second issue would be the clobbering problem.  I have confirmed this is the case through testing:

Manually restarting any service configured with run_as_user (except the last one chef configured) will fail, and the service will generally never start again.
The same happens upon rebooting the server.
This means the same will happen if the service fails.
The only workaround is to reconfigure (and effectively restart) the service every chef run, which is not a solution for many reasons I think are obvious and won't cover here.
Everything I have specified here is only an issue if you can work around the first issue above, as realistically the service won't actually ever start in the real world in the first place.

Maybe the resolution for the second issue would be to require log on as a service to be configured separately from the service credentials?
For us, the issue is going to prevent us running chef in our enterprise, and is a show stopper for our proof of concept.

Also tadrinth, I am not aware of a way to configure a service to run as a user via SID.  Do you know of a way to do this?  The Microsoft methods used by the code do not seem to support SID...

An update on the clobber issue, if you correctly specify the run_as_user credentials before all service start/restart resources, the services will actually start upon the next chef run correctly after all.  If you leave them out the chef run will fail.  There is no built in way that I can find to configure windows_service to detect the service name has changed and take action (IE run_as_user is ignored on :configure_startup) so I had to spend the time detecting this myself and coding in a not_if.  I had not been specifying the run_as_user credentials in the :start action as a result.  After doing this, the chef-client run will start the services, but if they fall over or the OS is rebooted, the services will not start automatically on boot or via manual intervention.  This means either waiting for the chef-client to run automatically (making automatic start a moot point) or by logging in and manually starting a chef-client run.  Not really ideal, but at least it actually works - but again - only if you hack windows.rb with my fix mentioned earlier.

For part 2 we need to add the ruby FFI equivilent of https://github.com/mwrock/chef-minecraft/blob/master/templates/default/LsaWrapper.ps1.erb to our the win32 code


Module import error with shell_plus --notebook (using wrong conda env)

In a Django project:
python manage.py shell_plus --ipython

is loading as expected with model imports, e.g., working just fine.
When trying to
python manage.py shell_plus --notebook

Jupyter will start. But when trying to create a new django shell plus notebook I will get the following import error:
[I 12:43:00.851 NotebookApp] Kernel started: 68eac163-4064-41ac-824d-5c839562814c, name: django_extensions
[IPKernelApp] WARNING | Error in loading extension: django_extensions.management.notebook_extension
Check your config files in /home/pumpkin/.ipython/profile_default
Traceback (most recent call last):
  File "/home/pumpkin/miniconda3/envs/django22/lib/python3.7/site-packages/IPython/core/shellapp.py", line 261, in init_extensions
    self.shell.extension_manager.load_extension(ext)
  File "/home/pumpkin/miniconda3/envs/django22/lib/python3.7/site-packages/IPython/core/extensions.py", line 87, in load_extension
    if self._call_load_ipython_extension(mod):
  File "/home/pumpkin/miniconda3/envs/django22/lib/python3.7/site-packages/IPython/core/extensions.py", line 134, in _call_load_ipython_extension
    mod.load_ipython_extension(self.shell)
  File "/home/pumpkin/miniconda3/envs/django22/lib/python3.7/site-packages/django_extensions/management/notebook_extension.py", line 10, in load_ipython_extension
    style=no_style(),
  File "/home/pumpkin/miniconda3/envs/django22/lib/python3.7/site-packages/django_extensions/management/shells.py", line 152, in import_objects
    setup()
  File "/home/pumpkin/miniconda3/envs/django22/lib/python3.7/site-packages/django/__init__.py", line 19, in setup
    configure_logging(settings.LOGGING_CONFIG, settings.LOGGING)
  File "/home/pumpkin/miniconda3/envs/django22/lib/python3.7/site-packages/django/conf/__init__.py", line 79, in __getattr__
    self._setup(name)
  File "/home/pumpkin/miniconda3/envs/django22/lib/python3.7/site-packages/django/conf/__init__.py", line 66, in _setup
    self._wrapped = Settings(settings_module)
  File "/home/pumpkin/miniconda3/envs/django22/lib/python3.7/site-packages/django/conf/__init__.py", line 157, in __init__
    mod = importlib.import_module(self.SETTINGS_MODULE)
  File "/home/pumpkin/miniconda3/envs/django22/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 953, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/pumpkin/django_projects/book_management/book_management/__init__.py", line 3, in <module>
    from .celery import app as celery_app
  File "/home/pumpkin/django_projects/book_management/book_management/celery.py", line 9, in <module>
    from celery import Celery
ModuleNotFoundError: No module named 'celery'

I might be missing something and I am happy to give more details and help reproduce the issue.
Versions:

django-extensions   3.1.1
Django              3.1.6
jupyter             1.0.0
jupyter-client      6.1.12
jupyter-console     6.4.0
jupyter-core        4.7.1
jupyterlab-pygments 0.1.2
jupyterlab-widgets  1.0.0

I could generalize the problem a bit. When executing:
django_environment_type='development' python manage.py shell_plus --notebook
and printing sys.path we get
sys.path=
['/home/pumpkin/django_projects/forecasting',
 '/home/pumpkin/miniconda3/envs/forecast_j2/lib/python39.zip',
 '/home/pumpkin/miniconda3/envs/forecast_j2/lib/python3.9',
 '/home/pumpkin/miniconda3/envs/forecast_j2/lib/python3.9/lib-dynload',
 '/home/pumpkin/miniconda3/envs/forecast_j2/lib/python3.9/site-packages']

which is expected (it is the conda env that is currently activated)
But when trying to start a new Django shell-plus notebook, we can see that the trace relies on another conda env:
[I 14:21:31.694 NotebookApp] Creating new notebook in
[I 14:21:32.373 NotebookApp] Kernel started: 8d4013f7-ae9e-4bf4-80a3-ca9483e72f0b, name: django_extensions
[IPKernelApp] WARNING | Error in loading extension: django_extensions.management.notebook_extension
Check your config files in /home/pumpkin/.ipython/profile_default
Traceback (most recent call last):
  File "/home/pumpkin/miniconda3/envs/django22/lib/python3.7/site-packages/IPython/core/shellapp.py", line 261, in init_extensions
    self.shell.extension_manager.load_extension(ext)

In this conda env the required modules are not installed. Hence the error.
Now my question would be, why does ipython(?) does not run in the proper conda env ?

When starting a python 3 notebook, we get:
print(sys.executable) => expected conda env
but when starting Django shell-plus notebook, we get:
print(sys.executable) => not the conda env we executed the command in


Test for permission errors fails as root

When running unit tests as root (i.e. as part of a install process that runs as
root) one test fails because root can still read files with 0 for permissions.
Attached is a pretty trivial way to skip the test that is compatible with any
version of python. A fancier way in >= 2.7 would be to call self.skipTest().

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 28 Jun 2013 at 6:37
Attachments:

python-gflags-2.0-skip-permission-test-as-root.patch

Simple and effective. Applied, thanks.


generate {started,finished}.json

needed for gcs federated test results
the copy pasta is making me a sad panda, would like to look into
squashing some nested j

lgtm


response vs responseText

It seems that when received type is json then response is null and responseText is json text, but from my understanding of standard it should be vice versa.
From: https://xhr.spec.whatwg.org/#the-responsetext-attribute about responseText

1 .If responseType is not the empty string or "text", then throw an "InvalidStateError" DOMException.

I am also not sure that I am looking at correct standard. Let me know where can I find text of standard that this library is based on.

I also got bitten by a similar issue. It seems like response is not supported at all (I also took a look at the code). I'm fetching binary data and getting the response in responseText as a binary-looking string.

Same for me, any update on this?

In the process of writing a workaround for this bug (passing the responseText.charCodeAt(i) into an ArrayBuffer), I've discovered the following:
Some data is unrecoverable in the incoming packet. Any byte which doesn't map to a known unicode code point gets mapped to 0xFFFD, i.e. https://www.fileformat.info/info/unicode/char/fffd/index.htm, which means you don't know what the actual response contained.
If anyone knows of a patched version of this library, or a workaround that actually works, it would be good to mention it here, since the project seems to be inactive.


🐛 BUG:A request to the Cloudflare API  backup failed

Which Cloudflare product(s) does this pertain to?
D1, R2
What version(s) of the tool(s) are you using?
3.9.0[wrangler]
What version of Node are you using?
v18.7.0
What operating system are you using?
mac
Describe the Bug
i am trying to work locally with d1, as described here :
https://github.com/cloudflare/workers-sdk/tree/main/templates/worker-d1
so when i try to create a backup with R2 i am getting
The request is malformed: Experimental DBs do not support backups yet:
please advice
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
No response

Had this issue aswell while migrating with d1, updating to 3.10.0 fixed it for me.

@abdolrhman Could you clarify the exact Wrangler command you're running that causes this error? Does upgrading to v3.10 fix the issue for you?

Not the issue creator, but I was stuck on this issue for a bit too
I kept running wrangler --version and getting 3.10.1, without realizing that my shell was using globally-installed Wrangler (3.10.1), but my package.json scripts were using my devDependencies-installed Wrangler.
After updating Wrangler in devDependencies, this is fixed after 3.10.

For future reference, using npx wrangler will use your local project wrangler first and then the globally installed version before getting the latest from npm and using that
Sounds like this is fixed in v3.10.0, so I will close this issue now.
@abdolrhman thanks for reporting the issue, if the problem still exists on the latest version please feel free to open

I met the same problem with wrangler 3.13.2.
Here is the relevant log.
╭─ ~/Documents/code/test ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── ✔  at 11:10:17
╰─ npx wrangler d1 backup create test-db
Proxy environment variables detected. We'll use your proxy for fetch requests.

✘ [ERROR] A request to the Cloudflare API (api address) failed.

  The request is malformed: Experimental DBs do not support backups yet:
  [my-database-id] (v3) [code: 7400]

  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

My system info:

wrangler: 3.13.2
node: 18.16.0
os: ubuntu 22.04

I am having the same issue:


[Fix #9325] Make Exclude config parameters merge by default

First of all, I'm not convinced that this is a good idea. Let's discuss.
It turned out to be trickier to implement than I had anticipated. There was code here and there that depended on the inherit mode being override for Exclude. The changes in pretty central parts of the logic makes me worry that we're opening up a can of worms. More issues will be reported down the line. That sort of thing.
And also, the complexities of configuration inheritance are getting worse with this change IMO. It's a bit weird that Excludes are merged while Includes are overridden. I experimented with letting Includes be merged as well, but that's a much bigger change since default configuration uses Include to let specific cops only inspect one kind of file.
So that's the case against. :slightly_smiling_face: Here's the description:
Add the inherit_mode setting in default configuration to make Exclude parameters in user configuration merge with the same Exclude settings in inherited configuration. The result of rubocop --auto-gen-config is affected by this change, since we otherwise copy values from inherited Exclude settings into the generated file.

I don't understand the build failure for Ruby 2.4, and I can't reproduce it locally.

By the way, this is a change to default configuration, which means it requires bumping the major version of RuboCop. Right?

Yes. That's why we have to weigh the pros and cons of this very carefully.

Looks good to me.
I think almost nobody ever wants to scan files under:
  Exclude:
    - 'node_modules/**/*'
    - 'tmp/**/*'
    - 'vendor/**/*'
    - '.git/**/*'

And it can still be done with
inherit_mode:
  override:
    - Exclude

if desired (as documented).
So I'm not sure as a RuboCop user that requiring a new major version for this is really needed.
OTOH, if releasing RuboCop 2.x would be something reasonably soon then I wouldn't really mind.
Another way to do this which would avoid changing the default inherit_mode for Exclude would be to have something like DefaultExclude: in addition to Exclude: and then merge both of these arrays.
Then it would solve the issue, and for people wanting no default excludes, it'd be quite clear:
AllCops:
  DefaultExclude: []

So I'm not sure as a RuboCop user that requiring a new major version for this is really needed.

I'm afraid that anything that will break RuboCop's behaviour for some users requires a major release. There are no plans for RuboCop 2.0 at this point, but it's bound to happen at some point.

Am I using the milestone feature correctly? I set 2.0 as milestone for this one, but does that mean that the PR should be merged exactly when we release 2.0 -- not before?

@jonas054 Yeah, you're using it correctly.

It would allow removing those tweaks from extensions: rubocop-rspec, rubocop-rails.

I experimented with letting Includes be merged as well, but that's a much bigger change since default configuration uses Include to let specific cops only inspect one kind of file.

It may seem that Include is semantically different. Where Exclude means "don't check those", and it makes sense to accumulate definitions from different places (default RuboCop config, gems, project root config, project sub-directory config). Include feels different, and is supposed to mean "only check those", e.g.
Include:
 - '**/Gemfile'

After checking the Include statements from config/default.yml of rubocop, rubocop-rspec and rubocop-rails, I couldn't come up with an example where users would suffer from Include merging by default. It was a revelation that it might make sense to add those as well, e.g.:
Rails/AddColumnIndex:
  Include:
    - db/migrate/*.rb

E.g. on my current project we have multiple databases, and migrations for the second one are in db/misc-migrate.
Having Include in override mode would skip the cop for db/migrate.

much bigger change

Code-wise, or impact-wise bigger?

Code-wise, or impact-wise bigger?

I was thinking impact when I wrote that. My intuition says that changing the meaning from include only to include also would be big, but I haven't conducted any experiments to prove it.

Another aspect on this situation is using rubocop --auto-gen-config as suggested in https://docs.rubocop.org/rubocop/configuration.html#automatically-generated-configuration. If you use it, you may get Exclude: set for certain cops, disabling the default excludes of those cops with the default inherit_mode, resulting in the end in rubocop failing even so you just tried to silence all complaints via the .rubocop_todo.yml.
Manually adding
inherit_mode:
  merge:
    - Exclude

fixes this, but it feels confusing this happens.


Exception when specifying format for page.GetPdfAsync

When specifying the format for pdf generation, an exception is thrown as a string is expected but an object is passed (of type PaperFormat). The actual call site where the conversion should be done I think would be here

Thanks for the report @lvmajor

Could you try 0.142.2?

Yes certainly

That seems to work :) I didn't see any code commit, did you update nuget from local source?

@lvmajor yeah, I wanted to get you unblocked :)

Ahah ok no problem I will keep it open even though the temporary fix works well for me :) I was not solely blocked by this hehe, I'm still struggling to get the html content size to be as expected but those conversions from css to inches... never really seem to work as expected ahah!


New tedlium3 conformet_ctc recipe problem

Hello guys,
I am trying new  tedlium3 conformet_ctc recipe which was lately added to icefall. I created following script to run training and decoder together:
export CUDA_VISIBLE_DEVICES="0,1,2,3"
./conformer_ctc2/train.py
--world-size 4
--num-epochs 40
--exp-dir conformer_ctc2/exp
--max-duration 150
--use-fp16 true
epoch=38
avg=26
ctc decoding
./conformer_ctc2/decode.py
--method ctc-decoding
--exp-dir conformer_ctc2/exp
--lang-dir data/lang_bpe_500
--result-dir conformer_ctc2/exp
--max-duration 500
--epoch $epoch
--avg $avg
Its behaviour is weird. After 3 days of training, and after the training was finished I got following messages. It seems that directory ~/icefall/egs/tedlium3/ASR/conformer_ctc2/exp was completed deleted. And all outputs that were created during the training were deleted. Could you help please.
2022-12-30 08:21:00,987 INFO [train.py:990] (3/4) Done!
2022-12-30 08:21:01,016 INFO [train.py:990] (2/4) Done!
2022-12-30 08:21:01,028 INFO [train.py:990] (1/4) Done!
2022-12-30 08:21:01,030 INFO [checkpoint.py:75] (0/4) Saving checkpoint to conformer_ctc2/exp/epoch-40.pt
2022-12-30 08:21:04,603 INFO [train.py:990] (0/4) Done!
fatal: detected dubious ownership in repository at '/fsx_new/Alex/tmp1/icefall'
To add an exception for this directory, call:
    git config --global --add safe.directory /fsx_new/Alex/tmp1/icefall

fatal: detected dubious ownership in repository at '/fsx_new/Alex/tmp1/icefall'
To add an exception for this directory, call:
    git config --global --add safe.directory /fsx_new/Alex/tmp1/icefall

fatal: detected dubious ownership in repository at '/fsx_new/Alex/tmp1/icefall'
To add an exception for this directory, call:
    git config --global --add safe.directory /fsx_new/Alex/tmp1/icefall

2022-12-30 08:21:08,389 INFO [decode.py:646] Decoding started
2022-12-30 08:21:08,390 INFO [decode.py:647] {'subsampling_factor': 4, 'feature_dim': 80, 'search_beam': 15, 'output_beam': 8, 'min_active_states': 10, 'max_active_states': 7000, 'use_double_scores': True, 'env_info': {'k2-version': '1.21', 'k2-build-type': 'Release', 'k2-with-cuda': True, 'k2-git-sha1': 'c3a7404e0d9da4d8d99f3f15c54d80b321c1b960', 'k2-git-date': 'Mon Oct 31 04:45:41 2022', 'lhotse-version': '1.10.0.dev+git.96884c9.clean', 'torch-version': '1.12.1', 'torch-cuda-available': True, 'torch-cuda-version': '11.3', 'python-version': '3.7', 'icefall-git-branch': None, 'icefall-git-sha1': None, 'icefall-git-date': None, 'icefall-path': '/fsx_new/Alex/tmp1/icefall', 'k2-path': '/opt/conda/lib/python3.7/site-packages/k2-1.21.dev20221102+cuda11.3.torch1.12.1-py3.7-linux-x86_64.egg/k2/init.py', 'lhotse-path': '/opt/conda/lib/python3.7/site-packages/lhotse/init.py', 'hostname': 'bdcf5ab79459', 'IP address': '<IP_ADDRESS>'}, 'epoch': 38, 'iter': 0, 'avg': 26, 'method': 'ctc-decoding', 'use_averaged_model': True, 'num_paths': 100, 'nbest_scale': 0.5, 'exp_dir': PosixPath('conformer_ctc2/exp'), 'lang_dir': PosixPath('data/lang_bpe_500'), 'lm_path': PosixPath('data/lm/G_4_gram.pt'), 'result_dir': PosixPath('conformer_ctc2/exp'), 'num_encoder_layers': 24, 'num_decoder_layers': 6, 'att_rate': 0.8, 'dim_feedforward': 1536, 'nhead': 8, 'dim_model': 384, 'manifest_dir': PosixPath('data/fbank'), 'max_duration': 500, 'bucketing_sampler': True, 'num_buckets': 30, 'concatenate_cuts': False, 'duration_factor': 1.0, 'gap': 1.0, 'on_the_fly_feats': False, 'shuffle': True, 'return_cuts': True, 'num_workers': 2, 'enable_spec_aug': True, 'spec_aug_time_warp_factor': 80, 'enable_musan': True}
2022-12-30 08:21:08,616 INFO [lexicon.py:168] Loading pre-compiled data/lang_bpe_500/Linv.pt
2022-12-30 08:21:08,688 INFO [decode.py:657] device: cuda:0
2022-12-30 08:21:11,451 INFO [decode.py:836] Calculating the averaged model over epoch range from 12 (excluded) to 38
Traceback (most recent call last):
File "./conformer_ctc2/decode.py", line 899, in
main()
File "/opt/conda/lib/python3.7/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "./conformer_ctc2/decode.py", line 844, in main
device=device,
File "/workspace/icefall/icefall/checkpoint.py", line 424, in average_checkpoints_with_averaged_model
state_dict_start = torch.load(filename_start, map_location=device)
File "/opt/conda/lib/python3.7/site-packages/torch/serialization.py", line 699, in load
with _open_file_like(f, 'rb') as opened_file:
File "/opt/conda/lib/python3.7/site-packages/torch/serialization.py", line 230, in _open_file_like
return _open_file(name_or_buffer, mode)
File "/opt/conda/lib/python3.7/site-packages/torch/serialization.py", line 211, in init
super(_open_file, self).init(open(name, mode))
FileNotFoundError: [Errno 2] No such file or directory: 'conformer_ctc2/exp/epoch-12.pt'
fatal: detected dubious ownership in repository at '/fsx_new/Alex/tmp1/icefall'
To add an exception for this directory, call:

Guys, I am pretty sure that there is some problem with decode.py.
I have created several directories under directory exp/ and once I run decode.py all these subdirectories are deleted. Could you help please.

Guys, I found the lines that cause the deletion problem.
You can see in decode.py following lines:
if args.result_dir.is_dir():
    shutil.rmtree(args.result_dir)
args.result_dir.mkdir()

Could you help with this issue.

once I run decode.py all these subdirectories are deleted. Could you help please.

Could you use pdb to run decode.py step by step and and try to find at which line exp gets deleted?

I know why this happen, it's because I added an opportunity to save decoding results in a separate folder and it cleans it in the begininng of decode.py script. By default I set --result-dir to conformer_ctc2/exp, the same as --exp-dir, it was a mistake. @AlexandderGorodetski could you please try decode.py with  --result-dir  equal to conformer_ctc2/exp/results. It should help. I'm sorry that you removed all your models because of this bug, with 4 GPUs it should take less than 2 days to retrain the model.

@csukuangfj I can modify the default value for --result-dir in decode.py to avoid this problem in the future.

Following lines delete the exp directory
if args.result_dir.is_dir():
shutil.rmtree(args.result_dir)
args.result_dir.mkdir()

@AlexandderGorodetski Yes, I know, please make --result-dir different from your --exp-dir and it will work.

I suggest that we delete
https://github.com/k2-fsa/icefall/blob/67ae5fdf2bf2b09d2ce9e5acb7dab12b2d2fc441/egs/tedlium3/ASR/conformer_ctc2/decode.py#L638-L639
and change
https://github.com/k2-fsa/icefall/blob/67ae5fdf2bf2b09d2ce9e5acb7dab12b2d2fc441/egs/tedlium3/ASR/conformer_ctc2/decode.py#L640
to
 args.result_dir.mkdir(exist_ok=True)

Even if we set the default value of --result-dir to be different from --exp-dir, there is still a chance
that someone provides the same value for both --result-dir and --exp-dir. It is better not to delete things in decode.py.

@AlexandderGorodetski Try out the latest master, the problem is fixed, also feel free to close this issue if everything works fine.


How to validate if element is non-editable.

Hi All,
I have a strange case to validate if a particular element is non-editable.
Unfortunately, this is a label element and hence it is non-editable.
So .isEnabled() always returns true and my test case is failing.
How to handle this situation to see if this element is non-editable.

Hi there!
Your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)

Thanks!


Crash Nuclear reactor

NuclearCraft-1.20.1-1.0.0-rc.2.jar
This error happens when you open the nuclear oven and click the (R) button to see the recipes
Crash report:https://mclo.gs/wX8zXWC
I already reported also in jei jei issue

I guess this one fixed already. As i made bunch of fixes in JEI compat features


Gradle build

just run gradle build for building using Ant

Great work!

thanks! i'm did it because when i run command gradle --version, it also returns ant version.
(ant path edited for fixing build as user with non a-z A-Z characters)


Remove None when making alternate alleles string if in allele list

Otherwise, this TypeError is encountered: expected str instance, NoneType found.

Yep, this is exactly why we made the allele None - so that errors are raised early on if you haven't thought how to deal with missing data.


feat(hits): Add a __position attribute to data passed to items

Fixes #903
The change itself was easy to do, but it broke all the tests because
we were testing a full JSX output and we now had one more key passed
to the data.
It took this as an opportunity to refactor the Hits tests uzing enzyme
to make them easier to read. It allow me to spot one or two
inconsistencies in the way the root class was added or not depending
on the kind of template used.

Nice, can you add that new data name to the documentation and we are good.

@pixelastic small changes needed before merging


broken forc in cpp.lua

code ref: https://github.com/mireq/luasnip-snippets/blob/main/lua/luasnip_snippets/cpp.lua?#L329
Error
Error executing vim.schedule lua callback: ...ng/.local/share/nvim/lazy/nvim-cmp/lua/cmp/utils/str.lua:81: bad argument #1 to 'byte' (string expected, got table)
stack traceback:
	[C]: in function 'byte'
	...ng/.local/share/nvim/lazy/nvim-cmp/lua/cmp/utils/str.lua:81: in function 'trim'
	...rtzeng/.local/share/nvim/lazy/nvim-cmp/lua/cmp/entry.lua:457: in function 'get_documentation'
	...ocal/share/nvim/lazy/nvim-cmp/lua/cmp/view/docs_view.lua:48: in function 'open'
	...ertzeng/.local/share/nvim/lazy/nvim-cmp/lua/cmp/view.lua:299: in function 'callback'
	.../.local/share/nvim/lazy/nvim-cmp/lua/cmp/utils/async.lua:138: in function ''
	vim/_editor.lua: in function <vim/_editor.lua:0>

To reproduce this issue:

type and cmp is shown
tabbing all the way
error shown

Screen Record:

@olivertzeng i don't see any string "loop focusing on iteration times" in this project. It looks, like you are using friendly-snippets. Can you check, error is really from this snippet library? Thanks.

@olivertzeng i don't see any string "loop focusing on iteration times" in this project. It looks, like you are using friendly-snippets. Can you check, error is really from this snippet library? Thanks.

I only use luasnip-snippets
the "broken" is meant to be about the error, not about the tooltip

I have tried with your config, but i can't reproduce problem.

Can you try with minimal config?

I have tried with your config, but i can't reproduce problem.

Can you try with minimal config?

Alr will try that later when I get home


Update URL when selecting a different theme

Testing #153318

open https://insiders.vscode.dev/theme/vscode.theme-defaults/Default High Contrast Light
select another built-in theme
😞 the URL isn't updated to the newly selected theme

I would actually expect that the URL reflects the open folder/workspace and selected file. Which bring up the discussion how that plays together with the theme tester URL.

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


New  control List-Item-Attachments

Q
A

Bug fix?
[ ]

New feature?
[ X ]

New sample?
[ ]

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
New SPFx Reusable Control, List-Item-Attachments,  Manage List Item Attachments in Tile View.
Guidance

You can delete this section when you are submitting the pull request.
Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to dev branch.

Codecov Report

Merging #176 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #176   +/-   ##
=======================================
  Coverage   80.63%   80.63%
=======================================
  Files          10       10
  Lines         346      346
  Branches       71       78    +7
=======================================
  Hits          279      279
  Misses         44       44
  Partials       23       23

Impacted Files
Coverage Δ

src/loc/en-us.ts
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 a903091...0e5c42e. Read the comment docs.


5.7.0 migration client PostgreSQL  DB script changes

When migrating to IS  5.7.0 from the older versions create and update statements in the Postgres SQL DB scripts needs to be executed before checking whether that table, column or index if exists

Fixed in https://github.com/wso2/product-is/pull/5000


src/beacon_root: gas optimization

This PR is a small gas optimization for the beacon_root-contract.

dropped stop at the end of the contract: the execution stops, if the end of the contract is reached. an explicit stop at the end is not required.
dropped iszero: jumpi jumps, if the condition is non-zero. thus, the input_timestamp can be used as the condition directly. This reduces the gas consumption of the execution with valid input data by 2 (-3 for dropping the iszero, +1 for an extra jumpdest)

Hi @lmittmann, thanks for your PR. Unfortunately this contract is already deployed to mainnet so we won't be accepted additional changes to it.


sendOperationRequest can receive OperationOptions

This PR seeks to address #6457 by extending sendOperationRequest.
I wanted to get some feedback on the implementation before I spent time adopting this in libraries.
I believe this change would necessitate bumping core-http to 1.1 so we can express a dependency on that from libs that want to take advantage of this new signature.
All feedback is appreciated! :heart:

Closing this old PR as its goal is achieved by the new core-https/core-client combination.


Close gunsafetytownhalls.org for the season

-Stop populating with new events
-banner in front of map to read "Check back soon for more from the gun safety coalition."

A few questions:
Do you want that wording instead of the current title, or below it? Should I remove the rest of the text?
For the events: should it just show nothing or keep showing events in the past?

Short answer: whatever is easiest for you since there won't be a ton of organic traffic to this url for now.
Long answer:
My ideal version of this is just freezing the whole site, including whatever events are displayed, and then graying out the whole thing with the Away message in a box on top of it (akin to what we did for Maine but for the whole site)


Add sell stop orders

Adds sell stop orders to the matchengine component. Aiming for fulfillment of the stop loss orders issue #1.
I've taken this description as the target and implemented only sell stop. Trying to post a buy stop order returns an error:

All I want for the bounty is basic stop-loss order which is a market order with a condition attached that says "this order shall only execute when price drops below X". In other words sell at the best market price when price drops below X.

The HTTP API has a new method order.put_stop_loss. The test file gist shows the parameters. Opening a stop loss order freezes the amount and begins watching market price. When a trade drops the price strictly below the trigger price, the order is closed and market sell order opened.
The logic is like this:

Triggering order executed completely.
All triggered stop loss orders located.
Each stop loss order converted. Each of these actions can trigger further stop orders.

So it's recursion safe. Everything happens atomically at the important points.
Stop loss orders are not visible in an API dump of the order book, which seems to be the normal way.
There's a schema change to add the trigger price. So if you go to test it you'll want to start a fresh database.
The commit history is my working sequence. If you prefer clean commits I can organize.

The test file gist runs a test sequence that triggers a stop loss order.
Condition:
1 stop loss < 90 BCH, sell 1 BTC
1 ask 80 BCH for 1 BTC
2 bid 20 BCH for 1 BTC

Behavior:

2 sells 80 BCH at market price. This consumes the 1 BTC at 80 BCH.
That price is below the stop price. Stop loss order becomes market sell of 1 BTC.
The market sell consumes the 20 BCH bid.
End result is 2 bought 2 BTC, 1 bought 100 BCH.

On Thu, Oct 18, 2018, 19:59 bookmoons<EMAIL_ADDRESS>wrote:

Adds sell stop orders to the matchengine component. Aiming for
fulfillment of the stop loss orders issue #1
https://github.com/cemkod/viabtc_exchange_server/issues/1.
I've taken this description
https://github.com/cemkod/viabtc_exchange_server/issues/1#issuecomment-408636231
as the target and implemented only sell stop. Trying to post a buy stop
order
https://en.wikipedia.org/wiki/Order_(exchange)#Buy–stop_order
returns an error:
All I want for the bounty is basic stop-loss order which is a market order
with a condition attached that says "this order shall only execute when
price drops below X". In other words sell at the best market price when
price drops below X.
The HTTP API has a new method order.put_stop_loss. The test file gist
https://gist.github.com/bookmoons/afad68ec11d5d3cf16e4301c2e563201
shows the parameters. Opening a stop loss order freezes the amount and
begins watching market price. When a trade drops the price strictly below
the trigger price, the order is closed and market sell order opened.
The logic is like this:

Triggering order executed completely.
All triggered stop loss orders located.
Each stop loss order converted. Each of these actions can trigger
further stop orders.

So it's recursion safe. Everything happens atomically at the important
points.
Stop loss orders are not visible in an API dump of the order book, which
seems to be the normal way.
There's a schema change to add the trigger price. So if you go to test it
you'll want to start a fresh database.
The commit history is my working sequence. If you prefer clean commits I
can organize.
You can view, comment on, or merge this pull request online at:
https://github.com/cemkod/viabtc_exchange_server/pull/2
Commit Summary

Define stop loss command
Add stop loss command to RPC server
Add put stop loss routing to matchengine
stoploss: Extract user_id
stoploss: Extract market
stoploss: Extract side
stoploss: Extract trigger
stoploss: Extract amount
stoploss: Extract taker fee
stoploss: Extract source
stoploss: Add branched invalid argument reply
stoploss: Add put procedure
stoploss: Error on buy stop order
stoploss: Verify balance
stoploss: Verify over min amount
stoploss: Add order.trigger
Add space to utils macros
Define stop loss order type
stoploss: Construct order
stoploss: Add execute sell stop procedure
stoploss: Remove execute procedure
stoploss: Add order.trigger to get_order_info
stoploss: Add order.trigger to order_free
stoploss: Add trigger to SQL schema
stoploss: Add trigger field to SQL code
stoploss: Add order_put
stoploss: Record in operlog
stoploss: Record left amount
stoploss: Implement operlog loading
stoploss: Add success reply
stoploss: Add to order_put
stoploss: Add stop asks list to market
stoploss: Create stop asks list on market create
stoploss: Construct stop asks list
stoploss: Add general trigger procedure
stoploss: Add sell stop orders trigger procedure
stoploss: Detect trigger failure
stoploss: Add price param to trigger procedures
stoploss: Simplify general trigger procedure
stoploss: Dump to database
stoploss: Implement trigger logic
stoploss: Correct price reference
stoploss: Implement stop loss order finishing
stoploss: Add order.trigger to history

File Changes

M accesshttp/ah_server.c
https://github.com/cemkod/viabtc_exchange_server/pull/2/files#diff-0
(1)
M matchengine/me_dump.c
https://github.com/cemkod/viabtc_exchange_server/pull/2/files#diff-1
(8)
M matchengine/me_history.c
https://github.com/cemkod/viabtc_exchange_server/pull/2/files#diff-2
(6)
M matchengine/me_load.c
https://github.com/cemkod/viabtc_exchange_server/pull/2/files#diff-3
(87)
M matchengine/me_market.c
https://github.com/cemkod/viabtc_exchange_server/pull/2/files#diff-4
(228)
M matchengine/me_market.h
https://github.com/cemkod/viabtc_exchange_server/pull/2/files#diff-5
(3)
M matchengine/me_server.c
https://github.com/cemkod/viabtc_exchange_server/pull/2/files#diff-6
(104)
M readhistory/rh_reader.c
https://github.com/cemkod/viabtc_exchange_server/pull/2/files#diff-7
(6)
M sql/create_trade_history.sql
https://github.com/cemkod/viabtc_exchange_server/pull/2/files#diff-8
(2)
M sql/create_trade_log.sql
https://github.com/cemkod/viabtc_exchange_server/pull/2/files#diff-9
(1)
M utils/ut_define.h
https://github.com/cemkod/viabtc_exchange_server/pull/2/files#diff-10
(15)
M utils/ut_rpc_cmd.h
https://github.com/cemkod/viabtc_exchange_server/pull/2/files#diff-11
(1)

Patch Links:

https://github.com/cemkod/viabtc_exchange_server/pull/2.patch
https://github.com/cemkod/viabtc_exchange_server/pull/2.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cemkod/viabtc_exchange_server/pull/2, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AD0YnBexkyWHVkkFc3-cqAJKy_FLGNEaks5umLN0gaJpZM4Xt39l
.

Hello again,
Thank you. We have reviewed the code. It looks clean and does what we asked for. If it passes the tests we are preparing, we'll release the bounty.
We also want to ask for some additional changes. Can you contact me at<EMAIL_ADDRESS>address to discuss the additional changes and pricing?

We also want to ask for some additional changes. Can you contact me at<EMAIL_ADDRESS>address to discuss the additional changes and pricing?

Thanks very much for the request. Will send an email.

I'm realizing the ordering might be wrong in nested triggering. What happens now is a triggered sell stop triggers new sell stops immediately. So if the first trigger finds eg 3, the items later in the list might not execute until 20 other sell stops have executed.
I'm not sure now what the typical ordering is on markets. Maybe the thing to do is execute the entire list of located sell stops, and only then trigger new ones. Does that seem right? If that's better I can update.

There's an exploratory branch with the change I mentioned above:
https://github.com/bookmoons/viabtc_exchange_server/tree/bookmoons/sellstop/ordered
It feels better to me. Trigger everything, then if the price has changed trigger again. It also happens to move the recursion into a tail call.
There's a diff of the changes:
https://github.com/bookmoons/viabtc_exchange_server/compare/bookmoons/stoploss...bookmoons:bookmoons/sellstop/ordered


Issue on Integration Setup

Logger: homeassistant.config_entries
Source: config_entries.py:406
First occurred: 8:52:55 AM (2 occurrences)
Last logged: 8:54:23 AM

Error setting up entry ---REDACTED--- for eyeonwater
Traceback (most recent call last):
  File "/config/lsiopy/lib/python3.11/site-packages/pyonwater/meter_reader.py", line 115, in read_historical_data_one_day
    data = HistoricalData.parse_raw(raw_data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "pydantic/main.py", line 549, in pydantic.main.BaseModel.parse_raw
  File "pydantic/main.py", line 526, in pydantic.main.BaseModel.parse_obj
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 2 validation errors for HistoricalData
timeseries -><PHONE_NUMBER>058372026,0 -> series -> 9 -> display_unit
  field required (type=value_error.missing)
timeseries -><PHONE_NUMBER>058372026,0 -> series -> 9 -> bill_read
  field required (type=value_error.missing)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/eyeonwater/coordinator.py", line 43, in read_meters
    await meter.read_historical_data(
  File "/config/lsiopy/lib/python3.11/site-packages/pyonwater/meter.py", line 64, in read_historical_data
    historical_data = await self._reader.read_historical_data(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/lsiopy/lib/python3.11/site-packages/pyonwater/meter_reader.py", line 79, in read_historical_data
    statistics += await self.read_historical_data_one_day(
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/lsiopy/lib/python3.11/site-packages/pyonwater/meter_reader.py", line 118, in read_historical_data_one_day
    raise EyeOnWaterAPIError(msg) from e
pyonwater.exceptions.EyeOnWaterAPIError: Unexpected EOW response 2 validation errors for HistoricalData
timeseries -><PHONE_NUMBER>058372026,0 -> series -> 9 -> display_unit
  field required (type=value_error.missing)
timeseries -><PHONE_NUMBER>058372026,0 -> series -> 9 -> bill_read
  field required (type=value_error.missing)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/lsiopy/lib/python3.11/site-packages/homeassistant/config_entries.py", line 406, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/eyeonwater/__init__.py", line 52, in async_setup_entry
    await eye_on_water_data.read_meters(days_to_load=30)
  File "/config/custom_components/eyeonwater/coordinator.py", line 48, in read_meters
    raise UpdateFailed(error) from error
homeassistant.helpers.update_coordinator.UpdateFailed: Unexpected EOW response 2 validation errors for HistoricalData
timeseries -><PHONE_NUMBER>058372026,0 -> series -> 9 -> display_unit
  field required (type=value_error.missing)
timeseries -><PHONE_NUMBER>058372026,0 -> series -> 9 -> bill_read
  field required (type=value_error.missing)

Should be fixed here: https://github.com/kdeyev/eyeonwater/releases/tag/v2.5.6


Fix for loadByPeriod rule

If a segment (say created by merge from multiple smaller segments), has a start time less than the loadByPeriod start time, it is currently dropped by the coordinator even if it overlaps the load period. This CL fixes that.

@anubhgup This is not a bug and was intended by design. This change also breaks router logic.

Added unit test.

What are the intended semantics of loadByPeriod? In my use case, this is breaking things since it leads to a segment getting dropped even though it contains data in my retention period. How can I work around this problem? Currently, I have a retention rule that says "loadByPeriod=7D, dropForever". When I enabled segment merging, and segment that spans that 7D boundary gets dropped by the coordinator.

@anubhgup Sorry I had to run before. Writing up a more complete view on loadByPeriod.
I am actually okay with redefining the semantics of loadByPeriod, and they should be changed to make more sense. The one use case that is currently problematic is that the router uses rules to determine how to forward queries. In a setup where you have different brokers dedicated to different time ranges, if the router receives a 1 yr query, we want this query to route to the broker dedicated for slow (older) queries. The changes here would mean the query would be forwarded to the brokers dedicated for fast queries. I am 100% in favor of removing the router entirely and having the routing logic live on the brokers.
One simple workaround is to introduce a new rule type, loadByPeriodByOverlap or something and use that. The correct solution is to rethink the router and some of the rules, which may require some more time dedication.

Thanks @fjy. I can introduce the new rule type. Would it be useful to merge the new rule CL to the main branch, or should I just implement that for local use?

@anubhgup feel free to submit a PR, I don't see a reason not to include it in the main branch.

Can we call it loadByOverlapPeriod instead?
Also, those semantics about dropping even though it has relevant data are very unintuitive, was that introduced when we added the router?  Just as a general rule, the load/drop/retention rule's semantics should be defined according to what makes sense for the retention of segments.  If the router's logic cannot re-use them as is, then it shouldn't be a problem with the interface, it just means that the router cannot reuse that same logic...


Fix incorrect documentation for ADF Python Trigger creation

The Python example for creating a ScheduleTrigger for ADF was missing
a wrapper class. This issue is mentioned here and here

@danielvdende : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@chez-charlie – Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"

@chez-charlie can you confirm if this change is correct, and I will merge if so.  Thank you!

Emailed Charlie and a few others to get a code review.

Thanks for helping us improve the docs, @danielvdende.  This change has been merged and will appear in the next publishing cycle later today.


Gradle daemon picking doesn't look on user groups / Provide a way to customize choosing Gradle daemon

Expected Behavior
Imagine me running two Gradle task sets:
./gradlew testClasses
# Tests use Docker, allow access to it
sudo -g docker ./gradlew test

Since second one is launched with different primary group & supplementary group set, it should pick a different Gradle daemon (launching one if missing).
Current Behavior (optional)
Of many things that Gradle takes into account when choosing a daemon to use, groups are not used for it.
Also, there is no way to provide Gradle some user information for daemon choosing, like custom disambiguation.
Context
I am trying to lock down my Linux work machine a bit by not providing unrestricted Docker access to my Linux user, since Docker access is essentially root access. I am trying to work around this by using sudo -g docker for workloads requiring Docker access, and this works fine-ish. However, when I try running Gradle builds that involve Docker for test purposes (see TestContainers), I have to either run the whole build with Docker group:
sudo -g docker ./gradlew ...

or, since I am trying to lock down machine a bit, only provide Docker access for step requiring it. However, as I've stated above, Gradle will try to reuse the daemon from the first step and fail.
This can be work-around by actually providing --no-daemon flag that will launch a one-off daemon, but that slows down every test launch.
Also, the problem isn't limited to this Docker setup or other things. One might look at other credentials (like key source for signing a release binary) and only expose them to tasks needing them. While not perfect (since Gradle will still re-verify all previous steps and possibly execute them), that can be a measure to short the window for credentials misuse.
Another process properties that could be considered are priorities. You could have two Gradle daemons: one with default priority for normal development and a separate background one with lower priority for some long-running tasks, and if Gradle would swap them that would be noticed by the end user.
Instead of providing Gradle information on how to select a daemon (we don't need another attribute-based mechanism here), probably option to start the daemon with user-specified disambiguation id and option to provide it to build launches would suffice.
P.S. Sorry for any typos, beta issue form is a bit annoying.

The feature you're requesting would imply a lot of problems from a security point of view: file permissions, ownership, process isolation, etc. We won't support that because it adds more problems than solves.
For your use case, you can try one of the following:

Launch a build with another Gradle home dir. This would isolate the daemon.
Launch a build with sudo and another user. This would isolate the daemon because Gradle home dir would change.
Create a trusted environment or launch every Gradle daemon with sudo.

P.S. Sorry for any typos, beta issue form is a bit annoying.

@LDVSOFT Could you elaborate a bit on how we can improve our issue forms?

Another Gradle home dir sounds cool! I wouldn't want to avoid whole cache duplication, but I guess I can look into that, thanks. Still I'm sad there isn't an option to control the daemon I'm starting in special environment.
About forms: it had three input boxes (like the ones I'm writing this comment in), yet they weren't resizable vertically, only one of them with focus was a proper editor (others swtiched to non-monospace text areas, still not resizable) and there wasn't a proper preview for the whole thing. So while writing it and jumping between input boxes I couldn't properly see my draft in full: only non-editable parts and the one with a focus.

Oh, so it is a GitHub UI problem, ok. Unfortunately, it's up to the GitHub team to improve this, consider contacting them.
BTW, you can resize an input box - there is a draggable bottom-right corner:

The resize of small boxes in the form didn't work: the comment form has a bigger and actually working box ;)


Issue86 functional theme change button

add a feature to toggle the theme
https://github.com/HimanshuNarware/CareerZunction_Intern/assets/119344874/97f7ce18-d546-4216-adc0-34096fed2334

@ANSH127 RESOLVE CONFLICTS

@HimanshuNarware  Done

@ANSH127 light theme has lots of problems like the font are not visible clearly. also internship section need improvement

add a feature to toggle the theme
CareerZunction.-.Google.Chrome.2024-05-13.16-15-35.mp4
like you show in video font are not that in color

@HimanshuNarware  let me fix the font issue and tell me in light theme what changes you want.?

@HimanshuNarware

could I make the card bg light black?

I fixed the font issue and changed the bg color of the card
https://github.com/HimanshuNarware/CareerZunction_Intern/assets/119344874/b4fdee9a-25ce-4582-b9be-79adcee9b6ce

@ANSH127 footer section text is not visible

@HimanshuNarware
Now is it ok?

done
https://github.com/HimanshuNarware/CareerZunction_Intern/assets/119344874/8a86d2a4-ed41-41a4-ad10-2f4d17647414

@HimanshuNarware
https://github.com/HimanshuNarware/CareerZunction_Intern/assets/119344874/9f9d1ee8-c05a-43a2-8acc-3fcf724f385b

Can you make hover effect in light theme to dark purple not black @ANSH127 ?

@PSS2134  okay sure

@PSS2134  done
https://github.com/HimanshuNarware/CareerZunction_Intern/assets/119344874/36e84723-25f6-466b-a70b-ddb950f4f076

In the Internship section, for light theme, the cards look too bright at borders, also the footer is not distinguishable , may be you can add a light grey line or something and keep the default theme to dark, when someone opens the site

@PSS2134 I have set the border gray on the light theme , distinguished the footer, and set by default the dark theme
Uploading CareerZunction - Google Chrome 2024-05-19 14-55-47.mp4…

Still looks bright and can't see gray line at the footer can you check @ANSH127

@ANSH127  are you still  working on this issue.

@ANSH127  for the light theme use a black background on the card, but  for the dark it is the same

@HimanshuNarware

could I make the card bg light black?

@ANSH127 only for the light theme , dark theme remain same

@ANSH127  Do one thing again raise PR with  recommended changes


Update a schema to demonstrate minimum/maximum supports floats

What is the context of this PR?
Update the JSON schema validator to accurately support decimal minimum and maximum constraints while disallowing string types. To demonstrate this, I changed a schema in runner to show that floats are allowed.
How to review
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

 Update validator to support float minimum/maximum


Linux Docker:  Docker Machine not installed

Hey,
I've a problem with connecting to my docker server.
DockStation says, no Docker machine installed. So I've the last version of docker machine installed.
docker-machine version 0.16.0, build 702c267f
with these documentation: https://docs.docker.com/machine/install-machine/
How can i fix them ?
Thank you!
Best Regards

Hi @cuban8IO. So, I need more info. What is driver do you use (VirtualBox, VMWare, etc...)?

Hi @cuban8IO are you using Linux as host to docker? looks like Docker Machine is only for Windows/Mac only where you can not setup docker engine.
Im running on linux and my docker engine is on other linux. And showed that error at start page but going to containers and adding a remote host to connect solved the issue and I can use dockstation


[Feature] Favicon path move to /static/images

I have checked all the prerequisites below and I'm yet experiencing a problem

[x] Read the README.md
[x] Have the extended version of Hugo installed
[x] Used the exampleSite's config.toml as a reference

Describe the bug
All branding assets for this theme related to images need to be stored together without having some components coming from the theme while others come from site directories. The thing missing here is favicons, which still are configured to point to the theme directory. Change these so that they can be picked up from /static/images just like the banner images.
Desktop (please complete the following information):

OS: N/A
Browser: N/A

The thing missing here is favicons, which still are configured to point to the theme directory.

@chipzoller, this is the desired behaviour. You can override favicons from the site directory. This way, the theme isn't dependent on the theme to function.

Can you provide some instruction on this in your docs, or is this a generic Hugo topic? Even if so, it may be kind of you to point users there.


enable selectedVoice switch

hi, very neat example.
just a reminder to enable selectedVoice switch at onclick() uncommenting
state.tts.selectedVoice = state.tts.voices[document.querySelector('select').value]
  function onclick () {
    // speak with default voice
    state.tts.selectedVoice = state.tts.voices[document.querySelector('select').value]
    emit('tts:speak', document.getElementById('text').value)
  }

Hi @sallespro nice catch.
I commented that line to replace it with the set voice event, but forget to update haha.

fixed in 14fd525


RDP Stopped working

I had RDP running for almost 8 months now after i used RDPWrap when setting this PC.
Suddenly, this morning i was not able to connect remotely to this PC. Searching on net i see people reported CredSSP issue causing similar observation. Anyway, i added the registry entries per the remediation steps mentioned elsewhere. That did'nt solve my issue.
Tried RDPConf and I see the state as attached. The listener state shows as Not Listening.
Uninstalled and Installed again but no help. Any ideas?

Duplicate of #456.


[misc] Refactoring & Cleanup - aliases and priorities in src/lib/units/

My mission with this refactoring was to make it more readable and procedural. Not only it reduces 32 function calls, It's all in one place. All aliases in aliases.js file and all priorities in priorities.js file

All the functions which were responsible for creating aliases from following files(comments are file names) have been moved to src/lib/units/aliases.js

// src/lib/units/day-of-month.js
addUnitAlias('date', 'D');
// src/lib/units/day-of-week.js
addUnitAlias('day', 'd');
addUnitAlias('weekday', 'e');
addUnitAlias('isoWeekday', 'E');
// src/lib/units/day-of-year.js
addUnitAlias('dayOfYear', 'DDD');
// src/lib/units/hour.js
addUnitAlias('hour', 'h');
// src/lib/units/millisecond.js
addUnitAlias('millisecond', 'ms');
// src/lib/units/minute.js
addUnitAlias('minute', 'm');
// src/lib/units/month.js
addUnitAlias('month', 'M');
// src/lib/units/quarter.js
addUnitAlias('quarter', 'Q');
// src/lib/units/second.js
addUnitAlias('second', 's');
// src/lib/units/week-year.js
addUnitAlias('weekYear', 'gg');
addUnitAlias('isoWeekYear', 'GG');
// src/lib/units/week.js
addUnitAlias('week', 'w');
addUnitAlias('isoWeek', 'W');
// src/lib/units/year.js
addUnitAlias('year', 'y');

Ran all the functions and final result has been saved as "aliases" object in  src/lib/units/aliases.js.

Commented out all the aliases creation functions in src/lib/units/aliases.js as we have final and known Object as a variable.

All the functions which were responsible for creating priorities from following files(comments are file names) have been moved to src/lib/units/priorities.js

// src/lib/units/day-of-month.js
addUnitPriority('date', 9);
// src/lib/units/day-of-week.js
addUnitPriority('day', 11);
addUnitPriority('weekday', 11);
addUnitPriority('isoWeekday', 11);
// src/lib/units/day-of-year.js
addUnitPriority('dayOfYear', 4);
// src/lib/units/hour.js
addUnitPriority('hour', 13);
// src/lib/units/millisecond.js
addUnitPriority('millisecond', 16);
// src/lib/units/minute.js
addUnitPriority('minute', 14);
// src/lib/units/month.js
addUnitPriority('month', 8);
// src/lib/units/quarter.js
addUnitPriority('quarter', 7);
// src/lib/units/second.js
addUnitPriority('second', 15);
// src/lib/units/week-year.js
addUnitPriority('weekYear', 1);
addUnitPriority('isoWeekYear', 1);
// src/lib/units/week.js
addUnitPriority('week', 5);
addUnitPriority('isoWeek', 5);
// src/lib/units/year.js
addUnitPriority('year', 1);

Ran all the functions and final result has been saved as "priorities" object in  src/lib/units/priorities.js.

Commented out all the priorities creation functions in src/lib/units/aliases.js as we have final and known Object as a variable.

@anandfresh Helllo sir,
Sorry for late reply.
I removed comments as requested..

Merge in d6d5df7b


lab 0.24.0, 0.25.0 failed due to ls-files not exist

not sure what was changed, but the most recent upgrade efforts (0.24.0 and 0.25.0) for homebrew formula failed due to command missing. Thanks!
error log as below:
  ==> git add haunted house
  ==> git commit -a -m Initial Commit
  [master (root-commit) e5075ad] Initial Commit
   2 files changed, 0 insertions(+), 0 deletions(-)
   create mode 100644 haunted
   create mode 100644 house
  ==> /opt/homebrew/Cellar/lab/0.24.0/bin/lab ls-files
  2022/03/14 07:33:38 root.go:201: No default remote found
  Error: unknown command "ls-files" for "lab"
  Run 'lab --help' for usage.

Hi @chenrui333 , ls-files is a git command and not a lab one. Until PR #809 (released with 0.25.0) the passthrough feature of lab was removed, meaning that commands not recognized by lab are no longer passed to git.
Another note is that the 0.25.0 tag is somewhat bogus release-wise, I'll probably have to delete it and recreate it due to a testing issue caused by misbehavior of our live testing repo :(. Stay tuned.

@chenrui333 feel free to review PR #836.


Can not set folder icons

Hello, thank you for the great work !
some of the icons for folders can not be set.
folder-actions
folder-effects
folder-facade

found the problem in the source code.  Had to use it like this folder-redux-actions.
cheers!


[SPARK-43443][SQL] Add benchmark for Timestamp type inference when use invalid value

What changes were proposed in this pull request?
When we try to speed up Timestamp type inference with format (PR: #36562 #41078 #41091). There is no way to judge whether the change has improved the speed for Timestamp type inference.
So we need a benchmark to measure whether our optimization of Timestamp type inference is useful, we have valid Timestamp value benchmark at now, but don't have invalid Timestamp value benchmark when use Timestamp type inference.

Why are the changes needed?
Add new benchmark for Timestamp type inference when use invalid value, to make sure our speed up PR work normally.

Does this PR introduce any user-facing change?
No

How was this patch tested?
benchmarks already are test code.

cc @MaxGekk

+1, LGTM. Merging to master.
Thank you, @Hisoka-X.

Thanks @MaxGekk


how to check client is live? java

i create about 20 account, then 3 hours not recived any response,
    private static class ResponseReceiver implements Runnable {
        public boolean isRun = false;

        @Override
        public void run() {
            while (true) {
                int resultN = nativeClientReceive(clientIds, eventIds, events, 100000.0 /*seconds*/);
                log.warn("resultN {}", resultN);
                for (int i = 0; i < resultN; i++) {
                    processResult(clientIds[i], eventIds[i], events[i]);
                    events[i] = null;
                }
            }
        }
}

this is tdlib code in  java

What do you mean by "not recived any response"?


programmatic keyboard focus to ColorPicker's hex field

ColorPicker has a private ExtendedColorPicker called picker. ExtendedColorPicker extends BasicColorPicker. BasicColorPicker has a private VisValidatableTextField called hexField. I'd like to be able to programmatically give keyboard focus to the hexField. However, because hexField is private, there's no way to get a reference to it in order to call
Stage.setKeyboardFocus() passing hexField (It also doesn't have name, so there's no way to search for it by name).
This issue is to request adding some way to get access to a reference to the hexField member in order to set the keyboard focus, or to add a method to ColorPicker to request that it set the keyboard focus to the hexField

I guess it makes sense to focus this field on show by default. Same for the FileChooser's selected file text field.

I'm not sure focusing by default would take care of all relevant use-cases. For example, imagine I want to add the hex field to a list of Actors that I'd cycle focus through with the tab button. I'd need to be able to get a reference to the field in order to focus on it in response to certain user inputs.

I've added method for focusing the hex field.


If loadStore returns current state, the STATE_LOADING_DONE action never gets called

It seems if I don't have anything in localStorage, the loadStore returns currentState, but never fires the STATE_LOADING_DONE action.
const loadStore = (currentState) => {
  return new Promise(resolve => {
    AsyncStorage.getItem('state')
      .then(state => {
        if (state === null) return currentState;
        const parsedState = JSON.parse(state);
        resolve({ ...currentState, ...parsedState });
      });
  });
}

  const appReducers = combineReducers({
   ...reducers
    asyncInitialState: asyncInitialState.innerReducer
  });

  const rootReducer = (state, action) => {
    if (action.type === 'AUTH_SIGNOUT') {
      const { initialState } = app;
      state = {
        app: {
          ...initialState,
          persistedData: state.app.persistedData
        }
    }
    return appReducers(state, action);
  }

const reducer = asyncInitialState.outerReducer(rootReducer);

createReduxStore(
    reducer,
    applyMiddleware(
      asyncInitialState.middleware(loadStore),
      thunkMiddleware
    )
  );

I believe this is because I dont resolve currentState.
if (state === null) return currentState;

to
if (state === null) return resolve(currentState);


Target linuxArm64

I am trying to build for the Raspberry Pi and therefore setting target to linuxArm64.
But that gives me build time error:
Execution failed for task ':compileKotlinLinuxArm64'.

Could not resolve all files for configuration ':linuxArm64CompileKlibraries'.
Could not resolve com.soywiz.korlibs.klock:klock:1.11.14.
Required by:
project :
Unable to find a matching variant of com.soywiz.korlibs.klock:klock:1.11.14:

If we can crosscompile this or having an arm64 on github actions we could support this

The Kotlin docs say: "Linux MIPS targets (linuxMips32 and linuxMipsel32) require a Linux host. Other Linux targets can be built on any supported host;"

https://github.com/korlibs/klock/commit/9c0c4e3c3acceb352c8b09bbc558af5d97926e84


Clarify the type of "address" triggers applies to

The proposal is that triggers match on virtual addresses (which are equivalent to physical in some scenarios). But this is not clear in the specification either way.

Clarified that matches apply to virtual addresses in b436d77


Adding contrib

Hi,
Would it be possible to add contrib packages to this image or perhaps on another tag?
The standard postgres image comes with most of them all compiled. I only need ltree and cube currently but it might be better to compile them all.
If not I can create a new image based off of this one but I would rather use this if possible.
Thanks

Unsure; there are rather a lot… I don't really want to make the image bloated or take far longer to compile, unless there's enough of a reason to do so. PostgreSQL itself coming with most of these extensions enabled is a compelling reason (do you perhaps have a link?).
Another tag is perhaps tempting, otherwise—but then there'd be double the amount of things to test prior to release.
Do you know if anyone else is in favour of this proposal? :)

You right there quite a few and some (dblink being an example) don't seem to work with postgres xl. I don't think anyone else needs this at the moment and the helm chart does let you specify your own image so I can just use my own one for the time being. I guess if more people need this it would make sense to add some.


Wait the kafka ready to apply global hub addon

Signed-off-by: myan<EMAIL_ADDRESS>Ref: https://issues.redhat.com/browse/ACM-7570

/retest

The bug happens after the initialization. So the fix is not correct.


Option to invoke wallet creation page directly.

Is your feature request related to a problem? Please describe.
It is not really a problem but a great way for non-crypto users to choose between options of "Create a wallet" or "Connect wallet"
Describe the solution you'd like
import { useConnectModal } from '@web3modal/react'

// Usage
const { isOpen, open, close, createWallet } = useConnectModal()

// Returns
interface Return {
  isOpen: boolean
  open: () => void
  close: () => void,
  createWallet: () => cb
}

Describe alternatives you've considered
Use the same open with a different CTA

Just to confirm, is this the screen you are referring to?

@IljaDaderko Yes the same screen.

This has now been added via options in modal's open method https://docs.walletconnect.com/2.0/web3modal/html-js/actions#web3modalopenmodal


Ansible 2.4 deprecates ‘include’ in favor of ‘import_*’ and ‘include_tasks’

Description
Since it seems we have essentially upgraded our deploy process to use Ansible 2.4.*, this PR goes through the various ansible files and replaces use of ‘include’ with use of ‘import_playbook’, ‘import_tasks’, or ‘include_tasks’ dependent upon the individual situations.
It eliminates the ugly warning Ansible 2.4 had been printing during the deployment process (hopefully without introducing any new ugliness).
Currently the PR also includes a .gitignore change that is also separately in PR #3456
Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[X] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[X] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[X] I signed an Apache CLA.
[ ] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Closes https://github.com/apache/incubator-openwhisk/issues/3345

Re-based to remove the .gitignore change addressed instead in #3456

This should probably get a PG for good measure. LGTM otherwise.

Hmm, seeing an error in the PG while initdb.yml is running.
TASK [include] *****************************************************************
Wednesday 21 March 2018  16:34:57 -0400 (0:00:00.635)       0:00:00.817 *******
fatal: [ansible]: FAILED! => {"reason": "'openwhisk_home' is undefined"}

'openwhisk_home' is undefined
	to retry, use: --limit @/home/cusina/workspace/Playground3/blue/ansible/initdb.retry

PG2 2043 ⏳

PG3 2055 :large_blue_circle:

Rebase to master without changes.  PG3 2055 should still be valid.


[security block power] Can cypher blocks run at the same time and spike chip power?

 It is assumed that these blocks run rarely, so preventing a worst case power condition is deemed desirable.

@tjaychen @zi-v @martin-lueker @cdgori @senelson7

@moidx
@gkelly
ah i think when we originally thought about this, the idea was more to manage it using software.
None of the crypto blocks (with the exception of es / csrng which run in the background) activate by themselves, and all need to be marshalled by software.
So my hope at least is that we will manage it at that level.
Let me know what you guys think.

An interface between entropy_src and csrng has been added to prevent power spikes, which basically prevents sha3 in ES and AES cipher core in csrng from running at the same time.


Chained search return an error about multiple resource type, even if only 1 is possible (patient.identifier)

Describe the bug
While playing around using this FHIR Server as a backend to a XDS Registry, is was observed that the handling of chained parameters seems cause a unexepcted behavior. Resource "DocumentReference" contain a search parameter "patient" which is already restricted by the spec to the Patient resource. When using a chained search here (e.g. "patient.identifier"), the MS FHIR Server complain about "multiple" possible resource types on this search paramter. Other FHIR Server like Hapi or Firely work as expected.
FHIR Version?
R4
Version used
Docker image from "mcr.microsoft.com/healthcareapis/r4-fhir-server" (4.0.128)
Data provider?
SQL Server
To Reproduce
Steps to reproduce the behavior:

Trigger a FHIR Query on DocumentReference resource with a chained search parameter, e.g. /DocumentReference?patient.identifier=urn%3Aoid%3A2.9<IP_ADDRESS>.4%7CIPF-1714920157063

Expected behavior
SearchResponse is successful and return the expected results.
Current workaround
Use a chained search with explicit resource type definition, e.g. "patient:Patient.identifier" instead of "patient.identifier"
Actual behavior
Server response with a http 403 containing the following error message:
<?xml version="1.0" encoding="utf-8"?><OperationOutcome xmlns="http://hl7.org/fhir"><id value="ef85d13d-804b-4074-87d3-3a92c19640a8" /><meta><lastUpdated value="2024-05-05T14:42:39.4336098+00:00" /></meta><issue><severity value="error" /><code value="invalid" /><diagnostics value="The reference search parameter 'patient' refers to multiple possible resource types. Please specify a type in the search expression: patient:Patient or patient:Group" /></issue></OperationOutcome>

@EXPEkesheth - thank you for your response. Do you have any further details here? Is this limitation independed from the data provider?
I assume the workaround is to add the ResourceType if there is only 1 resource type that is referenced and to split the query into multiple if more than 1 Resource is possible?
While testing the FHIR Server, i experience, that the ":identifier" modifier seems to be also not supported? E.g. when searching " GET [base]/Observation?subject:identifier=http://acme.org/fhir/identifier/mrn|123456" like mentioned in the fhir spec, i get a error "Modifier 'Identifier' is not supported for search parameter 'subject'."
Is there a list of known limitations in MS Fhir server documented?

@Thopap - This page provides details on supported modifiers and search result parameters.
Azure FHIR server does not support :identifier modifier today.
Please let me know if you have any additional questions

Item for tracking the issue reported: #AB120154


updated reusable variables

changes made for issue no #2919

Why:

Closes [issue link]
What's being changed:

Check off the following:

[x] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

@theerapong2425

@janiceilene where I will get those
Instance .Can I get one example .I m not getting those instances for 3 fix

@StarTrooper08 You can find an example of the three of them together here:
https://github.com/github/docs/blame/main/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md#L18-L20
What we need for you to do is to find all instances of this pattern in the entire project and change it to the second pattern as described in this comment. The most efficient way to do that is to make the changes with a text editor on your local computer rather than through the GitHub website. If you're unfamiliar with how to perform this task in your text editor, you'l have to consult your editor's documentation, specifically "Find in Files" or "Find in Project" is what the feature is typically called in most editors.
I hope that helps!

Thanks ,I should start working on it now.

@janiceilene I have done with few changes for instances mentioned. Work is in progress.
I will have pr in few days

Awesome @StarTrooper08! Thanks for the update 🎉

So far I have done with this much work.
And I have one question only were the 3 instances that are as follows :
```
{% data reusables.profile.access_profile %}
{% data reusables.profile.access_org %}
{% data reusables.organizations.org_settings %}

Should be replaced with this right :

{% data reusables.profile.access_org %}
{% data reusables.organizations.org_settings %}

And if I get something like this should I replace those 3 from here too??

![githubchanges.PNG](https://user-images.githubusercontent.com/72031540/114489613-0f5cc280-9c31-11eb-8bb3-5b22051198c5.PNG)

@StarTrooper08 That's exactly right! If you get a big list that starts with the three reusables
{% data reusables.profile.access_profile %}
{% data reusables.profile.access_org %}
{% data reusables.organizations.org_settings %}

you should replace the three reusables with the two updated ones
{% data reusables.profile.access_org %}
{% data reusables.organizations.org_settings %}

and leave everything else in the list as it is. Thank you for continuing to work on this PR 🎉

Okay👍

changes made for issue no #2919
Why:
Closes [issue link]
What's being changed:
Check off the following:
* [x]  I have reviewed my changes in staging. (look for the **deploy-to-heroku** link in your pull request, then click **View deployment**)

* [x]  For content changes, I have reviewed the [localization checklist](https://github.com/github/docs/blob/main/contributing/localization-checklist.md)

* [x]  For content changes, I have reviewed the [Content style guide for GitHub Docs](https://github.com/github/docs/blob/main/contributing/content-style-guide.md).

<EMAIL_ADDRESS>

It looks like this was made obsolete by #5538, so I'm going to close it. If I've misunderstood, please let me know!


Mobile-friendly design?

Hey @mcchrish, thanks so much for the issue report 😅 !
We are currently in the process of adding mobile support for this app. It should be ready to go some time next year, and we will let you know as soon as that happens.
Thank you!

That's great to hear. In the meantime, is there an equivalent app for android? any way to run tests from an android device at all?

Hey @theHilikus thanks for the question!
As of now there is no Twilio Video Diagnostics app for android or iOS. This app can only be used via web browser (either on your desktop or mobile device when we implement the designs).
That being said, once we have the mobile designs in place for this app, users should be able to run these tests on an android device using any of the supported browsers.
It is on our roadmap to implement mobile designs in the new year, so stay tuned!
Thank you and happy new year!

Hey @mcchrish and @theHilikus thank you for your patience!
Mobile support is finally available for the Video Diagnostics Application! 🎉  As long as users are accessing the application through any of our supported browsers, they should be able to successfully view and run the tests as they would via desktop.
Please let us know if you have any questions or run into any issues. Thanks again!


Language not making it's way to RSS

I've read the readmes and examples to make an aggregate podcast feed composed of several other podcasts. Everything works as intended, but iTunes will not validate my feed because the language is missing. I have tried "language": "en" or "language": "en-us" right beneath my description in my feed config, but it never makes it way over to the RSS feed.
Any guidance for me?

I was able to get around this for now by adding language to custom elements. It worked that way but it feels like a hack.


Implement BMC and Network API Endpoints

Provisioner should expose an API endpoint to be able to perform CRUD operations on BMCs.
Provisioner should expose an API endpoint to be able to perform CRUD operations on Networks.

The purpose of this request is to be able to automate the bring up of a mr-provisioner deployment. For this to happen we also need to create a token for the default user (or be able to generate a token from the API) and provide an api endpoint to read it.


Ingestion of old credible sets from old OTG

As part of the validation we discussed the ingestion of old credible sets from old OTG.
These CSs will be coloclized with the new one as part of scientific validation process.
We need to check whether it is possible or not.

[ ] Ingest study index
[ ] Ingest credible sets

I suggest to cancel it since it is not relevant anymore.


Toggle monthly leaderboards

I didn't get to enabling monthly leaderboards after my work trial was over (I enabled daily/weekly/alltime). The cache has been filled out for a while now, this toggles it on.

I wonder if maybe the tabs should be in the opposite order? Daily, Weekly, Monthly, All time?


RuntimeError: /usr/local/opt/libtool not present or broken

when i run flutter doctor, then there is some error about iOS toolchain
[!] iOS toolchain - develop for iOS devices (Xcode 9.2)
✗ libimobiledevice and ideviceinstaller are not installed. To install with
Brew, run:
brew update
brew install --HEAD usbmuxd
brew link usbmuxd
brew install --HEAD libimobiledevice
brew install ideviceinstaller
✗ ios-deploy not installed. To install with Brew:
brew install ios-deploy
✗ CocoaPods not installed.
CocoaPods is used to retrieve the iOS platform side's plugin code that
responds to your plugin usage on the Dart side.
Without resolving iOS dependencies with CocoaPods, plugins will not work
on iOS.
For more info, see https://flutter.io/platform-plugins
To install:
brew install cocoapods
pod setup
[✓] Android Studio (version 3.0)
when i run brew install --HEAD usbmuxd ,there is error:
Error: An exception occurred within a child process:
RuntimeError: /usr/local/opt/libtool not present or broken
Please reinstall libtool. Sorry :(

@Alan201601
Sad to hear that, however, it seems to be a libimobiledevice related problem.
I think https://stackoverflow.com/tags/flutter should be a better place to ask this kind of flutter support questions.
Closing this issue now. Feel free to file new issues if you find other flutter problems.


[Provider Audit] provider.mylibra.org

Prerequisite Steps:
1. Make sure your provider has community provider attributes:
I have those attributes.

2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)
It points to my public IP.

3. Please make sure your Akash provider doesn't block any Akash specific ports.
I have necessary ports open on my worker node.

Leave contact information (optional)
I'm on discord: @peper1415

Signed the provider. (tx hash 4288BB9F14C77EA27EEE727A814E3A52C4E206CF4FD205D6F83643F39746AFF3).
tested GPU deployment (dseq 14008582)

provider bids OK
creates deployment  OK
lease-shell, lease-logs, lease-events OK
can see the GPU:

root@app-657cb55dd-ccwcz:/# nvidia-smi -L
GPU 0: NVIDIA GeForce RTX 3070 (UUID: GPU-f88deec8-fb50-605e-edbc-abe91c77221e)

nodePort OK
ingress OK
speedtest OK

root@app-657cb55dd-ccwcz:~# speedtest --secure
Retrieving speedtest.net configuration...
Testing from Multi Media (<IP_ADDRESS>)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by Sptelek Sp. z o.o. (Zbaszyn) [71.36 km]: 54.874 ms
Testing download speed................................................................................
Download: 230.96 Mbit/s
Testing upload speed......................................................................................................
Upload: 55.96 Mbit/s

disk test OK

root@app-657cb55dd-ccwcz:~# curl -sL yabs.sh | bash -s -- -ig
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
#              Yet-Another-Bench-Script              #
#                     v2023-11-30                    #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #

Thu Dec  7 10:04:23 UTC 2023

Basic System Information:
---------------------------------
Uptime     : 0 days, 5 hours, 17 minutes
Processor  : Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
CPU cores  : 48 @ 2699.769 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 251.9 GiB
Swap       : 0.0 KiB
Disk       : 1.9 TiB
Distro     : Ubuntu 22.04.3 LTS
Kernel     : 5.15.0-89-generic
VM Type    :
IPv4/IPv6  : ✔ Online / ❌ Offline

IPv4 Network Information:
---------------------------------
ISP        : Multimedia Polska S.A.
ASN        : AS21021 Multimedia Polska Sp. z o.o.
Host       : MMP
Location   : Gorzów Wielkopolski, Lubusz (08)
Country    : Poland

fio Disk Speed Tests (Mixed R/W 50/50) (Partition overlay):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 928.00 KB/s    (232) | 11.63 MB/s     (181)
Write      | 964.00 KB/s    (241) | 12.14 MB/s     (189)
Total      | 1.89 MB/s      (473) | 23.77 MB/s     (370)
           |                      |
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 44.83 MB/s      (87) | 61.19 MB/s      (59)
Write      | 47.45 MB/s      (92) | 65.68 MB/s      (64)
Total      | 92.28 MB/s     (179) | 126.87 MB/s    (123)

YABS completed in 2 min 24 sec

There is one moment where I've got no bid for the other dseq 14008679 (with no GPU); followed up on this with peper1415 on Discord.


Release 0.51.1 checklist

numba

[x] Merge to master:

[x] No PRs pending

[x] Cherry-pick PRs:

[x] https://github.com/numba/numba/pull/6141
[x] https://github.com/numba/numba/pull/6146
[x] https://github.com/numba/numba/pull/6147
[x] https://github.com/numba/numba/pull/6153
[x] https://github.com/numba/numba/pull/6168

[x] merge change log changes

[x] https://github.com/numba/numba/pull/6171

[x] Cherry-pick change log:

[x] https://github.com/numba/numba/pull/6171

[x] annotated tag 0.51.1 on release branch
[x] build conda packages on buildfarm
[x] build wheels (3.6, 3.7, 3.8)
[x] upload wheels and sdist to PyPI
[x] Verify packages uploaded to Anaconda Cloud
[x] upload 0.51.1 docs, update "latest" link (is this now automatic since ReadTheDocs?)
[x] Send announcement
[x] Post link to twitter

Post release:

[x] Ping Anaconda distro team for build out.

🎉


Enable SPI documentation and add API doc link

Bug/issue #, if applicable: None
Summary

Add .spi.yml file to make SwiftPackageIndex build documentation for this package.
Update README.md to add a link pointing to the corresponding link. (The link will be available on the next day after the PR is merged.)

See https://github.com/apple/swift-algorithms/blob/main/.spi.yml

Dependencies
None
Testing
None
Checklist

[x] Ran the swift test and it succeeded
[x] Updated documentation if necessary

Future work
After this PR, we'll only get the basic docc documentation support.

[ ] Add SystemPackage.docc in Sources/System to adjust the doc page.

@swift-ci please test

@swift-ci please test

@Kyle-Ye would you kindly update the description providing more context and motivation for the change? Thanks!

@Kyle-Ye would you kindly update the description providing more context and motivation for the change? Thanks!

Done. Do you think we should address the "Future work" part in this PR?

IMO no need to get the PR bigger than it is now, let's wait for feedback from maintainers first.


Lightweight Python components

The goal of this issue is to let user define custom components in Python only instead of having to build a complete docker component with component spec.

Original description:
The Dockerfile of most components is identical, but the user still needs to provide the whole component structure to create a component, which introduces unnecessary complexity.
I see two options to do this:

Built the custom user code on top of a base image and use it like a docker component.
Run the base image and provide the custom user code as an argument. Any additional dependencies are installed at runtime.

In both cases, we could make the base image configurable by the user.
The first option has some downsides:

We need access to a user container registry to push to
The base image would still need to be pulled before building and then pushing, which can take some time

The second option also has some downsides:

Installs need to happen every time at runtime.
It might be hard to pass complex code structures via argument.

We could have a look at how Kubeflow's lightweight Python components are implemented.
We might also be able to generate the component spec from the Python code:

Arguments could be inferred by inspecting the __init__ method.
If we find a way to typehint dataframes, we could also infer the consumes and produces section. Tools like Pandera could be helpful in this.

### Tasks
- [ ] https://github.com/ml6team/fondant/issues/750
- [ ] https://github.com/ml6team/fondant/issues/751
- [ ] https://github.com/ml6team/fondant/issues/752
- [ ] https://github.com/ml6team/fondant/issues/753
- [ ] https://github.com/ml6team/fondant/issues/754
- [ ] https://github.com/ml6team/fondant/issues/755

We will need to be strict with the lightweight and clearly decide what it can and can't do. Otherwise it will become very complex very fast. We also need to think about how easy it would be to convert (for a user) a lightweight component to a real custom component (and a reusable one).
I'm a bit concerned these will become the first class way of doing things which makes sense since it the easiest but it will unload a lot of complexity to the fondant side.

I think it will indeed become the default way to run custom code, but I believe we need to make that easier to make Fondant more useful. Moving from a Lightweight Python component to a Docker component should only be needed when a user wants to make the component reusable or runs into a limitation of the Lightweight Python component.
I would remove as many limitations as possible, but can see the following:

Everything should be encapsulated in the Component class. Probably even non-Fondant imports (Fondant imports could already be needed to define the class, we can add those ourselves like kfp does.
Only support Python dependencies. If a component needs non-Python dependencies, it needs to be dockerized. This will allow us to be more flexible about which base docker image to run the component on or even run it outside of docker (eg. with a VenvRunner).

Moving from a Lightweight Python component to a reusable Docker component should be quite straightforward since the Python code can stay the same. The user will need to add a component specification and Dockerfile, and build it and make it available for remote runners.
I think the additional complexity on the Fondant side can be limited and best effort. Eg. we can try to infer types so the user doesn't need to define the consumes and produces arguments, but they can still do that as a fallback when inference does not succeed for some reason.