fatal error: miniz.h: No such file or directory

Hi @stricaud,
how can I fix this issue?

I pulled last commit and build fails in Travis of you project and also in SpamScope. I tried to build on my server and I think there is a wrong import of miniz.h.
Fails this import.

Thanks, this is the last change I did anyway, I will revisit. I was surprised as I did a fresh clone somewhere else and did not reproduce. However with the information you gave me I should be able to fix it shortly. Thanks!

Thanks, SpamScope is waiting you...

If you need more info, this was on Ubuntu 18.04
make
Scanning dependencies of target faup_static
[  1%] Building C object src/lib/CMakeFiles/faup_static.dir/civetweb/civetweb.c.o
[  3%] Building C object src/lib/CMakeFiles/faup_static.dir/webserver.c.o
[  5%] Building C object src/lib/CMakeFiles/faup_static.dir/b64/cencode.c.o
[  7%] Building C object src/lib/CMakeFiles/faup_static.dir/b64/cdecode.c.o
[  9%] Building C object src/lib/CMakeFiles/faup_static.dir/hash/hash.c.o
[ 11%] Building C object src/lib/CMakeFiles/faup_static.dir/hash/htable.c.o
[ 13%] Building C object src/lib/CMakeFiles/faup_static.dir/datadir.c.o
[ 15%] Building C object src/lib/CMakeFiles/faup_static.dir/decode.c.o
[ 17%] Building C object src/lib/CMakeFiles/faup_static.dir/features.c.o
[ 19%] Building C object src/lib/CMakeFiles/faup_static.dir/faup.c.o
[ 21%] Building C object src/lib/CMakeFiles/faup_static.dir/options.c.o
[ 23%] Building C object src/lib/CMakeFiles/faup_static.dir/output.c.o
[ 25%] Building C object src/lib/CMakeFiles/faup_static.dir/parson.c.o
[ 27%] Building C object src/lib/CMakeFiles/faup_static.dir/portable.c.o
[ 29%] Building C object src/lib/CMakeFiles/faup_static.dir/snapshot.c.o
/home/user/faup/src/lib/snapshot.c: In function ‘faup_snapshot_output’:
/home/user/faup/src/lib/snapshot.c:395:12: warning: ‘return’ with a value, in function returning void
     return NULL;
            ^~~~
/home/user/faup/src/lib/snapshot.c:384:6: note: declared here
 void faup_snapshot_output(faup_handler_t *fh, faup_snapshot_t *snapshot, FILE *fd)
      ^~~~~~~~~~~~~~~~~~~~
[ 31%] Building C object src/lib/CMakeFiles/faup_static.dir/snapshot-file.c.o
/home/user/faup/src/lib/snapshot-file.c:16:10: fatal error: miniz.h: No such file or directory
 #include <miniz.h>
          ^~~~~~~~~
compilation terminated.
src/lib/CMakeFiles/faup_static.dir/build.make:422: recipe for target 'src/lib/CMakeFiles/faup_static.dir/snapshot-file.c.o' failed
make[2]: *** [src/lib/CMakeFiles/faup_static.dir/snapshot-file.c.o] Error 1
CMakeFiles/Makefile2:1048: recipe for target 'src/lib/CMakeFiles/faup_static.dir/all' failed
make[1]: *** [src/lib/CMakeFiles/faup_static.dir/all] Error 2
Makefile:162: recipe for target 'all' failed
make: *** [all] Error 2```

Same issue here on 2 different installs.
Include path issues?

Thank you guys for your feedback. This was my bad, I could not reproduce because I have LUA installed and I was fine in the LUA check. However if you did not, that meant it would not compile.

Thanks for maintaining this and quickly fixing it!


DeepResolveType breaks React.ComponentType

Hi,
useSnapshot uses DeepResolveType as the return type which breaks the type if one of the props is a ref to a ComponentType.
const store: {Comp: React.ComponentType} = {Comp: () => null}

function MyComponent(){
	const snap = useSnapshot(store) as typeof store;

	return <snap.Comp/>; // this works fine
}

function MyComponent(){
	const snap = useSnapshot(store);

	return <snap.Comp/>; // TS2604: JSX element type 'snap.Comp' does not have any construct or call signatures.
}

A component is not a serializable object, so you may want to use ref().
Hopefully, it solves the type issue.
Anyway, DeepResolveType isn't an ideal solution and we would like to improve it in the future, maybe Awaited helps.

i am using ref but the problem is asRef does not seem to b exposed and when you define the interface of the state
you cant specify the type is a ref of something. so:
this works fine because you let it infer the type, but it's not a solution because you want to define the type of your store, not infer it from a specific value.
const store = {Comp: ref(() => null)}

function MyComponent(){
	const snap = useSnapshot(store);

	return <snap.Comp/>; // this works fine
}

if you try to define it, it breaks
const store: {Comp: React.ComponentType} = {Comp: ref(() => null)}

function MyComponent(){
	const snap = useSnapshot(store);

	return <snap.Comp/>; // TS2604: JSX element type 'snap.Comp' does not have any construct or call signatures.
}

Thanks for the explanation. Yeah, this is asked before, but we avoid to expose AsRef because it might be changing in the future.
Does this work in your use case?
const store = proxy({
  Comp: ref<React.ComponentType>(() => null),
})

or
const store = proxy({
  Comp: ref((() => null) as React.ComponentType),
})

But, I now think your first workaround is good enough in the meantime:
const snap = useSnapshot(store) as typeof store

this works, but i have to infer the type from the value. which is not what i want
const store = proxy({
  Comp: ref<React.ComponentType>(() => null),
})

type Store = typeof store;

i want to define the type of my store then use it
type Store = {
    components: React.ComponentType[];
}

const store = proxy<Store>({
  components: []
})

while this works, it is not very clean..
const snap = useSnapshot(store) as typeof store

How about this? I didn't try it though.
// we expect this is eliminated with minification.
const dummyRef = ref<React.ComponentType>(() => null)
type RefComponentType = typeof dummyRef

type Store = {
  components: RefComponentType[]
}

How about this? I didn't try it though.
// we expect this is eliminated with minification.
const dummyRef = ref<React.ComponentType>(() => null)
type RefComponentType = typeof dummyRef

type Store = {
  components: RefComponentType[]
}

There is a TS error
Exported variable 'dummyRef' has or is using name 'AsRef' from external module "node_modules/valtio/vanilla" but cannot be named.ts(4023)

🤦♂

i'd rather use as typeof store anyways haha

Sorry for the inconvenience. Thought AsRef is neat, but not very developer friendly (it breaks like this). Let's look for a better solution.


Is there a way to get the whole feed of the people I follow?

Hello,
I might be missing something, but can I get the whole feed of all the people I follow? If yes, how?
I just set up a page to deliver pictures to a DYI digital Instagram photo frame and it would be great to see other pictures than my own... (especially those of the people I follow...)
Thanks for any help! And also thanks for this great peace of code. Will pay for beer/coffee for sure!

Closed as part of https://github.com/stevenschobert/instafeed.js/pull/149


[exprtk] Update to v0.0.2

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

I will be converting your PR to draft status. The above suggested changes are only recommendations. If you are willing to adopt them, please click "ready for review" after making the modifications. If you do not wish to make any changes, please click "ready for review" directly. That way, I can be aware that you've responded since you can't modify the tags.

Closing at the request of the library author - a new upcoming release should be used instead of this one.


tracking: design polish

It would be good to get a 2nd opinion on the design of some of these pages. Any suggestions would be welcome.

[ ] / (item summary spacing can probably be improved)
[ ] /stats
[ ] /blog
[ ] /account
[x] /submit (feels a bit empty)
[x] /user/:login (perhaps, the profile details could be more prominent)
[x] /pricing

Todo:

#467
#468
#469

Adding to this here just two things that might make sense:

#268 the last thing that lighthouse is complaining in order to get a perfect score is adjusting the size of the tap areas on mobile
The links on the new pricing page are hard to see on dark mode:

These are just a suggestion, not a strong opinion.
Overall / nav

A little white space stands out, so it might be better to use the space loosely
Add a little more space between the header and the main content.

Root

increase the spacing between each item
Increase title font size for each item
Added selected state to Last Week / Last Month / All time buttons (logically tab / radio buttons)
Add buttons to pagination UI (I usually refer tailwind UI)
upvote button should be implemented with button element (for accessibility, keyboard operation)

/stats

Maybe create a section to display numbers such as today's total visitors, weekly total visitors, etc

/blog

Increase font size of main content

/item/:itemId

Increase font size of title text etc
maybe add a back link (you can go back by clicking the logo, but to clarify the relationship between collection view and single view)

submit
feels a bit empty, but I can't think of a way to improve it since there's nothing to display.

I'm not a big fan of this, but it can be used as an accent.

These are all excellent points. Thanks, guys! I mostly agree with the suggestions.

I would like to add my opinion on this. Deno's design has gradually improved to what is today, I personally love it and would like to see it reflected here as well. Here is an image of what I mean, I used screenshots from deno.land, dash.deno.land, and hunt.deno.land

Frankly, while SaaSKit takes inspiration from a few other Deno products, I'd like it to have its own flavour.

Gotcha 👌

@hashrock, many design changes have been made. Is there anything else remaining that could do with improvement? I think the design looks good now.

Actually, one issue I have is that x/tabler_icons, while great, doesn't have the official social icons. Is there another icons module that does?

I think there is no remaining thing for me. good time to close this issue

for branding icons, how about this
https://simpleicons.org/

Cool! I'll look into it!


it will throw an error when encode and decode function get a nil param

when I use rumoji, I get an error:
NoMethodError: undefined method `gsub' for nil:NilClass
i think we can fix it.

It does not feel like this library is the best place for that guard. Shouldn't you do nil checking in your implementation code?


Get the error: rpn data not found at ./data/cache/rpn_data/voc_2007_trainval_rpn.pkl

When i train faster-rcnn, i get the error:
rpn data not found at ./data/cache/rpn_data/voc_2007_trainval_rpn.pkl

Where can i get the voc_2007_trainval_rpn.pkl?

