"Writing a Custom Local Authenticator" Document needs to be improved

Is your suggestion related to a missing or misleading document? Please describe.
This[1] document can be improved in several ways.
Describe the improvement
1. Flow is not described completely.
Even though the first diagram shows an overview of what is happening here, information that is mandatory to implement a custom federated authenticator is missing IMO. As an example, how to redirect back to IS side is missing. ( Not even in the sample authenticator code in GitHub). Nothing is mentioned about the /commonauth call, How to pass data between the custom UI and custom authenticator JAR, etc.
2. Need to add sample implementation
The expandable view just shows the plain interface with its methods. Instead of this, I think it is better to show a sample implementation similar to how we have shown sample implementation in Writing a Custom Local Authenticator[2] doc. Maybe we can reuse the Custom Federated Authenticator code[3] in the sample-is repo.
3. Method Descriptions
We have explained what needs to be implemented in each method defined from the interface. This is good. But If we could explain this with the flow, IMO that is better. As an example, we can explain how we should first implement the initiateAuthenticationRequest method with the required redirection at the end and how we should include additional required parameters as query params, etc, how to pass additional params in the /commonauth call, how to implement canHandle method to uniquely identify the authentication request, how then use the /commonauth parameters inside processAuthenticationResponse and how to set subject identifier, user claims in that method, etc. If additional methods are there, we could describe them in a table as we have already done here[2].
[1] - https://is.docs.wso2.com/en/latest/develop/writing-a-custom-federated-authenticator/
[2] - https://is.docs.wso2.com/en/latest/develop/writing-a-custom-local-authenticator/
[3] - https://github.com/wso2/samples-is/blob/master/authenticators/components/org.wso2.carbon.identity.sample.federated.authenticator/src/main/java/org/wso2/carbon/identity/custom/federated/authenticator/CustomFederatedAuthenticator.java#L209

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


chore: Release Verax v4 on Linea Goerli

What does this PR do?
Releases Verax v4 on Linea Goerli
Type of change

[X] Chore
[ ] Bug fix
[ ] New feature
[ ] Documentation update

Check list

[ ] Unit tests for any smart contract change
[ ] Contracts and functions are documented

Codecov Report

Merging #302 (717f9c8) into dev (ec646e4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #302   +/-   ##
=======================================
  Coverage   93.40%   93.40%
=======================================
  Files          13       13
  Lines         197      197
  Branches       46       46
=======================================
  Hits          184      184
  Misses          8        8
  Partials        5        5

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


NFLOG support

Hello
I'm searching for a nice library to use for reading network packets coming from NFLOG and came about this crate. How hard would it be to add support for that protocol?
I'm trying to read the libnl code. From a high level, I have the impression the protocol should be quite simple ‒ sending two control messages, then subscribing into a multicast group and then the packets should start appearing. However, I'm having trouble finding any documentation how the structure of such messages would look like and how it translates into neli code. If you'd give me few hints how you usually go about finding such information, I might try submitting the new message types as a PR.
Thank you

Hi @vorner, in its current state, neli technically does support nflog at the socket level. If you do find out how nflog works, you could create your own structs that implement the Nl trait and make that the type of the Nlmsghdr payload (the P type parameter). If you do end up figuring out the structure of the protocol and want to have me support it in neli, I'd be happy to work it into the library upstream. I unfortunately don't know how the nflog protocol is structured, so I'm unable to give you any advice on how to structure it beyond general advice. /usr/include/linux/netfilter/nfnetlink_log.h seems to include the structures you want, but I'm uncertain where this protocol is used (my guess is some sort of logging for netfilter, but I've never used this protocol personally), so I don't think I would even be able to code against the messages the kernel generates like I did with some aspects of generic netlink. I hope this helps somewhat. If you get to the point where you have the necessary structs and they implement the Nl trait, I could certainly give you more guidance.

Thank you for the hint with nfnetlink_log.h. I guess I hoped for somewhat better documentation about how the protocol works, but this might be the missing link. I'll try to reverse-engineer it from some C examples.

I did also find this code. If you're familiar with Go, this might be helpful for reconstructing something in Rust. I would build support based on this code myself as I've written a fair amount of Go, but I have nothing I can really test it against as I don't know how nflog is used in Linux. If this helps you and you want to submit a PR, I'll gladly look it over. If you do, please also submit it with an example in the examples/ directory so I can test against it. For now, I'm going to close this out as I don't think I'll be able to help too much more here.

You could have just assigned the issue onto me, I'm working on this and I think I'm slowly getting somewhere. For now, I have code that's full of magic constants that'll have to be made into proper types and enums, but I'm reverse engineering the protocol slowly.
As for testing, there's not much, really. Just doing iptables -I INPUT -j NFLOG --nflog-group 0 and listening onto the group 0 should just start spitting packets, one message each. I just need to figure how to build the first few config messages to turn it on.

I'll reopen and assign this to you.


Bug: The Shadow checkbox is not clickable when it is unchecked

The label is still clickable, but not the box itself.

Looking into it

Determined the issue could be resolved by commenting out line 420 on the Editor.tsx file

Tested it with tab and arrow controls using space bar to activate checkbox. Test passed on local development environment.

Thanks!


M3-947 Update IconTextLink alignment

small tweak to re-align the icon and label.

Coverage remained the same at 28.004% when pulling 39c1e35f8e0904e927d7037046044edafcf39921 on alioso:M3-947 into 36931237d5c8c638c1eeeea4b6f8848091023258 on linode:develop.


Output HTML can't be saved due to UnicodeEncodeError exception: 'ascii' codec can't encode character u'\u2018'

Hi Gerben,
First things first - thank you for such great tool :) I've just started to use it ;)
Unfortunately, I've stuck with an error thrown by UnicodeEncodeError while HTML with output is saved to output file (sorry for url redacted, but it comes from private BB program and I can't disclose it - basically it's just big, minified JavaScript file, full of juicy endpoint URLs)
Here's how I call your script:
bl4de:~/hacking/tools/LinkFinder $ ./linkfinder.py -i https://[REDACTED]/script.js

And the result is:
Traceback (most recent call last):
  File "./linkfinder.py", line 132, in <module>
    text_file.write(html)
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2018' in position 71461: ordinal not in range(128)
bl4de:~/hacking/tools/LinkFinder $

\u2018 is Unicode Character 'LEFT SINGLE QUOTATION MARK' (http://www.fileformat.info/info/unicode/char/2018/index.htm). When I've tried to look for it in JS file, I found it's just regular \u0027 (apostrophe).
I found how to (probably) resolve such issues in this StackOverflow thread:
https://stackoverflow.com/questions/9942594/unicodeencodeerror-ascii-codec-cant-encode-character-u-xa0-in-position-20
For now, I've just made a quick workaround for this using try...except:
try:
    text_file = open(args.output, "w")
    text_file.write(html)
    text_file.close()
    print("URL to access output: file:///%s" % os.path.abspath(args.output))
except UnicodeEncodeError, e:
    print("Output can't be saved in {} due to exception: {}".format(args.output, e))

If you'd like to I can try to provide PR with fix for this issue :)
Regards,
bl4de

Hi bl4de! Thanks for the feedback. Using str.encode('utf-8') should have fixed this. Can you confirm whether: https://github.com/GerbenJavado/LinkFinder/commit/89771be1f7153f76c5c30012a64bd0dd0d1206fc fixed this or not?

Aah the fix seems incomplete for Python3 I'll further investigate

Hi Gerben,
On macOS/Python 2.7.10 I can confirm it's fixed 👍


allow edit of user name

Which Issue was this PR made for?

Closes #166

What is within the scope with this PR
Allow changing of user name by prompting user response and then send web socket event for the change and then all users in the room receive the event to change name in user context

https://user-images.githubusercontent.com/34047281/196068915-bd0e7594-5277-4892-80d5-3520a3a59f19.mp4
Thanks for the awesome work! It looks great.
I just saw this bug where pressing a button on the bottom bar caused the name to be reset.

Thank you @vinmaster for finding and contributing to the project.
Since this project was not very well documented what goes where, I think there are some confusions on what exactly is needed to update things.
In this particular issue, the user information is shared among all the people through webRTC protocol, after the initial handshake, it was needed to be updated through src/classes/PeerProcessor.ts, the example can be found in pages/RoomPage/index.tsx under updateSelfUserInfo.
What I would do instead is to reuse updateSelfUserInfo and change name through this.
It would be some props passing involved if this were to happen, but feel free to create follow up issue to avoid this props passing too!
Thank you again for your work!

Thank you @vinmaster for finding and contributing to the project. Since this project was not very well documented what goes where, I think there are some confusions on what exactly is needed to update things. In this particular issue, the user information is shared among all the people through webRTC protocol, after the initial handshake, it was needed to be updated through src/classes/PeerProcessor.ts, the example can be found in pages/RoomPage/index.tsx under updateSelfUserInfo. (Sorry about addUserInfo being a bad naming, should probably be updateUserInfo)
https://github.com/Amijakan/mochatto/blob/e813cde1c985380dbe6eb8b92e5d666753b01f9b/client/src/pages/RoomPage/index.tsx#L41-L46
What I would do instead is to reuse updateSelfUserInfo and change name through this.
It would be some props passing involved if this were to happen, but feel free to create follow up issue to avoid this props passing too!
Thank you again for your work!

I'm personally ok with keeping the editUserName but yeah I totally missed that.
@vinmaster We don't actually hold any value for userInfos (yeah it's unintuitive sry :smiling_face_with_tear:) so you need to pass in the current userInfo as a parameter to the reducer like we do with addUser. If just re-using addUser in the RoomPage seems easier, that totally works for me too.
@Njima1572 We should log a refactoring ticket for this to hold userInfos within UserContext (and also I guess renaming addUser)

I've updated to re-use addUserInfo. Not 100% sure if this is what you guys meant 😅


Add support for fill colors and font AA.

Also, mark Core Graphics contexts as Send and Sync since (I believe) they
are thread-safe.
r? @metajack

@bors-servo r+

Reviewed 2 of 2 files at r1.
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from the review on Reviewable.io

:pushpin: Commit d072ab3 has been approved by metajack

:hourglass: Testing commit d072ab3 with merge d683ba8...

:sunny: Test successful - travis


