Autocomplete/Dropdown - multi select

I have a problem, because I have to use multi select in my application, but in dropdown I can't make multi-select and make box (tags) of selected elements above input, because dropdown can't be multiple. Autocomplete can be multiple, but after each click, the select is hiding... User has to click to open select for each click (open select and find value - it's problem when it's more than a few elements).
Can you help me?

Exactly, this should be solved with #174


Add vertical swing mode swing (constantly moving up/down)

My Panasonic HZ25XKE has a vertical swing mode where the flap constantly swings up/down (like in auto, except that in auto "Once the temperature is achieved, the horizontal flap is fixed at upper position"). I get an error in the log when this mode is selected:
[23:25:30][V][panasonic_ac:245]: TX: 70.0A.<IP_ADDRESS>.<IP_ADDRESS>.00.00.86 (13)
[23:25:30][V][panasonic_ac:247]: RX: <IP_ADDRESS>.80.A0.ED.<IP_ADDRESS>.00.4C.<IP_ADDRESS>.<IP_ADDRESS>F.18.01.FF.80.80.FF.<IP_ADDRESS>.<IP_ADDRESS>D (35)
[23:25:30][W][panasonic_ac.cz_tacg1:374]: Received unknown vertical swing mode
[23:25:30][E][select:018]: 'Panasonic Vertical Swing Mode': invalid state for publish_state(): Unknown

The value of this mode is found by logging to be 0x0E.

Will test this over the weekend, thanks.

Does your AC have both an auto and a swing mode? Can you post a picture of your remote?

Remote auto:

Remote "swing":

Thanks! Didn't cause any issues on my units.


Set supported python version to >=3.9 - 113

[Auto generated]
Number: [#113]

python-simple-logger[pull_request][9b72-11ef-915a-092f0addae1e][PR 113]: Closing issue for PR: Set supported python version to >=3.9.
PR was closed.


[ffmpeg] enable a feature to support libpng

updates ffmpeg port to enable the optional libpng feature for libpng based encoders/decoders

[x] Changes comply with the maintainer guide
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Thanks :)

Another feature named like the dependency, not like the actual feature...

@dg0yt it makes sense what you say. And had I seen this before the PR got merged I'd have definitely changed it.
Not sure if we should still do it now though...

I think it is okay to leave it as is now (next to mp3lame ;-)
But I wish the official reviewers would pay more attention to this before approving. It is about designing long-lasting interfaces.

Another feature named like the dependency, not like the actual feature...

I have been paying attention to this but libpng sounded like the actual feature to me :shrug: . I guess just 'png' would have worked.


Code Helper using almost 100% CPU

how to fix this bug?

Please read the article at https://github.com/microsoft/vscode/wiki/Performance-Issues for advice about how you can investigate your problem.

how to fix this bug?


o1 cannot response when it think for a long time

Bug Report
Installation Method
Docker
Environment

Open WebUI Version: v0.3.32

**Operating System:**Windows 11, WSL2

Confirmation:

[ ] I have read and followed all the instructions provided in the README.md.
[ ] I am on the latest version of both Open WebUI and Ollama.
[ ] I have included the browser console logs.
[ ] I have included the Docker container logs.
[ ] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:
I can see the response.
Actual Behavior:

The log say that i got a timeout.
Description
Bug Summary:
If you ask a long or hard question, o1-mini may have to think for a long time. And you will get an error of timeout while the api work normally.

Api says that it need 84s, so i got a timeout.
Reproduction Details
Steps to Reproduce:

Answer o1 a quetion need a long time to response.

Logs and Screenshots
Docker Container Logs:
"POST /api/chat/completions HTTP/1.1" 504 Gateway Timeout

Same problem. I find that there exists a environment variable AIOHTTP_CLIENT_TIMEOUT, but I'm not sure if it refers to this timeout settings.


Fix UTF8 in JS getChar

The way getChar was implemented in JS was not matching the native implementation. The native version return a codepoint, the JS version was supposed to do the same (using a construction called .codePointAt), but it was not working on some utf8 encoded examples (for reasons that I don't understand).
This diff mimics the logic that we have natively. It would be probably worth revisiting at some point, because it would be nicer to use JS primitives to do the work, but it's not urgent. Let's fix our JS first.
The diff also includes tests on utf8 strings to make sure we don't regress.

Thanks guys!

It would be probably worth revisiting at some point, because it would be nicer to use JS primitives to do the work, but it's not urgent. Let's fix our JS first.

I pulled this down and played around. #113 seems to work for me locally. I'll check CI. LMK if you have concerns.


Update Mathoid to service-template-node v0.1.3

Brings a lot of bug fixes and improvements, yey :)

/cc @physikerwelt

@d00rman: Do you see an option to fix the integration tests. Disabeling PNG comparison is fine for me.

Do you see an option to fix the integration tests.

Yeah, that's a rather hard one. Perhaps in the tests use the underlying lib to produce the png, then issue the request to Mathoid and expect the outputs to match literally? It seems the usage of different libs/versions is the underlying problem in image discrepancies.

Disabeling PNG comparison is fine for me.

We could do that for now and think of a better way in the future as having tests that we know fail doesn't seem to be too useful :)

I checked it to the very best of my knowlege. However, I did no do an explicit code review... I expect that the template code already was reviewed in its repository. For the future, it would be nice to deduplicate that code... mathoid implements mwSrvTmpl


KAFKA-14965 - OffsetsRequestsManager implementation & API integration

Implementation of the OffsetRequestsManager, responsible for building requests and processing responses for requests related to partition offsets.
In this PR, the manager includes support for ListOffset requests, generated when the user makes any of the following consumer API calls:

beginningOffsets
endOffsets
offsetsForTimes

All previous consumer API calls interact with the OffsetsRequestsManager by generating a ListOffsetsApplicationEvent.
Includes tests to cover the new functionality and to ensure no API level changes are introduced.
This covers KAFKA-14965 and  KAFKA-15081.

Thank you @lianetm - I left a couple comments regarding logging level.  Otherwise it looks good.

Thanks @junrao , @philipnee and @kirktrue for all the helpful comments. All addressed!

Thanks for all the comment @junrao . All addressed. (I'm keeping an eye on the build and will update relevant results here)

Build completed with 10 unrelated test failures (mainly due to unexpected threads found before running them & timeouts):
Build / JDK 20 and Scala 2.13 / initializationError – org.apache.kafka.tiered.storage.integration.OffloadAndConsumeFromLeaderTest
Build / JDK 17 and Scala 2.13 / testLegacyAlterConfigs() – kafka.server.KRaftClusterTest
Build / JDK 17 and Scala 2.13 / testBalancePartitionLeaders() – org.apache.kafka.controller.QuorumControllerTest
Build / JDK 17 and Scala 2.13 / initializationError – org.apache.kafka.tiered.storage.integration.OffloadAndConsumeFromLeaderTest
Build / JDK 8 and Scala 2.12 / testReplicateSourceDefault() – org.apache.kafka.connect.mirror.integration.MirrorConnectorsIntegrationExactlyOnceTest
Build / JDK 8 and Scala 2.12 / testBalancePartitionLeaders() – org.apache.kafka.controller.QuorumControllerTest
Build / JDK 8 and Scala 2.12 / initializationError – org.apache.kafka.tiered.storage.integration.OffloadAndConsumeFromLeaderTest
Build / JDK 11 and Scala 2.13 / testBalancePartitionLeaders() – org.apache.kafka.controller.QuorumControllerTest
Build / JDK 11 and Scala 2.13 / initializationError – org.apache.kafka.tiered.storage.integration.OffloadAndConsumeFromLeaderTest
Build / JDK 11 and Scala 2.13 / testTaskRequestWithOldStartMsGetsUpdated() – org.apache.kafka.trogdor.coordinator.CoordinatorTest

KAFKA-15399 - Chris L. mentioned that he fixed the OffloadAndConsumeFromLeaderTest issue, but apparently we are still seeing it on trunk. I replied the thread.

The failure they were after with that fix seems different to this though, here is about hanging threads on the base QuorumTestHarness, so I would say it is not specific to the OffloadAndConsumeFromLeaderTest (it happened to be the one finding the hanging threads before starting I expect). I think there is ongoing work in AK for finding the tests leaving hanging thread (will double check on the issues)

Implementation of the OffsetRequestsManager, responsible for building requests and processing responses for requests related to partition offsets.
In this PR, the manager includes support for ListOffset requests, generated when the user makes any of the following consumer API calls:
beginningOffsets
endOffsets
offsetsForTimes
All previous consumer API calls interact with the OffsetsRequestsManager by generating a ListOffsetsApplicationEvent.
Includes tests to cover the new functionality and to ensure no API level changes are introduced.
This covers KAFKA-14965 and KAFKA-15081.
Reviewers: Philip Nee<EMAIL_ADDRESS>Kirk True<EMAIL_ADDRESS>Jun Rao<EMAIL_ADDRESS>


feat(binding_macros): wasm binding macro

Description:
Partially implements https://github.com/swc-project/swc/issues/5395.
This PR attempts to explore possibility to swc_core exposes set of builder macro to create binding functions for the SWC's features. As a first step, PR replaces all existing wasm binding implementation into naive macro-based expansion.
Key takeaway for this approach is, in most cases if someone wants to customize SWC's behavior to create custom binary they'll likely need few customization points only. For example, transform*'s before / custom_pass is what ppl mostly need if they want custom SWC binary, but it still requires to repeat existing codes compare to SWC's binding those. Macro tries to accept those as customizable param, and then scaffold boilerplate instead.
binding_core_wasm in result gets thinner dependency tree - it only needs swc_core and wasm-bindgen (TBD to remove this even or not). Custom binaries like next-swc can be the same instead of keep redundant code inside.
This born from internal need of discussions and I think it has some usecases, but the way it's implemented maybe debatable. Reason I started from simpler wasm binding first.

BREAKING CHANGE:

Related issue (if exists):

I'm not sure how much people will build a custom binary, though

Primary usecase (for now) is reduce repeated code between next-swc, and I guess that'll be suffecient win.
Once next-swc does bump for the SWC next time, we may able to try this.


Jinja template does not work for superset 2.1.1

I install superset 2.1.1 following the next steps:
git clone https://github.com/apache/superset.git
git checkout 2.1.1
TAG=2.1.1 docker compose -f docker-compose-non-dev.yml pull
I also change
DEFAULT_FEATURE_FLAGS: {
...
"ENABLE_TEMPLATE_PROCESSING": True,
...
}
in superset/config.py
TAG=2.1.1 docker compose -f docker-compose-non-dev.yml up -d
Expected results
SELECT '{{current_user_id()}}'
or
SELECT {{current_user_id()}}
should return a number
Actual results
SELECT '{{current_user_id()}}'
return the literal '{{current_user_id()}}'
without the quotes
SELECT {{current_user_id()}}
the result is:
PostgreSQL Error
Please check your query for syntax errors at or near "{". Then, try running your query again.

Try:
FEATURE_FLAGS = {
    "ENABLE_TEMPLATE_PROCESSING": True
}

You have a colon, not an equals sign.

I'm going to close this as it appears to be the case of a simple typo.  If that's not the case and you believe there's a bug in the Superset codebase, please feel free to reopen.

Try:
FEATURE_FLAGS = {
    "ENABLE_TEMPLATE_PROCESSING": True
}

You have a colon, not an equals sign.

Sorry, I copied it wrong in the question, it's always been like this.
DEFAULT_FEATURE_FLAGS: Dict[str, bool] = {
...
}
The error was that I was editing DEFAULT_FEATURE_FLAGS in superset\config.py
And seeing that you have responded by editing FEATURE_FLAGS, I have edited FEATURE_FLAGS in docker\pythonpath_dev\superset_config.py and it worked. Thank you.


Functions for restoring tables or individual rows

Illustrate how to restore things from the history table.

Prototype query here: https://github.com/simonw/sqlite-history/issues/1#issuecomment-1501013505


How to inject the scripts from page

The HTML page has the script as below:
<script src="/_res/js/jquery.js" type="text/javascript"></script>
<script src="/WebResource.axd?d=5At4BVuSsWGYDY9lb87tCvy" type="text/javascript"></script>

On onResourceRecevied function, i can see above script downloaded successful.
Then i inject them to page :
page.injectJs('/_res/js/jquery.js').then(async function(res) {
          console.log("injectJs")
        page.injectJs('/WebResource.axd?d=5At4BVuSsWGYDY9lb87tCvy').then(async function(res) {
            console.log("injectJs")
        })
})

The console logged "injectJs" but i can not call the any function on that script files.
I inject wrong path file or i have to use includeJs instead?
Thanks

injectJs runs inside phantomjs process. So you should probably do
page.injectJs('/_res/js/jquery.js').then(async function(res) {
          console.log("injectJs")
})

 page.injectJs('/WebResource.axd?d=5At4BVuSsWGYDY9lb87tCvy').then(async function(res) {
            console.log("injectJs")
        })

Also your use of async seems to be incorrect.  page.injectJs returns a promise. You'll have to figure out the correct syntax.

Because i want to inject all scripts before working on the page e.g: fill data or submit.
The issue i got is the path for these scripts seem to not correct, i'm not sure i should use relative or absoluate url for these scripts. Can you help to explain more? Thanks


Update README.md to change the word truthy to true

Changed truthy to true

"Truthy" is the intended word here. https://developer.mozilla.org/en-US/docs/Glossary/Truthy


:bug scroll bar is not updating its position in examples when scrolling

In following examples scroll bar does not update its position when using mouse-wheel or touch pad: "With JSON Data", "Fluid column widths", "Resizable columns", "Column Groups".
Browser: Chrome Version 43.0.2357.124 m

Hi! Thanks for bringing this up. The examples on the site will be working again soon, there has just been a small hiccup with a recent commit.

@skmasq things should be working again. The site publishing script happened to pick up a few of my local changes by accident, sorry about that!

@ehzhang  Thank you, cheers!


Release of pre-trained weights?

Thanks so much for this amazing new model.
I was wondering if you would be able to release some of the pre-trained weights behind these core benchmark datasets?
I pointed some colleagues to your paper and repo to show them what the SOTA was in this area, and couldn't easily point them to a collab notebook, or huggingface demo, or even build our own hosted demo to show them.
Love your work, please keep up the great work!

Have you reviewed the Readme file ?
we provide reproduction code for all the main results of the paper (single-label, multi-label, ZSL).
we can surely release pre-trained weights, but letting people validate our results via actual reproducible code is better, we think

Hi, yes I've read the README and your paper too. I love how you got rid of the self-attention layer. That was was a big problem with the query2label model.
I guess there are multiple users of your work?
There are fellow researchers who are trying to replicate your work, and build on your ideas, and what you've provided for reproducibility is fantastic.
However, there is another class of customer of your work who would just like to pick and up and try to use your work directly in their applications.
So, asking them to download the entire COCO dataset and train a model is a significant barrier. (At least hours of work for someone experienced).
I do note there are ZSL options as well to get people started. But even providing some weights will enable that community and users to build collab notebooks, hosted demos to showcase your excellent work, and upload it to sites like huggingface, etc, as well as increase the visibility of your work.
Anyway, if you were able to share this in some way that would very much appreciated by not only my team, but I'm sure thousands of others who would like to quickly evaluate your work, or use it directly in a ZSL context.
Amazing work again!

ok, i am convinced :-)
will share some model pre-train weights next week

