Could not import azure.core python package.

So I setup a fresh virtual environment with Python 3.10 and started messing around. I got my cookie token from chatGPT and placed it in  the .env file.
I installed all of the requirements. I had to use faiss-cpu instead of faiss-gpu. All good.
I start python autogpt.py. It tells me Could not import azure.core python package.
But it still put me in the menu but if I select ChatGPT it complains about a lack of a huggingface token:
Select the model you want to use (1, 2, 3 or 4)
 1) ChatGPT
 2) HuggingChat
 3) BingChat
 4) Google Bard
 5) HuggingFace
 >>> 1
Traceback (most recent call last):
  File "C:\pyenv310freeautogpt\Free-Auto-GPT\autogpt.py", line 116, in <module>
    raise ValueError(
ValueError: HuggingFace Token EMPTY. Edit the .env file and put your HuggingFace token

I fixed Could not import azure.core python package.  by installing it with pip install azure-core but I still have that traceback. So I guess the huggingface token is mandatory even if I use chatGPT?

Ok clearly the huggingface token was mandatory. Closing this


Duplicate module

Duplicating a module creates n copies of the module with the exact same field datas, same joint placement, etc.
The only difference should be the name of the module: It should include an index number to avoid duplicate names.
Don't use the metadata['id'] for the index but add it directly to the metadata['base_name'].

Clicking the Duplicate button duplicates all the selected modules once and not n times
closed by 34a50da65bcb23550f232df351e11458306f4663


[rom_ctrl] Fix ECC generation in testbench and pass through integrity data properly

The first two commits fix the DV side (ensuring that the data is randomized in a way that gives valid ECC checksums). This is needed because the smoke test expects those ECC checksums to be valid in TL transactions, but (as of the 3rd commit) we're now passing through whatever was stored in the ROM.
Fixes #9536.

@rswarbrick for #9536 i think the original intent was to solve it through window data integrity passthrough.  Please see here (https://github.com/lowRISC/opentitan/blob/master/hw/ip/otbn/data/otbn.hjson#L493).
Again this is a result of me not yet updating the transmission integrity documentation..but could you give that a try and see if it achieves what you need? The basic idea is that the place of the data integrity generation gets moved around depending on whether the windowed region passes through integrity directly or needs to have integrity generated for it.
I swear I will work on documenting all of this better at some point.

Ahah! That definitely sounds like the right thing to do (assuming we decide to carry on generating and using the reg_top. This PR is still needed (because we have to fix the testbench to avoid breaking things when we actually start passing the integrity bits through). But I'll change the last commit to specify that in the hjson instead.
I wonder whether it would make sense to require that flag to be explicitly set to true or false if a device has a window. Seems like it would make it a bit harder to shoot oneself in the foot! And, as you say, this does look like a good candidate for a directed test (or maybe a formal connectivity test?).

@tjaychen, @msfschaffner: Ping!

P.S @weicaiyang I think this type of issue does point to the fact that we need to create directed test cases on the blocks that SHOULD be passing integrity through directly. Ie, backdoor modify the integrity, and see if it actually fails. I think these tests can be on the block levels themselves, what do you think? The ones this would mainly apply to are probably otbn, flash_ctrl, sram_ctrl, rom_ctrl

I think this also applies to hosts like Ibex, where the ECC should be passed through into and from the regfile.

@tjaychen, @msfschaffner: Ping!

Pong! Sorry for the delay & LGTM

P.S @weicaiyang I think this type of issue does point to the fact that we need to create directed test cases on the blocks that SHOULD be passing integrity through directly. Ie, backdoor modify the integrity, and see if it actually fails. I think these tests can be on the block levels themselves, what do you think? The ones this would mainly apply to are probably otbn, flash_ctrl, sram_ctrl, rom_ctrl

This is discussed in #9546

I think this also applies to hosts like Ibex, where the ECC should be passed through into and from the regfile.

Agree. We have a test in top-level for it


List environments and processes

Parent issue
Closes #6
Closes #7
Technical implementation details
I added inquirer as suggested by the oclif docs to prompt the user for an environment or running process for the start and stop command respectively.
If the user does not specify an index or name in the command, the user will be presented a list of environments in the selected file (or an error if there are no environments) which he/she can choose from and directly select.
If the user does not specify a pid or process name, he/she will be prompted for selecting a process from a list of currently running processes. Hence, 'all' is no longer the default option for the stop command.

@255kb Thanks for the feedback! Would be great if you could have a look at the tests, I will look at how we can reuse the data best :)


Windows master list:

List of issues / suggestions for Windows configuration. Action item is to automate these or document them.

http://vim.wikia.com/wiki/Fix_system_path_for_Vim_launched_from_Windows_7_taskbar
https://www.vim.org/scripts/script.php?script_id=2596
http://vim.wikia.com/wiki/Launch_files_in_new_tabs_under_Windows
http://vim.wikia.com/wiki/Maximize_or_restore_window
Bundle esy cygwin/mingw environment even for use with GVim.
http://vim.wikia.com/wiki/Set_Vim_as_the_default_editor_for_unknown_file_types_in_Windows
https://www.vim.org/scripts/script.php?script_id=5535
https://github.com/dreadnaut/vim-bargreybars
vim-shell dll (supposedly not only hides window decorations in full screen but also integrates better with external shell commands on windows) https://www.vim.org/scripts/script.php?script_id=3123

Navigating menus:
(I actually wish there was a plugin like this for MacOS. Maybe we can embed AHK inside of an app distribution without stepping on other AHK installs https://hotkeyit.github.io/v2/docs/AutoHotkeyDll.htm ).

https://autohotkey.com/board/topic/91067-window-menu-search/ (A utility for mac could be built using menudump ).
https://autohotkey.com/board/topic/7771-extracting-menus/
https://autohotkey.com/board/topic/45298-removing-the-menu-bar-on-a-window/
Possibly useful for docking utility windows inside of gVim (https://autohotkey.com/board/topic/8142-setparent-function-make-a-gui-belong-to-another-window/)

Fonts:

https://stackoverflow.com/questions/235671/how-do-i-add-a-font-in-gvim-on-windows-system

Packaging:

Use cygwrapper by default for box global binary but first intelligently detect if in cygwin environment.

Utilities:

Probably want to include xolox's utilities especially the shell utilities, but look at the other usages here which help unify windows/unix environments.

https://github.com/drmikehenry/vim-fontdetect


[BEAM-8383] Add metrics to the Python state cache

Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

I think this is ready to go. Also see https://jira.lyft.net/browse/STRMCMP-597

The metrics ran 10 days on beamperf without any problems. Also checked that the metrics are reported correctly after an update with upstream changes. Merging.


Don't use accessor as Keys.

Describe the bug
v.7.0.0-alpha.36
Warning logs
backend.js:6 Warning: Encountered two children with the same key, `cell_1_account`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.
    in tr (created by Table)
    in tbody (created by Table)
    in table (created by Table)
    in Table (created by Users)
    in div (created by Users)
    ...

It's not really a bug but just something that we should have control or at least have a way to not have these duplicate warnings whenever I'm using columns with the same accessor.
My use case for this is that we use JSON fields returned for some columns, and even though this works fine, but because I need to span the column into more than one (i.e. account.first, account.last, ...), I get warning about duplicate keys.
A quick solution that I did was to expand these fields in the array, making them unique keys, which is totally fine, just that it would be better not to depend on accessor as unique key values.
To Reproduce
Steps to reproduce the behavior:
Add more than one column with the same accessor name, i.e.
      {
        Cell: row => (
          <EditingJSONCell
            row={row}
            updateFunc={updateUser}
          />
        ),
        Header: 'first',
        accessor: 'account',
      },
      {
        Cell: row => (
          <EditingJSONCell
            row={row}
            updateFunc={updateUser}
          />
        ),
        Header: 'last',
        accessor: 'account',
      },

Expected behavior
Not use accessor as key values.
Desktop (please complete the following information):
N/A

I think we can use id for the keys. Basically. If the id is not present on a column, then the accessor becomes an id, so adding unique ids by ourselves solves this (at least, I managed to solve this issue for myself this way).

sounds good to me :) id is good. Thank you.

Just add a new key called id in your column definition.

Just add a new key called id in your column definition.

This is correct


EngineBlock 5.1.0 Debug tool returning "htmlspecialchars() expects parameter 1 to be string" error

Hello,
We recently upgraded to EB 5.1.0  and noticed the following error through the sp debug tool under Attributes after authenticating with our IdP:
Identifier	urn:oid:<IP_ADDRESS>.4.1.59<IP_ADDRESS>.10
Warning: htmlspecialchars() expects parameter 1 to be string, array given in /opt/openconext/OpenConext-engineblock-5.1.0/library/EngineBlock/View.php on line 204

The Array store in this variable looks like: Array ( [Value] => bd7057e48ad9b3cbdca7a305f14bf448c730d1c1 [SPNameQualifier] => https://engine.dev.openconext.org/authentication/sp/metadata )
I confirmed that version 5.0.0 works as expected:
Identifier	urn:oid:<IP_ADDRESS>.4.1.59<IP_ADDRESS>.10	bd7057e48ad9b3cbdca7a305f14bf448c730d1c1

PS: I tried to do a git bisect to figure out exactly which commit was the cause of this..  But I noticed that after running the composer prepare-env  as per the README, it's looking for a vendor folder that doesn't exist in the repo and winds up failing.
Thanks!

Thanks for the issue report.
This probably has to do with changes in how EPTIs are being dealt with in SAML2 (I think). I will try and replicate this.

I currently have no IdP that sends EPTI's. It goes wrong in the following bit of code:

                      <?php /** Single attribute value */ if (count($attributeValues)==1) { ?>
                      <?= EngineBlock_View::htmlSpecialCharsText($attributeValues[0]);?>
                      <?php } /** Multiple attribute values */ else { ?>

                          <?php foreach ($attributeValues as $value) { ?>

<?= EngineBlock_View::htmlSpecialCharsText($value); ?>

                          <?php } ?>

                      <?php } ?>

IIRC, SAML2 has been changed to interpret EPTIs as multiple values, so the $value could contain an array representation of that value.
If this is indeed the culprit, a fix would be to check if $value is an array. If it is, we are dealing with an EPTI and the appropriate string representation should be handed over to the htmlSpecialCharsText method.

Awesome.  Thanks for the quick response guys.
Let me know if there's any testing you'd like us to do.. We're more than happy to help.


Changed the output format

As discussed with @nicoddemus and @tadeu , I am modifying the output of the pytest-replay to write more information which might be useful when we are dealing with some tests that can interfere in each other.
the new output format is explained in the README.rst, but is basically:
    {"nodeid": "test_foo.py::test[1]", "start": 0.000}
    {"nodeid": "test_foo.py::test[1]", "start": 0.000, "finish": 1.5, "outcome": "passed}
    {"nodeid": "test_foo.py::test[3]", "start": 1.5}
    {"nodeid": "test_foo.py::test[3]", "start": 1.5, "finish": 2.5, "outcome": "passed}
    {"nodeid": "test_foo.py::test[5]", "start": 2.5}
    {"nodeid": "test_foo.py::test[5]", "start": 2.5, "finish": 3.5, "outcome": "passed}
    {"nodeid": "test_foo.py::test[7]", "start": 3.5}
    {"nodeid": "test_foo.py::test[7]", "start": 3.5, "finish": 4.5, "outcome": "passed}
    {"nodeid": "test_foo.py::test[8]", "start": 4.5}
    {"nodeid": "test_foo.py::test[8]", "start": 4.5, "finish": 5.5, "outcome": "passed}

Cool, please take a look at my comments. +1

All requested changes were applied!

@nicoddemus
Could you please check if all the modifications were done correctly?

Yes, sure! I forgot about it :sweat_smile:
I will add it in a few minutes

1.2.0 released!
Thanks for the great work!

Thanks for reviewing it!


OFFSET requires an ORDER BY clause:

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
0.15.0
What's Wrong?
OFFSET requires an ORDER BY clause，能否不设置排序，因为设置之后直到超时也查不出数据
What You Expected?
不设置排序也能出结果
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[ ] I agree to follow this project's Code of Conduct

Can you describe the requirements in more detail?

不排序那分页查询数据就不确定了，执行2次结果不一样

不排序那分页查询数据就不确定了，执行2次结果不一样

不是有默认排序么

同问，我使用的是unique引擎，默认是有一个主键的，为什么不能在不指定orderby的时候按主键默认排序


Save the session-key as a unicode string in the db

The session-key should be saved as a string, not a byte string.

@posativ I believe I found the root cause this time. It seems that when creating a new database, what was put into the database for a session-key is actually a byte sequence, not a string. You didn't have this problem because you are using an old database, not newly created ones. This pull request should solve this problem.
print(binascii.b2a_hex(os.urandom(24))) gives b'1d794016f952ef113667f7428335866452e9711f2366acaf', which need to be decoded.
Thanks a lot for helping me debug this problem.

(Sorry for the spamming) In python 2, binascii.b2a_hex(os.urandom(24)) is enough to produce str, but in python 3, you have to do decoding, which also works for python 2.7. I have this problem because I created the database with the Python3 version.

Indeed, thanks for the debugging and the patch!


Page width changes when auth fails on login screen

Hello,
As can be seen on image below, the image seems to use width 100% on login screen the first time we access it:

But if auth fails, it seems to change it's width to 80%.

I believe it maybe related to the settings below:

But I believe it should use 100% when failing and sidebar isn't available.

Sorry for being late. I've missed this one.
I've tried with a fresh install and both the login page and the login failed page width was 80% when I set the width to 80%. Have you applied your own CSS?

No problem. There's no custom CSS, but the Sidebar is hidden through ACL to non-logged in users.
This also happens when a logged in user do logoff, as can be seen below.

There's a max-width property that isn't on the first time we access the page, but it's applied when the user do logoff or if he/she types the wrong login.

Thanks. The first page has a "mode_denied" class which is missing in the CSS. I've updated the theme. Could you try it?
Please be noted, 80% is the correct width, and 100% is the wrong width. So this patch makes the first-page width to 80%.

Hello. I'd applied your patch but the issue doesn't seem to be fixed. I only found CSS applied to sidebar height on your patch, didn't see any CSS specific to page width. In my case, I have a closed wiki and an ACL that limits the sidebar visibility to logged in users only. When accessing https://wiki.rnetworks.com.br/doku.php?id=start the "Permission denied" page shows with page content 100% width. When typing the wrong password or doing logoff, the page content resizes to 80% with the latest template version.

Apologies. I committed the wrong file. I've committed the correct one now. Could you try it?

It’s been a while since the last comment, I’m closing the issue. If you still have any problems, please reopen this issue or create a new one.

Oh, I didn't see that. Sorry. I tested it and I can confirm it's now 80% width as expected by you. Thank you!


[SPARK-49152][SQL][FOLLOWUP] DelegatingCatalogExtension should also use V1 commands

What changes were proposed in this pull request?

DelegatingCatalogExtension should also use V1 commands. Also make sure RepairTable use V1 command.
Why are the changes needed?

DelegatingCatalogExtension may also call HMS thus should use V1 command. RepairTable does not have an V2 implementation so should use V1 command.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing test case
Was this patch authored or co-authored using generative AI tooling?

No

@cloud-fan

also cc @yaooqinn  and @itholic (as the release manager)

thanks, merging to master/3.5!


Adding aws_redshift_snapshot_copy_grant to v1beta1 version

Description of your changes
Adding 1 resource in the redshift group:

[x] aws_redshift_snapshot_copy_grant

Fixes #407
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Manual:
aws_redshift_snapshot_copy_grant - can't run uptest because of receive an error "Resource aws_redshift_snapshot_copy_grant.test has lifecycle.prevent_destroy set, but the plan calls for this resource to be destroyed."

I haven't added an upjet.upbound.io/manual-intervention annotation because of this resource successfully applying and deleting, @sergenyalcin is it ok?

I haven't added an upjet.upbound.io/manual-intervention annotation because of this resource successfully applying and deleting, @sergenyalcin is it ok?

Did you observe that provisioning and deletion of this resource were successfully completed in manual tests? If it is the case we can do this

I haven't added an upjet.upbound.io/manual-intervention annotation because of this resource successfully applying and deleting, @sergenyalcin is it ok?

Did you observe that provisioning and deletion of this resource were successfully completed in manual tests? If it is the case we can do this

Yes, manually I've created and deleted the resource successfully.


getAllTransactions does not parse options properly

Description
When using the getAllTransactions with options following AllTransactionsOptions type to get only the safe txs that havent been executed yet. When changing the options, the results are not affected. The URL seems to be constructed correctly (I see it in the log) but for some reasons even changing the params in the URL does not seem to affect the number of results shown.
Not sure what I am missing ?
example:
const allTxs = await safeService.getAllTransactions(multisig, {
  executed: false,
  trusted: false,
  queued: true,
})

https://safe-transaction-mainnet.safe.global/api/v1/safes/0x9168EABE624e9515f3836bA1716EC1DDd4C461D4/all-transactions/?executed=false&limit=20&offset=20&queued=true&trusted=false
Environment

Safe Core SDK version:
Safe contract version:
Environment:

browser
non-browser

Steps to reproduce

create a ethers provider
initialize an eth adapter
initialize service with SafeApiKit
fetch all txs using options

const provider = await getProvider(chainId)
const ethAdapter = new EthersAdapter({
  ethers,
  signerOrProvider: provider,
})

// get Safe service
const safeService = new SafeApiKit({
  chainId,
  txServiceUrl: safeServiceURLs[chainId] || null,
})
const allTxs = await safeService.getAllTransactions(multisig, {
  executed: false,
  trusted: false,
  queued: true,
})

which gives
{
  count: 120,
  next: 'https://safe-transaction-mainnet.safe.global/api/v1/safes/0x9168EABE624e9515f3836bA1716EC1DDd4C461D4/all-transactions/?executed=false&limit=10&offset=10&queued=true&trusted=true',
  previous: null,
  results: [
...

Expected result
I will expect the already executed to be hidden when selecting executed: false but they are still returned by the API.

If you want to get the pending transactions you can use the getPendingTransactions method instead.


feat: Hide ion-header and ion-footer on keyboard open

Type: feat
Platform: all
In some screens, when you open the keyboard, the remaining space on screen is almost 0, when you have ion-header and, ion-footer.
Would be cool to have an option to hide ion-footer / ion-header on keyboard open.
I know I can use hide-on-keyboard-open class, but also need to clear ion-content top and css bottom properties.
A good usage would be:
<ion-header-bar hide-on-keyboard="true"> </ion-header> <ion-content> </ion-content> <ion-footer-bar hide-on-keyboard="true"> </ion-footer>

Hmm, well the keyboard plugin does provide some events for you to tap into and use an ng-if or ng-show.
https://github.com/driftyco/ionic-plugin-keyboard/#nativekeyboardshow
I think that this would be too specific of a thing to add to the framework, but all the pieces are there for you to makes something.


Compile error with GHC7.4

src/Data/CompactMap.hs:24:5:
    foldr' is not a (visible) method of class `Foldable'

src/Data/CompactMap.hs:27:5:
    foldl' is not a (visible) method of class `Foldable'

It seems that you edited the build constraints in hackage, and I am not seing which version isn't building. I just pushed a new version with proper lower bounds for base.

For the future, it's not necessary to push new versions if it's only the dependency edit, as the dependencies are (can be) edited (and you can edit dependencies bounds yourself too).
Especially with incorrect (too wide) bounds, pushing the new version doesn't help
Take for example pcre-utils. In complex setup, some other package might have mtl <2.2bound, so the solver would find a build plan with olderpcre-utils` - which will fail to compile.
To be clear, I opened the issues to notify that you'd need to correct bounds or/and code. As it's not obvious which GHC versions you want to support (setting up .travis.yml with e.g. https://github.com/hvr/multi-ghc-travis, testing GHCs you plan to support would make the fact more obvious)

Makes sense, thanks!


TypeError: init() got an unexpected keyword argument 'sim'

Hi everybody!
Thanks for releasing simHarness 1.0.0!
So I followed instructions to install simHarness with pyenv and poetry, I've created a ray cluster (ray start --num-gpus 1 --num-cpus 4 --head) and when I've typed "python3 main.py cli.mode=train" with original config.yaml (except for my own result path) and fire_harness.py modified to elude the circular importation of Harness, I've obtained this error:
(simharness3-py3.9) dbailleu@L-FRE-3KQMLX3:~/[...]/simharness$ python3 main.py cli.mode=train
2023-12-11 16:09:22,302 WARNING deprecation.py:50 -- DeprecationWarning: `DirectStepOptimizer` has been deprecated. This will raise an error in the future!
/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/pydantic/_internal/_config.py:321: UserWarning: Valid config keys have changed in V2:
 'allow_mutation' has been removed
  warnings.warn(message, UserWarning)
2023-12-11 16:09:23,296 WARNING deprecation.py:50 -- DeprecationWarning: `build_tf_policy` has been deprecated. This will raise an error in the future!
2023-12-11 16:09:23,298 WARNING deprecation.py:50 -- DeprecationWarning: `build_policy_class` has been deprecated. This will raise an error in the future!
2023-12-11 16:09:23,934 INFO worker.py:1431 -- Connecting to existing Ray cluster at address: <IP_ADDRESS>:6379...
2023-12-11 16:09:23,940 INFO worker.py:1621 -- Connected to Ray cluster.
2023-12-11 16:09:24,312 INFO main.py:278 -- Configuration files for this job can be found at /home/dbailleu/[...]/data_dir/simharness/experiments/2023-12-11_16-09-23/hydra_output.
2023-12-11 16:09:24,328 INFO layers.py:81 -- Saving LandFire data to: /home/dbailleu/.simfire/landfire/2019/lf_120.52193_36.09493_120.47563370366066_36.04863370366067
2023-12-11 16:09:24,514 INFO layers.py:81 -- Saving LandFire data to: /home/dbailleu/.simfire/landfire/2019/lf_120.52193_36.09493_120.47563370366066_36.04863370366067
2023-12-11 16:09:24,592 INFO layers.py:81 -- Saving LandFire data to: /home/dbailleu/.simfire/landfire/2019/lf_120.52193_36.09493_120.47563370366066_36.04863370366067
2023-12-11 16:09:24,657 INFO layers.py:81 -- Saving LandFire data to: /home/dbailleu/.simfire/landfire/2019/lf_120.52193_36.09493_120.47563370366066_36.04863370366067
2023-12-11 16:09:24,756 WARNING algorithm_config.py:2558 -- Setting `exploration_config={}` because you set `_enable_rl_module_api=True`. When RLModule API are enabled, exploration_config can not be set. If you want to implement custom exploration behaviour, please modify the `forward_exploration` method of the RLModule at hand. On configs that have a default exploration config, this must be done with `config.exploration_config={}`.
/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/gymnasium/spaces/box.py:127: UserWarning: WARN: Box bound precision lowered by casting to float32
  logger.warn(f"Box bound precision lowered by casting to {self.dtype}")
/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/gymnasium/utils/passive_env_checker.py:141: UserWarning: WARN: The obs returned by the `reset()` method was expecting numpy array dtype to be float32, actual type: float64
  logger.warn(
/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/gymnasium/utils/passive_env_checker.py:165: UserWarning: WARN: The obs returned by the `reset()` method is not within the observation space.
  logger.warn(f"{pre} is not within the observation space.")
2023-12-11 16:09:24,786 WARNING algorithm_config.py:2558 -- Setting `exploration_config={}` because you set `_enable_rl_module_api=True`. When RLModule API are enabled, exploration_config can not be set. If you want to implement custom exploration behaviour, please modify the `forward_exploration` method of the RLModule at hand. On configs that have a default exploration config, this must be done with `config.exploration_config={}`.
2023-12-11 16:09:24,803 WARNING deprecation.py:50 -- DeprecationWarning: `ignore_worker_failures is deprecated, and will soon be a no-op` has been deprecated. This will raise an error in the future!
2023-12-11 16:09:24,803 WARNING deprecation.py:50 -- DeprecationWarning: `AlgorithmConfig.rollouts(recreate_failed_workers=..)` has been deprecated. Use `AlgorithmConfig.fault_tolerance(recreate_failed_workers=..)` instead. This will raise an error in the future!
2023-12-11 16:09:24,803 WARNING deprecation.py:50 -- DeprecationWarning: `AlgorithmConfig.rollouts(restart_failed_sub_environments=..)` has been deprecated. Use `AlgorithmConfig.fault_tolerance(restart_failed_sub_environments=..)` instead. This will raise an error in the future!
2023-12-11 16:09:25,372 WARNING deprecation.py:50 -- DeprecationWarning: `rllib/algorithms/simple_q/` has been deprecated. Use `rllib_contrib/simple_q/` instead. This will raise an error in the future!
/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/utils/from_config.py:197: RayDeprecationWarning: This API is deprecated and may be removed in future Ray releases. You could suppress this warning by setting env variable PYTHONWARNINGS="ignore::DeprecationWarning"
The `TBXLogger interface is deprecated in favor of the `ray.tune.tensorboardx.TBXLoggerCallback` interface and will be removed in Ray 2.7.
  object_ = constructor(*ctor_args, **ctor_kwargs)
(pid=32469) DeprecationWarning: `DirectStepOptimizer` has been deprecated. This will raise an error in the future!
(RolloutWorker pid=32469) /home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/pydantic/_internal/_config.py:321: UserWarning: Valid config keys have changed in V2:
(RolloutWorker pid=32469) * 'allow_mutation' has been removed
(RolloutWorker pid=32469)   warnings.warn(message, UserWarning)
(RolloutWorker pid=32469) 2023-12-11 16:09:30,906       WARNING deprecation.py:50 -- DeprecationWarning: `build_tf_policy` has been deprecated. This will raise an error in the future!
(RolloutWorker pid=32469) 2023-12-11 16:09:30,908       WARNING deprecation.py:50 -- DeprecationWarning: `build_policy_class` has been deprecated. This will raise an error in the future!
(RolloutWorker pid=32469) Exception raised in creation task: The actor died because of an error raised in its creation task, ray::RolloutWorker.__init__() (pid=32469, ip=<IP_ADDRESS>, actor_id=d31df7eb3a285eacb138b40f01000000, repr=<ray.rllib.evaluation.rollout_worker.RolloutWorker object at 0x7f2aa5c9a8e0>)
(RolloutWorker pid=32469)   File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/rollout_worker.py", line 397, in __init__
(RolloutWorker pid=32469)     self.env = env_creator(copy.deepcopy(self.env_context))
(RolloutWorker pid=32469)   File "/home/dbailleu/[...]/simharness/main.py", line 208, in <lambda>
(RolloutWorker pid=32469)     register_env(cfg.environment.env, lambda config: env_cls(**config))
(RolloutWorker pid=32469) TypeError: __init__() got an unexpected keyword argument 'sim'
(pid=32580) DeprecationWarning: `DirectStepOptimizer` has been deprecated. This will raise an error in the future! [repeated 4x across cluster] (Ray deduplicates logs by default. Set RAY_DEDUP_LOGS=0 to disable log deduplication, or see https://docs.ray.io/en/master/ray-observability/ray-logging.html#log-deduplication for more options.)
(RolloutWorker pid=32580) /home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/pydantic/_internal/_config.py:321: UserWarning: Valid config keys have changed in V2: [repeated 4x across cluster]
(RolloutWorker pid=32580) * 'allow_mutation' has been removed [repeated 4x across cluster]
(RolloutWorker pid=32580)   warnings.warn(message, UserWarning) [repeated 4x across cluster]
(RolloutWorker pid=32478) 2023-12-11 16:09:31,260       WARNING deprecation.py:50 -- DeprecationWarning: `build_tf_policy` has been deprecated. This will raise an error in the future! [repeated 3x across cluster]
(RolloutWorker pid=32478) 2023-12-11 16:09:31,262       WARNING deprecation.py:50 -- DeprecationWarning: `build_policy_class` has been deprecated. This will raise an error in the future! [repeated 3x across cluster]
(RolloutWorker pid=32580) Exception raised in creation task: The actor died because of an error raised in its creation task, ray::RolloutWorker.__init__() (pid=32580, ip=<IP_ADDRESS>, actor_id=2eeb5ab4963bb9aab2499d7d01000000, repr=<ray.rllib.evaluation.rollout_worker.RolloutWorker object at 0x7f065f58a8b0>) [repeated 4x across cluster]
(RolloutWorker pid=32580)   File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/rollout_worker.py", line 397, in __init__ [repeated 4x across cluster]
(RolloutWorker pid=32580)     self.env = env_creator(copy.deepcopy(self.env_context)) [repeated 4x across cluster]
(RolloutWorker pid=32580)   File "/home/dbailleu/[...]/simharness/main.py", line 208, in <lambda> [repeated 4x across cluster]
(RolloutWorker pid=32580)     register_env(cfg.environment.env, lambda config: env_cls(**config)) [repeated 4x across cluster]
(RolloutWorker pid=32580) TypeError: __init__() got an unexpected keyword argument 'sim' [repeated 4x across cluster]
2023-12-11 16:09:37,690 ERROR actor_manager.py:500 -- Ray error, taking actor 1 out of service. The actor died because of an error raised in its creation task, ray::RolloutWorker.__init__() (pid=32469, ip=<IP_ADDRESS>, actor_id=d31df7eb3a285eacb138b40f01000000, repr=<ray.rllib.evaluation.rollout_worker.RolloutWorker object at 0x7f2aa5c9a8e0>)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/rollout_worker.py", line 397, in __init__
    self.env = env_creator(copy.deepcopy(self.env_context))
  File "/home/dbailleu/[...]/simharness/main.py", line 208, in <lambda>
    register_env(cfg.environment.env, lambda config: env_cls(**config))
TypeError: __init__() got an unexpected keyword argument 'sim'
2023-12-11 16:09:37,690 ERROR actor_manager.py:500 -- Ray error, taking actor 2 out of service. The actor died because of an error raised in its creation task, ray::RolloutWorker.__init__() (pid=32470, ip=<IP_ADDRESS>, actor_id=42fbe9f15ccfd1fbabfb21cc01000000, repr=<ray.rllib.evaluation.rollout_worker.RolloutWorker object at 0x7f94883e98e0>)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/rollout_worker.py", line 397, in __init__
    self.env = env_creator(copy.deepcopy(self.env_context))
  File "/home/dbailleu/[...]/simharness/main.py", line 208, in <lambda>
    register_env(cfg.environment.env, lambda config: env_cls(**config))
TypeError: __init__() got an unexpected keyword argument 'sim'
2023-12-11 16:09:37,690 ERROR actor_manager.py:500 -- Ray error, taking actor 3 out of service. The actor died because of an error raised in its creation task, ray::RolloutWorker.__init__() (pid=32477, ip=<IP_ADDRESS>, actor_id=ce012a1fe6e82ee1bac1e8f401000000, repr=<ray.rllib.evaluation.rollout_worker.RolloutWorker object at 0x7f8d036728e0>)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/rollout_worker.py", line 397, in __init__
    self.env = env_creator(copy.deepcopy(self.env_context))
  File "/home/dbailleu/[...]/simharness/main.py", line 208, in <lambda>
    register_env(cfg.environment.env, lambda config: env_cls(**config))
TypeError: __init__() got an unexpected keyword argument 'sim'
2023-12-11 16:09:37,691 ERROR actor_manager.py:500 -- Ray error, taking actor 4 out of service. The actor died because of an error raised in its creation task, ray::RolloutWorker.__init__() (pid=32478, ip=<IP_ADDRESS>, actor_id=2d6bb8799851805e4df55d2e01000000, repr=<ray.rllib.evaluation.rollout_worker.RolloutWorker object at 0x7f3f0ceb2910>)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/rollout_worker.py", line 397, in __init__
    self.env = env_creator(copy.deepcopy(self.env_context))
  File "/home/dbailleu/[...]/simharness/main.py", line 208, in <lambda>
    register_env(cfg.environment.env, lambda config: env_cls(**config))
TypeError: __init__() got an unexpected keyword argument 'sim'
2023-12-11 16:09:37,691 ERROR actor_manager.py:500 -- Ray error, taking actor 5 out of service. The actor died because of an error raised in its creation task, ray::RolloutWorker.__init__() (pid=32580, ip=<IP_ADDRESS>, actor_id=2eeb5ab4963bb9aab2499d7d01000000, repr=<ray.rllib.evaluation.rollout_worker.RolloutWorker object at 0x7f065f58a8b0>)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/rollout_worker.py", line 397, in __init__
    self.env = env_creator(copy.deepcopy(self.env_context))
  File "/home/dbailleu/[...]/simharness/main.py", line 208, in <lambda>
    register_env(cfg.environment.env, lambda config: env_cls(**config))
TypeError: __init__() got an unexpected keyword argument 'sim'
2023-12-11 16:09:37,691 ERROR actor_manager.py:500 -- Ray error, taking actor 6 out of service. The actor died because of an error raised in its creation task, ray::RolloutWorker.__init__() (pid=32584, ip=<IP_ADDRESS>, actor_id=0410e303dd563ca1ce13eea001000000, repr=<ray.rllib.evaluation.rollout_worker.RolloutWorker object at 0x7fbd3ee8f8e0>)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/rollout_worker.py", line 397, in __init__
    self.env = env_creator(copy.deepcopy(self.env_context))
  File "/home/dbailleu/[...]/simharness/main.py", line 208, in <lambda>
    register_env(cfg.environment.env, lambda config: env_cls(**config))
TypeError: __init__() got an unexpected keyword argument 'sim'
2023-12-11 16:09:37,691 ERROR actor_manager.py:500 -- Ray error, taking actor 7 out of service. The actor died because of an error raised in its creation task, ray::RolloutWorker.__init__() (pid=32589, ip=<IP_ADDRESS>, actor_id=2d4a45925e6bb22f186add7a01000000, repr=<ray.rllib.evaluation.rollout_worker.RolloutWorker object at 0x7fca872ad8e0>)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/rollout_worker.py", line 397, in __init__
    self.env = env_creator(copy.deepcopy(self.env_context))
  File "/home/dbailleu/[...]/simharness/main.py", line 208, in <lambda>
    register_env(cfg.environment.env, lambda config: env_cls(**config))
TypeError: __init__() got an unexpected keyword argument 'sim'
2023-12-11 16:09:37,691 ERROR actor_manager.py:500 -- Ray error, taking actor 8 out of service. The actor died because of an error raised in its creation task, ray::RolloutWorker.__init__() (pid=32597, ip=<IP_ADDRESS>, actor_id=8c383224369e88932846e7ff01000000, repr=<ray.rllib.evaluation.rollout_worker.RolloutWorker object at 0x7f1defb5a940>)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/rollout_worker.py", line 397, in __init__
    self.env = env_creator(copy.deepcopy(self.env_context))
  File "/home/dbailleu/[...]/simharness/main.py", line 208, in <lambda>
    register_env(cfg.environment.env, lambda config: env_cls(**config))
TypeError: __init__() got an unexpected keyword argument 'sim'
Error executing job with overrides: ['cli.mode=train']
Traceback (most recent call last):
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/worker_set.py", line 157, in __init__
    self._setup(
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/worker_set.py", line 227, in _setup
    self.add_workers(
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/worker_set.py", line 593, in add_workers
    raise result.get()
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/utils/actor_manager.py", line 481, in __fetch_result
    result = ray.get(r)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/_private/auto_init_hook.py", line 24, in auto_init_wrapper
    return fn(*args, **kwargs)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/_private/client_mode_hook.py", line 103, in wrapper
    return func(*args, **kwargs)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/_private/worker.py", line 2522, in get
    raise value
ray.exceptions.RayActorError: The actor died because of an error raised in its creation task, ray::RolloutWorker.__init__() (pid=32469, ip=<IP_ADDRESS>, actor_id=d31df7eb3a285eacb138b40f01000000, repr=<ray.rllib.evaluation.rollout_worker.RolloutWorker object at 0x7f2aa5c9a8e0>)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/rollout_worker.py", line 397, in __init__
    self.env = env_creator(copy.deepcopy(self.env_context))
  File "/home/dbailleu/[...]/simharness/main.py", line 208, in <lambda>
    register_env(cfg.environment.env, lambda config: env_cls(**config))
TypeError: __init__() got an unexpected keyword argument 'sim'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/dbailleu/[...]/simharness/main.py", line 306, in <module>
    main()
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/hydra/main.py", line 94, in decorated_main
    _run_hydra(
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/hydra/_internal/utils.py", line 394, in _run_hydra
    _run_app(
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/hydra/_internal/utils.py", line 457, in _run_app
    run_and_report(
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/hydra/_internal/utils.py", line 223, in run_and_report
    raise ex
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/hydra/_internal/utils.py", line 220, in run_and_report
    return func()
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/hydra/_internal/utils.py", line 458, in <lambda>
    lambda: hydra.run(
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/hydra/_internal/hydra.py", line 132, in run
    _ = ret.return_value
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/hydra/core/utils.py", line 260, in return_value
    raise self._return_value
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/hydra/core/utils.py", line 186, in run_job
    ret.return_value = task_function(task_cfg)
  File "/home/dbailleu/[...]/simharness/main.py", line 284, in main
    algo = algo_cfg.build()
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/algorithms/algorithm_config.py", line 1092, in build
    return algo_class(
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/utils/deprecation.py", line 106, in patched_init
    return obj_init(*args, **kwargs)
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/algorithms/algorithm.py", line 517, in __init__
    super().__init__(
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/tune/trainable/trainable.py", line 169, in __init__
    self.setup(copy.deepcopy(self.config))
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/algorithms/algorithm.py", line 639, in setup
    self.workers = WorkerSet(
  File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/worker_set.py", line 179, in __init__
    raise e.args[0].args[2]
TypeError: __init__() got an unexpected keyword argument 'sim'
(pid=32597) DeprecationWarning: `DirectStepOptimizer` has been deprecated. This will raise an error in the future! [repeated 3x across cluster]
(RolloutWorker pid=32597) /home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/pydantic/_internal/_config.py:321: UserWarning: Valid config keys have changed in V2: [repeated 3x across cluster]
(RolloutWorker pid=32597) * 'allow_mutation' has been removed [repeated 3x across cluster]
(RolloutWorker pid=32597)   warnings.warn(message, UserWarning) [repeated 3x across cluster]
(RolloutWorker pid=32597) 2023-12-11 16:09:36,552       WARNING deprecation.py:50 -- DeprecationWarning: `build_tf_policy` has been deprecated. This will raise an error in the future! [repeated 4x across cluster]
(RolloutWorker pid=32597) 2023-12-11 16:09:36,553       WARNING deprecation.py:50 -- DeprecationWarning: `build_policy_class` has been deprecated. This will raise an error in the future! [repeated 4x across cluster]
(RolloutWorker pid=32597) Exception raised in creation task: The actor died because of an error raised in its creation task, ray::RolloutWorker.__init__() (pid=32597, ip=<IP_ADDRESS>, actor_id=8c383224369e88932846e7ff01000000, repr=<ray.rllib.evaluation.rollout_worker.RolloutWorker object at 0x7f1defb5a940>) [repeated 3x across cluster]
(RolloutWorker pid=32597)   File "/home/dbailleu/[...]/simharness/.venv/lib/python3.9/site-packages/ray/rllib/evaluation/rollout_worker.py", line 397, in __init__ [repeated 3x across cluster]
(RolloutWorker pid=32597)     self.env = env_creator(copy.deepcopy(self.env_context)) [repeated 3x across cluster]
(RolloutWorker pid=32597)   File "/home/dbailleu/[...]/simharness/main.py", line 208, in <lambda> [repeated 3x across cluster]
(RolloutWorker pid=32597)     register_env(cfg.environment.env, lambda config: env_cls(**config)) [repeated 3x across cluster]
(RolloutWorker pid=32597) TypeError: __init__() got an unexpected keyword argument 'sim' [repeated 3x across cluster]

My own config is on WSL2 but I've also tried on my personal Linux computer: same error.
I have no idea how to solve this.
I just can say that there is a “sim” argument in the definition of EnvContext in reactive.py line 164 (and also marl_reactive.py but not relevant here).
There is no “sim” argument in the __init__ of rollout_worker.py, but Envcontext is mentioned:
"validate_env: Optional[Callable[[EnvType, EnvContext], None]] = None," line 217 (file attached)
rollout_worker.zip
No idea if it's helping.
Thanks a lot for simHarness and thanks for your help solving this!

@dbailleul Thank you for the issue! My apologies on your experience so far with SimHarness. We are actively in the process of publishing our internal code here on GitHub, and there are a few more updates on the way before the code base is "ready to go".
For a timeline, you can expect the state of SimHarness to be bug free come this Wednesday. Thank you for your patience!

Hi @dbailleul, the updates in 56b6be8f2277019e2a8e5b8adf65a98f34b0d8e9 should resolve the issue (s) you are experiencing with SimHarness. Please make a new issue for any bugs, questions, comments, etc. as you use SimHarness. Thank you for the support!


Adds tests for rendering of PropertiesWrapper component

Fixes #132

Coverage remained the same at 0.976% when pulling aef979d7bec39d30c19fe0307c0c90e4c1389a61 on properties-wrapper into 8a08fdeb7781eec59f572f06ac136e49ee68847d on master.

Thanks, Josh!


Expose registered message types on generated code

Currently generated code registers with proto.RegisterType and we can retrieve the type based on a string name.  However, it is not possible to list all registered types.  The types map is there but not exposed.
I'd suggest

Add ListTypes() and ListEnums()  to golang/protobuf/proto to get all the type names.
Or add the above methods to the generated package to list local types.

This is something I'm looking at, but it would help to know what you're using the listing for.

I'm writing a data management service, and the data schemas are defined in proto files.  Our service accepts data in JSON format and stores them in Protobuf.  We want to expose what formats we accept (and possibly their definitions) via an API.  That's why we need to list types of one generated protobuf package.
I'm currently using a custom protoc plugin for this.  The plugin will list all types being compiled into a .go file.  It could be better if the official protoc-gen-go can generate this.

It seems like your application should use an explicit registry, where you mark each proto that you accept.  You can use the generated Descriptor() method to grab the FileDescriptorProto. This is the approach taken by gRPC, for instance.

The grpc example uses pb.RegisterXXXServer which is generated by the grpc plugin built into protoc-gen-go. I cannot embed my plugin into protoc-gen-go. I have to write my custom generator, which is somewhat hard to implement.
However, if the registered types could be exposed (which IMHO is very simple to implement), I don't have to write the custom generator anymore. This might be helpful to other users as well.
On the FileDescriptorProto part, yes I can get one FileDescriptorProto for one message. However my package is generated by several proto files (and this list is changing). This isn't an API to list all registered FileDescriptorProto neither.

You don't need to hook into protoc-gen-go.  gRPC uses this to add extra metadata, but if you just need a list of filenames, you can set up a registry yourself.  Slightly tweaking the code from gRPC:
var filenames map[string]bool

func register(msg proto.Message) {
  d := msg.(interface {
    Descriptor() ([]byte, []int)
  })
  desc, _ := d.Descriptor()
  fd := new(descriptor.FileDescriptorProto)
  if err := proto.Unmarshal(decompress(desc), fd); err != nil {
    panic(err)
  }
  filenames[fd.GetName()] = true
}

func init() {
  register((*mypb.Message)(nil))
}

// later in app...
for _, fname := range filenames {
  fdBytes := proto.FileDescriptor(fname)
  // ...
}

I realize that exposing the map is not a difficult change, but it does lock the package's implementation into always using a map as the data structure.  The file descriptor map is lists all of the file descriptors present at link-time.  The reason we generally don't export this is because that list can change depending on what protos your dependencies bring in, which can cause action-at-a-distance.  The benefit of the more explicit registry I propose in that code snippet is that it ensures that all of the types and files that you expect are linked in, because you have a reference in code, and doesn't bring in additional types.

Thanks for the detailed response.  However, my use case is that I don't want to reference all the types in my code. The protobufs I'm using are for user data, not the program itself. The definitions of the user protobufs are also changing rapidly. I'm willing to recompile the program every day (which can be done automatically) but do not want to touch the code that frequently.
Please feel free to close this issue if exposing registered types is not a good idea for general users.

Yes, this seems more dynamic that what we're aiming to support for general users.

@thinxer , if possible can you share the protoc plugin you use? i am also looking for something similar as you have asked for in this issue.
i want to be able to lookup the input and output types of an API by name.
since this info is not readily available in the generated pb.go code, i thought of using a protoc plugin to generate this information.
thanks in advance,

@thinxer Could you share how you retrieve the type based on a string name?


in.js:3: ERROR - Duplicate let / const / class declaration in the same scope is not allowed.

Hi,
I have an error while compile a js file with ES6 code:
java -jar closure-compiler-v20170409.jar --compilation_level ADVANCED_OPTIMIZATIONS --js_output_file=in.js out.js

in.js:3: ERROR - Duplicate let / const / class declaration in the same scope is not allowed.
class Storage {
      ^^^^^^^

1 error(s), 0 warning(s)

There is conflict name Storage with something as I guess.
If I rename, for example, to _Storage then compilation ends successfully.
"use strict";

class Storage {

}

It's conflicting with the Storage interface. Either wrap your class in an IIFE or rename it.

Hi, is there any solution?

I also just found out the same problem with class Plugin. IIUC these aren't reserved words by the language, why from CC then?
Also is there a list of what else is reserved?

If I do console.log(Storage) in my chrome browser debug console I get
f Storage() { [native code] }
In other words there is already a global variable named Storage, so it isn't safe to define your own class with that name.
Look at the files under https://github.com/google/closure-compiler/tree/master/externs for other names that are already defined.

I meant to say:
"It isn't safe to define your own class named Storage in the global scope."

The problem here is that while using
```import {Plugin} from ./module-x``
there is a clear indication that

a. This is not on global
b. I totally want it mangled

So I there should be safe way to do this in modules "atleast"

The original example doesn't have an import or export statement in it, so closure-compiler doesn't consider that to be a module.
If you get the same error in a file that does contain either an import or export, I suggest you file a new bug with that example.

Hi @brad4d,

The original example doesn't have an import or export statement in it, so closure-compiler doesn't consider that to be a module.

You pretty much saved my life here :)
But, is there a way to make CC handle all my files as if they were modules?
Thanks in advance,
Flo.

You can put an empty export {}; into a file to mark it as a module.

Or you could put `"type": "module" in your package.json for marking all your files under that package.json as es6 modules I think. It usually works with node but i haven't tested it with closure compiler


chore: update changelog and chart to v0.6.5

Pull Request Description
Describe what this PR does / why we need it
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

Codecov Report
Patch coverage has no change and project coverage change: +0.18 :tada:

Comparison is base (b6e40f1) 41.00% compared to head (dca2953) 41.19%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #396      +/-   ##
==========================================
+ Coverage   41.00%   41.19%   +0.18%
==========================================
  Files          42       42
  Lines        2753     2753
==========================================
+ Hits         1129     1134       +5
+ Misses       1503     1500       -3
+ Partials      121      119       -2

Flag
Coverage Δ

unittests
41.19% <ø> (+0.18%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 4 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


include all repos for organization/ listing

I think in many cases, e.g dandi/ and in principle could apply to original datalad/ - it would be useful to allow for simply including all repos for the organization.
An alternative could be to add support for regexes or globs, to sub-select some, but I do not have immediate usecase so not worth bothering I guess.
Also i am afraid that sooner than later we would run into the case desiring to exclude some repos, e.g.

exclude public or private
exclude based on some regex
but I think we can worry about exclusion when we get there.

getting repos seems to be easy
In [16]: org = gh.get_organization('dandi')

In [17]: [r.name for r in org.get_repos(type='all')]
Out[17]:
['dandi.github.io',
 'dandi-infrastructure',
 'artwork',
 'dandisets',
 'dandi-cli',
 'dandiarchive-legacy',
 'dandi-hub',
 'z2jh-aws-ansible',
 'example-notebooks',
 'nwb-metadata-gui',
 'metadata-dumps',
 'ndx-dandi',
 'redirector',
 'dandi-core',
 'dandi-publish',
 'schema',
 'handbook',
 'neuroconv',
 'dandi-archive',
 'dandi-api-datasets',
 'dandi-api-webshots',
 'nwb-healthstatus',
 'helpdesk',
 'dandi-schema',
 'dandi-api-webshots-staging',
 'dandi-api-webshots-tools',
 'dandi-api-webshots-prs',
 '.github',
 'upload-benchmarks',
 'bids-examples',
 'dandisets-book',
 'rehack-book',
 'dandisets-healthstatus',
 'zarr_checksum']

@yarikoptic So how should this be specified in the config file?  As an organizations: [dandi, con, ...] field, or by including globs like dandi/* in the repositories list?

I thought just to have a convention , without even a glob, of using dandi/ (ie without any particular repo as  dandi/dandi-cli ) to signal similar to glob dandi/*.
Could be organizations as well I guess. Would make it easier later to make them into records to exclude stuff, e.g.
organizations:
   - name: dandi
   - name: datalad
     exclude: .*-ci

or alike.


Added cookbook support

It looks like there is already one pending pull request to add cookbook support to pychef.  I've taken a slightly different approach by using _latest as the default version to load.  I've only performed light testing...
Thanks

@coderanger any update on getting this merged in? I see there was some code feedback, then some followup commits, and a failed most-recent commit. What needs to happen next?


[BC API 2.0 | Create salesCreditMemoLine] Remove read-only fields and…

… a few otters

Thank you so much for all of your contributions, it is very much appreciated.


chore: upgrade version to 2.0.0

For a smooth migration this should be a major version bump.

Great. Are you able to give me access to the module on NPM? I use semantic release here so I would like to set up a NPM publish key before I merge this one (which will be the first publish).

What's your npm username?

Its trygve. https://www.npmjs.com/~trygve

Added you to the npm package.

Thanks a lot :) I've set up a publish token in NPM and added it to this repo so publish should now happen through the publish action when I merge this.

A bit of juggling but now out in v2.0.0: https://github.com/trygve-lie/rollup-plugin-import-map/releases/tag/v2.0.0 :tada:


[stable/prometheus-redis-exporter] Fix secret key path in deployment

Is this a new chart
No
What this PR does / why we need it:
This PR fixes the path of the secret key value in the deployment. In the values.yaml file and README the path of the secret key is auth.secret.key. However, in the deployment the path is secret.key.
The PR also updates the redisAddress field in the README to indicate that rediss:// should be used for SSL connections.
Which issue this PR fixes
None
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @acondrat

/ok-to-test

/lgtm


[BUG] vela exec

Describe the bug
I run a command
vela exec testapp -- printenv | grep KUBE
and it hangs without breaking the line.
To Reproduce
Use vela up to start any sample app.
Run vela exec <yourappname> -- printenv  and it works.
Then add a pipe vela exec <yourappname> -- printenv | grep KUBE. Vela hangs.
If you use kubectl exec with the same command, it works fine.

I couldn't reproduce it.

I'm attaching the screenshot of the situation I encountered.
bug589.zip

closing as I can't repoduce either. @szihai  please try the new version and feel free to reopen if it still exists.


Update README.md

After merging #1339 this project does have a dependency.
I think it is better to remove the "and has no dependencies" from the README.md.
Maybe it would be better to explain why lodash is added as a dependency.

Yeah, this came up before. Technically it has a dependency but we are talking about two ten-line files, not the whole Lodash. We use just those two modules, and similar code was previously bundled into Redux, so there is no sensible size difference.
Can we reword it in a way that suggests that it’s 2kB including the dependencies? This way we make it clear Lodash doesn’t make the build large.

I guess it would be nice to have a sentence something like the following;
It is tiny (2kB) including lodash utilities. ?
Because it makes it more clear that it has just one dependency that is lodash and it is using lodash for providing utility functions from lodash.

I don’t want to mention Lodash specifically. That we are using it is an implementation detail nobody should worry or care about.
Maybe like this?

It is tiny, even when bundled with the dependencies (2kB).

It is tiny (2kB, including dependencies).

?

@acdlite :+1:

I think that one is great i will change it tonight!

:+1:


Select the platform to use

We need a platform
Select a platform and post it out here, and we will start learning it.

Development started in python in a separate repository.
See the README for this branch.
@pranjali97 is working on the Facebook side of it. And I've done some work on the Slack end. If you wish you can start out the Twitter part.


Unable to run new app created from cli RN 0.60.5 version pod install glog (0.3.5) error, help me

React Native version: 0.60.5
System:
OS: macOS 10.14.3
CPU: (4) x64 Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Memory: 2.20 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.16.3 - /usr/local/bin/node
Yarn: 1.17.3 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 23, 27, 28, 29
Build Tools: 28.0.3, 29.0.2
System Images: android-28 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.5 AI-191.8<IP_ADDRESS>91312
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.5 => 0.60.5
npmGlobalPackages:
react-native-cli: 2.0.1
mojaves-iMac:NativeBridgeDemo mojave$
Steps To Reproduce

react-native init "ProjectName"

Installing DoubleConversion (1.1.6)
Installing Folly (2<IP_ADDRESS>)
Installing React (0.60.5)
Installing React-Core (0.60.5)
Installing React-DevSupport (0.60.5)
Installing React-RCTActionSheet (0.60.5)
Installing React-RCTAnimation (0.60.5)
Installing React-RCTBlob (0.60.5)
Installing React-RCTImage (0.60.5)
Installing React-RCTLinking (0.60.5)
Installing React-RCTNetwork (0.60.5)
Installing React-RCTSettings (0.60.5)
Installing React-RCTText (0.60.5)
Installing React-RCTVibration (0.60.5)
Installing React-RCTWebSocket (0.60.5)
Installing React-cxxreact (0.60.5)
Installing React-jsi (0.60.5)
Installing React-jsiexecutor (0.60.5)
Installing React-jsinspector (0.60.5)
Installing boost-for-react-native (1.63.0)
Installing glog (0.3.5)
[!] /bin/bash -c
set -e
#!/bin/bash
Copyright (c) Facebook, Inc. and its affiliates.

This source code is licensed under the MIT license found in the
LICENSE file in the root directory of this source tree.
set -e
PLATFORM_NAME="${PLATFORM_NAME:-iphoneos}"
CURRENT_ARCH="${CURRENT_ARCH}"
if [ -z "$CURRENT_ARCH" ] || [ "$CURRENT_ARCH" == "undefined_arch" ]; then
# Xcode 10 beta sets CURRENT_ARCH to "undefined_arch", this leads to incorrect linker arg.
# it's better to rely on platform name as fallback because architecture differs between simulator and device
if [[ "$PLATFORM_NAME" == *"simulator"* ]]; then
    CURRENT_ARCH="x86_64"
else
    CURRENT_ARCH="armv7"
fi

fi
export CC="$(xcrun -find -sdk $PLATFORM_NAME cc) -arch $CURRENT_ARCH -isysroot $(xcrun -sdk $PLATFORM_NAME --show-sdk-path)"
export CXX="$CC"
Remove automake symlink if it exists
if [ -h "test-driver" ]; then
rm test-driver
fi
./configure --host arm-apple-darwin
Fix build for tvOS
cat << EOF >> src/config.h
/* Add in so we have Apple Target Conditionals */
#ifdef APPLE
#include <TargetConditionals.h>
#include <Availability.h>
#endif
/* Special configuration for AppleTVOS */
#if TARGET_OS_TV
#undef HAVE_SYSCALL_H
#undef HAVE_SYS_SYSCALL_H
#undef OS_MACOSX
#endif
/* Special configuration for ucontext */
#undef HAVE_UCONTEXT_H
#undef PC_FROM_UCONTEXT
#if defined(x86_64)
#define PC_FROM_UCONTEXT uc_mcontext->__ss.__rip
#elif defined(i386)
#define PC_FROM_UCONTEXT uc_mcontext->__ss.__eip
#endif
EOF
Prepare exported header include
EXPORTED_INCLUDE_DIR="exported/glog"
mkdir -p exported/glog
cp -f src/glog/log_severity.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/logging.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/raw_logging.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/stl_logging.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/vlog_is_on.h "$EXPORTED_INCLUDE_DIR/"
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-apple-darwin-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for arm-apple-darwin-gcc... /Applications/Xcode 3.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -arch armv7 -isysroot /Applications/Xcode 3.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS12.1.sdk
checking whether the C compiler works... no
/Users/mojave/Library/Caches/CocoaPods/Pods/External/glog/2263bd123499e5b93b5efe24871be317-1f3da/missing: Unknown --is-lightweight' option Try /Users/mojave/Library/Caches/CocoaPods/Pods/External/glog/2263bd123499e5b93b5efe24871be317-1f3da/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
configure: error: in /Users/mojave/Library/Caches/CocoaPods/Pods/External/glog/2263bd123499e5b93b5efe24871be317-1f3da': configure: error: C compiler cannot create executables See config.log' for more details
It Should have created a new project rather than this.
Snack, code example, screenshot, or link to a repository:

@amitrai98 Hope this solution help https://forums.expo.io/t/pod-install-errors-on-newly-detached-app-on-macos-installing-glog-bin-bash-configure-bin-sh-m-bad-interpreter-no-such-file-or-directory/10054/3. Worked for me 😃

Yeah, mee too. I have same issues. :(

Resolved this issue,
open xcode and navigate to the settings
xcode>preference>location
change the value of command line tools to the latest version of xcode you have
my previous version was 9.3.1
I updated it to 10.2.1
now navigate to the location of derived data from the same menu by clicking forward arrow
under derived data menu
delete the data and quit xcode also epty the trash and try now
it worked for me.

Resolved this issue,
open xcode and navigate to the settings
xcode>preference>location
change the value of command line tools to the latest version of xcode you have
my previous version was 9.3.1
I updated it to 10.2.1
now navigate to the location of derived data from the same menu by clicking forward arrow
under derived data menu
delete the data and quit xcode also epty the trash and try now
it worked for me.

After cleaning derived data still, throw the same error

You either need to do a xcode-select, or at least in XCode. Preferences/Locations/Command Line Tools

Resolved this issue,
open xcode and navigate to the settings
xcode>preference>location
change the value of command line tools to the latest version of xcode you have
my previous version was 9.3.1
I updated it to 10.2.1
now navigate to the location of derived data from the same menu by clicking forward arrow
under derived data menu
delete the data and quit xcode also epty the trash and try now
it worked for me.

Work for me, thanks!


Add tracing back to petclinic

Context
In this PR ,tracing-server, grafana-server, prometheus-server were removed from docker-compose.yml,
Goal

add them back to make the sample works.
enable the Spring Cloud Azure Trace Sleuth in this sample.

@moarychan assign this to you.

Due to the limited support of Spring Cloud Azure Trace Sleuth and no library using storage, we will not add support for the time being.

closing it for now, no customer ask, reopen if anyone need it


Update applications runtimes

Re-estimate the runtime of the applications and update the documentation.

If it helps, I can say that it took less than 3 minutes to run the derive_mirror_rnda.py example.

All runtimes were updated in the develop branch. A PR will be done soon.


feat: controller input for UI buttons

Now, you can easily navigate the UI using a gamepad.
We've also introduced the option to play in fullscreen mode while in engine play mode.
You can now toggle the editor controls on or off in engine play mode.
Some missing windows are now automatically docked.

I was testing the branch in the main menu and its options, these are my conclusions:

In the main menu it works as such, although sometimes going up and down requires you to do the movement twice. I couldn't find out why.

When I enter a menu option it is not possible to return and it does not recognize the return button.

The mouse is disabled, I don't know how complicated it is but would it be possible to focus the controller or the mouse depending on which one is moving?

The in game menu does not work, I have tested it in gameplayfulltrial.

I was testing the branch in the main menu and its options, these are my conclusions:

In the main menu it works as such, although sometimes going up and down requires you to do the movement twice. I couldn't find out why.
When I enter a menu option it is not possible to return and it does not recognize the return button.
The mouse is disabled, I don't know how complicated it is but would it be possible to focus the controller or the mouse depending on which one is moving?
The in game menu does not work, I have tested it in gameplayfulltrial.

There is a cooldown of 0.2 seconds. We can tweak these values to make it feel more acessible.
I'm working on the back buttons of the menus, I'll let you know when this part is finished before we merge it.
I made it on purpose to avoid mixing the controls. The mouse works only when the controller is disconnected. We can have both at the same time but then we can have a button hovered by the mouse and another hovered by the gamepad at the same time (I don't know which one would be triggered if we click on the mouse left button when two buttons are hovered at the same time). So let me know what do you prefer, using the mouse and controller independently or using them at the same time knowing this possible issue. Changing between a solution or another by code is really easy and fast to do. We can meet together to discuss this if you prefer doing so.
I haven't worked yet on the in-game menu. Can we do this part in another PR?

* There is a cooldown of 0.2 seconds. We can tweak these values to make it more accessible.

For me it is fine but I think it can be improved, if it is a value leave it and we will change it in the future. Right now I couldn't tell you exactly how to improve it and we will have more controller updates.

* I'm working on the back buttons of the menus, I'll let you know when this part is finished before we merge it.

Ok, perfect!

* I made it on purpose to avoid mixing the controls. The mouse works only when the controller is disconnected. We can have both at the same time but then we can have a button hovered by the mouse and another hovered by the gamepad at the same time (I don't know which one would be triggered if we click on the mouse left button when two buttons are hovered at the same time). So let me know what do you prefer, using the mouse and controller independently or using them at the same time knowing this possible issue. Changing between a solution or another by code is really easy and fast to do. We can meet together to discuss this if you prefer doing so.

Maybe what I say sounds crazy, but you tell me if it's possible or not. In Diablo 2 or 4, when you have a controller and a mouse, both work but only 1 at a time, they become focused when you press a key or move the mouse and in turn when you touch something on the controller it becomes focused.
I know I'm talking about the Diablo but maybe it is possible and not so hard.

* I haven't worked yet on the in-game menu. Can we do this part in another PR?

Oh i didnt know it, ok.

* There is a cooldown of 0.2 seconds. We can tweak these values to make it more accessible.

For me it is fine but I think it can be improved, if it is a value leave it and we will change it in the future. Right now I couldn't tell you exactly how to improve it and we will have more controller updates.

I'm trying with 0.15 seconds and it looks better. 0.1 is too fast, so the optimal value should be near. I will update it soon with the new value and let you test it.

* I'm working on the back buttons of the menus, I'll let you know when this part is finished before we merge it.

Ok, perfect!

* I made it on purpose to avoid mixing the controls. The mouse works only when the controller is disconnected. We can have both at the same time but then we can have a button hovered by the mouse and another hovered by the gamepad at the same time (I don't know which one would be triggered if we click on the mouse left button when two buttons are hovered at the same time). So let me know what do you prefer, using the mouse and controller independently or using them at the same time knowing this possible issue. Changing between a solution or another by code is really easy and fast to do. We can meet together to discuss this if you prefer doing so.

Maybe what I say sounds crazy, but you tell me if it's possible or not. In Diablo 2 or 4, when you have a controller and a mouse, both work but only 1 at a time, they become focused when you press a key or move the mouse and in turn when you touch something on the controller it becomes focused. I know I'm talking about the Diablo but maybe it is possible and not so hard.

I have also seen this in other games but I think this is a bit more difficult, so it will require more time. It's achievable but I would do it later. Probably the teachers will test it only with a controller for this milestone

* I haven't worked yet on the in-game menu. Can we do this part in another PR?

Oh i didnt know it, ok.


Added maxRows functionality

Implement maxRows and enforce constraint during resize and drag.

I haven't contributed to this project, but I'd love it if this pull request gets merged; it would solve most of my problems with RGL. Thanks!

Any updates on this? I'm waiting for this to be merged too!

Any update on this?

Please rebase on master @samuelwong5

Any updated?

Please, let's make that one go forward!

Any update on this?

Any updates?

Can we please get this merged soon? My team needs to be able to limit the rows for our use case.


!(.exists) waits the full timeout duration

Currently .exists will wait 5 seconds for the element to exist. When doing !(.exists), it's simply returning the opposite of what the .exists matcher will give.
At that point, every !(.exists) is guaranteed to take 5 seconds to complete. The user would need to do !(.exists(waiting: 0)) for every ! check on exists.

I suspect I may need to remove the ! operator and add assertions like .doesNotExist instead - otherwise it might not be possible to get the same performance gains

I have left the ! operator in as its useful for most assertions. .exists is a special case as there's the potential for polling/waiting.. to resolve this I've added an explicit .doesNotExist counterpart.


python3Packages.semver: exclude documentation from tests

Motivation for this change
Fix build (https://hydra.nixos.org/build/163512178)
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Sure, I can do that

@ofborg eval


SyntaxError: Non-ASCII character '\xc2' in file

gcloud_options.job_name = "aaa"
gcloud_options.job_name ="aaa"
I got the same error but when i removed the space after =(equal to) then its gone


Implementation in Modelscope/Zeroscope?

How would this be implemented in modelscope/zeroscope t2v? Thanks!

Based on @lyn-rgb repository I added register methods for UNet3DConditionModel and successfully ran the Zeroscope model with FreeU.
You can check out the code with an example of usage in diffusers here 😊


Handle situations where score may be null

When returning sorted results I came across score:null results, I was able to produce this by a search similar to:
{
  "size": 1,
  "sort": [
    {
      "timestamp": {
        "order": "desc",
        "unmapped_type": "boolean"
      }
    }
  ],
  "query": {
    "query_string": {
      "query": "*"
    }
  }
}

This patch allows the score field in the response struct to be null

Ah good catch! Let's add another test case with a sample response with no score.

Ok - will do.


feat: Allow specifing custom origins

what

allow specifing/creating (additional) custom origins

why

This module is really useful for front-end website deployments but sometimes it is required to use the same domain for front-end and back-end (different paths) or add some back-end functionality to front-end website without creating real back-end
To configure API Gateway easily
We already have the ability to configure ordered_cache_behaviour so we technically support multiple strategies for different paths

references

https://www.terraform.io/docs/providers/aws/r/cloudfront_distribution.html#origin-arguments

example usage
module "cloudfront-s3" {
# ...
  ordered_cache = [{
    target_origin_id            = "api-gateway-with-lambda"
    path_pattern                = "/v1/lambda"
    allowed_methods             = ["HEAD", "GET"]
    cached_methods              = ["HEAD", "GET"]
    compress                    = true
    viewer_protocol_policy      = "redirect-to-https"
    min_ttl                     = 0
    default_ttl                 = 60
    max_ttl                     = 3600
    forward_header_values       = []
    forward_query_string        = true
    forward_cookies             = "none"
    lambda_function_association = []
  }]

  custom_origins = [{
    domain_name = "xxxxxxxxxx.execute-api.us-east-1.amazonaws.com"
    origin_id   = "api-gateway-with-lambda"
    origin_path = null
    custom_origin_config = {
      http_port                = 80
      https_port               = 443
      origin_protocol_policy   = "https-only"
      origin_ssl_protocols     = ["TLSv1.2"]
      origin_keepalive_timeout = 5
      origin_read_timeout      = 30
    }
  }]
}

/rebuild-readme

/test all

@k911 Thanks for the contribution! Released as 0.26.0.


Authorization and deployment failure using sf auth device login -r https://test.salesforce.com -a testAlias

Summary
sf command not working properly for authorization and deployment.
sys information
{
"cliVersion"<EMAIL_ADDRESS>"architecture": "win32-x64",
"nodeVersion": "node-v18.16.0",
"osVersion": "Windows_NT 10.0.22621",
"shell": "cmd.exe",
"rootPath": "C:\Users\user21\AppData\Roaming\npm\node_modules\@salesforce\cli",
"pluginVersions": [
"@oclif/plugin-autocomplete 2.3.6 (core)",
"@oclif/plugin-commands 2.2.22 (core)",
"@oclif/plugin-help 5.2.17 (core)",
"@oclif/plugin-not-found 2.3.37 (core)",
"@oclif/plugin-plugins 3.2.6 (core)",
"@oclif/plugin-search 0.0.22 (core)",
"@oclif/plugin-update 3.1.32 (core)",
"@oclif/plugin-version 1.3.8 (core)",
"@oclif/plugin-warn-if-update-available 2.0.48 (core)",
"@oclif/plugin-which 2.2.30 (core)",
"@salesforce/cli 2.5.7 (core)",
"apex 2.3.10 (core)",
"auth 2.8.12 (core)",
"data 2.5.6 (core)",
"deploy-retrieve 1.17.5 (core)",
"env 2.1.20 (user)",
"functions 1.21.10 (user)",
"info 2.6.39 (core)",
"limits 2.3.30 (core)",
"login 1.2.26 (core)",
"org 2.10.0 (core)",
"packaging 1.20.1 (user)",
"schema 2.3.23 (core)",
"settings 1.4.25 (core)",
"sobject 0.2.4 (core)",
"source 2.10.31 (core)",
"telemetry 2.3.0 (core)",
"templates 55.5.10 (core)",
"trust 2.6.1 (core)",
"user 2.3.28 (core)"
]
}
Steps To Reproduce
sf auth device login -r https://test.salesforce.com -a testAlias
Expected result
Login code and url in terminal
Actual result
Error (1): request to https://test.salesforce.com//services/oauth2/token failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443
Getting error while retreiving/deploying in vscode

System Information
@salesforce/cli/2.3.8 win32-x64 node-v18.16.0

I cannot reproduce this.  Do you have any additional steps to reproduce?

We recommend using -r with the mydomain (instanceUrl) instead of the generic https://test.salesforce.com because there can be replication delays between the real domain and the login servers at test.salesforce.com.
Other than that, there's not much to be done from the CLI side.  My guess is that this was intermittent or one org with a problem and not happening consistently everywhere.


As a visitor, I would like to see images that convey something about the task

I would like to have an image automatically pop up for each type of task we publish.  Right now when we post a new tapa task the image of a tapas plate appears, when we post a new 20% task there is  an image of a pie cut in six pieces that goes up with it and when we publish an agency rep task (50% or more time) goes up we post a photo of arms and hands coming together.
In addition, when a task is taken we change the photo to show the tapa, pie and arms with a closed through it. Here's an example:
Open tapas image: http://gsablogs.gsa.gov/dsic/2014/10/27/who-to-follow-on-twitter-kids-gov-wants-to-know/
Closed tapas image: http://gsablogs.gsa.gov/dsic/2014/09/30/task-for-video-script-writer/
We don't distinguish assigned from completed because the purpose of the image is to let people know what is available.  So we just use closed.
We have images we use but am happy to consider others.

Haven't heard this come up recently, but CCing @GailSwanson to think about when we redesign this page.

Thanks Dave,
I'll add it to the list of considerations for the platform's visual language.


[Spotify Player] Change the output device in the menu bar

Extension
https://www.raycast.com/mattisssa/spotify-player
Description
Add an option in the Spotify menu bar that allows users to select the output device.
Who will benefit from this feature?
This feature could be helpful for users who have multiple output devices (e.g. external speakers, a headset, multi-room audio setup) and want to control the device to playback. This could provide control and flexibility over the listening experience.
Anything else?
No response

see #4487


Bump conda version

This bumps the miniconda version to 4.5.12 (latest) and the conda version to 4.6.11 (latest). Conda 4.6 included a number of performance improvements that should help speed up install times for complex environments. It also included some improvements to conda's interoperability with pip. An overview of the conda release is available here: https://www.anaconda.com/conda-4-6-release/.
Fixes #593

Thanks for helping get this done! I edited your comment to include the issue that has been tracking this so it gets closed.
We should also refreeze our environments per https://github.com/jupyter/repo2docker/issues/593#issuecomment-476553639
What is your thinking behind bumping conda but not miniconda? My expectation was that we'd keep them in sync unless there is a reason not to.

The answer to "why not also update miniconda" is that there isn't a miniconda 4.6! See https://repo.anaconda.com/miniconda/

I think the TL;DR is that the new conda requires a Python version newer than 3.5. So we need to think of a way to deal with that.
I think the conda/simple-py2/verify::build FAILED failure is due to a network issue and will resolve itself. That's why the "verify" part of that test worked even though the build part had just previously failed.

The new version of conda doesn't work with Python 3.5 any more. At least I can't get it installed in a conda env with Python 3.5. First thought this was because conda-forge isn't building new packages for 3.5 any more but even without using conda-forge this seems to happen. There is nothing in the conda change log about this so I am suspicious/think I've made a mistake somewhere.
I think the way forward is that we need to start treating Python 3.5 separately. It already has a "deep frozen" environment.yml to setup the basic env. I am wondering if it is possible to adopt the same method we use for Python 2: have a "user env" and a "server env". The server env is always a modern Python 3, independent of what the user requested. Would it work to install conda there and use it in the Pythonn 3.5 env?

@betatim I agree re: separate server / user env, (or 'notebook' env and 'kernel' env) similar to python2. It'll also help with stuff like https://github.com/jupyter/repo2docker/issues/438

After the pointer to the Jupyter lab issue I think we will want to have separate user and kernel envs for everything. Right now we do it as a special case for Python 2. Do you think that is a good goal?
I think the downsides include: harder for users to install server extensions, impossible to organise for repositories that currently install server extensions to continue working, bigger docker images.
Advantages include: we don't have to special case certain setups, harder for users to break their kernel/notebook server
Is my assumption that notebook server extensions would need installing in the kernel env correct?
Overall: we have a few tricky trade-offs ahead of us. Is there a way to upgrade conda (resolve this PR) without having to first also have a decision on all the trade-offs? Maybe we spend a bit of extra effort to do so but I think this particular issue is worth resolving "now" instead of in a few weeks, even if it costs a bit extra in engineering effort.

I'm going to defer to you all on how to proceed here. FWIW, a refactor of the user/kernel envs is probably beyond what I can help with right now. If it makes sense to put this on hold until that is addressed, fine by me.

@betatim yeah, if we have a 'notebook' env where notebook lives and a 'kernel env' where kernel lives, notebook extensions need to be in the notebook env.
We 'hack' this with python2 by having a 'requirements3.txt' that installs things into the notebook env. This lets people install notebook extensions.
Doing that by default for everything would definitely break lots of current repos that install server extensions. I'd say for now we special case 3.4 and 3.5, and figure out a better solution for this after.

Out of curiosity, do we know how ofter 3.4 and 3.5 are being used with repo2docker?

do we know how ofter 3.4 and 3.5 are being used with repo2docker?

We don't, but I'm guessing it's rather few. #651 should get this unstuck because it leaves conda alone in the root env, installing the notebook in a dedicated env. This will presumably come at some cost to image size from the extra env, but may also improve installation time since it removes the step where the root env is switched to the chosen Python version.

Thanks all!

What GitHub magic is this that this PR also got merged when we merged #651? This is amazing.


fix(declarative) change default back to false skip_ws

Summary
declarative.export_from_db skip_ws was inadvertently changed to true in https://github.com/Kong/kong/pull/8113
Full changelog
declarative.export_from_db skip_ws default set back to false
Issues resolved
Tests break in ee without this.
Fix #XXX

Closed as I think this intentional difference between CE and EE.


Can not parse "\sum"

I'm trying to parse a summation equation such as

and get an error as below;

Most of the summation cases got similar errors. It recognizes exponentiation instead of summation.
Thanks!

The parsing of \sum (and \prod) has been fixed.


GitHub: illegal bibtex key, non-ascii character

When creating a BibTeX citation for any of my software, GitHub will chose the BibTeX key to be {lastname_title}, in my case resulting in, e.g.,
Schlömer_pygmsh_A_Python

This isn't a legal BibTeX key because of the ö, and should probably be replaced by oe.

I think we just used String#encode (e.g., https://stackoverflow.com/questions/1268289/how-to-get-rid-of-non-ascii-characters-in-ruby) but I'm trying to get a definitive answer here.

Yeah, I saw that one but it's still quite a lot of work to do "nice" transliteration. Rails adds the String#parameterize method (actually ActiveSupport::Inflector.parameterize) which would be perfect, but we can't pull Rails in just for this!
I was wondering about adding a "good enough" parameterize-type method based on that SO post you mention but using String#parameterize if available?
Certainly it seems we need to avoid UTF8 in BibTeX citekeys: https://tex.stackexchange.com/questions/359215/utf8-character-in-citation-keys

but we can't pull Rails in just for this!

Could we use the Rails/ActiveSupport method if they're available, and have some kind of fall-back for the Gem outside of a Rails-enabled context.
Not sure I've ever seen anything like this done before (or if it's a good idea) but just wanted to mention it incase :-)

Could we use the Rails/ActiveSupport method if they're available, and have some kind of fall-back for the Gem outside of a Rails-enabled context.

That's what I meant in my badly worded comment 😆
I'll look into it...


The "json" folder was not created in the "build" folder.

I generated all 10,000 images, everything is fine, but two folders (images and json) should be created in the build folder. They were not created, instead all the pictures just appeared there. And i need a: 1.json; 2.json etc for every picture.
The only json file that was created is "_metadata.json", which is located right where the pictures are.
What to do?

I'm having same problem


Disables highlighting for Supported data

Description
Closes #394
This disables highlighting for the Support data metadata:

hmm should this close #393?

dang it, i was off by one number 😢 yes it should be closing that issue lol


docker build failure

I clone the latest code and do docker build ., it reports error

..
Step 7/16 : RUN venv/bin/pip install gunicorn pymysql
 ---> Running in 83a49880f60b
Collecting gunicorn
  Downloading https://files.pythonhosted.org/packages/8c/da/b8dd8deb741bff556db53902d4706774c8e1e67265f69528c14c003644e6/gunicorn-19.9.0-py2.py3-none-any.whl (112kB)
Collecting pymysql
  Downloading https://files.pythonhosted.org/packages/a7/7d/682c4a7da195a678047c8f1c51bb7682aaedee1dca7547883c3993ca9282/PyMySQL-0.9.2-py2.py3-none-any.whl (47kB)
Collecting cryptography (from pymysql)
  Downloading https://files.pythonhosted.org/packages/22/21/233e38f74188db94e8451ef6385754a98f3cad9b59bedf3a8e8b14988be4/cryptography-2.3.1.tar.gz (449kB)
Requirement already satisfied: idna>=2.1 in ./venv/lib/python3.6/site-packages (from cryptography->pymysql) (2.6)
Collecting asn1crypto>=0.21.0 (from cryptography->pymysql)
  Downloading https://files.pythonhosted.org/packages/ea/cd/35485615f45f30a510576f1a56d1e0a7ad7bd8ab5ed7cdc600ef7cd06222/asn1crypto-0.24.0-py2.py3-none-any.whl (101kB)
Requirement already satisfied: six>=1.4.1 in ./venv/lib/python3.6/site-packages (from cryptography->pymysql) (1.11.0)
Collecting cffi!=1.11.3,>=1.7 (from cryptography->pymysql)
  Downloading https://files.pythonhosted.org/packages/e7/a7/4cd50e57cc6f436f1cc3a7e8fa700ff9b8b4d471620629074913e3735fb2/cffi-1.11.5.tar.gz (438kB)
    Complete output from command python setup.py egg_info:

        No working compiler found, or bogus compiler options passed to
        the compiler from Python's standard "distutils" module.  See
        the error messages above.  Likely, the problem is not related
        to CFFI but generic to the setup.py of any Python package that
        tries to compile C code.  (Hints: on OS/X 10.8, for errors about
        -mno-fused-madd see http://stackoverflow.com/questions/22313407/
        Otherwise, see https://wiki.python.org/moin/CompLangPython or
        the IRC channel #python on irc.freenode.net.)
...

I tried both in Ubuntu & Windows 7 (toolbox) platform,

$ docker --version
Docker version 18.03.1-ce, build 9ee9f40

Could insert below line to make it pass without optimization

RUN apk add --no-cache --virtual .py_deps build-base python3-dev libffi-dev openssl-dev

The pymysql package has made some changes that require a C compiler to be available. You can install a slightly older version of this package to avoid the problem. See https://github.com/PyMySQL/PyMySQL/issues/697#issuecomment-403817794.


License issue

This crate depends on ansi_colours, which is licensed under the LGPL-3.0-or-later.
I think it's confusing that an MIT-licensed crate has copyleft dependency.

I'm not an expert on license compatibility, but this issue seems to be addressed by https://old.reddit.com/r/rust/comments/fevz37/want_to_use_lgpl_licensed_library_do_i_need_to/fjsg393/ and https://opensource.stackexchange.com/questions/10537/mit-license-ok-if-dependent-package-uses-lgpl. If this is still a concern and the project's license were to be changed, it would also need to affect viu, which was the source of this project's code and license choice, and still features the MIT license while depending on this project.

I don't think there is license incompatibility but using a LGPL library adds some limitations to derived programs so I’m curious if this is intended or not.

There might be limitations in using the program. That depends whether you can fulfill the license conditions of the LGPL-3.0-or-later. If so, it does not affect the program itself. But you are right. The dependency under LGPL-3.0-or-later requires you to deliver the license text, provide source code etc.


Caffeinated will attempt to use Caffeine after entering Twitch as the platform.

Fixed in 0.4.2-release


Crash: System.Linq.Enumerable.FirstOrDefault(...) returned null.

Perhaps I'm a little bit too enthusiastic, but compiling the source (successfully) and then switching to the Wild RNG tab gave me a crash:
https://github.com/wwwwwwzx/3DSRNGTool/blob/4c1a9e6862c9ed19d6651c12de631e309d700a6a/3DSRNGTool/Controls/StringItem.cs#L39
System.Linq.Enumerable.FirstOrDefault(...) returned null.

Thanks


Coffeescript?

I love to write on preprocessors :laughing: so I love Coffee. and I love a coffee! 😂

As it stands now, I do not plan to support coffeescript. In the wake of ES6 and the ease of use through Babel, I don't believe it's necessary to support CS out of the box. I think adding a guide on how to add CS support to a project would be more beneficial, so I will work on that going forward.

Understand.
I tried do it by myself and even get some luck with grunt-coffee-chain to control partials but don't sure that this is the right way to build CoffeeScript with Grunt. I tried grunt-coffee-chain because regular grunt-contrib-coffee compiles all partials in alphanumeric order but I want to control this like in Sass. Can you write a right guide @larsonjj?

Hey @Grawl, Sorry for the delayed response. I'm currently deep in development for v1.0.0 of this generator, so I will not have time to create a guide for adding coffeescript for a while. If you find success in an implementation of coffeescript for a yeogurt project, feel free to submit a PR. Otherwise I will be closing this out for now.


[WORKFLOWS-55 | WORKFLOWS-96] Upgrade Nextflow Tower to v21.06.4

I was originally waiting for a major release before upgrading Tower, but Paolo suggested this patch release might address the issue I reported here. I already deployed this change to Nextflow-dev, and ECS transitioned to the new task definition as expected. I'm now running a test in Tower-dev to see whether the issue has been fixed or not.
Edit: This PR now updates Tower to v21.06.4, which was released to address the following error message that I reported to Seqera. This requires compute environments to be re-created so their configuration can be updated. Hence, I've also updated the Tower configuration script to create versioned compute environments (instead of managing a default CE, which would be more complicated). The latest version is marked as the primary CE (aka the default).
Error when retrieving credentials from container-role: Error retrieving metadata: Received error when attempting to retrieve ECS metadata: Connect timeout on endpoint URL: "http://<IP_ADDRESS>/v2/credentials/62307d39-2d77-4b25-b9e0-d08c257fe10a"

I'm also taking advantage of this update to the Tower configuration script to deploy a potential fix to WORKFLOWS-96, which has to do with running out of disk space despite EBS autoscaling being enabled. This seems to happen with large files 20-60 GB. Given that multiple jobs can run on a given instance, I suspect that the disk is running out of space before EBS autoscaling can kick in. I suspect that increasing the default EBS volume size from 100 GB (default) to 250 GB should mitigate this issue.
I'm still confirming whether the aforementioned issues are fixed. That said, I think we can start the review in the meantime.

I'm asking for a re-review because I made a significant change to the Tower configuration script. It now creates two compute environments per workspace: one for on-demand instances and another for spot instances. Some of the issues that I've been debugging are related to spot termination, so I figure it would be nice to provide the option to use on-demand instances (ideal for debugging when you don't want to also deal with spot termination issues).

@BrunoGrandePhD Thanks, if there are issues with spot instances currently, should we currently recommend users to use on-demand instances until the issue is resolved?
We actually don't have full control when spot instances are shut down, so if it is a extremely important workflow that we absolutely don't want an instance to go down, should our SOP be to use on-demands instances?

We expect errors due to spot termination, but I confirmed this morning that everything should work fine as long as you enable retries with the following snippet of Nextflow config. I'll be updating the wiki docs with a description of spot vs on-demand and recommendations for each. In general, on-demand is good for debugging to eliminate errors related to spot termination, whereas spot is cost-effective for running an established workflow on a large dataset (as long as retries are enabled to get passed the random errors).
process {
  errorStrategy = 'retry'
  maxRetries = 3
}

Merging this in the evening to avoid any disruption.


Hire some developers with more than 2 months experience

https://feedback.azure.com/forums/263030-azure-cosmos-db/suggestions/17265707-mark-geography-types-as-serializable?tracking_code=a4f656185d06f0aa174d7c4ed42ff2f9
Mark geography types as Serializable
Currently geography types such as Microsoft.Azure.Documents.Spatial.Point are not marked as Serializable which prevents them, or classes containing them, from being passed as arguments to Service Fabric services. If possible, please mark them as Serializable.
Closed because they didn't understand the request?!?!?!?!?!?!?!?!?!?!?!
How's BulkExecutor for .netstandard looking?
Hows the v3 SDK looking?
THIS TEAM IS A JOKE.

While you may have a point, and you may be having a bad day, I'd ask you to please edit this to have a more respectful tone. There are people hard at work here. If you want to rant, Twitter and other channels are available.
Regarding the specific complaint re the v3 SDK release timeline, shouting loudly at people and forcing a premature ship doesn't help anyone - I would like to register, for the record, my desire for people not to ship until it's right and they need to actually lie by having to make fast-follow breaking changes, and/or have warrens of obsoleted deprecated code making repos unreadable.

Also is https://github.com/Azure/azure-cosmos-dotnet-v3/pull/447#discussion_r293955958 relevant ?