Did you directly run train_rcnn .py?
If so, you need to know that this error is because you train a detector without specifying the proposal model. And currently we didn't provide a script to optimize faster rcnn alternatively.
You may want to look at and modify https://github.com/msracver/Deformable-ConvNets/blob/master/rfcn/train_alternate.py, where we provide how to train R-FCN alternatively.

yes. Thanks!


showMessageBox options are surprising

When calling showMessageBox:
On Mac:

Options.title has no effect on Mac, the title of the message box is always empty.

Options.message uses a bold font on Mac, and acts more like the title on Mac (unless the title issue above will be fixed).

Options.detail is the best way to set the actual message on Mac (otherwise using Options.message leads to an all-bold message).

On Windows:

Options.title works as the title on Windows.

Options.message works as the message on Windows.

The message box on Mac doesn't have title, and the message is expected to show int bold.

Would it not be better then if the "title" option mapped to "message" on Mac, and if the "message" option mapped to "detail" on Mac (with the "detail" option on Mac then doing nothing)?
By the way, I noticed that message boxes from native Mac apps do show a title in the window bar, but Electron does not?
Thanks for the great work.

For example at the moment I have code which has to do:
if (Environment.mac) {
  var options = { message: title, detail: message, buttons: buttons };
} else {
  var options = { title: title, message: message, buttons: buttons };
}
Electron.dialog.showMessageBox(options);


Layer shell blur rounding

Description
When using something like rofi with layer blur the layer blur cant be rounded and it can look bad under bright backgrounds

Would it be possible to add a rounding option to layer blur?

layerrule=ignorezero,rofi

as above


Unstyled Screenshots

I was able to successfully install this storybook addon, however when I click the Feedback or Report Issue buttons the Marker screenshot of Storybook does not include the component's styles. Here's an example.
Here's a screenshot of the component in storybook:

And here's the same component in a Marker screenshot (I highlighted the component):

To help here's my .storybook/main.js file:
/** @type { import('@storybook/svelte-vite').StorybookConfig } */
const config = {
  stories: ["../src/**/*.mdx", "../src/**/*.stories.@(js|ts|svelte)"],
  addons: [
    "@storybook/addon-svelte-csf",
    "@storybook/addon-links",
    "@storybook/addon-essentials",
    "@chromatic-com/storybook",
    "@storybook/addon-interactions",
    "@storybook/addon-a11y",
    "@etchteam/storybook-addon-marker"
  ],
  framework: {
    name: "@storybook/svelte-vite",
    options: {},
  },
};
export default config;

and here's my .storybook/preview.js file:

// Docs: https://storybook.js.org/docs/react/essentials/viewport
const customViewports = {
  mobile: {
    name: 'mobile',
    styles: {
      width: '376px',
      height: '100%',
    },
  },
  tablet: {
    name: 'tablet',
    styles: {
      width: '768px',
      height: '100%',
    },
  },
  'sm-desktop': {
    name: 'sm-desktop',
    styles: {
      width: '1024px',
      height: '100%',
    },
  },
  desktop: {
    name: 'desktop',
    styles: {
      width: '1440px',
      height: '100%',
    },
  },
};

/** @type { import('@storybook/svelte').Preview } */
const preview = {
  parameters: {
    layout: 'fullscreen',
    controls: {
      matchers: {
        color: /(background|color)$/i,
        date: /Date$/i,
      },
		},
		viewport: {
      viewports: customViewports,
    },
    marker: {
      destination: 'XXXXXXXXXXXXX',
    }
	}
};

export default preview;

Hey @brentrobbins a fix has been released in 4.0.1.


Bugfix: Get logo url when no website exists

Hi.
This is a very helpful project. I noticed that when no website exists on the info, the logo url is not generated. I add a little change that in this case uses the small name that allways is present.
I think this could help with this Issue:
yfinance info logo_url value problem #1062

Hi Jossan. Thanks for contributing a PR, but as you may have noticed the PRs are not being merged in. Only one person can merge and they have effectively abandoned this.
So I'm trying to set up a replacement fork with a team of maintainers, are you interested in volunteering?


hello: Fix client logos not changing on hello page.

Since zulip.com doesn't has /hello in URL, the JS code for hello page events was not running. We extract it to a new file and just always run it.

Pushed to fix the variable names.

Looks great, feel free to merge after addressing https://github.com/zulip/zulip/pull/27079#pullrequestreview-1662193296

Merged, thanks @amanagr!


fix: rawBody on empty request.body

Currently sends empty Uint8Array, but should probably send undefined|null as per the discussion in https://github.com/sveltejs/kit/pull/2295

Base types in Kit were updated in https://github.com/sveltejs/kit/pull/2299/files#diff-418712fdcdc80e8bf5cc0e519480d6bc0178a372c82aa3675dddd4870a5988a6R25


Testing - Containerlab and Mocking / Stubbing

Opening this issue to begin discussion on how we should handle testing with v2. Currently the unit tests return mocked data and integration tests require containerlab to be spun up.
I propose the following:

A GitHub action that conditionally spins up a 2-3 node Containerlab network when an srlinux_versions.txt file is update. This file contains supported SRLinux versions and (sequentially) spins up a network, captures the JSON RPC output for each set of paths used in the driver and commits the output to the test/<version>/rpc_<paths_name>.json or the like. These fixtures can then be used "offline" by committers and during regular GH Action runs to unit test against supported SRL versions.
Using the above captured output, we can stub all _jsonrpc* methods under text fixtures and enable per-getter tests without needing an online network.
Configuration testing can be performed against a mock JSONRPC endpoint (https://colin-b.github.io/pytest_httpx/) with derived  input and output to test load / merge / commit / rollback use-cases.

@hellt thoughts / ideas / comments / discussion?

I've always considered the live integration testing with Containerlab an important differentiator for the plugin. After having Containerlab installed and downloading the Docker image, the tests can be performed "offline" and are entirely optional. CI/CD workflows on GitHub spin up Containerlab instances internally
Having a 'snapshot' of JSONRPC output isn't as comprehensive as being able to spin up any release you want, with any node configuration / topology, and then running regression testing against that. I'd expect more bugs to be found in the area of specific (combinations of) config options and/or race conditions.
In short, I'm not sure what problem you'd be solving?

@jbemmel there would still be the option of running the tests locally, but having the option to run tests easily (e.g. for small fixes) without needing a full lab lowers the barrier of entry.

@tardoe I'd say on a high level I'd split the testing into the following parts:

Raw input extraction. This is what you proposed in the first bullet point. The goal is to get the raw json responses per each getter that would be used in unit testing of getters
local/remote unit testing of getters based on the previous step. This is where we a) take the raw json input extracted before, apply the getters logic, compare the result with a golden file.
unit testing of cfg workflows (merge replace, replace, etc). I think this is where we might always require a real system, granted it is easy to spin up one locally or in actions.
gh actions would use all of the above by also introducing a matrix of py versions to the mix. If we extract the raw json responses per each getter we support, there is no real need to perform the proper e2e test for all getters, although we can easily add this as an integration test.

@tardoe there is no barrier thanks to Containerlab and SR Linux. Unlike most other platforms that developers may be familiar with, SR Linux makes an easy-to-obtain free container image available. This makes it trivial to construct CI/CD pipelines such as the one illustrated in this repo - without the user having to lift a finger!
Consequently, there is no need to jump through hoops like you are suggesting. This is the best other platforms can do - but ours (yours) is better than that


Improve logging of message creation exceptions in the RmqMessageCreator

To aid debugging when de-serialisation of RabbitMQ messages goes wrong.

thanks @george-ayris :+1:


Make kwargs injection strategy the default

I'd like to help dry-auto_inject be as usable as possible for people, and I think making the kwargs injection strategy the default would help a lot for this.
Positional args are a bit magical and complex, and it the manual replacement of specific dependencies feels really awkward (e.g. MyThing.new(nil, nil, my_dep)). Keyword arguments make this feel a lot more natural (MyThing.new(my_dep: dep)) and will make for more flexible objects in general.
I don't think we should rely on each user coming this same conclusion and then having to make the decision themselves to switch strategies; I think kwargs should be the default, and users can then switch away from this in cases where they have compelling reasons.
This is a simple change to make, and it feels like it would nice to include in the upcoming release, given we have a lot of other nice improvements to share at the same time. What do  you think?

This is a good idea, it'll be most common usage I think. In fact we might as well consider deprecating positioned args in the longer term. Time will tell.


Bug: Updating cache in apollo store no longer updates query watcher

Summary
Since version 1.4.0, writing data to the cache, query watchers no longer appear to fire.
Description
Example code (AGPL 3.0):
class PayinStatusRepository(
    private val apolloClientWrapper: ApolloClientWrapper
) {
    private val payinStatusQuery = PayinStatusQuery()

    fun payinStatus() = apolloClientWrapper
        .apolloClient
        .query(payinStatusQuery)
        .watcher()
        .toFlow()

    suspend fun refreshPayinStatus() {
        val response = apolloClientWrapper
            .apolloClient
            .query(payinStatusQuery)
            .responseFetcher(ApolloResponseFetchers.NETWORK_ONLY)
            .toDeferred()
            .await()

        response.data()?.let { data ->
            val cachedData = apolloClientWrapper
                .apolloClient
                .apolloStore()
                .read(payinStatusQuery)
                .execute()

            val newData = cachedData.copy(payinMethodStatus = data.payinMethodStatus)
            apolloClientWrapper
                .apolloClient
                .apolloStore()
                .writeAndPublish(payinStatusQuery, newData)
                .execute()
        }
    }
}

where apolloClientWrapper holds an instance of ApolloClient.
In version 1.3.3 (last known working version), when performing .writeAndPublish(payinStatusQuery, newData).execute(), the watcher fires and sends the new data out on the Flow. In 1.4.0 and up, this no longer occurs.
Version
Last known working version is 1.3.3.
Issue exists in 1.4.0-1.4.4.

Hi 👋 Sorry for the huuuuuge delay...Are you still having this issue? If yes, any chance you can try on a recent version and let us know how that went?

