Another missing error in users.admin.invite

I just got a already_in_team_invited_user error from users.admin.invite which sounds really strange, like what does this even mean...?
The user shows up as a "Full Member" on the Slack admin. So I guess it's more similar to already_in_team error.

thanks for reporting the error. I can add it, but do you have any hint what the specific reason for that error occurring could be?

I do not, unfortunately. I haven't been able to reproduce this error

ok. I will add it anyways. maybe someone else can help us find more info for it.


add scoring to html output

It will be handy to have the prowler score added to html output, not just console

Hi @HG00, the plan is to publish a template to visualize the CSV output (from one or multiple accounts assessments) in Quicksight and eventually in Kibana and Grafana.
Can you please attach a screenshot of your html output to see how it looks like? Thanks!

Templates sounds much nicer, but here is what the html scoring i made looks like - poss it can be a colored div showing a percentage?

Ok, this is the new html output since 2.4:

That looks so much nicer than what I did, thanks!

it will be merged into master coming from 2.4 branch


Add additional message parsing for a select set of gst-messages in HandleBusWatchMessage()

Want to parse the following messages to provide additional log information.  There are a few messages that may require additional action such as the  GST_MESSAGE_BUFFERING. This will be handled in a subsequent issue.
The list to parse for now is.:

GST_MESSAGE_ASYNC_DONE
GST_MESSAGE_STREAM_STATUS
GST_MESSAGE_QOS
GST_MESSAGE_BUFFERING
GST_MESSAGE_PROGRESS
GST_MESSAGE_INFO
GST_MESSAGE_WARNING

Merged into the v0.27.alpha branch


How to get all the answers that have been made to an account?

I am trying to get the tweets replies that a account gots from users.
But I don't know what the command to get it is. I have tried it using the collect every Tweet containing name of account from everyone's Tweets, in order to get the replies. But the problem is that not only do they get me the answers, they also get me the tweets with their mentions. How can I get the replies tweets that an account has received?
I use twint from the cmd (command prompt), therefore I have used this command to get the replies that this account (meridaalcaldia) has received in a certain period of time:
twint -s @meridaalcaldia --since "2020-01-01 00:04:01" --until "2020-07-01 00:05:01" -o merida.csv --csv
can you help me please?
Thank you!

  --to USERNAME         Search Tweets to a user.

When I write: twint --to meridaalcaldia --since "2020-01-01 00:04:01" --until "2020-07-01 00:05:01" Twint return me this: [-] Error: Please use at least -u, -s, -g or --near
Can you help me, please?


EntityTrigger does not get triggered in version of Microsoft.Azure.Functions.Worker.Extensions.DurableTask 1.1.3

There is an issue in version 1.1.3 that prevents triggering EntityTrigger. I have been calling SignalEntityAsync and CallEntityAsync and none of them ever reached the entity. When I downgraded the package to 1.1.1 it started working.
Here is the repository for reference and testing if you wish.
https://github.com/netsharpdev/g9-durable/

Could this also cause my locks to never be entered anymore? Worked with 1.1.2 .
var entityLock = new EntityInstanceId("SomeLock", somekey);
await using (await context.Entities.LockEntitiesAsync(entityLock))
{
...
}

@netsharpdev, @th3ragex: do y'all have minimal repros you could share?
@netsharpdev: I looked at your repro but it seemed a bit complex, so I'm curious if there's a more minimal version of it that demonstrates the problem. I'm not able to reproduce this with a "hello world"-level entity app

@davidmrdavid Sure, minimal repo with LockEntitiesAsync demo: https://github.com/th3ragex/durabletask-dotnet-bug-315 (Currently with 1.1.2 which works, after update to 1.1.3 and a proper rebuild it's stuck)

@davidmrdavid, I tried the repro and it also worked for me after upgrading the .NET isolated extension version to 1.1.3.

Thanks for confirming. @th3ragex: When using 1.1.3 and a brand new taskhub name, does it still fail for you? Since it works for @bachuv and myself, I wonder if the reason for your lock's "stuckness" is that there's some actual deadlock in your storage account, not sure. A brand new task hub should help validate that theory.

@davidmrdavid thank for taking your time and testing

When using 1.1.3 and a brand new taskhub name, does it still fail for you?
yes, I have also tested with azurite local storage and a gen2 azure storage with new task hub names. I am testing locally with the VS debugger attached, didn't try how it behaves as deployed azure function. I have also updated my machine to the latest azure function host and VS version.

After playing with my sample code a bit I discovered that building the function after upgrading to the new nuget version occasionally didn't use the new assembly version. I have changed my code  to return the loaded assembly version to make it clear.
Sorry to bother you, could you please update and try my repo again and double check that your test run actually used 1.1.3?

We just made a hotfix release: https://github.com/microsoft/durabletask-dotnet/releases/tag/v1.2.4. Is this issue persisting for you all with this release?
@nytian

We just made a hotfix release: https://github.com/microsoft/durabletask-dotnet/releases/tag/v1.2.4. Is this issue persisting for you all with this release?
cc/ @nytian

@davidmrdavid
Confirmed resolved for me.

@davidmrdavid works for me too, thanks!

@davidmrdavid locking works now. Thank you!

Closing this issue as it is resolved in hotfix release durabletask-dotnet v1.2.4.


⚠ Anthelion has degraded performance

In 092171b, Anthelion ($ATH) experienced degraded performance:

HTTP code: 200
Response time: 3121 ms

Resolved: Anthelion performance has improved in f54e00e after 410 days, 19 hours, 59 minutes.


Login failing - ECONNREFUSED

Attempting login with known working credentials results in ECONNREFUSED
"code": "ECONNREFUSED",
"errno": "ECONNREFUSED",
"syscall": "connect"

Probably a duplicate of #102.  ping-pong.spotify.nodestuff.net appears down.  Time to learn how to run my own.

got the same problem. how do you fixed it?
Running the ping pong server locally (https://github.com/1994rstefan/Spotify-Ping-Pong-API) didn't worked


fix: lottie and svg not show after switching from Inbox to Settings

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/47041
PROPOSAL: https://github.com/Expensify/App/issues/47041#issuecomment-2294923394
Tests

Go to Settings
Go to any page with animated illustration (Preferences/Security/Troubleshoot/About/Save the world)
Go to Inbox
Go to Settings

Verify that the user avatar and the animated illustration shows

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Go to Settings
Go to any page with animated illustration (Preferences/Security/Troubleshoot/About/Save the world)
Go to Inbox
Go to Settings

Verify that the user avatar and the animated illustration shows

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/47c95821-5b14-479e-abb5-285aa16fa04d

Android: mWeb Chrome

https://github.com/user-attachments/assets/ff358b32-1195-4b31-814e-850ae225d3c6

iOS: Native

https://github.com/user-attachments/assets/f57cab34-7db3-43b0-aa03-f2635cded33c

iOS: mWeb Safari

https://github.com/user-attachments/assets/8944efd1-46cb-49fd-98b6-bd66c6ac3bbf

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/a90c07e1-cdbd-41c2-abff-5ea4c3639e98

MacOS: Desktop

https://github.com/user-attachments/assets/7788d6c5-b6ee-4529-9ac6-f6e3b5b2a0c2

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.0.37-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/grgia in version: 9.0.38-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Cannot parse argument of type None

My tconnectsync was working fine until i did a split bolus for 75% now and 25% later over 2 hours...30 min in i decided to cancel the rest of the bolus.  here is the verbose output for the command prompt (i am running using docker on windows 10)
DEBUG:root:Set logging level to DEBUG INFO:tconnectsync.process:Downloading t:connect ControlIQ data Processing data between 2021-07-08 07:09:01.450854 and 2021-07-09 07:09:01.450854 DEBUG:tconnectsync.api:Instantiating new ControlIQApi INFO:tconnectsync.api.controliq:Logging in to ControlIQApi... DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): tconnect.tandemdiabetes.com:443 DEBUG:urllib3.connectionpool:https://tconnect.tandemdiabetes.com:443 "GET /login.aspx?ReturnUrl=%2F HTTP/1.1" 200 33507 DEBUG:urllib3.connectionpool:https://tconnect.tandemdiabetes.com:443 "POST /login.aspx?ReturnUrl=%2F HTTP/1.1" 302 148 DEBUG:urllib3.connectionpool:https://tconnect.tandemdiabetes.com:443 "POST /CookieCheck.aspx?ReturnUrl=%2F HTTP/1.1" 302 118 DEBUG:urllib3.connectionpool:https://tconnect.tandemdiabetes.com:443 "GET / HTTP/1.1" 200 167543 INFO:tconnectsync.api.controliq:Logged in to ControlIQApi successfully (expiration: 2021-07-09T15:09:02.176Z, in 7 hours, 59 minutes) DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): tdcservices.tandemdiabetes.com:443 DEBUG:urllib3.connectionpool:https://tdcservices.tandemdiabetes.com:443 "GET /tconnect/controliq/api/therapytimeline/users/c6dfafb2-1dc0-47b4-9209-a985d311cf62?startDate=07-08-2021&endDate=07-09-2021 HTTP/1.1" 200 2049 INFO:tconnectsync.process:Downloading t:connect CSV data DEBUG:tconnectsync.api:Instantiating new WS2Api DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): tconnectws2.tandemdiabetes.com:443 DEBUG:urllib3.connectionpool:https://tconnectws2.tandemdiabetes.com:443 "GET /therapytimeline2csv/c6dfafb2-1dc0-47b4-9209-a985d311cf62/07-08-2021/07-09-2021?format=csv HTTP/1.1" 200 32835 DEBUG:tconnectsync.process:{'DeviceType': 't:slim X2 Insulin Pump', 'SerialNumber': '****** [tt-08072021_074258.xlsx](https://github.com/jwoglom/tconnectsync/files/6789493/tt-08072021_074258.xlsx) [tt-08072021_074258.xlsx](https://github.com/jwoglom/tconnectsync/files/6789495/tt-08072021_074258.xlsx) ', 'Description': 'EGV', 'EventDateTime': '2021-07-08T23:30:47', 'Readings (CGM / BGM)': '116'} INFO:tconnectsync.process:Last CGM reading from t:connect: 2021-07-08T23:30:47-06:00 (1 hours, 38 minutes ago) DEBUG:tconnectsync.process:No CSV basal data found DEBUG:tconnectsync.sync.basal:ns_write_basal_events: querying for last uploaded entry DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): n1ghtsc0ut.herokuapp.com:443 DEBUG:urllib3.connectionpool:https://n1ghtsc0ut.herokuapp.com:443 "GET /api/v1/treatments?count=1&find%5BenteredBy%5D=Pump%20%28tconnectsync%29&find%5BeventType%5D=Temp%20Basal&ts=1625814557.7124944 HTTP/1.1" 200 269 INFO:tconnectsync.sync.basal:Last Nightscout basal upload: 2021-07-09T07:02:11+00:00 DEBUG:tconnectsync.sync.basal:ns_write_basal_events: added 0 events DEBUG:tconnectsync.sync.bolus:ns_write_bolus_events: querying for last uploaded entry DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): n1ghtsc0ut.herokuapp.com:443 DEBUG:urllib3.connectionpool:https://n1ghtsc0ut.herokuapp.com:443 "GET /api/v1/treatments?count=1&find%5BenteredBy%5D=Pump%20%28tconnectsync%29&find%5BeventType%5D=Combo%20Bolus&ts=1625814558.1518533 HTTP/1.1" 200 198 INFO:tconnectsync.sync.bolus:Last Nightscout bolus upload: 2021-07-09T01:19:45+00:00 Traceback (most recent call last):   File "/home/appuser/main.py", line 77, in <module>     main()   File "/home/appuser/main.py", line 73, in main     added = process_time_range(tconnect, nightscout, time_start, time_end, args.pretend)   File "/home/appuser/tconnectsync/process.py", line 72, in process_time_range     added += ns_write_bolus_events(nightscout, bolusEvents, pretend=pretend)   File "/home/appuser/tconnectsync/sync/bolus.py", line 46, in ns_write_bolus_events     if last_upload_time and arrow.get(event["completion_time"]) <= last_upload_time:   File "/.venv/lib/python3.9/site-packages/arrow/api.py", line 80, in get     return _factory.get(*args, **kwargs)   File "/.venv/lib/python3.9/site-packages/arrow/factory.py", line 228, in get     raise TypeError("Cannot parse argument of type None.") TypeError: Cannot parse argument of type None.
I also attached my csv, the last entry is the extended bolus that i canceled.  Since this error no boluses have been uploaded to my nightscout.

