upgrade longhorn from 0.5.0 to 0.6.2 breaks on kubernetes 1.16.2

On rancher 2.3.2 apps, click upgrade available (0.6.2) and upgrade longhorn, I get a error
Failed to install app longhorn-system. Error: UPGRADE FAILED: failed decoding reader into objects: [unable to recognize "": no matches for kind "DaemonSet" in version "apps/v1beta2", unable to recognize "": no matches for kind "Deployment" in version "apps/v1beta2"]

The cluster is kubernetes 1.16.2. How to resolve this problem?

I don't why we can upgrade Longhorn from v0.5.0 to v0.6.2 in Kubernetes v1.16... Since Longhorn starts to support Kubernetes v1.16 in version v.0.6.0+. Could you provide more info about that?

@shuo-wu My kubernetes upgrade from 1.14.2 to 1.16.2, but there is no any tips I must upgrade longhorn before upgrade kubernetes, so I made this error. On another cluster I upgrade longhorn before upgrade kubernetes, it works fine.

OK. We will be careful about it next time.

@shuo-wu How do I fix this problem?

Actually, the error is caused by the Helm.
There are two ways to solve it:
2.1. Use kubectl apply -f https://raw.githubusercontent.com/longhorn/longhorn/v0.6.2/deploy/longhorn.yaml --force to upgrade your Longhorn system to v0.6.2.
2.2 I just found that this doc also worked for this issue.


Components

In this repository:

I used Git flow
Add linters configuration
Setup a new React application using [Create React App]
Created a directory for your reusable components: /components.
Installed React Router V6
Setup your router inside of
Add 2 routes that render a page component:

/
/categories

Created components inside of the src /components directory:

Contains individual book state, as well as a button to delete the book
Contains a list to renders individual books
Contains a form to create new books

Created components inside of the src /routes directory:

Contains a navigation to link to the 2 routes i created

Thank you for your review

Thank you


Got no connection errors when using autoconnect: true

This might be a misconception by me.
We noticed when we use autoconnect: true our Observable chain does not get any error callbacks when we are connecting. We have the following problem: We want to always reconnect as quickly as possible when connection is disrupted, however when the user connects the first time (with an action, like a button click), we want to show an error first and let him connect again.
rxBleDevice.establishConnection(true)
       .retryWhen { errorObservable ->
            return errorObservable.flatMap { error ->
               // we only get errors here with autoconnect: false, not true

               // decied to retry etc...
               return@flatMap Observable.error<RxBleConnection>(error)
            }
       }

Now it's already mentioned autoconnect might be confusing. From what I understand the problem is that the establishConnection never emits a connection observable, because a connection is never established.
Is there a way to handle errors that happen before a connection is created?
Note: The error occuring is not important for me here, Im only concerned about handling errors (before a connection is established)

What errors are you expecting?

GATT_ERROR 133, when I remove the battery from the device while connecting.

You probably won't get it when using autocorrect as the Android will continue until connection is successfully made

If you want to have a 30 second timeout then you should use autoconnect=false.
Why do you want to use autoconnect=true?

Closing due to lack of information and inactivity of the original poster.
When more data will be available—feel free to add that information and reopen this issue.
Best Regards


Clothes update

About the PR
Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

add: Added fun!
remove: Removed fun!

![markedwindbreaker](ht

tps://github.com/Nyanotrasen/Nyanotrasen/assets/121322002/0eea3fec-51dc-4045-b594-7da34a8b9ec2)

It's giving me rsi errors for unrelated items to the pr, I will look into it this weekend


Add piechart part

The original pie chart shows only the distribution among used and to-be-used tokens.
We add a unused (spare) tokens part, to give users a clear view of their context usage and remaining dialogue spaces.
Example pie chart below:

closed in favor of #102


Adding new Timestamp(rowversion) fields to temporal table with existing historioc changes not working

EF core does not append "NULL" to the generated sql script to add the new Timestamp(rowversion) column.
So if the table is system-versioned, and if it already has some changes made (saved in the history table), the db migration created for this schema change will not work.
Even "nullable" is sepefically set to true it does not create a nullable rowversion column. However, the history table set this column to Not Null by default. The primary table can work because it generates the value automatically for this column, but history table doesn't
Steps to reproduce

run ef core migrations to create a new table
run ef core migrations to conver the table to temporal table
ef database update
add a new row to the table
update the row so it adds rows to history table
alter the model to add a new Timestamp(rowversion) field
run ef core migrations to reflect the schema change
run ef database update to apply the change

Further technical details
EF Core version: 1.1.1
Database Provider: (Microsoft.EntityFrameworkCore.SqlServer)
Operating system:  (Visual Studio 2017)

Possibly fixed with #8146

Issue:
rowversion is by default non-nullable in SqlServer. It will be made nullable only when you specify NULL in declaration. Even with the NULL, when you add column with rowversion to existing table, SQL Server will add values for existing records. Hence nullable rowversion column is considered NOT useful.
For temporal tables, the main table acts same as normal table so can have just rowversion but history table is only inserted & never updated (perhaps SQL Server does not allow updates to it) hence it cannot insert values and hence needs nullable column.
ALTER TABLE only allows columns to be added that can contain nulls, or have a DEFAULT definition specified, or the column being added is an identity or timestamp column, or alternatively if none of the previous conditions are satisfied the table must be empty to allow addition of this column.

Fixed via #8146

We can report this to SqlServer team.


Proposal: workbox-clear-storage

Motivation
Any well-planned service worker production rollout should include steps for rolling back service worker functionality and clearing out cached data, to deal with a vulnerability or unintended behavior that can't be dealt with via a simple remediation. This "kill switch" behavior is best planned ahead of time, in a well-thought-out fashion, instead of attempting to implement something in an ad hoc fashion while in the middle of a production issue.
There are some existing recipes for implementing "kill switches," including this popular Stack Overflow answer. While that approach is a straightforward solution, involving as little as deploying a few lines of code in a special-purpose service worker file, more comprehensive solutions—involving, e.g., clearing out cached data across various storage mechanisms—are necessarily more involved.
The logic of implementing "kill switch" behavior from the context of the ServiceWorkerGlobalScope is also different from how you'd implement the same thing inside of the WindowGlobalScope (i.e. web app)'s scope, and both types of uses are valid for different scenarios.
For these reasons, it would make sense for Workbox to ship a new module, tentatively named workbox-clear-storage, that could be used either from the ServiceWorkerGlobalScope or the WindowGlobalScope, which would provide a way of both unregistering service workers and providing  fine-grained control over clearing out multiple types of storage across the entire origin.
Naming
I'm not keen on using the "kill" terminology as part of a module name. My current thinking is workbox-clear-storage. Alternative names I've considered are workbox-clear-data or workbox-clear-site-data, but the functionality isn't quite the same as what the Clear-Site-Data: header offers, so I don't want to confuse folks.
Proposed API
The API is designed around the idea of giving developers fine-grained control over what gets deleted/unregistered, while defaulting to a maximal "delete as much as possible" approach.
For each type of storage you might want cleared, you'd supply an async predicate function that would determine whether a specific "unit" of that storage should be deleted or not, with that unit's id passed in as a parameter. Each type of storage would have its own id values; for cacheStorage, for instance, the id would be each cache name, while for serviceWorkerRegistrations, the id would be the scriptURL associated with the service worker registration.
The return value of the single public method would summarize what was actually deleted, allowing web applications to take specific actions depending on what ended up being cleared out. For instance, a web app might want to redirect itself to a login page upon completion of the "kill switch" if it sees that there was a specific service worker registration that was previously active and is now removed.
interface AsyncPredicateFunction {
  (id: string): Promise<boolean>;
}

interface ClearOptions {
  cacheStorage?: AsyncPredicateFunction;
  serviceWorkerRegistrations?: AsyncPredicateFunction;
  cookies?: AsyncPredicateFunction;
  indexedDB?: AsyncPredicateFunction;
}

interface StorageToItems {
  cacheStorage: Array<string> | null;
  serviceWorkerRegistrations: Array<string> | null;
  cookies: Array<string> | null;
  indexedDB: Array<string> | null;
}

interface ClearReturnValue {
  cleared: StorageToItems,
  failures: StorageToItems,
}

// For any property in ClearOptions that's undefined,
// default to `async (id) => true`
function clear(options: ClearOptions = {}): Promise<ClearReturnValue>;

The usage would look like:
const {cleared, failures} = await clear({
  // Only delete caches that include "workbox" in their name.
  cacheStorage: async (id) => id.includes('workbox'),

  // Delete all service worker registrations.
  serviceWorkerRegistrations: async (id) => true,

  // Don't delete any cookies.
  cookies: async (id) => false,

  // Omitting indexedDB would be equivalent to the default:
  // indexedDB: async (id) => true,
});

for (const [storageType, items] of Object.entries(failures)) {
  if (items === null) {
    console.warn(`Unable to clear ${storageType} in the current browser.`);
  } else {
    console.warn(`Could not delete the following items from ${storageType}:`, items);
  }
}

if (failures.indexedDB === null) {
  // Manually clean up IndexedDB on browsers that don't support
  // iterating over DB names.
}

if (cleared.serviceWorkerRegistrations.length > 0) {
  // Do something if there was at least one SW registration deleted.
}

if (cleared.indexedDB.includes('my-indexedb-name')) {
  // Do something if there was an IndexedDB with that database
  // name that was deleted.
}

Open questions
Handling missing APIs
Cookies aren't widely available from inside of service workers (modulo this origin trial.) Iterating over a list of IndexedDB databases also isn't widely supported. This means there will be users for whom the module just isn't able to attempt to clear cookies or IndexedDB.
Right now, the idea is to reflect that by returning null for a given storage type in the failures return value. This at least lets the developer know that nothing was cleared out, but it's up to the developer to then follow-up with some manual steps to, e.g., clear cookies via the WindowGlobalScope.
id values
It might make sense to use more complicated id values for certain types of predicate functions. I.e. for serviceWorkerRegistrations, maybe pass in ServiceWorkerRegistration objects or the scope instead of strings corresponding to the scriptURL.
Similarly, what's the right indexedDB value? A database name?
localStorage? AppCache? Other storage mechanisms?
There are probably other types of storage—localStorage and AppCache both come to mind—that we could attempt to clear out as well, but those are mainly used by legacy applications. It's not clear that we should support them in this library.
Failures?
Should the clear() method ever fail? What happens if one of the attempts to clear something, like an IndexedDB database, does not succeed? What happens if an attempt to delete something doesn't complete within a reasonable amount of time?
Presumably it would be better to ensure that the method always fulfills and attempts to delete as much as possible, and then reports back any failures to delete items as part of the return value. This is open for discussion, though.
Relationship with other Workbox libraries
workbox-clear-storage is intended to be usable in a standalone fashion by any web application, regardless of whether its using a service worker that includes the other Workbox libraries.
It would likely share some of the IndexedDB code from workbox-core.

There are probably other types of storage—localStorage and AppCache both come to mind—that we could attempt to clear out as well, but those are mainly used by legacy applications.

In my PWA I'm using a bunch of firebase products as well as GunDB which, as a default, stores off-line data to localStorage (indexedDB as a config option). In this regard it would be great to also add localStorage to the list of caches that would be cleared out.

@evdama: A complication around support for localStorage is that it can't be accessed from inside of a service worker. So if we did support clearing it, that would only work when workbox-clear-storage was used from a window client, not from inside of a service worker.
Maybe that's okay, if folks think they are more likely to use this sort of module from their window client code? But we'd have to make it clear that it will fail when used inside of a service worker.

If I understood correctly, this module would allow operations ranging from deleting a single runtime cache, to a complete
storage dump, like the one Jake Archibald suggests in the section "Recovering after a successful hack" of this article. Correct?
https://jakearchibald.com/2018/when-packages-go-bad/
And I guess that what this module would be able to do should depend on the service worker's scope. Right?
What about deleting data stored in in-memory databases such as LokiJS and datascript? Is this something that could be handled by this module?
Regarding the difficulty of clearing cookies and localStorage/sessionStorage from a service worker, do you think it would be possible - and reasonable - to adopt the following solution?
At build time:

the developer decides what to delete using ClearOptions
on the basis on the configuration specified in 1, workbox-clear-storage builds a small event handler to be executed in a WindowGlobalScope

At runtime:

the user/app decides to clear storage
the service worker uses postMessage to send a CustomEvent to the event handler, which performs the necessary calls to localStorage/sessionStorage operating from a WindowGlobalScope, not a ServiceWorkerGlobalScope.

Hi there,
Workbox is moving to a new engineering team within Google. As part of this move, we're declaring a partial bug bankruptcy to allow the new team to start fresh. We realize this isn't optimal, but realistically, this is the only way we see it working. For transparency, here're the criteria we applied:

For PRs, we closed everything that doesn't target the current v7 branch.
For Issues, we closed everything that was created before 2024.

Thanks, and we hope for your understanding!
The Workbox team


Meta: clean up the issue tracker

In the new issue chooser, feature proposals are supposed to go in the Discussions tab.
Questions point to Discord.
I get that Issues can be used for for discussions and questions too.
I do think we have too many inactive or similar issues that are clogging up the tracker.
For example, on SSG/SSR:

Static Site Generation (SSG) Brainstorming #1379
Architectural Idea / Question #473
Proposal: Server-side rendering #41

Inactive questions or drive-by:

Sept 2018: Does Yew provide an 'app will terminate' lifecycle hook? #401
Oct 2019: Offscreen canvas transfer to dedicated worker #678
July 2020: Yew nextjs #1432
Aug 2020: Why Component required to be 'static? #1538
Jan 2021: Cannot log in to discord #1718

Suggestions

Clean up inactive issues.
Group issues or discussions.
Pin issues/discussions for important topics like Documentation, Router, Hooks.

Just a little FYI: the links are broken

Links fixed. Thanks

I do think we have too many inactive or similar issues that are clogging up the tracker.

I totally agree. It's just that right now no one seems to have the time to dig through all these issues and closing them outright doesn't feel quite right for most of them.

Could we add a meta tag on this issue?
What do you think for closing issues if a few months go by with no comment except for the original post?

What do you think for closing issues if a few months go by with no comment except for the original post?

That seems reasonable, yes.

Maybe a Github action for that would be helpful?

It's just that right now no one seems to have the time to dig through all these issues and closing them outright doesn't feel quite right for most of them.

I managed to skim though the issues to get this list of issues. There's probably more that I missed
Invalid/Unactionable
https://github.com/yewstack/yew/issues/1754: fixed in master
https://github.com/yewstack/yew/issues/1549
https://github.com/yewstack/yew/issues/1794
https://github.com/yewstack/yew/issues/1233
https://github.com/yewstack/yew/issues/1086: Trunk solved this
https://github.com/yewstack/yew/issues/1100: unactionable (never seen this happen before, no updates either)
https://github.com/yewstack/yew/issues/724: Trunk solved this
Question
https://github.com/yewstack/yew/issues/1603
https://github.com/yewstack/yew/issues/1576
https://github.com/yewstack/yew/issues/1439
https://github.com/yewstack/yew/issues/1385
https://github.com/yewstack/yew/issues/1251
https://github.com/yewstack/yew/issues/1073
https://github.com/yewstack/yew/issues/204
https://github.com/yewstack/yew/issues/226
stdweb
https://github.com/yewstack/yew/issues/942
https://github.com/yewstack/yew/issues/938
https://github.com/yewstack/yew/issues/750
https://github.com/yewstack/yew/issues/607
https://github.com/yewstack/yew/issues/402 (because of cargo web)
misc
https://github.com/yewstack/yew/issues/1751 (this should've already been published)
https://github.com/yewstack/yew/issues/1581 (duplicate of https://github.com/yewstack/yew/issues/1004)

@siku2

Clean up inactive issues.

That isn't what was done.  An issue I opened was closed without being resolved.  This is user-hostile IMO, as I explain here.
Regarding:
@allan2

What do you think for closing issues if a few months go by with no comment except for the original post?

IMHO that would only serve to discourage engagement with Yew in exchange for a false representation of project health.
@siku2

It's just that right now no one seems to have the time to dig through all these issues and closing them outright doesn't feel quite right for most of them.

I asked "Has the pace of dev halted again?" on Gitter on Nov 15 2020 22:22 and my concern was dismissed.  IMO there's a more fundamental issue with the project than lingering issues.

I'm new to the project and I don't speak for any of the regular contributors. Thoughts are my own.
@kellytk I don't think anyone intended to be hostile towards you. People are just trying their best to improve this framework.
I posted a reply to you at #401. Similar sentiments are below for posterity.
Many projects close inactive or stale issues. It's not to discourage engagement, but to focus the efforts on issues that we can solve and to identify bugs.
Going through the tracker, there were just a lot of issues that weren't helping that goal. That's why I opened this one.
If you have suggestions for the project, try posting to the Discussions tab. I just posted one recently. People are quite sometimes but the project is still growing :) At least I'll keep an eye out for it.