Thank you so much 🙇 ! I really appreciate it!

i have added example models and inference and validation code
enjoy :)

Thank you. This is amazing!


Update design system to version 30.0.0

This is an auto-generated PR.
Design system release: https://github.com/ONSdigital/design-system/releases/tag/30.0.0

Superseded by https://github.com/ONSdigital/eq-questionnaire-runner/pull/480

Superseded by https://github.com/ONSdigital/eq-questionnaire-runner/pull/480

Superseded by https://github.com/ONSdigital/eq-questionnaire-runner/pull/480

Superseded by https://github.com/ONSdigital/eq-questionnaire-runner/pull/480


fix: formatting and punctuation in blog files

Description

format blog correctly according to https://github.com/DavidAnson/markdownlint
Related Tickets & Documents

closes #425
Mobile & Desktop Screenshots/Recordings

Steps to QA

Tier (staff will fill in)

[ ] Tier 1
[ ] Tier 2
[ ] Tier 3
[ ] Tier 4

[optional] What gif best describes this PR or how it makes you feel?

Refer to this comment for the reason of PR closing.

@adiati98 i created and linked the proper issue, feel free to reopen when approved


Improper alignment of pictures in the "Featured" section

Issue:
The pictures in the "Featured" section are not properly aligned, with no spacing between images and excessive space around them, resulting in an unbalanced layout.
Expected Behavior:
The images should be properly aligned with consistent spacing between them and minimal space around the outer edges.
Screenshot:

GSSoC Contributor: Could you please assign this issue to me under GSSoC'24 extended?

@18Prachi You can start working on it, feel free to reach out if you have any doubts


[Feature Request]: Add Groq to model providers

Is there an existing issue for the same feature request?

[X] I have checked the existing issues.

Is your feature request related to a problem?
No response
Describe the feature you'd like
Add Groq to model providers
Describe implementation you've considered
Just like Ollama or XInference are used to manage the load of models
Documentation, adoption, use case
No response
Additional information
No response

#1447

@JinHai-CN & @KevinHuSh
Should I add support for Gemini APIs to model providers in the same pull request, or should I create a new pull request for it ?


feat(zk): add zk query