I'm not entirely sure about reproduction for this one anymore, but given that we are running 2.5.9 currently, I'm going to assume that it is actually working now. 🙂


Add design-goal for not being tied to specific IDEs

Use the reasoning that is also given in the "Eclipse plugin" requirement: Spoofax is currently in the process of not being tied to a specific implementation, so our REPL should do the same (or something like that).

Fixed. See ^.


Lfs fetch fail

This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

When I try to fetch pre-trained model from repo, it said this repo is over its data quota. Maybe you can use google cloud or some thing else, and put the download url in readme.md.

I uploaded the data and pretrained models to google drive and put the download links in the readme.md.


feat: add ocis_proxy example (separate web and proxy services)

Description
This is a working example of decoupling microservices from single containers in an effort to illustrate how to customise the config.json and proxy.json for use in different environments.  This example separates proxy, web, graph and graph-explorer services and has been tested with file and sharing operations to work correctly.
This also has a traefik frontend on a segregated network to the internal services via the proxy service.
Motivation and Context
Long-term goal is to have a docker compose template where all service (eg. ldap/idp/accounts/settings/storage-*) are all separate, this is the first step towards this with a meaningful example.
How Has This Been Tested?
Login as a test user (eg. admin:admin).
Upload and download files.
Share files with another user.
Login as another user and view/download the file.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

I'll have a look on this next week. In the meanwhile we have merged an example with oCIS running as individual services (https://github.com/owncloud/ocis/tree/master/deployments/examples/ocis_individual_services).
But I think your example does a great job explaining how to split out single services and we should have it, too :+1:

I'll have a look on this next week. In the meanwhile we have merged an example with oCIS running as individual services (https://github.com/owncloud/ocis/tree/master/deployments/examples/ocis_individual_services).
But I think your example does a great job explaining how to split out single services and we should have it, too 👍

Thanks for sharing - the individual services example is interesting, I will attempt to combine with this one to see if they work together as one key difference in this is that the networks are separated, which involves specifying bind ports for the services explicitly (which does yet work consistently with every service) as well as specifying bind ports for the dependencies.

@rpocklin if you are still working on this pls reopen!


Deliverable 6

Deliverable-6 is nearly done, we're merging to main early and updating testflight. Onboarding was added along with several bug fixes.

with the test cases now passing i am approving this PR to main issue with the test case was the node version running for the test cases was from 16 and the yml file was 14


implement delete and force source_image option

What this PR does / why we need it:
implement additional option for unitary management of each source_image
source_image_delete: allow to delete a downloaded image once build process is finished
source_image_force: allow to redownload a source_image even if they already exist in the library
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #124
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
Release note:
- implement delete and force source_image option

@tuxtof - When will the new release be ready that includes this fix?

Hello @ktinthecloud just release 0.8.0
i let you test and come back to me if needed

It's working as expected.  Thanks @tuxtof!

Nice , thanks for the confirmation


XMLHttpRequest: Support "upload" events

The upload property on the XMLHttpRequest returns a XMLHttpRequestUpload instance, which is similar to an event emitter. The consumer may use the upload instance to attach listeners on the request body upload progress.
const req = new XMLHttpRequest()
req.open('POST', '/upload')
req.upload.addEventListener('progress', (event) => {
  if (event.lengthComputable) {
    console.log('%d / %d', event.loaded, event.total)
  }
})

We should enable the upload events for both mocked and bypassed requests.
Event order
The upload events are called in the following order, given request body:

loadstart, request body is known, the lengthComputable value on the ProgressEventInit is set to a boolean representing if there's any upload work to be done (request has body).
progress, request body is known and read, the progress event contains loaded and total of transferred request body bytes.
load.
loadend, the upload is over.

hi @kettanaito, is there any chance that this will get fixed in the near future?

Hey, @eudinnou. This task is not on my list at the moment so I don't know when I'll get to it. That being said, you and anybody else are welcome to open a pull request with the implementation for XMLHttpRequest events. I believe I've described what has to be done in the issue's description. If you feel like making this happen, let me know and I will help you during the code reviews.

Released: v0.18.0 🎉
This has been released in v0.18.0!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i @mswjs/interceptors@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.

cool, but unfortunately it doesn't work with MSW itself :/
> TypeError: Class extends value undefined is not a constructor or null

> 1 | import { rest } from 'msw';

@KKrisu, MSW uses Interceptors v17 right now so this change is respectively not present there yet. It will be added with the Fetch API support later this year.

ok, we need to wait then, thank you @kettanaito

@KKrisu, MSW uses Interceptors v17 right now so this change is respectively not present there yet. It will be added with the Fetch API support later this year.

I also encountered this problem

cool, but unfortunately it doesn't work with MSW itself :/
> TypeError: Class extends value undefined is not a constructor or null

> 1 | import { rest } from 'msw';

I also encountered this problem, I hope the official fixes it as soon as possible

@kokiy please do not update @mswjs/interceptors manually. MSW on its latest tag relies on<EMAIL_ADDRESS>and it should stay that way.
https://github.com/mswjs/msw/blob/2633fa93af4bcbc33f12f69a6b83193684c3dfd3/package.json#L91
What you're doing is installing the next breaking version (0.18.0). Of course, things will break, they are promised to break.

@kettanaito

I followed the tutorial to configure step by step, but an error was reported, and I don't know where the problem is
repo link:  https://github.com/kokiy/react-webpack-demo

will MSW 1 be updated to use<EMAIL_ADDRESS>or obove?

I'm having this problem too. use<EMAIL_ADDRESS>How to do resovle this problem. use @mswjs/interceptors ? how to config

@kettanaito,
Is this update now available in the latest version of msw? I'm needing it, also.
Thank you!


Add prefix and suffix commands

When generating aliases it would be nice to add a prefix and suffix commands so we can generate things like watch commands/

Can now do so with general commands: https://github.com/Dbz/kube-aliases/commit/d2ee10e1c4eab0c26a5169b99a71171a25e1c6a6
Need to be able to do so for additional commands. Should be able to get to that early this week.

https://github.com/Dbz/kube-aliases/pull/20/commits/3d93b4571515eeead3522c4981570dd23af6e5ed


hotfix: add /stop

sorry bout that

The PR is missing the related issue number and QA. The exact file changes have been added and merged by another team member at https://github.com/ubiquity/ubiquibot/commit/b742637e3f95b91e0df0b36f0735d05f5b746dac
This PR can be closed without merging.

I think I already pushed that fix to the development branch.
https://github.com/ubiquity/ubiquibot/blob/development/src/handlers/wildcard/unassign.ts#L75


Update documentation to clarify support for flavor dimensions

Hi,
We had a premier customer who was confused about product dimension support for native android and we thought about a pull request to be more clear about product dimensions not being supported.
Christopher E. Rodriguez
MSFT Support Engineer

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

Based on some separate discussion, it seems like it's tricky to finalize this outside of the internal mirror. So I'm duplicating it into https://github.com/MicrosoftDocs/appcenter-docs-pr/pull/1936 and closing this PR.


Only Human - (From "Sierra Burgess Is a Loser") by Maggie Szabo unsupported.

Check if issue with swaglyrics or whether song lyrics unavailable on Genius.

not on genius.


ARTEMIS-1341 fix getBytes

https://issues.apache.org/jira/browse/ARTEMIS-1341

Behaviour should be the same, which ever JMS client they use, I'm not in favour of behaviours being different, this gives a bad experience to users if one client behaves one way and another behaves another.

Behaviour should be the same
True, there was little misunderstanding. I am working at fix.

This is just test fix. There are some issues with clients. I'll get back to it later.

Likewise i don't understand why OpenWire is skipped

Skipping OpenWire is appropriate here, as Message#getBody was added in JMS 2.0, and activemq-client implements only the 1.1 version of the JMS spec.

@jdanekrh cheers, makes perfect and very obvious sense. slaps hand against forehead and smashes it on table it’s been a long few days.

@stanlyDoge is this ready? If so could you squash the commits into one?

@michaelandrepearce Yes, it should be ready.

@stanlyDoge unfortunately it seems there is a build failure of this PR, could you look at it?

Oops with squashing. Should be ok now, let's wait for check.

@stanlyDoge I believe this is breaking the compatiblity testsuite I just added...
I'm glad I did :)

@stanlyDoge actually.. my bad.. I had something wrong...
At least I'm watching it ! :)

@clebertsuconic double check is better than no check :) Thank you.


--nodeport-addresses added on kube-proxy.manifest.j2 and on k8s-cluster.yml

Hi, i'm using kubespray to provision a cluster on hetzner cloud, and using internal vpn addresses i needed kube-proxy to use that cidr for nodeports instead of all interfaces.
I added two variables on k8s-cluster.yml and a condition on kube-proxy.manifest.j2
Info about --nodeport-addresses flag:

https://kubernetes.io/docs/concepts/services-networking/service/
https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/

Tested on hetzner cloud with terraform

@woopstar ok will do now

@woopstar , added kubeadm config v1alpha2

/assign @smana

Any reason not to add it to kubeadm-config.v1alpha1.yaml.j2

@woopstar you are right, i was reading https://v1-10.docs.kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/# but in the https://godoc.org/k8s.io/kubernetes/pkg/proxy/apis/kubeproxyconfig/v1alpha1#KubeProxyConfiguration there is listed NodePortAddresses

/retest

ci check this

/lgtm
/approve


Publish forecast to Hugging Face at 9am every day

Pull Request
Description
Publishes the site level forecast for a single site at 9am every day.
I also refactored the forecast_csv script a bit so that I could reuse some code from there.
Note:

Uploads in CSV format
I just used the same lat/long for the site as the forecast_csv script. Not sure if we want to change this.
The repo will need HF_REPO and HF_TOKEN secrets set up.

Fixes #135
How Has This Been Tested?
I set up and ran this script using github actions in my forked repo. It has been successfully pushing data to a test dataset I set up on Hugging Face.

[x] Yes

@peterdudfield this one is ready to go.
Any suggestions for other useful issues I could pick up?

