Unable to get Skicka token

Google blocking skicka token generation access. How Can I overcome this. People are suggesting to use rclone
$ skicka ls
skicka: attempting to launch browser to authorize.
(Re-run skicka with the -no-browser-auth option to authorize directly.)

I'll follow these steps:
https://github.com/satackey/action-google-drive#troubleshooting-of-sign-in


TDD

I suggest that, since we are starting with both a spec and and a reference implementation, we go the Test Driven Development route.
This raises the question, what test framework do we use? I'm most comfortable with unittest, but am entirely open to learning pytest or Nose.
Additionally, I was considering an essentially 3-branch structure: release, master, and unimplemented, where unimplemented holds tests for new features that have yet to be implemented. Upon those tests passing, master would receive both the tests and the code to pass them. That way, we can enforce an always-passing rule on master more easily.

Unittest works.
+1 3 branches + feature branches

Disagree. py.test offers many more features than unittest. Perhaps the most interesting is its concept of fixtures.
Check out setup.py ... it's already configured with py.test and Tox

There are several established approaches for managing branches/releases. Have you guys read the post from the Rust guys on the subject?

Normally I'd go the unittest + built-in mock route, but here we might need capabilities offered by pytest. I started using it recently and I like being able to run tests on multiple cpu cores.

A big issue I am running to testing my other massively p2p project is that a lot of important bugs don't show up until you have networks of 100+ nodes. We are going to need to make something like "fire up 1000 nodes and test for reach-ability in the network.

I think there's two seperate discussions here.  Can we

I think there's several separate discussions going on here.  Reviewing the comments so far I can call out the following items:

whether we should stick to just unittest and mock out of the standard lib or include a test runner like pytest or nosetests in the distribution.
if it's worth favoring a unit test-driven approach and whether or not everyone agree to this requirement
a call for an integration testing suite to catch bugs which cannot be identified by unit test suites (e.g. requiring 1000 nodes or more).

Regarding item no. 1, I personally like using a test runner like nosetests but am happy to stick to unittest and mock for development within the repo.
Regarding item no. 2, I'm personally strongly in favor of a strong test-driven development paradigm for our project.  I think we should definitely strive for a testable spec that both the golang and python implementation can strive for, and I think we should have our own unit tests, mocks, and possibly stubs in addition to that suite.
I think item no. 3 is really important, but might not be significant until this project has a little more momentum.  It seems like we're still working on an initial proof of concept and are deciding on the overall architecture of the project from what I can gather.  Once we can implement some subset of the ipfs spec, I think we should seriously consider these sorts of test scenarios.  I noticed that there's a weekly "testing + ci" sprint meeting in this document, maybe we can bring this concern up there and see what sort of resources might be available on that front.


Update README and CONTRIBUTING to use npm run start

The doc files both say to use npm run dev but dev is not a defined script in package.json. This small MR updates both to use npm run start which actually runs the project.

I think npm run dev is still a defined script in the package.json that is inside the example folder. It is there to run the examples vite project.


Make documentation easier to read

Please make the content box for the documentation bigger or the font smaller so the test is easier to read.

That is a bit of a mess isn't it...
I'll see what I can do - thanks!


Add prefix to constant name to avoid name conflicts

Fixes https://github.com/firebase/firebase-ios-sdk/issues/7635.

thanks. Any reason that the symbol is in a public header versus an internal header?

I guess the main reason is that the internal header didn't exist when the constant was added. I'm moving it to the internal header now.


Uploader-Password not working as expected

Not sure if I misunderstood the feature.
I have set an uploader password (MICROBIN_UPLOADER_PASSWORD) and enabled read-only mode (MICROBIN_ENABLE_READONLY) as described in the .env-file.
The microbin-UI then shows the "Uploader Password" field aside the Save-Button, but it does not seem to evaluate it when saving a post. In other words: even though the Uploader-Password is configured it lets me upload any data as if the MICROBIN_UPLOADER_PASSWORD is not configured.
I would expect it to deny upload of any type of post until I input the correct password.

I am facing the same issue on microbin 2.0.4. The feature would have been really useful as I do not wish for strangers to upload content to my server.

Level 3: Read-only
With this privacy setting, the upload cannot be found unless someone knows its unique, random identifier. If someone knows this identifier, they can see the contents but cannot modify or remove it without entering the password of the upload.

This is consistent with the description in the document, and what you expect should be using private. Although the document description is correct, it may not be intuitive. It may be a good idea to display the password input box when selected Privacy requires a password

oh, I see - seems then I did not understand that in detail .
could you still put my whish on the feature request list? So globally secure uploading/posting with a password - so that no one but the password-knowers can upload?

oh, I see - seems then I did not understand that in detail .
could you still put my whish on the feature request list? So globally secure uploading/posting with a password - so that no one but the password-knowers can upload?

I think I may understand what you need, what you need is to set the environment variable MICROBIN_READONLY to true, not MICROBIN_ENABLE_READONLY
If that's not what it's meant to be, sadly, I'm not the maintainer, I do not have the access to put it into the feature request list. But maybe I will fork a new repository to support this feature, if I have spare time.

The password required for uploading, if read-only mode is enabled
Default value: unset
export MICROBIN_UPLOADER_PASSWORD=

If set to true, authentication required for uploading
Default value: false
export MICROBIN_READONLY=false

@xeulife oops, I overlooked that you are not the maintainer :-D
well, I checked my config again and saw that I have the settings set to
MICROBIN_UPLOADER_PASSWORD="my secret"
MICROBIN_READONLY=false
MICROBIN_ENABLE_READONLY=true
anyway the restriction to upload only when password is given does not trigger. It shows the password-field but it is not checkend when posting. for me this now seems to be a bug. do you have thime to investigate the issue? maybe you could then provide the maintainer @szabodanika a bugfix 🥇

@xeulife oops, I overlooked that you are not the maintainer :-D
well, I checked my config again and saw that I have the settings set to
MICROBIN_UPLOADER_PASSWORD="my secret"
MICROBIN_READONLY=false
MICROBIN_ENABLE_READONLY=true
anyway the restriction to upload only when password is given does not trigger. It shows the password-field but it is not checkend when posting. for me this now seems to be a bug. do you have thime to investigate the issue? maybe you could then provide the maintainer @szabodanika a bugfix 🥇

Just try
MICROBIN_UPLOADER_PASSWORD="my secret"
MICROBIN_READONLY=true // it should be true

MICROBIN_READONLY should be true
If you find that the above actions are indeed not effective, I think it may be a bug.

oops again - should not write any reports on a monday
MICROBIN_READONLY is set to true already.
but I can upload without providing the password

oops again - should not write any reports on a monday
MICROBIN_READONLY is set to true already.
but I can upload without providing the password

I just tried the configuration and it works properly. A password upload box will appear on the left side of the Save button. If the password is incorrect, it will reject uploading anything and prompt "incorrect password". This is my deployment link, you can try it out:
<bin.xeu.life>
Here is my environment variable configuration
- MICROBIN_EDITABLE=true
      - MICROBIN_ENABLE_READONLY=true
      - MICROBIN_READONLY=true
      - MICROBIN_UPLOADER_PASSWORD=MySecret
      - MICROBIN_HIGHLIGHTSYNTAX=true
      - MICROBIN_PUBLIC_PATH=https://bin.xeu.life
      - MICROBIN_ENABLE_BURN_AFTER=true
      - MICROBIN_ENABLE_CUSTOM_URL=true
      - MICROBIN_PRIVATE=true
      - MICROBIN_SHOW_READ_STATS=true
      - MICROBIN_QR=true
      - MICROBIN_HASH_IDS=true
      - MICROBIN_ENCRYPTION_CLIENT_SIDE=true
      - MICROBIN_ENCRYPTION_SERVER_SIDE=true

Although I think the most critical configuration is only the following two lines, I still post the complete configuration for your convenience in debugging.
      - MICROBIN_READONLY=true
      - MICROBIN_UPLOADER_PASSWORD=MySecret

Since I copied the environment variable configuration directly from docker-compose.yml, it will contain some "-" symbols, so don't worry about them

I had the same issue. I figured it out, the problem is that
MICROBIN_UPLOADER_PASSWORD: ${MICROBIN_UPLOADER_PASSWORD}
is missing from the default compose.yaml. Add that and if you go to the admin page you'll see that it changes "uploader password" from "unset" to "set" and the tool behaves as expected.

I had the same issue. I figured it out, the problem is that  MICROBIN_UPLOADER_PASSWORD: ${MICROBIN_UPLOADER_PASSWORD}
is missing from the default compose.yaml. Add that and if you go to the admin page you'll see that it changes "uploader password" from "unset" to "set" and the tool behaves as expected.

cool, thanks! yes - this did the trick.

Something that has tripped me up for hours on this issue with the upload password being declined as incorrect, was my password contained the character $ inside of it. It's not the permission issue above, but could throw some people out badly if trying to diagnose this. A password should actually accept most special characters. I've seen some not accept a password that starts with a $ but this was also interesting.


Ci cache reset

Description
Reset cache on mac 3.7
Type of change
Nothing changed
References
https://github.com/napari/napari/issues/1527

I tested this on this branch to run on mac with python 3.7 (this change has been rolled back reset --hard)
When I tested it, CI was indeed rerunning pip install instead of using a existing matching, however I cannot guarantee this happens too on master, because branches was not running 3.7 before
Worst case scenario we would have to merge the 2 commits in this PR separately, which themselves individually are pretty harmless and cancels out each other anyway

upposedly we just need ci to think the build process is different, it looks like it uses a way to identify (during the PIP cache step it says it matches a hash) so ones we modify anything, the cache would be invalidated, so we are going to attempt change a harmless config flag (retry number) and trick ci to run the new flow and invalidate the existing cache, and maybe revert it if desired later