Implement the ProverQuery and VerifierQuery used in the proof generation process.
(See https://github.com/kroma-network/halo2/blob/dev/halo2_proofs/src/poly/query.rs.)

feat(zk): implement ProverQuery and VerifierQuery points to the same link with a different title

Please remove the CommitReference something from commit body


Spectrogram (image)-to-wav

Dear Authors and reader
I would appreciate it if you would give me an answer to my question:
Is it possible to convert the spectrogram image (not the array) to wav (reconstruct the wav audio from the spectrogram in image form)?

Yes, sure. It possible.

Dear Authors and reader I would appreciate it if you would give me an answer to my question: Is it possible to convert the spectrogram image (not the array) to wav (reconstruct the wav audio from the spectrogram in image form)?

https://github.com/magicse/ncnn-hifi-GAN


When doing authentication and redirect to ms login, get CORS error

Access to XMLRequest at ms login from origin null has been blocked by cors policy.
What is wrong with it?

Sorry no idea. Do you have any more information you can share on the error?

Closing due to lack of response.


Prepare release

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>9:
0.0%

Covered Lines:
824

Relevant Lines:
824

💛  - Coveralls


Your request to provision "Microsoft 365 learning pathways"  template failed!

Describe the issue
Tried to provision the M365 learning pathway via LookBook and get the above message.
Expected behavior
The template to be deployed successfully.
Screenshots
If applicable, add screenshots to help explain your problem.
Details (please complete the following information):
Correlation ID: 38fdf273-7013-4dc7-b715-7d2f2891ab37

Reference Template: https://lookbook.microsoft.com/details/3df8bd55-b872-4c9d-88e3-6b2f05344239
Primary language of the target tenant: English
Are you using a Tenant Global Admin account to provision the template: Yes

Additional context
I have removed the tenant level Enterprise Application from Azure, deleted the app from the Catalog site and tried again with the same result.
I did have an old v2 version of the learning pathways, and have deleted that site and the app before trying to install the new v4 version (I wasn't worried about keeping any of the old stuff).

I've checked this morning, and the site was created, but some of the menu options are in a foreign language:

And there seem to be a bunch of menu options missing.
I have installed Learning Pathways in a different tenant successfully this morning, so there must be something specific to this tenant that is causing it to fail/behave strangely.

Is there anyone looking at these issues and able to assist with them?

Hi,
Thanks for using the Look Book site. Inspecting the event log, we can see - based on the provided Correlation ID - that there was an exception while provisioning the navigation of the site. It is an uncommon issue. Considering that you were able to provision the template onto another tenant, what kind of tenant is this? Is it a demo tenant for partners? Thanks for your cooperation.

The tenant with the failure is my employers tenant. The successful tenant is my personal one. There are no demo/partner tenants.

Is this still being investigated?

Hi,
We've recently seen some provisioning processes failing during the creation of the navigation nodes. We're investigating the issue and we will eventually fix it, in case it depends on our codebase. Stay tuned. Thanks for your cooperation.

Hi,
Thanks for your patience. We've just updated the provisioning service with several fixes. Hopefully, this one is now solved or at least mitigated. Please try again and let us know in case of any further issues. Thanks for your cooperation.


new DLC items

Can items from DLC The Forgotten Kingdom be added?

Yep

They are now added. I will push the nuget packages later.


feat(compatibility): remove conflicts with material1 css styling

LGTM if this is identical to previous PR

Should be identical, good sign that tests pass. Dev site looks good to me as well.

LGTM

@andrewseguin as far as I can see, this needs to be reflected in the material.angular.io site? Specifically https://material.angular.io/guide/theming

It sure does, thanks for the callout. Will be fixed in #3013

The md- prefix is staying for components and directives, unless you turn on compatibility mode which forces you to use mat- for component and directive selectors. This is to allow projects to upgrade from AngularJS Material (1.x) to Angular Material (this version) without having their directives and styling collide.
In general, the rule going forward is that styling will be prefixed by mat- and selectors will be prefixed by md-.

Could you use semantic version on npm package for this update? Although the library still giving support to the directives with the same name, the css styles, scss mixins and variables doesn't have backward compatibility. It crashes the code of whom is reusing the mixins and variables for customize the styles of Material Design.
In this case, the most appropriate should improve the MAJOR on semver, that is better than just change from 2.0.0-beta.1 to 2.0.0-beta.2.

This is inconsistent. You should rename all components to mat- as well then.

it worked for my styles thanks.


Generating noisy data

How exactly can we generate a noisy data from clean and noise data, Which is the exact script to do that.
Got error as
FileNotFoundError: [Errno 2] No such file or directory: 'datasets\acoustic_params\RIR_table_simple.csv' when using noisyspeech_synthesizer_singleprocess.py
Am I using the right script to generate noisy data

You can download the file from the git history:
https://github.com/microsoft/DNS-Challenge/tree/0443a12f5e6e7bec310f453cf0d9637ca28e0eea/datasets/acoustic_params


Can you provide a grey Orange theme

Can you provide a grey Orange theme
grey_orange.zip

Can try.
Where can I launch this theme?
I didn't find where ".icle" format is used.

I understand, how to start it.
I can do this, but the theme itself is dark.
It is better to do it separately. It makes more sense.
I have only light information in my package.
I'm sorry, but I won't do this.
I made this theme because I use it and I like it.
Grey orange theme I'm not sure what I'll use.  : ||

Icls just import the theme on WebStorm, you can try it, if you really like it

Unfortunately, this will take a long time.
There are quite a few good dark themes.
Orange
https://github.com/raxjs/rax-vscode-extensions
Standard Dracula for example.
https://github.com/kevinvn1709/vscode-dracula-color-theme
If you want to make a theme to match your colors, I can send you good guides.


fix: cUrl target should encode x-www-form-urlencoded post data params

Closes #197

I'm encoding the key using encodeURIComponent (here).
I'm wondering if we should use it for the value or keep using --data-urlencode to let cUrl encode the value automatically. 🤔

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I came across this issue as well, but I'd argue that we should only be url-encoding values that require quoting. For example, the curl snippet output should look something like this where the values that required quoting are the ones passed using --data-urlencode.
curl --request POST \
  --url http://localhost/oauth/token \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data grant_type=password \
  --data client_id=XXXXXXXXXXXXXXX \
  --data-urlencode 'client_secret=sdhoisDDSHOIDHs/++SDOIhoDSHOIDHS' \ # made up
  --data username=foo \
  --data-urlencode 'password=P@$$w0rD'

This is working correctly for me on the CLI

thanks @bbbco for the heads-up.  I was thinking the same exact thing when I was reviewing this.  I went ahead and fixed it like you've suggested in https://github.com/Kong/httpsnippet/pull/198/commits/f2c115545f15f3a96df44cfd2acfa4ecef7c876a.


Implement Dockerfiles for both the agent and the server

#107
Implements Dockerfiles for the agent and server. These docker files efficiently use Docker's layer caching so that changes in the code don't require the entire image to be rebuilt. Additionally, these images do not include many unneeded dependencies.

Should port the makefile and the docker-compose.yaml over from my PR. this will allow devs  and production users to have a repeatable stack.


fixed some issues causing asm not to be compiled

Oops!

Ok I pushed a fix which should make it always compile. I also consolidated the conditional logic in build.rs to make it easier to audit. Thanks for bringing this to my attention!

Ok, ran the bench, everything seems to be in order.


Create a video and add video link in readme file in which describe "how to Add your profile?".

hey @vijayyprajapati can i work on this ?

Go ahead @stutisk

@vijayyprajapati Hi, Since I don't see any recent update regarding this issue. Can I work on this? pls, assign this to me.

Go ahead @stutisk
But make sure to show every step. If you have any doubt feel free to ask me.

@vijayyprajapati Hi, Since I don't see any recent update regarding this issue.
Can I work on this? If @stutisk is not working on it yet?? pls, assign this to me.


fix: multi select

fix(multi select): Collapse and scroll on open fixed

I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc
I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat
Lint and unit tests pass locally with my changes
I have labeled the PR correctly with the related package
I have run visual regression tests (if applicable)
I have added tests that prove my fix is effective or that my feature works (if applicable)
I have added necessary documentation (if applicable)
Any dependent changes have been merged and published in downstream modules

Proposed changes (including videos or screenshots)

added a state variable to control visibility
stopped the scrolling of select on open state

Issue(s)
https://github.com/RocketChat/fuselage/issues/1281

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@SySagar , could you please explain what you mean by the collapse issue you mentioned? I believe there is already a pull request raised at https://github.com/RocketChat/fuselage/pull/1265 for that particular issue. Please check it out and see if it addresses the same problem you have resolved here.

Yes I check the pr earlier but it resolves only the collapse not the scrolling part
In my pr both my the problems addressed are resolved

@SySagar Yeah, that's good. Now, you can focus on the scrolling issue only, as the other problem has already been addressed. Having multiple PRs solving the same issue will result in confusion. You can remove that commit and force push.

Wouldn’t it be good if this pr closes both or I can update the other pr don’t know if that is possible

@SySagar , but that has already been addressed, right? There has been effort put into solving the issue. Having multiple PRs solving the same issue may waste others' efforts.

No worried I will force push this will that be ok?

No worried I will force push this will that be ok?

Yeah sure. Thank you for your understanding, You can also update your issue solving the scroll issue.

No worried I will force push this will that be ok?or should I update that pr of other person

You won't be able to edit PR of other person.

Hi there, thanks for the contribution! 🚀 💯
We're planning an entire replacement of all the components related to AutoComplete and all the Select components since we're focusing a lot on accessibility. Trying to maintain it became a nightmare, and because of that we're not going to accept any contributions related to these components at this time.

Questions? Help needed? Feature Requests?

Join our Open Server in the #support channel and feel free to raise a question
Join our Community Forum and search/create a post there


No documentation for the ADSyncAADCompanyFeature cmdlets

The Azure AD Connect PowerShell module provides cmdlets for managing settings such as ForcePasswordChangeAtLogOn: Get-ADSyncAADCompanyFeature and Set-ADSyncAADCompanyFeature. However, these cmdlets are not documented anywhere.

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

ID: 737984d1-9a71-2472-e99b-f50871bd159f
Version Independent ID: 4b48ab78-8441-da95-d0cb-b225824e58b7
Content: Azure AD Connect: ADSync PowerShell Reference - Microsoft Entra
Content Source: articles/active-directory/hybrid/reference-connect-adsync.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@rgsteele
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Thank you for submitting this issue.  Unfortunately, due to high volumes I was unable to respond to this in a timely manner.  At this point, I am going to close this due to it's age and the possibility that it may have been addressed.  If this is still a problem, please consider submitting a new issue.  Thank you.
#please-close


customize libmapnik name inside bundled binaries

Will be good to do this in order to avoid the rare case where the bundled libmapnik.so could clash with an externally installed version - refs #262.

[x] Add option to Mapnik's build system to rename the library
[ ] Adapt the node-mapnik packaging scripts to work with custom library name

no longer seeing this as needed (have not hit any more errors that this would have prevented), closing.


No convenient way to get message without getting locked into a for loop

Use-case I need to listen to MQTT messages until I get a signal from an external non MQTT system to stop.
If I use the async for client.messages I am locked in the for loop until MQTT is disconnected or a message arrives. Neither are likely to trigger for hours or days in my scenario.
I can't client.disconnect() because that isn't implemented. Even if it did though (which I think it should) calling client.disconnect() seems wrong / excessive (it generates an MqttError after all).  There is no error. I want a graceful shutdown.
So I guess what I am proposing / have in mind something like:
import asyncio
from aiomqtt import Client, Message, MqttError

class DesiredClient(Client):
    def disconnect(self) -> None:
        rc = self._client.disconnect()
        if rc != MQTTErrorCode.MQTT_ERR_SUCCESS:
            raise MqttCodeError(rc)

    async def get_message(self) -> Message:
        task = self._loop.create_task(self._queue.get())
        try:
            done, _ = await asyncio.wait((task, self._disconnected), return_when=asyncio.FIRST_COMPLETED)
        except asyncio.CancelledError:
            task.cancel()
            raise

        if task in done:
            return task.result()

        task.cancel()
        raise MqttError("Disconnected while waiting for message")

I also looked into using the raw iterator outside the Client class but it seems wrong and is ugly
# save iterator and use it again next time
some_other_class.stored_iterator = aiter(aiomqtt_client.messages)
# of course this isn't "safe" as it doesn't watch for client disconnect and can get stuck
# and _disconnected (what I should watch to be safe) is protected / unavailable
next_message: Message = await anext(some_other_class.stored_iterator)

Hi skewty, thank you for opening this issue. 👍  Let me have a look.

Use-case I need to listen to MQTT messages until I get a signal from an external non MQTT system to stop.

Sounds like a reasonable use case.
Have you considered using task cancellation? It seems ideal for what you want to achieve. Something like this:
async def process_messages(client: Client) -> None:
    async for message in client.messages:
        ...

async with Client(...) as client, asyncio.TaskGroup() as tg:
    task = tg.create_task(process_messages(client))  # This schedules the task to run in the background
    await your_signal_arrives
    task.cancel()  # This stops the infinite loop inside process_messages

You can do something similar even without asyncio.TaskGroup (if you don't have python 3.11 or later).
Let me know if that helps you or not. :)

The log / logging messages are less useful but it works. Thank you.


Server Error by Azuriom Page by connecting to Litebans

Hi, i get an Server Error 500 by opening the url by my azuriom webpage. my entry datas are correct, can u help please

Please send the logs located in the storage/logs folder

log.txt
the website is on my webhosting provider "netcup" and i try to connect to my linux server by OVH;

The database credentials filled in the settings are not correct

i check the settings, but they are correct, 100%..

Look yourself at your logs, SQL Connection refused, so something is wrong

I'll check the firewall settings on the Linux server, maybe the IP is blocked by the web server and therefore no connection. Ty


Grash when inserting script card in wrong exporter slot

Issue type:

:bug: Bug

Short description:
Game crashes when I insert a card that executes this function into wrong slot in any exporter
function anvils() {   return [       itemByName("minecraft:damaged_anvil"),       itemByName("minecraft:chipped_anvil"),       itemByName("minecraft:anvil"),     ]; }

Steps to reproduce the problem:

make card that executes script provided above,
insert it into single item slot or predicate exporter

Expected behaviour:
Red X instead of crash.

Versions:

This mod: 1.0.6
Minecraft: 1.21.1
Mod loader version: NeoForge 21.1.72

Log file:
https://pastebin.com/KnvwzJdH

Thanks for reporting!

I haven't been able to reproduce the problem you're describing.
This should have been fixed as of https://github.com/CyclopsMC/IntegratedScripting/issues/9
Are you sure you're using the latest version of all ID mods?
If yes, could you share a video or more details steps to reproduce the problem?

https://streamable.com/ifbmeg
latest.log

Ah, it's the world item exporter. I thought it was the regular item exporter.

@Hiranus From your video, it also appears you are using an applied function (using apply3).
Could you describe the steps that were necessary to create this variable?

script0.txt
This is the script I'm using.
You can pick any function with 3 arguments. Here are some descriptions of parameters
itemsInChamber - list of items from entitiesToItemIds(entities) where "entities" is just a list of items on the floor read by entity reader
itemsToDisenchant - list of items from inventory reader
isChamberDisenchanting - boolean, you can just pass false during your testing
shouldImport*Realized - just functions with same name after running apply on them.
If you want to understand the goal of this script, here is a brief description:
Apotheosis adds disenchanting of items by dropping anvil on obsidian block that has enchanted items and books on it. Goal of this whole contraption is to automate this process. I'm checking if there are any items to disenchant and if there is anything being disenchanted. If nothing is being processed, then I drop stack of books and few items and drop anvil on it.


Fix fingerprint when bimmer_connected is installed via pip

I noticed that fingerprint doesn't work because it attempts to write the data next to where the account.py implementation is (/usr/local/...)
I've modified the code to use the current working directory.

That's strange. The fingerprint works for me in the current working directory.
Using Ubuntu 18.04 and installed bimmer_connected via pip.
I did notice that the fingerprint command doesn't work after I changed to setup.py (or maybe even before that) on a fresh install. I first thought you had a PR for that :wink:

When I did the pip install in Ubuntu, I think it assumes --user when the install is run as a regular user and put the package in ~/.local/lib/python3.5/site-packages/bimmer_connected which a regular user has access to.
In other distros, e.g. Sailfish O.S. or Ubuntu Touch -- I forget which which one it was now, pip install attempted to put the package in the dist-packages in /usr/local by default. When a regular user tries that, it fails. But if you do the install as root rather than adding the --user argument you can get the package in /usr/local which is owned by root and thus unwritable.
This also might vary for different versions of python, but I'm not clear on that from the docs.
But at any rate, local data should be written to the current user's local application data path when the package is run as user.

You're right, when bimmer_connected is installed with --user the issue doesn't happen. But it does happen when it's installed system-wide with sudo. In my opinion this a usecase that should be supported.
And even when it's installed into ~/.local/... it makes no sense that it writes into that directory. You also don't want to write into C:\Program Files\... on windows.

I did some looking around for a cross-platform method of getting the proper directory for an application to store its data in. The best match seems to be the appdirs module.  The downside is that I don't think it ships with python from the factory, but it can be installed with pip or included with the distributed project.

Keeping it open.

Hi @rikroe, would you mind reviewing this PR?
I just did a fresh install of bimmerconnected on Ubuntu 19.10 and the fingerprint indeeds uses /usr/local/lib/python3.7/dist-packages/bimmer_connected/vehicle_fingerprint for which you don't have permissions without sudo.

@swimsystems thanks for your PR.
Made a new PR #178 to fix the conflicts and CI failures. The data of fingerprint will be stored in the home dir.


Fix HMR in client components

Description
Closes #39
Closes #1793
Modifying client components was triggering a full page refresh because Vite was invalidating modules used in the server during SSR. This PR filters the modules Vite invalidates to only include browser files.
cc @await-ovo Thanks for all the research!

Before submitting the PR, please make sure you do the following:

[x] Read the Contributing Guidelines
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123)
[ ] Update docs in this repository according to your change
[x] Run yarn changeset add if this PR cause a version bump based on Keep a Changelog and adheres to Semantic Versioning

Right now the HMR test cases in the repository only seem to cover reloads

That's right. It should now check the local counter state 😄

I've created https://github.com/Shopify/hydrogen/issues/1824 to track HMR in server components. I think it should be possible to avoid full page refresh there as well 🤔


Remove MIPS_funcat xrefs ?

Hello,
Does anyone know if MIPS_funcat still exists ? If not, we should remove the xrefs we have to this resource.
@thomaspd @ValWood @cmungall any idea?
Thanks, Pascale

It seems to have gone
https://en.wikipedia.org/wiki/Munich_Information_Center_for_Protein_Sequences
forwards to
https://www.helmholtz-muenchen.de/ibis/

oh yeah they went defunct some years ago.

The yeast MIPS complexes are gone, I looked for them many times!!!
CORUM (mammalian complexes) used funcat, too. But they have now mapped to GO.


std,cmd: add a unit test to ensure that src/go.mod and src/cmd/go.mod are in sync

In https://github.com/golang/go/issues/36851#issuecomment-580438655, @FiloSottile noticed that the std module and the cmd module currently depend on different commits of the golang.org/x/sys module.
We should prevent such skew in the future. It should be straightforward to write a test that uses go list (or a similar approach) to check that the versions required by std and cmd agree for the modules in the intersection of their dependencies.

This issue is currently labeled as early-in-cycle for Go 1.15. That time is now, so friendly ping. If it no longer needs to be done early in cycle, that label can be removed.

I'm very glad this test exists and found it to work well while developing CL 231657. Thank you @bcmills and @FiloSottile!

Here's an excerpt from a moment when the x/sys versions diverged between the two modules; the test reported it correctly.
--- FAIL: TestDependencyVersionsConsistent (0.00s)
    moddeps_test.go:217: Modules within GOROOT require different versions of golang.org/x/sys.
    moddeps_test.go:229: cmd	requires v0.0.0-20191204072324-ce4227a45e2e
    moddeps_test.go:229: std	requires v0.0.0-20200323222414-85ca7c5b95cd
FAIL
FAIL	cmd/internal/moddeps	10.795s


Extension causes high cpu load

Issue Type: Performance
Extension Name: python
Extension Version: 2019.10.41019
OS Version: Windows_NT x64 10.0.18362
VSCode version: 1.38.1

:warning: Make sure to attach this file from your home-directory:
:warning:C:\Users\TMTsoka.THOKOLOSI.000.001\ms-python.python-unresponsive.cpuprofile.txt
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

@Tsokam Please open a new bug using our bug template and also upload this file: ms-python.python-unresponsive.cpuprofile.txt


chore: Fix the type definition of additionalJVMConfig

Please squash both commits. You could also use a more descriptive commit message, maybe something like:
Fix default value for additionalJVMConfig

`additionalJVMConfig` expects a list, so the default value should not be an empty object.

Ok, done 950e33837c38cdc31f4ef6eca411c8d91ec3b041
Thanks @nineinchnick


GH35641: [CI][C++] Disable precompiled headers

Rationale for this change
ccache does not like precompiled headers and does not cache anything in that case, which pessimizes build times.
What changes are included in this PR?
Disable precompiled headers, and enable unity builds to make up for it.
Are these changes tested?
Yes, by construction.
Are there any user-facing changes?
No.

@github-actions crossbow submit test-conda*

cc @kou

@github-actions crossbow submit test-conda*

@github-actions crossbow submit test-conda* example*

Hmm, CMAKE_UNITY_BUILD might actually make things worse if there's not enough RAM. Let's disable it again.

Before ("Uncacheable calls" are increased):
https://github.com/apache/arrow/actions/runs/6044793011/job/16403882283#step:6:996
Uncacheable calls:                  6314 / 9460 (66.74%)
  Could not use precompiled header: 6314 / 6314 (100.0%)

↓
https://github.com/apache/arrow/actions/runs/6044793011/job/16403882283#step:6:3341
Uncacheable calls:                  6888 / 10320 (66.74%)
  Could not use precompiled header: 6888 /  6888 (100.0%)

After ("Uncacheable calls" aren't increased):
https://github.com/apache/arrow/actions/runs/6042717769/job/16398390958?pr=37502#step:6:1180
 Uncacheable calls:                  6314 / 9460 (66.74%)
  Could not use precompiled header: 6314 / 6314 (100.0%)

↓
https://github.com/apache/arrow/actions/runs/6042717769/job/16398390958?pr=37502#step:6:3501
 Uncacheable calls:                  6314 / 10311 (61.24%)
  Could not use precompiled header: 6314 /  6314 (100.0%)

Can we merge this?
Do you want to do more tries on this PR?

Yes, we can merge.


Cannot find package

Hi,
Cloned the repo, run "make build" but the following errors are shown:
make build
go build -o terraform-provider-sendgrid -v
../go/src/github.com/hashicorp/go-getter/get_s3.go:11:2: cannot find package "github.com/aws/aws-sdk-go/aws" in any of:
/usr/lib/go-1.10/src/github.com/aws/aws-sdk-go/aws (from $GOROOT)
/root/go/src/github.com/aws/aws-sdk-go/aws (from $GOPATH)
../go/src/github.com/hashicorp/go-getter/get_s3.go:12:2: cannot find package "github.com/aws/aws-sdk-go/aws/credentials" in any of:
/usr/lib/go-1.10/src/github.com/aws/aws-sdk-go/aws/credentials (from $GOROOT)
/root/go/src/github.com/aws/aws-sdk-go/aws/credentials (from $GOPATH)
../go/src/github.com/hashicorp/go-getter/get_s3.go:13:2: cannot find package "github.com/aws/aws-sdk-go/aws/credentials/ec2rolecreds" in any of:
/usr/lib/go-1.10/src/github.com/aws/aws-sdk-go/aws/credentials/ec2rolecreds (from $GOROOT)
/root/go/src/github.com/aws/aws-sdk-go/aws/credentials/ec2rolecreds (from $GOPATH)
../go/src/github.com/hashicorp/go-getter/get_s3.go:14:2: cannot find package "github.com/aws/aws-sdk-go/aws/ec2metadata" in any of:
/usr/lib/go-1.10/src/github.com/aws/aws-sdk-go/aws/ec2metadata (from $GOROOT)
/root/go/src/github.com/aws/aws-sdk-go/aws/ec2metadata (from $GOPATH)
../go/src/github.com/hashicorp/go-getter/get_s3.go:15:2: cannot find package "github.com/aws/aws-sdk-go/aws/session" in any of:
/usr/lib/go-1.10/src/github.com/aws/aws-sdk-go/aws/session (from $GOROOT)
/root/go/src/github.com/aws/aws-sdk-go/aws/session (from $GOPATH)
../go/src/github.com/hashicorp/go-getter/get_s3.go:16:2: cannot find package "github.com/aws/aws-sdk-go/service/s3" in any of:
/usr/lib/go-1.10/src/github.com/aws/aws-sdk-go/service/s3 (from $GOROOT)
/root/go/src/github.com/aws/aws-sdk-go/service/s3 (from $GOPATH)
../go/src/github.com/hashicorp/go-getter/netrc.go:9:2: cannot find package "github.com/bgentry/go-netrc/netrc" in any of:
/usr/lib/go-1.10/src/github.com/bgentry/go-netrc/netrc (from $GOROOT)
/root/go/src/github.com/bgentry/go-netrc/netrc (from $GOPATH)
../go/src/github.com/hashicorp/go-getter/get.go:22:2: cannot find package "github.com/hashicorp/go-cleanhttp" in any of:
/usr/lib/go-1.10/src/github.com/hashicorp/go-cleanhttp (from $GOROOT)
/root/go/src/github.com/hashicorp/go-cleanhttp (from $GOPATH)
../go/src/github.com/hashicorp/go-getter/client.go:13:2: cannot find package "github.com/hashicorp/go-safetemp" in any of:
/usr/lib/go-1.10/src/github.com/hashicorp/go-safetemp (from $GOROOT)
/root/go/src/github.com/hashicorp/go-safetemp (from $GOPATH)
../go/src/github.com/hashicorp/terraform-plugin-sdk/terraform/state.go:18:2: no Go files in /root/go/src/github.com/hashicorp/go-uuid
../go/src/github.com/hashicorp/terraform-plugin-sdk/internal/configs/hcl2shim/single_attr_body.go:6:2: cannot find package "github.com/hashicorp/hcl/v2" in any of:
/usr/lib/go-1.10/src/github.com/hashicorp/hcl/v2 (from $GOROOT)
/root/go/src/github.com/hashicorp/hcl/v2 (from $GOPATH)
../go/src/github.com/hashicorp/terraform-plugin-sdk/internal/addrs/module_instance.go:8:2: cannot find package "github.com/hashicorp/hcl/v2/hclsyntax" in any of:
/usr/lib/go-1.10/src/github.com/hashicorp/hcl/v2/hclsyntax (from $GOROOT)
/root/go/src/github.com/hashicorp/hcl/v2/hclsyntax (from $GOPATH)
../go/src/github.com/hashicorp/terraform-plugin-test/config.go:8:2: cannot find package "github.com/hashicorp/terraform-exec/tfinstall" in any of:
/usr/lib/go-1.10/src/github.com/hashicorp/terraform-exec/tfinstall (from $GOROOT)
/root/go/src/github.com/hashicorp/terraform-exec/tfinstall (from $GOPATH)
../go/src/github.com/digitalocean/terraform-provider-sendgrid/sendgrid/resource_api_key.go:13:2: cannot find package "github.com/pkg/errors" in any of:
/usr/lib/go-1.10/src/github.com/pkg/errors (from $GOROOT)
/root/go/src/github.com/pkg/errors (from $GOPATH)
../go/src/github.com/hashicorp/go-getter/decompress_txz.go:8:2: cannot find package "github.com/ulikunitz/xz" in any of:
/usr/lib/go-1.10/src/github.com/ulikunitz/xz (from $GOROOT)
/root/go/src/github.com/ulikunitz/xz (from $GOPATH)
../go/src/cloud.google.com/go/internal/trace/trace.go:21:2: cannot find package "go.opencensus.io/trace" in any of:
/usr/lib/go-1.10/src/go.opencensus.io/trace (from $GOROOT)
/root/go/src/go.opencensus.io/trace (from $GOPATH)
../go/src/github.com/digitalocean/terraform-provider-sendgrid/sendgrid/resource_subuser.go:18:2: cannot find package "golang.org/x/sync/errgroup" in any of:
/usr/lib/go-1.10/src/golang.org/x/sync/errgroup (from $GOROOT)
/root/go/src/golang.org/x/sync/errgroup (from $GOPATH)
../go/src/cloud.google.com/go/internal/annotate.go:20:2: cannot find package "google.golang.org/api/googleapi" in any of:
/usr/lib/go-1.10/src/google.golang.org/api/googleapi (from $GOROOT)
/root/go/src/google.golang.org/api/googleapi (from $GOPATH)
../go/src/cloud.google.com/go/storage/bucket.go:27:2: cannot find package "google.golang.org/api/iterator" in any of:
/usr/lib/go-1.10/src/google.golang.org/api/iterator (from $GOROOT)
/root/go/src/google.golang.org/api/iterator (from $GOPATH)
../go/src/cloud.google.com/go/storage/storage.go:45:2: cannot find package "google.golang.org/api/option" in any of:
/usr/lib/go-1.10/src/google.golang.org/api/option (from $GOROOT)
/root/go/src/google.golang.org/api/option (from $GOPATH)
../go/src/cloud.google.com/go/storage/acl.go:24:2: cannot find package "google.golang.org/api/storage/v1" in any of:
/usr/lib/go-1.10/src/google.golang.org/api/storage/v1 (from $GOROOT)
/root/go/src/google.golang.org/api/storage/v1 (from $GOPATH)
../go/src/cloud.google.com/go/storage/storage.go:47:2: cannot find package "google.golang.org/api/transport/http" in any of:
/usr/lib/go-1.10/src/google.golang.org/api/transport/http (from $GOROOT)
/root/go/src/google.golang.org/api/transport/http (from $GOPATH)
Makefile:15: recipe for target 'terraform-provider-sendgrid' failed
make: *** [terraform-provider-sendgrid] Error 1

Hi @cmptscpeacock,
Apologies for the delayed response. It looks like you're using Go version 1.10, which isn't compatible with Go Modules. I recommend updating to the latest version of Golang, or, if that is not feasible, at least 1.13.
Please let me know if this resolves your issue.


[feat] Write the number of tasks in performance report

Change documentation regarding the performance report format.

Addresses #915.

This does not fix #915, but partially addresses it.

Hello @teojgo, Thank you for updating!

In the file reframe/core/pipeline.py:

Line 1209:80: E501 line too long (91 > 79 characters)

Do see the ReFrame Coding Style Guide


Release FreeBSD binary.

Please build and release a FreeBSD binary in addition to the Darwin, Linux, and Windows binaries.

Which architecture are important? Possible values are:
freebsd 	386
freebsd 	amd64
freebsd 	arm

Out of interest, what do you use GoAWK for?

I'm interested in amd64, but others may run FreeBSD on ARM processors in single board computers like the Raspberry Pi.
I use GoAWK for processing CSV files along with tools like csvtk, csvq, DuckDB, Miller, qsv, and Python modules or packages like csv, Pandas, and Polars.
Do you know if GoAWK is available in FreeBSD ports?  I run TrueNAS, a FreeBSD derivative, which does not include any compilers in its base "immutable" operating system, so if GoAWK were available in Ports, its build would have to first build the Go compiler and any other dependencies.

Thanks for the info. Unfortunately I know very little about FreeBSD, but a quick search here shows that v1.29.0 is in Ports (if I'm looking at the right place).
I've released v1.29.1 with FreeBSD amd64 and arm binaries, so closing this issue as complete.


Improve error handling by the program

sorry

na it's ok you just missed java.io.IOException. I'm gonna put a github workflow in place to prevent these things from getting unnoticed.


mouse.click() does not do mouse up

Setup:
autopy==1.0.1
python 3.6
Interacting with a VNC linux session like so:
autopy.mouse.move(1032, 126)
autopy.mouse.click()

This will move the mouse to the correct location
Then the mouse-down is issued, but a mouse-up does not occur.
If in this position I issue:
autopy.mouse.toggle(autopy.mouse.Button.LEFT, False)

The mouse up is given.

My guess is the delay isn't long enough for the click to register in VNC. I'll update this in the next release to take an explicit delay parameter so it can be increased.

I can confirm the same issue on Fedora 27 without the VNC session (physical workstation as well as a docker image). Using the toggle(..., False) step solves the issue for the time being.

This should be fixed by https://github.com/autopilot-rs/autopilot-rs/pull/8 (which is included on the latest master), I just haven't had time yet to distribute the new binary wheels.

This is fixed on the latest master. Moved binary wheel distribution task to separate issue: https://github.com/autopilot-rs/autopy/issues/18.


Scale caustics strength by primary light and depth fog

Scales the caustics strength by primary light colour, depth fog density and scene depth.
Solves the problem of caustics showing up under underwater lights when they shouldn't. This solution works independently from the UnderwaterEnvironmentalLighting component, but it is affected by it since it scales the primary light. But that is a separate problem.
I am not certain how they should co-exist with depth of field and focal depth, but right now they don't appear to conflict.
I plan to port this to HDRP to replace limiting caustics by scene depth, but it might be a bit more involved due to different lighting units.

Looks good to me, nice one. I think this co-exists fine with DoF etc.
One tiny nitpick - could you make the constants like 1.0, not 0 or 1. . I recently found this in the shader coding standard in SRP which i think gives a nice consistency/readability.

Thanks. Fixed and merged.


Prevent kept-alive render objects from doing layout/paint

Related Issues

https://github.com/flutter/flutter/issues/84896
b/179945024 (internal, maybe related)

Some "lazy" render parents (RenderSliverMultiBoxAdaptor, _RenderTheater) skip laying out off-screen children. Unfortunately nodes in these offscreen subtrees can still request repaint and get painted in PipelineOwner.flushPaint if there's a repaint boundary between them and the lazy render parent. This invalidates many common assumptions (for instance, the layout is always up-to-date when paint is called), causing unexpected behaviors and even crashes. Our current workarounds in place include setting the paint transform to a singular matrix. But there should be a way to tell if a specific render object's layout is not getting updated.
Another strange side effect of skipping layout is that the _needsLayout bit is not cleared after each flushLayout. _needsLayout  currently indicates whether a render object's layout information is dirty, as well as if a relayout has been scheduled for it: the current markNeedsLayout implementation returns early if _needsLayout has already been set. This will prevent an offscreen descendant from requesting layout update if it was previously marked _needsLayout. Not laying out a subtree does not necessarily mean that we want to ignore layout requests from that subtree.
Why having a dedicated pipeline owner

The tree hierarchy should be left intact since the offscreen render objects should still be able to call showOnScreen (but this probably isn't going to work very work for lazy lists since the offscreen render objects have outdated layout information).
Ideally the offscreen render objects shouldn't be detached from their own, as a kept-alive descendant of a list view that's also kept-alive (i.e. nested keep-alives) should unmount & dispose of itself when its "keepAlive" flag is turned off (this probably doesn't work today).

Edge cases to consider

EditableTextState should still be allowed to look up the text layout info, but the layout info could potentially be outdated (as the incoming constraints might have changed).
For instance, deleteLine could be using the outdated line breaks when the user invokes it while the text field is kept alive -- the width of the vertical scrolling list may have changed.
(if we want a kept-alive text field to respond to key events).

Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Not actively working on this right now. Closing.


Reddit user RSS feeds don't work when Reddit extension is enabled

If you try adding a Reddit user's RSS feed (i.e., https://www.reddit.com/user/NAME.rss) when the Reddit extension is enabled, NNW reports no feed is found. Disable the Reddit extension and it works again.

I'll confirm this is still happening.
I think that a fix could be to add an exception to RedditFeedProvider.ability] which just stops it from saying it can handle any URL ending in .rss? An alternative, though more complicated, would be to make sure the feed provider understands the .rss URLs and translates them into the API-fetchable feeds it knows about...

I am having the same issue. I can confirm that disabling the reddit extension does let you add reddit user's rss feeds.

Will disabling the reddit extension delete my existing reddit feeds, or is it safe for me to disable it just long enough to add a user feed? If not, is there any workaround?

@alltom That won't work. The feed will still be ignored when you reenable the extension. We do plan to fix this in the 6.3 release.

Even if I don't have the Reddit extension anymore (I'm on 6.1.4), it seems like I'm not able to import any feeds from Reddit. I'm getting this:
https://github.com/Ranchero-Software/NetNewsWire/assets/2979628/128dd09e-5d3b-4e02-b409-43dfb729dbd6
Does it work you?


Feature Request: Add default timezone to display on timestamps

Currently, the table views show timestamps in UTC, but I think it'd be nice if there could be a setting somewhere to change the displayed time zone

You can check https://github.com/pocketbase/pocketbase/discussions/1745.
This eventually may change in the future if introduce zone support in the filters, but for now is a low priority.


Pools/connections not being closed in tests

Crazy High Level
After upgrading from 0.5.11 to 0.5.12 (and trying 0.5.13), our test
suite fails because of this error:

remaining connection slots are reserved for non-replication superuser connections

I cloned sqlx and git bisected it and got to https://github.com/launchbadge/sqlx/pull/1799.

Details And Debugging
Every test in this particular test suite runs with #[tokio::test] so that seems
awfully related to the discussion of runtimes in https://github.com/launchbadge/sqlx/issues/1396#issuecomment-905127568. Every test in this
test suite calls a function which creates its own PgPool to run some queries.
This is, of course, not what pools are for but, if I add a pool.close().await to
the end of that function, the tests all pass.

Originally I thought I'd just do that, problem solved.  Every unit test
clones a template database and then connects a pool to its specific database.
This ensures no tests collide which is nice but, I think, prevents us from
sharing one pool among them.

Minimal Reproduction (sort of)
This reproducer shows the "bug" in both 0.5.11 and 0.5.13 so maybe
this is something we were bound to run into eventually but our test suite
happens to consistently pass on 0.5.11 and consistently fail otherwise.
This also, obviously, isn't how our tests work - we don't create the pools
in a loop, each test creates its own. But this is fewer lines of code :-).

#[cfg(test)]
mod tests {
    struct DropDetector(usize, sqlx::PgPool);
    impl Drop for DropDetector {
        fn drop(&mut self) {
            println!("Dropping {}", self.0);
        }
    }

    async fn handwavy_test_setup(i: usize) {
        let db_url = "your_connection_string_here";
        let drop_detector = DropDetector(i, sqlx::PgPool::connect(db_url).await.unwrap());
        let DropDetector(_, pool) = &drop_detector;

        // This "fixes" the "problem".
        // pool.close().await;
    }

    #[tokio::test]
    async fn test_stuff() {
        for i in 0..100 {
            println!("Starting test {i}");
            handwavy_test_setup(i).await;

            // Give time for pool to close? Simulate doing ... test stuff.
            tokio::time::sleep(std::time::Duration::from_millis(100)).await;
        }
    }
}

Cargo.toml:
[package]
name = "sqlx-pools"
version = "0.1.0"
edition = "2021"

[dependencies]
sqlx = { version = "=0.5.11", default-features = false, features = ["runtime-actix-rustls", "postgres"] }
tokio = { version = "=1.17.0", default-features = false, features = ["macros", "rt"] }

Versions And Things

Thing
Version

test suite sqlx
works on 0.5.11, did not on 0.5.12, does not on 0.5.13

reproducer sqlx
fails on 0.5.11 and 0.5.13 (at least)

driver
postgres

postgresql
14.1 and 12.6

#1799 was designed specifically to fix this situation so I don't understand how it could have made it worse unless it introduced an Arc-cycle somewhere. The fact that calling .close().await fixes the problem suggests it might be some sort of timing issue, though.
Since you're creating a number of different Pools potentially in parallel, you probably want to use something like a global tokio::sync::Semaphore to ensure you don't exceed Postgres' connection limit, or use --test-threads to limit the number of concurrently running tests.
Since the pools are short-lived, you can also turn off the idle reaper by setting max_lifetime and idle_timeout to None, or even try pool_options.after_release(|_| false) to force connections to be eagerly closed when returned to the pool. You might also want to use pool_options.max_connections(1) to make sure each pool is only opening a single connection.
Though, it might make sense to have a PoolOptions::new_test() config with different defaults specifically for testing. We've also been talking about adding a #[sqlx::test] attribute that does this configuration automatically.

Since you're creating a number of different Pools potentially in parallel, you probably want to use something like a global tokio::sync::Semaphore to ensure you don't exceed Postgres' connection limit,

That does sound pretty nifty but I was hoping to not have to make a pool for my connection pools :laughing: This may be the way though!

or use --test-threads to limit the number of concurrently running tests.

We actually do have --test-threads throttling in CI and locally that doesn't help either :-(

Example Local Output
➜ cargo test --quiet some_test_names -- --test-threads=2
running 82 tests
..................................................................................
test result: ok. 82 passed; 0 failed; 0 ignored; 0 measured; 47 filtered out; finished in 33.19s

➜ cargo update -p sqlx
    Updating crates.io index
      Adding event-listener v2.5.2
      Adding hkdf v0.12.3
      Adding hmac v0.12.1
    Updating md-5 v0.9.1 -> v0.10.1
      Adding sha2 v0.10.2
    Updating sqlx v0.5.11 -> v0.5.13
    Updating sqlx-core v0.5.11 -> v0.5.13
    Updating sqlx-macros v0.5.11 -> v0.5.13
    Updating sqlx-rt v0.5.11 -> v0.5.13

➜ cargo test --quiet some_test_names -- --test-threads=2

running 82 tests
...............................................test one_test has been running for over 60 seconds
test another_test has been running for over 60 seconds
..F^C # gave up

The tests start taking over 60s because the code that checks out the pool actually does it in a loop when it fails to connect to the DB so they just loop for a long time but if I turn on all the logging things I see the above mentioned error.

Since the pools are short-lived, you can also turn off the idle reaper by setting max_lifetime and idle_timeout to None, or even try pool_options.after_release(|_| false) to force connections to be eagerly closed when returned to the pool. You might also want to use pool_options.max_connections(1) to make sure each pool is only opening a single connection.

Ah that's great - I didn't know if None would make it infinite or effectively zero. I'll try that!

Since the pools are short-lived, you can also turn off the idle reaper by setting max_lifetime and idle_timeout to None, or even try pool_options.after_release(|_| false) to force connections to be eagerly closed when returned to the pool. You might also want to use pool_options.max_connections(1) to make sure each pool is only opening a single connection.

That also sounds really cool and would help our integration tests that connect to the various DB clones. Our integration tests use the same pool connection function that our actual application uses so it maybe can't benefit from this (or the other suggestions above - I'll see!).

Alrighty, I have a consistent reproducer on my local at least. I made 3 changes:
Dependencies
I needed to lock in sqlx-core. Otherwise, when I updated sqlx to 0.5.13 and then back to 0.5.11, sqlx-core stayed at 0.5.13:
[dev-dependencies]
sqlx = { version = "=0.5.11", default-features = false, features = ["runtime-actix-rustls", "postgres"] }
sqlx-core = "=0.5.11"
tokio = { version = "=1.17.0", default-features = false, features = ["macros", "rt"] }

Pool Acquisition
I added some code that's more similar to how our actual function sets up a pool. I removed some looping and error handling but one important thing is that we test the connection with a query before returning it (not sure if that's necessary - the issue is still open but if I stop my DB server it seems to correctly return an error without that query - maybe because we have a timeout?).
async fn get_pool() -> sqlx::PgPool {
    let db_url = "your_connection_string_here";
    let pool = sqlx::PgPool::connect(db_url).await.unwrap();

    // NOTE: Commenting out this query allows the tests to pass ... freaky

    // sqlx will not fail if it cannot connect to the database at all.
    // Until [this](https://github.com/launchbadge/sqlx/issues/744) is fixed,
    // we need to make a dummy query.
    sqlx::query("SELECT 1").execute(&pool).await.unwrap();

    pool
}