@allan2
It would be strange to take it personally so that's beside the point.  As a user and sometimes contributor, I consider it user-hostile.
I'm not contributing further with the precedent set that initiative can be rejected with no resolution.

IMHO that would only serve to discourage engagement with Yew in exchange for a false representation of project health.

@kellytk Agreed, a contribution in general should not be closed without some form of resolution unless the inactivity is coming from the author and their participation is required in order to resolve the matter.

Maybe a Github action for that would be helpful?

I like this idea, I haven't looked into it but I wonder whether we could use a label to mark an issue as "stale" as a warning and then have an action close the issue after a set amount of time. I wouldn't want to add this label on any issue that has had no response, only those that cannot be resolved because the author is not replying or that the issue is so outdated that it no longer applies. In the latter I think when applying the label the reason should still be given why it no longer applies and allow the "stale" timer for some rebuttal.

Closing this as issues have been cleaned up to a great extent and questions have been migrated to discussions.
Feel free to re-open this issue if needed


⚠ Adacta-fintech.com has degraded performance

In c7393a5, Adacta-fintech.com (https://www.adacta-fintech.com) experienced degraded performance:

HTTP code: 200
Response time: 4258 ms

Resolved: Adacta-fintech.com performance has improved in d0f1daa.


Fix that terrible calendar rendering bug

What Happened?

What appeared to be a front end issue was actually a set of bad serialization_options on the backend.

The Fix

We will always need to pass in a start_date and end_date when serializing schedule objects. We will also need to invalidate cache when we start allowing users to flip between dates.

Going to deploy now.


steamPackages.steam-runtime: 0.20210317.0 -> 0.20210527.0

Motivation for this change
Closes #124308
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126138 run on x86_64-linux 1

6 packages built:

kodiPackages.steam-launcher
lutris
protontricks
steam
steam-run
steamcmd

Result of nixpkgs-review pr 126138 run on x86_64-linux 1

7 packages built:

kodiPackages.steam-launcher
lutris
protontricks
steam
steam-run
steam-tui
steamcmd

I don't think this fixed the pipewire issue
$ ls $(nix-build -A steamPackages.steam-runtime)/lib/{i386,x86_64}-linux-gnu/lib* | wc -l
98
$ ls $(nix-build -A steamPackages.steam-runtime)/lib/{i386,x86_64}-linux-gnu/lib* | grep pipe | wc -l
0

guess git was playing tricks on me, i did a pull after it was merged, but it didn't actually update

actually, no, it wasn't I'm guessing valve rolled out an update, which required it, but then reverted the requirement.

https://github.com/ValveSoftware/steam-for-linux/issues/7807#issuecomment-847306383

Ah, my cognitive dissonance was correct :)

#126147


Mag app: figure re-drawing on update

With conda updates to matplotlib, notebook, ... the entire figures re-drawn on every slide-bar update --> need to return ax from each plotting routine (ie. see synthetic seismogram)

Fixed (b.t.w that was plt.show())

nice! that was quick :)


Missing image file Air.png

Reported by dietmarw on 30 Sep 2009 17:02 UTC
I just noticed that the image file Air.png is missing. It is referenced in
Modelica.Media.Air.DryAirNasa as
<IMG SRC=\"../Images/Media/IdealGases/SingleGases/Air.png\">

Migrated-From: https://trac.modelica.org/Modelica/ticket/217

Comment by dietmarw on 2 Oct 2009 07:49 UTC
File recovered from version history (was deleted in aaec571e048b8349c39e352c7544ba88175ce597, 72f431aa7cb79d99a5c9594e9d1b7fec8a50df05) and added again to trunk(0f2315feb57695ff84fcda8855089ef11baf9e93) und maintenance/3.1(a3a3790d0c29046c0e352702b18a1c8735d73cb6).

Comment by dietmarw on 25 Nov 2009 11:53 UTC
Milestone MSL3.1.1 deleted


Add basic tuning guide, getting started page, updated clustering docs

This PR:

