az login --use-device-code fails with InvalidAuthenticationTokenAudience when providing non-ARM --scope

Describe the bug
When specifying a non-ARM scope for device code flow to work with Conditional Access MFA, Azure CLI fails:
> az login --scope https://containerregistry.azure.net/.default --use-device-code

To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code xxx to authenticate.

(InvalidAuthenticationTokenAudience) The access token has been obtained for wrong audience or resource 'https://containerregistry.azure.net'. It should exactly match with one of the allowed audiences 'https://management.core.windows.net/','https://management.core.windows.net','https://management.azure.com/','https://management.azure.com'.

This is how Azure CLI interacts with ADAL:
https://github.com/Azure/azure-cli/blob/14cc787d0f58bc649d402b486fdecc5625eee9ac/src/azure-cli-core/azure/cli/core/_profile.py#L936-L938

Send https://containerregistry.azure.net as resource to acquire_user_code
Send https://management.core.windows.net as resource to acquire_token_with_device_code

However, due to https://github.com/AzureAD/azure-activedirectory-library-for-python/issues/255, the second step returns an access token for https://containerregistry.azure.net which can't be used to call ARM API.

After MSAL migration (https://github.com/Azure/azure-cli/pull/19853), this issue will be resolved because CLI changes how it works with device code flow:

Send https://containerregistry.azure.net/.default as scope to initiate_device_flow
Send no scope to acquire_token_by_device_flow. A refresh token and access token for https://containerregistry.azure.net/.default are returned.
Use the refresh token to get another access token for https://management.core.windows.net//.default


Update to support simulation of different client's speed in async mode

Description

In the async mode, most of the clients have a relatively fast speed, so it is sometimes quite hard to test Plato in a scenario where clients have various different speeds. This change allows users to simulate clients' speeds by providing a distribution in the configuration file. The user can also choose to only enable the simulation without providing a specific distribution, and the code would just use a default one.
Currently, the simulation only supports Zipf and Normal distribution. More distributions can be added in the future.
How has this been tested?

Test 1 with default distribution:
Run ./run -c ./configs/MNIST/fedavg_async_lenet5.yml
Test 2 with Normal distribution:
First update the client configuration in configs/MNIST/fedavg_async_lenet5.yml as below:

clients:
    type: simple

    total_clients: 2

    per_round: 2

    do_test: false

    simulation: true

    simulation_distribution:
        distribution: normal
        mean: 2
        sd: 1

Then run  ./run -c ./configs/MNIST/fedavg_async_lenet5.yml

Test 3 with Zipf distribution:
First update the client configuration in configs/MNIST/fedavg_async_lenet5.yml as below:

clients:
    type: simple

    total_clients: 2

    per_round: 2

    do_test: false

    simulation: true

    simulation_distribution:
        distribution: zipf
        s: 2

Then run  ./run -c ./configs/MNIST/fedavg_async_lenet5.yml
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue) Fixes #
[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:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Additional information
The current implementation deviates a bit from the original intent. The original intents were to put clients to sleep at the end of each epoch. To accomplish that, the await asyncio.sleep() code should be inserted in method Trainer.train_process() in file plato/trainers/basic.py, and that would require the method Trainer.train_process() to be changed to async, and we need to change every function that calls train_process() to async. I'm afraid that might break the code, so I just stay with the current implementation, where the clients are put to sleep after they finished the model training.
UPDATE: please ignore the information above, the code is now implemented in a way such that clients are put to sleep at the end of each epoch. Please refer to the conversation below for details.

We may still need to sleep at the end of each epoch, rather than at the end of each communication round. The training loop will need to be modified anyway due to the need for training to terminate prematurely when the servers requests a client to do so, so implementing a finer granularity sleep simulation in the training process may not be so risky and detrimental.

I see. That makes a lot of sense. The code is now modified such that clients are put to sleep at the end of each epoch in the simulation.
Thanks.

It appears that when max_concurrency in the trainer is not set, the clients will use exactly the same sleep time. Perhaps this is because the current code uses mp.Manager().dict() to store the sleep times simulated, yet without max_concurrency set, no processes will be spawned.

It seems like the problem is related to the random seed. I tried to run fedavg_async_lenet5.yml with random_seed and max_concurrency not set, and the clients had different sleep times.
I guess the seed is set sometime before train_process() is called, but with max_concurrency set, function train_process() is executed in a new process, so the memory related to the seed does not pass along. However withmax_concurrecy not set, no new process will be spawned, so the random seed will cause the clients to have exactly the same sleep time.
Thanks.

I have updated the implementation by removing the use of mp.Manager().dict() as it is causing memory leaks on my end (running on Windows 10) as well as failing the auto-tests.
Thanks.

I have fixed a bug related to obtain_model_update() in trainers/basic.py. The trainer originally uses self.tic + training_time to compare with wall_time. However, self.tic is initialized by time.perf_counter(), while wall_time is initialized by time.time() on the server side. These two numbers differ significantly (at least on my side), so the function never really finds and returns the model closest to wall_time with checkpoints files.
I updated the code such that obtain_model_update() uses a new variable self.training_start_time to replace self.tic, and self.training_start_time is set to time.time() at the beginning of function train(). This way, the function actually returns the model right after the time when sever requests for urgent model update.

Makes a lot of sense! Thank you! There could be other issues in the current codebase; I'm still testing it.

No problem. I will also continue to test the code.
Thanks

I have added the implementation for FedAsync. The overall structure is completed, but currently there is a small bug where an AssertionError will be raised from base.Server.choose_clients() if the total number of clients is the same as the number of clients selected per round, and I'm still working on resolving it.
Thanks.

I revised the design of FedAsync, as the previous design was faulty as it bypassed all the existing mechanisms on simulating the wall clock time and asynchronous mode.

I see. The revised structure makes more sense. But one small issue is that since we are now using process_client() of class base.Server, the client technically does not get processed immediately after it reports back in FedAsync. The client reports will need to wait for at most periodic_interval seconds to be picked up and processed by periodic_task(). Would that be an issue? Or is it a delay we can tolerate for FedAsync?
Thanks

No, this is not an issue as long as the periodic interval is sufficiently short, and much shorter than the typical time needed for local training on a client.

Ok I see. Thanks!

No, this is not an issue as long as the periodic interval is sufficiently short, and much shorter than the typical time needed for local training on a client.

Also, the duration of the periodic interval does not lead to any inaccuracy to the experimental results, since we will be simulating the wall clock time, taking advantage of all the recent work towards this direction.

Thanks! That makes a lot of sense.
I have also taken a deeper look at the bug of AssertionError of select_clients(). It seems like this is not specific to FedAsync, and it is not really a bug. Generally for asynchronous mode (without setting simulation, simulate_wall_clock, and request_update), the total number of clients (total_clients) needs to be at least twice the number of clients selected per round (per_round) to ensure that the AssertionError will not be triggered. Because the reported clients and clients that are still training cannot be re-selected when select_clients() is called, there need to be per_round idle clients available for selection.
I guess a question would be why couldn't we re-select the clients that already report back (i.e. in the self.reporting_clients list) for the next training round?
Thanks

Thanks! That makes a lot of sense.
I have also taken a deeper look at the bug of AssertionError of select_clients(). It seems like this is not specific to FedAsync, and it is not really a bug. Generally for asynchronous mode (without setting simulation, simulate_wall_clock, and request_update), the total number of clients (total_clients) needs to be at least twice the number of clients selected per round (per_round) to ensure that the AssertionError will not be triggered. Because the reported clients and clients that are still training cannot be re-selected when select_clients() is called, there need to be per_round idle clients available for selection.
I guess a question would be why couldn't we re-select the clients that have already reported back (i.e. in the self.reporting_clients list) for the next training round in select_clients()?
Thanks

This is due to the fact that, in asynchronous mode when the wall clock time is simulated, the server will need to wait for all the clients per round to report before it can take action. After it has processed the first minimum_clients_aggregated (say, 2) clients, the simulated wall clock time is advanced so that these 2 clients are in the history, but the other clients are still in the future in simulated wall clock time, even though they have already reported. In other words, the wall clock time that's simulated on the server decides what the current time is. The server certainly couldn't select a client that is currently still training locally in real-time, so it couldn't do so in simulated time either.


⚠ ClamAV has degraded performance

In 6720ac9, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 72 ms

Resolved: ClamAV performance has improved in f5211fe.


crosslinks proposals

PR #5525 introduces section-to-section crosslinks so that users looking for Angular books will find them whether they are looking for Angular or AngularJS.
This issue asks the community:

Is this a good way to make this repo more useful?
Should crosslinks look different from what is being done in #5525?
When should we add a crosslink? Should Android be crosslinked with Java? When should crosslinks should NOT be added? (we need guidelines)
how does this relate to #5249 (dealing with language agnostic books)

At a glance.... the proposal syntax is...
All crosslinks starts with > :information_source:  and uses horizontal ellipsis … as delimiter between crossed sections and it alphabetized text. This markup goes between heading and it listing first item preseving the 1 whitespaces rule on all of them.
One way reference:
### Heading A

> :information_source: See also … [Heading B](#heading-b)

* [Awesome book in A](https://library.example.com/awesome-book-a) - creator 1, creator2 et al. (FORMAT) (platform) (*notes*)

Two sides reference:
### Heading A

> :information_source: See also … [Heading Z](#heading-z)

* [Awesome book in A](https://library.example.com/awesome-book-a) - creator 1, creator2 et al. (FORMAT) (platform) (*notes*)

### Heading Z

> :information_source: See also … [Heading A](#heading-a)

* [Awesome book in Z](https://library.example.com/awesome-book-z) - creator 1, creator2 et al. (FORMAT) (platform) (*notes*)

Multireference: separate each one by a comma
### Cabecera A

> :information_source: Véase también … [Cabecera M](#cabecera-m), [Cabecera Z](#cabecera-z)

* [Un recurso alucinante en A](https://libros.example.com/libro-a) - creator 1, creator2 et al. (FORMAT) (platform) (*notes*)

### Cabecera M

> :information_source: Véase también … [Cabecera A](#cabecera-a)

* [Un recurso alucinante en M](https://libros.example.com/libro-m) - creator 1, creator2 et al. (FORMAT) (platform) (*notes*)

### Cabecera Z

* [Un recurso alucinante en A](https://libros.example.com/libro-a) - creator 1, creator2 et al. (FORMAT) (platform) (*notes*)

I hope this snippets helps to understand what is the idea.

did you try having the crosslinks below the list?

did you try having the crosslinks below the list?

I could try. Let me a bit to prepare a demo in my deploy with Angular resources

did you try having the crosslinks below the list?

It works fine at bottom too. No problems with linter if rule 1-0-2 is respected.
Now the rule will be 1-(0-1)*-0-2 at top, or 1-0-(1-0)*-2 if placed at bottom :laughing:
Here the example in both sides I promised (javascript section): DEPLOY and CODE BRANCH

Only one note: I prefer at top if lists are long because is more intuitive and don't need scroll

I was thinking that if we separate out the "language agnostic" section to a separate page, we might need more than one crosslink, and you don't want people scrolling through crosslinks to get to the listings. I looked in a cookbook with many "see also" listings in the index - it puts the cross links in the topic heading itself.

Well-thinking!
But If crosslink is attached after section title, auto TOC is broken in markdown because generated ids change according to heading text.
Therefore the multireference variant: one after other comma delimited.


Remove snapshots folders

This is related to to Issue 624.
Remove demo is not deleting snapshot folder under store.
Pull Request Template
The code review checklist below is used for all pull requests.

Review the list before submitting your pull request.
Leave the list intact for the code reviewer's use.

Checklist

[x] Latest code from master has been merged into the pull request branch
[x] Code is camelCased
[x] No commented out code (if required, place // TODO above with explanation)
[x] No linting issues
[x] Automated tests exist and pass
[x] Build is successful (npm run build)
[x] Works in IE 11, Chrome, Firefox, and Edge

Thanks!
:heart:

Coverage remained the same at 91.525% when pulling de91a3620e9e241a866559b5d830f8e4cd45a636 on kkankala:master into e12cf52a2360f0dddf07016071d244ec97e76436 on coryhouse:master.

Thanks!


"Application Insights" is not in a "Metric source"

At step "Provide a name for the scale setting, and the click on "Add a rule"..." I couldn't find "Application Insights" item. I want to create an autoscale rule for a web app(windows, core 2.2) S1 with application insights connected. Are there any extra steps required?

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

ID: 891f8dc0-5fa1-e5d7-5bf8-3ae6a3a60d7f
Version Independent ID: 496865c8-9065-c9b4-92de-1bb134db2ec8
Content: Autoscale in Azure using a custom metric
Content Source: articles/azure-monitor/platform/autoscale-custom-metric.md
Service: azure-monitor
Sub-service: autoscale
GitHub Login: @anirudhcavale
Microsoft Alias: ancav

More context:
http://prntscr.com/o68ant
http://prntscr.com/o68acx
http://prntscr.com/o68as9

@aderesh Thank you for your feedback! We will review and provide an update as appropriate.

@anirudhcavale For assistance.

slecting "Other Resource", and then "Application Insights" seem to be working.

@aderesh - @cijothomas has it right in the ocmment above. You have to choose the "Other resource" menu item, then select application insights as the resource type. The docs need to be updated with new screenshots.

#label:"CreateAzMonWIFeb2021"  New screenshots

Will update the documentation to update, where user should choose 'Other resource'

Noted, added the update the documentation with revised screenshots to our backlog. Closing.
#please-close


Make withCredentials configurable

In order for cookie to work for flutter web, we need to set the withCredentials = true.

Thanks for this PR.
LGTM


[CCL] Making buffer size dynamic to input slice

Ticket

#10062

Problem description
Currently, if a worker slice has size X and the channel buffer has a size Y, and X < Y, the channel will pad the message to size Y and send it. Therefore, an optimization is to change is to ensure that if X < Y, the sent message is the raw unpadded version with a size of X.
What's changed

add_sender_channel and add_reciever_channel now instantiate the current largest_message_size_bytes
in the EDM builder, where add_*_channel is called, pass along the expected message size for that worker

Checklist

[ ] Post commit CI passes
[ ] Model regression CI testing passes (if applicable)

CCL Post Commit Test: https://github.com/tenstorrent/tt-metal/actions/runs/9895307908


[Hacker wanted]: Looking for 2 more members (FE developer and designer)

Pitch it!
I'm co-founder of a blockchain dev company and a backend and smart contract developer who has built and designed a few  DeFi and other protocols from scratch. I love ideas and building them.
My friend is a founder of a project and also very knowledgeable in the blockchain space with awesome presentation skills and lots of ideas.
We've come up with some concepts around decentralized reputation. Generally, we're very open to new ideas and suggestions as well.
As there can be only 4 team members, we for sure need at least one FE developer. Ideally, this person alsoknows some design, or we can also take one UX/UI designer on board.
Send me a DM on Telegram, and we can quickly sync up on the idea and other details.
Skills wanted
Tell us what you are looking for:

[ ] Core Blockchain Development (Go, Rust, C++)
[ ] Smart Contracts (Solidity, Vyper)
[x] dApps (JavaScript, webdev)
[ ] Blockchain Operations, Infrastructure
[ ] Game theory, Crypto-Economics
[x] Design, User Experience
[ ] Project Management
[ ] Other:

Communication

[x] telegram: @dan_ryptoc

I sent DM. Please see it. Thank you!!!


add development/feature branches

to keep the main branch clean it can be a good idea to add little changes and changes that might break the project somewhere other than the main branch, and then merge to the main branch when there has been a significant change built up and all the tests are passing.

look into "branch strategies" for more information on different strategies for creating and managing branches. The three main ones are git flow, github flow, and gitlab flow.

develop branch added. @The-Chorus chose to use git flow.


feat: installer for the runner

Summary of Changes
Add a command "Install the Safe-DS Runner" to automatically install the runner and update the settings accordingly. It also gets suggested in the error message if the runner could not be started.

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

npm package (@latest dist-tag)
npm package (@latest dist-tag)
v0.12.0
GitHub release

Your semantic-release bot :package::rocket:


Fixed Apache Ant version in Dockerfile

Description
The main.yml workflow kept failing on me, so I figured it would be useful to fix the Apache Ant version issue that was making the docker build fail.
You can find the successful build logs here: https://github.com/dtemir/labgraph/runs/6014180685?check_suite_focus=true
You can find the unsuccessful build logs here: https://github.com/facebookresearch/labgraph/runs/5803725955?check_suite_focus=true
Type of change

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

Feature/Issue validation/testing
Testing is done by running the main.yml in GitHub Actions
Checklist:

[X] New and existing unit tests pass locally with these changes?

Thanks for this fix!


Make decryption code fail-fast AFTER logging the error.

This was driving me crazy recently trying to debug code running on my server that was set to failOnError=true, which was covering up any logging of the actual error message in the logs. Would love to get this fixed unless there is a good reason not to do it. Thanks!

@rhanton Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@rhanton Thank you for signing the Contributor License Agreement!

How about a test?

@spencergibb Is there a good paradigm folks here would use for testing the appearance or not of log statements?

Yes, the OutputCapture junit rule. See RefreshAutoConfigurationMoreClassPathTests

Thanks @spencergibb - I added a tweak to the two existing junit tests that shows logging of decryption errors both when failOnError is true and when it is false. Thanks!

Any ideas why the build is failing on CircleCI @spencergibb ?

I see similar errors when I build your branch locally.

I don't see the issue locally, I wonder if it was #358 that I just merged.

@rhanton could you update your branch?

Merged this as part of https://github.com/spring-cloud/spring-cloud-commons/commit/656feb275823eb4672658bf5b6f8f3b66ede2989


Translations functions are not used properly

Currently, because ngettext for plural mesages  is aliased as _  gettext catalogs would be wrong.
This is doucmented in Django documentation:
https://docs.djangoproject.com/en/4.2/topics/i18n/translation/#standard-translation

What functions may be aliased as _?
Because of how xgettext (used by makemessages) works, only functions that take a single string argument can be imported as _:
gettext()
gettext_lazy()

Also, I propose to use lazy translations.

In other commits there are more gettext related fixes and I have added special_characters to help text and message, as user should know which special characters she can use and adding them in translation catalog is difficult to escape. I have updated tests for this.
@ezrajrice please let me know if anything else is needed regarding this

PR: https://github.com/ezrajrice/django_advanced_password_validation/pull/9

@alex-a-pereira I apologize for the inconvenience. Life got in the way when I was setting up my automated deployment to PyPI and I forgot to make sure the fixes got there. There is a new version on PyPI and a new Release here on GitHub (see v1.2.0). I specifically added testing for your version of Django and Python combination and the build is currently passing the tests.


How to read stack trace from fatal error handler?

I've added my own fatal error handler following the guide here: https://wiki.duktape.org/howtofatalerrors
So far so good, I'm able to handle the error and the provided message as expected in my application, but how can I print the stack trace from the fatal error handler? Or would it be advised to just do everything inside duk_pcal/duk_peval and equivalent protected methods? What about for cases that don't have a protected API call?

A fatal error handler only receives an error message string to be stored/printed in whatever way suits the application. You should not call any Duktape API calls from the fatal error handler: the handler may be called when it's unsafe to do so. There is also no access to the stack trace of the fatal error, only the string message.
In production applications where you generally may not want to abort() on a fatal error (there are exceptions to this of course), you should always begin an API call sequence with e.g. duk_safe_call() or other protected call. Unsafe API calls (calls that may throw) should then happen inside the protected call wrapper.

Ok, got it! Thank you

You're welcome!


Add Tests for AES Key Wrap Cipher Functionality

Added tests to apply NIST AES Key Wrap (RFC-3394 and RFC-5649) vectors to the kmyth AES Key Wrap cipher implementation.

Latest commit updates to a hopefully less obtrusive means of reporting to the user whether the unit tests include test-vector-based tests or not. Lastest commit also attempts to implement some of the recent changes to the vector file processing loop for the AES/GCM code in a similar manner.


Outdated cask: slack

Outdated cask: slack.
Info:

version: 1.1.10.
appcast url: https://rink.hockeyapp.net/api/2/apps/38e415752d573e7e78e06be8daf5acc1.

Full appcast:
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
<title>Slack</title>
<link>https://rink.hockeyapp.net/api/2/apps/38e415752d573e7e78e06be8daf5acc1</link>
<item>
  <title>Version 1.1.10 (3117)</title>
  <description>

Slack 1.1.10

Release Notes

Fixed: Up there in the View menu are options to increase or decrease the size of the Slack display. For reasons that are too embarrassing to go into, no matter if you chose increase, or decrease, we wrote increase to your preferences. So if you went up two sizes, then down two sizes, then quit and relaunched everything would be 4x bigger. Seriously. Yeah, we know.

Fixed: A pesky bug that would cause Slack notification sounds to play even if you had OS-level Do Not Disturb enabled.

Fixed: A crash if you were signed in to multiple accounts, quit the app, had one of the accounts disabled, and then launched again. It&#8217;s sad enough that you were removed from a Slack team, we shouldn&#8217;t make it worse by crashing repeatedly afterwards…so now we don&#8217;t.

Fixed: Sometimes, if you left Slack running all night on a sleeping machine — specifically if the computer was asleep when the time crossed midnight — it would crash and need to be helped back to life, in some bizarre inexplicable software version of a Cinderella Complex. After considerable therapy, the app once more believes in itself as a strong, independent entity, and will live happily ever after, even over the witching hour. Until the next time.

For your consideration: we&#8217;ll be making some changes in our upcoming 2.0 release that will force you to sign in to your team(s) anew. We want you to be prepared for the inevitable&#8230;so please keep your password(s) at the ready! We apologize for the inconvenience.

</description>
  <pubDate>2016-01-08 20:53:19 UTC</pubDate>
  <enclosure sparkle:version="3117" sparkle:shortVersionString="1.1.10" url="https://rink.hockeyapp.net/api/2/apps/38e415752d573e7e78e06be8daf5acc1/app_versions/34?format=zip&avtoken=444ac582c97e2e3c99dd6bda07cdca3401de9909" length="21831298" type="application/octet-stream"/>
  <sparkle:minimumSystemVersion>
10.9      </sparkle:minimumSystemVersion>
</item>
<item>
  <title>Version 1.1.9 (3059)</title>
  <description>

Slack 1.1.9

Mac SSB 1.1.9 Release Notes

New: Updated emoji spritesheets. Now you can visually describe that time you got caught in a freak taco tornado with unnerving realism.

Fixed: We found what can only be described as a &#8220;hella big&#8221; memory leak that would happen any time you opened and closed a Post window. It has now been closed for, hopefully, good.

Fixed: The menu items to zoom the text size in and out now works in Posts windows. It was supposed to all along but it didn&#8217;t and we apologize for any frustration or eye strain this may have caused.

Fixed: If you went fullscreen, then went to add a new team, then switched windows, then went to add another new team we would crash. As a special holiday gift to you we no longer crash.

Slack will discontinue support for Mac OS X 10.8 in the next release. This is the final release that will support OS X 10.8.

</description>
  <pubDate>2015-12-14 18:06:39 UTC</pubDate>
  <enclosure sparkle:version="3059" sparkle:shortVersionString="1.1.9" url="https://rink.hockeyapp.net/api/2/apps/38e415752d573e7e78e06be8daf5acc1/app_versions/33?format=zip&avtoken=da656b5d702e95a7cd69ebd65856fb8b9476c38a" length="21550654" type="application/octet-stream"/>
  <sparkle:minimumSystemVersion>
10.8      </sparkle:minimumSystemVersion>
</item>
<item>
  <title>Version 1.1.8 (3051)</title>
  <description>

Slack 1.1.8

Mac SSB 1.1.8 Release Notes

Fixed: If you quit Slack while a download was in progress we&#8217;d leave things in a weird state that made it impossible to resume the download when you relaunched. Now, once you reload, you can resume that download and that download will be yours forever*. *Or for the internet value of &#8220;forever&#8221;.

Fixed: The version number in the about pull down is now copyable text.

Fixed: In our last release we fixed a bug where we were dismissing notifications too aggressively, which was bad. But then we discovered that if your Notification Center preferences were set to alerts instead of banners then we wouldn&#8217;t ever dismiss the notification… ever. Which was the opposite (not the opposite of &#8220;bad&#8221;, we mean. It was still bad). Clicking on the notification will now both bring Slack to the foreground, AND dismiss the notification.

Fixed: If you had your mouse set to treat two-finger swipes as forward/backward actions we, well? We had the directions backwards. Let&#8217;s never mention it again.

Fixed: We just can&#8217;t get enough of fixing data cache corruption bugs… So we fixed another one, because we needed to. Not because we wanted to distract you from the idiocy of the two-finger swipe thing we promised never to mention agai… Oh darn.

</description>
  <pubDate>2015-10-29 02:42:27 UTC</pubDate>
  <enclosure sparkle:version="3051" sparkle:shortVersionString="1.1.8" url="https://rink.hockeyapp.net/api/2/apps/38e415752d573e7e78e06be8daf5acc1/app_versions/26?format=zip&avtoken=ffaa98308c5c5da9faa664c25586f8f2b81a0d56" length="22440490" type="application/octet-stream"/>
  <sparkle:minimumSystemVersion>
10.8      </sparkle:minimumSystemVersion>
</item>
<item>
  <title>Version 1.1.6 (3001)</title>
  <description>

Slack 1.1.6

Mac SSB 1.1.6 Release Notes

- New: Some plug-ins were giving up, and letting us down by not showing video, making people  run around reinstalling plug-ins or desert the idea of watching video entirely. All our lovely media providers now serve us direct content that means we&#8217;ve been able to say goodbye to plug-ins forever. Now nothing can stop your roll.

- Fixed: We updated crash reporting library to fix problems with it, itself, crashing. Very meta.

- Fixed: The click targets of the team icons down the left side of the window were sometimes smaller than they should have been. It is no longer frustratingly difficult to click on the team icons.

- Fixed: A bug that would prevent files from downloading properly — well, at all — for users on Mac OS X 10.7. (Side note: this is the last version of the app that will support OS X 10.7, because of stuff like this.)

- Fixed: if your Mac abruptly shut down or restarted there was a chance that some of Slack&#8217;s cached data would be left in a bad state. We now detect that this has happened and recover, which we feel is preferable to just crashing every time you launched the app.

- Fixed: An unfortunate bug that would cause unfortunately poor performance when viewing Posts.

- Fixed: A font loading issue that would cause some ligatures to not render.

- Fixed: Sometimes you&#8217;d get a notification, and you&#8217;d reply directly from the notification, and the reply would never get posted. Now they always do.

- Fixed: …And as if that wasn&#8217;t enough, sometimes we&#8217;d accidentally clear all of your Slack notifications, whether you&#8217;d read them or not. That was a doozy. We do not do that anymore.

- Fixed: A rare bug could leave you staring at a sign-in screen when all you wanted was to reload your content. We love our sign-in page, and first impressions are important… but not that important.

</description>
  <pubDate>2015-10-07 22:12:09 UTC</pubDate>
  <enclosure sparkle:version="3001" sparkle:shortVersionString="1.1.6" url="https://rink.hockeyapp.net/api/2/apps/38e415752d573e7e78e06be8daf5acc1/app_versions/22?format=zip&avtoken=bd27a443d74858aca4b8ff549caaf812c6afa7b3" length="16965754" type="application/octet-stream"/>
  <sparkle:minimumSystemVersion>
10.7      </sparkle:minimumSystemVersion>
</item>
<item>
  <title>Version 1.1.4 (2815)</title>
  <description>

Slack 1.1.4

Mac SSB 1.1.4 Release Notes

- New: when viewing completed downloads in the flexpane you can open the file in its default application by holding down the shift key and clicking, with great flourish, upon the desired location.

- Fixed: a vile bug that could corrupt cache files if your Mac shut down or restarted unexpectedly while Slack was running.

- Fixed: a bug that would show greater than 100% completion of file downloads. This was not a useful area for overachievement.

- Fixed: A bug causing an erroneous zipper issue, automatically decompressing gzip files after they were downloaded has been totally repaired.

- Fixed: a bug that could leave you staring at a blank white window after signing in to a team whose session expiration time was set to zero. We now process the login result using a slightly larger value of zero. If you experienced this zero or less than zero times, congratulations. If you experienced it more than that, apologies, there is zero chance of you experiencing it again.

</description>
  <pubDate>2015-09-02 23:55:25 UTC</pubDate>
  <enclosure sparkle:version="2815" sparkle:shortVersionString="1.1.4" url="https://rink.hockeyapp.net/api/2/apps/38e415752d573e7e78e06be8daf5acc1/app_versions/19?format=zip&avtoken=d11b1b4d9f90d53702d26bd4972a757345f1cfc0" length="16881840" type="application/octet-stream"/>
  <sparkle:minimumSystemVersion>
10.7      </sparkle:minimumSystemVersion>
</item>
  </channel>
</rss>

Closing in favour of #17812.


after refresh

There is a case when the plugin is not working properly.
When user A saves and after his admin edit panel is fully refreshed and THEN user B updates - all is ok.
But when two users are editing the post and both of them will press 'Update' at the same time - one of them will get this :

user B has taken over and is currently editing.
Your latest changes were saved as a revision.

I checked the parameters' set send with this heartbeat request and there was no 'fce' field, so the
\Fabrica\CollaborativeEditing\Base::filterHeartbeatResponse method is not doing what it is supposed to do.
Somehow the code
wp.heartbeat.enqueue('fce', { 'post_id' : jQuery('#post_ID').val() }, true);
in \wp-content\plugins\fabrica-collaborative-editing\js\post.js takes no effect.


New Mapnik SDK

Need to pull in updated mapnik sdk tomorrow with https://github.com/mapnik/mapnik/pull/2901 for https://github.com/mapbox/mapnik-vector-tile/issues/116. After that v3.3.1 will be ready to tag.

[x] linux/osx: @springmeyer
[x] windows: @BergWerkGIS

10 failing tests on Windows:
https://ci.appveyor.com/project/Mapbox/node-mapnik/build/1.0.518/job/q8thh3n8g8mi6jt3#L4196

@BergWerkGIS - interesting. I presume that might be due to https://github.com/mapnik/mapnik/issues/2893 (did you build with that commit?) Unix builds are using and SDK from yesterday so do not include https://github.com/mapnik/mapnik/issues/2893 /cc @artemp

y, using commit https://github.com/mapnik/mapnik/commit/167708329df701805b6925f6f4facdc33d90dcb1
Should I try another one tomorrow (about to power down, dinner's already on the table)?

@BergWerkGIS yes, don't worry about this today. Have a nice dinner!


Reconcile terminology in the sanity checker with the README

(A lot of what's here is minor Python modernization, this was written
awhile ago...)
But the main "useful" thing is to reconcile the language in the
implementation here with what's in the README now:
https://github.com/json-schema-org/JSON-Schema-Test-Suite#terminology
i.e.:
files -> files
groups -> cases
cases -> tests

Will take the silence as indifferent approval given this isn't very impactful of a change :) but anyone feel free to pipe up with improvements.


Error in Laravel 8 migration problem, There is no active transaction

after installing this package and define settings into app/config.php and publishing configuration, when i try to run this command:
php artisan migrate:fresh

i get error after this part of readme install document
Migrate it

If you have set the default connection to tracker, you can:
php artisan migrate

Error:
Migrating: 2014_10_12_100000_create_password_resets_table
Migrated:  2014_10_12_100000_create_password_resets_table (43.99ms)
Migrating: 2015_03_07_311070_create_tracker_paths_table

   PDOException

  There is no active transaction

  at vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php:189
    185▕      */
    186▕     public function commit()
    187▕     {
    188▕         if ($this->transactions == 1) {
  ➜ 189▕             $this->getPdo()->commit();
    190▕
    191▕             optional($this->transactionsManager)->commit($this->getName());
    192▕         }
    193▕

      +35 vendor frames
  36  artisan:37
      Illuminate\Foundation\Console\Kernel::handle()

I'm using Docker as LaraDock and this is my database file content:
<?php

use Illuminate\Support\Str;

return [

    'default' => env('DB_CONNECTION', 'mariadb'),

    'connections' => [

        ///
        'tracker' => [
            'driver'   => 'mysql',
            'host' => env('DB_HOST', 'mariadb'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'charset' => 'utf8mb4',
            'strict' => false,
            'collation' => 'utf8mb4_persian_ci',
        ],
        'mysql' => [
            'driver' => 'mysql',
            'url' => env('DATABASE_URL'),
            'host' => env('DB_HOST', 'mariadb'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'unix_socket' => env('DB_SOCKET', ''),
            'charset' => 'utf8mb4',
            'collation' => 'utf8mb4_persian_ci',
            'prefix' => '',
            'prefix_indexes' => true,
            'strict' => true,
            'engine' => null,
            'options' => extension_loaded('pdo_mysql') ? array_filter([
                PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
            ]) : [],
        ],

        ///

        'laravel-visits' => [
            'host' => env('REDIS_HOST', '<IP_ADDRESS>'),
            'password' => env('REDIS_PASSWORD', null),
            'port' => env('REDIS_PORT', 6379),
            'database' => 3, // anything from 1 to 15, except 0 (or what is set in default)
        ],

    ],
    'migrations' => 'migrations',

    /

    ///

    ],

];

Hello

after installing this package and define settings into app/config.php and publishing configuration, when i try to run this command:
php artisan migrate:fresh

i get error after this part of readme install document
Migrate it

If you have set the default connection to tracker, you can:
php artisan migrate

Error:
Migrating: 2014_10_12_100000_create_password_resets_table
Migrated:  2014_10_12_100000_create_password_resets_table (43.99ms)
Migrating: 2015_03_07_311070_create_tracker_paths_table

   PDOException

  There is no active transaction

  at vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php:189
    185▕      */
    186▕     public function commit()
    187▕     {
    188▕         if ($this->transactions == 1) {
  ➜ 189▕             $this->getPdo()->commit();
    190▕
    191▕             optional($this->transactionsManager)->commit($this->getName());
    192▕         }
    193▕

      +35 vendor frames
  36  artisan:37
      Illuminate\Foundation\Console\Kernel::handle()

I'm using Docker as LaraDock and this is my database file content:
<?php

use Illuminate\Support\Str;

return [

    'default' => env('DB_CONNECTION', 'mariadb'),

    'connections' => [

        ///
        'tracker' => [
            'driver'   => 'mysql',
            'host' => env('DB_HOST', 'mariadb'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'charset' => 'utf8mb4',
            'strict' => false,
            'collation' => 'utf8mb4_persian_ci',
        ],
        'mysql' => [
            'driver' => 'mysql',
            'url' => env('DATABASE_URL'),
            'host' => env('DB_HOST', 'mariadb'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'unix_socket' => env('DB_SOCKET', ''),
            'charset' => 'utf8mb4',
            'collation' => 'utf8mb4_persian_ci',
            'prefix' => '',
            'prefix_indexes' => true,
            'strict' => true,
            'engine' => null,
            'options' => extension_loaded('pdo_mysql') ? array_filter([
                PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
            ]) : [],
        ],

        ///

        'laravel-visits' => [
            'host' => env('REDIS_HOST', '<IP_ADDRESS>'),
            'password' => env('REDIS_PASSWORD', null),
            'port' => env('REDIS_PORT', 6379),
            'database' => 3, // anything from 1 to 15, except 0 (or what is set in default)
        ],

    ],
    'migrations' => 'migrations',

    /

    ///

    ],

];

Hello, your have found a solved to the problem?

@HDsouls not yet, i think this package is not available for php 8 or laravel 8

You can 'fix' this by updating some code in PragmaRX\Support\Migration
The issue is with PHP8 and PDO transaction stuff. The original code of the 'executeInTransaction' function needs to be amended. The original code is:
/**
	 * Execute the migrationm command inside a transaction layer.
	 *
	 * @param $method
	 */
	protected function executeInTransaction($method)
	{
		$this->connection->beginTransaction();

		try
		{
			$this->{$method}();
		}
		catch (\Exception $exception)
		{
			$this->connection->rollback();

			$this->handleException($exception);
		}

		$this->connection->commit();
	}

Change the last bit to:
		if ($this->connection->getPdo()->inTransaction()) {
			$this->connection->commit();
		}

It works for me but I haven't tested it more broadly.

Thanks for the tip @ingoldsby - Have you had any side affects from this in the last 15 days? Or noticed any other issues abroad

I'm not sure if it was related or not, but I had some session_start() issues when I pushed it to AWS from local computer. So I took it off for now until I get time to investigate more.

Check if your php.ini file has php_pdo extension enabled. I am trying this on Laravel 8.44 and it migrated the migration files. I got the blade files through git checkout and opened Stats route which now only gives me Datatables error.
PS I did not follow @ingoldsby 's advice

I have same problem on Laravel 8

You can 'fix' this by updating some code in PragmaRX\Support\Migration
The issue is with PHP8 and PDO transaction stuff. The original code of the 'executeInTransaction' function needs to be amended. The original code is:
/**
	 * Execute the migrationm command inside a transaction layer.
	 *
	 * @param $method
	 */
	protected function executeInTransaction($method)
	{
		$this->connection->beginTransaction();

		try
		{
			$this->{$method}();
		}
		catch (\Exception $exception)
		{
			$this->connection->rollback();

			$this->handleException($exception);
		}

		$this->connection->commit();
	}

Change the last bit to:
		if ($this->connection->getPdo()->inTransaction()) {
			$this->connection->commit();
		}

It works for me but I haven't tested it more broadly.

Thank you it worked, rather than overwriting the packages I duplicated PragmaRX\Support\Migration locally as a util, applied the changes you suggested, and imported my util in the all the migrations.
Hope this helps someone else in the meantime

Any negative impact with this popup error? @rohanshukla9

after installing this package and define settings into app/config.php and publishing configuration, when i try to run this command:
php artisan migrate:fresh

i get error after this part of readme install document
Migrate it

If you have set the default connection to tracker, you can:
php artisan migrate

Error:
Migrating: 2014_10_12_100000_create_password_resets_table
Migrated:  2014_10_12_100000_create_password_resets_table (43.99ms)
Migrating: 2015_03_07_311070_create_tracker_paths_table

   PDOException

  There is no active transaction

  at vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php:189
    185▕      */
    186▕     public function commit()
    187▕     {
    188▕         if ($this->transactions == 1) {
  ➜ 189▕             $this->getPdo()->commit();
    190▕
    191▕             optional($this->transactionsManager)->commit($this->getName());
    192▕         }
    193▕

      +35 vendor frames
  36  artisan:37
      Illuminate\Foundation\Console\Kernel::handle()

I'm using Docker as LaraDock and this is my database file content:
<?php

use Illuminate\Support\Str;

return [

    'default' => env('DB_CONNECTION', 'mariadb'),

    'connections' => [

        ///
        'tracker' => [
            'driver'   => 'mysql',
            'host' => env('DB_HOST', 'mariadb'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'charset' => 'utf8mb4',
            'strict' => false,
            'collation' => 'utf8mb4_persian_ci',
        ],
        'mysql' => [
            'driver' => 'mysql',
            'url' => env('DATABASE_URL'),
            'host' => env('DB_HOST', 'mariadb'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'unix_socket' => env('DB_SOCKET', ''),
            'charset' => 'utf8mb4',
            'collation' => 'utf8mb4_persian_ci',
            'prefix' => '',
            'prefix_indexes' => true,
            'strict' => true,
            'engine' => null,
            'options' => extension_loaded('pdo_mysql') ? array_filter([
                PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
            ]) : [],
        ],

        ///

        'laravel-visits' => [
            'host' => env('REDIS_HOST', '<IP_ADDRESS>'),
            'password' => env('REDIS_PASSWORD', null),
            'port' => env('REDIS_PORT', 6379),
            'database' => 3, // anything from 1 to 15, except 0 (or what is set in default)
        ],

    ],
    'migrations' => 'migrations',

    /

    ///

    ],

];

had the same error. Found a work around by editing by editing the commit function. I reduced the transaction count to zero. Was able to seed without error, rolled back the code after I was through. Hope it helps someone.
public function commit()

187▕     {
188▕         if ($this->transactions == 0) {

➜ 189▕             $this->getPdo()->commit();
190▕
191▕             optional($this->transactionsManager)->commit($this->getName());
192▕         }

This error can be caused by different things, but ultimately a transaction being committed prematurely.
For me it was the because my base Tests\TestCase was using Illuminate\Foundation\Testing\RefreshDatabase a bunch of children TestCase were using Illuminate\Foundation\Testing\DatabaseMigrations. After removing DatabaseMigrations it works fine.

The solution from @bradietilley worked for me. After doing a little research I found out that RefreshDatabase starts every test with a brand new database and DatabaseMigrations executes a rollback after finishing the test. The second one is unnecessary since every test will start the database as brand new. There was no need for a rollback in my case.


Feat: Dark Mode for login & register page.

Describe the feature
There is no dark mode option for the login and register page. I would like to contribute by improving the login & register page by adding dark mode.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hi @Suchitra-Sahoo, Please assign this issue to me. I am a GSSOC '24 contributor. I would like to contribute by adding this feature.


cmd/go: error out of more commands used by module authors if go.mod's Go version is newer

https://github.com/golang/go/issues/46142 is a great change. It would have saved some head scratching for a coworker of mine, who was running go mod tidy on 1.16.x on a module that declared go 1.17. This version mismatch was causing problems, such as unintentionally removing some require lines.
I reckon we should throw this error for any command that relates to authoring a module and not just using it. Of course, only when run inside a module that has such a version mismatch. Off the top of my head:

go get, as nowadays it's only used for changing the module requirements.
go work, given how similar it is to go mod. Perhaps it should compare with the go 1.N line in the go.work file?
go fix and go generate, as they can only be useful to an author, given how they modify source files
Any other go mod command, not just go mod tidy. For instance, go mod edit or go mod vendor both feel potentially broken on a version of Go that's too old.

One may argue that there's no harm in some of these, like go fix or go generate, but I also think we should consistently push authors towards using a Go version that's recent enough to be compatible with authoring a module.

I think go generate and go fix are probably ok — if the generator program runs successfully on the older version it should produce the same output, and go fix on a newer version shouldn't actively undo transformations applied by go fix on an older version (or vice-versa).
But I agree that go get and go work should probably error out if they don't know how to interpret the main module's (or the workfile's) go version.

This should have been fixed by the changes for #61198. At this point, any go command in a module or workspace that declares go 1.21 or higher should either automatically upgrade the toolchain or fail explicitly.


[Docs] Simplification of Spark docs page

https://docs.lakefs.io/integrations/spark.html
Since there are two ways to use lakeFS with Spark (S3 compatible API vs. Hadoop FileSystem), this page is kind of messy.
We have all this before we even get to business:

Additionally, more stuff is going in there soon, namely the documentation of #5355.
Therefore, this page calls for simplification / splitting / pruning - anything really. I've opened #5401 as an SOS - but this is hardly enough.

I'd add a section at the top of the page explaining each of the two options, perhaps with a ✅❌ type chart to help the user pick which to use. Other than that, not sure what else to suggest for this page.

@johnnyaug I'm doing some GH issue housekeeping and came across this.
Could you review the current page and note any suggestions/observations here please? Or if it's looking OK now then close the issue.
thanks.


OSD-8578 update splunk forwarder version

Addressing CVEs in OSD-8578.
Rebuilding the image from the latest ubi-minimal and using the lastest splunk package can fix most of the CVEs.
Did a test in my staging OSD cluster with the latest image, the splunk-(heavy)forwarder doesn't show any error in the log in the past 12 hours, and I can see the audit log in splunk cloud after the change.

@gsleeman @jaybeeunix could help reviewing this?

/lgtm

/assign @wshearn

@jaybeeunix could you help to approve this?

/lgtm

/approve


recipes-core/systemd: Move audit socket removal to meta-balena

Removal of audit sockets to disable audit messages should
be done in meta-balena.
Changelog-entry: recipes-core/systemd: Move audit socket removal to meta-balena
Signed-off-by: Alexandru Costache<EMAIL_ADDRESS>

@balena-ci I self-certify!


Support custom parser in socketio packet

this PR is to support Custom parser in socketio
reimplement of #421
also this is still WIP

@1c3t3a and the code coverage test are rate limited

Closing this as it is WIP. Please open PRs once you're ready.

yea, I failed to done it, thanks


No handlers could be found for logger "werkzeug"

Empire Version2
OS Informationlinux
can not create stager/windows/macro

Any additional information

@mateo24xx This isn't an exception or error necessarily. Did this cause an issue for you in a module or when interacting with an agent.

no it works normaly..but i dont now if this problem persist it will always work good..

The output is from the logger module. It doesn't cause any exceptions or errors and I've only seen output like that once or twice. Kind of a outlier ¯_(ツ)_/¯


BAU: Hide sentry null exceptions due to certificates managed by self service tool

This is due to certificates managed by the Cert Admin tool
we will turn this back from warning to error once addressed by
https://govukverify.atlassian.net/browse/HUB-457

Are we sure this is the correct line to be changing from error to warning? I would have thought it was the other one.

https://sentry.tools.signin.service.gov.uk/verify/prod-hub/issues/4098/


Update to latest version of dependencies

PR Description
Updates dependencies to the latest stable versions. Left Javalin at an older version as the updated version pulls in a lot of extra transitive dependencies with licenses we'll need to more carefully check and Snyk flagged some security errors.
Changes to the java files are a result of new error prone rules.
Documentation

[x] I thought about documentation and added the documentation label to this PR if updates are required.

BTW, are there any reasons besides security to update lib versions?
TBH I usually did this only when there was a need for some fix or feature. Else there is a high chance to hit some regression bug

When and if to update dependencies is one of those hard questions with no real right answer. As you say updating dependencies has a risk of introducing new bugs but the more outdated the get the harder it often becomes to update and the harder to pinpoint the change that caused the bug when you do.
I think while we're in this test phase we should be pretty aggressive about keeping up to date (and hopefully avoid bug batches of updates like this one) but we may want to be a bit more selective as we get closer to production - or at least run more of a release candidate type process when we do pull in updates.

I think while we're in this test phase we should be pretty aggressive about keeping up to date (and hopefully avoid bug batches of updates like this one) but we may want to be a bit more selective as we get closer to production - or at least run more of a release candidate type process when we do pull in updates.

Thanks for explanation! Makes sense 👍


Failed to retrieve a connection pool from the hashring

Configuration:
200 php-fpm processes
1 rmux
[
	{
		"socket": "/tmp/rmux.sock",
		"poolSize" : 50,

		"tcpConnections": ["<IP_ADDRESS>:32888","<IP_ADDRESS>:32930","<IP_ADDRESS>:32799","<IP_ADDRESS>:32871","<IP_ADDRESS>:32849","<IP_ADDRESS>:32937","<IP_ADDRESS>:32865","<IP_ADDRESS>:32793"],

		"remoteConnectTimeout": 5
	}
]

Is this a sign our connection pool is too small?

It looks like this happens before we try to get a connection from the pool, so I doubt that the size of the pool is the issue.  My guess is that all of the configured redis instances are unreachable, perhaps due to a networking issue on the host running rmux.

It could also be that the instance that it is trying to hit for a given key
is down, I would recommend putting the pool into failover mode if that fits
your use case.
Sent from my iPhone
On Jul 14, 2016, at 9:07 AM, Michael Frank<EMAIL_ADDRESS>wrote:
It looks like this happens before we try to get a connection from the pool,
so I doubt that the size of the pool is the issue. My guess is that all of
the configured redis instances are unreachable, perhaps due to a networking
issue on the host running rmux.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SalesforceEng/rmux/issues/19#issuecomment-232712027,
or mute the thread
https://github.com/notifications/unsubscribe/AA6Zu1r03YpxL-HCGUcDOCE2T_yoh9Z1ks5qVl6tgaJpZM4JL94o
.

I should expand on the issue given your feedback.
1 container is 200 php-fpm processes, 1 rmux.
There are 30 container running across the network
There are the (as listed) 8 redis 3.0.3 servers (which all function and are reachable anywhere within the network). They basically should never be down (ideal scenario)
The reason we're trying rmux is we're having connection issues that we've tried about everything to resolve. We've put it down to 30 * 200 (6000) php-fpms trying to make their own connections to the 8 servers. Phpredis has been ever useful with it's one error for all "redis server has gone away" in some instances, and in others the connection times out after 30s
Our hope was to drop rmux in place, have it manage the connection pool (figuring 50'd be enough) and point php-fpm at it.
In testing that works fine, in production it was a totally different story.

Sorry, I think I've solved it, I read "remoteConnectTimeout": 5 as being 5 seconds, not 5ms (pay attention to application startup)
It's quite evident that under the load of all our web traffic the 5ms is an easily reached target - change it to 500 and that problem goes away.

Glad to hear you found the cause!  I'm going to close this one out.


WIP: Bulk update attachment metadata in asset manager

I rebased on master, added the missing worker call and force-pushed.

Rebasing on master before merging.

I ran the rake task asset_manager:update_attachment_metadata[0,10000] on integration at 16:03:09. It completed at 16:04:12 (~1min).
At peak (16:04:22) the rake task had added 47345 jobs to the asset_migration queue. The queue was empty at 16:29:02.

We've added https://github.com/alphagov/asset-manager/issues/525 as a place to capture more information about this bulk update of metadata.


Fixed #156: XhrManager/XhrIoPool withCredentials support

Based on Erik Timmers patch: https://codereview.appspot.com/12985043/.

We've also ran into the issue of not being able to efficiently set withCredentials for XhrIo objects when using the XhrManager. It's currently possible by listening to the goog.net.EventType.READY on the XhrManager, but this means an additional overhead by calling xhrIo.setWithCredentials(true) every time an  goog.net.EventType.READY is dispatched.
Considering the current architecture and implementation of the XhrIoPool and the XhrManager, i think this PR is the most desirable solution, though ultimately it highlights the inability to control dependencies (via dependency injection).

Made some changes and added test.

You'll also need to squash your commits before this can be merged.

Looks like I've grokked squash magic.


[Table] MatTableDataSource does not properly sort null/undefined values

Bug, feature request, or proposal:
Sort of bug, sort of feature request
What is the expected behavior?
rows with undefined values for a sorted column should sort properly
What is the current behavior?
null/undefined values cause random sorting issues
What are the steps to reproduce?
Providing a StackBlitz/Plunker (or similar) is the best way to get the team to see your issue.
Plunker starter (using on @master): https://goo.gl/uDmqyY
StackBlitz starter (using latest npm release): https://goo.gl/wwnhMV
Have a sortable mat-table with some null values in some columns.
Try to sort.
What is the use-case or motivation for changing an existing behavior?
columns often have empty values
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
material 5.0.0rc0
Is there anything else we should know?
MatTableDataSource has this line where the actual sorting is done:
      return (valueA < valueB ? -1 : 1) * (direction == 'asc' ? 1 : -1);
Note that like values are not treated correctly either. This could be replaced with the following:
     return this.compareItems(valueA, valueB) * (direction == 'asc' ? 1 : -1);

    private compareItems(itemA: any, itemB: any): number {
      let retVal: number = 0;
      if (itemA && itemB) {
        if (itemA > itemB) retVal = 1;
        else if (itemA < itemB) retVal = -1;
      }
      else if (itemA) retVal = 1;
      else if (itemB) retVal = -1;
      return retVal;
    }

Also, to make strict null safe, the sortingDataAccessor method should be modified to allow such a value.

@mcalmus Your fix worked for me. The sorting is accounting for null fields too now. Appreciate it.

@mcalmus I am also facing same issue with material sort. I think my data have some null values so i want use this code. Exactly where i need write this code

@yedidisatya it has been published with the last release: https://github.com/angular/material2/releases/tag/5.2.0
Update your library:
#if you are using npm:
npm install --save @angular/material @angular/cdk

#if you are using yarn:
yarn add @angular/material @angular/cdk

And that's it! ;)

@gangsthub  Thank you

Awesome! Thanks!

@gangsthub,
by upgrading the packing this seems to be not working.
I still see the same result while sorting the data when the rows have null/empty or undefined values.
Kindly suggest.

@gangsthub ,
What do you mean by "Also, to make strict null safe, the sortingDataAccessor method should be modified to allow such a value." where can I find this method? What changes are required in the method which you have mentioned?

sorry, @V2NileshSukalikar, that one was @mcalmus. He is refering to the sorting method of the
MatTableDataSource class. You can make your own class extending this one (class ... extends MatTableDataSource) and providing new methods to override sortingDataAccessor and/or sortData. But that wasn't my point. I was refering to the PR that fixed the issue they had sorting with "nil" values...: https://github.com/angular/material2/pull/8698.

for me its showing sort undefined in matsorttablesuorce object how i can fix that?


would you mind to provide some example of how to use this

would you mind to provide some example of how to use this?
it will be great if you provide with a gif too

I'm currently working on it, and provide as soon as possible.
Thank you for your interest in my project! 😄

@xycloud Please see updated README.md
If you possible, give me more feedback.
Thank you!


Invoking mock_s3 twice leaks key

Continued from #5913
$ python -Wall <<END
from boto3 import client
from moto import mock_s3, __version__

print(__version__)

with mock_s3():
    s3 = client('s3')
    s3.create_bucket(Bucket='foo')
    s3.put_object(Bucket='foo', Key='bar', Body='stuff')

with mock_s3():
    pass
END

produces
4.1.3.dev22
/Users/hannes/workspace/hca/azul/.venv/lib/python3.9/site-packages/moto/s3/models.py:349: ResourceWarning: S3 key was not disposed of in time
  warnings.warn("S3 key was not disposed of in time", ResourceWarning)

Didn't look into the cause this time. It must be a regression introduced by PR #5920 because I can't reproduce on 4.1.2.

Thanks for raising this @hannes-ucsc - that was a regression indeed. Should be fixed as of moto >= 4.1.3.dev29

Thank you for fixing it, @bblommers. I did find another one: https://github.com/getmoto/moto/issues/5937


Use parse_seq_to_before_end to keep the end token.

Without this change parse_seq_to_end eats the EOF so expect(Eof) ICEs under rust-lang/rust#32479.

@eddyb I kicked off Travis again. It looks like this is still causing an ICE?

Got it, thanks!


[Sema] Do not diagnose contextual type mismatches for malformed key path expressions

This just skips contextual type diagnostic for malformed key path expressions, because this leads at the very least, extra not good diagnostics. What do you think?

If it's already determined and diagnosed that that key path expression is invalid why not just return Type() while generating constraints for it and avoid running solver for invalid AST?

Humm, haven't thought about that ... makes sense, let's try that! Thanks, @xedin :)

If it's already determined and diagnosed that that key path expression is invalid why not just return Type() while generating constraints for it and avoid running solver for invalid AST?

Seems like doing this, affects code completion in a way, I'm still looking into this and not familiar with code completion ... but seems like it needs to type check \Root to provide completion

If it's already determined and diagnosed that that key path expression is invalid why not just return Type() while generating constraints for it and avoid running solver for invalid AST?

@xedin
Seems like it still needs to type check in order to provide code completion in situations like:
https://github.com/apple/swift/blob/e35d2d355f54052c75c98d03a0c038d4f576b9f9/test/IDE/complete_swift_key_path.swift#L47
So should we keep this approach, or maybe run the solver only if it is type checking for code completion using SuppressDiagnostics flag otherwise return Type() in CSGen? Not really sure about this last one ...

@LucianoPAlmeida before you merge please add one more test case like let _: KeyPath<A, C> = \A to make sure that contextual failure is still recorded.

@xedin

@LucianoPAlmeida before you merge please add one more test case like let _: KeyPath<A, C> = \A to make sure that contextual failure is still recorded.

Just added, together with a minor adjustments

@swift-ci please smoke test

@swift-ci Please smoke test Windows platform

@swift-ci Please smoke test

@xedin Naming and comments fixed :) Just making sure if there's anything else or we could land this?

:shipit:


Refactored several controls.

Adjusted controls for rebinning.
Refactored animation controls.
If Instagram messages have been loaded, make them the default graph data set rather than temperature.
When we aren't using a database for a long time, disconnect from it.  Connection seems to only take 20 milliseconds, and this makes it easier for me to update databases in place, and for some resources to be freed.
Removed backbone from the package list, as we don't need to install it (it comes with Girder).

Resolves issues #97 and #95.

This looks very good - much easier to follow. Perhaps "Window size" instead of "Group" might be a better name for that control - with the tooltip saying "time interval" instead of "time period". Duration and Rate seem like a big step up in usability.

I'll change to "Window" and "time interval".  The animation is much easier
to explain with the new controls -- thanks for suggesting the changes.
Do you think I should add or remove any of options for various select boxes?
On Thu, May 21, 2015 at 11:01 AM, Jeffrey Baumes<EMAIL_ADDRESS>wrote:

This looks very good - much easier to follow. Perhaps "Window size"
instead of "Group" might be a better name for that control - with the
tooltip saying "time interval" instead of "time period". Duration and Rate
seem like a big step up in usability.
—
Reply to this email directly or view it on GitHub
https://github.com/XDATA-Year-3/geoapp/pull/99#issuecomment-104311239.

--
David Manthey
R&D Engineer
Kitware Inc.
(518) 881-4439

Not sure the utility of 3 hour window - do you find it useful?

I thought I could see some effects better with it.  For instance, with one
of the protests, the activity lasted several hours, and I thought the
activity change viewed through the hour window wasn't as clear as the
activity change through a longer window (but a day was too long).
On Thu, May 21, 2015 at 12:03 PM, Jeffrey Baumes<EMAIL_ADDRESS>wrote:

Not sure the utility of 3 hour window - do you find it useful?
—
Reply to this email directly or view it on GitHub
https://github.com/XDATA-Year-3/geoapp/pull/99#issuecomment-104332702.

--
David Manthey
R&D Engineer
Kitware Inc.
(518) 881-4439


global variable and default value

Hi there,
When there is a global variable used in a @jit function, an error message shows up:
LoweringError: Internal error:
TypeError: unhashable type: 'numpy.ndarray'
When there is a variable with default value and not assigned when called, an error message shows up:
TypeError: Required argument 'xxx' (pos 3) not found
It took me sometime to figure these out.
Cheers,
SC

This was fixed in the above PR.


AAR build still got error

Hi,
After implementing the changes 024f7bf mentioned in issue 609, I retried to build aar for face detection and hand tracking, but both still failed with error message:
Hand tracking
ERROR: /mediapipe/mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example/BUILD:3:1: Linking of rule '//mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example:libmediapipe_jni.so' failed (Exit 254) clang failed: error executing command external/androidndk/ndk/toolchains/llvm/prebuilt/linux-x86_64/bin/clang -shared -o ... (remaining 588 argument(s) skipped)
Use --sandbox_debug to see verbose messages from the sandbox
clang: error: unable to execute command: Killed
clang: error: linker command failed due to signal (use -v to see invocation)
Target //mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example:mp_hand_tracking_aar failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 618.062s, Critical Path: 599.90s
INFO: 218 processes: 212 processwrapper-sandbox, 6 worker.
FAILED: Build did NOT complete successfully
Face detection
ERROR: /mediapipe/mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example/BUILD:3:1: Executing genrule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example:mp_face_detection_aar failed (Exit 127) bash failed: error executing command /bin/bash -c ... (remaining 1 argument(s) skipped)
Use --sandbox_debug to see verbose messages from the sandbox
/bin/bash: line 7: zip: command not found
Archive:  /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/sandbox/processwrapper-sandbox/2146/execroot/mediapipe/bazel-out/k8-opt/bin/mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example/mp_face_detection_aar_dummy_app_unsigned.apk
creating: lib/
creating: lib/arm64-v8a/
creating: lib/armeabi-v7a/
Target //mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example:mp_face_detection_aar failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 42.495s, Critical Path: 38.04s
INFO: 2 processes: 2 processwrapper-sandbox.
FAILED: Build did NOT complete successfully
Any idea what happen?
Thanks

Hi,
Build command as stated in new android archive library readme here
bazel build -c opt --host_crosstool_top=@bazel_tools//tools/cpp:toolchain --fat_apk_cpu=arm64-v8a,armeabi-v7a //mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example:mp_face_detection_aar
Thanks!

Hand tracking
the error is:
clang: error: unable to execute command: Killed
clang: error: linker command failed due to signal (use -v to see invocation)
clang program may be killed by the system, just try again.
Face detection
the error is:
/bin/bash: line 7: zip: command not found
do you install the zip command? just print zip in the shell, if not, install zip command.

Hi,
Thanks for the reply. Yes I am now able to build AAR for Hand Tracking after trying sometime. And I just installed zip (sorry my bad), and build AAR for face detection but now I have different error message:
ERROR: /mediapipe/mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example/BUILD:3:1: Executing genrule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example:mp_face_detection_aar failed (Exit 12) bash failed: error executing command /bin/bash -c ... (remaining 1 argument(s) skipped)
Use --sandbox_debug to see verbose messages from the sandbox
Archive:  /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/sandbox/processwrapper-sandbox/37/execroot/mediapipe/bazel-out/k8-opt/bin/mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example/mp_face_detection_aar_dummy_app_unsigned.apk
creating: lib/
creating: lib/arm64-v8a/
creating: lib/armeabi-v7a/
zip warning: name not matched: jni//.so
zip error: Nothing to do! (try: zip -r /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/sandbox/processwrapper-sandbox/37/execroot/mediapipe/bazel-out/k8-opt/bin/mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example/mp_face_detection_aar.aar . -i jni//.so)
Target //mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example:mp_face_detection_aar failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 52.828s, Critical Path: 28.39s
INFO: 0 processes.
FAILED: Build did NOT complete successfully
Zip command is now error
Please advise.
Thank you.

That's weird. If hand tracking aar works, everything else should work as well.
Do you put both hand tracking and face detection mediapipe aar rules in the same BUILD file? If that's the case, can you move the face detection aar rule to a BUILD file in another directory and build that face detection aar? My guess is this problem might be triggered by the existing build cache generated by the hand tracking aar.

Hi,
Thanks for replying. Anyway I re-create new docker container and re-build again everything from scratch and managed to print Hello World successfully. Now I got different error when trying to build AAR, both for hand tracking and face detection has same error below:
ERROR: /mediapipe/mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example/BUILD:3:1: Executing genrule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example:mp_hand_tracking_aar_binary_manifest_generator failed (Exit 127) bash failed: error executing command /bin/bash -c ... (remaining 1 argument(s) skipped)
Use --sandbox_debug to see verbose messages from the sandbox
/bin/bash: $'\r': command not found
Target //mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_example:mp_hand_tracking_aar failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 32.906s, Critical Path: 22.91s
INFO: 98 processes: 98 processwrapper-sandbox.
FAILED: Build did NOT complete successfully
P.S. I change the content of file .../aar_example/BUILD to hand tracking or face detection everytime I want to try each one.
Any idea?
Thank you

Hi all,
Apparently the last error was because incompatible command in Docker Toolbox in Windows 7. So I managed to setup WSL and now its working.
Thank you.


Update cats-core, cats-free to 2.2.0

Updates

org.typelevel:cats-core
org.typelevel:cats-free

from 2.1.1 to 2.2.0.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Applied Migrations

github:typelevel/cats/Cats_v2_2_0

Documentation:

https://github.com/typelevel/cats/blob/master/scalafix/README.md#migration-to-cats-v220

labels: library-update, semver-minor, scalafix-migrations

(forked this PR, will fix)


Remove mainainer badge.

I am not longer the primary maintainer of this project.

Understood. Thank you, @coot!


Check icon overflow fix

Description:
Added default height and width to icon on check component and relevant css variables.
All Submissions:

[X] I have followed the contribution guidelines for this project.
[X] I have checked to ensure there aren't other open Pull Requests for the same update/change.

Changes to Core Features:

[X] I have added an explanation of what my changes do and why I would like to include them.
[X] I have written new tests for my core changes, as applicable.
[X] I have successfully ran tests with my changes locally.
[X] I have added/updated docs, as applicable.

Do we need a story / test to reflect these changes?

There are existing stories relating to the affected icons and should now apply correctly on the mobile browsers where the bug was discovered


add BLAPrjnParams: AChThr and USTrace -- latter is key for eboa learning CS under curiosity

This is needed for eboa initial basic performance.

auto review as it works and passes tests :)


Tips and Tricks

I've added a new tips and tricks section to the SUSHI doc. Right now it just has some tips for issues related to package dependencies. My primary motivation was to document how to use Firely Terminal's bake command.
Please review and provide feedback.  I'd appreciate it if someone could test the "missing snapshot" instructions on Mac and someone else test them on Windows.
You can use this FSH project to test: NonHL7PackageDocs.zip. First confirm you get the missing snapshot error when running SUSHI. Then following the instructions and try SUSHI again.
I'm also open to feedback if people think this content should go somewhere else.
Oh -- and I also added a clarification about canonicals on the Configuration page, per the request of a SUSHI user. It was small, so it seemed easier to lump it with this PR.

When running the version check, I had to use dotnet --version in order to get the version printed.
I had to do the same, but I didn't even notice since I knew I was just looking for confirmation that it was installed. So yay for @mint-thompson being much more detail oriented than me.

I had no additional issues besides what @mint-thompson already pointed out. The documentation was clear and made sense!

Thanks, @mint-thompson and @jafeltra.  4ff339b fixes the dotnet -v issue and also adds a blurb about how to select your version.  It should be ready for re-review now.


argparse in the wrong place

argparse in pytzwhere.py is not guarded by if name == "main";, as a consequence argparse interferes when pytzwhere imported into a program that also imports and tries to use argparse.
This is easy to correct. Just wondering if this repository/project is still alive.

This should be fixed in the new version.


An error has occurred during metrics gathering:

2090 error(s) occurred:

collected metric pg_stat_statements_calls label:<name:"datname" value:"postgres" > label:<name:"queryid" value:"" > label:<name:"rolname" value:"postgres" > label:<name:"server" value:"sas-pgbouncer.pgo.svc.cluster.local:5432" > counter:<value:1 >  was collected before with the same name and label values
collected metric pg_stat_statements_total_time_seconds label:<name:"datname" value:"postgres" > label:<name:"queryid" value:"" > label:<name:"rolname" value:"postgres" > label:<name:"server" value:"sas-pgbouncer.pgo.svc.cluster.local:5432" > counter:<value:0.003291422 >  was collected before with the same name and label values
collected metric pg_stat_statements_min_time_seconds label:<name:"datname" value:"postgres" > label:<name:"queryid" value:"" > label:<name:"rolname" value:"postgres" > label:<name:"server" value:"sas-pgbouncer.pgo.svc.cluster.local:5432" > gauge:<value:0.003291422 >  was collected before with the same name and label values
collected metric pg_stat_statements_max_time_seconds label:<name:"datname" value:"postgres" > label:<name:"queryid" value:"" > label:<name:"rolname" value:"postgres" > label:<name:"server" value:"sas-pgbouncer.pgo.svc.cluster.local:5432" > gauge:<value:0.003291422 >  was collected before with the same name and label values
collected metric pg_stat_statements_mean_time_seconds label:<name:"datname" value:"postgres" > label:<name:"queryid" value:"" > label:<name:"rolname" value:"postgres" > label:<name:"server" value:"sas-pgbouncer.pgo.svc.cluster.local:5432" > gauge:<value:0.003291422 >  was collected before with the same name and label values

My postgres exporter shows the above errors. Please let me know how this can be fixed. I have it deployed as a helm chart on my kubernetes cluster.

When I granted the user superuser privileges, the issue got resolved.


Should use inference profile when using Claude 3.5 Sonnet (v2) on Amazon Bedrock

For now, Claude 3.5 Sonnet (v2) can only be used through an inference profile.
We should use us.anthropic.claude-3-5-sonnet-20241022-v2:0 rather than anthropic.claude-3-5-sonnet-20241022-v2:0.
The list of inference profie: https://docs.aws.amazon.com/bedrock/latest/userguide/inference-profiles-support.html

Ah, is this why it keeps giving the following message?
Please resolve the following auth issue:

You must have AWS credentials set up to use the Bedrock API.

Your message may not be relevant to this issue. The error message indicates that AWS credentials have not been properly configured to authenticate and invoke Claude from Amazon Bedrock. You can set the credential by aws configure, etc.

Your message may not be relevant to this issue. The error message indicates that AWS credentials have not been properly configured to authenticate and invoke Claude from Amazon Bedrock. You can set the credential by aws configure, etc.

But I have configured my credentials.


Code highlighting in issue titles - example

Feature Description
It would be great if Gitea would support code highlighting in issue titles (as GH does, see title).
Screenshot from 1.18.0+dev-289 below.
Screenshots

I'll take this


Bokeh TextPlot uses Text parameter settings

Previously bokeh ignored the alignment parameters on the Text Element.

Will have to rebuild test data, small change to Bokeh_Elements unsurprisingly.

Looks like a good change. Happy to merge once the tests pass.

Ready to merge, PR build passed.

Great! Merging now.


v0.0.6 bump and changelog & dependency updates

v0.0.6 - 2023-09-28 - Dynamic zones & subnet targeting fixes

Adds Provider.list_zones to enable new dynamic zone config functionality
Fix bug around root NS records when creating a new zone. See https://github.com/octodns/octodns-ns1/issues/48
Bump to octodns v1.2.0 to pull subnet-targeting related bug fixes

/cc https://pypi.org/project/octodns-ns1/0.0.6/


Use relative paths in C++ projects

$(SolutionDir) may have an incorrect value during command-line builds. This method is guaranteed to work, no matter what directory the user is building from. I also took an opportunity to update the gitignore. Thanks!

@kennykerr Honestly, that being said I would prefer that we close this PR; I will file one with README updates that instruct users to run that batch file rather than blindly attempting to build the solution. Thanks!

Sounds good.


GADBannerViewDelegate.h not found

Hi,
I'm very sorry but I'm having difficulty with the pod install.
I have managed to use only iAds but now I'm trying to use iAds and Google ads.
My Podfile is below. I'm cleaned the project, deleted derived data.
Thanks in advance.
platform :ios, '7.0'
source 'https://github.com/CocoaPods/Specs.git'
target 'myapp' do
pod 'LARSAdController', '~> 3.0'
end
target 'may' do
end

You are the second one to leave a comment about this in the last 4 hours or so (#111 being the first). Initially it looked like the cocoa pods install issue, but after looking into it, it appears google is now shipping their ad component as an actual framework, now. I'm not sure why this is failing, just yet, but this change appears to be new. I'm trying to figure out why it's not working, as everything I can see here says it 1. should be working or 2. Is an issue with Google's pod spec for their new 7.0.0 version

I believe that since google switched to using a .framework in 7.0.0 and I am using their pod in a subspec, it is triggering the issue outlined here, which was filed as a CocoaPods issue awhile ago. In the past, I have had no reason to restrict the use of Google's Mobile Ads SDK to any particular major version, but in hindsight, may have prevented this problem.
I've been trying to figure out a solution involving modifying the Podfile, but a sustainable solution is a little difficult since Google places their frameworks in a folder that also includes the version number...

Since this is still broken in CocoaPods 0.35, you'll have to force your Podfile to use the older version of the Google Ads SDK:
pod 'Google-Mobile-Ads-SDK', '~> 6.0'
pod 'LARSAdController'

cc: @YBthebest

Many thanks!
I can confirm that it compiles.
It seems that the order of the podfile items is important. I had LARSAdController first and even then 7.x of Google ads were being used.

On 11 Feb 2015, at 7:32 am, Lars Anderson<EMAIL_ADDRESS>wrote:
Since this is still broken in CocoaPods 0.35, you'll have to force your Podfile to use the older version of the Google Ads SDK:
pod 'Google-Mobile-Ads-SDK', '~> 6.0'
pod 'LARSAdController'
cc: @YBthebest
—
Reply to this email directly or view it on GitHub.

change
#import "GADBannerViewDelegate.h"
#import "GADBannerView.h"

to
#import <GoogleMobileAds/GADBannerView.h>
#import <GoogleMobileAds/GADBannerViewDelegate.h>

can fix the compile error

That doesn't actually work for me, maybe you're specifying search paths beyond what Cocoa Pods is?

I have stopped using CocoaPods. Just drag the files of LARSAdController into your project and make the changes above. I believe CocoaPod team will find a good solution. Before they do, the workaround is good enough.

@larsacus hey please can you add the changes which @haifengkao suggests so we don't have to use Google-Mobile-Ads-SDK 6.0 PLEASE :)

Should be fixed in #117


Compiling for WebAssembly

Compiling hdf5-sys and hdf5-types for WebAssembly seems to fail.
While cargo build is successful, running wasm-pack build ends up in a bunch of similar errors about libc:
error[E0425]: cannot find function `malloc` in module `libc`
  --> ~/.cargo/registry/src/github.com-1ecc6299db9ec823/hdf5-types-0.5.1/src/array.rs:71:29
   |
71 |             let dst = libc::malloc(len * mem::size_of::<T>());
   |                             ^^^^^^ not found in `libc`

Is might be related to https://github.com/rust-lang/libc/issues/858 but that issue seems to be resolved.
It should be possible to reproduce the issue by adding hdf5 dependency to Cargo.toml
[dependencies]
hdf5 = "0.5.1"

followed by running wasm-pack build.

Is this still an issue? I guess this is more a question of compiling hdf5-types. In fact, we don't really care if it's libc::malloc() or anything else since we are responsible for deallocating it (and not HDF5). If you have an alternative suggestion for hdf5-types that would work with wasm - sure, shoot.

@kerkomen Have you managed to compile the entire HDF5 C library into web assembly?...

Closing since it’s unclear what the OP means

Yes @aldanor
error[E0425]: cannot find function `malloc` in crate `libc`
  --> ~/.cargo/registry/src/github.com-1ecc6299db9ec823/hdf5-types-0.6.0/src/array.rs:71:29
   |
71 |             let dst = libc::malloc(len * mem::size_of::<T>());
   |                             ^^^^^^ not found in `libc`

[dependencies]
hdf5 = "0.6.0"

How can I compile the HDF5 C Library into WASM?


Add SSL support to minio

Add support in the charm to configure Minio to use SSL
ssl-secret-name needs to point to a kubernetes secret that has the following keys: PRIVATE_KEY, PUBLIC_CRT, and ROOT_CERT.  Minio will work normally without SSL if no config option is set.

Publish and check lib jobs are failing because it's a PR from a forked repo and thus the jobs can't fetch the necessary credentials. @jardon provided a fix #60 for that, but it's not yet merged.
Once this PR is approved and merged, publish to edge action should be ok.


USelectMenu  :option-attribute does not handle nested objects

Environment

Operating System: Windows_NT
Node Version:     v20.16.0
Nuxt Version:     3.13.2
CLI Version:      3.13.2
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      future, compatibilityDate, runtimeConfig, routeRules, app, devtools, css, modules, plugins, build, i18n, pinia, image, icon, ui, schemaOrg
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Version
2.18.6
Reproduction
https://stackblitz.com/edit/nuxt-ui-im7dek?file=app.vue
Description
USelectMenu  :option-attribute does not handle nested objects with dot.notation as described in the docs
Additional context
No response
Logs
No response

close in https://github.com/nuxt/ui/pull/2465


Better solution for gradle config issues with shadow jar

We should find a better way to solve this problem.  @kageiit suggests tweaking artifacts so that the shadow jar is the default artifact.

No longer an issue as we stopped shadowing