async fn handwavy_test_setup() {
    let pool = get_pool().await;
    let tx = pool.begin().await.unwrap();

    // Do actual test setup stuff ...

    tx.commit().await.unwrap();

    // This "fixes" the "problem"
    // pool.close().await;
}

Test Arrangement
I went away from the weird loop to the "lots of actual tests"
// Generate a test so we can fit this all on one screen.
macro_rules! t {
    ($test_name:tt) => {
        #[tokio::test]
        async fn $test_name() {
            handwavy_test_setup().await;

            // Do test stuff
            tokio::time::sleep(std::time::Duration::from_millis(10)).await;
        }
    };
}

#[rustfmt::skip]
mod actual_tests {
    use super::*;

    t!(a0); t!(a1); t!(a2); t!(a3); t!(a4); t!(a5); t!(a6); t!(a7); t!(a8); t!(a9);
    t!(b0); t!(b1); t!(b2); t!(b3); t!(b4); t!(b5); t!(b6); t!(b7); t!(b8); t!(b9);
    t!(c0); t!(c1); t!(c2); t!(c3); t!(c4); t!(c5); t!(c6); t!(c7); t!(c8); t!(c9);
    t!(d0); t!(d1); t!(d2); t!(d3); t!(d4); t!(d5); t!(d6); t!(d7); t!(d8); t!(d9);
    t!(e0); t!(e1); t!(e2); t!(e3); t!(e4); t!(e5); t!(e6); t!(e7); t!(e8); t!(e9);
    t!(f0); t!(f1); t!(f2); t!(f3); t!(f4); t!(f5); t!(f6); t!(f7); t!(f8); t!(f9);
    t!(g0); t!(g1); t!(g2); t!(g3); t!(g4); t!(g5); t!(g6); t!(g7); t!(g8); t!(g9);
    t!(h0); t!(h1); t!(h2); t!(h3); t!(h4); t!(h5); t!(h6); t!(h7); t!(h8); t!(h9);
    t!(i0); t!(i1); t!(i2); t!(i3); t!(i4); t!(i5); t!(i6); t!(i7); t!(i8); t!(i9);
    t!(j0); t!(j1); t!(j2); t!(j3); t!(j4); t!(j5); t!(j6); t!(j7); t!(j8); t!(j9);
    t!(k0); t!(k1); t!(k2); t!(k3); t!(k4); t!(k5); t!(k6); t!(k7); t!(k8); t!(k9);
    t!(l0); t!(l1); t!(l2); t!(l3); t!(l4); t!(l5); t!(l6); t!(l7); t!(l8); t!(l9);
}