Adds a basic cluster tuning guide at operations/basic-cluster-tuning.md
Updates tutorials/cluster.md with information on migrating from a single-server deployment, and changes the examples to use the new bin/start-cluster-* scripts and configurations under examples/conf/druid/cluster
Adds a "Getting Started" page that links to the design/ingestion overview, the single-machine quickstarts, the clustering guide, and the community page

👍

Oh wait, this is a doc change. I'm changing my vote to just +1.

I'm backporting this to 0.15.0-incubating since it contains changes for some scripts and tutorial configurations.


ads1.opensubtitles.org

Should be blocked.

Thanks @specter78, ads1.opensubtitles.org has been added.
Closing.


merging services and popular articles pages

Docs Build status updates of commit ba4e787:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-services-the-azure-cli-can-manage.md
:bulb:Suggestion
View
Details

docs-ref-conceptual/azure-services-the-azure-cli-can-manage.md

Line 51, Column 4: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /azure/devops/pipelines/apps/cd/azure/build-data-pipeline?view=azure-devops

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

Docs Build status updates of commit 862f97e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-services-the-azure-cli-can-manage.md
:bulb:Suggestion
View
Details

docs-ref-conceptual/azure-services-the-azure-cli-can-manage.md

Line 51, Column 4: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /azure/devops/pipelines/apps/cd/azure/build-data-pipeline?view=azure-devops

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


docs: fix README code on decoding tx instruction

Fixes issues on code sample provided in section "Parse/decode an instruction from a transaction" from the README:

if if typo replaced with if;
Error check added to call to function ResolveInstructionAccounts;
Example transaction fetched was changed because the transaction hash that was there could not be found by the solana public testnet RPC endpoint.

Thanks!
You're right, I should have probably selected a transaction from mainnet because the other clusters do get purged from time to time.

👍🏼 👍🏼
Let me know if you have any suggestion to add to the PR

Thanks!

Thanks for merging!


Yeoman generator not getting installed in VDI

Trying to install(with Admin privileges) the Yeoman using "npm install -g yo generator-office" in VDI for Office Word Add-in
All the proxies and registry  are set properly for the VDI, still facing the issue with below error.
Error:
npm install -g yo generator-office
npm WARN deprecated<EMAIL_ADDRESS>The package has been renamed to open
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>cross-spawn no longer requires a build toolchain, use it instead
C:\Users\Administrator\AppData\Roaming\npm\yo-complete -> C:\Users\Administrator\AppData\Roaming\npm\node_modules\yo\lib\completion\index.js
C:\Users\Administrator\AppData\Roaming\npm\yo -> C:\Users\Administrator\AppData\Roaming\npm\node_modules\yo\lib\cli.js

<EMAIL_ADDRESS>postinstall C:\Users\Administrator\AppData\Roaming\npm\node_modules\yo
yodoctor

