React 0.14

Is Griddle going to be updated for React 0.14?  I noticed a commit that locks the React peer dependency to v0.13.3.

+1

+1

+1

+1

#232

same here #232

I'm keeping my app at 0.13 (and using old releases of all the other React components) because Griddle is irreplaceable. It would be such a relief to be able to upgrade.

1, griddle is a big part of my app right now (I've got very good comment about it, so keep the good work!). It's the only thing keeping me from upgrading.

+1
npm install griddle-react => "react": "^0.13.3",
bower install griddle-react => "react": "~0.12.0",
please update both to 0.14 - and keep bower up-to-date!

I have another package which locks React at 0.14+. Please do it and enable latest React.

@ryanlanciaux Don't mean to pester, but I'm just not quite sure what the overall plan is in regards to Griddle and the newer separate components (griddle-core, etc).  Can you shed some light on exactly what is going to happen with the Griddle project and a timeline?
Is the main Griddle component going to go away and be replaced by griddle-core and other modules or is the modular action only going to happen behind the scenes?  Based on your answer to that question, does that have a bearing on the React 0.14 compatibility for the current Griddle component?  In other words, is griddle-core the future and therefore this repo now obsolete?  I would really like to get some clarification on these things so we don't keep beating a (potentially) dead horse.

Totally understand your concern and its not pestering me at all. We're trying to get this PR going from @sajinshrestha
In regards to the griddle-core / render / etc. The plan is that will eventually become 1.0 -- there will be some breaking changes but there will be an upgrade path. We're hoping to have an official release in the spring with an alpha coming in the next couple weeks to give people time to try it out and see what the new structure allows (biggest part is plugins / extensibility which I will be documenting a bit more later).
To clarify, though, this repository is not dead. Sorry about the delay with this -- I really would have liked to have this on 0.14 sooner -- I've been traveling a bit and been generally pretty swamped. Really thankful that others in the community have been working on getting this up-to-date. I am trying to make some headway on it tonight and will go from there. :+1: If you have anyone else has any thoughts around that PR it would be much appreciated.

If anyone wants to give https://github.com/GriddleGriddle/Griddle/pull/268 a look that would be fantastic. Basically pull down the branch and grunt serve and see if you notice any weirdness. I'm going to do the same tonight but if nothing else, it should be merged to master today. @sajinshrestha did awesome, awesome work here :+1: :fireworks:

@ryanlanciaux I'll test #268 in the next day and see if we can wrap the 0.14 upgrade up soon.

@sajinshrestha @ryanlanciaux my only concern is it running against the various versions of node 0.10 - 5.  I'll see if I can get a travis run against all of them.

That would be excellent. Thanks!

@ryanlanciaux we will need to downgrade jest-cli to 0.4.10 to support node 0.10. https://github.com/GriddleGriddle/Griddle/pull/268#discussion_r45384647

https://github.com/GriddleGriddle/Griddle/pull/268#event-470427284 is now merged into master (the 0.14 support PR from @sajinshrestha) -- We are holding off on npm publish while it is being tested on more node versions. If anyone else wants to try on various node versions and report back here version and result, that would be much appreciated.

Thanks for all the work on this.  I haven't had much time to test things out myself by I greatly appreciate those who are putting in the effort.

This has been tested locally on a handful of node versions and released to npm (0.2.15). Closing this one for now but please be sure to post any issues you run into. :+1:

Currently I have Error: Invariant Violation: Objects are not valid as a React child (found: object with keys {}). If you meant to render a collection of children, use an array instead or wrap the object using createFragment(object) from the React add-ons. Check the render method of GridRow. using React 0.14.1

@Firfi I think you need to use the, as yet undocumented, 'key' property of the rowMetadata setting. Give it the name of a column in your grid data that can be used as a unique key. If you don't have such a column yet you'll need to create one but exclude it from the column names property so it's not shown.

Hey @jgwconsulting, thanks for the tip. I use rowMetadata={{key: 'id'}} in my  component properties now, where 'id' is a columnName of a column with unique values.
It seems issue persists.
However, it definitely not React version differences as I found as I included it with React 0.14.1 as an external so there's no different React versions, only one 0.14.1.

Hmm, have you triple checked that you've got the very latest Griddle?
That's the only thing I can think of I'm afraid :/
On 28 Nov 2015 10:32, "Igor Loskutov"<EMAIL_ADDRESS>wrote:

Hey @jgwconsulting https://github.com/jgwconsulting, thanks for the
tip. I use rowMetadata={{key: 'id'}} in my component properties now,
where 'id' is a columnName of a column with unique values.
It seems issue persists.
However, it definitely not React version differences as I found as I
included it with React 0.14.1 as an external so there's no different React
versions, only one 0.14.1.
—
Reply to this email directly or view it on GitHub
https://github.com/GriddleGriddle/Griddle/issues/262#issuecomment-160271859
.

Yep, I even built it from master branch.


Remove scientific notation from logarithmic graphs

quickchart.io (and chart.js) both use scientific notation for log graphs by default. Perhaps it's a good idea to replace that with a normal notation to make the data more understandable.

Hello, @AntoniosBarotsis! I would like to take this issue for the hacktoberfest event.


Obtaining visual features for the ConceptualCaptions data set

Hi,
I'd like to take a look at the pretraining but I was wondering if there was a way to have access to the train_frcnn.zip files without having to run the caffe model, are they available somewhere?
Best,

Sorry about that. The files are too big to upload to online disks like Google Drive. You need to run the caffe code to extract the visual features.

+1 - I need this as well, and having problems with the caffe model.


HDHomeRun Scan Erroneous Channels

Whether scanning OTA (ATSC) or Cable (QAM) it seems to want to include some apparently erroneous channels that are just numbered. They show up in the web interface as "-", "- 2", "- 3", etc. Unsure how these are being produced. Trying to preview one shows a signal strength but no video. the associated mpgbuf for the tuner shows a zero size. This compared to a valid channel that shows a preview video and the associated mpgbuf file size is greater than zero.

Upon further testing I have discovered that the erroneous channels are actually misdetected channels. If I run further scans the erroneous channels get deselected and are replaced by their properly detected channels.

http://forums.sagetv.com/forums/showthread.php?t=62569 - I have the same or a similar issue. As well to filter out the audio / radio channels. Currently I would focus on the HDHomeRun2.0 library as I suspect something is not correctly handled.

Still the two issues of having the "- xx" channels and the Radio channels. See screenshots:

Another change was just checked in earlier today which should fix this
issue...did you check out the code today and build/test from that?
On Thu, Jan 14, 2016 at 1:37 PM, Yafra<EMAIL_ADDRESS>wrote:

Still the two issues of having the "- xx" channels and the Radio channels.
See screenshots:
[image: sagetv1]
https://cloud.githubusercontent.com/assets/2341192/12338308/450c6efc-bb0f-11e5-93ff-29017cba1595.jpg
[image: sagetv2]
https://cloud.githubusercontent.com/assets/2341192/12338310/46fb59e4-bb0f-11e5-9463-4a1ee3509aaf.jpg
—
Reply to this email directly or view it on GitHub
https://github.com/google/sagetv/issues/15#issuecomment-171787819.

--
Jeffrey Kardatzke
<EMAIL_ADDRESS>Google, Inc.

I just did a pull and my version is build 208. It should be the latest. Screenshot was done on build 208.

Are you sure those channels are just being listed from the prior scan?  It
won't remove them when it does the new scan...and your screenshot doesn't
show what it says about the "-" channels since you don't have one of them
highlighted in it.  And the radio channels are supposed to show up IIRC.
On Thu, Jan 14, 2016 at 1:41 PM, Yafra<EMAIL_ADDRESS>wrote:

I just did a pull and my version is build 208. It should be the latest.
Screenshot was done on build 208.
—
Reply to this email directly or view it on GitHub
https://github.com/google/sagetv/issues/15#issuecomment-171790014.

--
Jeffrey Kardatzke
<EMAIL_ADDRESS>Google, Inc.

I just updated my test server. I removed the epg entries in properties to clean things out. Re-added the source and did a scan. The erroneous channels were not there before starting the scan. Once the scan was finished they showed up in the scan results.

After looking at that fix again...It was apparently for a different
issue...sorry.  So this one's still on the table to get fixed by whoever's
interested. :)
On Thu, Jan 14, 2016 at 2:10 PM, Jason Bean<EMAIL_ADDRESS>wrote:

I just updated my test server. I removed the epg entries in properties to
clean things out. Re-added the source and did a scan. The erroneous
channels were not there before starting the scan. Once the scan was
finished they showed up in the scan results.
—
Reply to this email directly or view it on GitHub
https://github.com/google/sagetv/issues/15#issuecomment-171797831.

--
Jeffrey Kardatzke
<EMAIL_ADDRESS>Google, Inc.

My pull request https://github.com/google/sagetv/pull/62 isn't likely to affect network tuners.


CMake Error: install(EXPORT "ITKTargets" ...) includes target "gdcmjpeg8" more than once in the export set.

Description
RTK CI now fails with this error in the Build ITK step, see https://github.com/SimonRit/RTK/runs/1524238640. I noticed #2146 but the problem is on Ubuntu, not on mac OS. Since RTK uses the new github actions, I assume that the same problem will occur with the CI of all remote modules which use the ITKModuleTemplate.
Steps to Reproduce
See https://github.com/SimonRit/RTK/blob/master/.github/workflows/build-test-package.yml#L52-L56.
Expected behavior
ITK configuration and compilation!
Actual behavior
Error in the title when configuring ITK.
Reproducibility
100%
Versions
ITK v5.1.2

There is already the issue on Sourceforge 515. Probably the owner will look at it soon.
It is related to code like (not only here, many places)
if(NOT JPEG_INSTALL_NO_LIBRARIES)
  install(TARGETS ${JPEG_LIBRARY_NAME}8
    EXPORT ${GDCM_TARGETS_NAME} <---------------------------------
    RUNTIME DESTINATION ${JPEG_INSTALL_BIN_DIR} COMPONENT Applications
    LIBRARY DESTINATION ${JPEG_INSTALL_LIB_DIR} COMPONENT Libraries ${NAMELINK_SKIP}
    ARCHIVE DESTINATION ${JPEG_INSTALL_LIB_DIR} COMPONENT DebugDevel
  )
  if(NAMELINK_ONLY)
  install(TARGETS ${JPEG_LIBRARY_NAME}8
    EXPORT ${GDCM_TARGETS_NAME} <-----------------------------------
    LIBRARY DESTINATION ${JPEG_INSTALL_LIB_DIR} COMPONENT DebugDevel ${NAMELINK_ONLY}
  )
  endif()
endif()

In top level GDCM CMakeLists.txt file is block
if(BUILD_SHARED_LIBS)
  set(NAMELINK_ONLY NAMELINK_ONLY)
  set(NAMELINK_SKIP NAMELINK_SKIP)
