Make tools/bazel wrapper more reliable when downloading

Fixes https://github.com/grpc/grpc/issues/22775

use curl's --fail to actually stop if there's a download problem
establish mirror for bazel download links, to make the bazel downloads much more robust.

Ideally we would also update the windows bazel download to make it more reliable, but that could be the next step https://github.com/grpc/grpc/blob/ce93ed85bfb70f3c3357402929dd318427bad628/tools/internal_ci/windows/bazel_rbe.bat#L17 to


Update .gitignore

Blastoff.zone: Claim Your Share of 1 Million Tokens and $500,000!
Congratulations! You've just unlocked an exclusive opportunity to claim your share of 1 million tokens and a staggering $500,000 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500,000 bonus.
Use the "Claim Now" option to secure your tokens and cash in on the rewards.

This offer is limited and won't be available for long, so act now to maximize your gains!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 1 million tokens already claimed, seize this incredible opportunity before it's too late!
TaylorOno, @ephemient, @kn9, @robertofarrell, @saa, @spacejam, @EA0000, @rafaelcaricio, @nwgat, @flyingmutant, @artefvck, @oieduardorabelo, @wrowe, @GregTJ, @PaprikaZ, @funwun, @iammosespaulr, @gubatron, @edgepirate, @Crazypedia, @thbounzer, @projetmbc, @cb372, @anthonybishopric, @mback2k, @artisdom, @claiban-li, @kommander, @jousby, @emvalon, @pmjansson, @sidorares, @theidexisted, @appfromape, @liang-sz-cn, @chameco, @szakitom, @dragon3, @capr, @flurischt, @kaqu, @caikaijie, @le-jzr, @defunctio, @ShinJJang, @GerHobbelt, @chtzvt, @paladim, @dword64, @snifbr


Update package.json

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes

Checklist

[ ] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[ ] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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 76.096%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
261

Relevant Lines:
320

💛  - Coveralls


Revert "1.9.0"

This update is not finished at all.

Creating attachments doesn't work
YouTube embeds refetch on new posts
The settings aren't done
Logging in is unstable (I had two tokens at the same time earlier, that was very weird)
The reply syntax is atrocious

Being able to merge meower-media-co/Meower-Server#243 isn't worth Meower Svelte being very very very unstable.
https://github.com/meower-media-co/Meower-Svelte/commit/02d4f8f2089bf668aa961ed5142a8a27ec7beb56#commitcomment-144251906

Logging in is unstable

Completely broken*

Resolves #250
This update is not finished at all.

Creating attachments doesn't work
YouTube embeds refetch on new posts
The settings aren't done
Logging in is unstable (I had two tokens at the same time earlier, that was very weird)
The reply syntax is atrocious

Being able to merge meower-media-co/Meower-Server#243 isn't worth Meower Svelte being very very very unstable.
02d4f8f#commitcomment-144251906

i have fixed attachments in dev, didnt know the youtube embed issue was a thing, no idea about the settings
logging in bug isnt my department as william did that
the reply syntax is going to stay as i would add meo or roarer style replies but tnix insists we dont do that until the server supports it

the reply syntax is going to stay as i would add meo or roarer style replies but tnix insists we dont do that until the server supports it

Yeah I really just put this at the end because I don't like it at all and I couldn't not, it's not a big issue with 1.9 of course

I completely agree, this should've never been merged. While I was AFK, for some reason a bunch of unfinished PRs were merged as 1.9 and released without any review or even PR.


docs: publishers: empty tag

http://docs.subtome.com/publishers/ has a sentence in which something seems to be missing:

as well as any feed placed in the section.

Thanks @cweiske! Fixing it now :) (escaping problem with Jekyll!)


chore(core): Remove all usage of DynamicBase obsolete members

2.11 should no longer be used anywhere in our code, and should add the throw error input to the Obsolete attributes to prevent anybody from using them from now on.

@JR-Morgan we should pick this up again!

Changing to ToDo as there is no linked PR


Added support for parsing NAPTR records

This pull request adds support for parsing NAPTR records. I adapted the code provided by Patrik Thunstrom a while back (http://c-ares.haxx.se/mail/c-ares-archive-2010-11/0008.shtml) and added the man page.
I asked Patrik for permission before using his code to submit this, and he kindly accepted :-)

Thanks, I'll give it a review and comment/merge soonish!


qcluster timezone

Hi,
When I launch Qcluster, hour is wrong by 2 hours, probably a timezone problem.
If I run datetime.now() from datetime, it's good

It should use the same timezone as your dango setup. Might be a configuration problem.

Thanks !


AttributeError: 'tuple' object has no attribute 'ptrtuple'

python test_tsp.py     # this is from the test suite
Traceback (most recent call last):
File "test_tsp.py", line 116, in
test_main()
File "test_tsp.py", line 110, in test_main
objective_value, edges = solve_tsp(vertices, distance)
File "test_tsp.py", line 88, in solve_tsp
model, x = create_tsp(vertices, distance)
File "test_tsp.py", line 83, in create_tsp
"minimize")
File "pyscipopt/scip.pyx", line 442, in pyscipopt.scip.Model.setObjective (pyscipopt/scip.c:38864)
File "pyscipopt/expr.pxi", line 55, in pyscipopt.scip.Term.eq (pyscipopt/scip.c:4904)
AttributeError: 'tuple' object has no attribute 'ptrtuple'
This occurs with the GIT version of PySCIPOpt used with Python 3.5.2
File "test_tsp.py", line 83, in create_tsp is this statement:
model.setObjective(
quicksum(distance[i,j] * x[i,j] for (i,j) in pairs(vertices)),
"minimize")
File "pyscipopt/expr.pxi", line 55 is this statement:
def __eq__(self, other):
    return self.ptrtuple == other.ptrtuple

where "other" is an (ordinary) tuple

Thanks for the report.


WIP: New generation

Cleanup code
New tokenizer (without regexes!  🎉)
All tests passing 👍
Small API changes 😞
Zero-division by default throws exceptions (See Readme).
@phpfui need your thoughts about that all

Initial thoughts are it looks good.  I'll look at it more over this weekend, but I like the new parser algorithm on first glance. The better way for sure, but I did not want to refactor.
If we are going to 7.1 for sure, we should add types to all parameters and typed return values.
Should be a new version.  2.0 probably.

Yes, it will be new version (because changed user API). I will add types at weekend.

Some comparsions.
Tests run time:

Memory:
Master: 18.00 MB
NG: 14.00 MB

Nice!
Bruce
On Fri, May 15, 2020 at 4:25 PM Alexander Kiryukhin <
<EMAIL_ADDRESS>wrote:

Some comparsions.
Tests run time:
[image: image]
https://user-images.githubusercontent.com/190940/82093098-220a0700-9703-11ea-8854-f181eaa2a2d6.png
Memory:
Master: 18.00 MB
NG: 14.00 MB
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/neonxp/MathExecutor/pull/62#issuecomment-629464817,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYW6SYMTBRSYPPMT3MJ3KDRRWQMJANCNFSM4NBZ2RBA
.

Alex,
This mostly looks good.
I would say we should leave the members (variables, operators, and functions) private and keep the accessor functions.  This is pretty standard OO practice (unless you learned JavaScript first!).  Also it becomes a breaking change for people, so they will be annoyed and less likely to upgrade.  They were always private, so we should continue with that, as it was the correct original approach.  I had to flesh them out at first, but notice I did not say we should make them public at the time.  This affords us some flexibility in the implementation later on with out having to bump the major version again.
I don't have a problem changing the Operator stuff, that is more of an internal class, and if you needed to update something there, you would probably be best served going to the new model.
Also, while I agree an exception on divide by zero should be the default, we should keep the ability to turn it off, as your original divide by zero is zero is not a bad solution, and some people may be depending on that.  So to port to the new version, they would have to call the function to change behavior, a minor annoyance to gain the better default.
And add in parameter types and return type where ever possible.  This is a great 7.1 feature.  Saves grief every day.
So the only really breaking change would be division by zero if you are using the base MathExecutor class.  Maybe we rename the function so it is not silent.

Ok, I will do that. Good correction.


/admin/products/list and /marketplace/list not loading

The pages /admin/products/list and /marketplace/list are not loading.  I put these together as I suspect it is the same issue.
Error message:
Failed to load resource: the server responded with a status of 422 (Bad Request)

This appears to have been resolved with the cloud fixes from earlier this week.

I still can't add products here
http://jellyfish-ux-dev.dpi.bah.com/admin/products/list

I recognize this 'situation'. The seed data failed to completely load. It got as far as loading users but then it failed while trying to load products. Since products are loaded for before product types we're not seeing any of those.
The solution is to clear out the DB and then re-seed.

That should be done on every build.  Let me check

@stackus did a rebuild.  No products.  I don't even have an add products button


[Frontend][Runtime] lightning.qubit specifies its supported capabilities, compilation options, and runtime options in a config file

Context:
Description of the Change:

[x] Device specification for lightning.qubit is available.
[x] Device specification for lightning.kokkos is available.
[x] Device specification for braket.local.qubit device is available.
[x] Device specification for braket.aws.qubit device is available.
[x] Device specification for dummy.device is available
[x] Check validity by

[x] checking if existing file exists
[x] check if gates in "native", "decomp" and "matrix" overlap
[x] check if gates in "native", "decomp" and "matrix" do not match with those in qml.device.operations

[x] Support custom devices.
[x] decomposition to QubitUnitary may be specified by "matrix" gates in the specification.

[x] However, to maintain maximum differentiability at the moment this is overriden by the compiler.

[x] Users can specify compilation options/details, which will be taken into account by the compiler.

We don't have any compilation options at the moment that fit in this scope.

[x] Users can specify Lightning runtime options within the device loader, as allowed by the configuration, which will be taken into account at runtime (for example, MCMC sampling).

[x] options are encoded in the IR
[x] options are used in the device
[x] options are tested

[x] Documentation
[x] After discussion, do not install these files in Catalyst, have them be accessible from qml.Device.

[x] PR for changes in lightning https://github.com/PennyLaneAI/pennylane-lightning/pull/566
[x] Update dummy device to use field with path to config file.

Benefits:

Implementation of ADR. Please see ADR 73 for the details.

Possible Drawbacks:

Now tests for custom devices require toml files as well.

Related GitHub Issues:
Notes:

We should consider merging this one before https://github.com/PennyLaneAI/pennylane-lightning/pull/566 and then just changing the location of the config file once we sync up.

[sc-46420]

@dime10 feel free to add more suggestions. Will merge by the end of the day.

All good from my end 👍


video to sticker giving error

not able to convert video to a sticker @AlenSaito1

handleExit(new Error('ffmpeg exited with code ' + code));
^
Error: ffmpeg exited with code 1
at ChildProcess. (D:\Giga\Java Script\I-BOT\node_modules\fluent-ffmpeg\lib\processor.js:182:22)
at ChildProcess.emit (events.js:315:20)
at ChildProcess.EventEmitter.emit (domain.js:486:12)
at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
error Command failed with exit code 1.

Could you share a relevant code snippet and the image/video which you were converting?

const stream = await downloadContentFromMessage(
msg.videoMessage,
"video"
);
let buffer = Buffer.from([]);
for await (const chunk of stream) {
buffer = Buffer.concat([buffer, chunk]);
}
let randomName = (Math.random() + 1).toString(36).substring(7);
fileName = Media/stickers/${randomName}.mp4;
await writeFile(fileName, buffer);
}

const sticker = new Sticker(fileName, {
  pack: "I-Bot Stickers", // The pack name
  author: "I-Bot", // The author name
  type: StickerTypes.CROP, // The sticker type
  categories: ["🤩", "🎉"], // The sticker category
  id: "12345", // The sticker id
  quality: 50, // The quality of the output file
});
await sock.sendMessage(chatId, await sticker.toMessage());

}
https://user-images.githubusercontent.com/72668899/162237383-453e2bda-b9cb-496f-8714-d28f78fd4994.mp4

Thanks, I'll get back to you in a while

It worked for me. Are you on the latest version of WSF?

Thank you for the code.
It worked for me.


Allow for tern:Sample instances to exist without the need to have a tern:Sampling

Currently the tern:Sample class is a subclass of tern:Result and inherits the constraint from tern:Result.
The constraint is:

A Result requires exactly 1 sosa:isResultOf predicate.

This effectively means that all samples, whether it is used as a proxy or to represent a subset of the ultimate feature of interest must have a relationship to a tern:Sampling via the sosa:isResultOf predicate. In some cases, this requirement does not make sense and only makes the data more verbose.
There may be more cases but currently I see two main cases for using tern:Sampling:

Used in a sampling campaign, think collecting soil, fauna, or flora samples.
Used for proxy samples such as (sub-)sites and transects where you can capture the "setup" details and procedure in the sampling activity. Usually these samples are not features of interest of scientific observations but they may have sub-samples that are.

Examples - Where a sampling activity does not make sense
The "sample" highlighted in red does not meet case 1 or 2, instead it only represents the thing we are sampling with the camera trap. The current constraints for a tern:Result requires a sosa:isResultOf predicate to exist for the fauna community. If we had to create a sampling activity for the fauna community, what would be the procedure? What other properties would the sampling activity have? And what purpose is it serving?

Another example where a mandatory sampling activity does not make sense is on sampling points along transects. These sampling points are "sub-samples" of the transect but they are only there to provide intermediary information for further sub-samples that are of interest at the domain level. Such further sub-samples may be plant community, land surface, etc at a particular sampling point.
Proposal
Looking more closely at the examples from the SSN spec, most of the samples do not have an associated sampling activity.
My proposal is to change the constraint for tern:Result to optionally have a sosa:isResultOf predicate to allow for samples to exist without a link to a sampling activity.

all samples, [...] must have a relationship to a tern:Sampling

The word 'must' may be the problem here.
From an ontology perspective, it is actually 'all samples have a relationship to a tern:Sampling ' but the OWA means that it does not have to be ('must') included in any particular payload. The examples in the SSN spec reflect that.
It is only if you back up the cardinality constraint in the owl:Restriction with a SHACL that enforces this that it might be annoying.
It is unclear above whether you are proposing to change the OWL or the SHACL.

Thanks @dr-shorthair. I'm proposing to change the SHACL.

OK. The SHACL was overly strict then, for your application. Better fix it.

Thanks, I just wanted to check my thinking with you before I make any changes. I'll make a PR today or tomorrow.
FYI @miekeGR


Allow binary responses in getObject

Fixes #105

See design considerations in #105.

Hey @KOConchobhair 👋🏻
We have discussed it internally, and the maintainers agree we'd prefer the approach depicted in https://github.com/grafana/k6-jslib-aws/issues/105#issuecomment-2173486709.
If you have the capacity, we'd greatly appreciate it if you could align this PR's design. Otherwise, that's also fine, and we'd likely proceed with it ourselves. Just let us know 🙇🏻