I wonder if @ziyangczi should look into the github actions proposal from @tlambert03 in #1307 as a long term approach.

fwiw, that branch is still mostly in good shape.  Just updated and tests are mostly passing: https://github.com/tlambert03/napari/runs/986291638?check_suite_focus=true
needs a bit of love on windows, and needs isort added to CI.  (and a discussion as to whether people are ok with using tox as I've done there, or prefer not to)

Unfortunately @ziyangczi this approach has not succeeded - see

What do you recommend @ziyangczi we try next?

I took a look at 1307, I think we should move forward with the migration, I can take over the branch if desired. I can help with the windows test part.
regarding tox, We can talk about it in the next meeting, I don't think it is a deal-breaker, I personally would hope we do not use a tool to facilitate testing on different environments because it introduced some complexity/dependency in ci, and can be tricky later if breaks, etc

regarding the cirrus ci fix, I think the most viable fix would be updating some dependency in our pip file to force a new dependency installation process. I can't find any doc from cirrus explaining how they match the pip cache so we can find a way to work around it or any tutorial to do so manually.

because it introduced some complexity/dependency in ci

would be curious to know what difficulties you ran into... I actually added it there because, combined with tox-gh-actions I found that it actually simplified testing on CI with a variety of environments (and as a bonus, makes it much easier to test a matrix of environments locally, such as testing both pyside/pyqt on py3.6-3.x just by running tox)

because it introduced some complexity/dependency in ci

would be curious to know what difficulties you ran into... I actually added it there because, combined with tox-gh-actions I found that it actually simplified testing on CI with a variety of environments (and as a bonus, makes it much easier to test a matrix of environments locally, such as testing both pyside/pyqt on py3.6-3.x just by running tox)

not any difficulties immediately, but in my opinion, that is too much magic for the CI setup.  If we need to test out on a matrix of setups, I would rather just flush out the code completely instead of trying to be smart and optimize it. I have had enough nightmares dealing with "smart" CIs, the pip cache is certainly the most recent one :)
That being said, though I would not be setting up such a thing in my own project, I don't think this is a deal-breaker that we need to bang out head in arguing whether to have it or not, we can improve our CI setup later anyway since this is nothing relevant to our "business model", I am more concerned about what is the difference in cost than the tox. Hoping github is nice enough to allow us using it for free?


fido2 various smaller improvements + credential-management-poc

added type hints for cli/fido2 and fido2/client
improved passing pin(s) to various cli/fido2 operations (to improve batch friendliness)
introduce fido2 resident-keys, which for now just returns the RPs and their owned RKs in an overview
some docs improved in cli/fido2

Thanks for adding type hints!  Can we now enable strict mode for these modules?

Quick sanity check:
Have you tested it on Python3.6?
Have you run make check or make fix for the formatting check?
Have signed commits?

 This is anyways far from ready to merge, just wanted something to compensate -.- pull-requested this early state so its transparent. Overall the plan was roughly like this:

type hinting for the fido2 module (why not having this in a separate PR, can do, np) (how about rebasing PRs btw. instead of merge, then this issue would be gone and a history w/o endless non-telling merge-commits would hold up its name ... ok other topic :dancers:  )
credential management (more details are still missing and deletion)
some love for pynitrokey.fido2.client, much is unsused, some redundant w.r.t. fido2.client
bonus: revive hashing (probe)
the "pin"-struggle, explicitly wanted to get into discussion here, let's define something.....now:

PINs

let's ignore special/corner cases i.e.,e.g., 2 pins needed for now
consistency should be the main goal
pins through env-vars is likely for more advanced ppl and on-top of all this
possible rule set as a starting point:

a pin is never mandatory to be passed as an argument (partly enforces the more secure hidden-prompt method)
a func(tion) must always know (before) if a pin is needed or not, if not sure the assumption has to be yes,
as otherwise this would brake the 1st rule (the user would have to pass it as arg)
no magic character or similar stuff (as done in this PR), the fact that a pin was not provided by the user is the pin variable equal to None,
means all pin types will be Optional[str]
no re-iterations on fail, this is a lib/cli

what did I miss? or is this it? anyways, this looks like this might accidentally also close #194 , cool let's go

Thanks for adding type hints! Can we now enable strict mode for these modules?

nope not yet, but soon[tm]

oops, yeah don't care for the commit mess, this branch will be on top of fido2-types, means typehints first. see #218 already extended the type-addition scope

let's ignore special/corner cases i.e.,e.g., 2 pins needed for now
consistency should be the main goal
pins through env-vars is likely for more advanced ppl and on-top of all this

We need only one PIN for FIDO2 though, so perhaps reusing "admin" PIN variable would be intuitive enough, as it allows for the write operations.

Regarding consistency, we plan already to unify interfaces for the common operations, which potentially would decrease the need for making separate UI for the each command and device combination.

While using automation, env variables are a safer alternative against providing PINs by the command line. I am for completely removing the latter.
 possible rule set as a starting point:
 a pin is never mandatory to be passed as an argument (partly enforces the more secure hidden-prompt method)
 a func(tion) must always know (before) if a pin is needed or not, if not sure the assumption has to be yes,
 as otherwise this would brake the 1st rule (the user would have to pass it as arg)
 no magic character or similar stuff (as done in this PR), the fact that a pin was not provided by the user is the pin variable equal to None,
 means all pin types will be Optional[str] and None by default
 no re-iterations on fail, this is a lib/cli

See my previous point - it clears most of the doubts.

No re-iterations are fine for the library, but why UX has to suffer in CLI?

No re-iterations are fine for the library, but why UX has to suffer in CLI?

+1.  (Of course this only applies to re-iterations without side effects and non-trivial run time costs.)

Bumping.
Let's merge what we have (or extract the credential management?), as long as it is usable, and discuss improvements further in the next ticket.
Do you think this one is ready @daringer @robin-nitrokey ?
If not, please make it a draft @daringer .

Bumping.
Let's merge what we have (or extract the credential management?), as long as it is usable, and discuss improvements further in the next ticket.
Do you think this one is ready @daringer @robin-nitrokey ?
If not, please make it a draft @daringer .

For me the only open issue with this PR is the pin handling.

I am first working on fido2-types once this is done - how can I make this a draft? can't find the button :dagger:

bump

this waits for to be merged first, fixing make check issues there currently ... https://github.com/Nitrokey/pynitrokey/pull/218

bump

these are a lot of changes for just a PR :/ is everybody ok with opening single PR for the changes? i.e. I'm interested in having verify accept a PIN, I'll carry https://github.com/Nitrokey/pynitrokey/pull/216/commits/e49fe1f0adf3bc717dfb665cf2a958b7f315effe and make it a PR

Was here the PIN acceptance fix for make-credential and other FIDO commands?
It still does not work with the current master ^^


Pull send docs to the top

It's a bit of a long scroll down the docs page to find how to actually send off a request. I think this is information that should be at the start of the docs, and it introduces the user to all the necessary types and some functions that they can then investigate further.

Yep, sounds great to me. Thanks!


Updated example of vue-apollo

Hello,
I've seen #504 and I've tried to tune the exemple to be working with latest version of vu-apollo (collect seems to be no longer working) and nuxt (other plugin injection format ?)
Review and information are welcome, and I don't know if this plugin injection is the right way to go on 1.x.
Thanks,

Codecov Report

Merging #1160 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #1160   +/-   ##
=======================================
  Coverage   98.67%   98.67%
=======================================
  Files          12       12
  Lines         679      679
=======================================
  Hits          670      670
  Misses          9        9

Continue to review full report at Codecov.

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

haha a bit too late, but i added some more: #1161

See https://github.com/nuxt/nuxt.js/issues/504#issuecomment-318389265


Run specs on macOS 11

