Use Finnish locale in postgres in local development

Description :sparkles:
Use Finnish locale for the Postgres instance used for local development
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Commit message could be made specific to benefit, e.g. "BF: " or "BF-Backend: " prefix would solve that.

good idea. Maybe we should use this practice in the future, when the context is not clear otherwise, for example if Jira issue ID isn't clearly visible in the case


Using proxy user for Oracle Connections

Support for Oracle Proxy User through jdbc url sintax:
--url=jdbc:oracle:thin:PROXY_USER/@host:port/servicename

Thanks!


SparseConvTensor attribute is missing for spconv at runtime

Thank you very much for sharing this project. Here is a problem that I need to ask you. I debugged it myself and didn't solve it. Do you know the cause of this error?The specific error message is"AttributeError: module 'spconv' has no attribute 'SparseConvTensor'"

Thank you for your answer. I have improved this question according to your suggestions.Here is another question to ask.The results of the test code only have exponential results. Is there any way to visualize the results?Thank you again for your code sharing, and we look forward to your answer to the visualization of the results.


Support file syscall which are used by mkvmerge command.

This issue is originated from this discussion

Based on the error, it might be that mkvmerge is calling a file syscall we don't support yet. You can open another issue for that and we that's more feasible then the original issue.

Currently we can not debug programs which contains mkvmerge command because it seems mirrord doesn't support some of its underlying file syscalls.
More information
This is just a reminder from mentioned issue.
Target code:
 async merge(
    framerate: number,
    sourcePath: string,
    destinationPath: string,
  ): Promise<string> {
    // Two following lines, convert relative path to absolute path:
    sourcePath = sourcePath.replace(/^\.\//, '/app/')
    destinationPath = destinationPath.replace(/^\.\//, '/app/')

    if (framerate <= 0) throw new Error(`Received ${framerate} as framerate.`)
    this.logger.verbose(
      `Merging matroska multimedia with: mkvmerge --default-duration 0:${framerate}fps ${sourcePath} -o ${destinationPath}`,
    )

    return new Promise((resolve, reject) => {
      const child = spawn('mkvmerge', [
        '--default-duration',
        `0:${framerate}fps`,
        sourcePath,
        '-o',
        destinationPath,
      ])

      child.stderr.on('data', (chunk) => {
        this.logger.warn(chunk)
      })
      child.on('error', (err) => {
        this.logger.error(
          `Merging matroska failed: ${err.name} | ${err.message}`,
          err.stack,
        )
        reject(err)
      })
      child.on('close', (code, signal) => {
        if (code !== 0) {
          this.logger.error(
            `Merging matroska video faild with code ${code} and signal ${signal}`,
          )
          reject(code)
        } else {
          return resolve(destinationPath)
        }
      })
    })
  }

Here is output of debugging with mirrord:
VERBOSE [Matroska] Merging matroska multimedia with: mkvmerge --default-duration 0:25fps /app/media/da86527f-c75f-4e52-a98a-59186cbe0ba4/add17fb6-b571-434b-aaf8-7f1d45cc830f-1730724272420/recording-merged.webm -o /app/media/da86527f-c75f-4e52-a98a-59186cbe0ba4/add17fb6-b571-434b-aaf8-7f1d45cc830f-1730724272420/add17fb6-b571-434b-aaf8-7f1d45cc830f-fixed-framerate.webm
[Nest] 36046  - 11/04/2024, 9:41:24 PM    WARN [Matroska] terminate called after throwing an instance of 'boost::filesystem::filesystem_error'
  what():  boost::filesystem::status: Function not implemented [system:38]: "/app/media/da86527f-c75f-4e52-a98a-59186cbe0ba4/add17fb6-b571-434b-aaf8-7f1d45cc830f-1730724272420"

Thanks for the elaborate report!


Jupiter

Add support for jupiter

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

1.2.0
GitHub release

Your semantic-release bot :package::rocket:


ENH: pdfly x2pdf --layout

The new --layout parameter would allow the following values:

2x2 : meaning to combine input files on every page of the output PDF document so that it forms a grid of 2 columns & 2 rows ( this is similar to https://github.com/pmaupin/pdfrw/blob/master/examples/4up.py )
3x3 : same, with a grid of 3 columns & 3 rows
1x2 : same, with a grid of 1 column & 2 rows
2x1 : same, with a grid of 2 columns & 1 row

Hello! I would like to help you with this issue! Please assign me

Hello! I would like to help you with this issue! Please assign me

Hi @mulla028
Are you willing to work on both this issue and https://github.com/py-pdf/pdfly/issues/63?

Hello! I would like to help you with this issue! Please assign me

Hi @mulla028
Are you willing to work on both this issue and https://github.com/py-pdf/pdfly/issues/63 at the same time?
It may be better to tackle them one after the other 🙂

I have already opened a PR for issue #63, waiting for your review. I also started working on this one.

Hello! I would like to help you with this issue! Please assign me

Hi @mulla028
Are you willing to work on both this issue and https://github.com/py-pdf/pdfly/issues/63 at the same time?
It may be better to tackle them one after the other 🙂

@Lucas-C for these two issue (#63 & #64) I am opening two separate PRs.

@Lucas-C for these two issues (#63 & #64) I am opening two separate PRs.

Alright, go on then 👍


Update to a more recent rtdb emulator version

First time the integration tests have passed on CI in days. I'm not sure if it's luck or the newer emulator. Either way, this should merge.
#no-changelog

I wasn't able to repro anything related to #13877, but hopefully the integration tests are now more stable.

Nice to see the nightly run for the integration test passed too!


[icon request] Emoticon

Icon name
emoticon
Use cases

used in keyboard ui representing emoticons (e.g. ;-), B), ;-(, :^), (*_*),XD, <3, T_T)

Design ideas
Here's what I made:

Which one is good?
Checklist

[X] I have searched if someone has submitted a similar issue before and there weren't any. (Please make sure to also search closed issues, as this issue might already have been resolved.)
[X] I have searched existing icons to make sure it does not already exist and I didn't find any.
[X] I am not requesting a brand logo and the art is not protected by copyright.
[X] I am not requesting an icon that includes religious, political imagery or hate symbols.
[X] I have provided appropriate use cases for the icon(s) requested.

If it's for grapheme based emoji, I'd rather keep it as close to parentheses as possible:

Oh good, yes it is a grapheme based emoji. The colon will works, that's the most common.


Setting with empty value fails to convert to null-string

Giving following .ini-file and class:
[FOO]
SETTING=

public class FOO
{
  public string? SETTING { get; set; }
}

Reading the file with <IP_ADDRESS>, which was written with 3.2.8, and mapping the Section object to an actual object with SetValuesTo(object) now fails with the:
SharpConfig.SettingValueCastException: Failed to convert value '' to type System.String.
   at SharpConfig.Setting.CreateObjectFromString(String value, Type dstType, Boolean tryConvert)
   at SharpConfig.Setting.GetValue(Type type)
   at SharpConfig.Section.SetValuesTo(Object obj)
   at MY CODE ^^

There is no workaround available, since the default (false) for the tryConvert parameter of Setting.CreateObjectFromString is never overwritten!

Hi, I couldn't reproduce the exception; the object is constructed with SETTING's value being the empty string. Please verify in Setting.cs whether obj is the empty string or null.

Hi, and thanks for the follow-up!
Mea culpa, I have a custom string-converter, which returns null rather than string.Empty which makes the following comparison fail.

Sure thing. So reading from the title, you expect the string conversion to return a null-string? Just to be clear. At this moment, an empty setting value will let the converter return an empty string respectively, because the conversion is valid. Only invalid conversions should return null.

I am not sure, whether I should expect this OOTB - but this is, where custom converters kick in :)
Naming a method TryXXX should follow the best practice: indicate the success via a bool-return type (and the actual result via an out-parameter) rather than a magic value!

I am not sure, whether I should expect this OOTB - but this is, where custom converters kick in :)
Naming a method TryXXX should follow the best practice: indicate the success via a bool-return type (and the actual result via an out-parameter) rather than a magic value!

Yes, the naming is unfortunate. However, I won't drastically change the converter API until the next major release. So for the time being, we'd have to stick with the magic null values.

Fair enough. I then have to wait for the next major release.
Thanks for your input!

I see. So you're able to work around this issue for now?

Yep, sticking to 3.2.8 ;)

Noted. Thanks for reporting these issues by the way.


Bump version of actions/setup-python