Sorry for the delay, I was a little confused by your suggestion in https://github.com/grafana/k6-jslib-aws/issues/105#issuecomment-2173486709 since Accept is not even one of the headers listed at the S3 link. But i guess you are saying that it gives you the path to support them in the future.
I will just state that this is not an S3 API problem at all, its a very specific problem related to the inner workings of k6. So specifying an 1Accept1 header that doesn't actually change how S3 responds and only impacts the parsing on the k6 side is a little odd (but again, its putting in place the API for future stuff which is nice to not break the API again). I think this makes it a little difficult to support all types of binary headers (so we'll have to add images too, i guess image/*)
but this is a blocker for me using k6 how I want in my project so I'll implement since I'd really like to continue using k6
😄

We know this is not an official AWS header, but it is an official HTTP header, and it indicates to the server the response type you expect to receive back, so it is a good fit.
This is also why we call it additionalHeaders and not requestParameterHeaders: It allows you to add any headers to the request, not only AWS ones. Not being able to set the underlying HTTP request's headers has caused a couple of issues in this project over time. It is actually a design we could probably extend to the AWSClient itself to a certain extent.
This way of doing it feels like a better mitigation than aligning with the responseType approach of the k6 HTTP client, which is not ideal in my experience and, as we're redesigning our HTTP client, might go away in the future.
Regarding the different MIME types supported, my assumption was that using the Accept header in this case was meant more as a convention than a strict requirement we would expect S3 to comply with: " If you set the Accept header, the S3 client will return binary content, otherwise text."
I'll look at the official support AWS headers to see if another candidate I might have overlooked shows up 🙇🏻

Regarding the different MIME types supported, my assumption was that using the Accept header in this case was meant more as a convention than a strict requirement we would expect S3 to comply with: " If you set the Accept header, the S3 client will return binary content, otherwise text."

Just thinking from a k6 user perspective though, giving something as broad as an Accept header in this API which allows me to set it to { 'Accept': 'application/json' } and then have k6 interpret as binary, that would be confusing to the k6 script writer IMO.

For clarification, as mentioned in my initial comment only "Accept: application/octet-stream" would lead to the content being treated as binary.

oh duh, okay so rephrased  "If you set the Accept header (to application/octect-stream), the S3 client will return binary content, otherwise text."

Hey @KOConchobhair 👋🏻
Will you have capacity to update the PR according to our discussions? 🙇🏻
PS: I will be away for the next two weeks, but @joanlopez will be able to follow-up on this in the meantime.

this is still on my list but fell down the priority a bit, hopefully i can get back to it this week

Closing in favor of #113


Prefix Logs with Request ID

Prefix logs with the request ID, where possible.
Related changes:
Backend: https://github.com/triton-inference-server/backend/pull/60
Server: https://github.com/triton-inference-server/server/pull/4484

@rmccorm4 @GuanLuo This is now passing CI. The changes in this repo were: reverting the API version change, adding a default unknown request ID value for LogRequest(), and updating the query test to expect an unknown request ID. Please see last two commits.
(@rmccorm4 For the last one, it doesn't appear there's an easy gunit way to do "AssertIn" or substring without using other frameworks/libraries, so this may be the best use of time.)


Exporter port collision

I noticed that this exporter uses port 9248 which is reserved to gstat exporter.
While content is similar in intention, the format used and the data available is different and this exporter is not a drop-in replacement for that one, so I thing it would make sense for people (including myself) to use both while migrating dashboards, so it would be better to register a new ports specific for this exporter, so that by default they do not conflict.
-gstat_queue_depth{descr="KINGSTON SA400S37240G",fwheads="16",fwsectors="63",ident="50026B73825128F3",lunid="50026b73825128f3",mediasize="240057409536 (224G)",name="ada2",rotationrate="0",sectorsize="512"} 0.0
+geom_queue_length{device="ada2"} 0
-gstat_miliseconds_per_write{descr="KINGSTON SA400S37240G",fwheads="16",fwsectors="63",ident="50026B73825128F3",lunid="50026b73825128f3",mediasize="240057409536 (224G)",name="ada2",rotationrate="0",sectorsize="512"} 0.7
+geom_duration{device="ada2",method="write"}<PHONE_NUMBER>3172801

I chose that port number deliberately because there are very few unused ports available, and it should be very rare that somebody wants to use geom-exporter and gstat-exporter at the same time.  Migration would be an obvious exception.  But port 9248 is merely the default.  You can always override it with geom-exporter's -p option.  Is that not good enough?


rust_tokenizers support

Looking through the top tokenizer crates on crates.io, rust_tokenizers is one of the more popular ones, and allows for supporting users of this crate or the rust-bert crate.
It should be almost identical in scope to supporting the previous tokenizer crates, would be a quick win, and would allow users to use the crate without having to wrap items in a newtype to use text-splitter.
Todo:

[x] rust_tokenizers is added as an optional dependency feature
[x] ChunkSizer is implemented for Tokenizer, both by value and reference
[x] Determine is the same is also needed for MultiThreadedTokenizer, and implement for value and reference as well
[x] Generate snapshot tests for one specific tokenizer
[x] Add the same to the benchmarks as well

Is this issue closed with #145?

@anilaltuner It needs a little more cleanup, which is happening in #156, but should be almost done.
Were you looking to use this with the rust_tokenizers library? Or were you looking to help out?

it has potential on using synth data generation but more for discover and help out for right now

@anilaltuner v0.12.1 is out  with rust_tokenizers support, hopefully this helps you out!

I'll checking out, thanks for your work!


Added dark mode for the Web UI

Description
Added Dark mode for the web interface with minimum changes.

Added toggle to Options tab
Added darkreader package

Related issue https://github.com/mitmproxy/mitmproxy/issues/3886
Checklist

[x] I have updated tests where applicable.
[x] I have added an entry to the CHANGELOG.

In this PR I took into account comments from my previous PR

I appreciate the PR, but my comment in #5650 still stands: I don't want to maintain anything dark-mode related at all in my free time. I do appreciate your efforts here, but this needs to live as a user style/addon outside of the repo.


fix popup routes for FilePreview; also fix children key for breadcrumbs

Reverting the breadcrumb changes as we don't have it in FilePreview; but will keep the component key fixes.


rx_operation / rx_backgroundOperation do the same thing

They both seem to use the self.operation, which uses the shared saveContext, unless I am reading this wrong.

But rx_backgroundOperation executes the operation in background.

Yes I believe they are both using self.operation, which uses the saveContext to perform the block, so they would both be a background operation?


gl track .gitignore  (or any file starting with .git) fails with a complaint about paths

'gl track' is failing to work on any file prefixed with .git.  This is for 0.8.6, on OS X.  Examples:
$ gl track .gitignore
✘ path /Users/jhbrown/demo/.gitignore is absolute but should be relative to the repo root

$ gl track .gitx
✘ path /Users/jhbrown/demo/.gitx is absolute but should be relative to the repo root

$ gl track .xgitignore
✔ File .xgitignore is now a tracked file

$ gl --version
GL Version: 0.8.6
You can check if there's a new version of Gitless available at http://gitless.com

$ uname -a
Darwin montrose.local 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64

I'd like to take this one. The problematic line is https://github.com/sdg-mit/gitless/blob/master/gitless/cli/helpers.py#L134. I could just append a '/' to repo_dir for the starts with but I think a better condition would be is the file in the .git directory, which is what we're actually trying to check.
Further, I'm not sure I understand the else condition. Why return path if no one will be able to use it? I think this path is making the error message more confusing to users as well. Maybe it makes sense in the context of the helper functions.

There is a similar condition on https://github.com/sdg-mit/gitless/blob/master/gitless/cli/helpers.py#L121 which would stop someone from tracking a file like <repo>/.gitfiles/file. I can apply the same fix to both, because we are very specifically trying not to go in the .git/ directory exclusively.

I'd like to take this one. The problematic line is https://github.com/sdg-mit/gitless/blob/master/gitless/cli/helpers.py#L134. I could just append a '/' to repo_dir for the starts with but I think a better condition would be is the file in the .git directory, which is what we're actually trying to check.

Yes, good catch. The use of startsWith here is wrong.

Further, I'm not sure I understand the else condition. Why return path if no one will be able to use it? I think this path is making the error message more confusing to users as well. Maybe it makes sense in the context of the helper functions.

I don't understand it either. This is most likely another bug. One thing I remember is that PathProcessor is supposed to always returns paths that are relative to the repo root. The reason why we do that is because libgit2 expects paths relative to the repo root. So there are two things going on here: (1) we should skip .git, and (2) all paths we return should be relative to the repo root.
The first if seems to be doing the skipping wrong (because it is using startsWith) but the conversion looks fine (L124 & L132). The second if seems to be conflating both (1) and (2) and not doing either one correctly.

Got it! I did some research and it seems like this is a tricky thing to get right (surprise!). Here is a fun summary.
I'll try one of the simpler methods and get a fix up.


UpdateLiveStats Caching Username

Expected Behavior
Log shows correct username for the bot that is running.
Actual Behavior
Log shows username of a previous account that was used but is no longer being used anymore.
Steps to Reproduce
Run the bot using different logins (input as parameters in the terminal command), then use different accounts another day and the log is still showing the username of the previous accounts. Seems like the usernames are getting cached somewhere and not cleared out when a new instance of the bot is run.  Maybe I can remove them manually so they are recreated?
Other Information
OS: OSX
Branch: dev

Please add the exact commit you’re using

@JonnyBoy333 Still an issue?

I'll shut it down for now, will need to test more when I get a chance.


Editor says unsupported HUD was found despite no HUD being there

Whenever I try to install a HUD using the editor it says an unsupported HUD was found in my custom folder and it asks me if I want to delete it. Every time I click yes it always ends up deleting some files that are needed to even install any HUD.
EDIT: Nevermind, I just never extracted the files into my custom folder

User resolved. Closing.


Documentation for return value for submitHandler()

The documentation suggests in a submitHandler that you need to call form.submit() to continue the submission.
However 1.13.1 suggests that true / false can be used instead: https://github.com/jzaefferer/jquery-validation/releases/tag/1.13.1
Does the documentation need updating?

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.
To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!


fix typo and regular expression of algorithim

regular expression of algorithim in defs-image.json:
"pattern": "^[a-z0-9]+:[a-fA-F0-9]+$"
make descriptor.md consistent with it.
Signed-off-by: Deng Guangxing<EMAIL_ADDRESS>

40d169b2 looks good to me.

LGTM

defs-image.json is not the specification.
This was provide to allow case-insensitivity (although, we don't clarify this). If we do this, we would also have to remove [A-F] from the hex portion. In general, we should maintain that lower(digest) == upper(digest).

On Wed, Aug 31, 2016 at 01:35:01PM -0700, Stephen Day wrote:

This was provide to allow case-insensitivity (although, we don't
clarify this).

Case-insensitivity isn't hard to support, but I don't see a reason
to support it.  Can't we just require lowercase hex?

On Wed, Aug 31, 2016 at 01:44:38PM -0700, W. Trevor King wrote:

Wed, Aug 31, 2016 at 01:35:01PM -0700, Stephen Day:

This was provide to allow case-insensitivity (although, we don't
clarify this).

Case-insensitivity isn't hard to support, but I don't see a reason
to support it.  Can't we just require lowercase hex?

Actually, I'm pretty sure we don't want to support case insensitivity,
because allowing it increases the chances of two otherwise-identical
descriptor (or descriptor-containing) blobs having different hashes.
You could make the APIs case-insensitive if you really want to, but by
the time stuff makes it down to image-layout or the wire, digests
should be all lowercase.  I'd rather just require that at the API too
(with engines backed by directories on case-insensitive filesystems
taking care to downcase filenames as they read them off the disk).
It would be nice to have case-sensitive ref names too, but I don't see
an easy way to do that in storage backed by a case-insensitive
filesystem without #174.

LGTM
please rebase

rebased, waiting for the CI ;)

Sorry guys, not LGTM
The <algorithm> portion of digest needs to support tarsum.v1+sha256 definitions to at least reject them with a proper error message. We also need to be able to handle digest variations, such as sha3-256, blake2b-512 or git+sha1.
Digests in this class are valid syntactically but may not be supported.
This PR should only remove the uppercase components. We should also add a statement that a digest MUST be case flattened before parsing and verifying.

Sorry I missed the above in the initial review.

On Thu, Sep 08, 2016 at 12:40:17PM -0700, Stephen Day wrote:

The <algorithm> portion of digest needs to support
tarsum.v1+sha256 definitions to at least reject them with a proper
error message. We also need to be able to handle digest variations,
such as sha3-256, blake2b-512 or git+sha1.

With af00de09, this PR updates descriptor.md to match defs-image.json.
We want that consistency either way, but it sounds like you're asking
for [a-f0-9_+.-]+.  While we're adjusting the set of allowed
characters, are there any others that should be included?

With af00de0, this PR updates descriptor.md to match defs-image.json.

Yes, but as I said before, defs-image.json is not the specification.
I'm asking that [a-z0-9_+.-]+ (note that we cover to z here) be accepted here. This character set is similar to what is allowed by semver, so I don't see a need for expanding this further.
This provides for sufficient future proofing to defer algorithm to supportability validations rather than syntax validation. This will make for a much smoother transition if we ever encounter the dreaded break of sha256.

On Thu, Sep 08, 2016 at 01:05:07PM -0700, Stephen Day wrote:

With af00de0, this PR updates descriptor.md to match defs-image.json.

Yes, but as I said before, defs-image.json is not the specification.

Agreed, but i think everyone also agrees that the specificaiton in
descriptor.md should be changed.  I'm trying to figure out if we have
a consensus on what it should be changed to ;).

I'm asking that [a-z0-9_+.-]+ (note that we cover to z here) be
accepted here.

Sounds good.  And I'd missed the ‘z’ earlier, so thanks for pointing
it out :).

On Thu, Sep 08, 2016 at 12:40:17PM -0700, Stephen Day wrote:
The <algorithm> portion of digest needs to support
tarsum.v1+sha256 definitions to at least reject them with a proper
error message. We also need to be able to handle digest variations,
such as sha3-256, blake2b-512 or git+sha1.
this makes  [a-z0-9_+.-]+ reasonable, and thus we need to change the def-images.json as well. I think we should make them match anyway. what do others think about it?

LGTM

75a51ede looks good to me.

LGTM


As an API user, I can get the report of an individual uploaded keyword

Resolve #20
What happened 👀
Add an endpoint to get the report of an individual uploaded keyword
Insight 📝

Create KeywordSerializer and refactor the KeywordListSerializer
Re-use KeywordPresenter to get the links

Proof Of Work 📹
Found:

Not found:

@hoangmirs Do you miss some tests for this PR? 🤔


the scale value will all regression to 0.65

hello， @hujie-frank ,thanks for your great job.
But when I use se module after a normal conv layer, all the scale value regress to 0.65, are not different so obviously like in your paper, do you have any ideas? Thanks

Could you give detailed descriptions for your problem, e.g., network configuration, task, input?

Thanks.
Now I have solved the problem, but I have still some questions:

The two FC layers need biases or not?
Must I index se module after two conv layers like in the paper?
Have you try to use se module in a normal conv layer, not in res module?
At last, most of my sigmoid outputs are 0 and 1, not like in the paper, range in 0-1, is it ok?
Best regards

Besides residual architectures, we also tested it on the non-residual backbones in the paper. We presented one solution while the blocks can be implemented in a flexible manner (e.g., in the extension https://arxiv.org/pdf/1709.01507.pdf). Besides with/without biases, you can also try to add BatchNorm at the fc layers which we found work well on several backbone architectures.

Hello,
I am facing the same issue, most of the scales are 0.5, how could you solve it @ArtyZe ?
The halves mean the output is zeros so the sigmoid ouput haves which is wired, @lishen-shirley @hujie-frank Do you suggest any solutions or tricks?
I am integrating the SE-block on Resnet50.
Thanks in advance


Leave page

When exiting from a vote (Going out) there should be a "holding" page that redirects them. This should contain ad slots and info about the game with a redirect in 10 seconds or click here.

Leave page has been done


only keys with positive longitude are returned if center has positive longitude,  same with positive.

Hello
I am facing a really weird bug.
I am currently querying some geofire events with Android, and I noticed after some wasted hours of search that the geoquery returned only items with positive longitude, and not the one with negative longitude that is closed.
My code:
//FORCING LONGITUDE FOR TESTING
lastLoc.setLongitude(0.000000001);
//lastLoc.setLongitude(-0.000000001);

                Log.d("CVE", "QUERY at "+lastLoc.getLatitude()+","+lastLoc.getLongitude());
                geoFire.queryAtLocation(new GeoLocation(lastLoc.getLatitude(), lastLoc.getLongitude()), 6000.0d).addGeoQueryEventListener(new GeoQueryEventListener() {
                    @Override
                    public void onKeyEntered(final String key, final GeoLocation location) {
                        i++;
                        Log.e("CVE", i+"");

Notice the forcing at the beginning of the code.
The first case will return 12 items with positive longitude
The second one will return the only one with negative longitude
Here is an example of the data I query:

Funny thing, it seems that the error comes if I query something greater than 3000 km
I will try to give you an exact value if I have some findings


.env not setting environment variables.

Need to include better instructions around setting env variables.

Fixed.


Reloading integration deletes entities friendly names

Version of the custom_component

0.6.4
Configuration

Not relevant as it's independent from config.

Describe the bug
Steps to reproduce:

Install a plate having GPIOs configured. Switches will be imported in HA accordingly. For examle, Lanbon L8 will have switch entities like light.plate_konyha_light_12, light.plate_konyha_light_14, etc.
In HA Lovelace click on any of these entities and set a name for them. Any name like Light Bedroom Left
Go to Configuration > Devices and Services > (your plate) > 3-dots menu > Reload
Check the entities you've set name for. It will be missing, Reload function deleted the name.

Debug log

2022-01-23 21:33:53 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities openhasp.plate_konyha
2022-01-23 21:33:56 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities openhasp.plate_konyha

this is not handled by the CC...

It only happens with openHASP CC...

Added names to customize.yaml - not taken into account

customize.yaml is being deprecated, for integration based on config_entries most things already don't work

yes I know it's deprecated, just gave it a chance...
It's really annoying that for a minor change in Openhasp config you need to restart entire HA if you don't want to loose entity names :-(

Would be nice to be able to pre-set the names for these switches from the yaml configuration. That way, they will never be lost.

I think it could be set in firmware configuration :) and then I could receive it during discovery like it happens in tasiota
cc @fvanroie

Actually that would be great. Have a field in the Webif to set the names.

Perhaps "output":{{"gpio":"14","class":"light","name":"Kitchen lights"},{"gpio":"12","class":"light","name":"Kitchen cabinets"}} in the discocvery payload?
Also "Moodlight" and "Backlight" would be nice if had configurable names.

I just got hit with this as well
I don't understand why this is not a CC issue even if it could be addressed on the device side.  Under the hood, HA appears to track a device ID as a sha1 of mac address and some other system things and each entity id e.g.: switch.bathroom_switch_12 also gets it's own sha1.
Somewhere in HA it keeps track of what name the user would prefer sha1(switch.bathroom_switch_12) be known as.... unless reloading a configuration means erasing the sha1(device) and all it's children sha1(switch.bathroom_switch_12) from the HA store?
/shrug.

What would the discovery messages need to look like to handle the names?

That depends on if the CC is doing the devic reg or not.
For "basic" function like the GPIO built into a device (relays, power sensors, rgbled), i'd prefer going the "fist party" route using mqtt based auto-configuration. I did some work on the orig HASP to get some neopixels to be discovered automatically via MQTT: https://github.com/kquinsland/HASwitchPlate/blob/add-neopixels/Arduino_Sketch/HASwitchPlate/HASwitchPlate.ino#L3061
This way at least the basics of a device are accessible in HA w/o the CC and will "just work".  Of course, advanced UI stuff will still need to leverage the CC but I think there's a lot to be said for a sequence that works like this:

Install device
Connect to AP, configure real wifi/mqtt
New device page with toggle switches for the relays, backlight, moodlight show up
New sensor for power use shows up

Also a side effect: reloading the integration sometimes renames the main entity openhasp.plate_35 to something like openhasp.plate_35_2. I remember having something similar back in the summer, when entity IDs of the switches were renamed with _2 after certain scenarios (not reload), but @dgomes fixed that.

Also a side effect

This was caused by the plate running on a different IP address than at the time it was configured. Removed the plate from integrations, re-discovered and reloading config doesn't seem to rename the entity anymore.

Seems fixed but it only works on latest HA beta version 2022.2.b
number entity fails on HA versions prior to that

Reloading itself actually broke. Plate and HA loose connection.

Also a side effect

This was caused by the plate running on a different IP address than at the time it was configured. Removed the plate from integrations, re-discovered and reloading config doesn't seem to rename the entity anymore.

My DHCP server is pretty sticky. The device that I renamed the entities on and then reloaded the config for did not restart or otherwise get a new IP address.


Add serializer and display of serializer

It would be best if we included it in an endpoint with pagination.

Fixed by ab77d467a1cce3617d37e9358d1ede20105332eb


Blog: Using Admission Controllers to Detect Container Drift at Runtime

This PR adds a new blog post about using K8s admission controllers to detect container drift at runtime.

@sftim @onlydole The PR is ready for your review. Thank you for your time!
/assign @onlydole

/hold
publication date not yet set (SIG Docs blog can take care of this)

Or rather, there is a date set but we need to update it so that it's in the future (or the same day) when we merge.

Or rather, there is a date set but we need to update it so that it's in the future (or the same day) when we merge.

Thanks for your comments above @sftim. Is there anything I can work on to help set the publication date?

@dilyar85 I'm not sure what you're asking. You're welcome to suggest a publication date by looking at https://github.com/kubernetes/website/projects/11 and planning around:

scheduled articles
major events like KubeCon

Another way to help the blog team, the people who review and approve these articles, is to help out by providing informal reviews on the other open PRs for blogs. It might sound obvious or counter-intuitive; I'm not sure. Offering your time like that helps move your blog's approval forward because the less review work that remains overall, the more the blog team have time to review your PR.

@sftim Thanks again for your detailed review above. I believe all your comments should be addressed now in the last two commits.
I was wondering if we also have an estimated publication date for this blog, so that I can go ahead and update the file names and the frontmatter (metadata) information in the markdown file?

We're getting close to a Kubernetes release (for which articles are already planned), so how about the 21st of December?
Once you set that date, please squash commits.

We're getting close to a Kubernetes release (for which articles are already planned), so how about the 21st of December?
Once you set that date, please squash commits.

@sftim December 21st sounds perfect to us. I have put this date in the blog post and squashed all commits as required.
Please feel free to ping me if you need anything else from our side to get this published. We are looking forward to seeing this on K8s blog soon. Thanks!

/lgtm

@karenhchu is this date OK with you as well?

@karenhchu is this date OK with you as well?

Yup, it will not clash with my feature blog series which should have its last blog published on 12/16.

Thanks @karenhchu
/approve

/hold cancel

@sftim Thanks again for approving this!


VM sends wrong pause events to debugger

Originally posted here https://github.com/Dart-Code/Dart-Code/issues/3336
Describe the bug
Debugger doesn't hit breakpoint and jumps somewhere else and runs into loop instead (you can't unpause without removing the breakpoint)
To Reproduce

Copy the code below
Go to NestedScrollView source code
Set a breakpoint somewhere in _getMetrics method (from line 955 to 1000)
See that that the debugger loops into this line instead https://github.com/flutter/flutter/blob/ff15d04f214ae7cc4ffbacde2faefa1772e112e4/packages/flutter/lib/src/widgets/nested_scroll_view.dart#L1346

Code sample
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: NestedScrollViewExample(),
      // home: CustomScrollViewExample(),
    );
  }
}

class NestedScrollViewExample extends StatelessWidget {
  NestedScrollViewExample({Key key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: NestedScrollView(
        physics: ClampingScrollPhysics(),
        floatHeaderSlivers: true,
        headerSliverBuilder: (context, innerBoxIsScrolled) => [
          SliverAppBar(
            // floating: true,
            expandedHeight: 250.0,
            elevation: 0.0,
            forceElevated: false,
            flexibleSpace: FlexibleSpaceBar(
              title: Text('Demo'),
            ),
          ),
        ],
        body: CustomScrollView(
          slivers: <Widget>[
            SliverPadding(
              padding: const EdgeInsets.all(8.0),
              sliver: SliverFixedExtentList(
                itemExtent: 48.0,
                delegate: SliverChildBuilderDelegate(
                  (BuildContext context, int index) {
                    return ListTile(
                      title: Text('Item $index'),
                    );
                  },
                  childCount: 30,
                ),
              ),
            ),
          ],
        ),
      ),
    );
  }
}

class CustomScrollViewExample extends StatelessWidget {
  CustomScrollViewExample({Key key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: CustomScrollView(
        slivers: <Widget>[
          SliverAppBar(
            floating: true,
            expandedHeight: 250.0,
            elevation: 0.0,
            forceElevated: false,
            flexibleSpace: FlexibleSpaceBar(
              title: Text('Demo'),
            ),
          ),
          SliverPadding(
            padding: const EdgeInsets.all(8.0),
            sliver: SliverFixedExtentList(
              itemExtent: 48.0,
              delegate: SliverChildBuilderDelegate(
                (BuildContext context, int index) {
                  return ListTile(
                    title: Text('Item $index'),
                  );
                },
                childCount: 30,
              ),
            ),
          ),
        ],
      ),
    );
  }
}

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):

flutter doctor -v
[√] Flutter (Channel unknown, 2.3.0-2.0.pre.94, on Microsoft Windows [Version 10.0.19041.928], locale ru-RU)
    • Flutter version 2.3.0-2.0.pre.94 at C:\dev\src\flutter
    • Upstream repository unknown
    • Framework revision 3009bb3ffa (13 hours ago), 2021-05-11 14:11:03 +0300
    • Engine revision 1825befbc7
    • Dart version 2.14.0 (build 2.14.0-74.0.dev)

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\danya\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.7.7)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.7.30621.155
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] IntelliJ IDEA Community Edition (version 2020.3)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.3.3
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart

[√] VS Code (version 1.56.1)
    • VS Code at C:\Users\danya\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.22.0

[√] Connected device (4 available)
    • sdk gphone x86 (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • Windows (desktop)       • windows       • windows-x64    • Microsoft Windows [Version 10.0.19041.928]
    • Chrome (web)            • chrome        • web-javascript • Google Chrome 90.0.4430.93
    • Edge (web)              • edge          • web-javascript • Microsoft Edge 90.0.818.46

• No issues found!

Logs
Dart-Code-Log-2021-04-03 03-09-17.txt
PS while writing this issue, after I already stopped capturing logs, got this in the console
[+168893 ms] org-dartlang-debug:synthetic_debug_expression:1:1: Error: The getter 'hasPixels' isn't defined for the class '_NestedScrollController'.
[        ]  - '_NestedScrollController' is from 'package:flutter/src/widgets/nested_scroll_view.dart' ('../../src/flutter/packages/flutter/lib/src/widgets/nested_scroll_view.dart').
[        ] Try correcting the name to the name of an existing getter, or defining a getter or field named 'hasPixels'.
[        ] hasPixels
[        ] ^^^^^^^^^
[+18956 ms] org-dartlang-debug:synthetic_debug_expression:1:1: Error: 'class' can't be used as an identifier because it's a keyword.
[        ] Try renaming this to be an identifier that isn't a keyword.
[        ] class
[        ] ^^^^^
[        ] org-dartlang-debug:synthetic_debug_expression:1:1: Error: The getter 'class' isn't defined for the class '_NestedScrollController'.
[        ]  - '_NestedScrollController' is from 'package:flutter/src/widgets/nested_scroll_view.dart' ('../../src/flutter/packages/flutter/lib/src/widgets/nested_scroll_view.dart').
[        ] Try correcting the name to the name of an existing getter, or defining a getter or field named 'class'.
[        ] class
[        ] ^^^^^
[+16378 ms] org-dartlang-debug:synthetic_debug_expression:1:1: Error: The getter '_getMetrics' isn't defined for the class '_NestedScrollController'.
[        ]  - '_NestedScrollController' is from 'package:flutter/src/widgets/nested_scroll_view.dart' ('../../src/flutter/packages/flutter/lib/src/widgets/nested_scroll_view.dart').
[        ] Try correcting the name to the name of an existing getter, or defining a getter or field named '_getMetrics'.
[        ] _getMetrics
[        ] ^^^^^^^^^^^
[+3649 ms] org-dartlang-debug:synthetic_debug_expression:1:7: Error: Expected '(' before this.
[        ] assert
[        ]       ^...
[        ] org-dartlang-debug:synthetic_debug_expression:1:1: Error: `assert` can't be used as an expression.
[        ] assert
[        ] ^^^^^^
[+44612 ms] org-dartlang-debug:synthetic_debug_expression:1:1: Error: Expected an identifier, but got '.'.
[        ] Try inserting an identifier before '.'.
[        ] .minScrollExtent
[        ] ^

See https://github.com/Dart-Code/Dart-Code/issues/3336#issuecomment-904650238 for more details
cc @DanTup

/cc @bkonyi @cskau-g

I was also able to reproduce the issue in Android Studio.
But I seem to get slightly different behaviour with flutter run + Observatory. Notably, setting a breakpoint in _getMetrics results in an Observatory error:
Unexpected exception: ServerRpcException(getSourceReport: invalid 'tokenPos' parameter: -29336)
And I notice the nestedPositions code isn't marked possibleBreakpoint (i.e. there's no B in the left margin):

This indicates to me something 's not right in the VM debugger interface (which I'm less familiar with) - though it's possible that issue is triggered by some underlying sync* issue.

Actually, the issue seems more clear in Flutter DevTools where if you try set a breakpoint on any line prior to line 1342 the resulting breakpoint will always be for nested_scroll_view.dart:1342.

Aha, I've inspecting the requests from Flutter DevTools and something seems to go wrong in the addBreakpoint request handling.
The initial getObject and getSourceReport requests result in Script and SourceReport responses that look entirely reasonable with tokenPosTable and ranges (possibleBreakpoints) within the expected ranges.
So when I attempt to set a breakpoint on a line prior to 1342 the request correctly sends e.g. line: 361.
But the response I get back has tokenPos: 51653 which is clearly wrong.


How to detect when new text was extracted in watch mode?

I'm trying to do hot reloading of extracted CSS (so that dev and prod have the exact same CSS), and that's working, but I'm having trouble figuring out when there was a change to the CSS.
I tried attaching to "after-emit", but I can't really see what I should filter on to detect if a css file was rebuilt in the current compilation run.
Any hints? Maybe a special event should be emitted?

@wmertens seems add event is good solution. Can your write PR this for this?

@evilebottnawi I'd gladly create a PR but I don't know how to know when a text file was changed.

@wmertens in theory we can store hash of extracted files and when compare them with new extracted files, what do your think about this?

If you are already creating a hash, that would be great; if not, it seems
that there could be a more direct way somehow? Like keeping a list of files
that were output in this compile?
On Fri, Aug 18, 2017 at 12:48 PM Evilebot Tnawi<EMAIL_ADDRESS>wrote:

@wmertens https://github.com/wmertens in theory we can store hash of
extracted files and when compare them with new extracted files, what do
your think about this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/webpack-contrib/extract-text-webpack-plugin/issues/577#issuecomment-323322553,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADWllQ7zWR-VRPxaSPfRfUGjxEopQXWks5sZWvlgaJpZM4OfQ_e
.

@wmertens we already have content have https://github.com/webpack-contrib/extract-text-webpack-plugin/blob/master/src/index.js#L209

@wmertens btw can your describe more informatively why it is needs?

It seems that hash only gets created on-demand, so it would be a shame to
create it every time…
I tried to describe my use case above. I need to know when a CSS file was
emitted, so that I can tell the browser to hot-reload it. Right now I'm hot
reloading every time, which is annoying…
On Fri, Aug 18, 2017 at 1:14 PM Evilebot Tnawi<EMAIL_ADDRESS>wrote:

@wmertens https://github.com/wmertens btw can your describe more
informatively why it is needs?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/webpack-contrib/extract-text-webpack-plugin/issues/577#issuecomment-323327260,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADWlsEI5l7lqpaW_UdDMLTEYdIV1mhjks5sZXIvgaJpZM4OfQ_e
.

@wmertens why don't store hash of files directly in webpack-hot-middleware?

If I can get the hashes of all files after a compile was done, and know which ones were generated by extract-text-plugin, that would be great. Then I can indeed track hashes and emit on change.
But I don't know how to do that, which events to listen to…

ETWP entered maintenance mode and won't receive any feature updates, please open an issue in mini-css-extract-plugin instead


Enable AccessKit and update dependencies

Turn on the AccessKit dependency and also update to more recent glazier and Vello versions.
Also follow new policy of pinning git dependencies to avoid future breakage.

Yup, quite a few changes are similar. I don't have strong feelings about the order, if we want to land this I can rebase #26 (which has #36 in its commit change). This one pins to a more recent version which has some changes to gradient encoding, so we definitely want that change but on the other hand it isn't urgent.


IE11. Object doesn't support property or method 'repeat'

Describe the bug
When throwing an error using JS throw during IE11 development, the following script error dialog occurs:
Object doesn't support property or method 'repeat'

It is similar to the issue #8438 and #8405 except that it is in reference to repeat from String.prototype.repeat instead of entries from Object.entries.
The Object.entries issue was fixed in a CRA fork https://github.com/EverlongProject/create-react-app/pull/9. A similar fix might be needed for String.prototype.repeat.
The problem does not resolve itself when adding core-js package.
Did you try recovering your dependencies?
No
Which terms did you search for?
A combination of "object support repeat" in the GitHub issues.
Environment
npx: installed 98 in 6.932s
Environment Info:
  current version of create-react-app: 3.4.1
  running from C:\Users\Nathan\AppData\Roaming\npm-cache\_npx\35912\node_modules\create-react-app

  System:
    OS: Windows 10 10.0.18363
    CPU: (12) x64 Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
  Binaries:
    Node: 12.16.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.14.4 - C:\Users\Nathan\AppData\Roaming\npm\npm.CMD
  Browsers:
    Edge: 44.18362.449.0
    Internet Explorer: 11.0.18362.1
  npmPackages:
    react: ^16.13.1 => 16.13.1
    react-dom: ^16.13.1 => 16.13.1
    react-scripts: 3.4.1 => 3.4.1
  npmGlobalPackages:
    create-react-app: Not Found

Steps to reproduce

Add this to the constructor of App.js:

setTimeout(() => { throw new Error("Test throw!!"); }, 3000);

Open and view in IE11 and wait 3 seconds

Expected behavior
It should show the react error screen.
Actual behavior
Internet Explorer 11 shows an script error dialog containing the following:
errorLine (1)
errorCharacter (250504)
errorCode (0)
errorMessage (Object doesn't support property or method 'repeat')

Reproducible demo
None

Hey, Are you using "immer", the produce method of immer was causing issue for me.

@nikhiltech I am running into this same issue and am on immer - were you able to find a workaround?

@nikhiltech never mind! I updated to v 6.0.9 of immer and it seems to be working now.

I have the same problem. How did you solve it？I suspect I used React.Provider， but I don't know how to solve it

@littleLuyx use import { enableES5 } from "immer"; enableES5();
where you are using immer

@littleLuyx use import { enableES5 } from "immer"; enableES5();
where you are using immer

Thank you. It's very instructive. I didn't use immer in my document, but I was prompted with syntax errors. Finally, I introduced core JS to solve this problem

I was not using immer.


Division by zero in file: setup.php

any idea what is causing this?

2021/03/06 14:50:07 - CMDPHP PHP ERROR WARNING Backtrace: (/poller.php[699]:process_poller_output(), /lib/poller.php[544]:api_plugin_hook_function(), /lib/plugins.php[130]:api_plugin_run_plugin_hook_function(), /lib/plugins.php[237]:weathermap_poller_output(), /plugins/weathermap/setup.php[728]:CactiErrorHandler())
--
2021/03/06 14:50:07 - ERROR PHP WARNING in Plugin 'weathermap': Division by zero in file: /var/www/localhost/htdocs/cacti/plugins/weathermap/setup.php on line: 728

I think was related to other system performance issues


Avoid eval in cloneRegex

The main reason to replace eval is for better static analysis. Build tools such as rollup spit warnings about the use of local eval.
Not only that, but eval seems to be slower in some situations. It's also a lot faster to just return the passed in RegExp if it has the global flag already set -  no need to "clone".

Why hasn't this been merged yet?

What's the plan with this pull request?


[Question]: Issue with a missing Assets/Static folder

I'm currently attempting to serve an ebook file and am getting an exception when attempting to initialize an EPUBNavigatorViewController here
Effectively it seems like the URL [Bundle.module.resourceURL]/Assets/Static doesn't exist, which causes the exception. I'm not sure what would be causing this. Based on my limited understanding of whats going on Assets/Static is the directory the EPUB web assets get unpacked into. So is this a problem with the epub file being improperly unzipped which is resulting in this issue?
Thanks in advance!

Could you open a new issue following the Bug Report template, and adding as much details as possible regarding how you integrate Readium in your app?
The whole Assets folder in R2Navigator is supposed to be embedded in your app bundle as a resource folder.

@mickael-menu thanks a bunch for your response! I've created a new issue which conforms to the bug template, let me know if there's anything else I can provide and again, thanks a bunch for your help, I know my question is unusual given the way I'm using Readium.
https://github.com/readium/swift-toolkit/issues/74


URange's UI breaks after a certain value

Environment
N/A
Version
v2.18.3
Reproduction
N/A
Description
If you look closely to the slider in the docs page: https://ui.nuxt.com/components/range
The slider looks okay when a lower value is set:

If the value is set around the maximum (>=95 ish?), the design breaks:

Which is even more visible when the value is 100:

And it's prominent when the size is set to 2xl:

Also notice that the foreground isn't respecting the border radius of the "container"
Additional context
No response
Logs
No response

can u send your template?

try this
<URange size="2xl" v-model="value" class="m-10" :ui="{ progress: { rounded: 'rounded-full' } }" />

i dont understand what is broken when >=95


Font list in CSV format?

Thanks for providing these font lists!
I'd be nice if these font lists could be downloaded in a machine-readable form, like CSV.

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

ID: 0c0610f6-7c7b-b771-e635-84663af729db
Version Independent ID: 50a9b23c-733c-c934-95dc-0bbd5d502fea
Content: Font List Windows 10 - Typography
Content Source: typographydocs/fonts/Windows_10_Font_List.md
Product: typography
GitHub Login: @nihar
Microsoft Alias: nihar

Thank you for the feedback. I will look into this in the future updates.


RFC-060 gem metadata MVP

Implements RFC-60 'gem' keyword in metadata.rb

neat :-)

https://github.com/bundler/bundler/pull/4245 would be useful to leverage bundler/inline while still cleaning up the output format.

@chef/client-core this is probably good for review now.
travis will be busted right now due to github-changelog-generator.
bundler hasn't yet done a release, but it'll work fine without the bundler release, it just won't have nice output.
halite still has the busted spec due to needing to update bundler (test failure for halite, everything works fine) so it is moved to excluded for now.

:+1:

Awesome! :+1:

:+1: Side note, would like to get a workaround for the changelog generator thing so we can trust travis. We did this for ChefDK: https://github.com/chef/chef-dk/pull/704/files

@lamont-granquist We still need to do the Bundle.require bit secondarily, right?

you mean like gem "foo", require: "foo.rb"?  yeah, it does no automatic chef-tie-ing...

:+1: It's a good thing for a second round PR, just shouldn't forget about it :)

I thought we decided not to cheftie automagically, though?
You've got the whole Bundler gem API available, so required does work.  Even arguments like git and github should work provided the images that are used are prebaked with git.

We decided to not do any weird file-scanning like my code does in favor of a single Bundler.require call after installation. Without that, no code from the installed gems is actually loaded.

Ah, so Bundler#require is here and is basically
https://github.com/bundler/bundler/blob/master/lib/bundler.rb#L101-L103
I believe we're getting the same Bundler::Require.setup.require call sequence through here:
https://github.com/bundler/bundler/blob/master/lib/bundler/inline.rb#L59-L60
We definitely get the gems installed, and I (manually) tested that requiring worked...


Hardwire admin UI URL prefix

When the admin UI was first written, we wanted to allow for the possibility that
the frontend web server would do URL rewriting to expose it at a different path.
We thus needed to be able to easily change the path that was included in links
and form actions.
This has turned out not to be needed. Passing the prefix around and using it
everywhere adds noise to the templates and the controller classes.
Update AdminController to stop including the prefix in the models that get passed
to the templates, and update the templates to directly use /admin in their URL
paths. In many cases, this means attributes such as href can be string literals
instead of Thymeleaf expressions.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #1599

PR #1600

PR #1601   👈

PR #1602

This stack of pull requests is managed by Graphite.

Merge activity

Jan 4, 5:59 PM: @sgrimm started a stack merge that includes this pull request via Graphite.


Update f95d394f-fbed-8d64-143d-a51368df158c.md

Was looking for Microsoft VBA documentation, but apparently Microsoft can't be bothered documenting VBA any more, or providing help from the VBA editor, and now leaves it up to users to fix the documentation that does exist.

Hi @dickwatson, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Thank you for your feedback. We’ve made our VBA documentation available on GitHub to enable the community to engage with and contribute to the content. We are committed to continuously improving the documentation in response to feedback from our community. This new model will help us to be more responsive to community input.
We will review your changes and respond to them shortly.

I’m great with that as long as MS is still taking the lead in doing things like structuring and so forth—the page in question should have, for consistency, a Methods page with two methods, but I’m not going to go to all that trouble to figure out how to do that.
Yes, using the GitHub docs as a vehicle to correct or extend the docs is great. Just leaving it up to users to figure out what’s fundamentally missing, e.g., that the Debug object has methods and how they work, I’m not OK with. I’m pretty sure Debug.Assert used to be in VBA reference help in the good old days.
From: Laura Graham<EMAIL_ADDRESS>Sent: Thursday, November 5, 2015 8:56 AM
To: OfficeDev/VBA-content<EMAIL_ADDRESS>Cc: dickwatson<EMAIL_ADDRESS>Subject: Re: [VBA-content] Update f95d394f-fbed-8d64-143d-a51368df158c.md (#92)
Thank you for your feedback. We’ve made our VBA documentation available on GitHub to enable the community to engage with and contribute to the content. We are committed to continuously improving the documentation in response to feedback from our community. This new model will help us to be more responsive to community input.
We will review your changes and respond to them shortly.
—
Reply to this email directly or view it on GitHub https://github.com/OfficeDev/VBA-content/pull/92#issuecomment-154152316 .  https://github.com/notifications/beacon/AO6o1Ajwz6TW9VSwHiilZMmfZuAauB_Kks5pC52ygaJpZM4GbUHW.gif


Reduce the resolution of Dot3D

Enhancement proposal
Currently, Dot3D uses the default Sphere resolution of (12, 24). Running a scene with lots of Dot3Ds, like a scene with polyhedra, takes incredibly long because of the high resolution. I think a resolution of (8, 8) is a good balance between speed and visual looks. After changing the resolution, the control data for some tests have to be regenerated.
Additional comments

Hi! Can I pick up this issue ? I am a newbie to this project and would like to contribute whatever I can!

Sure! I've assigned to this issue 👍


MSVC JSON: mix serialize and save_minimal error

Hi everyone,
I ran into a runtime issue with the JSON archives on visual studio express 2013. It seems like I can not mix serialize and save_minimal functions when serializing hierarchical types. Here is a reproducer:
#include <stdio.h>
#include <stdint.h>
#include <cereal/archives/json.hpp>

template <typename T>
struct foo
{
	T value;
};

template<class Archive, typename T>
T save_minimal(const Archive&, const foo<T>& v)
{
	return v.value;
}

/*
// This version works.
template<class Archive, typename T>
void serialize(Archive & archive, foo<T>& v)
{
	archive(v.value);
}
*/