Yeoman Doctor
Running sanity checks on your system
√ No .bowerrc file in home directory
√ Global configuration file is valid
√ NODE_PATH matches the npm root
√ No .yo-rc.json file in home directory
√ Node.js version
ErrorClass [RequestError]: getaddrinfo ENOTFOUND registry.npmjs.org
at ClientRequest. (C:\Users\Administrator\AppData\Roaming\npm\node_modules\yo\node_modules\latest-version\node_modules\got\index.js:73:21)
at Object.onceWrapper (events.js:313:26)
at ClientRequest.emit (events.js:223:5)
at ClientRequest.EventEmitter.emit (domain.js:475:20)
at Socket.socketErrorListener (_http_client.js:406:9)
at Socket.emit (events.js:223:5)
at Socket.EventEmitter.emit (domain.js:475:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:81:21) {
code: 'ENOTFOUND',
message: 'getaddrinfo ENOTFOUND registry.npmjs.org',
host: 'registry.npmjs.org',
hostname: 'registry.npmjs.org',
method: 'GET',
path: '/yo'
}
× yo version
ErrorClass [RequestError]: getaddrinfo ENOTFOUND registry.npmjs.org
at ClientRequest. (C:\Users\Administrator\AppData\Roaming\npm\node_modules\yo\node_modules\latest-version\node_modules\got\index.js:73:21)
at Object.onceWrapper (events.js:313:26)
at ClientRequest.emit (events.js:223:5)
at ClientRequest.EventEmitter.emit (domain.js:475:20)
at Socket.socketErrorListener (_http_client.js:406:9)
at Socket.emit (events.js:223:5)
at Socket.EventEmitter.emit (domain.js:475:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:81:21) {
code: 'ENOTFOUND',
message: 'getaddrinfo ENOTFOUND registry.npmjs.org',
host: 'registry.npmjs.org',
hostname: 'registry.npmjs.org',
method: 'GET',
path: '/yo'
}
√ npm version
Found potential issues on your machine :(

<EMAIL_ADDRESS><EMAIL_ADDRESS>updated 2 packages in 194.549s

We currently do not support VDI environment. Based on the traces this looks to be an environment issue with access to the npm registry.


Failed to get a tun/tap device" error="route MTU not supported in Windows

on windows 10, with 1.5.2, as soon as I add unsafe_routes I get the error:
Failed to get a tun/tap device" error="route MTU not supported in Windows
I had to revert back to 1.5.0
on Linux everything is fine.

This was fixed with #648 , currently unreleased but it will be in the next one.


fix: improve picking response handler

Now it will raise an error if it's impossible to pick handler
It's now more explicit if response is not drf one or ninja.

It looks good! 🚀
Thanks @TheSuperiorStanislav


[locationd] Refactor input checks

[x] Use more generic checks
[x] Use FirstOrderFilter
[x] Make running offline compatible
[x] Verify
[ ] Falsify, just to be sure

As discussed, let's first move the input checks into rednose, so it's a more generic version of #26460. SubMaster is a good example of this.


Pretty sure commas are needed.

I know it's just an example, but I think commas are missing.

Thx


Add DESTDIR variable to Makefile

This PR depends on #184 which must be merged before this one.
This adds a DESTDIR variable to the Makefile which acts as a prefix for all directories in the install make target. This will make it much easier to package swhkd, as now building and installing boils down to: make && make DESTDIR="packaging_subdir" install. The default is still to install to the root.
This PR also updates contrib/PKGBUILD to make use of this updated install make target.

Note to self: after merging, update PKGBUILD

Just rebased manually as it seemed like something was wrong (but actually nothing was wrong).
Sorry for that, could you please approve again @Shinyzenith?


Add BOOST_NO_TYPEID=1 to the conan build environment to prevent crashes.

Cpprestsdk uses boost::asio itself, which caused conflicting definitions to be linked together, leading to the version with RTTI enabled taking precedence during linktime.

Does this fix the crash in faasm?

I guess it didn't, it crashed again on the actions runner

@eigenraven you may want to check #279 I will pick up this PR when the other one is ready.

@eigenraven after merging into (your branches) the changes to fix the CI/CD submodule fetching it seems that now we are picking up the right version of boost 1.80 and the right profile flags. Yet, the dist-tests in faasm are still failing. Could you take a look?

Yes, this seems to not reliably fix the issue which is why I left this pr as a draft, I'll have another look at it later

Sorry, I did not understand that from your comments. I thought the CI bugs where the blocker. Feel free to mark as draft again.

Ah yeah I didn't note it here, it's in one of my slack messages


Editing GDNS entry (associated with project) and adding a new project , results in GDNS entry associated with only the new project.

Rancher version - Build from master
Steps to reproduce the problem:
Create a GDNS entry associated with project say p1.
Edit GDNS entry and add another project say p2.
After Edit is done , GDNS entry  gets associated with only p2.

Tested with Rancher version 547cbe87
Editing GDNS entry (associated with project) and adding a new project results in the new project getting added to the GDNS entry without loosing the existing project.


initial page position of elements with a minus value 'margin-top' or 'top' is ignored and are automatically stuck to the top on page load

I have an element that has a minus top position (tried margin and top) for asthetic purposes but doing this makes ScrollToFixed stick it to the top automatically. Removing the minus value makes it work again.

That is a case I did not account for. I will look into it as soon as I get a chance. Thank you for reporting this.

1.5 years later, still no luck?


AWS Importing SG Rule from tfstate file doesn't work

What happened?
while trying to import SG Rule from tfstate file , relevant section :
Get this error :
 aws:ec2:SecurityGroupRule (eks_worker_nodeport):
    error: Preview failed: importing sgrule-123456: unexpected format for ID ("sgrule-123456"), expected SECURITYGROUPID_TYPE_PROTOCOL_FROMPORT_TOPORT_SOURCE[_SOURCE]*: too few parts

while importing security group itself works fine .
Example
while trying to import SG Rule from tfstate file , relevant section :
  {
     "mode": "managed",
     "type": "aws_security_group_rule",
     "name": "eks_worker_nodeport",
     "provider": "provider[\"registry.terraform.io/hashicorp/aws\"]",
     "instances": [
       {
         "schema_version": 2,
         "attributes": {
           "cidr_blocks": [
            <REDACTED>
           ],
           "description": "Allows communication with the cluster API Server",
           "from_port": 443,
           "id": "sgr-1234567",
           "ipv6_cidr_blocks": null,
           "prefix_list_ids": null,
           "protocol": "tcp",
           "security_group_id": "s<REDACTED>",
           "security_group_rule_id": "",
           "self": false,
           "source_security_group_id": null,
           "timeouts": null,
           "to_port": 443,
           "type": "ingress"
         },
         "sensitive_attributes": [],
         "private": "<REDACTED>",
         "dependencies": [
           "aws_security_group.eks_master"
         ]
       }
     ]
   },

got this error :
 aws:ec2:SecurityGroupRule (eks_worker_nodeport):
    error: Preview failed: importing sgrule-123456: unexpected format for ID ("sgrule-123456"), expected SECURITYGROUPID_TYPE_PROTOCOL_FROMPORT_TOPORT_SOURCE[_SOURCE]*: too few parts

Output of pulumi about
CLI
Version      3.134.1
Go Version   go1.23.1
Go Compiler  gc
Plugins
KIND      NAME  VERSION
resource  aws   6.37.1
language  go    unknown
Host
OS       ubuntu
Version  22.04
Arch     x86_64
This project is written in go: executable='/usr/bin/go' version='go version go1.23.1 linux/amd64'
Backend
Name           vanand-ThinkPad-P14s-Gen-2a
URL            file:///home/vanand/work/pulumi-state-dev/
User           vanand
Organizations
Token type     personal
Dependencies:
NAME                                 VERSION
github.com/pulumi/pulumi-aws/sdk/v6  v6.37.1
github.com/pulumi/pulumi/sdk/v3      v3.117.0
Pulumi locates its logs in /tmp by default
warning: Failed to get information about the current stack: No current snapshot
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Thanks for acknowledging this , is there a suggestive fix for now ? O/w I will need to modify the state to include the security group rule with the security group itself .
Also any ballpark ETA would be of great help , Thanks !


blog post: Geth GraphQL app tour

blocked by a geth regression https://github.com/ethereum/go-ethereum/issues/20083

https://medium.com/ethereum-grid/exploring-ethereum-with-geth-graphql-and-grid-6df38f2a86c


Not calling the JS Error Handler

Added the error handler before the app class but it is not being called.
const errorHandler = (e, isFatal) => {
  if (isFatal) {
    console.log("from Error Handler", e);
    Alert.alert(
      "Unexpected error occurred",
      `
        Error: ${isFatal ? "Fatal:" : ""} ${e.name} ${e.message}
        We have reported this to our team ! Please close the app and start again!
        `,
      [
        {
          text: "Close",
          onPress: () => {
            BackAndroid.exitApp();
          }
        }
      ]
    );
  } else {
    console.log(e); // So that we can see it in the ADB logs in case of Android if needed
  }
};

setJSExceptionHandler(errorHandler, true);

export default class App extends Component {
.....
}

in component render method, added the following error function
render(){
   this.test() // throws error
   return (
   .......
   )
}

React native version is 0.52 and testing it on android simulator.

Hmm . Looks like a duplicate of #36
Looks like the exception handler doesn't get called on first render.
Will need to look at that .
But I don't think this should effect the regular use case.

Thanks @master-atul. It doesn't work on first render but do work if triggered from a button.
It also works if you trigger the error from render function  of another screen but along with the error message, the red screen is also shown in this case.  Is this the expected behavior?

Hi @ozmaat  The red screen will occur only in the development build.  When you do a release build .. The redscreen is removed by reactnative itself. So at that time .. only the exception handlers you set using this library will be invoked.

Thanks  @master-atul.


feat: integrate hardhat-foundry and add example foundry tests

introduced hardhat-foundry plugin (https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-foundry)

bumped node to 18 for new dependencies

fixed CI to include foundry, but also test:prototypes which were missing and new forge tests

migrated 2 tests from hardhat to foundry, for illustration how tests look like in foundry, how cheatcodes are used etc, if direction is ok, separate issue to migrate all v2 tests, should be same as these 2 and fairly straightforward (https://github.com/zeta-chain/protocol-contracts/issues/213)

NOTE: too many generated files, maybe we can consider only generating go and ts bindings for things that are needed? these new forge lib sol files dont need all these generated bindings, but lets clear it up in separate issue (add ignore folders to generate_go script and find a way to ignore contracts in typechain)

Why do we need Foundry as a git submodule? Isn't it something developers can install with cargo, instead?


4.03, merlin complains about indexing operators in emacs

E.g. in the following program:
let () = ignore (Sys.argv.(0))

It highlights the .( and says Error: Unbound value .(). The same program is fine in 4.02.3.

Support for 4.03 is broken. No time to fix that this week.

Actually it's not too bad.

Fixed in master.


Remove extraneous f character from f-string.

Makes tracking experiment names confusion, especially when using uuids.
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos, doc improvements)
[x] Did you read the contributor guideline?
[ ] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?

This is a small typo fix.
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

LGTM. Thanks for the fix.


Provide a table for decision criterion for hashing to curve

Currently we implement three different 'hash' functions for going from strings to elliptic curve elements. https://github.com/arkworks-rs/crypto-primitives/tree/main/src/crh

Pedersen
Bowe-Hopwood
Injective map (I'm not really sure what this one is)

It'd probably be a handy reference to provide a table in the README for that directory explaining when to use each hash / what the different properties of each one is.

Yes, actually all of crypto-primitives is lacking documentation right now.


Updates

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #4   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           6      6
  Lines          61     61
=====================================
  Hits           61     61

Impacted Files
Coverage Δ

src/lib/commit-transform.js
100% <100%> (ø)
:arrow_up:

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 5b23fa8...b930edc. Read the comment docs.


module Stapfen::Logger should be optional or have a more specific use case

I'm having issues using logback with Stapfen. I've tried a few ways, all of which are hackish due to the fact that the Stapfen::Logger requires the "logger" attribute to be a Proc and all the proxy methods (info, debug, warn, etc) "call" the proc.
I have some ideas:

Rename the logger attribute to indicate Stapfen-specific application (logger_proc)
Remove the logger module entirely, as it doesn't serve a purpose to Stapfen itself (compare to something like Faraday, and it's logger)
Refactor the logger to use a Proc

https://github.com/lookout/stapfen/blob/master/lib/stapfen/logger.rb#L21
https://github.com/lookout/stapfen/blob/master/lib/stapfen/worker.rb#L109

I think the right way forward here might be to break some API compatibility, bump the major version and remove the log block and replace it with the before block we discussed IRL

I believe this can be closed now


z still being used

This is a great work. In the appendix, I see that no z in the mamba pro module but in the code, in projection will still generate z. Am I understanding it correctly?

Hi @andypinxinliu ,
Are you able to match the paper implementation with the current codebase?
Thanks!
Abdelrahman.

In the code of VideoMambaPro, there is indeed a part about z. Mainly, we inherited most of the code of VideoMamba to facilitate writing. However,  that of z is commented out based on a 'flag' setting.

Where is that z commented out? It seems to me like the code never runs your modified selective scan function. Did you change the cuda kernels for selective scan to also implement your changes?

Hi we didn't use the selective_scan_cuda module, instead, we write the function to replace the selective_scan_cuda module. More precisely, e.g., we use the function mamba_inner_ref to replace the forward function in class MambaInnerFn.


Not sure what is the problem, but maybe nodeos should exit here instead of running forever and never moving forward?

Matthew, do you have any steps to reproduce the problem? Does it always happen? I tried restarting nodeos but could not reproduce fork db corruption.

Sorry, the issue is not generally reproducible.  I don't know what happened in this situation that caused the issue.
I mainly opened the issue because when a problem happens, nodeos should exit instead of continuing to run and never recovering.

I was thinking about fixing the issue all together. Will make nodeos exit when the problem happens again, even if the root cause is not found.


FATAL: implicit-imports: Error, illegal value for 'standalone_macos_bundle_mode' for 'wx' entry.

I checked the source code and found that in nuitka/plugins/standard/standard.nuitka-package.config.yml, line 1315, standalone_macos_bundle_mode is set to "true". I solved the problem after changing it to standalone_macos_bundle_mode: True

I confirm I am having the same issue Python 3.9, wxpython version 4.1.1).

No, you do not @paddy-r you probably just used 0.9.0 and not 0.9.1 which wasn't on PyPI yet.

Thanks @kayhayen, I upgraded to 0.9.2 and my code now compiles successfully.


Is multi-scale training implemented?

As shown in the paper, the multi-scale training can import the mAP on VOC 2007 test set by 1.4. Has multi-scale training been implemented by YOLOv2?

Yes, leetenki implemented the  multi-scale training, see the yolov2_train.py file.


Choose the Correct Number of Topics for the DTM

Right now I just have two topics, which is obviously bad.
Check out GridSearchCV to help determine the right number of topics: https://investigate.ai/text-analysis/choosing-the-right-number-of-topics-for-a-scikit-learn-topic-model/
https://www.machinelearningplus.com/nlp/topic-modeling-python-sklearn-examples/

Jo says these are the best topic no. to choose:
k = 100
k = 500


feat: Rebuild deployment package on architecture change

Description
Rebuild the deployment package on CPU architecture change.
Motivation and Context
Previously the CPU architecture configured for an AWS Lambda Function wasn't taken into account when generating the file name hash for the deployment package. This meant that changing the CPU architecture of an AWS Lambda Function did not trigger a rebuild of the deployment package. As deployment packages might contain CPU-specific binaries, this could've caused deployments breaking AWS Lambda Functions.
Breaking Changes
As the file name hash changes due to these changes, a rebuild of all deployment packages will happen once using a version of this Terraform module with the changes included.
Also not really a breaking change, but a minor annoyance of the current implementation is that switching from an unconfigured CPU architecture to x86-64 will also result in a rebuild of the deployment package, as that results in a switch of the value for the architecture from null to ["x86-64"]. However, I'm not sure what'd be the best way to fix that and as it only happens when intentionally changing the architecture attribute, I believe it's fine as is as well.

not stale

var.compatible_architectures and var.compatible_runtimes get considered for rebuilding the deployment package now as well.

Not stale, just waiting for @antonbabenko to have a look at it again.

still relevant


Integrate Code Exporter Plugin

Hi, Thank you for this great project. We are using the static html file in one of our graphQL applications. It would be really helpful if we could get the code exporter plugin as well. Could you please help me get this PR merged? I am a backend engineer, so please review and let me know if any changes are required.
Thanks :)

Is this working with the Code Exporter? I would like to see it running


wasm file schema version: 0.2.84 (153a6aa9c) != 0.2.84

Hi *,
when trying to run the hello_world demo (wasm-bindgen/examples/hello_world) from wasm-bindgen 153a6aa9c7a989c1865df7f93b2ddbca1113a175 like this:
npm run serve
I get this error:
[INFO]: 🌀  Compiling to Wasm...
Finished dev [unoptimized + debuginfo] target(s) in 0.17s
error:
it looks like the Rust project used to create this wasm file was linked against
version of wasm-bindgen that uses a different bindgen format than this binary:
rust wasm file schema version: 0.2.84 (153a6aa9c)
this binary schema version: 0.2.84
I've tried both fixes:
cargo update -p wasm-bindgen
cargo install -f wasm-bindgen-cli
without any success.
What can i do to fix this?
PS: It's a MacBook M1/ARM64 with:
OS: v12.5.1
rustc 1.69.0 (84c898d65 2023-04-16)
wasm-bindgen 0.2.84
wasm-pack 0.11.0

OK, my one is duplicate of:
https://github.com/rustwasm/wasm-bindgen/issues/3379
We might place a warning in the main README.md.
Sorry for the noise ..

Duplicate of https://github.com/rustwasm/wasm-bindgen/issues/2619.


$myTenantName Variable isn't specified

$myTenantName variable isnt specified in the script and removed in a previous change. This needs to be specified and also it needs to be clear as to which tenant name needs to be provided. In this instance, we need to provide WVD Tenant Name.

