Support loading external files in OpenAPI

Regarding the updates made in 0.74.0: https://gohugo.io/news/0.74.0-relnotes/
The current implementation doesn't appear to allow isExternalRefsAllowed to be configured anywhere and it is false by default. This causes any attempt to unmarshal an openapi spec using external references to fail: https://github.com/getkin/kin-openapi/blob/9b9280d707773bb764ec07ac7363248d8240343d/openapi3/swagger_loader.go#L67
This could be a really fantastic feature for some of us building documentation sites in Hugo based on the OpenAPI spec, but due to the above, it's at present only useful for smaller and non-complex openapi specifications.
Could this either be set to true by default when initializing the kin-openapi library, or could this be designed so that we can set it to true in config.toml or somewhere else that makes sense?

My OpenAPI YAMLs are getting pretty big, would be appreciated

Question: I assume that you by external (mostly) mean files on the same file system (and not remote files)?

As for me, yes on the same file system.
Specifically, I organized all of my YAMLs under the assets/ directory since that's what works with resources.Get

Same for me, all on the same file system.

OK,
I hadded the initial OpenAPi support in Hugo, and the project I used it in has the API source mounted as a Hugo Module. So, this is what we need to do:

Set IsExternalRefsAllowed to true
Implement a ReadFromURIFunc that resolves the files in the Assets filesystem (which allows them to live in modules).

I was able to hack something together that works for my specific use-case, but isn't production ready.
There are a number of issues

Relative $refs (e.g. $ref: ./definitions/foobar.yaml#/components/schema/Foobar need to be resolved relative to the current YAML file being parsed, and it isn't clear how we're supposed to figure out the location of the current YAML file with kin-openapi.
It isn't clear how we're supposed to determine whether a file is in the Assets filesystem, and then receive a filepath in that filesystem. (e.g. go from ./definitions/foobar.yaml to /workspaces/my-docs/assets/api/definitions/foobar.yaml)

loader := kopenapi3.NewSwaggerLoader()
loader.IsExternalRefsAllowed = true
loader.ReadFromURIFunc = func(loader *kopenapi3.SwaggerLoader, url *url.URL) ([]byte, error) {
	if url.Scheme != "" || url.Host != "" || url.RawQuery != "" {
		return nil, errors.Errorf("unsupported URI: %q", url.String())
	}

	fullpath := filepath.Join(filepath.Dir(key), url.Path)
	assetpath := ns.deps.SourceFilesystems.Assets.RealDirs(fullpath)[0]
	return ioutil.ReadFile(assetpath)
}
err = loader.ResolveRefsIn(s, nil)

@illeatmyhat It's hard for me to debug your example/code without  additional context, but I'll try:

I think the closest existing example would be somthing like this: https://github.com/gohugoio/hugo/blob/8a308944e46f8c2aa054005d5aed89f2711f9c1d/resources/resource_transformers/js/options.go#L184
You by definition needs to mount all your API files inside /assets, so if it's not found there, it does not exist.
Then, in my head, there are two cases:

Either the file includes are root relative (e.g. definitions/foobar.yaml)
Or they are relative to the current file (e.g. ./baz.yaml)

There may be discussions about the details above, but the first is simple (use fs.Stat directly), for the second you need to determine the relative directory via MakePathRelative.

@bep is this still an issue? I'd like to take a crack at it

@alecgarza96 that would be great! A good first step, I think, would be to create a failing test in here:
https://github.com/gohugoio/hugo/blob/master/tpl/openapi/openapi3/integration_test.go

Hi, maintainer of kin-openapi here. Just to note that the ReadFromURIFunc mechanism can be more customized now. See<EMAIL_ADDRESS>

Hello! Is this issues still relevant?


did not work offline

I have a Moto G3 and used the app about a month ago.
I added it to my homescreen
I tried to open it today while offline, and I get an error "This webpage is not available - ERR_FAILED"
Wasn't it supposed to work offline? Is this an issue of chrome clearing its local serviceworker cache?

Hmmm. I'll check. "It should" work
On Tue, 27 Oct 2015, 23:09 Kyle Graehl<EMAIL_ADDRESS>wrote:

I have a Moto G3 and used the app about a month ago.
I added it to my homescreen
I tried to open it today while offline, and I get an error "This webpage
is not available - ERR_FAILED"
Wasn't it supposed to work offline? Is this an issue of chrome clearing
its local serviceworker cache?
—
Reply to this email directly or view it on GitHub
https://github.com/PaulKinlan/qrcode/issues/4.

After a year - have you found out if it is working offline? Else change the info on chrome webstore saying it is working offline.

I've just tested it again and it works for me.  I am making some updates today so I will see if that helps you.


[OPPRO-243] Support spark33 shim layer (pr1)

This PR will change much, so separate it to many PRs to avoid continuous conflict

@jinchengchenghh Can we consider binding Gluten minor versions to different Spark minor versions?
gluten-1.0.x rely on spark-3.2.x
gluten-1.1.x rely on spark-3.3.x
,etc.

I am thinking about if we can either support different Spark version by different Gluten version, e.g.

gluten-1.0.x -> spark-3.2.x
gluten-1.1.x -> spark-3.3.x

or we just support as many Spark versions in a single gluten bundled build, by programmatically loading different shim codes at runtime after checking Spark version running in current JVM.
Have you happened to make some investigations on such topics?

And delta lake newest version only support newest spark version

Delta Lake version
Apache Spark version

2.1.x
3.3.x

2.0.x
3.2.x

1.2.x
3.2.x

1.1.x
3.2.x

1.0.x
3.1.x

0.7.x and 0.8.x
3.0.x

Below 0.7.0
2.4.2 - 2.4.

We will support the latest 2 spark version, other older version can use our older version, so if spark release 3.4.x, we will not support 3.2 and upgrade gluten version to a new version

Do you think use gluten-spark3.2_2.12-1.0.0-snapshot-jar-with-dependencies.jar is a good idea?

That sounds reasonable to me.

We will support the latest 2 Spark version

Yes, by all means marking the supported Spark version somewhere if we decide to only support a specific version in a specific jar.

And delta lake newest version only support newest spark version

Also noted that they do bind their minor version to Spark minor version. So they can roll their minor versions in parallel.


Docker improvements

Codecov Report

Merging #36 (84cfd5c) into master (e202827) will increase coverage by 0.12%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #36      +/-   ##
==========================================
+ Coverage   93.97%   94.10%   +0.12%
==========================================
  Files          29       30       +1
  Lines         365      373       +8
  Branches       46       52       +6
==========================================
+ Hits          343      351       +8
  Misses         22       22

Impacted Files
Coverage Δ

src/config.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


[test-triage] Timeout of  pwrmgr_random_sleep_power_glitch_reset test

Hierarchy of regression failure
Chip Level
Failure Description
UVM_FATAL @ * us: (chip_sw_random_power_glitch_vseq.sv:58) [chip_sw_random_power_glitch_vseq] wait timeout occurred! has 1 failures:

Test chip_sw_pwrmgr_random_sleep_power_glitch_reset has 1 failures.
2.chip_sw_pwrmgr_random_sleep_power_glitch_reset.2369106033
Line 617, in log /container/opentitan-public/scratch/os_regression/chip_earlgrey_asic-sim-vcs/2.chip_sw_pwrmgr_random_sleep_power_glitch_reset/latest/run.log

  UVM_FATAL @ 33778.037303 us: (chip_sw_random_power_glitch_vseq.sv:58) [uvm_test_top.env.virtual_sequencer.chip_sw_random_power_glitch_vseq] wait timeout occurred!
  UVM_INFO @ 33778.037303 us: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]

Steps to Reproduce

GitHub Revision: 70b1e3d93
dvsim invocation command to reproduce the failure, inclusive of build and run seeds:
./util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_sw_pwrmgr_random_sleep_power_glitch_reset --build-seed<PHONE_NUMBER> --fixed-seed<PHONE_NUMBER> --waves fsdb

Tests with similar or related failures

[ ] chip_sw_pwrmgr_random_sleep_power_glitch_reset

As part of my initial investigation, I used the following command to see the UVM info statements in chip_sw_random_power_glitch_vseq.sv:
./util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_sw_pwrmgr_random_sleep_power_glitch_reset --build-seed<PHONE_NUMBER> --fixed-seed<PHONE_NUMBER> --verbosity h
These are the relevant lines that I see printed:
UVM_INFO @ 2889.828276 us: (chip_sw_random_power_glitch_vseq.sv:56) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.chip_sw_random_power_glitch_vseq] SW test ready
UVM_INFO @ 3159.388276 us: (chip_sw_random_power_glitch_vseq.sv:71) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.chip_sw_random_power_glitch_vseq] HW Booting is called
UVM_INFO @ 3159.388276 us: (chip_sw_random_power_glitch_vseq.sv:92) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.chip_sw_random_power_glitch_vseq] SW message delivered to TB
UVM_INFO @ 3727.936000 us: (chip_sw_random_power_glitch_vseq.sv:94) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.chip_sw_random_power_glitch_vseq] POR reset req set after fixed delay :          10 + variable delay :         104
UVM_INFO @ 3727.936000 us: (chip_sw_random_power_glitch_vseq.sv:106) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.chip_sw_random_power_glitch_vseq] wait for low power entry
UVM_INFO @ 3727.936000 us: (chip_sw_random_power_glitch_vseq.sv:108) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.chip_sw_random_power_glitch_vseq] reset after low power entry
UVM_FATAL @ 33778.037303 us: (chip_sw_random_power_glitch_vseq.sv:58) [uvm_test_top.env.virtual_sequencer.chip_sw_random_power_glitch_vseq] wait timeout occurred!

What this means is that it successfully enters the test the first time, does the reset. Successfully gets into the test the second time around, before hanging on this wait command:
https://github.com/lowRISC/opentitan/blob/0b88ad417414ce8cb6e2b80aeadac88307031073/hw/top_earlgrey/dv/env/seq_lib/chip_sw_random_power_glitch_vseq.sv#L58
Which in turn waits for various log prints from the software in this switch statement:
https://github.com/lowRISC/opentitan/blob/0b88ad417414ce8cb6e2b80aeadac88307031073/sw/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c#L465