I;'ve added HF_REPO and HF_TOKEN secrets, there's a chance the workflow might not have access to them

@mduffin95 do you mind merging the most recent main branch?

I;'ve added HF_REPO and HF_TOKEN secrets, there's a chance the workflow might not have access to them

Yes it's still using my versions of these secrets on this branch

I've moved both forecast_csv and hf_upload to a new utils module within the library. In a future PR I could move the test out of forecast_csv into tests/.

Not sure what's going on with these flaky authentication exceptions.

Not sure what's going on with these flaky authentication issues:
Cannot access gated repo for url https://huggingface.co/datasets/openclimatefix/uk_pv/resolve/main/metadata.csv.
Access to dataset openclimatefix/uk_pv is restricted. You must be authenticated to access it.

I'm not sure what I can do about this on my end.

Its because its needs a HF token, which do have on our CI as a github action secret, but perhaps not on your branch, or something like that

This looks already to go, apart from, do you mind updating the lat lon to 51.59, -1.89 and capacity to 4kw

Its because its needs a HF token, which do have on our CI as a github action secret, but perhaps not on your branch, or something like that

But strangely it seems to pass the first time it runs 🤷
I've made the required changes.


🪳

Description:
A clear and concise description of what the bug is.
Task version:
Specify the task version
Platform:

[x] Ubuntu
[x] macOS
[x] Windows

Runner type:

[x] Hosted
[x] Self-hosted

Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.
Expected behavior:
A description of what you expected to happen.
Actual behavior:
A description of what is actually happening.

Hello @Checkmate43. I'm going to close the issue because it looks like spam.


go: not found

My playbook stopped at line https://github.com/cloudalchemy/demo-site/blob/master/extras.yml#L67
To solve this, I added a task
  - name: Install "golang" package
     apt:
      name: golang

before it

Your proposal will install golang on a remote machine while the problematic task is executed on localhost (https://github.com/cloudalchemy/demo-site/blob/master/extras.yml#L71).
Since package installation needs elevated privileges and this needs to be done on deployer host (localhost) I think it would be reasonable to say that golang requirement is an external dependency that should be satisfied before running the playbook.
Additionally, this is extras.yml which is not required to start a monitoring stack :)

Description for extras.yml was improved in https://github.com/cloudalchemy/demo-site/commit/7935ea06b8624aa60b18d80a813d7ab1d2ea9ced
Thanks for finding this issue.


Error during the deploy

Hello everyone!
I'm trying to deploy the AOE and I'm receiving this error. I've tried the deployment many times but it didn't work.
Any suggestion?

Thank you for reporting this issue, @fbcarvalho. Can you please share more details about the template deployment failure? You can find more details by looking at the resourcesDeployment deployment in the aoebbb-rg resource group deployments.

If everything went fine at the resource group level, check also the Subscription deployments. If the error details link doesn't help, try looking at the "Related Events" link.

Thanks Elder.
There was a policy blocking my deployment at subscription level. I was looking for deployment errors at resource group level and I couldn't identify the error.
Thank you!


Incorrect handler name in docs: "SynchronousOidRequestHandlerComplete"

Ndis.h documentation for NDIS_FILTER_DRIVER_CHARACTERISTICS structure contains this sentence:

Added the SynchronousOidRequestHandler and SynchronousOidRequestHandlerComplete members for NDIS 6.80.

But the structure above shows the name is SynchronousOidRequestCompleteHandler instead.

Thanks very much for letting us know about this issue @dmiller-nmap. The fix is up now.


Python RuntimeError when trying to scan LiDAR point cloud data

I have successfully initialized a new TileDB database and am now trying to move onto the next step: scanning. Python throws a RuntimeError when I try to use the scan function of SilviMetric. This happened with my own data, but I can reproduce the error with test data from the SilviMetric GitHub repository as well.
System: OpenSUSE Tumbleweed (Linux)
Python version: 3.11
Here is my workflow (in Bash):
# Setup Python virtual environment
mkdir ~/working
cd ~/working
python3 -m venv .venv  # Create virtual environment
source .venv/bin/activate  # Activate virtual environment

# Install SilviMetric requirements
python3 -m pip install click dask 'dask[distributed]' pyproj numpy tiledb \
     scipy dill pdal gdal==3.8.4 pandas 'dask[dataframe]'

# Install SilviMetric into virtual environment
git clone https://github.com/hobuinc/silvimetric
pip install ./silvimetric

# Initialize SilviMetric database
# TileBD expects lower left coordinate pair first, then upper right
bounds='[495579, 4780091, 695301, 4978956]'
   silvimetric --database database.tdb initialize \
     --bounds "$bounds" --crs "EPSG:6342"
fi

# Scan?
path="$HOME"/working/silvimetric/tests/data/autzen-small.copc.laz
silvimetric --database database.tdb scan "$path"

When I run that last command, I get the error:
2024-04-10 09:59:10,013 - silvimetric - INFO - extent_handle:67 - Chunking 1 tiles at depth 0
2024-04-10 09:59:10,013 - silvimetric - INFO - extent_handle:67 - Chunking 1 tiles at depth 0
2024-04-10 09:59:10,013 - silvimetric - INFO - extent_handle:67 - Chunking 1 tiles at depth 0
2024-04-10 09:59:10,013 - silvimetric - INFO - extent_handle:67 - Chunking 1 tiles at depth 0
2024-04-10 09:59:10,048 - distributed.worker - WARNING - Compute Failed
Key:       ('tile_info-bag-from-delayed-1852343071d0de96aa6fe6c175b4f3aa', 0)
Function:  execute_task
args:      ((<function reify at 0x7f7e7f262fc0>, (<function tile_info at 0x7f7e62d06840>, ([635559.00,639009.00],[848856.00,853566.00]), <silvimetric.resources.data.Data object at 0x7f7e62d22a90>, 100.0, 600000, 6)))
kwargs:    {}
Exception: 'RuntimeError("No opening \'(\'.")'

