References

You should probably include references in the code to where these methodologies and ideas were original developed.
For the geomedian:
D. Roberts, N. Mueller and A. Mcintyre, "High-Dimensional Pixel Composites From Earth Observation Time Series," in IEEE Transactions on Geoscience and Remote Sensing, vol. 55, no. 11, pp. 6254-6264, Nov. 2017, doi: 10.1109/TGRS.2017.2723896.

For the SMAD, EMAD, and BCMAD:
D. Roberts, B. Dunn and N. Mueller, "Open Data Cube Products Using High-Dimensional Statistics of Time Series," IGARSS 2018 - 2018 IEEE International Geoscience and Remote Sensing Symposium, Valencia, Spain, 2018, pp. 8647-8650, doi: 10.1109/IGARSS.2018.8518312.

Happy to do that. I'll put some notes in the README.


Unable to extract uploader id when downloading YouTube video

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2021.12.17
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

[youtube] M9jZ2uon5U0: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see https://yt-dl.org/update on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description

I'm experiencing an issue while trying to download a video from YouTube using youtube-dl. The error message I receive is "Unable to extract uploader id." I have checked that the provided URL is alive and playable in a browser, and I'm using the latest version of youtube-dl.
The command I used is:
youtube-dl -v https://www.youtube.com/watch?v=M9jZ2uon5U0
Please let me know if there is a solution or workaround for this issue. Thank you.

Reading #30839 as asked should have led you there.


Dash datashader

App pull request

[ ] This is a new app
[x] I am improving an existing app (redesigns/code "makeovers")

About

Playground deployment URL (new version): https://dash-playground.plotly.host/dash-datashader/
Current gallery app URL: https://dash-gallery.plotly.host/dash-datashader/
Streambed issue card with link to redesign mockup: https://github.com/plotly/dash-sample-apps/issues/41

Workflow

[x] I have created a branch in the appropriate monorepo, and the
elements necessary for successful deployment are in place.
[x] If the app is a redesigned and/or restyled version of an
existing gallery app, I've summarized the changes requested in the
appropriate Streambed issue and confirm that they have been applied.
[ ] If the app is a reimplementation of a Python gallery app for the
DashR gallery, the app in this PR mimics, as closely as possible,
the style and functionality of the existing app.

The pre-review review
I have addressed all of the following questions:

[x] Does everything in my code serve some purpose? (I have removed
any dead and/or irrelevant code.)
[x] Does everything in my code have a clear purpose? (My code is
readable and, where it isn't, it has been commented appropriately.)]
[x] Am I reinventing the wheel? (I have used appropriate packages to
lessen the volume of code that needs to be maintained.)

@YunkeXiao The black test is failing on this file, please fix it ASAP! Other than that, it looks ready to be deployed to gallery. :)

@YunkeXiao Please make sure to also implement the mobile layout for this app!

Please also center all of the text in the page, like in the mobile mockup:

It still looks a little off (just the text for the bottom graph):


[pipeline] push down in filters for project node

Introduction
In-filters are constructed by a node and may be pushed down to its descendant node. Different tuple id and slot id between descendant and ancestor nodes may be referenced to the same column, such as ProjectNode, so we need use ancestor's tuple slot mappings to rewrite in filters, which maps input slot to output slot for ProjectNode.
Changes

Declare

Add struct TupleSlotMapping.
Add member ExecNode::_tuple_slot_mappings and Operator::_tuple_slot_mappings.

Push down in ExecNode Tree

Add method ExecNode::push_down_tuple_slot_mappings() overloaded by ProjectNode.
Call plan->push_down_tuple_slot_mappings() in pipeline::FragmentExecutor::prepare().

Pass to Pipeline

Pass ExecNode::_tuple_slot_mappings to Operator::_tuple_slot_mappings in  ExecNode::init_runtime_filter_for_operator().

Use

Use _tuple_slot_mappings to rewrite in filters in OperatorFactory::_prepare_runtime_in_filters().

Don't use tuple concept any more, we will remote tuple id later.


Windows support

I'm not aware of any blockers at the moment. After the macOS/Linux implementation solidifies a bit more, I should be able to port the scripts to Windows pretty easily.

This will be more difficult now that the bbin trust and bbin revoke commands exist. These commands require the ~/.bbin/trust directory to be owned by root, which means I'll need to understand how this all works from a Windows perspective.

We could also ask if @littleli is interested to help out with Windows support.

And/or @bobisageek

Windows gets interesting with respect to file ownership (and even 'sudo'). Typically on Windows, files don't have 'owners' per se, just ACLs with users/groups that have certain permissions. There's msys2, and I believe access to 'admin-y' things through a win-sudo package, but it's not built-in, and would only really apply to running stuff as admin, not file ownership. I assume it wouldn't be considered desirable to add dependencies on those things for Windows users.
The first thing that comes to mind is basically skipping those security checks on Windows, but from a cursory skim, I think it gets a bit more insidious than that, as we'd also need to filter out the chmods (and maybe some other things).
The other things that come to mind right away are:

conditional 'wrappers' for bash scripts vs windows cmd/batch files
Windows files will (I think) need an extension (e.g. .bat or .cmd) to be trivially executable; I think this would just affect naming the output files and possibly the ls command

I might get some time to play with this a bit over the weekend - I would expect that the PRs might be incremental (maybe see how big the changes are to get ls and install/uninstall up before diving into the security-focused commands).

I discussed with @rads and suggested that the first version should probably not have the sudo / trust mechanism. This can be built later with feedback from real usage. So maybe you can ignore that part for now.

As @borkdude mentioned, you can ignore the sudo / trust part right now. Going forward, this project (babashka/bbin) will not have any dependency on sudo or specific user privileges like it does now.
My current plan is to move the trust logic out of this repo this weekend and put it in a rads/bbin-strict repo, wrapping bbin to implement this. If you want to use bbin trust, you will be able to install io.github.rads/bbin-strict instead of io.github.babashka/bbin, but I will make it clear this is not an official Babashka repo, just a side project of mine.
I don't intend to suggest that bbin-strict is an alternative to bbin; it's more of a way for me (and others) to try out experimental stuff and avoid distractions from core features here. For example, I don't think I'd want to implement bbin exec without a security layer, so that will be included as part of my experimental rads/bbin-strict fork, but not the official babashka/bbin repo.

The sudo / trust stuff has been removed in v0.0.10: https://github.com/babashka/bbin/blob/main/CHANGELOG.md#0010

I got some basic stuff "working" (e.g. making the tests complete with failures but no errors on Windows). Essentially, I'm at the point where install and uninstall 'work', but they're still writing a bash script instead of a Windows batch file (so you can install a thing, but when you try to run it, it explodes because cmd isn't bash).
Obviously, the script bits are shell-dependent. I was brainstorming some ideas here but wanted some feedback/other perspectives on an approach to organizing the shell-dependent bits:

one var for e.g. tool-template-str that's defined conditionally on windows? or not

feels like potentially a handful of really big definitions, but both scripts are co-located for changes

separate namespaces and a conditional require (e.g. babashka.bbin.shell.(bash|windows))

'data' (e.g. string templates) are vaguely more organized, and the mental model is maybe nicer; the shell dependent-stuff is decided by the require (one conditional) instead of more widely-distributed conditionals
a trade off is that changing functionality that's in the shell scripts would require changes in multiple places (need to remember to keep the wrapper scripts in sync)

@bobisageek Good progress! I'll defer to @rads for the approach. Perhaps it's also possible to do more in bb rather than shell-specific things? bb now supports (process/exec ...) which allows you to do an exec call, so you don't even pay the price of an extra bb process as the parent of the invocation (although that price is fairly small I'd say).