Our macOS test jobs are pinned to 10.15 (#11282). We should test against macOS 11 as well, as soon as it works with nixpkgs (#11279).
A build matrix could be useful for that (see #11278).

Do we still need a matrix after #12570 and #13748? Is 11 even relevant?

It's probably okay to test against the latest version only.


SmartyPants: Smart punctuation for web sites

Support for Gruber’s smartypants would be great. It translates plain ASCII punctuation characters into “smart” typographic punctuation.
https://daringfireball.net/projects/smartypants/
Many markdown libraries implement this as an option.

It's trivial to do post-processing on the output of Showdown.


[+WATCH.]— Bad Boys: Ride or Die (.2024.) FuLLMovie Free Online on English

29 secs ago - [アニプレックス] While several avenues exist to view the highly praised film Bad Boys: Ride or Die online streaming offers a versatile means to access its cinematic wonder From heartfelt songs to buoyant humor this genre-bending work explores the power of friendship to upBad Boys: Ride or Diecommunities during troubling times Directed with nuanced color and vivacious animation lighter moments are blended seamlessly with touching introspection Cinephiles and casual fans alike will find their spirits Civil Wared by this inspirational story of diverse characters joining in solidarity Why not spend an evening immersed in the vibrant world of Civil War? Don't miss out!
~ Latst Update 09 June, 2024 ~
➤➤🔴📱 Watch Now ✅➤➤ Bad Boys: Ride or Die(2024) Fullmovie Online
➤➤🔴📱 Download Now ✅➤➤ Bad Boys: Ride or Die(2024) Fullmovie Online HD

Bad Boys: Ride or Die(2024) is a 1985 American epic coming-of-age period drama film directed by Steven Spielberg and written by Menno Meyjes, based on the Pulitzer Prize–winning 1982 novel of the same name by Alice Walker. It was Spielberg's eighth film as a director, marking a turning point in his career as it was a departure from the summer blockbusters for which he had become known. It was also the first feature film directed by Spielberg for which John Williams did not compose the music. The film instead featuring a score by Quincy Jones, who also produced. The cast stars Whoopi Goldberg in her breakthrough role, with Danny Glover, Oprah Winfrey (in her film debut), Margaret Avery, and Adolph Caesar.
Filmed in Anson and Union counties in North Carolina,the film tells the story of a young African-American girl named Celie Harris and the brutal experiences she endured including domestic violence, incest, child sexual abuse, poverty, racism, and sexism.
The film was a box office success, grossing $98.4 million against a budget of $15 million. The film received acclaim from critics, with particular praise going to its acting (especially Goldberg's performance), direction, screenplay, musical score, and production values. The film was nominated for 11 Academy Awards, including Best Picture, Best Actress for Goldberg, Best Supporting Actress for both Avery and Winfrey, and Best Adapted Screenplay, but did not achieve a single win. It also received four Golden Globe Award nominations, with Goldberg winning Best Actress in a Drama. In 2006, the American Film Institute ranked the film 51st on its list of most inspiring movies.
Despite the success, the film is a source of controversy with many criticizing the film for its negative depiction of African-American males who are all shown as brutally violent. The film was also criticized by some for being """"over-sentimental"""" and """"stereotypical"""".
WHEN AND WHERE WILL Bad Boys: Ride or Die(2024) BE STREAMING?
The new Bad Boys: Ride or Die(2024) prequel Bad Boys: Ride or Die(2024) will be available for streaming first on Starz for subscribers Later on the movie will also be released on Peacock thanks to the agreement between distributor Lionsgate and the NBC Universal streaming platform Determining the exact arrival date of the movie is a slightly more complex matter Typically Lionsgate movies like John Wick 4 take approximately six months to become available on Starz where they tend to remain for a considerable period As for when Songbirds Snakes will be accessible on Peacock it could take nearly a year after its release although we will only receive confirmation once Lionsgate makes an official announcement However Bad Boys: Ride or Die you wish to watch the movie even earlier you can rent it on Video on Demand (VOD) which will likely be available before the streaming date on Starz
WHERE CAN I STREAM THE ORIGINAL Bad Boys: Ride or Die(2024) MOVIES IN THE MEANTIME?
In the meantime you can currently stream all four original Bad Boys: Ride or Die(2024) movies on Peacock until the end of November The availability of Bad Boys: Ride or Die(2024) movies on Peacock varies depending on the month so make sure to take advantage of the current availability
HOW TO WATCH Bad Boys: Ride or Die(2024) 2024 ONLINE:
As of now, the only way to watch Bad Boys: Ride or Die(2024) is to head out to a movie theater when it releases on Friday, September 8. You can find a local showing on Fandango. Otherwise, you'll have to wait until it becomes available to rent or purchase on digital platforms like Vudu, Apple, YouTube, and Amazon or available to stream on Max. Bad Boys: Ride or Die(2024) is still currently in theaters Bad Boys: Ride or Die you want to experience all the film's twists and turns in a traditional cinema. But there's also now an option to watch the film at home. As of November 25, 2024, Bad Boys: Ride or Die(2024) is available on HBO Max. Only those with a subscription to the service can watch the movie. Because the film is distributed by 20th Century Studios, it's one of the last films of the year to head to HBO Max due to a streaming deal in lieu of Disney acquiring 20th Century Studios, as Variety reports. At the end of 2024, 20th Century Studios' films will head to Hulu or Disney+ once they leave theaters.
IS Bad Boys: Ride or Die(2024) MOVIE ON NETFLIX, CRUNCHYROLL, HULU, OR AMAZON PRIME
Netflix: Bad Boys: Ride or Die(2024) is currently not available on Netflix. However, fans of dark fantasy films can explore other thrilling options such as Doctor Strange to keep themselves entertained.
Crunchyroll: Crunchyroll and Funimation have acquired the rights to distribute Bad Boys: Ride or Die(2024) in North America. Stay tuned for its release on the platform in the coming months. In the meantime, indulge in dark fantasy shows like Spider-man to fulfill your entertainment needs.
Hulu: Unfortunately, Bad Boys: Ride or Die(2024) is not available for streaming on Hulu. However, Hulu offers a variety of other exciting options like Afro Samurai Resurrection or Ninja Scroll to keep you entertained.
Disney+: Bad Boys: Ride or Die(2024) is not currently available for streaming on Disney+. Fans will have to wait until late December, when it is expected to be released on the platform. Disney typically releases its films on Disney+ around 45-60 days after their theatrical release, ensuring an immersive cinematic experience for viewers.
IS Bad Boys: Ride or Die(2024) ON AMAZON PRIME VIDEO?
Bad Boys: Ride or Die(2024) movie could eventually be available to watch on Prime Video, though it will likely be a paid digital release rather than being included with an Amazon Prime subscription. This means that rather than watching the movie as part of an existing subscription fee, you may have to pay money to rent the movie digitally on Amazon. However, Warner Bros. and Amazon have yet to discuss whether or not this will be the case.
WHEN WILL 'Bad Boys: Ride or Die(2024)', BE AVAILABLE ON BLU-RAY AND DVD?
As of right now, we don't know. While the film will eventually land on Blu-ray, DVD, and 4K Ultra HD, Warner Bros has yet to reveal a specBad Boys: Ride or Dieic date as to when that would be. The first Nun film also premiered in theaters in early September and was released on Blu-ray and DVD in December. Our best guess is that the sequel will follow a similar path and will be available around the holiday season.
HERE'S HOW TO WATCH 'Bad Boys: Ride or Die(2024)' ONLINE STREAMING IN AUSTRALIA & NEW ZEALAND
To watch 'Bad Boys: Ride or Die(2024)' for free online streaming in Australia and New Zealand, you can explore options like gomovies.one and gomovies.today, as mentioned in the search results. However, please note that the legality and safety of using such websites may vary, so exercise caution when accessing them. Additionally, you can check Bad Boys: Ride or Die the movie is available on popular streaming platforms like Netflix, Hulu, or Amazon Prime Video, as they often offer a wide selection of movies and TV.
Mark your calendars for July 8th, as that's when Bad Boys: Ride or Die(2024) will be available on Disney+. This highly anticipated installment in the franchise is packed with thrilling action and adventure, promising to captivate audiences and leave them craving for more. Captivate audiences and leave them craving for more.
Here is a comprehensive guide on how to watch Bad Boys: Ride or Die(2024) online in its entirety from the comfort of your own home. You can access the full movie free of charge on the respected platform known as 123Movies. Immerse yourself in the captivating experience of Bad Boys: Ride or Die(2024) by watching it online for free.""
Heres How To Watch Bad Boys: Ride or Die(2024) Online FullMovie At Home
WATCH— Bad Boys: Ride or DieMovie [2024] FullMovie Free Online ON 123MOVIES
WATCH! Bad Boys: Ride or Die(2024) (FullMovie) Free Online
WATCH Bad Boys: Ride or Die2024 (Online) Free FullMovie Download HD ON YBad Boys: Ride or DieY
[WATCH] Bad Boys: Ride or DieMovie (FullMovie) fRee Online on 123movies
Bad Boys: Ride or Die(FullMovie) Online Free on 123Movies
Heres How To Watch Bad Boys: Ride or DieFree Online At Home
WATCH Civil War(free) FULLMOVIE ONLINE ENGLISH/DUB/SUB STREAMING
(Civil War) Full Movie Free online Bad Boys: Ride or DieFull Movie 123Movies Bad Boys: Ride or DieFull Movie online
Bad Boys: Ride or DieFull Movie youtube 123Movies Watch
Bad Boys: Ride or Die(2024) Movie Online Full Streaming at
Bad Boys: Ride or DiePelicula Completa
Bad Boys: Ride or Diebộ phim đầy đủ
Bad Boys: Ride or Dieหนังเต็ม
Bad Boys: Ride or DieKoko elokuva
Bad Boys: Ride or Dievolledige film
Bad Boys: Ride or Diefilm complet francais
Bad Boys: Ride or Diehel film
Bad Boys: Ride or Diecały film
Bad Boys: Ride or Dieपूरी फिल्म
Bad Boys: Ride or Die完整版
Bad Boys: Ride or Dieplena filmo
Bad Boys: Ride or Dieganzer film deutch
Bad Boys: Ride or Dieceo film serbija
Bad Boys: Ride or Diecely film zdarma
Bad Boys: Ride or Diefilm completo doblado
Bad Boys: Ride or Diecompleto italiano
Bad Boys: Ride or Diefree download mp4
Home 123Movies Bad Boys: Ride or Die2024 MP4/720p 1080p
HD 4K Hindi Tamil dubbed filmywap Watch Bad Boys: Ride or Die(Spider-Verse
Related Users Queries: Where can i watch Bad Boys: Ride or Die(2024) Bad Boys: Ride or Diestreaming date Bad Boys: Ride or Diereddit stream Bad Boys: Ride or DieFull Movie Bad Boys: Ride or DieFull Movie Bad Boys: Ride or DieFull Movie What demographic watches Bad Boys: Ride or Die? What is the plot in Bad Boys: Ride or Die? What characters are going to be in Bad Boys: Ride or Diemovie? How is Bad Boys: Ride or Diedoing in the box office? Bad Boys: Ride or Die—Watch Online At Home Watch Bad Boys: Ride or Die(2024) HD For Free Bad Boys: Ride or Diestreaming: watch online 'Bad Boys: Ride or Die': Where to Watch Online and Play [.WATCH.]full Bad Boys: Ride or Die(2024) FullMovie Free On Streamings Watch Bad Boys: Ride or Die2024 - Power Automate Ideas Bad Boys: Ride or Die| In Theaters & Streaming Now Watch Bad Boys: Ride or Die2024 (.FullMovie.) Free Watch Bad Boys: Ride or Die(Free) FullMovie Online At Home [.WATCH.] Bad Boys: Ride or Die(2024) FullMovie Free How to Watch Bad Boys: Ride or DieWATCH! Bad Boys: Ride or Die(FullMovie) Free Online Here’s How To Watch 'Bad Boys: Ride or Die’ Free Online At Home Where to Watch and Stream 'Bad Boys: Ride or Die’ Online WATCH Bad Boys: Ride or Die(FullMovie) Free Online on How to Watch 'Bad Boys: Ride or Die’ Online Bad Boys: Ride or Die(2024) [WATCH]—Bad Boys: Ride or DieOnline 'Bad Boys: Ride or Die': How To Watch Online Where to Watch Bad Boys: Ride or DieMovie Online Watch Bad Boys: Ride or Die2024 (.FullMovie.) Free Online on 123Movie How to Watch 'Bad Boys: Ride or Die’ Movie Online How to watch Bad Boys: Ride or Dieonline now: Peacock Bad Boys: Ride or Die- Online Game How To Watch Bad Boys: Ride or DieOnline And Stream Bad Boys: Ride or DieGame [Unblocked] | Play Online How to Watch Bad Boys: Ride or DieNow Play Bad Boys: Ride or DieGame Online How to watch Bad Boys: Ride or Die2024 Is it streaming? [WATCH-FREE] Bad Boys: Ride or Die2024 Full Movie Here’S HOW To Watch :: Bad Boys: Ride or Die:: OnLine Available in USA Bad Boys: Ride or Die~ (2024) FullMovie Watch 'Bad Boys: Ride or Die’ Online: A Guide to watch free at home [Where to Watch] Bad Boys: Ride or Die(2024) FullMovie Fr Bad Boys: Ride or Die(2024) Stream and Watch Online Bad Boys: Ride or Die- Bad Boys: Ride or Diewatch Bad Boys: Ride or Dieonline Full Movie free Bad Boys: Ride or DieGame Â· Play Online For Free How to stream Bad Boys: Ride or DieOnline for Free Watch Bad Boys: Ride or Dieonline: Netflix, Hulu, Prime & Disney+ How to watch Bad Boys: Ride or DieAt Home Free Bad Boys: Ride or Die4K HD Streaming Bad Boys: Ride or Die1080p Download How To Watch Bad Boys: Ride or DieHere’s Where To [WATCH]! Bad Boys: Ride or Die(2024) How to watch and stream Bad Boys: Ride or DieDownload Bad Boys: Ride or DieMP4 Parent reviews for Bad Boys: Ride or DieMovie When Will Bad Boys: Ride or Die(2024) Be Streaming On [Official] Watch! Bad Boys: Ride or DieFullMovie Free Bad Boys: Ride or Die2024 Full Movie Streaming¡ Bad Boys: Ride or Dieis playing now in theaters worldwide
(2024) Free Online Streaming at Home Watch Bad Boys: Ride or DieFree Online Streaming 123Movies Where Watch Spider-Man: Across the
Bad Boys: Ride or Die2024 Free Online Streaming At home 123Movies Bad Boys: Ride or Die(2024) Free: 'Civil War' Crosses $850 Million Globally in 10 Days.
Sale Hobe Dua Roilo
Bad Boys: Ride or Diefull movie
Bad Boys: Ride or Diedownload online on Reddit.T.hanks'HD

M ALL
### The Movie You are Looking for Is Available at watch4khd.com In Various Formats.


Setup staging flow

In the future it'd be nice to be able to work on the site and not worry about messing up actual user's data. To do so, we need a staging environment. Will require adding back the develop branch, which will essentially be the pre-release version of inquisitor. Branches will be made off develop and merged back into develop, and when it's time for a release a PR from develop to master will occur to bring in new features.

[ ] Bring back develop branch, setup branch protections, update contributing guidelines
[ ] Whenever a push/PR to develop happens, deploy to firebase hosting (master will continue to use gh-pages as the production hosting location)
[ ] To differentiate data, create another firebase project (import production to seed it). Inject the firebase config using env variables locally, and through github secrets/actions (just compress the config into a json string so its one var). Load the appropriate var based on whether its develop or master branch, then deploy

This way we can have a staging environment in which we can mess with data as much as we want without fear of accidentally deleting real user data. Will need more rigorous code review when pulling into master to make sure stuff doesn't break existing data.

Alternatively a simpler solution is writing instructions for using the Firebase Emulator. This way we don't need a staging environment as someone can test out exactly how it would work in production on their own machine, and an added benefit is that multiple devs can work in parallel without overwriting each others data (e.g. someone enables applications to test something and someone turns it off to test something else, with the emulator they can test everything locally).


fix(ngAnimate): close follow-up class-based animations when the same class is added/removed when removed/added

This patch ensures that if the same CSS class is added/removed within a
follow-up digest then the previous class-based animation is cancelled
beforehand.
Closes #11717

Landed as https://github.com/angular/angular.js/commit/db246eb701529b41049fc118908e528920f13b24


Track package size to provide valuable insight to developer

See https://github.com/ai/size-limit/issues/299#issuecomment-1308620699

Applicable to js-waku as well.

Applicable to js-waku as well.

We tracked in js-waku PRs. Already, what more are you thinking of?

I would add point to revisit how and what exactly we track in js-waku (I see core is tracked)
Another improvement I would introduce is this

I would add point to revisit how and what exactly we track in js-waku (I see core is tracked) Another improvement I would introduce is this, so that we will have a job failed at the over-the-budget change. This brings us into discussion what is an ideal size we'd like to have - additional research should be done.

Happy to track to revisit. size-limit does provide a similar feature, it's just not used.


Don't use skopeo inspect for non-canonical pull specs

skopeo inspect hits the /tags API which can be expensive
for registries to compute.  Quay.io recently changed how
they do rate limiting, and we started hitting this in OpenShift CI
jobs.
Since the machine-config-operator always provides canonical/digested
pull specs, the non-digested support is just for local developer
convenience.
And anyways, what we really should do is pull the image unconditionally
and then inspect it afterwards, we don't need all of the tag info.
Basically this PR ends up in a place where the non-canonical
path only loses out on the optimization of avoiding pulling the
image in the case where we already have that target.

Is there a double-negative issue in the PR/commit subject?  I think we want to skip skopeo inspect for canonical pull-specs, not non-canonical pull-specs.

Is there somewhere we can/should document the fact that with this PR pivot no longer uses skopeo at all?

Is there somewhere we can/should document the fact that with this PR pivot no longer uses skopeo at all?

Not sure why that'd matter?  The few people who should care are all reading this PR.

though it wouldn't be hard to just adjust the logic so we still do this in the developer case too right? I.e.

Since as noted above this isn't a hard error anymore, all we're avoiding is re-pulling the image and only when the sha256 would match, and if it does, why are you asking pivot to pull it?  Also I tested this PR manually in a few scenarios...fixes a pretty important issue, I don't think it's worth redoing just for that.

Ahh right, forgot about https://github.com/projectatomic/rpm-ostree/pull/1807.
/lgtm

Commit message is fixed, but PR subject still has the double-negative.


Added Namespace Background SVGs

Signed-off-by: Harshit Dandriyal<EMAIL_ADDRESS>Description
Added Namespace Background SVGs
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Why do we need another copy of these SVGs? Just use CSS to style the existing SVGs?

Ok, sounds good. In the past, I have recommend that we apply a framework:

.svg (color, logo only, no name)
<logo_white.svg (no color, white only, logo only, no name) - mandatory naming convention.
primary color in #HEX required
secondary color in #HEX optional

Ok, sounds good. In the past, I have recommend that we apply a framework:

.svg (color, logo only, no name)
<logo_white.svg> (no color, white only, logo only, no name) - mandatory naming convention.
primary color in #HEX required
secondary color in #HEX optional

okk, on it :+1:


Inference requires GPU

Inference on even one sentence (with the example code) fails. I used no GPU, and it seems the code doesn't support CPU inference, suppose it is better to note that if that is an expected behaviour.
[2019-10-22 08:57:51] [data] Loading SentencePiece vocabulary from file /cs/snapless/oabend/borgr/UEDIN2019/systems/model.restricted/vocab.spm
[2019-10-22 08:57:51] Error: Curand error 203 - /cs/snapless/oabend/borgr/UEDIN2019/systems/tools/marian-dev/src/tensors/rand.cpp:75: curandCreateGenerator(&generator_, CURAND_RNG_PSEUDO_DEFAULT)
[2019-10-22 08:57:51] Error: Curand error 203 - /cs/snapless/oabend/borgr/UEDIN2019/systems/tools/marian-dev/src/tensors/rand.cpp:75: curandCreateGenerator(&generator_, CURAND_RNG_PSEUDO_DEFAULT)
[2019-10-22 08:57:51] Error: Aborted from marian::CurandRandomGenerator::CurandRandomGenerator(size_t, marian::DeviceId) in /cs/snapless/oabend/borgr/UEDIN2019/systems/tools/marian-dev/src/tensors/rand.cpp:75
Aborted from marian::CurandRandomGenerator::CurandRandomGenerator(size_t, marian::DeviceId) in /cs/snapless/oabend/borgr/UEDIN2019/systems/tools/marian-dev/src/tensors/rand.cpp:75

Thanks for noting this! Marian works on CPU too, it needs to be compiled with make -DCOMPILE_CPU=on and then --cpu-threads needs to be added to the marian-decoder options.

Thanks for noting this! Marian works on CPU too, it needs to be compiled with make -DCOMPILE_CPU=on and then --cpu-threads needs to be added to the marian-decoder options.


List TIs/CBOs on the site and let applicants search for one

Many applicants would like help applying for programs, but can't find a TI/CBO who can help them. So add a page that lets them find CBOs they could work with.
MIBridges does this well.
This may require some UX -- what does that page look like? Who should maintain it?
Alternatively, we may just want to link out to a City of Seattle page that lists CBOs, since that's more likely to be actively updated and less likely to go stale.

this is probably a seattle specific thing right now and they can take this on, but p3 is reasonable for this

OIRA recommended using an approach similar to the work they did with CBOs to help clients apply for direct cash assistance. Working with OIRA to better understand outreach efforts, contracting, and reimbursement rates.

Reviewing with Digital Navigators to see if bandwidth and agreement to add contact info, by language, by CBO. Pending review on 2/22.

Ideas for adding Digital Navigators to Affordable Seattle AND CiviForm:
CiviForm - Digital Navigators.pdf

@ldinhcos FYI here is the FAQ item


Supporting Foundation: why it is not possible to do it seamlessly

So the newest version of Foundation depends on Apple's Combine and extends some types like NotificationCenter with convenience methods thet return Combine's Publishers like this:
extension NotificationCenter {

    public func publisher(
        for name: Notification.Name,
        object: AnyObject? = nil
    ) -> NotificationCenter.Publisher {
        // ...
    }
}

So the problem is that if now OpenCombine declares the same extension, the clients which import both Foundation and OpenCombine won't be able to call such functions because of how the mechanism of extensions work:
let pub = NotificationCenter
    .default
    .publisher(for: NSControl.textDidChangeNotification,
               object: filterField)
 // error: ambiguous use of publisher(for:object:)

This is why OpenCombine cannot be fully compatible with Apple's Combine.
We can provide ways to handle this, but it's not perfect, of course:

Function overloading — methods in extensions accept one additional argument that helps distinguish the overloads:
public struct OpenCombineNotificationCenterPublisher: Publisher {
    // ...
}

public enum OpenCombineNamespace {
    case openCombine
}

extension NotificationCenter {

    public typealias Publisher = OpenCombineNotificationCenterPublisher

    public func publisher(
        for name: Notification.Name,
        object: AnyObject? = nil,
        _ namespace: OpenCombineNamespace
    ) -> OpenCombineNotificationCenterPublisher {
        // ...
    }
}

which then would be called like this:
let pub = NotificationCenter
    .default
    .publisher(for: NSControl.textDidChangeNotification,
               object: filterField,
               .openCombine)

This is what, for example, PromiseKit does, but there's one pitfall: it doesn't work with properties.

Newtype exposed via property:
public struct OpenCombineNotificationCenter {
    public let underlying: NotificationCenter

    public func publisher(
        for name: Notification.Name,
        object: AnyObject? = nil
    ) -> Publisher {
       // ...
    }

    public struct Publisher: OpenCombine.Publisher {
        // ...
    }
}

extension NotificationCenter {
    var openCombine: OpenCombineNotificationCenter {
        return OpenCombineNotificationCenter(underlying: self)
    }
}

At call site it looks like this:
 let pub = NotificationCenter
    .default
    .openCombine
    .publisher(for: NSControl.textDidChangeNotification,
               object: filterField,
               .openCombine)

I'd personally took the second approach, but until we implement the fundamental functionality of Apple's Combine there's time to think on this.

There is another solution that resolves ambiguity:
let pub: OpenCombine.Publisher = NotificationCenter
    .default
    .publisher(for: NSControl.textDidChangeNotification,
               object: filterField)

Another way, which is not that appealing and would require lots of duplication is to replicate NotificationCenter in OpenCombine framework:
class NotificationCenter {
    public func publisher(
        for name: Notification.Name,
        object: AnyObject? = nil
    ) -> NotificationCenter.Publisher {
        // ...
    }
}

at call site it would look like:
import OpenCombine

let pub = OpenCombine.NotificationCenter
    .default
    .publisher(for: NSControl.textDidChangeNotification,
               object: filterField)

One way to remove dis-ambiguity can be using a proxy pattern.
public protocol OpenCombineExtensionsProvider {}
extension OpenCombineExtensionsProvider {
	public var oc: OpenCombine <Self> {
		return OpenCombine(self)
	}
}

public struct OpenCombine<Base> {
	public let base: Base
	fileprivate init(_ base: Base) {
		self.base = base
	}
}

extension OpenCombine where Base: NotificationCenter {
    public func publisher(
        for name: Notification.Name,
        object: AnyObject? = nil
    ) -> NotificationCenter.Publisher {
        // ...
    }
}

The you can call the same methods with namespace 'oc'.
let pub = NotificationCenter.default.oc.publisher(
	for: NSControl.textDidChangeNotification, object: filterField
)

Refer: https://github.com/ReactiveCocoa/ReactiveSwift/blob/master/Sources/Reactive.swift

@RahulKatariya the looks even better and more concise, thank you!
What I’m thinking about is to do this namespacing thing on Apple platforms, but on non-Apple platforms (Linux, Windows) also add extensions to the original types, since no Combine is present there, hence no ambiguity.

@broadwaylamb Adding extensions to original types for windows and linux would not give much benefit, just an extra maintenance and synchronization.
Most of the people using OpenCombine in a Swift Package will be supporting all the platforms - Apple, Linux and Window and will make use of one API. What I mean is, I don't think anyone would have the following checks in their code.
#if !os(Apple)
let pub = NotificationCenter.default.publisher(
	for: NSControl.textDidChangeNotification, object: filterField
)
#else
let pub = NotificationCenter.default.oc.publisher(
	for: NSControl.textDidChangeNotification, object: filterField
)
#endif

@RahulKatariya no, as a client you won't have to perform these checks.
I'm talking about this:
extension NotificationCenter {

    public var openCombine: OpenCombine<NotificationCenter> {
        return OpenCombine(self)
    }

#if !canImport(Combine)
    public func publisher(
        for name: Notification.Name,
        object: AnyObject? = nil
    ) -> NotificationCenter.Publisher {
        // ...
    }
#endif
}

As a client who targets Linux and, say, macOS prior to 10.15, you will always use:
let pub = NotificationCenter.default.openCombine.publisher(
	for: NSControl.textDidChangeNotification, object: filterField
)

If you target Linux and macOS 10.15 (or newer), since you don't have to link against OpenCombine on macOS, you will use:
let pub = NotificationCenter.default.publisher(
	for: NSControl.textDidChangeNotification, object: filterField
)

@broadwaylamb - This looks great 😎.


Scan distance not increasing for me

Long story short, the mod manages to add a node for the light switch (haven't tested drop ship yet though), but fails to increase the scan distance for any nodes. Tested one Dine for the Main Entrance scan, got nothing. Created a new save file and tested on the light switch, and found that the scan distance was not increasing.
There's a chance that this is down to my system, as I'm running LC on Linux through Proton-GE, but I've never seen a mod-specific bug show up under Proton.
Perhaps just an issue that's cropped up with v55? Attaching a BepInEx log with all log levels enabled in case it's helpful, but I didn't see anything noteworthy in it myself.
LogOutput.log

Hey!
I'm also running LC on Linux through Proton-GE.
I just pushed version 2.0.0, which should fix your issues :)

Looks like this update got the scan nodes mostly functional again. Still have a few issues, sadly.

The default 'Scan Distance Hard Limit' of 800 seems to be too low to see the main entrance from Experimentation's fence line. Setting it to the same value as the max distance settings fixes that though
The ship and entrance nodes are very inconsistent with how long they remain visible. In my quick testing tonight, they stayed on screen at most about 2 seconds, at worst not even half a second. Nodes also seem to decide individually how long they'll be visible, so the ship and entrance were each disappearing at different times each time.
Nodes inside the ship seem to completely ignore the distance increase

1 isn't a big deal, just a config tweak that makes sense to default low in order to avoid causing lag, but could debatably do with an increase to accommodate the larger maps like March.
Assuming 2 is a bug, what options would be available for me to provide more info to help track the issue down? I'd love to help resolve this and switch to using this instead of ShipScanRange, even if my main motivation is the light switch node.
I'm assuming 3 is intentional to avoid having a bunch of spam nodes show up when trying to find the ship, but personally I'd prefer to have those distances increased, even if it is just to find the light switch when someone hides it. I don't know if it's possible or feasible to make the inside-the-ship nodes only show up if the player is in the ship, so perhaps instead just increasing the max distance for them to roughly the length of the ship?

Looks like this update got the scan nodes mostly functional again. Still have a few issues, sadly.
1. The default 'Scan Distance Hard Limit' of 800 seems to be too low to see the main entrance from Experimentation's fence line. Setting it to the same value as the max distance settings fixes that though

2. The ship and entrance nodes are very inconsistent with how long they remain visible. In my quick testing tonight, they stayed on screen at most about 2 seconds, at worst not even half a second. Nodes also seem to decide individually how long they'll be visible, so the ship and entrance were each disappearing at different times each time.

3. Nodes inside the ship seem to completely ignore the distance increase

1 isn't a big deal, just a config tweak that makes sense to default low in order to avoid causing lag, but could debatably do with an increase to accommodate the larger maps like March.
Assuming 2 is a bug, what options would be available for me to provide more info to help track the issue down? I'd love to help resolve this and switch to using this instead of ShipScanRange, even if my main motivation is the light switch node.
I'm assuming 3 is intentional to avoid having a bunch of spam nodes show up when trying to find the ship, but personally I'd prefer to have those distances increased, even if it is just to find the light switch when someone hides it. I don't know if it's possible or feasible to make the inside-the-ship nodes only show up if the player is in the ship, so perhaps instead just increasing the max distance for them to roughly the length of the ship?

1 isn't a big deal, just a config tweak that makes sense to default low in order to avoid causing lag, but could debatably do with an increase to accommodate the larger maps like March.

I'll increase the default next Update :)

Assuming 2 is a bug, what options would be available for me to provide more info to help track the issue down? I'd love to help resolve this and switch to using this instead of ShipScanRange, even if my main motivation is the light switch node.

First of all... Are you moving? And are you using other Scan Mods?

I'm assuming 3 is intentional to avoid having a bunch of spam nodes show up when trying to find the ship, but personally I'd prefer to have those distances increased, even if it is just to find the light switch when someone hides it. I don't know if it's possible or feasible to make the inside-the-ship nodes only show up if the player is in the ship, so perhaps instead just increasing the max distance for them to roughly the length of the ship?

The scan distance of ship stuff is already quite big though?

First of all... Are you moving? And are you using other Scan Mods?

After first seeing that behavior, I switched to a modpack to only has bep and this mod installed, and standing in different spots to scan. The only movement that might've been happening is my camera

The scan distance of ship stuff is already quite big though?

I don't know how big they're supposed to be, but starting a new save for default ship layout and standing with my back against the landing lever, the scanner can't pick up the light switch or charging coil

After first seeing that behavior, I switched to a modpack to only has bep and this mod installed, and standing in different spots to scan. The only movement that might've been happening is my camera

I cannot reproduce this :/
The vanilla scan has a width attached to it, so you might be better off using one of the compatible scan mods.
I'd recommend GoodItemScan as it works best with this mod in my experience.

I don't know how big they're supposed to be, but starting a new save for default ship layout and standing with my back against the landing lever, the scanner can't pick up the light switch or charging coil

Well, they are supposed to be scannable in a radius of 6 units.
Which should be enough to find a hidden light switch quickly


Module not found: Error: Default condition should be last one

I'm trying to use this package in an Angular app and I'm encountering the following error:

Module not found: Error: Default condition should be last one

After doing some research online, I found this solution:
https://stackoverflow.com/a/76127619
I believe the issue comes from this commit (7f4e871). It seems like types should be placed before default:
https://github.com/Touffy/dl-stream/blob/7f4e871f594f4724fff30c77cc61e8c2241a4692/package.json#L6-L9

Thank you. The Node.js documentation does say "default" should always come last.

Just published.

Thank you. The Node.js documentation does say "default" should always come last.

Well that's odd. I just tried the new version you published and it works now :)

Why is that odd ? I merged your change.

The fact that Node.js documentation indicates that "default" should always be placed last, but doing so actually triggers an error.

Your bundler complained when "default" was not last. Your PR moved it to the end of the list and now you say your bundler is happy. So it's consistent with the docs.

Oh my bad, I misunderstood the docs. All good.


Fix delta trimming

I think perhaps the name convention for the keys changed?
This fix only looks at the last 3 hex characters of the key ...
that might not be correct.

The tests fail without #58
The test pass if js-ipfs is downgraded https://travis-ci.org/jimpick/peer-star-app/builds/437490138

That looks correct to me. Thanks @jimpick !

Thanks! Landed on v0.7.2.

Coming to think of it, I'm taking this back.
The delta prefix is /d:, followed by the hex sequence, zero-padded: https://github.com/ipfs-shipyard/peer-star-app/blob/master/src/collaboration/store.js#L100
@jimpick Is there something I'm not being here?

The old implementation was returning NaN and it only looked at 3 characters (non-hex).
It probably should look at all the characters in the hex sequence - I was just trying to fix it quickly without changing it too much. The hex sequence is more than 3 characters, some of them will get trimmed because of aliasing ... 3 characters gives us 4096 deltas. Right now, I'm not keeping that much history in the demos I'm trying to make work.

The problem was assuming decimal and using Number() instead of parseInt(s, 16). Should be:
const thisSeq = parseInt(key.toString().substring(3), 16)

This wasn't triggered because failing the delta extraction, the entire state would be sent.
Thanks for spotting this @jimpick !


<EMAIL_ADDRESS>

Yfhchcgxgfdg

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

ID: 144afccf-4ab9-bb34-957d-e86d3732d688
Version Independent ID: 863b80ff-f60a-e727-dc12-0d6aba937df6
Content: Azure Monitor overview
Content Source: articles/azure-monitor/overview.md
Service: azure-monitor
GitHub Login: @bwren
Microsoft Alias: bwren

@AsdfrGasd Hi, please provide more information about your issue. Thank you.

Due to the lack of actionable information in this issue we are going to close it out.
@MicrosoftDocs/azure-cxp-triage #please-close


DX: code grooming

Coverage remained the same at 91.902% when pulling 4d53238fdf594232c1e9d20936f5079a047ba4af on keradus:2.18_foo into 0e5b74046284b2a06f634e557737160435d6cab1 on FriendsOfPHP:2.18.


AttributeError: 'tuple' object has no attribute 'year'

Reporting error:
AttributeError: 'tuple' object has no attribute 'year'
Which can be reproduced with:
from dateparser.date import DateDataParser
DateDataParser().get_date_data('22nd July 2012')

Issue is present since merge of https://github.com/scrapinghub/dateparser/pull/50/files

@horva have you tried updating dateparser? Seems to be working fine for me.
In [8]: DateDataParser().get_date_data('22nd July 2012')
Out[8]: {'date_obj': datetime.datetime(2012, 7, 22, 0, 0), 'period': 'day'}

@horva Please check that your dateutil version is up to date with one in requirements.txt

Thanks @Allactaga updating dateutil fixed it.

I just installed dateparser module from master repo and can reproduce the bug with:
from dateparser.date import DateDataParser
DateDataParser().get_date_data('22nd July 2012')
I found out about the bug with a script like this:
record = "19 de Junio de 2006"
d = dateparser.parse(unicode(record))

Hi @garaged, seems to be working fine for me. Like advised above, please check your dateutil version in requirements.txt.
In [1]: from dateparser.date import DateDataParser

In [2]: DateDataParser().get_date_data('22nd July 2012')
Out[2]: {'date_obj': datetime.datetime(2012, 7, 22, 0, 0), 'period': u'day'}

In [3]: record = "19 de Junio de 2006"

In [4]: import dateparser

In [5]: dateparser.parse(unicode(record))
Out[5]: datetime.datetime(2006, 6, 19, 0, 0)

you are right, it works
I missed the fact that I should check dateutil version, I missread it as dateparser, so I knew I had the latest from git, but after your comment I took a look aht the requirements.txt file, and I had dateutil 2.2, after update to 2.4.x it worked as expected.
Thanks a lot !!
Max

Seems to be broken (again). My packages are up-to-date:
(env)~/D/Amazon-Review-Scraper ❯❯❯ pip freeze
...
dateparser==0.3.3
...
python-dateutil==2.5.0
...

But I get the same error:
(env)~/D/Amazon-Review-Scraper ❯❯❯ python
Python 2.7.11 (default, Dec 26 2015, 17:47:53)
[GCC 4.2.1 Compatible Apple LLVM 7.0.2 (clang-700.1.81)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import dateparser
>>> dateparser.parse('22nd July 2012')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/chris/Documents/Amazon-Review-Scraper/env/lib/python2.7/site-packages/dateparser/conf.py", line 80, in wrapper
    return f(*args, **kwargs)
  File "/Users/chris/Documents/Amazon-Review-Scraper/env/lib/python2.7/site-packages/dateparser/__init__.py", line 40, in parse
    data = parser.get_date_data(date_string, date_formats)
  File "/Users/chris/Documents/Amazon-Review-Scraper/env/lib/python2.7/site-packages/dateparser/date.py", line 343, in get_date_data
    language, date_string, date_formats, settings=self._settings)
  File "/Users/chris/Documents/Amazon-Review-Scraper/env/lib/python2.7/site-packages/dateparser/date.py", line 161, in parse
    return instance._parse()
  File "/Users/chris/Documents/Amazon-Review-Scraper/env/lib/python2.7/site-packages/dateparser/date.py", line 171, in _parse
    date_obj = parser()
  File "/Users/chris/Documents/Amazon-Review-Scraper/env/lib/python2.7/site-packages/dateparser/date.py", line 189, in _try_dateutil_parser
    self._get_translated_date(), settings=self._settings)
  File "/Users/chris/Documents/Amazon-Review-Scraper/env/lib/python2.7/site-packages/dateparser/conf.py", line 80, in wrapper
    return f(*args, **kwargs)
  File "/Users/chris/Documents/Amazon-Review-Scraper/env/lib/python2.7/site-packages/dateparser/date_parser.py", line 180, in parse
    date_obj, period = dateutil_parse(date_string, settings=settings)
  File "/Users/chris/Documents/Amazon-Review-Scraper/env/lib/python2.7/site-packages/dateparser/date_parser.py", line 163, in dateutil_parse
    return new_parser().parse(date_string, settings=settings, **kwargs)
  File "/Users/chris/Documents/Amazon-Review-Scraper/env/lib/python2.7/site-packages/dateparser/date_parser.py", line 40, in parse
    new_date = self._populate(res, default, settings=settings)
  File "/Users/chris/Documents/Amazon-Review-Scraper/env/lib/python2.7/site-packages/dateparser/date_parser.py", line 68, in _populate
    value = getattr(res, field)
AttributeError: 'tuple' object has no attribute 'year'

Hi @inkrement the error is because of python-dateutil version 2.5.0. Downgrading python dateutil to 2.4.2 should fix this.


No permissions to update docs.scipy.org

The content at http://docs.scipy.org/ is served from /srv/docs_scipy_org/doc/, which doesn't have the correct permissions for me to update it (and probably the same for the other user accounts).
This is very similar to gh-204. @Fleetside58, @dpinte could one of you have a look?
Permissions should be like for /var/www/html/, which is where http://scipy.org content is served from:
$ ls -l /var/www/html
total 312
-rw-rw-r-- 1 rgommers www-data  10463 Jun  8 10:54 about.html
-rw-rw-r-- 1 rgommers www-data   8684 Jun  8 10:54 bug-report.html
-rw-rw-r-- 1 rgommers www-data  15810 Jun  8 10:54 citing.html
...

rgommers@www:/var/www/html$ ls -l /srv/docs_scipy_org/doc/
total 16676
drwxr-xr-x  2 root root    4096 Mar 13 18:01 dev
-rw-r--r--  1 root root    3706 Mar 13 18:01 download.html
-rw-r--r--  1 root root  404489 Mar 13 18:01 error.html
drwxr-xr-x  2 root root    4096 Mar 13 18:01 external
drwxr-xr-x  2 root root   20480 Mar 13 18:03 _images
-rw-r--r--  1 root root   15690 Mar 13 18:01 index.html
lrwxrwxrwx  1 root root      12 Mar 13 18:01 numpy -> numpy-1.12.0
....

@rgommers looking at it now!

@rgommers can you try now? Permissions have been updated.

Thanks, that worked!


Cmake channel dependency fix

All CHANNEL_<NAME>_CLIENT and CHANNEL_<NAME>_SERVER variables are now dependent on CHANNEL_<NAME>
All dynamic channels are now dependent on CHANNEL_DRDYNVC

Reorder channels in channel/CMakeLists.txt to ensure drdynvc is loaded before any dynamic channel

@freerdp-bot test

@freerdp-bot test

@freerdp-bot test


how to use in Webpack 3

How to use  in Webpack 3? Is it  possible?
And how to use with spritesmith options in Webpack(for generate sprite png and scss files)

@rustam87
Yes, the plugin can be used with any version of webpack. You can see here how to configure any PostCSS plugin that will be used by webpack.


Checking aware of RFC landed!

https://amaranth-lang.org/rfcs/0061-minimal-streams.html

And streams are now in amaranth https://amaranth-lang.org/docs/amaranth/latest/stdlib/stream.html


Is it possible to streamline the requests more?

This looks a bit redundant and unnecessary. I suggest just returning the request itself, as it doesn't make a big difference and takes an unnecessary function away from the call stack:

Agreed, gonna write up some changes to simplify this. Thanks for pointing out the redundancy.

The client requests have been simplified in commit 93af83f96ebc053d643e5db10ed01a40b9800184.


Fix usage with commonjs modules

That would be a breaking change.
The code you have written is true only for babel-compiled scripts, while TypeScript has a different "default" behaviour.
First of all - what problem you are trying to solve?

I thought it was a universal solution.
For another configuration problem, I had a module that returned undefined, and I had a component {default: undefined, __esModule: true, ...} in React.

What about picking default when you sure you could do it, and using the old behavior in any other case?
loadedModule.__esModule ? loadedModule.default :  (loadedModule.default || loadedModule)

👍

Thanks!


Fix NodeGraph not displaying anything with Postgres datasource

Fixes: #78

Hope this falls under an acceptable maintenance update.

@ntap-fge @ntap-jbolle Could you please review? This is highly appreciated, thank you!

Ping @ntap-fge @ntap-jbolle @ntap-nmarco

That looks very neat! Kindly asking for a review @ntap-fge @ntap-jbolle @ntap-nmarco ❤

I think there is a quite high chance that we can adopt this in the early part of the next year.
I am sorry so far, but please give us a bot more time, as the patch needs to be reviewed and approved since it is related directly to Grafana.


Pagination events overriding internal handler

Current Behavior
If onPageChange is provided to Pagination by the user, it will take over the event and not update the page binding.
See discord discussion
Expected Behavior
The event handler passed in by the user should run along with the internal event code.
Steps To Reproduce
No response
Link to Reproduction / Stackblitz
No response
More Information
No response

I can throw a PR later today.

See also: https://github.com/skeletonlabs/skeleton/issues/3066#issuecomment-2555611065


Consider adding retries to ConfigWatch to increase resiliency.

Can retries increase the resilience of ConfigWatch? Specifically to retry on any random network failures.  If this exception below is thrown and no other KV change occurs, the original KVs from the one event never get applied.  In many cases, a retry attempt would help app instances achieve the desired state.
2018-06-20 22:54:59.767  WARN 10994 --- [ask-scheduler-4] o.s.cloud.consul.config.ConfigWatch      : service [c1d4e514022e6f2f] Error querying consul Key/Values for context 'config/application/'. Message: org.apache.http.conn.HttpHostConnectException: ...

Thanks all,
Terry

so, it's on a scheduled executor right now, how different is that than retry? Not saying retry is a bad option.

The difference, if not mistaken, is that if publish event fails there is no retry.  Next time the scheduled index check happens it has not changed so things remain in a bad state.  I believe adding retry logic in this section will all things to heal in case of a 404 or connection refused.  Next week at some point I'll try to reproduce the issue in a testcase.  Perhaps I'm mistaken here.  Thanks.
https://github.com/spring-cloud/spring-cloud-consul/blob/master/spring-cloud-consul-config/src/main/java/org/springframework/cloud/consul/config/ConfigWatch.java#L157

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Highlights in scripture pane do not persist when done in a newly added row and Original Quote is not saved

Steps to replicate:

Add a new row. Select and copy a Hebrew word from the scripture pane and paste it in the OriginalQuote.
Tab out of it, Note that the Text is not highlighted.
Save it. It does not highlight.

When done on the regular row, this works fine and the highlights show up.

This now works for Hebrew and Greek when adding highlights for a new row in both OT/NT books.
Tested on 0.9.0-rc.1

Works fine in 0.9.0-rc.1. The highlights are shown in the scripture pane when OriginalQuote matches the Greek text for a newly added row.

Has this been fixed implicitly?

Found during meeting with Zach, the highlight works on some notes which already had highlight in the mother note(from which the new row is added), otherwise it does not.
Works fine with existing note with hightlight:-

Look for a Note that has a highlight.
Add a new row from that Note.
Copy and paste Original Language text to OriginalQuote. The highlight works fine.

Problem with Notes with no highlight:-

Look for a Note that does not  have any highlight.
Add a new row from that Note.
Copy and paste Original Language text to OriginalQuote. The highlight does not show up.

e.g., Mark 1:4 in TN

@elsylambert , we found that the "notes with no highlight" issue is due to the occurrence field being cloned.
If no highlight, then occurrence defaults to 0.
changing occurrence to 1 makes highlighting work as normal.
we recommend that this is not a bug, since it is working as normal.
however, @klappy  recommends we add a feature for overriding the default values on new rows:

datatable-translatable new feature: allow default values
tc-create-app enhancement: specify particular default values (specifically, occurrence =1/etc)

Verified on translationCore Create - v1.0.0-beta.9. Highlights work on a new row and able to save the note correctly. Highlights depends on Occurrence Number. When adding a new row, Occurrence number has to be 1 for highlights to show up.
Separated the new feature suggestion to #205.


[Snackbar] Add ClickAwayListenerProps property

Adding feature ClickAwayListenerProps property to Snackbar.
Closes #12727

@tendermario It's a great first pull request on Material-UI 👌🏻. Thank you for giving it a shot!


menu width

Hi,
how is it possible to set the width of the menu?

found it, it's possible by setting contentViewInPortraitOffsetCenterX


Is Material-ui 1.0 alpha supported?

Im getting this error when I try to use it, is there another version that has correct bindings for that version of material-ui?
 in ./~/formsy-material-ui/lib/FormsySelect.js
 Module not found: Error: Can't resolve 'material-ui/SelectField' in '/Users/cvillalta/Proyects/admin8/node_modules/formsy-material-ui/lib'
  @ ./~/formsy-material-ui/lib/FormsySelect.js 17:19-53

Material UI 1.0 is still on alpha release. We're not going to chase supporting those quick iteration tags. Let's re-open when a stable version gets released.


Edges are created in the wrong direction

When an edge is created following the documentation, the edge is created in opposite direction. Steps to reproduce:
Create two vertices
select * from cypher('test_graph', $$CREATE (a:Person {id:1}) return a$$) as (a agtype);
                                      a
------------------------------------------------------------------------------
 {"id":<PHONE_NUMBER>842625, "label": "Person", "properties": {"id": 1}}::vertex
(1 row)

select * from cypher('test_graph', $$CREATE (b:Person {id:2}) return b$$) as (b agtype);
                                      b
------------------------------------------------------------------------------
 {"id":<PHONE_NUMBER>842626, "label": "Person", "properties": {"id": 2}}::vertex
(1 row)

Create an edge between the vertices. If the edge is returned, it is already clear the edge has the opposite direction.
select * from cypher('test_graph', $$MATCH (a:Person {id:1}), (b:Person {id:2}) CREATE (a)-[e:knows]->(b) return e$$) as (e agtype);
                                                              e
------------------------------------------------------------------------------------------------------------------------------
 {"id":<PHONE_NUMBER>553287, "label": "knows", "end_id":<PHONE_NUMBER>842625, "start_id":<PHONE_NUMBER>842626, "properties": {}}::edge
(1 row)

When querying the graph for the edge in the wanted direction, no results are returned.
select * from cypher('test_graph', $$MATCH (a:Person {id:1})-[e]->(b:Person {id:2}) return e$$) as (e agtype);
 e
---
(0 rows)

When querying the graph for the edge in the opposite direction, the edge is returned as a result.
select * from cypher('test_graph', $$MATCH (a:Person {id:2})-[e]->(b:Person {id:1}) return e$$) as (e agtype);
                                                              e
------------------------------------------------------------------------------------------------------------------------------
 {"id":<PHONE_NUMBER>553287, "label": "knows", "end_id":<PHONE_NUMBER>842625, "start_id":<PHONE_NUMBER>842626, "properties": {}}::edge
(1 row)

I am unable to reproduce this in the latest version -
psql-11.5-5432-pgsql=# drop extension age; create extension age; load
'age'; set search_path TO ag_catalog;
ERROR:  extension "age" does not exist
CREATE EXTENSION
LOAD
SET
psql-11.5-5432-pgsql=# SELECT create_graph('test_graph');
NOTICE:  graph "test_graph" has been created
create_graph
(1 row)
psql-11.5-5432-pgsql=# select * from cypher('test_graph', $$CREATE
(a:Person {id:1}) return a$$) as (a agtype);
a
{"id":<PHONE_NUMBER>31969, "label": "Person", "properties": {"id": 1}}::vertex
(1 row)
psql-11.5-5432-pgsql=# select * from cypher('test_graph', $$CREATE
(b:Person {id:2}) return b$$) as (b agtype);
b
{"id":<PHONE_NUMBER>31970, "label": "Person", "properties": {"id": 2}}::vertex
(1 row)
psql-11.5-5432-pgsql=# select * from cypher('test_graph', $$MATCH (a:Person
{id:1}), (b:Person {id:2}) CREATE (a)-[e:knows]->(b) return e$$) as (e
agtype);
e
{"id":<PHONE_NUMBER>842625, "label": "knows", "end_id":<PHONE_NUMBER>31970,
"start_id":<PHONE_NUMBER>31969, "properties": {}}::edge
(1 row)
psql-11.5-5432-pgsql=# select * from cypher('test_graph', $$MATCH (a:Person
{id:1})-[e]->(b:Person {id:2}) return e$$) as (e agtype);
e
{"id":<PHONE_NUMBER>842625, "label": "knows", "end_id":<PHONE_NUMBER>31970,
"start_id":<PHONE_NUMBER>31969, "properties": {}}::edge
(1 row)
psql-11.5-5432-pgsql=#
On Mon, Sep 27, 2021 at 7:53 AM Pieterjan De Potter <
@.***> wrote:

When an edge is created following the documentation, the edge is created
in opposite direction. Steps to reproduce:
Create two vertices
select * from cypher('test_graph', $$CREATE (a:Person {id:1}) return a$$) as (a agtype);
a
{"id":<PHONE_NUMBER>842625, "label": "Person", "properties": {"id": 1}}::vertex
(1 row)
select * from cypher('test_graph', $$CREATE (b:Person {id:2}) return b$$) as (b agtype);
b
{"id":<PHONE_NUMBER>842626, "label": "Person", "properties": {"id": 2}}::vertex
(1 row)
Create an edge between the vertices. If the edge is returned, it is
already clear the edge has the opposite direction.
select * from cypher('test_graph', $$MATCH (a:Person {id:1}), (b:Person {id:2}) CREATE (a)-[e:knows]->(b) return e$$) as (e agtype);
e
{"id":<PHONE_NUMBER>553287, "label": "knows", "end_id":<PHONE_NUMBER>842625, "start_id":<PHONE_NUMBER>842626, "properties": {}}::edge
(1 row)
When querying the graph for the edge in the wanted direction, no results
are returned.
select * from cypher('test_graph', $$MATCH (a:Person {id:1})-[e]->(b:Person {id:2}) return e$$) as (e agtype);
e
(0 rows)
When querying the graph for the edge in the opposite direction, the edge
is returned as a result.
select * from cypher('test_graph', $$MATCH (a:Person {id:2})-[e]->(b:Person {id:1}) return e$$) as (e agtype);
e
{"id":<PHONE_NUMBER>553287, "label": "knows", "end_id":<PHONE_NUMBER>842625, "start_id":<PHONE_NUMBER>842626, "properties": {}}::edge
(1 row)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-age/issues/119, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALPO4C4PXKKLCG3J6YB25LUECAOXANCNFSM5E2YH6UQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thank you for your quick responses. I am unable to reproduce the issue on a new virtual machine as well.
On my existing virtual machine (Debian buster), the issue occurred with 23ec457c951553994efa7ae9111d7761118a0270, v0.6.0 (3681c90da68353507001db89eb429755d34857f7) and the current master (fa5782f0f03e8172c5f367ad68794756593c18b0).
I managed to fix the issue on my existing virtual machine by uninstalling Apache AGE, uninstalling (purge) postgresql-11 and re-installing everything.