There are a number of prints coming from pwrmgr_random_sleep_power_glitch_reset_test.c, some of these contain the word "Booting":
UVM_INFO @  3159.388276 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:485)] Booting and setting deep sleep followed by hw por
UVM_INFO @  6665.627666 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:504)] Booting and setting deep sleep mode followed for low_power entry reset
UVM_INFO @ 11266.694350 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:544)] Booting and setting normal sleep followed by watchdog reset
UVM_INFO @ 13915.474094 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:532)] Booting and setting deep sleep followed by watchdog reset combined with sw_req
UVM_INFO @ 16030.043838 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:552)] Booting and setting deep sleep followed by watchdog reset
UVM_INFO @ 20630.190522 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:504)] Booting and setting deep sleep mode followed for low_power entry reset
UVM_INFO @ 25229.816664 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:532)] Booting and setting deep sleep followed by watchdog reset combined with sw_req
UVM_INFO @ 27343.626408 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:519)] Booting and setting normal sleep followed by watchdog reset combined with sw_req
UVM_INFO @ 29458.456152 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:519)] Booting and setting normal sleep followed by watchdog reset combined with sw_req
UVM_INFO @ 31572.945896 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:532)] Booting and setting deep sleep followed by watchdog reset combined with sw_req
UVM_INFO @ 33687.625640 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:519)] Booting and setting normal sleep followed by watchdog reset combined with sw_req

Only the first one triggers the vseq test. I currently have two ideas that need more investigation:

The hardware may need to trigger on every one of the software "Booting..." prints. The reason is that the hardware requires 12 iterations and the software has 12 entries in RST_IDX which determines what type of reset is done.
The other thing is that the values in RST_IDX are repeating, which I'm not sure if that is desirable.

Values of RST_IDX for this run:
UVM_INFO @ 3156.958276 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:433)] RST_IDX[0] = 2
UVM_INFO @ 6663.187666 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:433)] RST_IDX[1] = 4
UVM_INFO @ 11264.134350 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:433)] RST_IDX[2] = 9
UVM_INFO @ 13913.044094 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:433)] RST_IDX[3] = 6
UVM_INFO @ 16027.633838 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:433)] RST_IDX[4] = 8
UVM_INFO @ 20627.730522 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:433)] RST_IDX[5] = 4
UVM_INFO @ 25227.386664 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:433)] RST_IDX[6] = 6
UVM_INFO @ 27341.086408 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:433)] RST_IDX[7] = 7
UVM_INFO @ 29455.916152 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:433)] RST_IDX[8] = 7
UVM_INFO @ 31570.495896 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:433)] RST_IDX[9] = 6
UVM_INFO @ 33685.085640 us: (sw_logger_if.sv:521) [pwrmgr_random_sleep_power_glitch_reset_test_prog_sim_dv(w/device/tests/sim_dv/pwrmgr_random_sleep_power_glitch_reset_test.c:433)] RST_IDX[10] = 7

Since the timeout (33778.037303) only happens less than 100 micro seconds after the last software reset request (33687.625640), I am testing whether simply increasing the timeout will fix this test.

I've now opened a PR: https://github.com/lowRISC/opentitan/pull/16785 to increase the timeout and once merged will close out this issue.


Erro on task  Convert JMeter Results to JUnit Format

I didn't  understand what is necessary to perform the most basic test and publish.
At Jmeter folder I just let the sample.jmx I'm receiving the following error on the moment of Convert Jmeter Resullts:

I understand the script python don't found results.jtl , but  the tasks before works without errors and  generate this files on artifact:

What I'm missing out?

Hello, anyone can help ? Follow more information: Im receiving the follow error on the Collect JMeter Controller and Worker Logs:

Same issue here... but no idea how to fix. I think that the test did not even run

Hey @allantargino please some ideia why this error ?

@EdiFirst I pulled the newest version from the repository and then the issue was fixed. I think it had something to do with the az copy update.

@EdiFirst I pulled the newest version from the repository and then the issue was fixed. I think it had something to do with the az copy update.

Thank you @leonK-BO but there was a trouble with az copy too , but I already solve. What version did you got ? It's generated the jtl ?

@EdiFirst that one: https://github.com/Azure-Samples/jmeter-aci-terraform/tree/cdabee3a400a73e84fab6b4e6fc9e44788b9ef9b

Hi @EdiFirst, sorry the delay. From the image, the JMX file seems to be not present on the storage mount. Have you tried the newest fix that @leonK-BO mentioned?
Try to see if the jmx is present on the storage file share directly on Azure (using the portal or the CLI)

Hi @EdiFirst, sorry the delay. From the image, the JMX file seems to be not present on the storage mount. Have you tried the newest fix that @leonK-BO mentioned?
Try to see if the jmx is present on the storage file share directly on Azure (using the portal or the CLI)

No problem, yes the are files on storage:

Yes I saw the approach from @leonK-BO, but those azcopy tasks I already solved ,( just changed the path to results files as recommended):

It's like the jtl are not being generated by test execution. I'm not sure why this error: Can't open sample.jmx at task: 'RESULTS: Collect JMeter Controller and Worker Logs' This task should not try open sample.jmx should It ?

So @allantargino @leonK-BO Please some idea? I added the same code from repo and I'm receiving the same error (about could not open  sample.jmx) .

It's like the jtl are not being generated by test execution. I'm not sure why this error: Can't open sample.jmx at task: 'RESULTS: Collect JMeter Controller and Worker Logs' This task should not try open sample.jmx should It ?

That task simply prints the JMeter logs from controller and worker(s), so one of the nodes actually couldn't find sample.jmx. Since the file was in the share, the next thing to check is if the share was mounted properly on the node. Did you happen to change this part in main.tf?
    volume {
      name                 = "jmeter"
      mount_path           = "/jmeter"
      read_only            = true
      storage_account_name = azurerm_storage_account.jmeter_storage.name
      storage_account_key  = azurerm_storage_account.jmeter_storage.primary_access_key
      share_name           = azurerm_storage_share.jmeter_share.name
    }

Hey @devlie thank you by attention. Yes I change it from read_only to false. One detail that I realize running pwd inside de tf command was that the container is starting on the path: opt/apache-jmeter-5.1 (something like this), I believe because of that its not opening jmx file, because it doesn't exist on this path, the operation of copy are not working.

Does anyone know how to find the artifacts in azure portal? Like this?


Change telephone limit to 11.

Some countries have two-digit country code, so the limit should be 11.

10 digits it's only for the phone numbers not for the country code.
4 digits for somes north american countries like Bahamas or Barbade
4+10=14


Remove modin-spreadsheet package

Comment:
Currently, the build step for this output is skipped and there are no plans to support the package.

Closed in https://github.com/conda-forge/modin-feedstock/pull/148.


Add to dask graph mid-computation

Sometimes we learn about more tasks to compute during computation.  At the moment the dask schedulers don't support this and with good reason.  The state that we initialize at the beginning of computation might be tricky to update.
In practice our current solution to this problem is to have several completely separate calls to get.  This is simple and effective but loses some potential parallelism as we wait for stragglers.
However, in some cases this might be more doable.  In particular if the tasks that we want to add to the existing graph don't overlap with existing tasks then merging scheduling states might be straightforward.
A prototype implementation of this might add a function emit_tasks
from dask.async import incoming_task_queue

def emit_tasks(dsk, keys):
    incoming_task_queue.put((dsk, keys))