@nthewara : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

#hold-off

@nthewara : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Fix Vmware Fusion kernel panic at boot

Disable the dsbdriverd service when running under Vmware hypervisor to avoid a kernel panic or hang. Root cause still needs to be found.

Ignore, please. This wasn't meant to target the base repo.


togeojson deprecated

Hi,
please update the togeojson dependency:
npm WARN deprecated<EMAIL_ADDRESS>This module has moved: please install @mapbox/togeojson instead
thanks for the great work. Thanks!

please also alter the requires in js to require('@mapbox/togeojson'), then also webpack is satisfied. Thanks in advance. Thomas.

please also alter the requires in js to require('@mapbox/togeojson'), then also webpack is satisfied. Thanks in advance. Thomas.


Markdown Preview Flashes

Issue Type: Bug
When editing a Markdown file with the Preview open on the side, the Preview section flashes whenever it updates rather than having a smooth update.
It seems to happen more when editing lines in-between other lines, rather than lines at the bottom of the file.
My Markdown file has just under 1000 lines.
VS Code version: Code 1.26.0 (4e9361845dc28659923a300945f84731393e210d, 2018-08-13T16:29:31.933Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 x 2904)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
31.88GB (24.30GB free)

Process Argv
C:\Users\rtaite\AppData\Local\Programs\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (12)

Extension
Author (truncated)
Version

markdown-toc
Ala
1.5.6

spellright
ban
2.5.30

vscode-markdownlint
Dav
0.19.0

jshint
dba
0.10.19

vscode-eslint
dba
1.4.12

code-runner
for
0.9.4

beautify
Hoo
1.3.2

csharpextensions
jch
1.3.0

csharpfixformat
Leo
0.0.73

markdown-shortcuts
mdi
0.8.1

mssql
ms-
1.4.0

csharp
ms-
1.15.2

(1 theme extensions excluded)

Please share the contents of your markdown file

@mjbvz Here you go, slightly edited:
ryanTaiteMarkdownFileTextFormat.txt

We've made some fixed around this area recently and I can no longer reproduce this problem. Let me know if you still see this in the latest VS Code insiders build


Mod Button competes with RES's "hide child comments"

Example.
This is entirely a limitation of how we insert the "mod" button currently (which I wrote), which is to count some number of list items from the end of .flat-list.buttons. A smarter check would be to insert before the reply button directly, with support for internationalization:
$('.flat-list.buttons a[onClick="return reply(this)"]')

As an aside, @andytuba are y'all sure you want to put "hide child comments" after "reply"? Generally I've found that putting anything after "reply" just annoys users who go for "reply" by reflex, because they click the last list item before checking what it is. Sticking it up next to the regular collapse button doesn't make sense, but I feel like there's got to be a better place.

i hate the placement of the hide child comments button too.  i don't think i've heard people complaining about that particular button. i don't really know what to do about all of RES's buttons except add an   after the reply button and shove everything to the right, with an option for people to put everything in the crappy legacy locations.

Sorry man all I have is just make another row of .flat-list.buttons that aligns right instead of left and throw RES stuff in there. But that just seems like heaps of trouble. If you could do it cleanly I'd say just make them float right inside the existing row of buttons, but I know CSS and I know that'll be a pain.


objc: Implement whitelist tracing

This implements the tracing facility to enable whitelisting.
The most ugly thing is the collecting of the protocol ItemIds that a interface conforms to. I couldn't use the Item::from_ty because the protocols aren't actually types (in clang), I'm just making them look like one, as thats how they behave in bindgens perspective. So I resorted in linear search of all ItemIds, as it was easyish to implement (local to objc.rs), but there are several good avenues to make that faster if it needs to.
The change to naming the types with the rust_name is also a suspect, I'm not totally sure of all the consequences but this allows the protocols/categories to be disambiguated, otherwise there could be multiple type items with the same name. Somehow I feel that I'm forgetting another rationale as well, from when I originally wrote that line few days ago.
Locally I also got a test failure, but to me that does not seem like it was caused by these changes. In  call-conv-field.rs:
 extern "stdcall" {
-    #[link_name = "_bar@0"]
+    #[link_name = "bar@0"]
     pub fn bar();
 }

 Warning

These commits modify unsafe code. Please review it carefully!

Locally I also got a test failure, but to me that does not seem like it was caused by these changes. In call-conv-field.rs.

Hm, yeah, I know why that is and it's unfortunate :(. It's temporary though.
This looks fine, thanks for doing it!
@bors-servo r+

:pushpin: Commit 35159dc has been approved by emilio

:hourglass: Testing commit 35159dc with merge 6320ed2...

I invited you to have write access to the repo (feel free to accept or not if you don't want to). This wouldn't give you review privileges (we usually require a few reviews before that), but would allow you to file/triage/report issues if you need or want to do so.
Thanks for all the good stuff! :)

:sunny: Test successful - status-travis
Approved by: emilio
Pushing 6320ed2514d93fdbbd429a6d67ee9e8bfdfcb297 to master...


Fix the bug in gcc compiler specific

Currently, the if statement of __GNUC__ will let the compiler-specific header not work well.
It won't do as we think, since it doesn't let us use the GCC-specific function.

Fixed by a4511c2f8e03050781f966e4f25f216f97cdd484.


Update check tip util functions to return both at-tip status and block id

Fixes # .
Motivation

We added CheckNetworkTip and CheckStorageTip utility functions to DRY these checks in the Rosetta CLI. These methods return a block identifier if the network or storage block is at tip respectively.
In some contexts, the CLI needs to know the block identifier even if it is not at tip.
Solution

Updated these methods to return at-tip status in addition to the network or storage block identifier.
Open questions

Pull Request Test Coverage Report for Build 14236