tt-08072021_074258.xlsx

Thanks for the bug report! I just pushed a new commit which should contain a hotfix for this specific error. Might take about an hour for the docker images to be regenerated if you are using those.
Medium-term, I'm hoping to add end-to-end tests to catch things like this earlier. Extended boluses and cancelled boluses are two specific scenarios which come to mind where the Tandem API returns data in a slightly different form than normal which hasn't been fully tested -- coincidentally your situation here encompassed both of those :)
Let me know if this fixes the problem and if so I'll close the issue.

That solved the issue.  Thanks for the quick update!


Syntax error: Unknown word (39:93) while importing zuck.css locally

I got an error while importing zuck.css from node_modules using @import "~zuck.js/zuck.css"; in create-react-app . Here is the snippet of the code that I think produces the error :
#zuck-modal {     outline: 0!important;     overflow: hidden;      position: fixed;     background: rgba(0, 0, 0, 0.75);     0;     z-index: 100000;     font-size: 14px;     font-family: inherit; }
Thank you.

Hey,
I think you should remove "!important" to make this work here

I removed the 0; before the z-index and it finally works, thanks

Good catch, hahaha
Pure CSS simply ignores errors like this... When I update the code I'll fix this typo too.


Binding warnings in container output

Unable to run Mixcore as docker container. There is binding warnings in container output.
warn: Microsoft.AspNetCore.Server.Kestrel[0]
Unable to bind to http://localhost:5000 on the IPv6 loopback interface: 'Cannot assign requested address'.
warn: Microsoft.AspNetCore.Server.Kestrel[0]
Unable to bind to https://localhost:5001 on the IPv6 loopback interface: 'Cannot assign requested address'.
To Reproduce
Open terminal and run following commands:
docker pull mixcore/mix.core:latest
docker run -it --rm -p 5000:80 --name mixcore_cms mixcore/mix.core:latest
OS: Mac OS Monterey 12.0.1

@mrtasci could you help check again to see if there is any other app that already run with 5000/5001 ports?

@mrtasci I just tried from my side and it is fine. Please try again with the latest docker image from master.

@Smilefounder I can see same warning in your screen shot. Are you able to browse the site by http://localhost:5000?

@mrtasci we have updated the docker file to make it work properly. However, the Docker HUB (free package) can not sync the latest dockerfile at the moment.

Hi @mrtasci , you can try this
docker run -it --rm -p <IP_ADDRESS>:5000:80 --name mixcore_cms -e ASPNETCORE_URLS=http://+:80 mixcore/mix.core:latest

@nhathoang989  I just tried with the command you mentioned. It seems it started properly but I am not able to browse site by http://<IP_ADDRESS>:5000
There is a runtime error. I got HTTP 500 from http://<IP_ADDRESS>:5000/init page.

@mrtasci could you also help to try with docker IP?

There is a problem with razor while updating to Net 6. The views.dll file is now missing.
Please try again after updating mixcore/mix.core:latest.

@nhathoang989 It worked now with latest image and below command. I am able to browse the site by http://localhost:5000/ . Thank you!
docker run -it --rm -p 5000:80 --name mixcore_cms -e ASPNETCORE_URLS=http://+:80 mixcore/mix.core:latest


[Proposal] Consider support for Stride3d

https://www.stride3d.net/
https://github.com/stride3d/stride
In the end is another free open source engine released under the MIT license which also uses c# for scripting so it may be worth investigating as well since most of the logic won't need to be translated only the engine specific calls.
I really think there's pretty much limitless potential for this engine if people actually learn about it's existence and give it a try, and since won't make people learn a new programming language it may even be more comfortable to some users.
Doesn't matter if you decide to try adding support or no, i want to thank you in advice anyways for your time doing this project.

Stride seems really good! I've considered using it for some of my games a while back but I haven't been able to run it on my own machine due to some weird dotnet error.
Currently we have more important tasks at hand like getting Godot conversion to a stable point and running AI models locally.
Adding very basic Stride support might not be that difficult to do; All you'd have to do is create a config file and write a bunch of detailed prompts. The difficult part would be that the AI models very likely have no clue what Stride3D or it's API look like, so a lot of manual work would have to be done trying to explain to the AI how the API works and looks.
For the actual project files and assets it probably wouldn't be that hard to translate over, and there's probably another project out there that already does that.


Xcode reports "Couldn't find Assets.car"