endif()

where it is possible e.g. to comment NAMELINK_ONLY and Cmake will generate files, for example, not tested, just FYI.

Seems to work again as is with nightly build CMake 3.19.2

Thanks. The .github action of remote packages does not install cmake, it uses the version delivered with the ubuntu-18.04 os. Should this be changed?
I admit I don't understand this problem because it appeared suddenly without changing the os nor the ITK version...

Sorry, they actually update the os env, see the problem here.

This is related to a regression in CMake 3.19.1, xref https://gitlab.kitware.com/cmake/cmake/-/issues/21529
Yes, we should start using an explicit CMake version in the remote module GitHub Actions. I can start a patch.
CC @bradking @malaterre

PR: https://github.com/InsightSoftwareConsortium/ITKModuleTemplate/pull/98

This worked for me, thanks, see here, (but I now have another problem with MacOS python packages).

This worked for me, thanks, see here,

:+1:

(but I now have another problem with MacOS python packages).

I am working on this -- a different issue, but also related to updates on the build system.

@SimonRit both issues should now be addressed following updates in ITKModuleTemplate master -- if not, please re-open.

Yes, thanks, I confirm that it solved it.


[HOTFIX] Fix permission issue when creating job folders in HDFS

Coverage increased (+0.03%) to 49.664% when pulling 7c5d4f103b14a3e065e54a5da009f89e1cbaf57c on hwuu/pai-0.4.y_hotfix_rest-server into e9ec8749e9c7ab2f232a7fe6ec7ce912d0d1b445 on pai-0.4.y.

please merge this PR to master as well


Question:Support for Nested Routing in Pinecone Router

Is your feature request related to a problem? Please describe.
I'm currently developing an application using Alpine.js and Pinecone Router. My project requires nested routing to manage  UI structures, but I can't find support for nested routes in Pinecone Router.
Describe the solution you'd like
I would like Pinecone Router to support nested routing, allowing for more structured and hierarchical URL paths. This feature should enable defining child routes within parent routes directly.
Describe alternatives you've considered
As an alternative, I've considered manually handling route dependencies.
Additional context
Nested routing is crucial for applications that have multiple layers of components and need to maintain clean and organized URL structures. This feature would greatly enhance the usability of Pinecone Router for more complex applications.

Hey thanks for the suggestion!
To answer, no it doesn't support nested routing currently. I didn't plan this feature though I see how it is crucial in certain situations. I'm not sure how would I implement this in code, I'll try to think it over but I can't guarentee I will ship as I am busy with some other stuff. O
You said you considered manually handling dependencies, I guess that is tedious and not very organized. does using multiple reusable handlers help?  as in adding a profileHandler to all routes under the /profile path, including whichever handler they need?
Sorry for the inconvenience, hope you figure it out in the meanwhile. You might also want to look at alternatives, currently I only know of only one other Alpine.js router which is this: https://github.com/shaunlee/alpinejs-router, one difference is that it have RegEx route matching, which maybe would help you?

Hey thanks for the suggestion! To answer, no it doesn't support nested routing currently. I didn't plan this feature though I see how it is crucial in certain situations. I'm not sure how would I implement this in code, I'll try to think it over but I can't guarentee I will ship as I am busy with some other stuff. O
You said you considered manually handling dependencies, I guess that is tedious and not very organized. does using multiple reusable handlers help? as in adding a profileHandler to all routes under the /profile path, including whichever handler they need?
Sorry for the inconvenience, hope you figure it out in the meanwhile. You might also want to look at alternatives, currently I only know of only one other Alpine.js router which is this: https://github.com/shaunlee/alpinejs-router, one difference is that it have RegEx route matching, which maybe would help you?

Thanks for the prompt reply, Pinecone is a very good routing library.
Currently I'm using x-handle ,unified processing in
document.getElementById(templateTargetId)

is null according to certain rules to request the corresponding template, then
document.getElementById(currentTargetId). innerHTML

prepopulates the template.
I'm mostly a backend developer so I don't have a lot of good suggestions, maybe support nested definitions when defining routes?
I'll continue to use Pinecone, he's working great, thanks again for your contribution!
Translated with DeepL.com (free version)

I been quite been and only got back to checking on the code.
Since
youd have to do
<x-route="profile"


weapons dont work

character just holds the magazine but gun isnt there? and i never interacted with the weapon when pressing play

You may have to propify the weapon and then record with it.

I have a solution. There's a non-code mod that you can find in the releases, under the "assets" folder. It contains a spawnable object called "Propifier." You can find this in the "pallets" tab of the spawn gun, or under "MonoDirector"
So simply aim and shoot at whatever object you want your actor to interact with using the "Propifier" tool (there should be a new icon above the object for the actor to interact with), then record the action. Enjoy!


How to get the API ID and the env from a AppSync Resolver Mapping Template?

I'm currently writing a BatchGetItem resolver and for that I need to have the table name into the Mapping Template.
Table names are generated from the API ID, the GraphQL Model name and the environment.
My question is how to get these values inside a Mapping Template?

Doc about $ctx values
Doc about BatchGetItem

Table name into CloudFormation template:
"TableName": {
    "Fn::If": [
        "HasEnvironmentParameter",
        {
            "Fn::Join": [
                "-",
                [
                    "Comment",
                    {
                        "Ref": "GetAttGraphQLAPIApiId"
                    },
                    {
                        "Ref": "env"
                    }
                ]
            ]
        },
        {
            "Fn::Join": [
                "-",
                [
                    "Comment",
                    {
                        "Ref": "GetAttGraphQLAPIApiId"
                    }
                ]
            ]
        }
    ]
},

Unfortunately there isn't an easy way to get the API ID in the template. If you're using custom stack, then you could get the API ID by doing inline resolver template and substituting the value
You would have to use RequestMappingTemplate Property of AppSync Resolver and then use Fn::Sub and substitute the API ID

The issue with the solution you propose is that the CLI detach mapping templates to write them into the build directory. Then it creates the URL and fill the RequestMappingTemplateUrl field.
Is there a way to set some environment or context variables that would be accessible into the template?
This is a bit weird that we don't have access to these information into mapping templates.

I am going to mark this as enhancement and add it our backlog.

Is there a way to set some environment or context variables that would be accessible into the template?
This is a bit weird that we don't have access to these information into mapping templates.

The AppSync service does not expose this, so there isn't much we can do about making it available in the context


Fix a bug where making a connection to a remote server using CLI

Codecov Report

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

@@            Coverage Diff             @@
##           master     #118      +/-   ##
==========================================
- Coverage   61.44%   61.43%   -0.02%
==========================================
  Files         257      257
  Lines        8723     8723
  Branches     1002     1002
==========================================
- Hits         5360     5359       -1
- Misses       2758     2759       +1
  Partials      605      605

Impacted Files
Coverage Δ

.../linecorp/centraldogma/client/AbstractWatcher.java
55.46% <0%> (-0.85%)
:arrow_down:

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 718f63a...7bf017f. Read the comment docs.


Setting FlyoutPlacementMode to Auto crash

Describe the bug
    <muxc:SplitButton>
        <TextBlock Text="SplitButton"/>
        <muxc:SplitButton.Flyout>
            <MenuFlyout Placement="Auto">
                <MenuFlyoutItem Text="A"/>
                <MenuFlyoutItem Text="B"/>
                <MenuFlyoutItem Text="C"/>
            </MenuFlyout>
        </muxc:SplitButton.Flyout>
    </muxc:SplitButton>

Steps to reproduce the bug

Add a SplitButton as the code
Click the split button, app crash

Expected behavior
No response
Screenshots

NuGet package version
Microsoft.UI.Xaml 2.7.1
Windows app type

[X] UWP
[ ] Win32

Device form factor
No response
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

This issue still exists in WinUI 2.8.5. WinUI3 seems fine.

@ranjeshj Reason for closing a crashing bug?

The WinUI team is currently spending its time on WinUI 3. To help with this focus, new bugs filed against WinUI 2 are closed in this repo unless they're a security issue or are business critical.

This is not new, is it?


Checkout Error

The script runs fine, but when it buys GTA, it prompts me an error telling me I need to wait 24 hours. I have a VPN running so I don't know what can be the cause.
Edit: Nevermind, I fixed it

How did you fix it cause I have the same problem?


Support test 'watch' / auto-rerun mode