12 of 15 (80.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 77.922%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

utils/utils.go
12
15
80.0%

Files with Coverage Reduction
New Missed Lines
%

utils/utils.go
1
66.54%

Totals

Change from base Build 14219:
-0.01%

Covered Lines:
8287

Relevant Lines:
10635

💛  - Coveralls

Pull Request Test Coverage Report for Build 14236

12 of 15 (80.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 77.922%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

utils/utils.go
12
15
80.0%

Files with Coverage Reduction
New Missed Lines
%

utils/utils.go
1
66.54%

Totals

Change from base Build 14219:
-0.01%

Covered Lines:
8287

Relevant Lines:
10635

💛  - Coveralls


Implement certificate parser / validation

Yes, the most dangerous code in the world!
I currently only implemented DER parser a bit. I have to implement ASN.1 tree -> certificate parser and certificate validator. Not sure how macros work well for this..

Hi klutzy,
Are you actively working on this? I would be interested in contributing.
I have previously written a partial DER parser in C, which I had to abandon b/c it felt C didn't help much. I would work on this over the next few weeks most probably, implementing

a simple, non-streaming DER parser
implementations of operations on ASN.1 types
an X.509 parser that basically turns [u8] into a X509Cert, but does not do any validation itself
possibly a small DSL to define DER structures (time allowing)

This would allow suruga to implement all certificate validation logic, while keeping concerns separated.
I do not believe an ASN.1 schema parser is worth implementing, since a DSL is easier to implement and has less overhead.
With your help I'd like to flesh out a basic API that would make sense from the suruga side, and then see how I can make it possible.
What do you think?

Oops, I forgot to update current status: in my x509-parser branch, I've implemented DER reader and X.509 Certificate and CRL reader. Last month I checked it parses some wild certificates well, but I need more validation so haven't pushed to master yet.

I see! Are you looking for collaborators then or is this more of a one man project?

I'm also interested in helping.

I would suggest not implementing an ASN.1 -> DER parser; in my experience, you're much better off never using the ASN.1 at all, but instead re-expressing the structure in code or in some much simpler DSL, then writing a BER parser that goes from octets to parsed structure. You probably don't need a DER encoder; while the standard nominally requires DER expression as the signed structure, in practice, certificates are already DER and so don't require re-encoding. (In the past, some CAs signed BER, so re-encoding would never validate, but that is hopefully uncommon now.)

There is a useful online version of the PEM parser https://8gwifi.org/PemParserFunctions.jsp


JAMES-4085 [S3 SSEC] Guice binding & document

rebase & squash

Needs a rebase

Rebase & resolve & fixup comment & remove code related to key derivation

squash & rebase

Some guice injection issue with SMTPJamesServerTest : https://ci-builds.apache.org/job/james/job/ApacheJames/job/PR-2495/6/testReport/


MGDCTRS-1869 Upgrade Debezium Operator to use new storage config options

https://issues.redhat.com/browse/MGDCTRS-1869

There is a bug in the build-it pipeline. I'm sending a fix.


Ceska televize (iVysilani) is broken again_pls check it out

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2023.03.04
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[ ] I've searched the bugtracker for similar issues including closed ones

Region
Czech Republic
Verbose log

D:\CzTv-download>yt-dlp https://www.ceskatelevize.cz/porady/11781961862-barokni-srdce-evropy/217562263110001/
[CeskaTelevize] Extracting URL: https://www.ceskatelevize.cz/porady/11781961862-barokni-srdce-evropy/217562263110001/
[CeskaTelevize]<PHONE_NUMBER>10001: Downloading webpage
[CeskaTelevize]<PHONE_NUMBER>10001: Getting IFRAME hash
ERROR: [CeskaTelevize]<PHONE_NUMBER>10001: Unable to download webpage: HTTP Error 404: Not Found (caused by <HTTPError 404: 'Not Found'>); please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U

Description
Hello,
Ceska Televize updated their platform and the extractor is unable to fetch anything anymore.
Pls update yt-dlp for this domain. thx a lot

If you want yt-dlp updated, ask here: https://github.com/yt-dlp/yt-dlp/issues/6539 (and see #30839 again).
As you see, it's a known issue that both projects are working on.

I see, thx a lot for a message

yt-dl work-in-progress:
$ python -m youtube_dl -F -v 'https://www.ceskatelevize.cz/porady/11781961862-barokni-srdce-evropy/217562263110001/'
[debug] System config: [u'--prefer-ffmpeg']
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-F', u'-v', u'https://www.ceskatelevize.cz/porady/11781961862-barokni-srdce-evropy/217562263110001/']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Git HEAD: 6fece0a96
[debug] Python version 2.7.18 (CPython) - Linux-4.4.0-210-generic-i686-with-Ubuntu-16.04-xenial
[debug] exe versions: avconv 4.3, avprobe 4.3, ffmpeg 4.3, ffprobe 4.3
[debug] Proxy map: {}
[CeskaTelevize] Extracting URL: https://www.ceskatelevize.cz/porady/11781961862-barokni-srdce-evropy/217562263110001/
[CeskaTelevize]<PHONE_NUMBER>2: Downloading webpage
[CeskaTelevize]<PHONE_NUMBER>2: Downloading JSON metadata
[CeskaTelevize]<PHONE_NUMBER>2: Downloading JSON metadata
[CeskaTelevize]<PHONE_NUMBER>2: Downloading MPD manifest
[CeskaTelevize]<PHONE_NUMBER>2: Downloading MPD manifest
[CeskaTelevize]<PHONE_NUMBER>2: Downloading JSON metadata
[CeskaTelevize]<PHONE_NUMBER>2: Downloading JSON metadata
[CeskaTelevize]<PHONE_NUMBER>2: Downloading m3u8 information
[CeskaTelevize]<PHONE_NUMBER>2: Downloading m3u8 information
[download] Downloading playlist: Barokní srdce Evropy
[CeskaTelevize] playlist Barokní srdce Evropy: Collected 1 video ids (downloading 1 of them)
[download] Downloading video 1 of 1
[info] Available formats for<PHONE_NUMBER>7706695:
format code                      extension  resolution note
hls-audioDescription-128         mp4        audio only  128k , mp4a.40@128k
dash-audioDescription-1002-1507  m4a        audio only [que] DASH audio  128k , m4a_dash container, mp4a.40.2@128k (48000Hz)
dash-main-1002-1504              m4a        audio only [ces] DASH audio  128k , m4a_dash container, mp4a.40.2@128k (48000Hz)
dash-main-1001-1502              mp4        512x288    DASH video  500k , mp4_dash container, avc1.4d4015@ 500k, video only
dash-audioDescription-1001-1507  mp4        720x404    DASH video 1024k , mp4_dash container, avc1.4d401e@1024k, video only
dash-main-1001-1503              mp4        720x404    DASH video 1032k , mp4_dash container, avc1.4d401e@1032k, video only
dash-main-1001-1504              mp4        1024x576   DASH video 2048k , mp4_dash container, avc1.4d401f@2048k, video only
dash-main-1001-1505              mp4        1280x720   DASH video 3584k , mp4_dash container, avc1.4d401f@3584k, video only
dash-main-1001-1506              mp4        1920x1080  DASH video 6144k , mp4_dash container, avc1.4d4028@6144k, video only
hls-main-628                     mp4        unknown     628k video@ 628k, audio@  0k
hls-audioDescription-1152        mp4        unknown    1152k video@1152k, audio@  0k
hls-main-1160                    mp4        unknown    1160k video@1160k, audio@  0k
hls-main-2176                    mp4        unknown    2176k video@2176k, audio@  0k
hls-main-3712                    mp4        unknown    3712k video@3712k, audio@  0k
hls-main-6272                    mp4        unknown    6272k video@6272k, audio@  0k (best)
[download] Finished downloading playlist: Barokní srdce Evropy
$

Test 4 is problematic. It's an episode of the series Queer, with a trailer. The extractor used to produce a playlist containing both the trailer and the episode. However, although the trailer is still in the API results, I don't see a sign of it in the current programme page https://www.ceskatelevize.cz/porady/10520528904-queer/215562210900007/.
What do CZ viewers think?

is it just that this test page is quite old?
do new shows have trailers with URLs or JS page links?
should the trailer be included if found even if not requested?

Not sure what do you mean, but in previous version for some content, the yt-dlp grabbed also two files, first was some short file containing some info (something like trailer or etc), second the episode, movie file

Thanks for the test URLs.
A trailer would be included in a playlist together with the main content. With the right metadata definitions, trailers could be removed systematically using --match-filter ..., even by requiring duration > 60s, say. My concern is that, as trailers don't seem to be separately accessible (through their own dedicated URLs), there would be no way to extract them if they weren't included in the playlist result.

You know how to fix the bug? As we are unable currently to use yt-dlp to download content from ceskatelevize.cz

@asd123-007 @dirkf @bluenitepk
Hello. Now works this pre-release build of yt-dlp : https://github.com/bashonly/yt-dlp/releases/tag/ceskatelevize


This is not an antidote, it's a detector

The name is misleading.  This tool doesn't seem to let you "unpoison" an image and put it into the dataset, it just marks those images.  So, it's not an antidote, it's a detector, a sensor, a poison taster.
Nightshade is still useful even when it isn't secret, by deterring inclusion in training datasets.

I will give you the same response as the only other person who has realized that. If you can deduce that, then you can also deduce how to easily switch it into offense mode. I am not going to do that, personally. You can! I do not think an eye for an eye is good, I think balance in the force is good.

Why do you do an antidote? People are hating ai art, ai users, ect...
Why would you do an antidote do this solution? People want to keep their creation safe, why would you permit an antidote to steal their art? their work?
 People are hating ai art, ai users, ect... Why would you do an antidote do this solution? People want to keep their creation safe, why would you permit an antidote to steal their art? their work?  If you have looked at a few art pieces yourself and thought "Oh, I wanna make something in a similar style with a similar character", that is not stealing, that's drawing inspiration from the original work.
AI does the same. It learns how to draw alike and uses that to then be able to draw creative things that have not ever existed.

Why do you do an antidote? People are hating ai art, ai users, ect... Why would you do an antidote do this solution? People want to keep their creation safe, why would you permit an antidote to steal their art? their work?  If you have looked at a few art pieces yourself and thought "Oh, I wanna make something in a similar style with a similar character", that is not stealing, that's drawing inspiration from the original work.
AI does the same. It learns how to draw alike and uses that to then be able to draw creative things that have not ever existed.

It is stealing.  Imagine learning how to draw from 8 to 18 and people can copy your work with just a screen or code :/
Like hell nah bro, whats next?

If you arent happy its the same

This github issue isn't the place to argue in favor of or against the AI, it's just about the usage of the word "antidote" in the title!

Yeah, anyway did you get it to work with the unpoison thing, or is that not implemented?


Allow onHandlerStateChange to be an object

This enables onHandlerStateChange to be passed an Animated.Event which is technically not a function. Support for that case already exists, but was not represented in propTypes.

This issue is not related to RNR.
It's related to RNGH and fixed since 17 seconds 😄


add optional argument to !reset

The combination !reset + !send file is quite common during development, when things crash.
The !r command does not need an arg, so !r file could be re-defined to mean !r + !s file.

This has become a lot less of an issue now that ctrl-c also resets. Closing this for now.


Backport docs for iptables 1.8 support to v3.8

Description

Related issues/PRs

fixes

documents
Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit 08388407b0222dabc1c3f0daa84d097bbbcca426
https://deploy-preview-2708--calico.netlify.com


[DiscordRichPresence] Fix the extension for GD <v135

Replaces the use of getElectron().remote with getElectronRemote()

👍


Merge to stable branch

WIP

Verified to be completely functional for holoiso_rel_snapshot20240530.1926.43.
Merging.


In opening and closing only the latter operation gets gradients

Also noticing that when doing opening and closing, only the latter operation/strel gets gradients
Originally posted by @s-rog in https://github.com/Manza12/nnMorpho/issues/3#issuecomment-832648500

I have noticed that I only return gradients for the structural element when eroding and dilating.
@s-rog, what are your tensors that requiere grad? if the images requiere grad, it should refactor the backward functions to adapt.
In all the cases, I probably need to return both gradients (image and strel)

I meant like when your doing an erosion then a dilation, the erosion op doesn't produce any gradients.
In my testing if you have two morph ops in series, each using their own strel parameter, the first morph strel does not move.

Can you post a Python code doing that such that I can reproduce the problem? It will be easier for me to debug :)

A minimal snippet looks something like this:
import nnMorpho.functions as MF
import torch

class morph_module(torch.nn.Module):
    def __init__(self, sz=11):
        super(morph_module, self).__init__()
        self.strels = torch.nn.ParameterList([torch.rand(sz, sz), torch.rand(sz, sz)])

def forward(self, x):
    for strel in self.strels:
        origin = (strel.shape[0] // 2, strel.shape[1] // 2)
        x = MF.DilationFunction.apply(x, strel, origin, -1e4)
    return x


Prototype for the a mobile design with facets split into it's own page

This is the prototype for the new designs for smaller screens for the all finder. Emphasis on prototype, as it basically shows and hides things on the same page depending on which button the form is submitted with - this was the only way I could think of retaining the state of the search without JavaScript.

adds a filter page where facets can be selected
once the filter has been applied, a user can then go back to the search results

To get this working for the protoype, this is just showing and hiding certain elements of the same page to prevent a large-scale everything rewrite.
Trello card: https://trello.com/c/i8xtPcbY/947-build-the-prototype-for-improved-mobile-search-frontend
I cannot emphasise enough how none of this should go into production! This is just to give an idea of how splitting the facets could work with real search results can be used when testing it
WHAT WAS DONE
Phase one:

Search box restyled on mobile, placeholder text added and a search button added
Filter page added where facets can be selected on mobile - header and footer removed
Filters hidden on search page with a "Filters" link added that opens the filter page and shows the number of currently-applied filters
Facet tags not shown on search page, only on the new filters page
Facet tag styles tweaked (no background, darker border) and displayed inline instead of block
Keyword search facets not shown
Filters restyled to look like accordions
Topic selects and date range inputs moved into an "Expander" component
Expander component restyled like an accordion
A floating search button added to filters page with number of results available that dynamically updates with filter selection
Clear filter link added to the filters page that goes back to the search page (thus removing all filters)
Search results have an increased space and separator line removed
Subscribe to feed button moved to the bottom of results

@injms just looking through the PRs and tidying up. Do you want to keep this open?

@benthorner need to keep this open for a while. will close once we start the actual work

closing but keeping the branch


Add user opt-in page

Based on query params:
Automatically prevent deletion of inactive users
Automatically subscribe to general announcements
Prompt to subscribe to general announcements

Coverage increased (+0.03%) to 63.495% when pulling 7a2d512c684e4deea88c57c044f2f1873f9509f5 on opt-in-page into ffda59222fb62ab8f5ba217219d893e01335562f on master.


Bug fixes and optimization

0.10.2
Features

Model.save_related(follow=False) now accept also two additional arguments: Model.save_related(follow=False, save_all=False, exclude=None).

save_all:bool -> By default (so with save_all=False) ormar only upserts models that are not saved (so new or updated ones),
with save_all=True all related models are saved, regardless of saved status, which might be useful if updated
models comes from api call, so are not changed in the backend.
exclude: Union[Set, Dict, None] -> set/dict of relations to exclude from save, those relation won't be saved even with follow=True and save_all=True.
To exclude nested relations pass a nested dictionary like: exclude={"child":{"sub_child": {"exclude_sub_child_realtion"}}}. The allowed values follow
the fields/exclude_fields (from QuerySet) methods schema so when in doubt you can refer to docs in queries -> selecting subset of fields -> fields.

Model.dict() method previously included only directly related models or nested models if they were not nullable and not virtual,
now all related models not previously visited without loops are included in dict(). This should be not breaking
as just more data will be dumped to dict, but it should not be missing.
QuerySet.delete(each=False, **kwargs) previously required that you either pass a filter (by **kwargs or as a separate filter() call) or set each=True now also accepts
exclude() calls that generates NOT filter. So either each=True needs to be set to delete whole table or at least one of filter/exclude clauses.
Same thing applies to QuerySet.update(each=False, **kwargs) which also previously required that you either pass a filter (by **kwargs or as a separate filter() call) or set each=True now also accepts
exclude() calls that generates NOT filter. So either each=True needs to be set to update whole table or at least one of filter/exclude clauses.
Same thing applies to QuerysetProxy.update(each=False, **kwargs) which also previously required that you either pass a filter (by **kwargs or as a separate filter() call) or set each=True now also accepts
exclude() calls that generates NOT filter. So either each=True needs to be set to update whole table or at least one of filter/exclude clauses.

Fixes

Fix improper relation field resolution in QuerysetProxy if fk column has different database alias.
Fix hitting recursion error with very complicated models structure with loops when calling dict().
Fix bug when two non-relation fields were merged (appended) in query result when they were not relation fields (i.e. JSON)
Fix bug when during translation to dict from list the same relation name is used in chain but leads to different models
Fix bug when bulk_create would try to save also property_field decorated methods and pydantic fields

Other

Performance optimizations
Split tests into packages based on tested area

Codecov Report

Merging #140 (2cc3b55) into master (f4fa551) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##            master      #140    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files          129       132     +3
  Lines        11089     11340   +251
==========================================
+ Hits         11089     11340   +251

Impacted Files
Coverage Δ

ormar/models/quick_access_views.py
100.00% <ø> (ø)

tests/test_deferred/test_forward_cross_refs.py
100.00% <ø> (ø)

tests/test_deferred/test_forward_refs.py
100.00% <ø> (ø)

tests/test_deferred/test_more_same_table_joins.py
100.00% <ø> (ø)

tests/test_deferred/test_same_table_joins.py
100.00% <ø> (ø)

tests/test_encryption/test_encrypted_columns.py
100.00% <ø> (ø)

...exclude_include_dict/test_dumping_model_to_dict.py
100.00% <ø> (ø)

...test_exclude_include_dict/test_excludable_items.py
100.00% <ø> (ø)

...e_include_dict/test_excluding_fields_in_fastapi.py
100.00% <ø> (ø)

...include_dict/test_excluding_fields_with_default.py
100.00% <ø> (ø)

... and 75 more


WIP get health check path from readiness probe

This PR is not ready but I wanted to open it because I would like some feedback on the approach before continuing. I tried reusing as much as possible from ingress-gce, however I chose to copy GetProbe and getHTTPProbe from ingress-gce/controller/utils.go. This is because the GCETranslator that was the receiver needed a LoadBalancerController to initialize which seemed like unnecessary bloat. One possible solution would be to refactor the code in ingress-gce to make it easier to reuse so we could avoid code duplication. I haven't bothered with the tests yet since I'm not sure if this is the way you'd want to implement this.
I tested the implementation manually by running and it works ~with one exception, sometimes it seems like even though the cached informer has been synced it fails to get the correct path and defaults to /. I'm not yet sure if there's an issue with some race condition in the syncing or if the error is in this PR.~ EDIT: found the issue, I used the wrong HasSynced method when checking if the pod informer had synced

cc @nikhiljindal @csbell @bowei

/ok-to-test
Hey thanks a lot for the PR @glindste. Appreciate the contribution.
Regarding code duplication with ingress-gce, we are working with @bowei to reduce it. We have existing copied code here and want to get rid of it as soon as possible, but realize that requires refactoring in ingress-gce and then revendoring it here.
I am curious how you found this problem? Are you using kubemci?

@nikhiljindal I spent last week researching how to do multi cluster ingress. Kubernetes federation did not fit our usecase at all, we want individual control over the clusters and it doesn't mesh well with how we deploy things. I think I was digging around in the ingress-gce source code and found the gce-multi-cluster annotation which led me to kubemci, which seems to do exactly what we want.
Getting the health check path from the probe was pretty much the only missing feature before I could test how kubemci worked (neither our service or the default backend returns 200 on /) so I figured I'd give it a go.

Thats great @glindste! Are you going to use this with your GCP clusters?
We'd like to include you (and others) in our early access program if possible. Could you sign up for the EAP using this form?
https://goo.gl/forms/RHg032DrRnnqF0by1 .
We would love your feedback as you try out kubemci and would love to know what works and what doesnt.
cc @mdelio

Thanks a lot for the feedback! :)
Yes if no major blocker comes up we'll probably use kubemci to set up the LB for our clusters, the alternative currently is managing the LB manually which we'd like to avoid. I've signed up for the EAP

Thanks for the changes @glindste
This looks great.
I have a few comments, mostly minor about being explicit about which code is copied and better error messages.
We should be good to merge once we resolve them.
Thanks!

Changes Unknown when pulling 7e1ba4c7da01a0a5bbf8d29dfd21fca9c47ca60b on glindste:hc-path-from-probe into ** on GoogleCloudPlatform:master**.

@nikhiljindal I think I'm done now, please have a look if I addressed all your comments and if there's anything else I can fix. Thank you for the excellent review comments. Also, would you like me to squash the commits before merging?

Changes Unknown when pulling faac038510d2b5bd4a941d85c4e6972506c26436 on glindste:hc-path-from-probe into ** on GoogleCloudPlatform:master**.

I saw you'd fixed vet and fmt on master so I rebased and made sure they pass for this branch as well

Changes Unknown when pulling bc005f37674b4f8bc0a42d35043c45b009720e9b on glindste:hc-path-from-probe into ** on GoogleCloudPlatform:master**.

Yes, please squash the commits.
You can also remove WIP from the PR title and commit message :)

