rendering chunks terminate called after throwing an instance of 'std::bad_alloc'

Describe the bug
My project has more than 400 large pages。 In the trunk process, when using memory near 17GB, will throw 'std::bad_alloc' errors ，but my server's memory is sufficient。
If I reduce pages num to 300, it workers fine .
Here is the build process

pnpm run build

<EMAIL_ADDRESS>build /mnt/buildresult/63633915-9700-ff01-00a2-105767dee950/onein-ts
cross-env NODE_OPTIONS=--max-old-space-size=32768 vite build

vite v4.3.9 building for production...
transforming (5772<EMAIL_ADDRESS>(156:17) Use of eval in<EMAIL_ADDRESS>is strongly discouraged as it poses security risks and may cause issues with minification.
<EMAIL_ADDRESS>(157:17) Use of eval in<EMAIL_ADDRESS>is strongly discouraged as it poses security risks and may cause issues with minification.
✓ 5772 modules transformed.
rendering chunks (403)...terminate called after throwing an instance of 'std::bad_alloc'
terminate called recursively
command terminated with exit code 137
Reproduction
N/A
Steps to reproduce
N/A
System Info
System: Linux/CentOS7
Vite: 4.3.9
Rollup: 3.26.2
RollupConfig:
-----------------
build: {
      outDir: './build',
      reportCompressedSize: false,
      brotliSize: false,
      target: 'chrome70',
      minify: 'esbuild',
      rollupOptions: {
        plugins: [],
        input: {
          main: resolve(__dirname, 'index.html')
        },
        output: {
          manualChunks(id) {
            const modulesDir = 'node_modules/'
            const chunkId = id.toString() || ''
            if (chunkId.includes(`${modulesDir}`)) {
              const arr = chunkId.slice(chunkId.lastIndexOf(`${modulesDir}`) + modulesDir.length).split('/')
              const moduleName = arr[0] || ''
              switch (moduleName) {
                case '@onein':
                case '@onein-ui':
                case '@onein-act':
                case '@onein-func':
                case 'lodash-es':
                case '@vue':
                case '@icon-park':
                case 'element-plus':
                case '@element-plus':
                case 'vue3-sfc-loader':
                case 'dom-to-image-more':
                case 'jspdf':
                case 'print-js':
                case 'echarts':
                case 'pizzip':
                case 'docxtemplater':
                case 'jszip':
                case 'vue-router':
                case 'core-js':
                case 'canvg':
                case 'crypto-js':
                case 'jquery':
                case 'pinyin-pro':
                case 'html2canvas':
                case 'zrender':
                case '@antv':
                case 'quill':
                case 'docx-preview':
                case 'vod-js-sdk-v6':
                case 'cos-js-sdk-v5':
                case 'pako':
                  return `_${moduleName}`
                default:
                  return '__vendor'
              }
            }
          }
        },
        maxParallelFileOps: 50,
        watch: {
          chokidar: {
            useFsEvents: false
          }
        }
      }
    },

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Duplicate of https://github.com/vitejs/vite/issues/2433. We're trying to slowly pick off memory usage, but it won't be easy to fix. The linked issue has a few suggestions to workaround this, e.g. disabling sourcemaps.


Styles gone after revisting page

So I'm using react-tooltip for a register form.  When I redirect to the login page, then redirect back to the register page with the register form, all the styles are gone from the tooltips.  The text and css transitions still function, but the background and text color is gone.
I rebuild the tooltip bindings in useEffect with the following:
useEffect(() => {     ReactTooltip.rebuild();   });
Anyone having similar problems?

So it looks like on the redirect from register to login and back to register, that the tooltip's div element is being assigned a different hashed class.  The styles are in the console, but it's assigned to a different hashed className.

Having the mismatched hashed class name issue too. No style is being applied because the class name in <style> and the class name on the element doesn't match.

@faahim Had the same issue.To circumvent it for now, pass a 'uuid' prop to the styling component and it will not generate one on its own on re-render.  Haven't seen anything break because of this fix.... yet.
<ReactTooltip uuid="<some-uuid-here>" />

https://github.com/wwayne/react-tooltip/blob/master/src/index.js#L89 -> this shows that it generates a new uuid if it is not passed down.
https://github.com/wwayne/react-tooltip/blob/master/src/index.js#L680 -> shows where it is used to generate the class name on the div
https://github.com/wwayne/react-tooltip/blob/master/src/index.js#L678 -> shows where it is used to generate the styles with that classname. This generated styles don't appear on reload that said it appears if reloading the base page. Haven't dug in to find out why for now.

@Joseppi83 thanks for raising this. Helped me zero in on the temp fix.

@s-ashwinkumar Woo, thanks so much for all those info! When I saw it has mismatched hashes, I felt like, gosh, if it generates new ones every time, and it can go wrong, then it will go wrong at least some of the time. I know it can be reliable (UUID looks like solid fix here), but my OCD brain would give me the peace of mind. 😅
I'm overriding the stylings with a custom class name for now. But will use uuid approach next time.
Thanks a ton!

@s-ashwinkumar Thanks for the solution. Its working perfectly now.

Is there a more permanent fix? I'm seeing this happen already in my dev environment with only a few tooltips. I tried the uuid approach, but that actually broke more tooltips.
Overriding the styles with custom classes seems to work far better.


[APP-901] Some users get "can't decode bitmap" when attempting to upload an image

Need to figure out why this might happen and fix it
APP-901

Is there any logs you might have for this? I searched Sentry and could not find anything.


Set min and max labels programatically

hello, my client applies to be the min/max labels as the min and max values on the slider, is it, or will it be possible to set thees 2 values programatically? Now I can only set formatting and that is not enough. Now I am trying to fight the plugin css to set position of movable labels, but it seem really unethical to me doing it this way
this is my code now:
<InputRange
            maxValue={50}
            formatLabel={value => `${value}°`}
            value={temperature}
            minValue={-50}
            onChange={value => this.updateTemperature({ ...value })}
          />

Hi, any news on this issue ?


Unsigned 4-bit adder (synthesizable)

A request for a checkpoint commit that adds just enough functionality to express a 4-bit adder which can be synthesized from SystemVerilog, and a simple test bench (not assertion checking yet).

Looks good to me, perhaps in the future we can wrap the list bool along with its bitlength

The use of list bool to represent a bit-vector is only temporary here. Soon I want us to replace this with something that represents the vector length in the type e.g. Bitvector from the Coq library.


Move documentation to Wiki

We should consider migrating all documentation (from https://github.com/arrowhead-f/core-java/tree/master/documentation) to the wiki pages...

There is certanly some merit to doing this, but I feel like what would be even better is to have the general SoSDD and SysDD documentations here on the wiki page, and the contents of the SD and IDD docs should be hosted on the core system webservers. There are some tools for this in Java (Spring REST docs is 1 that comes to mind), and I guess there are similar tools in other languages as well.

Just realised that there were some inconsistencies between the documents I had inside the repository and then those on the wiki.
At least I think I manage to fix it (and delete those in the repo.), so hopefully I remember to update the  wiki the next time instead...
Btw. realised that the wiki is just a repository in itself (https://github.com/arrowhead-f/core-java.wiki.git).


Investigate upstream Vibe.d issue: Handle leak

We're currently seeing the following output in the integration tests:
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638919694Z Warning (thread: main): leaking eventcore driver because there are still active handles
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638924687Z    FD 10 (streamListen)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638929101Z    FD 12 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638933411Z    FD 13 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638937809Z    FD 14 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638942036Z    FD 15 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638946347Z    FD 16 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638951363Z    FD 17 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638955579Z    FD 18 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638959669Z    FD 19 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638980753Z    FD 20 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638985588Z    FD 21 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638989727Z    FD 22 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638993792Z    FD 23 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.638997937Z    FD 24 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639001990Z    FD 25 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639006007Z    FD 26 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639010869Z    FD 27 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639015242Z    FD 28 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639019546Z    FD 29 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639023989Z    FD 30 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639028130Z    FD 31 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639032640Z    FD 32 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639036978Z    FD 33 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639041578Z    FD 34 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639067064Z    FD 35 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639072500Z    FD 36 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639076984Z    FD 37 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639081561Z    FD 38 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639086015Z    FD 39 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639090539Z    FD 40 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639094719Z    FD 41 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639105485Z    FD 42 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639109921Z    FD 43 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639114316Z    FD 44 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639118739Z    FD 46 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639123226Z    FD 47 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639127643Z    FD 48 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639150530Z    FD 49 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639154919Z    FD 50 (streamSocket)
node-7_1_3e996a01b79d | 2020-08-23T14:44:18.639159332Z    FD 53 (streamSocket)

It  would be good to take a look into the issue. Some upstream discussion: https://github.com/vibe-d/vibe.d/issues/2245

quick update on the issue:

streamListen
I managed to solve this by issuing stopListen on the HttpListener object as the discussion on the vibe.d issue tracker suggested
streamSocket(this issue was NOT reported on the vibe.d tracker)
I managed to reproduce it in 2 different ways:

2.1 Reproduce issue of streamSocket
void main()
{
    auto settings = new HTTPServerSettings;
    settings.bindAddresses = ["<IP_ADDRESS>"];
	settings.port = 8080;
    auto router = new URLRouter;
	router.get("/weather", &weather);
    HTTPListener httpListener = listenHTTP(settings, router);

	runApplication();
    httpListener.stopListening;
}

2.1.1 start up the server above
2.1.2 press CTRL+C(the server will not exit immediately)
2.1.3 send curl -v <IP_ADDRESS>:8080/weather from the command line
when the server finally exits it will report streamSocket error
if you change the order of 2.1.2 and 2.1.3, then there is no error => socets after CTRL+C are not cleaned by vibe.d
2.2 Reproduce issue of streamSocket
2.2.1
start up agora and make sure the config files has hosts that are unreacheble with ping,for example
network:
Supported value: IPv4, IPv6

http://<IP_ADDRESS>:2828
http://<IP_ADDRESS>:2828
2.2.2 you will see some connection attempts like this:

2.2.3 when you press CTRL+C, those sockets in SYN states are reported as leaking streamSockets
2.2.4 I verified in the vide.d code that we register this new sockets into our internal datastructures, before we even manage to fully connect to the remote node

it doesn't seem straightforward to fix either 2.1 or 2.2 without delving into vibe.d code very heavily

and easier way to reproduce 2.2 is this:
void main()
{
    runTask({
        requestHTTP("http://www.index.hu",
            (scope req) {
                req.method = HTTPMethod.GET;
            },
            (scope res) {
                logInfo("Response: %s", res.bodyReader.readAllUTF8());
            }
        );

        requestHTTP("http://<IP_ADDRESS>:2828", // make sure this is not reachable by ping
            (scope req) {
                req.method = HTTPMethod.GET;
            },
            (scope res) {
                logInfo("Response: %s", res.bodyReader.readAllUTF8());
            }
        );
	});

	runApplication();
}

compile with "versions": [ "VibeHighEventPriority" ]

start the app
CTRL+C
you will see the the leaking streamSocket exception ONLY ONCE, this suggests that vibe.d only mishandle/leaking connections that are in SYN state


Revert "Add Double and Int Convenience Properties (#239)"

This reverts commit #239
This couldn't handle integer literal syntax more than Int.max e.g. 0x9e3779b97f4a0000
rdar://problem/70227387

https://github.com/apple/swift/pull/34292
@swift-ci Please test

@vermont42 Sorry, I have to revert it for now. This causes an error for valid UInt64 integer literals. like: https://github.com/apple/swift-argument-parser/blob/d424bca0ec66ec0e3888ebdc118379d348a67da3/Examples/roll/SplitMix64.swift#L19-L25

This causes an error for valid UInt64 integer literals

To be more clear, this was causing a fatalError crash.


fixed BLOG Pagination + SEO relevant Data

Updated SEO rel Links
Updated SEO Pagination more then actual 1 Link // now 4+ and 4-
Updated SEO title snippet for Page from to CounterAllPages

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-14146.
Please use this issue to track the state of your pull request.

 Seems like it is not fully responsive.
Would be great if you can change the following things so we can accept your pull request:
1.) Please have a look at pagings in other listings. Your change should work and look the same so we have it consistent.
2.) We don't work with the rel attributes because the destination page declares the meta information already.
Thanks again for your contribution.
Greetings,
Marcel

Hi,
I will now close this PR. Please create a new one and also notice my comments.
Greetings,
Marcel


Fix kubectl installation on dataflow e2e test

What this PR does / why we need it:
The current dataflow e2e test attempts to install kubectl via apt, but it will fail because the package is not available. This PR uses alternative way to install kubectl.
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

/test test-end-to-end-batch-dataflow

test-end-to-end-batch-dataflow

/test test-end-to-end-batch-dataflow

@khorshuheng should this still be open given #716?

Can be close.


Unblock read acks pump from inputhost

If the server is draining gracefully, then the server will send a
DRAIN command. The DRAIN command used to simply stop the write pump and
wait for the server to close the stream.
Even though server successfully will close the stream after finishing
the DRAIN, the readAcks pump will never see the EOF because we don't do
a stream.Read() unless we have some messages inflight.
This patch tries to solve that by waiting for a default of a minute and
explicitly closing the connection. In addition this patch also adds some
additional logs and metrics to make sure we can track retries and
failures on publish.

Coverage remained the same at 80.903% when pulling 98855f3ab35ec070d53cb41d5b63aac1d1b6abb7 on stuck_read into de07d3a434a354d72c5cea1c6afd40d9d26c62f3 on master.

Coverage remained the same at 80.903% when pulling fc9d7f1660e97df2cab4813cad6c9051c2c70766 on stuck_read into de07d3a434a354d72c5cea1c6afd40d9d26c62f3 on master.

Coverage remained the same at 80.903% when pulling 815cf5cd8e9d74e4c8b919dba77a388fbc461e0a on stuck_read into de07d3a434a354d72c5cea1c6afd40d9d26c62f3 on master.

Coverage remained the same at 80.903% when pulling 82196a0514b99cbc9b485b16010c236e2156ac26 on stuck_read into de07d3a434a354d72c5cea1c6afd40d9d26c62f3 on master.

Coverage remained the same at 80.903% when pulling 162eee472881470bdf45dd039fd3fa973d169c5c on stuck_read into de07d3a434a354d72c5cea1c6afd40d9d26c62f3 on master.


Various image/services bugfixes

CLOSES #248
CLOSES #315

@FnuGk Can you run it on your "complex" pipeline to verify that i haven't missed certain cases? Please 🤣


[HOLD ON #22589] [$1000] DEV: Web- Console Error on Display Name Page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

In Dev go to http://localhost:8080/
Open your browser console
Navigate to Settings > Profile > Display Name

Expected Result:
No console error
Actual Result:
Console error displayed:
Warning: TextInput contains an input of type text with both value and defaultValue props. Input elements must be either controlled or uncontrolled (specify either the value prop, or the defaultValue prop, but not both). Decide between using a controlled or uncontrolled input element and remove one of these props.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: Dev 1.3.42-9
Reproducible in staging?: n/a
Reproducible in production?: n/a
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/0ee0d41d-2354-4cc7-bfb1-d40f53e65d37
Expensify/Expensify Issue URL:
Issue reported by: @rayane-djouah
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689683515386629
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~013c91f4e75ba03ad5
Upwork Job ID:<PHONE_NUMBER>129561600
Last Price Increase: 2023-07-18

Reproducible.

Hi @danieldoglas I don't have a DEV environment, but are you able to reproduce this and let me know? Thanks in advance!

@jliexpensify it is reproducible

Proposal
Please re-state the problem that we are trying to solve in this issue.

Getting error for using value and defaultValue props together in TextInput component via Form.js file.

What is the root cause of that problem?

The root cause of the problem is that we are not removing defaultValue prop when cloning the Component in Form.js file.

What changes do you think we should make in order to solve the problem?

Adding defaultValue: undefined to the Form.js file's React.cloneElement function fixes the issue and it doesn't break as we are already initializing the value prop to defaultValue in the Form.js file.

What alternative solutions did you explore? (Optional)

N/A

Cheers @danieldoglas - if you want to be unassigned as the Engineer, lmk! Otherwise I'll keep you on this for the credit?

This is being fixed here

Awesome, thanks! I might keep this open until it gets deployed - that seems to be the process.

Still on hold

Still on hold

Awesome, thank you @Nikhil-Vats ! I'll need to pay out @rayane-djouah a reporting bonus though.

Ah, thank you @aimane-chnaif - you're correct. Unfortunately, you don't qualify for a bonus @rayane-djouah .


Dead project?

@blai, are you still maintaining grunt-express?  I'm happy to help if you don't have time.

Nevermind.  Getting rid of both Grunt and Gulp: http://blog.keithcirkel.co.uk/how-to-use-npm-as-a-build-tool/


Crash when running "gridcoinresearchd listreceivedbyaddress 1 true"

As the title says, when I try to see the addresses I have without a balence, I get "error: no responce from server" and gridcoinresearchd is no longer running. I am running Gentoo and version v<IP_ADDRESS>-g-research.

I can confirm a crash with daemon on Linux Ubuntu 17. It appears to work fine in windows thou.
redacted@vancouver01:~$ testnet -testnet listreceivedbyaddress 10 true
error: no response from server
and testnet daemon is not running
NOTE: testnet is the gridcoinresearchd daemon I just run production wallet as well on my nodes thus allowing me to support both testnet and production.

Should be fixed now. @Foggyx420 If you get the time, can you please double check?


Querying three (or more) tables

Hi Roland,
First, congrats for this cool. library.
Is there a way to query more than two tables? Didn't found any examples, only for two.
Thank you.
Regards, Pál
BTW, at the and of the page https://github.com/rbock/sqlpp11/wiki/Select instead of result.pop(); should be result.pop_front();

Hi Pál,
Glad you like the library :-)
You can chain joins to query more than two tables:
foo.join(bar).on(foo.id == bar.foo).left_outer_join(baz).on(bar.id == baz.ref);

Thanks also for the documentation hint. Fixed.
Best regards,
Roland

Can you give us an more full exmaple? like:
for (const auto& r : db.run(
			sqlpp::select(table.username, table.password, table.salt).from(table.join(role_table).on(table.username == role_table.username)).
				where(table.username == username)))

I found this
https://github.com/rbock/sqlpp11/wiki/Select

Like this?
for (const auto& r : db.run(
			sqlpp::select(all_of(foo))
                        .from(foo.join(bar).on(foo.id == bar.foo).left_outer_join(baz).on(bar.id == baz.ref))
                        .unconditionally()))
{
  // ....
}

Untested, I hope I got all the parentheses right :-)