Result
With this set up I get consistent failures with (both sqlx and sqlx-core at) 0.5.13 and consistent success with (both sqlx and sqlx-core at) 0.5.11.

Full Code
#[cfg(test)]
mod tests {
    async fn get_pool() -> sqlx::PgPool {
        let db_url = "your_connection_string_here";
        let pool = sqlx::PgPool::connect(db_url).await.unwrap();

        // NOTE: Commenting out this query allows the tests to pass ... freaky

        // sqlx will not fail if it cannot connect to the database at all.
        // Until [this](https://github.com/launchbadge/sqlx/issues/744) is fixed,
        // we need to make a dummy query.
        sqlx::query("SELECT 1").execute(&pool).await.unwrap();

        pool
    }

    async fn handwavy_test_setup() {
        let pool = get_pool().await;
        let tx = pool.begin().await.unwrap();

        // Do actual test setup stuff ...

        tx.commit().await.unwrap();

        // This "fixes" the "problem"
        // pool.close().await;
    }

    // Generate a test so we can fit this all on one screen.
    macro_rules! t {
        ($test_name:tt) => {
            #[tokio::test]
            async fn $test_name() {
                handwavy_test_setup().await;

                // Do test stuff
                tokio::time::sleep(std::time::Duration::from_millis(10)).await;
            }
        };
    }