Builds in retired test states (#115086). When a test result is retired, under watch mode, we should queue a request to rerun the test.

Implemented in the linked commit.
I took a slightly different approach from @hbenl's test explorer in that I only issue a rerun for tests that were previously run before. If the user ran all tests, then those can all be auto-run, but I think this might be better when working on large projects (like vscode) where tests take a while to run and you generally are only interested in the a subset of tests at any time.

For verification using the selfhost test provider

In a fresh window in the VS Code repo, turn on the auto-run ⚡ (better icon incoming soon) in the actions on the test explorer view
Edit a test, it should not auto-run.
Run the test or all test in the file (there's a Test: Run Tests in Current File command). That should now run
Edit the test again. Now that it's been run once, it should auto-run after a short (1000ms) delay when the file is saved.


Crash when choosing 'Close all other panes'

Windows Terminal version
1.22.2362.0
Windows build number
10.0.27699.0
Other Software
No response
Steps to reproduce

Open Windows Terminal.
Split panes so there are at least two panes.
Ctrl+Shift+P and choose ‘Close all other panes’

Expected Behavior
No crash.
Actual Behavior
Terminal crashes with an access violation:
(3c78.4aa0): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
TerminalApp!winrt::impl::consume_TerminalApp_IPaneContent<winrt::TerminalApp::IPaneContent>::TaskbarProgress+0x34 [inlined in TerminalApp!Pane::CollectTaskbarStates+0x82]:
00007ffb`45483032 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????

Here is the call stack:
TerminalApp!winrt::impl::consume_TerminalApp_IPaneContent<winrt::TerminalApp::IPaneContent>::TaskbarProgress
TerminalApp!Pane::CollectTaskbarStates
TerminalApp!Pane::CollectTaskbarStates
TerminalApp!winrt::TerminalApp::implementation::TerminalTab::GetCombinedTaskbarState
TerminalApp!winrt::TerminalApp::implementation::TerminalPage::TaskbarState
TerminalApp!winrt::TerminalApp::implementation::TerminalWindow::TaskbarState
TerminalApp!winrt::impl::produce<winrt::TerminalApp::implementation::TerminalWindow,winrt::TerminalApp::ITerminalWindow>::get_TaskbarState
WindowsTerminal
WindowsTerminal
TerminalApp!winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable>::operator()
TerminalApp!wil::details::dispatcher_handler::operator()
TerminalApp!winrt::impl::delegate<winrt::Windows::UI::Core::DispatchedHandler,wil::details::dispatcher_handler>::Invoke
Windows_UI!Microsoft::WRL::Details::DelegateArgTraits<long (__cdecl Windows::System::IDispatcherQueueHandler::*)(void)>::DelegateInvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::System::IDispatcherQueueHandler,Microsoft::WRL::FtmBase>,<lambda_980f345bc6e4ac8a906323c24a5fe9b1>,-1>::Invoke
CoreMessaging!Windows::System::DispatcherQueue::DeferInvokeCallback
CoreMessaging!CFlat::SehSafe::Execute<<lambda_654db17c35df07198786f0867aa10de6> >
CoreMessaging!Microsoft::CoreUI::ActionCallback::ImportAdapter$
CoreMessaging!Microsoft::CoreUI::Dispatch::DeferredCall::Callback_Dispatch
CoreMessaging!Microsoft::CoreUI::Dispatch::DeferredCallDispatcher::Callback_OnDispatch
CoreMessaging!Microsoft::CoreUI::Dispatch::Dispatcher::Callback_DispatchLoop
CoreMessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop
user32!_fnDWORD
ntdll!KiUserCallbackDispatcherContinue
win32u!NtUserGetMessage
user32!GetMessageW
WindowsTerminal
WindowsTerminal
WindowsTerminal
ucrtbase!thread_start<unsigned int (__cdecl*)(void *),1>
KERNEL32!BaseThreadInitThunk
ntdll!RtlUserThreadStart

I suspect this is the same underlying bug as #17869. If I try and reproduce that one in the debugger I get a very similar stack trace to this crash.

This must've regressed in #17750. Since we never wrote down what made it originally crash, I guessed it happened by simply closing panes, but this shows it was via the "Close all other panes" action. Not 100% sure how to best fix it. There were two simple options and neither worked. The correct approach would be to not tie the model (binary tree of panes) to the animations but fixing that is not an option for a hotfix.


Added Three Linux commands

Please read the README.md file once again @abhishekgupta23

@lachenlama changes made, Please Merge.

I have made the changes, Please Merge


Changing Session.Client to be interface type instead of concrete *http.Client can help with writing unit tests

Changing Session.Client to be an interface type instead of a concrete *http.Client can help with writing unit tests for projects that depend upon discordgo, while not breaking existing users by still allowing *http.Client.
An example repository I've been working on to help ease unit testing with discordgo can be found here: https://github.com/ewohltman/discordgo-mock
(FYI, the repo is still pretty new and no doubt missing API paths for the time being).
In particular, this function below allows us to create a  discordgo.RESTClient-satisfying object that will use discordgo.State to process API requests (found in https://github.com/ewohltman/discordgo-mock/blob/main/pkg/mockrest/mockrest.go):
type roundTripperFunc func(req *http.Request) (*http.Response, error)

func (rt roundTripperFunc) RoundTrip(req *http.Request) (*http.Response, error) {
	return rt(req)
}

type Client struct {
	*http.Client
	state  *discordgo.State
	router *mux.Router
}

func NewClient(state *discordgo.State) *Client {
	router := mux.NewRouter()

	client := &Client{
		Client: &http.Client{
			Transport: roundTripperFunc(func(r *http.Request) (*http.Response, error) {
				responseRecorder := httptest.NewRecorder()
				router.ServeHTTP(responseRecorder, r)
				return responseRecorder.Result(), nil
			}),
		},
		state:  state,
		router: router,
	}

	apiVersion := "/api/v" + discordgo.APIVersion

	client.addHandlersGuilds(apiVersion)
	client.addHandlersChannels(apiVersion)
	client.addHandlersUsers(apiVersion)

	return client
}

Example usage of the RESTClient with Session.Client change (found in https://github.com/ewohltman/discordgo-mock/blob/main/pkg/mocksession/mocksession_test.go):
func newSession(expectedResources *resources) *discordgo.Session {
	state, err := mockstate.New(
		mockstate.WithUser(mockuser.New(
			mockuser.WithID("Bot"),
			mockuser.WithUsername("Bot"),
			mockuser.IsBot(true),
		)),
		mockstate.WithGuilds(expectedResources.guild),
	)
	if err != nil {
		panic(err)
	}

	session, err := mocksession.New(
		mocksession.WithState(state),
		mocksession.WithRESTClient(mockrest.NewClient(state)),
	)
	if err != nil {
		panic(err)
	}

	return session
}

Since this field is exported, changing its type in the struct would be a breaking API change.

@zacharyburkett Good point. I'll leave this here in case there is appetite to adopt this change. If not, this PR can be closed without merge :+1:

As discussed, the scope of the proposed change in this issue would result in an API-breaking change and will be closed. Alternative methods for easing unit testing will be investigated.

For future reference:
I started looking into an alternative approach by replacing the *http.Client.Transport with a custom http.RoundTripper that seems to do the job:
https://github.com/ewohltman/discordgo-mock
Example usage of this new "helper" library can be found here until I can more fully flesh out the discordgo-mock repo with better examples and unit tests:
https://github.com/ewohltman/ephemeral-roles/blob/develop/internal/pkg/mock/session.go
Comments, questions, and improvements are welcome to discordgo-mock!


Naming Bikeshed: Response::into_{json,xml}_body

https://github.com/Azure/azure-sdk-for-rust/pull/1954 introduces two new methods on Response:

Response::<T>::into_json_body<U: DeserializeOwned>(self) -> crate::Result<U>
Response::<T>::into_xml_body<U: DeserializeOwned>(self) -> crate::Result<U>

The purpose of these methods is to consume the Response, stream the entire body, and deserialize it to the provided model type U, using either JSON or XML serde deserialization.
The method name isn't ideal, into properly implies consuming the Response to produce a new type, but the {json,xml}_body implies that it's "returning" JSON or XML somehow, when actually it's using JSON/XML deserialization to produce a model type.
However, we also have methods into_raw_body and into_body for returning a raw ResponseBody and a T: Model, which make more sense. Both are consuming the Response to produce a (potentially "raw") representation of the body. The into_{json,xml}_body methods align with the convention established by those methods.
We decided to move forward without resolving this naming conflict, so this issue exists to have a place to revisit it prior to a GA release, after which name changes would be much more costly.
Some potential ideas for discussion:

into_body_from_{json,xml} is more accurate, but verbose
body_from_{json,xml} loses the into_ prefix, which has meaning in Rust
parse_{json,xml} is more accurate, relatively terse, but does still lose the into_ prefix
into_{json,xml}_model may be clearer, since it indicates the model is defined by JSON or XML rather than implying it returns the "body". We could similarly rename into_body to into_model 🤔

cc @heaths

Hmm, hadn't considered parse_ but I think that almost works; however, std parse functions all borrow so we do lose the intent of the into_ ownership transfer. What about parse_{json,xml}_into()? Then again, that almost seems to imply into_body() should instead be into()...but is that so bad, I wonder now? I mean, a model could, technically, pull from headers to you're consuming more than just the body. into_raw() works as well.
The 4th bullet are good ideas as well, but I'm currently leaning toward brevity above e.g.,

into(self) -> Model...or even parse_into(self)?
into_raw(self) -> ResponseBody
parse_json_into<T>(self) -> Model (from JSON)
parse_xml_into<T>(self) -> Model (from XML)

Though, writing that out, prefaces are all over the place. Maybe your fourth bullet is better. @JeffreyRichter @RickWinter what are your thoughts?

Does Rust not use "from" as in "from_json" or "from_xml"?
If not, then "parse_json_into" seems fine to me.


get_html() Returns JSON Instead of HTML

A customer reported the get_html() method for this library returns a JSON response instead of the expected HTML.
I may be misunderstanding something about what the get_html method is intended to do, but I checked this locally and the customer's report appears to be correct:

Resolved in https://github.com/serpapi/google-search-results-python/pull/69. (Thanks @gutoarraes!)


Bump milli to v0.41.1

Pull Request
Related issue
Fixes #3438.
What does this PR do?

Bump milli to v0.41.1 that includes a bugfix for #3438

bors merge


[Feature][API] Support to complement data in descending or ascending order of date.

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Currently the DolphinScheduler doesn't support to complement data in descending or ascending order of date. If I'd like to complement data for 365 days I have to wait for all 365 parallel workflows to be done. That's really inconvenient.  So I expect that the system can support to complement data in descending or ascending order of date.

Use case
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

good job
Using screenshot in English environment will be better!


Error showing Restore Database File Browser dialog

Azure Data Studio Version: 1.26.0

Steps to Reproduce:

Connect to Server and open Restore Dialog
Switch to restore backup file and click browse for file "..." button

Expected: Remote Browser works without error
Actual: An error message pops up the first time.  Then the dialog doesn't render correct on subsequent launches.  A telemetry error shows in dev console.

 ERR Cannot read property 'providerName' of undefined: TypeError: Cannot read property 'providerName' of undefined
    at e.addTelemetryForConnectionDisconnected (file:///C:/Users/kburt/AppData/Local/Programs/Azure Data Studio/resources/app/out/vs/workbench/workbench.desktop.main.js:5561:443)
    at file:///C:/Users/kburt/AppData/Local/Programs/Azure Data Studio/resources/app/out/vs/workbench/workbench.desktop.main.js:5564:716
    at ZoneDelegate.invoke (C:\Users\kburt\AppData\Local\Programs\Azure Data Studio\resources\app\node_modules.asar\zone.js\dist\zone.js:388:26)
    at Zone.run (C:\Users\kburt\AppData\Local\Programs\Azure Data Studio\resources\app\node_modules.asar\zone.js\dist\zone.js:138:43)
    at C:\Users\kburt\AppData\Local\Programs\Azure Data Studio\resources\app\node_modules.asar\zone.js\dist\zone.js:872:34
    at ZoneDelegate.invokeTask (C:\Users\kburt\AppData\Local\Programs\Azure Data Studio\resources\app\node_modules.asar\zone.js\dist\zone.js:421:31)
    at Zone.runTask (C:\Users\kburt\AppData\Local\Programs\Azure Data Studio\resources\app\node_modules.asar\zone.js\dist\zone.js:188:47)
    at drainMicroTaskQueue (C:\Users\kburt\AppData\Local\Programs\Azure Data Studio\resources\app\node_modules.asar\zone.js\dist\zone.js:595:35)

FWIW, the error didn't repro after restarting ADS, so it's likely the bug is in the dashboard telemetry call and that is having a side-effect (at least with the rendering issue).  The first error still may be in the restore code, and what "broke" the connection, but I didn't see any exception from that error.

Closing older issue without recent repro reports.


Add playsinline prop

Hi!
I've been utilizing your component to integrate camera functionality to a Vue3 PWA. In order to obtain a 'native app' look and feel, simple-vue-camera was perfect! Thanks for making it available to the world :)
But, there is an issue (or difference in interpretation of web standards by Safari developers) with the video tag on iOS/Safari where the video will open full screen with an installed video player, like described here:
https://stackoverflow.com/questions/71326733/prevent-video-element-from-going-full-screen-on-iphone
As the SO answer states, this behavior can be simply avoided by adding the playsinline attribute to the <video> tag.
simple-vue-camera currently has no way to add this to the component via props, so I resorted to adding it to the DOM when mounting my own component. It works, but it would be much nicer if simple-vue-camera would be able to take care of this. I've added a prop to do just that. Since we're "abusing" the video tag to function as a camera, and opening another app to play the "video" isn't desirable, I've opted to make it true by default.
While doing this, I noticed the existing autoplay prop was set to false by default, while it was stated in the README.md it is set to true by default. Not a huge issue, but a bug nonetheless, so I've opted to change the default in the component to true since it makes the most sense in this case.
Then lastly, npm install was not able to resolve all package dependencies after fresh cloning the repo. I had to use npm install --legacy-peer-deps to be able to build successfully and run the testing app. I've included the updates it made in the package.json and package-lock.json, as well as bumping the version of vue-simple-camera to 1.1.2.
Summary;

Added ability to configure playsinline on the component via a new prop
Set default of autoplay to true to reflect the README.md
Bump package version

Ok, that's it. Thanks for your consideration and hoping to hear from you :)
~Michel

Great PR!


Command failed with exit code 123: xargs docker rmi -f

Hi,
Trying to use semantic-release from a Jenkins pipeline.
I get this :
[7:49:07 AM] [semantic-release] › ✖  Failed step "fail" of plugin "@codedependant/semantic-release-docker"
[7:49:07 AM] [semantic-release] › ✖  An error occurred while running semantic-release: Error: Command failed with exit code 123: xargs docker rmi -f
"docker rmi" requires at least 1 argument.
See 'docker rmi --help'.

Usage:  docker rmi [OPTIONS] IMAGE [IMAGE...]

Remove one or more images
    at makeError (/usr/local/lib/node_modules/@codedependant/semantic-release-docker/node_modules/execa/lib/error.js:59:11)

I can understand that my image shall be removed after being build and published. But I see no where any message concerning the build nore the publication...
Any idea ?

Having the same issue running in guthub action. I'm not convinced that I even need to do any cleanup. I'm building, publishing to ECR. I don't think I need to remove them from a local docker instance since the github actions docker instance is likely temporary for the lifetime of the build anyways?

@denispeyrusaubes Is there any error before these lines?
It looks like the build of the image didn't succeed in the first place, and rmi is failing because there is no image/tag to remove.
I could make the clean a little more forgiving and not kill the build. or make the autoclean and option. or both.

@jamesrusso @denispeyrusaubes There is the dockerAutoClean option as of v4.3.0 which you can set to false to disable the bit that tries to remove the images


[Bug]: Helm chart use latest image instead of appVersion

Describe the expected outcome
Installing the Helm chart should use the image matching the appVersion.
This will allow a reproducible deployment.
Describe the actual outcome
The latest image get always used, which will lead to unexpected upgrade in case the pod gets restarted.
Steps to reproduce
helm template pca-issuer awspca/aws-privateca-issuer --version 1.2.0
Output:
...
     containers:
        - name: aws-privateca-issuer
          image: "public.ecr.aws/k1n1h4h4/cert-manager-aws-privateca-issuer:latest"
...

Note:
I'm aware of the possibility to set image.tag to "" in the values file to fallback to the Chart.AppVersion.
Relevant log output
No response
Version

= 1.0.0

Have you tried the following?

[X] Check the Troubleshooting section
[X] Search open issues

Category
Other
Severity
Severity 4

Thank you for raising this issue with the AWS Private CA Issue plugin. We are currently reviewing #126 which should solve this issue. Will post here when it has been merged in.

Thanks again for raising this issue, we've merged in https://github.com/cert-manager/aws-privateca-issuer/pull/151 which is a follow-up to sarahhodne@'s original PR #126. The next step would be to cut a new release, but if building from source, this change is now available.

release with v1.2.1


Cards do not dim when hovered

In the default Jellyfin setup, hovering the mouse over a card dims its image, allowing the overlay buttons that appear to be clearly visible no matter the color of the card image. When Jamfin is enabled, this does not occur, making the overlay buttons difficult to see on some cards.

Thanks for your suggestion, i've added back the hover state.

Thanks, this is great! Only issue I noticed is that on some cards, the rounded corners on the dimmed area seem to have a different radius to the rounded corners on the card image.

Is that with the JMP client? As I think I noticed that on there too when I was testing your other issue.

This is with the JMP client yes
On Mon, 30 Sept 2024, 22:09 Jam, @.***> wrote:

Is that with the JMP client? As I think I noticed that on there too when I
was testing your other issue.
—
Reply to this email directly, view it on GitHub
https://github.com/JamsRepos/Jamfin/issues/18#issuecomment-2384148554,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ6TIWRJKEAM6ZOTVWS5RZDZZG4XLAVCNFSM6AAAAABOUDDSHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBUGE2DQNJVGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost' is therefore not allowed access.

hi, I'am getting a problem in the api, it says "Failed to load http://phisix-api4.appspot.com/stocks/BDO.json". What ways can I do to not commit in this problem? Sorry I'am just beginning to learn to fetch an api. Thank you in advance.

Duplicate of #9


Crashed when working on AnimationTree

Godot version
4.1.stable.mono
System information
Linux Mint 21.1 Cinnamon, 4.1.stable.mono, Mobile
Issue description
During workin on animationTree, is some cases like playing animation state or updade some data, engine freezes, after a moment program iis shut down.
Steps to reproduce
Crash was happened during development 2d game with sprite anmation on mobile settings.
game engine is located in /usr/local/bin
for animation i used [animation_lib]/Array(top/down/left/right) organization
just do some top, down, left, right animation, save as idle, attack and move lib, next upload them
Minimal reproduction project
; Engine configuration file.
; It's best edited using the editor UI and not directly,
; since the parameters that go here are not all obvious.
;
; Format:
;   [section] ; section goes between []
;   param=value ; assign values to parameters
config_version=5
[application]
config/name="IAmNinja2d"
run/main_scene="res://main.tscn"
config/features=PackedStringArray("4.1", "Mobile")
config/icon="res://icon.svg"
[dotnet]
project/assembly_name="IAmNinja2d"
[input]
up={
"deadzone": 0.5,
"events": [Object(InputEventKey,"resource_local_to_scene":false,"resource_name":"","device":-1,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"pressed":false,"keycode":0,"physical_keycode":87,"key_label":0,"unicode":119,"echo":false,"script":null)
]
}
down={
"deadzone": 0.5,
"events": [Object(InputEventKey,"resource_local_to_scene":false,"resource_name":"","device":-1,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"pressed":false,"keycode":0,"physical_keycode":83,"key_label":0,"unicode":115,"echo":false,"script":null)
]
}
left={
"deadzone": 0.5,
"events": [Object(InputEventKey,"resource_local_to_scene":false,"resource_name":"","device":-1,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"pressed":false,"keycode":0,"physical_keycode":65,"key_label":0,"unicode":97,"echo":false,"script":null)
]
}
right={
"deadzone": 0.5,
"events": [Object(InputEventKey,"resource_local_to_scene":false,"resource_name":"","device":-1,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"pressed":false,"keycode":0,"physical_keycode":68,"key_label":0,"unicode":100,"echo":false,"script":null)
]
}
[rendering]
textures/canvas_textures/default_texture_filter=3
renderer/rendering_method="mobile"

The contents of the project.godot file which you pasted in this issue do not consistent a minimal reproduction project, that's just an empty Godot project with no AnimationTree.
I'm assuming this is the same bug as #79012 though, so closing as duplicate.


bucket_num bucket_start

Would you please tell me how to choose the best bucket_num and bucket_start parameters?The range of labels in my dataset is (-2, 16)

Hi, thanks for your interest. The choice of bucket_num & bucket_start will depend on the (minimum) resolution you care about for your task. For example, in age prediction, the minimum interval we care about is 1 (year), so we chose bucket_num accordingly.


Create Lightweight Tests for Important Notebooks

Notebooks are pretty prone to getting out of date and breaking (e.g. #13). We should create some lightweight tests for notebooks which have no canonical implementations in the library (currently style_transfer.py, and cppn.py).

Unlikely to ever implement this.


Add assertion to simulate shouldComponentUpdate

Something like expect(a).toUpdateOnProp('data') (prop or state) would really help

Whoa! I really like this idea. I wonder if we could work for state changes too? So maybe something a bit more abstract?


Shortcut to switch windows between zones

Hi
I searched existing issues but didn't find a similar request yet, so opening this issues as a feature request.
Use Case
I have an ultra wide monitor and typically use the Priority Grid layout (main in the middle, and two narrower frames left and right).
Sometimes I need to bring to focus i.e. move to the middle frame, one of the side frames. This helps a lot as working on a side frame on an UW monitor requires to turn your head.
It would be great to have or be able to configure a shortcut to toggle 1) left pane with center pane, and 2) right pane with center pain.
Thanks!

@metropol
this is already tracked in https://github.com/microsoft/PowerToys/issues/6611 by https://github.com/microsoft/PowerToys/issues/1342 that provides a more general approach to the problem that works for any type of layout not just a specific one.

@metropol
this is already tracked in https://github.com/microsoft/PowerToys/issues/6611 by https://github.com/microsoft/PowerToys/issues/1342 that provides a more general approach to the problem that works for any type of layout not just a specific one.


[SPARK-37388][SQL] Fix NPE in WidthBucket in WholeStageCodegenExec

What changes were proposed in this pull request?

This PR fixes a NullPointerException in WholeStageCodegenExec caused by the expression WidthBucket. The cause of this NPE is that WidthBucket calls WidthBucket.computeBucketNumber, which can return null, but the generated code cannot deal with nulls.
Why are the changes needed?

This fixes a NullPointerException in Spark SQL.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Added tests to MathExpressionsSuite. This suite already had tests for WidthBucket with interval inputs, but lacked tests with double inputs. I checked that the tests failed without the fix, and succeed with the fix.

Test build #145458 has started for PR 34670 at commit ed96fcc.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49930/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49930/

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

Test build #145458 has finished for PR 34670 at commit ed96fcc.

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

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

Thank you for the review @c21! I will add the additional test case and I have provided answers to your questions.

Test build #145466 has started for PR 34670 at commit 0cba30d.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49938/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49938/

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

Test build #145466 has finished for PR 34670 at commit 0cba30d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

retest this please

Test failure seems unrelated but mind retriggering for doubly sure, @tomvanbussel? https://github.com/tomvanbussel/spark/actions/runs/1482727001

Test build #145487 has started for PR 34670 at commit 0cba30d.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49959/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49959/

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

Test build #145487 has finished for PR 34670 at commit 0cba30d.

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

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

Seems the GA job OOMed, I'm merging this to master/3.2/3.1/3.0, thanks!


Cluster Management Cluster Node/Node Pool lists fail to show

For a successfully imported cluster the node / node pool tab fails to show in the Cluster Management Cluster detail page

Reopening. I could not reproduce this.
Reproduction Environment:

Rancher version: v2.6-a015b10b4ee838ca7961caf6ed1279e8011d1ba8-head (build from about 5 days ago, before the change was merged in); v2.6.1 also attempted
Rancher cluster type: single-node docker install
Docker version: 20.10
Downstream cluster type: imported k3s
Downstream K8s version: 1.21
Reproduction steps:

Import any cluster. In my case I created a 1-node K3s 1.21 cluster and imported this into Rancher.
Notice, the management cluster shows the machine pools tab.

Additional Info:
Is it possible I am misunderstanding the issue? No steps to reproduce were provided so I am assuming this is the right way to test this.

@davidnuzik You're doing the correct steps to reproduce, however I can't tell you when this broke. There was logic that required the imported cluster's provisioning.cattle.io.cluster provisioner value to be imported... however this now gets updated to k3s. This meant we weren't showing the nodes (labelled as machines) list.


Enhancement: Add own protocol version to RPC version action

It would be nice if the protocol version would be returned via RPC:
Request:
{
  "action": "version"
}

Response:
{
    "rpc_version": "1",
    "store_version": "11",
    "protocol_version": "14",
    "node_vendor": "RaiBlocks 16.0"
}

The variable is set here: https://github.com/nanocurrency/raiblocks/blob/c03351b8ba246c6b6a856996178c97d5e8964b9f/rai/secure/common.hpp#L28
I'm lacking C++ knowledge so I can't create a PR but with this change I could add it to the Nano Node Monitor ( https://github.com/NanoTools/nanoNodeMonitor ). The network version does not always match the node version e.g. v16.0RC2 has the protocol version 13, v16.0 release has 14. Thanks!

This work has been done as part of pull request #1194 and will be in V17.0.  I'm closing this ticket based on the future release of V17.0.
Thanks !


Test command does not seem to be doin anything

Expected Behavior
Running command yarn-script.test should open a terminal (or at least output) window with test results
Actual Behavior
Nothing happens
Steps to Reproduce the Problem
Run yarn-script.test on a project with test command properly setup in package.json (running yarn test in terminal works)
Specifications
Platform: windows 10 x64

Just additional info:
package.json:
{
    "scripts": {
        "test": "jest"
    }
}

User settings:
{
    "yarn.runInTerminal": true,
    "yarn.dontHideOutputOnSuccess": true
}

This is working, make sure you have no other opened package.json if the project is a multi-root project.


Promise will never complete when instrumenting worker

We have a pretty complex cloudflare worker that we recently added instrumentation to with otel-cf-workers. The library has worked like a dream, providing extra insight into our requests. However, when we enabled the library, we noticed an uptick in errors from Cloudflare, with the error message Promise will never complete. This seems to happen on about 0.01% of requests (with a sampling ratio of 0.01, or 1%).
Has anyone else run into this? When we disable instrumentation, the error goes away. Unfortunately cloudflare's documentation about this error is pretty scant.

Hey @jmaroeder, the cause of the error is almost always that you end up awaiting a Promise that was created in another request.
I am not aware of any of those situations in this library (which obviously doesn't mean that there aren't any.. )
Do you have any more information about what these requests have in common? Are they requests that are cancelled from the client? Are they to a particular URL? Do those URLs use a particular type of instrumentation? (especially something like cache?

It is possible that the requests are being canceled from the client - we have a large number of those.
These do not appear to be limited to a specific URL or pattern of URL.
As far as instrumentation:

Nearly all of our requests instrument one or more fetch GET
A small portion (<5%) instrument fetch POST
Approximately half our requests instrument kv GET
A miniscule portion (0.0003%) instrument cache GET and cache PUT
Our worker only responds to handler.fetch events, and also makes extensive use of ctx.waitUntil

One other thing worth noting - it may have to do with the volume of requests. We have two different deployments of our worker running identical code, but with significant differences in the number of requests handled. Both workers handle multiple domains.
One deployment sees about 1,500 requests per second under typical load, and this particular worker actually only had an error rate of less than 0.0002%.
The other deployment sees about 15,000 requests per second under typical load, and this is the one that saw error rates of 0.01%. So perhaps the issue only shows up with extremely high request volume?

Thanks! That gives me at least some direction to look into things. It is possible that there is an interaction between the flushing of the exporter and ctx.waitUntil that you can run into under extremely high load.
This week is extremely packed, but hopefully I'll have some time next week to have a proper look at things.

Right.. sorry it took so long to find the cause of this.. as you can imagine it is quite tricky. But I think I found while doing a thorough rethink of the way the Tracer/SpanProcessor and Exporter work. I will take this on as part of said rethink and fix it..

Ok.. more analysis being done. And I know exactly where it is going wrong and that will indeed be taken care of in the upcoming logic rewrite. In the meantime I guess it would be good to know that there is no impact to your users. The error happens after the both responses are returned to their clients and one trace is being sent while another trace export is still in flight.
I am pretty sure that both traces are also still exported successfully, but even if they don't, with the percentage of errors, that won't make a meaningful impact anyway. But thanks for the report. Greatly appreciate being able to fix this bug, even if it is only rarely triggered.

Thank you for looking into it further!


[INF-0002] Fill out sections on Validations.

Filled out the sections on Validations in Sema and Codegen.
Fixes #233

I think some work is still needed to make this clear and consistent.
I also suggest you have a look at how this renders in a markdown preview - some of the headers seems to be getting excessively nested which I don't think helps with making it clearly formatted.

Changed inner headers to list.


[0/9/2] Unable to drop/recreate measurement

This is related to #2955.
Below you can find a complete reproduction of my steps for 0.9.2. I'm unable to drop measurement (ERR: database not open) and after recreating I get error while executing basic SELECT clause.
InfluxDB shell 0.9.2
> CREATE DATABASE drop_test
> USE drop_test
Using database drop_test
> INSERT response_times,server=honolulu value=44.44
> SELECT * FROM response_times
name: response_times
tags: server=honolulu
time                            value
----                            -----
2015-08-04T14:45:21.546067507Z  44.44

> DROP MEASUREMENT response_times
ERR: database not open
> SELECT * FROM response_times
ERR: measurement not found: "drop_test"."default".response_times
> SHOW SERIES
> SELECT * FROM response_times
ERR: measurement not found: "drop_test"."default".response_times
> INSERT response_times,server=honolulu value=44.44
> SELECT * from response_times
ERR: found FROM, expected identifier, string, number, bool at line 1, char 9

@jacekgrzybowski I cannot reproduce this error on my setup. I'm running InfluxDB 0.9.2 installed via Homebrew on OS X 10.10.4 with an unaltered generated config file.
> create database drop_test
> use drop_test
Using database drop_test
> INSERT response_times,server=honolulu value=44.44
> SELECT * FROM response_times
name: response_times
tags: server=honolulu
time				value
----				-----
2015-08-04T18:56:41.558963517Z	44.44

> DROP MEASUREMENT response_times
> SELECT * FROM response_times
ERR: measurement not found: "drop_test"."default".response_times
> SHOW SERIES
> SELECT * FROM response_times
ERR: measurement not found: "drop_test"."default".response_times
> INSERT response_times,server=honolulu value=44.44
> SELECT * from response_times
name: response_times
tags: server=honolulu
time				value
----				-----
2015-08-04T18:57:11.097944281Z	44.44

How did you install InfluxDB? Did you make any changes to the configuration file?

@beckettsean after a fresh system startup this situation hadn't occured anymore. However, after I ran my units tests a couple of times (before each test I initialize series by inserting a non relevant value and after each one I run DROP MEASUREMENT) it happened again. So imo it happens when I initialize and drop series over and over in small time intervals (like in  #2955). Also sometimes localhost:8086 stops responding and I need to restart influxdb service. Installed on Ubuntu 14.04 LTS from .deb package downloaded from influxdb.com.

So imo it happens when I initialize and drop series over and over in small time intervals (like in #2955).

 InfluxDB wasn't designed to handle frequent deletes, it's not part of the core use case. Perhaps you can fuzz the database or measurement name in each test run so they aren't identical?

@jacekgrzybowski can you provide a script to reproduce? We can't seem to get this to happen.

I'm also getting this error on 0.9.2.
Time seems to have no effect; I'm still unable to drop measurements even after many days.
Restarting the database fixes it.
These lines will always reproduce it for me.
curl -G http://localhost:8086/query --data-urlencode "q=DROP DATABASE droptest"
curl -G http://localhost:8086/query --data-urlencode "q=CREATE DATABASE droptest"
curl -i -XPOST 'http://localhost:8086/write?db=droptest' --data-binary 'test_point,tag1=one value=1'
curl -G http://localhost:8086/query --data-urlencode "db=droptest"  --data-urlencode "q=DROP SERIES FROM test_point"

The output from the final command is:
{"results":[{"error":"database not open"}]}

reproduced in 0.9.2 and 0.9.3-rc2. The latter has a more detailed error message:
curl -G http://localhost:8086/query --data-urlencode "q=DROP DATABASE droptest"; echo
{"results":[{}]}
curl -G http://localhost:8086/query --data-urlencode "q=CREATE DATABASE droptest"; echo
{"results":[{}]}
curl -i -XPOST 'http://localhost:8086/write?db=droptest' --data-binary 'test_point,tag1=one value=1'; echo
HTTP/1.1 204 No Content
curl -G http://localhost:8086/query --data-urlencode "db=droptest"  --data-urlencode "q=DROP SERIES FROM test_point"; echo
{"results":[{"error":"open /var/opt/influxdb/wal/droptest/default/122/000000.meta: no such file or directory"}]}

The error was consistent through multiple cycles of drop and recreate, always referencing /var/opt/influxdb/wal/droptest/default/122/000000.meta

After restarting the daemon and using DROP MEASUREMENT I get a slightly different error message (/124 vs /122):
curl -G http://localhost:8086/query --data-urlencode "db=droptest"  --data-urlencode "q=DROP MEASUREMENT test_point"; echo
{"results":[{"error":"open /var/opt/influxdb/wal/droptest/default/124/000000.meta: no such file or directory"}]}

@erikogenvik I just realized that the examples we've been working on recently are using DROP SERIES not DROP MEASUREMENT. The DROP SERIES issue already exists: https://github.com/influxdb/influxdb/issues/3087.
Cannot repro the original DROP MEASUREMENT issue, closing.

@beckettsean it happened in my unit test, but I was able to reproduce it in a way I posted in the opening post of this issue. However here's a sample of my ruby unit tests which use influxdb-ruby client lib.
require 'test_helper'

class ServiceStatusTest < ActiveSupport::TestCase

  setup do
    @service = services(:six)
    @influx = InfluxSource.connect
    initialize_series
  end

  teardown do
    cleanup
  end

  test "if no influx data for dc, status data should be blank" do
    assert_equal Hash.new, @service.status_data('fo.foobar.dc1')
  end

  test "if no influx data for dc, state should be unknown" do
    assert_equal :unknown, @service.state('fo.foobar.dc1')
  end

  test "status data should return data for latest point if no datacenter specified" do
    seed_influx
    expected_result = {"time"=>0, "value"=>0.033333333, "status"=>"OK", "code"=>200, "result"=>"success"}
    assert_equal expected_result, @service.status_data
  end

  test "status data should return latest data for a specified datacenter" do
    seed_influx
    expected_result = {"time"=>0, "value"=>0.022225555, "status"=>"No\\ Content", "code"=>204, "result"=>"success"}
    assert_equal expected_result, @service.status_data('us.new-york.dc3')
  end

 # ...

  private

  def seed_influx
    @influx.write_points([
      {
        series: "response_times",
        tags: {
          service_id: @service.id,
          datacenter_id: 'pl.warsaw.dc1'
        },
        values: {
          value: 0.011111111,
          status: "Service unavailable",
          code: 503,
          result: 'failure'
        },
        timestamp:<PHONE_NUMBER>
      },
      # ... some more data
    ])
  end

  def initialize_series
    @influx.write_point('response_times', tags: {service_id: 0}, values: {value: 0})
  end

  def cleanup
    @influx.query "DROP MEASUREMENT response_times"
  end
end

What happens here is:

initialize_series is called before running each test - some non-relevant data is saved just to initialize the measurement.
some tests use seed_influx to save some data, some don't.
after each test cleanup is called which drops the measurement.

The database not open happened to my coworker as well, and I had to stub all the interaction with db.

Thanks for the clarification, @jacekgrzybowski. I'll reopen the issue, but InfluxDB is not optimized for deletes, and certainly not for rapidly deleting and then recreating a measurement. I do understand the use case for automated testing but it's not an actual real-world issue. This might be something we don't fix for a while.

+1
X-Influxdb-Version:<IP_ADDRESS>

We have had a lot of work since this issue was filed. I'm going to close this as the issue may not be relevant anymore. Please try again with a newer version of InfluxDB and either comment here or open a new issue if this is still happening. Thank you.


Added two links in WebDev

What does this PR do?
(Provide a description of what this PR does.)
Related PRs and Issues
(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you updated the README.md file?

[x] yes
[ ] no

Have you checked for any duplicates (was the content already present in the list?)?

[x] yes
[ ] no

Have you rechecked for any grammetical errors?

[x] yes
[ ] no

Is the content placed in proper position?

[x] yes
[ ] no

Is the a content quality resource?

[x] yes
[ ] no

Is the Repository your own or is it forked?

[x] Forked
[ ] Own

Please check and confirm

@Vishank-WrapPixel sorry for the late reply. The repository does not contain any learning material or any knowledge base which can be repetitively referred. Hence this pr cannot be merged.
Thanks for your efforts 👍🏻


'There was a problem with the requested skill's response' when deploying sample project

I've been trying to setup an Alexa bot that talks to Azure without success. First I tried to deploy the sample project but I kept running into exceptions being thrown by the Logger.
After removing the Logger from the application I finally managed to get something working.
However, whenever I try to type start skill  in the Test Console I keep getting that an error:

There was a problem with the requested skill's response

The strange thing is, is that on the right I actually see data coming back from the service:

I'm a bit confused on how a Sample project that seems to be working for other people won't work for me. I simply cloned the repository, gave a right click on the sample project and published it to Azure.

There might be a problem with Alexa Simulator itself. Let me check.

I did find the solution eventually, according to https://github.com/alexa/skill-sample-nodejs-quiz-game/issues/33#issuecomment-375890483 I had to activate the 'Display Interface' option:

I have no idea why this works though.

Oh, sure. Azure Function sample shows how to work with Dialog Model and requires it enabled. I'll take a look how we can indicate it in ReadMe.

Was this already resolved in the documentation?


not finding version number change on windows

I love the idea behind looking for the change to the <version></version> attribute, publishing and tagging based on this, however, I can't reliably get it to work.
I wonder if you can help by looking at my repo and config. The process correctly finds my project file but fails to recognise the version change.
https://github.com/cuzzlor/password-check/commit/d8a509d62c28514444bc853062844148308886f7/checks?check_suite_id=362514686
It reports: no version change in PasswordCheck.csproj
If I run  git diff -U0 HEAD^ I see:
diff --git a/src/PasswordCheck/PasswordCheck.csproj b/src/PasswordCheck/PasswordCheck.csproj
index 9deb62f..fc555a4 100644
--- a/src/PasswordCheck/PasswordCheck.csproj
+++ b/src/PasswordCheck/PasswordCheck.csproj
@@ -13 +13 @@
-    <Version>1.0.2</Version>
+    <Version>1.0.3</Version>

this looks right!
Any idea what I am missing?
Thanks!

One thing just occurred to me trying to work out why this worked a couple of times then stopped working. I changed to run on windows-latest so I could target net461, I bet that is why the.
Here is one that worked early on:
https://github.com/cuzzlor/password-check/commit/a1374662f7b22ebad94cdbc451a3cdeafc1e9d30/checks?check_suite_id=361776879
Vs not working on Windows:
https://github.com/cuzzlor/password-check/commit/d8a509d62c28514444bc853062844148308886f7/checks?check_suite_id=362514686
Might be worth adding some debug code and running (on windows) to see if it's the git diff with path or the regex test that isn't working the same way..

I have done some debugging (on windows) and have found that running git diff via execSync always returns an empty string:
gitDiff = execSync(git diff -U0 HEAD^ -- ${projPath}, { encoding: "utf-8" }),
I can't work out why, because running the same git diff command outside of execSync works perfectly.
Some strange windows quirk. I tried changing lots of the execSync options such as cwd, shell etc and nothing seems to make a difference. It's not encoding, if I use the buffer returning overload the buffer is empty.

Hey @cuzzlor that's a ton of digging you've done on this & I truly appreciate the effort
I haven't really tested it out on windows-latest as my target has always been .NET Core with ubuntu-latest but let me take a look & see if I can fix it somehow. I'll respond here as I make progress

Thanks @rohith much appreciated. I have PR'd a fix for the command command also not being available on windows. When I researched a cross platform method to check if a command exists it seems surprisingly hard, therefore I just went for an easy truth check against the dotnet --version command.


Create a tutorial using a 'hello-world' repository in documentation

Create a hello-world public repository and use this repository in a 'deploying your first image' tutorial

Moved to the-concierge/concierge#5


[1.8.3 to 1.9.0] Error starting daemon: could not restore image

Description of problem:
After upgrading from 1.8.3 to 1.9.0, I noticed that on one of my boxes, the daemon didn't come back up.
docker version:
# docker version
Client:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   76d6bc9
 Built:        Tue Nov  3 17:43:42 UTC 2015
 OS/Arch:      linux/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

docker info:
n/a
uname -a:
# uname -a
Linux docker1 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Environment details (AWS, VirtualBox, physical, etc.):
KVM VM
How reproducible:
I can reproduce it on this one box I have; not sure about any others but I haven't seen the same upgrade issues on any other Ubuntu 14.04 box.
Steps to Reproduce:

Start from Docker engine 1.8.3 on Ubuntu 14.04
Upgrade engine
Daemon doesn't start

Actual Results:
The daemon does not start; daemon logs show:
INFO[0000] [graphdriver] using prior storage driver "aufs"
INFO[0000] Option DefaultDriver: bridge
INFO[0000] Option DefaultNetwork: bridge
WARN[0000] /!\
INFO[0000] Listening for HTTP on tcp (<IP_ADDRESS>:2375)
INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
WARN[0000] Running modprobe bridge nf_nat br_netfilter failed with message: modprobe: WARNING: Module br_netfilter not found.
insmod /lib/modules/3.13.0-66-generic/kernel/net/llc/llc.ko
insmod /lib/modules/3.13.0-66-generic/kernel/net/802/stp.ko
insmod /lib/modules/3.13.0-66-generic/kernel/net/bridge/bridge.ko
insmod /lib/modules/3.13.0-66-generic/kernel/net/netfilter/nf_conntrack.ko
insmod /lib/modules/3.13.0-66-generic/kernel/net/netfilter/nf_nat.ko
, error: exit status 1
INFO[0000] Firewalld running: false
INFO[0000] Loading containers: start.
......
INFO[0000] Loading containers: done.

INFO[0000] API listen on [::]:2375
INFO[0000] API listen on /var/run/docker.sock
INFO[0000] [graphdriver] using prior storage driver "aufs"
FATA[0000] Error starting daemon: could not restore image 27cf784147099545: invalidimageid: image ID '27cf784147099545' is invalid

Expected Results:
Upgrade works as expected and daemon starts
Additional info:
I was able to roll back to Docker 1.8.3 so I can get detailed information about the containers and any other environmental info that might be helpful.

Now images are restored on daemon startup and you actually have an image which is invalid (probably an old one I suppose?)
ping @calavera do we actually want not to fail in this case? Should we prevent corrupted images to be written under graph/ at all?
@mbentley you should have a folder under /var/lib/docker/0.0/graph/27cf784147099545/ which seems to be corrupted (?), could you check? could you also backup that dir and delete it and see if restarting the daemon works? you shouldn't even be able to see that image ID in docker images -a, could you also check this? Thanks!

@runcom - Yup, that fixed it.  It existed under /var/lib/docker/graph/27cf784147099545/.  I kept a tar of it if it is of any interest.

@mbentley could be useful to share it if you want so we can see which files got corrupted, but to me, it really seems like an old image (ID hasn't been validated at all), could you actually see that image id in docker images -a?

@runcom - Nope, I couldn't see it with a docker images -a.
Here is the tar of the layer.  It's pretty small.
https://dl.dropboxusercontent.com/u/30237834/27cf784147099545.tar

@mbentley thanks a lot

do we actually want not to fail in this case? Should we prevent corrupted images to be written under graph/ at all?

I'm not sure about it. Maybe we should just go back to the old behavior, ignoring all corrupted images. It looks like there are more cases than we expected. I think logging the error about invalid images is good in any case.

I'm not sure about it. Maybe we should just go back to the old behavior, ignoring all corrupted images. It looks like there are more cases than we expected. I think logging the error about invalid images is good in any case.

fair, I'm gonna remove the return when the error != EOF so everything is logged but it won't actually make the daemon crash

Same issue for me on the upgrade, same image ID.

@jkaplon #17695 has been merged and will probably be in 1.9.1 soon

Had same problem, folder above didn't exist in the exact path.
Found it at /var/lib/docker/graph
Had to 'sudo mv /var/lib/docker/graph /var/lib/docker/graph.old' for it to work.
Then after ' sudo systemctl start docker' it seems to create the 'graph' folder. It's now empty but all is working well inc. auto started containers.
Hope it helps someone.

@srfrnk the folder I mentioned above was his case and could be not the same as everyone

but thanks!

@runcom sure - no prob :) just thought maybe it'l save time for next person

I also had the same problem. Removing the folder from /var/lib/docker/graph fixed the startup.
Btw I use ubuntu 15.10 with the https://apt.dockerproject.org/repo repository.


ripasso-cursive: unstable-2019-08-27 -> 0.2.1

Motivation for this change
Updates ripasso-cursive to the latest release.
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

CC @etu

@GrahamcOfBorg build ripasso-cursive

Curious, I'm getting the following build failure locally (NixOS x86_64):
running 2 tests
test pass::test::get_password_dir_no_env ... ok
test pass::test::get_password_dir ... FAILED

failures:

---- pass::test::get_password_dir stdout ----
thread 'pass::test::get_password_dir' panicked at 'called `Result::unwrap()` on an `Err` value: Generic("failed to locate password directory")', src/libcore/result.rs:1084:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

failures:
    pass::test::get_password_dir

test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out

error: test failed, to rerun pass '--lib'
builder for '/nix/store/rgdqspr9wm7z537a4536jfz0vwr5q4sd-ripasso-cursive-0.2.1.drv' failed with exit code 101
error: build of '/nix/store/rgdqspr9wm7z537a4536jfz0vwr5q4sd-ripasso-cursive-0.2.1.drv' failed

But it seems to work on the build bot. The bot managed to build it on both aarch64 and x86_64 linux. So that's fine I guess?
We also have darwin as a new platform, where the build seems to fail. You have the full log here: https://logs.nix.ci/?key=nixos/nixpkgs.72188&attempt_id=abcfb437-2b42-4c2a-8f14-2a6465364206

We also have darwin as a new platform, where the build seems to fail. You have the full log here: https://logs.nix.ci/?key=nixos/nixpkgs.72188&attempt_id=abcfb437-2b42-4c2a-8f14-2a6465364206

@alexanderkjall Looks like a problem setting up the test environment? I'll be able to have a look on Darwin tomorrow.

I'll be able to have a look on Darwin tomorrow.

Stuck in the snow :snowman_with_snow:

Thx to @tssm for fixing MacOS build.
Pls don't merge yet. 0.3.0 is out, will update for this new version.

note: ripasso-cursive builds on macOS with nix-build -A ripasso-cursive, but nix-review fails:
$ nix-shell -p nix-review --run "nix-review pr 72188"
$ git -c fetch.prune=false fetch --force https://github.com/NixOS/nixpkgs master:refs/nix-review/0 pull/72188/head:refs/nix-review/1
$ git worktree add /Users/user/.cache/nix-review/pr-72188-1/nixpkgs 8d0263863a806af0a6bb66b09d849243e65e6a15
Preparing worktree (detached HEAD 8d0263863a8)
Updating files: 100% (20386/20386), done.
HEAD is now at 8d0263863a8 Merge pull request #74824 from jojosch/dbeaver_6.3.0
$ git merge --no-commit 2523a7f377d8d7fcd09c5e861b6346e162556aed
Auto-merging pkgs/top-level/all-packages.nix
Automatic merge went well; stopped before committing as requested
$ nix build --no-link --keep-going --max-jobs 4 --option build-use-sandbox true -f /Users/user/.cache/nix-review/pr-72188-1/build.nix
builder for '/nix/store/dd133ml884435n7byw2rgzr71f9gfgyn-source.drv' failed with exit code 1; last 10 log lines:
                                   Dload  Upload   Total   Spent    Left  Speed
  100   129    0   129    0     0    360      0 --:--:-- --:--:-- --:--:--   360
  100  115k    0  115k    0     0   114k      0 --:--:--  0:00:01 --:--:--  210k
  unpacking source archive /private/var/folders/g1/y968ywwx2s9c016g26_dbpcm0000gn/T/nix-build-source.drv-0/release-0.3.0.tar.gz
  dyld: Library not loaded: @rpath/CoreFoundation.framework/Versions/A/CoreFoundation
    Referenced from: /nix/store/rrg9ab9wnnd0n9hkl55miah824vv1xjq-gettext-0.20.1/lib/libintl.8.dylib
    Reason: no suitable image found.  Did find:
   /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation: file system sandbox blocked stat()
  /nix/store/ggw6axmdf4bg17z2pc2zaxpd1fjhsy3d-stdenv-darwin/setup: line 836:   687 Abort trap: 6           tar xf "$fn"
  do not know how to unpack source archive /private/var/folders/g1/y968ywwx2s9c016g26_dbpcm0000gn/T/nix-build-source.drv-0/release-0.3.0.tar.gz
cannot build derivation '/nix/store/zz9jv5havdgas57g382qlmh8drdqwndb-ripasso-cursive-0.3.0-vendor.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/vdh81mx9is33q034kpjry94c0nqgzaxw-ripasso-cursive-0.3.0.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/gqxyd9jpc5lslcyxv22c8cx1igfvjffn-env.drv': 1 dependencies couldn't be built
[0 built (1 failed)]
error: build of '/nix/store/gqxyd9jpc5lslcyxv22c8cx1igfvjffn-env.drv' failed
https://github.com/NixOS/nixpkgs/pull/72188
1 package failed to build:
ripasso-cursive

[0.0 MiB DL]
error: build log of '/nix/store/vdh81mx9is33q034kpjry94c0nqgzaxw-ripasso-cursive-0.3.0.drv' is not available
$ nix-shell /Users/user/.cache/nix-review/pr-72188-1/shell.nix

On darwin:
Result of nix-review pr 72188 1

1 package were built:

ripasso-cursive

@GrahamcOfBorg build ripasso-cursive


Many Packt books are not free anymore

What does this PR do?
Remove Resource(s)
For resources
Description
Packt has removed quite a few of their free ebooks on this list. I checked the ones that were removed and they all cost around 5 USD right now. If I'm not mistaken, there are some new ones that are not on the list so I'll add them later.
Why is this valuable (or not)
How do we know it's really free?
For book lists, is it a book?
Checklist:

[ ] Not a duplicate
[ ] Included author(s) if appropriate
[ ] Lists are in alphabetical order
[ ] Needed indications added (PDF, access notes, under construction)

It's a good reason to give preference to CC licenses.


Add new facility ports permissions for network model update 2a

Net.FacilityPort.Cloud-Facility-GCP "Google Cloud Platform"
Net.FacilityPort.Cloud-Facility-AWS "Amazon Web Services"
Net.FacilityPort.Chameleon-TACC "Chameleon@TACC Production"
Net.FacilityPort.Cloud-Facility-Azure-Gov "Microsoft Azure Gov Cloud"
Net.FacilityPort.Cloud-Facility-Azure "Microsoft Azure Cloud"
re: FIP-383

done, closing


add write::GzDecoder

ok, I'll remove tokio impls. I think write_buf has bug, I'll update later today.

should be good now

ping

i change strategy for partial gz header parsing.

any news?

Awesome, thanks so much for being patient and sticking with this!

Great! Could you make crates release with this Pr?

Thanks


Plan Approval Progress at Plan Page | Plan Status

See #372 and #376 to understand the status model and concept.
We want to display the plan progress on the UI. We will have a dedicated endpoint that returns the process itself (see #376).

See the full design in the figma link: [Status progress at Figma] (https://www.figma.com/file/za4s6kKXMHh0X3URWVpXg1/Meirim.org---2022?node-id=8141%3A115329) and
how it's part of mobile and desktop plan page
This task is UI only, with some BE integration. It consits of two parts: 1) creating the generic progress bar component, and 2) implementing and integrating in the plan page.

[ ] Create a new generic component, that renders the step progress bar. It should support multiple steps (1-10).
- [ ] There should be an indication of the current step
- [ ] There should be an indication of whether the current step is blocked (see the design, the red colouring)
- [ ] There should be an indication of whether the current step is completed, therefore, the process has finished  (see the design, the blue
colouring)
- [ ] The component should be responsive, and fit to the given height + width it's given
-  [ ] On hovering each step, a custom message may appear (optional)

[ ] Implement the new progress componnet at the plan page.
- [ ] Under the summary tab, add a new section called ״תהליך התכנוני״ (make sure to use the translation file)
- [ ] within it, render the new progress component.
- [ ] On loading the plan, there should be a request to the /:planId/progress endpoint
- [ ] Map the received response to present at the new progress. Make sure you use the isBlocked, isCompleted properties of each step.

@drorgivton , does the red button design refer to "cancelled" plans?


Blazor doesn't seem to follow default namespace

Describe the bug
Blazor generates cs files with a namespace using the project name instead of the default namespace
My csproj has
  <PropertyGroup>
    <TargetFramework>netstandard2.0</TargetFramework>
    <OutputType>Exe</OutputType>
    <LangVersion>7.3</LangVersion>

    <!-- The linker is not beneficial for server-side execution. Re-enable this if you switch to WebAssembly execution. -->
    <BlazorLinkOnBuild>false</BlazorLinkOnBuild>
    <Configurations>Debug;Release</Configurations>
    <RootNamespace>WebAppBootStrap.App</RootNamespace>
  </PropertyGroup>

but the generated WebAppBootStrap.App-core3_ViewImports.cshtml has
namespace WebAppBootStrap.App_core3 instead of WebAppBootStrap.App
To Reproduce
Steps to reproduce the behavior:

Create a project WebAppBootStrap.App-core3
Set WebAppBootStrap.App as default namespace
Write startup.cs
as

namespace WebAppBootStrap.App
{
    public class Startup
    {
        public void ConfigureServices(IServiceCollection services)
        {
            services.AddSingleton<AppState>();
        }

        public void Configure(IComponentsApplicationBuilder app)
        {
            app.AddComponent<App>("app");
        }
    }
}

Possibly related:
If the project name doesn't match the project folder name, none of the in-project components will be detected as components during the BuildRenderTree generation. They get picked up only as normal tags.
Ex.: A new project is created using the Razor Components template. The client app project file is renamed from Project1.Client.App.csproj to Project1.App.csproj, but the project folder isn't renamed. (In VS2019, project folders are out of view, and aren't renamed automatically when a project is renamed).
Component2.cshtml is located in the same folder as Component1.cshtml. <Component2 /> is used inside of Component1.cshtml.
When the project is built, both component files are detected as components and generated class files are produced for both files. Generated namespaces match the folder structure.
However, in Component1.cshtml.g.cs, the code corresponding to the Component2 /> tag is builder.OpenElement(0, "Component2") rather than builder.OpenComponent<Project1.App.Shared.Component2>(16).

#5524

The project/folder name issue is reporeted here: #6155

Thanks for contacting us, @ErikApption.
This will be fixed in VS 16.1 release.

Is there any way to specify the desired namespace for the component?


fatal error: non-Go code set up signal handler without SA_ONSTACK flag

Using go-libreofficekit I have this error message coming up:
signal 23 received but handler not on signal stack
fatal error: non-Go code set up signal handler without SA_ONSTACK flag

runtime stack:
runtime: unexpected return pc for runtime.sigtramp called from 0x7f25a7ad1228
stack: frame={sp:0xc000078ed8, fp:0xc000078f30} stack=[0xc000070e08,0xc000079208)

To avoid it I had to recompile libreoffice with the following patch:
diff --git a/sal/osl/unx/signal.cxx b/sal/osl/unx/signal.cxx
index 79721def6c5e..0694fc3c7b26 100644
--- a/sal/osl/unx/signal.cxx
+++ b/sal/osl/unx/signal.cxx
@@ -197,7 +197,7 @@ bool onInitSignal()

     struct sigaction act;
     act.sa_sigaction = signalHandlerFunction;
-    act.sa_flags = SA_RESTART | SA_SIGINFO;
+    act.sa_flags = SA_RESTART | SA_SIGINFO | SA_ONSTACK;

     sigfillset(&(act.sa_mask));

I will attempt to report the problem to the libreoffice project but meanwhile we have a workaround.

I reported the issue to the libreoffice project: https://bugs.documentfoundation.org/show_bug.cgi?id=140189

Not ideal, but a workaround I've used is to use Go 1.13.
1.14+ seems to throw this error

any new??

The issue in the libreoffice bugtracker is still "UNCONFIRMED", so for now we still use our recompiled libreoffice (and it works well).
I just changed the bug status to "NEW", as I am not the only one to have the issue (see https://wiki.documentfoundation.org/QA/BugReport/fr#Status)

Anyone come up with other choices besides compiling their own libreoffice? I'd like to be able to use Go Modules to vendor packages, and need to make it up to 1.14

I found a workaround and create pull request(https://github.com/dveselov/go-libreofficekit/pull/16)
By processing the signal on the C side, and adding a SA_ONSTACK flag.
static void libre_fix_signal(int signum)
{
    struct sigaction st;

    if (sigaction(signum, NULL, &st) < 0) {
        goto fix_signal_error;
    }

    st.sa_flags |= SA_ONSTACK;

    if (sigaction(signum, &st,  NULL) < 0) {
        goto fix_signal_error;
    }
    return;
fix_signal_error:
        fprintf(stderr, "error fixing handler for signal %d", signum);
}

void libre_init()
{
    signal(SIGURG, libre_fix_signal);
}

After importing the library, you need to call the function libre_init()
func init() {
	C.libre_init()
}

In my tests, there is no more panic and the lib works.


The exit button on the Artifact menu cannot be clicked on small monitors

Closed by https://github.com/AzerothWarsLR/WarcraftLegacies/commit/adfcace65f2fc59e0cd0100a887d46a0987c34c4.


Reseting model

I have some recommendation data in oryx. How can I remove everything I had sent there without reformatting hdfs?

You can just delete data and or models from the data and model dirs you set up on HDFS. You may also need to delete the Kafka topics to be sure they are empty.

I am still not able to reset model. Initially model is in place:

Now I kill hdfs, yarn, oryx-batch, oryx-serving, oryx-speed:

Now I delete all hdfs files and format hdfs the partition:

And recreate kafka topics:

After restarting yarn, hdfs, orix-* I still see model not being reset:

It looks like there is some inner cache somewhere inside one of layers, how can I reset it?

There are still a number of possibilities, and I think they're specific to your deployment.

 I'm not clear from the text above. That isn't using the script from the project.
Are you sure you deleted the topics? this shows they existed already, not deleted.


feat: ProtocolHandler

Part of https://github.com/kkrt-labs/kakarot/issues/1515
The owner of the Kakarot contract will be an intermediary contract: the ProtocolHandler.
This PR introduce the structure of the contract and implements the Admin functions:
fn emergency_execution(ref self: TContractState, call: Call);
fn upgrade(ref self: TContractState, new_class_hash: ClassHash);
fn transfer_ownership(ref self: TContractState, new_owner: ContractAddress);
fn soft_pause(ref self: TContractState);
fn hard_pause(ref self: TContractState);
fn unpause(ref self: TContractState);

Time spent on this PR:
Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Resolves #
What is the new behavior?
ProtocolHandler contract

This change is

Missing github CI


Errors timeout after 5 seconds.

Closes #542.

We may want to think about an exit animation at some point in the future.

:+1:


Add tip rename master to main

Description

Checklist

[x] I made sure that the markdown files are formatted properly.
[x] I made sure that all hyperlinks are working.

[x] I added the new content to the README.md inside the topics subdirectory, e.g., 01_version_control/README.md.
[x] I added the new content to the timetabe.md in the root of this repository.
[x] I make sure to update the content/links on the homepage.

Just saw this is already inside the exercise, I just missed it, sorry


[Query] How to label Dependabot Security Alert PRs

Dependabot creates two types of pull requests - standard version bumps and security vulnerability bumps.
Is there a way we can add a 'security' label to the latter?
Thanks

Closing as a dupe of https://github.com/dependabot/dependabot-core/issues/2294 which is "add more labels."
I will say that the "security" label is a bit tricky because as of right now, we only show admins that a PR fixes a vuln, while adding a label would be public to all repo viewers. This is mostly an issue on public repos, so there's a thought that we might only add this to private repos to start.
I will also say that if we go down the "actions labeler" path, as discussed in the issue, we will need to provide some sort of signal to the action, which is an open question on our side.

Thanks will check the other issue. For our large org of private repos, your suggestion would be very helpful. Thanks


Library Request: TensorTrade

Expected Behavior
Supports tensortrade
tensortrade is an open-source Python framework for building, training, evaluating, and deploying robust trading algorithms using reinforcement learning.
Actual Behavior
Not supported.
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

tensortrade==1.0.3 is already in the current foundation image


Go client timeout on Interop Cloud to Cloud tests

All the interop cloud-to-cloud tests involving Go clients seem to start failing since 11am Aug 5 PDT.
Dashboard (master): https://fusion.corp.google.com/projectanalysis/summary/KOKORO/prod:grpc%2Fcore%2Fmaster%2Flinux%2Fgrpc_interop_tocloud
Log example: https://source.cloud.google.com/results/invocations/b429d843-9d0d-4fb5-a90c-0bcf43414373/targets/grpc%2Fcore%2Fmaster%2Flinux%2Fgrpc_interop_tocloud/log
Cloud-to-Prod seems to be fine.

Potentially caused by grpc/grpc-go#3786
@easwars is taking a look

This should take care: https://github.com/grpc/grpc-go/pull/3804

Looks like we are getting back some green builds! Will monitor a little more. Thanks!


Move source and make build with latest Skia

PR by @sunflowerdeath refined to match project goals.

Turns out that we were building with C++14 on mac. Needed to revert std::tuple (which doesn't have a constexpr ctor in C++11) to the previously used struct.


[ENHANCEMENT] remote storage:Add default api implementation of remote write

[ENHANCEMENT] remote storage:Add default api implementation of remote write

@csmarchbanks @cstyan
remote storage module pr

prometheus.yaml 1
global:
scrape_interval:     15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
scrape_configs:

job_name: 'prometheus'
static_configs:

targets: ['localhost:9090']

prometheus.yaml 2
global:
scrape_interval:     15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
scrape_configs:

job_name: 'kafka'
static_configs:

targets: ['<IP_ADDRESS>:9997']

job_name: 'zookeeper'
static_configs:

targets: ['<IP_ADDRESS>:8997']
remote_write:

url: http://localhost:9090/api/v1/write
name: prometheus-hangzhou

This PR appears to be adding push to Prometheus, which is an explicit non-goal of the project.

Is that really something that can be solved in 126 lines of code? What is the catch?

@liguozhong Yeah this isn't really something we plan to support. You might find Thanos appealing as it's deployment on top of Prometheus to add a global query layer is relatively minimal. Otherwise remote write systems such as those suggest by Brian or others listed here are your best options.

This PR appears to be adding push to Prometheus, which is an explicit non-goal of the project.
I'd suggest looking at options like Cortex or M3.

thanks.
We use it in an IOT project. We write it to a remote storage of influxdb through remote write. Because the memory and CPU disk configuration of edge host are relatively low, and the network is unidirectional, but in the case of regular condition label filtering such as metrics {namespace ~ = ". *"}, influxdb The query performance of is very slow,And we are worried that in the future, if the influxdb fails, it will be difficult for us to recover from the failure . so we want to switch to Prometheus as a PlanB.
4 cpu core ,8GB mem: [edge host 1] [edge host 2] [edge host 3] （prometheus server）
⬇（by remote storage write）
24 core, 128GB mem: [iot master host 1]  （influxdb）
⬇（by remote storage read）
[prometheus server]
⬇(by promql  http api)
[grafana]
We only have one large memory host that can be used to store time series data. We don't know whether cortex or m3 can be deployed on one host. In addition, our team is only familiar with Prometheus thanos at present.
yeah , Prometheus is a pull model. I will close this PR first. We will maintain it in our branch for a while.

Yeah

thanks.
We have used thanos in other projects, Thanos is a great project.
but thanos is not suitable for IOT projects. Thanos needs 128GB memory host, and the network is bidirectional.
Edge host has only 8 GB of memory, and the network can only send out and prohibit inward network communication

Is that really something that can be solved in 126 lines of code? What is the catch?

Is that really something that can be solved in 126 lines of code? What is the catch?

Yes, the 126 line code works. We are going to use this PR in an IOT project, but this PR is still in the stage of performance test and stress test.
refs map[string]uint64
We are worried that this "refs cache" will expand infinitely and eventually lead to failure, but there is no good way to solve it at present. We hope that it can be put in the community and other experts can help to complete the optimization of "refs cache"

Is that really something that can be solved in 126 lines of code? What is the catch?

Yes, the 126 line code works. We are going to use this PR in an IOT project, but this PR is still in the stage of performance test and stress test.
refs map[string]uint64
We are worried that this "refs cache" will expand infinitely and eventually lead to failure, but there is no good way to solve it at present. We hope that it can be put in the community and other experts can help to complete the optimization of "refs cache"

Hello @liguozhong , we are willing to support this! Can you please help us? We are currently working on a design document:
#8307  https://docs.google.com/document/d/1PpTDtVaKAnhMRxBJ0k7_rCQ3Z3uJVcALgdPo0QpObSk
Thanks!!!!

Okay, I will complete this PR task

Hello @liguozhong , we are willing to support this! Can you please help us? We are currently working on a design document:
#8307 https://docs.google.com/document/d/1PpTDtVaKAnhMRxBJ0k7_rCQ3Z3uJVcALgdPo0QpObSk
Thanks!!!!

Okay, I will complete this PR task