So Great!


"deviceready" event

How can I handle "deviceready" event in this template?
Or it has been involved somehow to internal Vue components lifecycle (created, mounted etc.) ?

Guys?


space before trailing slash

Caught a bug in your template that makes rendering fail for my server:
in themes/avicenna/layouts/partials/header.html line 30,
I changed
30: 	<link rel="stylesheet" type="text/css" media="screen" href={{ "css/main.css" | absURL }}/>
to
30: 	<link rel="stylesheet" type="text/css" media="screen" href={{ "css/main.css" | absURL }} />
and it worked.
I guess it is not a problem for modern server, but it still takes me a while when I try to publish a personal website on my school's server.
c.f. https://stackoverflow.com/questions/462741/space-before-closing-slash
btw thanks for the template!

@linjiawu
Thank you! It's been a year that  I've not worked on this repo. I have a plan to refactor this and make new changes and adding new features.


Make vscode-docs-authoring a recommened extentions in repos

Is your feature request related to a problem? Please describe.
VS Code now supports suggesting extensions for when you open a repo https://code.visualstudio.com/docs/editor/extension-gallery#_recommended-extensions
Since the https://github.com/Microsoft/vscode-docs-authoring is the bundle for recommended authoring tools, it should be recommended for users that aren't aware of it.
Describe the solution you'd like
Add the following extensions.json to the MicrosoftDocs repos and be part of the scaffolding going forward
{
    "recommendations": [
        "docsmsft.docs-authoring-pack"
    ]
}

