[atspi-connection] Use a channel to communicate.

Some issues faced by @luukvanderduim when opening Thunderbird caused event storms to overwhelm the bus.
Since the MessageStream was not being polled fast enough, zbus was getting clogged up, which can cause issues like hanging.

This is even mentioned in the documentation for zbus.

This commit takes a different approach, adding a channel, where the receiving end is send out to the user (luckily for us, the return type hasn't changed at all thanks to impl Stream<_>)
Now, a separate task will poll the MessageStream, and add it to the channel.
If the channel gets backed up, we having tracing/debug information avaiable as to why this happened.
Now, at least if zbus is getting backed up, we should be able to find out what is slowing down to polling of the channel, and then blocking up zbus indirectly.
It is possible that we want to spawn a second thread to deal with these events storms, but I suspect this will not be necessary unless the "30,000" events reported by Luuk simply overwhelm even tokio's executor.
Odilia should in theory be unaffected by this, since each even handler is spawned on its own task, and Odilia shouldn't back up unless a very large quanitiy of events are mutating the same items in the cache (worst case scenario with locking).

The other option is that we simply can't launch tasks fast enough. Based on these benchmarks it seems spawning may be in the hundreds of microseconds, which may not be able to keep up with 30,000 spawns a second (it would need to be at least less than 333us, but ideally we'd want to some headroom).

If possible, I'd like Luuk's statspi to be tested with this branch and see if it can stave off the event storms backing up zbuss very small queue.

Luuk mentioned that an additional level of indirection would make this much harder to debug. I think he's right.


Implement CRUD Operations in Lambda for DynamoDB

Implement GET, POST, PUT, Delete methods in lambda to interact with DynamoDB

Done


Format F# code with Fantomas

This PR formats all F# code with Fantomas, using the default configuration except for a few changes. The configuration files changed are:

build/init.yml
build/steps.yml
.config/dotnet-tools.json
.editorconfig

The rest of the files are formatting changes only.
The Fantomas repo has some instructions for editor integration if you want to run it on your code. You can also run it from the command line with:
dotnet tool restore
dotnet tool run fantomas MyFile.fs

I did encounter some bugs in Fantomas, and a few of them caused comments to be deleted after formatting. The bugs were relatively rare compared to the total amount of code that was formatted, but it's probably a good idea to double-check that everything was formatted correctly and no comments were lost.

Thanks for setting it up!


Conditional counter fails update on multi-level cache

I have an arrangement like this:
class Child < ActiveRecord::Base
  has_many :parent_privileges, dependent: :destroy
  has_many :parents, through: :parent_privileges

  counter_culture [:parent_privileges, :parent], column_name: proc { |model| model.active? ? 'children_count' : nil }, column_names: {['children.active = ?', true] => 'children_count'}
end

class ParentPrivilege < ActiveRecord::Base
  belongs_to :child
  belongs_to :parent
end

class Parent < ActiveRecord::Base
  has_many :parent_privileges, dependent: destroy
  has_many :children, through: :parent_privileges
end