struct bar
{
	foo<uint8_t> v1;
	foo<uint8_t> v2;
	foo<uint16_t> v3;
	foo<uint8_t> v4;
};

template<class Archive>
void serialize(Archive & archive, bar& m)
{
	archive(::cereal::make_nvp("v1", m.v1));
	archive(::cereal::make_nvp("v2", m.v2));
	archive(::cereal::make_nvp("v3", m.v3));
	archive(::cereal::make_nvp("v4", m.v4));
}

int main(void)
{
	bar b;
	// Serialize to stream.
	std::ostringstream out;
	{
		cereal::JSONOutputArchive outArchive(out);
		outArchive(::cereal::make_nvp("param", b));
	}
}

This crashes when writing the third value. I started debugging and it seems like it is not considering the fact that the values serialized with save_minimal don't have a name. In writeName the first line popping the stack seems to fail because the stack is zero. The portable binary archive seems to work.
I hope somebody can reproduce this and help fix the issue.
Best,
Sebastian

The same code works fine on Linux with gcc 4.8.3.

I'll take a look at this - can confirm it works correctly on Linux.

Azoth, thanks for looking into this. Did you make any progress - could you reproduce the problem?

I can reproduce this on MSVC2013.

Seems that the minimal serialization is incorrectly entering the non-minimal epilogue for foo<unsigned char>.
The type traits correctly return false for arithmetic, false for having a minimal base class serialization, and true for having a minimal output serialization.  These OR together to give a true value to DisableIf, which should turn off the function if all of its arguments (in this case only the result of the OR) evaluate to true.
There's some kind of bug with MSVC here where it isn't evaluating the OR properly for whatever reason.  We can get around this error by putting parenthesis around at least the std::is_arithmetic<T>::value portion of the test.
Should be able to check in a fix for this tomorrow sometime.  I'll have to look around and see if there are any other EnableIf/DisableIf that MSVC might have some issue with.