    #[rustfmt::skip]
    mod actual_tests {
        use super::*;

        t!(a0); t!(a1); t!(a2); t!(a3); t!(a4); t!(a5); t!(a6); t!(a7); t!(a8); t!(a9);
        t!(b0); t!(b1); t!(b2); t!(b3); t!(b4); t!(b5); t!(b6); t!(b7); t!(b8); t!(b9);
        t!(c0); t!(c1); t!(c2); t!(c3); t!(c4); t!(c5); t!(c6); t!(c7); t!(c8); t!(c9);
        t!(d0); t!(d1); t!(d2); t!(d3); t!(d4); t!(d5); t!(d6); t!(d7); t!(d8); t!(d9);
        t!(e0); t!(e1); t!(e2); t!(e3); t!(e4); t!(e5); t!(e6); t!(e7); t!(e8); t!(e9);
        t!(f0); t!(f1); t!(f2); t!(f3); t!(f4); t!(f5); t!(f6); t!(f7); t!(f8); t!(f9);
        t!(g0); t!(g1); t!(g2); t!(g3); t!(g4); t!(g5); t!(g6); t!(g7); t!(g8); t!(g9);
        t!(h0); t!(h1); t!(h2); t!(h3); t!(h4); t!(h5); t!(h6); t!(h7); t!(h8); t!(h9);
        t!(i0); t!(i1); t!(i2); t!(i3); t!(i4); t!(i5); t!(i6); t!(i7); t!(i8); t!(i9);
        t!(j0); t!(j1); t!(j2); t!(j3); t!(j4); t!(j5); t!(j6); t!(j7); t!(j8); t!(j9);
        t!(k0); t!(k1); t!(k2); t!(k3); t!(k4); t!(k5); t!(k6); t!(k7); t!(k8); t!(k9);
        t!(l0); t!(l1); t!(l2); t!(l3); t!(l4); t!(l5); t!(l6); t!(l7); t!(l8); t!(l9);
    }
}