Using exec feels much nicer than dealing with the windows shell environment (and I think it's quite in the spirit of babashka).
To dodge the yak shaving about organization for now, I'm building the template strings inline conditionally. I'm also writing a batch file when bbin runs on windows to provide the executable 'feel' - that batch file is a pretty trivial call to a bb script that constructs the 'proper' exec call.
Currently, the existing tests are passing on windows. I haven't translated the tool mode template script yet (and I also want to add some testing around that).
To borkdude's point, if desired, I think we could throw a shebang at the top of the bb-templated script and (with the batch file on Windows), have more or less identical behavior across OSes, and only one set of non-trivial scripts to maintain. One aspect of this I haven't considered is how nicely it would play with the security stuff, so still an open question there.

@borkdude @bobisageek: Using babashka.process/exec does seem like a win for portability. The tradeoff would be startup time since we are then calling bb twice — that means we incur the cost of bb plus any BABAHSKA_PRELOADS twice.
I'm open to using babashka.process/exec even with the additional startup cost, though I'd like to know a little more about the challenges for the bash scripts. Are there any specific blockers for translating them to Windows? I admit I haven't looked into the specifics of Windows batch scripting too much myself yet.

Regarding code organization, I suggest we get things working in the existing namespaces first (so mainly babashka.bbin.scripts). Once we get a first-pass at the Windows version we can look into refactoring the namespaces as needed.

@borkdude: All right, I'm fine moving forward with the bb script approach over Bash/Batch scripts. As you suggested, it's probably a premature optimization.
@bobisageek: Feel free to open a PR whenever you're ready with your branch.

@bobisageek @borkdude: I've merged in https://github.com/babashka/bbin/pull/22 and released v0.0.11 which means we now have initial Windows support in bbin. Thanks @bobisageek for the PR!
It would be great to get some more Windows users trying this out. I'll announce the new version on Slack to help with this.
I'm going to close this issue since the initial version is working. We can make follow-up issues for more specific things we want to improve about the Windows implementation.

Woohoo!


Row padding

Hello!
I want to display  stacked items next to each other (not vertical margin between them) but have some space between the first and last item from each stack to the horizontal lines of the group row.

A possible solution would be to add a prop called groupRowVerticalPadding: number to specify the inner padding of each group row.
This would look something like:

how did you change the design sir?


Premium File Storage not working

Storage Explorer Version:  1.4.2
Platform/OS Version:  Windows
Architecture: ia32
Regression From:
Steps to Reproduce:

 Expand a premium file storage account

Expected Experience:

Show File shares.
Actual Experience:

It only shows Blob Containers, with an error prompt (ENOTFOUND). We don't have blob, only file share. File shares are not showing.

Are you talking about the File Storage preview under the premium account?

This:
https://azure.microsoft.com/en-us/blog/premium-files-pushes-azure-files-limits-by-100x/

Yeah. it's in a limited preview. We haven't on-board the support yet.


"undefined is not a function" Error in Console

When I use CSS Dig on http://www.dvorakmotors.com/ using the steps below, it throws the following error in the console: undefined is not a function
The error happens when you try selecting a rule on the left and the right side is supposed to narrow in on the selector that it's part of. I don't see this behavior on every site I visit, but this happened to be the first site I used CSS Dig on, hence my Twitter exchange with you about a feature addition.
Steps to recreate:

Visit http://www.dvorakmotors.com/
Click the CSS Dig for Chrome button
Deselect all styles but "/assets/styles/homepage.css"
Click "Start Digging"
Expand background-image
Choose the first rule
Check the console for the error message

Let me know if I can provide more information.

:+1: Works for me.
I honestly haven't been back to that client site since I posted my ticket, so this has probably been fixed for a while, but I just double-checked, and I'm no longer getting the error.
Thanks!


How to Load Created Model? (Not as Pre-trained)

I have trained Caffe Model using Digits 5.0 on server computer, but it had been formatted so all data including trained model in Digits was removed. Fortunately I have copied the downloaded caffe model to my PC, now I want to upload that model to Digits server again. But I couldn't find any option other than upload a pre-trained model which is not what I want. I just want to re-upload the model, I don't want to train it further, I just want to use it to classify images on Digits server. Thank you.

I have the same issue. Please, have you solved it?


Development Improvement: Mock data

Allowing the ability to mock data such as the pricelist would streamline the development process by not relying on the bot for data. This would also make it harder to mess up bot data, human error or otherwise, during development.
The big thing is to populate an object (pricelist, settings, etc) from the get-go, so no IPC.
I'll tinker, but if anyone wants to help me on this please do.

I'm worried about how messy the code could be. My current idea is to extend getBotPricelist() to conditionally return a Pricelist object that is already populated with some data.
I think a similar approach would be used for other data objects. I'll probably add this data in index.js to avoid code pasta.


Setup Staging Environment

Staging environment deployed with develop branch
Designers can log into current development version without requiring local environment
General QA testing can be carried out before deploying new release to master branch

This Issue already exists: #17


possibility to run containers with fsync=off

According to this article: https://pythonspeed.com/articles/faster-db-tests/ a lot of speed can be gained when running postgresql in docker with fsync=off.
When I look at the docker image that testcontainers start with "docker inspect" it doesn't seem to run it with fsync off, and I have tried to play around with the .withCommand() and .addEnv() functions without success.
Is there a recommended way to set -c fsync=off in the docker run command? If yes, could this maybe be a bit better exposed?

Sounds interesting.
Btw. you can already use the Testcontainers Postgres module with tempfs (
https://docs.docker.com/storage/tmpfs/), which might provide the same speed
boost.
Alexander Kjäll<EMAIL_ADDRESS>schrieb am Di., 19. Feb. 2019,
20:24:

According to this article:
https://pythonspeed.com/articles/faster-db-tests/ a lot of speed can be
gained when running postgresql in docker with fsync=off.
When I look at the docker image that testcontainers start with "docker
inspect" it doesn't seem to run it with fsync off, and I have tried to play
around with the .withCommand() and .addEnv() functions without success.
Is there a recommended way to set -c fsync=off in the docker run command?
If yes, could this maybe be a bit better exposed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/testcontainers/testcontainers-java/issues/1256, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AE2jaNJJeCGIjK57JOHamlckL5O7XhW3ks5vPE-GgaJpZM4bDsJY
.

That was a good suggestion, setting tmpfs to "/var/lib/postgresql/data" moved my heaviest tests from taking roughly 17 seconds to 3 seconds and the whole testsuite from about 90 seconds to 60 seconds.

Whoa! Nice, we should set it by default!
Perhaps you want to contribute? 🤞
On Tue, 19 Feb 2019 at 22:23, Alexander Kjäll<EMAIL_ADDRESS>wrote:

That was a good suggestion, setting tmpfs to "/var/lib/postgresql/data"
moved my heaviest tests from taking roughly 17 seconds to 3 seconds and the
whole testsuite from about 90 seconds to 60 seconds.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/testcontainers/testcontainers-java/issues/1256#issuecomment-465315718,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAIimgnCOjhIfo3erjlGbGNnDirfER7ks5vPGtKgaJpZM4bDsJY
.

Sure, I'll try to write a pull request tomorrow or the day after.

@bsideup I looked at creating a pull request yesterday, but I'm not really friends with gradle and the testsuite completely hosed my old laptop, but it looked like it might just be a one line change.
I'm sorry to say that someone else needs to create the pull request, I don't have enough free time to do it and do it well.

Releasing this in 1.11.0 🎉


Extend close time logic to differentiate between the claimant and other users

Closes #1451
This extends the closing logic for help channels to closed based on the claimant's last message time and last message in general.
This results in the help channel closing time being reduced if only others are chatting, and the claimant has already left.
Thanks to laundmo, Darr, Griff, LX and Hemlock for the group coding on this PR :D

Has it been decided to "take the hit" when the bot is offline and can't cache messages that get sent?

@MarkKoz might need to add a condition to the old method fallback, that checks for bot uptime smaller than idle_minutes_claimant so that there is at least that much time after a restart after which channels wont be unduly closed.
that is, if i understood correctly what you were referring to.

@MarkKoz might need to add a condition to the old method fallback, that checks for bot uptime smaller than idle_minutes_claimant so that there is at least that much time after a restart after which channels wont be unduly closed.
that is, if i understood correctly what you were referring to.

What I was referring to is the cache not having the latest times due to the bot going offline and more messages being sent in channels. Upon going online again, the bot may prematurely close channels due to the outdated cache leading to the perception that the channels have been inactive.
I don't understand what you're proposing.

@MarkKoz as it stands currently, it will fall back to the old behavior if the cache isn't available (empty/ returns None)
I am proposing extending the fallback conditions to always use the old method for a while after startup, as it does not rely on cache. This way, instead of channels being closed prematurely they might take a bit longer to close.

@MarkKoz as it stands currently, it will fall back to the old behavior if the cache isn't available (empty/ returns None)
I am proposing extending the fallback conditions to always use the old method for a while after startup, as it does not rely on cache. This way, instead of channels being closed prematurely they might take a bit longer to close.

Yes, that could work. It'd have to reschedule it for the maximum time.

@MarkKoz as it stands currently, it will fall back to the old behavior if the cache isn't available (empty/ returns None)
I am proposing extending the fallback conditions to always use the old method for a while after startup, as it does not rely on cache. This way, instead of channels being closed prematurely they might take a bit longer to close.

Yes, that could work. It'd have to reschedule it for the maximum time.

What about clearing the caches on init, so the bot uses the fallback on startup, until the caches have had time to populate?

i have committed some changes that implement the cache clearing on bot startup to force fallback behaviour, and to write stats specifically for different reasons the channel could be closed.
https://github.com/laundmo/bot/tree/help-channel-closing-delay-changes
Please merge them if they are okay, i did not want to make a new PR for this.

@MarkKoz as it stands currently, it will fall back to the old behavior if the cache isn't available (empty/ returns None)
I am proposing extending the fallback conditions to always use the old method for a while after startup, as it does not rely on cache. This way, instead of channels being closed prematurely they might take a bit longer to close.

Yes, that could work. It'd have to reschedule it for the maximum time.

What about clearing the caches on init, so the bot uses the fallback on startup, until the caches have had time to populate?
Another open is populating the cache's on init too.

I'm not a fan of relying on cache behaviour like this. It feels too fragile and implicit.

I'm not a fan of relying on cache behaviour like this. It feels too fragile and implicit.

Personally i think that clearing the caches is fine, as that solves exactly the issues we would have, which is outdated caches. The code has to handle non-existent caches anyway, and treating them as non-existent after a restart seems exactly the behaviour we want.
i understand that it doesn't feel clean since we have to manually clear them. If we were to handle that data as a python only variable, there wouldn't be a discussion about this at all.
Otherwise, we would have to complicate this more by somehow updating or otherwise handling outdated caches, which i personally like less.

I'm not a fan of relying on cache behaviour like this. It feels too fragile and implicit.

Personally i think that clearing the caches is fine, as that solves exactly the issues we would have, which is outdated caches. The code has to handle non-existent caches anyway, and treating them as non-existent after a restart seems exactly the behaviour we want.
i understand that it doesn't feel clean since we have to manually clear them. If we were to handle that data as a python only variable, there wouldn't be a discussion about this at all.
Otherwise, we would have to complicate this more by somehow updating or otherwise handling outdated caches, which i personally like less.

It's not complicated. Check if the cog is starting for the first time with self.init_task.done(). If it's true, then schedule channels to close 30 minutes (idle_minutes_claimant, the largest of all possible values) after the latest sent message. No need to worry about outdated caches because if a new message gets sent, the caches will get updated. If no messages get sent, then the outdated caches values will be old enough anyway to cause the channel to close. What are everyone's thoughts on that?
In any case, the current behaviour is still incorrect because it is using idle_minutes_others instead of idle_minutes_claimant when the cache is empty. It's not going to extensively search the message history for the claimant's last message. Therefore, it must assume the worst case and use idle_minutes_claimant to avoid prematurely closing a channel.

I'm trying this out with the following config:
    idle_minutes_claimant: 2
    idle_minutes_others: 1
    deleted_idle_minutes: 1

I simply claim a channel, and it correctly schedules it to close in 2 minutes. However, when the closing task runs, it calculates a wrong time. The log timestamps on the left are in UTC-8. Converted to UTC the times would be around 2021-03-26 20:58:06. Therefore, the time it calculates is off by 7 hours.
2021-03-26 13:58:06 | bot.exts.help_channels._channel | TRACE | #help-burrito<PHONE_NUMBER>92997918) should be closed at 2021-03-27 03:58:05.915000 due to claimant timeout.
...
2021-03-26 13:58:06 | bot.exts.help_channels._cog | INFO | #help-burrito<PHONE_NUMBER>92997918) is still active; scheduling it to be moved after 25199 seconds.
...
2021-03-26 13:58:06 | bot.utils.scheduling.HelpChannels | TRACE | Waiting 25199 seconds before awaiting coroutine for #800698210392997918.


Individual Membership Subgroup – Next Steps

A few months ago, I stepped up to take point in coordinating our Individual Membership Subgroup meetings. This past month, I started a new job. I have been able to sustain my responsibilities to the @nodejs/community-committee,  @nodejs/user-feedback and @nodejs/mentorship which have meeting times that are compatible with my work schedule with meetings on Thursday and Fridays.
Individual Membership Subgroup meetings (and tangentially the Bootstrap meetings) are not compatible with my schedule. Individual Membership is something that I am very passionate about, but at this time, I am unable to lead this effort.
At this point, I need to step back from this and ask if there is someone who can step up and carry this forward.

I know @amiller-gh and @hackygolucky were going over the current draft to work on it together. I'm wondering if after that there will be a need for the group to continue meeting or not?

Of course the last comment is in the context of making a proposal to the board.  In terms of implementing a program that would be completely different.

Current working plan discussed in today's CommComm meeting:

@hackygolucky and I are working on an updated draft of both the program proposal and representation proposal using the Bootstrap repo's stages proposal template. We will share a draft of this in Google docs shortly (ETA is EOD tomorrow).
We will sync offline on the proposal as-written and wordsmith with the group / CommComm. If we feel there is need for a final meeting to polish we will plan for next week.
Once the proposals are in a happy place, Tracy will bring them to the board for approval! We will then consider this phase of the Individual Membership Recommendation Subgroup done 🎉
Starting next year, assuming on Foundation support and approval, we will kick off a fresh initiative for program execution. The function of this group will be a lot different than the current subgroup, so it makes sense to me to treat it as a new initiative.

IMO – It is likely that:
a) Program execution (membership tooling, recruitment, benefits communications, etc) will be a close partnership between our Foundation resources and the initiative;
b) Representation recommendation, as currently written, is dependent on good program execution and will be blocked by point (a), and;
c) The representation plan recommendation will also likely move over to the Bootstrap repo for further refinement in the context of an umbrella foundation.
Does all this sound accurate / good? 🙂