Bitso implementation

Anyone doing Bitso yet? If not, I might implement parts of it in the near future (just the Ripple Gateway parts, ie. Ripple/Bitcoin withdrawal and probably Bitcoin deposit address).

Documentation: https://bitso.com/api_info

No one is doing it that I'm aware of.

Implementing Bitso is simple since their API is largely compatible with Bitstamp's. Here's the general recipe for implementation that worked for me:

Copy the Bitstamp classes
Search/replace bitstamp -> bitso
Search/replace usd -> mxn
Remove what Bitso doesn't support
Some tweaking (eg. some methods that return boolean with Bitstamp return "ok" string with Bitso).
Test.

Authentication using API keys is already implemented in my initial PR.
I found the Bitso technical team very helpful and quick to respond.
So all in all, completing this implementation should be a straightforward and easy task.

This is done now?

This is mostly done (PollingMarketDataService.getTrades implementation is still missing though).


Release 2.4.1 version.

try to fix that we cannot find ngx_tongsuo_module in previous release 2.4.0 https://github.com/alibaba/tengine/issues/1784


docs: Reverts index page content

@mircubed I discussed this with @shykes and he's fine with it, can you please approve it so I can merge? Thanks.


TODO in code

https://github.com/Lambda-School-Labs/djhelper-fe/blob/bcf03d7fc3ba8ca1266062f255a6172dcbe11b8d/src/tests/App.test.js#L51

