How to load the tree data only when it is needed?

I'm looking for a behavior similar to the java swing JTree. I want to build a tree model that allows the tree data to be loaded only when it is needed. My app's data is stored in a database and it is not practical to load it all into memory to build all the nodes up front. I suspect I can implement this but I'm curious since all the example code shows cases where the tree is loaded into memory.

Hi @swframe,
Sorry for reaching to you directly, but I was wondering if you've managed to find a solution to this issue?
We're also looking to lazy load list of files within folders and hoped there is an example here before we scratch heads ourselves.

I wrote a temporary solution but it repaints the tree when the nodes open/close.
I store the nodes that the are opened and when that Set changes I completely rebuild the tree.
I only load the children if the node is in the 'opened' set. I cache the children so once they
are loaded, they are not reloaded until the cache expires. I add a fake child to each node that
is closed so the UI will draw '>' to let the user know the node is not a leaf.
This is really hacky but it allows me to work on other features.
I will continue to work on it to implement a more efficient way to open and close
without needing to rebuild the entire tree widget. It shouldn't be too hard.

Thanks, we've addressed some of these issues and provided lazy load example: https://github.com/embraceitmobile/animated_tree_view/compare/main...tomekit:animated_tree_view:main#diff-2f45cb6453ada31c3ecd0f5cc5e11dedac8361c32f724278a9ccb4b749dbd435
There shouldn't be need to add fake child items or repaint tree.
I am not sure what else might come up at this stage, but with these changes we're happy to integrate it within our project.

Thanks! I will try it out.


[fix] prevent offload non-persistent or system topics

When ledger is closed, do not offload when this ledger is non-persistent or system topics.

Motivation
When ledger is closed, do not offload when this ledger is non-persistent or system topics.
Modifications

Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

NonPersistentTopic has no ledgers to persist messages, so we don't need to care about it.
About SystemTopic, I remember there is a PR to fix it

Got it, https://github.com/apache/pulsar/pull/22497

Got it, #22497

Thanks! But I see the #22497 did not merge. In our scenario, due to system topic triggered offload, many exceptions were printed in the log, so I submitted the above modifications

Got it, #22497

Thanks! But I see the #22497 did not merge. In our scenario, due to system topic triggered offload, many exceptions were printed in the log, so I submitted the above modifications

let me ask him, if there is no other problems, I'll reopen and merge it

Got it, #22497

Thanks! But I see the #22497 did not merge. In our scenario, due to system topic triggered offload, many exceptions were printed in the log, so I submitted the above modifications

let me ask him, if there is no other problems, I'll reopen and merge it

Thanks！

@chunxiaozheng https://github.com/apache/pulsar/pull/22497 merged, let's close this PR

@chunxiaozheng #22497 merged, let's close this PR

okay，thanks！


Fix value upgraded from version 3

Version 3 of SwiftyUserDefaults saved Array<String|Int|Float|Double...> as Array in UserDefaults, if upgrade it to version 4 or 5.x, the value will be saved as Codable. Then the values will be lost in the new version.

@sunshinejr could you review this, please?

Version 3 of SwiftyUserDefaults saved Array<String|Int|Float|Double...> as Array in UserDefaults, if upgrade it to version 4 or 5.x, the value will be saved as Codable. Then the values will be lost in the new version.

Another situation is: the user used UserDefaults directly before, and now is using SwiftyUserDefaults.

Why hasn't this pr been reviewed yet?


Server/Dashboard: Error showing "About" (/info) page