Closed since Bootsrap has taken ownership of the proposal 🎉


fees: clarify what the actual recommended fee is

Introduces RECOMMENDED_MIN_TX_FEE as a constant that explicitly sets a single value and then implements this value for each fee related constant throughout the code, instead of using values relative to COIN.
This helps because it makes the relation of other defaults to the fee recommendation clear and makes
choices made by developers in wallet configuration easier to read and understand. In the past we had the problem that
one constant / default was being used for multiple reasons, but now, all the logic between the different defaults is extremely hard to read because everything is expressed relative to COIN, and this makes it error-prone, for both developer and reviewer.
NOTE: This commit only changes existing values to be expressed relative to the recommended fee and does not change actual values.
Issues I detect by looking at it this way:

DEFAULT_INCREMENTAL_RELAY_FEE and DUST_RELAY_TX_FEE are probably wrong
DEFAULT_TRANSACTION_MAXFEE is on the high side
HIGH_TX_FEE_PER_KB is lower than the 5.21 DOGE from the slider
MIN_CHANGE is suboptimal
WALLET_INCREMENTAL_RELAY_FEE is probably wrong

Fixes to these can (and imho should) be proposed and discussed separately, so that this PR stays clean of changes, creating a clean audit trail.

Concept ACK, unlikely I can test this tonight though, and a couple of "are you sure?" comments to check

unlikely I can test this tonight

No problem. It may be wise to rebase this after #2564 to include those freshly enabled parameters?

Verified with a live tx: https://chain.so/tx/DOGE/5f1c3d610e32eb19e36ec0f212817906aed24e953c062c96a8533fa06a0d06f8


Sort out locales for OSL

I got quite the education this week, realizing just how much of C++'s I/O functionality implicitly takes the system's "locale" into consideration.  Of particular concern is the conversion of text to floating point numeric values and vice versa, for which much C++ functionality will happily swap the role of '.' and, say, ',' (comma) for the decimal mark, depending on the user's country and whether they are savvy enough to set their locale to the classic "C" (essentially US-style) version. On the other hand, who can blame somebody for not blindly accepting US hegemony these days?
But dammit, OSL is a programming language, and so '.' has a specific role in numeric constants and ',' does something quite different (comma operator!), and if you start mixing up the two when parsing programs, it will all end in tears. All other major programming languages just adopt this convention as well.
Now, if you were writing a full app, you could set the locale to the classic one globally (to that process) upon startup, and then never worry about it. Which we can do for oslc itself. But much of OSL is actually a library that can be embedded into other libraries or apps, so globally setting the locale can mess up UI internationalization or the intentional localization of other app I/O. So we have to handle this deftly throughout.
The fix comes in three parts:

I've submitted a separate review to OIIO here: https://github.com/OpenImageIO/oiio/pull/1785 which tries to straighten up that library, and in particular the various Strutil and ustring utilities that we liberally use throughout OSL. And patrol some of the places where we directly call the locale-sensitive C++ functions like atof and strtod, and replace them with the now-safe OIIO::Strutil equivalents. We'll be able to count on all this working for OIIO >= 1.8.6.

In a variety of places that don't rely on OIIO (for example, various outputs via std::ostringstream), we need to take care to explicitly set the stream's locale to produce the output we expect.

For people building OSL against a too-old version of OIIO to contain the fixes described above, when compiling a buffer of OSL source code, do the gross but necessary safeguard of saving the prior locale, globally changing to "C" locale while we compile the OSL, then restoring the locale.  And HOPE that the surrounding application isn't simultaneously counting on the original locale-based internationalization still being in effect for something it is doing in another thread that's unaware that we've temporarily altered a global setting. That's inherently unsafe, but remember it only affects OSL builds against pre-1.8 OIIO (once that patch is applied on the OIIO side), and only will be symptomatic for systems using a non-. locale (which is, empirically speaking, rare enough that nobody noticed this issue until this week).

LGTM, but why not using the safe float parsing and serializing function everywhere and bypass locale entirely? I still have nightmares with the locale thing from my early days. If the problem is ostreams, can those safe functions be used there somehow as well?

Using the safe version "everywhere" means that you can never write this natural thing:
// ostream out;
out << my_float;

Instead, you have to remember to do this awkward thing:
out << Strutil::format("%g", my_float);

That seems very error prone, so in addition to making sure we always use the "safe" versions of string->float and float->string, we also initialize every stream upon creation, so that ordinary stream output also works properly. That's really all this patch is doing.

Ok, fair enough. Still LGTM

This whole issue makes me want to tear my hear out!
Looking through the tickets of some other languages (Python, Julia, etc.) it seems they all have to grapple with this mess at some point.


update placeholder def for Safer-SeqS

Currently, this assay has a placeholder definition. It's not clear whether the assay described in the project is this, or something else entirely:
https://pubmed.ncbi.nlm.nih.gov/33941929/

OK after some spelunking I found this JHU press release: https://www.sciencedaily.com/releases/2021/05/210504135750.htm
So I'm guessing the paper linked above is the correct one. We should call it SaferSeqS, because that is what the paper calls it.


Tests for file validation

[x] Multer tests
[x] Formidable tests

#22 multer tests are done here

mistakenly closed the issue 😮💨

#25 formidable tests are done here


Use template string instead of templateUrl in ui-breadcrumbs

As far as I can see, this is not possible currently.
In my current scenario, I don't see the fit for templateUrl, but I could use a option to pass a template string.
I'm developing a common project (that uses ui-breadcrumbs) and a lot of other projects that use this common project, installing it as a npm dependency. Webpack bundles it all together, but in my dependent projects (the ones that depend on the common), the HTML template file (that would live inside the common project) is burried inside node_modules/my-common-project, so I can't reach that HTML file with some URL.

I wanted to use the string I used it like it.
$scope.paginationTemplate = $templateCache.put('angularUtils.directives.dirPagination.template', $templateCache.get('/views/pagination.view.html'))
where I use my custom template.

@MangeshPimpalkar Do you think this would be doable in breadcrumbs too? It just doesn't seem to work with template, only with templateUrl

Hi,
You are correct that it is currently not possible to specify a template string. That module was written way before the days of Webpack, so such a thing was not a common requirement (at least in my own projects).
The suggestion of using the $templateCache service could work for you. In your app run block, for example, you could do something like:
$templateCache.put('myBreadcrumbsTemplate.html', require('myTemplate.html'));

and then you specify myBreadcrumbsTemplate.html as the template-url attribute for the breadcrumbs. Not tested, but could work.

@michaelbromley It did work! That was nice.
Any chances of installing ui-breadcrumbs with npm?

I did installed pointing to the angularUtils Github repo. But I had to use the commit hash since there isn't a tag.

@rafaeleyng I've not got time atm to make an npm version. The commit hash should be pretty safe - I rarely change that code since I don't use it myself in production any more.


fix: count down timer is not working until reload

We have to reload the window to get infos from graphql.
Similar issues are here.
https://github.com/pixelaw/p_war_client/issues/47

After the game instance started, it's working.


MatDatepicker ngModel doesn't update from controller

Reproduction
Steps to reproduce:

Use a Mat Date Picker with a [(ngModel)]
Change the value of ngModel in the controller

Expected Behavior
The input should have updated the value shown
Actual Behavior
The input doesn't actualize
Environment

Angular: 7.0.1
CDK/Material: 7.1.0
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows 10

Can you post a Stackblitz that shows the issue?

This is a little bit more complicated than a Hello World, so stackblitz isn't working
Here's what I am trying to do anyway
https://angular-nqxvyh.stackblitz.io
While it's buggy on stackblitz, the only thing that's not working in my app is that when I clic on previous or next, the date in the input isn't updating.

I haven't tried moving this into our demo app, but from looking at the code I think the issue is that change detection isn't firing because subtract mutates the original Moment object, it doesn't create a new one so as far as Angular is concerned the date is the same. You can try adding .clone() before the .subtract.

Closing because this issue has been inactive for 2 weeks or more after follow up was requested.


Remove outdated comment about Parcel workaround

Those should no longer be needed. If you want to set those explicitly to aid React DevTools in production then I think the as any cast is still a preferred approach but for different reasons. TS isn't able to infer from functions with properties so some HOC-like/FP patterns don't work with React.FC-like types (see the thread here). It's best to keep those as plain functions if possible at type-level (note that components using forwardRef are already breaking that rule because the return type of forwardRef is a function with extra properties. You can't do much about that though unless you'd be ready to use some casts with types like this)

Sure, the thing that caught my eye was the comment - and not the .displayName per se. I pushed out a change to just remove the comment.


Slurm interactive jobs: HOSTNAME != $(hostname)

Hrrm...
when launching an interactive Slurm job:
[henrik@c4-dev3 ~]$ srun --nodes=1 --cpus-per-task=4 --mem=32G --time=03:00:00 --pty $SHELL
srun: job 406351 queued and waiting for resources
srun: job 406351 has been allocated resources

we get:
[henrik@c4-n3:job=406375 ~]$ rsc stop
ERROR: Stopping the RStudio Server can only be made from the machine (c4-n3) where it was started from

[henrik@c4-n3:job=406375 ~]$ echo $HOSTNAME
c4-dev3

[henrik@c4-n3:job=406375 ~]$ hostname
c4-n3

So, should use $(hostname) instead of $HOSTNAME.

Fixed in the next release.