[#329] Performance fix: doc detail page

Reported Issue:

0.247 CLS with 86 mobile lighthouse score reported in this doc detail page
https://pagespeed.web.dev/analysis/https-www-hlx-live-docs-sidekick/rc88p931o4?form_factor=mobile

Updates in current PR:

update embed.js to use intersectionObserver for rendering youtube & gist block
fixed height in breadcrumb to prevent layout shift
cleanup unused css

Test Urls:
Before: https://main--helix-website--adobe.hlx.page/docs/sidekick
After: https://redesign-doc-page-perf-fix--helix-website--adobe.hlx.live/docs/sidekick

@snowiewdev this PR is definitely a big step in the right direction! However, the main element still seems to move around quite a bit:
.
FYI, I added the .live URL as test URL to have a cached and more constant reference.

Just created a new issue related to the CLS issue on the <main> element, let's submit another PR for the fix there.


__wait_for_connect should inform it is waiting

For a beginner user of orchestrator, when running scripts it can be unclear what is happening, for example:
$ ./bm_cassandra.py
[14:52:01]-------------[ Installing Cassandra: started ]--------------------------------------------------------
    [<IP_ADDRESS>] Update: started

(in my case) hangs for a few minutes after "Update: started", with no feedback. Behind the scenes, it is waiting in __wait_for_connect, but no feedback for a user is presented. Ideally, something like this should be printed:
$ ./bm_cassandra.py
[14:52:01]-------------[ Installing Cassandra: started ]--------------------------------------------------------
    [<IP_ADDRESS>] Update: started
    [<IP_ADDRESS>] Waiting for a successful connection
    [<IP_ADDRESS>] Still waiting for a successful connection (10 seconds elapsed, X second timeout)
    [<IP_ADDRESS>] Still waiting for a successful connection (20 seconds elapsed, X second timeout)

There is a configurable silence period that defaults to 30s. So after 30s you will get logging that it is trying.


Added background opacity props

As requested on PR #137 and based on a personal need to have a transparent chart background, just added two options on chartConfig: backgroundGradientFromOpacity and backgroundGradientToOpacity, which controls the opacity of the start and the end gradient colors, respectively.
This way we can get a completely transparent chart background this way:
<LineChart chartConfig={{ ..., backgroundGradientFromOpacity: 0, backgroundGradientToOpacity: 0 }} />

Great job 👍
Thank you, this is now available in v3.4.0

Glad to help some way :)


Add 'Enable Logs' option for AppSync API

Is your feature request related to a problem? Please describe.
Would like an option for the CLI to enable logging for the AppSync GraphQL api it generates, i.e. turn this on:

Describe the solution you'd like
The CLI to do this and add it to the cloudformation template.
Describe alternatives you've considered
I believe I'll have to modify the cloudformation template myself.

Is this something that can be done via a nested stack under the stacks/ dir, or is the only way is to modify cloudformation-template.json under the build/ dir which I assume will be overriden on every gql compile?

For this to happen, LogConfig needs to be set as part of creating the GraphQLApi. See https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-appsync-graphqlapi.html#cfn-appsync-graphqlapi-logconfig.

Agreed. We should add this as part of the add api command. @kaustavghosh06

We ran into this as well.  Would be nice to have an easy way to switch it on.  It looks like we and @hisham keep on running into similar stuff.  :)

+1
Any update on this?

+1  ... Interested as well!

+1 Looks like this is still in the 'TODO' column. :(

+1

+1

+1, it's been almost 1 year since this was opened. Logging is important.
Rule #1 of cloud: if it isn't automated then you're doing it wrong.
I think everyone here can agree with that. ;)
We don't have the luxury of modifying the CloudFormation template since it is re-generated every time there is a API / schema update as part of the transform process and we would lose any modifications made to it to simply enable logging.
This leaves us with the only option of manually enabling Appsync logging, breaking "rule #1 of cloud".
Has anyone found a workaround for this?

Hey guys, we're looking into this and have added this to our backlog.

I'm having this issue as well and I believe there's no workaround. I tried to modify the CloudFormation stack but the LogConfig is a property of AWS::AppSync::GraphQLApi and this resource can't be modified since it's created by Amplify during build phase.

Similarly, created a new issue to enable Tracing if you'd like to +1 too: https://github.com/aws-amplify/amplify-cli/issues/3835

+1

+1

+1

As a workaround, my team implemented an amplify backend post build script. We wrote a node app that checks to see whether or not the log config is enabled, if not, it uses the sdk to update it. The AWS docs, found here, mention an IAM role/policy you need to create to enable logging for appsync. We added that into a custom amplify cloudformation template, and then, in the same node app I mentioned above, because it is a post build step, we can reference that role and apply it appropriately. Hopefully this helps others workaround this issue.

Any update on this?

+1

+1

+1

Any progress?

I accidentally deleted the log group created for my AppSync API via Amplify. Is it possible to undo that or attach a new log group? It doesn't seem possible in the console/UI. After a few attempts, it looks like that feature just causes the page to freeze.


Can you provide the inference version of DeepSeek based on vllm, deepspeed and tensorrt-llm

Can you provide the inference version of DeepSeek based on vllm, deepspeed and tensorrt-llm

we have support vllm in the latest version


Make the app wasm compatible

Attempt to make the app wasm compatible to serve in the web

│   ├── grammers-mtsender v0.5.0
│   │   ├── bytes v1.5.0
│   │   ├── futures-util v0.3.30 ()
│   │   ├── grammers-mtproto v0.5.0 ()
│   │   ├── grammers-tl-types v0.5.1 (*)
│   │   ├── log v0.4.20
│   │   └── tokio v1.36.0
│   │       ├── bytes v1.5.0
│   │       ├── libc v0.2.153
│   │       ├── mio v0.8.10
│   │       │   └── libc v0.2.153
mio is not wasm compatible! Likely won't be able to bypass it.

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
tedt10e, @willjleong, @tomasovic, @tocoteron, @brightclark, @yanganto, @Un4G173N, @g-r-a-n-t, @juniuszhou, @abel-byte, @LXJ2, @dav8t, @hustxiaoc, @daweth, @1701175145, @DaviRain-Su, @3b40eb98, @rahulnm, @masami87, @Dmdv, @Shawndslee, @Glow-in-the-dark, @Darth123658, @ZGQ-inc, @defispartan, @rofuun, @haua998, @Lz1y, @Dougie008, @TalkWIthKeyboard, @massun-onibakuchi, @jakerumbles, @hzqd, @longcpp, @alikonuk1, @steffenix, @stan-dot, @weipin, @19-xiaogao, @fanyang1988, @xiaosongfu, @dimlev, @Folyd, @mshrieve, @deadblackclover, @mdtanrikulu, @NukeManDan, @zeroXbrock, @3ddi, @chenjunwen186p0p3yee, @astrolemonade, @SergioArrighi, @archi-cszcli, @daiwanwei, @pedrommaiaa, @randhindi, @yihau, @andreisilviudragnea, @idkwim, @Godaiandi, @fuyutarow, @limotree, @intdance, @ccamateur, @coopbri, @macrocan, @yaroslavyaroslav, @DennisDv24, @nkysg, @iamazy, @b00f, @ZhiXiao-Lin, @zkmsg, @HAOYUatHZ, @lowlowcoder, @thasarito, @MRGRAVITY817, @caoanlong, @franssl, @ivanceras, @dalaorock, @ccmlm, @marko-lazic, @asadkovich, @Apoll95, @rameight, @sorawit, @misoobu, @MoodyBoi, @eratzlaff, @saki-osive, @DukeCaesar, @sashaaldrick, @tacoda, @greyireland, @frost-scorpio, @chirag-bgh, @bredamatt, @marmelo-cotoneum

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis.
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
zerosnacks, @lambda-0x, @llifezou, @vernonjohnson, @lightning-li, @micrub, @sebastiantf, @somerb, @kss-fluency, @whilei, @ZGQ-inc, @enif-lee, @earthflower, @WilfredTA, @Just4Ease, @haua998, @kootsZhin, @valeryz, @felixangell, @IvonaldoAmaral, @orangemio, @vbrvk, @execnow, @marko-lazic, @moreal, @brandawsd, @kimpers, @nuts-rice, @ZiNai, @sbusso, @pistomat, @dackerer, @garious, @hustxiaoc, @r-tom90, @kriptoibo, @dineshpinto, @saman-pasha, @dimlev, @TomaszWaszczyk, @trmaphi, @guijunchen, @Dmdv, @Jawy77, @qymlyl, @denismaxim0v, @0xbillw, @longcpp, @2Higara, @gabrielfalcaop4r4no1ak, @0xethsign, @sgc109, @puzzithinker, @goncaloMagalhaes, @zzir, @zqhxuyuan, @hyperleex, @BoundlessCarrot, @cherry-yl-sh, @Archisman-Mridha, @X4, @seyedhanaee, @p0p3yee, @jtriley-eth, @diazMelgarejo, @onlymaresia, @dcbuild3r, @Animismo, @jonahcui, @rhizome01, @joyqvq, @cd1m0, @TalkWIthKeyboard, @mmacedoeu, @zhangzhongzhong, @edmand46, @pinardZ, @tmpfs, @ImpossibleReality, @TheRustyPickle, @nellyisanon, @tommy-ca, @asadkovich, @zachperez, @alfellati, @willjleong, @Shawndslee, @marmelo-cotoneum, @hineso11, @wstreet, @sorpaas, @ackintosh, @mia-stein, @HegelXu, @HAOYUatHZ, @mcass19, @fwx5618177, @darrylyeo, @DieracDelta


Retinatrack

It could be really useful to compare your anchor-free approach with the tracking version of RetinaNet https://arxiv.org/abs/2003.13870

Thanks for the reference! Yes, this is relevant. We will try.

Yes seems natural :wink:


error in calling createTopicBrowser with output of clusterinfo

output <- createTopicBrowser(cinfo)
Writing html to /tmp/RtmpaK8rHp/topicbrowser_47c588cb82c.html
Error in nrow(info$topics_per_doc) : object 'info' not found

update: the function seems to be looking for a global object of info instead of what is passed in. this needs fixing.

 If I tested with the object called that I wouldn't have caught it.
Can you test with the following?
info <- cinfo
output <- createTopicBrowser(info)

this works as expected, but calling createTopicBrowser(cinfo) would not.


16.23 backports

More backports for the 16.x.x branch (created by cherry-picking commits from the master branch)

@davisagli
I went through the list and I've found these PRs missing from the backports:
https://github.com/plone/volto/pull/5018
https://github.com/plone/volto/pull/5017
https://github.com/plone/volto/pull/5029
I would merge them as well... any reason why you didn't?

@sneridagh
5018 - I wasn't confident it's backwards compatible
5017 - It's just a comment, I probably thought it didn't matter
5029 - this one caused a regression and was later reverted


Fixing reading files in sbt 1.4+ subprojects

I did some testing with the current edge release, and found a bug:
The fix for #2645 is not working when using sbt subprojects.
In my case I have a subproject, which pulls in and uses lombok, and a parent (root) project (which depends on the subproject).
Now when running sbt in the root project and start compiling that root project, which in turn also compiles the subproject, the lombok.config (located in the subproject) is, again, ignored, resulting in compiling errors in the subproject.
After some debugging it turns out that the URI reported by sbt for the subproject has the format:
vf://tmp//home/mkurz/myproject/src/main/java/example/Main.java

instead of the format
vf://tmp/$%7BBASE%7D/src/main/java/example/Main.java

when using a normal, single root project with lombok.
That makes sense, because the files of the subproject are obviously not located within the root project (=BASE, where relative paths like ${BASE}/src/main/java/example/Main.java are used), therefore absolut paths are used (/home/mkurz/myproject/src/main/java/example/Main.java).
The fix is quite easy: When the file path doesn't start with ${ (when looking for ${BASE}), we can assume the path is very likely an absolute one, so we just use it.
I can confirm this fixes our compiler errors and the app runs smoothly.