The hard part would be creating a function that could robustly merge two states.
from toolz import merge
def merge_state(old, new):
    return {'cache': merge(old['cache'], new['cache']),
            'running': old['running']
            'ready': old['ready'] + new['ready']
...

To be clear, it's not clear that this is a good idea.  Just something that has come up a couple of times and that we should probably keep in the backs of our minds.

Consider the the pipeline consists of a few computations, i.e. f -> g -> h, and suppose that f is very expensive to calculate, and g throws some error, I think it would be a waste to throw away the states dictionary and restart the whole pipe again. What if we could return the states dictionary, tweak it abit and resume the whole pipeline from where it stops?

If you supply your own cache you can manage this now if you're using the standard scheduler
In [1]: def inc(x):
    return x + 1
   ...:

In [2]: def throws(x):
    raise Exception()
   ...:

In [3]: dsk = {'x': 1, 'y': (inc, 'x'), 'z': (throws, 'y')}

In [4]: cache = {}

In [5]: import dask

In [6]: dask.get(dsk, 'z', cache=cache)
Exception:

In [7]: cache
Out[7]: {'y': 2}

In [8]: dsk.update(cache)

In [9]: dsk
Out[9]: {'x': 1, 'y': 2, 'z': (<function __main__.throws>, 'y')}

Thanks for the advice. How about the `get

All of dask.get, dask.threaded.get and dask.multiprocessing.get are mostly the same.  This should work with all of them.

This can be done with the distributed scheduler, which also operates well on a single machine.  Closing.


Ingester: defer converting labelPairs to Metric until flush

Another go at #997 , in which the code to delete blank labels was wrong.
I have added a unit test with ~a blank label~ two blank labels, since I got it wrong for that case the second and third attempt.
Also added a String() function so labelPairs print out like Metrics.

This branch is in production now at Weaveworks; CPU is down about 30% and memory down about 12%

LGTM!


m4 4.8 could have numeric on choice

    choices:
    - value: 1
      language:
        default:
          name: One
          description: ''
    - value: 3
      language:
        default:
          name: Three
          description: ''
    - value: 5
      language:
        default:
          name: Five
          description: ''
    type: choice
    choiceType: *ref_1
    defaultValue: 1
    language:
      default:
        name: Enum23
        description: 'Number of masters (VMs) in the container service cluster. Allowed values are 1, 3, and 5. The default value is 1.'
    protocol: {}

  - &ref_1
    type: number
    defaultValue: 1
    precision: 32
    language:
      default:
        name: Number
        description: 'Number of masters (VMs) in the container service cluster. Allowed values are 1, 3, and 5. The default value is 1.'
    protocol: {}


⚠ Bofrost.de has degraded performance

In 35998e7, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 922 ms

Resolved: Bofrost.de performance has improved in 903cb15 after 16 minutes.


feat: add command to change the project_name

Change name in melos.yaml
Change scripts in melos.yaml
Change dir names of `<project_name> and <project_name_ui>
Change dir names of all `packages
Change name in pubspec.yaml of all packages
Change imports and class names of all packages
Change some files in native part (?)

Rename all paths to update project name.
Replace all Strings below the project root in call kinds of cases (e.g camelCase, pascalCase, snakeCase ,...) to the new project name in same case.

The renaming of src files seems to error prone atm.


Implement/expose simplex method to compute orientation matrix UB

Implement (expose) the libhkl simplex method to refine the orientation matrix UB.  As described in https://github.com/bluesky/hklpy/issues/40#issuecomment-841672949,

The case of computing UB with more than 2 reflections is described in the libhkl documentation (simplex computation with more than 2 reflections using the GSL library) but not yet supported in the hklpy code.  This code should be revised as the simplex technique is supported in hklpy.

Already implemented as method affine(): https://github.com/bluesky/hklpy/blob/360609e0a73122e219e915367a4032cfa43c739e/hkl/sample.py#L377-L381


Docs pages are down

H,i it looks like there is an issue with docs page.
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
Opened docs tab, currently it is set to https://sonobuoy.io/docs/v0.57.2
What did you expect to happen:
Get docs
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
here screenshot

#1987 addresses it


H5pyDeprecationWarning

Hi,
I was trying to convert the bas.h5 RS-II Pacbio reads to fasta format by using:
bash5tools.py --outFilePrefix myreads --outType fasta --readType subreads m160604_s1_p0.bas.h5
and it gave me the following error:
miniconda2/lib/python2.7/site-packages/h5py/_hl/dataset.py:313: H5pyDeprecationWarning: dataset.value has been deprecated. Use dataset[()] instead.   "Use dataset[()] instead.", H5pyDeprecationWarning)
Is there any thing that I can do to fix this ?
Thanks

Hi,
Something similar happen to me and I got the following warning:
/usr/local/lib/python2.7/dist-packages/pbcore-1.2.10-py2.7.egg/pbcore/io/BasH5IO.py:294: H5pyDeprecationWarning: dataset.value has been deprecated. Use dataset[()] instead.
holeNumbers = self._mainBasecallsGroup["ZMW/HoleNumber"].value
as it is said in the warning, in my case by changing  line 294 in the BasH5IO.py script the following it was fixed:
Original:
numEvent   = h5Group["ZMW/NumEvent"].value
Changed:
numEvent   = h5Group["ZMW/NumEvent"][()]
Hope it helps


Documentation and PG14

Hi,
I have raised a pull request to improve the README and update to PG14. Please feel free to review.

PR is merged. Thanks for the help.


Support for stock Relay.route instead of Query

Hi,
I tried to use a Relay.route instance as value for Query param on a Route like this:
class ViewerQuery extends Relay.Route {

  static routeName= 'ViewerQuery'

  static paramDefinitions = {
    userID: {required: true},
  }

  static queries = {
    user: () => Relay.QL`query { user(id: $userID) }`,
  }
}

var ViewerQuery = new ViewerQuery({userID: userID});
```

and then on my Route

```
<Route path='/' component={Index} queries={ViewerQuery} renderFailure={function(error, retry) {console.log(error); }} >
```
It throw an error 'query is not a function' from routeAggregator.js
It would be great if we could avoid path='/:userID' to get the userID params in our query.
Do you plan to support this feature?
Thanks for what you've done so far! ;)

This is explicitly not supported - the route is owned by React Router, not by Relay. You also have to specify the URL parameters in the path anyway so React Router knows what to pick up.


add find count to close #283

.find().count() will return a count of the number of matching records for a query.
This returns only the number of results without needing to collect the records.

first attempt at a PR here!
please review and propose changes to match code style and tests.
There was not an obvious way to implement this much needed feature.
Using the AGGREGATE GROUP BY REDUCE feature may not be the best choice. Would love to find a better alternative.
Currently, this implementation is not working for queries where multiple find parameters match the same record. It will count duplicate matches twice. So the current implementation works only for queries with single parameters and the base find().count() use case.


Avoid SGMatrix/SGVetor in public linalg API

We realised a slight design issue in the linalg library:
Currently, a caller needs to pass SGMatrix<T> or similar, which means the template argument T needs to be known at call time. As linalg is intended to be called from the algorithm implementations, this requires data to be type-casted (i.e. T=float64_t) in the algorithm (as mostly done in Shogun atm), which is bad -- the algorithms should be free of any low-level types. For examples, one problem is that most Shogun algorithms explicitly cast the data to SGMatrix<float64_T>, so it is not possible to run the algorithm on other floating point precision. We have ad-hoc solutions for using multiple float bandwidths, but these just bloat the code, dont work for other types, and can be avoided using the below ideas. Here you go
This task is

Think of the old SGMatrix<T> as SWIGMatrix<T>, i.e. it is only a memory wrapper for the interfaces.
Introduce new data structures Matrix, SparseVector, etc (feel free to come up with better names).
Those classes are explicitly not templated (they contain a pointer to data and type information inside though).
Add methods to linalg such that they accept the new types. Inside of the linalg method, you then (at runtime) extract the type information, and call the appropriate *_impl method (these do already exist)
Potentially, we might remove all the templated methods from the linalg interface.

Before you start coding: there is some serious design thinking required on how to cast the type free new Matrix (think LinalgMatrix), so the typed version. We don't know the best solution yet, but have an idea which we are happy to share. Ping me or @vigsterkr


Better support for custom host/base url in CLI / env vars

Following on from #6337 we need to make sure CLI tasks can correctly work out their intended full URL.
Previously this was doing using $_FILE_TO_URL_MAPPING which has now been removed.
The environment variable SS_HOST has been added, but this only addresses the host name and not the protocol or base url (the sub directory that SS may be running in on a domain).
We currently have the ability to set Director.alternate_base_url as well as alternate_protocol and alternate_host. These can be used in combination but their effect isn't limited solely to CLI and this may be undesirable or inflexible on sites that require multiple domains to run.
Therefore, some environment variable(s) should be made available to provide a fallback when there is no other means to determine the host/protocol/base url.

Side note: it is currently possible to set the alternate_base_url to a full url (eg: https://example.com/base/). I feel this is confusing and we complicates our code and makes the behaviour less predictable. It may be worth deprecating this variable and replacing it with base_path as it appears the original intention was really only to set the base directory. It also leads to unexpected behaviours; if alternate_protocol is set, which protocol should be used - the one from the alternate_base_url or from alternate_protocol?

Side note: it is currently possible to set the alternate_base_url to a full url (eg: https://example.com/base/). I feel this is confusing and we complicates our code and makes the behaviour less predictable.

I'm not sure I agree. A URL captures protocol, host, and path in a single well-recognised string.

It also leads to unexpected behaviours; , which protocol should be used - the one from the alternate_base_url or from alternate_protocol?

Maybe we shouldn't have alternate_host and alternate_protocol? I agree that we should only have 1 way of providing a given piece of config.

In any case we should pick between either providing these options:

SS_HOST - e.g. "localhost"
SS_BASE_PATH - e.g. "/subsite"
SS_PROTOCOL - e.g. "https"
SS_PORT - e.g. "8080", "80", "443", or ""/null to infer from the protocol

Or this one:

SS_BASE_URL: "https://localhost/subsite"

The other question how this manifests as Director properties. We have alternate_base_url / alternate_host, which are slightly confusing names.
The best bet is probably to treat the values as the canonical URL rather than the default, and for instance when sending emails from a web request, favour the use of canonical URLs.
Additionally, perhaps we should refactor how Director is triggered so that we're always passing it an HTTPRequest object, and then Director doesn't need to be responsible for all this URL inferencing.

Alternatively an SS_WEBROOT environment variable could be use to infer the sub-paths. It would essentially be treated the same as the key of file-to-url-mapping, but wouldn't support multiple values.

@silverstripe/core-team my recommendation here is that we return to something closer to SS3's approach and allow for a SS_BASE_URL environment variable that can be a URL. This is a compact  and intuitive way of providing host, base path, protocol, and port in a single config option.
Can we get some votes on that solution?

Yes that's fine. we could support 'mixed' protocol by allowing protocol-less urls. E.g. //google.com/subdir.

I'm happy with a single consistent approach. At the moment, in 3, there are to many options. Alternate Base URL can mean base path or full URL...

Fix at https://github.com/silverstripe/silverstripe-framework/pull/6798


Velocity Support

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Simple Voice Chat is releasing a version for Velocity and it would be nice if this plugin could be updated or built to work with it, I know this is a big change and that no one is actively working on this project but it would be greatly appreciated
Describe alternatives you've considered
or maybe it could at least hook into a velocity instance while still running on the actual server
Additional context
I use this so bedrock (Geyser) players can use voicechat to and I want to switch to the velocity version but I also want bedrock players to still be able to use it

you need velocity for lobby right? Question why do you need voice chat in lobby

you need velocity for lobby right? Question why do you need voice chat in lobby

It would allow the Discord Bots to be shared across multiple servers instead of having to create seperate bots for each server, which is really annoying and impractical.

you need velocity for lobby right? Question why do you need voice chat in lobby

Velocity can also be used to create multiple SMPs in one network, for example.

I guess I never replied to this, but I don't plan to add this feature. Anyone is free to make a PR though


Fixed the content type in requests with external data

Added an explicit indication of the text/plain content type with UTF-8 encoding for an SQL query in MultipartEntityBuilder, otherwise the text/plain content type with ISO_8859_1 encoding is used and Latin letters turn into'??????'

Thanks for your contribution @MikhailMel. The change has been merged.


Enhance User Exit Framework

Currently, we are limited to one class (zcl_abapgit_user_exits) for implementing all exist methods. This leads to conflicts or manual effort when several solutions need to implement exits.
---
title: Existing framework
---
classDiagram
  direction LR
  class zcl_abapgit_exit {
    +gi_exit zif_abapgit_exit
    +create_http_client()
    +wall_message_repo()
  }
  class zcl_abapgit_user_exit {
    +create_http_client()
    +wall_message_repo()
  }
  zcl_abapgit_exit .. zcl_abapgit_user_exit

Note: There's a lot of text (documentation) below but the resulting solution is actually quite simple (see code example below).
Goals of this Enhancement

Compatibility: existing user exits continue to work as is
Development: new framework is easy to implement and maintain
Deployment: repos are able to ship user exit implementations
Runtime: support for more than one exit class within one or more repos
Migration: low effort to move existing user exit implementations to the new framework

Solution
---
title: Enhanced framework
---
classDiagram
  class zcl_abapgit_exit_caller  {
    <<new>>
    +gt_exits zif_abapgit_exit
    +create_http_client()
    +wall_message_repo()
  }
  class zcl_abapgit_user_exit {
  }
  class zcl_abapgit_exit_super {
    <<new>>
    +create_http_client()
    +wall_message_repo()
  }
  class zcl_abapgit_user_exit_client {
    +create_http_client() redefined
  }
  class zcl_abapgit_user_exit_wall {
    +wall_message_repo() redefined
  }
  zcl_abapgit_exit_caller <|-- zcl_abapgit_user_exit : inherit
  zcl_abapgit_exit_super <|-- zcl_abapgit_user_exit_client : inherit
  zcl_abapgit_exit_super <|-- zcl_abapgit_user_exit_wall : inherit

Class zcl_abapgit_exit_super

Contains a default implementation for all exit methods (i.e. just a RETURN statement)
Is used as super class for classes implementing exists
Therefore, a class for user exists just needs to redefined the methods it wants to implement
Changes to unused methods and addition of new methods will not impact your exit class anymore

Class zcl_abapgit_exit_caller

Collects all sub-classes of zcl_abapgit_exit_super
Is used as a super-class for zcl_abapgit_user_exit (see below)
For each exit method, zcl_abapgit_exit_caller calls the corresponding method in the sub-classes collected above (obviously, only redefined methods will have any effect)
For most methods, all sub-classes will be called (cumulative effect)
For some methods, the first successful call will win (exclusive effect)

Limitation
Currently, the solution only works for the developer version. The standalone continues to work with the existing include zabapgit_user_exit.
Note: I'm still investigating if and how this framework can work also for the standalone version.
Downside
When adding new exit methods, we have to maintain two additional classes:

zif/cl_abapgit_exit: same as before
zcl_abapgit_exit_super: add RETURN to new method implementation
zcl_abapgit_exit_called: implement a LOOP over all exit sub-classes

However, the additional effort is very low and only once per exit method.
Example
The implementation of zcl_abapgit_user_exit is reduced to the following (no method code):
CLASS zcl_abapgit_user_exit DEFINITION
  PUBLIC
  INHERITING FROM zcl_abapgit_exit_caller
  CREATE PUBLIC.

  PUBLIC SECTION.
  PROTECTED SECTION.
  PRIVATE SECTION.
ENDCLASS.

CLASS zcl_abapgit_user_exit IMPLEMENTATION.
ENDCLASS.

Here is one exit classes for creating the HTTP client based and another for setting a wall message:
CLASS zcl_abapgit_user_exit_client DEFINITION
  PUBLIC
  INHERITING FROM zcl_abapgit_exit_super
  CREATE PUBLIC.

  PUBLIC SECTION.

    METHODS zif_abapgit_exit~create_http_client REDEFINITION.

  PROTECTED SECTION.
  PRIVATE SECTION.
ENDCLASS.

CLASS zcl_abapgit_user_exit_client IMPLEMENTATION.

  METHOD zif_abapgit_exit~create_http_client.

    DATA:
      lv_host        TYPE string,
      lv_destination TYPE rfcdest.

    lv_host = zcl_abapgit_url=>host( iv_url ).

    IF lv_host CS 'github'.
      lv_destination = 'GITHUB'.
    ELSE.
      RETURN.
    ENDIF.

    cl_http_client=>create_by_destination(
      EXPORTING
        destination              = lv_destination
      IMPORTING
        client                   = ri_client
      EXCEPTIONS
        argument_not_found       = 1
        destination_not_found    = 2
        destination_no_authority = 3
        plugin_not_active        = 4
        internal_error           = 5
        OTHERS                   = 6 ).

    IF sy-subrc <> 0.
      zcx_abapgit_exception=>raise_t100(  ).
    ENDIF.

    zcl_abapgit_login_manager=>clear( ).

  ENDMETHOD.
ENDCLASS.

CLASS zcl_abapgit_user_exit_wall DEFINITION
  PUBLIC
  INHERITING FROM zcl_abapgit_exit_super
  CREATE PUBLIC.

  PUBLIC SECTION.

    METHODS zif_abapgit_exit~wall_message_repo REDEFINITION.

  PROTECTED SECTION.
  PRIVATE SECTION.
ENDCLASS.

CLASS zcl_abapgit_user_exit_wall IMPLEMENTATION.

  METHOD zif_abapgit_exit~wall_message_repo.

  ENDMETHOD.
ENDCLASS.

The implementation becomes a lot simpler and more robust. Plus you can have any number of such exit sub-classes. Repositories can include sub exit sub-classes.
Migration
You can easily transition from an existing zcl_abapgit_user_exit implementation to several classes:

Create one or more exit classes each with zcl_abapgit_exit_super as superclass
Redefine only methods as required and copy corresponding code from zcl_abapgit_user_exit
Once all methods are migrated to sub-classes, replace zcl_abapgit_user_exit as shown in the example above

Practical Experience
I have distributed methods across six exit classes and four repos and it works perfectly well. 🎉
Closes #4786

Certainly depends on the exit method. In some cases, having multiple classes won't make much sense (like for changing the proxy). But why would someone implement these methods multiple times?
If the order matters, you can redefine the method inherited from zcl_abapgit_exit_caller. You could use another order, or call only selected exit classes. Up to the user.
I have three different wall messages. Each is adding a bit of HTML. No problem.

But why would someone implement these methods multiple times?

thats my point, no-one would. But pulling 4 different exit classes, the developer will not easily know what is implemented and how/if they overlap or ordering matters
Alternative solutions:

do one interface per method, allows shipping
go full BADI, then its possible to get an overview and a familiar setup

We don't have to ship it with AG. I will put it in a separate repo.


Fix broken link to docs for cross origin script errors

Redo PR for #520 because slashes in the branch names break CI at the moment 😬

I can't "approve" this because I'm now the PR author but for the paper trail, I approve.


Your example is broken

Your 3rd to last example command has permissions set to "crdw" but that doesn't work.  They should be "rl".
[Enter feedback here]

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

ID: 240bf4b5-fe9e-7bb3-9494-fff3d085f3ea
Version Independent ID: b934319b-35be-f1e3-402c-c062ef13d99b
Content: What to do if there if an Azure service disruption that affects Managed HSM - Azure Key Vault
Content Source: articles/key-vault/managed-hsm/disaster-recovery-guide.md
Service: key-vault
Sub-service: general
GitHub Login: @mbaldwin
Microsoft Alias: mbaldwin

@carrel-gr
Thanks for your feedback! We will investigate and update as appropriate.

Thanks! This aligns with what is documented here: https://docs.microsoft.com/en-us/azure/key-vault/managed-hsm/disaster-recovery-guide
I made a pull request to update the guide.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/192186


[Feature Request]: Add auto-generated notice at the top of generated file

🔮 Relevant Command
importer generate
🗂 Language Type
All
🔎 Request Details
Because Importer is essentially code-generation tool, it should add a note at the top of the file that the file is created by some automation.
This could be useful for importer update as well, but importer update does not have any external template to be reviewed. From code review perspective, importer generate can benefit from this approach, but it may be better not to add such a note for importer update.

This ticket is probably better tackled by some documentation around the use of .gitattributes.
https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/customizing-how-changed-files-appear-on-github
https://github.com/github/linguist/blob/master/docs/overrides.md#generated-code

This ticket should be still tackled, as importer generate template.md -o ./some/directory/output.md would break the importer references as the relative paths change. Along with #11, it would be important how the file was created using which template file.
Fixing up relevant paths for each entry may be another possibility, if generate is used once to create a new file, but update to be used going forward. I don't particularly see a use case for that, so that will be considered separately.


Bibtex references don't capitalize countries and other items that should be capitalized

e.g. in http://childallowance.ubicenter.org/empirical.html#uganda-wfp-food this should be Tanzania:

and this should be LEAP:

To fix, add extra curly braces, e.g. {Tanzania} and {LEAP} in references.bib.
@jwal1024 could you take a stab at this?

Thanks @jwal1024 for addressing these two instances in https://github.com/jwal1024/childallowance/commit/12f7f05e175c88efb4b5479d7d0f371bed4db9cc. There are still several more throughout references.bib, could you please fix those in a pull request? This will allow for review before committing to master and it will also trigger tests and the updating of the site.


Add python 3.13 support

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

Project coverage is 100.00%. Comparing base (556b97f) to head (c770fda).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #264   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          139       139
  Branches        12        12
=========================================
  Hits           139       139

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


Maps

Brief Description of Fix
Detailed Description including steps taken and any changes made
Linked Issue
Closes #_ (Replace with Issue number)

Simple program to show implementation of maps/dicts in GO


The requirements.txt file is missing

The requirements.txt file is missing, which is preventing me from reproducing the experiment. Could you please tell me where I can obtain the requirements.txt file?

the requirements.txt is same as ties merging: https://github.com/prateeky2806/ties-merging


Does not support tasks_iam_role_statements through the single module?

Is your request related to a new offering from AWS?
Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

No 🛑: please wait to file a request until the functionality is avaialble in the AWS provider
Yes ✅: please list the AWS provider version which introduced this functionality

Is your request related to a problem? Please describe.

As the README, I want to create resources through a single module that creates both the cluster and service resources. But by this single module, it only supports task_exec_iam_statements for task exec role, but does not support tasks_iam_role_statements for task role.
Describe the solution you'd like.

Describe alternatives you've considered.

Additional context

it does https://github.com/terraform-aws-modules/terraform-aws-ecs/blob/2604124d05974c2ee47ff7194d62d55ac425a3cb/main.tf#L148
Are there any issues you are seeing with this?

it does
https://github.com/terraform-aws-modules/terraform-aws-ecs/blob/2604124d05974c2ee47ff7194d62d55ac425a3cb/main.tf#L148
Are there any issues you are seeing with this?

Yes, here is the code I use, then it pop up the below error.
module "ecs" {
  source  = "terraform-aws-modules/ecs/aws"
  version = "5.2.2"
  ...
  create_tasks_iam_role = true
  tasks_iam_role_statements = something
  }

The error message is below.
Error: Unsupported argument
│
│   on ecs.tf line 78, in module "ecs":
│   78:   create_tasks_iam_role = true
│
│ An argument named "create_tasks_iam_role" is not expected here.
╵
╷
│ Error: Unsupported argument
│
│   on ecs.tf line 79, in module "ecs":
│   79:   tasks_iam_role_statements = [
│
│ An argument named "tasks_iam_role_statements" is not expected here.

Thank you so much for looking at this.

Can you provide a proper reproduction

Can you provide a proper reproduction

Yes, I can paste my code here.
module "ecs" {
  source  = "terraform-aws-modules/ecs/aws"
  version = "5.2.2"

  cluster_name = "xxx"

  cluster_configuration = {
    execute_command_configuration = {
      logging = "OVERRIDE"
      log_configuration = {
        cloud_watch_log_group_name = "xxx"
      }
    }
  }

  fargate_capacity_providers = {
    FARGATE = {
      default_capacity_provider_strategy = {
        weight = 100
      }
    }
  }

  services = {
    xxx = {
      cpu    = 4096
      memory = 4096
      volume = {
        my-vol = {
          efs_volume_configuration = {
            file_system_id     = module.efs.id
            root_directory     = ""
            transit_encryption = "DISABLED"
          }
        }
      }

      # Container definition(s)
      container_definitions = {

        xxx = {
          cpu       = 4096
          memory    = 4096
          essential = true
          image     = "placeholder"
          mount_points = [
            {
              sourceVolume  = "my-vol",
              containerPath = "/opt/backup"
            }
          ]
        }
      }

      subnet_ids = concat(data.aws_subnets.private2a.ids, data.aws_subnets.private2b.ids, data.aws_subnets.private2c.ids)
      security_group_rules = {
        egress_all = {
          type        = "egress"
          from_port   = 0
          to_port     = 0
          protocol    = "-1"
          cidr_blocks = ["<IP_ADDRESS>/0"]
        }
      }
    }
  }

  create_task_exec_iam_role = true
  create_task_exec_policy   = true
  task_exec_iam_statements = [
    {
      actions   = ["s3:PutObject"]
      effect    = "Allow"
      resources = ["arn:aws:s3:::xxx"]
      sid       = "S3"
    }
  ]

  create_tasks_iam_role = true
  tasks_iam_role_statements = something

  tags = local.common_tags
}

Plan for this code, it pops up the error An argument named "create_tasks_iam_role" is not expected here. and An argument named "tasks_iam_role_statements" is not expected here.
Reproduce everytime.

Hello @bryantbiggs , may I know do you get any chance to reproduce the issue or is it anything wrong about my usage of the module?
Thank you so much in advance.

tasks role is specific to the service/task definition so it goes inside the service definition. also, I see you have S3 permissions on the task exec role - this role is used during task startup. so if you are pulling images or getting secrets and populating the task definition, it needs permission to do those things. the AWS permissions required by your task, those will go in the tasks role
Here is an updated copy of the code you provided that should do what you are looking for (bar from the correct permissions which you will need to amend):
module "ecs" {
  source  = "terraform-aws-modules/ecs/aws"
  version = "5.2.2"

  cluster_name = "xxx"

  cluster_configuration = {
    execute_command_configuration = {
      logging = "OVERRIDE"
      log_configuration = {
        cloud_watch_log_group_name = "xxx"
      }
    }
  }

  fargate_capacity_providers = {
    FARGATE = {
      default_capacity_provider_strategy = {
        weight = 100
      }
    }
  }

  services = {
    xxx = {
      cpu    = 4096
      memory = 4096
      volume = {
        my-vol = {
          efs_volume_configuration = {
            file_system_id     = module.efs.id
            root_directory     = ""
            transit_encryption = "DISABLED"
          }
        }
      }

      # Container definition(s)
      container_definitions = {

        xxx = {
          cpu       = 4096
          memory    = 4096
          essential = true
          image     = "placeholder"
          mount_points = [
            {
              sourceVolume  = "my-vol",
              containerPath = "/opt/backup"
            }
          ]
        }
      }

      subnet_ids = concat(data.aws_subnets.private2a.ids, data.aws_subnets.private2b.ids, data.aws_subnets.private2c.ids)
      security_group_rules = {
        egress_all = {
          type        = "egress"
          from_port   = 0
          to_port     = 0
          protocol    = "-1"
          cidr_blocks = ["<IP_ADDRESS>/0"]
        }
      }

      create_tasks_iam_role = true
      tasks_iam_role_statements = [
        {
          actions   = ["s3:PutObject"]
          effect    = "Allow"
          resources = ["arn:aws:s3:::xxx"]
          sid       = "S3"
        }
      ]
    }
  }

  tags = local.common_tags
}

tasks role is specific to the service/task definition so it goes inside the service definition. also, I see you have S3 permissions on the task exec role - this role is used during task startup. so if you are pulling images or getting secrets and populating the task definition, it needs permission to do those things. the AWS permissions required by your task, those will go in the tasks role
Here is an updated copy of the code you provided that should do what you are looking for (bar from the correct permissions which you will need to amend):
module "ecs" {
  source  = "terraform-aws-modules/ecs/aws"
  version = "5.2.2"

  cluster_name = "xxx"

  cluster_configuration = {
    execute_command_configuration = {
      logging = "OVERRIDE"
      log_configuration = {
        cloud_watch_log_group_name = "xxx"
      }
    }
  }

  fargate_capacity_providers = {
    FARGATE = {
      default_capacity_provider_strategy = {
        weight = 100
      }
    }
  }

  services = {
    xxx = {
      cpu    = 4096
      memory = 4096
      volume = {
        my-vol = {
          efs_volume_configuration = {
            file_system_id     = module.efs.id
            root_directory     = ""
            transit_encryption = "DISABLED"
          }
        }
      }

      # Container definition(s)
      container_definitions = {

        xxx = {
          cpu       = 4096
          memory    = 4096
          essential = true
          image     = "placeholder"
          mount_points = [
            {
              sourceVolume  = "my-vol",
              containerPath = "/opt/backup"
            }
          ]
        }
      }

      subnet_ids = concat(data.aws_subnets.private2a.ids, data.aws_subnets.private2b.ids, data.aws_subnets.private2c.ids)
      security_group_rules = {
        egress_all = {
          type        = "egress"
          from_port   = 0
          to_port     = 0
          protocol    = "-1"
          cidr_blocks = ["<IP_ADDRESS>/0"]
        }
      }

      create_tasks_iam_role = true
      tasks_iam_role_statements = [
        {
          actions   = ["s3:PutObject"]
          effect    = "Allow"
          resources = ["arn:aws:s3:::xxx"]
          sid       = "S3"
        }
      ]
    }
  }

  tags = local.common_tags
}

I tried the above code. Same error.
Error: Unsupported argument
│
│   on ecs.tf line 78, in module "ecs":
│   78:   create_tasks_iam_role = true
│
│ An argument named "create_tasks_iam_role" is not expected here.
╵
╷
│ Error: Unsupported argument
│
│   on ecs.tf line 79, in module "ecs":
│   79:   tasks_iam_role_statements = [
│
│ An argument named "tasks_iam_role_statements" is not expected here.

So I think as long as you use the single module which according to the README, it fails to pass tasks_iam_role.
module "ecs" {
  source  = "terraform-aws-modules/ecs/aws"

I think it work for use it like below.
module "ecs_service" {
  source  = "terraform-aws-modules/ecs/aws//modules/service"

But the thing is it should work through the wrapper cause the single module contain cluster service and task, all in one. That's the reason why I raised this issue call it Does not support tasks_iam_role_statements through the single module?.
Thank you.

This issue has been resolved in version 5.3.0 :tada:


media-types: Define layer media types suffix '+zstd'

Closes: https://github.com/opencontainers/image-spec/issues/787
Signed-off-by: Giuseppe Scrivano<EMAIL_ADDRESS>

LGTM

@AkihiroSuda thanks for the review.  Pushed a new version

@brendandburns @cyphar @jbouzane @jstarks @philips @stevvooe @xiekeyang PTAL
@giuseppe Any idea how to fix travis?

@giuseppe Any idea how to fix travis?

I've opened another PR to address the error raised by "make lint": https://github.com/opencontainers/image-spec/pull/789

rebased on top of the fix for travis

LGTM

@vbatts PTAL

LGTM


Is it working in Blender 3.4

Hello,
as the Title says, is it working in Blender 3.4 ?
Matthias

Hello. It doesn't work for me!?

Hello,
thanks a lot for the answer, so i must not wonder :-)
I think there will be a update comming...
Matthias

Hello,
We have to stick to Blender 3.3 for now as it's the latest LTS version of blender. We can't assure that everything would work with other versions of blender.
Thank you !


Adunits and Timeline Sections - Added bidderRequests and topics to JSON modals

ADUNITS section

added bidderRequests to the JSON modal popup when a user clicks on a bid under the "bidders" column.
also added topics present in a user's browser for a specific url (if any are present), when a user clicks on a bid under the "bidders" column.  if none are present topics will be sent as an empty array.

TIMELINE section

added topics within the json modal popup when a user clicks on an ssp in the timeline section as well (bidderRequests are present here as well, they were there prior to this PR)

thanks @florianerl !

Hi @jlquaccia ,
very welcome 😃 !
I'll do some beta testing with this version and plan to release it beginning of next week.

@florianerl awesome, I see that has been released!  thank you!


Add tests

After some thinking and some motivational sessions, I've decided to start/finish writing tests for the bot. These tests will be available in the spec folder, and will follow the current testing style by bonnici, using Jasmine and Sinon.

:+1:
I'm going to be lazy. I don't like testing. :relieved:

@bonnici
I've been testing out my tests, and all of them fail. Here's the log for it: http://pastebin.com/XjBU0gf7
Most of these errors are Cannot read property 'error' of undefined. This is in baseTrigger, specifically when calling this.winston.error (inheriting winston from chatbot), and me and Efreak don't really know how to fix it. If you do, could you comment on here about it? Also adding one of us on steam would be nice, since we could open up a group chat so it's easier. Thanks.
http://steamcommunity.com/id/dragonbanshee
http://steamcommunity.com/id/efreak

Hmm it looks like winston and some other stuff isn't being initialized before the tests run. It's been a while since I ran the tests so maybe the module updates has broken them. I'll see if I can take a quick look this weekend some time.
I've sent you both friend requests, I'm http://steamcommunity.com/id/steve_holt

Sorry I'm travelling right now and I don't have node or anything set up on my laptop. I'll take a look when I get back home but it will be a few weeks.

OK, just looked into this a bit. There were a few errors in the tests in my branch so I cleaned them up (https://github.com/bonnici/node-steam-chat-bot/commit/0eae3fbf0cd2b4aaae15c6af30ebce3602f6d8e5). I tried running the tests on this branch and ran into a few more errors.
It looks like the winston setup in the bot breaks the tests because it tries to log to a file and can't. I worked around that temporarily by commenting out the winston setup, so you could fix it by making sure whatever code path the tests run does not try to log to file. That should fix "Error: Cannot log to file without filename or stream" and "TypeError: Cannot read property 'error' of undefined".
The other errors look like they are just happening because the code has changed so much that the tests aren't really appropriate anymore (especially the chatBot tests). I'd recommend you start by starting from scratch and completely rewriting the chatBot tests, then use what you learn to make the other tests work.

I'm going to close this now since I don't really have motivation or time to work on this. If I feel like doing it again in the future I'll reopen this thread.


Flakey test:  istio-pilot-e2e-envoyv2-v1alpha3   istio.io/istio/tests/e2e/tests/pilot TestIngressGateway503DuringRuleChange

Describe the bug
I've seen this across several unrelated PRs.  https://k8s-gubernator.appspot.com/build/istio-prow/pr-logs/pull/istio_istio/12278/istio-pilot-e2e-envoyv2-v1alpha3/16369/
istio.io/istio/tests/e2e/tests/pilot TestIngressGateway503DuringRuleChange 1m3s
gateway.networking.istio.io "istio-ingressgateway" created
destinationrule.networking.istio.io "destination-rule-c" created
virtualservice.networking.istio.io "gateway-bound-route" created
destinationrule.networking.istio.io "destination-rule-c" configured
virtualservice.networking.istio.io "gateway-bound-route" configured
destinationrule.networking.istio.io "destination-rule-c" configured
virtualservice.networking.istio.io "gateway-bound-route" deleted
destinationrule.networking.istio.io "destination-rule-c" deleted
gateway.networking.istio.io "istio-ingressgateway" deleted
ingressgateway_test.go:263: Could not parse response codes from the client

See also  #11929 and #11700

Duplicate of https://github.com/istio/istio/issues/11700


fix Disable MOW and memtable on sink node for cloud ci

Proposed changes
Issue Number: close #xxx

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

run buildall


portfolio - sorting tokens

What would you like to be added:
Ability to sort tokens based on these criterias:

[ ] Default (Sort by ID)
[ ] Highest USD
[ ] Lowest USD

@chloezxyy something to take note, how would it look like with translated labels

Adding in design link for easy reference:
https://www.figma.com/file/SDIpZciuxJlUf4xf8yheiY/PRDCT---Mobile-Light-Wallet?node-id=6556%3A133899

Put the list of tokens that we have


Add "open WOF doc from URL" button

If you land on the test page it's blank. So add button at top that says "load WOF place" and accepts URL, to then reload the page with the URL param trick?

I think I finally found a decent path on this one.
The default landing page looks like this:

You can enter a WOF ID and it will use data.whosonfirst.org to figure out which repo to load from or you can pass in your own URL if you want to load a specific branch/fork. In either case, it redirects you to the edit page, but now instead of having a WOF ID in the URL it has an entire URL as a parameter:

That URL is loaded to show in the form and make edits. It uses the wof:repo property of that doc to decide which repository to make the pull request against.

I dig it!
The only change I'd make is to layout them top and bottom instead of side by side...

ID
URL

Instead of - ID | URL
Right now it looks like I should do both fields... Or you could make the find by URL just a button that prompts for the URL value with a dialog?

It's also confusing that the text in the boxes isn't actually text, so clicking them doesn't do anything.

we can add e.g.:  prefix on the text you have in those boxes and call it good?

Adjusted alignment and improved placeholder text:

FYI:

https://github.com/whosonfirst/go-whosonfirst-uri/blob/master/parse.go
https://github.com/whosonfirst/go-whosonfirst-uri/blob/master/parse_test.go

@iandees formatting nit: can you add 2 lines of whitespace between the blue button Find by ID and the text Find by URL, please? Then we can close this out...

Ah, another annoyance on the Bootstrap 3 -> 4 upgrade. Gave it some bottom margin:

Works for me :)


Build proper integration test infrastructure (strategy)

My idea is to introduce some kind of snapshot testing mechanic, which runs the native binary on multiple input files and checks if the output matches the expected format.
odoc does something similar with a home brewed snapshot tester with a mechanic to automatically submit changes to the expect-file in case there are expected changes.

Done with #62 and #77


Option to style template

There must be an option to style the template. Like implementation of Material template and Material icons. I tried searching for template but couldn't find as npm install compiles the project.

I don't fully understand what you mean. I got property [style] to let user provide inline style to the whole component and [styleClass] to provide styleClass. You could learn more about these two from README

I know but the problem is you're using fonts awesome in your your project I guess. What if I want to use Material Icons with Material Input Design? Like floating placeholder etc.

Oh,
I see what you mean. I will look at it.
Thanks.

How does commit https://github.com/DanielYKPan/date-time-picker/commit/b95bd1c41e13f0cf8f2dfb1c01e7e0264241ee52 fix this issue?
Could you give an example of using the picker in conjunction with Material features such as placeholder?

@doginthenight
Sorry, I typed the wrong issue number.
I still working on this...


OneTrust cookie overlay on rockpapershotgun.com

OneTrust cookie overlay on rockpapershotgun.com is not blocked. https://github.com/oblador/hush/pull/44

Duplicates https://github.com/oblador/hush/issues/8

Duplicates https://github.com/oblador/hush/issues/8


Add possibility to configure plugin for element clickability

I am trying to click on an element which is visible, but its attribute enabled is false. The plugin is therefore waiting for it to become true, so the test fails.
Is it possible to configure the plugin to check only if an element exists, regardless of its enabled attribute?

Thanks for checking this so quickly! I'm getting this on macOS, but maybe I'm doing something wrong:
~ [ appium --allow-insecure=adb_shell --log-timestamp  --use-plugins=element-wait --plugin-element-wait-element-enabled-check-exclusion-cmds-list=['click']                                              ] 11:57 am
zsh: no matches found: --plugin-element-wait-element-enabled-check-exclusion-cmds-list=[click]
~ [ appium --allow-insecure=adb_shell --log-timestamp  --use-plugins=element-wait --plugin-element-wait-element-enabled-check-exclusion-cmds-list=\[\'click\'\]                                          ] 11:57 am

[ERROR] Unrecognized arguments: --plugin-element-wait-element-enabled-check-exclusion-cmds-list=['click']

Check with latest version. Readme is updated


Fix: Hyprland/Workspaces' windows disappearing when moving around

Fixes #2557
About this PR
This PR fixes an issue that caused windows to disappear. This was caused because, sometimes, Hyprland's IPC decides to report the window-related event (openwindow, movewindow) before the createworkspace event. This, in turn, caused Waybar to have nowhere to put the moved/opened window, causing it to be discarted.

About the solution
In order to solve this problem, the window creation has been delayed, much akin to how workspaces are created; they are pushed into a vector and are processed during Workspaces::update(). There will be 3 attempts to create each window, accounting for the possibility that the createworkspace message got just late enough that it wasn't processed in the same update() call.

Thanks a lot again!


bug(widget-roster):Add people icon does not overlay the Participants …

https://jira-eng-gpk2.cisco.com/jira/browse/SPARK-66001

wait i lied @akoushke can you change the commit message from bugfix to just fix please? for consistency in our changelog. thanks!


chore: model optional model type required

https://app.shortcut.com/galileo/story/9036/dq-make-the-model-a-manual-param-for-watch-fn?vc_group_by=day&ct_workflow=all&cf_workflow=500000005
In this PR we:

Rename Seq2SeqModelTypes -> Seq2SeqModelType
Make model optional in watch
Make model_type required in watch
Move watch fn to core

Codecov Report
Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (5c5467d) 86.67% compared to head (f6637de) 86.63%.

:exclamation: Current head f6637de differs from pull request most recent head 6e97ccf. Consider uploading reports for the commit 6e97ccf to get more accurate results

Files
Patch %
Lines

tests/integrations/seq2seq/test_core.py
83.33%
3 Missing :warning:

dataquality/integrations/seq2seq/s2s_trainer.py
0.00%
2 Missing :warning:

dataquality/integrations/seq2seq/core.py
92.85%
1 Missing :warning:

...uality/loggers/data_logger/seq2seq/seq2seq_base.py
90.00%
1 Missing :warning:

...ality/loggers/model_logger/seq2seq/seq2seq_base.py
90.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #800      +/-   ##
==========================================
- Coverage   86.67%   86.63%   -0.04%
==========================================
  Files         196      196
  Lines       15555    15569      +14
==========================================
+ Hits        13482    13488       +6
- Misses       2073     2081       +8

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


Add test stage with minified Android builds

This adds a test-sync test stage running all sync tests with minification on Android. It was not possible to add minification for test-base due to our current project setup, but as test-sync holds quite many models and cover reasonably base functionality it will in fact act as a sanity validation of our library-base/proguard-rules-consumer-common.pro configuration, especially initialization of the native class and method references.
If needed it is relatively easy to manually run the full test-base test suite with minification following the instructions in test-base/build.gradle.kts
Closes #1114

We could enable running test-base with minification in CI if we remove its dependency from test-sync. We could manually link the shared sources and add the kotlinx-datetime dependency to test-sync.


Please migrate this Plugin to be used with the new Flat Config for ESLint v9

This Plugin is a very useful tool that I have been using since quite some time. However, since recently we have migrated to ESLint v9 and it would be very helpful if this Plugin can be migrated to use the new Flat Config of the ESLint.

Any updates on this?

Hey. Pr welcome :)
Do you have any info on what’s involved? Does it just error currently if you try and use it?

I have tested it and it seems to work when configured in this way:
// eslint.config.js
import eslint from '@eslint/js';
import redosDetector from 'eslint-plugin-redos-detector';
import tseslint from 'typescript-eslint';

export default tseslint.config(
  eslint.configs.recommended,
  tseslint.configs.strict,
  tseslint.configs.stylistic,
  {
    files: ['src/**/*.ts'],
    plugins: { 'redos-detector': redosDetector },
    rules: {
      'redos-detector/no-unsafe-regex': ['error', { ignoreError: true }],
    },
  }
);

Ah great. Is there anything that I actually need to do then. Other than maybe update the readmr?

I recommend exporting a redosDetector.configs.recommended as this is easier than manually passing the plugin to ESLint. But to keep things simple you can also just update the readme for the flat config file.


Merge pull request #3 from dev-b8u8-github1/dev-b8u8-todo-list

Dev b8u8 todo list

Merged main and spike.


"seen-on-relays" css overflow

notice the broadcast-to-all button overflow

The issue has been fixed https://github.com/digi-monkey/flycat-web/pull/111


Proximity forest testing

Proximity forest needs to be tested under the new parameter spaces, as old ones were incorrect and likely the issue of ~3% accuracy missing.

I can also test this when I can bring myself back (kicking and screaming) to python world. But if you have queue space, use it

err, whats going on here?

Could we perhaps also make the proximity forest unit test a little faster (looking only data subsamples for example), would really appreciate this!

Gone through and tidied it up, and am running it next week, fingers crossed! I'll put some minor queries here that might be addressed in due course (i.e. in the next master push after this one)

there are a lot of functions not in a class. This seems messy to me, whole lot of getters etc. Could they not be inside base class
I think the CachedTransformer should be moved back to transformers, it has generic usage. As far as I see can see its just a wrapper for and Transformer that caches instances for the use case of multiple calls with the same data set.
However, I'm not sure it is set up to take sktime Pandas, i.e. where the whole series are in columns? If true, (also suggested by later functions) leave it here for now.
all the distance function getters use dim_to_use, which we are removing. If efficiency is an issue, just use column 0, if not, check if it has more and ditch if it has.

I've re-activated the unit tests for proximity forest (#116), I tried to make them faster but the array for the true predictions seems to be formatted in a weird way, values are not comma separated?

Fixed by #145


cas redirect not working for /authenticate/login endpoint

When the login endpoint is inside another route, other than index (/authenticate/login), redirect to /login instead.
part of request object included for review-
_parsedOriginalUrl:
{ protocol: null,
slashes: null,
auth: null,
host: null,
port: null,
hostname: null,
hash: null,
search: null,
query: null,
pathname: '/authenticate/login',
path: '/authenticate/login',
href: '/authenticate/login',
_raw: '/authenticate/login' },
sessionStore:
{ sessions: { nhi_54kpnp3vRkKSbu4hXiyMupoAHp4z: '{"cookie":{"originalMaxAge":null,"expires":null,"httpOnly":true,"path":"/"}}' },
generate: [Function],
_events: { disconnect: [Function], connect: [Function] } },
sessionID: 'nhi_54kpnp3vRkKSbu4hXiyMupoAHp4z',
session:
{ cookie:
{ path: '/',
_expires: null,
originalMaxAge: null,
httpOnly: true } },
route:
{ path: '/login',
stack: [ [Object], [Object], [Object] ],
methods: { get: true } } }

ah I see, req.path only shows the subroute and does not contain the full path.
req.originalUrl is documented both in express and connect, why not use that?

I tested with req.originalURL , after authentication it is goiing in a redirect loop..req.orginalUrl after authentication has ST , maybe that is causing the redirect.
I could remove the ticket and test, if originalUrl is cleaner.
after succesful auth-
req.originalUrl -> /authenticate/login?ticket=ST-1443771885r29645
req._parsedOriginalUrl.pathname -> /authenticate/login
with originalurl ,evey redirect in the loop is adding ticket.
/authenticate/login?ticket=ST-1443771628rCBC77
/authenticate/login?ticket=ST-1443771628rCBC77
/authenticate/login?ticket=ST-1443771628rCBC77&ticket=ST-1443771628rE2E9F
/authenticate/login?ticket=ST-1443771628rCBC77&ticket=ST-1443771628rE2E9F
/authenticate/login?ticket=ST-1443771628rCBC77&ticket=ST-1443771628rE2E9F&ticket=ST-1443771628rA0254
/authenticate/login?ticket=ST-1443771628rCBC77&ticket=ST-1443771628rE2E9F&ticket=ST-1443771628rA0254
/authenticate/login?ticket=ST-1443771628rCBC77&ticket=ST-1443771628rE2E9F&ticket=ST-1443771628rA0254&ticket=ST-1443771629r47FB3
/authenticate/login?ticket=ST-1443771628rCBC77&ticket=ST-1443771628rE2E9F&ticket=ST-1443771628rA0254&ticket=ST-1443771629r47FB3

Ahh thanks for checking, looks like I didn't read it carefully enough.
Can you help me test req.basePath?  I think it should give the same value as your _parsedOriginalUrl.pathname.  I just prefer to use the documented api whenever possible
Unfortunately, it does seem like connect itself doesn't have either _parsedOriginalUrl or req.basePath, maybe only in express.

The surest way is to serialize this ourselves I think, at the risk of being redundant since _parsedOriginalUrl isn't guaranteed to be in connect I think?:
url.parse(req.originalUrl).pathname

What do you think?

agree, updated.

please review the changes and merge when you get time.

thanks, republished as 1.4.4!


Questions about Res-Connection Based Gradient Projection Method in your journal work

Hi, I've read your latest journal work Gradient Projection For Continual Parameter-Efficient Tuning and confused about your deduction.

How to get the equation
$$
y_t=W_t^d x_t=W_{t+1}^d x_t
$$
?
Why does $W_t^d x_t=W_{t+1}^d x_t$?
Look forward to your response, thank you very much!

Hi, Pixel, an observation solution of Eq.(18) is as follows: We first need to make $W_t^dx_t=W_{t+1}^dx_t$. If it is achieved, we next need to make $W_t^uy_t=W_{t+1}^uy_t$. Thus, you can see that $y_t=W_t^dx_t=W_{t+1}^dx_t$ is guaranteed by making $W_t^dx_t=W_{t+1}^dx_t$, which equals to make $\DeltaW^dx_t=0$, one of the aim of our method.

Hi, Pixel, an observation solution of Eq.(18) is as follows: We first need to make W t d x t = W t + 1 d x t . If it is achieved, we next need to make W t u y t = W t + 1 u y t . Thus, you can see that y t = W t d x t = W t + 1 d x t is guaranteed by making W t d x t = W t + 1 d x t , which equals to make \DeltaW d x t = 0 , one of the aim of our method.

Why do we need $W_t^dx_t=W_{t+1}^dx_t$ to satisfy eq18? Is it the Necessary condition or Sufficient condition of eq18?

Hi, Pixel, an observation solution of Eq.(18) is as follows: We first need to make W t d x t = W t + 1 d x t . If it is achieved, we next need to make W t u y t = W t + 1 u y t . Thus, you can see that y t = W t d x t = W t + 1 d x t is guaranteed by making W t d x t = W t + 1 d x t , which equals to make \DeltaW d x t = 0 , one of the aim of our method.

Why do we need W t d x t = W t + 1 d x t to satisfy eq18? Is it the Necessary condition or Sufficient condition of eq18?

I'm foolish, and can you provide an inversed chain to explain it step by step for me? That is to say, if $w_d^dx_t=W_{t+1}^dx_t$ can be achieved, how can it lead to eq18?

Well, you can see that in Eq.(18) ($W_t^uW_t^dx_t=W_{t+1}^uW_{t+1}^dx_t$), there is a corresponding relationship between the terms on the left and right sides of the equation. For example, $W_t^u$ corresponds to $W_{t+1}^u$, $W_t^d$ corresponds to $W_{t+1}^d$, and $x_t$ corresponds to $x_t$. Thus, it is just like a match game to realize the equation. Obviously, $x_t$ equals to $x_t$. Next, we hope to achieve $W_t^dx_t=W_{t+1}^dx_t$. In this way, we obtain the first equation in Eq.(22). Subsequently, we assume that we have already realized $W_t^dx_t=W_{t+1}^dx_t$, so we can command $y_t=W_t^dx_t=W_{t+1}^dx_t$ and replace $W_t^dx_t$ and $W_{t+1}^dx_t$ with $y_t$. Therefore, Eq.(18) can be written as $W_t^uy_t=W_{t+1}^uy_t$ with $y_t$. Similarly, like the way to solve $W_t^dx_t=W_{t+1}^dx_t$, we can obtain the second equation in Eq.(22). In summary, if we can realize the two equations in Eq.(22), we can achieve Eq.(18)

Process about how to address $W_t^dx_t=W_{t+1}^dx_t$, please refer to the way in Sec 3.2 Self-Attention Based Gradient Projection Method


Reworked RDFa parsing/serializing and UI/UX

Overview
This (draft) PR contains a major overhaul on how we handle RDFa in the editor.
Specifically, it contains the following changes/additions:

Improved parsing/serialization of RDFa.
Improved UI/UX to allow for users to edit the underlying RDFa in a document. Users can add/edit/remove properties and relationships between resources and nodes.
Improvements to UI/UX in how we display block nodes inside an editor document.

connected issues and PRs:

GN-4506
GN-4507
GN-4508
GN-4579

TODOS

[x] Finish up the parsing/serialization system
[x] Finish up rdfa commands
[x] Introduce new interface for properties/backlinks
[x] Add support for deleting resource/content nodes
[x] Improve gap-cursor behaviour
[x] Finish up insert/wrapping of content/resource nodes
[x] Convert needed nodespecs to be rdfa-aware
[x] Check ux of isolating/non-isolating rdfa-aware nodes
[x] Make variables work with content/resource node system

The reason why playwright is failing is due to a visual regression: li element now have div elements inside of them. These div elements have a margin-top of 1.2rem (as defined in https://github.com/lblod/ember-rdfa-editor/blob/46821444607a91e47ef16598e49f99f76daf2be2/app/styles/ember-rdfa-editor/_c-content.scss#L122-L130)

There are still 2 failing tests:

rdfa | parsing: it should convert rdfa correctly
rdfa | parsing: it should convert rdfa with property spans correctly
These tests fail due to a (wrong) assumption that the __rdfaId is not stripped out when loading html in the editor. I'll check if I can adapt them so they do not rely on the __rdfaId attribute.

We could also adapt the html-cleaner to not strip out __rdfaId attribute if it finds them.

It also does not help that these test cases have div elements contained in span elements.

I think its better to keep stripping the id and adjust the tests


How can I remove the select code snippet shadow

when I USE , the vscode show:

the shadow cover all functions snippet, what config I change can remove this。

Please retry without extensions enabled. Select 'Extensions View > ... > Disable all Installed Extensions' and try again. Thanks.

Please retry without extensions enabled. Select 'Extensions View > ... > Disable all Installed Extensions' and try again. Thanks.

I need some extensions, I don't know what extention cause this problem

Please retry without extensions enabled. Select 'Extensions View > ... > Disable all Installed Extensions' and try again. Thanks.

disabled and enabled config have some change。。。。my god 。。。。。。

I am sorry but I cannot follow

I am sorry but I cannot follow

never mind, it doesn't matter, I think I need more explore and attempt.


fix(blueprint) compute destAbsolutepath after renaming any files

This fixes the issue shown in denali-js/denali#252 where the .gitignore files aren't being renamed correctly.
/cc @davewasmer

This is good for now, but points to the testing gap here. Not sure how we want to approach this since Denali itself is a great test of the CLI ...


Fossils Add business content to front page

I believe this is done. Any further chagned can be done in a new Issue.


Replace _kitchen completion with the version from zsh-users

This fixed #5008 for me. It's a copy from https://github.com/zsh-users/zsh-completions/ and I'm not sure about the license text but I hope it's good to merge. 👍

I've been applying this fix locally, any chance it can be merged? The current kitchen plugin doesn't work at all for completion.

You can install it using this guide: https://github.com/zsh-users/zsh-completions/#oh-my-zsh
That said, I'm merging this. Thanks for the reminder!


Merge pull request #1 from angular-ui/master

update

ｕｐｄａｔｅ

@292388900 we have no idea what this is.  I'm going to close it.


Add GMCM support and multilingual capabilities for English and Japanese

Pull Request: Add GMCM Support and Multilingual Capabilities
Description
This pull request introduces several enhancements to the LadderLocator mod, enhancing its configuration options and accessibility. Key changes include:

GMCM Integration: Added support for the Generic Mod Config Menu (GMCM), enabling users to conveniently adjust mod settings directly from the in-game menu.
Multilingual Support: Implemented internationalization (i18n) to support both English and Japanese languages, ensuring a broader user base can enjoy the mod with their preferred language.
Enhanced Configuration Options: Users now have more precise control over key bindings and display settings within the GMCM interface.

These improvements are aimed at enhancing user engagement and making the LadderLocator mod more user-friendly and accessible.
Files Modified

ModEntry.cs: Integrated GMCM functionality and added language support.
i18n/default.json: Added default English texts.
i18n/ja.json: Included Japanese translations.
IGenericModConfigMenuApi.cs: Added interface for integrating mods with GMCM.

Additional Note
This marks the initial implementation of GMCM features in the LadderLocator mod. If there are any inconsistencies or issues with the integration, please feel free to provide feedback or suggest improvements. Your input is invaluable for refining the functionality and enhancing the overall user experience.

Looks great, thanks!


CARDS-2141: The "Token Expired" page should display the affiliation logo when enabled

To test, start in prems and navigate to http://localhost:8080/Expired.html.
For more thorough testing:

start in prems
create a Visit dated in January 2023
get the token of that visit
navigate to http://localhost:8080/Survey.html?auth_token=<the token>
-> You should be redirected to the Expired.html page with both logos

tested post merge
before vs now:


Fix SVM and XGBOOST

They have NAs in their tables, probably because the values are not needed in that context because of the other parameters.

Can you give an example. Does it also occur in PR #59 ?


Register new package

@JuliaRegistrator register

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/106790
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 73b53ac9dcf42e0d81ddea6192a598b8f1a49f3a
git push origin v1.0.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/106804
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 73b53ac9dcf42e0d81ddea6192a598b8f1a49f3a
git push origin v1.0.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/106807
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" e4d50ab9166cdf9c001df16c764e01e037eadc9b
git push origin v1.0.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/106959
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 2eae4ba07f89698faf9b10f278812e5c586dbdf8
git push origin v1.0.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/107016
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 89653197a23b3ec68e166e61805971ab03b5cbe3
git push origin v1.0.0


Jupyter notebook

Issue Type: Bug
Jupyter notebook command cannot run when opening VsCode. It worked on the initial setup but after a restart, it does not work.
It displays the following error:
Command 'Jupyter: Create New Blank Notebook' resulted in an error (command 'jupyter.createnewnotebook' not found)
VS Code version: Code - Insiders 1.56.0-insider (633562da380f9161ea2fd783e561eed508cfbbea, 2021-04-26T05:14:38.204Z)
OS version: Windows_NT x64 10.0.19042

Restarting pc helped it return, amazing integration


How can I make popper the same with as a trigger?

Sorry for posting as a bug.
I need to make popup the same width as a trigger for things like selects, date pickers, etc.
Thanks in advance!

I think maybe these headless components are more suitable for your requirements.


About dialog with versions and links to online resources

Most applications will have an "About" window that shows the exact version that the user is running. Here's Gazebo-classic's one for example:

This is handy for users that are not on a terminal or aren't running with enough verbosity to see the version printed.
I also think it would be handy to print the version of all Ignition libraries that Gazebo is using.
And we should have links to online resources too.
Ignition GUI has a silly About dialog that could be updated as well:

Some tips on getting started with this issue:

I recommend targeting Ignition Citadel, which is branch ign-gazebo3
The dialog code can go directly into GazeboDrawer.qml
We can create a new C++ class similar to GuiFileHandler that will provide version information to the QML code. To start with, it could just provide IGNITION_GAZEBO_VERSION_FULL.

@chapulina
I have created a dialog box inside GazeboDrawer.qml

Currently, I'm providing the version number and header using IGNITION_GAZEBO_VERSION_HEADER, and the dialog content is:
std::string(IGNITION_GAZEBO_VERSION_HEADER)

    ...

However, the hyperlink to the tutorials is specific to Citadel, which might cause an issue in a future version, when the version name changes. Is there a general way to provide the hyperlinks?

@chapulina
I have created a dialog box inside GazeboDrawer.qml

Currently, I'm providing the version number and header using IGNITION_GAZEBO_VERSION_HEADER, and the dialog content is:
std::string(IGNITION_GAZEBO_VERSION_HEADER)

    ...

However, the hyperlink to the tutorials is specific to Citadel, which might cause an issue in a future version, when the version name changes. Is there a general way to provide the hyperlinks?

This is great, thanks for working on this, @atharva-18 !

I'm providing the version number and header using IGNITION_GAZEBO_VERSION_HEADER

Perfect

the hyperlink to the tutorials is specific to Citadel, which might cause an issue in a future version, when the version name changes. Is there a general way to provide the hyperlinks?

How about just linking to https://ignitionrobotics.org/docs/ now?

Some UI suggestions that you can feel free to ignore:

Try using the background color from the theme, Material.background, so it should be white for light theme and black for dark
For the text, try using black or white according to the theme, something like this: color: Material.theme == Material.Light ? "black" : "white"
Give the dialog a maximum width, so that it's a bit more compact.

Looking forward to a pull request!

Added in #609


Global pointer assignment doesn't work

A pointer defined globally is not getting assigned value later in code
Code to reproduce
char* dummy;
void main()
{
    char* hello = "Hello String";
    puts(hello); //works
    char* test = hello;
    puts(test); //works
    dummy = test;
    puts(dummy); //doesn't works prints 0
}

I did find this bug before 😅
I'll get around to fixing it for sure, but lots of work to do on NCC. The compiler is fairly MacGuyvered together 😅
If you'd like to help fix it, your help is welcome.

Sure. I'll try to fix this. Can you point in the right direction where to start off ?

Sure.
One way to debug this is to look at the instructions output by the compiler. It gets written into the out.asm file. It's a human-readable test file. This will be easier to debug if you strip it down to the smallest possible test case:
#include <stdio.h>
char* dummy;
void main()
{
    char* hello = "Hello String";
    dummy = hello;
    puts(dummy); //doesn't works prints 0
}

So the output code for the main function is:
main:
push 0;
push __CONST_STR_0__;
set_local 0;
push dummy;
get_local 0;
store_u64;
push dummy;
call puts, 1;
pop;
push 0;
ret;

Here dummy is just a label, an address in the heap. At the top of the file we see:
dummy:
.u64 0;

That's good. It's a 64-bit value (a pointer), and it's initialized to zero (null).
I think the problem is it's pushing the address of the global variable dummy, because it expects the data for the char* pointer to directly live at that address... But that's not right, because dummy is not a global array of characters, it's a pointer to a string. We're missing a load_u64 instruction to load from that pointer and get the actual string data.

Should be fixed now.


Visual Studio Code trouble shooting as bar moving above explorer.

i think i've deleted a file and the system and now it wont. There is a constant bar moving above explorer. i have tried reloading but no luck so far. any suggestions? very new to this piece of software. trying to do the CS50P course and already messed the system up.
Version: 1.82.2
Commit: abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!