Litmus Chaos 3.1.0 cleanup-chaos-resources does not work well

What happened:
cleanup-chaos-resources does not work well, some pods still exist after experiment completed successfully
What you expected to happen:
all related chaos resources can be cleaned up after experiment is completed.
Where can this issue be corrected? (optional)
How to reproduce it (as minimally and precisely as possible):
Chaos Experiments --> New Experiment --> Templates from ChaosHubs --> Podtoto-head Chaos
run the experiments

but some resources are still here.
kubectl get pod -n litmus | grep test
test-1702639060018-2219617156               0/2     Completed   0             29m
test-1702639060018-2512681660               0/2     Completed   0             30m
test-1702639060018-2653935615               0/2     Completed   0             27m
test-1702639060018-3378946198               0/2     Completed   0             27m
test-1702639060018-3661524617               0/2     Completed   0             31m

Anything else we need to know?:

i launched this experiment from chao center directly, not use any manifest.
Chaos Experiments --> New Experiment --> Templates from ChaosHubs --> Podtoto-head Chaos

podtoto.txt
this is manifest file download from chaos center.

@amityt can you please check?

@neelanjan00 is it resolved?


openmw aborts when running wizard or launcher binaries

Describe the bug
It seems the package openmw (morrowind game engine) is missing dependencies, maybe Qt related.
openmw-wizard
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Aborted (core dumped)

To Reproduce
Install openmw and run openmw-wizard or openmw-launcher, you don't need Morrowind asset files to run them.
Expected behavior
A window is opened.
Notify maintainers

@abbradar

Metadata

