Code review

please kindly add proper icon like enter-down-left to the input field.

Good job so far. You have followed best practices in your index.html file.
(a) Your code does not contain blank lines, spaces, or indentations.
(b) Your lines of code are not too long (100 characters or more).
(c) You have used HTML5 semantic tags properly.
(d) All HTML elements closed.
You have followed best practices in your style.css file.
(a) Do not use inline styles.
(b) You do not overuse !important rule in your CSS style definitions.


how to get keys list which are older than 60 seconds

How my requirement is get all the keys that are older than 60 seconds. Is there any way I can get all the keys that are older than 60 seconds. One way i can think of is set the timeout and then check for each key if is expired. But can we set the timeout in pymemcache and check if item is expired? but in this case also i have to go through each key and check which is very costly. Can you suggest any better way?
Thanks,
Shashi

Memcached itself doesn't support key scanning like this (except slowly for debugging purposes), pymemcache can do nothing to help you there really.


Expiretime bug azure cli

expiretime=$(date -u -d '30 minutes' +%Y-%m-%dT%H:%MZ)
Throws an error both on zsh macos and latest mcr/azure-cli container

date: invalid date '30 minutes'

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

ID: aca59e66-f6e4-33ec-b831-21b08c188cf7
Version Independent ID: 208f2ef8-5447-3250-94c2-38c65dce9029
Content: Securely deploy template with SAS token - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/secure-template-with-sas-token.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

@tiny-dancer Thanks for your comment! We will review and provide an update as appropriate.

@KrishnaG-MSFT did a little more digging and it’s due to the azure cli container executing the busy box version of date rather than GNU. Requires different syntax

@tiny-dancer - sorry, in this case, we standardize on the Bash environment that runs in CloudShell. If there is a common format for the date function that works for both environments, we can change it to that, but I haven't been able to find one.

@tiny-dancer - you might also want to consider Template Specs. You grant access through RBAC roles so you don't have to manage the SAS tokens. It is currently in preview.

Well that’s mighty interesting, thanks for the forward!
RE docs, understandable. A quick win may simply be adding that statement as an inline comment.  It took me a bit to even realize there were different implementations of date in bash.

Thanks for this feedback. I have added that info to the article. It should get published later today.

#please-close


grub2disk is no longer on quay.io

When going through the sandbox and then experimenting with different actions, I went to pull down the grub2disk action and it said the tag was deleted
Expected Behaviour
$ docker pull quay.io/tinkerbell-actions/grub2disk:v1.0.0
v1.0.0: Pulling from tinkerbell-actions/grub2disk:v1.0.0
...

Current Behaviour
$ docker pull quay.io/tinkerbell-actions/grub2disk:v1.0.0
Error response from daemon: unknown: Tag v1.0.0 was deleted or has expired. To pull, revive via time machine

Possible Solution
restore the image on quay.io
Steps to Reproduce (for bugs)

docker pull quay.io/tinkerbell-actions/grub2disk:v1.0.0

Without knowing why the tag was intentionally deleted, I think the best move here is to push the tag again.
In the meanwhile, the SHA<PHONE_NUMBER>0c) can be used.
https://artifacthub.io/packages/tbaction/tinkerbell-community/grub2disk

@displague or @mmlb are you able to get the tag rebuilt? Who is the right owner who has permissions?

https://github.com/tinkerbell/hub/pull/78 should go green and be merged soon which should cause the image to be pushed up again.


Update Song “index”

Automatically generated by Netlify CMS

👷 Deploy Preview for starlit-starburst-6cb938 processing.

Name
Link

🔨 Latest commit
ed2c1c52ed219c646d523a977217973ef5c138c0

🔍 Latest deploy log
https://app.netlify.com/sites/starlit-starburst-6cb938/deploys/66a08aabc696dc00097adf2b


Getting Nans when training MQCNN on GPU

Description
FROM nvidia/cuda:9.2-cudnn7-runtime-ubuntu18.04

RUN apt-get update --fix-missing && \
    apt-get install -y --no-install-recommends \
        wget bzip2 ca-certificates curl git build-essential \
        cmake python3.7 python3.7-dev python3.7-distutils pkg-config && \
    apt-get clean && \
    rm -rf /var/lib/apt/lists/*
RUN curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py && python3.7 get-pip.py

# We're emulating nvidia-smi to be able to build GPU container on devices without GPU
RUN echo '#!/bin/bash\necho Building container with GPU support' > /usr/bin/nvidia-smi && \
    chmod +x /usr/bin/nvidia-smi

ADD . /gluonts

RUN pip3.7 install mxnet-cu92>=1.6
RUN pip3.7 install /gluonts[shell]

ENTRYPOINT ["python3.7", "-m", "gluonts.shell"]

If I set hybridize=False it works again.
This does not happen in our internal MXNet version/container (see MQCNN).
This does not happen with older MXNet versions (I think 1.4)
This does happen also for newer Cuda versions (I think 10.?)
Reducing the initial learning rate only works for ridiculously low learning rates, and even then it's not reliable

Error message or code output
Traceback (most recent call last):
  File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.7/dist-packages/gluonts/shell/__main__.py", line 154, in <module>
    cli(prog_name=__package__)
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/gluonts/shell/__main__.py", line 131, in train_command
    train.run_train_and_test(env, forecaster_type_by_name(forecaster))
  File "/usr/local/lib/python3.7/dist-packages/gluonts/shell/train.py", line 85, in run_train_and_test
    forecaster, env.datasets["train"], env.datasets.get("validation")
  File "/usr/local/lib/python3.7/dist-packages/gluonts/shell/train.py", line 100, in run_train
    training_data=train_dataset, validation_data=validation_dataset
  File "/usr/local/lib/python3.7/dist-packages/gluonts/model/estimator.py", line 271, in train
    **kwargs,
  File "/usr/local/lib/python3.7/dist-packages/gluonts/model/estimator.py", line 244, in train_model
    validation_iter=validation_data_loader,
  File "/usr/local/lib/python3.7/dist-packages/gluonts/mx/trainer/_base.py", line 373, in __call__
    "Got NaN in first epoch. Try reducing initial learning rate."

Environment

see Dockerfile

(Add as much information about your environment as possible, e.g. dependencies versions.)

Possibly related to: https://github.com/awslabs/gluon-ts/issues/501

Also facing similar issue as can be seen in the output logs here:
http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1198/43/tutorials/forecasting/forecasting-quickstart.html
where during GPU-training of MQCNN we see warnings like this:
Batch [8] of Epoch[0] gave NaN loss and it will be ignored
This only seems to an issue for MQCNN with GPU on certain datasets (same code works fine running on CPU), eg. in the linked example we are running on a dataset that contains many 0s.

@jwmueller is there a way to isolate the issue into a MWE? That would be very useful to try to understand what is failing. I guess that requires extracting some data pre-processing from the ForecastingPredictor class of AutoGluon, and getting a sample HP settings that produces the issue (maybe default settings fail already?)
Work-around in the mean time: try disabling hybridization with MQCNN on GPU (does that slow down training by a lot?)


Return empty command lines for permission issues or already exited pids

We should consistently return strings so the best we can do is return an empty
string for these unhappy paths.
We can't take action for empty command lines, so in the case of exited pids, this
should be ok.  Permission issues are only a problem on development environments
but not for appliances.
[NoMethodError]: undefined method `include?' for nil:NilClass  Method:[rescue in monitor]
../gems/pending/util/miq-process.rb:163:in `is_worker?'

cc @lfu

A couple of comments of good, but otherwise LGTM

Done

:+1: Will merge when green

:large_orange_diamond: - Line 1, Col 1 - Style/FileName - Use snake_case for source file names.

tell me about it miq-bot

Related to #6269


Replacing assets not working correctly

I'm trying to replace some assets in an asset bundle using a tool I made that runs on this library (https://github.com/Skyluker4/UnityAssetReplacer). When I save a new asset bundle to replace assets, something gets messed up. Without even actually replacing any assets and just making a copy of the bundle using AssetTools.NET it ends up being 20 bytes less than the original. The beginning of the file differs from the original (about the first few hundred bytes or so are different).
This is only for one specific asset bundle, other ones work fine. When trying to read from UABE, it says "invalid assets file".
Here's a look at the files -- the original on the left and the one AssetTools.NET generated on the right.

I don't know if this is a problem with my own code or a problem with the library. I'm using AssetReplacerFromMemory to replace the assets and BundleReplacerFromMemory and AssetsFileWriter to create the new bundle.

When writing, I only create one block whereas the file you have has three blocks. Since the file is decompressed, there shouldn't be any difference in the data, only the block table (which is 10 bytes each, 310-110=20 byte difference). Does this open in UABEA or only fail in UABE?

It does not open in UABE, UABEA, or the game itself when imported. Here's a stack trace and the exception with UABEA:

Only so much I can do without the file so I'll try to ask some questions to figure out what's going wrong.

If you write just the modified assets file without the bundle, can you still open it?
When you hit the exception, what is Type_0D's reader.Position value?
It shouldn't affect opening the file initially, but on this line
https://github.com/Skyluker4/UnityAssetReplacer/blob/main/UnityAssetReplacer/UnityAssetReplacer.cs#L75
you should replace 0xFFFF with AssetHelper.GetScriptIndex(_assetsFile.file, assetInfo); if you're reading monobehaviours.

I'll work on modifying my program to save just the assets file.
When it gets to the exception, reader.Position is 0x55488 in AssetsTools.NET.TypeTree.Read(AssetsTools.NET.AssetsFileReader reader, uint version), which is also the exact value of reader._stream._capacity and length of reader._stream._buffer.
Should I replace it only if it's monobehaviours and check for that or just straight up replace 0xFFFF with that for everything? I'm not too familiar with Unity.

Also, if you want, I can send the assets file to you if you'd think it would help.

Should I replace it only if it's monobehaviours and check for that or just straight up replace 0xFFFF with that for everything? I'm not too familiar with Unity.

Monobehaviours are kind of a pain in unity because they are of the same type (MonoBehaviour 0x72) but they are unique because they use a second field called scriptIndex that differentiates different monobehaviours. Anything that isn't a monobehaviour is script index 0xFFFF and anything that is a monobehaviour has a different script index unique to each c# script. tldr, using GetScriptIndex is never a bad thing, but if you know you're not replacing any monobehaviours, you can use 0xFFFF as a shortcut.

Also, if you want, I can send the assets file to you if you'd think it would help.

That will make debugging easier if you could.

Here you go

This is a bug with your program. Close the writer you use on the bundle file so that the bundle header can update.

I couldn't get it to work with that. Is this the right way to do it? https://github.com/Skyluker4/UnityAssetReplacer/tree/replace-fix

Close the writer, not the reader.

I see what you mean now. It works. Thank you! Do you know why it only messed up with this one specific file? Also, the documentation should probably be updated so no one else runs into this problem.

I would've honestly expected more to break, but I figure that the other bundles you edited only had one block instead of the three in this one.


Fixed collection twice after edit collection

tasks:

[ ] gather feedback for my changes

informations:

q
a

Fixed tickets
none

BC breaks
none

Documentation PR
none

@danrot fixed


Alias "element" with "createElement" for JSX compatibility.

I'm not sure if it's the jsx compiler I am using but when supplying the
// @jsx element
<input type="radio"/>

It transforms the jsx into:
element.createElement("input", {
      "type": "radio"
    })

If we alias "element" with "createElement" (What react uses) it will resolve this issue and we can do:
// @jsx deku
<input type="radio"/>

Which would become:
deku.createElement("input", {
      "type": "radio"
    })

Out of curiosity which jsx compiler are you using? I think babel and the jsx-tools used to work that way, but they changed it. If it's just the way one of the jsx compilers work then I don't mind adding this :)

Currently using the "coffee-react" transformer so it could just be that. Not sure what they use internally.

Just pushed 0.4.4 that adds createElement as an alias :)


Unexpected crash when not cleaning your stubs correctly

Summary
Whenever you forget to clean your stubs, this can have very strange consequences. For example:
$ npx stryker run
14:54:25 (19520) INFO ConfigReader Using stryker.conf.json
14:54:26 (19520) INFO InputFileResolver Found 28 of 71 file(s) to be mutated.
14:54:28 (19520) INFO Instrumenter Instrumented 28 source file(s) with 363 mutant(s)
14:54:28 (19520) INFO ConcurrencyTokenProvider Creating 1 test runner process(es).
14:54:29 (19520) INFO Sandbox Running build command "yarn build" in the sandbox at "/user/nicojs/backend-common/.stryker-tmp/sandbox1547662".
14:54:58 (19520) INFO DryRunExecutor Starting initial test run. This may take a while.
14:55:18 (19520) INFO DryRunExecutor Initial test run succeeded. Ran 87 tests in 53 seconds (net 534 ms, overhead 5535 ms).
Mutation testing  [                                                  ] 0% (elapsed: <1m, remaining: ~13m) 3/360 tested (0 survived, 0 timed out)14:55:26 (19520) WARN ChildProcessProxy Child process [pid 16432] exited unexpectedly with exit code 134 (without signal). Last part of stdout and stderr was:
        Debugger listening on ws://<IP_ADDRESS>:9229/91e56797-13e6-49b9-9e00-80e74706f520
        For help, see: https://nodejs.org/en/docs/inspector
        Debugger attached.
        stryker[16432]: c:\ws\src\node_contextify.cc:997: Assertion `args[0]->IsString()' failed.
         1: 00007FF6EFEA5EBF napi_wrap+114095
         2: 00007FF6EFE50B46 v8::base::CPU::has_sse+66998
         3: 00007FF6EFE50EC1 v8::base::CPU::has_sse+67889
         4: 00007FF6EFE59EE7 v8::base::CPU::has_sse+104791
         5: 00007FF6F061AAE0 v8::internal::Builtins::builtin_handle+323456
         6: 00007FF6F061A027 v8::internal::Builtins::builtin_handle+320711
         7: 00007FF6F061A368 v8::internal::Builtins::builtin_handle+321544
         8: 00007FF6F061A16E v8::internal::Builtins::builtin_handle+321038
         9: 00007FF6F0ABB4BD v8::internal::SetupIsolateDelegate::SetupHeap+546893
        10: 00007FF6F0A4036C v8::internal::SetupIsolateDelegate::SetupHeap+42748
        11: 00007FF6F0A4036C v8::internal::SetupIsolateDelegate::SetupHeap+42748
        12: 00007FF6F0A4036C v8::internal::SetupIsolateDelegate::SetupHeap+42748
        13: 00007FF6F0A4036C v8::internal::SetupIsolateDelegate::SetupHeap+42748
        14: 00007FF6F0A4036C v8::internal::SetupIsolateDelegate::SetupHeap+42748
        15: 0000031AB9126D4E
         ChildProcessCrashedError: Child process [pid 16432] exited unexpectedly with exit code 134 (without signal). Last part of stdout and stderr was:
        Debugger listening on ws://<IP_ADDRESS>:9229/91e56797-13e6-49b9-9e00-80e74706f520
        For help, see: https://nodejs.org/en/docs/inspector
        Debugger attached.
        stryker[16432]: c:\ws\src\node_contextify.cc:997: Assertion `args[0]->IsString()' failed.
         1: 00007FF6EFEA5EBF napi_wrap+114095
         2: 00007FF6EFE50B46 v8::base::CPU::has_sse+66998
         3: 00007FF6EFE50EC1 v8::base::CPU::has_sse+67889
         4: 00007FF6EFE59EE7 v8::base::CPU::has_sse+104791
         5: 00007FF6F061AAE0 v8::internal::Builtins::builtin_handle+323456
         6: 00007FF6F061A027 v8::internal::Builtins::builtin_handle+320711
         7: 00007FF6F061A368 v8::internal::Builtins::builtin_handle+321544
         8: 00007FF6F061A16E v8::internal::Builtins::builtin_handle+321038
         9: 00007FF6F0ABB4BD v8::internal::SetupIsolateDelegate::SetupHeap+546893
        10: 00007FF6F0A4036C v8::internal::SetupIsolateDelegate::SetupHeap+42748
        11: 00007FF6F0A4036C v8::internal::SetupIsolateDelegate::SetupHeap+42748
        12: 00007FF6F0A4036C v8::internal::SetupIsolateDelegate::SetupHeap+42748
        13: 00007FF6F0A4036C v8::internal::SetupIsolateDelegate::SetupHeap+42748
        14: 00007FF6F0A4036C v8::internal::SetupIsolateDelegate::SetupHeap+42748
        15: 0000031AB9126D4E

    at ChildProcessProxy.handleUnexpectedExit (C:\z\nn\poe\shared\backend-common\node_modules\@stryker-mutator\core\src\child-proxy\ChildProcessProxy.js:32:37)
    at ChildProcess.emit (events.js:315:20)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) {
  innerError: undefined,
  pid: 16432,
  exitCode: 134,
  signal: null
}

The reason for this error is this test hooks logic:
export const mochaHooks = {
  beforeEach() {
    nock.cleanAll();
    sinon.restore();
  },
};

After changing the beforeEach to afterEach it works.
The root cause is that we stub away fs.readFileSync in one of the tests. When nodejs loads files (require) it relies on fs.readFileSync, as you can see here:

Stryker handles it correctly (restart the runner and try the mutant again), but maybe we should try to help our users better? Maybe add this error to an FAQ?
Stryker config

{
  "$schema"<EMAIL_ADDRESS>  "buildCommand": "yarn build",
  "testRunner": "mocha",
  "coverageAnalysis": "perTest",
  "mochaOptions": {
    "spec": ["dist/src/**/*.test.js", "dist/src/**/*.spec.js"]
  },
}