This counter_culture works fine with Child.counter_culture_fix_counts, but fails on an update to the active field of the Child instance (for instance, Child.first.update(active: false) with NoMethodError: undefined method 'child_id_was' for #<Child:0x007fdd43b69478>.  It appears to not be going off the hierarchy as I expect.
My question: is this a bug I stumbled across, or am I doing something invalid by having the belongs_to class in the middle of the hierarchy?

Yes, you want the counter_culture call on the model that has the belongs_to relationship. I should clarify this in the documentation. Also, this probably still doesn't do what you want here as the count then wouldn't be updated on changes to active in the child. My guess is that that wouldn't currently be possible with just counter_culture code.


Release <IP_ADDRESS>

OpenSearch 2.6.0 has been released, see release notes.
Official OpenSearch release ticket: https://github.com/opensearch-project/opensearch-build/issues/3081
Checklist:

[x] Compatibility Matrix is updated (https://github.com/aiven/prometheus-exporter-plugin-for-opensearch/pull/145)
[x] Release <IP_ADDRESS> tag is present in the repo
[x] Release artifacts are available and downloadable
[x] Release notes published
[x] Forum announcement published

Done: https://forum.opensearch.org/t/prometheus-exporter-plugin-2-6-0-0-and-1-3-8-0-released/12921


Search Box - 'Match whole words' error message is confusing

Match whole words does not seem to be working.
This Message does not seem to be useful-too confusing for user:
Because of the brevity of your search term, partial search was omitted.
Click here to include searching through partial words.

Whole/partial search is working, except when there are multiple words (anther issue).
For this, just remove the confusing message

Wait with this issue until #184, https://github.com/sillsdev/webonary/issues/184
has been addressed.

Possible wording for the error message is: "Only showing whole words that matched your string (if any).  To search for partial matches as well (possibly with a lot of results), click here."

Just checking to see if this is still "In progress".  Is there an estimated ship date for it, so we can test for it?


Powerpoint presentation via iOS bug discovered

If the filename of a powerpoint-presentation on (saved on OneDrive) contains the Character "&" (and possibly more similar chars), users are met with an error message. The same file with the same filename on the same location can be presented on a Windows 10 PC though.
Thought Id share...

We tried the same at our end, but it seems working on our device. Could you please let us know the name you are trying to provide. Thanks.

Hello!
Thanks for the quick reply.
Is your test file on OneDrive?
The top file on the list is the one, which didn’t work. The error message reads “The file couldn’t be shared – an error occurred while sharing the file. Please try again later.”
After deleting the “&-Symbol” it work on the clients side and also on my side… Meanwhile, other files, shared without a problem – although we didn’t try all other below listed pptxs.
<EMAIL_ADDRESS>Mit freundlichen Grüßen
Makan Sheida

Brillux GmbH & Co. KG
Makan Sheida
IT Systemadministration
Weseler Straße 401
48163 Münster

https://www.brillux.de
m.sheida<EMAIL_ADDRESS>Tel. +49 251 7188-451tel:+492517188-451
Fax +49 251 7188-59838tel:+492517188-59838

Brillux GmbH & Co. KG, Sitz Münster, AG Münster HR A 3194
P.h.G. Brillux GmbH, Sitz Münster, AG Münster HR B 4272
GF Peter König, Ulrike Nordemann, Michael Thompson
Von: Manish-MSFT<EMAIL_ADDRESS>Gesendet: Mittwoch, 18. November 2020 10:40
An: MicrosoftDocs/msteams-docs<EMAIL_ADDRESS>Cc: Sheida, Makan<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Betreff: Re: [MicrosoftDocs/msteams-docs] Powerpoint presentation via iOS bug discovered (#2330)
We tried the same at our end, but it seems working on our device. Could you please let us know the name you are trying to provide. Thanks.
[image]https://user-images.githubusercontent.com/70321016/99512915-0d5b4400-29b0-11eb-9adc-6b563590b127.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/msteams-docs/issues/2330#issuecomment-729558016, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARYVLYQUYZSI3U2ZJZNCSILSQOI6BANCNFSM4TW6HO5A.

@SheidaBX, I have hosted the file on one drive via MS Teams. Are you also facing the same issue with teams? or is it just related to One Drive.

I tried both ways to be sure…
Testfile & 1.pptx went directly to OneDrive and provoked the error.
Testfile & 2.pptx was saved locally, uploaded via Teams into a Testteam and used in a 1:1 call – it also provoked the same error message.
After deleting the “&”-Symbol, it worked out immediately.
Out of curiousity I exchanged the “&-Symbol” for “%” and it still worked out. Renaming it back, and it didn’t.
Von: Manish-MSFT<EMAIL_ADDRESS>Gesendet: Donnerstag, 19. November 2020 05:33
An: MicrosoftDocs/msteams-docs<EMAIL_ADDRESS>Cc: Sheida, Makan<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [MicrosoftDocs/msteams-docs] Powerpoint presentation via iOS bug discovered (#2330)
@SheidaBXhttps://github.com/SheidaBX, I have hosted the file on one drive via MS Teams. Are you also facing the same issue with teams? or is it just related to One Drive.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/msteams-docs/issues/2330#issuecomment-730122942, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARYVLYW632KRCVLLVPRUN73SQSNZJANCNFSM4TW6HO5A.

Thanks @ShiedaBx. We are investigating this internally.

@SheidaBX , On our side we see ppt appearing correctly. Which MS Teams version are you using? Could you please test it after updating teams desktop client.


Fuse limits range weights from >0 to <1, contradicting the docs

Describe the bug
I am receiving the error '"weight" property in key must be in the range of (0, 1)' when using weights that are suggested as an example in the Fuse.js docs, including a weight of exactly 1, or weights of more than 1.

Version
Version 5.2.3
Is this a regression?
I do not know
🔬Minimal Reproduction
const list = [{
title: "A Bug Report",
author: "Bashu"
}]
const options = {
   keys: [
          {
            name: 'title',
            weight: 2
          },
          {
            name: 'author',
            weight: 1
          }
   ]
}
const fuse = new Fuse(list, options)
fuse.search('Bashu')

Additional context

Hey :)
I've dealt with that problem recently, just do:
npm i<EMAIL_ADDRESS>For some reason, "npm i fuse.js" doesn't install the latest version...
Wrote about it: https://github.com/krisk/Fuse/issues/463
Enjoy the weekend! :)


Remap ¬ to | (pipe)

Hey !
I'm on MacOs Sierra and i can't remap the pipe ( alt+shift+L ) on the ¬ ( alt+L ), i put this in my karabiner.json :
"simple_modifications": {
    "¬": "|"
}

But it does not work, what im doing wrong ?
Thanks !

"simple_modifications" means that only single keycode (physical key) can be mapped to another single keycode (e.g. caps_lock to escape). Support for keycode combinations is planned, but yet not implemented.

I'd like to do similar by changing the session to pipe symbol: "§" : "|".
Is there any new update that enables that?


[MM-46683]: Add alt click shortcut to mark thread unread in global threads inbox

Summary
Marking thread item unread on alt + click in global threads inbox
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-46683
Related Pull Requests
NONE
Screenshots
https://user-images.githubusercontent.com/16203333/188550922-391f5d5d-c026-47b7-9ff1-3ed88409b150.mov
Release Note
* Marking thread item unread on alt + click in global threads inbox

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

@mylonsuren If you could prioritize this.

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/238378

/cherry-pick release-7.3

Cherry pick is scheduled.

/cherry-pick cloud

Cherry pick is scheduled.


Bug in backpress.

Current behavior - If the navigation bar is open and user presses back key the app is closed.
Expected behaviors - If the navigation bar is open and user presses back key the navigation bar should close.
Should I send a PR.

@free4murad Go on

@garg-anuj Please don't forgot to assigned the issue when say "Go on" to avoid confusion


Design API for converting data to/from bytes

The current #[bitfield] API is self-contained in the sense that within a single Rust application we can place data into bitfields and get the data back out, which is potentially useful for optimizing memory usage of memory-intensive applications but not the primary use of bitfields. For interacting with other systems, we would need more than this. For example to use modular-bitfield to manipulate incoming data packets from the outside world -- this isn't a thing that can be implemented using new and get_* and set_*. Would transmute be the recommended way for downstream code to solve this or is there a better approach?

Thanks for the suggestion!
The to_bytes conversion is simple. We can just generate:
fn to_bytes(&self) -> &[u8] { &self.data }

The from_bytes conversion is actually the annoying one since we may have to consider bitfield structs that might contain invalid bit sets. For example this could be well introduced with the feature to support non-powers-of-two enum bit specifiers.
Also it is an open question whether to take [u8; N] where N is the total number of bytes in the struct or whether something more generically useful such as &[u8] or impl Iterator<Item = u8> should be taken as argument in the from_bytes constructor.
Also for the cases with invalid bit ranges mentioned above we need to return a Result instead of Self directly.

With https://github.com/Robbepop/modular-bitfield/commit/48bd16c09226512653f5b27c159777084c43b3d1 in place we should have an easier life implementing a sane API for converting from bits.

Simplified implementation that does not yet respect the eventually future addition of non-power-of-two enums: https://github.com/Robbepop/modular-bitfield/commit/5c557985ead499083582cc6c7891377c6516a2bc


feat(ga): backfill unit tests

Issue
https://github.com/SAP/guided-answers-extension/issues/141
Description
Tests for:

Logo
Navigation Buttons

Checklist for Pull Requests

[ ] Supplied as many details as possible on this change
[ ] Included the link to the associated issue in the Issue section above
[ ] The code conforms to the general development guidelines.
[ ] The code has unit tests where applicable and is easily unit-testable
[ ] This branch is appropriately named for the associated issue

Thanks!


Please update index.d.ts

Hi,
Please update sagaMiddlewareFactory interface.
I realize it is not updated to a newer version.
params emitter is require. Why?
In API Reference it was not mentioned as require.
Please update index.d.ts
Thanks.

cc @aikoven

This will be covered by https://github.com/redux-saga/redux-saga/pull/740.
For now, if you're not using strictNullChecks, you can set emitter: null. Otherwise, you can try this:
const sagaMiddleware = sagaMiddlewareFactory({...options} as any)

@aikoven: Thank for your solution.
Currently, I'm using override code with:
/**
 * Redux Saga
 * redux-saga-d.ts
 */
import {SagaMiddleware, Monitor, Emit} from "redux-saga";

declare module 'redux-saga' {
    export default function sagaMiddlewareFactory<T>(options?: {
        sagaMonitor?: Monitor;
        emitter?: (emit: Emit<T>) => Emit<T>;
    }): SagaMiddleware;
}

Going to close it for now as issue seems to be resolved. If you have any further issues please reopen.


WIP: Various bugfixes and enhancements

Bugfixes and enhancements for the following issues:

Clair database injected postgresql PVC
Added support for compute resources
Added support for node selector
Mount Quay SSL into extra_ca_certs directory

Resolves #50 #52 #51 #43

Operator Image to test: quay.io/ablock/quay-operator:1547d53517b381c28f2441650ff335a4a6976ab7


Improve testing mechanisms

Intro
Here is a suggestion to improve the testing process.
What was the problems:

The VCR cassettes are only usable with the CLIENT_ID and CLIENT_SECRET of the person that created the record.
Every time a test is run, even against the cassette, there is an authentication. It is therefore impossible to create tests without storing some credentials in the code, which is obviously not good.

What I propose:

Adding a tag type to each spec to be able to execute before :all calls in the rspec config file and not have to write it in every single test. I set the tag game_date for every call against an "Game Data API" and community against the "Community API"
Adding a fake_authentication method in the RBattlenet Class. It sets the @@token variable with a dummy token.
Update every VCR cassettes to use the dummy token. It's probably dangerous to let valid tokens in the record.
Removing the before call on every spec, and add new configuration in the spec_helper.rb file to set the dummy token when testing or execute the RBattlenet.authenticate if the REAL_CONNECTIONS or RECORD_CASSETTE ENV variables are set.
If the VCR cassette does not exist yet, it's possible to write a new ones with the RECORD_CASSETTE ENV variable

What for

It is now possible to simply execute bundle exec rspec spec/ to execute every tests without any authentications (good for automated tests, code coverage, etc). It is also way more quicker this way.
There is no more "real" tokens stored in the VCR cassettes, only the dummy one.

thanks!


Can you set it to slide left and right

Can you set it to slide left and right

Yes, of course you can. Swiping left and right is the default behaviour :+1:

Yes, of course you can. Swiping left and right is the default behaviour :+1:

what if slide it bottom to top and
vice versa top to bottom...? in which syntax should we declare to achieve this functionality?

what if slide it bottom to top and vice versa top to bottom...? in which syntax should we declare to achieve this functionality?

#7 and the related issues.


Customize success message

Would be better to have an environment variable to customize the success message shown in the success page. Having to touch the codebase for a text customization feels unnecessary.

@VigneshPT did you get a chance to work on this?

Thanks for the information Oursainsburys


Typescript error: Interface 'Card' incorrectly extends interface 'ReactListViewProperties'

- react-native 0.54.2 (via expo sdk-26.0.0)
- @types/react-native 0.55.1
- react 16.3.0-alpha.1
- @types/react 16.3.8
- native-base 2.4.1
- typescript 2.7.1

Expected behaviour
./node_modules/.bin/tsc --pretty command should not return any errors
Actual behaviour
./node_modules/.bin/tsc --pretty
node_modules/native-base/index.d.ts:482:13 - error TS2430: Interface 'Card' incorrectly extends interface 'ReactListViewProperties'.
  Types of property 'ref' are incompatible.
    Type 'string | ((instance: ViewProperties | ReactListViewProperties | null) => any) | RefObject<ViewPro...' is not assignable to type 'string | ((instance: (ListViewStatic & ScrollViewStatic & ViewStatic) | null) => any) | RefObject...'.
      Type 'RefObject<ViewProperties | ReactListViewProperties>' is not assignable to type 'string | ((instance: (ListViewStatic & ScrollViewStatic & ViewStatic) | null) => any) | RefObject...'.
        Type 'RefObject<ViewProperties | ReactListViewProperties>' is not assignable to type 'RefObject<ListViewStatic & ScrollViewStatic & ViewStatic>'.
          Type 'ViewProperties | ReactListViewProperties' is not assignable to type 'ListViewStatic & ScrollViewStatic & ViewStatic'.
            Type 'ViewProperties' is not assignable to type 'ListViewStatic & ScrollViewStatic & ViewStatic'.
              Type 'ViewProperties' is not assignable to type 'ListViewStatic'.
                Property 'DataSource' is missing in type 'ViewProperties'.

482  	interface Card extends ReactNative.ViewProperties, ReactListViewProperties {
     	          ~~~~

Thank you for Native Base and thank you for helping with this issue!

Seeing the same issue.

I had the same issue and I think the problem is with the latest @types/react as opposed to Native Base???

If I use @types/react 16.3.10 I get the above error but if I revert to 16.3.5 I can build OK

See my working package.json - where I have 2 React Native hacks currently:

Fix TypeScript at 2.7.2 since the 2.8 version is broken I think
Fix the above typings at version 16.3.5 to work around the issue you've found

Anyway - I'm not any kind of React Native expert - but I hope this helps.

Fixed with 2.4.3


upcoming: [M3-7301] - Replace Linode Network Transfer History chart with Recharts

Description 📝
This PR is part of a bigger effort to replace chart.js with the more modern Recharts. As a first step, replace the Linode Network Transfer History chart.
Preview 📷

Before
After

How to test 🧪
Prerequisites

Have a Linode that's been running for a while

Verification steps

Go to the Network tab of a Linode that's been running for a while
Confirm the updated UI and that there are no regressions in the graph, units, etc

As an Author I have considered 🤔
Check all that apply

[x] 👀 Doing a self review
[x] ❔ Our contribution guidelines
[x] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[x] 🧪 Providing/Improving test coverage
[x] 🔐 Removing all sensitive information from the code and PR description
[x] 🚩 Using a feature flag to protect the release
[x] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[x] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

Dark mode looks much better now, but would it be possible for the tooltip to have a dark gray background with white text instead of a while background? I think that would look more fitting with our theme.
Hopefully we can do this without adding a ton of extra code. If we need to, we can define a custom component to use as the tooltip (https://github.com/bnussman/managernext/blob/main/src/linodes/Stats.tsx#L121-L132)

Nice, I really like the refreshed look of the chart. I tested the changes in mobile view and only noticed a small visual regression, however, it appears that the dates displayed to the user are also different.

OLD
NEW

@carrillo-erik Updated x-axis intervals. The dates will be slightly different but there's not much we can do without increased code complexity. The information is still correct, recharts is just choosing to display a different date


Make screen reader announce successful MovePane and MoveTab actions

Uses the RaiseNotificationEvent() API from UIA automation peers to announce successful MovePane and MoveTab actions. The announcements are localized in the resw file.
Closes #15159
Based on #13575

This complies with the letter of the requirement, but does it comply with the spirit of the requirement? What does it mean for it to have been "moved successfully"?

This complies with the letter of the requirement, but does it comply with the spirit of the requirement? What does it mean for it to have been "moved successfully"?

Yeah, the associated bug isn't that descriptive. And I have trouble finding other apps that do this too (VS Code doesn't do it, and VS is notoriously noisy so I didn't bother to check), ugh.
All the associated bug says (even in the video) is that we need to say that we've moved successfully. So, it seems like the requirement is just to tell the user that the action was executed successfully.
@codeofdusk is there anything specific you'd expect the screen reader to say if you moved a tab or pane to another window?

The announcements now include a bunch more info. I tried building/deploying this commit, but I got a weird error down in the AcvtivationFactory that didn't really explain anything at runtime. I'll try building/deploying on my machine at home and I'll look into this more tomorrow.
For now, this should be in a good reviewable state though :)


Improve Echo Logger

Change default logger for something like this :
[2018-01-16 10:35:24.38231] [MiddlewareServer/server.go:147] [INFO ] – Starting....
[2018-01-16 10:35:24.38252] [MiddlewareServer/server.go:148] [ERROR] – some error
Instead of JSON
See : https://github.com/labstack/echo/issues/1017

Is there a reason to not be logging in JSON? JSON logging seems pretty standard to me...


Unified Pipelines clean-up.

This PR removes the client.yml pipeline that was in use before unified pipelines was rolled out. As part of this clean-up we will also be doing the following:

[ ] Removing the internal python - client pipeline.
[ ] Removing the public python - client - ci pipeline.
[ ] What else do we need to do here?

Can one of the admins verify this patch?

@scbedd are you good with removing the python - client - ci pipeline or are you still depending on it?

Before we do this, I gotta write up instructions for the management team. They still need the ability to do this.
Also, our nightly build (which the management team also uses to release) is using the client.yml. I can swap that to just leverage the archtype-sdk-nightly.yml specifically.
However, I don't want to remove the nightly build entirely. I want to use it to test some of our other scenarios.

I want to use it to test some of our other scenarios. I do not agree with the complete removal of this pipeline by any stretch.

The python - client build has been failing since Friday. If a build fails in the forest and no-one hears it ...
I think we should try to figure out a way of detecting the issues we want to detect more efficiently and ideally within the bounds of the scoped unified pipelines. I don't know how we do that though.
One issue you highlighted when we discussed was namespace corruption. It's a specific instance of socialization testing where we see whether modules if loaded into the same process step on each other. That was one of the stated goals of smoke tests, which seemed lighter weight than the test runs.
Currently python - client consumes 18 hours of agent time each time it runs.

It's been failing since Friday except for last night where it was disabled. Praveen checked in the fix to resolve the failure yesterday :) We definitely knew it was blowing up.
You have a good point about the smoke-testing. Maybe we move the socialization build and test to a separate in the smoke-test build? If we do that. Yeah, I'm cool with killing this thing.

You have a good point about the smoke-testing. Maybe we move the socialization build and test to a separate in the smoke-test build? If we do that. Yeah, I'm cool with killing this thing.

The smoke test would be strictly a subset of the current test scenarios?

I believe that this PR is ready to go @scbedd  --- I've moved the python - client definition into \python\legacy rather than delete it (just for services issues that might come up) - but the pipeline itself is disabled so won't run unless someone explicitly re-enables it.


doesn't compile with gcc or clang

Using gcc (4.8.2) and clang (3.3 or 3.6) ripe_attack_generator.c fails to compile:
Here are two errors I've seen a few times:
/source/ripe_attack_generator.c:80:34: error: initializer element is not a
compile-time constant
0xDEADBEEF,0xDEADBEEF,0xDEADBEEF,&exit, &cf_ret_param,448}; //448 => 0700 mode
^~~~~
./source/ripe_attack_generator.c:112:27: error: initializer element is not a
compile-time constant
static int rop_sled[7] = {&gadget1 + 62,0xFFFFFFFF,&gadget2 + 62,&cf_ret...
^~~~~~~~~~~~~
Any idea what it would take to fix this? From a cursory look at the file, it looks like these could just be filled in at runtime...

Hi,
This must be something that happened due to a change in what's allowed in GCC and what's not. I will have a look and let you know.
Nick

This issue seems not effecting 32-bit builds. I faced the same issue exactly as @jugonz described, but it disappeared after passing '-m32' to GCC (5.2.0) or Clang (3.6.2).

@jugonz I have the same problem with you, Have you solve it?


Rlarsson/replymessage whatsapp optin methods

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

[X] I attest that the connector works and I verified by deploying and testing all the operations.
[X] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[X] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[X] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[X] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[ ] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

@sriyen-msft the requested changes have now been made.

Hi @robin-larsson! Our certification engineer, Srikanth, is currently on emergency leave. Please expect a delay with your PR. He will return January 31st, 2022. We apologize for any inconveniences.


Better map appearance

Change the appearance of the map to look more like League Of Legends (not only some grass-tiles repeated, but maybe some lanes, water, etc)

Connected to #23


python3Packages.edge-tts: init at 7.0.0

edge-tts is an utility to use Microsoft Edge's online text-to-speech service from Python without needing Microsoft Edge or Windows or an API key.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

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

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Moved package to python3Packages since it can be better packages as a Python module


Set Week Days Label IN Upper Case

Hi
How can set week days label in capital letters Like (SUN,MON , etc)
i have used
_calenderView.appearance.caseOptions = FSCalendarCaseOptionsHeaderUsesUpperCase;
but its not working
can you please give me and idea
i have faced other issue i have set titleoffset
_calenderView.appearance.titleOffset = CGPointMake(0, 2);
its seem perfect, but while selecting a cell text goes down.
is there any way to fix in correct location
Thanks

for your first question, you can use this option :
_calenderView.appearance.caseOptions = FSCalendarCaseOptionsWeekdayUsesDefaultCase | FSCalendarCaseOptionsWeekdayUsesUpperCase;

thanks.

can you please check title offset issue i have faced
thanks

could you provide screen shoots for that issue ?

Same request as @yigityuksel .  And can you provide more information as the issue template requested?

Thanks for support
i have set tittleOffset (0,3)
its perfect for unselected dates, but when i select a date date text is shown bit below.
please check images attached
please help to fix this issue

Still cannot reproduce. If you have a demo for this, please feel free to send.

谢谢你的支持>> 我设置了tittleOffset（0,3）>>它非常适合未选择的日期，但当我选择日期时，文本如下所示。>> 请检查所附图像>> 请帮助解决这个问题>> ![屏幕截图2016-11-11晚上7 32 30]（https://cloud.githubusercontent.com/assets/16162588/20179635/2cfb3982-a77d-11e6-84af-15a2727ea60d.png）！[屏幕截图2016-11-11晚上7 32 50]（https://cloud.githubusercontent.com/assets/16162588/20179637/2f6545be-a77d-11e6-9fe1-9620a422723b.png）规定浓度
最后怎么解决的?


Simplified syscall error

Refactored the syscall errors. There is no need to create an error for each syscall. Only the errno is what is required. Other context can be logged at the site of the errors.
Removed the UnifiedSyscallError. It was not well thought out at the moment.
Refactored close_range and mount_set_attr to use libc::syscall directly.

Codecov Report

Merging #1949 (07f4aca) into main (0d6b0d5) will decrease coverage by 0.06%.
The diff coverage is 7.38%.

:exclamation: Current head 07f4aca differs from pull request most recent head c45e5f2. Consider uploading reports for the commit c45e5f2 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1949      +/-   ##
==========================================
- Coverage   64.88%   64.82%   -0.06%
==========================================
  Files         127      127
  Lines       14674    14659      -15
==========================================
- Hits         9521     9503      -18
- Misses       5153     5156       +3

Refactored the syscall errors. There is no need to create an error for each syscall. Only the errno is what is required. Other context can be logged at the site of the errors.

I agree with you! It would be wiser for them to see man than for us to give them the message from us.

I've been working on this area lately, and thiserror makes it easy to identify errors. Thanks.


Custom rewrite rules with dots?

I know that this is getting dangerously close to Quantomatic complexity, but I want to at least consider what restricted cases we can reasonably attempt without blowing everything up. I am opening this issue to start a discussion. I don't want to implement general !-graphs because they are too powerful and complex. But something that can allow us to do basic rewrites (e.g. pi-copy to arbitrary number of wires) would be useful in many situations.
Fragment of scalable ZX? Restricted bang boxes? Something even simpler?

We already have a back-end of PyZX where we can write arbitrary Python code to implement rewrites. There's already quite a lot of arbitrary-arity rewrites in there that can be used in ZXLive, including the copy rule and bialgebra. Is it really worth it to build a system around this that is necessarily going to be at least a little complicated while also being restricted in what it can do?

But just to give a suggestion of a restricted pattern that might still cover many use-cases: have certain standard patterns that a user can define on certain generators. We had this different idea of a user being able to specify a custom generator. We could then have something say 'this generator interacts with Z-spiders according to the bialgebra rule', or 'this generator copies through W-states'.

Oh I like this idea of custom generators. This will also give an easy route to qudits by defining the multiplier. Do you think we can define a rule like the following WW bialgebra using these patterns?

Hmm, that is not a standard bialgebra, so that is not covered by what I was proposing I think.
That rule is also quite complicated in that it has 2 bang-boxes and not just 1 (although this is true for any bialgebra rule).

For now, we should do custom generators + standard patterns. I am also interested in looking at scalable ZX but the divide and gather generators are not commutative so I can't think of an obvious way to represent them in pyzx as a graph.


spaceauth token obtained by fastlane spaceauth -u [username] doesn't last a day

New Issue Checklist

[ x] Updated fastlane to the latest version
[ x] I read the Contribution Guidelines
[ x] I read docs.fastlane.tools
[x ] I searched for existing GitHub issues

Issue Description

I am running a github actions pipeline that uses fastlane and spaceauth to deploy a flutter app to the appstore. It works great, but the session token seems to expire within a few hours to a day (haven't tried to narrow down further as mac vms are expensive).
The docs (https://docs.fastlane.tools/best-practices/continuous-integration/) say the token should last about a month.
Is there a fix for this?
Command executed

fastlane spaceauth -u [username]
Complete output when running fastlane, including the stack trace and command used
Output is irrelevant here, i'm asking about the expiry time above.
Environment

 🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.15.7

Ruby
2.6.3

Bundler?
false

Git
git version 2.18.0

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.15.7 (19H2)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
12.1

System Locale

Variable
Value

LANG
en_AU.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.160.0
🚫 Update available

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

slack-notifier
2.3.2

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
4.0.6

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

babosa
1.0.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.76.0

faraday
1.0.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.0

gh_inspector
1.1.3

mini_magick
4.10.1

rubyzip
2.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.6

bundler
1.17.2

naturally
2.2.0

simctl
1.6.8

jwt
2.2.2

uber
0.1.0

declarative
0.0.20

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

multi_json
1.15.0

signet
0.14.0

memoist
0.16.2

os
1.1.1

googleauth
0.13.1

httpclient
2.8.3

google-api-client
0.38.0

google-cloud-env
1.3.3

google-cloud-errors
1.0.1

google-cloud-core
1.5.0

rake
13.0.1

digest-crc
0.6.1

google-cloud-storage
1.29.0

emoji_regex
3.0.0

jmespath
1.4.0

aws-partitions
1.376.0

aws-eventstream
1.1.0

aws-sigv4
1.2.2

aws-sdk-core
3.108.0

aws-sdk-kms
1.38.0

aws-sdk-s3
1.81.1

nanaimo
0.3.0

colored2
3.1.2

claide
1.0.3

CFPropertyList
3.0.2

atomos
0.1.3

xcodeproj
1.18.0

json
2.3.1

forwardable
1.2.0

logger
1.3.0

stringio
0.0.2

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

date
2.0.0

fileutils
1.1.0

etc
1.0.1

io-console
0.4.7

zlib
1.0.0

libxml-ruby
3.1.0

rexml
3.1.9

psych
3.1.0

mutex_m
0.1.0

webrick
1.4.2

generated on: 2020-10-23

We don't really have any influence on how long Apple decides cookies / tokens are valid. If possible switch over to using the new App Store Connect API key, if your action supports this.

The document should state that it shouldn't last about a month.  But less than a day.

There's no official documentation how long this lasts. It's completely in Apple's domain.

https://docs.fastlane.tools/best-practices/continuous-integration/ says that it can last about a month. You may as well change the wording there saying it is in Apple's domain and note that people may be experiencing it only lasting a day.  Because having it written there will make more people open bugs like this.

I agree with @trajano . I raised this ticket because it doesn't behave as the documentation says.
This ticket should be kept open until it's fixed?

I changed the documentation. There is nothing we can „fix“, as we have no influence on how long cookies from Apple last. Please open a radar with Apple if you are not happy with their cookie durations.


Add test for foreign keys

Desired Behaviour
Foreign keys is one of the trickier functions to automate testing for. Try add this as example for others to leverage for their code contributions

foreign keys is part of validation acceptance tests, so have had to spend time on overarching validation instead.


Storage Java Client Library Samples

link does not work?

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

ID: 6783e136-eeb6-054d-c257-ee3e7135caae
Version Independent ID: 86cb3b76-050d-c9a3-0402-c2af496e7364
Content: Azure Storage samples using Java
Content Source: articles/storage/common/storage-samples-java.md
Service: storage
GitHub Login: @seguler
Microsoft Alias: seguler

@jontejj Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@jontejj can you tell me specifically which link did not work for you? Thanks

#reassign:@mhopkins-msft

@mhopkins-msft - I think you've already verified all links in the article, right? If so, please go ahead and close.

Yes, the broken links were fixed.
#please-close


Include code examples of what to do/what not to do when handling errors

Guidance here needs to be much stronger:
https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/conversations/subscribe-to-conversation-events?tabs=dotnet#handling-errors-in-conversation-events
Provide a sample of incorrect vs correct error handling code
Give examples of cases that lead to nonsensical messages like the one in the screenshot.
Tell developers how they can test these cases. These error conditions are often edge cases that developers might not know how to test until they see them in production after deployment. For example, the conversationUpdate that they receive when a user leaves the tenant.

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

ID: 0a6d00a4-dd28-33c4-002e-2e8e7c653ce2
Version Independent ID: 0856927a-25f4-b1e0-5f1b-d55dc61796f3
Content: Conversation events - Teams
Content Source: msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
Service: msteams
GitHub Login: @WashingtonKayaker
Microsoft Alias: anclear

Hello @aosolis We will investigate the issue and get back to you soon.

Hello @aosolis
**Provide a sample of incorrect vs correct error handling code:
Incorrect sample code C#**
public class AdapterWithErrorHandler : CloudAdapter
{
public AdapterWithErrorHandler(BotFrameworkAuthentication auth, ILogger logger, ConversationState conversationState = default)
: base(auth, logger)
{
OnTurnError = async (turnContext, exception) =>
{
// Log any leaked exception from the application.
logger.LogError(exception, $"[OnTurnError] unhandled error : {exception.Message}");
            await turnContext.SendActivityAsync($"Sorry, it looks like something went wrong. Exception Caught: {exception.Message}");

            // Send a trace activity, which will be displayed in the Bot Framework Emulator
            await turnContext.TraceActivityAsync("OnTurnError Trace", exception.Message, "https://www.botframework.com/schemas/error", "TurnError");
        };
    }
}
**Node js**
adapter.onTurnError = async (context, error) => {
// This check writes out errors to console log .vs. app insights.
// NOTE: In production environment, you should consider logging this to Azure
// application insights.
console.error(`\n [onTurnError] unhandled error: ${ error }`);

// Send a trace activity, which will be displayed in Bot Framework Emulator
await context.sendTraceActivity(
    'OnTurnError Trace',
    `${ error }`,
    'https://www.botframework.com/schemas/error',
    'TurnError'
);

 // We should not send this kind of error to users.
 await context.sendActivity(`Sorry, it looks like something went wrong. Exception Caught: ${error}`);

};

Give examples of cases that lead to nonsensical messages like the one in the screenshot.
During error handling at global level, we should not send unnecessary message to users like below:
adapter.onTurnError = async (context, error) => {
await context.sendActivity(Sorry, it looks like something went wrong. Exception Caught: ${error});
};
Tell developers how they can test these cases. These error conditions are often edge cases that developers might not know how to test until they see them in production after deployment. For example, the conversationUpdate that they receive when a user leaves the tenant.
Developers can put a debugger and can test the different cases in the application errors in onTurnError method like below:
adapter.onTurnError = async (context, error) => {
 // Comment this line during production deployment.
 await context.sendActivity(`Sorry, it looks like something went wrong. Exception Caught: ${error}`);

};


Syncing with nodes out of sync?

While updating to v13 in one of my nodes somenthing weird happened. I used the database I had in v12, which was almost up to date, then the v13 started syncing just fine for a while:
    DEBUG SYNC [sync-import]: <try-import-block num=266113 hash=d5c851 parent=c39e81>
    INFO  SYNC [sync-import]: <import-best num=266113 hash=d5c851 txs=0>
    DEBUG SYNC [sync-import]: <try-import-block num=266114 hash=029168 parent=d5c851>
    INFO  SYNC [sync-import]: <import-best num=266114 hash=029168 txs=0>

But then at some point it started failing all of a sudden:
    ERROR SYNC [p2p-write]: <res-bodies decode-msg>
    DEBUG SYNC [p2p-write]: <res-bodies bodies=321 from-node=0466a7>
    DEBUG SYNC [p2p-write]: <validate-incoming-blocks size=321 from=265877 to=266197>
    DEBUG SYNC [sync-import]: <try-import-block num=265877 hash=fcb880 parent=436f5b>
    DEBUG SYNC [sync-import]: <import-unsuccess err=no-parent num=265877 hash=fcb880>
    DEBUG SYNC [sync-import]: <try-import-block num=265878 hash=1c4293 parent=fcb880>
    DEBUG SYNC [sync-import]: <import-unsuccess err=no-parent num=265878 hash=1c4293>

The only way I find to explain this is that my node started to sync with another peer with off-chain blocks and got off-chain as well, then it tried to sync with an on-chain node and could not move forward. Is somenthing like this possible?

I can confirm that this behavior is also happening to me.  However, it even happens when the only peers it's connected to are all up to date.

the upcoming release ( v0.1.14,  Mar 5, Monday)  will help fix this issue by bring better stable syncing.  but incase you on sidechain,  you need ./aion.sh -r  block_number to revert your sidechain back.


New window with no selected panel item

I keep getting a panel open with no selected tab:

I can't figure out why this is happening, it must be related to which panel I had focused the last time the window was open. But I have seen it many times in the past couple days. Is this related to grid stuff and how can I get more info?

@roblourens anything in dev console? can you try testing with grid layout disabled for a bit if it reproes very consistently

I'm pretty sure there were no errors anywhere. It doesn't repro that consistently but I can disable grid layout to see whether it shows up.


Add option to not follow copilot-chat--shell-cb-prompt point?

When asking a question to Copilot Chat using shell-maker, the current point continuously jumps to the end of the chat buffer. This is because the current point is being modified without the use of save-excursion.
https://github.com/chep/copilot-chat.el/blob/d2f3ef17d755d8920c747ee5677db5b003a13406/copilot-chat-shell-maker.el#L105-L129
This might be intended behavior, but I find it very challenging to read Copilot's responses until the message is finalized.
Suggested options:

If this is intended behavior, add an option to wrap the entire body of copilot-chat--shell-cb-prompt in a save-excursion block.
If this is intended behavior, wrap the body in save-excursion and add an option to scroll down after an input. At the end of copilot-chat--shell-cb-prompt add (when option (goto-char (point-max)) (outside of save-excursion).
If this is not intended behavior, simply wrap the body in save-excursion without an option to disable it.

Can you test the new branch 47-shell-follow ?
There will be a new custom copilot-chat-shell-maker-follow. You should set it to nil.

(defun copilot-chat--shell-cb-prompt-wrapper (shell content)
  (if copilot-chat-shell-maker-follow
    (copilot-chat--shell-cb-prompt)
    (save-excursion
      (copilot-chat--shell-cb-prompt))))
;;...
(apply-partially #'copilot-chat--shell-cb-prompt-wrapper shell)

I believe something like this would fix it

I already tried something like this in the past. I got problems with shell-maker.

FWIW this is how I currently resolve the issue locally. By redefining copilot-chat--shell-cb-prompt
(defun copilot-chat--shell-cb-prompt (shell content)
   "Callback for Copilot Chat shell-maker.
 Argument CALLBACK is the callback function to call.
 Argument ERROR-CALLBACK is the error callback function to call.
 Argument CONTENT is copilot chat answer."
   (save-excursion
     (with-current-buffer copilot-chat--buffer
       (goto-char (point-max))
       (when copilot-chat--first-word-answer
         (setq copilot-chat--first-word-answer nil)
         (let ((str (format-time-string "# [%T] Copilot:\n"))
               (inhibit-read-only t))
           (with-current-buffer copilot-chat--shell-maker-temp-buffer
             (insert str))
           (funcall (map-elt shell :write-output) str)))
       (if (string= content copilot-chat--magic)
           (progn
             (funcall (map-elt shell :finish-output) t) ; the end
             (copilot-chat--shell-maker-copy-faces)
             (setq copilot-chat--first-word-answer t))
         (progn
           (with-current-buffer copilot-chat--shell-maker-temp-buffer
             (goto-char (point-max))
             (let ((inhibit-read-only t))
               (insert content)))
           (funcall (map-elt shell :write-output) content))))))

(defun copilot-chat--shell-cb-prompt-wrapper (shell content)
  (if copilot-chat-shell-maker-follow
    (copilot-chat--shell-cb-prompt)
    (save-excursion
      (copilot-chat--shell-cb-prompt))))
;;...
(apply-partially #'copilot-chat--shell-cb-prompt-wrapper shell)

I believe something like this would fix it, and then you won't have to change any of the logical code.

You're right, it seems to work. I pushed your code and added the copilot-chat-shell-maker-follow custom (default is t).

Tell me if I can close the issue.


Actual SourceMap default (Docu)?

Hey @JeffreyWay and crew,
whats the actual .sourceMaps() default output? Is:

in dev build: inlined source maps
in prod build: source maps in separated file

correct?
Where is that documented right now, having a hard time to find info about it 😄
Thanks,
Paul

The default webpack source map plugins are:
Local: cheap-module-eval-source-map
Production: cheap-source-map

@JeffreyWay thanks for your answer, what would be the best place to document that?

I've had an issue with source maps not showing the correct line for months and while it's been a pain, I've lived with it until today. I wish I had done this so much sooner and I hope this will help others.
After doing a source code search I found that sourceMaps takes a second argument, type which correspond to the source map devtool list on the webpack website. Settings this to anything else than the default eval-source-map, worked great!
PS. Not finding this written anywhere on https://laravel-mix.com/docs/2.1/


 Check if this snippet runs on official Go playground - https://go.dev/play/p/UIVCeAUVSyY
I was unable to run the code by myself.

what about wasm backend? it didn't work either

@dcu tried Wasm backend - cannot reproduce.
https://goplay.tools/snippet/_gY0tANzJ4l
Can you open btowser DevTools and check what is going there?

it works, thanks!

@dcu unfortunately WASM mode do not support third party packages for now and considered Expermiental


Unrecognized font family

Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
Please provide a clear and concise description of what the bug is. Include screenshots if needed.
Please test using the latest React Native release to make sure your issue has not already been fixed: https://reactnative.dev/docs/upgrading.html
React Native version:
Run react-native info in your terminal and copy the results here.
System:
OS: macOS 11.2.1
CPU: (8) x64 Apple M1
Memory: 26.16 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.15.4 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 6.14.10 - /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK:
API Levels: 30
Build Tools: 30.0.3
System Images: android-30 | Google APIs Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.87<IP_ADDRESS>42882
Xcode: 12.4/12D4e - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_282 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: ~0.63.4 => 0.63.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Create react-native.config.js with following code:
module.exports = {  assets: ['./assets/font'] }
Run npx react-native link
start project and build to iOS
Getting Unrecognized font family 'Rf-Font'

Expected Results
I wanted get working ttf fonts
Using in my project
export default function App() {   return (       <>       <Text style={{fontSize: 32, marginTop: 64, fontFamily: 'Rf-Font'}}>Test font</Text>       <Text style={{fontSize: 32, }}>Test font</Text>       </>   ); }


ERR_REQUIRE_ESM

Hi
I just clone the sample project and run the typescript script project. I get error
ic import() which is available in all CommonJS modules.
at Object. (kiota-samples\get-started\quickstart\typescript\out\index.js:15:30) {
code: 'ERR_REQUIRE_ESM'
}
Could you please let me know what is wrong here?
Thanks
Chandra

Hi @chandraarora
Thank you for using kiota and for reaching out.
The samples were trailing behind the ongoing development efforts. I have put a PR together to refresh them.
#6755
Let us know if you have any additional comments or questions.


Crashed in first time ssh  connection

First of all, welcome back:D
Describe the bug
after adding a new SSH connection, the app crashed and only crashed in first connection. work fine in second and other times.
Informations

Device : iPhone X
OS : iOS 13.6
WebSSH Pro version : 14.0.4

Screenshots
To Reproduce
Steps to reproduce the behavior:

Go to SSH tab
Add SSH connection
Enter the server info, login with Private key, Save
Tap the server created in step 3 to connect first time
After the fingerprint dialog, turn to the terminal screen, app crash when the transition animation playing

Hey @celerysoft  👋
Thank you a lot for your harm support and for your issue!
Please come on and join on my beta releases :

Please install WebSSH Beta from TestFlight app : https://testflight.apple.com/join/QSrBK59z
Then reproduce the crash
Finally you will able to send the crash report to me through TestFlight app

Could you try again?
☀ Have a nice day

awesome, this bug was fixed in TestFlight version


manager multi tenant

Feature request:

Add manager multi tenant.

Use case:

UI Example:

REST API Example: /api/v1/tenants/{:tenant_id}/schedulers/{scheduler_id}
Create Tenant table associated other tables without CasbinRule.
When creating a tenant, tenant root permissions are automatically created in CasbinRule table.
Root user can manage all tenants


Add build information to diagnostic output

Adds important build information to SHOW DIAGNOSTICS output. To make this work I had to add more information to the Server type.
> show diagnostics
name: build
-----------
Branch  Commit  Version
master  kahk397 0.9

+1

Thanks @corylanou

This passed on Circle, but they decided to run the build again.


Expected behaviour for booleans with no set default

What is the intended behaviour for a boolean field that does not have a default in the schema but is empty/unset in the samplesheet?
I believe this may be an issue because I was under the impression that we do not support default: false in schema jsons (although maybe I am wrong here?).
Currently if there is no default and someone leaves the field unset it will result in:
in meta:
[boolean_field: null]

otherwise:
[[]]

This is a really difficult issue to tackle due to the complexity of the new JSON schema. An input can sometimes be more than one type so it's hard to define what the default should be. I'll take a look at this later and see if there maybe is some kind of a compromise to be made

The easiest solution in this case would be to just set the default to false that way you specifically annotate what value should be the default instead of having an inferred default. Feel free to reopen if you disagree with this :)

I am not sure what the current status of "default": false is in the schema but nf-core/tools still seems to advise against it:
https://github.com/nf-core/tools/blob/ddb58c20e757e3b2a384a5ccb8ddd2a5b4af59f9/nf_core/pipelines/schema.py#L334C1-L338C18
Perhaps @mirpedrol can shed a bit more light?

I personally don't like having inferred defaults especially for samplesheets. It just makes everything way more complicated overall IMO.
AFAIK nf-core/tools only has this for the parameters (in which case it is fine because nf-schema doesn't fill in parameter defaults). The tooling does nothing with the samplesheet schema I think

Hi! Yes, the decision of removing default: false is only for parameters, this was done to avoid printing all the parameters when we print the summary of parameters that change (here some Slack conversations about this back when we made the change). We don't have tooling for the schema yet, so you can add a default there :)


Payment gateway UI bug

Description

As soon as a logged in user enters cart, payment gateway automatically pops up without any clicks. Needs to be fixed.

Also, the increase count button is not working.

Hi!
I'd love to work on both of these issues, please.

Go ahead @Mehdi-Messaadi, and yes tracking 2 tickets makes sense.

Closing as fixed by #133. Making a new issue for count not working.


CI can randomly fail

Emulating the examples can rarely fail due to the wowki api hanging.
Seen in https://github.com/Reavershark/esp-dlang/actions/runs/10300703635.

Similar issues (upstream)

https://github.com/wokwi/wokwi-features/issues/843
https://github.com/wokwi/wokwi-features/issues/721

It is possible to check some tests configured in wokwi.
https://github.com/wokwi/esp32-test-binaries/actions/runs/9772848828#summary-26978099923


Build from guide template file incompatible with EPIC components

Hi @miquelcampos
It turns out that building from a guide file is incompatible with EPIC components. In the EPIC components __init__.py jnt_pos gets appended with self.guide.guide_locators which is referencing what is in the scene at the time thus it will return None because the guide is not in the scene.
I tried finding an alternative way of accessing specific guide locators. Apart from the root, for which self.root exists, you cannot seem to get any of the locators under the root, like the spineTop or spineBase in the case of the EPIC spine.
the guide file with the component dictionary has those locators in there but they are keys with position values. Perhaps updating what information gets stored in the guide file will help, like adding "guide locators" to the .sgt file per component?

Hi @Lohult
Sorry, I didn't reply before to this. That is a very nasty bug. I will fix it ASAP.
Thanks for the feedback!

@Lohult this was fixed in the issue #112


move_to_curved function added (revised)

There is still quite a few things bothering me here, I appreciate the attempt to contribute but I cannot accept the pr as it is;

_beziercurve.py does not follow the same naming conventions as the rest of the projects, function names and several variables names are not written in snake_case as they should be.
Most of the math essentially just looks gpt generated and pasted, it doesnt even attempt to explain what the purpose of it is or link to any article to read about the functionality.
In both inputs.py and _beziercurve.py you added a MOVE_SPEED parameter, why is it full caps? That should be reserved for constants..
I understand what you were trying by placing the math functions into the curvePoints function, but the correct way would have been to have them scoped to the modul prefixed with an underscore.
Why do we need both _curve.py and _beziercurve.py? They should just be the same module
With this design we expose zero control over the specific creation of the bezier curve to the user, the move_to_curved function should have an optional bezier curve object parameter and people should be able to create custom bezier curves.

Decided to have a go at adding this myself - implemented it by offering the functionality if pyclick is installed and exposing a dataclass with the curve parameters to the API that can be used to generate the curve.
IMO this is the best of both worlds, dont need to write up code someone else already has but also dont force the PyClick install on someone who isnt even going to use the curves.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.13 to before v5.16.11",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=232f75d3b4b5456de6f0b671aa86345d62de1473",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=352193edda48e08e8824a7ece09aec830a603cfe"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "232f75d3b4b5456de6f0b671aa86345d62de1473",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "352193edda48e08e8824a7ece09aec830a603cfe",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "KVM: x86: nSVM: fix potential NULL derefernce on nested migration\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.16.11 by commit 352193edda48e08e8824a7ece09aec830a603cfe, it was introduced in version v5.13 by commit 232f75d3b4b5456de6f0b671aa86345d62de1473. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000537


Brainstorming and Selecting a Persuasive Quote for Marketing Campaign

Description:
In preparation for an upcoming marketing campaign, we aim to incorporate a compelling and persuasive quote that resonates with our target audience. This issue is dedicated to brainstorming and collaborating with team members to generate ideas and ultimately select a quote that effectively communicates our brand message and motivates action.
Objective:
Engage the team in a collaborative brainstorming session to generate impactful quotes that align with our marketing campaign's goals. The selected quote should serve as a powerful method of persuasion, encouraging audience engagement and fostering a positive perception of our brand.
Proposed Steps:

Brainstorming Session:

Schedule a team meeting to collectively brainstorm potential quotes.
Encourage team members to think about the campaign's objectives, target audience, and the emotions we aim to evoke.

Discussion and Evaluation:

Facilitate a discussion to review and evaluate the proposed quotes.
Consider the alignment of each quote with our brand identity, campaign theme, and the desired emotional response from the audience.

Finalization:

Narrow down the list of quotes based on team feedback and discussion.
Aim for a quote that is concise, impactful, and aligns seamlessly with the campaign's persuasive intent.

Went through different interations for this one.
Came up with 2-3 quotes to write in the hero section to create interest among the customers.
After being reviewed by the professor, changed the quote as adviced by Professor William and added a sense of urgency and scarcity with the help of quote.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-source-version-target/pull/179 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-source-version-target.git

Docs Build status updates of commit 8f64f01:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

versioningArchiveSourceFolder/TOC.yml
:white_check_mark:Succeeded
View (sql-server-2014 || azuresqldb-current || azuresqldb-mi-current || azure-sqldw-latest || >= aps-pdw-2016 || >= sql-server-2016 || >= sql-server-linux-2017 || sql-server-previousversions || sqlallproducts-allversions)

versioningArchiveSourceFolder/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Use of inline classes does not play well with iOS

It was nice to use inline classes for some of the types, but unfortunately the Swift interoperability is greatly hampered by this. For example, a function that returns a Date or a DateTime when translated to Swift it simply becomes int32_t and the Date and DateTime classes are not accessible at all from Swift. This makes it extremely to write iOS apps dealing with dates. While it would be nice to be able to write all code in Kotlin without resorting to Swift, the fact that you can't export a UIViewController class to IOS makes that unrealistic

The idea of doing this is because I'm using this library in projects where being as allocation-free as possible is pretty critical (games). Unfortunately Java unlike .NET doesn't support value types until Project Valhalla is out. Kotlin/Native as far as I'm concerned is not optimizing small immutable types as values types either. That's the same reasong I'm using Double types instead of Long so JS doesn't require allocations either. There are some tricks like object pooling, or threadlocals to be able to pass complex value to upper functions without allocating, but not implemented by Kotlin either due to complexity which makes sense.
I'm not pretty sure about a good solution. I could create two versions of the library, one providing inline classes, the other providing data classes. Kotlin/Native could also expose inline functions to swift as structs and do casting as required, no allocations either, but nicer to swift.
Summarizing:

From my side I can only see the option of publishing two variants of the library (if you are aware of other solutions, please let me know)
From the Kotlin side we could propose that they consider exposing inline types as structs and perform casting automatically starting with 1.4

What do you think?

Also inline classes makes the Kotlinx serialization compiler plugin crash.
I believe publishing two versions is the best solution.

Kotlin/Native could also expose inline functions to swift as structs and do casting as required, no allocations either, but nicer to swift.

Would be nice, but unfortunately is not the case. As noted here:

Currently, following features are not properly exposed in generated framework headers:

inline classes (arguments are mapped as either underlying primitive type or id)

From the Kotlin side we could propose that they consider exposing inline types as structs and perform casting automatically starting with 1.4

Apparently they will actually be introducing their own date time classes in 1.4:

The support for dates is really needed in the multiplatform world, and this is what we are working on: experimental Durations have been already added to stdlib, and DateTime support is under way.

What I said was to propose doing that to the K/N team. Right now indeed it is not the case.

Some features of Kotlin programming language are not yet mapped into respective features of Objective-C or Swift. Currently, following features are not properly exposed in generated framework headers:

Yeah I'm aware of them to include date and time classes. Please read this one: https://github.com/korlibs/klock/issues/79
So the question is: would it help you at this point to expose a variant of the library without inline classes? Obviously all the dependencies using klock should use the same variant.
Right now, for passing dates you can use DateTimeTz that is not inline. And if you need another one, I can create a non-inline wrapper so you can use both and use the wrapper version to interop with swift.

So the question is: would it help you at this point to expose a variant of the library without inline classes?

Unfortunately I am in the middle of implementing a page that is all about dates and am having to work around it. So unless it is available like this week I will already have it worked around.
What I am ending up doing is using extension methods in my iOS Kotlin code that wraps the existing methods to e.g. take year, month, day parameters instead of a Date and similar tactics.

I have decided to not publish separate artifacts. I have created a wrapped package with all the inline classes prefixed with W (Wrapped). This should play nice with interoperability and serialization, and you can wrap with .wrapped and unwrap with .value at any time. Going to release this so you can use it in the case you still want this.
I have marked it as experimental warning for now in the case I have to change something after people try this out.

Once the deploy is completed you can find this stuff in 1.11.0:
https://github.com/korlibs/klock/commit/088119e824fedc11172e4a7afabe4376ae0f1059

Am I interpreting this issue the wrong way, or should WDateTime be translated to a DateTime in Swift?
Because what is happening is that WDateTime is still being translated to Double on Swift.
Should this be still happening after 1.11.0 ?


Logitech MX Master 3S constantly loses pairing since bluez: 5.76 -> 5.78

Describe the bug
I keep having to repair my mouse every few hours since https://github.com/NixOS/nixpkgs/pull/341994 was merged
Steps To Reproduce
Steps to reproduce the behavior:

Update to unstable
After a few hours your mouse doesn't work anymore

Expected behavior
Mouse works
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers

Metadata

Add a :+1: reaction to issues you find important.

Switching from linuxPackages_latest to linuxPackages fixed the issue for me


Add ability to select path segments using Python re regexprs;  follow on to PR#146

Hi,  this is a follow-on of my previous PR (#146) on same subject; apparently it was simpler for me to use a different branch.
This has run Action https://github.com/AlainLich/dpath-python/actions/runs/3684590771 in my branch AL-master4merge. I have added tests exercising this with most functions, and documented in README.rst
All details are in the list of commits, including documentation, tests,...
I hope this suits your needs, let me know if there are still issues for merging in the main baseline.

Hi @moomoohk

after looking at yesterday's tests, failure was apparently caused by lack of support for typing.Protocol, which implements https://peps.python.org/pep-0544/ , because pypy's version was older than the one I have been using.

I am preparing an improved version that supports both PEP-544 compliant and ignorant compilers, with a little bit more work for the user in the latter case.

Apparently most of the work TBD is in the testing, so don't expect a revised version before next week-end.

Hi Alain,
I've cleared enough from the backlog and now I'd like to focus on your PR.
After reviewing the changes you've made it's clear a lot of work has been put in and that's much appreciated.
That said, I feel that a lot of the changes included aren't within the scope of the feature addition you're proposing.
If the core functionality (adding regexes to paths) works well enough then I'd like to restructure this PR. I hope that's ok with you!
Perhaps the other changes can be considered separately.
Thanks.

Hi,
a) I will be pushing a version that cleans up the functionality you
probably are not interested in (using a class or a function to define
matching).
b) doing this, I have cleared the issues with running on (slightly) older
versions of the Python or Pypy (which was more difficult/surprising).
c) having a lot of tests helped, especially because the type
identification for instances is subtle.
So you should probably start with this forthcoming version, to clean up
and see what  you want to keep.
For me, it is OK that you keep only the functionality you are interested
in.
( Personally, I got interested in the example with Levenshtein
approximate matching, when it seemed clear that this would be such a small
change)
Looking forwards to reading you
Le mar. 10 janv. 2023 à 21:51, moomoohk @.***> a écrit :

Hi Alain,
I've cleared enough from the backlog and now I'd like to focus on your PR.
After reviewing the changes you've made it's clear a lot of work has been
put in and that's much appreciated.
That said, I feel that a lot of the changes included aren't within the
scope of the feature addition you're proposing.
If the core functionality (adding regexes to paths) works well enough then
I'd like to restructure this PR. I hope that's ok with you!
Perhaps the other changes can be considered separately.
Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/dpath-maintainers/dpath-python/pull/177#issuecomment-1377831824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACWFOIQCUDDT25O7WUHZQI3WRXDUHANCNFSM6AAAAAAS5CSIO4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi @moomoohk,
After thinking about it, I think it will be simpler for you if I committed:
a) a simplified version with only re regexp in the branch linked to the PR.
This will keep only that functionality plus workarounds for working Pypy if
required.
b) another full featured version in a new branch, which includes what I
have now and can be readied for a PR after some testing in Github's
containers
This plan should be simpler for you, since I know what I put in!
Have a good day !😀
Le mar. 10 janv. 2023 à 22:35, Alain Lichnewsky @.***>
a écrit :

Hi,
a) I will be pushing a version that cleans up the functionality you
probably are not interested in (using a class or a function to define
matching).
b) doing this, I have cleared the issues with running on (slightly) older
versions of the Python or Pypy (which was more difficult/surprising).
c) having a lot of tests helped, especially because the type
identification for instances is subtle.
So you should probably start with this forthcoming version, to clean up
and see what  you want to keep.
For me, it is OK that you keep only the functionality you are interested
in.
( Personally, I got interested in the example with Levenshtein
approximate matching, when it seemed clear that this would be such a small
change)
Looking forwards to reading you
Le mar. 10 janv. 2023 à 21:51, moomoohk @.***> a
écrit :

Hi Alain,
I've cleared enough from the backlog and now I'd like to focus on your PR.
After reviewing the changes you've made it's clear a lot of work has been
put in and that's much appreciated.
That said, I feel that a lot of the changes included aren't within the
scope of the feature addition you're proposing.
If the core functionality (adding regexes to paths) works well enough
then I'd like to restructure this PR. I hope that's ok with you!
Perhaps the other changes can be considered separately.
Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/dpath-maintainers/dpath-python/pull/177#issuecomment-1377831824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACWFOIQCUDDT25O7WUHZQI3WRXDUHANCNFSM6AAAAAAS5CSIO4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi @moomoohk
a) this is fine, do you expect me to do anything?
b) while you are on this, could you make your workflow "deploy" dependent on your user name; the way things are set up now, each time I pull master for synchronising (and if the version has changed), it launches (under my name) and
fails as it should... and I get some spurious mail. ( https://github.com/AlainLich/dpath-python/actions/runs/3900678773)
Something like the following should work (not tried):
deploy:
   ...
    # Check that this only occurs on maintainer repo
    if: ${{ github.actor == "dpath-maintainers" }}

Have a good day :-)