When I created this workflow, the version of actions/setup-python was set to v4. When you updated the workflow, you changed it to v2. As it might be nicer to go with more modern versions, I am considering bumping the version. Was there a specific reason you went for this version or can I just bump it?

Hi @felix-seifert , that was not my intention. To be honest, I have no idea what happened. I was just merging your PR to the main branch, I did not changed anything.


no-jira: Fix dockerfile

SSIA

/override ci/prow/e2e-aws-operator
/override ci/prow/images
/override ci/prow/security
/override ci/prow/unit
/override ci/prow/verify

@openshift-ci openshift-ci bot assigned evakhoni Nov 27, 2024

please stop this. received over 30 notifications just today from oc, for PRs that i have nothing to do with

opened https://github.com/openshift/release/pull/59284

@evakhoni apologies for the noise. I do not know why you are getting assigned here. This is part of Konflux onboarding and there's not much I can do about the noise. Please, feel free to filter out any email notification coming from this repository.

ok. hope my pr removing myself from the tags will clam the bot.


Bring Your Slot Machine to Life requires double quotes to pass

Challenge http://freecodecamp.com/challenges/waypoint-bring-your-javascript-slot-machine-to-life has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
There's no syntactic reason to require double quotes. The following should pass, but fails.
    $($('.slot')[0]).html(slotOne);
    $($('.slot')[1]).html(slotTwo);
    $($('.slot')[2]).html(slotThree);

Switching to double quotes passes.

I just had this happen to me as well. I couldn't figure out for the life of me what was wrong with what I had written.

Just had the same thing happen to me. Thanks for opening this.

Hey @denmch thanks for posting this.
We have a few duplicate postings of this so see #2522 for updates on this issue.
Please close this as a duplicate, and take a look at our Bug Report Guidelines.

I know you mean well, but keep in mind that you're asking people who posted 3 or 5 days ago to check the guidelines because someone else who posted 2 days ago got a response. I know the guidelines and follow them. This isn't a perfect process, and we can't predict the future.


Please tag/release a new version

~The problem described here still exists in main's HEAD.~
~Update methods are still generating insert queries.~
~I did some grepping and was not able to find exactly where this occurs, unfortunately, but I suspect it's rooted in the logic that converts an Update to an Insert or vice versa; that happens here and there throughout the library.~
Please ~fix and also~ tag a new release; there have been some fixes that are not included in the latest tagged.
EDIT: Whoops! Didn't catch that I had a submodule. Updated that to use main HEAD and can confirm the proper update Operations are generated! A new tag is probably needed, especially with the context stuff.

Directly iterating over each of the generated operations and explicitly setting the operation as an Update does work and leads to expected behavior, e.g.:
for ... {
	if tmpOps, err = c.Where(np.old).Update(np.new, &np.new.Tag); err != nil {
		log.Panicln(err)
	}
	txOps = append(txOps, tmpOps...)
}

for idx, _ := range txOps {
	txOps[idx].Op = ovsdb.OperationUpdate
}

I have confirmed this by both tracing the messages sent on the Open vSwitch socket and dumping the operations generated by the .Where(...).Update(...) that Update() does, indeed, generate insert instead of update operations -- which (of course) is what causes the error found in #193 .

Thanks for the reminder @nf-brentsaner
https://github.com/ovn-org/libovsdb/releases/tag/v0.7.0


gyro and accel scale wrong: should be specified in milli-unit per bit!

possibly also wrong in Adafruit driver: https://github.com/adafruit/Adafruit_LSM6DS/issues/40
this gives better values for acceleration when using other scales than
2.
Please take a good look on this one, not sure if it is correct.

Basically it seems like I introduced this error here: 23dbc52 ! However, the gyro values are still wrong in the same way as the adafruit driver is. If that is the case.

I've asked on the ST forum: https://community.st.com/t5/mems-sensors/ism330dhcx-gyro-range-in-driver-calculation-does-not-make-sense/m-p/605528#M21746

I think it is correct now. The scaling for the gyro is given in the datasheet as mdps / LSP in table 2.

I have made some more structural changes. These will make it easier to keep track of units, scaling and not mixing different value types.

@gauteh finally had time to look into this!
Tested it on my end and the values indeed look better with the fix, nice spot haha
I'll borrow your idea for the value types and add it to the magnetometer later
one thing, do you mind rewording the commits to adhere to the "conventional commits" convention?
then our versioning bot can pick up the changes and generate the changelog right away (not sure I can push to this branch to help)
otherwise, as soon as I merge I'll release the new version to crates.io!

Nice, thanks. I think you can rebase+edit+amend the commits. Not sure how you want the text. What magnetometer? I need to add one to my project soon 😁

I don't have access to your repo, so I'll do a little duct tape on main, should be fine :D

Thanks! I forgot to check the allow edits box! Sorry about that.


can you add here this tool | GO111MODULE=on go get -u github.com/xm1k3/cent

GO111MODULE=on go get -u github.com/xm1k3/cent
add this tool  for update  nuceli templates

Cent is used to download and keep updated a lot of third party nuclei templates, in most of the cases duplicates or not well designed causing errors. In reconFTW nuclei templates are updated on every run and I prefer to stick to the official templates for the moment, anyway you can add any template to your templates folder.


New Feature Request 2.0

Cheers for that latest change, brilliant response time.
Possible to code in a limit system too as in able to specify a limit to how many whitelists you can have per user?
Would be brilliant to have for my SMP community where they can have say 3 whitelists of a friend.
If not, no problem!

Should be possible but it would have to be in a separate discord role. I'll take a look into it.

Should be possible but it would have to be in a separate discord role. I'll take a look into it.

No rush, could be done via specifying a limit per role?

How does the bot work in regards to people having _ in their name? For example, few of my players have underscores either side of their name and discord markdown converts that into italics. Does the bot pick up the username?

if you're talking about their minecraft names the bot will pick it up just fine, it's just discord that the name will appear altered. if you're on about their discord names you can just get their id which is stored as a number which also helps if they change their name later on.

Yeah I was talking about their minecraft name, that's fine though cheers.
Can't wait for the update if it comes, cheers for everything btw.

@LubricantJam I added a limited whitelist role to the latest version (https://github.com/JoeShimo/DiscordWhitelisterBot-Spigot/releases/tag/1.0.4) if you wouldn't mind testing it for bugs, it seems to run fine but I may have missed something. You'll need to remove your old config and use the new one if you do, thanks.

Seems to work fine :)


First round of engagement - CAS Staff

Describe the task
Reach out to first group of CAS & EMILI staff to get an understanding of their perspectives on access to climate related data.
Acceptance Criteria

[ ] Reach out to staff (Hilary, Jen, Elaine, Nancy, Rob) & book sessions
[ ] Develop questions
[ ] Hold session
[ ] Document feedback

FYI @jaimiebutton - I added Rob T to this ticket, which I'm assuming we will want to start next sprint?

Thanks @LindsayMacfarlane, adding Robb here is a great call!

Thank you so much @jaimiebutton ! This first round was fantastic and a great start to user engagement.


 See the net/http docs.
A better forum for discussion is probably the mailing list. See https://golang.org/wiki/Questions

i close...

me,too

sometimes (randomly) it doesnt work. looks like response body ignores Close call
after 100k requests or works several days and then sometimes appears readLoop + writeLoop. these go routines are not used anymore and they slowly grows. and i think they are not in idle conns list.
resp, err = hc.Transport.RoundTrip(req)
if resp != nil {
	if resp.Body != nil {
		defer resp.Body.Close()
	}
}
if err....

For questions about Go, see https://golang.org/wiki/Questions.


Settings with custom prompts

The thread starts in https://github.com/carlrobertoh/CodeGPT/issues/20
To bring prompts in another language, custom prompts, add personal prompts, fix prompts without waiting for a release, etc. it can be interesting to have this in the settings of the plugin with the form of a table with:

a name, the same name will be used dynamically in the submenu of the right-click
a prompt, with a limited form of formatting to include info like the part selected, the language detected, etc.

The Environment Variables of the Run configurations can be a good candidate for inspiration of the GUI.
Example:

You can see the name column with a short name to be reused in the GUI and prompts with some sort of formatting to dynamically be replaced during call {{known part}}}.

For example, in the settings without the add, copy, delete, etc.

https://github.com/rangzen/CodeGPT/tree/lme-custom-prompts-experiment

For example, in the settings without the add, copy, delete, etc.

Perhaps it needs to be entirely new settings panel?
CodeGPT:

Prompts