Changes Unknown when pulling f3b69812719c4315fa819bac89337d5d0dcd6f9b on glindste:hc-path-from-probe into ** on GoogleCloudPlatform:master**.


Update core to bundle all errors using error module,

Bundle and export all errors using error module.
Rename result module to "error" for out-of-core-workspace users.
Update storages/ and test-suite/ codes to use global error module.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

78 of 78 (100.0%)  changed or added relevant lines in 9 files are covered.
14 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.02%) to 98.939%

Files with Coverage Reduction
New Missed Lines
%

core/src/data/value/binary_op/f64.rs
1
99.75%

core/src/executor/fetch.rs
13
96.95%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
43178

Relevant Lines:
43641

💛  - Coveralls


Rename tiddlers when dragging and dropping

Consider adding the option to rename a dragged and dropped node to change its title prefix to match the new root.
The issue is that this is highly dependent on the title configuration being used.
This may not be feasible unless we are willing to limit the title configuration to a choice between a free pre-defined presets.
See https://groups.google.com/g/tiddlywiki/c/-xTFWPwzq6g/m/zNJ_9iLRAgAJ

As a workaround that works for me, consider the move as a "copy the node to a new root tiddler + delete". When proceeding this way, the copied node takes the naming convention of a new node in the destination root tiddler.


Added request tracing support to BulkIndexer

See last sentence of #194

@kpashka Can we get some basic tests around this?  Currently the code is "safe" not having RequestTracer set automatically and it is up to the user to set their own tracer (it is public, so they can do that).  If we introduce this method we start excercising code in baserequest.go that wasn't being used previously so tests would be imperative before merging.

@weberr13 I will make new PR, lost previous fork


5.3.9 changelog

Laravel Version: 5.3.9

Description:
plz update CHANGELOG-5.3.md file for 5.3.9 version

It'll be done in good time. If you'd like to do it, please go ahead. The change log is community contributed.


documentation for DATE_TIMEZONE(S) and zoneinfo switch

Documentation for the new AQL functions in PR #13334 / #13464
and  #13320
DATE_TIMEZONE
DATE_TIMEZONES
DATE_UTCTOLOCAL
DATE_LOCALTOUTC

I see were closing in on this.
I'm having some problems with the formatting on the return object from DATE_UTCTOLOCAL and DATE_LOCALTOUTC.
Is there any other sample in the docs where you describe a 'complex' return object.

Sorry that it took so long.
There aren't that many functions which return objects. Most of them are so simple that they are described in a single sentence. There's one notable exception however:
https://www.arangodb.com/docs/stable/aql/functions-miscellaneous.html#schema_validate
The formatting/notation is admittedly a bit strange, but I can't think of a good alternative. I'm open to suggestions.

Let me know if you can think of a better way to format complex return values.


Remove a redundant call to Router::remove_connected_peer

If we're confident that https://github.com/AleoHQ/snarkOS/pull/2168 solved the issue of missing calls to Disconnect::handle_disconnect, we can now remove this duplicate cleanup call.
Closes #2102.

Closing in favor of https://github.com/AleoHQ/snarkOS/pull/2180.


Some spawned threads block SIGPROF

