source apero.bash.setup fails

❯ source apero.bash.setup
Traceback (most recent call last):
  File .../apero/tools/recipes/bin/apero_validate.py", line 101, in <module>
    ll = main()
  File ".../apero/tools/recipes/bin/apero_validate.py", line 64, in main
    recipe, params = core.setup(__NAME__, __INSTRUMENT__, fkwargs)
  File ".../apero/core/core/drs_startup.py", line 131, in setup
    pid, htime = _assign_pid()
  File ".../apero/core/core/drs_startup.py", line 1423, in _assign_pid
    unixtime, humantime, rval = unix_char_code()
  File ".../apero/core/core/drs_startup.py", line 1439, in unix_char_code
    time.sleep(rint)

TypeError: only integer scalar arrays can be converted to a scalar index
Changing unix_char_code() to

def unix_char_code():
    # we need a random seed
    np.random.seed(random.randint(1, 2**30))
    # generate a random number (in case time is too similar)
    #  -- happens a lot in multiprocessing
     rint = np.random.randint(1000, 9999, 1) / 1e7
    # wait a fraction of time (between 1us and 1ms)

    **time.sleep(float(rint))**
    # get the time now from astropy
    timenow = Time.now()
    # get unix and human time from astropy time now
    unixtime = timenow.unix * 1e7
    humantime = timenow.iso
    # generate random four characters to make sure pid is unique
    rval = ''.join(np.random.choice(list(CHARS), size=4))
    return unixtime, humantime, rval

fixed the issue.
Runing:

FedoraRemix@WSL2 on Windows 10 Pro machine (Clevo P775-DMG3, i7-7700K, 64GB RAM)
Python 3.8 on Anaconda

Hi @jorgehumberto  this has been corrected in our 0.7 branches quite a while ago (this will be python 3.8 compatible).
Note for the 0.6.131 and 0.6.132 version python 3.8 is not supported.
I assume you were using the master branch )v0.6.131) as this was also fixed in the developer branch (currently on v0.6.132) - I would suggest using the developer branch

OK, thank you, I'll move to the dev branch then!
Closing.


[MINOR] add toString for handshake messages

PR description
Before -
{"@timestamp":"2024-04-03T04:03:50,365","level":"TRACE","thread":"nioEventLoopGroup-3-10","class":"ECIESHandshaker","message":"First ECIES handshake message under INITIATOR role: org.hyperledger.besu.ethereum.p2p.rlpx.handshake.ecies.InitiatorHandshakeMessageV4@2a66bbb5","throwable":""}
After -
{"@timestamp":"2024-04-03T04:03:50,925","level":"TRACE","thread":"nioEventLoopGroup-3-1","class":"ECIESHandshaker","message":"Received responder's ECIES handshake message from node 0xb2aaeccb38b380e6663458bf7066f132...: ResponderHandshakeMessageV4{ephPublicKey=0xe8afcfe96360bb7e83a223d5b0b080a9b7157db5edfda2dfbadcb057c512dacd3718a538a64afa41e2e5fbcc929154bedd861619f72ca413ecabe8f8e0678bf6, nonce=0xb4235af56982f5f348bb762625da18a775a977053b0e4bfec9546e3b6abc9858}","throwable":""}
Fixed Issue(s)

Thanks for sending a pull request! Have you done the following?

[ ] Checked out our contribution guidelines?
[ ] Considered documentation and added the doc-change-required label to this PR if updates are required.
[ ] Considered the changelog and included an update if required.
[ ] For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

[ ] unit tests: ./gradlew build
[ ] acceptance tests: ./gradlew acceptanceTest
[ ] integration tests: ./gradlew integrationTest
[ ] reference tests: ./gradlew ethereum:referenceTests:referenceTests

I like the addition of the node address:
0xb2aaeccb38b380e6663458bf7066f132...
I'm unsure how useful this bit might be: ResponderHandshakeMessageV4{ephPublicKey=0xe8afcfe96360bb7e83a223d5b0b080a9b7157db5edfda2dfbadcb057c512dacd3718a538a64afa41e2e5fbcc929154bedd861619f72ca413ecabe8f8e0678bf6, nonce=0xb4235af56982f5f348bb762625da18a775a977053b0e4bfec9546e3b6abc9858


Update runners

Small PR to replace the Ubuntu 16.04 runner by Ubuntu 22.04. The 16.04 runner was removed a year ago (https://github.blog/changelog/2021-04-29-github-actions-ubuntu-16-04-lts-virtual-environment-will-be-removed-on-september-20-2021/)
Ubuntu 18.04 is deprecated but not yet removed, so I don't know if you want to keep it (https://github.blog/changelog/2022-08-09-github-actions-the-ubuntu-18-04-actions-runner-image-is-being-deprecated-and-will-be-removed-by-12-1-22/)

Darn, missed the approval by 14 seconds ;-)


Update readme.md

extract documentation for gradle from readme.md and put it in the wiki

Hi @serious6, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

:+1:


DRFT-64 - add pull request template for secure coding checklist

thank you, @eherget can you move this to a .github directory as this is specific to github and won't change much.

@sthirugn This has been done.


Texts Alignment and Clickable items pointer to be changed from cursor to pointer

@sanika391 I want to work on these enhancements without disturbing any pre alignments, please assign me this task to let me complete. Kindly also label this as Gssoc'24.
Thanks

@sanika391 assign this to me i have 2+ years of experience in flutter i am GSSOC'24 contributor

Hello @sanika391 can you please assign me this isssue. I wanted to work on issue.

Have you send an issue regarding it??
On Sun, May 19, 2024, 9:32 PM Dakshesh Gupta @.***>
wrote:

Hello @sanika391 https://github.com/sanika391 can you please assign me
this isssue. I wanted to work on issue.
—
Reply to this email directly, view it on GitHub
https://github.com/sanika391/SpoonShare/issues/5#issuecomment-2119285912,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A34TW24WB3HORHKWEB6XNUTZDDEJNAVCNFSM6AAAAABHS55F46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGI4DKOJRGI
.
You are receiving this because you were mentioned.Message ID:
@.***>


2.0.0 users.list not working

Calling users.list results in — nada. No response or error is printed to the console and I don't seem to have any problems with other methods using the client.
For example, here:
web.team.info(function teamInfoCb(err, channels) {
    if (err) return console.log('Error:', err);
    console.log('Team Info:', channels);
});

web.users.list(function userListCb(err, response) {
    if (err) return console.log('Error:', err);
    console.log('List', response);
})

...the team info is printed but not the users.list info.

My bad. I was not passing an opts parameter (empty in this case):
web.users.list({}, function userListCb(err, response) {
    if (err) return console.log('Error:', err);
    console.log('List', response);
})

I believe that call actually has a signature like:
/**
 * Lists all users in a Slack team.
 * @see {@link https://api.slack.com/methods/users.list|users.list}
 *
 * @param {?} optPresence Whether to include presence data in the output
 * @param {function} optCb Optional callback, if not using promises.
 */