Hi Alain

Hi @moomoohk
a) this is fine, do you expect me to do anything? b) while you are on this, could you make your workflow "deploy" dependent on your user name; the way things are set up now, each time I pull master for synchronising (and if the version has changed), it launches (under my name) and fails as it should... and I get some spurious mail. ( https://github.com/AlainLich/dpath-python/actions/runs/3900678773)
Something like the following should work (not tried):
deploy:
   ...
    # Check that this only occurs on maintainer repo
    if: ${{ github.actor == "dpath-maintainers" }}

Have a good day :-)

Hi Alain,
I might have some time to go through your changes over the next few days.
I would much appreciate if you could open a separate PR/restructure this one to include the necessary changes for your proposed features.
I'll be glad to review miscellaneous infrastructure changes in a separate PR.
As it stands, the miscellaneous changes are blocking your feature.
Thanks and regards

Hi @moomoohk,
I will try to look into this before the end of next week-end. I will send you a few questions about what to keep in the mean time. Will keep the bare minimum for the feature to work, and for tests, and prepare a PR based on current master commit.
For now:
a) do you want to always enable the feature ? to allow enabling/disablig by DPATH_ACCEPT_RE_REGEXP  ?
b) I will review tests I have added for their usefulness
Regards

Hi @moomoohk
following your remarks, I submitted PR #186 as replacement for this one, with only required changes.  This PR #177 can be closed.
You were right to spot not needed stuff, some that can be assumed for Python >= 3.7, others that were left from my exercise with duck-typed generalization.
Regards
Alain