Traceback (most recent call last):
  File "/home/daniel/working/.venv/bin/silvimetric", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/click/decorators.py", line 45, in new_func
    return f(get_current_context().obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/silvimetric/cli/cli.py", line 90, in scan_cmd
    return scan.scan(app.tdb_dir, pointcloud, bounds, point_count, resolution,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/silvimetric/commands/scan.py", line 24, in scan
    cell_counts = extent_handle(extents, data, resolution, point_count,
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/silvimetric/commands/scan.py", line 68, in extent_handle
    n = curr.compute()
        ^^^^^^^^^^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/dask/base.py", line 375, in compute
    (result,) = compute(self, traverse=False, **kwargs)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/dask/base.py", line 661, in compute
    results = schedule(dsk, keys, **kwargs)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/silvimetric/commands/scan.py", line 85, in tile_info
    pc = data.estimate_count(extent.bounds)
      ^^^^^^^^^^^^^^^^^
  File "/home/daniel/working/.venv/lib64/python3.11/site-packages/silvimetric/resources/data.py", line 153, in estimate_count
    qi = pipeline.quickinfo[reader.type]
  ^^^^^^^^^^^^^^^^^
RuntimeError: No opening '('.

Hey @danielrode thanks for posting! I'm taking a look at this, but currently unable to replicate from the main branch of silvimetric and copying your environment process.
Would you mind providing environment versions with
pip list
which pdal
pdal --version

Thank you!

pip list:
Package            Version
------------------ -----------
certifi            2024.2.2
click              8.1.7
cloudpickle        3.0.0
dask               2024.4.1
dask-expr          1.0.11
dill               0.3.8
distributed        2024.4.1
fsspec             2024.3.1
GDAL               3.8.4
importlib_metadata 7.1.0
Jinja2             3.1.3
locket             1.0.0
MarkupSafe         2.1.5
msgpack            1.0.8
numpy              1.26.4
packaging          24.0
pandas             2.2.1
partd              1.4.1
pdal               3.3.0
pip                24.0
psutil             5.9.8
pyarrow            15.0.2
pyproj             3.6.1
python-dateutil    2.9.0.post0
pytz               2024.1
PyYAML             6.0.1
scipy              1.13.0
setuptools         65.5.0
silvimetric        1.0.0
six                1.16.0
sortedcontainers   2.4.0
tblib              3.0.0
tiledb             0.27.1
toolz              0.12.1
tornado            6.4
tzdata             2024.1
urllib3            2.2.1
zict               3.0.0
zipp               3.18.1

which pdal --> /usr/bin/pdal
pdal --version --> pdal 2.5.6 (git-version: Release)

Update: I get the same No opening '(' RuntimeError when running shatter as well:
silvimetric --log-level DEBUG --database autzen-smdb.tdb shatter https://s3.amazonaws.com/hobu-lidar/autzen-classified.copc.laz --date 2001-01-01:
2024-04-10 16:43:34,167 - silvimetric - INFO - chunk:71 - Filtering 1 tiles at depth 0
2024-04-10 16:43:34,167 - silvimetric - INFO - chunk:71 - Filtering 1 tiles at depth 0
2024-04-10 16:43:34,167 - silvimetric - INFO - chunk:71 - Filtering 1 tiles at depth 0
2024-04-10 16:43:34,167 - silvimetric - INFO - chunk:71 - Filtering 1 tiles at depth 0
2024-04-10 16:43:34,167 - silvimetric - INFO - chunk:71 - Filtering 1 tiles at depth 0
2024-04-10 16:43:34,167 - silvimetric - INFO - chunk:71 - Filtering 1 tiles at depth 0
2024-04-10 16:43:34,167 - silvimetric - INFO - chunk:71 - Filtering 1 tiles at depth 0
2024-04-10 16:43:34,203 - distributed.worker - WARNING - Compute Failed
Key:       ('filter-bag-from-delayed-f8b79650d1280add110b061dd0bb38fa', 0)
Function:  execute_task
args:      ((<function reify at 0x7f7c2fe35440>, (<function Extents.filter at 0x7f7c13917600>, ([635549.20,639029.20],[848856.21,853566.21]), <silvimetric.resources.data.Data object at 0x7f7c13937050>, 100, 600000, 6)))
kwargs:    {}
Exception: 'RuntimeError("No opening \'(\'.")'

Traceback (most recent call last):
  File "/home/daniel/bh/.venv/bin/silvimetric", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/click/decorators.py", line 45, in new_func
    return f(get_current_context().obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/silvimetric/cli/cli.py", line 161, in shatter_cmd
    shatter.shatter(config)
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/silvimetric/commands/shatter.py", line 179, in shatter
    leaves = extents.chunk(data, 100)
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/silvimetric/resources/extents.py", line 72, in chunk
    n = curr.compute()
        ^^^^^^^^^^^^^^
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/dask/base.py", line 375, in compute
    (result,) = compute(self, traverse=False, **kwargs)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/dask/base.py", line 661, in compute
    results = schedule(dsk, keys, **kwargs)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/silvimetric/resources/extents.py", line 106, in filter
    pc = data.estimate_count(self.bounds)
  ^^^^^^^^^^^^^^^^^
  File "/home/daniel/bh/.venv/lib64/python3.11/site-packages/silvimetric/resources/data.py", line 153, in estimate_count
    qi = pipeline.quickinfo[reader.type]
  ^^^^^^^^^^^^^^^^^
RuntimeError: No opening '('.

The error you're seeing is a PDAL error message referring to the bounds created, and I don't think this exists in the latest version of PDAL.
I can't replicate your error, and I'm fairly certain it's because of the mixing of environments. The latest version of python-pdal that you have installed should be using pdal version 2.7.1 or newer, but this error is coming from the pdal installed in your /usr/bin.
Relevant issue in pdal python: https://github.com/PDAL/python/issues/164
If you have conda available to you, the easiest solution would be to use that to manage your environment with conda env create -f environment.yml && conda activate silvimetric from the base directory of the project. If you're stuck with source installs and pip, then I would update the pdal you have installed in /usr/bin and see if that fixes it.

I tried the Conda approach shown in the SilviMetric QuickStart doc. However, that resulted in a libglog.so.2: cannot open shared object file error on my machine. I may open a separate issue about that later.
I got things working using just the native OpenSUSE package manager and venv/pip. Looks like older versions of PDAL expect the ([minx, maxx], [miny, maxy]) bounds format, but SilviMetric uses [minx, miny, maxx, maxy] format internally when passing the bounds object to PDAL. I patched that so the code now works with my older version of PDAL (which is currently the latest version of PDAL available in OpenSUSE repos). Here's the modification I made: https://github.com/hobuinc/silvimetric/commit/1b6e973648a5187308d2515c503c452c1b10b96f
If you are interested in adding this to the main repo, let me know and I can make a PR. Otherwise, feel free to close this issue.
Specifying a minimum expected PDAL version number in the guide/docs is an alternative solution, but I don't know when PDAL switched from expecting that specific bounds format to the several currently supported in the latest version.


Use genproto.Options to parse command

This PR updates the plugin to use flags and the standard genproto.Options,
instead of the paramsMap which made it hard to see what functionality was
supported.
Please review the following commits I made in branch dan/options:
9439cb6641581e646a480a184112bf61aea4c5b0 (2024-04-25 16:39:29 -0700)
Use genproto.Options to parse command
Code review reminders, by giving a LGTM you attest that:

Commits are adequately tested
Code is easy to understand and conforms to style guides
Incomplete code is marked with TODOs
Code is suitably instrumented with logging and metrics

Closing because genproto is intended only for go code, so introduces some weird side effects.


Fix issues with Godot 4 tutorial

OK, so when I moved the docs, this got closed.  I do need to go and fix this in the tutorial though!


Implement on successful fridge creation, fridge item creation ->show indication for success and then exit fridge creation page

Quality of life improvement to prevent users from spamming multiple fridge creations

done!


Typo in source_id registration EMAC-2-53-AerChem

    "EMAC-2-53-AerChem":{

....
"atmosphere":"ECHAM5.3.02 (modified; spectral T42; 128 x 64 longitude/latitude; 47 levels; top level 0.01 hPa)",
...
},
We had a typo in "atmosphere".
Please correct the number of vertical levels and the top level height.
Thank you!
Phoebe

@PhoebeGraf no problem, we can update that. We also require some additional information from you which wasn't captured originally. The updated entry looks like, the missing fields that require updating are marked by the ### TEXT ### entries below:
        "EMAC-2-53-AerChem":{
            "activity_participation":[
                "" ### See activity list at https://github.com/WCRP-CMIP/CMIP6_CVs/blob/master/CMIP6_activity_id.json ###
            ],
            "aerosol":"gmxe 2.2.x",
            "atmosphere":"ECHAM5.3.02 (modified; spectral T42; 128 x 64 longitude/latitude; 47 levels; top level 0.01 hPa)",
            "atmospheric_chemistry":"MECCA 3.8.x",
            "cohort":[
                "Registered"
            ],
            "institution_id":[
                "MESSy-Consortium"
            ],
            "label":"EMAC-2-53-AerChem",
            "label_extended":"EMAC-2-53-x-AerChem",
            "land_ice":"None",
            "land_surface":"same as Atmosphere",
            "nominal_resolution_atmos":"", ### See Appendix 2 in https://goo.gl/v1drZl ###
            "nominal_resolution_landIce":"", ### See Appendix 2 in https://goo.gl/v1drZl ###
            "nominal_resolution_ocean":"", ### See Appendix 2 in https://goo.gl/v1drZl ###
            "ocean":"MPIOM 1.3.0-beta (bipolar GR1.5; approximately 1.5deg latitude/longitude; 40 levels; top grid cell 0-12 m)",
            "ocean_biogeochemistry":"None",
            "release_year":"2017",
            "sea_ice":"thermodynamic (Semtner zero-layer) dynamic (Hibler 79) sea ice model",
            "source_id":"EMAC-2-53-AerChem"
},

@PhoebeGraf I wonder if you've had a chance to look at this?

@durack1 Sorry for the delay, we will provide the missing info in the next days!

@PhoebeGraf any chance we could sort these additional details out this week?

@durack1 finally, here are the missing details:
"EMAC-2-53-AerChem":{
           "activity_participation":[
                "AerChemMIP", "CMIP"
            ],
            "aerosol":"gmxe 2.2.x",
            "nominal_resolution_aerosol":"500 km",
            "atmosphere":"ECHAM5.3.02 (modified; spectral T42; 128 x 64 longitude/latitude; 47 levels; top level 0.01 hPa)",
            "nominal_resolution_atmos":"500 km",
            "atmospheric_chemistry":"MECCA 3.8.x",
            "nominal_resolution_atmosChem":"500 km",
            "cohort":[
                "Registered"
            ],
            "institution_id":[
                "MESSy-Consortium"
            ],
            "label":"EMAC-2-53-AerChem",
            "label_extended":"EMAC-2-53-x-AerChem",
            "land_ice":"None",
            "nominal_resolution_landIce":"None",
            "land_surface":"same as Atmosphere",
            "nominal_resolution_land":"500 km",
            "ocean":"MPIOM 1.3.0-beta (bipolar GR1.5; approximately 1.5deg latitude/longitude; 40 levels; top grid cell 0-12 m)",
            "nominal_resolution_ocean":"250 km",
            "ocean_biogeochemistry":"None",
            "nominal_resolution_ocnBgchem":"None"
            "sea_ice":"thermodynamic (Semtner zero-layer) dynamic (Hibler 79) sea ice model",
            "nominal_resolution_seaIce":"250 km",
            "release_year":"2017",
            "source_id":"EMAC-2-53-AerChem"
},

@PhoebeGraf this is great.. Once last query, we are attempting to grab the grid info (# longitude and latitude values) for each realm.. Could you provide this for the ocean realm if possible (I have guessed below):
"ocean":"MPIOM 1.3.0-beta (bipolar GR1.5, approximately 1.5deg; ###240 x 120 longitude/latitude; 40 levels; top grid cell 0-12 m)"

I assume the seaIce grid is the same as the ocean grid so I could potentially copy this information across if required too

Please check the updated longitude and latitude values:
"ocean":"MPIOM 1.3.0-beta (bipolar GR1.5, approximately 1.5deg; 256 x 220 longitude/latitude; 40 levels; top grid cell 0-12 m)"
You are right, the seaIce grid is the same as the ocean grid!

@PhoebeGraf thanks for this, peek at CMIP6_source_id.html and let me know if any further tweaks are required


Enhance KubeArchiveConfig to support filtering.

Resolves https://github.com/kubearchive/kubearchive/issues/222.

Shouldn't this PR include an update to the KubeArchiveConfig documentation?

Only if you think documentation should be kept up-to-date.
Yeah, I'll add it.


update rpc vendor and add relevant adapters

relevant discussion: https://github.com/keybase/go-framed-msgpack-rpc/pull/134

Ugh please hold off review. I'm realizing this disables the connection.go logging altogether for CORE. Will go with the Info->Debug shift approach. I'm gonna remove people from review and tag again when it's ready.

OK ready again!

If you don't like this solution, why not set a flag in the rpc class to switch between Debug and Info depending on what you want?

@maxtaco Hmm but how is that different from a typed wrapper? With the stuff in this PR, if one doesn't need to shift Info to Debug, they just don't use that wrapper. It's the same thing as a flag.

@songgao it doesn't matter to me, I was reply to @jzila, sorry I didn't make that clear...

If the whole reason all these patches are being created is because you can't turn on debug mode on the KBFS servers, why not just remove all the spammy KBFS server output? Or, how about just moving that down to "profile" level so if you still want it in dev you can. Or just add a dev mode to KBFS servers that only runs the spammy debug output in dev.
In other words, it seems like this problem can be totally solved in the kbfs-server repo, and shouldn't have to bubble all the way down to the client.

We have multiple flags and env variables in client for rpc debug logging. I mentioned this in a different PR already but could do something similar here.

On Feb 3, 2018, at 8:14 AM, Mike Maxim<EMAIL_ADDRESS>wrote:
If the whole reason all these patches are being created is because you can't turn on debug mode on the KBFS servers, why not just remove all the spammy KBFS server output? Or, how about just moving that down to "profile" level so if you still want it in dev you can. Or just add a dev mode to KBFS servers that only runs the spammy debug output in dev.
In other words, it seems like this problem can be totally solved in the kbfs-server repo, and shouldn't have to bubble all the way down to the client.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub, or mute the thread.

why not just remove all the spammy KBFS server output

We were going with that approach and had a PR (https://github.com/keybase/go-framed-msgpack-rpc/pull/134) to change all INFO in rpc/connection.go back to DEBUG, where @maxtaco suggested this hack. That said, this approach (Max-hack) also has the added benefit that we'll get rpc/connection.go in mobile KBFS for free since mobile KBFS logs at INFO. The mobile KBFS one isn't really in a rush but it'll be helpful in unlikely situation where we need to debug a {md,b}server connectivity problem when KBFS mobile is released.

Or, how about just moving that down to "profile" level so if you still want it in dev you can.

The lowest log level in logrus is Debug, so to get logs in kibana we can't use Profile.

Or just add a dev mode to KBFS servers that only runs the spammy debug output in dev.

You mean selectively guard some of Debug logging calls under a configurable log but always log other DEBUG messages? That sounds a bit confusing and more hacky to me since we are essentially introducing another layer of log level. Let me know if you meant something different.

We have multiple flags and env variables in client for rpc debug logging. I mentioned this in a different PR already but could do something similar here.

If I understand correctly, this solves the problem with rpc/connection.go logging on KBFS mobile, but not server-side where the logrus logging path is used. I guess if we end up not being able to merge this PR, the flags/env-var approach is the solution for KBFS mobile.

How about change all the RPC library stuff to Debug, and then put the "switching" logger in kbfs-server to switch up Debug to Info in the logger you pass into the RPC library. That way we don't need to get the client involved.

As for KBFS mobile, if the KBFS client could have a version of VDebug like the service does that would be useful. The service has essentially two different debug modes depending on if we are running on mobile or desktop.

How about change all the RPC library stuff to Debug, and then put the "switching" logger in kbfs-server to switch up Debug to Info in the logger you pass into the RPC library.

This is exactly the first approach I went with. But @jzila brought up a good point that the rpc library should be portable: https://github.com/keybase/go-framed-msgpack-rpc/pull/132#pullrequestreview-91724964 and I think those logs should really be Info instead of Debug. And we can’t log as Info just because client leaks Info to CLI, essentially making Debug the only level usable by logs. So honestly I think having the switch in client makes more sense.

That way we don't need to get the client involved.

So instead of “pushing” the switch to client, we are now “pushing” it to kbfs-server. This is essentially the same thing if looking from the entire team’s perspective.

I would think making all the logs Debug inside the RPC library is actually more portable, not that I agree that really matters here.

I’m not going to debate this anymore, but I’ll just end it by saying that I think it is a weird play to put this very confusing code here to solve a problem in a completely different repo. If there is another option available I think we should pursue that.

Let’s have a five minute meeting on Monday
Patrick / song / mike / John / me
On Sat, Feb 3, 2018 at 6:07 PM Mike Maxim<EMAIL_ADDRESS>wrote:

I’m not going to debate this anymore, but I’ll just end it by saying that
I think it is a weird play to put this very confusing code here to solve a
problem in a completely different repo. If there is another option
available I think we should pursue that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/pull/10420#issuecomment-362863483, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA05_3uP4jaS3RRL84qCCL-g_cp2H9Tdks5tRObNgaJpZM4R36kF
.

Sorry if I made the discussion frustrating, @mmaxim .
@maxtaco I think that will be very helpful. Thanks!


Add object relationships

We should add a Relationship field whose role is to reference another resource.
However, how to deal with references to other namespaces ? We could support:

ClusterResource → ClusterResource
NamespacedResource(ns n) → NamespacedResource(ns n)
NamespacedResource(ns n) → Cluster resource

We need to deal with Relationship Resource CRUD operations.
I have two ideas.

association based on ownerReferences of Kubernetes.
association based on structured annotations

If we adopt the first, Kubernetes will help us deal with garbage collection. but cross-namespace owner references are disallowed.

Maybe we could have both ?
Indeed, ownerReferences are useful, but sometimes soft dependencies (that don't imply parent-child, unlike ownerRef) are also useful. I'm imagining something like:
@pykorm.k8s_custom_object
class Server(pykorm.NamespacedModel):
  pass

@pykorm.k8s_custom_object
class User(pykorm.NamespacedModel):
  # Many-to-one or one-to-one
  server = pykorm.fields.Relationship(field=pykorm.fields.Spec('server'), relationship=Server, lookup_field='name')

In this case, behind the scenes, the user CRD would have their .spec.server field equal to the name of the corresponding CRD in the same namespace.
This is easy when having references in the same namespace (for a Namespaced resource) or for the whole cluster (cluster resource). However we could, at first, disallow inter-namespace references for the sake of clarity.
What do you think ?

Hey @Frankkkkk, i'm currently looking into using pykorm as i've been writing way to much boilerplate for my liking with pykube.
this feature would be something i'd be using a lot. My use-case is as following:

my Kubernetes operator listens for CRD creations
on creation it'll generate child resources like pods, pvcs, svc etc.
later on specific changes of the CRD it would be usefull to easily request all children of the original CRD

as of now i'm just requesting the k8s api & then filtering in my code but it would be nice to use the relationships estabilished in ownerReferences.
i'd like to help with this feature  if you can give me some guidance on how to contribute

Maybe we should decide whether we want lazy loading or not. I'd think that its not a bad idea to load on the fly so we have less "circular" checking to do.
With lazy loading, we could handle the relationship loading on the model's  __getattr__. It shouldn't be really hard as we'd have the class, so we can do some querying and return the found (or not) object
On https://github.com/Frankkkkk/pykorm/issues/2#issuecomment-715301548 I thought that sqlalchemy-like relationships sounded neat, but if you've got another idea I'm all for it !
Maybe we could start with many-to-one (or one-to-one as it's the same from the "father" object) relationships ?
Would you like to do a POC MR @Roni1993  and then we can improve on it ?
Cheers

I think lazy loading sounds like a good idea.
As in my use case I'm often requesting the CRDs but require the ownerReference relationships only in a few cases.
I think i can try to create a MR for these relationships.
Regarding the custom relationships I'm thinking that it might be a good idea to build on a similar approach like the labels are used with service selectors
Labels allow more efficient requests as the k8s API already provides special filters & it would also align with the standard approach. What do you think about this?

Maybe we could have both ? Indeed, ownerReferences are useful, but sometimes soft dependencies (that don't imply parent-child, unlike ownerRef) are also useful. I'm imagining something like:
@pykorm.k8s_custom_object
class Server(pykorm.NamespacedModel):
  pass

@pykorm.k8s_custom_object
class User(pykorm.NamespacedModel):
  # Many-to-one or one-to-one
  server = pykorm.fields.Relationship(field=pykorm.fields.Spec('server'), relationship=Server, lookup_field='name')

In this case, behind the scenes, the user CRD would have their .spec.server field equal to the name of the corresponding CRD in the same namespace.
This is easy when having references in the same namespace (for a Namespaced resource) or for the whole cluster (cluster resource). However we could, at first, disallow inter-namespace references for the sake of clarity.
What do you think ?

I know it's been a while but this soft dependency pattern has a lot of benefits though I appreciate it doesn't solve all the issues.


String links animate as white

Not pale green.

By the way, even with animation off, the color is still white.


add props to lifecycle sort group

When using Flow, you’ll often include types for your props like so:
class MyComponent extends Component {
  props: {
    a: number,
    b: number,
  }

  state: {
    c: number,
    d: number,
  } = {
    c: 1,
    d: 2,
  }

  ...
}

In such a case you will also want the props type definition on top of the component. This PR adds the props to the sort-comp lifecycle rule so that by default the props property will be sorted to the top. Adding a props property is generally not desirable in any other case but this one.

Why would this be an unidiomatic way of typing props? Other than the fact that props are meant to be read-only you are typing an object that does exist.

@thejameskyle in React, prior to Flow, props were typed with propTypes. I do accept that typing it this way makes more sense since it's directly using the property name, but at the moment, having types at all is unidiomatic, let alone when there's no associated value (ie, no default prop). Is that allowed in Flow? (specifying the default value along with the type)

propTypes is something separate because it lives in value-space and needs to be a separate property name to make sense in JavaScript. Flow is able to merge values from both props and defaultProps fine and is totally idiomatic in terms of how classes work.
Class property types in Flow with values look like this:
class Foo {
  bar: boolean = true;
}

Thanks for the Flow explanations (I don't use it yet). I'm convinced that support for this belongs in the plugin - i'm just not convinced it belongs in the default ordering. I'm content to be overruled by another collab, however.

Seems like you need the ability to differentiate values from types. It seems like it's currently treating both as one in the same which, as you pointed out, is not the case.
class Component { props: {...} } // ok
class Component { props = {...} } // bad

What if we added another rule where assignment of props was treated as an error? That way, practically, this sort would only affect types.

I think this can be closed now that there is a type-annotations group.
"react/sort-comp": [1, {
  order: [
    'type-annotations',
    'static-methods',
    'lifecycle',
    'everything-else',
    'render',
  ],
}]

Closing per https://github.com/yannickcr/eslint-plugin-react/pull/923#issuecomment-312373840


skip .swp files for vim users

skip .swp files for vim users

Codecov Report

Merging #4052 into master will decrease coverage by 0.09%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #4052     +/-   ##
===========================================
- Coverage     66.72%   66.63%   -0.1%
  Complexity       20       20
===========================================
  Files          1033     1033
  Lines         51388    51388
  Branches       7196     7196
===========================================
- Hits          34291    34240     -51
- Misses        14734    14789     +55
+ Partials       2363     2359      -4

Impacted Files
Coverage Δ
Complexity Δ

...r/validation/RealtimeSegmentValidationManager.java
43.33% <0%> (-38.34%)
0% <0%> (ø)

...startree/executor/StarTreeAggregationExecutor.java
72.72% <0%> (-27.28%)
0% <0%> (ø)

...apache/pinot/common/metrics/ValidationMetrics.java
20.28% <0%> (-23.19%)
0% <0%> (ø)

...aggregation/function/CountAggregationFunction.java
70.73% <0%> (-14.64%)
0% <0%> (ø)

...y/aggregation/function/AvgAggregationFunction.java
69.87% <0%> (-10.85%)
0% <0%> (ø)

...e/operator/dociditerators/SortedDocIdIterator.java
55.55% <0%> (-8.34%)
0% <0%> (ø)

...a/org/apache/pinot/common/config/TagNameUtils.java
64.1% <0%> (-5.13%)
0% <0%> (ø)

...org/apache/pinot/common/metrics/MetricsHelper.java
72.5% <0%> (-2.5%)
0% <0%> (ø)

...ller/validation/OfflineSegmentIntervalChecker.java
26.74% <0%> (-2.33%)
0% <0%> (ø)

.../core/realtime/PinotLLCRealtimeSegmentManager.java
66.61% <0%> (-1.65%)
0% <0%> (ø)

... and 20 more

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 c7450ab...5c07dd1. Read the comment docs.

Thanks @snleee @jackjlli !
I am very interested in Pinot. Hope to contribute more to the community. Are there any features or bugs I can start with?

@katewang0710 Thank you for the contribution! You can start to pick some items from issues (https://github.com/apache/incubator-pinot/issues). For quick communication, please join to slack if you need some help from the community.
https://join.slack.com/t/apache-pinot/shared_invite/enQtNDY4NDczOTYyNjk1LTExODVjY2QxYzBkMzJjNTk0ZGQ3NThiYTU2YzdlNjE0MWI5ZjUwYjI2ZTgxNjNiYWJiNmEzYjkxMTIzMzUxNTQ


Uswds 3 upgrade

This is upgrade to USWDS 3 with a gulp build. toolchain. I've also removed old folders and merged assets so thaaht files are largely in one place.
I strongly recommend merging this into a new dev branch and not master as it likely needs some more polishing, setting of color tokens, etc.

Amazing, thank you @kasigi. I see a few layout bugs introduced in these changes but I'm going to go ahead and approve (and fix the conflicts) and then merge. We can fix the layout bugs in future PRs.
Really appreciate this effort. It's huge (literally -- I couldn't review the PR except in codespaces. the page just crashes even on a beefy 2023 MBP). Nice to see the bits of cleanup here and there -- reorganizing and removing dead code. Kudos 👏


Drop CircleCi in favor for github actions

The test badge is broken on the README file

drop support for ruby 1.8.7.
reflect the license in the gemspec file

could allow the merge of https://github.com/madrobby/zaru/pull/9 facilitating testing

@hellvinz Thank you! Do you want to take a stab at #9?


Proxmox status not working

Question
Hi,
I have an issue with the status of proxmox. I am a new user, maybe i did something wrong... Tried different settings, but can't get it working. Also couldn't  find the error.

Category
Status Checking
Please tick the boxes

[X] You are using a supported version of Dashy (check the first two digits of the version number)
[X] You've checked that this question hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

Settings are incorrect.
Set Status Check URL to https://<IP_ADDRESS>:8006
-Dashy doesn't ping the device. It contacts the HTTP/S server and waits for a response.
Set Status Check Disable SSL to False
-Proxmox uses TLS by default. Settings this option to True will break the status check of this service.

Hi,
Thanks for your support!
It should:

but after save, Status Check Disable SSL is removed.

Are you saying that the status check is still not functioning after the changes? You probably don't even need the Status Check URL, since the service URL and status check URL are the same.

No still not working.
Also did a test without Status Check Url
After saving the settings, the Status Check Disable SSL is removed. So i doesn't save the settings.

I have it working for me, here are my settings.  Hope this helps.

Heya @marktn - Could you share the contents of your browser console (here's how), as there should be some info explaining why it's not working there.
The relevant parts of your YAML might also be helpful. And just to confirm, if you visit that page directly (https://<IP_ADDRESS>:8006) does it return a 200?
I also recommend that if you haven't already, you take a look at Troubleshooting → Status Checks not Working, as there are some more ideas there. But my guess is that it's a CORS error.
Also, have you seen #181 as it looks to be the same/ similar issue.

Found it! After using Firefox the save function works!


Mastodon specs want both links in the same Link header

https://docs.joinmastodon.org/api/guidelines/#pagination

I didn't check before, sorry. Isn't the original code better then as one Link per line is clearer?

I didn't check before, sorry. Isn't the original code better then as one Link per line is clearer?
Actually, I did but this is probably not the right code (or I'm unable to decipher.)

I think its fine the way it is.


Parabolic Mortar for AMR P4estMesh{3}

Do you have the time to carve out the 3D additions compared to main?
The current version contains many things that where disregarded in the process of merging the 2D parabolic P4est AMR.
If not this is also fine, I would then need to start altering this PR.


[react-native] Automatic sourcemap upload as part of Gradle release build fails on Windows

Describe the bug
After setting up automatic sourcemap upload with Gradle, ./gradlew bundleRelease fails with the error
java.io.IOException: Cannot run program "C:\Projects\CareServices\BugsnagRepro\node_modules\@bugsnag\source-maps\bin\cli": CreateProcess error=193, %1 is not a valid Win32 application

Steps to reproduce

npx react-native init BugsnagRepro --skip-install
yarn set version berry
Edit .yarnrc.yml to add nodeLinker: node-modules.
Run yarn to install packages.
Follow the Bugsnag manual setup guide for React Native on Android. At this point, ./gradlew bundleRelease will succeed.
yarn dlx @bugsnag/react-native-cli automate-symbolication

PS> yarn dlx @bugsnag/react-native-cli automate-symbolication
i Detecting repo state                                                                                09:41:16

 WARN  This command may make modifications to your project. Afterwards you can                                09:41:16
review the diff and commit them to your project.

√ Do you want to continue anyway? ... yes
√ Are you using Bugsnag on-premise? ... no
√ Do you want to automatically upload JavaScript source maps as part of the Xcode build? ... yes
i Modifying the Xcode project                                                                                09:41:27
i Ensuring React Native build phase outputs source maps                                                       09:41:27
i Adding build phase to upload source maps to Bugsnag                                                         09:41:27
√ Written changes to Xcode project                                                                            09:41:27
√ To configure your project to upload dSYMs, follow the iOS symbolication guide:

    https://docs.bugsnag.com/platforms/ios/symbolication-guide/

  This will enable you to see full native stacktraces. It can't be done automatically.

 ... Hit enter to continue …
√ Do you want to automatically upload JavaScript source maps as part of the Gradle build? ... yes
» Enabling Bugsnag Android Gradle plugin React Native mappings                                                09:41:33
√ React Native mappings enabled in android/app/build.gradle                                                   09:41:33
i Adding @bugsnag/source-maps dependency                                                                      09:41:33
√ If you want the latest version of @bugsnag/source-maps hit enter, otherwise type the version you want ... latest

 ERROR  spawn yarn ENOENT                                                                                09:41:37

  at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
  at onErrorNT (internal/child_process.js:467:16)
  at processTicksAndRejections (internal/process/task_queues.js:82:21)

(See issue #1511 for the "spawn yarn ENOENT" problem.)

Since adding @bugsnag/source-maps failed, install it manually with yarn add --dev @bugsnag/source-maps.
Run ./gradlew bundleRelease again. Error occurs (see full Gradle output below).

Environment

Bugsnag version: "@bugsnag/react-native": "^7.11.0"
Browser framework version (if any): "react-native": "0.64.2"
Server framework version (if any): N/A
Browser version (e.g. chrome, safari): N/A
Device (e.g. iphonex): N/A
OS: Windows 10

Example Repo
https://github.com/srmagura/BugsnagRepro, no-source-maps branch: Gradle release build will succeed.
https://github.com/srmagura/BugsnagRepro, source-maps branch: Gradle release build will fail with the following output:
Error messages:
PS> .\gradlew bundleRelease

> Task :app:bugsnagReleaseReleaseTask
Bugsnag: Uploading to Releases API

> Task :app:uploadBugsnagReleaseSourceMaps FAILED
Bugsnag: uploading react native sourcemap: [C:\Projects\CareServices\BugsnagRepro\node_modules\@bugsnag\source-maps\bin\cli, upload-react-native, --api-key, ***REDACTED***, --app-version, 1.0, --app-version-code, 1, --platform, android, --source-map, C:\Projects\CareServices\BugsnagRepro\android\app\build\generated\sourcemaps\react\release\index.android.bundle.map, --bundle, C:\Projects\CareServices\BugsnagRepro\android\app\build\generated\assets\react\release\index.android.bundle, --project-root, C:\Projects\CareServices\BugsnagRepro]

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:uploadBugsnagReleaseSourceMaps'.
> java.io.IOException: Cannot run program "C:\Projects\CareServices\BugsnagRepro\node_modules\@bugsnag\source-maps\bin\cli": CreateProcess error=193, %1 is not a valid Win32 application

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.7/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 10s
59 actionable tasks: 12 executed, 47 up-to-date

The contents of @bugsnag/source-maps/bin/cli are:
#!/usr/bin/env node

require('../dist/bin/cli.js').default(process.argv)

Looks like the first line needs to be tweaked to work on Windows!

Hi @srmagura, thanks for the report. We'll look into this along with #1511 as soon as priorities allow.

Hi @srmagura, as per https://github.com/bugsnag/bugsnag-js/issues/1511#issuecomment-904118746; the @bugsnag/source-maps CLI tool only support macOS & Linux which is why Windows will throw an error that the binary node_modules\@bugsnag\source-maps\bin\cli is not executable.
Therefore, in order to upload source maps from a Windows machine, you will need to invoke curl (or Invoke-WebRequest if curl is not available for any reason) directly from PowerShell. You can find details on how to interact with the React Native source map upload API here: https://docs.bugsnag.com/api/rn-source-map-upload/. Or alternatively, you can interact with the @bugsnag/source-maps JavaScript API: https://docs.bugsnag.com/build-integrations/js/source-maps-react-native/#usage.
To stop Bugsnag from trying to upload source maps through Gradle, you can remove the uploadReactNativeMappings option from you app/build.gradle.


keychain file should auto create

The keychain file is not automatically created.  As a result, the first command in the readme fails with an error.
❯ prelude iam create-account
Enter an email<EMAIL_ADDRESS>Please create a /Users/octavia/.prelude/keychain.ini file

Let's additionally auto-add the registration details into your new/existing keychain.


[SPARK-18103][Follow-up][SQL] Rename MetadataLogFileCatalog to MetadataLogFileIndex

What changes were proposed in this pull request?
This is a follow-up to https://github.com/apache/spark/pull/15634.
How was this patch tested?
N/A

@rxin @ericl please take a look thanks!

Test build #67884 has started for PR 15712 at commit d5680b3.

Test build #67884 has finished for PR 15712 at commit d5680b3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67884/
Test PASSed.

Thanks - merging in master.


flutter create --template plugin has failing tests

Steps to reproduce:
flutter create --template plugin myplugin
cd myplugin
flutter test

Fails with:
00:06 +0 -1: getPlatformVersion [E]
  ServicesBinding.defaultBinaryMessenger was accessed before the binding was initialized.
  If you're running an application and need to access the binary messenger before `runApp()` has been called (for example, during plugin initialization), then you need to explicitly call the `WidgetsFlutterBinding.ensureInitialized()` first.
  If you're running a test, you can call the `TestWidgetsFlutterBinding.ensureInitialized()` as the first line in your test's `main()` method to initialize the binding.
  package:flutter/src/services/binary_messenger.dart 73:7    defaultBinaryMessenger.<fn>
  package:flutter/src/services/binary_messenger.dart 86:4    defaultBinaryMessenger
  package:flutter/src/services/platform_channel.dart 140:62  MethodChannel.binaryMessenger
  package:flutter/src/services/platform_channel.dart 393:5   MethodChannel.setMockMethodCallHandler
  my_plugin_test.dart 9:13                                   main.<fn>

  ServicesBinding.defaultBinaryMessenger was accessed before the binding was initialized.
  If you're running an application and need to access the binary messenger before `runApp()` has been called (for example, during plugin initialization), then you need to explicitly call the `WidgetsFlutterBinding.ensureInitialized()` first.
  If you're running a test, you can call the `TestWidgetsFlutterBinding.ensureInitialized()` as the first line in your test's `main()` method to initialize the binding.
  package:flutter/src/services/binary_messenger.dart 73:7    defaultBinaryMessenger.<fn>
  package:flutter/src/services/binary_messenger.dart 86:4    defaultBinaryMessenger
  package:flutter/src/services/platform_channel.dart 140:62  MethodChannel.binaryMessenger
  package:flutter/src/services/platform_channel.dart 393:5   MethodChannel.setMockMethodCallHandler
  my_plugin_test.dart 15:13                                  main.<fn>

00:06 +0 -1: Some tests failed.

We should fix this failure, and also we should add a test to the Flutter CI to prevent this type of failure from occurring in the future.

@adazh this was introduced in https://github.com/flutter/flutter/pull/38464

Ya... the error message is caused by the PR. Anything you need my help?

Can you review #39080?
#38464 also broke all the tests in the flutter/plugins repo, if you'd like to submit a PR for that I can land it for you.


[TEST][TPCDS] Introduce schema check for queries-4

Why are the changes needed?

Introduce schema check for queries(forty plus)
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

Codecov Report

Merging #594 (c3590db) into master (1820864) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #594   +/-   ##
=======================================
  Coverage   79.86%   79.86%
=======================================
  Files         118      118
  Lines        4545     4545
  Branches      549      549
=======================================
  Hits         3630     3630
  Misses        608      608
  Partials      307      307

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 1820864...c3590db. Read the comment docs.

thanks meging to master for v1.2.0


UNR-4843: Added actor ownership component to better handle player ownership

Description
Modified simulated/client ownership subviews to take ownership completeness into account.
This resulted in additional component to store ownership information (ActorOwnership), a new query tag, and a new FOwnershipCompletenessHandler class.
Release note
Should there be a bugfix patch note? This is an internal implementation change, which fixes potential issues with ownership.
Tests
Existing tests + added a couple new low-level tests.
Documentation
No docs

The commits are rewritten for ease of reading.

Does the new included schema file affect snapshots?


Use custom shell to tidy up AutoMerge

The multiline string of the run key will be saved to a file. The filename will be inserted in place of the {0}.
ref. https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#custom-shell
(needs to be tested, but I don't know how)
@DilumAluthge

I'll merge this once we've reverted #18991


Added NGC Lamp5

Fixes #864

Updated the description to try to make it more congruous with the one in the google sheets


Fixed linux_x86_icc compiler errors in EC code related to _uint128 &  __int128_t

Performing the following operation

icc -m32 -dM -E -o main.P main.c

Showed that  __SIZEOF_INT128__ == 16  (32 bit build on a 64 bit machine).
So another define also needs to be used. I chose __SIZEOF_POINTER__ initially but then changed it to match the code in poly1305.c

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Is this tied to some specific compiler version?

ICC linux x86 build.
Code in poly1305.c does the same thing..

You're referring to poly1305.c, but there's a difference.  In poly1305.c, it's
# if (defined(__SIZEOF_INT128__) && __SIZEOF_INT128__==16) && \
     (defined(__SIZEOF_LONG__) && __SIZEOF_LONG__==8)

While you do this:
#  if (defined(__SIZEOF_INT128__) && (__SIZEOF_INT128__ == 16)) \
      && (!defined(__SIZEOF_LONG__) || (__SIZEOF_LONG__ == 8))

Would you mind telling us why?

So my logic was:
If for some strange reason SIZEOF_LONG is undefined then work how it worked before.
otherwise if it is defined check its the right size. I think that is better than the && logic maybe?
Either way I dont care as long as it builds.

This is really messy having this code in multiple places - especially when it looks different in one place when it also checks for android and clang..
Maybe a header that does this in one place that defines yet another define would be a better approach?

 e_os.h?
Not e_os2.h since it is public.

@levitte  any thoughts?

__SIZEOF_<type>__ might be compiler specific, how about simply excluding the ICC compiler,
there must be something that is only defined by them?

it works in 64bit, just not 32 bit..
And we are doing a similar check in other .c files.

If this is compiler bound, @bernd-edlinger has the right idea that compiler specific macros should be used.  On the other hand, it's quite possible that future versions (*) of ICC might correct the confusion they seem to cause, so it may turn out that we exclude them unnecessarily.
Either way, when it comes to predefined macros, this is a treasure to look into

(*) Side note: when I ask for the compiler version I do mean the version and not what flavor it is.  So in when I asked about the version higher up, I wanted to know the ICC version number, not that it was ICC.

As for a generic place, we don't really have that for this sort of thing.  e_os.h is a hodge podge of different hacks, and could possibly work, but to make it readable?  We should really have something like internal feature macros, such as HAVE_INT128 for this case...  Not sure that this PR is a place to start such things, though...

Compiler version ICC_14.0

But what is exactly wrong?
The code in poly1305 actually uses typedef unsigned long u64;
so it is clear that it depends on 64-bit long integers,
but nothing here uses long, what is used is only uint64_t

The problem is that compiling with icc on a 64 bit machine in 32 bit mode (i.e icc -m32) actually defines SIZEOF_INT128 == 16 (see below) and then complains that the _uint_128_t  is undefined if you try to use it.
Checking for SIZEOF_LONG == 8 sounded like a reasonable way of doing this since 32 bit modes probably should not be trying to use _uint_128_t .
It could also check __ICC, __INTEL_COMPILER, __INTEL_COMPILER_UPDATE  but that also seems ugly. Note that BN code has bypassed this problem by using configuration options.
 That config attribute is used for more than just BN, you have probably notice things like RC4_CHAR and RC4_INT. This is a construct that hasn't been expanded for a loooong time (because we rely more on predefined compiler macros in more modern times, I suppose), but that could be a way to handle things too...

ping

Is this for master only, or does it also apply to 1.1.1?

@paulidale I only need it for master, but it could be applied to 1.1.1 also?

(I am not @paulidale :wink:)  If it's applicable, I think we should.

Yes to 1.1.1 as well.

Merged to master and 1.1.1.  Thanks all.


#ZgotmplZ as link in serve http

What is your rclone version (eg output from rclone -V)

rclone v1.39
- os/arch: linux/amd64
- go version: go1.9.2

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Ubuntu 16.04

Which cloud storage system are you using? (eg Google Drive)

Google Drive encrypted

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone serve http remote:
In one of my directories must be some bad character and I get this as links:
example/
I have quite a few folder names in there with non-ascii characters, but I'm unsure which causes the issue. Seems to be related to https://stackoverflow.com/questions/14765395/why-am-i-seeing-zgotmplz-in-my-go-html-template-output
Looks like it happens if the folder contains a ":".

This is easy to replicate by trying to serve a file with a : in it as you suggested.
I'll fix shortly then post a beta for you to try.


how to consume?

How to consume products? Can you give me a sample code?
This is mine but it seems doesnt work..
Users cant buy an item again..
InAppBilling.open()
            .then(() => InAppBilling.purchase(productID))
            .then((details) => {
                //console.log("You purchased: ", details)
                this.checkPayment(details, (res) => {
                    if (res) {
                        return InAppBilling.consumePurchase(productID)
                    }
                    else
                        return false
                })
            })
            .then((consumed) => {
                if (consumed) {
                    ....
                }
                return InAppBilling.close()
            })

Is the product you're trying to consume setup as a consumable product for your app on the Google Play Dev page?

Yes it is.

I'd recommend running adb logcat in terminal as you debug on device (you cannot test on emulator), or look through the logs in Android Studio, to see if you get an exception.
Also, have you debugged the JS so you are sure that the consumePurchase function is actually executed?

Stale issue, closing. Re-open if it is still a problem.