This sounds exactly right @AzothAmmo. I could track it down to it entering the non-minimal epilogue and it trying to erase a name that was not there because for the prologue the minimal path was taken. Unfortunately my investigation ended there.
Very happy you're looking into this!

Fixed on develop, will organize issues and milestones to get recently done changes pushed out sooner rather than later.


Label selector argument

Added label selector to filter out what exact objects to scan, a proposed by @dohnto-s1
Added as --selector, because -l (the same as in kubectl) is already occupied
Will close #62

Otherwise LGTM, I verified it for my use case and it works as expected.


Add per-band options for rpc bus connection parallelism

Set requst multiplexing parallelism in chunk client

Add for RPC bus band config options for range of multiplexing parallelism

Motivation: required connection parallelism more depends on cluster topology.
It's easier to provide configuration on this level than fixing all possible initiators.

Shipped!

Let's run some tests just in case


Look at supporting msgpack-RPC

After reading this it seems like we're pretty close to supporting msgpack-rpc for the message pack flavor of our protocol:
https://github.com/msgpack-rpc/msgpack-rpc/blob/master/spec.md
I haven't dug in but it might be possible to support this directly as a subset of our msg pack protocol or have it be another protocol.
/cc @moozzyk @anurse

JSON-RPC?

Look forward to see msgpack-rpc for CSharp. I found the current RPC library is gRPC in CSharp field. But msgpack's performance looks better.