Installed Epinio to RKE2 cluster with ./epinio-0.0.11 install --system-domain epinio.paas.suse.de.
Accessing "http://epinio.epinio.paas.suse.de/" works, showing the Epinio dashboard (https will not work).
If I click on "About" (-> http://epinio.epinio.paas.suse.de/info), I'll get the following error message:
html/template:page_template:113:15: no such template "new-org-modal"
and the server logs:
2021/04/27 08:21:33 http: superfluous response.WriteHeader call from github.com/epinio/epinio/internal/web.handleError (applications_controller.go:163)
This hould not happen, and the info page should be shown.

Still happens with Epinio-0.0.12: "html/template:page_template:113:15: no such template "new-org-modal""

> grep -rn new-org-modal .
./assets/embedded-web-files/views/modals.html:1:[[define "new-org-modal"]]
./assets/embedded-web-files/views/main_layout.html:113:    [[template "new-org-modal"]]

The line number in the error message matches the location in the main_layout.html file where the template is invoked.
I suspect that modals.html is somehow not present/used/invoked, leaving the the template it defines as not known.

The template icon-plus-rectangle defined inicons.html otoh does not cause an error. Lets see how that file is made use of.

./internal/web/info_controller.go:37:	Render([]string{"main_layout", "icons", "info"}, w, r, data)
./internal/web/applications_controller.go:109:	Render([]string{"main_layout", "icons", "modals", "applications_index"}, w, r, data)

looks promising.

Certes.


v1.8.0rc4 collector

Post recovery from v1.8.0rc3:

[x] lnd shows v0.14.2 on display vs
₿ lncli getinfo
{
    "version": "0.15.0-beta commit=v0.15.0-beta",

even after a restart:
₿ /home/admin/_cache.sh meta ln_lnd_mainnet_version
value="0.14.2-beta"
initiated=1
lasttouch="1658356611"
outdatesecs="-1"
stillvalid="1"

This is due to  a mismatch with lit:
admin@<IP_ADDRESS>:~ ₿ lnd --version
lnd version 0.15.0-beta commit=v0.15.0-beta
admin@<IP_ADDRESS>:~ ₿ lncli --version
lncli version 0.14.2-beta commit=lightning-terminal-v0.6.3-alpha

[x] ssh menu didn't progress from sync screen (lnd autounlock is used)

ok, I think I was just too impattient. This is not reproducable.

[ ] blitzapi restart fixed
[ ] access to lightning-rpc for blitzapi fixed


Are there plans to merge this?

We are evaluating TiDB but need graph querying. TiGraph looks like a great option if it becomes production-grade.
Does the team intend to merge this with TiDB at some point, or is TiGraph just sitting here as a forgotten hackathon project?

+1 for TiGraph in TiDB


Add OSGi support

This change moves to using the biz.aQute.bnd Gradle plugin to
produce OSGi-compatible manifests in jar files. Currently, only the
org.agrona.core module has been updated to provide OSGi metadata
because the Agrona agent should never need to be visible inside an
OSGi container. Care has been taken to preserve the existing defined
manifest fields (Automatic-Module-Name, Implementation-Title, etc).

I think static.javadoc.io is having problems today. I saw a couple of failures like this when I built locally, but they stopped occurring when I built on my own Travis CI account.

what does this mean for the manifest in the normal Jar?

what does this mean for the manifest in the normal Jar?

I've preserved the properties you were using in the jar and this adds extra OSGi headers on top. This was your old jar manifest (agrona 1.0.3):
$ bnd print agrona-1.0.3.jar
[MANIFEST agrona-1.0.3]
Automatic-Module-Name                    org.agrona.core
Implementation-Title                     Agrona
Implementation-Vendor                    Real Logic Limited
Implementation-Version                   1.0.3
Manifest-Version                         1.0

This is the manifest now:
$ bnd print ./agrona/build/libs/agrona-1.0.4-SNAPSHOT.jar
[MANIFEST agrona-1.0.4-SNAPSHOT]
Automatic-Module-Name                    org.agrona.core
Bundle-ManifestVersion                   2
Bundle-Name                              org.agrona.core
Bundle-SymbolicName                      org.agrona.core
Bundle-Version                           1.0.4.SNAPSHOT
Export-Package                           org.agrona;uses:="org.agrona.concurrent,sun.misc";version="1.0.4",org.agrona.collections;version="1.0.4",org.agrona.concurrent;uses:="org.agrona,org.agrona.concurrent.status";version="1.0.4",org.agrona.concurrent.broadcast;uses:="org.agrona,org.agrona.concurrent";version="1.0.4",org.agrona.concurrent.errors;uses:="org.agrona,org.agrona.concurrent";version="1.0.4",org.agrona.concurrent.ringbuffer;uses:="org.agrona,org.agrona.concurrent";version="1.0.4",org.agrona.concurrent.status;uses:="org.agrona,org.agrona.collections,org.agrona.concurrent";version="1.0.4",org.agrona.console;version="1.0.4",org.agrona.generation;uses:="javax.tools";version="1.0.4",org.agrona.hints;version="1.0.4",org.agrona.io;uses:="org.agrona";version="1.0.4",org.agrona.nio;version="1.0.4",org.agrona.sbe;uses:="org.agrona";version="1.0.4"
Implementation-Title                     Agrona
Implementation-Vendor                    Real Logic Limited
Implementation-Version                   1.0.4-SNAPSHOT
Import-Package                           javax.tools,org.agrona,org.agrona.collections,org.agrona.concurrent,org.agrona.concurrent.status,org.agrona.hints,sun.misc,sun.nio.ch
Manifest-Version                         1.0
Require-Capability                       osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"

All of these properties are ignored by anything that isn't either an OSGi tool, or an OSGi container.

Thanks. That makes sense. I'm merge when javadoc.io lets the tests complete.


fix(tables): Cell reactivity

Resolves #6376 #5722

maybe rename PR "table reactivity" since "cell reactivity" is still TODO?


[Improve] Improve streampark-spark module based on [4 Exception Processing]

Search before asking

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

Description
[Improve] Improve streampark-spark module based on 4 Exception Processing
Usage Scenario
No response
Related issues
#2986
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

N.A


Backend gets 500 from Ollama that works fine

Describe the bug
I get
perplexica-backend-1   | error: Unhandled Rejection at: [object Promise], reason: Error: Ollama call failed with status code 500: llama runner process no longer running: -1

To Reproduce
Launch Perplexica with OLLAMA = "http://host.docker.internal:11434"  in config, launch ollama and configure to use it
Additional context
Perplexica sees ollama, because I can choose it in settings, it also correctly detects the model that is running.
I checked ollama with
curl http://localhost:11434/api/generate -d '{
  "model": "aya",
  "prompt":"Why is the sky blue?"
}'

And it works fine.

It seems to work fine for me, maybe checkout https://github.com/ollama/ollama/issues/3774


[Bug report]:  Fix language unknown error

Platform
Desktop
Version
desktop-2.0.0-beta-1.0.1
Description
When using the Shimmer Firefly wallet, if change the language will show an unknown error.
Expected behaviour
If the language setting has an issue, needs to show up an error message.
Actual behaviour
Here are the steps:

Choose Simplified Chinese
Then set the Pin Code
Click Next
Then there is no response and no error message

And if switch back to EN, it can work.
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue

Choose Simplified Chinese
Then set the Pin Code
Click Next
Then there is no response and no error message

Operating System
Linux
Diagnostics
No response
Developer Profile
Yes
Profile Type
Software (Stronghold)
Staking
Actively staking
Crash Status
Non-responsive
Error Messages
No response
Error Logs
No response
Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

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

It looks like the problem are non-latin alphabets.
I tested it with: greek, russian, chinese for i got stuck after entering the pin, and english, german, italian, spanish for which it works

Hmm I've tested Japanese and Chinese both in the dev instance and the Beta build - didn't have any problems with this :thinking: @annie101101046 would you mind providing more info about your system / OS?

I've also just tested with simplified Chinese, recovering a profile and logging into an already created profile, and I cannot reproduce this issue.

Also cannot reproduce it.


[Bug]:@use-funnel/browser is not being processed on the server side.

Package Scope
@use-funnel/browser
Bug description
I think this is a bug.
@use-funnel's docs recommend using @use-funnel/browser when using the next.js approuter, but
In fact, if you use @use-funnel/browser in the app router, the project cannot be built because server-side processing is not performed properly.
This issue can also be found in<EMAIL_ADDRESS>version.
The reason this problem occurs is that using the 'use client' directive when using the next.js app router does not mean that the file will never be evaluated on the server side.
In fact, next.js also analyzes files containing the use client directive during the build process, and if there is code that accesses the window object, an error occurs.
If we want to pass the use case for app router to @use-funnel/browser, I think we will have to do server-side processing.
Expected behavior
We want error-free builds.
To Reproduce
@use-funnel/browser 0.0.5
next 14.2.13
Possible Solution
I made a few modifications to this code base locally to resolve this issue.
Simply put, the problem of errors occurring during build can be solved by modifying the code so that it does not directly access the window object.
Because this is exactly the code that is causing the problem.
export const useFunnel = createUseFunnel(({ id, initialState }) => {
  const [location, setLocation] = useState(() => ({
    search: window.location.search,
  }));
  const [state, setState] = useState(() => ({
    ...window.history.state,
  }));

This code raises an error in an environment where the window object does not exist.
So, you can modify it like this:
  const [location, setLocation] = useState({ search: '' });
  const [state, setState] = useState<any>({});

  useEffect(() => {
    if (typeof window !== 'undefined') {
      setLocation({ search: window.location?.search ?? '' });
      setState(window.history?.state ?? {});

      const handlePopState = (event: PopStateEvent) => {
        setLocation({ search: window.location?.search ?? '' });
        setState(event?.state ?? {});
      };

      window.addEventListener('popstate', handlePopState);
      return () => {
        window.removeEventListener('popstate', handlePopState);
      };
    }
  }, []);

This code is buildable because it does not access the window object on the server side and only reflects the state through useEffect on the client side, and can also avoid the Text content does not match server-rendered HTML error.
However, there are user experience issues with this approach.
Since the initial value of the server is first rendered and updated according to the current position through useEffect, if it is not initialStep, initiailStep is shown first and then the UI blinks as the desired step is rendered.
What's even more disappointing is that this approach has the potential to affect use cases that don't use app-router.
So I think there are two options.

Create a new adapter for app-router, place a dependency on next, and create a package that uses hooks provided by next.js, such as useSearchParams.

Modify the @use-funnel/browser package to take server side into consideration.

In my opinion, if there is a way to solve the problem of UI flickering when @use-funnel/browser properly supports the server-side environment while also properly supporting the server-side environment, that would be the best method.
Alternatively, creating an adapter for app-router seems attractive.
Do you have any ideas?
etc.
Or there is another way: Using dynamic in next.js ensures that it will always run only on the client, thus solving UI flickering issues and build issues.
However, this method requires more knowledge from the user.
import dynamic from "next/dynamic";
const Example = dynamic(() => import('../src/funnel'))

thank you!

Wow! I thought when using 'use client' directive, should window.* commands not evaluated at server side. but it is incorrect.
I think we should add isServer condition, and using like this.
const isServer = typeof window === 'undefined';
const [location, setLocation] = useState(() => ({
  search: isServer ? '' : window.location.search,
}));
const [state, setState] = useState(() => ({
  ...isServer ? {} : window.history.state,
}));

This can be not rerender at first render compared by useEffect solution.

That solution creates a hydration error in non-initial cases.
The server always returns the initial value, but the render actually attempted by the client produces different results depending on the window object, so the results of server rendering and client rendering are different.
Therefore, to avoid hydration errors, we had to handle side effects in useEffect.

oh i doesn't understand about next.js app router build and 'use client'.
You solution is right. it should be inside in effect by only using client.

I will use useLayoutEffect to solve this solution to avoid flikering!

I will use useLayoutEffect to solve this solution to avoid flikering!

I also thought of that method and tried using layoutEffect, but the flickering was still there.
It is difficult to explain the reasons for this, but the phenomenon can be identified.
Test it in your app router using the simple code snippet below:
export default function Home() {
  const state = useExample()
  return (
    <div>
      {state}
    </div>
  );
}

const useExample = () => {
  const [state,setState] = useState('default state')
  useLayoutEffect(() => {
    setState('layout state')
  } , [])
  return state
}

If you run this code in the app-router environment, the layout state will blink after the default state.
When I tested it, useFunnel was the same.
The only reliable way to eliminate flickering that I have found so far is using  useState(() => ) with next dynamic
Server-side processing seems difficult. What do you think?

Thats right. it should be add documention with using @use-funnel/browser and next.js app router, or add a new package about @use-funnel/next-app-router

If we want to add new packages, we need to be able to add an array of funnel states to history.state. However, we need to find a way to access history.state in the next.js app router safely from the server build.
Like: https://github.com/toss/use-funnel/blob/main/packages/browser/src/index.ts#L36-L40

Or, your solution  of #63 can be a good idea (using suspense about ready for using history.state)

Or, your solution of #63 can be a good idea (using suspense about ready for using history.state)

Unfortunately, the suggestion in #63 only works with pages routers.
This is because the app router and pages router use different router instances.
If using history.state is so important we should probably create our own.
An implementation like 'useHistory' that triggers suspense instead of producing a blink without causing a hydration missmatch.

I've tried several simple methods, but I haven't found a way to implement all of these requirements yet.
next.js's useSearchParams seemed to take the approach of checking whether the above requirements are a server by checking whether a specific instance within next.js exists only on the server, and then skipping pre-rendering by raising an error if it is a server.
next.js useSearchParams implementation | bailout-to-client-rendering.ts
adopt this approach, i can skip rendering on the server and always access the window object on the client.
Instead, there was no way to ignore server errors.
Maybe I'm just stuck with the next.js implementation and not being imaginative.
Do you have any ideas?

After discussing the refresh implementation of @use-funnel/next, we are considering supporting both history.state and querystrings at the same time. This is likely to be implemented similarly for @use-funnel/next-app-router in the future.
Currently, @use-funnel/next has the funnel state history in history.state and an index to the current history in a query string. However, there is an issue with losing the funnel staff history after a refresh.
We are looking to improve this to store the current staff and context in a query string, and only store the "old" history in history.state (#69). Some features (overlays) that use the old history will be unavailable on refresh, but at least we can guarantee the state for the current history.
After some more testing, I'm going to merge that PR. Feedback on that PR is also welcome!

의 새로 고침 구현을 논의한 후 @use-funnel/next, 우리는 history.state동시에 와 쿼리 문자열을 모두 지원하는 것을 고려하고 있습니다. 이는 @use-funnel/next-app-router미래에도 비슷하게 구현될 가능성이 높습니다.
현재, (next.js 페이지 라우터에서 트릭을 사용하여 ) @use-funnel/next퍼널 상태 기록이 있고 쿼리 문자열에 현재 기록에 대한 인덱스가 있습니다. 그러나 새로 고침 후 퍼널 스태프 기록을 잃는 문제가 있습니다.history.state``asPath
우리는 이것을 개선하여 현재 직원과 컨텍스트를 쿼리 문자열에 저장하고, "이전" 기록만 history.state( #69 )에 저장하려고 합니다. 이전 기록을 사용하는 일부 기능(오버레이)은 새로 고침 시 사용할 수 없지만, 최소한 현재 기록의 상태는 보장할 수 있습니다.
몇 가지 테스트를 더 거친 후, 그 PR을 병합할 겁니다. 그 PR에 대한 피드백도 환영합니다!

@use-funnel/next I understand what trick it was implemented with.
So it was different from what you wanted.
I think storing the context in the query string is a really good idea.

After discussing the refresh implementation of @use-funnel/next, we are considering supporting both history.state and querystrings at the same time. This is likely to be implemented similarly for @use-funnel/next-app-router in the future.
Currently, @use-funnel/next has the funnel state history in history.state(in next.js page router, using asPath trick) and an index to the current history in a query string. However, there is an issue with losing the funnel history after a refresh.
We are looking to improve this to store the current step and context in a query string, and only store the "old" history in history.state (#69). Some features (overlays) that use the old history will be unavailable on refresh, but at least we can guarantee the state for the current history.
After some more testing, I'm going to merge that PR. Feedback on that PR is also welcome!

Hi!
I'm testing various ideas to implement the next-app-router adapter.
I have a few questions about the implementation. Why did you have to implement it with history.state?
I guess queryString is probably not a suitable storage for storing complex objects or arrays, so the contexts were saved in history.state.
Is this correct? If it's true, I think we need to think a little more about the implementation, so I'm asking!

After discussing the refresh implementation of @use-funnel/next, we are considering supporting both history.state and querystrings at the same time. This is likely to be implemented similarly for @use-funnel/next-app-router in the future.
Currently, @use-funnel/next has the funnel state history in history.state(in next.js page router, using asPath trick) and an index to the current history in a query string. However, there is an issue with losing the funnel history after a refresh.
We are looking to improve this to store the current step and context in a query string, and only store the "old" history in history.state (#69). Some features (overlays) that use the old history will be unavailable on refresh, but at least we can guarantee the state for the current history.
After some more testing, I'm going to merge that PR. Feedback on that PR is also welcome!

It seems like a good idea to keep only previous records in history.state!
I haven't tried it yet, but I think this method might be of great help in creating an app router adapter.
I'm currently writing code for an app router adapter.
I haven't yet solved the issue of flickering caused by history.state, but I'm thinking of trying a method of moving only the current context to the query string.
I'll be back with the code thank you!

This issue is fix at<EMAIL_ADDRESS>Thanks for your issue and will prepare to @use-funnel/next-app-router soon


admob_utils.py need update

I found code
    @redirect_uri.setter
    def redirect_uri(self, value):
        if value in _OOB_REDIRECT_URIS:
            warnings.warn(
                "'{}' is an OOB redirect URI. The OAuth out-of-band (OOB) flow is deprecated. "
                "New clients will be unable to use this flow starting on Feb 28, 2022. "
                "This flow will be deprecated for all clients on Oct 3, 2022. "
                "Migrate to an alternative flow. "
                "See https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html?m=1#disallowed-oob".format(
                    value
                ),
                DeprecationWarning,
            )
        self.oauth2session.redirect_uri = value

in https://github.com/googleapis/google-auth-library-python-oauthlib/blob/main/google_auth_oauthlib/flow.py
and  The notice in https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html?m=1#disallowed-oob
and the new generated client_secrets.json don't contain urn:ietf:wg:oauth:2.0:oob any more.
So we need a new way to do the admob auth.

we must use InstalledAppFlow.run_local_server instead


Add esy.sh dependencies

Description

This adds the esy lockfile and build dir to the vendor list.
Checklist:

[x] I am adding new or changing current functionality

[ ] I have added or updated the tests for the new or changed functionality.

Linguist doesn't acknowledge the .lock extension, so adding .esy.lock as a vendored file is redundant. Instead, we mark such files as generated, which is handled in lib/linguist/generated.rb.
Could you give a link that explains more about _esy build directories?

I only see composer.lock, Cargo.lock, Pipfile.lock and (Gopkg|glide)\.lock also side note.
https://github.com/github/linguist/blob/50005d6e607d956479f03e378c9c54aed03e7a6e/lib/linguist/generated.rb#L364 we have the two !! we didn't have it here https://github.com/github/linguist/blob/50005d6e607d956479f03e378c9c54aed03e7a6e/lib/linguist/generated.rb#L430
for _esy The better link I have found is https://esy.sh/docs/en/how-it-works.html#local-build-store
but it deal only with some specific folder. Maybe @andreypopp can give you more information/link because it is the main developper (2084 commits vs <113 commits for others)

_esy should not be committed avd is ignored in all "official" templates.
esy.lock is a directory with a bunch of files that describes the current snapshot including overrides of some packages. When something is updated there is often a huge amount of changed files here.

If we should add test I want to add theese one https://gist.github.com/Et7f3/c36059408ffb2f648618e798b54d1d6f


SR-4842: Allow JSONSerialization to serialize optionals without requi…

…ring NSNull()
Since the test cases works on Darwin Foundation it seems reasonable to make them work on open-source Foundation.

@swift-ci test this please

@swift-ci please test

@kevints can you make the tweak requested by @parkera? It would be nice to get this bugfix into Swift 4!

@swift-ci please test

@swift-ci please test

@kevints
Test Case 'TestNSJSONSerialization.test_isValidJSONObjectFalse' started at 2017-07-26 09:16:04.489
TestFoundation/TestNSJSONSerialization.swift:924: error: TestNSJSONSerialization.test_isValidJSONObjectFalse : XCTAssertFalse failed -
Test Case 'TestNSJSONSerialization.test_isValidJSONObjectFalse' failed (0.0 seconds)

@swift-ci please test

@swift-ci please test

Test Case 'TestNSJSONSerialization.test_isValidJSONObjectTrue' started at 2017-07-27 06:38:12.967
TestFoundation/TestNSJSONSerialization.swift:883: error: TestNSJSONSerialization.test_isValidJSONObjectTrue : XCTAssertTrue failed -
Test Case 'TestNSJSONSerialization.test_isValidJSONObjectTrue' failed (0.0 seconds)

@alblue updated, can you kick off the CI bot again

@swift-ci please test

@swift-ci please test

@parkera This PR has changed a bit since you last looked - it's simpler now. What do you think? AFAICT it's fine.

Looks good to me; also cc @itaiferber

LGTM


[HYP-152]create email form to send when click email at footer

Jira: HYP-152

when in mobile view change to text "Click to send email"

– [x] Artifacts Added

good


Warning in scenarios where SampleState is ignored

On some targets it is not possible to allow the separation of a texture from a sampler. The HLSL language supports SamplerState that allows a texture to be used with multiple sampler states. When using a target that doesn't allow separation we in effect ignore SamplerState. Ignoring is perhaps fine assuming there is only one SampleState ever used with the texture. The assumption being the programmer knows for that target the texture is in effect a combined texture sampler.
In the scenario when there is more than one SamplerState being used with a texture, it would be useful to at least give a warning that, that is indeed the scenario.
This could happen when the target is known. Another path might be to have a "compatibility" mode which provides a lowest common denominator compatibility.

Move this to bankrupcy for now, unless we have a user request to bring it back into priority.


Add Pulumi Package Schema documentation

Fixes pulumi/docs#5997.

@cnunciato A couple of the tables are overflowing the main section - do you know of a way to tell Hugo to force them not to overflow (perhaps requiring wordbreaks)?

@lukehoban not at present, but even so, forcing the text to wrap would still make some of these pretty hard to read.
Since these are all property lists, though, what about using the same lists we use in the resource docs? I've been meaning to make it easier to write these lists by hand, so I just threw together a couple of shortcodes as a POC that would probably work. Something like:
{{% property-list %}}

{{% property-list-item name="name" type="string" required="yes" %}}
Name is the unqualified name of the package (e.g. "aws", "azure", "gcp", "kubernetes", "random").
{{% /property-list-item %}}

{{% property-list-item name="meta" type="[`Metadata`](#metadata)" required="no" %}}
Meta contains information for the importer about this package.
{{% /property-list-item %}}

{{% property-list-item name="packageImportAliases" type="map[string]" required="No" %}}
Map from package name -> package alias (e.g. `{ "github.com/pulumi/pulumi-kubernetes/sdk/go/kubernetes/flowcontrol/v1alpha1": "flowcontrolv1alpha1" }`).
{{% /property-list-item %}}

{{% /property-list %}}

... would get you a list that that looked like

What do you think? I could push a commit to add the shortcodes, or maybe a separate PR first.

As a follow-up change, it would be useful to show some examples of how to specify more complex types like arrays, maps, and enums, and how to reference resources/types (internal and external).

Good suggestion - I replaced the example in the intro with a slightly more "real" one which uses most of these to some limited degree.  It might still be nice to have examples that go into more detail in each individual section - but I think this is good for now.

@lukehoban not at present, but even so, forcing the text to wrap would still make some of these pretty hard to read.

Got it.  I went ahead and just manually inserted spaces in the two places that were problematic, and that avoids the overflow, and is sufficiently readable for now.

Since these are all property lists, though, what about using the same lists we use in the resource docs?

Love it.  I don't think I'll block on this - but if we do add shortcodes to reuse this UX, we could follow-up by migrating this over.  Note though that this content is manually maintained, so not sure how "usable" the shortcodes will be for manually maintained content at this scale (vs. a table which is relatively simple).  If we can make this (nearly) as easy as managing a table (or can eventually autogenerate this content from the Go struct types it was manually ported from), then this would definitely be the best way to go.


Update RFC numbering guidance to use PR number

Hi all,
After some discussion, we'd like to propose that RFCs are numbered according to the GitHub PR number. This follows the idea of documenting those RFCs which are rejected. While it adds an extra step to the initial RFC posting, it simplifies all future references by not allocating two different IDs (PR number and RFC number). It also makes it very easy to find the discussion associated with a given PR when viewing it outside of a PR (e.g. through browsing the tvm-rfcs repo) and makes for one less link to update.
This also has precedent in the rust community.
Sending this PR as a proposal and would like for everyone to discuss/approve/reject this idea here.
@hogepodge @apache/tvm-committers @tqchen
-Andrew

I liked the idea. It follows the common practice in previous communities and simplifies the RFC process.

Yes we can udpdate the merged RFC, the only one I am aware of is autoTIR RFC and perhaps @junrushao1994 can chime in

let us wait for another two days and if there is no objection, we can merge it in

cc @junrushao1994 would be great if you can send a followup PR to rename the autoTIR RFC, and update links

Thanks for the update. I'm glad to see that we're refining the RFC process as it goes into production.

Will apply the rule to meta schedule RFC this weekend


If Items Absolutely Positioned, Tether Gets Confused And Moves To A Negative Y Position

Running into the issue of Tether moving elements to a negative Y position if everything on the page is positioned absolutely (height of document is 0). This is happening on Chrome. Sometimes works fine on Firefox.
I am currently using a workaround by adding a height of 100% for HTML document.

+1

+1
See related issue here: https://github.com/bootstrap-vue/bootstrap-vue/issues/193


export PROMPTFOO_CACHE_ENABLED=false not disabling cache

Running:
> export PROMPTFOO_CACHE_ENABLED=true
> promptfoo eval
...  # Takes < 1 sec
> export PROMPTFOO_CACHE_ENABLED=false
> promptfoo eval
...  # Takes < 1 sec
> rm -r ~/.promptfoo/cache
> promptfoo eval
...  # Takes >> 1 sec

I think this means export PROMPTFOO_CACHE_ENABLED=false doesn't get respected.

Should be fixed with 63eebeee45bcd1266c9d09ec7a78b670cd6c3be0

The original Boolean(process.env.PROMPTFOO_CACHE_ENABLED), what was the value for PROMPTFOO_CACHE_ENABLED supposed to be?  I guess just 1?
And looks like your change will work, thanks

Any non-empty string is truthy, so it didn't behave correctly without parsing.  Thanks for catching this!


Role-create edit page: This page displays checkboxes without calling the checkbox component. It's not DRY. So when I modify the component, I have to think about doing it in the component AND here.

What is annoying is that when you make a modification of the component, you expect to see it in this view. We waste time to understand why the modification is not taken into account.

@brunobuddy Don't you think this issue is relevant and should be reopened ?


How to extract and apply CSS styles when using in shadow Dom?

Hey, first of all thanks a lot for this awesome piece of software :+1:
Is there any way to extract the generated CSS so I can add it to the shadow Dom?
Leva is working fine for me, except when it's placed in a shadow Dom, then it looses all styles, see screenshot:

I tried the following in my app index.tsx, but it seems only some basic leva css is extracted like this
// stitches styles, because leva
const stitchesRoot = document.createElement('style')
stitchesRoot.setAttribute('data-why', 'because-leva')
const { getCssText } = createStitches()
stitchesRoot.innerHTML = getCssText()
shadowContainer.appendChild(stitchesRoot)

Don't think we can do much about this, you'd have to look for solutions within stitches repo... stitchesjs/stitches#534
If we ever hit 1.0 with Leva I think we'll use a more solid library. Stitches is awesome but has too many cons I'm afraid. Vanilla extract might be a better fit.

Ok, thanks for quick reply!

Have this problem as well. It is also happening with MaterialUI which can be fixed using workaround.
Maybe it would work here too.


feat: replace_global_define optional chain

#7433  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Nov 23, 10:15 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
Nov 23, 10:15 AM EST: A user added this pull request to the Graphite merge queue.


Biased color at early stage of training / blurry foreground when fullly trained

Kudos for the work!
When training the 360 dataset with the default 360_glo config using 4GPUs, I noticed two problems with the result:

During early stages of the training, the test image of foreground object shows weird color,  For example the bicycle scene (I can't upload images...): The frame of the bicycle is went from red to gray to blue to white (still a bit blue)

When fully trained, the objects (chair and bicycle) are still blurry compared with the background, and both the chair and bicycle have a blue color shade..d

Could it be the view-dependent MLP?
Thanks in advance!

@jingyibo123 I think this may results from the glo_vec proposed in paper which is used to scale and bias the bottleneck feature. If you get a weird result, you can try the default 360.gin instead.

Indeed, thanks!


add ever driver and docker test

I resolve the conflict via Github WEB GUI. Just check if indentation is correct


Broken stop limit pagination and child jobs demo

https://keboola.atlassian.net/browse/COM-283
When the child jobs are added to resource with stopLimit pagination, pagination stops on 2nd page.
Without child jobs or with child jobs and recursion filter which returns 0 results:
Returns three pages as expected.

With child jobs or with recursion filter which returns 0 results :
Stops after 2nd page.

update docs https://github.com/keboola/developers-docs/pull/130


Update for the revision 13

The current implementation has been prepared for revision 3 and the current is revision 13. Check what changes came and apply them.

Corrected. The actual revision is rev7. Revision 13 is for version 2.0, not for 2.1, but made four years after 2.1 rev 3.

During the parser creation process the model has been updated.


Improve build on Linux without Docker

Update the build script to move the library into place for Linux x86 and x64 even when Docker is not available. Changes one of the Travis jobs to test this path.

Pull Request Test Coverage Report for Build 37

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.142%

Totals

Change from base Build 33:
0.0%

Covered Lines:
317

Relevant Lines:
323

💛  - Coveralls


Dropping rows into a separate component

Hi,
from what I can see in documentation, dnd is meant to be within a reactabular table.
If I want to drop into an external custom react-dnd dropzone (of a custom, non-reactabular component), can I do that fairly easily with reactabular?
I have started looking at the reactabular-dnd source code to see what it exposes that I could reuse. For example I see it exposes a row id. Therefore, one way would be that drop zone would be receiving that row id and then I would extract colomns from my core data source based on that id, as opposed to them being passed along as props in dragzone.
Are there better/quicker/cleaner ways to achieve what I am trying to do? My objective is to reuse as much readily available functionality as possible and rewrite as little as possible.
Thank you

This is a similar problem as dragging rows between tables.
I don't see why a custom drop zone wouldn't work as long as you have a DragDropContext on high enough level (wraps both table and the zone). I imagine a slight amount of custom logic may be required on the table side to deal with the row removal.
The code is modular so I imagine it should be fairly easy to do the custom functionality. I can also add flexibility there as needed (better as PRs, though).


GDScript: Highlight code region comments

Also optimizes color region type checking by using an enum instead of string comparison.

How does this look with the light mode theme?

How does this look with the light mode theme?

Thanks!


[Form] - Unreadable Label of checked toggle on Inverted form

Steps to Reproduce
Put a toggle checkbox inside an inverted form, check it.
Expected
The label should not be black (since the background is black)
Result
The label is black because of
.ui.toggle.checkbox input:checked~label {
    color: rgba(0,0,0,.95)!important;
}

So, maybe, do not use important?
Testcase
http://jsfiddle.net/6xq1jc1z/1/

Sorry @stale, but this is an important bug.

Fomantic-UI supports inverted toggle checkbox since 2.4.4
https://fomantic-ui.com/modules/checkbox.html#inverted
See your adjusted jsfiddle here http://jsfiddle.net/py51scbL/


Add FreeRTOS

Eventually I would like to add the BUILD.bazel and MODULE.bazel files directly to FreeRTOS. Started the conversation with maintainers here: https://forums.freertos.org/t/bazel-build-file-for-the-freertos-kernel/20963

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (freertos) have been updated in this PR. Please review the changes.


Modded dimensions aren't loaded properly on creating the world

Minecraft version
1.19.2
LibX version
1.19.2-4.2.6
Skyblock Builder version
1.19.1-4.2.0
Forge version
43.1.33
The latest.log file
unnecessary
Issue description
Dimensions by other mods are likely not loaded with Skyblock world preset. Because of this, these dimensions can't be visited or used as starting dimension. However, after re-loading the world, the dimensions are back in.
Steps to reproduce

Add a mod which adds new dimensions (e.g. Cosmopolis runtimeOnly curse.mod(556904, 4016840)) to dependencies.
Run the runClient task.
Create a new world with world preset Skyblock.
Try to type in /execute in  and see that the dimensions are not listed. Manually typing doesn't help, too.

Other information
While trying to find the cause, I found out that the datapack dimensions are added in CreateWorldScreen#tryApplyNewDataPacks. It seems like the Skyblock world preset isn't loaded at the time this is being called.

https://github.com/MelanX/SkyblockBuilder/commit/640455a16fccbd560f40274df6c4cf216580a859


Compatibility layer for HTTPretty

All the commits related to #60.

Coverage decreased (-0.07%) to 99.117% when pulling<PHONE_NUMBER>34c4f1fb122df18fa49f87c9886fbb on httpretty into c5d3cfe7a267c6708c54d4628f9b890db56c2951 on master.

Coverage decreased (-0.07%) to 99.117% when pulling 9bc4410de43a7a0cb167a6a37c591404ad006184 on httpretty into c5d3cfe7a267c6708c54d4628f9b890db56c2951 on master.

Coverage decreased (-0.07%) to 99.117% when pulling 9bc4410de43a7a0cb167a6a37c591404ad006184 on httpretty into c5d3cfe7a267c6708c54d4628f9b890db56c2951 on master.

Coverage decreased (-0.06%) to 99.12% when pulling 768be33aa2b174c8800f008a115c37fa963986c6 on httpretty into c5d3cfe7a267c6708c54d4628f9b890db56c2951 on master.

Coverage decreased (-0.06%) to 99.12% when pulling 768be33aa2b174c8800f008a115c37fa963986c6 on httpretty into c5d3cfe7a267c6708c54d4628f9b890db56c2951 on master.

Coverage decreased (-0.06%) to 99.12% when pulling 0657ddc7024dd38d71f96432d003c5a26b67fb80 on httpretty into c5d3cfe7a267c6708c54d4628f9b890db56c2951 on master.

Coverage decreased (-0.06%) to 99.12% when pulling 8201dcaafae7758975ffd12cf1aa3792b8bc7f99 on httpretty into c5d3cfe7a267c6708c54d4628f9b890db56c2951 on master.

Coverage decreased (-0.06%) to 99.12% when pulling 73f8dea1042e216cae6b24cd7d87596cca686976 on httpretty into c5d3cfe7a267c6708c54d4628f9b890db56c2951 on master.


add a new project to Shopify open source

The partner team wants to add the following project repo:
https://github.com/MLH/mlh-localhost-shopify-graphql
to the Shopify open source page listing:
https://shopify.github.io/
Legal has approved cloning/copying  this repo.

I would like to work on this issue.

Closing this, as the project in this issue isn't directly affiliated with Shopify.


Issue:  module' object has no attribute 'libusb_get_port_numbers'

when exec below command on MAC (high Sierra), it always report no attribute libusb_get_port_numbers issue.
$ python adb.zip  list /sdcard/
Traceback (most recent call last):
File "/usr/local/Cellar/python/2.7.12_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"main", fname, loader, pkg_name)
File "/usr/local/Cellar/python/2.7.12_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "adb.zip/main.py", line 178, in
File "adb.zip/main.py", line 174, in main
File "adb.zip/adb/common_cli.py", line 150, in StartCli
File "adb.zip/adb/adb_commands.py", line 75, in ConnectDevice
File "adb.zip/adb/common.py", line 212, in FindAndOpen
File "adb.zip/adb/common.py", line 93, in Open
File "adb.zip/adb/common.py", line 138, in port_path
File "/usr/local/lib/python2.7/site-packages/usb1.py", line 1510, in getPortNumberList
result = libusb1.libusb_get_port_numbers(self.device_p, port_list,
AttributeError: 'module' object has no attribute 'libusb_get_port_numbers'

That's a libusb version issue. The version of libusb1-dev installed in your system is too old, it needs to be 1.0.16+


[Backport 2.x] Removing extra protobuf notice file

Description
Backport of #10114 to 2.x
Related Issues
Resolves #[Issue number to be closed when this PR is merged]

Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[ ] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

❌ Gradle check result for 43d5c4b: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

https://github.com/opensearch-project/OpenSearch/issues/13600


wikibase: Alert the user when they do not provide an edit summary

Closes #6306
Changes proposed in this pull request:

Unfortunately, i couldn't configure the request for a working "required" tag inside the HTML code.
Directly implementing the "required" tag in the appropriate HTML "input" tag did not work, since the form isn't directly submitted from the HTML code, but from a JavaScript code that doesn't recognize the "required" tag.
Although, as i noticed in different parts off the project, problems as such are dealt with the pop-up window that follows:

-(The previous message pops-up when the user clicks "next" without choosing a file in the "create project" section).
-What this PR changes, is instead of focusing to the box next to "summary", it pops-up the following message:

-(This validation message was already implemented inside the code but never reached).

Absolutely, I understand your concerns. I will close this pull request for now, and if I manage to address these points, I'll open a new one.


such error:  [!]This script must be run as root

Empire Version
newest
OS Information (Linux flavor, Python version)
win7
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
iwant it run in win7,
bash is allowed,
but still except such error:  [!]This script must be run as root
PS G:\PenetrationTools\T00Ls\提权exp\powershell\Empire-master\setup> bash ./install.sh
[!]This script must be run as root
Screenshot of error, embedded text output, or Pastebin link to the error

Any additional information

The answer is somewhere in the screenshot you posted. It's self-explanatory.

nonono , actrually.  i had run cmd.exe or bash.exe as administrator alerady ...
it's still such error
this is the reason i want to ask my dear xorrior

As far as I understand, you want to install Empire on Windows via bash on Windows ? I don't think Empire server is compatible with such setup. Empire (server side) is only compatible with Linux/MacOS.

Thanks for ur relply,  and then I will trying to setup in my kali ...


Write a Python program to convert time from 12-hour to 24-hour format

Description
Write a Python program to convert time from 12-hour to 24-hour format
Input  : 12:05:45PM
Output : 12:05:45

How to contribute

Save the solution in program/convert-time-from-12-hour-to-24-hour-format.py file
Add convert-time-from-12-hour-to-24-hour-format.py file in convert-time-from-12-hour-to-24-hour-format folder

!assign


When I configured the Prometheus receiver, the fields were not differentiated.

I have configured the otel collector with Prometheus as the receiver and Data Prepper as the exporter.
So, while I can retrieve data from the OpenSearch dashboard, it appears that all data is grouped under the name field.
To create a dashboard, I believe the fields need to be distinguished.
What additional settings should I add to the otel collector configmap to differentiate fields?
I am attaching the yaml file of the otel collector configmap that I have written. Thank you.
[otel collector configmap yaml]
data:
relay: |
exporters:
otlp/metrics:
endpoint: data-prepper-headless.opensearch.svc:21891
tls:
insecure: true
extensions:
health_check:
endpoint: ${env:K8S_POD_IP}:13133
processors:
memory_limiter:
check_interval: 5s
limit_percentage: 80
spike_limit_percentage: 25
receivers:
prometheus/internal:
config:
scrape_configs:
- job_name: apps
kubernetes_sd_configs:
- role: pod
selectors:
- role: pod
# only scrape data from pods running on the same node as collector
field: "spec.nodeName=${NODE_NAME}"
relabel_configs:
# scrape pods annotated with "prometheus.io/scrape: true"
- source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape]
regex: "true"
action: keep
# read the port from "prometheus.io/port: " annotation and update scraping address accordingly
- source_labels: [address, __meta_kubernetes_pod_annotation_prometheus_io_port]
action: replace
target_label: address
regex: ([^:]+)(?::\d+)?;(\d+)
# escaped $1:$2
replacement: $$1:$$2
- source_labels: [__meta_kubernetes_namespace]
action: replace
target_label: kubernetes_namespace
- source_labels: [__meta_kubernetes_pod_name]
action: replace
target_label: kubernetes_pod_name
- job_name: 'otel-collector'
scrape_interval: 5s
static_configs:
- targets: ['prometheus-k8s.monitoring.svc:9090']
metric_relabel_configs:
- source_labels: [ name ]
regex: '.grpc_io.'
action: drop
otlp:
protocols:
grpc:
endpoint: ${env:K8S_POD_IP}:4317
http:
endpoint: ${env:K8S_POD_IP}:4318
service:
extensions:
- health_check
pipelines:
metrics/internal:
exporters:
- otlp/metrics
processors:
- memory_limiter
receivers:
- prometheus/internal
- otlp

Please provide your data prepper config yaml


New responsive input does not respect Alpha

I love the new responsive color data tag for input, but I can't use it quite yet because it doesn't respect alpha which looks very strange and silly. See the top element here:

I'll definitely use it if/once alpha is incorporated though. I may be able to get rid of my "div.color-splash" hack entirely with it, which would be awesome. I may keep it though to show the previous color, and just expand the input button itself when closed so that it's clearer to the user where they can click to open the color picker.

turned out to be a custom-hotbar sided css issue


[1.1.x] skip ceres tests if not installed | Fix LDAP email address | Django 2 support | fix typo: matric -> metric in feeding-carbon.rst | Fixing typo in docs | improve performance of keepLastValue | expand k

Backports the following commits to 1.1.x:

skip ceres tests if not installed (#2276)
Fix LDAP email address (#2277)
Django 2 support (#2278)
fix typo: matric -> metric in feeding-carbon.rst (#2281)
Fixing typo in docs (#2284)
improve performance of keepLastValue (#2285)
expand keepLastValue test (#2285)
hashing: bisect fix for py3 (#2291)
handle highest/lowest thresholds specified as numeric strings (#2294)
Generate error when find query is empty (#2295)

Part 1 of 1.1.4 backport. Sorry, it's not fit in one change because of Github API limitation :)

Codecov Report

Merging #2343 into 1.1.x will decrease coverage by <.01%.
The diff coverage is 83.33%.

@@            Coverage Diff            @@
##            1.1.x   #2343      +/-   ##
=========================================
- Coverage   79.61%   79.6%   -0.01%
=========================================
  Files          85      85
  Lines        8840    8847       +7
  Branches     1891    1892       +1
=========================================
+ Hits         7038    7043       +5
- Misses       1543    1544       +1
- Partials      259     260       +1

Impacted Files
Coverage Δ

webapp/graphite/account/ldapBackend.py
0% <0%> (ø)
:arrow_up:

webapp/graphite/metrics/views.py
86% <0%> (-0.72%)
:arrow_down:

webapp/graphite/render/hashing.py
93.39% <100%> (ø)
:arrow_up:

webapp/graphite/user_util.py
96.15% <100%> (+0.91%)
:arrow_up:

webapp/graphite/app_settings.py
90.9% <100%> (ø)
:arrow_up:

webapp/graphite/dashboard/views.py
99.25% <100%> (ø)
:arrow_up:

webapp/graphite/render/functions.py
96.22% <100%> (-0.01%)
:arrow_down:

webapp/graphite/account/views.py
30.76% <50%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

will merge that, because part 3 is not mergeable until I merge this to 1.1.x


Create Gitlab "Releases" in CI pipeline

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/181
Originally created by @aaronsteers on 2021-08-04 23:15:58

We currently create Gitlab tags for each SDK release but we do not automatically create a Release due to #129

View 2 previous comments from the original issue on GitLab

Not relevant anymore


About the choice of initial point

Hello, this paper uses topleft's initial point selection method, I would like to ask where this method is reflected in the code

Hi, yes we do this when preparing the dataset.
https://github.com/amazon-science/polygon-transformer/blob/69fc728b2ec6a2b3595ec34db64074badcb19151/data/poly_utils.py#L68


test_heal is flaky

Log:
=================================== FAILURES ===================================
__________________________________ test_heal ___________________________________

pool = MAPDL Pool with 3 active instances

    @skip_if_not_local
    def test_heal(pool):
        pool_sz = len(pool)
>       pool[0].exit()
E       AttributeError: 'NoneType' object has no attribute 'exit'

tests/test_pool.py:68: AttributeError
---------------------------- Captured stderr setup -----------------------------

Again I'm starting to see this test and test_empty_mesh failing a lot.
https://github.com/ansys/pymapdl/actions/runs/5878340721/job/15940214006?pr=2207#step:10:1965


Missing Microflow aspose image size pixels

https://github.com/mendix/docs/blob/development/refguide/java-actions.md line 81
"Expose as Microflow action" there is no suggestion for the icon size.

I Andries, do you have a suggestion for this?

No. Don't know. I was trying to find out from the documentation ;)
On 16 Jun 2017 15:53, "Adam Dupaski"<EMAIL_ADDRESS>wrote:

I Andries, do you have a suggestion for this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mendix/docs/issues/488#issuecomment-309031788, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGacjcsK9m9eefB5Hj453w2Ci_djgEXZks5sEojEgaJpZM4N8X0u
.

Documentation updated: https://docs.mendix.com/refguide/java-actions#expose-as-microflow-action
Closing this issue.


TPS-358 - Pivot Table Time Zone

Resolves an issue where PivotTable dates were displaying differently depending on the user's timezone (eg: not showing 10/29 for users in Pacific Time despite data coming in from 10/29 UTC).
Fixes TPS-358
Acceptance Criteria
It's a little complicated to replicate this - you need to create a pivot table that contains dates, set your granularity to day, then manually change your computer over to a different timezone that's behind UTC, and then test against data that exists for the current UTC date. I've done this and can confirm that the code change works. I correctly see data for 10/29 (the date of this PR) even when set to San Francisco time.
Here's a screenshot of it working - before the fix the last date in the table was 10/28. With the fix, even in Pacific time, the last date in the table is correctly showing as 10/29:

A quick note: this fixes the pivot table but may not fix issues in other components that haven't been identified yet - I didn't want to start messing with the other parts of the formatValue function without knowing what they impacted (also, since this is a customer-facing issue, I wanted to get it fixed ASAP). If we want to revisit the overall format.ts file I can do that, but I'd like to make it a separate issue.


refactor(esl-footnotes): move esl-note to esl-footnotes as part of component

move esl-note to esl-footnotes as part of component
create a promise-based version of scrollIntoView()

:tada: This PR is included in version 3.0.0-beta.15 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update rrdserver.go

Coverage remained the same at 75.556% when pulling 78d89c9886f7c4553c6c37c1cbbcb43d77ef7042 on jmgarciac:patch-1 into e1595f81c00f841c279b9b36c871806f13a21459 on doublemarket:master.

@jmgarciac Thank you for the pull request! I missed the misspellings.


Update CHANGELOG before releasing patch versions and new major version and backport changes.

Update the CHANGELOG to indicate what changes are being made in each patch version of the gem and backport applicable changes to each stable branch before releasing.

Resolved by #55


Specify more information about priority on CsUnassignedNumber page

Per @kenwith 's request in the thread for #714, a recommendation for how this could be made more clear in the documentation.

@rdbahm - this is awesome and thank you for adding the clarity. It really shows the power of an open system like GitHub where the real knowledge is from the community and experts like you who experience a particular issue and can add the knowledge you gain back into the community. It is greatly appreciated and welcome to contributor status for the content repo!


Upgrade to jOOQ 3.19.0

Switch to the latest open-source jOOQ release and to the Gradle plugin that
supports it by default.
3.19.0 includes a breaking API change related to inserting lists of records;
update the code accordingly.

Current dependencies on/for this PR:

main

PR #1574   👈

This stack of pull requests is managed by Graphite.


Search Engine Presets PR2

I had to delete my old repo so I made a new PR.

Thanks for contributing! I have a few changes that I would like to be made.
* Change the buttons to a `select` element. This will save space and make it easier to use.

* Refrain from using the `onclick` attribute; instead, inside of the `listeners.js` file, use the `change` event listener to listen for changes of the selection.

Here's an example:
<select id="settings-presets">
  <option value="">Select a preset</option>
  <option value="https://example.com"></option>
  ...
</select>

byId('settings-presets').addEventListener('change', (e) => {
  ...
});

How do I view the change you requested?

Thanks for contributing! I have a few changes that I would like to be made.
* Change the buttons to a `select` element. This will save space and make it easier to use.

* Refrain from using the `onclick` attribute; instead, inside of the `listeners.js` file, use the `change` event listener to listen for changes of the selection.

Here's an example:
<select id="settings-presets">
  <option value="">Select a preset</option>
  <option value="https://example.com"></option>
  ...
</select>

byId('settings-presets').addEventListener('change', (e) => {
  ...
});

How do I view the change you requested?

I'll just PR into your branch and fix it.

Thanks for contributing! I have a few changes that I would like to be made.
* Change the buttons to a `select` element. This will save space and make it easier to use.

* Refrain from using the `onclick` attribute; instead, inside of the `listeners.js` file, use the `change` event listener to listen for changes of the selection.

Here's an example:
<select id="settings-presets">
  <option value="">Select a preset</option>
  <option value="https://example.com"></option>
  ...
</select>

byId('settings-presets').addEventListener('change', (e) => {
  ...
});

How do I view the change you requested?

That is the change I requested.

Thanks for contributing! I have a few changes that I would like to be made.
* Change the buttons to a `select` element. This will save space and make it easier to use.

* Refrain from using the `onclick` attribute; instead, inside of the `listeners.js` file, use the `change` event listener to listen for changes of the selection.

Here's an example:
<select id="settings-presets">
  <option value="">Select a preset</option>
  <option value="https://example.com"></option>
  ...
</select>

byId('settings-presets').addEventListener('change', (e) => {
  ...
});

How do I view the change you requested?

That is the change I requested.

Okay, the changes I made don't have styling for the dropdowns. So it's in plain-html. Would you mind doing some TailWindCSS? Or do you want me to style it with normal CSS?

I can do some TailwindCSS tomorrow for you.

I can do some TailwindCSS tomorrow for you.

Thanks you, I will check with hello-smile6 to see whose code we use.

I can do some TailwindCSS tomorrow for you.

Thanks you, I will check with hello-smile6 to see whose code we use.

You mean @hello-smile6 ? :)

I can do some TailwindCSS tomorrow for you.

Thanks you, I will check with hello-smile6 to see whose code we use.

You mean @hello-smile6 ? :)

Yes, I didn't know you could mention users like that.

I can do some TailwindCSS tomorrow for you.

Thanks you, I will check with hello-smile6 to see whose code we use.

You mean @hello-smile6 ? :)

Yes, I didn't know you could mention users like that.

You can. Also, I check every comment on any PR or issue I care about.

I can do some TailwindCSS tomorrow for you.

Thanks you, I will check with hello-smile6 to see whose code we use.

You mean @hello-smile6 ? :)

Yes, I didn't know you could mention users like that.

You can. Also, I check every comment on any PR or issue I care about.

Okay, whose code should we use?

I can do some TailwindCSS tomorrow for you.

Thanks you, I will check with hello-smile6 to see whose code we use.

You mean @hello-smile6 ? :)

Yes, I didn't know you could mention users like that.

You can. Also, I check every comment on any PR or issue I care about.

Okay, whose code should we use?

Use mine, but rewrite it to support your dropdown version.

I can do some TailwindCSS tomorrow for you.

Thanks you, I will check with hello-smile6 to see whose code we use.

You mean @hello-smile6 ? :)

Yes, I didn't know you could mention users like that.

You can. Also, I check every comment on any PR or issue I care about.

Okay, whose code should we use?

Use mine, but rewrite it to support your dropdown version.

Okay, I'll add the dropdowns to the code at some point.

Finished the Tailwind.

Added changes with the dropdowns. Anything else to change?

Do you mind replacing swisscows with Startpage?

Why did you change the styling I did? You removed the flexbox.

I think this would be easier for me just to do it locally and push it to v2.2.4.

Okay then. Also I tried to add Startpage, the problem is that the search results don't show up in the URL.

Okay then. Also I tried to add Startpage, the problem is that the search results don't show up in the URL.

You use the URL https://startpage.com/sp/search?q=<query>


Improve search for settings

When searching for settings in the UI settings page, I believe results are sorted alphabetically, which makes users have to scroll down a lot in order to find the most relevant result. For example, if you have the Python extension installed and look for "pylint", you're going to have to scroll down through bandit, flake8, general linting, mypy, pep8, prospector, pydocstyle and pylama configuration options until you reach pylint settings. It's a LOT of scrolling:

Most of users seem to be configuring their experience through settings.json, but my understanding is that there's no plan to enhance the experience that way. So I believe there really should be an improvement of the UI settings search experience.

Dupe of https://github.com/microsoft/vscode/issues/187959


[Bug report] Performance issues with large number of images in the library.

Version
3.6.2
Platforms
iOS
Device Model
iPhone 16 Pro
flutter info
[✓] Flutter (Channel stable, 3.24.3, on macOS 14.5 23F79 darwin-x64, locale en-DE)
    • Flutter version 3.24.3 on channel stable at /Users/alehhutnikau/Flutter/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2663184aa7 (4 months ago), 2024-09-11 16:27:48 -0500
    • Engine revision 36335019a8
    • Dart version 3.5.3
    • DevTools version 2.37.3

[✓] Android toolchain - develop for Android devices (Android SDK version 36.0.0-rc1)
    • Android SDK at /Users/alehhutnikau/Library/Android/sdk
    • Platform android-35, build-tools 36.0.0-rc1
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)

[✓] VS Code (version 1.93.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 13 (API 33) (emulator)
    • macOS (desktop)              • macos         • darwin-x64     • macOS 14.5 23F79 darwin-x64
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 131.0.6778.205

[✓] Network resources
    • All expected network resources are available.

• No issues found!

How to reproduce?
Many users report the same issues (mostly on iOS devices):
When their photo library is relatively big (more than 50K images) the photo manager loads very slow (sometimes it takes up to few minutes) or not loads at all. After the list is loaded it's laggy and may not respond on interactoins.
Logs
No response
Example code (optional)
No response
Contact
hutnikau

AI Summary: The photo_manager package has performance issues on iOS when handling large libraries (50K+ images), causing slow loading and laggy interactions.


It is not automatically changing file paths or changing folders

Type: Bug
It is not automatically changing file paths or changing folders. If I have a file in the components folder and set to components -> here (for example) it sends it, but the option to update the path does not appear
    "javascript.updateImportsOnFileMove.enabled": "always",
    "typescript.updateImportsOnFileMove.enabled": "always",

My project is using vue and I have the Vetur tool installed, but the prompt does not appear warning or changing automatically
VS Code version: Code 1.74.3 (97dec172d3256f8ca4bfb2143f3f76b503ca0534, 2023-01-09T16:59:02.252Z)
OS version: Windows_NT x64 10.0.25272
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 5 3600 6-Core Processor               (12 x 3593)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.95GB (3.39GB free)

Process Argv
--crash-reporter-id b76b8ab9-6cd3-43e7-adc5-61e6c60dae27

Screen Reader
no

VM
0%

Extensions (43)

Extension
Author (truncated)
Version

codesnap
adp
1.3.4

vscode-color
ans
0.4.5

icons-carbon
ant
0.2.6

turbo-console-log
Cha
2.6.2

path-intellisense
chr
2.8.4

vscode-svgviewer
css
2.0.0

windows-terminal-opener
cyr
1.1.0

githistory
don
0.6.19

gitlens
eam
13.2.0

EditorConfig
Edi
0.16.4

vscode-great-icons
emm
2.1.90

prettier-vscode
esb
9.10.4

auto-close-tag
for
0.5.14

auto-rename-tag
for
0.1.10

todo-tree
Gru
0.0.220

vue-snippets
hol
1.0.4

path-autocomplete
ion
1.22.1

vue
jcb
0.1.5

vscode-nuget-package-manager
jmr
1.1.6

unity-code-snippets
kle
1.3.0

csharpextensions
kre
1.7.3

vscode-eslint-ts-fix
lyn
2.2.2

git-graph
mhu
1.30.0

vscode-docker
ms-
1.23.3

csharp
ms-
1.25.2

remote-containers
ms-
0.266.1

vsliveshare
ms-
1.0.5808

color-highlight
nau
2.5.0

vetur
oct
0.36.1

errorlens
Phi
1.1.3

LiveServer
rit
5.7.9

text-marker
ryu
1.11.0

markdown-preview-enhanced
shd
0.6.7

mdx
sil
0.1.1

vue-preview
Sim
1.7.3

unity-tools
Tob
1.2.12

vscode-mdx
uni
1.1.0

unity-debug
Uni
3.0.2

vscode-icons
vsc
12.0.1

gitblame
wad
10.1.0

JavaScriptSnippets
xab
1.8.0

vscode-mdx-preview
xyc
0.3.3

unity-snippets
Ycl
0.1.2

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyonecf:30548226
pyindex848cf:30577861
nodejswelcome1:30587005
2e4cg342:30602488
89544117:30613380
2i9eh265:30646982

Please file this against the Vue extension. These settings are only for JS and TypeScript files

Please file this against the Vue extension. These settings are only for JS and TypeScript files

And what should I do? Sorry I didn't understand very well, even without these settings it doesn't work

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!

any other solution?


Link to the tBTC FAQ #200

This needs to be redone to fit into the changes from #264 🙊
I think the markup in the footer file is simplified though. It makes sense to do this as a separate PR, since the commit will be new, but will leave it up to you if you want to do it that way @DaniellMesquita . Thanks for the PR, sorry we invalidated it 😞

Closing, would love to see a new one if it's not been done in the latest release @DaniellMesquita


In-Game: Show Debug Info and Options for facilitator

While the facilitator is taking care of the test, we should show some guiding information (not visible to the VR participant).

New Icons in this mockup can be gotten from the zip file below and the rest are in issue #5:
facilitator-ui-ressources.zip
Debug Info:

[ ] Show the Participant Number and Test number
[ ] Show the current eye tracking coordinates for Left and Right Eye
[ ] Show the current time which has passed of the test.

Display Options

[ ] Show a Grid (indicates the positions of the circles which measure accuracy)
[ ] Show a Gaze Dot (indicates the gaze by showing a dot on the screen)
[ ] Show a Trace (shows a LineRenderer of where on the screen the eye has been so far)
[ ] Show the pupils (shows the webcam pictures of the pupils, useful to debug if something has gone wrong).

There should also be an option to finish the test prematurely, or after the test has finished and the facilitator wish to continue.

I have worked out some improved mockups for the in-game behavior with Hendrik. it's based on the following:

In principle, we want to be able to test the whole visual field of the person in VR, rather than just 9 points.
We want to remove all distractors in VR (Grid, gaze points,..) and only show the "Focal Point", the person is supposed to look at.
We should then overlay the VR view with information which can only be seen by any therapists/faciliators of the experiment.

VR View

Facilitator View

Facilitator View Minimized

Test Summary View

There is a lot of subtle behavioral changes and information slots which I have left unexplained. Feel free to ask questions in here, related to them and we can get them clarified as we go.


New embed lacks of Google Analytics code

cc @beloneys

The current property where the embeds are being tracked is (UA-20934186-10).
Once we have https I'll do the set up for the new domain so I'll keep you updated.
Thxs!
B

dont forget this please guys!

On Jul 7 2016, at 11:35 am, Sergio Álvarez Leiva
<EMAIL_ADDRESS>wrote:

dont forget this please guys!

—
You are receiving this because you were assigned.
Reply to this email directly, view it on
GitHub,
or mute the
thread.![](https://github.com/notifications/beacon
/AAIEMh6GCOd9UGt6XRP7PMa2Ezhfs-Bqks5qTMhhgaJpZM4JEL7q.gif)


Suggestion for multiple audio renderer devices

##Suggestion: add multiple audio render devices in mediauriplayer using directshow infinite pin tee filter

I do not know if it should be in the library, since I assume not so many users may use it. But what about to allow to plug in some user code to change the directshow graph?

For plug multiple soundcards at same time, needed to create array filter of soundcard and connect this with infinite pin tee filter. For this infinite pin tee filter join input with decoder filter output and present output +1 respect to output filters connected.  see this https://msdn.microsoft.com/it-it/library/windows/desktop/dd390336(v=vs.85).aspx. Note infinite pin tee filter also available for video rendering

@fabcal24 DirestShow has many possibilities, this library cannot support all of them. However, it should allow the user to modify the behaviour without changing the code.
I think you can plug your code, when you subclass the MediaUriPlayer and override InsertAudioRenderer. See also Wiki.

@xmedeko ok, but infinite pin tee filter is native on directshow and isnot complex. Because is possible to render into multiple objects video with d3d clone function, why don't implement same for audio?

I just worry the code become to large to be easily maintained. I generally miss some pluggable architecture of the WPF-MediaKit. Maybe I do not get your idea right. Submit a PR, please, so I may better understand the problem.

@xmedeko I understand and share your concern. I would like to be able to contribute to the growth of this project, but in this period I have to complete software for clients. I'm really happy with the work you did, because with this component I solved only a few problems on my project. I've already made small implementations like player status (playing, paused, stopped, failed) and as soon as I can share them. The implementation I suggest does not require many lines of code and I could safely propose the modification code as soon as the pending work with customers is terminated. I find it fair to prevent the project from growing in a chaotic and disorganized way because already the manufacturers of operating systems and components used to change APIs are already in place, keeping it and making it compatible with technological evolution is already exhausting. I unfortunately do not speak English (this is Google Translator) but if you want we can keep in touch outside of github and I can contribute to this project. But I need time. You can contact me directly at info at softwaremagic dot it, then I'll give you my personal email address  (I am the owner of the domain company ;-) )

No kudos to me, the author is Jeremiah Morrill and @Sascha-L, I just do some necessary maintenance, but do not know DirectShow much. Still need some more people to take care of the project, see the README.md.

hi guys,
is it possible to select audio output in existing source code if one wants to use multiple sound card?
thanks
rex


⚠ Bofrost.es has degraded performance

In 21cd213, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1686 ms

Resolved: Bofrost.es performance has improved in 9b9c71d after 13 minutes.


Generic types in responses

Hi!
We have some generic response class, and we want to show responses with specified types.
Can we show response with considering parameter type?
We're using 2.5.0 version.
For example.
Swagger now shows respose schema:
{
  "body": {},
  "error": "string"
}

We want:
{
  "body": {
    "id": "string",
    "login": "string",
    "email": "string"
  },
  "error": "string"
}

Controller:
@RequestMapping("/info")
public Response<JsonUser> info() {
    Authentication authentication = SecurityContextHolder.getContext().getAuthentication();
    User user = userService.getUserByUsername(authentication.getName());
    return new Response<>(null, new JsonUser(user));
}

Response:
public class Response<T> {

    private String error;

    private T body;

    public Response(String error) {
        this.error = error;
    }

    public Response(T body) {
        this.body = body;
    }

    public Response(String error, T body) {
        this.error = error;
        this.body = body;
    }

    public String getError() {
        return error;
    }

    public void setError(String error) {
        this.error = error;
    }

    public Object getBody() {
        return body;
    }

    public void setBody(T body) {
        this.body = body;
    }
}

JsonUser:
public class JsonUser {

    private String id;

    private String login;

    private String email;

    public JsonUser(User user) {
        this.id = user.getId();
        this.login = user.getLogin();
        this.email = user.getEmail();
    }

    public String getId() {
        return id;
    }

    public void setId(String id) {
        this.id = id;
    }

    public String getLogin() {
        return login;
    }

    public void setLogin(String login) {
        this.login = login;
    }

    public String getEmail() {
        return email;
    }

    public void setEmail(String email) {
        this.email = email;
    }
}

yes you can

but how?

Not sure what you're asking i.e. are you reporting a bug or is this a question? What is it doing and what do you think its supposed to be doing? What have you tried?
Here is an example in the demos project.

We want structure like this:
{
  "body": {
    "id": "string",
    "login": "string",
    "email": "string"
  },
  "error": "string"
}

We have tried to use genericModelSubstitutes
With genericModelSubstitutes(Response.class):
{
  "email": "string",
  "id": "string",
  "login": "string"
}

Without genericModelSubstitutes(Response.class):
{
  "body": {},
  "error": "string"
}

Hi Dilip,
I have been trying to create API specification using springfox-swagger-ui, springfox-swagger, and swagger-springmvc. I have spring 4.X with interface drivern REST services.

I have interface which is having REST annotations. In the same file I have added Swagger annotations like @Api, @ApiResponse, @ApiOperation etc along with all details

I have its implementation. But at the moment I guess we are not supporting interfaces as part of swagger project. I have found a way out using RestEasy 2.3.5 but It is also not supporting Spring 4.x.
Using RestEasy we can support interface driven swagger specification. But I would like to do it using your way.
Thanks,
Sachin

Guys please help me out..

Swagger REST API annotation not working on interface but working on implementation class
I want to support it.

@sac10nikam please create a new issue and not add unrelated requests onto existing issues in the future.
Springfox totally supports interface based approach. Here is an example of an Abstract Controller and its Concrete Implementation.

Hi Dilip,
Thanks for your quick reply. I will create new issue for sure. It would be
great if you could share an example having interface with spring 4.x
annotations and swagger annotations. My interface has @RequestMapping at
interface level and as well as at method level. Methods has @PathVariable's.
My controller  should have just its implementation. This class will have
@RestController at class level.
Note: I am using springfix-swagger-ui, springfox-swagger2 and
swagger-springmvc pom entries. Will share my code in next email.
I will highly appreciate your reply on this. I have been working on this
from last 3 days. My client has this requirement.
Have a nice day ahead man.
Many Thanks,
Sachin
On Jul 12, 2016 7:47 PM, "Dilip Krishnan"<EMAIL_ADDRESS>wrote:

@sac10nikam https://github.com/sac10nikam please create a new issue and
not add unrelated requests onto existing issues in the future.
Springfox totally supports interface based approach. Here is an example of
an Abstract Controller
https://github.com/springfox/springfox/blob/master/springfox-spring-web/src/test/java/springfox/documentation/spring/web/dummy/controllers/AbstractController.java
and its Concrete Implementation
https://github.com/springfox/springfox/blob/master/springfox-spring-web/src/test/java/springfox/documentation/spring/web/dummy/controllers/ConcreteController.java.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/springfox/springfox/issues/1383#issuecomment-232061355,
or mute the thread
https://github.com/notifications/unsubscribe/AGOFOAptrjFUNUWGQL5j6uLqaZZ9cYL8ks5qU6IEgaJpZM4JJiW6
.

You don't need swagger-springmvc entries. Please check the the docs? There are the demos for you to use as well.

Seems like you'd need to @RestController annotation on the interface implementation otherwise it will not work. No need to repeat the request mappings, swagger annotations etc.

i made an example for this issue - https://github.com/satahippy/springfox-issue-demo
$ git clone git@github.com:satahippy/springfox-issue-demo.git
$ cd springfox-issue-demo
$ git checkout 1383-generic-types-in-response
$ ./gradlew bootRun

Open http://localhost:8080/swagger-ui.html#!/user-controller/infoUsingGET

This is what I see... which seems like it is what you want

Thanks Dilip. If you look at my example if will find interface has swagger
annotations and spring 4.x annotations. And it's controller implementation
class has just a overridden method which returns address json.
But only one annotation named as @Restcontroller is there.
I want to execute all HTTP statuses with this example. I could run this
example.
Thanks,
Sachin
On Jul 15, 2016 7:48 PM, "Dilip Krishnan"<EMAIL_ADDRESS>wrote:

This is what I see... which seems like it is what you want
[image: swagger_ui]
https://cloud.githubusercontent.com/assets/73257/16877303/0cd191f0-4a6d-11e6-8cd1-2e7147f1e257.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/springfox/springfox/issues/1383#issuecomment-232963132,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGOFOMkQLN8WRzOkvcfYsI9zNlYvmxqNks5qV5bEgaJpZM4JJiW6
.

@dilipkrish, sorry, my bad)
thnx!
feel free to close issue

Can you please send my example with changes if there are any. I want to
test all HTTP statuses. I don't know how to test swagger statuses.
Thanks.
On Jul 16, 2016 3:37 PM, "satahippy"<EMAIL_ADDRESS>wrote:

@dilipkrish https://github.com/dilipkrish, sorry, my bad)
thnx!
feel free to close issue
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/springfox/springfox/issues/1383#issuecomment-233123361,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGOFODm6Ja3kYEZBCd6P7CLt7ChFJ295ks5qWK1ZgaJpZM4JJiW6
.

I don't know why do you think it is easy to support Generic Type. I still can not get the correct result which show the generic type successfully.

@tbwork does that mean it works as expected?

@dilipkrish  but, how to do?

@dilipkrish Hello. This behavior has been broken in 3.0.0. Should I open new issue for this?


[TeX] Add .spl and .soc

Reasons for making this change:
.soc and .spl were missing for TeX

.soc - package changes
.spl - documentclass elsarticle (Elsevier journals)

Links to documentation supporting these rule changes:
http://tex.stackexchange.com/a/256803/9075

@koppor thanks!


fix: Remove compression from serving

Fixes #32. Compression is handled by appengine automatically anyways, so should be redundant

Compression should be handled by appengine: https://cloud.google.com/appengine/docs/standard/nodejs/how-requests-are-handled#response_compression


Testing wheel cache (seems broken)

why do you update the superbuild though ?

That's a mistake, thanks

@mwestphal see https://github.com/f3d-app/f3d-superbuild/actions/runs/7164851701/job/19505672622?pr=124#step:3:3635
My understanding is scikit build is automatically targeting 10.9 ( see https://scikit-build.readthedocs.io/en/latest/generators.html#default-deployment-target-and-architecture).
However, it's trying to link to the system library zstd built on 12.0.
So the questions are:

Why does netcdf have a dependency on zstd now?
Why is the cache is not rebuilding it? (should we add more things like deps versions in the cache key?)

Why does netcdf have a dependency on zstd now?

Looks like optional dependency to zstd was added fairly recently in netcdf:
https://github.com/Unidata/netcdf-c/issues/2173
But there is no zstd project in the superbuild, so it should be disabled instead of using system zstd.
Not sure what changed though, all of that is at least 6 month old or more.

Why is the cache is not rebuilding it?

There is no zstd project, so it cant be built.

should we add more things like deps versions in the cache key?

The wheels system require changing the cache number manually whenever we change anything that may require a rebuild of the superbuild. I'm open to improve that but it would require separating it in another repository imo.

But there is no zstd project in the superbuild, so it should be disabled instead of using system zstd.

Any idea how to disabled it?


[bugfix][relay] Fix alpha attribute with None in ELU

This patch fixes a bug in ELU. when the alpha=None, It will lead to a wrong compilation and give a confusing inference result.
For example, the following script will produce inconsistent inference results between TVM and Keras. However, we hope tvm can reject it immediately in the model loading stage. Because the model is invalid (see Line 210-212 in keras source code file).
This PR is a similar fix to the pr-14707. pr-14707 fixed a similar bug in  LeakyReLU.

Reproducible script
import tvm
import tvm.relay as relay
import numpy as np
from tensorflow import keras
from tensorflow.keras import layers, models

input_shape = (1, 2, 3, 4)
input_data = np.random.random(input_shape)
x = layers.Input(shape=input_shape[1:], dtype='float32')

layer = keras.layers.ELU(alpha=None)
layer.set_weights(layer.get_weights())

y = layer(x)
model = models.Model(x, y)

res_keras = model.predict(input_data)

shape_dict = {'input_1': input_shape}
mod, params = relay.frontend.from_keras(model, shape_dict)

with tvm.transform.PassContext(opt_level=3):
    model = relay.build_module.create_executor("graph", mod, tvm.cpu(0), 'llvm', params).evaluate()

test_x_tvm = input_data
res_tvm = model(tvm.nd.array(test_x_tvm.astype('float32'))).numpy()

np.testing.assert_allclose(res_keras, res_tvm, atol=1e-3, rtol=1e-3)

Hi @echuraev @AndrewZhaoLuo, could you help me review it? Thank you!

@tvm-bot rerun


[FLINK-31351][sql-gateway] Don't stop the stuck thread by force

What is the purpose of the change
We should not stop the thread by force because it may cause an inconsistent state. So we just notify the users it has the possibility to cause resource leak.

lgtm, just a couple of minor comments

Thanks a lot for @snuyanzin review. Because all comments are in about the public modifier, so I fix the comments locally.
Merging...


Improve encryption support in FileInputStreamCache

Failing test: CachedOutputStreamTest.testCacheStreamToFileAndCloseStreamEncrypted
It works for me locally, so need to investigate...

closing old PR


feature(paginate): Adding new feature to search for deleted items wit…

…h soft delete

LGTM, ci fails tho due to formatting. you can npm run format to fix

also please describe new config param in README

Thanks for reminding me =), I put this new parameter in the README.

:tada: This PR is included in version 2.6.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Consider splitting RSpec shared behaviours and development dependencies

Hola :v:
First of all thanks for your awesome project! We're happily using it for at least a year now in production. But today I spotted a minor problem. We're requiring slack-ruby-bot/rspec in spec_helper (as it's noted in the README) which loads and configures VCR gem and it causing some unexpected exceptions to be raised by VCR, e.g.
================================================================================
An HTTP request has been made that VCR does not know how to handle:
  GET https://www.iana.org/domains/reserved?foo=moo

There is currently no cassette in use. There are a few ways
you can configure VCR to handle this request:

  * If you're surprised VCR is raising this error
    and want insight about how VCR attempted to handle the request,
    you can use the debug_logger configuration option to log more details [1].
  * If you want VCR to record this request and play it back during future test
    runs, you should wrap your test (or this portion of your test) in a
    `VCR.use_cassette` block [2].
  * If you only want VCR to handle requests made while a cassette is in use,
    configure `allow_http_connections_when_no_cassette = true`. VCR will
    ignore this request since it is made when there is no cassette [3].
  * If you want VCR to ignore this request (and others like it), you can
    set an `ignore_request` callback [4].

[1] https://www.relishapp.com/vcr/vcr/v/4-0-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/4-0-0/docs/getting-started
[3] https://www.relishapp.com/vcr/vcr/v/4-0-0/docs/configuration/allow-http-connections-when-no-cassette
[4] https://www.relishapp.com/vcr/vcr/v/4-0-0/docs/configuration/ignore-request
================================================================================

I'll add a few notes about our project setup:

It's a huge monolith app that includes slack bot alongside the rest of the application
Specs for slack bot share rspec configuration with the rest of the test suite
We've been using VCR prior to the introduction of slack-ruby-bot
Our VCR has different configuration

You may see where it leads already. The exception above were a surprise because we don't even  load our VCR helper with configuration in a given spec. We haven't spotted this problem immediately on slack-ruby-bot/rspec addition because most of the time we're running the whole suite and due to a  load order our VCR configuration usually loaded shortly after slack-ruby-bot/rspec/support/vcr and overrides the config.
I appreciate the effort to ship RSpec matchers and shared behaviour with this gem but these things do not require VCR as a dependency (I've checked how VCR is used).
I'd like to open up minimal PR to fix the issue, by excluding support/vcr from eager loading and require it only in the gem specs that need it. That's the cheapest way to fix the issue I guess. However, I think that such eager-loading may cause further problems of similar nature in the future. Ideally, I'd create a separate gem for RSpec shared matches and behaviours to physically split development dependencies and public API.

I would support a separate slack-ruby-bot-rspec gem, however that's not going to fix your problem if it were identical to what we have here and you required it.
The fix you suggest sounds good to me. Without digging into it none of the shared matchers need VCR, or do they?

none of the shared matchers need VCR

That's correct. I'll prepare a PR a bit later then.

@dblock may I ask you when do you plan to publish a new gem version?

@dblock may I ask you when do you plan to publish a new gem version?

Done.


Question: Why was remote webcam function removed?

I just noticed that old Quasar from the year 2016, 2017 included the remote webcam function, I am curious why was this function removed from recent versions? Thanks!
Edit: Also audio recording function is still not merged with the recent releases, even though it has been implemented from some pull back in 2017, will it be merged in the near future?

To actually answer the question :

Remove features such as password recovery
Features which could get abused too easily should get removed from Quasar.

To actually answer the question :

Remove features such as password recovery
Features which could get abused too easily should get removed from Quasar.

Controlling what people have access to, it's called Communism....


Adding Thorlabs PM100 Powermeter

This is to add this powermeter from Thorlabs.

Thanks again @dvspirito! Please add a docs page for this instrument as well.

Thanks again @cjermain

Thanks @dvspirito!


Add support for $ prefixed container names (like $root)

Currently, when trying to create a container with $ in front of the name, the server rejects it with error 400. $root is a well known supporter container.
More information on the $root container:
https://docs.microsoft.com/en-us/rest/api/storageservices/working-with-the-root-container

Hi @SimonLuckenuik ! Thanks for reporting this! Confirmed as bug / missing feature. Currently, Azurite does not support the $root container semantics. Will release a fix as part of v.2.2.2 within the next couple of days. Will keep you posted about the progress here.

FYI my workaround for now has been to add manually the container in the JSON file. I eas able to add the $logs container that way and have the storage explorer working as well.

Cross-referencing #155 regarding $logs container and storage explorer integration

@SimonLuckenuik just released v2.2.2. let me know if it works for you!


[UPDATE] splitpayments to v0.1.3

https://github.com/lnbits/splitpayments/releases/v0.1.3

utACK
CI check passed


[Event Request] Table 5407 "Prod. Order Component" - OnAfterSetFilterFromProdBOMLine

Hello, Is it possible to get this event ?
procedure SetFilterFromProdBOMLine(ProdBOMLine: Record "Production BOM Line")
    begin
        SetRange("Item No.", ProdBOMLine."No.");
        SetRange("Variant Code", ProdBOMLine."Variant Code");
        SetRange("Routing Link Code", ProdBOMLine."Routing Link Code");
        SetRange(Position, ProdBOMLine.Position);
        SetRange("Position 2", ProdBOMLine."Position 2");
        SetRange("Position 3", ProdBOMLine."Position 3");
        SetRange(Length, ProdBOMLine.Length);
        SetRange(Width, ProdBOMLine.Width);
        SetRange(Weight, ProdBOMLine.Weight);
        SetRange(Depth, ProdBOMLine.Depth);
        SetRange("Unit of Measure Code", ProdBOMLine."Unit of Measure Code");
        //>>>>>>>>>>>>>>>>>>>>>>>>>
        OnAfterSetFilterFromProdBOMLine(Rec, ProdBOMLine);
        //<<<<<<<<<<<<<<<<<<<<<<<<<
    end;

  [IntegrationEvent(false, false)]
    local procedure OnAfterSetFilterFromProdBOMLine(var ProdOrderComponent: Record "Prod. Order Component"; ProdBOMLine: Record "Production BOM Line")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.