https://github.com/dpayne/CodeGPT.nvim#overriding-command-configurations

Yeah, I think the value overriding shouldn't apply to prompts only.
Almost everything can be done via configuration table/settings, e.g. I think there's no point of creating some fancy user interfaces only to change some of the request params.

https://minimaxir.com/2023/03/new-chatgpt-overlord/
Didn't know about the "system" part... Interesting

https://minimaxir.com/2023/03/new-chatgpt-overlord/ Didn't know about the "system" part... Interesting

https://github.com/f/awesome-chatgpt-prompts/blob/main/prompts.csv

Thank you!
I will try to add more features step-by-step whenever I have time altho I'm worried about breaking stuff since the code lacks of tests.


feat: Use subscription to track changes in Gallery Item

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[x] Refactoring

Context

[x] Closes #4614
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </bsx/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

✅ Tested: the info of gallery item will update after subscription message coming
I relist the nft and change the price from another window. https://beta.kodadot.xyz/snek/gallery/659233203-5
Then the price of nft was changed accordingly, without polling the request. https://deploy-preview-4633--koda-nuxt.netlify.app/snek/gallery/659233203-5?redesign=true

pay 50 usd

😍 Perfect, I’ve sent the payout
💵 $50 @ 24.71 USD/KSM ~ 2.023 $KSM
🧗 Caiv9TbPz68q5dC8EcHu5xKYPRnremimGzqmEejDFNpWWLG
🔗 0xcfccc2b68a37837494f266e27320a8983bf87ea6a40ab8295bd3fbe301570149
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues

@vikiival merge it if good

related with #2201

pay 70 usd

pay 70 usd

bounty has been paid in the previous comment.

Please fix deepsource

✅ Fixed


MB-15567 Discovery: How does our integration with DTOD work (The Environment Variables part)

Add documentation around how environment variables get from AWS into Go.
I went with putting it under the CI/CD because it felt like that was the most relevant spot. However, if folks think it should be somewhere else, I'm open to moving it too.

question: Is this about how we use environment variables locally or in CI? I know you said it's about AWS env variables in go, but I'm asking if we're going for local or CI docs because I think the answer is different depending on the environment.
Like for example, this seems to be where circleci sets up access to the aws staging secrets: https://github.com/transcom/mymove/blob/d99f31acbb6d42a4b2eb341aeab30ebc9366fc40/.circleci/config.yml#L216-L225
and then that command gets used as needed in jobs as needed, like this one: https://github.com/transcom/mymove/blob/d99f31acbb6d42a4b2eb341aeab30ebc9366fc40/.circleci/config.yml#L1415-L1425
I could definitely be wrong though, I don't know much about how we manage secrets in circleci, I'm just guessing based on what it looks like those parts of the config are doing.
So, I think what you're documenting here is more about local dev, which means it could likely go in the backend section. There are some env vars we use on the FE, like A11Y_AUDIT and some playwright vars, but those aren't currently set anywhere in the .envrc files or loaded in chamber, so idk where those should be documented.
Maybe since env var setup could be across the app, it could be somewhere more shared like the project layout is: https://transcom.github.io/mymove-docs/docs/about/project-layout or maybe we need a new shared section? Idk, categorization is hard 😅

Categorization is hard!
I think I'll make a new section in the backend and put it in there since that feels most appropriate.

Oh looks like that page that moved needs to have references to it updated. I'm seeing these:
https://github.com/transcom/mymove-docs/blob/6e79bf5b76325bdd8e42f8d0e7a65b3dc369b04d/docs/tools/docusaurus/docusaurus.md?plain=1#L208-L217
https://github.com/transcom/mymove-docs/blob/6e79bf5b76325bdd8e42f8d0e7a65b3dc369b04d/utils/redirect-backend.js#L152-L157

Oh looks like that page that moved needs to have references to it updated. I'm seeing these:
https://github.com/transcom/mymove-docs/blob/6e79bf5b76325bdd8e42f8d0e7a65b3dc369b04d/docs/tools/docusaurus/docusaurus.md?plain=1#L208-L217
https://github.com/transcom/mymove-docs/blob/6e79bf5b76325bdd8e42f8d0e7a65b3dc369b04d/utils/redirect-backend.js#L152-L157

Thanks for pointing those out! I missed those when I did the initial commit.


Support informal delimiter literals

Interprets the {, }, and ] delimiters as literals depending on the context.
Notes

Reduce ambiguity in the quantifier_interval pattern by replacing the optional matchers with 4 fixed patterns.
Remove the premature_end_error final state handler from quantifier_interval to permit valid literal sequences.

Closes #63

Thank you for the review. Very helpful.

i've checked some more edge cases and found no issues. maybe we should add one example to spec/parser/quantifiers_spec.rb to document that leading zeros are correctly ignored as in MRI:
include_examples 'quantifier', /a{004}+b/, '{004}+', :possessive, :interval, 4, 4

Good call. I will add it.
I will wrap this up and push out a new release (1.8) this afternoon.

On second thought, I'll consider this a bug fix, and release as 1.7.1.


vsr: complete rollout of the new state sync protocol

The final piece of the puzzle -- complete removal the old messages. Now the replicas would panic if they see any of the old messages, treating them exactly as any other kind of an unknown message.

To be merged after the next release!

One thing this PR doesn't do is that it doesn't flip visit back to false. If I am reading the code correctly, visit affects the previous release, as the current one is always visit=true. So it's the next week we could flip visit back to false (but I am tempted to refactor that logic maybe to remove this shift by one)