Since updating to Xcode 11.1 and iOS 13, (that's when I started to notice it anyway, not certain that this is the root cause) I'm seeing the following warning logged twice each time a PasswordTextField is rendered on a given iOS screen:
[framework] CoreUI: RunTimeThemeRefForBundleIdentifierAndName() couldn't find Assets.car in bundle with identifier: 'org.cocoapods.PasswordTextField'

Probably related to #27

@PiXeL16 Also as of Xcode 15 and iOS 17 this issue is not occuring so it can be closed

Thanks!


feat: Add PayPal pay function

Signed-off-by: MRGUOKING<EMAIL_ADDRESS>Add PayPal pay function
Signed-off-by: MRGUOKING<EMAIL_ADDRESS>

https://user-images.githubusercontent.com/55344330/133295284-720e2823-924b-43e5-8fd8-2e5b0c999ecc.mp4

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: hsluoyz:x: MRGUOKINGYou have signed the CLA already but the status is still pending? Let us recheck it.

Archived at: https://github.com/casdoor/casdoor/tree/doorPay , closed here


[FEATURE REQUEST]data.csv example please～

Feature Request
is there any data.csv examples for new comer? it can be only 2-3 rows, seems to be very clear
Motivation
maybe better for us to get know it
Additional Context
No response

have you checked the docs? hf.co/docs/autotrain


Multiple spark versions for breaking changes in spark submit

Suppose a user's cluster has a Spark operator bundled with version 2.3 of Spark Submit. Suppose then we introduce a breaking change in the contract between Spark Submit and the Spark application docker containers. Therefore any Spark application using Spark 2.4 needs to use Spark 2.4's spark submit, and conversely, all applications using Spark 2.3 need to use Spark 2.3's spark submit.
Unfortunately it's not easy right now to support having a single Spark operator deploying both Spark 2.3 and Spark 2.4 applications. If you upgrade the Spark operator's bundled Spark submit version to 2.4, suddenly all applications running Spark 2.3 will break.
There are multiple ways to tackle this problem. First of all, we should be ensuring that the contract between spark submit and the Spark driver it launches is stable. This has been the case for a long time with Spark on YARN.
However, we can be clever and allow for the above use case even if the above contract breaks, as follows:

Add a sparkVersion field to the spec of SpatkApplication
The Spark operator comes bundled with a certain Spark submit version that is compatible with some subset of spark versions of Spark applications
A given operator will only deploy a SparkApplication if the sparkVersion declared by that application is compatible with its bundled spark-submit version.

This allows one to implement something like a rolling upgrade strategy for Spark applications run on their cluster. As an example, a cluster administrator can install a Spark 2.4 compatible Spark operator and leave the Spark 2.3 operator running on the cluster. Once the organization has upgraded all Spark applications to Spark 2.4 and higher, the Spark 2.3 operator can be decommissioned.
Tasks:

[x] Add a new field for specifying the Spark version.
[x] Use a Kubernetes Job to run spark-submit.

Tasks:

[ ] Add a new field for specifying the Spark version.
[ ] Add an optional command-line flag for specifying the list of Spark versions supported.
[ ] Add logic for checking version match.

@liyinan926 , @mccheah
This is something of interest to us(/Lyft) as well as we are starting to use the Operator for production use-cases. We were also looking at a few potential solutions to achieve this and I can share more details. What's the current status of this: Is the story/design closed out, is this being actively worked on ?
( cc @kumare3)

No, this is not being worked on. It's great to know that you have some thoughts, and looking forward to the details.

@akhurana001 thanks for proposing the solutions!

CRD Label based Routing/Multiple Operators: This is very similar to the approach mentioned above but instead of adding spark-version as part of the CRD Spec, users/clients add a relevant spark-version label to SparkApplication CRD and we run multiple Operators one for each spark version we want to support. Each Operator will listen to SparkApplications only for the particular spark-version it supports. Additionally, the Operator is also responsible for propagating this label to any driver/executor pods it creates and listening for status update for only those pods.

This requires separating out the code for registering/updating the CRDs and carefully coordinating the creation/updating of CRDs for all instances of the operator running in a cluster. There is also an issue with applications not properly labeled. For example, SparkApplications not labeled or labeled with a version with no corresponding operator instance won't be handled.

Multiple Spark-Version within SparkOperator: In this approach, we install multiple spark-distributions within the Operator image. Each SparkApplication CRD will have a spark-version field and the Operator will consume this spark-version to create the correct spark-submit arguments and trigger the spark-submit on the correct distribution via correctly set environment variables like SPARK_HOME etc.

You summarized pretty well the issues with this solution.

Spark Submission via Kubernetes Job: In this approach, the spark-distribution the operator image will not contain the spark-distribution and spark-submit will be triggered on separate Spark-Distribution images via Kubernetes Jobs. Same as above, each SparkApplication CRD will have a spark-version field and the Operator will consume this spark-version to create the correct spark-submit arguments for the spark-version but instead of directly executing spark-submit, the Operator will create a new Kubernetes Job with the relevant spark-distribution image as the container image, spark-submit as the container entrypoint and the spark-submit arguments as the container arguments. This Job will just trigger the spark-submit on the correct distribution and exit.

One benefit of this approach is we can delegate the handling of submission retries to the Job controller. The Kubernetes Job can use the user-specified image in the SparkApplication resource. However, it has the same problem with the proposal of using a Job to run the driver pod in https://github.com/apache/spark/pull/21067. See https://github.com/kubernetes/kubernetes/issues/66620. This might not be a real issue given that the submission command should complete or fail fairly fast.

@liyinan926 as @akhurana001 explained above, Solution (3) seems promising and Solution (2) is also workable.
As explained in Solution (3), in the previous PR we made it such that Spark-Driver pod creation is idempotent. As long as the name is deterministic, we guarantee only one pod creation per SparkApplication, even if the spark-submit is invoked multiple times.
Solution (2) seems ok for a migration strategy, but seems unwieldy where the matrix of versions increases.
I think we should narrow down on the solution, as we ramp up our production traffic on the operator, we want it to be easy for the users to migrate versions, without breaking their usecases. An important thing to note is @akhurana001 is going to be out for rest of the month and I am really slammed, but can definitely help you in CodeReviews. Do you feel you can take this up? OR lets come up with a gameplan, before Anmol leaves for vacation next week, do you want to have a quick hangout?

@kumare3 @akhurana001 I like solution 3 better. Let's meet and come up with a plan before @akhurana001 leaves for vacation. Also FYI: I will be at kubecon in the week of 12/10. So maybe let's meet next week?

@liyinan926 Kubecon is in Seattle this year, I have my name in the waitlist :) (was late in registering). But, you should definitely come visit us at the Lyft Seattle office. Also, lets setup sometime next week for Tuesday 12/04 or 12/06, you can send us an invite.

@kumare3 sounds good. I will send an invite.

Multi-version support has been implemented in the branch multi-version-support.

@liyinan926 I see this has been implemented in the branch, but not sure what the status of that branch is the last commit was from July? Is this still being worked on? Has it been abandoned? If possible I am willing to help with making this land.

@stijndehaes we actually use this branch in production at Lyft and has been the way to migrate from spark 2 - spark 3. It does add the additional dependence on jobs api (which is a little brittle) but we are still happy with this change as this allows us to transparently migrate our users.
We run spark in GitHub.com/lyft/Flyte project


Feature: Now any localizations are not included in the LibrariesHash (not just custom ones)

Fixed by 006c248 commit


fix #5972

Fix now, integration test later. This first needs some additional refactoring.

For future reference it was https://github.com/mitmproxy/mitmproxy/issues/5973 not #5972


How does monosdf get the pose of tanks and temples dataset ?

Thank you for this great work, the result of tanks and temples dataset looks impressive!
Recently I tested volsdf  on this dataset , using the pose provided by colmap, but basically could not reconstruct a reasonable shape. I notice that the test datasets are also tested. How does monosdf get pose of this dataset?
Thanks for your help and looking forward to your reply

Hi, we used the preprocessed data from Vis-MVSNet which I think is originally provided by MVSNet. You can download it in Data preparation in https://github.com/jzhangbs/Vis-MVSNet

Thanks!


(chore)license: add license notice

Signed-off-by: ksatchit<EMAIL_ADDRESS>
What this PR does / why we need it:

Adds license notice files for test tools

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

There are no modified subcomponents, though they are pulled as dependencies (vendor) https://app.fossa.com/attribution/a8a6a1e8-164c-4803-a1b3-84a794765f3c


Fix drone exec identity

When using -i with drone exec, the specified key is not applied in the build container, this is caused by the two reasons:

docker-exec overrides the workspace with its own, using payload.Keys and payload.Netrc
docker-exec only adds the key to the build script if both payload.Workspace.Keys and payload.Workspace.Netrc are present, otherwise it just ignores it (link)

This pull requests fixes this by sending Keys and Netrc where docker-exec expects it and by sending an empty Netrc.
For the second issue, it serves just as a temporary fix as this behaviour seems wrong. Also, drone/drone-exec#12 seems to fix this.

Apply the comment of brad, than LGTM


Avian won't extract when enabling IOS plug in.

The avian-openjdk folder doesnt install itself when switching on the IOS plugin for the first time.

This is known. The Problem is we're currently unable to build avian ourselves, there are multiple errors and we don't have many mac guys.
You can try to build it by yourself, see the docs folder in this repo and the forums, maybe you can get it to work.

Hi
Thanks but I've tried and the instructions are not complete as I can't seem to get the components together as described and I'm not familiar enough to fill in the gaps.
Can I get hold of the 4 folders that Norman used to build it on the last version?    If I can at least build the old one it gives me a pointer to what I need for new one?
Regards
Anthony
Sent from my iPad

On 24 Apr 2016, at 20:35, MeFisto94<EMAIL_ADDRESS>wrote:
This is known. The Problem is we're currently unable to build avian ourselves, there are multiple errors and we don't have many mac guys.
You can try to build it by yourself, see the docs folder in this repo and the forums, maybe you can get it to work.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

I guess he doesn't have them anymore and the problem is for some reason we have no chance to build it anymore since we're over a threshold. You see this Linker Error happen for some Unity Guys and the only Solution seems "reducing the filesize", which won't work for an entire JDK.
You can use this to checkout everything (I had some compile errors in openJDK Code before)
wget https://bitbucket.org/alexkasko/openjdk-unofficial-builds/downloads/openjdk-1.7.0-u80-unofficial-macosx-x86_64-image.zip
unzip openjdk-1.7.0-u80-unofficial-macosx-x86_64-image.zip
hg clone http://hg.openjdk.java.net/jdk7u/jdk7u
cd jdk7u
bash get_source.sh
cd jdk/
hg checkout jdk7u80-b32
cd ../hotspot/
hg checkout jdk7u80-b32
cd ../..
git clone git@github.com:readytalk/avian
git clone git@github.com:readytalk/hello-ios