[Fix][Txn]Fix transaction component recover fillQueue

Motivation & Modification
The queue size + NUMBER_OF_PER_READ_ENTRY should <= the capacity of queue instead of the queue size <= the capacity of queue. If the processing speed is less than the read speed, the part that exceeds the queue capacity will be ignored.
About test
It hard to add test for this change.
This class of replay/recover/FillEntryQueueCallback is not public, so it can not be import by test.
And then their flied can not be changed by reflection.
With Thread.sleep allowed, we  can only test the recover of  TC by call a Thread.sleep in transactionLogReplayCallback and can not test TP/TB.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] no-need-doc
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-added
(Docs have been already added)

Feels like more context is needed to help contributors review.

Question:
Does this PR solve the problem of skipping entries?
/cc @congbobo184

@mattisonchao yes, after testing it solved the problem

/pulsarbot run-failure-checks


Issue 2160

Pull request template
Checklist

[x] I have read the CONTRIBUTING guide
[x] branch rebased on develop
[x] styleguide check npm run validate
[x] good naming
[x] keep simple
[ ] video or screenshot attached
[ ] testing instruction attached
[x] check your PR once again

Description
Решение ишью https://github.com/swaponline/swap.react/issues/2160
Video or screenshot

What and how to test

тревис на отступы загоняется


Optimize for long strings

I was thinking if var vector = new Array(2 * la) would help instead of var vector = [];? In theory arrays are created with predefined size and they are reallocated if that size is exceeded (with some new limit estimate). I don't know how the browsers optimize it today, but surely the length constructor exists for a reason.

That was my thought too and I have experimented with that, but V8 (at the time of writing) could optimize better with [] because it could then infer that only numbers was used and have the array optimized for numbers.


Request for Digital Wallets / Bank transfer features

Describe the solution you'd like
Looking for following features for South-east Asia market.

Digital wallets for Malaysia, Singapore, and Hong Kong?
Bank transfer for Malaysia, FPX

Are these payment method supported by Stripe yet?

@hideokamoto Yes, all of them are supported by Stripe.

Thanks for request. We had same request already, and We will this at future: https://github.com/capacitor-community/stripe/issues/88
But these function can't use in Japan... ( me and @hideokamoto is in Japan ).
We will start it someday, but welcome to create a pull request.

@dodomui Did you adapt this plugin for production? If yes, please tell us what app. Please help us to develop this plugin in 2022.
https://github.com/capacitor-community/stripe/issues/145

@rdlabo I didn't use this plugin for production.

@dodomui Thanks for information! If use for production. please tell to https://github.com/capacitor-community/stripe/issues/145 !

#201

This is a duplicate of https://github.com/capacitor-community/stripe/issues/88 , so it is closed.


post  method in result The input was not valid.

Before you open an issue
If the issue is with an ASP.NET Core document, open the issue with the Content feedback button at the bottom of that document page.
If the issue is:

A simple typo or similar correction, you can submit a PR. See the contributor guide for instructions.
A general support question, consider asking on a support forum site.
A site design concern, create an issue at MicrosoftDocs/Feedback.
A problem completing a tutorial, compare your code with the completed sample.
A duplicate of an open or closed issue, leave a comment on that issue.

Issue description
{ description here }
Software versions
Check the .NET target framework(s) being used, and include the version number(s).

[x] .NET Core
[ ] .NET Framework
[ ] .NET Standard

If using the .NET Core SDK, include dotnet --info output. If using .NET Framework without the .NET Core SDK, include info from Visual Studio's Help > About Microsoft Visual Studio dialog.

dotnet --info output or About VS info
<replace>

"The input was not valid.

Hello! Thanks for contacting us. This sounds like a general question about using ASP.NET Core. While we try to look at and respond to all issues, for questions like this we recommend posting to a community support group like Stack Overflow with the asp.net-core tag.


"Sampaikan masukan" in all pages

Description
We already create a link in the homepage to submit any discussion if the user found the bugs from our web.
But the visibility is very bad, it's only on the homepage which is quite long to be scrolled.

Implementation Model
My suggestion is to put it in all pages.
Keep it on the very bottom, like the copyright in the other websites.
But need confirmation from @zainfathoni if he wants to take this or just close this if it's invalid.
Tasks

[ ] Create seperate React Component
[ ] Put it on the Layout

Agreed. I think it's better if we can make it a part of our layout that appears on every page.
Currently, we have no proper footer for the page that contains the Copyrights and other relevant information, including our GitHub repository.