Yeah, the state sync docs are in general out of sync, but that's tackled in #2269
Curious though, what is gg? (my gg is https://github.com/matklad/config/blob/master/gg/src/main.rs)

alias gg='git grep --line-number'


Added John Purcell's Java tutorial

@shravan20 Fixed, what about now?

Thank you for contribution, PR accepted.


Add: Channel Europe [BD]

Channel Name
Channel Europe
Alternative Names (optional)
No response
Network (optional)
No response
Owners (optional)
No response
Country
BD
Subdivision (optional)
No response
City (optional)
No response
Broadcast Area
c/BD
Languages
Ben
Categories (optional)
Entertainment
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
No response
Logo
https://www.jagobd.com/wp-content/uploads/2022/12/cheu.png
Notes
No response

Please update your request:

category name should be in lowercase
language code must be in lowercase

https://github.com/iptv-org/database/blob/master/CONTRIBUTING.md#channels


158595244 Final Navigation

IMPORTANT: This PR includes a travis.ci  configuration change which needs to be removed after the branch is accepted.  Because the navigation changes require new portal pages to run.
Please review #519  before this.   That PR keeps existing (non portal pages) navigation.
This PR is based on that, but removes non-portal pages navigation, and fixes cuke tests.

About 10 navigation related cucumber test started failing after reverting to portal-pages master in 5821980.
I am confused because, I think master has all of navigation-z-order-fix commits in it.
Are we sure that Travis is testing against portal-pages master when we don't specify otherwise in .travis.yml?

It looks like we finally went green on all the tests 🎉
I also put in b95abc7  to address the haml comments in the navigation partial.


GallatinOwnerParcel_shp.zip is no longer available for download

ftp://ftp.geoinfo.msl.mt.gov/Data/Spatial/MSDI/Cadastral/Parcels/Gallatin/GallatinOwnerParcel_shp.zip is no longer available for download.
Any alternatives that I can use to follow along with the tutorial?
Cheers!

@xndong1020 sorry about that! Looks like that file has been renamed to ftp://ftp.geoinfo.msl.mt.gov/Data/Spatial/MSDI/Cadastral/Parcels/Gallatin/Gallatin_SHP.zip Can you try with that file?


Support psr/simple-cache 3.0

Hey, I was wondering whether you want to support psr/simple-cache 3.0? It would require dropping support for PHP 7.4 which you might not want to do. I'm happy to submit a PR to drop support for PHP 7.4, and then another to add the return types to your cache implementations and delete stubs/Psr/SimpleCache/CacheInterface.stub and the reference to it in phpstan.neon.dist.

Hi @brayniverse, I noticed that when I added support for psr/simple-cache:^2.0. You're right, supporting v3.0 would mean dropping PHP 7.4 support.
While I plan to do it at some time, that would mean maintaining two separate branches, because the old branch would live at least until the end of PHP 7.4 security support, on 28 nov. 2022.
What is the reason that forces you to have psr/simple-cache:^3.0 support on your side? Are there alternatives?

I only noticed it while trying this package on a demo application and wondered if you wanted help upgrading. I'll close this ticket for now and we can revisit the idea next year.

Thanks for clarification, I honestly can't wait to upgrade the codebase to PHP 8.0 as well 🙂 — if you're still around at that time I wont hesitate to ask for help!


Trim deleted entries after recover cursor.

Motivation
The recovered cursor already has the marked individually deleted messages ranges and the last mark delete entry, for messages redelivery,  messages that were marked for deletion before the recovery are not being replayed.
But for message delivery, broker will read entries after the last mark delete entry, have not handle
the marked individually deleted messages ranges. This PR will trim messages which are contains in the marked individually deleted messages ranges.
Modification
While the read position of the cursor is less than the upper of  LastIndividualDeletedRange, already acked messages are not being dispatched, otherwise not.
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): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: ( no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation

Does this pull request introduce a new feature? (no)

retest this please

@merlimat @rdhabalia PTAL

@merlimat I have update the description, please take a look.

ping @merlimat

@codelipenghui can you rebase the pull request?

@sijie I have rebase the pull request, please take a look.

run cpp tests

Change the Milestone to 2.4.2, because of conflict.

improved fix is #5894


Replace cached self._win with EventLoop.window

Fixes #2936 by not caching EventLoop.window but using it directly. We don't check whether there is a root window, so it just makes sense to use the window directly. That code was old leftovers.
@akshayaurora, @tito please check if that fixes things.

:+1:


test(delete-pr-preview) add test for delete pr preview command

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

v4.2.2
GitHub release

Your semantic-release bot :package::rocket:


Configure LineChart: Max marker points

Google & Highcharts: Configure line charts to hide their markers, after a certain number of data points.
Highcharts: You can also configure what symbol a series should use.

This is to avoid:

Google & Highcharts do this, sometimes, on their own, but I think it could be useful to control that directly.

Hey @buren, thanks for the PR, and sorry this was never responded to. There's now a points option that can be used to turn markers off.


BUILD_FAILED on protobuf:x86-windows

The following packages will be built and installed:
    protobuf[core]:x86-windows
Starting package 1/1: protobuf:x86-windows
Building package protobuf[core]:x86-windows...
-- Using cached C:/vcpkg/downloads/protocolbuffers-protobuf-v3.11.2.tar.gz
-- Using source at C:/vcpkg/buildtrees/protobuf/src/v3.11.2-b4b83ed380
-- Configuring x86-windows
-- Building x86-windows-dbg
-- Building x86-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:136 (message):
    Command failed: C:/vcpkg/downloads/tools/cmake-3.14.0-windows/cmake-3.14.0-win32-x86/bin/cmake.exe --build . --config Release --target install -- -v
    Working Directory: C:/vcpkg/buildtrees/protobuf/x86-windows-rel
    See logs for more information:
      C:\vcpkg\buildtrees\protobuf\install-x86-windows-rel-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_build_cmake.cmake:91 (vcpkg_execute_build_process)
  scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
  ports/protobuf/portfile.cmake:55 (vcpkg_install_cmake)
  scripts/ports.cmake:94 (include)

Error: Building package protobuf:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: protobuf:x86-windows
  Vcpkg version: 2019.09.12-nohash

install-x86-windows-rel-out.log

If this issue is still not resolved, please reopen it.


chore(NODE-4174): Use $$unsetOrMatches for upsert and multi in update command expectations

Description
What is changing?
Is there new documentation needed for these changes?
What is the motivation for this change?

Double check the following

[x] Ran npm run check:lint script
[ ] Self-review completed using the steps outlined here
[x] PR title follows the correct format: <type>(NODE-xxxx)<!>: <description>
[ ] Changes are covered by tests
[ ] New TODOs have a related JIRA ticket

Could we also update the PR description to note what the changes being introduced are? Right now it's just the template. Thanks!


add resource lix setter method

Summary
adding resource lix setter method
Testing Done
./gradlew build
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 67.44%. Comparing base (3c10b71) to head (31f714f).
Report is 2 commits behind head on master.

Files with missing lines
Patch %
Lines

...m/linkedin/metadata/restli/BaseEntityResource.java
0.00%
2 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #414      +/-   ##
============================================
- Coverage     67.80%   67.44%   -0.36%
- Complexity     1514     1518       +4
============================================
  Files           137      137
  Lines          5898     5947      +49
  Branches        636      640       +4
============================================
+ Hits           3999     4011      +12
- Misses         1628     1665      +37
  Partials        271      271

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


Maya: Vray Scene creator fails

Describe the bug
Maya Vray Scene creator fails

Failed to create Subset: "vraysceneMain" Family: "vrayscene" in Asset: "sh010"

Error: Unsupported type: <class 'dict_keys'>

Traceback (most recent call last):
  File "D:\REPO\OpenPype\openpype\tools\creator\window.py", line 432, in _on_create
    data={"variant": variant}
  File "D:\REPO\OpenPype\openpype\pipeline\create\legacy_create.py", line 196, in legacy_create
    instance = plugin.process()
  File "D:\REPO\OpenPype\openpype\hosts\maya\plugins\create\create_vrayscene.py", line 81, in process
    self.instance = super(CreateVRayScene, self).process()
  File "D:\REPO\OpenPype\openpype\hosts\maya\api\plugin.py", line 96, in process
    lib.imprint(instance, self.data)
  File "D:\REPO\OpenPype\openpype\hosts\maya\api\lib.py", line 426, in imprint
    raise TypeError("Unsupported type: %r" % type(value))
TypeError: Unsupported type: <class 'dict_keys'>

Desktop (please complete the following information):

OS: windows
Host: Maya 2022

[cuID:2u0h4ph]

Subsequently Vray scene collector fails as well
Instance:
vraysceneMain
Message:
'NoneType' object has no attribute 'group'
Line:
50
Traceback:
Traceback (most recent call last):
  File "D:\REPO\OpenPype\.venv\lib\site-packages\pyblish\plugin.py", line 522, in __explicit_process
    runner(*args)
  File "D:\REPO\OpenPype\openpype\hosts\maya\plugins\publish\collect_vrayscene.py", line 50, in process
AttributeError: 'NoneType' object has no attribute 'group'


Fix: Remove button isn't disabled when a user is removed by pressing Enter

Details

When the button is disabled, even if you hover over it, the renderProp hover property of the Pressable react native component is false. However, if the button is not disabled, the hover property starts to work fine. In our case, the button is active initially, thus the hover style get applied correctly. When we remove the user by keyboard, the button state changes to disabled but the hover style still applies. This might be due to a bug in the Pressable component.
Fixed Issues

$ https://github.com/Expensify/App/issues/8935
Tests

Go to settings
Open any workspace
Click Manage members
Select any member
Click on the remove button
Press enter/return key on the remove popup and keep the cursor still

The remove button should be disabled right after the member is removed

[x] Verify that no errors appear in the JS console

PR Review Checklist

Contributor (PR Author) Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for Staging and/or Production testing in the QA steps section
[ ] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors (if there’s a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained “why” the code was doing something instead of only explaining “what” the code was doing.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named “index.js”. All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] Any functional components have the displayName property
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose and it is

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn’t already exist
[ ] The style can’t be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.

PR Reviewer Checklist

[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[ ] MacOS / Chrome
[ ] MacOS / Desktop

[ ] I verified there are no console errors (if there’s a console error not related to the PR, report it or open an issue for it to be fixed)
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained “why” the code was doing something instead of only explaining “what” the code was doing.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named “index.js”. All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] Any functional components have the displayName property
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose and it is broken down into smaller components in order to separate concerns and functions

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn’t already exist
[ ] The style can’t be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.

QA Steps

Go to settings
Open any workspace
Click Manage members
Select any member
Click on the remove button
Press enter/return key on the remove popup and keep the cursor still

The remove button should be disabled right after the member is removed

[x] Verify that no errors appear in the JS console

Screenshots

Web

https://user-images.githubusercontent.com/30054992/171585934-117c8445-6ead-4b10-96c5-d04518dded4f.mov
Desktop

https://user-images.githubusercontent.com/30054992/172489493-23c68c6c-a215-477d-a5c6-b7653e453537.mov
iOS
https://user-images.githubusercontent.com/30054992/173203963-2b5ebbc5-4ec3-4020-beca-6c3995626af5.mp4
Android
https://user-images.githubusercontent.com/30054992/173204049-1f9980eb-2395-4bd5-8b6c-2bed79c34e84.mov
Mobile Web
https://user-images.githubusercontent.com/30054992/173204145-5df25692-4ee4-44b9-933f-886d2166bda7.mp4

I will merge once we have videos for all the platforms

@parasharrajat @pecanoro Updated.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @pecanoro in version: 1.1.78-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by @sketchydroide in version: 1.1.78-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Don't crash if comfy directories exist

Currently the comfy-install-linux.sh script and fatal errors if the directory exists. This is likely to happen when doing installs and reinstalls:
mkdir: dlbackend: File exists
fatal: destination path 'ComfyUI' already exists and is not an empty directory.

The new code uses mkdir -p which will exit 0 even if the dlbackend directory already exists. We could optionally wipe it.. but why not save some bandwidth on reinstalls and avoid re-downloading models?
It also does a simple directory check to see if the ComfyUI directory exists for the repo. If it does, it deletes it to be safe because using git pull instead can bring a whole host of merging conflicts, divergent branches, and other git nightmares.
:warning: It's best to start fresh, but in the future some folks might want to customize their Comfy repo codebase and prefer not having it wiped when reinstalling, so this might warrant caution in review.

Closed because I accidentally made this PR from my fork's master branch. I can re-open if you think it's useful @mcmonkey4eva.

... Really don't want rm -rf $variable in a generic script.
That aside, handling re-installs with a pre-existing folder path sounds reasonable. Probably better to handle the cleanup in C# rather than bash (naturally cross-platform, and avoids sus bash commands lol)

Yeah except you'll likely have to interact with git state which I wouldn't wish on my favorite C# nerd. 😄
I think it's fine to avoid deleting anything actually, and defer to git to see if there's a manageable repo state. The trick is going to be different versions of git handling a git pull slightly differently since there have been a bunch of improvements lately.
If folks are using their own ComfyUI this is not an issue of course, but it would really suck to wipe out the repo if someone's done some customizations.
Maybe you could:

check if it exists

if not cool, git clone
if it does:

easy git pull (fast-forward, no merge) is possible:

prompt: y/n

can't easily git pull: error recommending manual resolution

I might tackle that if that sounds interesting to you or if you get enough Issues mentioning re-install in the future.


Consider hashing  STRING columns as UTF-8 instead of UTF-16 in HLL

Currently the HLL implementation hashes STRING columns by converting the value the java.lang.string, and then hash the underlying UTF-16 char array:
https://github.com/apache/incubator-datasketches-hive/blob/master/src/main/java/org/apache/datasketches/hive/hll/SketchState.java#L66
This is looks like an optimization at first, as the UTF-16->UTF-8 conversion can be skipped, but actually Hive stores STRINGs as hadoop.io.text as far as I know, which holds the string as UTF-8 encoded byte arrays:
https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/Text.java#L214
This came up during Apache's Impala's HLL implementation, which should be compatible with Apache Hive's existing DataSketches wrapper. As Impala stores strings as byte arrays, converting the values to UTF-16 adds overhead and can also cause problems for byte arrays that cannot be converted to UTF-16.

Changing this will be fraught with problems as other Hive users may have a history of sketches created with Strings encoded as char[].  I'm not sure I see an easy solution other than documenting it & putting warnings everywhere.  Any ideas?

Yes, I would think that we should provide a new way leaving the current way alone and  explain tradeoffs in the documentation.

I have created a [DISCUSS] thread on our<EMAIL_ADDRESS>list if you wish to add comments to that.

Perhaps, this is moot.  Both Pig/HLL and Hive/HLL allow updating the sketch as a raw byte[].  So the user could do their own encoding and present the sketches with byte[].
I checked Theta and Tuple for both Pig and Hive and the same options exist.

This should be documented where users can find it. :)