Also make sure to apply this PR https://github.com/ReadyTalk/avian/pull/480 when you have a new OS, 10.9.5 seems to be too old. (You might see missing TCP IP Header Files when it's wrong)
Then there is this (which is where I am stuck myself, but googling the error doesn't lead to a good solution):
         [exec] creating build/ios-arm-interpret-openjdk-src/classpath.jar
         [exec] creating build/ios-arm-interpret-openjdk-src/classpath-jar.o
         [exec] linking build/ios-arm-interpret-openjdk-src/avian
         [exec] ld: Unable to insert branch island. No insertion point available. for architecture armv7
         [exec] clang: error: linker command failed with exit code 1 (use -v to see invocation)
         [exec] make[1]: *** [build/ios-arm-interpret-openjdk-src/avian] Error 1
         [exec] make: *** [build/ios-arm-bootimage-openjdk-src/bootimage-generator] Error 2

Good Luck Anyway!

The latest sdk Release comes with a bundled avian again.
Everything should work as expected (apart from a guiNode Bug and that we only Support the 64bit Simulator)


add xpla

Description

Checklist

Adding Chains

If adding a new chain, please ensure the following:

[x] Chain is registered to the Cosmos Chain Registry.
Note:

Chain's registration must have staking defined, with at least one staking_token denom specified.
Chain's registration must have fees defined; at least one fee token has low, average, and high gas prices defined.

[x] Add chain to bottom of zone_chains.json
Note:

RPC and REST must not have any CORS blocking of the Osmosis domain.
RCP node must have WSS enabled.

Adding Assets

If adding a new asset, please ensure the following:

[x] Asset is registered to the Cosmos Chain Registry.

[x] Add asset to bottom of zone_assets.json.
Note:

The IBC channel referenced in path must be registered to the Chain Registry.
osmosis_main defaults to false (or else cite the listing rule that justifies enlisting to the Main app)

Validation Testing
If adding or updating a chain or asset, the changes must be validated from the updated build of the Osmosis Frontend. Please specify who shall validate:

[ ] Osmosis assetlists repo maintainers are to validate--testers will need a small amount of tokens to validate. In which case:

[ ] Validaters can buy a small amount of this asset from Pool ID: {PROVIDE POOL ID}.

OTHERWISE

[x] Submitting team are to validate--a preview link is requested in the comments of this PR. The submitting team will provide evidence of success of the Deposit and Withdraw functions from the Preview Frontend. (screenshot + tx url)

On-chain liquidity
If adding a new asset, please provide the plan for on-chain liquidity of the asset: (choose one)

[x] The submitting team will ensure a pool will be created soon. Please hold off until further communication, which will notify of the Pool ID. (Please set the PR's status to Draft until the pool has been created)

OR

[ ] A preview link is requested for the submitting team to be able to create a pool using the Osmosis Frontend.

OR

[ ] The token is, or will be, going through a StreamSwap stream; thus, the token should be listed without requiring on-chain liquidity. A Pool ID will be provided in this PR following the stream's completion once the team has had a chance to create a pool using the earned funds.

Thanks for this. Please see the checklist--there seems to be quite a bit missing

Checklist completed.

please remove the image file--we don't store those here

이미지 파일을 삭제하세요. 여기에 저장하지 않습니다.

sorry, deleted.

Can you please add gas rates to the Chain Registry here, as noted in the description template:
"Chain's registration must have fees defined; at least one fee token has low, average, and high gas prices defined."

add gas completed

Thanks, @park1847 . As requested, here is a preview link of the Osmosis Frontend with XPLA. Please prove working Deposit, Withdraw, and Deposit Transaction Explorer URL.
Once we have a pool ID, we can finalize the pricing mechanism.

Thanks, @park1847 . As requested, here is a preview link of the Osmosis Frontend with XPLA. Please prove working Deposit, Withdraw, and Deposit Transaction Explorer URL. Once we have a pool ID, we can finalize the pricing mechanism.

[Osmosis Frontend with XPLA] There was an error in progress, so I edited and uploaded the [osmosis-1.chainlist.json] file.

Not sure why the frontend PR was closed, but I hope the preview link still works properly. Please let me know once it's been validated

Not sure why the frontend PR was closed, but I hope the preview link still works properly. Please let me know once it's been validated

I'm getting the error below
Please let me know if there is anything else I need to set up. :'
Transaction Failed
Broadcasting transaction failed with code 8 (codespace: ). Log: pubKey does not match signer address xpla1avuk09szwmnjmtva3f2w4mjeg6z8u0ew7u4au6 with signer index: 0: invalid pubkey
——————————————————
{
"account_number": "37098",
"chain_id": "dimension_37-1",
"fee": {
"gas": "210000",
"amount": [
{
"amount": "240975000000000000",
"denom": "axpla"
}
]
},
"memo": "",
"msgs": [
{
"type": "cosmos-sdk/MsgTransfer",
"value": {
"receiver": "osmo1n4m4ag8sq3mx6eetd2kt6f27n4mptvt9a9hu8r",
"sender": "xpla1avuk09szwmnjmtva3f2w4mjeg6z8u0ew7u4au6",
"source_channel": "channel-9",
"source_port": "transfer",
"timeout_height": {
"revision_height": "10715959",
"revision_number": "1"
},
"token": {
"amount": "100000000000000000",
"denom": "axpla"
}
}
}
],
"sequence": "4"
}

Hi Jeremy, I'm from team xpla
We have a question about the above error..We set slip44 to 60 because xpla chain supports evm.
Besides us, Planq, Acrechain, and other chains that set slip44 to 60 and perform deposits on the asset page are all getting the same error as xpla.
Among the chains with slip44 set to 60, some chains such as evmos and injective seem to support deposit from an external link not from the asset page of Osmosis.
Can I ask if the chains that support EVM can only deposit via an external link?

Hi @scrolldown , thanks for explaining. Although I wouldn't be able to explain the reasoning very well, the short answer is: yes; the type 60 coins have required an alternative frontend for transferring because so kind of custom messaging or tx is required. Does XPLA have it's own frontend for transferring? or no?

ok. thanks for your reply. XPLA doesn't have its own frontend for transferring.
But IBC transferring to osmosis are available in the Kepler wallet.
Is own frontend for transferring required?

I'll instead be using this PR to add XPLA to the frontend.
https://github.com/osmosis-labs/osmosis-frontend/pull/1939
Please let me know once a pool is created so I can validate myself. (will use TFM for Deposit)

TFM interface is not working. I'm trying to transfer from xpla to osmosis. But "Sorry, we don't have the data to suggest this chain" error occurs when trying "connect wallet".  So I opened ticket with this matter on TFM discord.
XPLA Pool will be created after it is added to the assetlist, so I'll comment a success screenshot and tx at this PR.
Thank you as always for your kind.

TFM interface is not working. I'm trying to transfer from xpla to osmosis. But "Sorry, we don't have the data to suggest this chain" error occurs when trying "connect wallet". So I opened ticket with this matter on TFM discord. I think that the TFM team will fix this issue. When the Deposit feature via TFM is working, I'll comment a success screenshot and tx at this PR. Because XPLA Pool will be created after it is added to the osmosis asset-list. Thank you as always for your kind.

FYI, I've been able to Connect a Wallet on TFM for XPLA (thought I don't have any XPLA tokens to test with). Think it's worth re-testing to see if it works on TFM now?

Connecting a wallet is now available, but IBC transfers are not yet available. I don't recommend testing it yet.
https://github.com/osmosis-labs/assetlists/assets/11815825/089d2ccc-a96d-4ebf-8cb0-728b2538e667
https://github.com/osmosis-labs/assetlists/assets/11815825/a02e914e-da1a-4b21-8b19-32b3fbbd4078

We have completed building the pages for IBC depsoit and withdraw, Can you please use this site?
https://ibc.xpla.io/

Here is a preview link you can use to create pool. Please let me know the pool ID number so I can buy a small amount and validate myself.
https://osmosis-frontend-git-jp69-add-xpla-osmo-labs.vercel.app/?from=ATOM&to=OSMO

Thanks for your work! XPLA-OSMO pool ID is 1173. Here is a link for validation test.
https://osmosis-frontend-git-jp69-add-xpla-osmo-labs.vercel.app/pool/1173

Also, I believe this interface should show 0.4 (my total balance) here, but then show this 0.1705 as the net amount sent after subtracting the fee. It makes sense for the big number to show that, as it's simulating the amount transferred, but for the (green underlined) balance it should be the actual balance.

This is a problem we were thinking about.
Due to the feature of XPLA as a Game-centric mainnet, there are many users who are new to blockchain. Therefore, if we don't calculate the fee first, if the user puts the max value and executes the tx, it may happen that only the fee is consumed and the tx fails.
That's why we made the page like this. However, we agree that the balance should show the actual value, so we have modified the page according to your suggestion.
Thank you for your suggestion!


More Template 5.3/7.3 support necessary for GDAS

Motivation
The GDAS data referred to in #29 uses Template 5.3/7.3, but it sometimes cannot be decoded with current decoder:
% ./target/debug/gribber decode nomads.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/gdas.20230111/12/atmos/gdas.t12z.pgrb2.0p25.f000 0.0
error: ComplexPackingDecodeError(
    NotSupported,
)

Detailed Information on the Data

URL is documented in #29

Additional Context
Octet 49 (numberOfOctetsExtraDescriptors in ecCodes) in some submessages of this data is 3, although this crate currently supports only 2.  It is the reason of this error. That octet in other submessages is 2.

@LafeWessel Thank you very much for reporting!
I have reproduced the issue using your code and understand its cause. This is due to the same cause as #30. However, since checking the number of bytes and returning the #30 error is done a little later than accessing the bytes, we are getting a different error in the case where the access fails as in this case.
The current code only supports 2 bytes as a number of extra parameters in Section 7. #30 should occur when it is greater than 2 bytes, and as far as I can tell from checking the data, it occurs when the submessage contains 3-bytes parameters. This #31 occurs when it is less than 2 bytes (the data which I reproduced the issue with contains 1-byte parameters).
Fixing #30 should resolve this issue together, so please be patient for a little longer.


Calico doesn't start

Rancher Server Setup
Rancher version: v.2.6.3
Information about the Cluster
Installation option:

Helm version: v3.8.0
k3s version: v1.22.6+k3s1

Openstack:

Microstack Installation - version ussuri, Revision 245

Describe the bug
I created an RKE2 Cluster with Calico in two machines (the first one has the three roles - etcd, control plane, and worker- and the second one is just a worker. These machines are in the same network and it works okay.
The ports that are open in Master Node are the followings:

Then, I am trying to create a new node worker inside of OpenStack, to do that I create an instance with Debian 11, and paste the registration command to the machine.
To do that in the first two machines I create a route to the external and internal networks of OpenStack. Also, I am using network rules to allow all traffic that comes from outside and that goes outside.
Result
In Rancher Interface, the Provisioning Log shows the message:

Pods that are running (trying) in new node:

The logs from the pods:

The describe pod:

The logs of rke2-agent:

Expected Result
In Rancher Interface, the "State" of the Cluster should become "Active"
To Reproduce
Create a Cluster with the configuration mentioned.

Your first server and worker nodes are not running inside openstack but the additional worker is based on an OpenStack VM?

Yes, exactly. My first two nodes are not OpenStack instances and worked fine, when I try to add a new node (OpenStack instance) the problems appear. I already tried to run a Cluster in OpenStack only but I stuck in this issue too: https://github.com/rancher/rancher/issues/37075#issue-1183487517

Did you open all required ports to run Calico? I wonder if the neutron network policies are blocking the communication

Did you open all required ports to run Calico? I wonder if the neutron network policies are blocking the communication

Yes, in Master node I allow all traffic, and in my new instance (Openstack instance), at the moment I have the following rules:

What is the output you get when running kubectl get nodes -o wide?
According to your logs, the agent is unable to connect to the server <IP_ADDRESS>:9345. That's the first thing you should investigate. Could you try running nc -zv <IP_ADDRESS> 9345 from the Debian VM running on OpenStack?

If nodes are running, you should not see the log in the agent not being able to connect to <IP_ADDRESS>:9345. Can you please verify?

If nodes are running, you should not see the log in the agent not being able to connect to <IP_ADDRESS>:9345. Can you please verify?

I installed netcat and used the command that you have mentioned and  this is the output:

The node alternate in "Ready" and "NotReady" state, depending on this restarts, which means that when the pods  are Running (the only one that does not turn "Running" is the calico one) the node is "Ready" when the pods restart, the node becomes "NotReady"

When I see the logs from the calico pod this is the output:

In the Worker node, the 10250 port is open but the connection to 53726 is denied

So the node alternates between Ready and Not-ready state and when it is not-ready, you see in the logs that it can't reach <IP_ADDRESS>:9345?

So the node alternates between Ready and Not-ready state and when it is not-ready, you see in the logs that it can't reach <IP_ADDRESS>:9345?

Yes. When is in a Ready state, the rke2-agent is fine and does not show any logs.

So the node alternates between Ready and Not-ready state and when it is not-ready, you see in the logs that it can't reach <IP_ADDRESS>:9345?

Yes. When is in a Ready state, the rke2-agent is fine and does not show any logs.

So, from time to time, something in your networking connection between nodes breaks. And then your openstack node is unable to communicate with the server on port 9345? That's when you see the logs, right? Have you tried other type of traffic? For example pinging between nodes? Does it fail also intermittently?

So the node alternates between Ready and Not-ready state and when it is not-ready, you see in the logs that it can't reach <IP_ADDRESS>:9345?

Yes. When is in a Ready state, the rke2-agent is fine and does not show any logs.

So, from time to time, something in your networking connection between nodes breaks. And then your openstack node is unable to communicate with the server on port 9345? That's when you see the logs, right? Have you tried other type of traffic? For example pinging between nodes? Does it fail also intermittently?

Yes, I already tried pinging between nodes but the connection is always okay! The only thing that I see that can cause this is the pods (that I already mentioned) are always restarting and don't keep running, but I don't understand why this happen

Let's focus on another problem which is fishy. You can't see the logs of your pods because the server can't access $openstack_node:10250. From the server, can you try: nc -zv <IP_ADDRESS> 10250? Please check several times to verify if it is also failing intermittently

When the Node is in the state not Ready, the connection is refused:

But in Worker node when I see the ports that are open, the port is okay:

When the port is ready, does netcat work?

calico depends on (https://github.com/kubernetes/cloud-provider-openstack)
You have checked if the openstack cloud controller services are up?

calico depends on (https://github.com/kubernetes/cloud-provider-openstack)
You have checked if the openstack cloud controller services are up?

I'm sorry but could you be more clear? The repository that you mention is necessary for what? I do not see any documentation mentioning this in Rancher documentation. I'm starting to use this tool so I don't have a lot of knowledge.
Yes, my Openstack is running and it's okay.


Retrieve Conversation ID for any conversation the Bot is a member of, and not only the conversation which the Bot is in at a given time

Moved from: https://github.com/microsoft/botbuilder-dotnet/issues/4475
Is your feature request related to a problem? Please describe.
Yes. At this time, I am unaware of an ability for a bot to obtain the conversation ID for any conversation the Bot is a member of-- without the Bot utilizing the TurnContext of the conversation the Bot is participating in. Due to this, the Bot is only able to obtian data about the conversation at hand, rather than any conversation. Via MS Graph API, I understand conversation IDs can be obtained (https://docs.microsoft.com/en-us/graph/teams-proactive-messaging#get-the-chat-thread-id). However, this method does not support authentication tokens acquired via Application permission. This method only supports delegate authentication tokens, and my use case does not support delegate permission. I must use Application permission.
The conversationUpdate event, which triggers an overridden OnTeamsMembersAddedAsync method that gathers and stores the conversation ID in a database, is not passed each time the Bot is uninstalled and reinstalled for a user. I take this action in the event the conversation ID is not within the database.
Describe the solution you'd like
It would be great if the Bot had the ability to gather the conversation ID for ANY conversation which the Bot is a member of. Not just for the conversation the Bot is in at a given time. For my use case, 1:1 chats are my target

Thanks for reaching out to us. We have raised a feature request for this.

I see this has been closed. However, I could not find any updates. Has this been implemented?


Device stuck into respring. Cant reboot. Buttons donot working.

Hey guys,
my phone is stuck in the respring mode. I tried to Jailbreak but then it failed between package 27 and 36.
Now my little respringtire (or wheel) whatever stopped turning and i can't reboot with my buttons.
Any possible way to get out there?
Thanks a lot.

You sure you uninstalled the update OTA?

yes i am!
But just did the hard restart front now it works.

That problem caused after installing the Tweak : CleanHomeScreen

Marcel please help me. I installed clean home screen and now I have the same issue...what do i do?


OME-TIFF Read / Write

added OME-TIFF support

If you haven't already, please read through our contributing guidelines before opening your PR
What is the purpose of this PR?
Closes #807. Adds support for converting a FOV to an OME-TIFF and vice versa.
How did you implement your changes
Added two functions, fov_to_ome and ome_to_fov in load_utils.py.

fov_to_ome: Can convert multiple FOVs with whatever channels necessary to OME-TIFFs
ome_to_fov: Can only convert one OME-TIFF to a FOV.
Added a Jupyter Notebook which walks users through the conversion process.
Added an OME-TIFF into the Example Dataset.

Remaining issues

[x] Merge HF PR 10

@cliu72 I've added a short utility notebook which walks a user through the conversion process. Let me know your thoughts!

@cliu72 I updated the OME-TIFF converter notebook to be more descriptive, and added a FOV to OME-TIFF section.

Okay sorry one more anal thing - can we name the notebook "OME-TIFF_Conversion.ipynb" to match the other notebook names?

I tried to test the notebook using the CyCIF OME data I got here: https://www.synapse.org/#!Synapse:syn25372889, but I'm getting this error:

I tried it on this one: https://downloads.openmicroscopy.org/images/OME-TIFF/2016-06/sub-resolutions/Brightfield/Leica-1/Leica-1.ome.tiff
And got this error:

@cliu72 I fixed the issue for reading the second image. You need the imagecodecs library in order to decompress the first image (the second image requires it as well).
imagecodecs does not have a native Apple Silicon PYPI build, that architecture's version is only available through Anaconda, but for any other platform it should be pip installable.

If it's not too much work, can we add an example OME-TIFF? I think you can just take one of the example FOVs, use this notebook to create the OME-TIFF, and then add it to the example dataset. I think just one FOV would be fine.
And then can we move the cell to download the example dataset to the relevant sections? I.e. move the get_example_dataset for single channel TIFFs to the section "Single Channel TIFFs to OME-TIFF", and then add the cell to get the example OME-TIFF to the first section. Since presumably most users will be only doing one of the two.

@cliu72 Dataset is available on this branch, Need to fix a couple of tests, but you can use it with the conversion notebook.

Sweet, looks good!
Last thing, can we add more description to before the cell to download the example dataset? Maybe so it looks like this:
OME-TIFF to Single Channel TIFFs
If you would like to test this feature using an example dataset, run the cell below. To use your own data, skip the cell below and change ome_dir_path and data_dir_path below to point to your own data.
example_dataset.get_example_dataset(dataset="ome_tiff", save_dir = pathlib.Path("../data/example_dataset/"), overwrite_existing = True)
[rest of the code]
Single Channel TIFFs to OME-TIFF
If you would like to test this feature using an example dataset, run the cell below. To use your own data, skip the cell below and change data_dir and save_dir below to point to your own data.
[rest of the code]

@ngreenwald Missing some coverage, as I'm not able to create ome-tiffs with tifffile that have an incorrect format (i.e. a couple of the example ones that @cliu72 tested out).


Apple ID Authentication — Cannot login after Apple ID email change

Build/Submit details page URL
No response
Summary
I recently updated the email address on my Apple ID account and it seems I cannot login to Apple via eas-cli or legacy build system. Email and password is correct, I'm able to login on the web portal.

[X] Tried the old email/username as well.
[X] All user agreements signed on the portal.

Get the following output:
Accessing credentials for rgordon in project never-better
✔ Do you have access to the Apple account that will be used for submitting this app to the App Store? … yes

› Log in to your Apple Developer account to continue
✔ Apple ID: …<EMAIL_ADDRESS>› The password is only used to authenticate with Apple and never stored on EAS servers
  Learn more.
✔ Password (for ********@supryan.com): … ****************************
› Saving Apple ID password to the local Keychain
  Learn more.
✖ Logging in...
Invalid username and password combination. Used<EMAIL_ADDRESS>as the username.

Managed or bare?
Managed
Environment
expo-env-info 1.0.5 environment info:
    System:
      OS: macOS 12.5.1
      Shell: 5.8.1 - /bin/zsh
    Binaries:
      Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
      Yarn: 1.10.1 - /usr/local/bin/yarn
      npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
      Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
    Managers:
      CocoaPods: 1.11.3 - /usr/local/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
      Android SDK:
        API Levels: 27, 28, 29, 30
        Build Tools: 28.0.3, 29.0.2, 30.0.2
        System Images: android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-30 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 4.1 AI-201.87<IP_ADDRESS>53283
      Xcode: 13.4.1/13F100 - /usr/bin/xcodebuild
    npmPackages:
      @expo/metro-config: ^0.1.59 => 0.1.59
      expo: ^44.0.0 => 44.0.6
      react: 17.0.1 => 17.0.1
      react-dom: 17.0.1 => 17.0.1
      react-native: 0.64.3 => 0.64.3
      react-native-web: 0.17.1 => 0.17.1
    npmGlobalPackages:
      eas-cli: 0.60.0
      expo-cli: 6.0.5
    Expo Workflow: managed

Error output
Accessing credentials for rgordon in project never-better
✔ Do you have access to the Apple account that will be used for submitting this app to the App Store? … yes

› Log in to your Apple Developer account to continue
✔ Apple ID: …<EMAIL_ADDRESS>› The password is only used to authenticate with Apple and never stored on EAS servers
  Learn more.
✔ Password (for ********@supryan.com): … ****************************
› Saving Apple ID password to the local Keychain
  Learn more.
✖ Logging in...
Invalid username and password combination. Used<EMAIL_ADDRESS>as the username.

Reproducible demo or steps to reproduce from a blank project

Change email address/username for Apple ID
Logout of the eas if already logged in
eas login
Run a new build and provide Apple account credentials
See error

try running: EXPO_APP_STORE_DEBUG=1 npx @expo/apple-utils login and share the output

and if that doesn't work.. try EXPO_NO_KEYCHAIN=1 EXPO_APP_STORE_DEBUG=1 npx @expo/apple-utils login

@brentvatne the latter worked for me! I'm all logged in now thank you for a quick response!

and if that doesn't work.. try EXPO_NO_KEYCHAIN=1 EXPO_APP_STORE_DEBUG=1 npx @expo/apple-utils login

I had the following issue when running eas build -p ios and the above solution worked like a charm, thanks @brentvatne !!
✖ Logging in...
Authentication with Apple Developer Portal failed!
    Error: Apple Service Error -36607. Unable to sign you in to your Apple ID. Try again later. Learn more. Opens in a new window.
node:child_process:935
    throw err;

Get the following output:

I cannot login to Apple via eas-cli or legacy build system. Email and password is correct, I'm able to login on the web portal.
Get the following output:
`➜  app-mobile git:(main) ✗ eas device:create
This command lets you register your Apple devices (iPhones, iPads and Macs) for internal distribution of your app.
Internal distribution means that you won't need to upload your app archive to App Store / Testflight.
Your app archive (.ipa) will be installable on your equipment as long as you sign your application with an adhoc provisioning profile.
The provisioning profile needs to contain the UDIDs (unique identifiers) of your iPhones, iPads and Macs.
First of all, choose the Expo account under which you want to register your devices.
Later, authenticate with Apple and choose your desired Apple Team (if your Apple ID has access to multiple teams).
✔ You're inside the project directory. Would you like to use the app-mobile account? … yes
› Log in to your Apple Developer account to continue
✔ Apple ID: …<EMAIL_ADDRESS>› Using password for<EMAIL_ADDRESS>from your local Keychain
Learn more
✖ Logging in...
Invalid username and password combination. Used<EMAIL_ADDRESS>as the username.
› Removed Apple ID password from the native Keychain
? Would you like to try again? › no / yes`
I've tried this commands already, but still not working. https://github.com/expo/eas-cli/issues/1294#issuecomment-1222609571
https://github.com/expo/eas-cli/issues/1294#issuecomment-1222610936

i have the same problem, but the solution above is not woking:
FF416:FDTest user252449$ EXPO_NO_KEYCHAIN=1 EXPO_APP_STORE_DEBUG=1 npx @expo/apple-utils login
-- Enabled debug logging --
Log in to your Apple Developer account to continue
✔ Apple ID: …<EMAIL_ADDRESS>› The password is only used to authenticate with Apple and never stored on Expo servers
Learn more: https://bit.ly/2VtGWhU
✔ Password (for prenner.products@gmail.com): … **********
Skip storing Apple ID password in the local Keychain.
⠋ Logging in...GET https://idmsa.apple.com/appleauth/auth/signin?widgetKey=e0b80c3bf78523bfe80974d320935bfa30add02e1bff88ec2166c6bd5a706c42
⠧ Logging in...200  (GET https://idmsa.apple.com/appleauth/auth/signin?widgetKey=e0b80c3bf78523bfe80974d320935bfa30add02e1bff88ec2166c6bd5a706c42)
POST https://idmsa.apple.com/appleauth/auth/signin
⠙ Logging in...Error: Request failed with status code 409 (POST https://idmsa.apple.com/appleauth/auth/signin)
✔ Logged in, verify your Apple account to continue
GET https://idmsa.apple.com/appleauth/auth
Error: Request failed with status code 423 (GET https://idmsa.apple.com/appleauth/auth)
✖ Logging in...
This phone number cannot be used at this time. Try again later or choose a different number.
Error: This phone number cannot be used at this time. Try again later or choose a different number.
at a (/Users/user252449/.npm/_npx/0c9fefa1aae6e81c/node_modules/@expo/apple-utils/build/index.js:1:718209)
at o (/Users/user252449/.npm/_npx/0c9fefa1aae6e81c/node_modules/@expo/apple-utils/build/index.js:1:718164)
at t.idmsaRequestAsync (/Users/user252449/.npm/_npx/0c9fefa1aae6e81c/node_modules/@expo/apple-utils/build/index.js:1:718423)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async t.requestAuthAsync (/Users/user252449/.npm/_npx/0c9fefa1aae6e81c/node_modules/@expo/apple-utils/build/index.js:1:731967)
at async t.handleTwoFactorAuthentication (/Users/user252449/.npm/_npx/0c9fefa1aae6e81c/node_modules/@expo/apple-utils/build/index.js:1:728132)
at async S (/Users/user252449/.npm/_npx/0c9fefa1aae6e81c/node_modules/@expo/apple-utils/build/index.js:1:709726)
at async t.loginAsync (/Users/user252449/.npm/_npx/0c9fefa1aae6e81c/node_modules/@expo/apple-utils/build/index.js:1:713310)
at async /Users/user252449/.npm/_npx/0c9fefa1aae6e81c/node_modules/@expo/apple-utils/build/index.js:1:968934
at async c. (/Users/user252449/.npm/_npx/0c9fefa1aae6e81c/node_modules/@expo/apple-utils/build/index.js:1:973474)
FF416:FDTest user252449$

uninstalling and reinstalling eas globally did it for me 🤷♂

I am still facing this very same issue, uninstalling and reinstalling eas globally didnt work.

I just had to update my Expo CLI, then the problem was fixed.

I had installed the cli as a dependency by mistake at some point. That was overriding the globally installed version.
So I removed that, updated global and all worked :)


How to config class agnostic nms in train_cfg?

   test_cfg=dict(         rpn=dict(             nms_pre=1000,             max_per_img=1000,             nms=dict(type='nms', iou_threshold=0.7),             min_bbox_size=0),         rcnn=dict(             score_thr=0.05,             nms=dict(type='nms', iou_threshold=0.5),             max_per_img=100)         # soft-nms is also supported for rcnn testing         # e.g., nms=dict(type='soft_nms', iou_threshold=0.5, min_score=0.05)     )
The nms will not deal with overlaping bboxes with different classes. However now it's a strong prior that my detection task involves objects will never overlap each other. And the result can have many high IOU bboxes with different classes.
I notice there is a batched_nms in mmcv with a class agnostic option. But I've no idea how I config it in model test_cfg scope. Also it should support deployment export with that config.
Any solution ?

@sipie800 I'm sorry, but currently, that parameter is not exposed. It can only be manually modified for now.

@sipie800 I'm sorry, but currently, that parameter is not exposed. It can only be manually modified for now.

Could you show me about how to modify the program to expose that parameter? As the test_cfg use type="nms", what's the connection between nms and batched_nms ? Or is the batched_nms itself exposed in a config?


0.6.0: allow to receive arbitrary messages from server

onMessage signal is being triggered only for a specific message kind. It needs to be triggered for any message.
https://github.com/gamestdio/colyseus.js/blob/master/src/Client.ts#L117
(reported by @AnubisCode on Gitter, thanks!)

#5 this

Thanks @AnubisCode, just published version 0.6.0-alpha.1 with your fix 👏


Add Theravada

https://github.com/johnjago/awesome-theravada
This list contains a variety of resources on Theravada Buddhism, including academic articles, books, talks, communities, videos, and more. The goal of this list is to provide quick access to information on the Theravada tradition and to have this information presented in many forms. That way, it will be useful to people all people, whether they are looking for a place to start academic research or just learn about the religion.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either fullwidth or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of sub-lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

In Theravada is a branch of Buddhism that draws its doctrine from the Pali canon, can you linkify Theravada to the Wikipedia page? Not everyone would know to click the image.

Really cool to have more non-tech lists. And thanks for taking the time to make it awesome.

I will tweet the list later this week from this account: https://twitter.com/awesome__re


Group Certificate with "Firstname Lastname" and "Lastname Firstname"

Current Implementation
Certificates are grouped together as long as they are for the same Person. The group logic checks, if trim(firstname) and trim(lastname) are identical.
Some Certificate Authorities invert firstname and lastname. Therefore, these certificates aren't grouped together.
Suggested Enhancement
Certificates are grouped even if firstname and lastname are mixed up.
Expected Benefits
Clean interface and grouped certificates.

Idee: Manuelle Clusterrung; Hilft z.B. bei unterschiedlichem Handling vom Zweitnamen
https://twitter.com/9lukas5/status/1477625249470586881?s=21

Related issue:

#705

FYI: iOS PR https://github.com/corona-warn-app/cwa-app-ios/pull/4179 starts working on an automatic solution, e.g. filtering out "Dr." (link to code).

Closing this ticket as this was implemented in version 2.19 of the Corona-Warn-App.
See FAQ or Blog

Corona-Warn-App Open Source Team


Fix topic creation for system tests

Type of change

Bugfix

Description
Increased the timeout to wait for a topic to be created and added a check for topic existence before deleting a topic
Additional Context
Sometimes the topic creation failed because of a timeout and when the topic was not created, there was another failure when trying to delete it.
Checklist

[ ] Write tests
[X] Make sure all tests pass
[ ] Review performance test results. Ensure that any degradations to performance numbers are understood and justified.
[ ] Make sure all Sonarcloud warnings are addressed or are justifiably ignored.
[ ] Update documentation
[ ] Reference relevant issue(s) and close them after merging
[ ] For user facing changes, update CHANGELOG.md (remember to include changes affecting the API of the test artefacts too).

@strimzi-ci run system tests

:arrow_forward: Build started - check Jenkins for more info. :arrow_forward:

:heavy_check_mark: Test Summary :heavy_check_mark:
BUILD NUMBER: 31
KAFKA VERSION: 3.6.1
TOTAL: 11
PASS: 10
FAIL: 0
SKIP: 1

@franvila looks good to me. I made a couple of suggestions.

@strimzi-ci run system tests

:arrow_forward: Build started - check Jenkins for more info. :arrow_forward:

:heavy_check_mark: Test Summary :heavy_check_mark:
BUILD NUMBER: 32
KAFKA VERSION: 3.6.1
TOTAL: 11
PASS: 10
FAIL: 0
SKIP: 1

Lgtm

@strimzi-ci run perf

:arrow_forward: Build started - check Jenkins for more info. :arrow_forward:

:heavy_check_mark: Test Summary :heavy_check_mark:
BUILD NUMBER: 1
KAFKA VERSION: null
NUMBER OF BROKERS: 1
NUMBER OF MESSAGES: null
MESSAGE SIZE: null bytes
PRODUCER PROPERTIES: null
:heavy_exclamation_mark: Performance Tests Failed for Producer (no tests results are present) :heavy_exclamation_mark:
:heavy_exclamation_mark: Performance Tests Failed for Consumer (no tests results are present) :heavy_exclamation_mark:


[libiconv] Deploy on BSDs

Fixes #39748

[x] Changes comply with the maintainer guide.
[ ] ~SHA512s are updated for each updated download.~
[ ] ~The "supports" clause reflects platforms that may be fixed by this new version.~
[ ] ~Any fixed CI baseline entries are removed from that file.~
[ ] ~Any patches that are no longer applied are deleted from the port's directory.~
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Reproducting Github Action using ChristopherHX/github-act-runner on a vultr hosted OpenBSD-7.5: link
Notoriously, the artifact for ${VCPKG_ROOT}/installed/vcpkg/info indicates that the libiconv package did not provision the iconv.h file consumed by the glib build process, causing the later to fail.

Build run on the PR branch: link
iconv.h and the other content of the libiconv package is deployed, enabling glib and other consumers to be built.

Build run on the PR branch: link
iconv.h and the other content of the libiconv package is deployed, enabling glib and other consumers to be built.

Thanks for testing.

OpenBSD has BSD's implementation of iconv, but glib and friends - via gnu gettext - rely on GNU's implementation of iconv.

Where can this be verified w.r.t. BSD?

[ ] glib relying on the GNU implementation of gettext/libintl
[ ] GNU gettext relying on the GNU implementation of iconv

FTR we also to deal musl libc Linux systems which don't have gettext/libintl in the C lib.
I do know that gettext comes with detection logic built into m4 files for autotools, and I assume that's why we don't have pkg-config files.
CMake has Find modules, but they need wrappers in vcpkg.
Meson ... still not encouraging.

OpenBSD has BSD's implementation of iconv, but glib and friends - via gnu gettext - rely on GNU's implementation of iconv.

Where can this be verified w.r.t. BSD?
* [ ]  glib relying on the _GNU_ implementation of gettext/libintl

* [ ]  GNU gettext relying on the _GNU_ implementation of iconv

FTR vcpkg should also correctly handle musl libc Linux systems which don't have gettext/libintl in the C lib.
I do know that gettext comes with detection logic built into m4 files for autotools, and I assume that's why we don't have pkg-config files. CMake has Find modules, but they need wrappers in vcpkg. Meson ... still not encouraging.

I was wrongly assuming the glib port tracks its dependency on iconv by depending on gettext which implies iconv, because I didn't double-check it yesterday. The glib port directly tracks it's dependency on iconv, hence it's glib → GNU iconv (rather then glib → gettext → GNU iconv).
There's a lengthy discussion in a FreeBSD mailing list about glibmm consumers throwing exceptions when linked against FreeBSD's libiconv reducing the problem to glib being reliant on the availablity of the nonstandard WCHAR_T extention available in GNU iconv but not BSD iconv.
FreeBSD's ports have resolved this by hard-depending the glib20 port on gnu's libiconv by adding a corresponding dependency line into the glib20 port Makefile (iconv:wchar_t triggers this branch to depend on converters/libiconv which is GNU's one), just as vcpkg's glib port has an entry in glib's vcpkg.json leading to vcpkg's libiconv port which also is GNU's one. However, the vcpkg libiconv port, at this time, omits the deployment of libiconv on FreeBSD systems, therefore the dependency declaration has no effect.

The vcpkg port currently fiters on the operating system rather then find_library / try_compile / try_run-ing something to detect the iconv function's availability on the build system. On setups where libiconv is an explicit package and not installed, or has the library but not the header files installed, this could lead to failures further down the dependency chain.
As I wrote in the issue, we should be able to deploy and use our iconv even in environments where iconv is part of the libc, so always deploying it "should" work there, too.

More important then implementational details of the various iconv implementations, though, I'd like vcpkg to provision a dependency when I add it to my vcpkg.json dependency list, or to emit a diagnostic indicating the deployment was skipped, rather then silently providing me with an Operating System provided dependency.


No longer compatible with sybil==3.*

Tests fail:
error: builder for '/nix/store/x1x2xj9539pqydnqqc7syi4hqpvkm3wv-python3.9-testfixtures-6.18.3.drv' failed with exit code 4;
       last 10 log lines:
       > Executing pythonImportsCheckPhase
       > Check whether the following modules can be imported: testfixtures
       > pytestCheckPhase
       > Executing pytestCheckPhase
       > ImportError while loading conftest '/build/testfixtures-6.18.3/testfixtures/tests/conftest.py'.
       > testfixtures/tests/conftest.py:21: in <module>
       >     CodeBlockParser(),
       > /nix/store/zqhlwzm5nqg6fx04cvjbja0wm0dm0zm1-sybil-3.0.0/lib/python3.9/site-packages/sybil/parsers/codeblock.py:34: in __init__
       >     assert self.language, 'language must be specified!'
       > E   AttributeError: 'CodeBlockParser' object has no attribute 'language'
       For full logs, run 'nix log /nix/store/x1x2xj9539pqydnqqc7syi4hqpvkm3wv-python3.9-testfixtures-6.18.3.drv'.

This cropped up in https://github.com/simplistix/testfixtures/pull/167 too.
Unfortunately, python packaging metadata has no way to express "if you have this package installed, it needs to match there version requirements". If you know better, please let me know!
What lead you to encounter this? Are you using sybil with testfixtures?

What lead you to encounter this? Are you using sybil with testfixtures?

I'm running the test suite of this package
       > testfixtures/tests/conftest.py:21: in <module>
       >     CodeBlockParser(),

What lead you to run the test suite?
How are you setting up your development environment?

So here's the thing: you're throwing out a "bug" report without doing even a basic amount of due diligence.
Had you bothered to look, you might have noticed:

I'm the author of sybil. I'm also the author of testfixtures.
The CI for both testfixtures and sybil is green, so rather than reporting a "bug", maybe consider what you're doing wrong.
This is already accounted for on master, so seems fairly obvious to a packager like yourself that the correct solution here is to pin sybil<3 until a new release of testfixtures is made.
I've explained there's no way this can be expressed in a Python package's metadata.

With a bit more digging you may have even found https://github.com/cjw296/testfixtures/tree/v7.
Where this once again leaves me, as you'll see by looking at issues tagged with linux-distro-packaging, is yet more of the precious little time I have to do open source development being wasted to dealing with spurious issues logged up "distro packagers.
Please do the work, don't expect me to.

Wow, you could even be bothered to read the issue linked from your own "expression" :-/
For the record, this is totally bogus.

sorry if my short response are coming off as rude. Your package is just one of 4800 that we try to maintain.

This is already accounted for on master, so seems fairly obvious to a packager like yourself that the correct solution here is to pin sybil<3 until a new release of testfixtures is made.

We don't have that luxury. I mentioned earlier that we only have one version of a package, so we can't have sybil==2.x and sybil==3.x.

I've explained there's no way this can be expressed in a Python package's metadata.

I'm not sure what this means in this context

With a bit more digging you may have even found https://github.com/cjw296/testfixtures/tree/v7.

I don't think a version control branch is regarded as proper python package management.

Where this once again leaves me, as you'll see by looking at issues tagged with linux-distro-packaging, is yet more of the precious little time I have to do open source development being wasted to dealing with spurious issues logged by "distro packagers.

I'll add a comment to not contact this upstream.

Wow, you couldn't even be bothered to read the issue linked from your own "expression" :-/

The comment is a link to this bug report. It's to record that the upstream was made aware there's an issue with their released packages.

For the record, this is totally bogus.

Not all of them, at least datetime object are immutable, according to cpython.

Your package is just one of 4800 that we try to maintain.

How incredibly rude. "you're just a small cog, sorry we don't care".

Hi, I just spoke to @jonringer, and I think that some sort of miscommunication happened here.
To clarify, their issue wasn't meant as a support request (in which case I could see why it'd come across as low-effort!), but rather just as a heads-up that something seemed broken on your end, in case you didn't know about it yet. On the NixOS side, there's already a solution in place, so there's really no rush for an upstream fix here.
So as I understand the situation, the frustration on your side seems to be because you felt like you were being asked to provide support without the necessary details, whereas the frustration on their side was because they thought they were being asked to do extra investigative work for something that was just supposed to be a heads-up.
I don't think that the intention of it being a heads-up was clear from their original post, though, so apologies for that. I won't bother you about this issue any further, I just want to try and clear the air; I know that the tension between packagers and maintainers can run high at times, and I don't think it's good for anybody involved for things to end in conflict :)
(Full disclosure: I'm not a packager myself, just a NixOS user and community member who cares about keeping the community healthy and friendly)

"keeping the community healthy and friendly" - you're failing by continuing to waste yet more of the precious little time I have to do open source development.
To clarify, support or heads-up, issues like this are unhelpful and unwelcome. There's is nothing solvable or "broken" related to this issue in this package. Packaging spammers like @jonringer, @fabaff and @kloczek need to do better. If you're going to spam a package with your "issue", make very sure it's actually a problem.
Maybe a metaphor will help?
"Hey, that bolt you give away for free..."
"Oh? This one that's carefully measured each evening with demonstrations of how it can be used with this nut and when the nut changes size, changes have to be made?"
"Yeah, we bashed it into the nut we had lying around with a hammer. The bolt broke."
"..."
"Your bolt is wrong and broken."
😳 "Don't do that..."
"No look, we bang, thousands of things that might be nails into stuff, 4,800 things no less, we've got a great hammer. We're being helpful by telling you this, why are you so ungrateful?!"
"Please go away."
"Hey, so you told my friend to go away, so here's the thing... when you bash this bolt of yours into the wrong size nut, you should be grateful that we make you listen to us complain about it not working".
🙄


Event sources as Connectables

This pull request does two things:

Breaks up MobiusLoopTest into smaller files grouping tests by behavior category. No Tests have been changed, only extracted to other classes. (1st commit)
Changes MobiusLoop's API to accept a Connectable<M, E> in place of an EventSource<E> for an event source. The change is non-breaking and is backwards compatible. (2nd commit)

The actual change to the API is only in the second commit, about 340 additions :)
Reasons for the change:
Our initial choice for EventSource<E> does not allow for conditional subscriptions based on the state of the loop. This change enables users to achieve that. The current structure of event sources also makes composition of loops more difficult since subscriptions happen immediately and not based on what state we're in. In this case, subscriptions could possibly happen before a subdomain is initialized. This can lead to overly complex update functions and state definitions just to work around the fact that an event source started emitting things prematurely.
This change brings Mobius' EventSources closer to Elms Subscriptions concept. With this change, every time the Model changes, the connectable is notified of that change, and can therefore determine if any changes should occur in subscriptions it is currently maintaining.

@pettermahlen I've changed it so that the adapter will now subscribe immediately to the event source. This means it has the exact same behavior as before. There's no change in threads. Whatever thread you start a loop from, is where it'll subscribe to the event source. Disposal is also the same. Not fully convinced this is really makes a difference, but it does maintain the current behavior. But I'd like to revisit this in the next major release.


all buttons will be pressed when switch windows

all sliders value is 128 when switch windows.
when ds3 connected is will happened too
sorry for my English. problem just like this video.
https://www.youtube.com/watch?v=EEyrLsEoq-4

Hello,
This seems like an issue with PCSX2 since the driver doesn't care which window is active. Can you try with different controllers or a newer version of PCSX2?
Cheers

I have tried 1.4.0 1.6.0 and 1.7.0 version. is all same
using "Monitor when in background" is no problem.
rpcs3 don't have problem like this

Looks like a PCSX2 bug to me. The driver always reports the current state of the controller, so this behaviour is exclusive to PCSX2. Please report the issue to them, nothing I can do about here.
Cheers


Zoom is slower when close to a model

Reported in the forum here: http://cesiumjs.org/forum.html#!msg/cesium-dev/C_OT9kB9RV8/-zlIMRjWCAAJ
Zooming is slower when the camera is close-ish to a model. Possibly not the proximity to the model, but the fact that the model is "in the center" of the view.
http://cesiumjs.org/Cesium/Apps/Sandcastle/?src=Hello World.html&label=Showcases&gist=a4bc90cb451cc3c997566e34a655c5ca
if you change the value of latOffsetin getPositionCentered() you will notice the difference.

This is by design, because of the vast difference that Cesium deals with, the magnitude of zooming with the mouse gets progressively smaller/larger the closer/further away you are from an object.
Now it could be that we need expose a good way to tweak this behavior, but ultimately it's working as intended.
@bagnell can confirm, and if there's no a decent way to tweak this with the existing API, we can leave this open as an issue to add such a capability.

I'm working on s.th. where there is a model in front of the camera pretty much all the time – but I still need users to be able to zoom normally. — is there a workaround to disable this?
I can see why you'd want this kind of behaviour, but it has caused me a bit of headache to figure out what is actually happening. in general I'd say make it opt-in for those who (know they) need this, rather than the default behaviour.

@mramato is right that this is by design. In the mean time, you can add this to disable it:
scene.screenSpaceCameraController.minimumPickingTerrainHeight = 0.0;
We need to update the name. If you have the depth texture extension, the camera will pick the depth texture which includes models and other geometry. If the extension is unavailable, th eterrain mesh is picked.
@freder I'm not sure the now default behavior should be opt-in behavior. The linked Sandcastle example seems unusual where the model is always in front of the camera. What is the use case for that?
Updated forum link: https://groups.google.com/forum/#!topic/cesium-dev/C_OT9kB9RV8

@bagnell could you please suggest a new name and some guidance for @rahwang to make this change?

@bagnell any thoughts on https://github.com/AnalyticalGraphicsInc/cesium/issues/5131#issuecomment-288228977?


Add sandboxed option, if set to false, iframe is not sandboxed

Add tests and documentation for sandboxed: false, replaces #84

Replaces #84

@hjdivad ping. happy to help out with maintaining this project if you want, too

:+1: on getting this in. I could really use this for a couple of projects.

This PR makes me sad.

Let's see what we can do about that, @jaehess. I just kicked the build. If we can get this green, I think it is mergeable.

We have a CI problem due to sauce labs being non-responsive and me not having credentials for the project's sauce labs account. I ran tests locally in latest Chrome, Safari and Firefox. Chrome passes on with both. Safari has one failure not present on master. Firefox has many tests that hang. I would like to at least have the Safari failure fixed before merging this.

Thanks for trying to get this merged @lukemelia - I would like to not have to work off a fork for long...


Regarding the test accuracy

I hope I am not wrong. In the code I am seeing that you are calculating test accuracy after every few training iterations and taking the max of them.
My question was

The results reported in the paper, Are they the maximum accuracy or the final accuracy after all the iterations?.
Is the validation same as test in cifar ?

I have the same question. Can you please clarify
@zs-zhong

Hi,
Very thanks for your interest! In fact, there is no much difference for selecting models by the last epoch or taking the max of them in our experiments. Further, the code could achieve better accuracies than the results reported in the paper.

Thanks for your reply,
Also regarding my second question I think both test and validation are taken to be the same.
My question is:
Have authors experimented using separate validation and test split?

The CIFAR experiments are followed LDAM-DRW (https://github.com/kaidic/LDAM-DRW).

Thanks . I will be closing this issue


feat: Add npm publishing workflow

This commit introduces a new GitHub Actions workflow for publishing the package to npm. It also includes a new script for building the npm package using the Deno dnt tool. The version of the package is passed as an argument to the script. The package.json for the npm package is generated by the dnt tool during the build process.
The .gitignore file has been updated to ignore the npm directory which is created during the build process.
The import_map.json file has been updated to include the Deno dnt tool as a dependency.
The deno.json file has been updated to include a new task for building the npm package.
fixes: #248

Summary by CodeRabbit

New Features

Implemented an automated workflow for building and publishing npm packages.
Added a new build script for npm package preparation.

Chores

Updated .gitignore to exclude npm build outputs.

Documentation

Updated import mappings to support new dependencies.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@c7d9dfc). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##             main      #253   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         5
  Lines           ?        23
  Branches        ?         2
========================================
  Hits            ?        23
  Misses          ?         0
  Partials        ?         0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Display a UIImage

Is your feature request related to a problem?
Hi, No bugs for me, your kit works well in my apps.
I was wondering if it was possible to use a UIImage instead of a system icon for a WhatsNew.Feature.
What solution would you like?
Use a UIImage instead of system icon
What alternatives have you considered?
I'm pretty new to this so I am a little stuck.
I was thinking it would be something like:
Instead of:
WhatsNew.Feature(
image: .init(systemName: "ladybug"),
title: "Cleaned up some Bugs",
subtitle: "We have sorted out some minor bugs and UI updates. "
),
my feature could be:
WhatsNew.Feature(
image: .init(UIImage: "myImage"),
title: "Cleaned up some Bugs",
subtitle: "We have sorted out some minor bugs and UI updates. "
),
I would be grateful for any help with pointing me in the right direction.
Any additional context?
No response

Hi @coldfingersnz,
You can simply use the WhatsNew.Feature.Image.init(image:) initializer and initialize a SwiftUI.Image with the appropriate UIImage initializer.
let image = WhatsNew.Feature.Image(
    image: SwiftUI.Image(
        uiImage: UIImage()
    )
)

Fantastic, thanks for the quick response, really appreciate it.
Great Plugin!!


[AppConfig]Add example for using --fields in appconfig revision

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

hi @bim-msft could you  pls review this PR ? thanks


colvis buttons issue with dynamically adding more buttons

I noticed when dynamically adding more buttons to datatables that the colvis active setting throws an error.
This can be seen in the following fiddle:
https://jsfiddle.net/719media/t2vaj88t/3/
click on the columns and notice that the active state does not get changed (and js error thrown). If you remove the dynamic add column, things work normally.
It has something to do with the column index referencing, as dynamically adding more buttons AFTER the buttons/colvis instance does not trigger the issue, only if adding it before (and therefore changing the colvis index).

Thanks for this. It should probably be filed at DataTables/Buttons or in the forums, however this is a bug for sure. And unfortunately its a bit of a rabbit warren bug - the deeper you go the bigger it gets...
The basic issue here is that the reference that the event handler is using for a button is out of date after adding a new button (it uses an array index). Since the init function is using a closure, that out of date reference is used.
I could just have the code get a new reference to the button since the node is being passed in, but the nodes can be regenerated when adding buttons, so actually the node reference is also out of date. This is resulting in a memory leak when you add a new button dynamically...
So it needs:

To reuse already constructed buttons when a new button is added
Change the internal referencing to use nodes rather than indexes

I was planning to do a 1.2 release of Buttons this week, so it makes sense to put a large change like this into it, although it might push the release back into next week...
Thanks for flagging it up. I'll post back when I've made the required changes.

That was a bit of an epic :-). Fixed in Buttons and will be included in the 1.2.0 release.

Wow that was fast. Thanks! You're awesome!


fix: add quick-config.sh

Adds the missing quick-config.sh script as noted in https://github.com/ipfs-shipyard/ipfs-webui#config-your-ipfs-daemon.

Closing this PR as it was branched off of the wrong branch. New clean PR incoming.