Stryker environment

| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>deduped
| | +--<EMAIL_ADDRESS>deduped
| +--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS> | +--<EMAIL_ADDRESS>deduped
| +--<EMAIL_ADDRESS>deduped

For anyone who runs into this and cleaning up after each does not fix it, make sure that you are also awaiting your test expectation:
it('fails when receiving exception', async () => {
	const error: Error = { name: 'BadError', message: 'Oh no!' }
	quickSightMock.on(ListUsersCommand).rejects(error)

	await expect(quickSightUserManager.retrieveUsers()).rejects.toThrowError(error)
})

I struggled with this error for a long time and finally fixed it by adding the await. Thanks @nicojs for the original issue that helped me troubleshoot mock cleanup.


[website] update charts documentation

Motivation and Context

Updated documentation for chart's API pages.
Updated a little bit examples for Cigarette chart and added descriptions.

How has this been tested?

Locally with our website.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[x] Nice improve.

Checklist:

[x] My code follows the code style of this project.
[x] I have updated the documentation accordingly or it's not required.
[ ] Unit tests are not broken.
[ ] I have added changelog note to corresponding CHANGELOG.md file with planned publish date.
[ ] I have added new unit tests on added of fixed functionality.

@ilyabrower Hey! Please check changes only for Cigarette chart. I've added more context to the examples.
Other changes are similar and you don't need to check them.


Multi WAN + Captive Portal not working

Guys,
I am running on OPNsense 16.1.18-i386. I am not able to get Captive Portal to work on a Multi-WAN scenario. Captive Portal works fine if there is no policy based routing applied to the default LAN rule. As soon as I set a Gateway Group, Captive Portal fails to show, though I still get internet.
The 'ipfw' rules fail to apply when gateway group is set.
I have posted in the forum as well. Please find the details in the link below:
https://forum.opnsense.org/index.php?topic=3600.0

You should be running 16.7 and see if you have that issue on that version as 16.1 is not supported anymore

Upgraded to OPNsense 16.7.3-i386, still facing the same issue.

@srijannandi just tried it on my end and can confirm it doesn't work. Looks like a kernel issue. Found this online from some time ago https://lists.freebsd.org/pipermail/freebsd-pf/2010-July/005739.html , not sure if its related, there doesn't seem to be a quick fix.

Thanks, AD.
Do we have a sysctl setting to specify the order such as these:
sysctl net.inet.ip.pfil
net.inet.ip.pfil.inbound=pf, ipfw*
net.inet.ip.pfil.outbound=pf, ipfw*
Maybe this can keep the order fixed.

@srijannandi No (its not part of FreeBSD), but the loading order should be handled correctly by the rc script https://github.com/opnsense/core/blob/master/src/etc/rc.ipfw

AD,
Is the correct order PF and then IPFW?
Because, if I set default as gateway in the LAN to any rule. I have ipfw process the packet first which then pass it to pf. That's how the captive portal appears for authentication. Once authentication is done, it goes to pf for processing.
As soon as I set gateway group in LAN, this breaks and ipfw does not come into picture, and pf sends the packets out.

