Integrate scrape metadata into code files

We've got a great spreadsheet where we're storing metadata about our scrapes. My proposal is that we write these values into the Python as __ values at the top of each file. Those values could then be published in our dashboard table in the docs via our automated doc generator.
The table would give us everything the spreadsheet does. By integrating the metadata into the repository we wouldn't have to keep up a separate sheet, which is less work, and we'd be able to more closely monitor changes.

@palewire One question to consider -- for the __authors__ dunder var, should we use GH contributor usernames instead of actual names? Or perhaps both? That could let us link to the contributor home pages using our auto-doc generators. So a convention such as __authors__ = 'Ben Welsh:palewire,Dilcia Mercedes:dilcia19' etc.?

Gotcha. Maybe just a list and not a string, too.

This has been superseded by #334 and #335


Add help for user status (admins only) on profile page

If I have a quick operation to perform, sometimes I forget which status does what.

Put it in a howto on IG?


[Question] About "modality_lengths" in vicuna-v1.5

Question
Awesome work~
Q1: I see that in the latest code base, there are two new func called "modality_lengths" and "lengths" in train.py.
May I know what is the usage for these two func? Since I don't see where they are called.

Q2: Does llava-v1.5 support task like translation? I see that llama-2 is not good at it as author mentioned.
Looking forward to your kind reply~

Are you working on translation and tried with llava? if you've done it, plz share your thought and results on it. thx

Question
Awesome work~
Q1: I see that in the latest code base, there are two new func called "modality_lengths" and "lengths" in train.py. May I know what is the usage for these two func? Since I don't see where they are called.
Q2: Does llava-v1.5 support task like translation? I see that llama-2 is not good at it as author mentioned.
Looking forward to your kind reply~

In llava/train/llava_trainer.py, it is used in LengthGroupSampler.


HIP 108: Mobile Hotspot Suspension Framework

HIP 108: Mobile Hotspot Suspension Framework

Author(s): @zer0tweets
Start Date: 2024-01-27
Category: Meta, Governance
Original HIP PR: #886
Tracking Issue: #887
Vote Requirements: veMOBILE Holders

Summary
This proposal outlines the duties and guidelines for MOBILE hotspot vendors (CBRS and Wi-Fi) as it relates to suspending hotspots engaging in counterproductive and/or malicious activity on the MOBILE network.
Rendered Text
https://github.com/helium/HIP/blob/main/0108-mobile-hotspot-suspension-framework.md

@zer0tweets  it might be worth including know VPN ip addresses. For instance users in China might try to fake the CPI location via VPN backhaul ..


How to pull application logs

I'm having an issue signing in where I get "Error: unknown" in red at the top at initial sign-in on a completely new docker install.  I looked around but could not find how to pull application logs (container logs don't give anything useful). I think it might be a DNS issue.
Any help?  TIA.

To get the TeslaMate Docker container logs, for example, use the following command: docker-compose logs teslamate.

Thanks @cwanja.  I did look at the container logs but they didn't result in any useful information.  I was hoping their might be a shell script I could execute through a docker exec command.  I'm getting the following error and I'm having trouble tracking it down.

I'll likely open another question on this since my title is misleading trying to track it here.

Hey, just had a similar issue. You know it's a DNS issue (out to the world) if you see :nxdomain from the teslamate container, or if you see nc ... when running docker-container top (DNS between containers)


Fixed #34455 -- Unified language prefix handling from LocalePrefixPattern and LocaleMiddleware.

Ticket: https://code.djangoproject.com/ticket/34455

@oussjarrousse Does it work for you?

@sarahboyce Thanks :+1: I added a release note.


fix: Respect detectionTimeout on iOS

Respect detectionTimeout on iOS devices, instead of arbitrarily waiting 10 frames
Don't start a second scan until the first one is done, to keep memory usage more fixed if the device is slow

Thanks for the contribution!


storage: API should use structs or interfaces rather than free functions

The storage package is currently a grab bag of free functions:

ACL
BucketACL
ListObjects
(etc.)