Allow jquery 1.x to be used

The existing version is over-specific. jquery >= 1.11.x (1.11.1 for example) works just fine

did you try materializecss with jquery 1.11?
i got some errors and some features didn't work.

What is the reason people need to use the old jquery version? The framework is only tested on the jQuery 2 versions although it may work on older versions.

IE8 support.

Because they want a better browser compatibility.
I think it would be useful to have a JSBin using JQuery 1.11 to show errors if they are.


Improved kill icons mod

...

Assuming this is a suggest addition, I'm fairly hesitant to add something like this because it would be borrowed from someone else (and it appears it's been reuploaded a number of times, as well). I try to limit how many things I add to the hud that I don't more or less have direct control over, and I leave that instead to people who want to customize TF2 further.


Script for collecting information

Create a script to collect information about the courses and insert them into the database.

https://github.com/henrikbossart/courseTracker/commit/9b14f4af3d2c044612737d690df8536730da0f6f


SelectRegion masking data

The edit_radar script is not working (_parse_dir is not imported). It is also making absolute imports, that is not recommended.

Darn, I didn't notice this comment until after merge.
I'll need to look into this, and fix.

These are addressed in PR #106


New Securtiy TRG´s

Hi All,
Can you please tell me what you think? Do you have any feedback regarding our TRG?