yes, the current order is correct (ipfw loaded before pf), its likely a bug in combination with route-to.
Using ipfw in combination with pf sometimes provides provides some headaches (like the loading order).
In case you want to dig in the code, these two areas might be of interest:
https://github.com/opnsense/src/blob/master/sys/netpfil/pf/pf.c#L5459
https://github.com/opnsense/src/blob/master/sys/netpfil/pf/pf.c#L5434
(call if_output directly like mentioned in https://lists.freebsd.org/pipermail/freebsd-pf/2010-July/005739.html)
You can find some additional information about the normal package flow in this blog post in case your interested http://deadloop.blogspot.nl/2010/04/who-comes-first-ipfw-or-pf.html
Currently I don't have a lot of time to really dig into this.

Just performed some additional testing, the problem is that the pfil ordering can't be correct for both dummynet (traffic shaper) and route-to / captive portal.
pfSense has added a kernel hack to adjust the pfil ordering, we do the same in our scripting.
To handle the traffic shaping correctly, we need to catch the traffic before NAT happens, which is what https://github.com/opnsense/core/blob/master/src/etc/rc.ipfw#L39 does.
If we change the order, route-to/Captive portal works (easy to test, just unload ipfw and load it again), but the shaper won't be able to match all the traffic correctly (due to being post nat).
In case you want to test the same I did, execute the following steps on your console (after captive portal has been started):
ipfw flush
kldunload dummynet
kldload ipfw

note: you need to add a rule to accept traffic without policy based routing, so your internal machine can access the internal webserver.
Long story short, without serious kernel chances there is no simple fix here. We could add an advanced option to change the order somehow, but it would be difficult for people to understand what it actually does.

I think a fix in FreeBSD will be sensible and possible due to the fact that pf(4) just doesn't adhere to packet filter chaining during route-to. The ipfw equivalent seems to work, which is used by the captive portal to redirect, isn't that right?

On 15.09.2016, at 18:00, Ad Schellevis<EMAIL_ADDRESS>wrote:
Just performed some additional testing, the problem is that the pfil ordering can't be correct for both dummynet (traffic shaper) and route-to / captive portal.
pfSense has added a kernel hack to adjust the pfil ordering, we do the same in our scripting.
To handle the traffic shaping correctly, we need to catch the traffic before NAT happens, which is what https://github.com/opnsense/core/blob/master/src/etc/rc.ipfw#L39 does.
If we change the order, route-to/Captive portal works (easy to test, just unload ipfw and load it again), but the shaper won't be able to match all the traffic correctly (due to being post nat).
In case you want to test the same I did, execute the following steps on your console (after captive portal has been started):
ipfw flush
kldunload dummynet
kldload ipfw
note: you need to add a rule to accept traffic without policy based routing, so your internal machine can access the internal webserver.
Long story short, without serious kernel chances there is no simple fix here. We could add an advanced option to change the order somehow, but it would be difficult for people to understand what it actually does.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

working patch available, test builds soon

Call for testing instructions here: https://forum.opnsense.org/index.php?topic=3704.0

with 	OPNsense 17.7.1_2-amd64 I see the same problem and I can't find 83fd8a6 on master.
I lost something?
thanks

This is old. If you have trouble with Multi-WAN + Captive Portal, enable "Shared forwarding" under Firewall: Settings: Advanced.

ops. thank for the hit. have a nice day


benchmarks are broken

The benchmarks are broken.
Probably due to not pinning the K6 version used for running the tests.
Run k6 -e GITHUB_PR=1387 -e GITHUB_SHA=6d677f4a58483ee8929bca29f026077877c6aa40 -e GITHUB_TOKEN=*** -e GRAPHQL_HOSTNAME="[::1]" run ./benchmark/k6.js
time="2022-05-10T10:50:[4](https://github.com/dotansimha/envelop/runs/6368443658?check_suite_focus=true#step:10:4)9Z" level=error msg="invalid threshold defined on no_errors{mode:envelop-cache-and-no-internal-tracing}; reason: no metric name \"no_errors{mode:envelop-cache-and-no-internal-tracing}\" found"

          /\      |‾‾| /‾‾/   /‾‾/
     /\  /  \     |  |/  /   /  /
    /  \/    \    |     (   /   ‾‾\
   /          \   |  |\  \ |  (‾)  |
  / __________ \  |__| \__\ \_____/ .io

Error: Process completed with exit code [10](https://github.com/dotansimha/envelop/runs/6368443658?check_suite_focus=true#step:10:10)4.

https://github.com/dotansimha/envelop/runs/6368443658?check_suite_focus=true

@n1ru4l we have similar issues on other repos, did you manage to find the reason for that?

closed in https://github.com/n1ru4l/envelop/pull/1402


Should a notification successfully be fetched, I am able to either accept or decline the split

Earlier commit that worked on this issue: baef2b255239474ab37a35afd3a4c14990c29463


Added Errata for F200/SR300 Camera Types

Changes proposed in this pull request:

Document errata for multiple F200/SR300 camera use cases.

Approved :+1:


Revert "Build widget fix - Search with job name"

Reverts capitalone/Hygieia#2017

@tabladrum @nireeshT Reverting. Please investigate the possibility of moving the queries to collectorItemRepository. Also we want to ensure its not tool specific..ie. it should work for any build tool.


WFCORE-1663 WFCORE-1669 Update legacy controllers and improve core transformers

Core - Full Integration Build 3127 outcome was FAILURE using a merge of d3b8f5005cfc142efe63495ccc2753fb1e007ade
Summary: Tests failed: 1 (1 new), passed: 3397, ignored: 193 Build time: 01:01:17
Failed tests
org.jboss.as.test.xts.annotation.compensationScoped.CompensationScopedTestCase.shouldSeeDifferentValuesInDifferentTransactions: com.arjuna.mw.wsas.exceptions.WrongStateException: ARJUNA041018: Cannot enlist child activity with parent as parent's status is: Status.Completed
	at com.arjuna.mwlabs.wsas.activity.ActivityImple.addChild(ActivityImple.java:583)
	at com.arjuna.mwlabs.wsas.activity.ActivityImple.start(ActivityImple.java:160)
	at com.arjuna.mwlabs.wsas.UserActivityImple.start(UserActivityImple.java:136)
	at com.arjuna.mwlabs.wsas.UserActivityImple.start(UserActivityImple.java:99)
	at com.arjuna.mwlabs.wscf.model.sagas.arjunacore.CoordinatorServiceImple.begin(CoordinatorServiceImple.java:108)
	at org.jboss.narayana.compensations.impl.local.LocalBAController.beginBusinessActivity(LocalBAController.java:28)
	at org.jboss.as.test.xts.annotation.compensationScoped.CompensationScopedTestCase.shouldSeeDifferentValuesInDifferentTransactions(CompensationScopedTestCase.java:76)
------- Stdout: -------
 [0m09:56:12,638 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 90) WFLYUT0022: Unregistered web context: /transactional-test
 [0m [0m09:56:12,645 INFO  [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0004: Stopping service jboss.ws.endpoint."transactional-test.war".TransactionalServiceImpl
 [0m [0m09:56:12,662 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 87) WFLYCLINF0003: Stopped client-mappings cache from ejb container
 [0m [0m09:56:12,675 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment transactional-test.war (runtime-name: transactional-test.war) in 39ms
 [0m [33m09:56:12,681 WARN  [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
 [0m [0m09:56:12,682 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /opt/buildAgent/work/29472398f1ae6497/full/testsuite/integration/xts/target/jbossas/standalone/data/content/a8/3c963b221958284228e2f3b11d91c7f47c3c07/content
 [0m [0m09:56:12,682 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "transactional-test.war" (runtime-name: "transactional-test.war")
 [0m [0m09:56:13,352 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /opt/buildAgent/work/29472398f1ae6497/full/testsuite/integration/xts/target/jbossas/standalone/data/content/7a/c8e19aa74d922838d1d7929ce9d9b9defdc6c2/content
 [0m [0m09:56:13,354 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
 [0m [0m09:56:13,491 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment test.war
 [0m [0m09:56:13,716 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 88) WFLYUT0021: Registered web context: /test
 [0m [0m09:56:13,722 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war")
 [0m

Full integration - Windows Build 1571 outcome was FAILURE using a merge of d3b8f5005cfc142efe63495ccc2753fb1e007ade
Summary: Execution timeout (new); tests passed: 2752, ignored: 163 Build time: 01:46:32

retest this please

Core - Full Integration Build 3130 outcome was FAILURE using a merge of d3b8f5005cfc142efe63495ccc2753fb1e007ade
Summary: Tests failed: 1 (1 new), passed: 3397, ignored: 193 Build time: 00:59:41
Failed tests
org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testMessageRemoval: java.lang.AssertionError: expected:<2> but was:<0>
	at org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testMessageRemoval(JMSQueueManagementTestCase.java:226)
------- Stdout: -------
 [0m12:34:23,668 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 27) AMQ221003: trying to deploy queue jms.queue.JMSQueueManagementTestCase1469475262806
 [0m12:34:23,674 INFO  [org.jboss.as.test.integration.common.jms.JMSOperationsProvider] (main) Operation successful for update = {
    "operation" => "add",
    "address" => [
        ("subsystem" => "messaging-activemq"),
        ("server" => "default"),
        ("jms-queue" => "JMSQueueManagementTestCase1469475262806")
    ],
    "entries" => ["java:jboss/exported/queue/JMSQueueManagementTestCase1469475262806"]
}
 [0m12:34:23,676 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 26) AMQ221003: trying to deploy queue jms.queue.JMSQueueManagementTestCaseother1469475262806
 [0m12:34:23,684 INFO  [org.jboss.as.test.integration.common.jms.JMSOperationsProvider] (main) Operation successful for update = {
    "operation" => "add",
    "address" => [
        ("subsystem" => "messaging-activemq"),
        ("server" => "default"),
        ("jms-queue" => "JMSQueueManagementTestCaseother1469475262806")
    ],
    "entries" => ["java:jboss/exported/queue/JMSQueueManagementTestCaseother1469475262806"]
}
12:34:23,760 INFO  [org.jboss.as.test.integration.common.jms.JMSOperationsProvider] (main) Operation successful for update = {
    "operation" => "remove",
    "address" => [
        ("subsystem" => "messaging-activemq"),
        ("server" => "default"),
        ("jms-queue" => "JMSQueueManagementTestCase1469475262806")
    ]
}
12:34:23,766 INFO  [org.jboss.as.test.integration.common.jms.JMSOperationsProvider] (main) Operation successful for update = {
    "operation" => "remove",
    "address" => [
        ("subsystem" => "messaging-activemq"),
        ("server" => "default"),
        ("jms-queue" => "JMSQueueManagementTestCaseother1469475262806")
    ]
}

retest this please


Htp table optimizations/v3

Previous PR: https://github.com/OISF/libhtp/pull/431
Changes since v2:

cleaner commit history

Information: QA ran without warnings.
Pipeline 22083

Looks good to me globally, I wonder if we should just merge the CI changes in a separate PR first...


Create index.html

Movie Rting App Html file

please accept my PR , after that i will add style.css and javascript file.

please accept my PR , after that i will add style.css and javascript file.

Add all files


Update docs (schema diagram)

Signed-off-by: kuba--<EMAIL_ADDRESS>Closes https://github.com/src-d/gitbase/issues/608

FYI: I've added binary assets to git-lfs


TypeScript, MobX-React, and RefObjects

Fixed issue where inject decorated classes were not compatible with strongly typed RefObjects

Fixes #616
This is missing unit tests currently and should be added, I'm not really an expert here so I wouldn't know how to write them myself.
This should be treated as a breaking change, as it affects the usage of wrappedInstance on RefObjects, the migration path is to remove the .wrappedInstance and use the item directly.

@42shadow42 I need a little clarification. Is the goal to fix typings, or do you want to enable refForwarding on inject? Which of those two would be according to you the correct fix?
In either case, could you demonstrate what you are fixing in a small reproduction (codesandbox, unit test or otherwise), so that the solution can be verified?

@mweststrate The goal is to fix typings, the proposed solution is refForwarding.
Here is my reproduction:
mobx-injector.zip
If you look at parent-component.tsx you will see that typescript enforces typings of child and child2 variables, but the actual runtime types are inject wrappedInstances so while the typescript compiles runtime fails, the proposed fix of refForwarding makes the compile time type match the runtime type.

Thanks for the PR! I took the important changes, but refactored and cleaned up the as it got a bit messy in #644. Also added / updated tests.
So closing this one in favor of that one, but thanks for pointing out the solution and will put your name on the contributors list!


remove-layers-v1_1-step-1

1st step of https://github.com/CartoDB/cartodb/issues/4621

@juanignaciosl CR please

:+1:

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)


Semicolon not allowed after function-local item

As seen in etaoins/arret@9e2989198556c8f0ef322cde0913d98299c65e05 rust-analyzer does not allow a semicolon after a function-local enum:
fn simple_function() {
    enum LocalEnum {
        One,
        Two,
    };
}

This is accepted by rustc but rust-analyzer complains with:
Syntax Error: expected item, found `;`
consider removing this semicolon

I'd like to try to tackle this issue :)


fsdoc keywords (like @summary) break line numbering

The line number reported by #info is off by one for certain dependencies, but nor for the current file (concretely, pressing M-. goes to the right line for local definitions, but e.g. for List.append it goes one line too high).

Test case:
a.fst:
module A
(**
@summary XXX
*)
let b = 1 + "A"

$ fstar a.fst
./a.fst(4,12-4,15): (Error) Expected expression of type "Prims.int"; got expression ""A"" of type "Prims.string"
1 error was reported (see above)

Contrast this with:
a.fst:
module A
(**
// @summary XXX
*)
let b = 1 + "A"

$ fstar a.fst
./a.fst(5,12-5,15): (Error) Expected expression of type "Prims.int"; got expression ""A"" of type "Prims.string"
1 error was reported (see above)

I think the @-keyword handling code was written by @ad-l . Though @kyoDralliam maybe you can help too, since you're good with parsers :)

The problem is in the fsdoc_kw_arg rule of the lexer
The newline handler does not call mknewline which throws the lc off

Thanks! Do you want to prepare a patch, or should I?

I fixed it in the Unicode lexer... it can probably wait until the feature lands


Create a step-by-step landlord explainer to go w/ education tool

It could includes some of the FAQs aimed at LLs

I am interested in working on this but see that it is dated and want to confirm that it is still a priority.

I think we need to discuss again to make sure we know what this is, yeah. And maybe we won't do it at all

@nonprofittechy is this still open?


begining to work at 62

the inox's pkgbuild gaves troubles with version 62,  and i'm working with chromium-dev pkgbuild + @gcarq + @eloston useful patches
changes

new dead-patch,   disable-help-menu
gn-patch its taken from ubuntu ppa
the rest of patches (no inox, no ug, no gn from ubuntu)      its from chromium-dev, made by  @sl1pkn07

First issues

/third_party/crc32c
/third_party/leveldatabase

NEEDS this flag   -std=c++17
if you dont provide it, DONT BUILD

real trobles with safebrowsing  :(


feat: [GH-198] Adding unit tests for eval.go file

Adding unit tests for eval.go file
Few test cases are blocked due to GH-201, would update once issue is resolved.

@JyotinderSingh @yashs360 please review once.

Could you please rebase on latest master and resolve the conflicts?

@JyotinderSingh please review once have rebase the branch, and edited some new test case to maintain parity with testCase struct.


Button :active styles not applied in Firefox

🐛 Bug report
Current behavior
When clicking on a Button in Firefox, the hover styles are applied on hover but the active styles are not applied on click.
When using Chrome, the active styles are applied correctly on click.
Steps to reproduce the bug

In Firefox, navigate to https://reakit.io/docs/button/
Click the Button

Expected behavior
The active styles should be applied, as they are in Chrome.
Possible solutions
¯\(ツ)/¯
I did notice that you perform a variety of checks on the onMouseDown handler of Tabbable, it's possible that one of those event.preventDefaults() is somehow preventing Firefox from thinking the Button is being clicked?
Environment
Verified locally and via Browserstack on Firefox 69 (latest) on both Windows 10 and Mac Mojave

Thank you for opening the issue, @folz! :)
I confirm that this is the line that is preventing Firefox from setting the :active state on any Tabbable component (including Button):
https://github.com/reakit/reakit/blob/efaa95e2090853fa70c401487f0173c6cb684738/packages/reakit/src/Tabbable/Tabbable.ts#L98
I'm still not sure how to fix that. That preventDefault is necessary so we can consistently set focus on buttons when they get clicked (currently, some browsers set focus, others don't).

Gotcha, I appreciate the time you spent looking into it.
I came across https://github.com/w3c/csswg-drafts/issues/2262, which links to two other Firefox bugs [one] [two]. It appears that, unlike other browsers, Firefox considers the :active state finished once preventDefault() is called, so there is not really a way to both use preventDefault and have the :active pseudoclass. Same thing would apply to the :hover pseudoclass if reakit called preventDefault on that event.
Since I am mainly interested in applying styles,

I wrote a PR to demonstrate how data-active might be applied, as I think that a consistent visual active state is closely related to accessibility and is something that Reakit should consider addressing across browser differences.
However, I get that this might be outside the scope of what you want Reakit core to ship with, so please feel free to close the PR and I'll introduce those changes locally to my repo.

I posted a Twitter thread about turning Reakit buttons into divs: https://twitter.com/diegohaz/status/1176998100495491072
Getting rid of this onMouseDown will potentially fix this problem and #448


Attempt fixing Issue 3923 by caching and reusing resolution results

Description of Change
As discussed in Issue #3923 try caching the resolution results and reusing that instead of doing (un)filtered resolutions  dependency-by-dependency
Think that a bit of further testing would be warranted to ensure it does not introduce regressions.
Have test cases been added to cover the new functionality?
no, functionality was refactored

@jeremylong a good step forward. But definitely needs more work as it currently creates duplicate dependencies on aggregate-scanning a large multimodule project

@jeremylong Differences in results can be explained by a failure to resolve the reactor-projects in the new code plus existing behaviour that virtual dependencies are not merge together as a single one.
If you're working towards a 6.5.2 release feel free to already promote this from draft to normal and merge it. I will try to find out why the resolution did work in the 6.5.1 case and doesn't work in the 6.5.2-SNAPSHOT case from this branch, but the difference I spotted is in my view sufficiently explainable to warrant inclusion of this change in a next fixpack in order to solve the massive slowdown.
The project I used had 10 inter-module-dependencies, which were 10 resolved dependencies in 6.5.1. In 6.5.2-SNAPSHOT they become unresolved, triggering virtual dependency creation. And as some of those inter-module dependencies occur for multiple dependencies it results in a total of 24 inter-module dependencies being listed for what actually is only 10 inter-module dependencies.
That multiplication of virtual dependencies also happens in 6.5.1 if a reactor-dependency in a project is not yet resolvable.
Not resolving the (existing) release versions of the reactor-dependencies I consider a regression of this change. Duplicating the virtual dependencies I will file a separate GH issue once I've managed to tackle this regression.
If you decide to merge this already in order to put out a 6.5.2 the regression could be handled under a new GH issue.

@jeremylong already found the pattern when it fails: when the artifact searched for uses a classifier. So think it's better to get this resolved before merging.

@jeremylong already found the pattern when it fails: when the artifact searched for uses a classifier. So think it's better to get this resolved before merging.

Minor correction, not the classifier, but a non-jar packaging (ejb)

I feel like we need to release 6.5.2. We can publish another release as soon as the regressions are solved.

I feel like we need to release 6.5.2. We can publish another release as soon as the regressions are solved.

Sorry I hadn't commented that the regression was resolved by my last commit. Could've gone into the 6.5.2. But I propose to hold back 6.5.3 until the duplication of virtual dependencies also gets resolved as well as I intend to look at that tonight.

@jeremylong Fix for #3944 is in its final testing stage and will get its own branch and PR


analyzer co19_2 test failures when switching the parser to fasta

@danrubel

Are there test failures that need to be tracked here, or can we close this?

I see 60 references from co19_2/co19_2-analyzer.status.

I have fixed what I can in the parser (see above) and many (all?) of the rest are pre-existing issues. If you do find another parser or AstBuilder related issue, please let me know

Great! I'll close this now given that the remaining issues are pre-existing.


服务启动后异常终止

当我执行脚本  aws_e2e.sh reparallelization 6.7B As
报错
[2024-07-26 11:42:36.911325] logfiles in SpotServe-artifact/elastic-switch/log/6.7B/real/baseline_tpt1.5_cv6-0304
[2024-07-26 11:42:36.913075] gs TcpThread, listening,<PHONE_NUMBER>.913
[2024-07-26 11:42:37.853532] gs, accepted from pc rank 9,<PHONE_NUMBER>.854
[2024-07-26 11:42:37.861020] gs, accepted from pc rank 8,<PHONE_NUMBER>.861
[2024-07-26 11:42:37.861646] gs, accepted from pc rank 5,<PHONE_NUMBER>.862
[2024-07-26 11:42:37.861808] gs, accepted from pc rank 4,<PHONE_NUMBER>.862
[2024-07-26 11:42:37.862042] gs, accepted from pc rank 7,<PHONE_NUMBER>.862
[2024-07-26 11:42:37.862121] gs, accepted from pc rank 6,<PHONE_NUMBER>.862
[2024-07-26 11:42:44.969868] gs, accepted from pc rank 2,<PHONE_NUMBER>.970
[2024-07-26 11:42:45.016907] gs, accepted from pc rank 1,<PHONE_NUMBER>.017
[2024-07-26 11:42:45.188154] gs, accepted from pc rank 3,<PHONE_NUMBER>.188
[2024-07-26 11:42:45.230694] gs, accepted from pc rank 0,<PHONE_NUMBER>.231
[2024-07-26 11:42:45.275082] (0.000) system initialized.
[2024-07-26 11:42:45.275225] (0.000) next-event: add at 0.000, waiting...
[2024-07-26 11:42:45.275558] (0.000) cur_nnodes: 7, next_strategy: (1, 4, 1, 4, 4, 1), requited_tpt=2.0
[2024-07-26 11:42:45.275718] (0.001) **init** set new strategy (1, 4, 1, 4, 4, 1) to shared memory
[2024-07-26 11:42:45.277036] batch_requests: False
.
.
.
[2024-07-26 11:42:46.003677] >>>>> (0.709) -- (0.709) dispatch query 0 to replica 0, n: 1, pool: 0
[2024-07-26 11:42:46.614326] >>>>> (1.320) -- (1.319) dispatch query 1 to replica 0, n: 1, pool: 1
[2024-07-26 11:42:47.302399] >>>>> (2.008) -- (2.008) dispatch query 2 to replica 0, n: 1, pool: 2
[2024-07-26 11:42:47.891319] >>>>> (2.597) -- (2.596) dispatch query 3 to replica 0, n: 1, pool: 3
[2024-07-26 11:42:48.638453] >>>>> (3.344) -- (3.344) dispatch query 4 to replica 0, n: 1, pool: 4
[2024-07-26 11:42:49.300773] >>>>> (4.006) -- (4.006) dispatch query 5 to replica 0, n: 1, pool: 5
[2024-07-26 11:42:49.991542] >>>>> (4.697) -- (4.697) dispatch query 6 to replica 0, n: 1, pool: 6
[2024-07-26 11:42:50.825222] >>>>> (5.530) -- (5.530) dispatch query 7 to replica 0, n: 1, pool: 7
[2024-07-26 11:42:55.454942] >>>>> (10.160) -- (6.221) dispatch query 8 to replica 0, n: 4, pool: 7
[2024-07-26 11:42:55.454987] >>>>> (10.160) -- (6.832) dispatch query 9 to replica 0, n: 4, pool: 8
[2024-07-26 11:42:55.455010] >>>>> (10.160) -- (7.542) dispatch query 10 to replica 0, n: 4, pool: 9
[2024-07-26 11:42:55.455029] >>>>> (10.160) -- (8.168) dispatch query 11 to replica 0, n: 4, pool: 10
[2024-07-26 11:46:15.288729] (210.014) cur_nnodes: 8, next_strategy: (2, 4, 1, 4, 4, 1), requited_tpt=2.0
[2024-07-26 11:46:15.288793] (210.014) switching from (1, 4, 1, 4, 4, 1) to (2, 4, 1, 4, 4, 1)
[2024-07-26 11:46:15.289258] (210.014) set new strategy (2, 4, 1, 4, 4, 1) to shared memory, estimate transfer cost: -0.500
[2024-07-26 11:46:15.346544] cluster strategy changed, state: 1, strategy: (2, 4, 1, 4, 4, 1), is_finished: False
[2024-07-26 11:46:15.346719] api_server close replicas 0...
[2024-07-26 11:46:15.346736] api_server send xfer_cost -0.5...
Process api_server:
Traceback (most recent call last):
  File "/usr/lib64/python3.9/multiprocessing/process.py", line 315, in _bootstrap
    self.run()
  File "/usr/lib64/python3.9/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/home/ansible/SpotServe-artifact/elastic-switch/scheduler/api_server.py", line 538, in deploy_api_server
    asyncio.run(api_server.run())
  File "/usr/lib64/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/lib64/python3.9/asyncio/base_events.py", line 647, in run_until_complete
    return future.result()
  File "/home/ansible/SpotServe-artifact/elastic-switch/scheduler/api_server.py", line 532, in run
    await asyncio.gather(self.watch_cluster(), self.dispatch_request())
  File "/home/ansible/SpotServe-artifact/elastic-switch/scheduler/api_server.py", line 311, in watch_cluster
    await self.send_xfer_cost(xfet_cost, replicas_to_close)
  File "/home/ansible/SpotServe-artifact/elastic-switch/scheduler/api_server.py", line 272, in send_xfer_cost
    await self.api_agent[replica_id].request_agent.async_send(struct.pack('ii', -2, -2))
  File "/home/ansible/SpotServe-artifact/elastic-switch/util/util.py", line 52, in async_send
    sent = self.conn.send(msg)
ConnectionResetError: [Errno 104] Connection reset by peer

Hi @guangtoudun , have you resolved this issue? I encountered similar error and it would be really helpful if you could share how you resolved this ; )

Hi @guangtoudun , have you resolved this issue? I encountered similar error and it would be really helpful if you could share how you resolved this ; )

这类文件的最后一列数据有问题，需要修改。

Hi @guangtoudun , have you resolved this issue? I encountered similar error and it would be really helpful if you could share how you resolved this ; )

这类文件的最后一列数据有问题，导致读取请求数据错误。

Thanks for the prompt reply! Would you mind elaborating on what the problem is and how you modify it to get it running properly? This would be really helpful 🙌

QUERY_FILE 一行为一条请求，QUERY_TRACE 是请求的trace，最后一列即当前请求行在QUERY_FILE的偏移。
当前逻辑是根据QUERY_TRACE读取QUERY_FILE的某一行，读取后需要将字符串转为数字，由于偏移错误导致转换错误，从而导致该client断开。
解决方法：重新计算QUERY_FILE每行开始的偏移，替换QUERY_TRACE的最后一列。

QUERY_FILE 一行为一条请求，QUERY_TRACE 是请求的trace，最后一列即当前请求行在QUERY_FILE的偏移。
当前逻辑是根据QUERY_TRACE读取QUERY_FILE的某一行，读取后需要将字符串转为数字，由于偏移错误导致转换错误，从而导致该client断开。
解决方法：重新计算QUERY_FILE每行开始的偏移，替换QUERY_TRACE的最后一列。

Thanks! That really helps. I found this is also the root cause of the problem described in #8.


how to convert created dataset to coco detection yolo format?

I am using  GroundedSAM as base model to label all images , i have only 1 class.
Resulting dataset contains many points of identified labels (probably for segmentation usage as well).
However I need to convert this dataset to coco detection format (class and 4 points) to use it outside of auto distill.
Is it possible?

It’s saved in YOLO format in the output_folder directory you pass to your BaseModel by default. It uses the YOLO polygon txt format supported by most modern YOLO models if your BaseModel predicts polygons (like GroundedSAM does), or the YOLO box format if your BaseModel predicts boxes (like GroundingDINO, DETIC, and OWL-ViT do).


Localtunnel.me is down

ITs down.

+1

The website or the service? The latter is down for me too.

Well
Both for me
Manuel Dupont
On 13 Nov 2017, at 18:34, Jonathan Arbely <notifications<EMAIL_ADDRESS>wrote:
The website or the service? The latter is down for me too.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/localtunnel/localtunnel/issues/199#issuecomment-343995859, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHN6oVJxksNLLRKmrmNClZNqvYKW4IiZks5s2H2SgaJpZM4QbuXs.

Same for me...

The localtunnel.me site is also giving 502. Service is also giving error in nodejs err event
Error: localtunnel server returned an error, please try again

All services have been restored. This can be closed.

Thanks @jonathanarbely, indeed everything works fine now.

Its down for me, gives me a status of 502 and a tunnel server offline error

is localtunnel.me down right now?

Hey @nicklesscs
Nope the service seems to be up just fine

Yeah, it was my school wifi blocking it.> Hey @nicklesscs

Nope the service seems to be up just fine

Yeah, it was my school Wi-Fi blocking it.


MaterializeEncodingConversionTarget + Debug + ASan = weird stack-buffer-overflow

STR:
Configure with Debug build type and enable ASan:
cmake -DCMAKE_BUILD_TYPE=Debug IREE_ENABLE_ASAN=ON

Rebuild iree-compile.
cmake --build . --target iree-compile

Run:
tools/iree-compile --iree-hal-target-backends=llvm-cpu $HOME/iree/runtime/src/iree/modules/check/test/success.mlir -o /tmp/a.vmfb

Result:
https://gist.github.com/bjacob/bd789d070aae45a6848887cef60fe064
I debugged this in GDB. The op here is a arith.constant 0 : index .   The getOperands() returns an empty range, which consists of a nullptr base pointer and a 0 length. Then as I step into the llvm::any_of at https://github.com/iree-org/iree/blob/1b95a2f285ac8d44e44f06de322abf5b315495bd/llvm-external-projects/iree-dialects/lib/Dialect/LinalgExt/Passes/MaterializeEncoding.cpp#L413 , it immediately triggers the ASan error (above gist link).  Emphasis on immediately. So the code that's at fault here is part of the mechanics of the function call to llvm::any_of, before the actual start of llvm::any_of. Either that, or a miscompile.

Can you try dropping the & here https://github.com/iree-org/iree/blob/1b95a2f285ac8d44e44f06de322abf5b315495bd/llvm-external-projects/iree-dialects/lib/Dialect/LinalgExt/Passes/MaterializeEncoding.cpp#LL417C6-L417C10

Nice, it works with a = instead of the &.  (I need the = to be able to reference hasOperandOrResultsWithEncoding, unless i nested lambdas, which would look even hairier.
Can you make sense of the fact that changing the & into = makes it work? I can't.


[resotolib][feat] enum support for data model export

Description
Allow exporting enumerations as part of the data model.
The enumeration has to be based on string.
Example:
class ExampleEnum(Enum):
    Moon = "moon"
    Sun = "sun"
    Earth = "earth"

@dataclass
class DataClassExample:
    kind: ClassVar[str] = "example"
    some_enum: ExampleEnum

To-Dos

[x] Add test coverage for new or updated functionality
[x] Lint and test with tox

Issues Fixed

Fixes #XXXX

Code of Conduct
By submitting this pull request, I agree to follow the code of conduct.

Codecov Report

Merging #720 (16cafba) into main (1e814f3) will decrease coverage by 0.06%.
The diff coverage is 80.95%.

@@            Coverage Diff             @@
##             main     #720      +/-   ##
==========================================
- Coverage   89.50%   89.44%   -0.07%
==========================================
  Files          67       68       +1
  Lines        9456     9513      +57
==========================================
+ Hits         8464     8509      +45
- Misses        992     1004      +12

Flag
Coverage Δ

resotocore
89.44% <80.95%> (-0.07%)
:arrow_down:

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

Impacted Files
Coverage Δ

...esotocore/resotocore/config/core_config_handler.py
79.48% <58.62%> (-12.83%)
:arrow_down:

resotocore/resotocore/__main__.py
87.85% <100.00%> (ø)

resotocore/resotocore/core_config.py
98.09% <100.00%> (+0.29%)
:arrow_up:

resotocore/resotocore/validator.py
100.00% <100.00%> (ø)

resotocore/resotocore/worker_task_queue.py
88.75% <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 917ee62...16cafba. Read the comment docs.


Retort-button missing from PMs

For some reason the retort-button is no longer shown in private messages...

This works again :)


false is not a valid value

MyApp.config[:live] = true
MyApp.config.live # => true
MyApp.config[:live] = false
MyApp.config.live # => Econfig::NotFound: configuration key 'live' is not set

This is more or less by design at the moment, considering we raise an error when a key is missing and we can't differentiate a missing value from a nil or false value.
Perhaps allowing false would be in order, but still treat nil as a missing value?
// @Burgestrand

Closes 36b49e9b84b2795c3bcc42c522e0b59e406f9b38


Login Button adding a border of black colour on hover

Description
When the cursor hovers over the login button of the website, add a black (dark colour) colour border around it so that the user can know that they are about to click abutton.
Screenshots

Additional information
No response
🥦 Browser
Other
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to work on this issue ?
Yes I am willing to submit a PR!

can I work on this issue ?

I can work on this. Please assign me this issue

Please assign this issue to me.

@exotic123567 Can you make something like this for all the register and Login buttons :
https://user-images.githubusercontent.com/72851613/196376112-892e0ece-25ab-4a1b-ab53-44e575177e16.mp4

Yes. I just have to add this to the css file when the cursor is hovering over the buttons

Can I work on this issue @IAmTamal

@exotic123567 What's the update on the issue ?
Are you working on it ? OR should i remove the assignment


token-client: Check simulation results for error

Problem
If the simulation for compute unit limit fails in the token-cli, it may continue to try to broadcast a transaction since the error falls through. Although that transaction should fail too, at least we don't run the risk of broadcasting something known to be bad.
Summary of changes
Add an err() function on the simulation results, and abort if the simulation for compute units fails.

What shall I do?


[Dubbo-2323]the AsyncRpcResult should store the copy of the context #2323

What is the purpose of the change
fix https://github.com/apache/incubator-dubbo/issues/2323
Brief changelog
the AsyncRpcResult should store the copy of the context
Verifying this change
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn clean install -DskipTests & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

@chickenlj

I will take a look at it now.

Hi @bneliao ,  I think a copy of RpcContext would be a good solution, I wil merge it to master now.
Please see the comment I made on #2323.


Support net40

This implementation was recently re-extracted from Serilog, and an unfortunate side effect was that we dropped support for net40. Serilog is typically used in apps where newer runtime versions are easier to target, and dropping net40 made sense there. However,  Message templates can be used in libraries where support for a wider range of framework versions are more important.
Examples of existing libraries that may target older net frameworks and could benefit from message templates are: web servers (eg. suave), actor frameworks (eg. Akka.net), libLog, build tools (eg. Fake).
The main issues for supporting net40 is use of System.Reflection and collections (eg. IReadOnlyDictionary<T>), which were solved previously by a few well-placed #if directives.
A pain in serilog (1.5.x) was the lack of binary compatibility between net40 and net45. For example, the use of IReadOnlyDictionary<T> (only available in net45+) in the public interface makes it impossible for net40 targets to execute against net45 binaries. Message templates C# inherited this problem from Serilog, but we are pre 1.0 and can avoid that mistake by changing the public API types to only use types available in all supported targets.
/cc @nblumhardt thoughts?

I copied src from an old version that did support net40 and made PR #5.
I don't want to pull #5 because it's a mess with multiple unrelated changes and whitespace everywhere, but at it shows how net40 could be done relatively easily.

Fixed via #6


I would like to add a coding website template to it

I would like to add a coding website template for coding newbies

@Satakshijain go ahead and make a PR with deployed link :)


[api-docs] removes dscord + adds dsharp slash commands library

A new commit was made into the api-docs repo. This issue was created automatically. Need to review if we made any change to the library for this commit.
https://github.com/discord/discord-api-docs/commit/ba9e3e14b457900d47c0d43892f5698e7a6d8d04

ncn


Qdynamic calibration quantizer does not compute symmetric clips correctly

Setup
Running Direct Quantization (DQ) of RoBERTa. Clips are set using only calibration, no additional training.
Setting qcfg["qa_mode"] = "maxsym" to select a symmetric max quantizer for the activations.
Qdynamic is automatically selected as calibration quantizer.
Using qmodel_calibration_new or qmodel_calibration.
Issue
activation clip values resulting from DQ are asymmetric.
Observations

Symmetry is enforced within Qdynamic whenever the quantization mode ends with _sym:
https://github.com/foundation-model-stack/fms-model-optimizer/blob/31bc3f6b0b01a43dbf5d05102b549b87168271c7/fms_mo/quant/quantizers.py#L3515
However, quantizers ending with _sym are not supported, symmetric quantizers are maxsym, pactsym, pactsym+.

even fixing this line, clip values remain asymmetric

roberta.encoder.layer.0.attention.self.query.quantize_feature.clip_val          5.0156
roberta.encoder.layer.0.attention.self.query.quantize_feature.clip_valn        -2.3047

replacing Qdynamic with Qmax (with argument minmax=False) produces activation symmetric clips.

PR #26 addresses the most common scenarios in which this issue arises, although some selection of symmetric quantizers may still behave incorrectly at calibration. Closing this issue, we can reopen in the future if there is a need.


docker-compose exec mysql bash  error

Info:

Docker version ($ docker --version): Docker version 17.06.1-ce, build 874a737
Laradock commit ($ git rev-parse HEAD):
System info (Mac, PC, Linux):  Linux
System info disto/version: ubuntu 16.04

Issue:

Frist I did ..docker-compose up mysql. It will show Creating laradock_mysql_1 ... done
but when I do docker-compose exec mysql bash will show
ERROR: No container found for mysql_1
then I checked docker ps, mysql is not there.

Expected behavior:

Reproduce:

Relevant Code:
// place a code sample here

What's the output of docker-compose ps?

Also please post the logs from docker-compose logs mysql.


Webpages go blank

Upon visiting any page on the site, pageviews will temporarily display with all asset variables loading, then the page  goes blank - no error message displayed, just a blank page.

This issue appears to be resolved


Clarify section 3.14 and add Third Party Tracking as an opt-in threat model

Migrated from https://github.com/mikewest/spec-questionnaire/issues/6
@mikeperry-tor wrote:

It seems that the question in section 3.14 ("Does this specification distinguish between behavior in first-party and third-party contexts?") is very easy to misinterpret or overlook entirely, even though it is absolutely essential to any evaluation of an API from a privacy perspective.
For example, I could easily see a specification that decides that this section is satisfied simply by allowing for the third party script to detect its context, and then decide for itself how it wants to use the API (independent of any considerations of tracking, consent, or user control).
Something like this would be a bit stronger and clearer:
"At minimum, every new API or feature should be capable of being configured by the user to gracefully degrade into a functional mode of operation that does not allow third party content elements to use it to track unique users between different first party sites. Specifically, any storage, authentication tokens, shared state, and cross-window communication should be capable of being isolated between different first party origins, at user option.
For detailed guidance on how to provide graceful degradation to protect against more subtle forms of tracking that do not involve direct communication or unique identifier storage (aka 'fingerprinting'), we refer the reader to https://w3c.github.io/fingerprinting-guidance/."
In Tor Browser, we've implemented graceful degradation of the browser cache and DOM storage APIs by double keying all entries using both the first party and third party origin. This allows third party elements to continue to use this functionality in iframes and mashups, but prevents them from using the functionality to track users between different first party sites. In other cases, we've simply had to disable offending functionality (due to lack of engineering resources), which obviously has a significant impact on usability when things break.
If new APIs and feature specifications came with graceful degradation modes that did not require disabling them outright, the web would be a much better place.
If it were up to me, I would also elevate "Third Party Tracking" to a threat model that users could opt-in to protect themselves against, and specify this in the threat model section. All features should be capable of allowing the user to select this threat model via a single choice in their browser UI that applies to all browser features (instead of being given control only over third party cookies, as is the case today).
I can submit a pull request for this threat model addition if you like.

@marcoscaceres commented:

@mikeperry-tor I'm having trouble understanding:
"At minimum, every new API or feature should be capable of being configured by the user to gracefully degrade into a functional mode of operation that does not allow third party content elements to use it to track unique users between different first party sites."
Can you maybe follow that by a couple of examples to clarify what you mean? Or how it could be done with some other existing APIs?

I agree that "Does this specification distinguish between behavior in first-party and third-party contexts?" is not strong enough but OTOH, @mikeperry-tor's examples sound more like an issue with browser implementation than the feature specification itself. Perhaps I'm not understanding - are there examples of features that prevent techniques like double-keying at the specification level?

If it were up to me, I would also elevate "Third Party Tracking" to a threat model that users could opt-in to protect themselves against, and specify this in the threat model section. All features should be capable of allowing the user to select this threat model via a single choice in their browser UI that applies to all browser features (instead of being given control only over third party cookies, as is the case today).
I can submit a pull request for this threat model addition if you like.

I am in favor of this addition.

Are there examples of features that prevent techniques like double-keying at the specification level?

Typically they tend to impede compatible, gracefully degrading implementations of these techniques through neglect of treatment of third party tracking. This leads website developers to create sites that rely on a particular type of functionality behaving in a way that is incompatible with isolation in  unpredictable and/or breakage-inducing ways.
Four examples:

URL.createObjectURL creates blob URL UUIDs that may be sourced from any origin. The spec seems unclear on this point, but the Firefox implementation allows image src, script src, iframe, and other accesses to succeed. A hypothetical example of breakage would be if a site stores my account's current avatar/availability status in a blob URL and expects to be able to display it in like buttons or federated login choices on arbitrary sites.
SharedWorker threads specify that if the user agent is choosing to isolate third party content, the scope (and presumably the reflected self object) should be set to null (https://html.spec.whatwg.org/multipage/workers.html#sharedworker). Unfortunately, this is described as a developer feature, not an anti-tracking feature, and so none of the developer docs describe this potential breakage-inducing variant in functionality. It would make more sense if this object was non-null, but not shared, and the specification was clear that content should not rely on the self property to contain values they expected, or share state, documents, and event handlers how they expect. I'm also unclear based on the spec how the application cache or the document list should behave..
HTTP/2 section 9.1 (https://http2.github.io/http2-spec/#rfc.section.9.1) specifies that clients SHOULD NOT create more than one connection to a site, where as in Tor Browser, we will be creating a new connection to sites that are loaded under different top-level first party domains. This is unlikely to cause breakage, but it is a worrying thing to see specified.
In cases like HSTS and possibly also CSP upgrades (https://w3c.github.io/webappsec/specs/upgrade/), to avoid supercookies we will likely ignore cached HSTS and CSP state for third parties when the first party is HTTP, and simply block third party elements that would have been upgraded because of previously cached rules when the first party is HTTPS. This may lead to situations where sites rely on this caching functionality to deploy HTTPS properly, and those sites will break when isolation is enabled.

Let me know when any pull requests should be submitted, and what form they should take.

An example of doing this (comparatively) well in a spec is Canvas, which has the origin-clean flag http://www.w3.org/TR/html5/scripting-1.html#security-with-canvas-elements. The only issue I have with it is that it says the flag MUST start as 'true', whereas someone might want to default it to false (thereby making the canvas unreadable).
I had thought that privacy mode might be one thing that took advantage of these kinds of hooks in the specs to give users control. It probably isn't the right thing to do this with, but there could eventually be some sort of mode like it -- either in the standards our outside of them (like TorBrowser has done) that takes advantage of them.
So, +1 from me, even if browsers don't surface controls immediately, having these controls in the specs is important.
WRT H2 connection coalescing and similar things - this is actually being discussed right now, see https://github.com/w3c/resource-hints/issues/32.

@mikeperry-tor Thanks, you can submit pull requests at any time to this repo. The earlier the better since some specs are already using them, ex: #1

Hello.
Tough one.
To simplify this (as it's not the core element of the questionnaire), I'll include:
_Third-party tracking may occur when content from one origin is embedded or otherwise injected in another origin in a way that information may be accessed, revealed, queried or reasoned by third-party. This third-party may be a script injected on a first-party site

The simplest example is injecting a link to a site that behaves differently under specific condition, for example based on the fact that user is or is not logged to the site. This may reveal that the user has an account on a site._


Update forum references

:tada: This PR is included in version 1.16.2 :tada:
The release is available on:

1.16.2
GitHub release

Your semantic-release bot :package::rocket:


turbo:load won't be triggered when a FormSubmission request fails

When a FormSubmission request fails and return 400-500 code, turbo:load won't be triggered. eg:
application.js
document.addEventListener('turbo:load', function () {
  console.log('turbo load')
  document.getElementById('demo').replaceWith('demo replace')
})

new.html.erb

demo

<%= form_with(model: @post) do |f| %>
  <%= f.label :title %>
  <%= f.text_field :title %>
  <%= f.submit %>
<% end %>

posts_controller.rb
def create
    @post = Post.new(post_params)

    respond_to do |format|
      if @post.save
        format.html { redirect_to @post, notice: "Post was successfully created." }
        format.json { render :show, status: :created, location: @post }
      else
        format.html { render :new, status: :unprocessable_entity }
        format.json { render json: @post.errors, status: :unprocessable_entity }
      end
    end
  end

class Post < ApplicationRecord
  validates :title, presence: true
end

After submit form, it should show demo replace, but it showed demo because of turbo:load hasn't be triggered.

More info https://github.com/SimoTod/alpine-turbo-drive-adapter/issues/29#issuecomment-756062646

This is by design. The turbo:load event fires in response to a successful visit, and form submissions only trigger visits when the server responds with a redirect.

This is by design. The turbo:load event fires in response to a successful visit, and form submissions only trigger visits when the server responds with a redirect.

So, the PR https://github.com/hotwired/turbo/pull/39  is useless?  We often use turbo:load event to run some codes, if this is by design, after submit form fail and return 422, the code inside turbo:load won't run. So, how to run the codes inside turbo:load?

So, the PR https://github.com/hotwired/turbo/pull/39  is useless?  We often use turbo:load event to run some codes, if this is by design, after submit form fail and return 422, the code inside turbo:load won't run. So, how to run the codes inside turbo:load?

You shouldn't listen for the turbo:load event unless you specifically want to know that a visit—a navigation that changes the URL—has finished.
The Hotwire way is to put the code you want to run in the connect() method of a Stimulus controller, and then add a matching data-controller attribute to an element so that the code runs whenever the element appears on the page.

You shouldn't listen for the turbo:load event unless you specifically want to know that a visit—a navigation that changes the URL—has finished.
The Hotwire way is to put the code you want to run in the connect() method of a Stimulus controller, and then add a matching data-controller attribute to an element so that the code runs whenever the element appears on the page.

The Hotwire way is to put the code you want to run in the connect() method of a Stimulus controller, and then add a matching data-controller attribute to an element so that the code runs whenever the element appears on the page.

I see, thanks.

The Hotwire way is to put the code you want to run in the connect() method of a Stimulus controller, and then add a matching data-controller attribute to an element so that the code runs whenever the element appears on the page.

I see, thanks.

@sstephenson Silly question, the page does get replaced though (it rerender the old page triggering a turbo:render event).
If the goal is to keep the page as it is, why does it replace the content? Thanks

@sstephenson Silly question, the page does get replaced though (it rerender the old page triggering a turbo:render event).
If the goal is to keep the page as it is, why does it replace the content? Thanks

I find the decision not to fire the turbo:load event not in line with the docs:

Turbo Drive evaluates

I find the decision not to fire the turbo:load event not in line with the docs:

Turbo Drive evaluates

Ouch! This means that all of our existing legacy code that once was based on:
$(document).ready( function( e ) { ... code to init legacy js like parsley, datatables, datetimepicker etc. ...}
Then replaced with:
$(document).on('turbolinks:load', function( e ) { ... legacy js code ...}
Then replaced with:
$(document).on('turbo:load', function( e ) { ... legacy js code ...}
Now won't work in the case of a form submission that has validation errors?
And all of that has to be migrated to Stimulus?
Is there no way around this?  I tried to use the turbo:render event and it too does not get triggered when a form submission fails.

I ended up booting 3 times: turbo:render, turbo:load and load.
Because React seems to be idempotent, and our codebase seems to be as well, we haven't noticed a major memory leak or slowness. Still, this is upsetting because it's not advertised as such.
What I understand is that only stimulus code is automatically re-booted if necessary, but external dependencies are to be either idempotent and booted multiple times, or booted once and hope for no re-render @sstephenson ?

I also have a react component that I attached using turbo:load
my current solution is
adding document listerner for turbo:load and turbo:render
  document.addEventListener('turbo:load', () => {
    let domContainer = document.querySelector('#like_button_container');
    if (domContainer) {
      ReactDOM.render(<MyComponent />, domContainer);
    }
  })

  document.addEventListener('turbo:render', () => {
    let domContainer = document.querySelector('#like_button_container');
    if (domContainer) {
      ReactDOM.render(<MyComponent />, domContainer);
    }
  })

What I understand is that only stimulus code is automatically re-booted if necessary, but external dependencies are to be either idempotent and booted multiple times, or booted once and hope for no re-render

if that's how about we attached the react component using stimulus controller?

One year later, do we have a proper workaround for this? Is turbo really encouraging us to use an event that is fired twice?
Thanks!

Still looking for a proper workaround.
Even ugly hacks such as
document.addEventListener('turbo:load', () => queryDocumentForTomSelect());
document.addEventListener('turbo:render', () => queryDocumentForTomSelect());
document.addEventListener('turbo:frame-load', () => queryDocumentForTomSelect());

Don't work when rendering using turbo-stream with a status of 422 unprocessable_entity


Update requirements.txt to pin wheel and setuptools

pin
wheel==0.38.4
setuptools==65.6.3

to avoid ReDoS

Can you give me some more context on why this is necessary? Fine with adding it if I have a little more info. otherwise like to leave things looser

This is only intended to keep the version numbers above the given versions, so we could also use >= probably. The reason for them is that both are requirements for requirements, and they use insecure versions themselves currently. This would be removable at a later date.
That said, I'm not sure security needs to be the biggest concern with this particular project!

ah I see. lemme think about this one and get back to ya :)
Thinking its not needed but perhaps it would be nice to have this loosely pinned somewhere. Only concern I have is having them be too high of versions here, which could cause issues. Worth checking colab's versions, etc.


Contact info for honor code

We need an email address that people can write to in case someone breaks the rules of the honor code.

openmlhq?

Sure


unexpected behavior of trash can on literal or lookup fields; fix or remove trash can

Our model is that all fields are shown "open" except for fields of type nested resource.
Unexpected behavior is this: when you use the trash can to delete info you entered in a lookup field or a literal field, the field ends up closed with a +Add. Instead the field should just be blank.
Example template on stage: pcc:bf2:Monograph:Work
The "Date of Work" field is a literal. It is shown open when the template is opened, as desired.

If I add some text:

and then use the "x" to remove the text I added:

the field is still open, as expected (and the date statement is removed from preview).
But if I use the trash can, I end up with this

Instead I should end up with the field still open but blank.
The same unexpected behavior happens in lookup fields.
Brings up the question: Why do we have the trash can on simple (unnested) fields? is it just so you could easily delete everything in a field, when there are multiple values, instead of having to delete each one by one?
Do we need the trash can on fields other than fields of type nested resource?

re "Why do we have the trash can on simple (unnested) fields?"
currently if you have a literal field with a default, and you delete the default value with the "x" button, you have no way to get the default value back (like if you deleted it accidentally).
if instead you delete the default value with the trash can, then +Add appears to get the default back
if we were to remove the trash can on simple fields, we need to consider whether users would need to retrieve a default that was deleted

putting this on ice for now

@michelleif The UI has changed since this ticket was written. Can it now be closed?

so you want to put a message on the page saying this is all out of date?


can't start language_server_windows_x64.exe

Error detected while processing function codeium#server#Start[30]..<SNR>70_ActuallyStart:
line   14:
E903: Process failed to start: unknown error: "C:\Users\choij/.codeium/bin/daf4912ada2a4934c00b8c5a321cec4998a15e70/language_server_windows_x64.exe"

is printed as soon as I start Neovim and the plugin doesn't work
Environment:
Windows 11
neovim 0.8.3

Running from the console give me following error message:
The specified executable is not a valid application for this OS platform.At line:1 char:1

Are you on 32 bit or ARM Windows? We currently don't yet support those.

I'm using 64bit Windows 11 22H2 22621.522

Completey removing $HOME/.codeium/bin folder and letting the plugin reinstall language server solve the issue


RFC: Session API

Goal
Session and pty decoupled.
Some plugins need more control about Session instances in main process. It would be required, for example, if a plugin want to launch the pty in another host (like #2978) or intercept pty stream to duplicate/record/stream/log it.
Interception can already be done with a middleware in renderer process, but having a Session without a pty can't.
Proposal
I would suggest to add a new API entry: decorateSessionClass(Session). A plugin can expose this function that would return a new class that inherit from the (kind of) Session class received in parameter.
If multiple plugins declare this hook, we would finally get a class that have been multiple times inherited. It can lead to some conflicts but this is already the case for other decorate functions.

Can this be closed?

Yes! Thanks!

@chabou  Is there a PR to track the progress of this RFC?


s2geometry take 2

swap s2geometry-node (C++) for s2-geometry (pure javascript)
As per #165

On testing it , if already ok will merge it .

Verified , Will Merge it .. Thanks @coolaj86

Awesome! @billyriantono @Armax is client-side compatibility something this repo is interested in? That is, should I submit a PR or fork?


Unable to create working surge demo

https://auro-datepicker-v1.surge.sh/demo/
Running surge agains the rc-v1.0 branch results in a demo with the following error:
Uncaught TypeError: Failed to resolve module specifier "lit-element". Relative references must start with either "/", "./", or "../".

Transferred this issue to the generator as this is not only a problem with datepicker. The demo creation and distribution process has not been kept up well and there are abundant issues.


Fix issue affecting multi-label extlinux.conf files

The value for UBOOT_EXTLINUX_DEFAULT_LABEL needs to be the menu
description for the label (UBOOT_EXTLINUX_MENU_DESCRIPTION), not the
internal identifier for that label.
In the common case of a single entry, it's not necessary to specify a
default, and in the case of multiple entries, it's probably better to
require the distribution developer to provide a value for
UBOOT_EXTLINUX_DEFAULT_LABEL, to explicitly specify the description of
the label that should be default, if a default is required.

The settings currently there should work as-is, though, since the menu description defaults to being the label if not explicitly set, right?  I don't object to removing the default setting, or using ?= to make it easier to override.

The settings currently there should work as-is, though, since the menu description defaults to being the label if not explicitly set, right? I don't object to removing the default setting, or using ?= to make it easier to override.

It would, if there weren't an upstream bug in uboot-extlinux-config.bbclass, where they define a default menu description for the label "linux", but because of how they do label processing using OVERRIDES, and because OVERRIDES by default contains ${OS}, which pretty much always evaluates to "linux", the menu description not only defaults to "${DISTRO}", it's actually almost impossible to override currently.
OE has accepted my patch for those issues into master, but I'm not sure they're going to backport it to warrior.


max-height not working

If I use max-height in the component it does not work. max-width works as expected. Any idea?

Sorry, just had a container which was breaking my layout, so, all fine!


report on a Linux (Ubuntu) attempt to install Sabaki

On a recent and up-to-date Ubuntu:
$ sudo apt-get install nodejs
$ sudo apt-get install npm
$ npm run build:linux
This gives error messages about a missing "node"
$ sudo apt install nodejs-legacy
$ npm run build:linux
$ bin/sabaki-linux-x64/sabaki file.sgf
This yields a window with a dark dot where move 1 is going to be.
There are no navigation buttons. A navigation menu has "Forward --- Down arrow" but clicking the menu does not work, and there is no reaction to keys either. In fact no navigation seems possible. At the bottom right there is a button with three horizontal lines. Selecting the Info item shows players, date, event, so file.sgf was read successfully. In fact the player names are also given below the board.
No reaction at all is observed from choosing any of the menu items. (Left) clicking on the board gives alternatingly black and white stones. Middle and right clicks and keystrokes do not give any reaction. Since the menus do not work, saving is impossible. In short, this is mostly a failure. Leaving Sabaki elicits the question whether I want to save my changes. When I answer Yes, no filename is asked, but the input file is overwritten. My clicks have become a new variation in the given game.
$ npm test
...
Sabaki-master/test/boardTests.js:8
let board = new Board()
^^^
SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:374:25)
at Object.Module._extensions..js (module.js:417:10)
...
Uninstalled everything again.

You don't have to build Sabaki in order to use it. I recommend downloading the prebuilt binaries from the release page.
Of course, building Sabaki shouldn't have failed. I have some conjectures as to why it failed:

Your node is not up to date. Run node --version to check your version. The tests are written in ES6 which is almost fully supported in node 6.9.0.
You haven't installed the dependencies by running npm install.
Your npm is not up to date. Check your version with npm -v and run sudo npm install npm -g to update npm.

The software involved (sabaki, node,npm) was freshly installed. Now they have been removed again, but the versions must have been recent.
Using prebuilt binaries is a very dangerous thing to do. I really never do, but just this time I tried,
downloaded sabaki-v0.18.2-linux-x64.tar.gz, unpacked an ran the sabaki binary.
Comment on the unpack: unpacking littered the current directory. Standard is that foo-1.2.3.tar.gz unpacks to a subdirectory foo-1.2.3.
Comment on the execution: my window manager twm crashed, the system no longer reacted to mouse and keyboard. A reboot was needed. My first reboot in 2016. That is what happens if one runs random executables found somewhere on the net.

The software involved (sabaki, node,npm) was freshly installed [...] but the versions must have been recent.

Usually the node version you get with apt-get is an ancient one, like v0.6.19. Follow these instructions to install the latest version v6.9.0. Same with npm.

Comment on the unpack: unpacking littered the current directory. Standard is that foo-1.2.3.tar.gz unpacks to a subdirectory foo-1.2.3.

What standard are you speaking of?

Comment on the execution: my window manager twm crashed, the system no longer reacted to mouse and keyboard.

Is it still on Ubuntu? If not, please state your Linux distribution and other data.

That is what happens if one runs random executables found somewhere on the net.

These are not random executables, they are created by using the same method you are attempting to do.

Nothing wrong with the SGF (ASCII-only, no comments, small pro game). It was read correctly.
Sabaki is a random 69MB executable, full of libraries that were compiled on some system, with some version of the C library and dozens of other libraries. If my system was compiled with a different version of one of these libraries, crashes will happen. I expected a crash, but it was a bad crash, necessitating a reboot, since I lost mouse and keyboard.
It is bad to have a package unpack to a lot of junk in the current directory. Almost all packages, at least in a Linux environment, do the right thing, and unpack in a subdirectory. That makes it possible e.g. to have both foo-1.2.3 and foo-1.2.4.
If one has a system like Ubuntu then doing things behind the back of their package manager only leads to trouble, and an instable system. If Sabaki really fails to work with the latest that Ubuntu provides, then I must wait a few years and come back if/when the node version needed by Sabaki is provided by Ubuntu.
By the way - I suppose you are aware of the node vs nodejs name variation?

Sabaki is a random 69MB executable, full of libraries that were compiled on some system, with some version of the C library and dozens of other libraries. If my system was compiled with a different version of one of these libraries, crashes will happen.

Then you have to build Electron by yourself as well since the run script downloads prebuilt binaries provided by Electron. I'm actually surprised that the binaries you got by running npm run build:linux didn't crash your system, too.

If Sabaki really fails to work with the latest that Ubuntu provides [...]

Sabaki doesn't need node or npm to run; you only need them to build.

[...] then I must wait a few years and come back if/when the node version needed by Sabaki is provided by Ubuntu.

Ok, see you then! I'm closing this issue for now.


[TEVA-1784] Confirmation email for job application submit

Jira ticket URL
https://dfedigital.atlassian.net/browse/TEVA-1784
Changes in this PR:

Adds the email
Some light refactoring of mailers
Updates seeds (was a separate PR https://github.com/DFE-Digital/teaching-vacancies/pull/2997 so feel free to ignore the last commit in this PR - I forgot that it was branched off this one so when I merged it it just went into this PR.)

Screenshots:
A job application at a central office of a trust

A job application at multiple schools in a local authority

A job application at a single school in a trust

https://teaching-vacancies-review-pr-2994.london.cloudapps.digital/

Review app deployed to https://teaching-vacancies-review-pr-2994.london.cloudapps.digital

It also actually sends, if you tell it to on the review app:


fix: reset args.kwargs before running benchmark suites

This pr fixed keyError issue when running different datasets in all files from benchmark/suite.
Relavent issue: #67  bullet point 1
issue: args.kwargs kept values from old dataset.
fIx: reset args.kwargs before running dataset

@Char15Xu What is the use of args.kwargs? It feels like we need a bigger change for the args.kwargs design. It's mysterious why one needs to reset it.

Based on my understanding of the original code, it is used in libem/prepare/datasets to parse data from datasets.

@Char15Xu @daiwaid Instead of relying on the client code to reset the kwargs -- which is really an unknown unknown for them - we should https://github.com/abcsys/libem/blob/b16907cdd5334f915ef585cbf74fc86a2c1db3ff/benchmark/classic/abt_buy.py#L38 do a deep copy of the args here!

Alternate fix implemented in PR #73.


Multiple backends

Great tool and it works as described but I'd lie to be able to sync multiple kv's in my vault without having to run separate instances. We have our secret engines separated by environment and I'd love to sync all to a DR instance of vault.

Do you mean multiple sources or destinations?

I mean what you call backends, it defaults to secrets/
Would be great if it could be a list so you can sync eg
src:
…
Backends: [dev,test,prod]
To the equivalent in destination. Hope it makes sense.


gmid 2.0

I've mentioned before in some issue and in private conversations but never said clearly (outside of commit messages): the next release of gmid will be 2.0 and have some breaking changes.
The master branch is currently the work-in-progress for the future 2.0 so use it at your own risk.  The documentation is incomplete.  For something stable and documented, please use the latest 1.8.X release (currently 1.8.4) that will keep to receive updates until 2.0 is out.  Said that, if you want to help squashing out bugs you're encouraged to try the master.
My plan is to try fix all of the things that would require a breaking change in 2.0 to provide a stable interface again after.
The biggest change is an internal one, half of which is already been done: fixing privsep.  We had an "executor" process that was some sort of hack to do all the nice things we can't do in a sandbox.  The server process asked this "executor" to run CGI scripts, open network sockets for proxying and/or fastcgi.  I wanted to get rid of this because it's a way to escape the sandbox, and this has been done.  Now it's the server process that opens the network sockets and CGI script support has been removed (see d29a2ee2246e1b1b0c5222a823820e42422c894e, the alternative is to use FastCGI with for e.g. slowcgi-portable).  The downside is that we loose the sandbox for the server process outside of OpenBSD.
The other half of the privsep issue is to make the internal process handling better.  The configuration should be sent over imsg and the sub-processes spawned only once at startup.  Imsg handling should be fully asynchronous.
Running as uid 0 and chroot should also probably be made mandatory, or at least enabled by default.
Another invasive, but less than the previous, change to do is to allow binding to specific ip/ports per vhost, and possibly multiple times.  Each server block should have a listen on directive and the global port one should be removed.
The fastcgi support should be extended to allow setting and changing parameters more easily, and under the hood it would be nice to "batch" multiple fastcgi params instead of one-per-record.  FastCGI multiplexing is really nice but probably won't be done in time for 2.0.
If there are other things that would require a breaking change, feel free to open an issue so they can be discussed before 2.0.  There isn't a clearly defined deadline for it, but I'd like to get it done by the end of the year.
As always, patches are welcome! :)

There isn't a clearly defined deadline for it, but I'd like to get it done by the end of the year.

it didn't aged well, did it?
Anyway, I've resurrected the work and I'm happy with the privsep improvements.  Now we follow a fork+exec pattern, propagate the configuration to sub-processes via ipc and the imsg handling is fully asynchronous.
What remains in my todo list is: (for the time being)

a privsep crypto engine.  I need it.
listen on per virtual host.
improve logging (style, location, etc.)
make fastcgi easier to use / configure and more flexible.

The privsep crypto engine is now in (although only limited to OpenBSD until libretls gets an update...) and listen on too 🎉
The next step would be to improve fastcgi, then we could have a 2.0 release.

fastcgi was improved and i've also started to improve the logging.  What's currently missing is:

SCRIPT_PATH / PATH_INFO handling in fastcgi
fix the remaining XXX in the logging
fix titan(1) with query parts (it currently appends ;size=... at the end of the URL, not at the end of the path)
revisit the IRI parser for gg(1)

then we could have a 2.0.  Server-side titan support will have to wait 2.1.  A question remains regarding the logging: eventually the condensed logging style would also log the uploaded size via titan.  Should we stick to legacy as default for 2.0 and tell folks that condensed could be changed in a subsequent release?

titan(1) was fixed and I believe it's fine for the next release.  The IRI parser for gg(1) and titan(1) will be revisited post 2.0.  The logging style has been switched back to legacy and the new 'condensed` commented out in the manpage.  What's currently missing for 2.0 is:

SCRIPT_PATH / PATH_INFO handling for fastcgi
fix the XXX (certificate CN and bytes of the response) in the logging code

gmid 2.0 is here :)