UsersFacet.prototype.list = function list(optPresence, optCb) {

... so would take a boolean rather than an opts object there.

Given that the first arg is an opt, it should check the # of args passed, so I'm going to reopen this and add some logic to do that.

https://github.com/slackhq/node-slack-client/commit/2a13901b5e7d94bc154d05d89efd5a4d8cbe0d6f fixes this properly


Make README just point to wiki

From @mabelzhang
Is the top-level README intentionally vague? The Wiki has a wealth of information, but it’s not discoverable. I propose putting a sentence in the top-level README that links to the wiki. #126

@mabelzhang Once we get the v3.1 reorganization done - please make a tiny PR to make this so.

Closing on #131


fix: Update readme -- we need go 1.17

Background
Update README and boilerplate go.mod to set version to go 1.17 per the pulumi dependency:
❯ go test -v ./...
# github.com/pulumi/pulumi/pkg/v3/codegen/schema
../../../go/pkg/mod/github.com/pulumi/pulumi/pkg/v3@v3.23.2/codegen/schema/loader.go:120:30: not enough arguments in call to pkgPlugin.Install
        have (*os.File)
        want (io.ReadCloser, bool)

Conflated a different issue with the go version being the culprit
/close


Is this work on live AWS server ( Linux )

Hi,
I have a new issue. I have an aws linux server. I referred the below link
http://elementalselenium.com/tips/38-headless
which option is suitable for my server.
share the clear steps for this issue.
Kindly do the needful

There isn't a clear-cut suitable option, as it depends on how you setup your scripts and infrastructure
If you are running a process manager, like PM2, you'll probably want to start your xvfb and keep it running for all your apps.
pm2 start Xvfb -- :99
export DISPLAY=:99
pm2 start /path/to/my/app --update-env

But if you're running an one-time script, you could use
xvfb-run node /path/to/my/script

It's up to you how to setup your environment.

xvfb-run node /path/to/my/script
This one working fine.
pm2 start Xvfb -- :99
export DISPLAY=:99
pm2 start /path/to/my/app --update-env

we need continuous running process
It's not working. It creates two pm2 instance.
kindly do a needful.

What is the meaning for --:99 in below statements
pm2 start Xvfb -- :99
What is the meaning for this statement
export DISPLAY=:99

What is the meaning for --:99 in below statements
pm2 start Xvfb -- :99

in PM2, everything after -- is an argument that will be passed to the child process
pm2 start Xvfb -- :99 will run Xvfb :99
The :99 argument tells Xvfb to create a virtual display on screen server 99
Run man Xvfb for more info

export DISPLAY=:99

This tells the programs you'll be running next that they should use the screen server on port :99

pm2 start /path/to/my/app --update-env
In this, bold statement - app path or script path ?

Path to your server.
Since i've noticed that your server startup script was already running, you may want to pm2 restart index --update-env

Ok Thank you. It's working.


genann_run() always return constant value

trained a very simple stock price predictor
the input and the outputs that go into the genann_train() seem correct,
as soon as the training is completed, a call to genann_run with any set of inputs will always produce the the same, constant value.
const auto layers = 40;
const auto neurons = 40;
const auto N = 100;
genann* ann = genann_init(5, layers, neurons, 1);

...

for (auto& p: inputs) {
    const double o = outputs[i_outputs] / maxValue[targetFilename];
    genann_train(ann, p.second.data(), &o, 0.01);
    i_outputs++;
}

...

for (... test inputs ...) {
   const auto prediction_raw = *genann_run(ann, input);
   LOG(INFO) << "prediction_raw: " << prediction_raw;
}

the prediction_raw value will be the same, regardless of the input.

You need to loop through your training data many, many times. Not just once.
Each time, you should randomize the order that you train on your inputs.
After each training, you should call genann_run() and subtract that output from your expected output. Square this difference so that it's always positive, and then add it to a running sum for that training epoch. That's your error.
You should monitor the error for each loop through all the training data. It should start high, and then go down as you train.
You should also try 1 layer and 10 neurons to start. Get that working, then increase it and see if you get better results. 40 x 40 is huge, and you would probably need deep learning techniques for that.
Also, are you sure your outputs are correlated with your inputs? A neural network isn't psychic, it can only calculate something that is possible to calculate.
Anyway, there's a ton I left out, but that's a starting point.
Good luck, and let me know what you find out.

i didn't try randomizing the order of the training set for each epoh yet,
or calculating the err, as i just let it run for many epohs for about an
hour or so
the result is the same, at the end of the training session, the network
output is always the same for any input.
On Mon, Jul 9, 2018 at 7:29 PM Lewis Van Winkle<EMAIL_ADDRESS>wrote:

You need to loop through your training data many, many times. Not just
once.
Each time, you should randomize the order that you train on your inputs.
After each training, you should call genann_run() and subtract that
output from your expected output. Square this difference so that it's
always positive, and then add it to a running sum for that training epoch.
That's your error.
You should monitor the error for each loop through all the training data.
It should start high, and then go down as you train.
You should also try 1 layer and 10 neurons to start. Get that working,
then increase it and see if you get better results. 40 x 40 is huge, and
you would probably need deep learning techniques for that.
Also, are you sure your outputs are correlated with your inputs? A neural
network isn't psychic, it can only calculate something that is possible to
calculate.
Anyway, there's a ton I left out, but that's a starting point.
Good luck, and let me know what you find out.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/codeplea/genann/issues/23#issuecomment-403679523, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AECFGYresu7xOvOstnawc2GBjxtNa78dks5uFBGfgaJpZM4VIW91
.

--
Best Regards,
H

If you take my earlier advice, I'm sure you'll have better luck.
You can post the complete example with training data if you need more help.


Slices of no copy Data bridged to and back incorrectly account for the start index

when bridging back from objc the start index was not correctly re-constructed into the slices of no copy datas. This adds functionality for that.
resolves rdar://130106808

@swift-ci please test


add missing include in uvwasi.c

uvwasi.c uses functions from string.h without directly or indirectly including the header file.

Landed in https://github.com/cjihrig/uvwasi/commit/154a714e1ff676a535c97f3a483fbd1ea2ed7d8c. Thanks!


Allow simple string substitutions

I’d like to write a shortened url in docstrings:
[ClassName][:ss:ClassName]
versus how I’ll do it now:
[ClassName][pysimplesql.pysimplesql.ClassName]
Of course, I can currently just hack this in, but I want to know if you like the idea for the project.
Perhaps an option could be added: “replace”, that accepts a key/value pairs, like:
plugins:
    - autorefs:
       replace :
            “:ss:”:”pysimplesql.pysimplesql.”

This would be used in on_post_page:
for k, v in c.replace.items():
    output = output.replace(k, v)

Or maybe I’m overlooking an easier way of doing this? Thanks for mkdocstrings and crew!

I’m going to close this for now, reading up on some previous issues/prs


Use module github.com/prometheus/prometheus/v2 in go.mod

In order to follow golang conventions for versions you need to update the module in go.mod to be v2.
Try:
go get<EMAIL_ADDRESS>
go: finding github.com/prometheus/prometheus v2.19.3
go: finding github.com/prometheus/prometheus v2.19.3
go get<EMAIL_ADDRESS><EMAIL_ADDRESS>invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v2

Prometheus is NOT following golang convention.
Adding v2 would mistake people into believing that we follow Go conventions. This is not the case.
You can go get specific commit id's or tag ids:
git rev-list -n 1 v2.19.3
657ba532e42f1db8d7c77bf802378643da0d3118
go get github.com/prometheus/prometheus@657ba532e42f1db8d7c77bf802378643da0d3118

Duplicate of #6048

@roidelapluie mistake people into believing that we follow Go conventions If you are using go mod, you should be following go conventions. This makes it impossible for anyone else to use go mod to pull in prometheus. We followed the workaround, and it just does not work.

Hi Benjamin,
We are happy to help you on the prometheus-developers mailing list about this matter, if you can provide us with more details there about what does not work.

Use go (I believe) 1.14.x. Try and import promethues. See that it gives the following error<EMAIL_ADDRESS>invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v2, even when imported using the former method.

Yes, you need to
go get github.com/prometheus/prometheus@657ba532e42f1db8d7c77bf802378643da0d3118

yeah, that doesn't work

I am on go 1.15. It works for me:
~/testgoprom $ go mod init github.com/roidelapluie/testgoprom
go: creating new go.mod: module github.com/roidelapluie/testgoprom
~/testgoprom $ go get github.com/prometheus/prometheus@657ba532e42f1db8d7c77bf802378643da0d3118
go: downloading github.com/prometheus/prometheus v1.8.2-0.20200724121523-657ba532e42f
go: github.com/prometheus/prometheus 657ba532e42f1db8d7c77bf802378643da0d3118 => v1.8.2-0.20200724121523-657ba532e42f
~/testgoprom $ go version
go version go1.15 linux/amd64

Note that you can ignore the v1.8.2, that does not reflect the reality.

Hmm, I'm majorly confused. I was in a state where I was getting the error, now I'm suddenly not? I still have some major concerns about the workaround required to be functional with go mod(especially as it's been the very strong stance of go mod that users of go mod should use major versioning in their modules, and as they've reduced workarounds to do so, like removing +incompatible to do so. https://blog.golang.org/v2-go-modules. We'll keep investigating.

go mod can be a frustrating mystery sometimes :/


fix: change typo on config file (minfy to minify) and implement custom prefix for assets route

Issue #2

I am facing a problem in this package, the problem is after minifying files the style is not implemented on any tag
include file link


[dev-tool] stop rolling up types for ESM

For packages that have been migrated to ESM, Rolled up dts files are no longer used but they are still packaged because our files field include an entry of dist/.  Since they are not used anymore, this PR stops generating them, instead of more complicated approach of excluding them from npm pack.

API change check
API changes are not detected in this pull request.

/check-enforcer override


header name: add from_static method

Implements: #168 : HeaderName::from_static
Converts a static string to a HTTP header name.
Function panics on an invalid headers, and requires lowercase characters, as so the static string will have the same format as the internal format.
Function should also be zero copy, beyond what is done in parse_hdr, with the static slice being used for the ByteStr in custom headers.

No worries, and thanks for all your work on Hyperium!


compute/node: add zone config

This change allows the "zone" resource to be configured for nodes, which allows a cluster of nodes to be split up into groups, which may be requested by tasks. This is useful as a crude way of partitioning a cluster, and/or for designating some nodes which have different config, such as a "debug" zone which keeps more logs/working directories.
I had some hacky version of this deployed previously, and it was very useful, but I've lost it.
To do:

[x] tests

The remaining problem here is that Elasticsearch is a terrible database for something which requires consistency, such as the scheduler. Duplicate tasks are getting assigned to nodes (#478) which is breaking the test.
I think I'm going to recommend we remove the scheduler backend from the Elasticsearch code.


Powertoys Run won't Open

Microsoft PowerToys version
0.75.1
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
PowerToys Run
Steps to reproduce
Windows 11
When I try to open powertoys Run, it doesn't do anything. I tried changing the shortcut, opening it directly from the .exe, opening it as administrator but nothing works.
I watched the task manager as i open it and it opens for a split second and then closes (but you dont see it on the screen, only on the task manager).
Here is the events visor log (translated):
Record name:Application
Source: Application Error
Date: 2/11/2023 14:40:26 PM
Event ID:1000
Task category:Application crash events
Level: Error
Keywords:
User: ***
Team: ***
Description:
Application name with errors: PowerToys.PowerLauncher.exe, version: <IP_ADDRESS>, timestamp: 0x653067fb
Buggy module name: KERNELBASE.dll, version: 10.0.22621.2428, timestamp: 0x9223bda8
Exception code: 0xe0434352
Error offset: 0x00000000000000064ffc
Process identifier with errors: 0x0x3B34
Application start time with errors: 0x0x1DA0DB3A7562422
Path of the application with errors: C:\Program Files\PowerToys.PowerLauncher.exe
Path of the failed module: C:\WINDOWS\System32\KERNELBASE.dll
Report Identifier: 097a59b9-a7d9-476f-9aa2-b4bca459476d
Full name of the package with errors:
Relative application identifier of the package with errors:
Event XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2023-11-02T17:40:26.6453064Z" />
    <EventRecordID>37332</EventRecordID>
    <Correlation />
    <Execution ProcessID="18820" ThreadID="11088" />
    <Channel>Application</Channel>
    <Computer>***</Computer>
    <Security UserID="S-1-5-21-944201711-1061701843-3258512876-1001" />
  </System>
  <EventData>
    <Data Name="AppName">PowerToys.PowerLauncher.exe</Data>
    <Data Name="AppVersion"><IP_ADDRESS></Data>
    <Data Name="AppTimeStamp">653067fb</Data>
    <Data Name="ModuleName">KERNELBASE.dll</Data>
    <Data Name="ModuleVersion">10.0.22621.2428</Data>
    <Data Name="ModuleTimeStamp">9223bda8</Data>
    <Data Name="ExceptionCode">e0434352</Data>
    <Data Name="FaultingOffset">0000000000064ffc</Data>
    <Data Name="ProcessId">0x3b34</Data>
    <Data Name="ProcessCreationTime">0x1da0db3a7562422</Data>
    <Data Name="AppPath">C:\Program Files\PowerToys.PowerLauncher.exe</Data>
    <Data Name="ModulePath">C:\WINDOWSystem32KERNELBASE.dll</Data>
    <Data Name="IntegratorReportId">097a59b9-a7d9-476f-9aa2-b4bca459476d</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
  </EventData>
</Event>

✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

Can you post a bug report?
Can you also check if there is a dump in the folder %LOCALAPPDATA%\CrashDumps named PowerToys.PowerLauncher.exe...dmp? It could also help.
/bugreport

The file is bigger than 25MB, I uploaded the file here [https://go.wetransfer.com/t-5F6mlZ93j7](PowerToys Report)

The error is the following and it's a duplicate of #14840
System.UnauthorizedAccessException: Access to the path 'C:\Users\brank\AppData\Local\Microsoft\PowerToys\PowerToys Run\Settings\ImageCache_version.txt' is denied.
   Source: System.Private.CoreLib
   TargetAssembly: System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e
   TargetModule: System.Private.CoreLib.dll
   TargetSite: Microsoft.Win32.SafeHandles.SafeFileHandle CreateFile(System.String, System.IO.FileMode, System.IO.FileAccess, System.IO.FileShare, System.IO.FileOptions)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode)
   at System.IO.File.OpenHandle(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
   at System.IO.File.WriteToFile(String path, FileMode mode, String contents, Encoding encoding)
   at System.IO.Abstractions.FileWrapper.WriteAllText(String path, String contents)
   at Wox.Infrastructure.Storage.StoragePowerToysVersionInfo.Close()
   at Wox.Infrastructure.Storage.JsonStorage`1.Save()
   at Wox.Infrastructure.Storage.JsonStorage`1.LoadDefault()
   at Wox.Infrastructure.Storage.JsonStorage`1.Load()
   at Wox.Infrastructure.Image.ImageCache..ctor()
   at Wox.Infrastructure.Image.ImageLoader..cctor()

Does this file exist? C:\Users\brank\AppData\Local\Microsoft\PowerToys\PowerToys Run\Settings\ImageCache_version.txt
If yes, is your user able to delete it?
Since it's a cache it can be safety deleted. It will be re-created on next PowerToys startup.
/needinfo

Now this appears at start:
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.22621.0
IntPtr Length: 8
x64: True
Date: 2/11/2023 16:41:04
Exception:
System.UnauthorizedAccessException: Access to the path 'C:\Users\brank\AppData\Local\Microsoft\PowerToys\PowerToys Run\Settings\PowerToysRunSettings_version.txt' is denied.
   at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode)
   at System.IO.File.OpenHandle(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
   at System.IO.File.WriteToFile(String path, FileMode mode, String contents, Encoding encoding)
   at System.IO.Abstractions.FileWrapper.WriteAllText(String path, String contents)
   at Wox.Infrastructure.Storage.StoragePowerToysVersionInfo.Close()
   at Wox.Infrastructure.Storage.JsonStorage`1.Save()
   at Wox.Infrastructure.Storage.JsonStorage`1.LoadDefault()
   at Wox.Infrastructure.Storage.JsonStorage`1.Load()
   at PowerLauncher.ViewModel.SettingWindowViewModel..ctor()
   at PowerLauncher.App.<>c__DisplayClass19_0.<OnStartup>b__0()
   at Wox.Infrastructure.Stopwatch.Normal(String message, Action action)
   at PowerLauncher.App.OnStartup(Object sender, StartupEventArgs e)
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Uuuuh.. Same error but another file.
Can you run this command on a PowerShell and post the output?
Get-ChildItem "$env:LOCALAPPDATA\Microsoft\PowerToys\PowerToys Run\Settings\"

Directorio: C:\Users\brank\AppData\Local\Microsoft\PowerToys\PowerToys Run\Settings

Mode                 LastWriteTime         Length Name

-a----         2/11/2023     16:40              2 ImageCache.json
-a----         2/11/2023     16:40              7 ImageCache_version.txt
-a----         2/11/2023     16:41           1248 PowerToysRunSettings.json

I was hoping for some read-only files.
I would try to delete every file in C:\Users\brank\AppData\Local\Microsoft\PowerToys\PowerToys Run\Settings but I think you'll hit the error on another file.

Closing this as duplicate. /dup #https://github.com/microsoft/PowerToys/issues/14840

Deleting every file in that directory worked!
Thank you!


Get specific message by offset from kafka topic

Hi all
is there a way to get a specific message by an offset?

You can manually seek the consumer to an offset and start polling from there.

and then i receive all the messages from the offset to the end...

pause is not enough.
i need to disconnect, and reconnect the next time.

That'll work too. Offsets are stored in Kafka consumer groups. You won't lose positioning

i know, but a reconnection takes ~3 seconds.
i want an open, connected consumer that will be ready to go and read a single message by an offset.


Swift-NIO async port

To make multiple compilation jobs easier and avoid tying up a thread while the compiler works.
Goodpath working.

Codecov Report

Merging #2 (0aa4d74) into main (a8ede60) will decrease coverage by 22.44%.
The diff coverage is 79.03%.

@@             Coverage Diff             @@
##             main       #2       +/-   ##
===========================================
- Coverage   98.26%   75.82%   -22.45%
===========================================
  Files          19       19
  Lines        1267     1249       -18
===========================================
- Hits         1245      947      -298
- Misses         22      302      +280

Impacted Files
Coverage Δ

Sources/EmbeddedSass/Compiler.swift
75.35% <76.43%> (-20.38%)
:arrow_down:

Sources/EmbeddedSass/Exec.swift
51.08% <81.25%> (-44.79%)
:arrow_down:

Sources/EmbeddedSass/BinaryProtocol.swift
96.00% <96.00%> (+3.89%)
:arrow_up:

Sources/EmbeddedSass/Timer.swift
0.00% <0.00%> (-100.00%)
:arrow_down:

Sources/Sass/ImporterTypes.swift
0.00% <0.00%> (-100.00%)
:arrow_down:

Sources/EmbeddedSass/Errors.swift
0.00% <0.00%> (-100.00%)
:arrow_down:

Sources/EmbeddedSass/ProtobufConversion.swift
29.12% <0.00%> (-70.39%)
:arrow_down:

Sources/Sass/CompilerTypes.swift
77.35% <0.00%> (-22.65%)
:arrow_down:

Sources/Sass/Constants.swift
83.33% <0.00%> (-16.67%)
:arrow_down:

... and 8 more

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 a8ede60...0aa4d74. Read the comment docs.


Add item conditions

Doesn't look like there's any way to track item condition. It'd be great if this were both added and automatically set the appropriate conditions for use of the item (e.g. adding setback dice.)

My concerns with this:

If we make a new item type called condition, so we can effectively track setback dice we would need to rely on the item to item associations, which I would rather avoid.
If we make it a static field for items, then we have to either hardcode the setback dice calculation, or manage that attribute on the item itself.

This along with the weapon/armor modifications need additional planning before implementing so that we are consistent.  I'd lean toward 2 but I'd like to find a solution to both this and mods that use the same process and code.

If this isn't easily solvable it may be worth implementing some form of tracking that doesn't auto-apply anything and then when you have time you can extend it.

One of the few advantages I would see of Option 1 is easily adding new item condition types, but in my last few years of GMing, I personally have never needed the flexibility of adding new 'types' of conditions. The core rules have been plenty sufficient in my games.
Since it's such a core piece of the game that hasn't changed over years and many books, option 2 - managing on the item itself - seems plenty sufficient, flexible, and low risk in my uses.

If this one is to go into v1.2 I think it needs to be in the form of option 2, with a static String field on items for the condition, and handle any relevant modifiers manually on the item modifiers tab.
This makes the best use of our existing functionality while also avoiding hardcoding any unnecessary proprietary rules into the system.

+1

Added to dev branch, will be in 1.2 release.


default size for the fit function behaves unintuitively

Is your feature request related to a problem? Please describe.
If you work on an app that uses multiple openlayers map, the default size value is very unintuitive. The actual size default value is the size of the first map in the dom. One would expect that the size is from the map that uses the view. I know that the view does not have a reference to the map.
Describe the solution you'd like
I would suggest to move the size out of the options object and make it a parameter (view.fit(extent, size, options) . This will remind the developer to think about it.
This would be a breaking change.
Also I would consider removing the default. In every case I encountered while working with openlayers so far, the map was known at the point where .fit was called.

Maybe the documentation needs an update. Since quite a while, fit does not use the size of the first map in the dom, but the actual size of the map the view is associated with. The size parameter is only necessary for a view that has not been associated with a map yet.
Maybe you want to create a pull request that fixes the documentation?

Ok, then it is bugged. I will look into that.

If setTarget is called from a react mount callback the call of getComputedSize returns a CSSStyleDeclaration that does not contain width and height.
That is no problem in updateSize because it uses the offsetWidth and calculates the actual size from there. But in updateViewportSize_ the problem occurs.
This leads to the question: Why is updateViewportSize_ in Map.js a different logic from updateSize, anyways? I don't see any reason for that.
I would suggest passing the size as a parameter to updateViewportSize_.

the actual size of the map the view is associated with

A view can be associated with multiple maps.  In this example https://codesandbox.io/s/side-by-side-forked-qwqf8v?file=/main.js both calculateExtent() and fit() are defaulting to the size of the second map - if map sizes can be independently updated it could be either map.

Ok, according to implementation then the size that would be used, would be the map where one of the following events occured last:

setSize
resize event
setView
setTarget

I would then write that the size can not be determined correctly if more than one map is used with one view. Is this features used often? I think it might be used for overview maps, but in any application I work with, we actually use a different view.

See the linked PR for a formulation.


TypeError: Cannot read properties of undefined (reading 'dispatch')

Describe the bug
Getting TypeError: Cannot read properties of undefined (reading 'dispatch') issue when running mock api test in Nuxt using testing library, msw
Steps to reproduce the bug
My code:
import {render} from '@testing-library/vue'
import '@testing-library/jest-dom'
import {rest} from 'msw'
import {setupServer} from 'msw/node'
import ComponentWithRequest from './ComponentWithRequest'
import VuexORMAxios from '@vuex-orm/plugin-axios'
import VuexORM from '@vuex-orm/core'
import axios from 'axios'

VuexORM.use(VuexORMAxios, {axios})

const server = setupServer(
  rest.get('/brands', (req, res, ctx) => {
    return res(ctx.json({data: []}))
  }),
)

beforeAll(() => server.listen())
afterEach(() => server.resetHandlers())
afterAll(() => server.close())

test('Brands should render properly', async () => {
  const {getByText} = render(ComponentWithRequest)
})

Error:
 TypeError: Cannot read properties of undefined (reading 'dispatch')
        at Function.Object.<anonymous>.Model.dispatch (/home/user/node_modules/@vuex-orm/core/dist/vuex-orm.cjs.js:2817:28)
        at Function.Object.<anonymous>.Model.insertOrUpdate (/home/user/node_modules/@vuex-orm/core/dist/vuex-orm.cjs.js:2901:21)
        at Response.<anonymous> (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:110:64)
        at step (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:61:23)
        at Object.next (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:42:53)
        at /home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:35:71
        at new Promise (<anonymous>)
        at __awaiter (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:31:12)
        at Response.Object.<anonymous>.Response.save (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:88:16)
        at Request.<anonymous> (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:323:55)
        at step (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:61:23)
        at Object.next (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:42:53)
        at /home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:35:71
        at new Promise (<anonymous>)
        at __awaiter (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:31:12)
        at Request.Object.<anonymous>.Request.createResponse (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:309:16)
        at Request.<anonymous> (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:292:52)
        at step (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:61:23)
        at Object.next (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:42:53)
        at fulfilled (/home/user/node_modules/@vuex-orm/plugin-axios/dist/vuex-orm-axios.cjs.js:32:58)
        at processTicksAndRejections (node:internal/process/task_queues:96:5)

Expected behaviour
Should pass the test
Versions

Vuex ORM: 0.36.4
Nuxt: 2.15.7
msw: 0.43.0
testing-library/vue: 5.8.3

+1


Introductory page updated

Moved page to correct place (was in the files structure)
Updated page with new content from wiki.

Reviewed.


Director 2.5 doesn't allow Name tags

When the instance template specifies a Name tag, Director 2.5 appends without checking if the name was already specified.
* │oudera.launchpad.bootstrap.AllocateInstances$AllocateAndWaitForInstancesToRun - c.c.director.aws.ec2.EC2Provider: Exception while trying to allocate instance.                                         │
* │java.util.concurrent.ExecutionException: com.cloudera.director.aws.shaded.com.amazonaws.services.ec2.model.AmazonEC2Exception: Duplicate tag key 'Name' specified. (Service: AmazonEC2; Status Code: 40│..
..│0; Error Code: InvalidParameterValue; Request ID: cde4ca05-8ddc-4b79-92f8-11cc50850d37)                                                                                │
* │Caused by: com.cloudera.director.aws.shaded.com.amazonaws.services.ec2.model.AmazonEC2Exception: Duplicate tag key 'Name' specified. (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParamete│
* │rValue; Request ID: cde4ca05-8ddc-4b79-92f8-11cc50850d37)

Related code https://github.com/cloudera/director-aws-plugin/blob/8f21c1623d5675178024ba7124bb719bb560f057/provider/src/main/java/com/cloudera/director/aws/AbstractAWSTagHelper.java#L120-L122

Letting you know we're aware of this bug and are working it internally. We've utilized AWS's new tag-on-create feature for on-demand instances, but it seems that this is less permissive about duplicate tags than our previous mechanism. Previously it seems that user supplied tags would win out vs. the AWS plugin's internal name tag, but the new command errors out.
We did predict that this could be an issue, and thus the AWS plugin has a mechanism to allow renaming of our internal tags using CustomTagMappings. However, looks like we've got a bug in our CustomTagMappings code (stemming from the same class) which renames user supplied tags as well, so it's not currently available as a fix. I'll let you know when we've fixed this!

Thanks!

Hi @vinceprignano, this has been corrected with the release of Director 2.5.1. CustomTagMappings has been corrected in 2.5.1, so you should be able to work around this now: http://docs.mtv.cloudera.com/builds/docs-director-master-d4p/latest/topics/director_aws_custom_tag_names.html
Please give that a try and let me know if that works for you. If so I'll close the issue. Thanks!

We've utilized AWS's new tag-on-create feature for on-demand instances, but it seems that this is less permissive about duplicate tags than our previous mechanism.

The tag-on-create feature isn't available in all regions, did the fix happen to take that into account and perhaps revert back to the old way?

@sdavids13 Unfortunately those regions -- AWS China and GovCloud, at least according to this -- are not currently supported by Director 2.5 (see the KI here). Director 2.4.1 should still work just as well, and additionally will not have this particular issue as described, e.g. you can supply your own Name tags.
You could potentially compile the older version of the plugin to 2.5.1 if you want to take advantage of new features in Director 2.5.1 as well, though this isn't something that we test for.

@meowfaceman It seems that the issue still remains though. Our template specifies a custom name like
tags {
    Name: "zookeeper"${?suffix}
    environment: "production"
}

It seems that the current plugin doesn't check if the Name tag is already specified, therefore it may cause issues with duplicate values.

@vinceprignano This is after configuring the AWS plugin for customTagMappings as per http://docs.mtv.cloudera.com/builds/docs-director-master-d4p/latest/topics/director_aws_custom_tag_names.html? You should be able to tell Director not to use the Name field to make room for the custom Name field that you want to provide.

I don't have access to that link. Is the public one this https://www.cloudera.com/documentation/director/latest/topics/director_aws_custom_tag_names.html? I'm not sure how to tell Director not to use the Name field from those docs.

Oops, thank you, my bad. That's the correct link. When you install Director, there should be a /var/lib/cloudera-director-plugins/aws-provider-1.4.3/etc/aws-plugin.conf. If you add in a customTagMappings blurb to that file as specified in teh docs, it will rename what tag Director uses. So, for example:
customTagMappings {
    Name: some-other-tag
}

Instead of using the Name tag, it will use some-other-tag instead, allowing you to use the Name tag.

Oh I see! Thanks :)

@meowfaceman I just tried to apply the proposed fix. Although that didn't work as expected. It seem that even if I rename the Name tag, Director uses the same Key as tag. This seems to be happening here https://github.com/cloudera/director-aws-plugin/blob/master/provider/src/main/java/com/cloudera/director/aws/AbstractAWSTagHelper.java#L120-L122 where the call to https://github.com/cloudera/director-aws-plugin/blob/master/provider/src/main/java/com/cloudera/director/aws/Tags.java#L53 returns still Name

@vinceprignano The code replaces the "Name" with the CustomTagMapping in the createTag method. see https://github.com/cloudera/director-aws-plugin/blob/master/provider/src/main/java/com/cloudera/director/aws/AbstractAWSTagHelper.java#L76
Can you verify that you are using the aws plugin version 1.4.3, shipped with Cloudera Director 2.5.1?
Can you share your aws-plugin.conf file?

The version seems correct.
[ec2-user@ip-XXX5 ~]$ cat /var/lib/cloudera-director-plugins/aws-provider-1.4.3/etc/aws-plugin.conf
customTagMappings {
    Name: Director-Name
}
awsFilters {
    "com.cloudera.director.aws.ec2.EC2Provider" {
        template {
            image {
                ownerId {
                    blacklist {
                        "137112412989": "Amazon Linux",
                        "379101102735": Debian,
                        "125523088429": Fedora,
                        "902460189751": "Dowd and Associates Pygoscelis-Papua, Gentoo",
                        "341857463381": Gentoo,
                        "056126556840": "SUSE Studio, OpenSUSE",
                        "013907871322": "Amazon, SUSE Linux",
                        "099720109477": "Canonical, Ubuntu"
                    }
                },
                platform {
                    blacklist {
                        "amazon linux": "Amazon Linux",
                        debian: Debian,
                        fedora: Fedora,
                        gentoo: Gentoo,
                        opensuse: OpenSUSE,
                        "suse linux": "SUSE Linux",
                        ubuntu: Ubuntu,
                        windows: Windows
                    }
                },
                spotOwnerId {
                    blacklist {
                        "309956199498": RedHat
                    }
                },
                spotPlatform {
                    blacklist {
                        "red hat": "Red Hat"
                    }
                }
            }
        }
    }
}

This is the patch I applied after the same error happened.
From 1c10839437b66aafd76d28693632371d75bf8c46 Mon Sep 17 00:00:00 2001
From: Vincenzo Prignano<EMAIL_ADDRESS>Date: Mon, 25 Sep 2017 16:31:21 -0700
Subject: [PATCH] remove logic to append naming tags

---
 provider/src/main/java/com/cloudera/director/aws/AbstractAWSTagHelper.java | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/provider/src/main/java/com/cloudera/director/aws/AbstractAWSTagHelper.java b/provider/src/main/java/com/cloudera/director/aws/AbstractAWSTagHelper.java
index e184ecb..4072c31 100644
--- a/provider/src/main/java/com/cloudera/director/aws/AbstractAWSTagHelper.java
+++ b/provider/src/main/java/com/cloudera/director/aws/AbstractAWSTagHelper.java
@@ -117,9 +117,6 @@ public abstract class AbstractAWSTagHelper<T> {
   public List<T> getInstanceTags(InstanceTemplate template, String virtualInstanceId,
       List<T> userDefinedTags) {
     List<T> tags = Lists.newArrayList(
-        createTag(
-            Tags.ResourceTags.RESOURCE_NAME.getTagKey(),
-            String.format("%s-%s", template.getInstanceNamePrefix(), virtualInstanceId)),
         createClouderaDirectorIdTag(virtualInstanceId),
         createClouderaDirectorTemplateNameTag(template.getName())
     );
--
libgit2 0.26.0

@vinceprignano I had tried to send you a private message a while ago but had not received a response. I tried changing the Name through the customTagMappings and it worked for me. We'd need some more information about your setup and some log files to figure out why it's not working for you.

Upgraded to 2.6 and it seems to work fine now :)


Fix issues with building from source

This remove warning which prevent to perform build of MSI, See #891

@mousetraps Can you please take a look at this one.

This change has a good chance of breaking installations of NTVS on machines that do not have the VS SDK installed because required interop types are no longer being embedded. Instead, I believe the proper and less risky fix is to embed interop types on the Microsoft.VisualStudio.CommandBars reference instead. Could you try this and see how it goes?
Additionally, I can't reproduce this behavior at all. Could you specify some more details about your machine configuration? VS version / update #, etc? Which VS command prompt are you using? And presumably you're building from master?

@mousetraps

I build from master.
I have installed VS2013, VS2015 and VS15 Preview.
I use Git Shell form GitHub for Windows (which is basically Powershell + some adjustments)

I have to make MSbuild from VS2015 to path, in order to make a build.
If I understand correctly somehow references from VSN15 (Next) picked up instead of VS2015.
I run build like that:
msbuild NodejsTools.sln /p:Configuration=Release /p:VsTarget=14.0 /p:VisualStudioVersion=14.0
What I notice is just now is that in each project envdte used from VS15 folder, not VS2015.
In the project reference properties
Path = C:\Program Files (x86)\Microsoft Visual Studio 15.0\Common7\IDE\PublicAssemblies\envdte.dll
Instead of
Path = C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PublicAssemblies\envdte.dll
That's I see in MSBuild logs and inside VS 2015.

Okay, thanks for the additional info. I'll see if I can reproduce your environment when i get the chance - also did you try the fix suggested above?

@mousetraps I try instead of that fix, just change EmbedInteropTypes to True for Microsoft.VisualStudio.CommandBars, but still no luck.
error CS1762 : Warning as error : A reference was created to embedded interop assembly
'c:\Program Files (x86)\Microsoft Visual Studio 15.0\Common7\IDE\PublicAssemblies\envdte.dll'
because of an indirect reference to that assembly created by assembly
'c:\Program Files (x86)\Microsoft Visual Studio 14.0\VSSDK\VisualStudioIntegration\Common\Assemblies\v4.0\Microsoft.VisualStudio.Shell.14.0.dll'.
Consider changing the 'Embed Interop Types' property on either assembly.

Sorry for bothering, I do full clean and build working.


Fix: added auto_increment to sql dump

fixes #306
and #251 can be closed?

@ins0
Looks good to me, but since @GeeH deploys, I think he should have a look!

@GeeH
If we merge this, how are you going to make the changes to the database? Manually? Since we decided against #252, shall we maybe use http://phinx.org?

@ins0
I'm happy to merge this so I could remove this workaround in a test

https://github.com/localheinz/modules.zendframework.com/blob/feature/search/module/ZfModule/test/ZfModuleTest/Integration/Mapper/ModuleTest.php#L176-L191

however, my concerns in https://github.com/zendframework/modules.zendframework.com/pull/340#issuecomment-73226042 are still valid, no?

as the page was working (adding/removing) repositorys and the state bug was fixed too before this PR, the database should be allready in this format and could be safely merged. no?

@ins0
I have no idea, I don't have access to the production system.
@GeeH
Can you confirm that the @ins0 statements are true for the production system?

Confirming that the database schema in production is up-to-date with this, and merging.
Thank you, @ins0!

i love your server access :dancers:  - thanks!

@gianarb
:smile:


Multiple prometheus with one operator

Hello,
at the moment we have one prometheus-operator with one prometheus deployed via helm on our cluster. This prometheus is used to monitor all deployments.
But we decided that it would be more useful for us to have multiple prometheus. We have several namespaces for our customers and would like to use one prometheus per customer. As far as I read in another (closed) issue, it's recommended to use one operator for all prometheus in a cluster.
So my questions are, did I understand that correctly? And if so, is there a way to tell the prometheus-operator to create a prometheus in a namespace with a specified label even if I create new namespaces after the operator has been deployed?

As far as I read in another (closed) issue, it's recommended to use one operator for all prometheus in a cluster.
Please link the issue.

You can just create a Prometheus object in any namespace you like :slightly_smiling_face: .

Theoretically you can create as many objects of the kind Prometheus as you like and they can be in any namespace that you like.
The key thing to understand here is the difference between the actual deployment of prometheus instances and the deployment of objects of the kind prometheus.(
https://github.com/coreos/prometheus-operator#customresourcedefinitions)
About the topic of one operator per cluster: from my personal experience you have have trouble if you run multiple operators in a cluster, which might even have different defaults set for the prometheus and Alertmanager instances.

Hello,
We are planning to use multiple prometheus instances in the same cluster for functional sharding.
prometheus-adaper has input args --prometheus-url=http://prometheus-k8s.monitoring.svc:9090/ which seems to accept only one URL, If i try with comma seperated URL's it does not work?
Should we have multiple prometheus-adapter, one for each prometheus instances ?

@gogineni99 you're always going to end up running a Prometheus server that collects all the cluster global metrics like cadvisor metrics, so you would point the adapter at that Prometheus.

Hey, @RickS-C137, could you please link the issue that u read about "As far as I read in another (closed) issue, it's recommended to use one operator for all prometheus in a cluster."
Also, @brancz , are there any peace of documentation or any other mentions about several prometheus-operator instances in one cluster in different namespaces? because I want to keep them both, to break dependencies between both namespaces, but when I want to change one of them, all prometheus instances are going crazy

@Dimpison you can't have two controllers act on the same objects, that's always going to end badly. It's the reason why the kubernetes controller manager and scheduler do leader election.

Closing due to inactivity.


Add printing support

I support the push for better printing support in the browser, even independent of its effect on the progress of printing support in pdf.js. So I'm all for trying that route.

I'll say what I said on Google Plus here just so everyone sees it:
CSS and HTML are good high level tools, but honestly I think we need both low level APIs and high level ones so we can properly fill both use cases. I would love a WebPrint API that allowed me direct, pixel perfect control over my printed output rather than leaving that up to the browser. CSS will be good enough for most people, but there are some use cases for a lower level API as well. PDF.js is one of them.
Honestly, the real reason why I wrote PDFKit (my PDF document generator), is so that I could generate nice looking printed documents from an app I was working on. I originally tried doing things with CSS paged media and HTML but had all sorts of problems, namely getting things to lay out properly and issues like not being able to programmatically hide and show the headers and footers with the webpage URL in them that browsers put there, etc. So I wrote PDFKit, and generate the documents server side. The user then has to download the PDF and print it from there. This works but it is very cumbersome for the user, and for the developer.
I don't think there is any problem with supporting both low level and high level APIs in the browser in general. Most people will use the high level one, but for certain use cases low level APIs are really useful when we want to do really custom things that the standard hadn't thought of yet. Anyway, just my two cents!

Based on the feedback and some other discussions I've started to scratch what a WebPrintAPI could look like. See this post:
https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.webapi/2J4wigFiCF8

Future discussion about the API will happen on the mailing list.


Various improvements to the QubitMapper classes

Summary
This PR adds the following improvements to the QubitMapper classes:

[x] makes suppress_none a keyword-only argument everywhere (this matches how it was in the QubitConverter; this does not need a release note since it is an unreleased change)
[x] deprecates the QubitMapper.allows_two_qubit_reduction attribute (#1039)

[x] needs to be added to the release note

[x] renames the nmodes argument to register_length everywhere

[x] needs to be added to the release note

Details and comments
The reason for that last change is in preparation for #831. I do plan to include allowing to overwrite register_length as part of a call to QubitMapper.map in this PR. This already works mostly but I still need to check the mappers which do not use the QubitMapper.mode_based_mapping.
EDIT: #831 is now fully implemented in this PR, too.
Finally, I would also like to raise the question of whether we need to keep the FermionicMapper, SpinMapper, and VibrationalMapper classes. These do not really add any benefit except typing but those are not even enforced at runtime.
I would thus suggest any of the following options:

remove these classes alltogether (respecting the deprecation period ofcourse..)
actually use these classes to enforce types at runtime (in the sense of an isinstance check in their _map_single methods and corresponding super()._map_single(...) calls in their subclasses
at least hide these from the public API since they honestly just add noise to the documentation page of the mappers since these are abstract and cannot be used by the users directly anyways.

EDIT: I opted to keep these classes but removed them from the public documentation page (since these are not actually usable by an end-user and add unnecessary noise). I updated the classes to type the public .map rather than private ._map_single method such that an IDE can actually aid a user with these type hints.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

69 of 70 (98.57%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 85.963%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_nature/deprecation.py
4
5
80.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
17686

Relevant Lines:
20574

💛  - Coveralls

I am not sure about not having FermionicMapper etc as part of docs. If say I look at ParityMapper in the current resultant docs I can see some method, that pretty much as a end user of the mapper I should not care about. But I don't, unlike before, see any map method, the one and only thing as an end user I normally would use. I cannot navigate up the class structure to see what it may inherit since the FermionicMapper link there is not operational, although maybe that class won't show map there either. If I happen to know its QubitMapper (now I would be able to go up once again from FermionicMapper were that included) I can go there, though then I see it more as a generic map method taking a SparseLabelOp. Maybe that common base method is all we would get now anyway. For any classes etc that are exposed to an end user, or developer to extend, we have normally included them. Maybe its not a lot better in regards of how map method gets exposed with including it  (not sure)  but at least one can navigate up through the parents in the docs.

Thanks for raising this! I think this is actually a symptom of the underlying issue that we do not document inherited members in our classes. I have fixed this for the mappers module in the last commit but I think we should revisit this choice for all docs in a separate PR.
In fact, Qiskit Terra also already differentiates between two cases where classes should document the inherited members and where they should not. For the ad-hoc fix here, I mirrored that (actually the inverse because our default is the opposite). We should revisit this in a separate step and align our docs with that of Terra. I will open a separate issue for this shortly.


could this improve rendering latency for web browsers ? (2D GUIs)

Unfortunately, I think there would be a lot of obstacles applying this to 2D GUIs. Here are some reasons:

Web browser workloads are highly uneven. Sometimes they don’t update at all, sometimes they do a partial update, once in a while they do a full repaint. It’s drastically different from video games where workload changes smoothly frame-to-frame.
2D GUIs relies on VSync, and VSync heavily penalizes deadline misses. LatencyFleX currently assumes that missing the target time is OK, given that most games are ran inside FreeSync range or VSync off. I still haven’t decided what’s a good strategy to handle such an asymmetric deadline model.

@kvark @nical @emilio friendly ping, I wonder wether you have thoughts to share on this topic

I agree with ishitatsuyuki's assesment regarding how uneven browser workloads are and how vsync affects these things. Note that Firefox already does some things like refresh driver throttling when the end of the pipeline can't keep up with the start, although it's more to avoid catastrophic accumulation of gpu work than to fine tune latency.

However, if Firefox could detect adaptative sync support that would mitigate the vsync issue no?

In theory maybe, but you still have the problem of very uneven workloads. More importantly we already have some lower hanging (and more impactful) fruits to pick in terms of latency improvement including work in this year's roadmap. And variable refresh rate monitors are too uncommon as of today in proportion for us to dedicate more time than making sure it works as well as vsync.

If you really want lower latency for whatever reason in a web browser, you can always disable vsync in most browsers though flags or about:config to my understanding. I don't really know why it would be a issue in the context of a browser though, but browsers are so easy to run that you can get like 500+ FPS easily


Unable to change height of individual timeline box for raidboss module

Hi, I understand that there is a specific note that adjusting appearances of the timeline container in the raidboss module will be difficult due to its custom nature.
However, I would like to just check if this is a bug or intended:

While I am able to adjust parameters such as the font size and width of the timeline container, I am unable to adjust the height, no matter what I change to the "height: ___" attribute in the specific user css file. This results in the customised timelines unable to cater to font-size that are bigger than the default font size of 14.
Just want to ask if it is possible to adjust the height of the timeline boxes.

This would be the element to adjust (i used a high value so its abvoius in testing), but currently it seams to ignore user css file completly for me
.timeline-bar-color {
    height: 200px !important;
}

What about to ajust the "zoom" level in OverlayPlugin ?

thank you, your comment solved my issue for me. What I did wrong, was basically editing the info-text for the class "timeline-container" (which apparently seems to me is the correct and only way to change the width of the timeline alerts) instead of "timeline-bar" as you mentioned. But in my case, tested and the raidboss module goes thru my user css file.
Closing this issue.

What about to ajust the "zoom" level in OverlayPlugin ?

that would work and is a good idea for a quickfix if someone simply wanted a minor upscale or downscale of the timeline alerts. However, without changing the CSS file, the "zoom" function cannot make the timelines go beyond the default container size, and hence there is a limit to simply just zooming w/o making changes to CSS.


Export ROS2 definitions, change package export to { ros1, ros2 }

Public-Facing Changes

The top-level package export is no longer ROS1 definitions, but two objects named ros1 and ros2 containing definitions

Description
This adds concatenated .msg files for common_interfaces and rcl_interfaces from ROS2 and exports them under a top-level ros2 object.

Posting here so we have a record of it outside of slack:
The marker message changed between galactic and humble. I don't know that we have any Studio users on humble yet but we do have users on foxy and galactic. If we move to the latest marker message (in this PR) then we won't be able to deserialize the Markers in their .db3 files or live ros2 native connections.
https://github.com/ros2/common_interfaces/blob/galactic/visualization_msgs/msg/Marker.msg
https://github.com/ros2/common_interfaces/blob/humble/visualization_msgs/msg/Marker.msg
It seems that for ROS we need to expose versions of the messages specific to each release. That's a larger effort so I would also be ok with using the galactic versions of the messages in Studio for now to solve https://github.com/foxglove/studio/issues/3901


Saving the comment fails in a CSV::Table test

See contents of file tmp/saved.csv:

False alarm. The error was caused by CSV::Table.


Move Job.Steps as last serialized property (behind timeount for instance)

I am not sure about this change because it might mean people will have to regenerate their YAMLs when bumping Sharpliner because of the new order of elements but no actual changes. Not sure we want that?


Composed estimator hierarchy for cached native price estimations

Since #1619 triggered a discussion about the viability of the approach of composing a new native price estimator entirely from existing components, I wanted to share what I got so far.
The current code already highlights one weird thing with reusing the CachingPriceEstimator:
The CachingPriceEstimator as well as the task maintaining it in the background need to be parameterized a little bit different but not that different that it would make much sense introducing more CLI arguments for that.
Note creating the new estimator hierarchy is quite verbose but relatively painless in this approach but optimizing the task to maintain the cache in the background further would probably end up quite hacky.

Codecov Report

Merging #1622 (d50d43c) into caching-price-estimator-maintenance (47e251b) will increase coverage by 0.02%.
The diff coverage is 43.34%.

@@                           Coverage Diff                           @@
##           caching-price-estimator-maintenance    #1622      +/-   ##
=======================================================================
+ Coverage                                66.62%   66.64%   +0.02%
=======================================================================
  Files                                      172      172
  Lines                                    33752    33894     +142
=======================================================================
+ Hits                                     22486    22589     +103
- Misses                                   11266    11305      +39

Closed in favor of #1626


Coordinate Conversion: should clear all outputs when invalid coordinate is entered

NOTE: This is an enhancement, but a very critical enhancment
Widget
Coordinate Conversion
Version of widget
14 December 2016
Bug or Enhancement
When you specify an invalid coordinate in the Input textbox, any previous calculated results in the Output texboxes are not cleared. The last valid output is still displayed. This is extremely dangerous as the user may not have realized they entered an invalid coordinate or did not realize that the output values didn't change from the last valid coordinate entered; they will then copy the outputs to use in other applications thinking they copied valid values.
Example:
The user enters the following valid MGRS coordinate: 34PFR1459853908
The output textboxes are updated to display the output coordinates...

Then the user enters the following invalid MGRS coordinate, either because the user was given an invalid MGRS coordinate or maybe they did a copy/paste from a report and didn't copy all the coordinates: 34KGE358193443
(it's invalid because it's missing the 10th digit in the easting/northing; perfect example of a copy/paste issue)...
We at least notify the user that there was a problem...

But we should clear the output textboxes instead of leaving the calculated coordinates as it is now...

Repo Steps or Enhancement details

This issue was moved to Esri/coordinate-conversion-addin-dotnet#149


HBASE-24166 Duplicate implementation for acquireLock between CreateTa…

…bleProcedure and its parent class
The override method acquireLock in CreateTableProcedure and InitMetaProcedure is the same as the implementation in its parent class AbstractStateMachineTableProcedure. So delete the override method in subclass.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 32s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 53s
the patch passed

+1 :green_heart:
compile
1m  5s
the patch passed

+1 :green_heart:
javac
1m  5s
the patch passed

+1 :green_heart:
shadedjars
5m 19s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 40s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
118m 51s
hbase-server in the patch passed.

148m 17s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1486/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1486

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ee8f13c92441 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ac4e94e868

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1486/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1486/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1486/1/testReport/

Max. process+thread count
4239 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1486/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 16s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
6m 12s
master passed

+1 :green_heart:
compile
0m 58s
master passed

+1 :green_heart:
shadedjars
5m  1s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 40s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 35s
the patch passed

+1 :green_heart:
compile
1m  0s
the patch passed

+1 :green_heart:
javac
1m  0s
the patch passed

+1 :green_heart:
shadedjars
4m 57s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 36s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
175m 41s
hbase-server in the patch passed.

203m 45s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1486/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1486

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 539dc16ff28b 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ac4e94e868

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1486/1/testReport/

Max. process+thread count
3546 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1486/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Sanic Documentation

I'm going to use Sanic 0.4 (or maybe 0.5 in few days), but it seems the documentation here is out of date.
Am I right? Won't you update documents in readthedocs?
Thanks.

maybe there's a few things outdated, but you can do almost everything the same.
at least what i can confirm is that listeners are not working for me...

The documentation on ReadTheDocs is apparently out of date, the title says Sanic 0.31 documentation while the latest version is 0.4.1.
Something is wrong with ReadTheDocs build I think.

@channelcat @seemethere @kdelwat I can't even log into my http://readthedocs.io account (apparently I have two and can't reset the one with access to Github). If any of you can look into why the build is breaking that would be awesome.

@messense
So can you help me to build it myself?
When I write "make html" command in my sanic/docs directory, I get the following error:
Running Sphinx v1.3.6 Exception occurred:   File "conf.py", line 14, in <module>     from recommonmark.parser import CommonMarkParser ImportError: No module named recommonmark.parser The full traceback has been saved in /tmp/sphinx-err-M6Tal3.log, if you want to report the issue to the developers. Please also report this if it was a user error, so that a better error message can be provided next time. A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks! Makefile:20: recipe for target 'html' failed make: *** [html] Error 1
(recommonmark itself is installed in my system)

@sinahmr pip install -r requirements-dev.txt

@messense Tnx

@r0fls I will look into the issue in the next day or too.

After #561 merged ReadTheDocs build still seems broken.
Would you guys consider uploading documentation to  http://pythonhosted.org/ for now?

Doesn't appear to be broken, I think it just generates docs on a release.

Just manually triggered a build and it seems to be working fine when I trigger it manually.

@messence @seemethere On my test ReadTheDocs account it definitely now works fine. Could be a problem with the Git hook?

@kdelwat I'd believe so but I don't have admin access to the repo so it could be difficult to discern.
@channelcat to the rescue?

This looks to be working fine now. Anyone feel free to reopen if there is still an issue.


Code bundled with webpack runs 5-10 times slower in Chrome than the same code not bundled with webpack

Do you want to request a feature or report a bug?
I guess it's a bug.

What is the current behavior?
I'm measuring how much it takes to run an arbitrary slow (lots of iterations) function.
The thing I noticed is that when the code is bundled with webpack, the function takes 5-10 times longer to run than when I do not use webpack and just run code as is (copying imports to the file).
If the current behavior is a bug, please provide the steps to reproduce.
The problem can be reproduced in Chrome (i'm running on 61.0.3163.91).
In other browsers (safari and ff) there seems to be no difference, so there's no problem.

I have created a minimal demo where you can try to run the code yourself and see the results: https://everdimension.github.io/webpack-bundle-test/
Source code: https://github.com/everdimension/webpack-bundle-test
What is the expected behavior?
There should be no measurable performance difference between code bundled with webpack and one that is not.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
I'm running it on mac os 10.12.6
<EMAIL_ADDRESS>Chrome 61.0.3163.91

You seem to transpile the code in the webpack bundle with babel. This makes the generated code not identical:
function doComputations() {
  var iterations = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : 100000000;

  var arr = [];
  for (var i = 0; i < iterations; i++) {
    var val = i * Math.sqrt(arr.length);
    if (arr.length > 1000000) {
      arr.length = 200000;
    }
    arr.push({ val: val });
  }
  return arr;
}

vs
 function doComputations(iterations = 100000000) {
    /* this function is an exact copy of `/src/doComputations.js` */
    const arr = [];
    for (var i = 0; i < iterations; i++) {
      const val = i * Math.sqrt(arr.length);
      if (arr.length > 1000000) {
        arr.length = 200000;
      }
      arr.push({ val });
    }
    return arr;
  }

My guess is using arguments makes the function not optimizable. Try to omit the default argument to see better performance.
cc @bmeurer: maybe an opportunity to optimize v8 for babel generated code?

@sokra Your guess is correct, i've discussed the issue on reddit and we've discovered that this is indeed the reason behind this performance drop.
There also seem to exist relating issues in the babel repo: https://github.com/babel/babel/issues/5922 and https://github.com/babel/babel/issues/5776
They're closed, though.

upd: Ok, the babel issues are closed because the PR that's considered a fix has already been merged.
It's in beta (babel v7.0.0) and requires you to add a special option to babel: { "loose": true } which would tell babel to transpile without referencing the arguments variable.
I guess that's the cost of transpilation.


added flight price prediction using machine learning

Description
In this project, I developed a flight price prediction system using machine learning techniques. The dataset consisted of various flight details including airline, source, destination, total stops, departure and arrival times, and flight duration. I began by preprocessing the data, converting 24-hour times to 12-hour format with AM/PM labels and formatting flight durations into hours and minutes. Categorical variables were encoded appropriately for model training.
I trained multiple regression models including Linear Regression, Random Forest, Gradient Boosting Regressor, and XGBoost to predict flight prices. Each model was evaluated using metrics such as R^2 score, mean squared error (MSE), root mean squared error (RMSE), and mean absolute percentage error (MAPE). Visualizations, including scatter plots comparing actual vs. predicted prices, provided insights into model performance.
The Gradient Boosting Regressor demonstrated the highest accuracy. Real-time predictions were implemented using this model, allowing users to input flight details and receive instant price estimates. Overall, the project integrated data preprocessing, model training, evaluation, and real-time prediction, showcasing the application of machine learning in predicting flight prices accurately.
Fixes #556
Type of change

[X] Added a new machine learning frameworks, libraries or software.

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings

@sanjay-kv please merge this PR along with level and label , it will resolve issue no 556

@sanjay-kv please merge this pr


Add example of NextSequence() usage to readme

See: https://github.com/boltdb/bolt/issues/436

:+1: thanks for adding to the README!


Error while opening xx: file does not exist

migration.go
migrations := &migrate.HttpFileSystemMigrationSource{ 	FileSystem: pkger.Dir("/db/migration"), }
setps
1.pkger
2.go build xx.go
3.run exe file, get error

what if you replaced step 2 to
2.go build


Got an error: 'Import or export declaration in an ambient module declaration cannot reference module through relative module name'

Got an error when compiling:

ERROR in [default] c:\Codes\angular2\quick-start\node_modules\angular2-data-table\release\angular2-data-table.d.ts:176:4
Import or export declaration in an ambient module declaration cannot reference module through relative module name.

How to fix such a kind of error? Thanks.

The file is there, see: https://github.com/swimlane/angular2-data-table/blob/master/release/angular2-data-table.d.ts
Can you provide a demo maybe?

Dupe of #55


Cannot extract functions with type annotations using Karamel

In some cases, functions defined using the fn foo (...) : ty = args { ... } syntax cannot be extracted using Karamel:
module ExtractionTest

let noop = x:SizeT.t -> stt SizeT.t emp (fun y -> pure (y == x))

(*
Cannot re-check ExtractionTest.foo as valid Low* and will not extract it.  If ExtractionTest.foo is not meant to be extracted, consider marking it as Ghost, noextract, or using a bundle. If it is meant to be extracted, use -dast for further debugging.

Warning 4: in top-level declaration ExtractionTest.foo, in file ExtractionTest: Malformed input:
subtype mismatch, size_t (a.k.a. size_t) vs size_t -> size_t (a.k.a. size_t -> size_t)
*)
inline_for_extraction
```pulse
fn foo () : noop = x { x }
```

// Extracts fine
```pulse
fn foo' () requires emp returns z:SizeT.t ensures pure (z == 42sz) {
  foo () 42sz;
}
```

The OCaml extraction looks fine though:
type noop = FStar_SizeT.t -> FStar_SizeT.t
let foo uu___ x = x

Adding the following function already breaks fstar.exe --codegen krml --extract:
(*
Unexpected error; please file a bug report, ideally with a minimized version of the source program that triggered the error.
Failure("Impossible: Tm_unknown")
*)
let foo'' = foo () 42sz

Apparently I missed a warning during extraction:
Not extracting Bug9.foo to KaRaMeL (function type annotation has less arrows than the number of arguments; please mark the return type abbreviation as inline_for_extraction)
Adding inline_for_extraction to noop makes extraction work again.  (Though it would be great if this was an error and not a crash.)


Replace schema validation library with actively maintained library

Reference

https://github.com/networknt/json-schema-validator

Make use of json-schema-validator by rest-assured.
https://mvnrepository.com/artifact/io.rest-assured/json-schema-validator


This page is not for "Encrypt video with AES-128" but for playready license

Hi team,
When I click the article from Tutorials -> .NET-> Encrypt dynamically with AES-128, but it will show the article for "Media Services v3 with PlayReady license template". Please check the screenshots for details.

Thanks.

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

ID: d2802360-c171-66dd-47de-ca39d3e04adb
Version Independent ID: 0629fb96-ea73-ef3a-507f-ff8ec6148378
Content: Media Services Microsoft PlayReady license template - Azure Media Services v3
Content Source: articles/media-services/latest/drm-playready-license-template-concept.md
Service: media-services
Sub-service: rest-v3
GitHub Login: @IngridAtMicrosoft
Microsoft Alias: inhenkel

Thanks for reporting this. I have assigned the issue to the content author to investigate further and update the document as appropriate.

This has been corrected. Thanks!
#please-close


Add session schedule to session page

Add session schedule to the
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

@astephanus Could you review please?


[Spotify Player] Menu Bar player always says Nothing is Playing

Extension
https://www.raycast.com/mattisssa/spotify-player
Description
Menu Bar player always says Nothing is Playing
Steps To Reproduce

Install spotify extension from raycast store
Authenticate
Activate Menu Bar Command
Play some song
Notice that Menu bar still says "Nothing is playing right now"

Current Behaviour
Menu bar player says "Nothing is playing right now" even though song is playing
Expected Behaviour
Menu bar player shows the song being played

@syuraj for the menu bar to work unfortunately we need to have the mac app installed
its possible to show now playing without it too afaik it isn't implemented yet
fell free to create a pr if you want

mac app was open,
if you see in the screenshot, it was being played on desktop app.

mac app was open,

By mac app i mean the spotify desktop app, not the web version


Make a "release" of the specs

In order to merge and publish improvements to the protocol it is desirable to integrate things on "main" that may represent future improvements to the protocol.
Thus, it is important to have releases.

The first release should probably be against https://github.com/magic-wormhole/magic-wormhole-protocols/commit/9565dad5da53b88eff5677fb30d0146bdea68b69 (i.e. the latest commit on main right now).

Are these hosted anywhere already? (I assume the RTD https://magic-wormhole.readthedocs.io/en/latest/ is all coming from the Python implementation repo)

No, not that I know of. We could publish the docs there, but mid-term I'd like to have them as part of a proper magic-wormhole.io home page. Not sure what to do with magic-wormhole.readthedocs.io though. Maybe host information specific to the Python implementation there only?

Regarding version numbers: not sure how strictly we want to follow semver. I suggest tagging the initial commit with 1.0 and then the current state 1.0.1, as it only contains clarifications and no new features.

Sure. I've been using "calver" usually but that seems right for semver (AFAIK).


feat: reduce local-environmnet to one cardano-node

Description
This reduces local environment to just one cardano node.
Context for this decision is that having multiple cardano nodes without multiple db-syncs has little sense from Partner Chains point of view. Having multiple makes this setup heavy.

removed cardano-node-2 and cardano-node-3
reduced stake of cardano-node-2 and cardano-node-3, E2E tests depend on this stake so it was not removed completly
active_slots_coeff has been set 0.4 everywhre
removed redundant env variables in containers
removed passing native token variables using shared files

Checklist

[x] Commit sequence broadly makes sense and commits have useful messages.
[ ] New tests are added if needed and existing tests are updated.
[ ] Relevant logging and metrics added
[x] CI passes. See note on CI.
[ ] Any changes are noted in the changelog.md for affected crate
[x] Self-reviewed the diff

Note on CI
If your PR is from a fork, the necessary CI jobs won't trigger automatically for security reasons.
You will need to get someone with write privileges.  Please contact IOG Partner Chains developers to do this
for you.

I just realized you haven't updated the readme.

Looks clean, great PR. The local-environment-tests job completed in under 7 minutes which could even be a slight improvement
Thanks Lech


docs: Actualize grafana dashboards for v0.33

Fixes #4838
Description
Actualize grafana dashboards for v0.33
How was this change tested?
Does this change impact docs?

[ ] Yes, PR includes docs updates
[x] Yes, issue opened: #4838
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I'm allow maintainers of Karpenter edit my PR and do changes. Thank you!

@ljosyula this helped to fix Karpenter Capacity dashboard.
However my knowledge not enough to fix Controllers / Allocation dashboard, because that metrics not send anymore by karpenter:
karpenter_allocation_controller_bind...
karpenter_allocation_controller_binpacking...
karpenter_allocation_controller_scheduling...

But please, let's merge this to fix Karpenter Capacity dashboard.
Thanks!

Thank you for making these changes. Nicely done. Would you mind copying these changes to v0.32, preview and docs?

@jigisha620 It's not needed to be copied to v0.32 as v0.32 has old and new API. Starting from v0.33 old API stops working including dashboards.

@jigisha620 It's not needed to be copied to v0.32 as v0.32 has old and new API. Starting from v0.33 old API stops working including dashboards.

@Hronom You are right about v0.32 having both old and new API. But we have decided to document the new API while delivering the experience to customers who are new to Karpenter. That means we would want this change for v0.32 as well along with a change to preview and docs.

@jigisha620 alright, added as requested.
Also feel free to make any changes from your side in order to speed up merge of these. Thanks!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.627%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5008

Relevant Lines:
6061

💛  - Coveralls

LGTM 🚀

Never mind, I copied over the changes to v0.34.


Publish compute-baseline to npm

In order for @LeoMcA to use this on MDN, we need to publish it.
@ddbeck is it just a question of running npm publish?

@foolip I think there's a few little things to do first:

[ ] Remove "private": true from package.json
[ ] Copy over LICENSE.txt at publishing time (kinda like we do in build.ts)
[ ] Add a (bare-bones) README.md to /packages/compute-baseline

@ddbeck seems like most of the work is done and all is left is making the package public and publishing it. I could make use if it was published.

@captainbrosset Yes, I'm working on this. See https://github.com/web-platform-dx/web-features/pull/961.

And we're live: https://www.npmjs.com/package/compute-baseline/v/0.1.0-dev-20240425134050-57ad8a7


I got error "error: resulting document after update is larger than 16777216"

Hi,
I tried to add data to NLU, but i got error "error: resulting document after update is larger than 16777216"
Could you, please help to advise this?
Before of this error, i got "error: bsonobj size: 16904485 (0x101f125) is invalid"
Is it Mongo issue ? if yes, could you, please advice this?
Thanks you alot

I added more information in mongo log:
2020-06-20T14:17:44.094+0000 I  NETWORK  [conn12] end connection <IP_ADDRESS>:34960 (7 connections now open)
2020-06-20T14:41:31.256+0000 E  -        [conn15] Assertion: BSONObjectTooLarge: BSONObj size: 16939217 (0x10278D1) is invalid. Size must be between 0 and 16793600(16MB) First element: $v: 1 src/mongo/bson/bsonobj.cpp 98
2020-06-20T14:46:20.183+0000 E  -        [conn8] Assertion: BSONObjectTooLarge: BSONObj size: 16809968 (0x1007FF0) is invalid. Size must be between 0 and 16793600(16MB) First element: $v: 1 src/mongo/bson/bsonobj.cpp 98

Hi, seems your model hit the MongoDB document size limit. How many examples
do you have?
Le sam. 20 juin 2020 10 h 51, nhha1602<EMAIL_ADDRESS>a écrit :

I added more information in mongo log:
2020-06-20T14:17:44.094+0000 I NETWORK [conn12] end connection
<IP_ADDRESS>:34960 (7 connections now open)
2020-06-20T14:41:31.256+0000 E - [conn15] Assertion: BSONObjectTooLarge:
BSONObj size: 16939217 (0x10278D1) is invalid. Size must be between 0 and
16793600(16MB) First element: $v: 1 src/mongo/bson/bsonobj.cpp 98
2020-06-20T14:46:20.183+0000 E - [conn8] Assertion: BSONObjectTooLarge:
BSONObj size: 16809968 (0x1007FF0) is invalid. Size must be between 0 and
16793600(16MB) First element: $v: 1 src/mongo/bson/bsonobj.cpp 98
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/botfront/botfront/issues/641#issuecomment-647005407,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4GAKT6IV5IXKYPF5VDXZTRXTEH3ANCNFSM4OCPVAJA
.

Hi, seems your model hit the MongoDB document size limit. How many examples do you have? Le sam. 20 juin 2020 10 h 51, nhha1602<EMAIL_ADDRESS>a écrit :
…
I added more information in mongo log: 2020-06-20T14:17:44.094+0000 I NETWORK [conn12] end connection <IP_ADDRESS>:34960 (7 connections now open) 2020-06-20T14:41:31.256+0000 E - [conn15] Assertion: BSONObjectTooLarge: BSONObj size: 16939217 (0x10278D1) is invalid. Size must be between 0 and 16793600(16MB) First element: $v: 1 src/mongo/bson/bsonobj.cpp 98 2020-06-20T14:46:20.183+0000 E - [conn8] Assertion: BSONObjectTooLarge: BSONObj size: 16809968 (0x1007FF0) is invalid. Size must be between 0 and 16793600(16MB) First element: $v: 1 src/mongo/bson/bsonobj.cpp 98 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#641 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4GAKT6IV5IXKYPF5VDXZTRXTEH3ANCNFSM4OCPVAJA .

Hi,
Yes, there are alot ... around 100K and may be more
Do you have any solutions for this ? I think data will be more and more :) when we have more complicated stories

Can we use GridFS to break big size documents @znat @nhha1602

Can we use GridFS to break big size documents @znat @nhha1602

@engahmed1190 Do you know how to do it? Please help. Thank you.

Hello @nhha1602 .
Please refer to this link
@znat can we add this as enhancement feature


perf: add db pagination to speed up uuid column migration

SUMMARY
We have tens of thousands of dashboards and more than 1 million slices in our Superset deployment. It takes forever to run the db migration for #11098 . This PR tries to speed up the migration process by adding pagination to db queries. I also tried to utilize ThreadPoolExecutor to parallelize the db operations and uuid generations, but it doesn't seem to help the overall speed much.
Also fixes certain API errors while downgrading in MySQL and added the option to adjust batch size from command line.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
N/A
TEST PLAN
Make a copy of your very large database, then try:
superset db downgrade
superset db upgrade

ADDITIONAL INFORMATION

[x] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[x] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #11209 into master will increase coverage by 0.80%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11209      +/-   ##
==========================================
+ Coverage   61.49%   62.30%   +0.80%
==========================================
  Files         828      436     -392
  Lines       39145    14590   -24555
  Branches     3589     3589
==========================================
- Hits        24073     9090   -14983
+ Misses      14892     5320    -9572
  Partials      180      180

Flag
Coverage Δ

#javascript
62.30% <ø> (ø)

#python
?

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

Impacted Files
Coverage Δ

superset/migrations/versions/d39b1e37131d_.py

...set/migrations/versions/55179c7f25c7_sqla_descr.py

superset/views/chart/views.py

...ions/versions/7e3ddad2a00b_results_key_to_query.py

...tions/versions/db527d8c4c78_add_db_verbose_name.py

superset/css_templates/dao.py

.../versions/a6c18f869a4e_query_start_running_time.py

superset/views/base_schemas.py

...a74826_add_metadata_column_to_annotation_model_.py

...817e1c9b09d0_add_not_null_to_dbs_sqlalchemy_url.py

... and 381 more

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 761e6db...dcd4c79. Read the comment docs.

got a bit too late to this pr, thanks @ktmud for the fix!


feat(Dashboard): add button to schedule erp update manually

Description

solves #490 by adding a button to the dashboard view allowing users to schedule the item stock update for what they currently see:

customer or supplier tab defines the direction
partner = the one associated with the selected sites (mutliple schedules)
material = the one selected

beside that I added notifications for the async tasks (schedule erp update, trigger refersh of partner data) in the dashboard view -> solve #414
Note on helm version: keep it as 2.7.0 as it's the next unreleased minor version.
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files
[x] If helm chart has been changed, the chart version has been bumped to either next major, minor or patch level (compared to released chart).

LGTM, thank you very much, Only the chart version needs to be incremented ;)

@eschrewe thanks for reviewing! I won't bump the chart version as we currently have not yet released a new version (current is puris-2.6.3). In the past we didn't release each chart bump and only bumped the chart as it has been blocking. The workflow is meant for real devOps (each commit = new release) which we don't follow (also due to splitting PRs to smaller ones). Recent pratice actually lead to some version gaps in the released charts (not smart from my side).
I removed the setting, that the chart is blocking but keep it failing indicating that the reviewer needs to check if nevertheless the increase is needed e.g.: we already increased the chart version to a patch level in a previous change. The chart has not yet been released. In the next pr we have a minor level change in the chart -> now we should increase the chart version to the next minor.
Sidenote: also our PR template now has a new box indicating this helm chart check :)