May we close this PR for the time being?


jenkinsslave: .gitconfig needs to be created

When run for the first time, the task fails with
fatal: [web-qa-staging.openmicroscopy.org]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_args": {"dest": "/home/hudson/.gitconfig", "group": "hudson", "owner": "hudson", "src": "gitconfig.j2"}, "module_name": "template"}, "msg": "file (/home/hudson/.gitconfig) is absent, cannot continue", "path": "/home/hudson/.gitconfig", "state": "absent"}

This was fixed by running ansible from tag v2.0.0-0.4.beta2


Editor keep scene collision when switching to bg without collision

Only keeps if it's the same width, and if there's no other collision currently for that background.

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?
Feature / bug fix

What is the current behavior? (You can also link to an open issue here)
When you change the background of a scene containing collision, it destroys the current collision and either copies collision if a scene with that background has some, or clears it.

What is the new behavior (if this is a feature change)?
If you change the background of a scene to one that has not been used yet, and is the same width, it will keep your current collision.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
The original method takes priority, if it finds a scene it can copy collision from, it will.
If the scene is taller, it will work fine, if the scene is shorter, it will split/crop the collision array to size.
If the width changes, it will clear the collision (unless there's a background in use with collision to steal).

Other information:
This was asked for on discord, and when i had the issue and found how frustrating it was, decided to fix it.
It took me an hour or more just to find where background switching happened...

Works great, thanks @RichardULZ


Possible Memory leak

The memory consumption by Dataset GPUEnabler API increases on every invocation. This is prominent while running the provided sample program SparkDSLR.scala (logistic regression) on a million samples with 400 features for more iterations. Finally the program will abruptly stop with java stack and GC details.
This problem is not seen with RDD GpuEnabler APIs.

Heap
 PSYoungGen      total 6171648K, used 475205K [0x00003ffbb0000000, 0x00003ffd4ec00000, 0x00003fff70000000)
  eden space 6135808K, 7% used [0x00003ffbb0000000,0x00003ffbcd011728,0x00003ffd26800000)
  from space 35840K, 0% used [0x00003ffd4c900000,0x00003ffd4c900000,0x00003ffd4ec00000)
  to   space 248320K, 0% used [0x00003ffd30700000,0x00003ffd30700000,0x00003ffd3f980000)
 ParOldGen       total 12095488K, used 11796920K [0x00003ff430000000, 0x00003ff712400000, 0x00003ffbb0000000)
  object space 12095488K, 97% used [0x00003ff430000000,0x00003ff70006e0d0,0x00003ff712400000)
 Metaspace       used 64478K, capacity 65163K, committed 66816K, reserved 67584K

The above patch addresses the issue.


[BUG] All tailwind classes are marked as out-of-order

Describe the bug
Even after linting & fixing all tailwind class order, they are all linted as "warning" by vscode eslint language service.
Expected behavior
No lint error should be shown.
Screenshots

$ npx prettier --check libs/ui-kit/form-blocks/src/lib/components/input-checkbox/input-checkbox.component.html
Checking formatting...
All matched files use Prettier code style!

Environment (please complete the following information):

OS: Linux Fedora
Softwares + version used:

vscode 1.63.2
Node 14.17.0
Nx 13.7.1

Additional context
Nx & Angular.
Also using "extends": ["prettier"], in my eslint config.
I understand from this issue that the root cause might be identified? https://github.com/tailwindlabs/prettier-plugin-tailwindcss/issues/31
Posting it here though, in case it needs to be tracked (or I'm mistaken).

Actually no, removing https://github.com/tailwindlabs/prettier-plugin-tailwindcss does not interfere, I have mixed up things in my head.

Hi @qortex,
If you want to use both eslint-plugin-tailwindcss and prettier-plugin-tailwindcss you must disable "tailwindcss/classnames-order" rule because both plugin use a different ordering system.
in your .eslintrc file:
    "tailwindcss/classnames-order": "off",

Aw ok makes sense, thanks.
(Tried that actually but put it in the *.ts rules so it didn't have any effect -_- )


Emby has runtime dependancy on FFmpeg

Issue description
Emby uses ffmpeg for transcoding media and for generating thumbnails. Emby fails to find the FFmpeg binary during the setup wizard but /run/current-system/sw/bin/ffmpeg can be specified manually if FFmpeg has been installed separately.
Steps to reproduce
Add emby.enable = true to /etc/nixos/configuration.nix, browse to localhost:8096, and advance through the wizard.
Technical details

System: 17.03pre92039.adfcc2d (Gorilla)
Nix version:nix-env (Nix) 1.11.4
Nixpkgs version: 17.03pre92039.adfcc2d

cc @fadenb

Funny thing is that I was just watching a movie when I was mentioned on a system without any ffmpeg/ffprobe binary. My system was upgraded from an older version (config was already existing so no check was done by the wizard).
I was able to reproduce the issue. Will take a more detailed look at it sometime tomorrow :)


Questions about the radiance field color loss

Excellent work! Here is my question:
Is the radiance field color (computing by volume rendering) uesd as the indirect lighting, same as the radiance field color used in the loss   L_RF? If so, Why does the indirect lighting need to be consistent with GT color?
I apologize for the possible error in my understanding. Looking forward to your answer and thank you for your excellent work!

I am not affiliated to or involved in the research of this repo but if that helps I can share my understanding of the method.
The radiance color obtained from vanilla TensoRF is used as guidance for learning the volume rendering and geometry of the scene (it benefits from a 10k steps warmup at which point the brdf rendering is not yet trained). After this point, both radiance and physics-based renderings are supervised eq 11 in parallel. Keep in mind l_PB loss is kept with a lower weight than l_RF. The motivation behind using radiance for 2nd bounce ray marching is that it's cheap to query the tensoRF.
So in other words: radiance is not originally made for 2nd bounce, it is needed to train the brdf which is more ambiguous to train alone. They leverage the predicted radiance to obtain an efficient way to compute indirect light.

The radiance field constructed from the input GT images provides information for the indirect lighting, i.e. the indirect light from one particular direction observed at one particular position should be aligned with the radiance color observed. Therefore, directly querying the radiance field from the incident lighting direction and using the results as the indirect light from that direction can avoid the costly multi-bounce ray tracing computing process.


Fix a faulty setState call when container could be unmounted in future

Hello, we have been using this great library but there is a issue when you use HeaderImageScrollView inside a View that also has onLayout callback attached then rotating the device will cause the error to come up in React-Native warning box stating that setState can't be used on unmounted component.
This is happening because:
onContainerLayout = () => {
    if (!this.container) {
      return;
    }
    this.container.measureInWindow((x, y) => this.setState(() => ({ pageY: y })));
};

The actual callback with this.setState call might indeed happen when the component is unmounted.
Therefore I have added additional guard inside that callback to make sure that  setState won't fire if container does not exist anymore.

Thanks for you contribution :-)

Thank you for merging :+1:
Are you planning to release new version any time soon? I would love to switch to a official npm distribution in my package.json instead of using my forked github repo :)