(Side note: some of these are poorly named. I can't tell from its name what ACL does. It really should be called GetObjectACLs or similar.)
Because each of these is a free function, if I write code that operates on GCS I can't easily give it a fake GCS implementation for testing.  This is busy work for each of us, and it makes it impossible to offer an 'official' fake.
Additionally, the free function approach means that authorization material needs to be handed over anew on each call to the package. Currently this takes the form of a context.Context implementation with a magic entry in its value map that can only be checked at runtime. It is very easy to accidentally do the following:
type myRequestHandler struct {
  authenticatedTransportForGCS *http.Client
}

func (h *myRequestHandler) HandleRequest(ctx context.Context, ...) error {
  // Spot the bug!
  return storage.DeleteObject(ctx, "bucket", "object")
}

The bug is easy to miss at first glance. The handler is invoked with a context and must supply a context to storage.DeleteObject, so it's natural to just pass in ctx. And the compiler will be happy with that. But this will cause a run-time panic, because you should have remembered to instead call cloud.NewContext.
myRequestHandler shouldn't need to know about the authorization issues involved in the storage package; it should just be able to accept a struct representing a GCS bucket and call into it with its plain old request context (to support cancellation).
So for these reasons, I think the following would be a better approach:

The storage package defines interfaces like Bucket, containing methods like NewWriter and DeleteObject.

In order to get hold of a bucket, you call storage.OpenBucket, which accepts an http.Client. (Actually you probably do something like get a Conn object that lets you create, delete, and open buckets. But similar idea.)

Each method accepts a context.Context, so that it is cancellable. But the context is a plain old request context; it need not have any special junk added to its value map. So the myRequestHandler example above is not buggy.

Methods don't need to specify the bucket name; it is implicit in the bucket you are calling.

Optionally, the package provides good fakes for all of its interfaces, for use in tests.

Now code that calls GCS can be agnostic to how authorization works (it need only have a bucket interface injected). You can't screw up and forget to passthe right kind of context; instead the compiler checks that you've handed over  an HTTP transport at the right point. And in tests you can easily use fakes.
If it helps to see an example, github.com/jacobsa/gcloud/gcs is a partial implementation of this idea. There is a fake at github.com/jacobsa/gcloud/gcs/gcsfake.

It really should be called GetObjectACLs or similar

In Go, you never prefix getters with Get. It could have been ObjectACL, but it's unnecessary verbose. Godoc explains what the call does well, it's quite obvious from the signature as well.

have to write my own wrapper struct/interface and then fake that.

No, you can provide your stub RoundTripper to the context to handle fake the responses. We should provide some testing utilities to make it easier/visible. The question is whether it's convenient to depend on network level mocking.

Currently this takes the form of a context.Context implementation with a magic entry in its value map that can only be checked at runtime

Context objects are evil, but it was a sacrifice to keep the API surface similar to the Go AppEngine packages. I'm agreeing that a flat API surface with context.Context is not necessary and can be replaced by connection and service types. We can always box the type of the context, let's say, with cloud.Context, so you get the compilation-time errors.

I don't think @jacobsa is suggesting removing the context.Context arguments from the calls; they're necessary in a lot of contexts. Just that providing the authentication via the context argument is wrong.
Take a look at the package he put together: http://godoc.org/github.com/jacobsa/gcloud/gcs
@jacobsa can you point me toward a usage of your API? I'm curious how it looks in practice, particularly the authentication stuff.

Also, I don't think a concrete type like cloud.Context would be a great solution here. Introducing our own context type would mean it wouldn't play well with standard context mechanisms, like timeouts.
I think if we took the "context"-ness out of cloud.Context, then we'd be left with something more akin to a Client. What @jacobsa is calling a gcs.Conn.

Just that providing the authentication via the context argument is wrong.

I do not think it's entirely wrong. If you authenticate with a service account, it's just awkward. Because the authentication is actually free from the request context. But from a user access token point of view, it makes sense to keep the auth bits in a value context. You may say putting an HTTP client in a value context is a bit extravagant, I'd agree with that.

I think if we took the "context"-ness out of cloud.Context, then we'd be left with something more akin to a Client.

There is actually nothing contexty about the context we return from cloud.NewContext. And I wonder how contexty it can get. An HTTP connection is not abort-able, yet a timeout could be set. So, deadline and timeout issues should be decided at the initialization of the connection object (on the HTTP client). That's why I don't see a reason why we should keep having a context argument.

We should be aiming to get rid of cloud.Context and only use the standard net.Context. Anything that's special to an API should be attached to that as a context value, or passed as an explicit function argument, or be used to configure a Client type.
A context argument gives timeout/deadline control (on a per operation basis), and also tracing (e.g. dapper). An HTTP request is definitely abort-able (see the CancelRequest method). But if there's things that are outside the scope of a single request (e.g. auth details for a long-lived connection) then they don't belong in the context but rather in some other persistent value (e.g. a Client type).

@rakyll: You're right that you can fake RoundTripper, but that is extremely difficult compared to a fake for a service-specific interface -- it requires you to implement much more of the GCS stack than what the interface actually cares about (a map from keys to values).
I do think a plain old "golang.org/x/net/context"-type context should continue to be there, for essentially the reasons dsymonds said. But the HTTP client doesn't need to go in there for the usual reasons that layering is nice: the user of the interface doesn't care about the fact that the interface is implemented with an HTTP client, so they shouldn't have to hand it one. Just like I don't have to hand a file descriptor to an io.Reader that I was handed.
@adg: I have a real user of the package, but it's not yet open source. I've added you as a collaborator so you can see it. The Bucket interface is injected into the code in the fs/ directory, which therefore doesn't need to care about HTTP at all. See getConn in the root directory for the wiring code.

By the way, if it got lost in the noise: there is a fake that faithfully implements the Bucket interface here. Take a look at the source; it's quite easy to fake this sort of interface. It would be much more difficult to do it at the HTTP layer.

A bit late, sorry.
@dsymonds, we wrap the generated client that doesn't expose the request objects. We need to provide a custom RoundTripper to capture the ongoing request and cancel it when time has come. I'm not sure how readable it will be, so some experimental work would be very valuable to evaluate this idea.
@jacobsa, we may think of providing some stub RoundTripper generators from a testutil package. I don't think introducing an interface and a concrete type is the approach in Go when it comes to testability. Browse the entire standard library and you won't see interface definitions for the sake of mockability.
I agree that we should keep the context argument and don't depend on the transport layer for any context-related functionality. Context may depend on the transport layer, but the transport layer shouldn't replace the context.

It doesn't have to be an interface type; a struct would be almost as good, because then the user can still define their own interface around it.
I disagree with your assessment of the standard library (assuming you mean to imply that a struct is also not a good choice). All over the place it uses structs and interfaces with methods in this sort of situation rather than free functions. The interface for writing to a file doesn't look like this:
func WriteToFile(fd int, p []byte) (int, error)

Instead you have an os.File struct, which you can inject into anything that expects an io.Writer or an io.WriteCloser, or even an os.File. The user doesn't have to manually carry around the file descriptor and hand it to free functions, which is something like manually carrying around an HTTP client.

This work was started in b467501b


I added a new renders + constants if you want :)