The commented-out code is now removed from App.test.js


Add matchings_path option to be used alongside disassemble_all

I found that disassemble_all was a great addition that made it pretty easy to quickly use or analyze the original assembly of an already matched function. That said, it splits the assembly for matching functions to the nonmatching path. While this isn't a big deal, I do think it is a determent to organization, and may possibly conflict with some makefiles or progress scripts which blindly scan the nonmatching folder.
This PR adds an option that works alongside disassemble_all, where if a function is a global asm func, and if disassemble_all is true, it will be split to the directory pointed to by a new variable matchings_path. I set the default value of this variable to matchings.
Besides being a solution to the problems I listed earlier, this might also have the benefit of giving the user more options to determine matching progress, and maybe more stuff I haven't considered.

I OK'd the unit test by adding an empty matchings directory in the expected build directory, and ignoring the .gitkeep file in the directory comparison. Might be more ideal to add a matching function in the split, though

it looks like there's some formatting issues. could you try running black locally to fix those? if that doesn't work, it might be due to a version mismatch..

Looks like it's still failing. The version of black I have seems to be black-24.4.2

wait I just forgot test.py my bad

Could you mention this new option in the changelog?


Add support for X-RateLimit-Bucket

See:

https://github.com/discordapp/discord-api-docs/issues/981
https://github.com/discordapp/discord-api-docs/pull/1005