Hai Mas, could I work on this ticket?
*I've never worked on a React project, but I've tried web components and Tailwind, may I try (while I'm learning)?

Please try to take a look the code and run on your local first, if you think you can work on this, then please take it.

Agreed. Once you're able to set this project up locally in your machine, you can start creating a draft pull request to signal other developers that you're currently working on it.
Please read our contributing guide for more complete guidelines.

Well noted Mas @mazipan, Mas @zainfathoni.
I will try to create a draft pull request first.


Enhance environment trait to include values from secrets/configmaps

We can enhance the trait to include values taken directly from secret without the need to expose them or to mount as files via mount trait. For example we should have something like kamel run test.yaml -t env.vars=MY_VAR=secret:my-secret/my-value converted in a Pod like:
apiVersion: v1
kind: Pod
...
spec:
  containers:
...
    env:
    - name: MY_VAR
      valueFrom:
        secretKeyRef:
          name: my-secret
          key: my-value

sign me on

PR: https://github.com/apache/camel-k/pull/5639


Emitter: add missing parenthesize calls

Fixes a bug in the Emitter introduced by https://github.com/freechipsproject/firrtl/pull/1817
input:
circuit foo :
  module foo :
    input in1 : UInt<1>
    input in2 : UInt<1>
    input in3 : UInt<1>
    output out : UInt<2>

    out <= dshl(in1, or(in2, in3))

emits incorrect verilog due to missing parentheses, in2 | in3 should have parentheses because | has lower precedence than <<:
module foo(
  input        in1,
  input        in2,
  input        in3,
  output [1:0] out
);
  wire [1:0] _GEN_0 = {{1'd0}, in1};
  assign out = _GEN_0 << in2 | in3;
endmodule

This PR adds missing calls to parenthesize to emit these parentheses.
Contributor Checklist

[n/a] Did you add Scaladoc to every public function/method?
[n/a] Did you update the FIRRTL spec to include every new feature/behavior?
[ ] Did you add at least one test demonstrating the PR?
[x] Did you delete any extraneous printlns/debugging code?
[x] Did you specify the type of improvement?
[x] Did you state the API impact?
[x] Did you specify the code generation impact?
[x] Did you request a desired merge strategy?
[x] Did you add text to be included in the Release Notes for this change?

Type of Improvement

bug fix

API Impact

none
Backend Code Generation Impact

adds missing parentheses
Desired Merge Strategy

Squash

Release Notes

Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (1.2.x, 1.3.0, 1.4.0) ?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you mark as Please Merge?

Can you add the specific examples as tests to InlineBooleanExpressionsSpec?

I'm trying to exercise the bug with firrtlEquivalenceTest, but it runs InlineBooleanExpressions after VerilogEmitter so it always emits identical verilog. not sure what the correct fix is. should I add InlineBooleanExpressions as an optional prerequisite of MinimumVerilogEmitter?

Yes that makes sense

Just saw this. Yes, that's the correct approach. You'd probably want to add:
override def optionalPrerequisiteOf = Forms.BackendEmitters

Don't forget to run Scalafix 🙂


travis continues to deploy when build fails

See for example https://s3.amazonaws.com/archive.travis-ci.org/jobs/125733067/log.txt
     ...
     [exec] :core:javaAction:distDocker FAILED
     ....
     [exec] Executing 'docker --host <IP_ADDRESS>:4243 tag -f whisk/javaaction whisk/javaaction:latest'
     [exec] Error response from daemon: no such id: whisk/javaaction
     ....
     [exec] :core:javaAction:tagImage FAILED
     [exec]
     [exec] BUILD FAILED
     [exec]
     [exec] Total time: 9 mins 41.115 secs
     [exec]
     [exec] FAILURE: Build completed with 2 failures.

and then
setDeployTarget:
     [echo] deploy target: local

writePropertyFile:
     [exec]
     [exec]
     [exec]

deploy:

deployDatabase:

further on
pullImageFromRegistry:
     [exec] Unable to find image 'whisk/zookeeper:latest' locally
     [exec] Pulling repository docker.io/whisk/zookeeper
     [exec] docker: Error: image whisk/zookeeper not found.
     [exec] See 'docker run --help'.

BUILD FAILED
/home/travis/build/openwhisk/openwhisk/build.xml:53: The following error occurred while executing this line:
/home/travis/build/openwhisk/openwhisk/services/build.xml:5: The following error occurred while executing this line:
/home/travis/build/openwhisk/openwhisk/services/build.xml:18: The following error occurred while executing this line:
/home/travis/build/openwhisk/openwhisk/services/zookeeper/build.xml:17: exec returned: 125

and even though it did not deploy properly, it continues to run the tests.

had the same problem with ansible tests.
a && in the script should do the trick. lemme try that real quick.


[SymDeposit] Improve re-loading of balances

by clicking "refresh" button. Currently we load ALL balances, but we just need to reload balances of selected assets

Duplicated by https://github.com/thorchain/asgardex-electron/issues/1185


On Rancher upgrade to v2.6.7, the Azure AD link to update config freezes the UI

Setup

Rancher version: v2.6.7 (with an upgrade from v2.6.6)
Browser type & version: Firefox

Describe the bug
If Rancher has a deprecated configuration of Azure AD, the UI shows the banner at the top prompting admins to update the configuration. The banner has a link Update it here. Clicking on it freezes the UI, nothing is displayed, except the header.
To Reproduce

Set up Azure AD in Rancher v2.6.6.
Upgrade Rancher to v2.6.7.
See the banner at the top. Click the link.

Result
The UI is Loading forever with no errors in the console. Only the header is shown grayed-out. I can get around this by going to the Auth Provider screen directly. Locally, I see the Expected "cluster" to be defined displayed without Loading.
Expected Result
The link should take me to the auth provider screen with a button to update its the auth provider configuration.
Screenshots

Additional context
When I click Home, there is an error in the console. A full refresh helps, but the issue with the link does not go away.
Find All: [management] userpreference console.js:26:30
Find: [rancher] authconfig azuread console.js:26:30
Uncaught (in promise) TypeError: Expected "cluster" to be defined
    NuxtJS 3
    d runtime.js:45
    _invoke runtime.js:274
    e runtime.js:97
    Babel 4
    T NuxtJS
    _ vue-router.esm.js:2362
    r vue-router.esm.js:2004
    r vue-router.esm.js:2005
    _ vue-router.esm.js:2384
    e NuxtJS
    d runtime.js:45
    _invoke runtime.js:274
    e runtime.js:97
    Babel 6
    O NuxtJS
    _ vue-router.esm.js:2362
    r vue-router.esm.js:2004
    r vue-router.esm.js:2008
    It vue-router.esm.js:2012
    confirmTransition vue-router.esm.js:2392
    transitionTo vue-router.esm.js:2260
    push vue-router.esm.js:2606
    push vue-router.esm.js:3037
    push extend-router.js:12
    push NuxtJS
    j vue-router.esm.js:1139
    VueJS 33```

Tried reproducing the issue on an upgrade from 2.6.6 >> 2.6.7
This is seen happening when the endpoint update is attempted from home page. If the endpoint update is attempted from cluster management/Users & auth/cluster explorer/global settings we will be navigated to the auth providers page.

Verified on v2.6-head 79a5328 upgraded from v2.6.5 as an admin user
Pre -reqs

Installed rancher on v2.6.5 and created 1 node driver linode rke1 and 1 node driver AWS rke2 cluster
Enabled azure AD auth
Upgraded rancher server to v2.6-head
Installed CIS v2 apps in both the downstream clusters and rancher backup in local cluster

Test cases:

Update endpoints navigated from home page  - PASS
Update endpoints navigated from local cluster explorer - PASS
Update endpoints navigated from downstream rke1 and rke2 cluster's CIS app - PASS
Update endpoints navigated from cluster management page - PASS
Update endpoints navigated from Global settings/Continuous delivery/Virtualization management - PASS
Update endpoints navigated from Users/Groups/Roles - PASS


Optionally allow java to not be managed via the java cookbook.

Allows for conditional exclusion of the java cookbook's default recipe for those of us who use other methods to configure our java environments.

+1, and remember to sign the CLA to have the label!

@bdclark Thanks for this contribution. I know this is a much delayed appreciation. I'm going to go ahead and close this, as rather than using the java community cookbook explicitly, I'm going to rip out the dependency entirely. This is the pattern we've used for example with the tomcat rewrite. There are so many different ways to install java, and we want to make sure to minimize the external dependencies. I'm going to go ahead and close this request as I'll be doing a release shortly that will eliminate this dependency.


[IPv6] adjust MTU for IPv6 overhead

If MTU is too large for IPv6 environment, large packet with overhead
IPv6ExtraOverhead, 20 is from observation of IPv4 and IPv6 packets under same situation.

Codecov Report

Merging #1305 into ipv6 will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             ipv6    #1305      +/-   ##
==========================================
- Coverage   41.14%   41.07%   -0.07%
==========================================
  Files          77       77
  Lines        9978     9980       +2
==========================================
- Hits         4105     4099       -6
- Misses       5501     5507       +6
- Partials      372      374       +2

Flag
Coverage Δ

#unit-tests
41.07% <0.00%> (-0.07%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/agent/agent.go
12.73% <0.00%> (-0.07%)
:arrow_down:

pkg/agent/config/node_config.go
0.00% <ø> (ø)

pkg/apiserver/storage/ram/store.go
77.44% <0.00%> (-1.51%)
:arrow_down:

...ntroller/networkpolicy/networkpolicy_controller.go
71.58% <0.00%> (-0.56%)
:arrow_down:

/test-ipv6-only-conformance
/test-ipv6-only-e2e

/test-windows-conformance

/test-ipv6-only-conformance
/test-ipv6-only-e2e

/test-ipv6-only-e2e

Question - is it possible we use IPv4 tunnel when Pod CIDR is IPv6? @wenyingd

In theory, it is possible. We use Node's Internal Address to set tunnel header. If there is a Dual-Stack cluster, and the Node reports its address using an IPv6, then for the Pod's traffic in IPv4 should be transmitted with IPv6 tunnel.

Question - is it possible we use IPv4 tunnel when Pod CIDR is IPv6? @wenyingd

In theory, it is possible. We use Node's Internal Address to set tunnel header. If there is a Dual-Stack cluster, and the Node reports its address using an IPv6, then for the Pod's traffic in IPv4 should be transmitted with IPv6 tunnel.

Got it. Maybe good to add comments somewhere about this behavior (why IPv6 or v4 tunnel is decided by Pod CDIR is v4 or v6).
@lzhecheng

/test-all
/test-ipv6-e2e
/test-ipv6-only-e2e

Question - is it possible we use IPv4 tunnel when Pod CIDR is IPv6? @wenyingd

In theory, it is possible. We use Node's Internal Address to set tunnel header. If there is a Dual-Stack cluster, and the Node reports its address using an IPv6, then for the Pod's traffic in IPv4 should be transmitted with IPv6 tunnel.

Got it. Maybe good to add comments somewhere about this behavior (why IPv6 or v4 tunnel is decided by Pod CDIR is v4 or v6).
@lzhecheng

Got it. Updated.

/test-ipv6-e2e
/test-ipv6-only-e2e

/test-windows-networkpolicy

/test-ipv6-conformance
/test-ipv6-only-conformance

/test-ipv6-conformance
/test-ipv6-only-conformance


Fix the combination of setters and post-{increment/decrement}

Migrated from https://bugs.webkit.org/show_bug.cgi?id=193550 on March 7, 2019
From @RobinMorisset:
The reference implementation currently behaves really weirdly on post-incrementing a field of a struct with an overriden setter (and getter).
It correctly uses the getter for having the current value, increment it, uses the setter for updating it.. but somehow returns the new value instead of the old one.
I believe this is a bug in the reference implementation.
Example:
struct Foo {
  int z;
}
int operator.w(Foo foo) {
  return 8;
}
Foo operator.w=(Foo foo, int value) {
  foo.z = value;
return foo;
}
int bar() {
  Foo foo;
  foo.z = 3;
  int value = foo.w++;
  return value*100 + foo.z*10 + foo.w;
}

Calling bar() return 998 instead of 898 as I would expect.

The JS implementation is now dead, so this issue is irrelevant.
We should just remember to add this test to the test suite.


Notify producers/consumers on schema changes

What is currently missing?
When a new version of schema is uploaded on a topic, producers and consumers should be notified
How could this be improved?
Notifications should be sent when schema changes are done on a topic to all acl owners.
Is this a feature you would work on yourself?

[ ] I plan to open a pull request for this feature

Greetings @muralibasani, I would like to work on this could you please link the GitHub file. It would make it a lot easier for me!

Hey @muralibasani , I would like to work on this issue. If it's still available.

@dipeshsingh253 please go ahead, as you are a new contributor.
@Sadaf-A you might want to review the PR from this.

@dipeshsingh253 please go ahead, as you are a new contributor.
@Sadaf-A you might want to review the PR from this.

hey, I hope you are well. did you mean yo say I should review the PR? just wanted to confirm.

Hey @muralibasani, I was trying to replicate this issue in my local but I am not able to access the clusterapi-webportal in my local.
I am getting this error :

I followed this to run Klaw local: https://www.klaw-project.io/docs/HowTo/installation/run-source
Thanks for your time !!!

Hey @muralibasani, I was trying to replicate this issue in my local but I am not able to access the clusterapi-webportal in my local.
I am getting this error :
2023-10-06T05:29:50.995+05:30  INFO 13653 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 9343 (http) with context path ''
2023-10-06T05:29:51.032+05:30  INFO 13653 --- [           main] i.a.k.c.KafkaClusterApiApplication       : Started KafkaClusterApiApplication in 4.383 seconds (process running for 5.334)
2023-10-06T05:29:57.341+05:30  INFO 13653 --- [nio-9343-exec-1] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring DispatcherServlet 'dispatcherServlet'
2023-10-06T05:29:57.342+05:30  INFO 13653 --- [nio-9343-exec-1] o.s.web.servlet.DispatcherServlet        : Initializing Servlet 'dispatcherServlet'
2023-10-06T05:29:57.345+05:30  INFO 13653 --- [nio-9343-exec-1] o.s.web.servlet.DispatcherServlet        : Completed initialization in 2 ms
2023-10-06T05:29:57.382+05:30  WARN 13653 --- [nio-9343-exec-1] i.a.k.c.config.JwtRequestFilter          : JWT Token does not begin with Bearer String
2023-10-06T05:30:40.499+05:30  WARN 13653 --- [nio-9343-exec-2] i.a.k.c.config.JwtRequestFilter          : JWT Token does not begin with Bearer String

I followed this to run Klaw in local : https://www.klaw-project.io/docs/HowTo/installation/run-source
Thanks for your time !!!

Hello @dipeshsingh253 ,
I kindly request that you format your token as follows:
Bearer ${token}
So, it should be a string that looks like "Bearer <your_token>"
Your attention to this matter is greatly appreciated.

Hello @Sadaf-A , I am using a browser to access the web portal. and also in the , there is no mention of how to get the token for the first time.
Can you please elaborate more on this? It will be very helpful.
Thanks :relaxed:

@Sadaf-A @dipeshsingh253
Klaw cluster api doesn't have a web portal. Only core module has a web portal. And by default it runs at port 9097.
http://localhost:9097
For the token part, in cluster api properties, property klaw.clusterapi.access.base64.secret there is an example token above. You can use the same and copy that token to core module application properties.

Hi @muralibasani ,
I've successfully run and logged into the Klaw UI in my local environment. However, I have faced some difficulties while trying to create a Kafka cluster:
What should be filled in the "rest API server" field in the Kafka cluster creation form?
I'm curious if there's a Klaw community on Discord or Zulip where I can seek assistance. I couldn't find any links to these platforms and currently, this issue is my sole means of communication.
If there are any how-to guides or documentation available for setting up Klaw locally for development purposes, please share them with me.
Thank you!

@dipeshsingh253
https://aiven.io/community/forum/tag/klaw is klaw community
However restapiserver is optional field there. Docs : https://www.klaw-project.io/docs/HowTo/clusterconnectivity/kafka-cluster-ssl-protocol
what is your mail id ? I can send a slack invite.

Thanks @muralibasani , and sure here is my email<EMAIL_ADDRESS>


module_test_ios failing in staging, "Could not find any supported simulator runtimes"

As of https://github.com/flutter/flutter/pull/98297 that test is running on Xcode 13a233 and should be grabbing ios_runtime simulator runtimes from cipd https://github.com/flutter/flutter/issues/91689
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8821388884257231665/+/u/run_module_test_ios/test_stdout
[module_test_ios] [STDOUT] stdout:         Underlying Errors:
[module_test_ios] [STDOUT] stdout:             Description: Could not find any supported simulator runtimes

list simulators shows no simulators:
== Runtimes ==
== Devices ==

In the install Xcode step it only shows installation from flutter_internal/ios/xcode/mac and flutter_internal/ios/xcode/ios but not ios_runtime
[P22871 17:11:36.330 action_plan.go:174 I]     flutter_internal/ios/xcode/mac (8cf87f9a7d8b31aa99d303dcd9c0277dbc91198c -> UCaNcftiBhJwpRpc5DUfKSIw8COAV-Tys6P58EzPEykC)
[P22871 17:11:36.330 action_plan.go:174 I]     flutter_internal/ios/xcode/ios (41641f55a9654db87d73faf1d316fe71cf7df5d7 -> rWdxdSMwqPafHwtN9Uh77do6HVmD6iVatO_XNPbfHvEC)

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8821388884257231665/+/u/install_xcode/stdout
It's supposed to look like successful run https://ci.chromium.org/p/flutter/builders/prod/Mac_ios flutter_gallery_ios__start_up/3680
== Runtimes ==
iOS 15.0 (15.0 - 19A339) - com.apple.CoreSimulator.SimRuntime.iOS-15-0

Maybe the mac_toolchain running in staging isn't the one that knows how to handle default runtimes? https://flutter-review.googlesource.com/c/recipes/+/23980 & https://github.com/flutter/flutter/issues/94780
/cc @godofredoc @keyonghan

The mac_toolchain in staging does use the latest version, same as prod ones:
"instance_id": "Lmnduk3ULUqIVoSwGka-yEiHkb_6pBo6RpJXIoXtS6IC",

CIPD version list: https://chrome-infra-packages.appspot.com/p/infra/tools/mac_toolchain/mac-amd64/+/

Here's an example of a led engine builder run that shows what this should look like when there's an Xcode cache miss:
Packages:
  flutter_internal/ios/xcode/ios_runtime:xbExNWHTJfpNf8vDNXhmLNx9sjfFvAl4ed74gTrXl3cC
[P92814 19:01:12.305 action_plan.go:160 I] In root:
[P92814 19:01:12.305 action_plan.go:166 I]   to install:
[P92814 19:01:12.305 action_plan.go:168 I]     flutter_internal/ios/xcode/ios_runtime:xbExNWHTJfpNf8vDNXhmLNx9sjfFvAl4ed74gTrXl3cC
[P92814 19:01:12.305 client.go:1655 I] Dry run, not actually doing anything.
[P92815 19:01:13.007 action_plan.go:160 I] In root:
[P92815 19:01:13.007 action_plan.go:166 I]   to install:
[P92815 19:01:13.007 action_plan.go:168 I]     flutter_internal/ios/xcode/ios_runtime:xbExNWHTJfpNf8vDNXhmLNx9sjfFvAl4ed74gTrXl3cC
[P92815 19:01:13.007 instancecache.go:187 I] Using instance cache at /opt/s/cipd_cache/cache/instances
[P92815 19:01:13.009 client.go:1594 I] [fetch] Resolving fetch URL for flutter_internal/ios/xcode/ios_runtime:xbExNWHTJfpNf8vDNXhmLNx9sjfFvAl4ed74gTrXl3cC

https://logs.chromium.org/logs/flutter/led/magder_google.com/34b0add45b8fe97daadbfb8f634b2426c6fdea1e39c03af96488ca5ff59eb6f2/+/u/install_xcode/stdout

That one is using L7ipPezGFZNueu6j99coF-PbUIE6l-bUXDK5mHNOOoQC maybe they changed the behavior?

And it passed as a try job from https://github.com/flutter/flutter/pull/99009 so what's up with staging? https://ci.chromium.org/p/flutter/builders/try/Mac module_test_ios/12059

This is strange.. Try and staging have exactly the same configs..

Maybe we just need to be explicit that we want that runtime? https://github.com/flutter/flutter/pull/99093

One difference is the mac os version: staging bots are all with 12.0.1 whereas try bots are with 12.2. Will this cause the different behaviors?

staging bots are all with 12.0.1 whereas try bots are with 12.2

I don't think that should matter, the mac_toolchain just isn't pulling in the default runtime.
https://g3doc.corp.google.com/company/teams/chrome/ios/docs/infra/xcode_upload.md?cl=head#upload-ios-runtimes

iOS builders will use the default runtime from the Xcode used for building. iOS testers will dynamically download (or read from cache) the runtime it needs during task.

See also https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/cmd/mac_toolchain/README.md

staging bots are all with 12.0.1 whereas try bots are with 12.2

I don't think that should matter, the mac_toolchain just isn't pulling in the default runtime. https://g3doc.corp.google.com/company/teams/chrome/ios/docs/infra/xcode_upload.md?cl=head#upload-ios-runtimes

iOS builders will use the default runtime from the Xcode used for building. iOS testers will dynamically download (or read from cache) the runtime it needs during task.

See also https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/cmd/mac_toolchain/README.md

This is because the devicelab builds use a different recipe module that does not have support for runtimes. We'll need to copy https://cs.opensource.google/flutter/recipes/+/main:recipe_modules/osx_sdk/api.py to https://cs.opensource.google/flutter/recipes/+/main:recipe_modules/devicelab_osx_sdk/api.py and fix the destination folder to /opt/flutter/xcode/%s/XCode.app

This is because the devicelab builds use a different recipe module that does not have support for runtimes.

But the recipe shouldn't need to handle downloading the default runtime, mac_toolchain does it.  We would only need the recipe change if we needed to add additional runtimes.  Which we shouldn't if it was behaving correctly and the default iOS 15 one was being installed...

Like this:

Here's an example of a led engine builder run that shows what this should look like when there's an Xcode cache miss:
Packages:
  flutter_internal/ios/xcode/ios_runtime:xbExNWHTJfpNf8vDNXhmLNx9sjfFvAl4ed74gTrXl3cC
[P92814 19:01:12.305 action_plan.go:160 I] In root:
[P92814 19:01:12.305 action_plan.go:166 I]   to install:
[P92814 19:01:12.305 action_plan.go:168 I]     flutter_internal/ios/xcode/ios_runtime:xbExNWHTJfpNf8vDNXhmLNx9sjfFvAl4ed74gTrXl3cC
[P92814 19:01:12.305 client.go:1655 I] Dry run, not actually doing anything.
[P92815 19:01:13.007 action_plan.go:160 I] In root:
[P92815 19:01:13.007 action_plan.go:166 I]   to install:
[P92815 19:01:13.007 action_plan.go:168 I]     flutter_internal/ios/xcode/ios_runtime:xbExNWHTJfpNf8vDNXhmLNx9sjfFvAl4ed74gTrXl3cC
[P92815 19:01:13.007 instancecache.go:187 I] Using instance cache at /opt/s/cipd_cache/cache/instances
[P92815 19:01:13.009 client.go:1594 I] [fetch] Resolving fetch URL for flutter_internal/ios/xcode/ios_runtime:xbExNWHTJfpNf8vDNXhmLNx9sjfFvAl4ed74gTrXl3cC

https://logs.chromium.org/logs/flutter/led/magder_google.com/34b0add45b8fe97daadbfb8f634b2426c6fdea1e39c03af96488ca5ff59eb6f2/+/u/install_xcode/stdout

Played around a bit with runtime via led:
By specifying the runtime_version:ios-14-0 ('$flutter/osx_sdk={"sdk_version": "13a233", "runtime_versions": ["ios-14-0"] }'), it installed the correct runtime, and the runtime shows up in list simulators: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/keyonghan_google.com/4c5ed369b54fe8780f4d6ee9c1db3df0003bd79654b54e114f68377547ab7555/+/build.proto
When using runtime_version: ios-15-0 ('$flutter/osx_sdk={"sdk_version": "13a233", "runtime_versions": ["ios-15-0"] }'), it installed the runtime, but the runtime doesn't show up in list simulators: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/keyonghan_google.com/bde43be1da39029643243b283b1284c04be99a9ebf2bc6b539f3d31c85b708f8/+/build.proto
Does this suggest something wrong this the ios-15-0 version?

The test was enabled in prod moments ago, and is running well. So the issue happens only in staging...

Based on the observation the only difference is the mac bot version.. I requested an os upgrade in crbug.com/1300948, just in case (we need to upgrade to 12.2 any way).

Bad caches of the xcode cipd package coming from tests while the package was created?

Duping this against https://github.com/flutter/flutter/issues/99429. Upgrading the bots is another way of doing a cache flush.

This seems to be happening again https://ci.chromium.org/ui/p/flutter/builders/try/Mac build_tests_2_4/18290/overview

Some updates here:
The current logic for managing runtimes is faulty:

If the runtime folder inside xcode is  a symlink is not being deleted, instead it is deleting the destination folder from the cache leaving a symlink point to a non existent directory.

One data point: the runtime issue started happening on bot: build842-m9 after a failed build: https://luci-milo.appspot.com/ui/p/flutter/builders/try/Mac module_test/14975/overview on Install gems step (03/24).

@godofredoc is working on a fix:
https://flutter-review.googlesource.com/c/recipes/+/28680 landed
https://flutter-review.googlesource.com/c/recipes/+/28684 to be landed

https://flutter-review.googlesource.com/c/recipes/+/28684


Cassie, Hand and Mug do not load in the demo

Hi, really cool work!
I played with the online demo https://zalo.github.io/mujoco_wasm/ on safari (16.3) + chrome (112.0.5615.49) and I noticed that the Cassie, Hand and Mug mujoco models are not shown.
Do they work only in specific browsers e.g. firefox?

Oops, nope, there was a residual broken function from a recent refactor to use properties instead of getter methods; somehow these functions must have escaped my notice...
Should be fixed in a few minutes when the GH Pages rebuilds.


[Bug]Issue on copper glass casing from Create:Crystal clear

Describe the bug
Some unnecessary block faces are not culled
Screenshots

Desktop (please complete the following information):
Mods:
Create-1.19.2-0.5.1.b
CreateCasing-1.19.2-1.2.1
Create_crystal_clear-0.2.1-1.19.2

That will be fix in the next update


Promise support

Are there plans to introduce a Promise based version of the library?
They have been in language since 2015 and now with async/await they are core part of how people write modern JavaScript

There is a https://github.com/Azure/azure-documentdb-node-q. Not using it personally so cannot tell much about it but it exists :)

+1 for that.

You can also take a look at documentdb-typescript. No TypeScript required if you're using modern JS and async/await.

This work is done in the v2 API which will GA later this year. You can follow that work on the new repo: https://github.com/Azure/azure-cosmos-js

Great! Thanks @christopheranderson . From even a quick 5 minute glance I can see the new API and library is huge improvement


Object Name Character Length

Hi,
There is 30 characters length restriction for object and field names for years. Isn't that possible for you to allow more than 30 characters of length? As of now when developing extensions we have to add affixes to object and field names and this makes it really difficult to find short version of the name.
Thanks in advance!

Hi @muratkarabek ! Thank you for your suggestion. We have considered this, but as Johan mentions in  #4488 , it would require a major refactoring of our system. As an alternative, we are investigating support for namespaces in AL.
I will close the issue as it is a duplicate of #4488


Incorrect SQL Syntax - Unclosed quotation mark after the character string

Hi, everyone.
I encountered a strange problem.When I run the same code on test platform using the same conf, it work well. Once I run the same code on production platform, I got the following error:
General SQL Server error: Check messages from the SQL Server

Msg 170, Level 15
General SQL Server error: Check messages from the SQL Server

Msg 105, Level 15, State 1
Server 'SERVER', Line 24
        Unclosed quotation mark before the character string '<E5><90>?'.

Msg 170, Level 15, State 1
Server 'SERVER', Line 24
        Line 24: Incorrect syntax near '<E5><90>?'.

My code is :
_, err := db.Exec(`
		INSERT INTO Table (
			field1
			, field2
			, field3
			, field4
			, field5
			, field6
			, field7
			, field8
			, field9)
			VALUES (
				?
				,?
				,?
				,?
				,?
				,?
				,?
				,?
				,?)`, info.TopMarketId, Info.MarketId, Info.GoodsId, Info.GoodsAttribute, Info.TrackDate, Info.Value, Info.TimeCreated, Info.TimeLastUpdated, Info.Type)
	if err != nil {
		log.Println("DB Exec failed: ", err.Error())
		return err
	}

Anyone can help?Thank you very much : )

In case like this I will fire up SQL Server Profiler and catch the exact command which is sent to the mssql.
The other way is to switch on freetds logging and find there the command:
export TDSDUMP=/tmp/freetds.log
./my_app
...
less /tmp/freetds.log

Once you find what is exactly sent to the mssql it should be obvious where we failed.


Build project using pyproject.toml rather than current use of setup.py with setup.cfg

Switch to building project using newer pyproject.toml based build.

440076d012e23206d321b6e74d5ba292ab2777e0

Additional commits to fix GitHub actions:
4d188d386cbb554c5f6078e30be1904d42190b21,
d0a714a95221e7286dc0a75ae0f17805acc8d51a,
8c214915ee88e53c100ff055f48a795766b360c5


Faker::Types minor cleanup

It'd be great if you could add examples in the docs with params and without params.

Thanks!


Support pushing all sensors and fix wrong metrics (prometheus).

Description:
For example all metrics with unit % match humidity.
This generate correct metrics like this
# HELP nut_ups_battery_charge sensor.nut_ups_battery_charge
# TYPE nut_ups_battery_charge gauge
nut_ups_battery_charge{entity="sensor.nut_ups_battery_charge",friendly_name="NUT UPS Battery Charge"} 98.0
nut_ups_battery_charge{entity="sensor.nut_ups_battery_charge_2",friendly_name="NUT UPS Battery Charge"} 97.0

Related issue (if applicable): fixes #
fixes #10084, fixes #9346

https://community.home-assistant.io/t/prometheus-missing-data/23888

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

Hi @michaelkuty,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Could you please upgrade the REQUIREMENTS? The lastest release of prometheus_client seems to be 0.1.0 and I assume that you have a running setup which would allow to test it.
Thanks

I'm guessing this PR is a breaking change even though it's presumably for the better. @michaelkuty am I correct?
@bah2830 you have done the recent changes to this component. What do you think about this change?

This is a breaking change but it is a needed change. Seems fine to me.
Defining the metric name based on the entity name could generate a lot of metrics when it was a label (No difference to prometheus), but that should be fine.

@michaelkuty please add a paragraph in the description, describing the breaking changes, for the release notes.

Yes, this produces a lot of metrics, but you can use exclude for pushing what you want.

@fabaff updated


Implementation details of the loss scaling algorithm

Thank you for sharing such great works!
I encountered the following problem during the reproduction of your paper and was wondering if you might be willing to offer some guidance or clarification.
I trained the 2M VIMAPolicy (with all weights initialized by their default initial distributions except T5) on a small subset of the VIMA-Bench dataset (32 samples per task and 13 tasks in total) and tried to make it overfit.
It can be found that the imitation loss (calculated by cross_entropy_loss(dist_dict._logits, discrete_target_action)) of different action attributes (such as pose0_rotation, pose1_position) can change very differently during the training process, like the plot showing below. In this experiment, the final loss is calculated by taking the sum of all those action attributes with equal weights and then normalized by time step length

The plot shows how different loss (per step) attributes converges.  for example, `pose0_rotation_0` means the loss associated with the first dimension of `pose0_rotation` at a single time step.

By zooming to the first and last 100 epochs of the experiment, it can be found all dimensions of pose0_rotation and the first two dimensions of pose1_rotation converge very quickly to zero while the other losses converge relatively slow. The scaling between them changes dynamically.

 First100 epochs

 Last 100 epochs

In the same experiment, I also measured the ratio of the average loss between different tasks and got the following table. For example, 16.745474 means that the average loss of rearrange_then_restore samples is about 16x larger than the one of novel_noun samples
novel_noun                     1.000000
sweep_without_exceeding        1.602642
rotate                         1.857377
visual_manipulation            1.998764
twist                          3.802508
manipulate_old_neighbor        4.956325
scene_understanding            5.033336
follow_order                   5.132609
rearrange                      5.827855
pick_in_order_then_restore    11.248917
rearrange_then_restore        16.745474

I would like to know how those losses (per action attribute and per task) are balanced during training. Thank you

I've encountered similar questions. I released everything I did here: https://github.com/amitkparekh/CoGeLoT, maybe it has some answers to your questions?


Add new localisation strings

Add new localisation strings for handling errors when requesting data from the API.

I'm going to keep the branch from now on...


Better input dataset hash handling

Closes #51 . Branched off #43 - do not merge until after merging #43.
This PR makes InputDataset.file_hash an optional attribute but throws an error in InputDataset.__init__() if source.location_type is "url" and file_hash is None. It also updates Case.from_blueprint to use dict.get rather than attempting to directly access potentially nonexistent keys for optional attributes (such as file_hash).
This behaviour improves consistency following #30  .

TIL backticks in commit messages make words disappear...
"make Optional with ValueError if None and is" = "Make InputDataset.file_hash Optional with ValueError if None and InputDataset.source.location_type is 'url'"

@TomNicholas Hoping to put this in so I can update the changelog in #55 (branched off this one). Any comments?


test: cases for both valid and confusing error messages re: types

(Initially as part of independent discovery of #3127.)


About download_data.sh

Thank you for your contribution!
May I ask if you provide the dataset?
I saw on the homepage it says
chmod +x download_data.sh
./download_data.sh

But I couldn't find this file？

Thank you for your interesting! Yes, we actually provide the dataset. We just added the download_data.sh to our repo. We actually used the the same dataset of Transfuser. Also, you can generate the dataset through Carla Simulator.

Thank you for your interesting! Yes, we actually provide the dataset. We just added the download_data.sh to our repo. We actually used the the same dataset of Transfuser. Also, you can generate the dataset through Carla Simulator.

Thank you for your response, but as far as I know, the dataset for Transfuser seems to lack the 'light' and 'stopsign' folders, which your model requires for supervision during training. When I attempted to generate data myself, I found that I had to comment out the lines in base_agent.py:
#'vehicle_present': self._vehicle_present,
#'walker_present': self._walker_present,
#'light_present': self._light_present,
#'stop_sign_present': self._stop_sign_present,

Otherwise, I encountered an
AttributeError: 'AutoPilot' object has no attribute '_vehicle_present' error.

However, after commenting out these lines, although the program runs normally, the generated data lacks the 'light' and 'stopsign' folders, resulting in being unusable for training.
So i'm not sure if the download_data.sh provided this time includes the 'light' and 'stopsign' files?

Actually, the stop sign and traffic sign information should be added to the dataset before training. I add two python files prepare_light.py and prepare_stopsign.py . I included instructions on how to use them in the readme.

Actually, the stop sign and traffic sign information should be added to the dataset before training. I add two python files prepare_light.py and prepare_stopsign.py . I included instructions on how to use them in the readme.

Thank you for your kind help.


Fix Name of the Elements CP cost

As of 5.1, the CP cost of Name of the Elements is now 30, instead of 15.

Thanks for the PR but we already have this change incorporated into the 5.1 patch update PR #333.


Profile mehari

Is your feature request related to a problem? Please describe.
We need to understand, which code paths influence mehari performance.
Describe the solution you'd like
Use flamegraph, DHAT to understand code paths and allocations. Add a branch with coz support. Look into https://crates.io/crates/criterion.
Describe alternatives you've considered
None
Additional context
This is the basis for additional work.

profiling
Profiling was done with an explicit profiling profile:
[profile.profiling]
inherits = "release"
debug = true

on a machine with the following specs
CPU: quad core Intel Xeon E5-1630 v3 (-MT MCP-)
speed/min/max: 1621/1200/3800 MHz Kernel: 6.5.0-28-generic x86_64
Mem: 9386.1/64180.0 MiB (14.6%) Storage: 685.61 GiB (26.7% used) Procs: 337
Drives:
  Local Storage: total: 685.61 GiB used: 182.78 GiB (26.7%)
  ID-1: /dev/sda vendor: Samsung model: MZ7LN256HCHP-00000 size: 238.47 GiB  # hosts /, /home
  ID-2: /dev/sdb model: MZ7KH480HAHQ0D3 size: 447.13 GiB  # hosts mehari DB

flamegraph
Only uses the first 1M records from the input file (NA-12878WGS_dragen.vcf.gz)
invocation
cargo flamegraph --profile profiling --bin mehari -- annotate seqvars --path-db /mnt/data/mehari/0.21.0/db --path-input-vcf tests/data/annotate/seqvars/NA-12878WGS_dragen.first1M.vcf.gz --path-output-vcf /tmp/NA-12878WGS_dragen.first1M.annotated.vcf.gz --path-input-ped data/FAM_BE_10.sup.ped

result

dhat
Only uses the first 100k records from the input file (NA-12878WGS_dragen.vcf.gz)
invocation
cargo run --profile profiling --features dhat-heap --bin mehari -- annotate seqvars --path-db /mnt/data/mehari/0.21.0/db --path-input-vcf tests/data/annotate/seqvars/NA-12878WGS_dragen.first100k.vcf.gz --path-output-vcf /tmp/NA-12878WGS_dragen.first100k.annotated.vcf.gz --path-input-ped data/FAM_BE_10.sup.ped

result
dhat-heap.json
coz
Figure out reasonable scopes before running coz.

At the moment, my reading of this is roughly:

have a look at ConsequencePredictor (predict/build_ann_field)
is using bcf instead of vcf an option? (smaller files, less text parsing)
check hgvs Mapper g_to_n
…

caching build_alignment_mapper: 103s/1M records → 71s/1M records

Setting lto = "fat" and codegen-units = 1 shaves another ~8s off the 1M records timing.

Using noodles Async{Reader, Writer} shaves another ~10s off the 1M records timing. (54s/1M records)

@tedil impressive 50% time saved!


ubuntu 22 depends build failure

This issue tracker is only for technical issues related to Raptoreum Core.
General Raptoreum questions and/or support requests and are best directed to the Raptoreum Discord.
To report critical security issues, DM the Core or Developer Teams instead of creating Github issues.
Describe the issue
Depends do not current build on ubuntu 22. Need to be able to build on ubuntu 22.

Just some more info about the problem of more specifically boost not compiling.

It is because some constants (in this case PTHREAD_STACK_MIN were changed in glibc-2.34 and ubuntu uses glibc-2.35.

The boost compile can be "fixed" by changing  one macro in boost/thread/pthread/thread_data.hpp:60:
#if PTHREAD_STACK_MIN > 0
    if (size < PTHREAD_STACK_MIN) size = PTHREAD_STACK_MIN;
#endif

into
#ifdef PTHREAD_STACK_MIN
    if (size < static_cast<std::size_t>(PTHREAD_STACK_MIN)) size = PTHREAD_STACK_MIN;
#endif

This is just that particular part but from a higher version of boost where it was changed already since boost-1.73

Default gcc compiler on Ubuntu 22.04 is now gcc-11 which also causes some problems when compiling the boost 1.70 library. I'm a little lost in the boost lib so I cannot provide a simple fix for it :/

Just fixing 1. allows for compilation but requires a change of the compiler to gcc-10.
Both of those issues are addressed in boost 1.73.


Updates

Pull Request
Short Summary
Fix a few naming consistencies.

Defaulting name and repository to __missing__ instead of raising an error. This is done so that we can inject name and repository into the DriftProfile when creating a modelcard in OpsML

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

Project coverage is 91.93%. Comparing base (a375771) to head (a10ddc3).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #16      +/-   ##
==========================================
+ Coverage   91.90%   91.93%   +0.03%
==========================================
  Files          12       12
  Lines         531      533       +2
==========================================
+ Hits          488      490       +2
  Misses         43       43

Files with missing lines
Coverage Δ

py-scouter/python/scouter/drift.py
90.00% <100.00%> (ø)

py-scouter/python/scouter/utils/types.py
100.00% <100.00%> (ø)


Add what-the-commit extension

Description

This is a basic extension that calls the https://whatthecommit.com/index.txt endpoint to fetch a absurd and comical commit message. Then it displays the commit message and gives the user to copy and paste the generated message.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi!
Thank you for your contribution! My name is Milena and I will be reviewing it today.
We have an extension on the store that does the exact same: https://www.raycast.com/rokartur/commit-message-generator
Or am I missing something from your extension?

Hi,
Thank you for looking into the extension.
I did not discover the extension you mentioned when searching for it. Hence the same contribution. I would be more careful next time.
Sorry for the inconveniences caused
On 4 Jul 2024 at 3:23 PM +0530, Milena Araujo @.***>, wrote:

Hi!
Thank you for your contribution! My name is Milena and I will be reviewing it today.
We have an extension on the store that does the exact same: https://www.raycast.com/rokartur/commit-message-generator
Or am I missing something from your extension?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Though the extensions do the same thing, there is a subtle difference in that, the one mentioned has an array of commits, from which it selects a random one, while mine actually queries the whatthecommit.com endpoint to get the message.
Though I am not sure if both have the same commits list.
On 4 Jul 2024 at 4:08 PM +0530, Pranshu Goyal @.***>, wrote:

Hi,
Thank you for looking into the extension.
I did not discover the extension you mentioned when searching for it. Hence the same contribution. I would be more careful next time.
Sorry for the inconveniences caused
On 4 Jul 2024 at 3:23 PM +0530, Milena Araujo @.***>, wrote:

Hi!
Thank you for your contribution! My name is Milena and I will be reviewing it today.
We have an extension on the store that does the exact same: https://www.raycast.com/rokartur/commit-message-generator
Or am I missing something from your extension?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Well, I would encourage you to make that change to that extension instead of making a new one, if you believe querying the website is a better way to do it.
Closing due to duplication.


Don't push a change if there haven't been any updates

This is spamming with unnecessary updates.  The result is that this repo is almost always at the top of https://github.com/sympy/, and I even once noticed it at https://github.com/timeline, which I think would normally be pretty rare.  The bot should push only when there is something to push.

I absolutely agree. However I don't have time currently to implement this. It shouldn't be that difficult --- pretty much this line:
https://github.com/sympy/planet.sympy.org/blob/master/server_update#L40
has to be modified. If anyone would like to give it a shot, that'd be great.

For now, since the summer is over, I have decreased the bot frequency from every 20 minutes to every 2 hours. Let's fix it though, that'd be much better.

Do you know how to do it?  It looks to me like it recreates the whole planet from scratch, then replaces the old one, so it's not obvious to me how to tell if something significant has changed or not.
I did notice that the rss10.xml and rss11.xml files are only updated when something changes (btw, I found 2f78760189bc0306059089bc2442bdc197aa9276 as a random example of a commit that actually changed something, since this is non-trivial to do).  Do you know if this is always the case?  If so, then we can make the rule to only commit if one of those files was updated (or maybe just if any file other than the three that are always updated is updated).  Will that always work?  I don't know too much about planet.

Good catch. That could work. I don't know much myself, but at least we have things tracked by git, so that we can experiment and improve.
Btw, I made a mistake in the cronjob, and it was executing every minute. Oops. I fixed it finally, now it should run every two hours.

Ok, I think I have fixed this in 87a03cfe5d5632b1ebd6510b0bf14bfb5b1eefbc. I did a few tests and things seems to be working well. I am now running the bot every 20 minutes, and no change is pushed unless rss10.xml changes, see the commit. I am closing this one.

I have to reopen it. Aaron,  your blog is causing it to flip the RSS each time

I have no idea what's going on there.  Obviously, my blog is just a vanilla WordPress blog, so I don't control any of that.  Maybe it's a bug in planet.
By the way, why was gh-pages forced updated?  Because of the 1 minute updates?

I forced updated it, so that instead of 50+ MB, the git repo only has 2MB. For easier manipulation.

So I think that we need to write a simple Python parser, that would parse the rss feed before and after, and tell the number and type of commits, somehow, and decided, whether something has changed or not.

Maybe we should contact planet and see if they've already solved this problem.

I am currently a little busy, but it shouldn't be hard to fix this issue for good with a simple Python script, checking the changes with the help of git diff.


Self defined entities

Hi,
Can the model be used to train on own dataset with self-defined entity types? If so, is there a tutorial how to do it?
Thanks.

You can look at examples/ there is fine-tuning notebook. You may also check train.py and data/

yes, exactly

You should pass a validation data (eval_data) to monitor the performance
you can also modify the code and log the validation performance in a text file


ApplicationCommand missing fields

DiscordGo v0.25 is missing fields for ApplicationCommands documented here: https://discord.com/developers/docs/interactions/application-commands#application-command-object

default_member_permissions - Implemented on master
dm_permission - Implemented on master
guild_id

default_permissions will soon be removed infavor of default_member_permissions.
Registering commands via the guilds endpoint will soon be depricated infavor of restricting a command to a guild on the ApplicationCommand object

Having the same issues with the examples.
ApplicationCommandPermissionTypeChannel not declared by package discordgocompilerUndeclaredImportedName

Having the same issues with the examples. ApplicationCommandPermissionTypeChannel not declared by package discordgo compiler UndeclaredImportedName

Permissions aren't released yet. To use them you can use the master branch however:
go get github.com/bwmarrin/discordgo@master

DiscordGo v0.25 is missing fields for ApplicationCommands documented here: https://discord.com/developers/docs/interactions/application-commands#application-command-object

default_member_permissions - Implemented on master
dm_permission - Implemented on master
guild_id

default_permissions will soon be removed infavor of default_member_permissions. Registering commands via the guilds endpoint will soon be depricated infavor of restricting a command to a guild on the ApplicationCommand object

Sorry for a late response, can you link the documentation/changelog on where the "registering commands via ..." behaviour is described. Can't seem to find it anywhere.

It has yet to be announced. Its been discussed to remove duplicate endpoints.


Release v0.23.0 changelog update

I had wanted to get the turbomole Hessian correction (#349) and the cleanups (#350) in, but I didn’t communicate that well, and I haven’t been able to give them the review attention needed. and I don’t want to hold up openff, so please go ahead @dotsdl .  apologies, @coltonbh and @eljost .


tracer copies multiple files to same location, triggering file corruption

Environment
Nitropack 0.3.8
Node v16.14.2
Reproduction
npx nuxi init nuxt3-app
cd nuxt3-app && pnpm i --shamefully-hoist
pnpm build && node .output/server/index.mjs

Sometimes this will trigger an error due to a ufo package.json corruption.
Describe the bug
Multiple minor version copies of the same package are being written to the same location in .output/server/node_modules, which sometimes triggers file corruption.
Additional context
No response
Logs
No response

https://github.com/nuxt/framework/runs/7251588947?check_suite_focus=true


remove fetch of msi since nvm is used

Thanks!

you're welcome @bbyars. when would you make another release? Trying to use the updated dependencies in our mountebank server in order to get rid of the vulnerability in the ejs package.

Sure, just released.
On Sat, Aug 19, 2023 at 12:38 AM Arvind Sridharan @.***>
wrote:

you're welcome @bbyars https://github.com/bbyars. when would you make
another release? Trying to use the updated dependencies in our mountebank
server in order to get rid of the vulnerability in the ejs package.
—
Reply to this email directly, view it on GitHub
https://github.com/bbyars/mountebank/pull/739#issuecomment-1684835722,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAARFP5NKHE54ITM7RII3ZLXWBGOBANCNFSM6AAAAAA3VA3WLA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add sbi_fence_dma function in memory model.

Signed-off-by: Guo Ren<EMAIL_ADDRESS>

@guoren83 : I am closing this due to lack of interest. This kind of feature fits under vendor extensions.


Add notification count label

This was having too many problems with the bigger changes of the wizard... I reopened as #94