@nschonni Thanks for your recommendation. @cillroy Is this your area?

Found there was a typo in my original example, since it needs to be in a publisher.extension format

@meganbradley for awareness.


iferr snippet in go creates problems

VSCode Version: Version 1.31.1 (1.31.1)
OS Version: 10.12.6 (16G1815)

Steps to Reproduce:

type iferr to use go snippet for if/err

Does this issue occur when all extensions are disabled?: Yes/No

Please file the issue against the go extension. Thanks!


Obstacle drawing optimization

If you have a larger square, draw only outer layers of it

I think this can wait for now and we focus on implementing category #12 and #13

Optimized it in https://github.com/Blarc/crowd-evacuation/commit/81983d8c30f311cc40fb1f31404db702ddb947de.

Closing for now.


Request for AndroidX compatible alpha/beta release

Similar to https://github.com/google/flexbox-layout/issues/445 I hope you can just tag an alpha/beta release and I am opening this in order to get notified

WorkManager 2.0.0-rc01 is now released. This version is identical to 1.0.0 stable but has AndroidX dependencies.


adapter terminated, cannot find module phpdebug.js

Getting this error when I do "Listen for XDebug".  Windows 10.  vscode 1.29.1.  php 7.1.11.
Ideas?
module.js:545
throw err;
^
Error: Cannot find module 'c:/Users/John/.vscode/extensions/felixfbecker.php-debug-1.12.6/out/phpDebug.js'
at Function.Module._resolveFilename (module.js:543:15)
at Function.Module._load (module.js:473:25)    at Module.require (module.js:586:17)
at require (internal/module.js:11:18)
at [eval]:1:41
at ContextifyScript.Script.runInThisContext (vm.js:50:33)
at Object.runInThisContext (vm.js:139:38)
at Object. ([eval]-wrapper:6:22)
at Object. ([eval]-wrapper:8:3)
at Module._compile (module.js:642:30)

As those more knowledgeable probably already know, this was a problem with installation.  What I didn't realize was that I had to delete the folder for the extension rather than just uninstall and reinstall.


history of lightning: fix OP_CSV in transcript

fix OP_CSV from OP_CHECKTIMELOCKVERIFY to OP_CHECKSEQUENCEVERIFY
remove EOL extra spaces

Thanks for the clean up @jonatack


Logout causes entire page to reload

[ ] Login/Logout should not make the page reload and cause all information to be lost
[ ] Rename "Exit" to "Logout"

Fixed


Improve with upcoming changesets workspace support

Describe the bug
changeset publish does not replace workspace: ranges with current version in workspace before publishing with yarn as a package manager
To Reproduce
https://github.com/changesets/changesets/issues/432
https://github.com/soluble-io/cache-interop/pull/222
https://github.com/belgattitude/nextjs-monorepo-example/issues/2821

now try to use   "@changesets/cli": "2.22.0-temp.0", try  https://github.com/changesets/changesets/pull/758


r9 290x - one of 2 cards no longer visible to zogminer

I got this running earlier today and on boot, zcash-miner -listdevices shows both cards.

Upon hitting ctrl-c and running zcash-miner -listdevices it only shows one card at this point.
Nothing in syslog, dmesg, etc.
lspci shows the device
clinfo shows the device
Ubuntu 16.04 - Fresh install today
amdgpu-pro drivers
First part of clinfo:
`Number of platforms                               1
Platform Name                                   AMD Accelerated Parallel Processing
Platform Vendor                                 Advanced Micro Devices, Inc.
Platform Version                                OpenCL 2.0 AMD-APP (2117.10)
Platform Profile                                FULL_PROFILE
Platform Extensions                             cl_khr_icd cl_amd_event_callback cl_amd_offline_devices
Platform Extensions function suffix             AMD
Platform Name                                   AMD Accelerated Parallel Processing
Number of devices                                 2
Device Name                                     Hawaii
Device Vendor                                   Advanced Micro Devices, Inc.
Device Vendor ID                                0x1002
Device Version                                  OpenCL 1.2 AMD-APP (2117.10)
Driver Version                                  2117.10 (VM)
Device OpenCL C Version                         OpenCL C 1.2
Device Type                                     GPU
Device Profile                                  FULL_PROFILE`

Looks like the newer version has helped with this (or updating my bios)


Fix genomes params usage

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/rnaseq branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

Still seeing 2 warnings, but a nice improvement already:
WARN: Access to undefined parameter `bbsplit_index` -- Initialise it to a default value eg. `params.bbsplit_index = some_value`
WARN: Access to undefined parameter `star_index` -- Initialise it to a default value eg. `params.star_index = some_value`


Added ValueTuple so we can start taking advantage of C# 7 tuples.

@agocke added ValueTuple as a core reference to Roslyn, so it should be in VS now. Tagging @dotnet/project-system for review.

This dependencies indicates our Roslyn dependency, ValueTuple isn't a Roslyn dependency.

@davkean it seemed the best fit of the current dependency projects to use. I can make a new project for it if we want to.

A new project seems cleaner because then if a project wants to use tuples but doesn't need Roslyn APIs it can simply add a reference to the ValueTuple project.

As a middle ground, should we have a corefx dependency project?

Dependency projects are being removed from roslyn: https://github.com/dotnet/roslyn/pull/15465
Should we be doing the same?

RE Dependency projects - until we have something better (ie msbuild-based packagerefs that are unified in a targets), I still prefer them over Jared's approach which is to duplicate the refs at all the roots and than have an after the fact enforcement (read: PowerShell script) that makes sure they are the same version.
I can live what you've got here - given we're going to replace this with packagerefs anyway soon.

@333fred Can you figure out if this is supposed to be a RTM dependency and if not just merge it in?

There's a 4.3.0 of the ValueTuple package which is also the version that the IDE's codefix adds. Let's use that.

@srivatsn, updated to 4.3.0. @jaredpar or @agocke, can either of you confirm that this is the final version?

CC @jcouv
It's the final version until we make another change :)

We just need some stable dependency - so 4.3.0 is good. We can merge this change.

This construct does not work: new (IDependencyNode a, IProjectDependenciesSubTreeProvider b) { }; how do i create a new Tuple with new syntax? Also be careful with var (type1 x , type2 y) = ...  it would throw if any of the values is null.

you can simply say var (x, y) = (new DependencyNode(), new SubTreeProvider())

what if i don't want to instantiate them yet, with possible null values? I need to declare types not instances

(IDependencyNode node, IProjectDependenciesSubTreeProvider provider) = (null, null);

it does not work -red squiggles

What do the red squiggles say? - I just tried this on my machine and it works fine.