This issue can now be closed.


haskellPackages.Agda fails to build due to lifted version restrictions

Log: http://hydra.nixos.org/build/32250896/log/raw
I believe the problem is that Agda <IP_ADDRESS> requires unordered-containers < 0.2.6: https://github.com/fpco/stackage/issues/1222#issuecomment-184022870

What's a workaround for the time being?


Fix: Wrong php7 fpm service name

Hello @reyhansofian, thanks for your contribution, i hope my code will help you automate the installation. Cheers!


Cheese Charger - C140478, low stock

Hi, is there another fuse that could be used in place of C140478?  It's currently low stock at JLCPCB.  Can C182445 be used instead?

Yes, you can use C182445 or C14165 instead. And you can also use 0Ohm resister C17888 instead of using fuse 'cause most of charger don't output over 3A in 5V condition.


Support column groups for final merge.

What type of PR is this：

[ ] bug
[x] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #7332
Problem Summary(Required) ：

It will take up a lot of memory when merging temporary segment files in final merge procedure, which may cause OOM.
Support column groups when merging segment files.
There does exists some repetitive code, but other unrelated code will be influenced if refactor it now, so let them go and refactor it in next individual PR.

Better to test the memory optimization effect and performance optimization effect

run starrocks_be_unittest


Added render_order to material

This PR is part of the effort to avoid z-fighting between coplanar meshes.
Related with https://github.com/ignitionrobotics/ign-rendering/pull/188
Signed-off-by: ahcorde<EMAIL_ADDRESS>

Codecov Report

Merging #446 (8c5ab76) into sdf10 (7dbf121) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##            sdf10     #446      +/-   ##
==========================================
+ Coverage   87.54%   87.56%   +0.01%
==========================================
  Files          61       61
  Lines        9357     9365       +8
==========================================
+ Hits         8192     8200       +8
  Misses       1165     1165

Impacted Files
Coverage Δ

src/Material.cc
98.17% <100.00%> (+0.09%)
:arrow_up:

Continue to review full report at Codecov.

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


[Serialization] If we fail to deserialize a type, dump it.

...rather than just printing it, which isn't giving us enough info. When this is all over we can go back to the simple assert.
In pursuit of rdar://problem/30382791.

@swift-ci Please smoke test and merge


pip install fails with error: externally-managed-environment

Using Ubuntu Nobel to build the documentation fails with the following error during installation of required packages.
root@tomoyafujita:~/ros2_ws/work/ros2_documentation# pip install -r requirements.txt -c constraints.txt
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.12/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

This is due to Ubuntu Nobel adopting PEP 668 – Marking Python base environments as “externally managed”
The followings are suggested fixes,

https://github.com/ros2/ros2_documentation/blob/rolling/README.md, add virtualenv build example to avoid --break-system-packages option to override the system packages.
https://docs.ros.org/en/rolling/The-ROS2-Project/Contributing/Contributing-To-ROS-2-Documentation.html