Also see https://gist.github.com/z64/939560261b16dfb68fa4aef9a2979688

Given the recent changes to 401/403/429 behaviour, this seems a lot more important to add now. See ex. https://discordapp.com/channels/81384788765712384/381887113391505410/609899398469648396 in DAPI


wip: ci: add step to push to aws ecr too

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
This PR adds a job to build and publish a container image to AWS public ECR registry.
Which issue(s) this PR fixes:
NONE
Special notes for your reviewer:
We try to make OCI artifacts highly available by hosting them on different public registries like Docker Hub and AWS ECR.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

fa326ae ci: add step to push to aws ecr too

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: maxgio92
To complete the pull request process, please assign nibalizer after the PR has been reviewed.
You can assign the PR to them by writing /assign @nibalizer in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, maxgio92
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

This is a work in progress, as the AWS ECR repositories need to be in place before trying to push images to them.


Additional app-fixes [artv3/appfixes]

This PR fixes minor things in MFEM needed in applications running on GPUs.

Merging directly since the target branch is not master.


tvOS compatibility possible?

Is your feature request related to a problem? Please describe.
It's not really a problem but I'm just porting my iOS app to tvOS and I was surprised that this library doesn't work on tvOS. Is there any specific reason for that?
Describe the solution you'd like
To be able to use this lib on tvOS apps.
Describe alternatives you've considered
Only other solution is to not use AlertToast on tvOS and build the view in a different way.
Additional context
I just finished porting my Android app to iOS so some of the Apple stuff is still new to me. If it is obvious why this lib can't work on tvOS I'm sorry for creating this ticket.

Hey @grill2010 ,
This is definitely a feature that I would add in the future.
Currently, I don't have enough time to create it so I'll close this issue and reopen it once it becomes more relevant.


(PEAR-1810): disable buttons while loading for Analysis cards and Cases View

Description

disable buttons while loading for Analysis cards
disable buttons while loading for Cases View

Checklist

[na] Added proper unit tests
[na] Left proper TODO messages for any remaining tasks
[na] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)

The two areas changed work fine for me. 👍
Qn: did you find other areas of the portal where a user could click on a button before the data has finished loading and it results in some error or incorrect data being downloaded? E.g. TSV button above Repository's big table?

@wteouchicago added disabled to a lot of tsv and json buttons, also refactored Cases View ones

looks good -- thanks for adding the remaining ones! 👍