@abpiskunov, try running a NuGet restore. I was seeing System.ValueTuple`2 not imported until I reran restore.

I am trying to use value tuple in one of the property page providers and am able to build fine, but doing an F5 with ProjectSystemDogfoodSetup as the startup project generates the following FileNotFoundException when attempting to open property pages:

Do I need to move to a newer VS drop or is there a workaround?

The version number looks wrong - it should be <IP_ADDRESS>. Maybe you have some stale version?

The version of ValueTuple in my install is <IP_ADDRESS> under PrivateAssemblies.

Yes, the NuGet package version is 4.3.0 but the assembly is <IP_ADDRESS>. I verified the assembly is missing in my PrivateAssemblies, so time to move to a newer D15PreRel drop for me :) Thanks!

Btw, also worked by manually copying the assembly to PrivateAssemblies.

@jcouv has the 4.3.0 version been inserted to the latest PreRel builds?

Also filed this: https://github.com/dotnet/roslyn/issues/16036 as it looks like it's been shipped many times.

@srivatsn after i re-ran nuget restore it started to work , will update my change in the next coming bug fix.

@srivatsn Sorry, I don't understand the question.
My understanding is that a copy of System.ValueTuple.dll is copied in the VS install for the interactive window (originally added as 4.3-preview1 in https://github.com/dotnet/roslyn/pull/14376).
And then Roslyn also has a reference to the nuget package (updated to 4.3 in https://github.com/dotnet/roslyn/pull/14879).


Enchantment menu mixin breaks Botania's pylon enchanting

https://github.com/paulevsGitch/BCLib/blob/8ebcf2352ac7d4a940ee1ec799972a22ef28906f/src/main/java/ru/bclib/mixin/common/EnchantmentMenuMixin.java#L58-L59
Originally reported to us as https://github.com/VazkiiMods/Botania/issues/3901
We mix into the lambda in the same method to allow our pylons to provide a variable enchanting power, but you use an unconditional cancellable inject (which basically is an @Overwrite but worse) only to use a copy of the vanilla code.

New mixins should work fine

Should be fixed in 1.2.4


feat: add multiline property to Label component

@niktverd  Could you provide link to connected issue/rfc?

@niktverd Could you provide link to connected issue/rfc?

UXRFC-310


Prim's Algorithm | Java

Prim's Algorithm -
A new file to be added demonstrating the Prim's Algorithm -
Type of Issue -

[x] Adding New Code
[ ] Improving Code
[ ] Improving Documentation
[ ] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[ ] Python
[ ] C++
[x] Java
[ ] C
[ ] Go
[ ] Other language

Self Check

Ask for issue assignment before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Happy Coding,

please assign this to me


auction Contract

Auction Smart Contract , it allows users to bid at a certain period of time ,after that auction ends, after auction ends , Amount will be transfer to highest bid contract
Please include a summary of the change and which issue is fixed.
Fixes #112
Type of change
Please delete options that are not relevant. In order to tick the check box just put x inside them for example [x] like this :

[x] Add a new project

Please delete options that are not relevant. In order to tick the check box just put x inside them for example [x] like this

[x] Project using only Solidity

[x] Project Test on the Remix IDE

Checklist ✓
Please delete options that are not relevant. In order to tick the check box just put x inside them for example [x] like this

[x] l have performed a self-review of my own code or work.

[x] I have commented on my code, particularly in hard-to-understand areas.

[x] My changes generate no new warnings

I am Hactoberfest 2022 Contributor
Screenshots/Gif (Recommended)
Compilation with zero warnings

Deploying smart Contract

bidding:

@Vikash-8090-Yadav  The PR is ready to review .

Write brief introduction in the readme about the Auction smart contract

Updated Reamde . Can you e Review it Again @Vikash-8090-Yadav

@saikishore222   where did u write the brief intro ? can u please tell the line number .

Hmm done . @saikishore222  .
Look's great to me  , Your code looks clean and clear .
Happy  Open source :smile:


Firefox,

Just in case it's news:
https://twitter.com/hsinyi71/status/870436875214782464

+1

Right now it's still only in Nightly, I think.

Right now it's marked as "on by default" (non-Nightly) for FF 56+, but in the Mozilla wiki, it says 57+.

This just landed in the stable Firefox 57, so I think this issue can be closed.


Release Best Practices Guide

Purpose

A guide to help make release-making as consistent and automated as possible
PLEASE REVIEW LIVE VERSION HERE: https://github.com/NASA-AMMOS/slim/tree/issue-97/docs/guides/documentation/releases

Help provide feedback in this PR by testing it out on your project!

Proposed Changes

[ADD] A draft guide text
[ADD] A template release.yml file to help make release notes look good and standardized with categories
[ADD] A python script to help aggregate release notes from multiple GitHub repositories into a single file

Issues

#97

Testing

Guide successfully rendered in SLIM docusaurus view (locally)
See template release.yml in action for the SLIM project here: https://github.com/riverma/slim/releases/tag/v1.4.0
Automation release notes aggregation script tested successfully on all SLIM repositories with the following output:$ python gh_aggregate_release_notes.py gh_aggregate_release_notes_config.yml
Downloading release notes: 100%|█████████████████████████████████████████████████████████████| 2/2 [00:00<00:00,  3.47it/s]
# slim-starterkit-python

## What's Changed
* Release Update of Python Starter Kit with Scanning by @ingyhere in https://github.com/NASA-AMMOS/slim-starterkit-python/pull/14
* NASA-AMMOS/slim#89: Functional GitHub Actions-based secrets detection… by @ingyhere in https://github.com/NASA-AMMOS/slim-starterkit-python/pull/10
* NASA-AMMOS/slim#25: Functional GitHub Actions-based SCRUB (CodeQL) analysis... by @ingyhere in https://github.com/NASA-AMMOS/slim-starterkit-python/pull/11
* NASA-AMMOS/slim#110: Functional Pylint static code analysis. ... by @ingyhere in https://github.com/NASA-AMMOS/slim-starterkit-python/pull/12
* Add Governance documentation by @jpl-jengelke in https://github.com/NASA-AMMOS/slim-starterkit-python/pull/9

**Full Changelog**: https://github.com/NASA-AMMOS/slim-starterkit-python/compare/1.0.0...1.0.1

# slim-starterkit

## What's Changed
* Remove duplicate text. Standardize text for link insertion. by @jpl-jengelke in https://github.com/NASA-AMMOS/slim-starterkit/pull/2

## New Contributors
* @jpl-jengelke made their first contribution in https://github.com/NASA-AMMOS/slim-starterkit/pull/2

**Full Changelog**: https://github.com/NASA-AMMOS/slim-starterkit/commits/v1.0.0

@mike-gangl - would this help Unity make releases across many repositories? Let me know what you think.

Received a use case from the OPERA project regarding the following question: how do we safeguard that a super release will include the right versioned repositories?
In other words, can this best practice guide PR help ensure that a particular build or release of many repositories doesn't lead to a situation where the wrong version of a particular repository's code is mixed up with another repository during a super release?
CC @philipjyoon @hhlee445

@mike-gangl - would this help Unity make releases across many repositories? Let me know what you think.

So in terms of unity, we keep a changelog which is where most release notes comes from; thought this can still be very useful- there is a bit of a difference in what goes into a changelog and what we would describe at a system level release (which, in my opinion, is slightly different than these super releases. I can see "super releases" on a service area basis. The System releases, however, would be manually currated and de-jargoned for a slightly different audience.

Recommend using AI/ML to process code commits in addition to commit and PR comments for generating release notes.
There is significant benefit if AI/ML can extract release note information from code from that has not already been captured as a developer comment.

Great idea! Will consider a prompt scenario to support this.
Rishi

From: stirlingalgermissen @.>
Sent: Thursday, July 11, 2024 11:56:26 AM
To: NASA-AMMOS/slim @.>
Cc: Verma, Rishi (US 398B) @.>; Mention @.>
Subject: [EXTERNAL] Re: [NASA-AMMOS/slim] Release Best Practices Guide (PR #149)
Recommend using AI/ML to process code commits in addition to commit and PR comments for generating release notes.
There is significant benefit if AI/ML can extract release note information from code from that has not already been captured as a developer comment.
—
Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https://github.com/NASA-AMMOS/slim/pull/149*issuecomment-2223672415__;Iw!!PvBDto6Hs4WbVuu7!OV9IQiv9KLKLbgpTfGg0oR_EHKxA5kY3SCIKx-TznvhjJwQ8kQ9pfBgfll6M8-MlZiGZDd36yHXoAYqwVWtp2yYNjvyOuA$, or unsubscribehttps://urldefense.us/v3/__https://github.com/notifications/unsubscribe-auth/AAX36LWWZUZ6TI2YT4LGQYTZL3INVAVCNFSM6AAAAABFIE2S7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRTGY3TENBRGU__;!!PvBDto6Hs4WbVuu7!OV9IQiv9KLKLbgpTfGg0oR_EHKxA5kY3SCIKx-TznvhjJwQ8kQ9pfBgfll6M8-MlZiGZDd36yHXoAYqwVWtp2ybCMkpDDA$.
You are receiving this because you were mentioned.Message ID: @.***>


Integrating MegaMedical to train UniverSeg

I have a question regarding how do you integrate a huge dataset like MegaMedical to train UniverSeg.
From your supplementary, you mentioned using LMDB datastores (also related to issue #29) for fast I/O processing via Thunderpack. I am interested in the details as to how Thunderpack is being implemented as part of the training pipeline. Ie:

Do you initialize ThunderDataset with the entire development set of MegaMedical? And if so, how is the dataset class for MegaMedical being implemented?
From your paper Algorithm 1, it seems that the hierarchical task sampling and augmentations are performed online. Can I confirm then that these two steps are done when __getitem__ is called? If so, how is it done?

Thanks for your great work! It would be really helpful if you could share any additional technical details/code regarding the training pipeline., looking forward to hearing from you!

Greetings!
Indeed we did you LMDB stores (publicly available with https://github.com/JJGO/thunderpack) that allowed us to have super fast I/O despite having tons of files. In response to your questions,

Instead of a single LMDB for the entire dataset, we implemented our MegaMedical class object as a collection of LMDBs, one corresponding to each task.

Actually, while these augmentations are done online, we didn't actually do this in our __getitem__ call but rather in the forward loop. What this allows you to do is to perform the augmentations on the GPU rather than CPU (which makes them significantly faster). We used Kornia https://kornia.readthedocs.io/en/v0.4.1/tutorials/data_augmentation.html for this.

Hope this helps!

Thank you for your reply! So during forward, you do you use a conventional dataloader to iteratively load all collection of LMDBs (tasks), or that for each forward loop, only a single LMDB (task) is sampled from the MegaMedical class object? After selecting the task, the query and support data is sampled in the __getitem__ of the LMDBs? And finally, the augmentations are then performed?
Thank you !!

can I also confirm then that during the data processing with MegaMedical, do you perform the augmentation before or after converting the images into greyscale/single-channel? Since some of the augmentations include changing the brightness and contrast. If it was done after, it would have different transformations.
(im assuming here that a conversion to greyscale is done somewhere in the pipeline, since Universeg takes in a single-channel image, and uses the channel dimension for cross convolution)
Thanks for your insights so far, it has been really helpful !!

can I also confirm then that during the data processing with MegaMedical, do you perform the augmentation before or after converting the images into greyscale/single-channel? Since some of the augmentations include changing the brightness and contrast. If it was done after, it would have different transformations.

We converted the images into greyscale/single-channel before training to save doing that during training

Also, when you perform benchmarking with the other models (PANet, ALPNet, SENet and nnUNet), did you also used the greyscaled versions of size (128, 128) across all models for training?

Yep! We made sure that all models trained on the same data.
Let me know if you have any more questions!

Ok, got it, thank you!


dep ensure does not prune automatically by dep ensure

What version of dep are you using (dep version)?

version: v0.5.0
git  hash: 224a564
What dep command did you run?

dep ensure and dep prune
What did you expect to see?
some unused files not exist in vendor
What did you see instead?
Files: *.sh *_test.go *.md LICENSE OWNERS BUILD all exist.
dep prune also does not prune these useless files.

/kind bug

dep prune was merged into dep ensure. Gopkg.toml options now control what should be pruned: https://golang.github.io/dep/docs/Gopkg.toml.html#prune.

Thanks @AlekSi , IC.


Catalog apps should not re-use existing image and tag if the version is upgraded

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Catalog apps should not re-use the existing image and tag if the app version is upgraded.

select the Drone app with app version 1.4.0 and the existing image tag would be 0.8.5
upgrade to v1.7.4 and the default image tag would be 0.8.6, but because there are a default image and image.tag value so the app will still using 0.8.5 image.

Result:
need to upgrade to a newer version of the image and image.tag even if there is a default value in the answers.

Rancher version: master-head (v2.3) (08/22/2019)
Some Catalog apps doesn't update the image tag between App versions. Drone uses a new tag between App versions and is now working fine.
Another example is dask, Installing App 2.0.0 it uses image tag 1.0.0. And upgrading the App to 3.0.0 also upgrades the tag to 1.1.5.
The docker-registry App however if you install 1.4.3 and then make the upgrade to 1.6.1 both has the same image tag 2.6.2.
I don't think we don't have control for the image tag unless the App version explicitly use a new image tag.
But right now when the App version upgrades the the new version has a new image tag is used instead of reusing an existing while I was doing this validation.


Diameter of a Tree || Python

🚀 Feature
(A clear and concise description of what the feature is.)
Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation
This question is very often asked in the interviews. A lot of students think this is an easy question but actually it is very tricky to solve. I would like to work on this problem of Diameter of a Tree in Python.
I would like to work on this issue under WoC and Devscript WoC.

assigned @Pranav016

assigned @Pranav016

assigned @Pranav016

I would be working on this under WoC

assigned @Pranav016

I would be working on this under WoC

Please assign the issue to me I would like to work on this problem of the Diameter of a Tree in Java under DWoC

Please assign the issue to me I would like to work on this problem of the Diameter of a Tree in Java under DWoC

assigned @ankitasantape

assigned @ankitasantape


Add sections specifying use of flux:: and flux_rs:: for files vs. crates

@nilehmann, do we want to replace subsequent examples of refinement annotations using flux:: with flux_rs::?

@vrindisbacher
Yeah, let us change all the examples to use flux_rs otherwise it'd be confusing, because flux:: is not really usable.
I sent you an invite to give you write access to the repo. Main is branch protected so everything has to go through a PR, but I typically accept PRs if I think they are good enough even with remaining comments so people can fix them and then merge at their discretion.

Great. I updated everything.


Fix language detection handling

This has two parts:

The "high level" bug is that inputs don't affect the Tool.lang correctly -- Tool.lang is determined only by the presence of an -x flag or the tool class itself, meaning that blight.CC.lang will always report Lang.C unless -x c++ is passed. This manifests particularly as the wrong lang value for assembly inputs: cc foo.s ought to report Lang.Asm (which doesn't exist yet), but reports Lang.C instead.
The "low level" bug is that Tool.lang is a bad abstraction: a given tool invocation might be handling multiple languages at once, or no languages at all.

 Shorter term, we should try to make its behavior more intuitive (e.g. sniffing file suffixes when available, and presenting a Lang variant based on them).

#43495 would probably help with this but is much larger in scope.


Sync, Async, Postfixes why bother?

The library provides both sync and async versions. Some methods are only available as sync APIs, the sync APIs sometimes reuse async APIs internally and are subjected to deadlocks because of context capturing. Some methods are postfixed with async when they return a task. Sometimes not.
the client is mostly pure IO based using HTTP calls. .NET Framework already moved into pure async APIs with the new HTTP client. Embrace async, make the whole library fully async. Remove the sync wrapper by embracing Async All the way. It's time to move into the async world ;). Get rid of the postfixes, see our reasoning for NServiceBus. This makes the client code and API calls simpler to compose (embracing concurrency and asynchronisity). Synchronization for sync environments is now up to the caller (makes is a top level concern anyway). Your libs becomes simpler to maintain because you write less code. Because you think async first you minimize the risk of using "older" concepts like ThreadAffinity, ThreadLocals ... and design upfront for async (floating state, no more ambient context...)
Btw. Quartz.net is also moving in this direction (I admit I oooh so gently pushed ;) )
https://github.com/quartznet/quartznet/issues/331

Please excuse any naivety in my questions here!
So - on the postfix side of things - it makes sense if the whole library is Async - so that's all good.
In your view - is this a big (as in time to do it) change?
I assume this would be a major version change (semver wise) as Results would now be ResultsAsync and that would cause breaking changes?

Yes it would be a major.
Switching to async only seems to be involved especially on the transaction side of things. The rest seems to be pretty straight forward

Am 20.04.2016 um 12:14 schrieb Chris Skardon<EMAIL_ADDRESS>Please excuse any naivety in my questions here!
So - on the postfix side of things - it makes sense if the whole library is Async - so that's all good.
In your view - is this a big (as in time to do it) change?
I assume this would be a major version change (semver wise) as Results would now be ResultsAsync and that would cause breaking changes?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

Just check if this is still waiting in the queue?

I know this is an old thread, but as a developer who is NOT moving to async everywhere, consider making separate async and sync versions that don't use each other maybe? Async infects code by requiring you to move your functions to async all the way up the chain, and does not work well with threading or callback functions. It's a nightmare to debug. Think MQ libraries, or threaded HTTP/TCP servers - they're already multi threaded, and don't need async.
I know, I know, "async is the big thing, everyone's doing it", but some of us like being able to manage thread pools - our downstream developers don't run GUIs and so don't benefit from async everywhere.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/79685

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/79871

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/80000

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88712


Give user option to restart on page 1 when encountering end of pages

My net is so slow that by the time I get to the last page it's pretty much time to start at the beginning again. (mainly due to missed capcha's and the aggravating necessity of sleep)
Perhaps the program could prompt in the console:   Restart at Page 1 (Y/n):_
with no being the default.   This cuts down on having to deal with the whole 2FA mess again and/or amazon asking for a capcha  (if it's been asking for a capcha on the signin page somehow your program ignores it and continues so as soon as it dies on restart you get the guaranteed capcha you have to enter)
This would also work well in combination with the issue requesting to resume from where it left off since they might be towards the end of the pages.

After #40 is complete I can add this as an option in the config file.

FYI,   When on the last page and it was showing "giveaway not found" I manually clicked it to page 1.   The program kept on chugging and processing sweeps from page 1....the total count displayed however never reset ie page 1 was displayed as MaxPage + 1
Seems like the changes would be minimal to allow restarting at page 1.

I have been thinking about this one in relation to making the bot a little more intelligent.  I would like to introduce a yardstick and database driven approach to determining if it is time to click the bouncy box.
My plan would be to track boxes and when they ripen. When gg goes through all the pages it will go to sleep and wake up and start working again when either a sweep is determined to be mature or the sleep period between site sweeps.  Extremely long term, I would hope to introduce some sort of Machine Learning to help determine when a sweep should be considered "ripe" based on when similar sweeps were considered won or expired.
However, this enhancement would be a great first step.  I will type up the data driven approach sometime over the next couple of days.   Especially now that the config file enhancement is done and in the wild.


Yet another OAuth scope to add to the table

Thanks again!

You're welcome. By the way, there might be more.

Yes, if I'm correct these are what's left:
account, history, livemanage, modcontributors, modself, wikiedit
I'm going to start checking the methods for each one and make sure they have the right scope decorators. I've just been putting it off.

Yes, if I'm correct these are what's left:
account, history, livemanage, modcontributors, modself, wikiedit

Yeah, I'm working on adding those, too.

I'm going to start checking the methods for each one and make sure they have the right scope decorators. I've just been putting it off.

I seem to have found some problems in internal.py. See PR #451.


Add KafkaStreams customizers and wrapper configurer for StreamsBuilderFactoryBean.

Addresses https://github.com/spring-projects/spring-kafka/issues/621

@nyilmaz Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@nyilmaz Thank you for signing the Contributor License Agreement!

Merged as https://github.com/spring-projects/spring-kafka/commit/e77e1efbc5ef9c27d6aa50d8a7c1e9fd9962b516.
@nyilmaz ,
Thank you for contribution.
Looking forward for more!


Native Support for LDAP

I can't figure out a good way to get LDAP supported with this module. If I enable it myself then the CLI tool stops working.

@tedivm what do you mean "LDAP support"? What functionality would that enable for you?
I'm not using Jenkins with LDAP and while I'm aware of how that works inside of the Jenkins context, I'm not sure I understand what you're asking for here

LDAP authentication. I want to define a set of LDAP attributes in my puppet config, so when a jenkins host rolls up the only people who can access it are those in my directory and with the attributes I defined.
The other issue I have is that once I setup LDAP the CLI tool stops working. Resolving this is a matter of adding a user into ldap for CLI and the running the --login option to save those parameters. It would be nice if it was possible to specify credentials for the user via puppet (just for the command line, I'm not expecting this module to modify ldap).

This is so much needed

See: https://issues.jenkins-ci.org/browse/JENKINS-15063  TL;DR when using the ldap plugin, the jenkins admin ssh private key credentials must be in ldap.

I extended the puppet_helper.groovy to support ldap configuration.  This is my first groovy code ever, so i need to beautify the code a lot.  But it works executing the 'actions' the same way as the jenkins::cli::exec.
I'm looking for some comments/advice cmcerning my code.  One can the ldap piece here : https://gist.github.com/witjoh/c01a7c24fc9e100c6c1bc5a65d79f649
Since the ldap is now a jenkins plugin, I'm looking for a way to put the code specific for a plugin in its own groovy file, that in a way extends the main puppet_helper classes.
When i get may code cleaner, I can crfeate a pull request.   but now I will try to use the ldap groovy code in some puppet code.   And maybe when i'm in a crazy mood add some new type/providers for it.
In the meantime waiting for some feedback/guidance
Thx


server__port env value seems not working

I'm trying to change the default port with the latest Ghost image:
docker run -d --name some-ghost -e NODE_ENV=development -e url=http://localhost:3001 -e server__port=2355 -p 3001:2355 ghost
and the running result seems still using the port 2368:
CONTAINER ID   IMAGE     COMMAND                  CREATED         STATUS         PORTS                              NAMES
f2d85a146c8f   ghost     "docker-entrypoint.s…"   3 seconds ago   Up 2 seconds   2368/tcp, <IP_ADDRESS>:3001->2355/tcp   some-ghost

That's due to the EXPOSE directive in the original Dockerfile, and should be totally safe to ignore (the container shouldn't actually be using 2368 in your configuration).


Output the exact verses in each chapter

Output a CSV with the total as well as the verse number
Chaper Name, Total, Verse Num
2, 6, 2.04,2.05,2.06,2.07,2.08,2.54

Fixed in https://github.com/suresh-srinivas/arjuna-uvacha/commit/0d76baa7b5280c45d9c604ac6d35b262047cad88
Chapter 1: ['1.21', '1.22', '1.23', '1.28', '1.29', '1.30', '1.31', '1.32', '1.33', '1.34', '1.35', '1.36', '1.37', '1.38', '1.39', '1.40', '1.41', '1.42', '1.43', '1.44', '1.45', '1.46']
Chapter 2: ['2.04', '2.05', '2.06', '2.07', '2.08', '2.54']
Chapter 3: ['3.01', '3.02', '3.36']
Chapter 4: ['4.04']
Chapter 5: ['5.01']
Chapter 6: ['6.33', '6.34', '6.37', '6.38', '6.39']
Chapter 8: ['8.01', '8.02']
Chapter 10: ['10.12', '10.13', '10.14', '10.15', '10.16', '10.17', '10.18']
Chapter 11: ['11.01', '11.02', '11.03', '11.04', '11.15', '11.16', '11.17', '11.18', '11.19', '11.20', '11.21', '11.22', '11.23', '11.24', '11.25', '11.26', '11.27', '11.28', '11.29', '11.30', '11.31', '11.36', '11.37', '11.38', '11.39', '11.40', '11.41', '11.42', '11.43', '11.44', '11.45', '11.46', '11.51']
Chapter 12: ['12.01']
Chapter 14: ['14.21']
Chapter 17: ['17.01']
Chapter 18: ['18.01', '18.73']
Chapter-wise count: {1: 22, 2: 6, 3: 3, 4: 1, 5: 1, 6: 5, 8: 2, 10: 7, 11: 33, 12: 1, 14: 1, 17: 1, 18: 2}
Total verses by Arjuna: 85

In main


Cleanup: Delete unnecessary outdated modules

Although some modules have already been removed from the software (e.g. https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/888), some other outdated modules are still present (such as the "Game" module).
pH7CMS has to be more "lightweight" and "minimalist". We don't want unnecessary modules that no one uses.

Let's do it on screencast!

It has been done here: https://github.com/pH7Software/pH7-Social-Dating-CMS/pull/947


Seconds circle and steps freezing and not updating

Hello,
I’ve been using this clock for the last 8 or 9 months and recently the seconds circle and step count freezes at a certain point in the day and the display doesn’t update.
The device is still counting steps but the display doesn’t update. I’ve shut down the device and restarted which temporarily fixes the issue but the next day or later that day it freezes again.
This only started a few weeks ago. Everything seems to stay updated and function fine.
Any thoughts?
thanks!
hilary

I am having the same issue - will  you be able to provide an update?

Sure! I haven’t heard anything yet. What has helped is shutting it down and the restarting. But it’s only temporary, that can last anywhere from 1 day to maybe a week and then it freezes again. I’ve done a factory reset which helped for a while but eventually it froze. Done a few updates but the freeze keeps coming back.


HORRIBLE BUG: The plugin-publish plugin is not documented to be closed-source proprietary software

HORRIBLE BUG:
The plugin-publish plugin is not documented to be closed-source proprietary software. The Gradle ecosystem is supposedly free software. The documentation for the plugin-publish plugin is integrated with the rest of the Gradle docs, essentially making users believe that it is trustworthy free software, and leading them to run dangerous and non-free software in their local machines.
The license for this software and its closed-source status should be clearly stated in the docs, so that users can avoid the dangers of non-free software and can comply with entity policies that avoid dependence on non-free software and services.
Now that you already messed up, you REALLY should publish source ASAP. In the meantime, you should clearly warn users about the proprietary nature of this plugin.

Maybe you should try it with a more friendly tone and asking for what you want
instead of using very rude language and demanding what you have no rights for?
The guys at Gradle are doing a great job delivering the best build tool I have ever seen.
Also just that something is closed source does not at all mean it is in any way dangerous.
And at the same time, just that something is open source does not at all mean it is in any way safe.
If they decide to have that plugin being closed-source, that's fine, they have the copyright and can do what they want and they surely have reasons to not open-source that plugin.
You are maybe right, that they could communicate it better.
But then, it is not documented inside the normal Userguide that describes the open-source Gradle.
It is just included in a Guide that shows how to publish to plugin central which you don't have to use if you don't want to.

ranting is a common means of expression in developer forums. just take a peek into the devel mailing list of the linux kernel for fun. (developers are known for caring more about ideas and less about "feelings".)
rants express frustration and/or anger which exactly express how i feel.
i want to express anger, not a technical problem with a plugin. because i was TRICKED into running non-free software on my systems, a thing that i don't want to do irrespective of all your opinions regarding the "safety" of software. rest assured if the closed-source nature of that software was mentioned ANYWHERE AT ALL, i wouldn't have fallen for that trick.
i'm also angered because i was tricked into LEARNING how to use proprietary tools, which is something i ABSOLUTELY NEVER DO. my investment only happens in free tools: tools that I OWN AND CANNOT BE TAKEN AWAY OR USED TO CONTROL ME.
in essence, i was tricked into INVESTING (my time) in gradle when i didn't want to. and it was not lack of due diligence on my part.
some people may be more careful around gradle if they choose to behave this way. others (like me) tend to sever ties when tricked. that is why i will NEVER be part, for instance, of the .NET ecosystem (which is free as in freedom and technically sound): microsoft breached my trust and they lost me; no amount of promises or turd polishing will have me eating their crap again.
regarding the tone: yes, it's harsh maybe, it's also free speech. the tone is there to alert gradle that this kind of thing is serious for some people.
the whole point is that this issue is trivial and easily prevented. there's nothing trade secret in the plugin, no reason not to publish. conversely, it wouldn't have negatively impacted gradle to document the non-free nature of the plugin portal and its plugin. so why did it happen? because no one in gradle thinks this is an issue. this issue is about changing that. gradle: don't shoot yourselves in the foot for no gain at all!
regarding you: were you offended by the tone? i don't care, being offended is your problem. please keep it out of here if possible, this issue is not about you (or me). you remind me of religious people that get offended by my atheist speech. so what? as richard dawkings says: i'm offended by people who chew gum. so what? and yes, like you, religious people also try to censor me.
but due to your msg i'll state one thing here (which should be obvious because all tracker issues are here to help):
gradle: don't get frustrated by issues like this; get better instead. keep on getting better.
so to recap:
you can argue.
and i can too.
but i was still tricked into using proprietary software against my will.

Well said @Vampire. I believe this issue should be close as it stands and instead split it into more actionable steps.

An issue on gradle/plugin-portal-request should be open regarding clarifying the language around the plugin-publish plugin licenses. Most likely here, here and here.
A different issue should be open on gradle/plugin-portal-request regarding open-sourcing the plugin-publish. There were some talk internally that the plugin is essentially open-source but doesn't have any public repository as a home.
Another issue should be open on gradle/plugin-portal-request for having the option to explicitly declare a plugin as open-source or not and under which license. If my memory serves me right, the plugin portal started off as "assuming" all plugins are open-sourced but nothing enforced this assumption. At this time, there are closed-source and open-source plugin on the portal. It should be clearer for the user to know which one is which. It's also important to mention how it affects the users. A closed source plugin isn't making the users accountable for anything except if you uber-jar the plugin inside your own at which point the licensing is important.
Finally, another issue should be open on gradle/plugin-portal-request to groom the published plugins for any unsafe behaviour to avoid obviously malicious plugins. This feature is a rabbit hole as malicious activity in a plugin can be hard to detect. I believe passing all plugins through a Virus Total scan could be good enough for a "obviously malicious" check.

It's important to keep in mind the Gradle code of conduct for the issue tracking and any other resource of the Gradle community.

#response_container_BBPPID{font-family: initial; font-size:initial; color: initial;}  Open source != free.Free != open source.Closed source != !free.Omission != trickery.Documentation issue != product bug.Proprietary = protection of intellectual property.Rant is only as valid as what it claims, otherwise it is just noise. You are using and running (maybe even making) closed source systems all around you. Some are built using Gradle. Some free open-source products are built using Gradle.You may view publicly reviewed code as better in some respects but you have to appreciate that some things put food on people's tables and need to be protected.      Learner Evermore                                                                                From<EMAIL_ADDRESS>June 29, 2020 10:13 a.m.To<EMAIL_ADDRESS>to<EMAIL_ADDRESS><EMAIL_ADDRESS>Re: [gradle/gradle] HORRIBLE BUG: The plugin-publish plugin is not documented to be closed-source proprietary software (#13544)
ranting is a common means of expression in developer forums. just take a peek into the devel mailing list of the linux kernel for fun. (developers are known for caring more about ideas and less about "feelings".)
rants express frustration and/or anger which exactly express how i feel.
i want to express anger, not a technical problem with a plugin. because i was TRICKED into running non-free software on my systems, a thing that i don't want to do irrespective of all your opinions regarding the "safety" of software. rest assured if the closed-source nature of that software was mentioned ANYWHERE AT ALL, i wouldn't have fallen for that trick.
i'm also angered because i was tricked into LEARNING how to use proprietary tools, which is something i ABSOLUTELY NEVER DO. my investment only happens in free tools: tools that I OWN AND CANNOT BE TAKEN AWAY OR USED TO CONTROL ME.
in essence, i was tricked into INVESTING (my time) in gradle when i didn't want to. and it was not lack of due diligence on my part.
some people may be more careful around gradle if they choose to behave this way. others (like me) tend to sever ties when tricked. that is why i will NEVER be part, for instance, of the .NET ecosystem (which is free as in freedom and technically sound): microsoft breached my trust and they lost me; no amount of promises or turd polishing will have me eating their crap again.
regarding the tone: yes, it's harsh maybe, it's also free speech. the tone is there to alert gradle that this kind of thing is serious for some people.
the whole point is that this issue is trivial and easily prevented. there's nothing trade secret in the plugin, no reason not to publish. conversely, it wouldn't have negatively impacted gradle to document the non-free nature of the plugin portal and its plugin. so why did it happen? because no one in gradle thinks this is an issue. this issue is about changing that. gradle: don't shoot yourselves in the foot for no gain at all!
regarding you: were you offended by the tone? i don't care, being offended is your problem. please keep it out of here if possible, this issue is not about you (or me). you remind me of religious people that get offended by my atheist speech. so what? as richard dawkings says: i'm offended by people who chew gum. so what? and yes, like you, religious people also try to censor me.
but due to your msg i'll state one thing here (which should be obvious because all tracker issues are here to help):
gradle: don't get frustrated by issues like this; get better instead. keep on getting better.
so to recap:
you can argue.
and i can too.
but i was still tricked into using proprietary software against my will.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.

@Lanchon : There are multiple ways of asking for things.
Being demanding, entitled and rude when asking for FREE stuff is not the way to go.
People have no obligation to do work. for you or anyone else for that matter.
If you don't like it, express your disapproval and either propose an alternative or use something else that better suits your requirements.
I don't imagine there is a conspiracy to conquer the world using the proprietary plugin-publish .

the plugin portal started off as "assuming" all plugins are open-sourced but nothing enforced this assumption

the current policy is that proprietary closed-source plugins can be published to the portal.
malicious build scripts will happen sooner or later. gradle may want to keep overt closed source plugins out of the portal to increase transparency. companies could still make their secret plugins, they'd just need to host them elsewhere.
repos like f-droid build the stuff they publish themselves and save the source tarball, so you can always access the source of any given version of anything there. of course the source can just pull in a jar with closed source software, but at least that's easy to see. upon detection of such a thing, you'd ban the plugin. the point is that at least those cases can be detected if you look into them.
maybe there's a way to integrate some CI service to do the plugin building for you. just a thought

If you don't like it, express your disapproval and either propose an alternative or use something else that better suits your requirements.

have you read the thread? my point is that i was tricked into using this. it is NOT DOCUMENTED not to be free. so are we suppose to ask before using any feature of gradle: hey is this free "too"? are we supposed to clone the source repo and, before using a feature, double check that the source is there? are we supposed to know how the project is split in repos before using it?
gradle dropped the ball on this. and it's a good thing @lacasseio is acknowledging this and proposing to fix it. it gets fixed? good! i shouldn't ask for this to get fixed? nope, disagree.

People have no obligation to do work. for you or anyone else for that matter.

and you are stating the obvious: everybody knows that people have no obligation of fixing bugs reported in a tracker, including you and me. trackers are still used and work.
jeez! end of being trolled here. no more replies of this kind from me.

I've closed this issue and blocked @Lanchon because of repeated violations of the code of conduct in this issue tracker.
It would be appreciated if someone could create a new issue(s) for this using appropriate language.

This will be my last message to this thread, just to clarify some things you said.
Rants belong to blogs, not to an issue tracker.
If you participate in a community you should follow its code of conduct which you clearly did not do. And even if no code of conduct is defined, you should follow the Netiquette which you also didn't do.
The only thing you gain with such a post as here is to pester the athmosphere of the community.
There are people like Linus that can allow themselves to be gits (his words, not mine), but for most people this is not an acceptable behaviour.
Also you were not tricked into anything.
If you have that strong feelings about closed source software, you need to put more effort in ensuring you only use open source software.
If you for example go to the plugin page on the plugin portal (https://plugins.gradle.org/plugin/com.gradle.plugin-publish) you can see that its id is starting with com.gradle., not org.gradle. and gradle.com is the domain for the closed source Gradle enterprise package opposed to gradle.org which is for the open source part.
Also for each plugin in the portal you find a link to its homepage, in case of the plugin-publish it is https://plugins.gradle.org/docs/publish-plugin and nowhere on that page is any link to the source code.
So yes, the documentation could clearer state that it is not open source, but there is no sign at all that says "this is open source" which I would agree to be tricking you into using it. You just didn't verify enough yourself and request a change in documentation to make it clearer and easier to see. But there is objectively no tricking to complain about.
Freedom of speech is a principle that supports the freedom of an individual or a community to articulate their opinions and ideas without fear of retaliation, censorship, or legal sanction. Freedom of speech does not mean that you can say whatever you like to whomever you like.
I was not actually offended by the tone, no.
I just think that this is not how people should talk to each other.
And I think that this is not how the people at Gradle deserve to be talked to for providing an amazing tool for free to the world.
And actually, I did not try to censor you.
You can write anything you like in any tone you like, if you can cope with you being ignored or deleted or however Gradle guys will handle the violation of code of conduct.
What I wanted to achieve was helping you being heard and get your issue resolved.
I just advised you on how to improve your communication to actually reach your goal.
If getting the issue fixed actually is your goal that is.
If just pissing people was your goal, then your post was probably appropriate.
Whether you think about what I said or not and whether you heed it in the future
or not is of course totally up to you.

@Vampire @lacasseio @ieugen Thanks for pushing back on this kind of language.


Add luisApplicationId parameter to CICD pipeline

Fixes #minor
Proposed Changes
That parameter deploys the luis__applicationId configuration setting to Azure, which is required for bots using LUIS to work.

Apparently luis__applicationId is NOT needed. Another test deploy without it, and the bot works. ??


Destinations: add configuration set subcommand

Motivation:
To update destinations configuration we need a new subcommand to complement existing configuration show and configuration reset subcommands.
Modifications:
Added new SetConfiguration type with the implementation. Additionally, new ConfigurationCommand protocol was added that inherits from and extends DestinationCommand protocol to provide configuration-specific properties and arguments. This new protocol is used to reuse common configuration code.
Also improved logging in ResetConfiguration to make it clear which properties were reset.
Result:
Users can run swift experimental-destination configuration set subcommand to customize properties of installed destinations.

@swift-ci smoke test

@swift-ci test Windows

@swift-ci test Windows


Issue in onFocus while copy pasting a normal text in date picker

Steps:

Select a valid date from the date picker or enter it manually in the field.
Copy some text.
Use the mouse to select the date in the date picker field.
Paste the copied text into the date picker field and observe that the value becomes null, but upon focusing on the picker, the previously selected date is visible.

Expected: In this scenario, when focusing on the field, it should be empty since the value has become null.

Hello @Nithinmon-D. This package has long been out of maintenance.
Please find the important information here.
We highly encourage you to start using @mui/x-date-pickers.
You can start here, then migrate to @mui/x-date-pickers@v5 using this guide and consider spending time to bump your usage to at least v6 (current LTS) with this guide.


Raycast ignores RigidBody's children when colliding with bodies

Godot version
4.1.1
System information
WIndows 11
Issue description
I have a rigid body with multiple child nodes - each od them has mash and collider.
I am using a raycast to detect a child inside that rigid body.
But, it only detects the rigid body (parent) and ignores its children.
I tried to change raycast collision mask and children’s collision layer, but it didn’t work - it works if I set “Collide with: Areas”, but it doesn’t work on “Collide with: Bodies”. I think that is a bug.
Steps to reproduce

Open attached project
Run the game and nothing will be printed in the console (children ignored)
On player raycast switch "Collide with: Bodies" to "Collide with: Areas"
Run the game and child area name with be printed (children not ignored)

Minimal reproduction project
CollisionIssue.zip

Collision object only work when directly under a body, are you not getting a warning in the editor?

This is not a bug but the way the code works currently, there is a proposal for changing this:

https://github.com/godotengine/godot-proposals/issues/535

This is not a problem, collider is directly under the RigidBody3D. The issue is that raycast is not detecting it, but can only detect Areas.

Does it work if you change collision_layer of the RigidBody to 1? Or change the collision_mask of the ray cast to 2?

After updating the layers to be correct it works fine for me

I tried differant combinations. If they metch like you wrote the RigidBody is detected.
But, I'm trying to detect it's children (Child1, Child2). If I match Raycast mask with children layers it still doesn't work.

What children layers? The detection is the body, not the collision shapes.

The specifics here could be documented more clearly, but there's no bug here

Ok thank you! The code you provided is working, so it's not a bug. I didn't know that CollisionShape3D is not recognized as a body. Can I add any other node inside the RigidBody that will be recognized as a body?

You can, but it kind of defeats the purpose, you are colliding with bodies, will make a documentation update to help with this.

So, for example if I'm shooting RigidBody3D car and I want to know that I hit the "door", not just a "car" I have to use your 3 lines of code and there is no other simpler way? Sorry I'm coming from Unity3D, maybe I'm thinking too much from the Unity user prespective :)

That's the simple way :)

You can open a proposal if one isn't opened already to suggest adding this method to RayCast2D/3D as a convenience

Correction, the full code is:
var target = raycast.get_collider()
var shape_id = raycast.get_collider_shape()
var owner_id = target.shape_find_owner(shape_id)
var shape = target.shape_owner_get_owner(owner_id)

largely the same I believe, but to be fully clear

Great, thank you again for your time and all the help!
I apologize for misunderstanding and reporting it as a bug.

No worries! It brought to attention the limited documentation


Consider using monoid action

Time differences act on times as a monoid action: https://hackage.haskell.org/package/monoid-extras-0.6.1/docs/Data-Monoid-Action.html
In fact, they do a bit more than that. The action is invertible because we can take the difference of two timestamps. So it's a transitive group action.  There exists a group package: https://hackage.haskell.org/package/groups but there is no action class, and no transitivity.

See https://github.com/Taneb/groups/issues/15

https://github.com/diagrams/monoid-extras/issues/53


Tests of .arch

This adds full test coverage of the existing the logic of ChildProcess.arch. Mocked responses are used to allow continuing to support historical platform oddities without having to reproduce those platform environments.

Coverage increased (+1.5%) to 94.567% when pulling a2e9bb42e9e9d496c68b1e734fb3dd110e4ec573 on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

Coverage increased (+1.5%) to 94.567% when pulling a2e9bb42e9e9d496c68b1e734fb3dd110e4ec573 on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

Coverage increased (+1.5%) to 94.567% when pulling a2e9bb42e9e9d496c68b1e734fb3dd110e4ec573 on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

@enkessler Whoops, looks like I used too-modern ruby syntax in the tests for the versions of ruby supported here. I'll push syntax compatibility revision.

The first broken build on the new CI. We're getting value return already. ;)

Coverage increased (+1.4%) to 94.453% when pulling f07cef861cae39bb614ad2076cde250c7ee41bd1 on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

Coverage increased (+1.4%) to 94.453% when pulling f07cef861cae39bb614ad2076cde250c7ee41bd1 on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

Coverage increased (+1.4%) to 94.453% when pulling f07cef861cae39bb614ad2076cde250c7ee41bd1 on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

Coverage increased (+1.5%) to 94.575% when pulling 5759a8ad2a178621a244437eccfb51d3bf104e6c on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

Coverage increased (+1.5%) to 94.575% when pulling 5759a8ad2a178621a244437eccfb51d3bf104e6c on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

Coverage increased (+1.5%) to 94.575% when pulling 5759a8ad2a178621a244437eccfb51d3bf104e6c on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

Coverage increased (+1.5%) to 94.575% when pulling 7c426d97bea50e720332de3008dbff0b27e367ea on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

@enkessler ok, here's test coverage of all logic in arch detection.

Sorry for the silence. I've never used the code review tool before and I am guessing that you haven't been seeing my comment from days ago until just now. But, yeah, I am thinking that we can do without the Ruby version check.

Coverage increased (+1.5%) to 94.587% when pulling 015f8cce869a70827830874c0401fd0b037a6673 on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

Coverage increased (+1.5%) to 94.587% when pulling 015f8cce869a70827830874c0401fd0b037a6673 on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

Coverage increased (+1.5%) to 94.587% when pulling 015f8cce869a70827830874c0401fd0b037a6673 on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

@ms-ati Take out the Ruby versions checking stuff and this should be good to go.

Back to you @enkessler

Coverage increased (+1.5%) to 94.543% when pulling e948377bc60b4a56ec52812f507a1e75022f10c1 on ms-ati:test-arch-detection into 2aa19af1d058b8a12ff29098d788043e2a454db1 on enkessler:dev.

Note: the Travis CI output is misleading. One build is marked as failed (jruby on os x) because the worker appears to have timed out, but you can see in the output that the tests actually passed: https://travis-ci.org/enkessler/childprocess/jobs/203832681

Yeah, JRuby is fragile. I'll take a look tonight.

Anything else to do here?

Nope. I'm merging it now.


Update Swift Language version to 4.2 under build settings

Update Swift Language version to 4.2 under build settings.
Update SnapKit podspec swift version.

I think need to also bump version in podspec and maybe mention in Readme that this version is Swift 4.2

@ibrahimkteish Trouble to update, please~

Releeeease it please! 🚀  :)

@robertjpayne Pretty please, one more PR about this warning so we can have 0 warnings projects again :)

Any update on this?


Covariance data handled incorrectly in unSupervisedLearning

Issue Description
What did you expect to see happen?
That cov(x,y) == cov(y,x), but instead they are very different numbers.
What did you see instead?
cov(x,y) and cov(y,x), are very different numbers.
Do you have a suggested fix for the development team?
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.
Note that you have to add a print statement to see both covariance's:
framework/PostProcessors/TemporalDataMiningPostProcessor/Clustering.GaussianMixture
framework/PostProcessors/DataMiningPostProcessor/Clustering.GaussianMixture

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[ ] 1. Is it tagged with a type: defect or task?
[ ] 2. Is it tagged with a priority: critical, normal or minor?
[ ] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[ ] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[ ] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[ ] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

Note that this was partially fixed for covariance type full, but not fixed for type diag.  See XXX comment in framework/unSupervisedLearning.py


Caption using Coca instead of BLIP

Now that we have open-sourced COCA which is SOTA at image captioning, I think it's better to use it instead of BLIP.
https://huggingface.co/spaces/laion/CoCa

Git still better for some things. Git and Coca are almost the same now.

Thank you!, i'll consider to add that in the future updates, but for now i'll revert Git fo blip because of slower inference


[Doc] Link for MessageListener interface is broken

Search before asking

[X] I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?
Step 1: Naviagate to the link (https://pulsar.apache.org/docs/2.11.x/concepts-messaging/#listeners)
Step 2: Click on the hyper link associated with the text 'MesssageListener', you will see a '404 Not Found' message
What is your suggestion?
Update the hyper link correctly
Any reference?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Fixed. See https://github.com/apache/pulsar-site/pull/533#discussion_r1174491831 for more details if interested.


Master

Hi, your works are great.
I am a  Master in china, i Want a State Machine/hybrid automata described in Modelica 3.3.
so, when it will be released?
I am looking forward to your reply, thanks.

This is just a mirror that does not accept any pull requests.


Example index.html renders blank page

Hello there,
I just stumbled across this awesome project, and I decided to check out the example you provided in your README. I cloned the project, opened the provided example index.html with Google Chrome, and it returned a blank page.
Screenshot of rendered example

I am not sure if I am just missing something or if there are some additional steps I need to run/implement. I  realize this project is still a WIP so if this is the expected output, please let me know.
Thank you again for your time and help, and a great day!
Best regards,
Skyler Kuhn

Hey there,
Thanks for reporting this issue, it's just been fixed with #149. Sorry for the trouble!

Sweet, thank you for looking into the issue. I appreciate it!

@biharygergo I just cloned the repo again, and I am still observing the same behavior.

The example/index.html is an example for how this could be used as a web component, but it doesn't run on its own. You'll need to build/bundle the component and reference it in a script tag to the example file to run it locally.
A better way to test this is to run pnpm install and ng serve to spin up the local development environment and see the graph in action. If you need to use this as a web-component, the react example here should give you some pointers: https://github.com/biharygergo/workflow-graph-example-react
Note that the version released on NPM is not always up-to-date (it currently isn't).

@biharygergo Okay, that sounds good!
I was thinking the example index.html was a self-contained (all resources embedded), static HTML file that I could just open with Chrome and check out.
Would it be possible to create something like that and host it on GH pages? It would be nice for anyone that stumbles across this project.