update the procedure using virtualenv as well.
add how to use devcontainer to build the documentation. (https://github.com/ros2/ros2_documentation/blob/rolling/.devcontainer/devcontainer.json)

So the thing is, the README here already says that you need a virtualenv:
To build this you need to install

* make
* graphviz
* python virtualenv

In the virtualenv

``
pip install -r requirements.txt -c constraints.txt
``

I guess we can reword it to make it clearer, but I'm not sure what else to do here.

Could we add the commands needed to create the venv? Before running pip install.

@clalancette you can assign this to me.


Link to new Azure tutorial from Pipelines cloud-tutorials page

PR https://github.com/kubeflow/website/pull/956 has added a new Azure tutorial:
https://www.kubeflow.org/docs/azure/azureendtoend/
We should add a link to the new tutorial on this page:
https://www.kubeflow.org/docs/pipelines/tutorials/cloud-tutorials/
And at the same time remove the wording: "We currently have only a GCP tutorial for Kubeflow Pipelines. A tutorial for Microsoft Azure is on its way (see PR #956)."

/good-first-issue

/close
Thanks @rem20806!


TW system doesn't let me note past classification as incertae sedis

Happy New Year for all:
I want to report what I suspect to be an incorrect error message:
Genus Glysterus Roewer, 1931 has been assigned to the following parent taxa:
(1) Glysterus was originally in Hernandariinae.
(2) Transferred to Gonyleptinae by Goodnight & Goodnight (1947a: 13).
(3) Put in Gonyleptidae incertae sedis by Kury (2003a: 104).
(4) Transferred to the Ampycinae by Kury & Alonso-Zarazaga (2011: 52).
So, we see that in 3 it was not included in any subfamily, but in 4 it is already in Ampycinae.
That means, during a window of seven years Glysterus was a Gonyleptidae incertae sedis.
But TW doesn't let me note this in the CLASSIFICATION module, because it doesn't understand that G inc. sedis is a PAST CLASSIFICATION.
It keeps saying the the tag incertae sedis is incompatible with the allocation to Ampycinae.

All I can do is this:

Yes, you should you Classified as relationship.
Incertae sedis is reserved for current classification only. It is a temporaty status, befor better position for the taxon is recognized. In fact, you cannot even change the parent of the taxon before you remove the Incertae sedis relationship. Using Incertae sedis, will let the sistem negate some of the soft validation messages, and could also be used as a filter. For historical placements we reserved "Classified as" relationship. Which is designed for historical placements of the taxon. If you want to be more specific, you have to use comments, for example OTU Contents.

Yes, you should you Classified as relationship.
Incertae sedis is reserved for current classification only. It is a temporaty status, befor better position for the taxon is recognized. In fact, you cannot even change the parent of the taxon before you remove the Incertae sedis relationship. Using Incertae sedis, will let the sistem negate some of the soft validation messages, and could also be used as a filter. For historical placements we reserved "Classified as" relationship. Which is designed for historical placements of the taxon. If you want to be more specific, you have to use comments, for example OTU Contents.

Thanks, Dmitry. So I basically did what was correct in this case...

Thanks, Dmitry. So I basically did what was correct in this case...


Undefined name '$pb' used as an annotation

After updating to the latest version protobuf-2.0.1, protoc_plugin-20.0.1  my generated code came with an error when generating with the "grpc:." tag.
When executing this line:
protoc stripe_events.proto --dart_out=grpc:../../../../core/lib/generated &
My file "stripe_events.pbgrpc.dart" comes with the following error:

This started to happen after I updated to the latest version of the package.

I am also having this issue, I don't know if they are related:
https://github.com/google/protobuf.dart/issues/786


Missing Information about what is considered as a base license

In a support case I was informed that "Power Apps per User" and "Power Automate per User" licenses are considered as the same base license and therefore their requests limits are not cumulated. I think this is important to know. Please put some information on this page which clarifies this. This would definitely help to reduce support requests.

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

ID: 02f2c989-54cf-d81a-aafb-2f4cd6fef108
Version Independent ID: 69811228-6a61-a078-86b3-ed11a6d9c84d
Content: Requests limits and allocations - Power Platform
Content Source: power-platform/admin/api-request-limits-allocations.md
Service: power-platform
Sub-service: admin
GitHub Login: @MicroSri
Microsoft Alias: sriknair

Thanks for your comment, @WinOnMarco. This issue has been assigned to the doc author for review.


Russian abbreviation weekdays

Added russian abbreviation weekdays:
Monday: Пнд
Tuesday: Втр
Wednesday: Срд
Thursday: Чтв
Friday: Птн
Saturday: Сбт
Sunday: Вск
Fixes #436

@christianfm10 Do you think you will have time to address @lopuhin’s feedback?
Otherwise, @eLRuLL, @lopuhin, @asadurski, shall we merge as is?

totally up to @lopuhin and @asadurski at this point I think

In terms of Russian language, changes are good. From the dataparser side, I have the following questions:

does capitalization matter? If yes then I can check in more detail which capitalization is better
yaml and py files are different, is this fine?

yaml and py files are different, is this fine?

It is not fine. We need to add a check for this to the CI.

Hi @lopuhin
There is a PR adding tests to avoid merging different yaml - py files: https://github.com/scrapinghub/dateparser/pull/663.
On the other side, as answered in the inline comment, capitalization doesn't matter.


Add Volcano Plot function

Volcano plots are popular in a lot of -omics analyses. Generally the idea is to plot Log2(fold-change) against the p-value for a two group comparison, and often certain cutoffs (e.g. p <= 0.05) are used to highlight the significantly different features. An example:

The plot itself should be easy enough to generate, it would work like the S-plot function which pulls two sets of statistics calculated using the same two groups: Log2(fold-change) and t-test (or equivalent nonparametric test) p-value and plot them against each other with formatting and whatnot. Two group Log2(fold-change) is already implemented as a stats function, but there is not yet a function for getting the p-value for comparison of two groups. See issue #66  regarding that stats function which needs to be implemented first...

Like the p-value stats function (#66) the plotting function should take an argument that specifies the statistical test to use for computing p-value so that the appropriate data can be fetched from Dataset.stats
The signature of the plotting function should be as follows:
def volcano_2group(dset, groups, stats_test, save_dir, normed=False):

where dset is a reference to the Dataset object
groups is a list of the (two) groups to compare
stats_test specifies the statistical test used to compute p-values
save_dir is the directory to save the image into
and normed is the kwarg indicating whether normalized intensities were used in the comparison


Unable to run claims with kevm prove

I have a lemmas.k file with a LEMMAS module and a LEMMAS-SPEC module with a claim claim-1. I'm trying to run this claim with the commands
kevm kompile-spec lemmas.k --target haskell --main-module LEMMAS --syntax-module LEMMAS -o kompiled
kevm prove lemmas.k --claim LEMMAS-SPEC.claim-1 --definition kompiled

but I get the error ValueError: Claim labels not found: ['LEMMAS.LEMMAS-SPEC.claim-1']. In other words, it automatically prefixes the claim label with the main module LEMMAS, which is incorrect because the claim is in the LEMMAS-SPEC module. It's not even possible for the claim to be in the main module because in this case kevm kompile-spec fails with the error message Claims are not allowed in the definition.
kevm prove used to have a --spec-module option, but it no longer seems to accept it, so I don't know how else to specify the spec module.

I would classify this as high priority, since we do need it for ongiong engagements and standard testing.

In pyk version 0.1.696 we have an update_args static method for KDefinitionOptions here, which has --spec-module. We also have update_args for all subclasses of Options.
In pyk version 0.1.697, KDefinitionOptions disappears entirely.
In pyk version 0.1.712, KDefinitionOptions makes a comeback, but without the update_args static method (here). No subclass of Options has update_args anymore.


Add index attribute to Question

This PR poses a change which introduces the index attribute explicitly to the Question class.
Previously, we relied on array order to implicitly define question order. Adding an explicit reference to order in the Question class allows us to further simplify the logic resolve the question to be displayed and decouples the data structure from the underlying persistence layer.

I think we need to be clearer about the problem this is solving. What problem does the reliance of array order currently cause?
I’m also struggling to see this as a reduction in complexity, since this PR is actually a net addition to the codebase. I reckon this feature could be helpful as a way to make our configuration more flexible, so perhaps it’s worth focusing on that instead?

I'm coming from a view of tidying up the logic to make it easier for developers to understand how we resolve the next question. It also has the added bonus we don't have a concept that is tied to how we store the data.
I also would be wary about conflating "number of lines" with complexity. The variables relative_next_question_index and question_index add extra concepts that developer has to reason with.

Thanks for explaining your thoughts a bit more. I like that we're making an effort to tidy up our code, and you're right that lines != complexity - that was a low shot! I think I haven't been clear about the concerns I have with this change, so I'll try to outline them again:

For me, I don't find the current code difficult to follow. It's not clear to me who is struggling with the current code, and that this particular change will make things better for them
This will make it harder to add or reorder the questions in the YAML file, since a developer will now have to manually alter all of the indices to ensure they are still a sequence
This could also make understanding the order of the questions harder, as it's no longer guaranteed to be the top-to-bottom ordering in the YAML file, which I currently find helpful

I see your point that there are some non-trivial variables in the code we're talking about, which isn't ideal and perhaps we can think of better names for them. But removing them doesn't reduce the conceptual load, since we're also introducing a new concept (index). In a way, we've just moved the current concept somewhere else - sometimes that's a more natural fit and does indeed make the codebase more readable, but I don't think that's the case here.
As a way to proceed, I'd suggest getting someone who's having trouble understanding the current code to review this PR. We should also have a think about how much of a pain point maintaining the manual numbering is going to be, and whether we need to do anything to mitigate this as part of making this change.

@theseanything this one's been around for a while. Do you mind if we close?


Support disabling tag helper processing at the element level

There should be the ability to disable a specific element instance (in a CSHTML file) from being processed as a Tag Helper. e.g. consider that the input tag is mapped to the InputTagHelper class but I want a specific input element instance to be client-side only:
@addtaghelper "InputTagHelper"
@addtaghelper "DivTagHelper"

<input />  @* This will be processed as a tag helper *@

<!input /> @* This will *not* be processed as a tag helper and the '!' will be removed from the output HTML *@

<!div>     @* This will *not* be processed as a tag helper and the '!' will be removed from the output HTML *@
    Hello there
</!div>

If a prefix is also declared for the page with the same value, an exception should be thrown at parse time to indicate that the combination is invalid, e.g.:
@addtaghelper "InputTagHelper", prefix: "!"

@* Explodes at parse time *@

Note: We've designed out the "only remove the ! if an element is a TagHelper.

94230a5a145d11b3772cd54a1ae17b036ac326ff
cf3d0492721cd61b262babfa3cc9b9efbf9c21aa


43 Completion Block Rework

What
This is the culmination of work towards reworking completionHandlers and response processing.
How
See PRs linked from issue #43
Reviewers
reviewer @ricellis
Issues
Resolves #43

+1


Include lldb_sys as a re-export

Given the tight coupling between this library and the lldb_sys crate, perhaps it would be a good idea to add a public re-export of the lldb_sys crate?
As it stands, I grabbed the latest version of both 0.0.10 and 0.0.29, and they don't work together so I had to drop to 0.0.27, but if we export lldb_sys as sys we can avoid people having to pull the lldb_sys crate manually.

that seems like it might be worthwhile. I have changes locally that I was still working on for lldb to use current lldb-sys, but I didn't think anyone was using this at this point.
I'll publish it shortly, I think.
What do you use the sys crate for in terms of things that don't yet have bindings?

I've published lldb version 0.0.11 which works with the current lldb-sys. It also re-exports lldb-sys as sys.
I'd love to hear about what you're doing with it all though.

@waywardmonkeys that's awesome, thanks!
My use case is running *.dsym files through for Apple crash reporting, the API I specifically use is:
SBDebuggerCreateTargetWithFileAndArch
Which is the equivalent of: lldb -arch <arch> <symbol>.
It might be there's a better way to do this, this code is from a few years ago!

Fixed in 0.0.11.


Network Policy task example does not work because busybox pod is still alive with the old access rights.

This is a Bug Report

Problem:
Network Policy task example does not work because pod containing Busybox remains alive.
dropaflame@1dropaflame:~/CKAD$ kubectl run busybox --rm -ti --labels="access=true" --image=busybox:1.28 -- /bin/sh

Error from server (AlreadyExists): pods "busybox" already exists

dropaflame@1dropaflame:~/CKAD$ wget --spider --timeout=1 nginx

Spider mode enabled. Check if remote file exists.

--2023-04-03 09:29:57--  http://nginx/

Resolving nginx (nginx)... failed: Temporary failure in name resolution.

wget: unable to resolve host address ‘nginx’

Proposed Solution:
After each of the sub-sections are done, delete the BusyBox pod.
So that subsequent sub-sections like
https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy/#test-access-to-the-service-when-access-label-is-not-defined
and
https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy/#define-access-label-and-test-again
will work.
dropaflame@1dropaflame:~/CKAD$ k delete pod busybox

pod "busybox" deleted

dropaflame@1dropaflame:~/CKAD$ kubectl run busybox --rm -ti --labels="access=true" --image=busybox:1.28 -- /bin/sh

If you don't see a command prompt, try pressing enter.

/ # wget --spider --timeout=1 nginx

Connecting to nginx (<IP_ADDRESS>:80)

Page to Update:
https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy/

/sig network

/priority awaiting-more-evidence

It may have been a glitch. I have not seen the issue again.


fix: strings properly mapped to YText

This fixes issue #49.

:tada: This PR is included in version 1.3.1-rc.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


create_passwords script fails (no vault?), perhaps due to missing file

Version
I did a git clone at approx 19:20 BST today 28 Sept 2023.
$ git clone --recursive https://github.com/Azure/az-hop.git
Cloning into 'az-hop'...
remote: Enumerating objects: 23668, done.
remote: Counting objects: 100% (4839/4839), done.
remote: Compressing objects: 100% (678/678), done.
remote: Total 23668 (delta 4183), reused 4619 (delta 4084), pack-reused 18829
Receiving objects: 100% (23668/23668), 10.64 MiB | 5.05 MiB/s, done.
Resolving deltas: 100% (15982/15982), done.
Submodule 'playbooks/roles/ood-ansible' (https://github.com/OSC/ood-ansible.git) registered for path 'playbooks/roles/ood-ansible'
Cloning into '/home/mkb/az-hop/playbooks/roles/ood-ansible'...
remote: Enumerating objects: 1561, done.
remote: Counting objects: 100% (488/488), done.
remote: Compressing objects: 100% (219/219), done.
remote: Total 1561 (delta 372), reused 297 (delta 261), pack-reused 1073
Receiving objects: 100% (1561/1561), 290.48 KiB | 1.71 MiB/s, done.
Resolving deltas: 100% (909/909), done.
Submodule path 'playbooks/roles/ood-ansible': checked out '12995d36f4fde2fb5839e50664521e4bd39bd0c0'
In what area(s)?

/area administration
/area ansible
/area configuration
/area documentation

Expected Behavior

The tutorial at https://azure.github.io/az-hop/tutorials/quick_install.html#quick-installation-guide in Task 6 says to run ./create_passwords.sh but actually fails:
Actual Behavior
$ ./create_passwords.sh
Error: open playbooks/group_vars/all.yml: no such file or directory
Keyvault retrieved from playbooks/group_vars/all.yml is empty
There is no group_vars dir within playbooks. If I create empty dir or even empty group_vars/all.yml the command still fails/gives errors

You need to build your environment first before applying this script. the missing files will be created by the build command.

As per tutorial, the step before ./create_passwords.sh was
./build.sh -a plan -l bicep

great. Have you run ./build.sh -a apply -l bicep ? this command is the one creating these resources. The plan one is to check configuration is correct and will list what will be created.

My mistake, I had missed the "apply" command (from step1 of Task6). However, when I do that know I get this long error:
mkb@ASN-ACA7353:~/az-hop$ ./build.sh -a apply -l bicep
Activating conda environment
ok -- validation done
config.yml passes validation

logged in Azure with User<EMAIL_ADDRESS>

Deploying using Bicep
/home/mkb/az-hop/bicep/mariadb.bicep(36,30) : Warning use-resource-symbol-reference: Use a resource reference instead of invoking function "reference". This simplifies the syntax and allows Bicep to better understand your deployment dependency graph. [https://aka.ms/bicep/linter/use-resource-symbol-reference]

{"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/providers/Microsoft.Resources/deployments/azhop_2023.0929.085400","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"ResourceDeploymentFailure","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhop","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"DeploymentFailed","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhop","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"ResourceDeploymentFailure","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhopVmscheduler","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"DeploymentFailed","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhopVmscheduler","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"NotFound","message":"Subscription not found."}]}]},{"code":"ResourceDeploymentFailure","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhopVmccportal","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"DeploymentFailed","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhopVmccportal","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"NotFound","message":"Subscription not found."}]}]},{"code":"ResourceDeploymentFailure","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhopVmad","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"DeploymentFailed","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhopVmad","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"NotFound","message":"Subscription not found."}]}]},{"code":"ResourceDeploymentFailure","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhopVmgrafana","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"DeploymentFailed","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhopVmgrafana","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"NotFound","message":"Subscription not found."}]}]},{"code":"ResourceDeploymentFailure","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhopVmjumpbox","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"DeploymentFailed","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhopVmjumpbox","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"NotFound","message":"Subscription not found."}]}]}]}]}]}}

Please confirm that your user account used to logged in on Azure is using the right subscription as listed on Task4.
Also check your user's permission as listed here

Hi, as you can tell, I'm fairly new to Azure sys admin logistics. I'm presuming something timed out (re az login) so have re-done Task 4 steps 1-3, then jumped back to Task 6, step 1 'apply' and now get a quota error (NB I'm using the free $200 azure trial):
mkb@ASN-ACA7353:~/az-hop$ ./build.sh -a apply -l bicep
Activating conda environment
ok -- validation done
config.yml passes validation

logged in Azure with User<EMAIL_ADDRESS>

Deploying using Bicep
/home/mkb/az-hop/bicep/mariadb.bicep(36,30) : Warning use-resource-symbol-reference: Use a resource reference instead of invoking function "reference". This simplifies the syntax and allows Bicep to better understand your deployment dependency graph. [https://aka.ms/bicep/linter/use-resource-symbol-reference]

{"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/providers/Microsoft.Resources/deployments/azhop_2023.0929.111500","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"ResourceDeploymentFailure","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhop","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"DeploymentFailed","target":"/subscriptions/998dc91b-1656-4989-b13e-859e66197475/resourceGroups/azhop-resourcegroup-mkb/providers/Microsoft.Resources/deployments/azhop","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"InvalidTemplateDeployment","message":"The template deployment 'azhopVmjumpbox' is not valid according to the validation procedure. The tracking id is '520cbb00-f3a6-4beb-b463-d18738099b54'. See inner errors for details.","details":[{"code":"QuotaExceeded","message":"Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: uksouth, Current Limit: 4, Current Usage: 4, Additional Required: 2, (Minimum) New Limit Required: 6. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/{"subscriptionId":"998dc91b-1656-4989-b13e-859e66197475","command":"openQuotaApprovalBlade","quotas":[{"location":"uksouth","providerId":"Microsoft.Compute","resourceName":"cores","quotaRequest":{"properties":{"limit":6,"unit":"Count","name":{"value":"cores"}}}}]} by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/regional-quota-requests"}]},{"code":"InvalidTemplateDeployment","message":"The template deployment 'azhopVmscheduler' is not valid according to the validation procedure. The tracking id is '30f3f900-3b46-4250-bcca-b7b82ff75b2a'. See inner errors for details.","details":[{"code":"QuotaExceeded","message":"Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: uksouth, Current Limit: 4, Current Usage: 4, Additional Required: 2, (Minimum) New Limit Required: 6. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/{"subscriptionId":"998dc91b-1656-4989-b13e-859e66197475","command":"openQuotaApprovalBlade","quotas":[{"location":"uksouth","providerId":"Microsoft.Compute","resourceName":"cores","quotaRequest":{"properties":{"limit":6,"unit":"Count","name":{"value":"cores"}}}}]} by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/regional-quota-requests"}]},{"code":"InvalidTemplateDeployment","message":"The template deployment 'azhopVmad' is not valid according to the validation procedure. The tracking id is 'e0aa3160-9d97-485d-8524-42c7ad13d3a1'. See inner errors for details.","details":[{"code":"QuotaExceeded","message":"Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: uksouth, Current Limit: 4, Current Usage: 4, Additional Required: 2, (Minimum) New Limit Required: 6. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/{"subscriptionId":"998dc91b-1656-4989-b13e-859e66197475","command":"openQuotaApprovalBlade","quotas":[{"location":"uksouth","providerId":"Microsoft.Compute","resourceName":"cores","quotaRequest":{"properties":{"limit":6,"unit":"Count","name":{"value":"cores"}}}}]} by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/regional-quota-requests"}]},{"code":"InvalidTemplateDeployment","message":"The template deployment 'azhopVmgrafana' is not valid according to the validation procedure. The tracking id is 'bbb6f1dd-98fe-4ad1-b542-2a894a34df3b'. See inner errors for details.","details":[{"code":"QuotaExceeded","message":"Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: uksouth, Current Limit: 4, Current Usage: 4, Additional Required: 2, (Minimum) New Limit Required: 6. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/{"subscriptionId":"998dc91b-1656-4989-b13e-859e66197475","command":"openQuotaApprovalBlade","quotas":[{"location":"uksouth","providerId":"Microsoft.Compute","resourceName":"cores","quotaRequest":{"properties":{"limit":6,"unit":"Count","name":{"value":"cores"}}}}]} by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/regional-quota-requests"}]},{"code":"InvalidTemplateDeployment","message":"The template deployment 'azhopVmccportal' is not valid according to the validation procedure. The tracking id is 'b805aefe-7869-4ca8-842a-8658df892e17'. See inner errors for details.","details":[{"code":"QuotaExceeded","message":"Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: uksouth, Current Limit: 4, Current Usage: 4, Additional Required: 2, (Minimum) New Limit Required: 6. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/{"subscriptionId":"998dc91b-1656-4989-b13e-859e66197475","command":"openQuotaApprovalBlade","quotas":[{"location":"uksouth","providerId":"Microsoft.Compute","resourceName":"cores","quotaRequest":{"properties":{"limit":6,"unit":"Count","name":{"value":"cores"}}}}]} by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/regional-quota-requests"}]}]}]}]}}
mkb@ASN-ACA7353:~/az-hop$

hi, with the free Azure trial I do not have option to adjust quotas.
i am currently looking to eval Azhop as a method to set up virtual HPC cluster. I don't need to use significant resources but rather to understand the methods/options available.
Which makes me think I want to amend config to have fewer, smaller VMs (= virtual compute nodes?)
Can you, please, advise on an appropriate config.yml?
Yours, M

let me build one simplified and push it in the repo. but at least you would need 3 VMs dual cores each.

Please confirm that your user account used to logged in on Azure is using the right subscription as listed on Task4. Also check your user's permission as listed here

On this, I am using AZ free (which presume isn't a problem in and of itself?)

let me build one simplified and push it in the repo. but at least you would need 3 VMs dual cores each.

that would be most useful, please let me know when it's available. thanks in advance!


I get error when I use hover

Description
This is in my init.lua.
local function map(mode, lhs, rhs, opts)
  local options = { noremap = true, silent = true }
  if opts then
    options = vim.tbl_extend("force", options, opts)
  end
  vim.api.nvim_set_keymap(mode, lhs, rhs, options)
end
require("lspsaga").init_lsp_saga({
  server_filetype_map = { metals = { "sbt", "scala" } },
  code_action_prompt = { virtual_text = false },
})
map("n", "K", [[<cmd>lua require"lspsaga.hover".render_hover_doc()<CR>]])

Expected Behavior
When I press K in normal mode I'd expect to see a hover pop-up window.
Actual Behavior
I get this error message:
Error executing vim.schedule lua callback: ...te/pack/packer/start/lspsaga.nvim/lua/lspsaga/window.lua:290: attempt to call field '_trim' (a nil value)

Details

Environment

nvim --version output:

NVIM v0.5.0-dev+9f5c8226b
Build type: Release
LuaJIT 2.1.0-beta3
Compilation: clang -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNDEBUG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/tmp/neovim-20210323-89866-nmyed9/build/config -I/tmp/neovim-20210323-89866-nmyed9/src -I/usr/local/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include -I/usr/local/opt/gettext/include -I/tmp/neovim-20210323-89866-nmyed9/build/src/nvim/auto -I/tmp/neovim-20210323-89866-nmyed9/build/include
Compiled by jesse.atkinson@C02ZH2XRLVDR
Features: +acl +iconv +tui
See ":help feature-compile"
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/usr/local/Cellar/neovim/HEAD-9f5c822_2/share/nvim"
Run :checkhealth for more info

Operating system:

macOS 11.2.3

lspsaga commit: https://github.com/glepnir/lspsaga.nvim/commit/b77a08be564ccba4bd8c68cca89aa87e5520b3c3

9f5c822 is 21 days old. Update to the latest nightly.

9f5c822 is 21 days old. Update to the latest nightly.

Apparently I needed to update with --fetch-HEAD flag.

@jsatk
I have the same issue. What did you mean by Apparently I needed to update with --fetch-HEAD flag. ?

@jsatk
I have the same issue. What did you mean by Apparently I needed to update with --fetch-HEAD flag. ?

brew update neovim will pull the latest. But this needs 0.5. The latest nightly.


ScrollTo only working on initial load

If i set the data and options inside ngOnInit, everything works fine.
If i call a webservice and populate the data in a subscribe, the data updates the chart but the scrollto  has no effect.
I have explicitly set the data in the subscribe to make sure its not a data issue.
ngOnInit() {

this.projectsObservable = this.projectService.getProjectPlans(0);
this.projectsObservable.subscribe(projects => {
this.data = [{example data goes here}]
	this.editorOptions = {
		vFormat: 'month',
		vScrollTo: '2019-01-01',
	}

}
Im guessing the scroll has already run before teh data has loaded.
Is there anyway to force the scroll to run again after the data has loaded?

try to call  this.editor.setOptions(this.editorOptions); after the data and options
is this feature working on vanilla js gannt?
https://github.com/jsGanttImproved/jsgantt-improved

Ok, thank you. Will try it as soon as I get back to the office. I believe it's vanilla jsganttimproved

Thank you very much. It works perfectly :-)


PLAT-10410: Add tag parameter for DF2 Agent's API

This is used to support running multiple instances of a bot.
This is added manually now so we can start using it before a release of the agent/specs.

Don't we need to add this change also in the agent-api-public-deprecated.yaml file?

Don't we need to add this change also in the agent-api-public-deprecated.yaml file?

I guess they would be properly overwritten when we release the specs but I updated this file too to keep them in sync