If only we could do pull requests for just these files! Thank you, I'll push it to master and Muledump Online tonight as v0.8.1-7.

You're missing this:
./Pets.xml:

I've pushed this to Muledump Online, finally. It'll be included in the next actual release of Muledump Local.
I look forward to the next update with Moon Bunny and the Halloween updates :)
Thanks!


Add "Launching methods" under each status bar tutorial

For this I will open a PR adding the launch commands for Hybrid and Waybar since It's not all that hard but I am very confused on what command to use for launching ewwbar, If anyone knows how to do that, send it under this issue or open a PR.
If you as a maintainer are reading this, please add the launch commands! It would be very helpful to anyone new to Waybar, Eww or Hybrid (more so to new eww users)

eww daemon && eww open <your_bar_name>

or you can just eww open/eww open-many, it will start the daemon if not already running

eww daemon && eww open <your_bar_name>

bar_name is that of defwindow <bar_name> in your .yuck
or you can just eww open/eww open-many, it will start the daemon if not already running

I'm not entirely familiar with setting up eww yet. I've forked this repo and have added a few changes, would you be willing to add a few lines there that we could open a PR with?

I believe this is out of scope for the wiki. Each of the listed projects already have the instructions in their READMEs.


[BUG] White box appearing at bottom of App

On https://github.com/voxel51/fiftyone/pull/747, there is a small white box appearing at the bottom left of the App. It is present in both the browser and desktop versions of the App.

Hmm, I don't see it using fiftyone==0.7.1rc66 and fiftyone-desktop==0.8.0rc0 though.

Hmm, I don't see it using fiftyone==0.7.1rc66 and fiftyone-desktop==0.8.0rc0 though.

Working on it. This arises when long field names are in the dataset. Likely affects fiftyone==0.7.1rc66 though I haven't checked yet.

Working on it. This arises when long field names are in the dataset. Likely affects fiftyone==0.7.1rc66 though I haven't checked yet.

Resolved by #747

Resolved by #747


How do I upload file with parameters?

Hi,
How do I upload file with parameters?
given().
.param("key","value")
.param("key","value")
.param("key","value")
.multiPart(new File("/path/to/file.zip")).
when().
post("/upload")
.then()
.statusCode(200).log().body();
Thanks!

Please use the mailing list, http://groups.google.com/group/rest-assured.