Hi @klaudiaZF,
thanks for your input and your work, overall really needfull information.
Guess your title of the PR for TRG is a bit missleading maybe add new securtiy trg´s 😉
feedback:

trg 8-3 is IMHO a guideline how to use your repo and how to contact you and i would move it to the README.md for sig-security
for the other to new TRG´s (Tractus-X Release Guidelines) i questioned myself, is this full needed for the upcomming release or is this just an information, how to use the security tools and process to check?

IMHO such information which tools we have to use should be explicit mentioned as "you have to" like should / must do this for the release.

Hi @FaGru3n it's not new, because we didn't add any security TRG yet
trg 8-3 is providing a steps and in our README file we have only information and links
Is an information how to use security tools and process
I move it to the right place... sorry for that

Thank you for that ...
👍🏼


grounded_sam_simple_demo.py no CUDA accelerated

Hi everyone!
I was testing grounded_sam_simple_demo.py and got surprised about set_image computing time. After checking, it's missing a line to send the model to CUDA devide. After line 25 there should be something like this:
sam.to(device=DEVICE)
Hope it is useful!

Hi everyone!
I was testing grounded_sam_simple_demo.py and got surprised about set_image computing time. After checking, it's missing a line to send the model to CUDA devide. After line 25 there should be something like this:
sam.to(device=DEVICE)
Hope it is useful!

Thanks for fixing this!

@dankresio @rentainhe Hello!
I changed sam.to(device=DEVICE) some days ago and I get a mask of one image within 2.5-2.7 seconds. But then I tried to set grounding_dino_model.to(device=DEVICE) to accelerate the prediction, but I got this error.
AttributeError: 'Model' object has no attribute 'to'
The detection of objects with testing prompt using grounding_dino_model for one image takes now 10-11 seconds. Is there some way to accelerate the prediction and reduce the time for groundingdino model ?

Hi @HripsimeS,
Method "to" is only available when the class inherits from parent nn.Module such as Sam class here.
If you check grounding DINO initialization you can check

it doesn't inherit from nn.Module
__init__ method includes device attribute and is default to "cuda"

Hope it helps!

@dankresio thank you very much for your reply! So it is already on GPU device settled. But is there some solution to make the inference of GroundingDino model faster, currently it takes 10-11 seconds/image with GPU type A100.
Can you please advice me how I can reduce the inference time for groundingdino model. Thanks a lot in advance!

@HripsimeS check if the model is loading on GPU because this inference time with an A100 is huge. I have a GT1070 and G-DINO inference timpe is arount 2.67 seconds.
PS: check RAM vs GPU usage when inferencing with G-DINO and there you will get the answer

@dankresio thanks for the advice. I use Google Colab's GPU. How to check if the model is loading on GPU?
Normally I used this command to see if GPU is available torch.cuda.is_available()
Is there some python command that allows to check RAM vs GPU usage on Google Golab?

@dankresio thanks for your advice. I used GPU of Google Colab and below you can find results for one image. I would love to reduce the GroundingDino inference time to 1-2 seconds, but don't know how to do on Google Colab.

And this is for SAM model, much faster than GroundingDino model

Hi @HripsimeS I think it is an optimization issue regarding the wrapper class gor G-DINO.
Try running grounded_sam_demo.py just for de G-DINO inference. In my machine, it reduces inference time x3:

Inference G-DINO: 1.115
Run it a tell me if this improves execution time :smiley:

@danigarciaoca thanks a lot for your advice, indeed using the grounded_sam_demo.py made a fantastic change for both GroundingDino and SAM models. You can see results below 🥇 👍


[FLINK-4460] Side Outputs in Flink

FLIP-13 Expose sideOutput with OutputTag<T>,
For those userFunction provide Collector<OUT> collector as a parameter,

it offer a util classCollectorWrapper<OUT> wrapper = new CollectorWrapper<OUT>(collector); which can write sideOutput element wrapper.collect(OutputTag<SIDEOUT> tag, sideout) as well as getSideOutput(OutputTag<SIDEOUT> tag) in singleStreamOutputOpeator and get sideOutput DataStream.
each OutputTag with same type can have different value, getSideOutput will only expose element with exact same OutputTag type and value.

sideOutput Late arriving event if

time characteristic set to eventTime
all assigned window(s) isLate return(s) true
event timestamp no later than currentWatermark+ allowedLateness)

cc @aljoscha

@chenqin I had a quick look at the implementation and it looks quite good. I'll look at it in more detail once the 1.2 release is out and then I'll also have more thorough comments.
These are some quick comments off the top of my head:

I think we can extend Collector with a collect(OutputTag, T) method. Then we wouldn't need the extra RichCollector and CollectorWrapper to work around that.
For WindowedStream I would like to have something like this:

OutputTag<T> lateElementsOutput = ...;
DataStream<T> input = ...
SingleOutputStreamOperator<O> windowed = input
  .keyBy(...)
  .window(...)
  .apply(Function, lateElementsOutput);

DataStream<T> lateElements = windowed.getSideOutput(lateElementsOutput);

or maube something else if we find a better Idea. With the WindowedStream.tooLateElements() this would instantiate an extra WindowOperator just for getting late elements while another window operator would be responsible for processing the actual elements. That seems wasteful.
What do you think?

@aljoscha Thanks for your time. We can chat more after 1.2 release!
I think it makes sense to extends Collector, even though we may not remove collect(T obj) due to API compability issue in 1.X. Per @fhueske comments in FLIP-13 email thread
Only point I would like to add: there seems decent amount of refactor to replace underlining output chains using collect(tag, element), yet seems reasonable investment moving forward (multiple inputs/ multiple outputs)
tooLateEvents() method is something added for user's convenience. should be fine to remove if doesn't gain much benefit. LateArrivingTag share same type as input (which is like already fixed once input type defined). Add late arriving tag within apply method seems redudant. In fact, without any changes to this diff, user also be able to access late arriving events via following way.
`
OutputTag lateElementsOutput = new LateArrivingOutputTag();
DataStream input = ...
SingleOutputStreamOperator windowed = input
.keyBy(...)
.window(...)
.apply(Function);
DataStream lateElements = windowed.getSideOutput(lateElementsOutput);
`
Thanks,
Chen

@aljoscha,
diff has been updated and merged to support apply(Function, lateElementsOutput);
Collector refactor seems not viable option as stated above.
Seems travis-ci timeouted here, is there a way to increase timeout setting?
https://travis-ci.org/chenqin/flink/builds/201329246
Chen

@chenqin
I rebased and consolidated your PR a bit and played around with the APIs.
Some of the changes:

Separation into internal changes/window operator changes and user-function changes. I have a prototype commit that exposes side outputs using ProcessFunction.
I removed CollectorWrapper/RichCollector in favour of the ProcessFunction approach
The internal implementation now doesn't store the OutputTag on the StreamRecord but instead adds an additional method on Output that should be used for emitting data to a side output. Side outputs now also work with chaining.
WindowedStream is changed to add a sideOutputLateData() method that is used to specify that late data side output is required. This is more general than putting it into the method signature of apply() because it will simply work for all different window types.

I quickly talked to @StephanEwen and we agreed that we need to further think about how we want to expose side outputs for user-defined functions. Especially, we have to think about what this addition means for the split()/select() pattern. I will also do another change where sideOutputLateData() is not required but instead will be added when the late-date stream is requested.
What do you think?

@aljoscha Looks good to me 👍
I briefly looked at your git branch, a minor comment would be adding comments to sideOutputLateData so user get better idea when they opt-in to late arriving event stream.
Initial late arriving event is decided by comparing watermark & eventTime, do you think there is a need to allow user pass a kinda Evaluator and enable user sideOutput any kind of sideOutputs?
window.sideOutput(OutputTag<IN>, Evaluator)
interface Evaluator{ MergedWindows, key, watermark}

Regarding split select, I think there is a chance of consolidate select and build upon OutputTag, but might be out of this PR's scope.
Regarding to WindowStream, I am a bit confused to figure out  if I use allowedlateness and  sideOutputLateData at same time.