@rzwitserloot Can you please have a look at this pull request before the next release? The sbt fix you provided unfortunately does not handle sbt subprojects yet. Thanks!


Update PreciseManeuver for the new version of KSP

I also have a .version file in my repo now (available here https://raw.githubusercontent.com/radistmorse/KSPPreciseManeuver/master/PreciseManeuver.version). I was said you can use it, somehow. Can you?

I also have a .version file in my repo now... I was said you can use it, somehow. Can you?

Add a $vref property with a value of #/ckan/ksp-avc. Like this.

LGTM Thanks


feature: Add hint to docs about lazy.nvim setup

Did you check the docs?

[X] I have read all the neoconf.nvim docs

Is your feature request related to a problem? Please describe.
I just installed neoconf for the first time, using lazy.nvim. However, the plugin wasn't getting imported. I realised this is happening because there is no opts in the example which was originally included in https://github.com/folke/neoconf.nvim/pull/48 which even includes an explanation.
However, this means that I had to do a bunch of debugging before I realised what was going on.
Describe the solution you'd like
Some update to the docs so that users aren't confused by this. If I understand correctly, because users need to ensure neoconf is loaded first, you don't want users blindly copying the line and ending up with a broken neoconf. I had actually added neoconf as a dependency to nvim-lspconfig , but that alone obviously that alone doesn't fix it.
I might be missing something, but could a full example look like this:
  {
    "folke/neoconf.nvim",
    cmd = {
      "Neoconf",
    },
    opts = {},
  },
{
    "neovim/nvim-lspconfig",
    -- Add this to your nvim-lspconfig to ensure neoconf is loaded first
    dependencies = { "folke/neoconf.nvim" },
  },

If this is the correct config, I'm happy to make a PR, if it's not then I've set it up wrong and would appreciate some help in what to do better.
Describe alternatives you've considered
I think the issue is fixed for me, but I'm sure I won't be the last neovim newbie to step into this trap. Or maybe I did something else wrong?
Additional context
No response

I still think this is worth having in the docs


DOC: #2 clarify theme change process in lazygit config.yml

@nullishamy per the discussion in #2, specifically per this comment.

[x] Updated the README.md.
[x] Fixed minor markdown linting issues.

Please let me know if there are any further changes you would like me to make.

Are the theme keys case sensitive? You lower-cased them all, so it would make sense to be consistent. The example config from lg has it in the case shown in this repo.

Are the theme keys case sensitive? You lower-cased them all, so it would make sense to be consistent. The example config from lg has it in the case shown in this repo.

nice catch! I've updated in the latest commit

LGTM - thanks for the contribution!

thank you for creating this theme, and your patient help with the PR.


Test should run as a Docker run command

currently the tests run as part of the Docker build process.
Ideally a testing docker image could be generated that has the compiled code ready for tests. This will require modifying the CMakeLists.txt to build the tests (but not run them) and then copy the test files into the new container.

looks like the test files (i.e. test_*) should be copied in the the docker image in a known location.
then, an entrypoint needs to be made that catched test and runs the app accordingly.

fixed with:  2f84c39


Added Catch the object game

PR Description 📜
I have added the catch the object game
Fixes #5033
https://github.com/user-attachments/assets/60cc8e17-00cb-48e7-a531-2cf245a6dd44

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in GameZone's README.md
[x] I have added README.md in my Game folder
[x] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.
[x] I have added my Game to gamesData.json file and it is loading properly on main website as intended.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @Ayushmaanagarwal1211 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@ishita-43  Please review it and merge it

Also add your game image in the pr follow naming convention for that mentioned in contribution. Md

@ishita-43  Done Please check

Thank you  @Ayushmaanagarwal1211 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Toggling opacity is slow in Firefox

Having a lot of features in a vector layer, and setting the opacity to the layer causes Firefox (43) to be really slow.

The conversion from opaque to semi-transparent is a lot slower in Firefox than in Chrome.
The reverse operation (semi-transparant to opaque) is very fast in both.
The map panning and zooming with semi-transparent features also seems slower in Firefox than in Chrome, but the difference is smaller here.

This doesn't happen when setting the opacity of a tile layer. Probably due to the lower number of images on the canvas.
IMO this should certainly be mentioned in the docs on setOpacity, and the toggling slowdown should be fixed. But I don't know if you can fix this, or if this bug needs to be passed upstream to Firefox (with a different minimal example in that case).
The minimal example includes 400 features that can have an opacity set.

minimal example (of course a html file, but that extension wasn't allowed):
minimal.html.txt

Do you see the same decrease in performance when using a PNG image instead of a SVG?

I just tested that case, and I don't see a slowdown for PNG. I also tested whether a data URI makes a difference or not, and apparently it doesn't. For completeness and clarity, my tests and results:

Data URI PNG: fast toggling
External PNG: fast toggling
Data URI SVG: slow toggling
External SVG: slow toggling

Closing due to lack of activity.


replaced ${ARCHITECTURE}" by  "${BUILD_CONFIG[OS_ARCHITECTURE]}"

This should fix windows issue I see:
Certificate was added to keystore
Number of certs processed: 147

real	2m26.134s
user	0m42.929s
sys	0m24.072s
build.sh : 20:48:54 : Initiating build ...
Version: local dir; OPENJDK_BUILD_NUMBER set as
/home/tester/temurinbuild-1717011006/temurin-build/sbin/build.sh: line 193: ARCHITECTURE: unbound variable
+ BUILD_RESULT=1
+ popd

I'm just testing it on widows VM. But it seems that the ARCHITETURE is indeed not set. Please eyball carefully, I'm unable to judge the impact

the build failure: https://github.com/adoptium/temurin-build/actions/runs/9301406891/job/25599478960 is related

fixed

grep -r ARCHITECTURE=
sbin/common/downloaders.sh:      local ARCHITECTURE="${1}"
build-farm/platform-specific-configurations/mac.sh:MACHINEARCHITECTURE=$(uname -m)
build-farm/platform-specific-configurations/linux.sh:       echo /bin/ls is not a 32-bit binary but ARCHITECTURE=arm. Non-32-bit userland is invalid without extra work
build-farm/make-adopt-build-farm.sh:   ARCHITECTURE=$(uname -p)
build-farm/make-adopt-build-farm.sh:   if [ "$OSTYPE" = "cygwin"  ] || [ "${ARCHITECTURE}" = "unknown" ]; then ARCHITECTURE=$(uname -m); fi # Windows / Alpine
build-farm/make-adopt-build-farm.sh:   if [ "$ARCHITECTURE" = "x86_64"  ]; then ARCHITECTURE=x64;        fi # Linux/x64
build-farm/make-adopt-build-farm.sh:   if [ "$ARCHITECTURE" = "i386"    ]; then ARCHITECTURE=x64;        fi # Solaris/x64 and mac/x64
build-farm/make-adopt-build-farm.sh:   if [ "$ARCHITECTURE" = "sparc"   ]; then ARCHITECTURE=sparcv9;    fi # Solaris/SPARC
build-farm/make-adopt-build-farm.sh:   if [ "$ARCHITECTURE" = "powerpc" ]; then ARCHITECTURE=ppc64;      fi # AIX
build-farm/make-adopt-build-farm.sh:   if [ "$ARCHITECTURE" = "arm"     ]; then ARCHITECTURE=aarch64;    fi # mac/aarch64
build-farm/make-adopt-build-farm.sh:   if [ "$ARCHITECTURE" = "armv7l"  ]; then ARCHITECTURE=arm;        fi # Linux/arm32
docker/dockerfile-generator.sh:ENV ARCHITECTURE=x64

I really think it is bad sed/refactoring/reuse or whatever.. as ARCHITECTURE seems to be related only to build-farm.  Except that docker file
docker/dockerfile-generator.sh-
docker/dockerfile-generator.sh-printContainerVars(){
docker/dockerfile-generator.sh-  echo "
docker/dockerfile-generator.sh-ARG OPENJDK_CORE_VERSION
docker/dockerfile-generator.sh-ENV OPENJDK_CORE_VERSION=\$OPENJDK_CORE_VERSION
docker/dockerfile-generator.sh:ENV ARCHITECTURE=x64
docker/dockerfile-generator.sh-ENV JDK_PATH=jdk
docker/dockerfile-generator.sh-ENV JDK8_BOOT_DIR=/usr/lib/jvm/jdk8" >> "$DOCKERFILE_PATH"
docker/dockerfile-generator.sh-}
docker/dockerfile-generator.sh-
docker/dockerfile-generator.sh-generateFile() {

Where however
grep -e ARCHITECTURE docker/dockerfile-generator.sh
ENV ARCHITECTURE=x64
BUILD_CONFIG[OS_ARCHITECTURE]=\"x86_64\"

it do not seem to b eused.

@andrew-m-leonard  @sxa  thoughts?

@andrew-m-leonard @sxa thoughts?

@judovana so we have to be careful here, as OS_ARCHITECTURE is the "BUILD arch", whereas ARCHITECTURE is the TARGET arch
We have a known issue with these variables that needs investigating: https://github.com/adoptium/temurin-build/issues/3648

Ouch.
So for the
-  if [ "${BUILD_CONFIG[OPENJDK_CORE_VERSION]}" = "${JDK8_CORE_VERSION}" ] && [ "${ARCHITECTURE}" = "x64" ] && [ "${BUILD_CONFIG[BUILD_VARIANT]}" != "${BUILD_VARIANT_OPENJ9}" ]; then
+  if [ "${BUILD_CONFIG[OPENJDK_CORE_VERSION]}" = "${JDK8_CORE_VERSION}" ] && [ "${BUILD_CONFIG[OS_ARCHITECTURE]}" = "x86_64" ] && [ "${BUILD_CONFIG[BUILD_VARIANT]}" != "${BUILD_VARIANT_OPENJ9}" ]; then

Then ${BUILD_CONFIG[ARCHITECTURE]} should be used instead of ${BUILD_CONFIG[OS_ARCHITECTURE]  as free type builds only for x64 target?
But with the
-   if [ ${JDK11_BOOT_DIR+x} ] && [ -d "${JDK11_BOOT_DIR}" ] && [ "${ARCHITECTURE}" != "arm" ]; then
+  if [ ${JDK11_BOOT_DIR+x} ] && [ -d "${JDK11_BOOT_DIR}" ] && [ "${BUILD_CONFIG[OS_ARCHITECTURE]}" != "arm" ]; then

The ${BUILD_CONFIG[OS_ARCHITECTURE]} is correct, as it is OS where this special case bites?

Just to clarify, I'm not sure why your builders are passing,  but the ARCHITECTURE: unbound variable is default build of jdk8 on windows. This really should be fixed.

Just to clarify, I'm not sure why your builders are passing, but the ARCHITECTURE: unbound variable is default build of jdk8 on windows. This really should be fixed.

The builders use the build-farm, which set ARCHITECTURE

ty!


get error in testing pyrouge!

 This usually isn't a problem, but if you run this code on another system, or in a different virtual environment, it may use a different parser and behave differently.

The code that caused this warning is on line 4 of the file /home/mahsa/anaconda3/bin/pyrouge_convert_rouge_format_to_plain_text.  Saving system files to /tmp/tmph0s8_f0z/system and model files to /tmp/tmph0s8_f0z/model.
2017-12-14 01:53:10,477 [MainThread  ] [INFO ]  Processing files in data/systems_plain.
2017-12-14 01:53:10,477 [MainThread  ] [INFO ]  Processing D30002.M.100.T.A.
2017-12-14 01:53:10,478 [MainThread  ] [INFO ]  Processing D30003.M.100.T.A.
2017-12-14 01:53:10,478 [MainThread  ] [INFO ]  Processing D30001.M.100.T.A.
2017-12-14 01:53:10,479 [MainThread  ] [INFO ]  Processing D30005.M.100.T.A.
2017-12-14 01:53:10,479 [MainThread  ] [INFO ]  Saved processed files to /tmp/tmph0s8_f0z/system.
2017-12-14 01:53:10,479 [MainThread  ] [INFO ]  Processing files in data/models_plain.
2017-12-14 01:53:10,479 [MainThread  ] [INFO ]  Processing D30005.M.100.T.C.
2017-12-14 01:53:10,480 [MainThread  ] [INFO ]  Processing D30002.M.100.T.E.
2017-12-14 01:53:10,480 [MainThread  ] [INFO ]  Processing D30001.M.100.T.C.
2017-12-14 01:53:10,481 [MainThread  ] [INFO ]  Processing D30001.M.100.T.B.
2017-12-14 01:53:10,481 [MainThread  ] [INFO ]  Processing D30003.M.100.T.F.
2017-12-14 01:53:10,482 [MainThread  ] [INFO ]  Processing D30003.M.100.T.C.
2017-12-14 01:53:10,482 [MainThread  ] [INFO ]  Processing D30001.M.100.T.D.
2017-12-14 01:53:10,483 [MainThread  ] [INFO ]  Processing D30005.M.100.T.G.
2017-12-14 01:53:10,483 [MainThread  ] [INFO ]  Processing D30002.M.100.T.C.
2017-12-14 01:53:10,483 [MainThread  ] [INFO ]  Processing D30002.M.100.T.B.
2017-12-14 01:53:10,484 [MainThread  ] [INFO ]  Processing D30005.M.100.T.B.
2017-12-14 01:53:10,484 [MainThread  ] [INFO ]  Processing D30003.M.100.T.B.
2017-12-14 01:53:10,484 [MainThread  ] [INFO ]  Saved processed files to /tmp/tmph0s8_f0z/model.
2017-12-14 01:53:10,486 [MainThread  ] [INFO ]  Written ROUGE configuration to /tmp/tmp6a8qeb0b/rouge_conf.xml
2017-12-14 01:53:10,486 [MainThread  ] [INFO ]  Running ROUGE with command /home/mahsa/ROUGE-1.5.5/ROUGE-1.5.5.pl -e /home/mahsa/ROUGE-1.5.5/data -c 90 -2 -1 -U -r 1000 -n 2 -w 1.2 -a -m data/config_test2.xml -m /tmp/tmp6a8qeb0b/rouge_conf.xml
Cannot open exception db file for reading: /home/mahsa/ROUGE-1.5.5/data/WordNet-2.0.exc.db
Traceback (most recent call last):
  File "/home/mahsa/anaconda3/bin/pyrouge_evaluate_plain_text_files", line 4, in <module>
    __import__('pkg_resources').run_script('pyrouge==0.1.3', 'pyrouge_evaluate_plain_text_files')
  File "/home/mahsa/anaconda3/lib/python3.6/site-packages/setuptools-27.2.0-py3.6.egg/pkg_resources/__init__.py", line 744, in run_script
  File "/home/mahsa/anaconda3/lib/python3.6/site-packages/setuptools-27.2.0-py3.6.egg/pkg_resources/__init__.py", line 1499, in run_script
  File "/home/mahsa/anaconda3/lib/python3.6/site-packages/pyrouge-0.1.3-py3.6.egg/EGG-INFO/scripts/pyrouge_evaluate_plain_text_files", line 25, in <module>
    main()
  File "/home/mahsa/anaconda3/lib/python3.6/site-packages/pyrouge-0.1.3-py3.6.egg/EGG-INFO/scripts/pyrouge_evaluate_plain_text_files", line 21, in main
    output = rouge.convert_and_evaluate(args.system_id, args.split_sents)
  File "/home/mahsa/anaconda3/lib/python3.6/site-packages/pyrouge-0.1.3-py3.6.egg/pyrouge/Rouge155.py", line 364, in convert_and_evaluate
    rouge_output = self.evaluate(system_id, rouge_args)
  File "/home/mahsa/anaconda3/lib/python3.6/site-packages/pyrouge-0.1.3-py3.6.egg/pyrouge/Rouge155.py", line 339, in evaluate
    rouge_output = check_output(command).decode("UTF-8")
  File "/home/mahsa/anaconda3/lib/python3.6/subprocess.py", line 336, in check_output
    **kwargs).stdout
  File "/home/mahsa/anaconda3/lib/python3.6/subprocess.py", line 418, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/home/mahsa/ROUGE-1.5.5/ROUGE-1.5.5.pl', '-e', '/home/mahsa/ROUGE-1.5.5/data', '-c', '90', '-2', '-1', '-U', '-r', '1000', '-n', '2', '-w', '1.2', '-a', '-m', 'data/config_test2.xml', '-m', '/tmp/tmp6a8qeb0b/rouge_conf.xml']' returned non-zero exit status 255.
E.2017-12-14 01:53:11,148 [MainThread  ] [INFO ]  Writing summaries.
2017-12-14 01:53:11,151 [MainThread  ] [INFO ]  Processing summaries. Saving system files to /tmp/tmpub0odyyt/system and model files to /tmp/tmpub0odyyt/model.
2017-12-14 01:53:11,151 [MainThread  ] [INFO ]  Processing files in data/systems_plain.
2017-12-14 01:53:11,151 [MainThread  ] [INFO ]  Processing D30002.M.100.T.A.
2017-12-14 01:53:11,152 [MainThread  ] [INFO ]  Processing D30003.M.100.T.A.
2017-12-14 01:53:11,152 [MainThread  ] [INFO ]  Processing D30001.M.100.T.A.
2017-12-14 01:53:11,153 [MainThread  ] [INFO ]  Processing D30005.M.100.T.A.
2017-12-14 01:53:11,154 [MainThread  ] [INFO ]  Saved processed files to /tmp/tmpub0odyyt/system.
2017-12-14 01:53:11,154 [MainThread  ] [INFO ]  Processing files in data/models_plain.
2017-12-14 01:53:11,154 [MainThread  ] [INFO ]  Processing D30005.M.100.T.C.
2017-12-14 01:53:11,155 [MainThread  ] [INFO ]  Processing D30002.M.100.T.E.
2017-12-14 01:53:11,155 [MainThread  ] [INFO ]  Processing D30001.M.100.T.C.
2017-12-14 01:53:11,156 [MainThread  ] [INFO ]  Processing D30001.M.100.T.B.
2017-12-14 01:53:11,156 [MainThread  ] [INFO ]  Processing D30003.M.100.T.F.
2017-12-14 01:53:11,157 [MainThread  ] [INFO ]  Processing D30003.M.100.T.C.
2017-12-14 01:53:11,157 [MainThread  ] [INFO ]  Processing D30001.M.100.T.D.
2017-12-14 01:53:11,158 [MainThread  ] [INFO ]  Processing D30005.M.100.T.G.
2017-12-14 01:53:11,158 [MainThread  ] [INFO ]  Processing D30002.M.100.T.C.
2017-12-14 01:53:11,159 [MainThread  ] [INFO ]  Processing D30002.M.100.T.B.
2017-12-14 01:53:11,159 [MainThread  ] [INFO ]  Processing D30005.M.100.T.B.
2017-12-14 01:53:11,160 [MainThread  ] [INFO ]  Processing D30003.M.100.T.B.
2017-12-14 01:53:11,160 [MainThread  ] [INFO ]  Saved processed files to /tmp/tmpub0odyyt/model.
2017-12-14 01:53:11,162 [MainThread  ] [INFO ]  Written ROUGE configuration to /tmp/tmprdoxel4d/rouge_conf.xml
2017-12-14 01:53:11,162 [MainThread  ] [INFO ]  Running ROUGE with command /home/mahsa/ROUGE-1.5.5/ROUGE-1.5.5.pl -e /home/mahsa/ROUGE-1.5.5/data -c 95 -2 -1 -U -r 1000 -n 4 -w 1.2 -a -m /tmp/tmprdoxel4d/rouge_conf.xml
Cannot open exception db file for reading: /home/mahsa/ROUGE-1.5.5/data/WordNet-2.0.exc.db
Traceback (most recent call last):
  File "/home/mahsa/anaconda3/bin/pyrouge_evaluate_plain_text_files", line 4, in <module>
    __import__('pkg_resources').run_script('pyrouge==0.1.3', 'pyrouge_evaluate_plain_text_files')
  File "/home/mahsa/anaconda3/lib/python3.6/site-packages/setuptools-27.2.0-py3.6.egg/pkg_resources/__init__.py", line 744, in run_script
  File "/home/mahsa/anaconda3/lib/python3.6/site-packages/setuptools-27.2.0-py3.6.egg/pkg_resources/__init__.py", line 1499, in run_script
  File "/home/mahsa/anaconda3/lib/python3.6/site-packages/pyrouge-0.1.3-py3.6.egg/EGG-INFO/scripts/pyrouge_evaluate_plain_text_files", line 25, in <module>
    main()
  File "/home/mahsa/anaconda3/lib/python3.6/site-packages/pyrouge-0.1.3-py3.6.egg/EGG-INFO/scripts/pyrouge_evaluate_plain_text_files", line 21, in main
    output = rouge.convert_and_evaluate(args.system_id, args.split_sents)
  File "/home/mahsa/anaconda3/lib/python3.6/site-packages/pyrouge-0.1.3-py3.6.egg/pyrouge/Rouge155.py", line 364, in convert_and_evaluate
    rouge_output = self.evaluate(system_id, rouge_args)
  File "/home/mahsa/anaconda3/lib/python3.6/site-packages/pyrouge-0.1.3-py3.6.egg/pyrouge/Rouge155.py", line 339, in evaluate
    rouge_output = check_output(command).decode("UTF-8")
  File "/home/mahsa/anaconda3/lib/python3.6/subprocess.py", line 336, in check_output
    **kwargs).stdout
  File "/home/mahsa/anaconda3/lib/python3.6/subprocess.py", line 418, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/home/mahsa/ROUGE-1.5.5/ROUGE-1.5.5.pl', '-e', '/home/mahsa/ROUGE-1.5.5/data', '-c', '95', '-2', '-1', '-U', '-r', '1000', '-n', '4', '-w', '1.2', '-a', '-m', '/tmp/tmprdoxel4d/rouge_conf.xml']' returned non-zero exit status 255.

----------------------------------------------------------------------
Ran 11 tests in 3.937s

FAILED (errors=3)

Please help me. I dont know what to do?

Hi,
My problem has been solved.
First I like to tell some basic explanations that may be helpful to the others that are new to summarization and ROUGE-1.5.5 and pyrouge...
pyrouge is a python interface to contact with ROUGE-1.5.5 package that is written in Perl.
So you should first download ROUGE-1.5.5 package.
After that, you should download the latest version of the pyrouge package by this command:
git clone https://github.com/bheinzerling/pyrouge
Now the pyrouge package has been downloaded and you should go to this directory:
cd pyrouge
Install the setup.py file in pyrouge folder by this command:
python setup.py install
pyrouge needs to know where is the path to ROUGE-1.5.5 in your computer by running this command:
pyrouge_set_rouge_path.py /path_to_ROUGE-1.5.5/
for example in my Ubuntu this is:
pyrouge_set_rouge_path.py /home/mahsa/ROUGE-1.5.5/
Now you should test the correctness of the installation by this command:
python -m pyrouge.test
But when I run this command I get an error and finally:
Ran 11 tests in 3.937s

FAILED (errors=3)

I paid attention to the error and i see this in my error:
 Cannot open exception db file for reading: /home/mahsa/ROUGE-1.5.5/data/WordNet-2.0.exc.db
It means that WordNet-2.0.exc.db file can't be read.
To solve this problem I saw this link and it solved my problem.
cd data/WordNet-2.0-Exceptions/
rm WordNet-2.0.exc.db # only if exist
./buildExeptionDB.pl . exc WordNet-2.0.exc.db

cd ../
rm WordNet-2.0.exc.db # only if exist
ln -s WordNet-2.0-Exceptions/WordNet-2.0.exc.db WordNet-2.0.exc.db

It removes that file and reconstruct a new one. After that i run again python -m pyrouge.test and i get:
Ran 11 tests in 8.391s

OK

Thanks from bheinzerling and Masters Informatique 2014-2016.


LDAP 'group search' returns no results

when I select 'Look up LDAPS Groups', fill out the appropriate credentials, then search for a user, nothing happens. The UI spins for a second, then returns to its normal state. (originally I thought this might be a browser problem, as I don't use one of the big browsers, but testing across firefox and chromium have the same result).
In troubleshooting this issue, I enabled debugging mode, and can see the response from our ldap server is appropriate and contains groups. however after the response, these messages pop up in the logs:
[----] D, [2017-04-07T05:06:54.537825 #1975:3fddb5f48508] DEBUG -- : MIQ(MiqLdap#get_memberships) Enter get_memberships: cn=$REDACTED_USER,ou=Users,o=$REDACTED_ORG, max_depth: 5, current_depth: 1, attr: memberof
[----] D, [2017-04-07T05:06:54.538104 #1975:3fddb5f48508] DEBUG -- : MIQ(MiqLdap#get_memberships) Groups: []
[----] D, [2017-04-07T05:06:54.538395 #1975:3fddb5f48508] DEBUG -- : MIQ(MiqLdap#get_memberships) Exit get_memberships: cn=$REDACTED_USER,ou=Users,o=$REDACTED_ORG, result: []
For some reason, even though there are plenty of groups returnend on the debug logs, MIQ believes 'Groups' is an empty set

What type of Ldap server is this targeting ? Does it provide the memberof attribute on user objects ?


Account Activation Route Issue

Overview of the issue
An error is thrown "The page you requested does not exist" when one clicks the url received for account activation.
Motivation for or Use Case
Generate application using generator-jhipster-vuejs with "jhipster --blueprint vuejs" command.
Reproduce the error
Generate application using generator-jhipster-vuejs with "jhipster --blueprint vuejs" command.
Related issues

Suggest a Fix
Change activation route path from "/activate" to "/account/activate"
JHipster Version(s)
6.5.1
JHipster configuration
JHipster Version(s)
<EMAIL_ADDRESS>/home/ubuntu/JHipster/
└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>

JHipster configuration, a .yo-rc.json file generated in the root folder

.yo-rc.json file

{
  "generator-jhipster": {
    "promptValues": {
      "packageName": ""
    },
    "jhipsterVersion": "6.5.1",
    "applicationType": "monolith",
    "baseName": "",
    "packageName": "",
    "packageFolder": ",
    "serverPort": "8080",
    "authenticationType": "jwt",
    "cacheProvider": "ehcache",
    "enableHibernateCache": true,
    "websocket": "spring-websocket",
    "databaseType": "sql",
    "devDatabaseType": "postgresql",
    "prodDatabaseType": "postgresql",
    "searchEngine": false,
    "messageBroker": false,
    "serviceDiscoveryType": false,
    "buildTool": "maven",
    "enableSwaggerCodegen": true,
    "jwtSecretKey": "",
    "embeddableLaunchScript": false,
    "testFrameworks": ["gatling", "cucumber"],
    "jhiPrefix": "jhi",
    "entitySuffix": "",
    "dtoSuffix": "DTO",
    "otherModules": [
      {
        "name": "generator-jhipster-vuejs",
        "version": "1.3.0"
      }
    ],
    "enableTranslation": false,
    "clientPackageManager": "npm",
    "blueprints": [
      {
        "name": "generator-jhipster-vuejs",
        "version": "1.3.0"
      }
    ],
    "herokuAppName": "",
    "herokuDeployType": "git"
  },
  "generator-jhipster-vuejs": {
    "jhipsterVersion": "6.5.1",
    "applicationType": "monolith",
    "baseName": "",
    "useSass": true,
    "clientPackageManager": "npm",
    "clientFramework": "vue",
    "clientTheme": "solar",
    "clientThemeVariant": "primary"
  }
}

JDL for the Entity configuration(s) entityName.json files generated in the .jhipster directory

JDL entity definitions

.
.
.

Environment and Tools
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
git version 2.7.4
node: v10.16.3
npm: 6.9.0
yeoman: 3.1.1
yarn: 1.17.3
Docker version 19.03.1, build 74b1e89e8a
docker-compose version 1.8.0, build unknown
Entity configuration(s) entityName.json files generated in the .jhipster directory

Browsers and Operating System
Ubuntu 16.04.6 LTS

[ ] Checking this box is mandatory (this is just to show you read everything)

See my https://github.com/jhipster/jhipster-vuejs/issues/538#issuecomment-582128505
Already fixed in v1.4.0


Show original exercise in diff for an edit of a solution

When I check an unrevised edit for a solution it would be great to see also the original exercise text. Example (is an exercise part without the original exercise text):

This will get solved with the new editor, so #wontfix


Weather forecasting data

Just read http://www.randalolson.com/2015/08/13/the-new-york-times-weather-chart-redux/ that is scrapping from http://www.wunderground.com/
Useful and appropriate?

Certainly, especially the scraper and parser.


Intermittent error "Fail to load customizer for column"

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version: 114.0.1823.43 (64 bit) Edge
SPFx version: 1.16.1
Node.js version 16.20.0

Describe the bug / error
I've created a field customizer to override the rendering of a text field. It works fine when deployed and running locally.
The app package is deployed to the site catalog and besides the field customizer also contains a web part.
With Powershell I've set the ClientSideComponentId of the Title field to the ID of the field customizer. When I go to the site for the first time, the title field is empty, and the console shows this error:
Fail to load customizer for column: Title, error: Manifest not found for componentId
When I hard refresh once or twice, the field becomes visible most of the times, but not always. From that moment on it works, until I close the browser.
It has been replicated consistently across multiple users.
I've also tried to create a new column instead of using the title field, but the same problem occurs.
Whenever the problem occurs, I noticed that in the dev console => sources => the bundle for the field customizer hasn't been loaded. When it works, I can see a bundle there containing the field customizer.
So my guess is that somehow SharePoint doesn't load my app javascript for some reason.
Steps to reproduce

Create field extension with yeoman
Create app package and deploy to site app catalog
With powershell, set the ClientSideComponentId of the title field
Notice that the title field is empty and a message is shown in the console that the field extension couldn't be found.

Expected behavior
The field extension shows every time.

Also getting this behaviour with a field customizer built with 1.13.1 and using latest Chrome (115.0.5790.110). The F12 Console has an info message for splistwebpack.js:
"Fail to load customizer for column: <fieldname>, componentId: 699096e5-97d5-4024-a72c-ef7d4bdde998, error: Manifest not found for componentId "699096e5-97d5-4024-a72c-ef7d4bdde998"

Hi @anthonywhite yep, I could also reproduce it with the default generated customizer. We also raised a ticket with MS who confirmed the issue, and they could replicate it. After internal escalation we have received the disappointing response from the product team that this is by design and won't be fixed any time soon...

@roldengarm I really hope I have misunderstood. You seem to be saying that the product group (SharePoint product group?) is basically saying "yeah customizers don't work and we're not going to fix them" !
I don't understand how something not working can be "by design"
Please tell me I'm wrong...

@anthonywhite no, you haven't misunderstood.

@VesaJuvonen any comment on the above?

@roldengarm - I believe there is a misunderstanding.
I don't know the details of the support ticket.
But most probably the response was that it may happen due to caching when some Web Front Ends are not getting updated right away.
And on some tenants it might take a while while the cache is updated.
We have a fix rolling out to decrease the time for cache update. When it's propagated (I would give it a few weeks) all the cache should be up to date in 10 minutes.
Meaning if you upload an SPFx app in 10 minutes it MUST be available (same for new versions of the app).
If in a few weeks you're still experiencing the issue - please mention me in this issue. I will not be closing it.

@AJIXuMuK the response from the SP team was indeed it would be caching. However, the problem also happens weeks after the last deployment, so it doesn't seem like a caching issue.
We replied that to the product team, after which we got the response that it was by design.

@roldengarm @AJIXuMuK I can also confirm we see this issue with packages deployed days or weeks ago.

Let's wait while the change is propagated.
If you see the issue in two weeks from now - let me know.

I understand this issue is with the field customizer, but could it be related to the Application extension's partial page issue discussed here, as well as a several other places: https://github.com/SharePoint/sp-dev-docs/issues/1971 "OnInit is called when the extension is loaded (onDispose when it is unloaded). If you have the same extension on multiple site collections / lists / etc. then the design is that onInit is not called when you do a partial navigate between them. This keeps them working fast." How do we assure stability/consistency if these are only fired some of the time -- especially since each library may need some special look or behavior, ,i.e. ribbon/menu controls, etc.? What can we do to provide a more consistent experience/display?

@roldengarm @Scottlis26 I have just discovered that the issue (at least for us) is that the field we have a customizer for was not in the default view of the list, just in other views. Adding it to the default view makes it load and work consistently in the other views.
@AJIXuMuK interested to know if this makes sense and is it a bug to fix?

@anthonywhite I think I discovered that as well, and it seemed to help, but then the problem came back.
I'll give it another try though, thanks.
We got a response again on our support ticket that a fix is underway without an ETA.

@anthonywhite - you are referencing another issue #8571.
For the default/non default view - we are rolling out the fix. It should be on 100% prod next week.
However, the issue described here is different. In the scenario with non-default view the field customizer is just not loaded.
But here the manifest of the customizer is not found.

We are also experiencing this issue with field customizers built with version 1.4.1 since a few weeks back.
It occurs in 2 of 3 tenants with the same package deployed.
It does not help to include the field in the default view.
The following js error also pops up in the console when the issue occurs - plt.odsp-common.js:
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'length')
    at e.collectSPClientFlights (plt.odsp-common.js:1:165108)
    at t._logWindowVariables (splistwebpack.js:2:208734)
    at splistwebpack.js:2:203159

Hi @AJIXuMuK,
I'm having the exact same issue.
The error 'Fail to load customizer for column: MyTestColumn, error: Manifest not found for componentId [guid]'
I'm getting the same errors in the console as @joliq
I've tested this with version 1.16.1 and 1.17.4
The field customizers used to load correctly and now only show after a CTRL+F5 unfortunately.
Is there any update regarding a fix for this?
Many thanks,
Remco

Hi all,
I am getting the same error with version 1.16.1
The same package is installed on several site app catalogs and working. The latest one installed is not working.
Of course, I doublechecked the componentId, urls, field- and library names.
I can see following errors right before: Fail to load customizer for column:... Manifest not found for componentId...
error loading spfx preloaded data with spfxPageContext
error parsing pageContextJson for manifests
from plt.items-view.js
Uncaught (in promise) SyntaxError: Unexpected token 'J', "JSON.parse"... is not valid JSON
at JSON.parse ()
at plt.items-view.js:1:885271
This is a big pain now, as we cannot roll out a new process.
Is there any update regarding a fix for this?
Many thanks, Ronny

Still the same issue here. Just got a response from support that they could reproduce the issue still as well and would reach out to the product team.
It's two weeks ago now @AJIXuMuK and still not fixed.

 I added the package to the site app catalog, but didn't added the app. This solved "Fail to load customizer for column:... Manifest not found for componentId..." for me.

Still the same issue here. Just got a response from support that they could reproduce the issue still as well and would reach out to the product team.
It's two weeks ago now @AJIXuMuK and still not fixed.

Still the same issue for us as well - now in all our 3 tenants.

@roldengarm - are you using custom CDN or deployment of assets to the app catalog?
If the latter - there is a known issue that was there for a while that repros when you have a default view without SPFx extensions and another view WITH extensions.
If you navigate from one to another - the extensions will not work.
But you should see errors like that in this case:
Refused to load the script '<URL>' because it violates the following Content Security Policy directive: "script-src 'self' <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> *.cdn.office.net *.fluidpreview.office.net <URL> <URL> <URL> <URL> <URL> <URL> <URL> 'unsafe-eval' 'nonce-'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

Hi @AJIXuMuK  we're using the app catalog, not a CDN.
We've investigated that default view issue in the past, and added the field with the extension to the default view, but that didn't solve the issue either.
So it doesn't look like the caching changes have fixed the issue?

@roldengarm - there are "types" different issues I'd say:

cache issue: when a new version of a package is installed it was not available for users for a while. It should have been fixed and the new version should be there in ~10 minutes.
custom CDN: the one that I described above
non default view without custom CDN: this should have been fixed last week
something else I'm not aware about.

If the support team can repro - it will come to us and we'll figure it out.
For now, without a repro, I can't tell what issue is there.

Yep, it's something else. The support team can reproduce and should have already contacted you / the product team. @AJIXuMuK

@roldengarm - are you using custom CDN or deployment of assets to the app catalog? If the latter - there is a known issue that was there for a while that repros when you have a default view without SPFx extensions and another view WITH extensions. If you navigate from one to another - the extensions will not work. But you should see errors like that in this case:
Refused to load the script '<URL>' because it violates the following Content Security Policy directive: "script-src 'self' <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> *.cdn.office.net *.fluidpreview.office.net <URL> <URL> <URL> <URL> <URL> <URL> <URL> 'unsafe-eval' 'nonce-'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

Hi @AJIXuMuK  it just happened to me again. I went to the site, then to one list with the custom field extension (worked fine), then to another list with the same field extension => empty.
I don't see the CSP error you describe. What I do see is that it tried to load a JS file from /ClientSideAssets//details-link-field-customizer_.js which does not exist. When I go to that folder, I see a JS file with another guid.
We did do a deployment yesterday; which is now about 16 hours ago. You mentioned it should be present within 10 minutes, which is acceptable. It's not acceptable what I'm seeing.
Hope this helps.

@roldengarm - is this infor provided in the support ticket?
The issue with caching is hard to repro and can be a cross-org effort to address.
For that reason I would like to have a support ticket with all the info provided in there.
Thanks for understanding.

I only have the issue in a new tab when I open the list using Quicklink or Quick Launch Bar. Do you have the same behaviour?

@KienbMi
We have the same behaviour. It does not work when when you first visit the site home page and then click a "standard" quicklaunch link that points to the default view.
I have noticed a workaround - it works if you add a list web part on the site start page.

@roldengarm - is this infor provided in the support ticket?
The issue with caching is hard to repro and can be a cross-org effort to address.
For that reason I would like to have a support ticket with all the info provided in there.
Thanks for understanding.

Yes, I have provided all information in the support ticket, see ticket number<PHONE_NUMBER>005503
The support person could reproduce the issue relatively easily. @AJIXuMuK

@roldengarm - I believe there is a misunderstanding. I don't know the details of the support ticket. But most probably the response was that it may happen due to caching when some Web Front Ends are not getting updated right away. And on some tenants it might take a while while the cache is updated. We have a fix rolling out to decrease the time for cache update. When it's propagated (I would give it a few weeks) all the cache should be up to date in 10 minutes. Meaning if you upload an SPFx app in 10 minutes it MUST be available (same for new versions of the app).
If in a few weeks you're still experiencing the issue - please mention me in this issue. I will not be closing it.

A month later and the issue still persists, multiple days after a deployment. Our ticket with Microsoft has been open for almost three months now. The support person has supplied additional logs & screenshots to the PG this week. Any ideas?  @AJIXuMuK

@roldengarm - unfortunately, I don't have any information on the support ticket.

Update on the initial topic.
There were some additional fixes needed that are still rolling out.
The issue should be fixed by end of the next week.

@AJIXuMuK  thanks for the update. We've also gotten word that it has been fixed, and that seems to have arrived to our tenant finally. It still is empty for about 10 minutes after deployment, which is not ideal, but much better than previously. I think this issue can be closed.

@roldengarm - thanks for the confirmation!
10 mins is our internal time for cache update.

Hello,
We are too facing an intermitted issue related to "Field Customizer". It does not load sometime. We need to refresh the page to make it work.

That seems like a different bug @pkrsingh86 . Please click the link after "visit" as it seems like an error in your code.

@roldengarm : Thanks for your response. It seems version compatibility issue. Ref link: https://github.com/SharePoint/sp-dev-docs/issues/9270


Update plugin.spring.xml

Added support for security logic to the Xmla connections (non Mondrian)

wrong file


Sometimes controller is null and has no property 'draw' which throws …

When using Chart.js with AngularJS, occasionally - what I believe is just changing scope causes an error to be thrown,
Chart.js:4192 Uncaught TypeError: Cannot read property 'draw' of null
    at Chart.Controller.<anonymous> (Chart.js:4192)
    at Object.helpers.each (Chart.js:4808)
    at Chart.Controller.draw (Chart.js:4189)
    at ChartElement.animation.render (Chart.js:4154)
    at Object.startDigest (Chart.js:3694)
    at Chart.js:3667
(anonymous) @ Chart.js:4192
helpers.each @ Chart.js:4808
draw @ Chart.js:4189
animation.render @ Chart.js:4154
startDigest @ Chart.js:3694
(anonymous) @ Chart.js:3667
2017-01-13 18:04:48.577 ```

This simple check stops those errors from being thrown.

Worth noting I am using Chart.js directly and not an off-the-shelf Chart.js and Angular bundle.

I will see if I can make one, works finished and it's 7pm here so won't be
till next week unfortunately!
On Fri, 13 Jan 2017 at 18:54, Simon Brunel<EMAIL_ADDRESS>wrote:

@simonbrunel commented on this pull request.

In src/core/core.controller.js
https://github.com/chartjs/Chart.js/pull/3793:

@@ -457,7 +457,7 @@ module.exports = function(Chart) {

  	// Draw each dataset via its respective controller (reversed to support proper line stacking)

  	helpers.each(me.data.datasets, function(dataset, datasetIndex) {

		if (me.isDatasetVisible(datasetIndex)) {

		if (me.isDatasetVisible(datasetIndex) && me.isDatasetVisible(datasetIndex).hasOwnProperty('controller')) {

The data implicit synchronization only alters the meta-data (
getDatasetMeta(datasetIndex)().data array), not the dataset meta object,
so controller should not be null here. Anyway, a proper fix need to be
done on the issue origin, else we will have this workaround at many places
in the code (need a test case).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chartjs/Chart.js/pull/3793, or mute the thread
https://github.com/notifications/unsubscribe-auth/AECveEBrHNc7r1D-pss-vCMamde8eZa2ks5rR8hTgaJpZM4LjJ2r
.

Closing as out of date


how to judge if this field has an explicit "optional" label in pb2

how to judge if this field has an explicit "optional" label in pb2, I use code bollow, but it seemed doesn't work
if field.AsFieldDescriptorProto().Label != nil && field.GetLabel() == descriptor.FieldDescriptorProto_LABEL_OPTIONAL {
RawOptional = true
}

What type is field? What doesn't work? There is no type with an AsFieldDescriptorProto method in this module. Perhaps you're using some other implementation?
In google.golang.org/protobuf/reflect/protoreflect, the FieldDescriptor.HasOptionalKeyword method reports whether the optional keyword was explicitly specified for a field.


Using the class_name of a subclass results in spurious 'nonexistent function' errors at runtime

Godot version
4.2-dev4
System information
Godot v4.2.dev4 - Arch Linux #1 SMP PREEMPT_DYNAMIC Sat, 10 Jun 2023 00:35:35 +0000 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 970 (nvidia; 530.41.03) - AMD Ryzen 5 2600 Six-Core Processor (12 Threads)
Issue description
I tried updating a project from Godot 4.1 to 4.2 using the dev snapshot and encountered this issue.
One of my editor plugins has a class called 'Table', that both preloads and uses the class_name of one of its subclasses (let's call it DerivedTable). This seems to trigger a bug in 4.2 that wasn't present in 4.1. At runtime, the engine reports an error that a static function doesn't exist, when it clearly does.
From the attached reproducer:
table.gd:
extends Resource
class_name Table

static func from_directory(path: String, extension := "tres"):
	return preload("derived_table.gd").some_method()

static func from_array(array: Array):
	var table := DerivedTable.new()
	table.set_data(array)
	return table

derived_table.gd:
extends Table
class_name DerivedTable

static func some_method():
	pass

Then when you call Table.from_directory(""), the engine reports:
SCRIPT ERROR: Invalid call. Nonexistent function 'from_directory' in base 'GDScript'.

Steps to reproduce

Run the attached reproduction project.

Minimal reproduction project
Reproducer

[7d29ac0bf271cf1c730465bbd76c05ecf8e1c6a0] GDScript: solve _populate_class_members() cyclic dependency problem
Regression from #79205. CC @anvilfolk

Thank you for the heads up, @dalexeev, and @tcoxon MRP! Will take a look when I have some time!
Now that cyclic dependency bugs in compilation steps are fixed, it seems like a lot of things were relying on the previous solution :)


wrong architecture detected

I'm on IOS 16.6.1, running an A13 bionic chip which is arm64, however the app detects that I'm on arm64e which is A11 and lower

A13 is not arm64

A13 is not arm64

it is


common 24v pin?

Hi,
I read about a 24V common PIN - do you know if I can catch 24V to power a LED?
Thx

The heater and fans all share a common power line -- I believe -- on pins 21-24 of the 24-pin connector. (I'm trusting that this thing is designed by a sane human being and they share power and switch on ground, I don't actually own one to check it anymore.) You should be able to solder to any of those four pads to get 24V if you need it, and the common ground pins are 1 and 2 way over on the other side. It would be a relatively trivial add to throw either another two-pin connector on the board for auxiliary power, or a couple of test points to solder to, but I can't remember offhand where it would be safe to put those for mechanical clearance.


nixos: fix release notes about linux_latest version

Motivation for this change
It's version 5.13, not 5.12.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

It currently is not officially supported for use with the zfs filesystem

is that still the case?

Having linux_latest version in release notes seems kind of pointless to me, as it follows the latest version from upstream.  Originally it was 5.11 (when 21.05 was forked off).

the item might be just there for the zfs note?
i agree it does not make a lot of sense

Yes, that part is useful.  The ZFS problem still exists; it's typical for nontrivial out-of-tree drivers.  (e.g. nvidia, too)

does the issue still exist for 5.12 as well? maybe that should be documented as well

I think generally the support always arrives at some point, but it would be too late so it's not worth delaying linux_latest because of that.


spe2any in submodel output

supported in https://github.com/kfuku52/csubst/commit/38af41dea3ee509a1d668b6ced31a64a52df8edb


Document dodge keyword argument to boxplot, etc

It would be nice to add some documentation on the dodge keyword argument to the docstrings for boxplot, barplot, violin, etc.

Maybe also document the dodge_gap keyword argument?


Invalid handling of trailing dots in DnsNameResolver

@jonas-ren:
Found another related issue. If the domain name in DNS question has trailing dot, the resolver would also complain "Received a mismatching DNS response", because the question section in received DNS response doesn't have trailing dot.

For a possible fix see:
https://github.com/netty/netty/pull/4979#issuecomment-196975935

Working on a fix...

Fixed

Thanks for fixing this!


Remove kubelet extra args when kubelet configuration is set

Issue #, if available:
Description of changes:
This PR sets the kubelet configuration with providerID (Cloudstack) and cloud-provider (vSphere, Nutanix) setting which will be blocked for users to set. This setting is set by EKSA for kubelet extra args if Kubelet Configuration is not used.
Testing (if applicable):

unit test
E2E test

Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test eks-anywhere-presubmit


Issue/5041 fix documentation build issues (#5239)

Pull request opened by the merge tool on behalf of #5239

Merged in 8ac772b39855a49b8b7d0066d01d07c5fce85e29


Added NewConnWithUser to allow users other than the default

We have a need to use usernames that are not the default client.admin.  This new NewConnWithUser is the same as NewConn except it adds the ability to pass in a username, without the client. prefix.
The user of this new function doesn't store their keyring at /etc/ceph/ceph.client.$USER.keyring, they would find value in setting their keyring (or key or keyfile) in their ceph config file or setting conn.SetConfigOption("keyring", "/path/to/my/keyring") (or the key or keyfile equivalent).

BTW, I didn't write a test for this new function.  I'm not sure how to go about testing this without a means to mock the call over to C.  Please let me know if this test would be required and ideas on how to get there.  It does pass my local non-automated test, but that's probably little comfort.

@dustywilson this looks good. would it be possible to make a simple test for the success case? you could just pass in the admin user to NewConnWithUser() which is what the tests currently assume.

I've added the new test.  Much of the test suite seems to fail, but the test I added passes, so I hope that means we're good for this PR.

@dustywilson Thanks, merged! Note that the test suite should be passing. are you running it against a running cluster (or single node vstart cluster)? the travis-ci runs the tests against a temporary ceph installation. I can see your test and all the others passing here: https://travis-ci.org/noahdesu/go-ceph/builds/51756632

It's going against a running test cluster in three VMs.  I'll explore that and if it seems to be something that is a fault in the tests, I'll see if I can remedy.  I'll do that in a separate issue, if it's not simply a fault on my end.  Thanks!

Thanks, please report anything you find. I haven't seen issues, so it might be a quirk in our different environments.


Failed to build docker image for Defects4J benchmark

Hi @Marti2203 , I am trying to run an example to understand the flow of Cerberus. Here’s what I have done so far, step by step:

Activated the source environment source activate
Installed the required packages pip install -r requirements.txt in my environment.
Ran the command: cerberus -task repair --tool=arja --benchmark=defects4j --bug-index=1.
3.1. First, I received the following error message: "Could not get the submodule. Maybe the system asked for an SSH key, and it could not be provided." Instead of fixing this by adding an SSH key to GitHub, I traced the issue in the log file and ran git submodule update --init benchmark/defects4j manually, which resolved the error.
3.2. Then, I encountered another error: "[error] Image was not built successfully. Please check whether the file builds outside of Cerberus." I am unsure why Cerberus cannot build the benchmark image. Here's the log output:[framework] loading benchmark defects4j Sep 27 22:54:49
[framework] benchmark environment not found for defects4j-benchmark Sep 27 22:54:49
[framework] building benchmark environment Sep 27 22:54:49
[framework] building docker image defects4j-benchmark Sep 27 22:54:49
Task repair failed Sep 27 22:55:38
[error] Image was not built successfully. Please check whether the file builds outside of Cerberus Sep 27 22:55:38
Error. Exiting... Sep 27 22:55:38
Task repair failed Sep 27 22:55:38
[error] unable to build image: unhandled exception Sep 27 22:55:38
Runtime Error Sep 27 22:55:38
Error. Exiting... Sep 27 22:55:38

Then I printed process of building image by adding a line of code "print(line["stream"])" at line 124 in container.py. I found an error here:
Get:129 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 software-properties-common all <IP_ADDRESS> [10.4 kB]
Get:130 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 unattended-upgrades all 2.3ubuntu0.3 [48.5 kB]
debconf: delaying package configuration, since apt-utils is not installed

Fetched 35.9 MB in 15s (2451 kB/s)
(Reading database ...
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 4124 files and directories currently installed.)

Preparing to unpack .../libsystemd0_245.4-4ubuntu3.24_amd64.deb ...
Unpacking libsystemd0:amd64 (245.4-4ubuntu3.24) over (245.4-4ubuntu3.23) ...
Setting up libsystemd0:amd64 (245.4-4ubuntu3.24) ...
Selecting previously unselected package libssl1.1:amd64.
(Reading database ...
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 4124 files and directories currently installed.)
Preparing to unpack .../libssl1.1_1.1.1f-1ubuntu2.23_amd64.deb ...
Unpacking libssl1.1:amd64 (1.1.1f-1ubuntu2.23) ...
Selecting previously unselected package libpython3.8-minimal:amd64.
Preparing to unpack .../libpython3.8-minimal_3.8.10-0ubuntu1~20.04.12_amd64.deb ...
Unpacking libpython3.8-minimal:amd64 (3.8.10-0ubuntu1~20.04.12) ...
Selecting previously unselected package libexpat1:amd64.
Preparing to unpack .../libexpat1_2.2.9-1ubuntu0.7_amd64.deb ...
Unpacking libexpat1:amd64 (2.2.9-1ubuntu0.7) ...
Selecting previously unselected package python3.8-minimal.
Preparing to unpack .../python3.8-minimal_3.8.10-0ubuntu1~20.04.12_amd64.deb ...
Unpacking python3.8-minimal (3.8.10-0ubuntu1~20.04.12) ...
Setting up libssl1.1:amd64 (1.1.1f-1ubuntu2.23) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype
Setting up libpython3.8-minimal:amd64 (3.8.10-0ubuntu1~20.04.12) ...
Setting up libexpat1:amd64 (2.2.9-1ubuntu0.7) ...
Setting up python3.8-minimal (3.8.10-0ubuntu1~20.04.12) ...
dpkg: error processing package python3.8-minimal (--configure):
 installed python3.8-minimal package post-installation script subprocess was killed by signal (Killed)
Errors were encountered while processing:
 python3.8-minimal
E: Sub-process /usr/bin/dpkg returned an error code (1)

Could you help me figure out how to resolve this issue?
Originally posted by @brojackvn in https://github.com/nus-apr/cerberus/issues/156#issuecomment-2379304556

Hi @brojackvn, I saw the issue. In the last version we have started using groups to allow sharing of files between container and tool. I will push a fix tomorrow for this. Apologies

Should be fixed now on master

Thank you so much for your support.
I have encountered another error. Could you help me resolve it? I think there is still a bug in using the group

Yes, I thought that group 100 was not defined... can you change the value in task/image.py to 999 and I will push a fix.

Yeah. That's right. But when I changed it, I ran the command again cerberus -task repair --tool=arja --benchmark=defects4j --bug-index=1, and it automatically changed that Dockerfile.

Oh nono, I meant modifying the cerberus source code. The Dockerfile is automatically rebuilt

Thank you, it worked.

[ERROR][genprog]: 'binary_path' Oct 02 00:30:56
[ERROR][genprog]: Traceback (most recent call last):
File '.........../cerberus/app/core/task/task.py', line 268, in execute_setup
tool.invoke_advanced(
File '.........../cerberus/app/drivers/tools/repair/AbstractRepairTool.py', line 65, in invoke_advanced
super().invoke_advanced(
File '/home/student.unimelb.edu.au/anhh1/working-space/APR/research-paper-repo/cerberus/app/drivers/tools/AbstractTool.py', line 208, in invoke_advanced
self.invoke(bug_info, task_config_info)
File '.........../cerberus/app/drivers/tools/repair/c/GenProg.py', line 49, in invoke
join(self.dir_expr, 'src', bug_info[self.key_bin_path])
KeyError: 'binary_path' Oct 02 00:30:56
I encountered this error. It might be due to a timeout when running the repair tool?

[ERROR][genprog]: 'binary_path' Oct 02 00:30:56
[ERROR][genprog]: Traceback (most recent call last):
File '/cerberus/app/core/task/task.py', line 268, in execute_setup
tool.invoke_advanced(
File '/cerberus/app/drivers/tools/repair/AbstractRepairTool.py', line 65, in invoke_advanced
super().invoke_advanced(
File '/cerberus/app/drivers/tools/AbstractTool.py', line 208, in invoke_advanced
self.invoke(bug_info, task_config_info)
File '/cerberus/app/drivers/tools/repair/c/GenProg.py', line 49, in invoke
join(self.dir_expr, 'src', bug_info[self.key_bin_path])
KeyError: 'binary_path' Oct 02 00:30:56
I encountered this error. It might be due to a timeout when running the repair tool?

I also encountered this error when running Cardumen tool on Chart-1 of Defects4J

reported by test-runner. Test [Manual]TestMethod=org.jfree.data.xy.junit.TableXYDatasetTests#testEquals result was not reported by test-runner. Test [Manual]TestMethod=org.jfree.chart.axis.junit.LogarithmicAxisTests#testAdjustedLog10 result was not reported by test-runner. Tests found: 751 Tests executed: 719 Failing test cases was not passed as argument: we use the results from running them[] Executing time Fault localization: 65 sec Setting up the max to 655740 milliseconds (655 sec) Exception in thread "main" java.lang.IllegalStateException: No suspicious line detected by the fault localization 	at fr.inria.main.evolution.AstorMain.createEngine(AstorMain.java:105) 	at fr.inria.main.evolution.AstorMain.run(AstorMain.java:160) 	at fr.inria.main.evolution.AstorMain.execute(AstorMain.java:222) 	at fr.inria.main.evolution.AstorMain.main(AstorMain.java:193)
This is a log of the above errors, which shows that spectrum FL cannot detect the buggy line. I wonder if I need to add any configurations for this repair tool or how to use perfect FL for this tool. (I see on Defects4J that this bug can be fixed by this tool)

I found the error, which was caused by an incorrect configuration when using the Astor tool. I fixed it, and now it works

Hi @Marti2203 , I am trying to run an example to understand the flow of Cerberus. Here’s what I have done so far, step by step:

Activated the source environment source activate
Installed the required packages pip install -r requirements.txt in my environment.
Ran the command: cerberus -task repair --tool=arja --benchmark=defects4j --bug-index=1.
3.1. First, I received the following error message: "Could not get the submodule. Maybe the system asked for an SSH key, and it could not be provided." Instead of fixing this by adding an SSH key to GitHub, I traced the issue in the log file and ran git submodule update --init benchmark/defects4j manually, which resolved the error.
3.2. Then, I encountered another error: "[error] Image was not built successfully. Please check whether the file builds outside of Cerberus." I am unsure why Cerberus cannot build the benchmark image. Here's the log output:[framework] loading benchmark defects4j Sep 27 22:54:49
[framework] benchmark environment not found for defects4j-benchmark Sep 27 22:54:49
[framework] building benchmark environment Sep 27 22:54:49
[framework] building docker image defects4j-benchmark Sep 27 22:54:49
Task repair failed Sep 27 22:55:38
[error] Image was not built successfully. Please check whether the file builds outside of Cerberus Sep 27 22:55:38
Error. Exiting... Sep 27 22:55:38
Task repair failed Sep 27 22:55:38
[error] unable to build image: unhandled exception Sep 27 22:55:38
Runtime Error Sep 27 22:55:38
Error. Exiting... Sep 27 22:55:38

Then I printed process of building image by adding a line of code "print(line["stream"])" at line 124 in container.py. I found an error here:
Get:129 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 software-properties-common all <IP_ADDRESS> [10.4 kB]
Get:130 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 unattended-upgrades all 2.3ubuntu0.3 [48.5 kB]
debconf: delaying package configuration, since apt-utils is not installed

Fetched 35.9 MB in 15s (2451 kB/s)
(Reading database ...
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 4124 files and directories currently installed.)

Preparing to unpack .../libsystemd0_245.4-4ubuntu3.24_amd64.deb ...
Unpacking libsystemd0:amd64 (245.4-4ubuntu3.24) over (245.4-4ubuntu3.23) ...
Setting up libsystemd0:amd64 (245.4-4ubuntu3.24) ...
Selecting previously unselected package libssl1.1:amd64.
(Reading database ...
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 4124 files and directories currently installed.)
Preparing to unpack .../libssl1.1_1.1.1f-1ubuntu2.23_amd64.deb ...
Unpacking libssl1.1:amd64 (1.1.1f-1ubuntu2.23) ...
Selecting previously unselected package libpython3.8-minimal:amd64.
Preparing to unpack .../libpython3.8-minimal_3.8.10-0ubuntu1~20.04.12_amd64.deb ...
Unpacking libpython3.8-minimal:amd64 (3.8.10-0ubuntu1~20.04.12) ...
Selecting previously unselected package libexpat1:amd64.
Preparing to unpack .../libexpat1_2.2.9-1ubuntu0.7_amd64.deb ...
Unpacking libexpat1:amd64 (2.2.9-1ubuntu0.7) ...
Selecting previously unselected package python3.8-minimal.
Preparing to unpack .../python3.8-minimal_3.8.10-0ubuntu1~20.04.12_amd64.deb ...
Unpacking python3.8-minimal (3.8.10-0ubuntu1~20.04.12) ...
Setting up libssl1.1:amd64 (1.1.1f-1ubuntu2.23) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype
Setting up libpython3.8-minimal:amd64 (3.8.10-0ubuntu1~20.04.12) ...
Setting up libexpat1:amd64 (2.2.9-1ubuntu0.7) ...
Setting up python3.8-minimal (3.8.10-0ubuntu1~20.04.12) ...
dpkg: error processing package python3.8-minimal (--configure):
 installed python3.8-minimal package post-installation script subprocess was killed by signal (Killed)
Errors were encountered while processing:
 python3.8-minimal
E: Sub-process /usr/bin/dpkg returned an error code (1)

Could you help me figure out how to resolve this issue?
Originally posted by @brojackvn in #156 (comment)

However, this error occurs when I run certain bugs in Defects4J


PS-2111 table files

so, @odinuv this is passing now.  what do you think of the metadata change?

i think it's ok provided that the branch id on files is not used anywhere, but i'm not aware of that

yeah, it's definitely not because until now the file metadata was only under the feature anyhow.


Update CONTRIBUTING.md

Coming from this slack discussion. I made a small update to the instructions on how to propose a job (e.g. discover a bug).

Details
Removed the part about "including a solution proposal" in slack reports, when a bug is posted.

Merging since it's only a text change to the contributing guidelines.

Removed the Emergency label since it's only a text change to a .md file.

: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 @marcochavezf in version: 1.2.52-0 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @Julesssss in version: 1.2.52-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Block Deletion of Terms when Term Grades Exist

Note: FOR INTERNAL USE ONLY. For support questions, please use the EDA Chatter group in The Power of Us Hub.
For feature requests, please use the Ideas tab in The Power of Us Hub.

Do you want to request a feature or report a bug?
Feature

What is the current behavior?
Terms can be deleted even if there are Term Grade records associated with that Term.

What is the expected behavior?
Terms should not be able to be deleted if Term Grade records exist.

What is the motivation / use case for changing the behavior?
Data integrity

**lurch: add

Tracking W-035719

Closed by #1025


Firebase channels instead of google channel api

Related rogerthat-platform/rogerthat-backend#49.
Should be merged first rogerthat-platform/rogerthat-backend#180
Don't know what to do with src-frontend for now.

update dev-server.sh to do export GOOGLE_APPLICATION_CREDENTIALS=${DIR}/google-app-credentials.json  if ${DIR}/google-app-credentials.json exists.

add this file to gitignore

update the oca-setup (private repo on gitlab) code to add the firebase related server settings
add the google-app-credentials.json file to the oca-setup repo, and add instructions in the README file

I'd say we remove src-frontend and everything related to it as it's probably not used anymore anyway.
We could always make a plugin on rogerthat control center which does the same thing if we need it.


KeyError

https://www.imdb.com/title/tt0655437/
KeyError: 'Title' (file "/home/sopel/.local/lib/python3.7/site-packages/sopel_modules/imdb/imdb.py", line 103, in run_omdb_query)

Fixed in https://github.com/RustyBower/sopel-imdb/commit/92f5774fc9cc86d2e6e461a8496acb7fdfe47bc5


Creating middle layer stl file for the opposite hand

Hi thanks for the awesome keyboard :) I'm totally in love with it.
I have 1 question about the middle layer file.
Looks like the issue creator in #18 managed to create the opposite hand's file.
But I'm a noob so would be awesome if someone can point out how to create the opposite hand's stl file for this one: https://github.com/keebio/iris-case/blob/master/rev3-only/Iris R3 Middle Layer - Normal for 1.5mm Plate.stl
Thanks.

was able to do this using autodesk netfabb 🎉
https://www.youtube.com/watch?v=mU_oB31Y_tg


Text doesn't appear in text boxes in mod settings

Geode Issue

[X] I confirm that this bug is NOT related to a mod but directly to Geode Loader itself.

Platform
Windows
SDK commit
No response
Geode Version
v2.0.0-beta.10
Mods Installed
No response
Expected Behavior

A number appears in the text box (integer)
Actual Behavior

Text is invisible in the textbox after updating
Steps to Reproduce

Look at the settings of a mod that has a textbox
No text appears in the textbox.

Additional Information
No response

fixed in beta.11


Centralize web app name

Description

centralized the web app name
changed top level pages to reflect correct name
changed start script name to be more generic to shield against future name changes

Testing

Reviewers
@jojoboateng @markowusu @KristenAP

Good approach to make the app name centralised. We can create a task to remove that from the utilities file and have a separate folder and json file for anything that has to do with text. Reducing the hard coding of text in the application. This is a step in the right direction but we must apply it to every aspect of the application too as well.

@markowusu yes. I had a task at some point to do that but skipped my mind for a while. Let's plan to tackle that as well once we resume


Page allocation in MessageQueue

Fixes #35653

I have pending to work on this on the 4.x branch in the next days, but I want to use a bit of a different approach. I suggest we wait some days and then discuss the PR again

@staddy Is this still desired? If so, this needs to be rebased on the latest master branch.
The core internals of the engine have changed a lot for 4.0, so it's possible this PR isn't relevant anymore.

In the end, I think it should be easier to just resize the buffer, given no pointers are kept to it either way.

Superseded by #62303, thanks for the contribution nevertheless!


Update sbt-avrohugger to 2.5.3

About this PR
📦 Updates com.julianpeeters:sbt-avrohugger from 2.5.2 to 2.5.3
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (2.5.2).
You might want to review and update them manually.
project/plugins.sbt

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.julianpeeters", artifactId = "sbt-avrohugger" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.julianpeeters", artifactId = "sbt-avrohugger" }
}]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, version-scheme:semver-spec, old-version-remains, commit-count:1

Superseded by #786.