After trying the repro locally, it does seem to be leaking connections for some reason but I can't fathom why. #1799 shouldn't have introduced it, although the extra cloning of Arc may have changed exactly which task drops things.

Okay, it took me an embarrassingly long time to find the problem, but I think I've figured it out. In hindsight, it should have been painfully obvious from the diff of #1799 but Github collapsed the lines by default because they weren't changed: https://github.com/launchbadge/sqlx/pull/1799/files#diff-782a6e0cb2edbd43e45dfef48fae8534c6a8f46cddebca66256e6f88819f7ef0R397-R399
That mem::forget() was perfectly innocuous when it contained a reference to SharedPool, but now that it contains an Arc, it's effectively leaking the SharedPool because that is called when a connection is released back to the pool, permanently adding 1 strong reference to the Arc every time.

It's here on master: https://github.com/launchbadge/sqlx/blob/fa5c436918664de112677519d73cf6939c938cb0/sqlx-core/src/pool/inner.rs#L397-L399

Would it be sufficient to call drop(self.pool) before that mem::forget call to decrement the Arc?


Crash with flux ducts

https://gist.github.com/EnderT5/60107f338dbc61636e1a70b0a4c8707b
why this mod tries to compress flux duct???
(im testing new version of flux duct, mod maker tries to do fix problem himself, but real problem is this mod)
https://github.com/mezz/JustEnoughItems/issues/293
jei maker explains

For now, you can blacklist the item using the newest version of compression. I will look into why this is crashing.
As for why compress them? because compress ALL THE THINGS. But in all seriousness, the only reliable way to be able to compress the most blocks / items, it to assume everything works, and create filters from those that don't.

crash fixed, flux duct compressing disabled by flux duct mod maker i think, because compressing flux duct shows in recipe viewing screen of jei but you cant compress flux duct. i will report to the jei for unusing recipes of compression because jei shows compressing recipe of flux duct but you cant compress it.

closed thread, fixed in latest version of flux duct

Kept open for bug tracking of blocks/items which should not be compressed


Pagopa 897 int test nuove api gestione iban

List of Changes
Addition of integration tests for the iban CRUD in api-config core

Motivation and Context
This addition was required in order to test properly the new iban CRUD APIs and to start the development of api-config integration tests

How Has This Been Tested?
This has been tested manually using h2 profile and cucumber with the yarn command. For the dev and uat cases the APIs are not working yet

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

update_code

What is missing for the Ibans CRUD APIs to work in the DEV and UAT environments? By checking release, status page, APIM and infra in the mentioned environments the functionality has been deployed.

What is missing for the Ibans CRUD APIs to work in the DEV and UAT environments? By checking release, status page, APIM and infra in the mentioned environments it seems that the functionality has been deployed.

@AngeloCaporaso @FedericoRuzzier if DEV e UAT use really IBAN table we shall disable mock resp into those envs, and leave it only in PROD


Enhanced Editor - Allow a user to select a field at runtime to sticky or add to the preset fields

Similar to the concept as Survey 123 as save as favorites
Request was once I create a feature, can I use the same values for the next feature.  This workflow is supported is collector.  So one thought was to allow the user to sticky fields and move them to the preset list

A workflow for this could be the following.  If you have a person inspecting trees.  A field like "isFireZone" might not be a preset field and has no need to be.  But since he/she is working in a known fire area today or if it's fire season, they could runtime, add the field "isFireZone" and set it "Yes" for their daily work.

Thanks for providing a sample workflow. It helps a lot :+1:


Feature/linear hardening

We didn't have linear hardening as a standalone option. You could get it as a special case of power law or Voce by choosing the parameters in a particular way, but it's easier for users to have the linear case explicitly available.
This is a first step towards reducing code repetition. We have several J2 model implementations now, including one that only has linear hardening (but also has linear kinematic hardening). I want to have one implementation with options that are easily configurable.
There are a few other small items in this PR:

I used the new linear hardening struct in tests that were using linear hardening behavior
I improved the readability of an old test (behavior is unmodified)
I switched one of the existing tests from power law to Voce, because this hardening option was not used in any test. Increases test coverage one iota.

@samuelpmishLLNL , would you mind taking a look at this?


Update External links

This looks OK now, will merge to the develop branch to deploy to staging.

Thanks for making this change, Adam. I realise that Anna is now on leave anyway.
We need to update the date on any pages where we make a substantive change. I'll get someone to do that tomorrow when I run my GitHub session.


Opening preferences window in Mac changes UI color

You need to be using a Mac and the "Native" theme to see this.

Open TLV
Open any log file
Open the "Preferences..." window
=>Notice how the style and color changes on the main window, a hybrid of light and dark elements. Change is undoable unless you re-start TLV

I am seeing the same behavior. In general, there is a lot of weirdness going on with themes on Mac

I was hoping the Qt updated fixed this but it still reproes on the current dev branch :/

This issue was fixed on the PR #131


Publicise Catalyst Project website to Community Partners

Hi @SLLDeC and @elletjies ,
@katiepratt from CSCCE has drafted an email to publicise our recently released website to our community partners.
Would you be able to send this out on our behalf please (draft below)?

Dear name,
I’m writing to let you know that the English version of the website for the Catalyst Project is now live:  https://catalystproject.cloud/. A Spanish version of the site will be available soon.
As a Community Partner in this project, you are listed on the website. You can also find information about available training through the Catalyst Project, as well as stay up-to-date on news and activities on the blog.
We would appreciate any feedback you have about the website - you can either reply to this email, or submit your feedback via the Catalyst Project GitHub repo (I’ve included detailed instructions for how to do this below).
We are also in the process of creating an “FAQ” page, so if you have suggestions for things to include there (e.g., questions you had while getting set up as a community partner), please let me know.
All the best,
-Angelique/Sabrina
Instructions for submitting updates to the Catalyst Project website
To suggest an update or correction on existing content, e.g., you spotted a typo or need to update a team members’ information:

Go to the Catalyst website GitHub repository
From the top menu, click on Issues. You will see a list of ongoing issues
Click on the green “New Issue” button and then select the template called “Suggest minor edits”.
This will display a template issue where you can add your request details
Tips:

Please add a direct link to the place on the website that you would like to be updated. If you hover over headings on the website this will reveal an anchored URL. This will help the website team to find the correct place.

When you have added all the required info, click the “submit new issue” button
You can expect Jenny to respond to your issue within a week. She may ask clarifying questions in the issue comment so please make sure you have notifications enabled. Jenny will likely package multiple issues into a next release so you may not see a resolution to your issue immediately.

@jnywong this is great! I will send out the emails today.

@jnywong thank you!
If this email comes from the MD team will must translate it to Spanish because we always communicate in Spanish with Latin American communities. All our time for Catalyst is currently being used to address the bottleneck of new community onboarding.
Thus, to have this email out timely two possibilities come to mind:

Someone else at Catalyst sends this email to Latin American communities in English at their earliest convenience or
MetaDocencia's team sends it in Spanish once we are on the other end of the current onboarding crunch, date tbd 😃

Please let us know what works best. Thank you so much for your help and understanding with this! 💮

Hi @lauracion!
You're welcome. I understand that the onboarding crunch is the main focus for MetaDocencia at this time, so I am happy with option 2.
I'll pick this up again with @SLLDeC after April has passed :)

I sent out the emails. Thank you for your understanding!


fix(core): fixes #356 and prevents dupes dynamic properties (detached…

Description

fixes #356 and prevents dupes dynamic properties (detached and non detached) to exist

For dynamic props, now the logic is that a prop becomes detached or non detached the first time it's created. Afterwards, it can be either accessed with base["@prop"] or base["prop"] equally.
For typed props, they can now be accessed with base["@prop"] or base["prop"] equally whether they are detached or not.
Type of change

Bug fix (non-breaking change which fixes an issue)

How has this been tested?

New tests were made

Docs

Will be updated ASAP

I hear you izzy! Since it seems the decision is between: "not properly setting a prop as detached" and "not being able to access a prop because of @ confusion" I think the first is preferable :) But let's let @didimitrie weigh on this...

Ok thought on this more. I don't really like the backchannel extra magic, and it has the potential to add extra confusion. There's an extra layer of indirection that I feel is not needed...
IMHO, the way to fix #356 is with a change in code, in how those funcs deal with the ["@elements"] prop (see comment in issue).
One thing that is an improvement is being able to allow, if one uses the square bracket notation, to get/set typed detachable props with it. Ie, if i do base["@test"], it can pull in/try to set the typed detachable prop called test on that class, rather than add an extra dynamic prop called @test.