Thanks,
Chen

Thanks for looking at that! I'll open a new discussion thread on the Mailing lists to discuss Side Outputs and split/select and how we're going to proceed with that.
Regarding your other questions: I think we might add such an Evaluator interface in the future but for now I would like to keep it simple and see if that works for people. And yes, a user would have to use allowedLateness and sideOutputLateData at the same time if they want to use late data, or they can go with the default allowed lateness of zero and also get the late data as a side output.

@chenqin Would you like your commits to be attributed to "Chen Qin<EMAIL_ADDRESS>or "Chen Qin<EMAIL_ADDRESS>I see both in your set of commits?
I'm finally putting everything together and hopefully merging soon since the mailing list discussion seems to favour our approach. 😄

@aljoscha
Nice! Let's do "Chen Qin<EMAIL_ADDRESS>

@chenqin I finally merged it. Could you please also close this PR?
And thanks again for working on this for so long! 👍

Wow, finally in!
It was fun and thanks for you help along every step of the journey!
Chen

Nice :)


Set rpath to enable building scalardb_fdw on MacOS

Description
This PR enables us to build scalardb_fdw on Mac more handy by setting rpath when building it.
Related issues and/or PRs
This PR is marked as a draft because it is based on #49. After #49 is merged, I will change the base branch to main and make this PR ready for merge.
Changes made

Set rpath to the path to the directory containing libjvm.dylib when being built on Mac.

The reason why this is required is described in the Additional notes section.

Checklist

[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have updated the documentation to reflect the changes.
[ ] Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
[ ] Tests (unit, integration, etc.) have been added for the changes.
[ ] My changes generate no new warnings.
[ ] Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

Since libjvm is a dynamic library, it must be found when PostgreSQL loads scalardb_fdw
rpath is a library search path, which is similar to LD_LIBRARY_PATH for Linux but is embedded and resolved when building binary.

You can see what path is embedded in each binary with otool -l. For example:

❯ otool -L<EMAIL_ADDRESS><EMAIL_ADDRESS>        @rpath/libjvm.dylib (compatibility version 1.0.0, current version 1.0.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1336.61.1)

Previously, if rpath is not specified, when the library is loaded, the loader (i..e. dyld on Mac) also searches it in the default paths including /usr/local/lib.
That's why scalardb_works works if users put the libjvm.dylib under /usr/local/lib, as described in the README.md
However, this behavior seems to be changed in some update (maybe from Sonoma?) so that it doesn't see /usr/local/lib anymore unless it is specified as rpath explicitly.

Release notes
N/A

@choplin QQ: In the following corner case, scalardb_fdw wouldn't work?

scalardb_fdw.dylib is built on a build server which has /usr/local/lib/libjvm.dylib

The path to libjvm is encoded in the binary file

The scalardb_fdw.dylib is copied and used in a different production server which has /bit/different/dir/libjvm.dylib
The encoded path /usr/local/lib/libjvm.dylib is searched, but not found on the production server

This is just to confirm if my understanding is correct.

It could happen, but I expect it would be pretty rare. This is because the issue depends on the Mac. Typical users would build and use scalardb_fdw on a Unix variant environment, where users can adjust the search path with LD_LIBRARY_PATH on runtime.
Truthfully, I don't fully understand the loader mechanism on Mac. Still, since it worked properly with /usr/local/lib (and it doesn't for now), I would suspect Apple has drastically modified how the loader works for the end user's security or something like that at the expense of developer-friendly.


fix(connector): fixed the edc discovery endpoint

Description
Fixed the EDC discovery endpoint by filtering an grouping it by Host
Why
Earlier its was filtering by provider which was showing managed connector under provider BPN which is incorrect.
Issue
#1089
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally
[x] I have checked that new and existing tests pass locally with my changes

@Phil91 : Can i update the Dependency as a blank file because in artifacts it is blank
https://github.com/eclipse-tractusx/portal-backend/actions/runs/11551164069?pr=1120
Please help

@Phil91 : Can i update the Dependency as a blank file because in artifacts it is blank https://github.com/eclipse-tractusx/portal-backend/actions/runs/11551164069?pr=1120 Please help

@dhiren-singh-007 sometimes the workflow fails because the dependencies aren't build correctly. I'll restart the workflow again

@Phil91 I thought that two reviewers which i selected will be treated as optional if one approves , so removed the other one.


Syndicate name with question mark included

Syndicate names must not include a question mark as the name is used throughout the system as part of href(url). I have removed the question mark from 'Any Questions? Ask Us' syndicate name (via the Syndicate Coordinators/Edit options).
There are 3 Rake tasks that specifically reference 'Any Questions? Ask Us' as a syndicate name - I will update those.
I will also modified the forms that are used to create or rename a syndicate so that a question mark will not be permitted in the name.

Updated code deployed to Test3 and I tested it there.
All seems ok.

Deployed by Vino 31/03

Closing


Uncaught FirebaseError: Firebase: No Firebase App '[DEFAULT]' has been created - call Firebase App.initializeApp() (app/no-app).     at Object.f [as app] (https://www.gstatic.com/firebasejs/8.2.1/firebase-app.js:1:16867)

Flutter Web Version:
Browser Version: Version 87.0.4280.88 (Official Build) (64-bit) Chrome
Trying to build flutterFire web app is always causing the same error. Below is my index.html and main.dart files that are handling the initialization of the app.
Index.html

<meta charset="UTF-8" />
<meta content="IE=Edge" http-equiv="X-UA-Compatible" />
<meta name="description" content="A new Flutter project." />

<!-- iOS meta tags & icons -->
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black" />
<meta name="apple-mobile-web-app-title" content="web_product_unitrade" />
<link rel="apple-touch-icon" href="icons/Icon-192.png" />

<!-- Favicon -->
<link rel="icon" type="image/png" href="favicon.png" />

<title>web_product_unitrade</title>
<link rel="manifest" href="manifest.json" />

<script>
  if ("serviceWorker" in navigator) {
    window.addEventListener("flutter-first-frame", function () {
      navigator.serviceWorker.register("flutter_service_worker.js");
    });
  }
</script>
<!-- Firebase App (the core Firebase SDK) is always required and must be listed first -->
<script src="https://www.gstatic.com/firebasejs/8.2.1/firebase-app.js"></script>

<!-- If you enabled Analytics in your project, add the Firebase SDK for Analytics -->
<script src="https://www.gstatic.com/firebasejs/8.2.1/firebase-analytics.js"></script>

<!-- Add Firebase products that you want to use -->
<script src="https://www.gstatic.com/firebasejs/7.8.0/firebase-auth.js"></script>
<script src="https://www.gstatic.com/firebasejs/7.17.1/firebase-firestore.js"></script>
<script src="https://www.gstatic.com/firebasejs/8.2.1/firebase-storage.js"></script>
<!-- <script src="/lib/configuration/firebase-config.js"></script> -->

<script type="module">
  // import { firebaseConfig } from "/lib/configuration/firebase-config.js";
  // Initialize Firebase
  var firebaseConfig = {
  //data removed for security reasons
  };

  firebase.initializeApp(firebaseConfig);
  //firebase.analytics();
</script>

<script src="main.dart.js" type="application/javascript"></script>

main.dart
Future main() async {
// WidgetsFlutterBinding.ensureInitialized();
// await Firebase.initializeApp();
// developer.log('${Firebase.apps.length}', name: 'main.dart');
// FlutterError.onError = (FlutterErrorDetails details) {
//   FlutterError.dumpErrorToConsole(details);
// };
runApp(App());
}
class App extends StatefulWidget {
_AppState createState() => _AppState();
}
class _AppState extends State {
final Future _initialization = Firebase.initializeApp();
@override
Widget build(BuildContext context) {
return FutureBuilder(
future: _initialization,
builder: (context, snapshot) {
if (snapshot.hasError) {
return Container(
child: Text('An Error Occurred'),
);
}
if (snapshot.connectionState == ConnectionState.done) {
return StreamProvider.value(
value: AuthService().user,
child: MaterialApp(
title: MAIN_TITLE,
debugShowCheckedModeBanner: false,
theme: ThemeData(
primarySwatch: Colors.amber,
accentColor: Colors.amber[200]),
home: MyHomePage(
title: HOME_PAGE,
),
routes: <String, WidgetBuilder>{
'/home': (BuildContext context) => new Wrapper(),
},
),
);
}
return MaterialApp(
title: MAIN_TITLE,
debugShowCheckedModeBanner: false,
theme: ThemeData(
primarySwatch: Colors.red, accentColor: Colors.red[200]),
home: Loading(),
);
});
}
}
I have tried cleaning the code and building again several times, but the error persists, Is there anyway to get more details on the error from index.html?

@bgwissam
This seems to be an issue with Flutterfire which has separate repo for tracking issues : https://github.com/FirebaseExtended/flutterfire/issues
Closing this from here.

@bgwissam
This seems to be an issue with Flutterfire which has separate repo for tracking issues : https://github.com/FirebaseExtended/flutterfire/issues
Closing this from here.

Flutter Error : No Firebase App ‘[DEFAULT]’ has been created – call Firebase.initializeApp() in Flutter and Firebase

The error is here may be the default SDK setup and configuration -

is added and other firebase sdk services such as firebase-firestore is defining before the

So you need to add other services as

etc.
if you use CDN configuration, configure other sdk services as below after the firebase-app.js

etc.


cmd-keypad: Exit also on key press on serial/USB connection.

"keypad" command so far assumes rather adhoc keyboard map, and effectively
locks up otherwise. Allow to break out of it from host connection.

@thesourcerer8: FYI

Great! Thanks for the improvement!

@thesourcerer8 : Of related question, did you get power key detected? The datasheet says it should have a (repeated) bit in KBD_MEM* regs. I modified cmd-keypad to dump raw register contents, but nothing. My device (smartwatch) has only 1 key. It would be logical for that key to be PWRKEY, but - nothing. Of course, and explanation of that can be that my key is just on some GPIO (but why?)

Bunnie said that the power key is specially handled, not by the keypad controller. I forgot to continue the investigation ...

@thesourcerer8 , if you can provide more info, or reference, I'd appreciate. (I don't know if it's better to do it here or on forum.)

I'm guessing the power key is wired through the RTC/PMU, which needs to be started up in order to receive PWRKEY presses.  But I haven't managed to get that working yet.