@scheglov filed a report via email that after awhile his program on Linux stops being sampled. Digging into this, it appears that if a thread is spawned from the EventHandler (which is blocking SIGPROF), the spawned thread will also block SIGPROF. The stack trace at the point of spawn:
#0  0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007ffff6c050d8 in __GI_abort () at abort.c:89
#2  0x00000000007e5589 in dart::OS::Abort () at runtime/vm/os_linux.cc:406
#3  0x00000000005a3935 in dart::DynamicAssertionHelper::Fail (this=this@entry=0x7ffff7fc14f0,
format=format@entry=0xb3eba4 "expected: %s") at runtime/platform/assert.cc:42
#4  0x00000000007e76ef in dart::OSThread::Start (name=name@entry=0xdea7ea "Dart ThreadPool Worker",
function=function@entry=0x907300 <dart::ThreadPool::Worker::Main(unsigned long)>, parameter=parameter@entry=140737152813440)
at runtime/vm/os_thread_linux.cc:128
#5  0x0000000000906598 in dart::ThreadPool::Worker::StartThread (this=this@entry=0x7fffec000980) at runtime/vm/thread_pool.cc:345
#6  0x0000000000906aa3 in dart::ThreadPool::Run (this=, task=task@entry=0x7fffec000960) at runtime/vm/thread_pool.cc:70
#7  0x0000000000749c68 in dart::MessageHandler::PostMessage (this=0x1230310, message=0x0, message@entry=0x7fffec000920,
before_events=before_events@entry=false) at runtime/vm/message_handler.cc:152
#8  0x000000000083e3fd in dart::PortMap::PostMessage (message=0x7fffec000920) at runtime/vm/port.cc:258
#9  0x0000000000598fdf in dart::PostCObjectHelper (port_id=898657390, message=) at runtime/vm/native_api_impl.cc:56
#10 0x00000000005a67cc in dart::bin::EventHandlerImplementation::HandleEvents (this=this@entry=0x11491e0,
events=events@entry=0x7ffff7fc1de0, size=) at runtime/bin/eventhandler_linux.cc:352
#11 0x00000000005a6a10 in dart::bin::EventHandlerImplementation::Poll (args=args@entry=18125280)
at runtime/bin/eventhandler_linux.cc:399
#12 0x00000000005a1d59 in dart::bin::ThreadStart (data_ptr=) at runtime/bin/thread_linux.cc:91
#13 0x00007ffff7bc4182 in start_thread (arg=0x7ffff7fc2700) at pthread_create.c:312
#14 0x00007ffff6cc547d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Note this doesn't occur on MacOS

A simple way to reproduce this is a Dart program that does the following:

Do some work in main().
Schedule a timer for 30 seconds in the future.
Do some work in the timer callback. Nothing will be sampled here.

Stack trace of spawned thread blocking SIGPROF:
#0  0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007ffff6c050d8 in __GI_abort () at abort.c:89
#2  0x00000000007e5589 in dart::OS::Abort () at runtime/vm/os_linux.cc:406
#3  0x00000000005a3935 in dart::DynamicAssertionHelper::Fail (this=this@entry=0x7ffff4a8be20,
format=format@entry=0xb3eae4 "expected: %s") at runtime/platform/assert.cc:42
#4  0x00000000007e7457 in dart::ThreadStart (data_ptr=) at runtime/vm/os_thread_linux.cc:106
#5  0x00007ffff7bc4182 in start_thread (arg=0x7ffff4a8c700) at pthread_create.c:312
#6  0x00007ffff6cc547d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Fix is here: https://codereview.chromium.org/1953143002


Updating Calico-Kube-Controller from 3.10 to 3.11 inadvertidely caused deletion of all nodes and workloadendpoints

At the end of our main Production cluster, as the last component, we updated Calico-Kube-Controller from 3.10.2 to 3.11.2.
For some unknown reason, all entries for calico nodes and workloadendpoints got removed from our ETCD database.
As side effects, all of our 5000+ pods lost connectivity and had to be restarted.
A downgrade from 3.11 to 3.10 also triggered the event - all nodes and workloadendpoints got removed again.
A valid sidenote: we've updated 4 clusters, and it only happened on 1 (the important one, of course), so it most likely irreproduceable.
Expected Behavior
 Flawless update and beers;

Current Behavior
 Fire and brimstone and long hours to recover everything.

Possible Solution

I wouldn't say a solution, but we removed 'node' from enabled controllers for the kube_controller since this misbehaviour:
    - name: ENABLED_CONTROLLERS
      value: policy,namespace,serviceaccount,workloadendpoint

Steps to Reproduce (for bugs)

Its probably irreproduceable, since it didn't happen before on our 'trial' updates.
Context

I'd guess that it might be due to stale data on our ETCD datastores.
We use IP addresses of our nodes as their nodename, but neither IPs or names changed during migration.
It happened both ways: 3.10 to 3.11, and rolling back from 3.11 to 3.10.
It was also triggered before, after we inserted some 3.11 calico-node machines on a mainly 3.10 cluster.
Even though it might be impossible to pinpoin the cause, since this is a soul crushing and major breaking event, if you guys want to, I'd accept some suggestions of scenarios to try and identify what happened. I.e., I wonder if maybe if I spin up some VMs that roll ETCD backups and 1 kubernetes master running we might map what caused it.
Your Environment

Calico version: 3.11.2 with ETCD datastore;
Orchestrator version (e.g. kubernetes, mesos, rkt): Kubernetes, kube controller running as pod;
Operating System and version: CoreOS 2303.3.0
Link to your project (optional):

@mrrandrade any updates on this issue? Would really like to get to the bottom of it if we can!

@mrrandrade Could you give us an update on this one? Thanks

Closing this out under the assumption that you all got to the bottom of your issue.  Please re-open if you still need help!

Hey, I came here to this long forgotten issue to apologize, I got realocated to something else that was of a higher priority so had to just pretend everything was "normal" and move on. I only get about 1 day or 2 in a semester window to figure out stuff about this problem, which clearly is not enough.
Not only that, but I switched github accounts, which means I didn't get the notifications of the follow ups.
Again, truly sorry for "having forgotten" about this and no, no one actually got to the botton of the issue (we still run calico without the node controller because of the fears).


[Bug] 星穹鐵道多帳號躍遷更新紀錄結果顯示異常

Description
我有兩個國際服的帳號，一個是透過米哈遊帳號註冊登入(80開頭)，另一個是透過 Google 帳號登入(82開頭)。
躍遷紀錄分別為 49 次(80開頭)和 38 次紀錄(82開頭)。

Reproduction Steps
一開始我先登入的米哈遊帳號，並且有了一次以上的更新紀錄，之後我新增了我另一個 Google 帳號的紀錄。
如果你要指定某一个账号，请使用更新记录（缓存的 URL）。

游戏内最后一次登录的哪个账号，更新记录时获取的就是哪个账号的抽卡记录。如果你要指定某一个账号，请使用更新记录（缓存的 URL）。

瞭解，感謝答覆
這筆我就先Close了


added Tushar's details

Updated my bio, current research, and publication.

Thanks @tushartushar and @dspinellis !


Failed to get blob object from return value of $fetch.raw

const resp = await $fetch.raw("https://test.com/blob");
console.log(resp.blob()); // caused error

get Failed to execute 'blob' on 'Response': body stream already read
still can get data by resp._data

@ppodds
ohfetch package has been updated since you created this issue, so would you try it again with the latest version?
If you find it still does not work, please reopen this issue with a reproduction.

I have the exact same issue.
Reproduction is quite simple :
// Run on browser
import ofetch from "ofetch";
const response = await ofetch.raw("/n/assets/favicon.png", { responseType: "blob" });
await response.blob(); // <- trigger TypeError: Response.blob: Body has already been consumed.

It seems ofetch.raw already parse the response and put it in response._data.

The exact same code with native fetch instead of ofetch works perfectly

@ppodds @NozomuIkuta can you reopen this issue or should I create a new one ?

@felicienfrancois
I just reopened this issue for now.
Would you provide a working reproduction in Stackblitz or something else?

@NozomuIkuta here a working reproduction on node
https://stackblitz.com/edit/stackblitz-starters-zyf8ky

$fetch always consumes body. As per docs, you can directly use res._data:
import { ofetch } from 'ofetch';

const res = await ofetch.raw('https://fel.icien.fr/favicon.png', {
  responseType: 'blob',
});

console.log(res._data); // <-- Blob {}

$fetch always consumes body. As per docs, you can directly use res._data:

Is this  also the recommended way to access the data inside onResponseError handlers to e.g. access error reasons in JSON form send by the backend? Having to use _data (where the underscore usually notes private, undocumented, fragile interfaces often without any stability guarantees between library versions) seems very hacky and is commonly configured to raise a warning by linters.


⚠ Bofrost.be has degraded performance

In 11ffe0d, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1734 ms

Resolved: Bofrost.be performance has improved in b233f15.


Test out strategies

Test out strategies using the simulator. Record any errors.

I will be working on this aswell, still need to be added to the github.


Add more plant types to the initial database creation

This will create a better database for the user to start with. Code is in DataAccess.Local.HomesteaderRepository

Also add comments for the plants that gives some detail on them.


NameError

Unexpected error: <class 'NameError'>
An error occurred internally.
Traceback (most recent call last):
File "tallyarbiter-gpolistener.py", line 165, in
sio.connect('http://' + server + ':' + port)
NameError: name 'server' is not defined
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "tallyarbiter-gpolistener.py", line 179, in
doBlink(0, 0, 0)
NameError: name 'doBlink' is not defined

Fixed with the new update


[PackageGraph] Fix package name validation for product target dependencies

The package name validation was wrong for product target dependencies
(.product(name: "<product>", package: "<package>")) as we were looking
up the package using its identity instead of the name. This completely
breaks package loading in 5.2 if a package wants to use a product from
a dependency that doesn't match the package name of that dependency.
rdar://problem/59821906
(cherry picked from commit e3a880b310e5ded7e19a0f8cb3ca91f5e1e777a9)

@swift-ci smoke test


[Text-field] Number input

Request from AI - Valentina
Is your feature request related to a problem? Please describe.
Number input is a two-segment UI control used to incrementally increase or decrease a numeric value. The two buttons are placed farther apart and allow for easier selection.  For horizontal steppers, plus and minus signs usually work best as labels for the step segments.
Describe the solution you'd like
Ability to set the most frequently selected value as a stepper default. Ability to the quick entry of a number using a text field along with stepper buttons on the sides for adjustment. Block words typing in stepper field. Selecting a value greater than set or less than set should be disabled.
Describe alternatives you've considered
Design proposed by Valentina -

Additional context
Examples from other design systems:

Carbon

Shopify

Spectrum

We can currently support this -

what's the conclusion here? which of the designs above are we planning for?

I need to talk about it with the designers in the vivid discussions, but I thought for the first step you will add the one we currently support?
this one?

After design discussion with designers, and agreeing on the desired design, this variant can be developed :)
Design here.
Thank you!

Please notice the comment on the separator between the button-controls

interesting article about - not every input that contains numbers should have an input type number:
https://kilianvalkhof.com/2022/css-html/are-you-sure-thats-a-number-input/


Go To Symbol is Broken

Hi,
I think "Go To Symbol" is broken in latest version. Paste the below snippet in editor and press "CMD + Shift + o". It will not show "getName" and "getAge" in list. It used to work in previous versions.
function Employee() {

}

Employee.prototype = {
	getName: function() {

	},
	getAge: function() {

	}
};

-Thanks

This requires a new/better TypeScript version