system: "x86_64-linux"
host os: Linux 5.10.37, NixOS, 21.05pre289339.83d907fd760 (Okapi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.11
channels(root): "nixos-21.05pre289339.83d907fd760"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

I've had the same problem, but it seems that installing qt5.full fix this problem.
Sorry for my english, I hope this helps anyway.


Difficulty with debugging

I have the following error.
I am not able to determine what the source of error is
INFO:beancount_black.main:Processing file ledger.bean
Traceback (most recent call last):
  File "/home/user/.local/bin/bean-black", line 8, in <module>
    sys.exit(main())
  File "/home/user/.local/lib/python3.9/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/home/user/.local/lib/python3.9/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/home/user/.local/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/user/.local/lib/python3.9/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/user/.local/lib/python3.9/site-packages/beancount_black/main.py", line 49, in main
    formatter.format(tree, output_file)
  File "/home/user/.local/lib/python3.9/site-packages/beancount_black/formatter.py", line 558, in format
    self.calculate_column_widths(tree)
  File "/home/user/.local/lib/python3.9/site-packages/beancount_black/formatter.py", line 550, in calculate_column_widths
    width = len(self.format_number(amount.children[0]))
  File "/home/user/.local/lib/python3.9/site-packages/beancount_black/formatter.py", line 210, in format_number
    value = token.value.replace(",", "")
AttributeError: 'Tree' object has no attribute 'value'

I have the same error with a valid bean-check verified file as well.

Hi there, thanks for reporting this issue. I am currently overwhelmed by other stuff, will look into this later when I have more spare time

@alexhallam @kaiwei sorry for long waiting, now the new logging level option has been added
https://github.com/LaunchPlatform/beancount-black#debug
that should make it much easier to debug if there's anything stop the formatter from formatting

the AttributeError: 'Tree' object has no attribute 'value' from format_number bug has been fixed in the latest version as well, by the way


Memory

Thank you for sharing this model. But when I use Xcode to debug this Example, there will be a memory issue. Can you can help me？

I have the same issue for devices like iPhone 6s and etc. But on iPad Pro there is no this crash (out of memory). I guess it's related to model.

I have the same issue for devices like iPhone 6s and etc. But on iPad Pro there is no this crash (out of memory). I guess it's related to model.
upd. As I see, the issue is related to internal part of CoreML:

upd2: I've researched this crash and found the place of out of memory:
PyramidROIAlignLayer.swift L.116 after comment

//This is the main bottleneck. Is there a more efficient approach?

Did you ever figure out a workaround to the memory issue? Also, what iPad model and iOS version were you able to make it work on? I'm currently struggling to get the debugger working even on my First Gen iPad Pro running iOS 12.1.1.

@deandiakov right now i'm trying to find a workaround for this issue.
I use several devices and only on iPad Pro (ML0G2CL/A) with iOS 12.1 (16B92) there is no this memory issue.

@deandiakov
Unfortunately, I could not find a fix for this crash


How to install for Android and iOS?

How to install this library to work on Android and iOS in delphi 10.2?

delphi 10.2 is not anymore supported ... you must upgrade to delphi 10.3 (anyway with delphi 10.2 you are  not anymore able to upload any new app to google play)


Recipe to remove dead repositories like  maven.glassfish.org

As noted in this comment https://github.com/jenkinsci/core-annotation-processors/pull/3#issuecomment-1179304090 maven.glassfish.org no longer responds. Instead of upgrading it to HTTPS we should just remove it completely.

It would be simple enough to create a recipe that will remove a repository and use recipe configuration to support glob expressions in the URL...and possible also allow a repo to be removed by ID.


NetBSD fixes

This is a collection of the patches from pkgsrc to make libuv work better on NetBSD.

Part of these patches are for NetBSD 6.x, do we still want to clobber 3rd party with EOL version of NetBSD?

I've removed the NetBSD-6 specific patch.

I was waiting for comments on how to proceed with the exepath code.

https://github.com/libuv/libuv/pull/2507

I would drop patches for netbsd-7 here too.. 9.0 is planned to be releases soon and -7 will fade away officially.

Sorry that took so long to reply. This seems good overall, but needs a rebase now due to merge conflicts. Then happy to land for you once the code-duplication comment is addressed.

Sorry, I lost interest in this, and it doesn't improve the 'make test' situation. I'll file a report about the broken tests.


Attribute assignment improvements

converts floats to integers when possible in tagged attributes
added history attribute
concatenate cell_methods from indicator with source data cell_method

Fixes #114, #80

Pull Request Test Coverage Report for Build 314

33 of 34 (97.06%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.5%) to 84.38%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

xclim/utils.py
33
34
97.06%

Totals

Change from base Build 313:
0.5%

Covered Lines:
578

Relevant Lines:
685

💛  - Coveralls

I think that timestamp test might be prone to fail since it really depends on the processing speed of the Travis CI instance. Is there a way of increasing the range of acceptable times? Maybe with a datetime.now(), datetime.now()+1s, datetime.now()+2s...
assert "[2018-11-22 01:37:13] tmin0(da, thresh=0.0, freq='YS')" in
   ("[2018-11-22 01:37:12] tmin0(da, thresh=0.0, freq='YS')", "[2018-11-22 01:37:13] tmin0(da, thresh=0.0, freq='YS')", "[2018-11-22 01:37:14] tmin0(da, thresh=0.0, freq='YS')")


update architecture for compose library

fixed https://slack-pde.slack.com/archives/C058XKY4DRV/p1710438490115959

hmm, is there a way we can make a universal binary? The focus plugin seems to accomplish this by just adding all the targets: https://github.com/DevSrSouza/dropbox-focus-intellij-plugin/blob/main/build.gradle.kts#L38-L43


Policies may need to be checked to deal with actions running on each scheduled policy run

Policy Template Name
Seeing the untagged resources policy is sending an email every time it runs.
Should check the other policies too to make sure they handle the fact that actions run each time now.
Issue Type
[Bug -or- Feature Request -or- New Policy Template Request]
Use Case (Feature Request -or- New Policy Template Request Only)
[Describe the use case for this feature request or new policy template request]
Policy Template version (Bug Only)
[Version of Policy Template in use, this can be found in the long_description]
Code Snippet (Bug Only)
[Please provide any relevant code snippets (ie. datasource,escalation,policy, RCL, etc.) as it relates to the bug]
Error Messages (Bug Only)
[Provide any error messages returned (if applicable)]

Non-issue.
It turns out policies are acting as expected.


Add authn protocol

This PR proposes a fairly significant change to our authn story. Instead of running a separate protocol, we would just add a Token type, carrying pretty much the same payload as authn.Request does, to the message/v1 protocol. The Token  would need to be attached to every request and validated by the nodes (again same type of validation as authn did), so the validation would happen on every request instead of on every run of the authn protocol (although significant chunk of this could be cached since the token remains the same during its validity period).
The token can be carried as a standard HTTP/GRPC authorization header (The gateway maps these automatically https://github.com/grpc-ecosystem/grpc-gateway#mapping-grpc-to-http). The server side processing can be implemented with a GRPC interceptor.
Upsides:

no need to orchestrate the interaction of the the two protocols
the token is portable across nodes, so the client doesn't need to "reauthenticate" if it gets loadbalanced to a different node
implementation should be simpler

Downsides:

The token/signature validation happens on every request (we can cache some of that if needed)
We are losing the channel binding of the token that was mediated by the peer IDs, so the blast radius of a leaked token is necessarily larger (but comparable to JWT token style authorization)

@neekolas I'm not entirely sure what to do on the TS side. It doesn't seem like I should just add
export * from "./auth/v1/authn.pb"

to ts/index.ts. Wouldn't that yield a single package with everything mixed together?

Wouldn't that yield a single package with everything mixed together?

Ya, we should probably move to namespacing the exports. export * as authn from './auth/v1/authn.pb'

Although we don't have to export anything right now. All we are ultimately going to care about from Typescript is whatever GRPC Gateway API gets exposed. We shouldn't need any typescript for the actual protos.

Hrm, this will be a problem, whan I run npm run generate I get:
authn/v1/authn.proto: is a proto3 file that contains optional fields, but code generator protoc-gen-grpc-gateway-ts hasn't been updated to support optional fields in proto3. Please ask the owner of this code generator to support proto3 optional.--grpc-gateway-ts_out:

@mkobetic There is a hack listed in this issue, but it's not great. The suggestion is just to modify the generator and make it register itself as supporting optional fields when it doesn't. Given that we don't actually have optional fields (I'm not entirely sure why this is triggered, but I suspect it's because oneof fields with a single option are effectively the same as optional in proto3) that may be enough to make it generate valid code.
Open to better suggestions.

@mkobetic There is a hack listed in this issue, but it's not great. The suggestion is just to modify the generator and make it register itself as supporting optional fields when it doesn't. Given that we don't actually have optional fields (I'm not entirely sure why this is triggered, but I suspect it's because oneof fields with a single option are effectively the same as optional in proto3) that may be enough to make it generate valid code.
Open to better suggestions.

It's because of the optional Signature on the PublicKey. We can actually remove optional on it since we require the wallet signature anyway. That's also why I dropped the separate signature field from the message, we my as well use the field on the PublicKey struct (I understand that Jazz was trying to preserve the original definition, but I don't think we really need to in this case). So I just removed optional on that field and it's not complaining now.

OK, great. optional fields are kinda silly in protobuf since all fields are technically optional

@mkobetic OK, great.

@neekolas, the latest is how it would look if Authn was just a Token that is part of the message/v1 protocol. WDYT?

I updated the PR description to summarize where we are atm (including Jazz's objections). Let me know if something's off.
I'd like to go ahead with this so that I can move forward on the node side. I'd appreciate some ✅ if we are far enough here.

Great. This is going to be quite easy to integrate into my branch.

Sigh, as soon as I merged I realized that AuthData.timestamp should probably be AuthData.created_ns to fit the message/v1 theme. Worth fixing in a follow up?
I also note that there's also PublicKey.timestamp, but changing that would move us away from the xmtp-js stuff. Not quite sure that actually matters though.

And I think I tripped up with the semantic releaser thingy 🤦


DisplayConfig cannot execute via remote tool (Intune Win32app, SCCCM task scheduler, etc.)

Hi Martin,
I tested it works well after install the module on local laptop, but when I want to use it for bulk display config . There is nothing happen , the script just execute but the display resolution didn't change and apply.
May I know if there is any limitation?

It seems to be an API limitation, see this thread where another user has the same issue: https://stackoverflow.com/questions/36066380/getdisplayconfigbuffersizes-inside-local-windows-service
If I run it on my own system through task scheduler I can see that the path/mode array sizes are zero like he described. I don't check for that, so when I run QueryDisplayConfig with those parameters set to 0 it throws the invalid parameters error that my module currently output.
I may release an update in the future so it throws a better error message but I can't do anything to make it work in that scenario.

I see. thanks for your great help , let me try to find another way to achieve ...


Termination terminal UI not visible, keybinds not working on Atom 1.19

Description
After updating to the newly released Atom 1.19, the terminal UI added by this package is no longer visible. The toolbar under the editor is not there, and the keybindings and menu elements seem to do nothing. Could be related to #56.
Steps to Reproduce

Use/update to Atom 1.19
Have the package activated
Notice the lack of UI
Try using the keybindings
Notice how nothing happens

Expected behavior: Visible termination UI, keybinds and menu elements work
Actual behavior: UI not visible, keybinds and menu elements not working
Reproduces how often: Seems to reproduce all the time
Versions
Atom: 1.19.0
Electron: 1.6.9
Chrome: 56.0.2924.87
Node: 7.4.0
OS: macOS Sierra 10.12.6
Additional Information
Community Packages (30)
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

Hi, sorry about this. Hopefully it's fixed now with the 0.6.0 release. After updating, Atom may tell you to rebuild Termination due to incompatibilities... just click the red bug icon and follow the prompts.

Linux Mint 18.2 amd64
After the 0.6.0 release, all good.

Thanks. After updating and rebuilding, there seems to be no problems anymore. 👍🏼


Newline (\n) shown as icon in CPU and MEMORY modules.

On Arch Linux update 0.9.4 changed behavior for (at least) cpu and memory modules.
How it set up in config:
   "cpu": {
        "interval": 3,
        "format": "CPU\n{}%",
        "max-length": 10
    },
    "memory": {
        "interval": 3,
        "format": "RAM\n{}%",
        "max-length": 10
    }

Output for 0.9.3:

Output for 0.9.4:

As I use side position it's quite noticeable.
A pulseaudio and clock modules are giving correct output for a \n in both versions.

#828. Removing max-length from the module configuration should restore the old behavior.
Skipping set_single_line_mode for vertical bars could a good idea, but to achieve that modules need to be aware of the bar position.

Experiencing the same issue


[QUESTION] error uploading a file with a post request

Description
How do I upload a file with a post request?
I have done what is described here - https://fastapi.tiangolo.com/tutorial/request-files/ - so the following code is in my main.py file
from fastapi import FastAPI, Request, File, UploadFile

app = FastAPI

@app.post('/uploaddata/')
async def create_upload_file(file: UploadFile = File(...)):
    return {"filename": file.filename}

and on the client side i have a simple form like this:
  <form method="post" action="/uploaddata/" enctype="multipart/form-data">
            <button class="btn btn-outline-secondary" type="submit">upload</button>
            <input type="file" id="file_upload">
   </form>

I get the error: {"detail":"There was an error parsing the body"}, just like issue #201
https://github.com/tiangolo/fastapi/issues/201
In that case the problem seemed to be that python-multipart wasn't installed. I have installed it, but I still get the error.
Is there something obviously wrong? If not, how can I get hold of more information that just this reply:
{"detail":"There was an error parsing the body"}?
thanks!

Can you please format the code using markdown code blocks. Right now we cannot see your HTML because it is automatically removed by the formatter.

@retnikt sorry about that. I'm new to this. I just reformatted the code into blocks.
thanks for any help you might provide!

You are missing the name attribute on the HTML form, it must be the same as the parameter name (in your case file). So:
<form method="post" action="/uploaddata/" enctype="multipart/form-data">
    <button class="btn btn-outline-secondary" type="submit">upload</button>
    <input type="file" id="file_upload" name="file">
</form>

dammit that was easy. thanks @retnikt for the prompt and correct solution.
could i ask one more stupid question? is it the case that every post request uploading a file must have a name matching the serverside parameter, or is this specific to fastapi?
thanks again, this is super helpful.

This is a standard for all file uploads. See: https://tools.ietf.org/html/rfc7578 and https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file

thanks @retnikt

Thanks for the help here @retnikt ! :clap: :bow:
Thanks for reporting back and closing the issue @fdennig  :+1:

This question links to this issue.


Finally!  Something that gives me a clear example on how to use Power Automate to run a script that works

Thank you for this tutorial.  I will be able to take this example and use it in my real world examples.
I love step by step examples that actually work and reflect the applications I have.

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

ID: 4b951170-8016-6d95-be28-575a0e728c4b
Version Independent ID: 42b9d09a-9e39-f9ed-c278-d40982c8defc
Content: Call scripts from a manual Power Automate flow - Office Scripts
Content Source: docs/tutorials/excel-power-automate-manual.md
Product: excel
Technology: scripts
GitHub Login: @o365devx
Microsoft Alias: o365devx

Hi @bocikt,
I'm glad to hear this was helpful! If you ever need any other samples or documentation to help with your Office Scripts scenarios, please don't hesitate to ask. Good luck learning Scripts and automating your workflows!


Make all the error messages more useful

All the error messages since #63 have been somewhat cryptic. This will likely also require a PR to stylewarning/policy-cond to allow for custom assertion messages in with-expectations.

Waiting on stylewarning/policy-cond#1 to add messages to asserts


Country Request: Greenland

Can you please add Greenland to the new list? Thanks!

Hi Justin, we can look into it, but I feel it won't be very efficient -- the number of the roads is very small, while there could be a bunch of false positives (cracks in the ice shield, river beds, etc). Of course, you can still use RapiD for mapping Greenland -- similar to a common iD editor.

@danil-kirsanov I think you would know more about this than me. I believe based on your comments, we can close this out. I'll let you decide. Thanks for your help!  Justin


Add first cut of git-credential-fdoss

Add the initial version of git-credential-fdoss. It basically works
but has some unsupported cases such as:

Handling "prompts"
Handling locked secrets (probably requires prompts to work)
Using a non-default keyring
Creating a non-existent default keyring (not even sure we we should,
but this is something libsecret does, and hence
git-credential-libsecret too)
Encrypted sessions via dbus (not "plain")
Non-pageable memory for holding secrets

Also missing:

Go unit tests
Expanded readme with setup instructions

Has the do-not-merge label because it is not based on master. Once PR#1 is merged, this can be rebased and I'll then remove the label. But it could be reviewed now.


Fixed InlineField()

Fixes #25
@epicserve -- Would you like to take a look at this? I like your patch, it's very simple, but it doesn't add in the placeholders (which we have on the bs4 pack).

@smithdc1,
Looks good to me. Nothing jumped out at me as being wrong. If you wanted to make a release with this, I would be happy to use it in our BS5 upgrade branch.

@smithdc1,
Looks good to me. Nothing jumped out at me as being wrong. If you wanted to make a release with this, I would be happy to use it in our BS5 upgrade branch.

Thanks for the quick response. :+1:
I'll have a go at a release later... I want to try and get the automated release process working to make it easier in the future. I think it should "just work" but....  :shrug:

Thanks for the quick response. :+1:
I'll have a go at a release later... I want to try and get the automated release process working to make it easier in the future. I think it should "just work" but....  :shrug:

@smithdc1,
I randomly found this project and you could see how they do it.
https://github.com/jazzband/django-formtools/blob/master/.github/workflows/release.yml

@smithdc1,
I randomly found this project and you could see how they do it.
https://github.com/jazzband/django-formtools/blob/master/.github/workflows/release.yml

https://pypi.org/project/crispy-bootstrap5/ ok, a new release is now available on PyPI.

https://pypi.org/project/crispy-bootstrap5/ ok, a new release is now available on PyPI.

@smithdc1,
I'll try it tomorrow. BTW, how do you trigger a release event. I was looking at.
https://github.com/django-crispy-forms/crispy-bootstrap5/blob/master/.github/workflows/publish.yml

@smithdc1,
I'll try it tomorrow. BTW, how do you trigger a release event. I was looking at.
https://github.com/django-crispy-forms/crispy-bootstrap5/blob/master/.github/workflows/publish.yml

It's triggered by creating a 'release' on GitHub. I've linked below the item I created which triggered this workflow. It also created the version tag for me.
First time I did it this way and it seemed to work well.
https://github.com/django-crispy-forms/crispy-bootstrap5/releases

It's triggered by creating a 'release' on GitHub. I've linked below the item I created which triggered this workflow. It also created the version tag for me.
First time I did it this way and it seemed to work well.
https://github.com/django-crispy-forms/crispy-bootstrap5/releases

@smithdc1,
Did you create this commit manually or does creating a release add the commit?
https://github.com/django-crispy-forms/crispy-bootstrap5/commit/81f458f479a00b5ee8026effe0656e10465a576e

@smithdc1,
Also, I tested this and it seems to work, however it adds the class "field.html" is that a crispy-forms thing or BS5 thing or a bug? It doesn't seem correct to have CSS class with a period in the name.
<div id="div_id_first_name" class="field.html">
  <label for="id_first_name" class="visually-hidden">
      First name
  </label>
  <input type="text" name="first_name" value="Brent" maxlength="150" class="textinput textInput form-control" placeholder="First name" id="id_first_name">
</div>

@epicserve

Did you create this commit manually or does creating a release add the commit? 81f458f

I created the commit manually -- then the release manually. (Would be nice if it was a one-time thing!)

Also, I tested this and it seems to work, however it adds the class "field.html" is that a crispy-forms thing or BS5 thing or a bug? It doesn't seem correct to have CSS class with a period in the name.

The field.html in the class looks very odd to me, it's certainly not intended! I'm not quite sure what is going on here as it seems odd to get the file name into the class!
In my small test,  I don't see this happening. Are you able to share a small example so I can reproduce the bug?

@smithdc1,
Regarding deployment ... I wrote this deployment script that does everything. The only drawback is that you would have to run it locally.
https://gist.github.com/epicserve/2f0a2f270c8c78119cab44247f6339e6
Regarding feild.html it looks like that was an issue with my custom templatetag, so please disregard my comment.

Thanks for the quick feedback. 👍


Update wordpress/scripts

Changes proposed in this pull request
This PR updates @wordpress/scripts to version 26.
Details

node bumped to >=20.10.0
yarn bumped to >=4.4.1
wordpress/scripts updated to 26.4.0. The accompanying packages have been updated using packages-update
image-webpack-loader package and the custom webpack rules have been removed

Packages added with wordpress/scripts update

There were a large number of warnings in our previous build messages. I believe that dependencies were expected that were no included.
Dependencies added:

@playwright/test

eslint

react

react-dome

webpack

Resolutions were added for Yarn in the package.json file.
The resolutions field allows you to specify exact versions of packages that you want to enforce across the entire dependency tree. This means that even if different packages request different versions of the same dependency, the version you specify in resolutions will be used instead.
In tailwind.config.cjs the content items are more specific to exclude node_modules and satisfies an error encountered during testing.
yarn.lock is updated.
References to a past project removed from .env.sample.
NOTE: During the build you might see the following messages. They can be ignored.
➤ YN0060: │ react is listed by your project with version 18.3.1 (p0346b), which doesn't satisfy what react-autosize-textarea (via @wordpress/block-editor) and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react-dom is listed by your project with version 18.3.1 (p1a471), which doesn't satisfy what react-autosize-textarea (via @wordpress/block-editor) and other dependencies request (but they have non-overlapping ranges!).

➤ YN0007: │ core-js@npm:2.6.12 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js-pure@npm:3.38.1 must be built because it never has been before or the last one failed

Closes https://app.asana.com/0/1203895219649773/1208159906836440/f
Pre-submit checklist
As the author of this pull request, I verify that:

[x] I have set the target branch to master.
[x] I have detailed the purpose of this Pull Request in a non-technical way.
[x] I have detailed how to test the changes in the Pull Request.
[x] I have detailed the functional tests required for approval.
[x] I have performed a self-review of my code to ensure it is DRY and follows the team's coding standards.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] I have verified that my code does not introduce a debug warning in my local environment.
[ ] I have verified that the functional tests work in my local environment.
[ ] I have verified that all automated tests pass or have provided a detailed comment about why I am submitting with a failed pipeline.
[ ] I have verified that any dependent changes have been merged and published in downstream commits.
[ ] I have added a link to this Pull Request in the Asana task.
[ ] I have moved the Asana task to "Ready for Functional Review".
[ ] I have left a comment in Asana and GitHub tagging a team member with a request for `review.

Testing
How to test the changes in this pull request

Follow the steps below to test the changes in this PR.

Branch has been deployed to demo site: https://kindlingprd.wpengine.com
I've not seen any issues on the demo site.

Code review
As the code reviewer for this pull request, I verify that:

[ ] All automated tests have passed.
[ ] The code is written (or documented) in a way that is easy to understand.
[ ] The code is free of obvious errors.
[ ] The code is free of obvious duplication.
[ ] The code follows our coding standards.
[ ] The code is sanitized or escaped appropriately for any SQL or XSS injection possibilities.

Once testing is complete, notify the author of any failed tests and move the task to "Kick back" in Asana or continue with the "merging" steps below.
Merging
As the individual merging this pull request, I verify that:

[ ] All automated tests have passed.
[ ] All functional tests have passed.
[ ] All code review tests have passed.
[ ] I have moved the task to "Ready to Deploy" in Asana and notified the pull request author.

Re: tailwind config updates -

@sstruemph This worked for me, but I had to change the configuration of my machine. Below is an overview of what I discovered and the steps I needed to take before this update worked.
I'd like to have @EugeneKyale and @stonetim test in their locals to see if they experience a similar issue. Adding some dev notes in the readme may be worth it.
After updating locally, I attempted to run the yarn command but was met with an error that my version of yarn didn't meet the minimum requirement. This was accurate, but took me a bit to figure out the issue. I had installed node and yarn using homebrew, but the highest version of yarn homebrew supports is 1.22.22.
This led me to review the official Yarn docs and discover the following.

You may notice by reading our installation guide that we don't tell you to run npm install -g yarn to install Yarn - we even recommend against it. source

I attempted to install using their recommended method, only to discover that the homebrew package of node doesn't include corepack.
To fix this, I had to remove yarn and node from Homebrew using brew uninstall --force yarn and brew uninstall --force node. Then reinstall using the following steps.

Install nvm.
VERY IMPORTANT! Close and reopen the terminal window.
Install node using nvm install 22.
Enable corepack using corepack enable. I may have had to use sudo corepack enable this.
I was prompted to install yarn v1.22.22 and selected yes.
Ran yarn -v to confirm that v1.22.22 was installed.
Upgrade yarn to 4.4.1 using yarn set version stable.
Ran yarn -v to confirm that v4.4.1 was installed.

This is working as expected now. Did you run into anything like this during your testing?

@sstruemph This worked for me, but I had to change the configuration of my machine. Below is an overview of what I discovered and the steps I needed to take before this update worked.
I'd like to have @EugeneKyale and @stonetim test in their locals to see if they experience a similar issue. Adding some dev notes in the readme may be worth it.
After updating locally, I attempted to run the yarn command but was met with an error that my version of yarn didn't meet the minimum requirement. This was accurate, but took me a bit to figure out the issue. I had installed node and yarn using homebrew, but the highest version of yarn homebrew supports is 1.22.22.
This led me to review the official Yarn docs and discover the following.

You may notice by reading our installation guide that we don't tell you to run npm install -g yarn to install Yarn - we even recommend against it. source

I attempted to install using their recommended method, only to discover that the homebrew package of node doesn't include corepack.
To fix this, I had to remove yarn and node from Homebrew using brew uninstall --force yarn and brew uninstall --force node. Then reinstall using the following steps.

Install nvm.

VERY IMPORTANT! Close and reopen the terminal window.

Install node using nvm install 22.

Enable corepack using corepack enable. I may have had to use sudo corepack enable this.

I was prompted to install yarn v1.22.22 and selected yes.
Ran yarn -v to confirm that v1.22.22 was installed.

Upgrade yarn to 4.4.1 using yarn set version stable.

Ran yarn -v to confirm that v4.4.1 was installed.

This is working as expected now. Did you run into anything like this during your testing?

@unscripted @sstruemph I encountered some issues when trying to build the project locally, but I was eventually able to resolve them. Initially, when I attempted to run the build, I encountered the following errors:
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=18.12.0". Got "16.6.1"
error<EMAIL_ADDRESS>The engine "yarn" is incompatible with this module. Expected version ">=4.22.22". Got "1.22.17"
error Commands cannot run with an incompatible environment.

These errors indicated that my local environment was not aligned with the required Node.js and Yarn versions specified by the project.
To fix the issue, here are the steps I followed:

Switch Node.js to the required version: I used nvm to switch to Node.js 20.0.0, which aligns with the project's requirements. I also removed the globally installed version of Yarn to avoid any conflicts.
nvm use 20.0.0 && npm uninstall -g yarn
Enable and prepare Corepack: I enabled Corepack and then activated the latest stable version of Yarn, ensuring that it meets the project's expectations.

corepack enable
corepack prepare yarn@stable --activate

Verify the Yarn installation: I confirmed that the correct version of Yarn was installed.
yarn --version
Clean up and reinstall dependencies: After deleting the old node_modules directory to prevent issues related to outdated packages, I reinstalled the dependencies with the correct versions of Node.js and Yarn.
nvm use 20.0.0 && yarn install
Build the project: Finally, I ran the build command using the appropriate Node.js version.
nvm use 20.0.0 && yarn build

After following these steps, the build process completed successfully.

@EugeneKyale  @unscripted I started a slack thread but maybe we should discuss it here instead?
Thank you both for testing this! It seems that Yarn is adding a few additional steps versus what we would have with NPM. In the past I have always used NPM on dev projects and that would be my preference.


Remove panicky Event wrapper methods

Event provides a set of trivial wrapper methods that call a corresponding e.Context Get/Set method and panic if it returns a non-nil error.I suggest these wrapper methods  be removed, they add  nothing and create a dangerous point of confusion for the API user: it is normal to assume that a simple Get/Set method with no error return is safe to call, it is very abnormal for such a method to crash the program if it gets invalid arguments.
Methods that panic should be clearly documented and it should be easy for the caller to establish the pre-conditions for a safe call  (e.g. a pointer is not nil) - that isn't the case here e.g. how should the caller know the set of allowed version for SetSpecVersion() in advance of calling it, as this set changes with new versions of the cloudevents library?

I understand that. The problem is that
a) they are redundant, you can just say event.Context.SetBlah instead of event.SetBlah.
b) they panic instead of returning an error
The panic is the bigger problem, it is not the normal way to indicate a runtime error in Go. Programmers who see functions like cloudevents.New() or Event.SetSpecVersion() with no error return value are likely to assume they always work (setters and constructors are often error-free) so they will be surprised when their application crashes. Handling panics is quite different from normal error handling so these methods are awkward to use safely.

a) they adapt the old field names to the new field names so the encoders do not need to understand the versions, so they are not 100% redundant. They also help convert types from strings to strongtypes.
b) you can recover if you really want to and 99% of the time this is what the user wants to do because error checking all the setters is a bummer.

Fair enough, but the API comments need to be clear about the panic. It's
natural to assume that what looks like a simple Set function and returns no
error is a non-failing operation.
Also if New() and SetVersion() can panic on an invalid version string, then
the API needs to provide a safe way to determine what is a valid version
string. The set of valid versions changes with new releases of the library.
It's OK to panic if the (documented!) preconditions of the API are not met

but there has to be a non-panic way to establish those preconditions.

On Fri, Sep 20, 2019 at 11:47 AM Scott Nichols<EMAIL_ADDRESS>wrote:

a) they adapt the old field names to the new field names so the encoders
do not need to understand the versions, so they are not 100% redundant.
They also help convert types from strings to strongtypes.
b) you can recover if you really want to and 99% of the time this is what
the user wants to do because error checking all the setters is a bummer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudevents/sdk-go/issues/182?email_source=notifications&email_token=AB3LUXWWSNV2DEAJXTSRQMLQKTWBVA5CNFSM4IT7MYF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7HDUYY#issuecomment-533609059,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3LUXVWTALCCRXFZ3EV6WTQKTWBVANCNFSM4IT7MYFQ
.

We removed these now.


Breadcrumb component to allow a react-router  instead of a bare

[x] I have searched the Issues to see if this bug has already been reported
[x] I have tested the latest version

Summary
Currently, <BreadcrumbItem> can be rendered as an anchor link or a span. But given that this is a React library, and the overwhelming majority of React apps use react-router, <BreadcrumbItem> should at least be able to render a <Link>.
This can probably be accomplished by refactoring <BreadcrumbItem> to accept as={Link}.

i'm using next, also want this feature...

I am working on this feature

this changes based on button, but how to test it?
import type { ComponentPropsWithoutRef, ElementType, ForwardedRef, FC } from "react";
import { createElement, forwardRef } from "react";
import { HiOutlineChevronRight } from "react-icons/hi";
import { twMerge } from "tailwind-merge";
import { mergeDeep } from "../../helpers/merge-deep";
import { getTheme } from "../../theme-store";
import type { DeepPartial } from "../../types";
import type { FlowbiteBoolean } from "../Flowbite";

export interface FlowbiteBreadcrumbItemTheme {
  base: string;
  chevron: string;
  href: FlowbiteBoolean;
  icon: string;
}

export type BreadcrumbItemProps<T extends ElementType = "span"> = {
  as?: T;
  href?: string;
  icon?: FC<ComponentPropsWithoutRef<"svg">>;
  theme?: DeepPartial<FlowbiteBreadcrumbItemTheme>;
} & ComponentPropsWithoutRef<T>;

export const BreadcrumbItem = forwardRef(
  <T extends ElementType = "span">(
    { children, className, as: Component, href, icon: Icon, theme: customTheme = {}, ...props }: BreadcrumbItemProps<T>,
    ref: ForwardedRef<T>,
  ) => {
    const BaseComponent = Component || (href ? "a" : "span");

    const theme = mergeDeep(getTheme().breadcrumb.item, customTheme);

    return (
      <li className={twMerge(theme.base, className)} {...props}>
        <HiOutlineChevronRight aria-hidden className={theme.chevron} data-testid="flowbite-breadcrumb-separator" />
        {createElement(
          BaseComponent,
          {
            ref,
            href,
            className: theme.href[href ? "on" : "off"],
            "data-testid": "flowbite-breadcrumb-item",
            ...props,
          },
          <>
            {Icon && <Icon aria-hidden className={theme.icon} />}
            {children}
          </>,
        )}
      </li>
    );
  },
);

BreadcrumbItem.displayName = "Breadcrumb.Item";


Mutator called 9 times

Laravel Version: 9.2
PHP Version: 8.0.16

Description:
class Category extends Model
{
    public function banner(): Attribute
    {
        return Attribute::make (
            get: fn ($value) => asset('images/category/Banner/'.$value),
            set: function ($value) {
                if(is_file($value))
                {
                    Log::info('count');
                    $fileName = 'Banner_'.rand(11111,99999).'.'.$value->getClientOriginalExtension();
                    $value->storeAs('images/category/Banner', $fileName );
                    return $fileName;
                }
            }
        );
    }
}

when creating a new Category -
the Log count called 9 times
which cause the image to be uploaded 9 times

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

Hello Dries
please let me if I am wrong -
when I use the old way SetBannerAttribute() It worked fine - but with the new way - it has been called 9 times  -
so I assumed that this is a problem in the library

@driesvints I think it's an issue. It seems that to allow things such as $model->address->lineOne = '123 High St.' the set function of the Attribute is called on save (which is correct) and on every subsequent call of any accessor.
i.e. if the model has a secondaryAddress Attribute doing this
$model->address->lineOne = '123 High St.';
echo $model->secondaryAddress->lineOne;

triggers the set function on the address Attribute.

You should not perform file operations in an attribute. The attribute is purely to transform the attribute's value and shouldn't perform any side effects. It shouldn't matter how many times it's invoked.

Ok, I get it. My mutator doesn't have side effects. But if you have many Attributes and you are showing an index page, these calls add up pretty quickly.

The amount of times an attribute is invoked purely depends on how many times the attribute is called and how many records are involved. If you multiple those then the method can potentially get called a lot. These should have no impact on performance. There should not be any heavy operations performed in these attributes.

What seems odd to me is that when I access attribute A the mutator for attribute B is called. First, mutators should not be called if I'm accessing the value. Second, the mutator for a different attribute should not be accessed when calling other attributes.

@zupolgec that's definitely true. At the moment I don't think this leads to bugs. But if anyone can figure out how to prevent that from happening we'd welcome PR's for it.


Cut the next release?

Would it be possible to make another release with some of the recent changes that were merged? Or is there a defined timeline/milestone when a release will happen?

Hi @afgane, here's the milestone for the next point release: https://github.com/cvmfs-contrib/cvmfs-csi/issues?q=milestone%3A"Release+v2.2.0"+. There is no concrete date, but I'm aiming to include these tasks in the release.

Hi @afgane, FYI v2.2.0 is out.


Create EnglishAuction.sol

Hi @adielliot37
This repo is only for solutions to Frontend Mentor challenges. I cannot accept this PR


*** stack smashing detected ***:  terminated

ubuntu 18.04.3  kernel 5.0.37
rocm 2.10.14 can't work.
code:
import tensorflow as tf
mnist = tf.keras.datasets.mnist

(x_train, y_train),(x_test, y_test) = mnist.load_data()
x_train, x_test = x_train / 255.0, x_test / 255.0

model = tf.keras.models.Sequential([
  tf.keras.layers.Flatten(input_shape=(28, 28)),
  tf.keras.layers.Dense(128, activation='relu'),
  tf.keras.layers.Dropout(0.2),
  tf.keras.layers.Dense(10, activation='softmax')
])

model.compile(optimizer='adam',
              loss='sparse_categorical_crossentropy',
              metrics=['accuracy'])

model.fit(x_train, y_train, epochs=5)
model.evaluate(x_test, y_test)

error:
2019-12-10 01:34:21.442336: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libhip_hcc.so
*** stack smashing detected ***: <unknown> terminated

clinfo:
Number of platforms:				 1
  Platform Profile:				 FULL_PROFILE
  Platform Version:				 OpenCL 2.1 AMD-APP (3019.0)
  Platform Name:				 AMD Accelerated Parallel Processing
  Platform Vendor:				 Advanced Micro Devices, Inc.
  Platform Extensions:				 cl_khr_icd cl_amd_event_callback cl_amd_offline_devices

  Platform Name:				 AMD Accelerated Parallel Processing
Number of devices:				 1
  Device Type:					 CL_DEVICE_TYPE_GPU
  Vendor ID:					 1002h
  Board name:					 Vega 20
  Device Topology:				 PCI[ B#40, D#0, F#0 ]
  Max compute units:				 60
  Max work items dimensions:			 3
    Max work items[0]:				 1024
    Max work items[1]:				 1024
    Max work items[2]:				 1024
  Max work group size:				 256
  Preferred vector width char:			 4
  Preferred vector width short:			 2
  Preferred vector width int:			 1
  Preferred vector width long:			 1
  Preferred vector width float:			 1
  Preferred vector width double:		 1
  Native vector width char:			 4
  Native vector width short:			 2
  Native vector width int:			 1
  Native vector width long:			 1
  Native vector width float:			 1
  Native vector width double:			 1
  Max clock frequency:				 1801Mhz
  Address bits:					 64
  Max memory allocation:<PHONE_NUMBER>2
  Image support:				 Yes
  Max number of images read arguments:		 128
  Max number of images write arguments:		 8
  Max image 2D width:				 16384
  Max image 2D height:				 16384
  Max image 3D width:				 2048
  Max image 3D height:				 2048
  Max image 3D depth:				 2048
  Max samplers within kernel:			 26287
  Max size of kernel argument:			 1024
  Alignment (bits) of base address:		 1024
  Minimum alignment (bytes) for any datatype:	 128
  Single precision floating point capability
    Denorms:					 Yes
    Quiet NaNs:					 Yes
    Round to nearest even:			 Yes
    Round to zero:				 Yes
    Round to +ve and infinity:			 Yes
    IEEE754-2008 fused multiply-add:		 Yes
  Cache type:					 Read/Write
  Cache line size:				 64
  Cache size:					 16384
  Global memory size:<PHONE_NUMBER>8
  Constant buffer size:<PHONE_NUMBER>2
  Max number of constant args:			 8
  Local memory type:				 Scratchpad
  Local memory size:				 65536
  Max pipe arguments:				 16
  Max pipe active reservations:			 16
  Max pipe packet size:<PHONE_NUMBER>
  Max global variable size:<PHONE_NUMBER>2
  Max global variable preferred total size:<PHONE_NUMBER>8
  Max read/write image args:			 64
  Max on device events:				 1024
  Queue on device max size:			 8388608
  Max on device queues:				 1
  Queue on device preferred size:		 262144
  SVM capabilities:
    Coarse grain buffer:			 Yes
    Fine grain buffer:				 Yes
    Fine grain system:				 No
    Atomics:					 No
  Preferred platform atomic alignment:		 0
  Preferred global atomic alignment:		 0
  Preferred local atomic alignment:		 0
  Kernel Preferred work group size multiple:	 64
  Error correction support:			 0
  Unified memory for Host and Device:		 0
  Profiling timer resolution:			 1
  Device endianess:				 Little
  Available:					 Yes
  Compiler available:				 Yes
  Execution capabilities:
    Execute OpenCL kernels:			 Yes
    Execute native function:			 No
  Queue on Host properties:
    Out-of-Order:				 No
    Profiling :					 Yes
  Queue on Device properties:
    Out-of-Order:				 Yes
    Profiling :					 Yes
  Platform ID:					 0x7f968d20bd50
  Name:						 gfx906+sram-ecc
  Vendor:					 Advanced Micro Devices, Inc.
  Device OpenCL C version:			 OpenCL C 2.0
  Driver version:				 3019.0 (HSA1.1,LC)
  Profile:					 FULL_PROFILE
  Version:					 OpenCL 2.0
  Extensions:					 cl_khr_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_media_ops cl_amd_media_ops2 cl_khr_image2d_from_buffer cl_khr_subgroups cl_khr_depth_images cl_amd_copy_buffer_p2p cl_amd_assembly_program

Hi @love-moon , can you first try to use tensorflow docker container and see if the issue remains:
https://hub.docker.com/r/rocm/tensorflow

Hi @love-moon , can you first try to use tensorflow docker container and see if the issue remains:
https://hub.docker.com/r/rocm/tensorflow

After I update Tensorflow to version 2.0.1, this issue dose not occur.


Fix portal delay on website

I think to fix this would involve implementing handlebars and preloading the content before outputting the webpage. Made the SourcePortal project for this implementation and pushing ticket to 0.3.0.


Feature/process listening on port public api change name

Description
Minimum changes to make the name of the public API listening_endpoints instead of processes_listening_on_ports.
Checklist

[ ] Investigated and inspected CI test results

Testing Performed
CI is sufficient

/test gke-nongroovy-e2e-tests

/retest

/test gke-postgres-qa-e2e-tests


Feature Request: easily build flatpaks and/or appimages

Feature description
We can use dockerTools.buildImage to easily take an existing package and turn it into a docker app. Can we make something similar for Flatpak or AppImage?
The use-case is: I'm making an app, and building it with nix. Now, once I'm done I want to make it available on other linux distros (without having to install nix). Wouldn't it be nice to just wrap it in flatpakTools.buildFlatpak call and have something portable?
Questions
I'm happy to do some work on this, but I'm not very familiar with the systems involved, so I figured i would also post something here to ask:

Am I understanding how these systems work and what they're for correctly?
Would this be outside the scope of what nixpkgs does?
How much work would this end up being? dockerTools.buildImage seems quite complicated.

I don’t think this is realistic. Binaries built with Nix are full of hard-coded references to /nix/store paths for the dynamic loader, libraries, and any other data the package needs. Unlike Docker containers, which have their own filesystem, a Flatpak or AppImage can’t (and/or shouldn’t) just put stuff in /nix/store.
Depending on the application, you may be able to link everything statically, and then you don’t need further help from Nix to package it in whatever format you want. Otherwise, you’ll probably need to set up a more traditional build using the upstream Flatpak or AppImage toolchain.

I don’t think this is realistic. Binaries built with Nix are full of hard-coded references to /nix/store paths for the dynamic loader, libraries, and any other data the package needs. Unlike Docker containers, which have their own filesystem, a Flatpak or AppImage can’t (and/or shouldn’t) just put stuff in /nix/store.
Depending on the application, you may be able to link everything statically, and then you don’t need further help from Nix to package it in whatever format you want. Otherwise, you’ll probably need to set up a more traditional build using the upstream Flatpak or AppImage toolchain.

Flatpak has a notion of runtime (mounted to /usr inside the sandbox) and an app (mounted to /app). Each app has one runtime associated. So you would have to decide if you want to build your runtime or choose some tiny one and stuff everything into the app bundle.
Since you can only use /usr or /app prefix, you would also need to modify the store paths. For example, in Flatpak tests, we build the test runtime by replacing /nix/store with /usr/store: https://github.com/NixOS/nixpkgs/blob/5bcc26338d42c8bc53cf9ed4bc2ae7c28ab66f69/pkgs/development/libraries/flatpak/fix-test-paths.patch
https://github.com/flatpak/flatpak-builder might be also interesting.

Flatpak has a notion of runtime (mounted to /usr inside the sandbox) and an app (mounted to /app). Each app has one runtime associated. So you would have to decide if you want to build your runtime or choose some tiny one and stuff everything into the app bundle.
Since you can only use /usr or /app prefix, you would also need to modify the store paths. For example, in Flatpak tests, we build the test runtime by replacing /nix/store with /usr/store: https://github.com/NixOS/nixpkgs/blob/5bcc26338d42c8bc53cf9ed4bc2ae7c28ab66f69/pkgs/development/libraries/flatpak/fix-test-paths.patch
https://github.com/flatpak/flatpak-builder might be also interesting.

nix-bundle supports building AppImage executables. I have used this for distributing two applications and it works fine so far.

nix-bundle supports building AppImage executables. I have used this for distributing two applications and it works fine so far.

Thanks so much y'all. I'm looking into nix-bundle right now, which seems to be exactly what I'm looking for. It's also accessible directly using nix via something like:
(import "${nix-bundle}/share/nix-bundle { nixpkgs = import <nixpkgs> { }; }).nix-bootstrap {
  target = import ./default.nix;
  run = "/bin/command";
}

It's not currently working for me, but in theory this is what I wanted.
I still think it'd be worth integrating more closely with nix (importing a nix file from a derivation feels kind of janky to me), but I'm fine with closing this.

Thanks so much y'all. I'm looking into nix-bundle right now, which seems to be exactly what I'm looking for. It's also accessible directly using nix via something like:
(import "${nix-bundle}/share/nix-bundle { nixpkgs = import <nixpkgs> { }; }).nix-bootstrap {
  target = import ./default.nix;
  run = "/bin/command";
}

It's not currently working for me, but in theory this is what I wanted.
I still think it'd be worth integrating more closely with nix (importing a nix file from a derivation feels kind of janky to me), but I'm fine with closing this.

nix-bundle works for this, and flakes makes it quite convenient for my purposes. Closing.


Fix: typos

Codecov Report

Merging #7 (1e7430c) into main (8942c76) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #7   +/-   ##
=======================================
  Coverage   97.19%   97.19%
=======================================
  Files           6        6
  Lines         214      214
  Branches       40       40
=======================================
  Hits          208      208
  Misses          6        6

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I think I need to add spellchecking to the pipeline for the READMEs. This is the second PR I am approving for the typo fixes in less than a week. 😄


[WIP] Move Right drawer into the Left Drawer as a tab

@nashvail I don't think joining both drawers is a step in between implementing the design.
Maybe you missed the discussion in #mobile but we talked with Tim to show the Unread Streams UI in the left sidebar until you are finished with the mocks.
The PR for that is here:
https://github.com/zulip/zulip-mobile/pull/968

@borisyankov sorry about the confusion. Me and @neerajwahi had a discussion and decided that I should get started with first, moving the right drawer into the left drawer with a tab view and then moving it all to a modal.
I think we should have a quick meeting on this so that everybody is on the same page 😅

@neerajwahi ready for review

@neerajwahi rebased, please review :)

This looks like ready to merge.
Please, rebase, and we can get it in.

Rebased.


Automatic Labeling of Topics

Ready for Automatic Labeling of Topics.
Functionality should be implemented in function get_tpc_labels() of class TMmodel, in src/topicmodeling/manageModels.py

Already implemented. Pending validation including infrastructure on which it should run ... Can it run on a normal Virtual Machine ?

We also need to link automatic topic labeling with other parts of the project:
1/ Generation of lists. We need to implement also lists of labels
2/ In the CMD and graphical UIs, we need to ask the user what lists of labels they wish to use for labeling topics.


Automated cherry pick of #3491: feat(region): Add list and delelte apis for snapshot policy cache

Cherry pick of #3491 on release/2.12.
#3491: feat(region): Add list and delelte apis for snapshot policy cache

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@6e1a684). Click here to learn what that means.
The diff coverage is 3.22%.

@@              Coverage Diff               @@
##             release/2.12   #3504   +/-   ##
==============================================
  Coverage                ?   6.99%
==============================================
  Files                   ?     498
  Lines                   ?   83047
  Branches                ?       0
==============================================
  Hits                    ?    5809
  Misses                  ?   76744
  Partials                ?     494

Flag
Coverage Δ

#aFlag
6.99% <3.22%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/snapshotpolicycache.go
4.43% <3.22%> (ø)

Continue to review full report at Codecov.

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

/lgtm
/apprvoe

/approve


Code Smells Always 0 ?

Hi,
I dont understand why the code Smell is always 0.
when i check the installation guide, i visit the following link, but still have 0.
It is a bug or a misconfiguration ?
https://sonar.pablissimo.com/overview?id=20352
https://sonar.pablissimo.com/overview?id=18822
Sincerely,

On the demo site it's just because those code bases happen to be clean relative to their rules files (they used to be dirtier, sadly they aren't very good as a demo case any more)
So are you having issues with your own installation? Would start by running the scanner with -X -e options to see what is happening, and post or email the log.
-------- Original message --------
From: Kévin Giroux<EMAIL_ADDRESS>Date: 19/01/2017 07:38 (GMT+00:00)
To: Pablissimo/SonarTsPlugin<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [Pablissimo/SonarTsPlugin] Code Smelles Always 0 ? (#90)
Hi,
I dont understand why the code Smell is always 0.
when i check the installation guide, i visit the following link, but still have 0.
It is a bug or a misconfiguration ?
https://sonar.pablissimo.com/overview?id=20352
https://sonar.pablissimo.com/overview?id=18822
Sincerely,

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Pablissimo/SonarTsPlugin/issues/90, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABZvgHSmaB5-lUnFELi1U1LH9qGSugfuks5rTxMDgaJpZM4Lnyjc.

Just email the stack on<EMAIL_ADDRESS>

So to me everything in the log looks good. Next step - find the command line in the log you sent and try to run it in a shell - you can omit the --out parameter. See if you get any issues reported.
If you don't, congrats! Your code is clean. If you do, check:

whatever user is running the scanner has write access to the temp path descrobed by the --out parameter
that on SQ the rules profile actually has rules enabled, and that they've not all defaulted to Off

I need to add better logging of the tslint output to aid this sort of thing, but let me know how you get on. At a conference this week but have little bits of downtime...

Also: what version of tslint are you using?

tslint version<EMAIL_ADDRESS>If you don't, congrats! Your code is clean. If you do, check.  ===> it seems difficult to believe because, i try the following command  with the tslint in my project and i have a big file of error.
"lint": "tslint -t checkstyle --force -o target/checkstyle-result.xml "src/**/*.ts"",

But did you run it with the specific command line the plug in was sending? Entirely possible there is a bug, just want to make sure we're not missing something

Without changing anything, it is working.
Thank for your help


429 from RPC provider: "future transaction tries to replace pending" When using forge script

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (388c3c0 2023-04-11T00:17:58.707017000Z)
What command(s) is the bug in?
forge script
Operating System
macOS (Apple Silicon)
Describe the bug
I have a somewhat complex deployment procedure that produces around 20 transactions. I am using forge script to invoke the deployment on the Goerli network.
I have run multiple deployments in the past with no issue. Now, when running the command I get the error:
Error:
(code: -32000, message: future transaction tries to replace pending, data: None)

If you were trying to resume or verify a multi chain deployment, add `--multi` to your command invocation.

2 of the 21 transactions were successfully broadcast, but it appears that maybe forge is not waiting for the results properly before submitting other transactions with the same nonce?
If I run the same command with --resume, then forge correctly picks up from where it left off, but errors again with the same message after submitting a single transaction.
By checking the nonce of the transaction in etherscan and matching it to the relevant transaction in deploy-latest.json, I can see the the hash field is set as null - which I assume means that forge didn't pick up that this transaction was included in a block.
When running with --resume for 3rd time, more transactions are created, but the hashes of completed transactions are never filled in.
As an example, here is the record from the deploy-latest file for nonce 0xe4 which was a contract creation. The equivalent etherscan transaction is here: https://goerli.etherscan.io/tx/0x829df2c378cadcf10b06ddacfd7726813000e516bf82eff4fda2eab6e8f4b17a
{
      "hash": null,
      "transactionType": "CREATE",
      "contractName": "TransparentUpgradeableProxy",
      "contractAddress": "0xFb97e05422b45fe1e21fB4d70FFE1797dC79d095",
      "function": null,
      "arguments": [
        "0x94da33946150493388dBa3fb77Bb292ed9351657",
        "0x2dFD34e23315d9eB9E59E4567120bA34F6a9C63D",
        "0x"
      ],
      "rpc": "https://eth-goerli.g.alchemy.com/v2/dGQ882Y37nKEkoy6dvAnna5S_x0DoB0n",
      "transaction": {
        "type": "0x02",
        "from": "0xc42721384b6e914f33da870b75d793ccebe576cc",
        "gas": "0xb8531",
        "value": "0x0",
        "data": "[encoded data, 7588 characters]",
        "nonce": "0xe4",
        "accessList": []
      },
      "additionalContracts": [],
      "isFixedGasLimit": false
    },

Edit:
After digging into this, it appears to be caused by rate limiting from my RPC provider.

Running the script caused ~80 concurrent RPC requests to Alchemy, which rate limits me every time. I have just found the --slow flag, though when running with that I just get under the rate limit (forge still does a lot of queries before sending a single tx). However, I then got the error: EOA nonce changed unexpectedly while sending transactions. Expected 237 got 238 from provider. - I am not changing the nonce or doing transactions through any other process.
I think that generally the UX can be improved here:

Detecting 429s from rpc providers (if possible) and emitting a better error message.
Adding the ability to put a client side rate limit on requests to the RPC url.

Just ran into the same problem with a forge script against mainnet. --slow fixes this, but is also very slow (for 30+ transactions). Didn't run into rate limit, but ran into https://github.com/ethereum/go-ethereum/issues/26890

I currently have this bug on mainnet, anyone knows how to solve it?

I currently have this bug on mainnet, anyone knows how to solve it?

It is because rpc limits, just use --resume with running your script until all transactions will be completed.

I encountered this issue today and managed to resolve it by adding --slow. Sharing this here in case someone else faces the same problem and comes across this thread.


Fix ci upload latest bundle bug

Coverage remained the same at 56.192% when pulling 48cdc0fb04cc26f5c197d205ad33f6f3a62c9391 on wy65701436:fix-ci-bug into d13321f2b5d6d6f2e4ed822efc78cc1aff089dde on vmware:master.


grant_max does not reserve the largest contiguous buffer available

This might just be a documentation issue, but I was assuming that grant_max should behave identically to grant wrt. the successful case. An example:
use bbqueue::*;

fn main() {
    let bbq = bbq!(1000).unwrap();

    let size = 999;
    let grant = bbq.grant(size).unwrap();
    bbq.commit(size, grant);
    let grant = bbq.read().unwrap();
    bbq.release(size, grant);

    let grant = bbq.grant_max(500).unwrap();
    println!("{}", grant.len());
    bbq.commit(0, grant);
}

This consumes and then frees all but 1 Byte of the queue. Then it tries to obtain a 500-byte grant using grant_max. I would expect this to succeed and return the requested 500-byte grant, since there's a large 999-byte area that's still free. Instead it returns a grant of length 1.
Using grant instead will successfully grant 500 bytes.

The docs have been updated in #37, and work on new grant types is tracked in #38.


make_port dumps core

Describe the bug
Calling make_ports dummy_port input triggers a core-dump.
I have additionally attached an ipython notebook for Google Colab to reproduce the issue.
/cc @proppy
/cc @dhaentz1
Expected Behavior
make_ports should not core-dump but trigger an error message if required.
OpenROAD Environment
Env.sh seems not to be included in my litex-hub package - please use the testcase notebook to extract data.

OpenLane Environment
env.py seems to be broken in my setup - please use the testcase notebook to extract data.

To Reproduce
_build.core_dump__make_port.zip
OpenRoad__make_port_dumps_core.ipynb.gz
Relevant log output
Create a port ...
Signal 11 received
Stack trace:
 0# 0x0000000000B9E2AB in openroad
 1# 0x00007FD1088FB090 in /lib/x86_64-linux-gnu/libc.so.6
 2# sta::ConcreteInstance::addPin(sta::ConcretePin*) in openroad
 3# sta::ConcreteNetwork::makePin(sta::Instance*, sta::Port*, sta::Net*) in openroad
 4# sta::Sta::makePortPin(char const*, char const*) in openroad
 5# 0x0000000000D5F7FB in openroad
 6# TclNRRunCallbacks in /content/eda/bin/../lib/libtcl8.6.so
 7# 0x00007FD10A41B1BF in /content/eda/bin/../lib/libtcl8.6.so
 8# Tcl_EvalEx in /content/eda/bin/../lib/libtcl8.6.so
 9# Tcl_Eval in /content/eda/bin/../lib/libtcl8.6.so
10# sta::sourceTclFile(char const*, bool, bool, Tcl_Interp*) in openroad
11# ord::tclAppInit(Tcl_Interp*) in openroad
12# Tcl_MainEx in /content/eda/bin/../lib/libtcl8.6.so
13# main in openroad
14# __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6
15# 0x0000000000B885C2 in openroad

Screenshots
No response
Additional Context
No response

I am little confused about this issue. If STA is integrated into Openroad and has callbacks to stay in sync with the Openroad DB (odb) ... how is it possible to create a port via what seems to be a pure STA command (since I don't think the call back mechanism is bi-directional).
cc: @tspyrou @maliberty

dbNetwork::connect makes a bterm (called from dbSta::connectPin) so it seems bidirectional.

Thanks. Let me take a look at that.


Error code 400: The chatCompletion operation does not work with the specified model, gpt-35-turbo. Please choose different model and try again.

I tried using Open-AI to do simulations before but the simulation (only 3 agents) would usually get stuck within 100 steps. I don't think it can reach the rate limit of Open-AI, but I cannot find what is wrong.
So I decided to switch to azure open-ai. I deployed the gpt-3.5-turbo (0125) model on azure. This is the deployment infomation.

This is part of the conifg file:
"client": "azure",
    "model": "gpt-35-turbo",
    "model-key": "xxx",
    "model-endpoint": "https://xxxxxx.openai.azure.com/",
    "model-api-version": "2024-08-01-preview",
     ...

After opening the backend and typing "run 10" I got this error:
Error: Error code: 400 - {'error': {'code': 'OperationNotSupported', 'message': 'The chatCompletion operation does not work with the specified model, gpt-35-turbo. Please choose different model and try again. You can learn more about which models can be used with each operation here: https://go.microsoft.com/fwlink/?linkid=2197993.'}}

This is the first time that I use azure. Did I make anything wrong?

Looks like that I am using the Azure student pack and sadly not able to do completions or chat completions because I can only deploy the type of Global Batch for gpt-3.5-turbo.


[Feature] Add width_bucket function

What type of PR is this:

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes:

Fixes #12990
Problem Summary(Required):

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[x] This pr needs user documentation (for new or modified features or behaviors)

[x] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

@Mergifyio rebase

Please fix the problems based on the ci reports.

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

LGTM


Fixes in preparation for Flatpak packaging

I am trying to get the (standalone) TurtleBlocks app on Flathub, and I packaged it as Flatpak.
I had to write a few fixes in preparation for that, that I would like to bring upstream.
Thanks for considering them!
(As an aside, it would be great if the new v217 and v218 releases could be tagged in git so that I can use that tag to build the Flatpak, or perhaps a new v219 when these fixes are in :-))

It would also be awesome if you wanted to help with maintenance of the Flatpak manifest, since we prefer upstreams to maintain their own apps on Flathub!

Merged, thanks.


[Bug]: wrong argument passing?

Describe the bug
https://github.com/microsoft/autogen/blob/fb74624376fa0f5b5a0b8da6677624bf3692eb6c/autogen/agentchat/contrib/retrieve_user_proxy_agent.py#L346-L352
Should not be on line 349 self._chunk_token_size?
Because we want to split by chunk size and not by maximal context size of the LLM.
Steps to reproduce
No response
Model Used
No response
Expected Behavior
No response
Screenshots and logs
No response
Additional Information
No response

This has been fixed.


Add Website link in Readme.

Changes made-

Added the live web hosting link for the website in the readme.

@rakshitgondwal Issue no?
__
  Summary: :question: I have a question

@rakshitgondwal Issue no?
__
  Summary: :question: I have a question

nope. no issue.

I can't merge like this
__
  Summary: :hammer_and_wrench: This code needs a fix

closes #254

@Susmita-Dey is it alright now?

@Susmita-Dey is it alright now?

yes


Using decorator syntax doesn't pass eslint

Intended outcome:
I trired to start a new react native boilerplate project with mobX. After followed the steps to use decorators from document, expected to not see any error from eslint
Actual outcome:
I got Parsing error: Unexpected character '@' from eslint
How to reproduce the issue:
Start a new react native project with bable 7
Versions
The configs in short:
package.json
"dependencies": {
    "mobx": "^5.15.4",
    "mobx-react": "^6.1.8",
    ...
  },
"devDependencies": {
    "@babel/cli": "^7.8.4",
    "@babel/core": "^7.6.2",
    "@babel/plugin-proposal-class-properties": "^7.8.3",
    "@babel/plugin-proposal-decorators": "^7.8.3",
    "@babel/plugin-transform-flow-strip-types": "^7.8.3",
    "@babel/preset-env": "^7.8.7",
    "@babel/runtime": "^7.6.2",
    "@react-native-community/eslint-config": "^0.0.5",
    "babel-eslint": "^10.1.0",
    "babel-jest": "^24.9.0",
    "babel-preset-mobx": "^2.0.0",
    "babel-preset-react": "^6.24.1",
    "babel-preset-react-native": "^4.0.1",
    "eslint": "^6.8.0",
    "eslint-config-prettier": "^4.1.0",
    "eslint-config-standard": "^12.0.0",
    "eslint-plugin-import": "^2.16.0",
    "eslint-plugin-node": "^8.0.1",
    "eslint-plugin-prettier": "^3.0.1",
    "eslint-plugin-promise": "^4.0.1",
    "eslint-plugin-react": "^7.12.4",
    "eslint-plugin-react-native": "^3.6.0",
    "eslint-plugin-standard": "^4.0.0",
    "jest": "^24.9.0",
    "metro-react-native-babel-preset": "^0.56.0",
    "prettier": "^1.16.4",
    "react-native-rename": "^2.4.1",
    "react-test-renderer": "16.9.0"
  },

babel.config.js
module.exports = {
  presets: ['module:metro-react-native-babel-preset'],
  plugins: [
    ['@babel/plugin-transform-flow-strip-types'],
    ['@babel/plugin-proposal-decorators', { legacy: true }],
    ['@babel/plugin-proposal-class-properties', { loose: true }],
    ['@babel/plugin-transform-runtime', {}],
  ],
};

.eslintrc
...
"parserOptions": {
    "parser": "babel-eslint",
    "ecmaVersion": 2018,
    "ecmaFeatures": {
      "jsx": true,
      "modules": true,
      "legacyDecorators": true
    },
    "sourceType": "module",
    "useJSXTextNode": false
  },
...

The example screen to use decorators
...
@inject('counter')
@observer
class ExampleScreen extends React.Component {
...
}

The errors

babel-eslint@<11 doesn't read your Babel config. Please use the latest prerelease version of babel-eslint@11.

babel-eslint@<11 doesn't read your Babel config. Please use the latest prerelease version of babel-eslint@11.

Hello @kaicataldo ,
I tried to use babel-eslint@11, it doesn't work.

If you could make a repo with a minimal reproduction case, that would be really helpful.

If you could make a repo with a minimal reproduction case, that would be really helpful.

Yes, here's the repo

parser should be a sibling of parserOptions.

parser should be a sibling of parserOptions.

@kaicataldo Thank you! It works now, sorry for my misplacing the parser

Glad you got it working :)


change mount options for performance gain

following the advise found in this article, i changed the mount options accordingly. This gives me way faster results when polling for file-changes inside a container.

Like ten times faster for a container running webpack with source code mounted as volume :+1:

Unfortunately when I try this my sbt build runs about 3x slower

Hey,
This is a tricky change. As you can see it's not a "one setting rules it all" ... I'd be more in favor of providing a command line option to override this (e.g. --mount-opts=xxx).
I already had in mind of having a configuration file located in the user dir (e.g. ~/.docker-machine-nfs.config) in order to be able to define your own defaults which avoids a user to always have to provide through the command line.
What ya think? :)
Cheers

I think to have an option also on the side of boot2docker and not only on the host side makes, sense, but we should still have sensible defaults. Please also refer to https://github.com/mitchellh/vagrant/issues/4204#issuecomment-49856008 where a user took the time to test a set of different options.
For now I just patched my personal docker-machine-nfs to include exactly the options that were also provided in this pull request and the performance has greatly improved.

@alexex I completely agree that we should have the most performant default mounting options. I could accept this and see how it goes ... but I still think we should be able to override them without having to change the code base or patch manually like you did :)
Let me try out those and if I don't find any issues I'll merge this.
Thanks for the feedback.
Cheers

@chrisdostert On your machine it works faster with the current default values? So if I merge this config it will not suit you at all?!

I got
sudo mount -t nfs -o noacl,async,actimeo=2 ...

from https://github.com/gulpjs/gulp/issues/448 and it works well for me (for a gulp watch).

+1 Wold like the option to mount with actimeo=2

This is fixed with #45


SqlClient PlatformNotSupported_DataSqlClient

Very excited about this app! Went ahead and installed it on my x86 mac running macOS 13.4.1 with dotnet version 6.0.301 and efcore tools 7.0.9. I'm able to connect to my local Sql Server running in a docker container and can view the db schema in the left hand pane. When I try to run a LINQ query against that database I get the following error. Have I not configured things correctly somehow?
System.PlatformNotSupportedException: Strings.PlatformNotSupported_DataSqlClient
   at Microsoft.Data.SqlClient.SqlConnectionStringBuilder..ctor(String connectionString)
   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerConnection.<>c.<get_IsMultipleActiveResultSetsEnabled>b__7_0(String cs)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerConnection.get_IsMultipleActiveResultSetsEnabled()
   at Microsoft.EntityFrameworkCore.SqlServer.Query.Internal.SqlServerCompiledQueryCacheKeyGenerator.GenerateCacheKey(Expression query, Boolean async)
   at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.Execute[TResult](Expression query)
   at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryProvider.Execute[TResult](Expression expression)
   at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryable`1.System.Collections.IEnumerable.GetEnumerator()
   at O2Html.Common.LazyEnumerable.Enumerate[T](IEnumerable collection, Nullable`1 maxItemsToEnumerate, Action`2 action)
   at O2Html.Converters.CollectionHtmlConverter.Convert[T](T obj, Type type, SerializationScope serializationScope, HtmlSerializer htmlSerializer)
   at O2Html.Converters.CollectionHtmlConverter.WriteHtml[T](T obj, Type type, SerializationScope serializationScope, HtmlSerializer htmlSerializer)
   at O2Html.HtmlSerializer.Serialize[T](T obj, Type type, SerializationScope serializationScope)
   at O2Html.HtmlConvert.Serialize[T](T obj, HtmlSerializerSettings htmlSerializerSettings)
   at NetPad.Html.HtmlSerializer.Serialize(Object output, String title, Boolean isError)

Thank you for reporting this issue. I don't think that's anything you're doing incorrectly, I'll look into this. Out of curiosity do you see the same issue if you use v0.4.0?
Glad you're enjoying the app!

I found the issue, there are MS SQL specific assemblies missing from the Mac build. I will release a hotfix release soon.

Until the hotfix is released, to immediately fix this issue, extract this and copy the Assets folder to /path/to/NetPad.app/Contents/Resources/bin
MissingAssemblies.zip

Thanks for digging into this!


ZTL issues arising from duplicate BBLs in DTM

Per discussion with @caseysmithpgh and @jackrosacker
New logic in #171 updated some rankings of zoning districts by bbl based on aggregation. There are a couple odd edge cases where it seems there are multiple entries for bbls in dtm. Due to the way the aggregation/ranking of zoning districts logic is written, we're getting (extra) duplicate rows for bbls as well as duplicate rankings.
So if bbl 1 appears twice and should be zd1 = R5 and zd2 = Park (zd3, zd4 both empty), what we're seeing is

bbl
zd1
zd2
zd3
zd4

1
R5
R5
Park
Park

1
R5
R5
Park
Park

1
R5
R5
Park
Park

1
R5
R5
Park
Park

We don't want to remove the duplicate bbls, since that's coming from dtm. However, we do want to remove the extra rows and duplicated zoning districts
Other random notes

2050340001 has second district that doesn't seem to be above threshold
2028650160

So we actually do remove duplicates in dtm, with the following query
    SELECT
        bbl,
        COALESCE(boro::text, LEFT(bbl::text, 1)) AS boro,
        COALESCE(block::text, SUBSTRING(bbl::text, 2, 5)) AS block,
        COALESCE(lot::text, SUBSTRING(bbl::text, 7, 4)) AS lot,
        ST_MULTI(ST_UNION(ST_MAKEVALID(f.geom))) AS geom
    FROM dof_dtm AS f
    GROUP BY bbl, boro, block, lot

The issue here is that we have some of these "duplicates" where they have same bbl but different borough, block, or lot. Specifically lot

I think the fix is implemented, we can check the outputs tomorrow. But just given the specific example of this behavior, I wanted to raise the question on if we want to re-evaluate how we're grouping the dtm. @AmandaDoyle ?

Oh my.  How is what looks like it would be<PHONE_NUMBER> becoming 415905003 (or vice versa)?  We do need to group the dtm, but if the current way is causing unexpected issues, let's revaluate.  Maybe it's only grouping by BBL?

So per what we discussed earlier, it'd potentially be desirable to leave the current grouping, but just make sure that code runs smoothly (zoning district assignment doesn't get messed up by duplicate bbls, which is what @caseysmithpgh saw originally).
To actually address the root issue in dtm, if that's what we want to do, we could either

group by only bbl, derive boro block and lot from bbl. However this throws away the data we have that differentiates these two rows. If they refer to different footprints, they'd just get unioned
have some sort of special logic if bbl and provided boro, block, and lot don't match up. Override bbl with boro+block+lot if they're provided? But obviously, does the opposite a bit

If any of those fields being off is really a dtm issue that we don't want to be overly specific about trying to correct, then we can just do neither and report issues like this


Dropbox settings cannot be adjusted

Steps
1. Visit your user settings, scroll down to Dropbox
2. Clicking "Delete Access Token"
OR
1. At the top of your user settings page in "Select Addons", de-select "Dropbox" and submit your change.
Expected
1. Dropbox token should be deleted, allowing the user to click on "Create Access Token"
2. No projects should be listed as "authorized projects"
3. No projects should have Dropbox files listed in them.
OR
1. Dropbox should be removed as an add-on, meaning no settings are listed below in the "Configure Add-ons" section.
2. No projects should have Dropbox files listed in them.
Actual
1. When visiting the Dropbox settings, there is text alerting me that my settings cannot be retrieved:
![screen shot 2015-01-23 at 11 03 29 am](https://cloud.githubusercontent.com/assets/4965832/5877760/d95f4ac2-a2ef-11e4-9c2e-17ebb814e3fc.png)
2. Clicking on "Delete Access Token" produces an error that says that it could not be deleted:
![screen shot 2015-01-23 at 11 06 36 am](https://cloud.githubusercontent.com/assets/4965832/5877773/f2f8d872-a2ef-11e4-9412-49bb4e0eee76.png)
3. Dropbox files cannot be accessed by the OSF. Below is an example of a folder that I have confirmed does have the displayed path on my computer, and does contain files:
![screen shot 2015-01-23 at 11 11 49 am](https://cloud.githubusercontent.com/assets/4965832/5877871/b4abeee6-a2f0-11e4-8b28-05b983466fd2.png)
OR

A pop up notifies me that the request failed and that Dropbox could not be removed at this time:

Dropbox files cannot be accessed by the OSF.

I have been able to successfully log out and into Dropbox from the website, and the app appears to be working correctly on my computer.

@jlcohoon Is this issue live / on Production?

yes

TY! Might not be a "bug" per se, but rather a need to clarify expected action after deactivating a DropBox Add-On -- I have label'd as "Bug: Production" with "Discuss" -- and we'll move this forward.

As a followup to this, not all of my Dropbox-connected projects are displaying in my user settings. The ones shown below are only a few of the ones that I have connected. I assume this is because the OSF isn't able to properly connect with DropBox at the moment.

Because of the interaction between this and #1583, we are trying removing all of the projects from the project setting page, then when they are all gone deleting the access token from the user account, then reapplying everything. If this works, this is obviously not how it should. It would seem that there's a bug in there somewhere.

There's an error on sentry. https://sentry.osf.io/osf/production/group/1705/
website/addons/dropbox/utils.py Line 55:
'folder': self.node.get_addon('dropbox').folder
Attribute error: 'NoneType' object has no attribute 'folder'

In the meantime, this leaves @jlcohoon unable to use Dropbox on her production projects.

Looking into this

I just deauthorized the OSF via Dropbox. My OSF user settings are still saying that they can't connect and are still not allowing me to delete the token.

OK, found the root cause of this: When creating a "node_deauthorized" log for all a user's Dropbox-authorized nodes, we weren't accounting for DropboxNodeSettings records that had the deleted field set True. This resulted in the AttributeError seen by Sentry.
Once the CI build passes, will merge the hotfix.


Upgrade Scala3 to 3.3.1

looks like overly sensitive test expectations that just need adjusting?

It looks like the Compare helper isn't working on Scala 3.3.1.
For the assertion
assertEquals('a', 'a'.toInt)

We used to have something like:
error:
Can't compare these two types:
  First type:  Char
  Second type: Int
Possible ways to fix this error:
  Alternative 1: provide an implicit instance for Compare[Char, Int]
  Alternative 2: upcast either type into `Any` or a shared supertype.

Followed by some additional text about implicits if on Scala 3.1.
But now we have just:
error: missing argument for parameter compare of method assertEquals in trait Assertions: (implicit loc: munit.Location, compare: munit.Compare[Char, Int]): Unit

Which seems like a regression.
I think we want to actually try and restore the old behaviour.

Already updated in main


Failed XSS Attempt at https://wiki.developer.mozilla.org/zh-CN/docs/MDN/Feedback

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details

There's code that seems to be a failed (not successful; not vulnerable to the user) XSS attempt in the zh-CN MDN wiki page Array.prototype.map(), specifically at https://wiki.developer.mozilla.org/zh-CN/docs/Web/JavaScript/Reference/Global_Objects/Array/map#See_also . Please refer to the screenshot below.

By checking the history records of the wiki page, it seems the change comes from Revision 1616575 (diff), which is committed by an user named Jayly.
Side Notes
I don't have much of the skill about analyzing malicious JavaScript scripts, but by doing a quick search of cookie and http in the script billyjons.net/21db1c5c8b372aecca.js it seems that it is a real XSS script that might send information including Cookies in browser to the attacker, and may also contain other credentials. This behavior is quite uncommon and suspicious so I decided to report it here ;)

Affected Page(s)

Array.prototype.map()#相关链接

Thanks! I removed the failed xss attempt and banned the user.


Add verifySsl option #64

Allows to disable the ssl verification for remote repo

Is there anything missing or something to improve to enhance the pull request?


Script arguments containing ':' are truncated

I need to pass an argument containing a URI.
The line got truncated due to parseNameAndValue of src/action.ts (line 63) splitting the line on ':' (without limit) and then only using the first two entries in the result.
e.g.:
arguments: |
address: https://somewhere/something

Resolved in d2188bf.

Released in version 1.4.1. 🎉