Fix hyperlink

In README.md, simplesamlphp link is broken. This pull-request fixes it.

Thanks very much!


NSF NCAR branding updates

Changes to align with the new NSF NCAR branding guidelines and some fixes of broken links along the way.
Closes #272.

Good finds! Thanks for doing this @kafitzgerald


Forcing to set ACCESS_BACKGROUND_LOCATION

Expected behavior
I am using version ^6.2.1 , My app needs location in foreground , and NOT in background ,but app run in android studio errors like this ,

/Users/sajansj/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/geolocator-6.2.1/android/src/main/java/com/baseflow/geolocator/permission/PermissionManager.java:48: error: cannot find symbol
if (Build.VERSION.SDK_INT < Build.VERSION_CODES.Q) {
^
symbol:   variable Q
location: class VERSION_CODES
/Users/sajansj/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/geolocator-6.2.1/android/src/main/java/com/baseflow/geolocator/permission/PermissionManager.java:54: error: cannot find symbol
context, Manifest.permission.ACCESS_BACKGROUND_LOCATION);
^
symbol:   variable ACCESS_BACKGROUND_LOCATION
location: class permission
/Users/sajansj/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/geolocator-6.2.1/android/src/main/java/com/baseflow/geolocator/permission/PermissionManager.java:60: error: cannot find symbol
ContextCompat.checkSelfPermission(context, Manifest.permission.ACCESS_BACKGROUND_LOCATION);
Configuration
Already set foreground settings in manifest
uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"
uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"
Flutter doctor
[✓] Flutter (Channel stable, 2.0.3, on macOS 11.2.3 20D91 darwin-x64, locale en-IN)
• Flutter version 2.0.3 at /Users/sajansj/Developer/flutter
• Framework revision 4d7946a68d (2 weeks ago), 2021-03-18 17:24:33 -0700
• Engine revision 3459eb2436
• Dart version 2.12.2
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/sajansj/Library/Android/sdk
• Platform android-30, build-tools 30.0.3
• ANDROID_HOME = /Users/sajansj/Library/Android/sdk
• ANDROID_SDK_ROOT = /Users/sajansj/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.4, Build version 12D4e
• CocoaPods version 1.10.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
[✓] Connected device (2 available)
• sdk gphone x86 arm (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
• Chrome (web)                • chrome        • web-javascript • Google Chrome 89.0.4389.114
• No issues found!
Version: 6.2.1
Platform:

[x] :iphone: iOS
[x] :robot: Android

I have found a workaround for this , I had to edit the PermissionManager.java located at
ios/.symlinks/plugins/geolocator/android/src/main/java/com/baseflow/geolocator/permission/PermissionManager.java
Since I never used background location I had to edit the file for commenting out the logics on ACCESS_BACKGROUND_LOCATION in the above file
This link gave me the idea
https://github.com/permissions-dispatcher/PermissionsDispatcher/pull/679#issue-456238328

@sajanyamaha this issue probably occurs because your App targets Android API 28 or below.
You can resolve this issue by setting the targetSdkVersion in you android/build.gradle file to 29 or higher.
The Build.VERSION_CODES.Q and Manifest.permission.ACCESS_BACKGROUND_LOCATION enum values are only available from Android Q (API 29). There is no need to remove any code.


Improve test coverage from 70%

~61%~~64%~70%
Remaining:
lucid/optvis/transform.py                        74     57    23%
lucid/optvis/objectives.py                      203    133    34%
lucid/optvis/param/lowres.py                     23     12    48%
lucid/misc/environment.py                        14      7    50%
lucid/misc/io/showing.py                         47     17    64%
lucid/optvis/render.py                           90     22    76%
lucid/optvis/param/spatial.py                    37      8    78%
lucid/misc/io/saving.py                          41      7    83%
lucid/misc/io/serialize_array.py                 47      8    83%
lucid/misc/io/reading.py                         58      9    84%
lucid/optvis/param/resize_bilinear_nd.py         37      6    84%
lucid/misc/channel_reducer.py                    26      3    88%
lucid/optvis/param/images.py                     17      2    88%
lucid/misc/io/writing.py                         29      3    90%
lucid/optvis/param/color.py                      21      2    90%
lucid/misc/gradient_override.py                  36      3    92%
lucid/modelzoo/vision_base.py                    30      1    97%
lucid/misc/io/loading.py                         46      1    98%

Continuously tracked via coveralls from now on. Per-file statistics can be viewed by clicking the badge.


Fix bugs with express-angular-bootstrap rock

@jprichardson What's the issue here?

I don't remember - was three years ago :( I'll just close it.


[Feature Request] Honors Configuration

Background
In the earlier unreleased version, we had a space for FastTrack, future plans, and an honors designation. However, beta does not include this honors section.
Overview
The honors population at UTD is significant, and their requirements/goals for using Nebula may differ slightly from non-honors users. Listed some off top of my head below:

Using Nebula to determine their fulfillment of Proper/Advanced Hours
Mapping out the omission of a semester to study abroad/other programs offered in CV (e.g. Archer)
Minimum hours per semester (e.g. NM/CS^2 req. 15 hour minimum vs. 12 minimum for normal full-time UTD definition).

Proposal
Pt 1
Include an honors designation upon onboarding (specification of which honors is not as relevant for now; in the future can look to shape/recommend plans based on particular honors programs sure, but not now). This way, honors reading courses + honor proper/advanced hours (+ honor section professors, if we want to get into that level of specificity) can be accessible solely to honors users vs. potentially confuse non-honors users.
Implementation: In on-boarding, could simply be a Yes/No question (or list w/ different honors specifications in the future) declaring, "Are you a CollegiumV member?" [Drop down: Yes ; No].
Pt 2
Option 1. Have an "Honors Hours" counter. Either cumulative on a total "4-yr plan requirements post-it-note" type section on the screen. Would be another drop down on Post-It Requirements (potential courses would ideally be prioritized by relevance to major plan) #313 .
OR
Option 2. Assuming the student chose the Honors designation upon on-boarding, with each semester, spatially left to the # of total semester credit hours (SCH) they took, can there be a green/contrasting label of "X Honors Hrs." Which will not show by default; only when an honors course is recognized within the semester.
Supplementary Information
Additionally, most of these honors students will have credits coming in, so the current templates may also be excessive and energetically unattractive to them since they'll have to reconfigure them to their personal needs, which almost entirely nullifies the value of using a template in the first place. I'll provide a proposal for another template format in a future issue.

Good idea; will revisit at a later date!


arch/xtensa: Fix return context for nested interupts

The xtensa interrupt return path was forgetting to check the nested interrupt state and calling into the scheduler to select the context to which to return, which of course is completely wrong.  We MUST return to the ISR we interrupted.
In fact in practice this was only visible in the case of a nested interrupt that causes a context switch, otherwise the "interrupted" argument just gets returned and things work.  In particular, it can happen when the nested context is a fatal exception that aborts the current thread, which is how this was discovered.  The timing required to see this on live interrupts on real applications is likely to have been extremely difficult to detect.

Fix for the nested interrupt return bug.  Took a little puzzling to figure out how to write a test case for this, but I had a cute idea that works (even on qemu) and shows the problem.  Classic bisection cycle though: people will just have to take me on faith that the test in the SECOND patch here does indeed fail on xtensa (it blows up and times out) and that it's fixed by the FIRST.  Either that or pull it apart and hand-verify.

Should unblock #45570 though, please try

(And this is a good candidate for backporting, once merged.  Frequency is likely to be very low in real apps but severity is quite high.)

Thanks for solving this issue, I mentioned the issue I had last time. https://github.com/zephyrproject-rtos/zephyr/issues/40946


Returning a struct instead of Vec

Returning a simple struct with an internal and an external field instead of a Vec with two fields in various functions.

done in https://github.com/RCasatta/electrum2descriptors/commit/b491f6c2e0bc9214b73dc70438130643d377f094


Time to remove LISP, overlay, and underlay docs and names

A long time ago we had integrated LISP secure overlay network code, and as a result zedrouter had functions and variables named "underlay*" or "ul*".
I noticed we still have some text left in SECURITY.md so I did a pass over the code.
Note that there are several commits with different potential for merge conflicts with existing work; the "underlay" commit with "ul*"  renames is the one most likely to cause such issues. Note that the Underlay struct is renamed to AppNetAdapter{Config,Status} but I'm open to other name suggestions.
The underlay term still remains for the geolocation code and API, but added comments explaining that this is the underlay/public IP address.
Let me know if this is a good time to do this cleanup or if it will cause conflicts with ongoing network work and should be deferred.

I think we can go ahead with this - I will rebase https://github.com/lf-edge/eve/pull/3513 and fix merge conflicts once this is merged.

Note that some workflows are currently failing because of this issue: https://github.com/golang/go/issues/63684


Ancient Beast turn based strategy game

My main game should make the list as well -> https://github.com/FreezingMoon/AncientBeast
There's a PR opened for 2 months now, but some other game was merged in the same spot and now there's conflict -> https://github.com/bobeff/open-source-games/pull/37

My own PR for this is up, see #53