No Rotating Planets

^

Non rotating 3d planets implementation added in a1489a8

Public release of planets planned only after rotation is implemented. Rotation planned to be added very soon.

Rotation implemented in 79be037 . Closing issue


global variable definition seems incorrect

The following program sample.go triggers a panic with the latest version:
package main

var optionsG map[string]string = nil

var roundG = 30

func main() {

	dummy := roundG

	roundG = dummy + 1
	println(roundG)

	println(optionsG)
}

Expected result:
$ go run ./sample.go
30
nil

Got:
$ yaegi ./sample.go
9:2: panic
failed to run script(sample.go): reflect: call of reflect.flag.mustBeAssignable on zero Value

Thanks for this report.
What happened here is that the dummy + 1 operation attempted to write its result to the wrong frame location, due to a frame indirection level not correctly updated. The PR #733 fixes that.


WIP: Improve *-all error message output

Hi all,
Thanks for this awesome project, we are using it in production with 50+ AWS accounts in our two organizations every day!
This PR aims to improve the readability of the *-all error messages. With our huge codebases, it can get really hard to find a small module, which errors out during a big apply-all run. The PR tries to improve this, by printing the root-cause error messages at the end of the execution run. Root-cause in this case means all module errors, excluding dependency errors.
Please let me know if you have any suggestions to improve this further.

I know using global variables is probably not the best way to achieve this, but I tried it earlier by incorporating the variables into the Stack struct, but this made everything way more complicated, so I decided to go for readability.
Also the go channel is currently not really needed, but might improve readability and future refactoring, as the concurrency is now explicitly coded.
Do you have any suggestions for unit tests?

Nice, thanks for the PR! Could you share an example of what the log output will look like now (a small snippet, not the whole thing, of course)?
Please note that we're going to hold off on merging anything until #466 is resolved, as that's very high priority. Once that one is in, please pull the latest from master, and give us a ping to review.

@brikis98 I just rebased from master and pushed again.
The output currently looks like this: At the end of the exuction of an *-all command, we see the following summary when errors occurred. The output with terraform > v0.12 is a little bit more verbose now, as it prints an additional warning:

Warning: Skipping backend initialization pending configuration upgrade

[terragrunt] 2019/06/10 22:50:20 Encountered the following root-causes:
------------------------------------------------------------------------------------------------------------------------------------
Module /Users/msvechl/go/src/github.com/gruntwork-io/terragrunt/test/fixture-auto-retry/apply-all/app1:
[terragrunt] [/Users/msvechl/go/src/github.com/gruntwork-io/terragrunt/test/fixture-auto-retry/apply-all/app1] 2019/06/10 22:50:20 Running command: terraform init

Warning: Skipping backend initialization pending configuration upgrade

The root module configuration contains errors that may be fixed by running the
configuration upgrade tool, so Terraform is skipping backend initialization.
See below for more information.

Terraform has initialized, but configuration upgrades may be needed.

Terraform found syntax errors in the configuration that prevented full
initialization. If you've recently upgraded to Terraform v0.12, this may be
because your configuration uses syntax constructs that are no longer valid,
and so must be updated before full initialization is possible.

Terraform has installed the required providers to support the configuration
upgrade process. To begin upgrading your configuration, run the following:
    terraform 0.12upgrade

To see the full set of errors that led to this message, run:
    terraform validate

Error: Unsupported block type

  on main.tf line 1:
   1: outputa "app1_text" {

Blocks of type "outputa" are not expected here. Did you mean "output"?

------------------------------------------------------------------------------------------------------------------------------------
Module /Users/msvechl/go/src/github.com/gruntwork-io/terragrunt/test/fixture-auto-retry/apply-all/app2:
[terragrunt] [/Users/msvechl/go/src/github.com/gruntwork-io/terragrunt/test/fixture-auto-retry/apply-all/app2] 2019/06/10 22:50:20 Running command: terraform init

Warning: Skipping backend initialization pending configuration upgrade

The root module configuration contains errors that may be fixed by running the
configuration upgrade tool, so Terraform is skipping backend initialization.
See below for more information.

Terraform has initialized, but configuration upgrades may be needed.

Terraform found syntax errors in the configuration that prevented full
initialization. If you've recently upgraded to Terraform v0.12, this may be
because your configuration uses syntax constructs that are no longer valid,
and so must be updated before full initialization is possible.

Terraform has installed the required providers to support the configuration
upgrade process. To begin upgrading your configuration, run the following:
    terraform 0.12upgrade

To see the full set of errors that led to this message, run:
    terraform validate

Error: Unsupported block type

  on main.tf line 1:
   1: outputwas "app2_text" {

Blocks of type "outputwas" are not expected here.

[terragrunt] 2019/06/10 22:50:20 Encountered the following errors:
Hit multiple errors:
exit status 1
Hit multiple errors:
exit status 1

Still, having all errors and the related modules printed at the end of the runner is a great benefit when running large executions. Please let me know what you think.

Thanks for the feedback @brikis98!
I did some refactoring and removed the channels. For sure I will add tests once this last bit is resolved.
Do you have any idea why I still get the terraform init output, even though I only print the stderr stream at the end?

Do you have any idea why I still get the terraform init output, even though I only print the stderr stream at the end? As far as I know the terraform init messages should be on the stdout stream.

Not sure I follow. You seem to be getting an error about a missing variable. What does stdout or stderr have to do with it?

What I posted is the new detailed output of my change. The idea is to have a summary of all module errors including their error messages (stderr) at the end of the execution. If you check out https://github.com/gruntwork-io/terragrunt/pull/722/files#diff-86e77ee353cd3bacb4a1f0c492bf9e2cR169 of my change, you can see that I am capturing the stderr and outputting it in the collectErrors() method: https://github.com/gruntwork-io/terragrunt/pull/722/files#diff-86e77ee353cd3bacb4a1f0c492bf9e2cR186.
Somehow the terraform init code shows up in the stderr stream, even though when I do a normal terraform run, it is printed to stdout.
So my question would be if you have any idea why the terraform init output shows up in `stderr.

Ohhhh, I gotcha, thx for providing the context 😁
The behavior you're seeing is probably from this: https://github.com/gruntwork-io/terragrunt/blob/master/cli/cli_app.go#L606-L607

Yep, thats it.
In the comment here it says:

Don't pollute stdout with the stdout from Auto Init

So I assume it will not be a big issue moving this back to stdout? Of course I will run the tests to make sure.
Also I found this part where the logger is set by default to stderr, which also leads to some pollution of my error output.
I now adjusted both parts and now the detailed error output is clean. Can you think of any issues these changes could cause from the top of your head?

Can you think of any issues these changes could cause from the top of your head?

Yes. Consider someone running the following:
url=$(terragrunt output url)

They expect that the value of the output variable url, and only that value, is written to stdout. If the auto init functionality writes to stdout, then that assumption will break. Hence, we redirect auto init output to stderr.
In general, if you run terragrunt <cmd>, where <cmd> is any standard Terraform command, what's written to stdout should be the same as if you had run terraform <cmd> directly.

Thanks for clarifying, of course that makes perfect sense.
In this case we would either have to live with the more verbose detailed error message at the end of the execution, or I would have to come up with some way of extracting the auto-init output from the detailed error message.
I will look into it again.

Alright, I made it work by saving the auto-init output and extracting it from the detailed error messages.
The current detailed error messages now look like this:
[terragrunt] 2019/07/02 23:46:37 Encountered the following errors:
====================================================================================================================================
/Users/msvechl/go/src/github.com/gruntwork-io/terragrunt/test/fixture-auto-retry/apply-all/app1 (root error):

Hit multiple errors:
exit status 1

[terragrunt] [/Users/msvechl/go/src/github.com/gruntwork-io/terragrunt/test/fixture-auto-retry/apply-all/app1] 2019/07/02 23:46:37 Running command: terraform init

Error: Reference to undeclared input variable

  on main.tf line 2, in output "app1_text":
   2:   value = "app1 output ${var.aasd}"

An input variable with the name "aasd" has not been declared. This variable
can be declared with a variable "aasd" {} block.

------------------------------------------------------------------------------------------------------------------------------------
/Users/msvechl/go/src/github.com/gruntwork-io/terragrunt/test/fixture-auto-retry/apply-all/app2 (dependency error):

Cannot process module Module /Users/msvechl/go/src/github.com/gruntwork-io/terragrunt/test/fixture-auto-retry/apply-all/app2 (excluded: false, dependencies: [/Users/msvechl/go/src/github.com/gruntwork-io/terragrunt/test/fixture-auto-retry/apply-all/app3, /Users/msvechl/go/src/github.com/gruntwork-io/terragrunt/test/fixture-auto-retry/apply-all/app1]) because one of its dependencies, Module /Users/msvechl/go/src/github.com/gruntwork-io/terragrunt/test/fixture-auto-retry/apply-all/app1 (excluded: false, dependencies: [/Users/msvechl/go/src/github.com/gruntwork-io/terragrunt/test/fixture-auto-retry/apply-all/app3]), finished with an error: Hit multiple errors:
exit status 1

------------------------------------------------------------------------------------------------------------------------------------
[terragrunt] 2019/07/02 23:46:37 Unable to determine underlying exit code, so Terragrunt will exit with error code 1

What do you think? Should we also make this output optional or use it by default?

So that's the output you see at the end of an xxx-all call?
If so, I think that looks like a terrific improvement. I assume those errors are grouped by module?

Yep, that is correct. As the collectErrrors() method loops over all running modules, this automatically groups all the errors by module.
I will try and add some tests now.

Alright, I just added module and integration tests. Do you have further improvement suggestions?

I did some refactoring to separate the normal and detailed errors in the MultiError struct. This also fixed problems with some of the tests. Do you have any further input @brikis98?

Apologies for the delay! Been completely buried. I really appreciate this PR and will try to review this as soon as I can. 🍺

Don't worry, take your time! Just get back to me when you can 👍


export trial status to csv

using nnictl trial export xxxxxxxx -f hello.csv
test code pending discussion with @chicm-ms

please update doc or docstring accordingly


[FEATURE] Missing function editor.setEditorValue(value)

Is this a unique feature?

[X] I have checked "open" AND "closed" issues and this is not a duplicate

Is your feature request related to a problem/unavailable functionality? Please describe.
Here's a function to get the editor content (document)
const editorContent = editor.getEditorValue();
but no way to set it with similar function editor.setEditorValue(value);
Proposed Solution
Implement function editor.setEditorValue(value); that also should rerender YoptaEditor component
Screenshots
No response
Do you want to work on this issue?
No
If "yes" to the above, please explain how you would technically implement this (issue will not be assigned if this is skipped)
No response

Added in v4.2.0