Hi @johanhaleby
tried looking for a similar problems like I have (https://groups.google.com/forum/#!searchin/rest-assured/upload|sort:date/rest-assured/6j3JwM5BazY/cWxRCeu3BAAJ), still no luck, can you help me with this issue? Thanks!


Adding MDCS scripts and config files for generating mosaic datasets

Add a directory containing the files associated with Esri's MDCS workflow for generating mosaic datasets. These mosaic datasets are used by the ArcGIS Image Server or Dedicated Imagery service to publish image services.

@hjkristenson which files haven't been updated? All the python files that had the Ersi copyright should have been updated. You might just need to pull

@hjkristenson Ah, I understand. I think broadly re-applying the copyright for any modifications (whether or not they exist) is the right approach since we're "redistributing" them and then we don't have to worry about it in the future. We can track modification ourselves, or if we want to state specific changes, we can include a CHANGES.diff file

@jhkennedy Great. That sounds good. Thanks!


Switching menubar display position failed with error

Reproduction steps:

Use vscode.dev to open a project, such as https://insiders.vscode.dev/github/microsoft/vscode
Switch the top menubar from TitleBar to the ActivityBar, or do the opposite.
After switching several times, it was found that the switch failed. If you open the console, you will find an error.

Version: 1.87.0-insider
Commit: ee69e2887fbe532588f74ae86560e7fdc1e59550
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: vscode.dev

ref: https://github.com/microsoft/vscode/issues/199744, because command with the same name cannot be registered now.
The process of switching menu bars is accompanied by the destruction and initialization of two custom menu bars from A and B respectively, and their destruction execution order cannot be guaranteed. When one of the instances is destroyed and executed, the initialization of the new instance will have this problem, because initialization means registering a command with the same name.
https://github.com/microsoft/vscode/blob/f7f9fb09a3200246a55da9d6882d56b82eb4fe9a/src/vs/workbench/browser/parts/titlebar/menubarControl.ts#L440

I think the issue here is that the menu bar control gets disposed in the one place and then created in the other place (title bar, activity bar) but the order is not guaranteed to be dispose first and create later, as such this action gets first registered a second time and then gets disposed:
https://github.com/microsoft/vscode/blob/67f91582f588d1d37a94ce5b18e01ba535184967/src/vs/workbench/browser/parts/titlebar/menubarControl.ts#L437-L454

id: workbench.actions.menubar.focus,

Yeah, I found it, too. My original idea was to ensure that it was reasonable to reinstall after the uninstall was completed through some event mechanism, such as use this.titleService.onMenubarVisibilityChange, but that would require listening on both sides.

We only recently changed to throwing an error in this case which now breaks this flow, but the issue was there before already...

Yes, Previously command with the same name can be overwritten without causing a problem. The exception thrown now causes the handler to not be executed and the switch fails.

Switch the top menubar from TitleBar to the ActivityBar, or do the opposite.

How can I do this? I'm having trouble understanding how to get the top menu to show at all. I can only get the hamburger menu.

Finally found it.


File Details Panel

Panel that shows detailed information about the selected file, such as its size, type, and attributes.

Same as Issue #4


Using "-" in gen.py

My country plate has - in plate like 29-A1 1234 but i can't use - in my code.
When i add - to my code, it return KeyError: '-'
Can anyone help me to solve it?

You need to edit the commons.py adding ta symbol category

I’m not sure how to do that, can you show me an example?


It looks like you've wrapped styled() around your React component (ReactTooltip), but the className prop is not being passed down to a child. No styles will be rendered unless className is composed within your React component.

It looks like you've wrapped styled() around your React component (ReactTooltip), but the className prop is not being passed down to a child. No styles will be rendered unless className is composed within your React component.

I get this warning when I use it with Styled-Components as Below
import ReactTooltip from 'react-tooltip
import styled from 'styled-components'

export default styled(ReactToolTip)`
// some styles
`

Quick fix, you can turn off the warning using .attrs({ suppressClassNameWarning: true }) provided by styled-components as below...
import ReactTooltip from 'react-tooltip
import styled from 'styled-components'

export default styled(ReactToolTip).attrs({ suppressClassNameWarning: true })`
// some styles
`

I have the same issue. Any plans to fix it?

Sounds like it might be a fairly easy fix - we would welcome a PR :)
On Thu, Oct 10, 2019 at 3:45 AM Jakub Syrek<EMAIL_ADDRESS>wrote:

I have the same issue. Any plans to fix it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wwayne/react-tooltip/issues/489?email_source=notifications&email_token=AEX6THKH3BL55WIEPFAWEU3QN3MQFA5CNFSM4HINVWXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA3HWNQ#issuecomment-540441398,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEX6THNP7AUI6OWDLLV57M3QN3MQFANCNFSM4HINVWXA
.

Hi @yqbk, would you try the new version and let me know if the issue continue.

@Rogger794, unfortunately, the problem still exists (version 3.11.5).
import React from 'react'
import ReactTooltip from 'react-tooltip'
import styled from 'styled-components'

const StyledTooltip = styled(ReactTooltip)`
  max-width: 20vh;
  white-space: normal;
`
const Tooltip = ({ ...props }) => (
  <StyledTooltip effect="solid" multiline place="top" {...props} />
)

export default Tooltip

Warning:
backend.js:6 It looks like you've wrapped styled() around your React component (ReactTooltip), but the className prop is not being passed down to a child. No styles will be rendered unless className is composed within your React component.

I updated the form it pass the styles, could you try the new release 3.11.6 and tell me if it works.

@Rogger794 It fixes the problem! Thank you! :)