terser mangle is breaking js on fresh laravel install

Laravel Mix Version: 4.0.15
Node Version (node -v): 8.12.0
NPM Version (npm -v): 6.4.1
OS: ubuntu

Description:
Laravel 5.8 fresh install, enabling vue example component, and then enabling mangle in mix causing js to break.
Steps To Reproduce:
install a fresh laravel project
run npm install / yarn
inside  \resources\views\welcome.blade.php
delete the body content and add:
<div id="app">
        <example-component></example-component>
    </div>
<script src="js/app.js"></script>
inside webpack.mix.js
add options:
mix.options({
terser:{
terserOptions:{
mangle:{
//properties:{}
}
}
}
});
now if you run npm run dev and npm run prod both work fine and load the page,
when you uncomment the properties:
mix.options({
terser:{
terserOptions:{
mangle:{
properties:{}
}
}
}
});
the npm run prod build successful,
the js code breaks:
Uncaught TypeError: Cannot set property 'placeholder' of undefined
at app.js:1
at Kn (app.js:1)
at t (app.js:1)
i have traced this error to loadash code,
but couldn't fix this,
i have tried with debug enabled, but didn't get any help from it.
also tried keep_quoted true, but didn't change anything.

this unmangled loadash code  does work when running npm run dev:
arrayEach(['bind', 'bindKey', 'curry', 'curryRight', 'partial', 'partialRight'], function(methodName) {
lodash[methodName].placeholder = lodash;
});
but when running npm run prod,
it breaks inside the loop on the bindKey string,
i tried to add it to the reserved array,
then it breaks on the next string,
i tried to add the entire array to reserved,
and then the error was too broad to trace.

Why don't you report this issue here
https://github.com/terser-js/terser

because i am not sure from where the problem is.
is there a way to mangle out of the box?


feat: drag-drop

Looks like this contains my commit from the other PR adding the event to onButtonClick


[Background Sounds] "Something went wrong" while trying to turn background sounds on

Extension
https://www.raycast.com/SebDanielsson/background-sounds
Raycast Version
1.83.1
macOS Version
Sonoma 14.6.1
Description
Error:
Error: Command failed with exit code 1: osascript
Background sound is on
Background sounds turned off
757:788: execution error: No matching processes belonging to you were found (1)

Background sound is on
Background sounds turned off
O9:run-applescript.js:38:21

---
35:         timedOut,
36:         command: "osascript",
37:         options,
38:         parentError: new Error(),
39:     })

### Steps To Reproduce

Just toggle the background noise to off, and then on

### Current Behaviour

_No response_

### Expected Behaviour

It shouldn't throw the error, but rather toggle the background sound

Duplicate of #14126
@raycastbot close this issue


DNS Record - Authorize Marketing Tool

Marketing and Communications would like the following DNS record entered for eosnetwork.com to authorize one of their tools to send emails from<EMAIL_ADDRESS>NAME scph0823._domainkey
TYPE TXT
VALUE v=DKIM1; k=rsa; h=sha256; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC4tXAIvUiae0mMLL2FE4V5pxehsZ83NIAp1KrIAFGaUZSXxTYod/xk8NVHvM++yY1vkXA7DC5hwawSV1feb1QzWmFUcKu7x8QjT5tIVoxbZJKHQb+rRO7zkGKKd1D9Cp444uG9OS9tFMuUrjpTTt7bRi6i0OA1D9h8042NXq+CvwIDAQAB

Do the thing.

Done.


PermissionError: [WinError 5] Access is denied

How Fix?

it's a full error if u can help me
Traceback (most recent call last):
File "E:\FastAPI\FastOcrThNationcard\main.py", line 7, in
result = reader.extract_front_info("E:/FastAPI/FastOcrThNationcard/front.jpg")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "E:\Automate\Vene\Lib\site-packages\ThaiPersonalCardExtract\PersonalCard\PersonalCard.py", line 231, in extract_front_info
return self.__extractItems()
^^^^^^^^^^^^^^^^^^^^^
File "E:\Automate\Vene\Lib\site-packages\ThaiPersonalCardExtract\PersonalCard\PersonalCard.py", line 174, in __extractItems
" ".join(pytesseract.image_to_string(imgCrop, lang=box["lang"].split(",")[0],
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "E:\Automate\Vene\Lib\site-packages\pytesseract\pytesseract.py", line 423, in image_to_string
return {
^
File "E:\Automate\Vene\Lib\site-packages\pytesseract\pytesseract.py", line 426, in
Output.STRING: lambda: run_and_get_output(*args),
^^^^^^^^^^^^^^^^^^^^^^^^^
File "E:\Automate\Vene\Lib\site-packages\pytesseract\pytesseract.py", line 288, in run_and_get_output
run_tesseract(**kwargs)
File "E:\Automate\Vene\Lib\site-packages\pytesseract\pytesseract.py", line 255, in run_tesseract
proc = subprocess.Popen(cmd_args, **subprocess_args())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Nosf3ratu\AppData\Local\Programs\Python\Python311\Lib\subprocess.py", line 1024, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\Nosf3ratu\AppData\Local\Programs\Python\Python311\Lib\subprocess.py", line 1493, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PermissionError: [WinError 5] Access is denied

What is IDE tools that you use?
Seems the error message about can’t read your image because don’t have permission on that path.

ok I can fix it because tesseract_cmd is the wrong path now I have a new question
why when I use extract_back_info when I print result i have respond like this
Card(Identification_Number='', FullNameTH='', PrefixTH='', NameTH='', LastNameTH='', PrefixEN='', NameEN='', LastNameEN='', BirthdayTH='', BirthdayEN='', Religion='', Address='', DateOfIssueTH='', DateOfIssueEN='', DateOfExpiryTH='', DateOfExpiryEN='', LaserCode='')
this is my code:
reader = PersonalCard(lang="mix", tesseract_cmd="C:\Program Files\Tesseract-OCR\tesseract.exe", sift_rate=50000)
result = reader.extract_back_info("E:/FastAPI/FastOcrThNationcard/front.jpg")
print(result)

Hi
Kindly try sample image that in test folder to make sure script able to extract data. If the result of this try is work. I think your image might has very large size that we recommend. Or you can increase KEYPOINT value  to cover your image mapping point.

but your sample image does not have back info

Please try change LAG from mix to eng


CLI golden tests for common command usage

Issue Number

#357
Overview

[x] I have transformed the comments in the CLI module about usage into executable specifications

Comments

The idea is to get some sort of visual golden tests to help us keep track of the CLI looks like and if it's not getting out of hands.

I agree with the goal "don't let the CLI get out of control", but not fond of the mechanism used here.
Maintaining the golden strings in this way is going to be a pain.
Golden tests ensure that the help text won't change -- not even a single whitespace character is allowed to change. This is not what we want. We want a qualitative judgement about whether the CLI is sensible (i.e. "not getting out of hands").
Why don't we generate a man page style document from the CLI and upload it to the web site through CI. There are multiple ways of doing this, and the solution doesn't need to be highly sophisticated. Then QA can compare the man page between releases and assess whether it is suitable.

@rvl wrote:

Maintaining the golden strings in this way is going to be a pain.

If we think it's a pain to maintain strings this way, then perhaps we can follow the approach used in hspec-golden-aeson, where expected results are stored in version-controlled files?
When running the tests, we compare each expected output with the contents of the appropriate file. If a given output is unexpected, then the test suite overwrites the appropriate file. On test failure, we can check trivially to see whether it's a "real" failure. If not, then we can commit the new versions and carry on.
What do you think?

@rvl @jonathanknowles
I tend to agree with @rvl on that. This is going to be cumbersome to maintain, and we need to make sure that we keep an eye on it actually. I already imagine people updating things without much considerations (by lack of time or priority ...).
Note that we already have an command-line guide on the wiki:
https://github.com/input-output-hk/cardano-wallet/wiki/Wallet-command-line-interface
It is not automatically generated, but we do maintain it and update it on every release, with QA validation on top. Perhaps this is enough in the end.

If we think it's a pain to maintain strings this way, then perhaps we can follow the approach used in hspec-golden-aeson, where expected results are stored in version-controlled files?

@jonathanknowles I don't think this solves our issue here, unless we do indeed manually check those files (which don't really happen with the API golden tests..). We do want to keep an eye on the output and make sure the CLI remain in-control. If we tests against auto-generated strings, it's not going to help much as we could simply auto-generate "gibberish" and validate against it.

@rvl, @jonathanknowles

Maintaining the golden strings in this way is going to be a pain.

Isn't it just the matter of adjusting the test whenever you change something? In that case it shouldn't be a lot of additional work, or maybe I miss something?
I generally like the idea. In my mind such tests can give feedback immediately (on every pr or merge to master) in case something is wrong. Off course this would not throw away manual verification of the CLI however such verification is not done every day, (it's done rather opportunistically every once in a while or just before the release). Such tests would give potenital feedback automatically and much more often.

When running the tests, we compare each expected output with the contents of the appropriate file. If a given output is unexpected, then the test suite overwrites the appropriate file.

It sounds a bit unsafe to me as we can get some unwanted content to get merged and then test against it...

@KtorZ

(which don't really happen with the API golden tests..)

I was under the impression that the tests fail if the output is different from the expected output? Perhaps I was mistaken? (Runs away to check.)

@KtorZ

I tend to agree with @rvl on that. This is going to be cumbersome to maintain, and we need to make sure that we keep an eye on it actually. I already imagine people updating things without much considerations (by lack of time or priority ...).

I think that when you have a test that you also need to look at and adjust when making a change it gives you additional opportunity to consider the change actually... ¯_(ツ)_/¯

I was under the impression that the tests fail if the output is different from the expected output? Perhaps I was mistaken? (Runs away to check.)

They do, and it happens when we change API types. Then usually, golden samples get re-generated and merged. I believe people usually look at the generated golden tests when this happens and give a justification for the change. But, I haven't actually checked them in a while. There's no manual review on the output there which is ... okay for API tests since they really are there for alerting us in case we were to change the representation of an API type in a non-compatible way.
The CLI tests here have a rather different purpose: we want to be sure that our little optparse-applicative pieces, once composed together, look reasonable and / or consistent. In that sense, we are much more interested into the output and the way it looks.

What do we do about this one?
@rvl @piotr-iohk @jonathan.knowles?

What do we do about this one?
@rvl @piotr-iohk @jonathan.knowles?

While solution used in this PR has some drawbacks, I still think it's an improvement over the status quo.
With the status quo, we have our specification in comments that are checked by neither the compiler nor our test suite.
With this, at least our specification is checked, even if it's not encoded in the most efficient fashion.
How about we go ahead with this PR, and if we really find that it's cumbersome to update, then we perhaps we can look at the problem again?


Based on choice above

On the final consent form, there are parts of the form that should only show based on what was chosen on the form above.
For instance, school email address and MCAT score should only display if the person filling out the form about has listed themselves as a medical student..
The phrase "(based on choice above)" should be removed from all form elements, and instead they should only show when that choice is taken.

The question "Enter your STEP 1 Score (optional) "
is supposed to appear for 3rd and 4th year medical students and residents and interns only..
The question "Enter the name of your illness(s)" should only appear for people who are patients or caregivers...
The NPI question should show up for:
I am a practicing physician
I am a mid-level provider (nurse, PA, etc)
I am in a residency or fellowship program
The question: "In what language do you communicate with your patients? "
should appear for everyone who says they are any kind of caregiver...
The questions:
Enter your STEP 2 Score (optional) ?
What medical school did you attend?
What year did you graduate medical school?
What is your primary specialty?
Should appear for practicing physician, resident or fellowship only...

closed via https://github.com/docgraph/batea_consent/commit/6b27eda73fcde6b14d74c03c8364468e34bf2dcd

Right now, I can choose "No" I am not a clinician of any kind and "No" I am not a patient or a caregiver... and I am still asked questions that are specific to medical students and questions that are specific to patients and caregivers.
That does not make any sense. My expectation is that you are understanding the purpose of the form, and that you understand what this form is doing: gather relevant information depending on what type of data contributor is being consented. The form needs to make sense.
Please do not close the issue, unless you are confident that the survey form makes sense.
Thanks,
-FT


Make copy edits on the Encryption at Rest docs

Fixes #3526, #2220.
Summary of changes:

Mostly copy edits with few substantive content changes.

Biggest change is to the Overview section: changed a table to a
list, made some content edits in there to (hopefully) make it a bit
easier to read and understand.

Moved the note about Encryption at Rest vs. BACKUP into a red warning
block, and rewrote the text a bit to make it clearer that this
feature does not result in your backups being encrypted.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1ee883656ba6c73c8583484810ae24b997741309/

@rmloveland, haven't reviewed this yet, but can you also complete the --enterprise-encryption flag in the cockroach start docs as part of this follow-up?

LGTM. Thank you for the improvements.

@rmloveland, haven't reviewed this yet, but can you also complete the --enterprise-encryption flag in the cockroach start docs as part of this follow-up?

Just updated in latest changes - thanks for the reminder @jseldess !
And thank you @mberhault for the excellent doc - very informative.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a7245f5832dcbb38bc079dba0ccbbc2298bfd19b/


Issue 5

Feature work for issue #5 based off of bug 1314740.
Test uploading compressed dumps in this range:

[x] 100k
[x] 150k

Test uploading uncompressed dumps in this range:

[x] 400k
[x] 4mb
[x] 20mb
[x] 50mb (greater than 20mb threshold)

Do these need to raise an error if the content they get back is not a crash id?

Oh, opps. I see that I missed adding this. I'll take a step to make this happen.

This is not ready for merge, the tests throw a HTTP 405 error. https://pastebin.mozilla.org/8961787

Also, I'm not sure sending empty dumps really helps us learn anything about how the system handles load.
I think our plan was to use a dump file ~20M which I believe you said was the size limit.  We could run tests with files ~19M and then an additional tests that exceeds 20M to verify that dump files exceeding max allowable would be rejected.

One of the things I thought of while looking at this code is that each test generates a brand new payload every time it runs, but the payloads are identical--there's no randomness in them. I don't know if it's worth spending time optimizing the load tests or not, but if it is, then memoizing the payload seems prudent.


Codeunit 90 new event on procedure PostItemTrackingForShipment

Hi,
We need a new event on Codeunit 90 procedure PostItemTrackingForShipment:
....
repeat
                    IsHandled := false;
                    OnPostItemTrackingForShipmentOnBeforeSetItemEntryRelationForShipment(ItemEntryRelation, ReturnShptLine, TempTrackingSpecification, IsHandled);
                    if not IsHandled then
                        if TrackingSpecificationExists then begin  // Item Tracking
                            ItemEntryRelation.Get(TempTrackingSpecification."Item Ledger Entry No.");
                            ReturnShptLine.Get(ItemEntryRelation."Source ID", ItemEntryRelation."Source Ref. No.");
                        end else
                            ItemEntryRelation."Item Entry No." := ReturnShptLine."Item Shpt. Entry No.";
                    UpdateChargeItemReturnShptLineGenProdPostingGroup(ReturnShptLine);
                    // > New Event
                    OnBeforeCheckReturnShptLine(ReturnShptLine, PurchLine, IsHandled);
                   // < New Event
....
 [IntegrationEvent(false, false)]
    local procedure OnBeforeCheckReturnShptLine(ReturnShptLine: Record "Return Shipment Line"; PurchLine: Record "Purchase Line"; var IsHandled: Boolean)
    begin
    end;
...

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


Added a cheat code and bedlike improvements

Description

What was changed in this pull request?

Added a cheat code which, if typed, toggles the header

Added fontColor, fontSize and fillOpacity options to the BedLikeTrack

Fix track name in the config menu

Why is it necessary?

Fixes #___
Checklist

[x] Set proper GitHub labels (e.g. v1.6+, ignore if you don't know)
[x] Unit tests added or updated
[x] Documentation added or updated
[o] Example(s) added or updated
[o] Update schema.json if there are changes to the viewconf JSON structure format
[x] Screenshot for visual changes (e.g. new tracks or UI changes)
[x] Updated CHANGELOG.md

Thanks for the suggestions!
I used concat instead of push because it's two strings that are being joined. document.hasFocus() always seems to return true so I took it out.
I also added a change to allow users to pass in a custom PIXI import for using canvas.


Improve SSR debugging with SourceMap

Vue.js version
2.x.x
Reproduction Link
Because it is a ssr issue and hard to provide a running demo online, please see Steps to reproduce
Steps to reproduce

clone the https://github.com/vuejs/vue-hackernews-2.0.git repostory
edit file src/\components/ItemList.vue to cause an error. For example:

// ...
import Spinner from './Spinner.vue'
import Item from './Item.vue'
import { watchList } from '../store/api'
// abc is a undeclared variable that can cause a ReferenceError
console.log(abc)
// ...

then run npm run build, npm run start in command line
open browser and navigate to http://localhost:8080
the command line will report some error info as below:

error during render : /
ReferenceError: abc is not defined
    at Object.module.exports.exports.default.props (__vue_ssr_bundle__:388:13)
    at __webpack_require__ (__vue_ssr_bundle__:21:30)
    at Object.module.exports.__vue_styles__ (__vue_ssr_bundle__:994:19)
    at __webpack_require__ (__vue_ssr_bundle__:21:30)
    at Object.module.exports.module.exports (__vue_ssr_bundle__:866:83)
    at __webpack_require__ (__vue_ssr_bundle__:21:30)
    at Object.<anonymous> (__vue_ssr_bundle__:650:80)
    at __webpack_require__ (__vue_ssr_bundle__:21:30)
    at Object.module.exports.exports.default.name (__vue_ssr_bundle__:224:66)
    at __webpack_require__ (__vue_ssr_bundle__:21:30)

What is Expected?
The error info in the command line should include the specific file path and line number, for example:
ReferenceError: abc is not defined
    at src/components/ItemList.vue (26:13)
    ...

What is actually happening?
Error info dose not include the file path and line number that cause the error to produce..
I know it is the bundle render that cause the error hard to locate. And is there any solution, like soucemap, that can solve this debug issuse with bundle render?

Relevant threads: https://github.com/nodejs/node/issues/8042, https://github.com/nodejs/node/issues/6471

This is on the roadmap. I have some ideas on how to improve it, probably
for 2.2.
On Sat, Dec 3, 2016, 10:22 AM Denis Karabaza<EMAIL_ADDRESS>wrote:

Relevant threads: nodejs/node#8042
https://github.com/nodejs/node/issues/8042, nodejs/node#6471
https://github.com/nodejs/node/issues/6471
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue/issues/4376#issuecomment-264628035, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAefXoSKQi-dWdo3aqm-913mvOt-6Celks5rETTfgaJpZM4LDPRI
.

@yyx990803 Great! Waiting for Vue 2.2 . It will be more suitable to use SSR bundle render for production environment. And what is the release date for Vue 2.2 in the roadmap?

Implemented and will ship in 2.2.

"stay tuned for a detailed writeup"
Are we still getting the writeup mentioned in the release notes? For some reason I couldn't get it working with the new bundle even though the old bundle works fine.

@jazoom you need to use https://github.com/vuejs/vue-ssr-webpack-plugin to enable sourcemaps in the server bundle.

@simplesmiler that is what I meant. I changed to using that and the build didn't work at all.

First of all, devtool: 'sourcemap' has to be added to webpack.config to enable source map output, which is not documented clearly.
And I have maps:[] output in the bundle file, but I still get unclear error from node output.
It's not what I expected...
2017-04-21 16:08:32,168 GET /sample/ssr status 204 (rt: 25ms)
[Vue warn]: Error in data():
(found in <Root>)
Cannot read property 'text' of undefined
TypeError: Cannot read property 'text' of undefined
    at Vue$2.data (main.js:303:30)
    at Vue$2.mergedInstanceDataFn (/Users/shenyi/Documents/aliwork/projects/quan-m/node_modules/.2.2.6@vue/dist/vue.runtime.common.js:1025:20)
    at getData (/Users/shenyi/Documents/aliwork/projects/quan-m/node_modules/.2.2.6@vue/dist/vue.runtime.common.js:2751:17)
    at initData (/Users/shenyi/Documents/aliwork/projects/quan-m/node_modules/.2.2.6@vue/dist/vue.runtime.common.js:2720:7)
    at initState (/Users/shenyi/Documents/aliwork/projects/quan-m/node_modules/.2.2.6@vue/dist/vue.runtime.common.js:2661:5)
    at Vue$2.Vue._init (/Users/shenyi/Documents/aliwork/projects/quan-m/node_modules/.2.2.6@vue/dist/vue.runtime.common.js:3752:5)
    at new Vue$2 (/Users/shenyi/Documents/aliwork/projects/quan-m/node_modules/.2.2.6@vue/dist/vue.runtime.common.js:3845:8)
    at Object.<anonymous> (public/error/404/entry-ssr.js:5:12)
    at __webpack_require__ (webpack:/webpack/bootstrap 4db82d0f851ec15f529c:19:0)
    at main.js:67:18


Fixes #17309: Added label to edit topic button in streams.

Fixes #17309 [https://github.com/zulip/zulip/issues/17309]
Added a Label for edit topic button in streams.
GIFs or screenshots:

@zulipbot  add  "needs review"

@zulipbot remove "needs review"

@Uttam-Singhh can you squash these commits into one commit.

Hey, @ritikchauhan-01
I tried it but wasn't able to do it.

@Uttam-Singhh Maybe you were trying to push the wrong branch. Did you double-check the branch name?

@garg3133 Yeah I checked it is still showing "everything is up-to-date"

What else do I need to do to get this or merge? @garg3133

As the changes are very small, the best way at this point would be to close this PR and open a new one from anew branch and make the changes there in a single commit.

sure @garg3133
I will do it!

There's no need to close a PR; one can always use git rebase -i to clean up history and then force-push to correct an existing PR.  It's well worth taking the time to learn how to do that -- you'll need those skills for future contributions to Zulip or other OSS projects.
Check out our GitHub guide and commit guidelines for more details.

Okay @timabbott I will try again!

@garg3133
Hey, I created a new PR for this please check -


feat(sdks): upgrade to fb-sdk-16.0.1

Based on https://github.com/thebergamo/react-native-fbsdk-next/pull/408 and https://github.com/thebergamo/react-native-fbsdk-next/pull/339 but more complete with updates in Readme

I would love to see this merged. <3

+1,  any update regarding this point?

+1, keeping an eye on this one

Thanks for setting this up! 👍 Hoping it will be merged soon. In the meantime, a few comments that may (or may not) be of use.

While the removal of trailing whitespace is an improvement, it might be better to minimize the diff by undoing those changes? Not sure...
Newest version is now 16.1.0, do you know if it would require any changes other than to FBSDKVersion to support it?

Hi
Let's see what the maintainers will say

Any update?

Really waiting for this to get merged and released so we can leverage the AEM AutoSetup in our Expo app and start using advantage ads on Meta. Let me know if I can help in any way.

Meta have a compliance deadline against this SDK of August 1st, is it possible to see this merged ASAP so we can avoid any issues?

Hi! Any updates to merge this?

Superceded by #441 - the updates are happening though!


feat_stock_typeahead

Stock Component Coverage Screenshot

App Component Coverage Screenshot

There is an input text-box and drop down for user input/selection in stock component html page, apart from this there was no html-error tag for drop down.
Secondly, In Chart component html, the ngIf condition was not written properly.


New results with depthwise separable convolution

Not exhaustive, but could serve as the new baseline.
In particular,

depthwise (x4) should be used for "stem" as well, but I got "out of memory". When batch_size is lowered, training is a lot slower, and the result is not as good as it could be.
stem_size, currently at [3,32,64,64], may need to be optimized for this new design;
the 4 (sometimes called depth or channel multiplier) may not be optimal.

Please hold off on this PR. The results are correct; I just need to do more testing to attribute them to the right cause.


bridge: show actual state in approval finished events

Closes #2371

Codecov Report

Merging #2427 into master will decrease coverage by 0.01%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##           master    #2427      +/-   ##
==========================================
- Coverage   33.48%   33.46%   -0.02%
==========================================
  Files         157      157
  Lines        8805     8809       +4
  Branches      168      170       +2
==========================================
  Hits         2948     2948
- Misses       5368     5370       +2
- Partials      489      491       +2

Flag
Coverage Δ

#moduleA
24.08% <20.00%> (-0.10%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

bridge/client/app/_models/event-icons.ts
100.00% <ø> (ø)

bridge/client/app/_models/event-labels.ts
100.00% <ø> (ø)

bridge/client/app/_models/trace.ts
34.48% <20.00%> (-2.56%)
:arrow_down:

Continue to review full report at Codecov.

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


Removing unused kernel features from the image.

Hello, I'm new in Yocto and i want to remove machine features which i'm not using in my project. I did not find any guide for this. Could you help me please?

The "right" way to do it would be to create another machine inheriting a base one.


coala

Hey, you know us already IIRC, just wanted to let you know that we added CPPClean support in coala (coala-analyzer.org). Usual things apply, this opens it up for several editor plugins, our automatic GitHub pull request review thingy, various analysis data dumps and so on. As always we're open for collaboration but I think we had this discussion so feel free to close this bug when read. :)
Have a nice day!

Great!
https://github.com/coala-analyzer/coala-bears/commit/812c9750d8212c31e52df541daccfa8cb670d754


allow flowRuns route to pass workspace and account id if not availabl…

…e from route context

Found route.workspace in nebula ui that does the same thing.


Refactor safezone positioning (fix selection outside of canvas)

Summary
Minor refactor to the safezone/dangerzone positioning to fix oddities in measurements in react-moveable and lasso selection. Most notably fixes an issue that used to shift frame boxes when selecting an element that partially sits outside of the canvas.
Relevant Technical Choices
Moved to using position: absolute for a few layers to minimize side effects of adding/removing elements to the layers and used explicit pixel heights of the danger zone instead of relying on flex-box centering.
Testing Instructions

Add an element to the canvas
Drag the element to the edge of the canvas such that part of the element is outside of the page
Unselect and reselect the element, this should show the correct box around the element, which used to be wrong.

Fixes #1787
Fixes #1545

@wassgha It still seems to have the issue in testing, actually, now the issue seems to appear for all the elements -- for the ones that are on the Canvas as well and not partly outside of the edge:

Thoughts?


ExcelPainter: cell_details should be optional

This can be done with a boolean arg, show_cell_details

Resolved by #416.


Accept manifest path option

Hi there!
Kind of a rust newbie here and I think I may have bitten off more than I can chew. I'm looking to solve #2817 and I'm struggling. I'd like to get cargo fmt --manifest-path working like cargo run --manifest-path but I'm not sure how to mesh it with the other strategies: CargoFmtStrategy::Root, CargoFmtStrategy::All, and  CargoFmtStrategy::Some.
I guess what I'm stuck on is trying to understand the reasoning behind how those strategies work. There aren't any tests to reference so it's hard to dig up the reasons behind them, like what kind of project setups they're meant to be used with. I'd be happy to write up some tests for this once I can wrap my head around it. I think understanding that would help me add a new strategy.
Thoughts? Is this something you'd like to see in the project?
Thanks for your time and the awesome project!

Aborting all of this and restarting in another branch because I'm awful at git rebasing. Thanks for the direction!


Fix: Implemented Rate Limiter against Message Flooding.

Fixes Issue
**My PR closes #470 **
👨💻 Changes proposed(What did you do ?)
✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.

Note to reviewers
The message will not be sent when it hit the count 25 in a minute.
📷 Screenshots

Hello, Maintainers!
I hope you are doing well. I've submitted a pull request by Adding the Rate Limiter for Messages .Please feel free to review my changes and provide any feedback you may have.
Thank you for your time and consideration. I look forward to hearing from you soon.
Best regards,
Tholkappiar

Hello, Maintainers!
I hope you are doing well. I've submitted a pull request by Adding the Rate Limiter for Messages .Please feel free to review my changes and provide any feedback you may have.
Thank you for your time and consideration. I look forward to hearing from you soon.
PS : Kindly Add up Hacktoberfest things for this PR !
Best regards, Tholkappiar

just talk like a normal person, no need for the email


Set minimum version number of dependency

If click is not fixed to a minimum version number it has the potential to crash the 32blit tool when executed resulting in a broken build of a 32blit game.

Pull Request Test Coverage Report for Build 558925684

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

Totals

Change from base Build 555360144:
0.0%

Covered Lines:
878

Relevant Lines:
1201

💛  - Coveralls

Thank you, will get the next release out ASAP!


... during tool call looks like a triple dot menu

Testing #6331
the way the formatting looks when the status message comes up it looks like the ... is a new menu which I then attempted to click. I think because it looked like a column format I thought of the words, the link, and the three dots and separate sections of the message.

We're not adding those ..., they come from core. There's also this strange column layout that's happening.


Add AUTO_REFRESH_INTERVAL override

This PR supersedes #691, merging conflicts and adding the setting to local_settings.py.example. The Graphite administrator can now override the default 60s composer refresh interval with this setting.

Current coverage is 66.16% (diff: 100%)

Merging #1654 into master will increase coverage by <.01%

@@             master      #1654   diff @@
==========================================
  Files            54         54
  Lines          6034       6035     +1
  Methods           0          0
  Messages          0          0
  Branches       1190       1190
==========================================
+ Hits           3992       3993     +1
  Misses         1836       1836
  Partials        206        206

Powered by Codecov. Last update 22ddff8...14945a9


Webspace key index

Why is the webspace key index to unstored? does this mean that it is not stored in the index? @danrot @dantleech @chirimoya
tasks:

[ ] gather feedback for my changes

informations:

q
a

Fixed tickets
none

BC breaks
none

Documentation PR
none

same here https://github.com/sulu-io/sulu/pull/1079/files#diff-0f5e72e095573a1b0d9d9f805cd9703bR160 why unstored? didnt we need this value in the index?

@wachterjohannes unStored means that it is indexed but the value is not retrievable.
It is in the index :)

but it is not returned when we search for it ...

and we need it to generate the deeplink ...

Aggregate wouldn't work at all. Aggregate is an optimization which aggregates all of the searchable values into a single field, so you would not be able to do webspace_key: foo

See https://github.com/massiveart/MassiveSearchBundle/pull/40.
Change would be identical to this accepting that you use Field::INDEX_STORED_INDEXED instead of AGGREGATE

@dantleech should i set state also to INDEX_STORED_INDEXED?

@dantleech could you please take a look at this? if it is green you could merge it into master and develop! i will make a hotfix release until this is merged!

Merged


Breaks out player update logic

Description

cut out player update stuff from any hardware entanglement
makes player updates "event based" to abstract away hardware events like interrupts or wake-up-type-specific behaviors
adds abstract game_update event handler function which can be customized per target device
updates health_monitor.ino to use the new stuff

Testing
Not yet; early looks only
Notes
Tried to do a little event loop thing to abstract out wakeup-specific behaviors and interrupt stuff.
In its current state, you could totally write a simulated player(s) which update periodically completely absent of any BT logic, which is how I chose a stopping point. Tried to keep logic and spirit the same as much as possible during refactoring, but leaked in some idiosyncrasies.
We need a linter.

+@tylerjw
+@griswaldbrooks

Will re-open as branch of remote


cannot load mime-type

I have created a Ruby project to use your mail lib but mail 2.5.4 complains that it cannot load such file -- mime/type even if mime-type 1.16 is installed on my machine
/Users/chmoulli/.rbenv/versions/1.9.3-p484/lib/ruby/gems/1.9.1/gems/mail-2.5.4/lib/mail.rb:9:in `require': cannot load such file -- mime/types (LoadError)
	from /Users/chmoulli/.rbenv/versions/1.9.3-p484/lib/ruby/gems/1.9.1/gems/mail-2.5.4/lib/mail.rb:9:in `<module:Mail>'
	from /Users/chmoulli/.rbenv/versions/1.9.3-p484/lib/ruby/gems/1.9.1/gems/mail-2.5.4/lib/mail.rb:2:in `<top (required)>'
	from /Users/chmoulli/MyProjects/hyla/lib/hyla/send_mail.rb:4:in `require'

and gem mime-types
ll /Users/chmoulli/.rbenv/versions/1.9.3-p484/lib/ruby/gems/1.9.1/gems/mime-types-1.16/

Is there a workaround ?

just remove require 'mime-types' in your ruby file.
as mime-types is built in ruby. you don't need to install its gem or include its explicitly.
just use it.
this works for me.


init fresh app get wrong dir

when I init app with code in Doc deno run -A -r https://fresh.deno.dev my-app
I get these message

Project created!
`cd my-project` to enter to the project directory.
Run `deno task start` to start the development server.

my dir Name is my-app why I got cd my-project !

This has already been fixed by https://github.com/denoland/fresh/pull/415

I see .. thanks 👍🏽


Custom Model names

Description
We need to be able to type in our own string for 'model' which would allow you to use a lot more custom endpoints as well as fix the issue of different OpenAI models not being supported.
Who will benefit from this feature?
Anyone that wants to use custom endpoints besides OpenAI, like Ollama, Perplexity, etc.
Anything else?
No response

Just inputting your own string doesn't really do anything. We would have to support all those different endpoints internally, each using different API formats with different API keys. So it's unlikely that we'll support arbitrary AI model with the extension API in the short term.


Start building with sphinx 1.8

Currently we use sphinx 1.7,
we already have some projects building with 1.8 (with feature flag)
and with custom requirements.
We also have fixed/adapted some of our code to support the
new version.
I'm also updating the projects with a feature flag to use 2.0
when it's available.
Release history https://pypi.org/project/Sphinx/#history

There isn't going to be a 1.9 release, but, yeah, we can just put the same version for both

Makes sense. We should also look at upgrading our other python_environments requirements in this PR. The pillow and other packages we install are quite old.

I'll open a new PR with those requirements. I want so see how they affect us first :)


you asked me to comment on tools/release

you had asked me to comment on tools/release
https://github.com/peggyjs/peggy/blob/main/tools/release#L90
there's a lot of value in doing things in the standard way.  i worry that i'm becoming a wet blanket about this
this has no attachment to pipes.  everything is run through a large monolithic custom script.
there's no way to multiplex processes here.  you can't see what actually went wrong in an action.
because this is all buried in a custom script, we lose all piping benefits of the unix way, and gh actions' reporting stuff is no longer available
we can't re-use any standard actions because there's no way to put anything in the positioning chain
users can't use individual steps at their discretion; there can only be one path through this, ever
we're trying to manually implement publishing through npm through a wrapper script in a javascript.  this is extremely dangerous and is likely to get hacked.
we're writing our own child process spawning and queueing system
i don't understand why we keep inventing unnecessary infrastructure
there's something really good here for this already.  it's called npm scripts.  it has the unix interface, which carefully correctly manages process parallelism (this is hard) and has standard logging expectations.
everybody already knows how to use it and work with it.
the result to replace this code is seven lines and is in a standard place where every node programmer will immediately look for it, is robust to several classes of operating system problem that are not handled here,  and have been extensively tested
we don't want to write our own auto-publish.  that's dangerous.  if we're going to auto-publish, it should be the standard one that's been gone over extensively for security topics.
it would be difficult to use that here because it's an action and this doesn't participate in the pipeline lifecycle
this also appears to be doing git diffing.  why?  is the idea that this would be automated on the developer's local machine?  that's not reproducible.  this needs to be in ci/cd, and if it's in ci/cd, that's already done
i'm currently somewhat confused what this file is for.  it was represented as equivalent to a two line script i put up that replaces a file with a number exported, and allows the source code compile process to handle everything else
these are actually quite night and day different

I'm willing to take a patch to replace this, but I want to make sure the functionality remains.  What I'm trying to accomplish is ensuring that a release gets done in completely automated fashion, including several ways I've messed up builds in the past.  The git diff bits are trying to ensure that the repo is all checked in clean at each step.  The auto-publish doesn't happen for me because there's a pause for OTP.  I'm planning on making 2FA required in the npm config, once @phpnode turns it on for his account.

i don't understand why we keep inventing unnecessary infrastructure

Would you mind please assuming that there are reasons I'm doing some of these things that are not just because I'm stupid?  It will make it easier for us to make progress more quickly.  There are definitely things I'm going to learn from this process, and I'm willing to learn those things and make changes.

it needs to be possible to say "this is dangerous" without getting yelled at for it

What I'm trying to accomplish is ensuring that a release gets done in completely automated fashion, including several ways I've messed up builds in the past.

i'd like to help, but the tone of this last comment is very difficult for me
i've said the same things i said in this comment for about five years now, since long before you showed up.
i said them to you in a friendly way a week ago, and then again two days ago.
i showed you working code and an example.  i emphasized how important it was that it was two lines, and that it was separated into its own script, so that it followed the unix way.
you told me "oh yeah that's totally what we're doing" and asked me to come look at this.
.
i'm having some trouble with communication.  when i asked you to please not install lerna, pointed out that this had already been done to this repo several times with disastrous consequences, then pointed out the universal normalcy of those consequences, you said there were no new package managers going in.  then it was both lerna and pnpm.
then it was a fight to get this project not put into a position where it would lose 40% of its historical contributions, and exclude me.
next when i said "please don't make a monolithic script build, let's do this in the standard way in scripts and use the standard github actions," you said that sounded good.  but then you posted a really massively overengineered third party solution.  i said "no, we can just do it like this," and tried to show you one.
i don't know if i think you read it?
you told me to come here and comment.  so i did, and you said i was calling you stupid.
i'm not, though.  actually, in my head, quite the opposite.  i believe that only smart people over-engineer, because i believe that stupid people who try to eat the ground early, and learn not to do this.
it makes me sad, because i didn't actually throw any insults.
i just said the same thing i keep saying: "hey guys, can we please do it the standard way that i told you about before this went in?  i already have it done, i can just donate it."
and then i see something, and i try it, and it excludes me as a developer.  this is #3 in a row.  this time it's because there's an unknown script invoking child process, so both my work and my home antivirus panic.  i can tell norton to shut up, but not my work antivirus.

i want to help, because this tool is incredibly important to me.
can you please tell me what was wrong with the way i communicated specific engineering concerns to you, that you ignored all of them?
can you help me understand how you would like me to communicate, in the future, my confusion?
is there actually something wrong with my saying "here is a practice which is repeating that i do not understand?"  at literally every job i've ever had, that would have been treated as a valuable concern.
i don't want to feel like a bully.  i haven't criticized you in any way.  i most certainly did not call you stupid, and thought the opposite.
i just want the tool i depend on, which was taken over right before i saved it with enormous invested work, to not be destroyed by people who want to try out cool new things.
this is a core infrastructural piece of the internet.
everything about it should be boring and standard.  many of the rest of us are depending on it.


MDN Compat Survey Banner

What's changed, or what was fixed?

Re-adds MDN compat survey banner

:+1:


Test for pub and sub with different topics in proxy.  And  add ISSUE_Template

#229
#235
test for pub and sub with different topics in proxy.
and add a Issue_template

Not right and conflicted. Close.


ARR translation and added minor Fr

t1 correction
t4, t9, t12 added
t5, t6, t7, t8, t11 correction and remove area name useless
t10 adjustment for timeline Fr and remove area name useless
 Add must be before name monster in french. Screen of the corrected version
ifrit nm, titan ex, remove double symbol (( ))
 before
 after

Everything is corrected with the names of the games, I redid the instances.

t6

t7

t8

in t9 and other, I see this, how sync is this supported?

t11, As for t6, I corrected so that the timeline Fr is correct.
 Before
 After

Thank you for your corrections, help, I am learning a lot from you.

Everything is corrected with the names of the games, I redid the instances.

Thanks!

in t9 and other, I see this, how sync is this supported?

Via https://github.com/quisquous/cactbot/blob/master/ui/raidboss/common_replacement.js#L46, which applies to both text and syncs.

Ah, I seemed to have seen it. Thank you.


feat!: Handle receiving multiple readings in the async payload

BREAKING CHANGE: The published async payload must now be json containing the resource names and values, even when a single resource is sent. Redendent single resource Device Commands (testrandfloat32, testrandfloat64, testping and testmessage) in mqtt.test.device.profile.yml have be removed. Use the corrisponding resource name (randfloat32, randfloat64, ping or message) instead.
closes https://github.com/edgexfoundry/device-mqtt-go/issues/299

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/device-mqtt-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?) N/A
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[x] I have opened a PR for the related docs change (if not, why?)
https://github.com/edgexfoundry/edgex-docs/pull/1046

Testing Instructions
Run the updated example from this PR: https://github.com/edgexfoundry/edgex-docs/pull/1046
Verify the async event now have three readings
New Dependency Instructions (If applicable)

Codecov Report

Merging #586 (5500aa3) into main (44db128) will decrease coverage by 1.15%.
The diff coverage is 8.45%.

:exclamation: Current head 5500aa3 differs from pull request most recent head e966283. Consider uploading reports for the commit e966283 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #586      +/-   ##
==========================================
- Coverage   23.34%   22.19%   -1.15%
==========================================
  Files           5        5
  Lines         454      482      +28
==========================================
+ Hits          106      107       +1
- Misses        334      361      +27
  Partials       14       14

Impacted Files
Coverage Δ

internal/driver/incominglistener.go
0.00% <0.00%> (ø)

internal/driver/driver.go
13.20% <20.00%> (+0.20%)
:arrow_up:

recheck


fixthe data type of compareExpr and listQuery should be the same when creating InSubquery

Proposed changes
Issue Number: close #xxx
Problem summary
Consider sql select table_B_alias.b from table_B_alias where table_B_alias.b in ( select a from table_A_alias );
if table_B_alias.b is int and table_A_alias.a is bigint, we should cast(b as bigint) to make the data type the same as the InSubquery.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

Maybe you should modify TypeCoercionUtils.processInPredicate instead of FunctionBinder


retarget the platform

Windows 8.1 SDK -> Windows 10 SDK
toolset v141 -> toolset v142

... thanks for at least pushing me into doing the update :) master is retargeted to v142 since now.


Trying to appease dependabot

This, I think, should make dependabot happy...
Fixes #14

Just yank the whole eval as we’ve done elsewhere and you’re good to go

https://github.com/chef/mixlib-log/commit/7ca990c44a96146d84cb8257fb421e4dce9298f1

Absolutely not.


[1545] Add E2E Tests for Browse Bills Page

Summary
Issue: #1545
This PR adds Playwright end-to-end (E2E) testing for the Browse Bills page, including:
Finding bills via text search
Sorting bills by various criteria
Filtering bills based on different attributes
My Playwright version 1.43.1 and yarn version is 1.22.19
Checklist
Playwright test covering the Browse Bills page, including:
Able to find Bills via Text Search - finished
Able to sort Bills as expected - finished
Able to filter Bills as expected- finished
Screenshots

Known issues
1.The sorting function for "sort by relevance" is not implemented as I do not have access to the relevance score needed to test this functionality.
2.Only a couple of pages were tested due to time constraints, as testing every page would take too long.
3.For the filtering function, the tests mostly focus on ensuring that the labels are showing correctly. The content itself wasn't thoroughly checked since this would require looking into the bill page in detail, which is extremely time-consuming.
Steps to test/reproduce
To run the e2e tests with the Playwright UI, run yarn test:e2e.

This is a great start! Some general comments I have:

I'd avoid using CSS classes for the locators, especially since there are generated CSS glasses that may not always be the same every time. I find that the getBy... locators work really well because it forces you to look at the page from a user's perspective, and they also have built in retries, so it may not be necessary to use manual waits. https://playwright.dev/docs/locators
I only just found this feature recently, but Playwright's Page Object Model will be very useful for frequently used elements or actions: https://playwright.dev/docs/pom
Still in progress, but if you want to see my WIP files:
https://github.com/seatuna/maple/blob/1546_browse-testimonies-e2e-tests/tests/e2e/testimony.spec.ts
https://github.com/seatuna/maple/blob/1546_browse-testimonies-e2e-tests/tests/e2e/page_objects/testimony.ts (page object model for the Testimonies page).

Ready to be reviewed!

This is looking solid to me - I'll approve and we can merge as soon as the build passes (looks like we need to run prettier for the Code Quality check). The integration test issue is fixed in main - if the build passes except for the firebase-admin/auth/UserRecord in the integration tests, it should resolve itself by rebasing off main.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-27-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3393

Questions ?
Please refer to the Backport tool documentation


What is the configuration of pertraining on hypersim ?

Epoch, Task weighting or the other settings, can you show the training command on hypersim ?

 The epoch number had not been set in the command, does this mean that the number of epoch is 500, as set in the args.py ？

Yes. However, note that the actual number of iterations also depends on the specified subset parameter.  Even with a random subset of 0.2 or 0.3 per epoch, training on an A100 will take around one week.

Thank you ! 🙏  But there is an another problem. That is when I train EMSANet on nyuv2 with the the pretrained weights for the encoder backbone ResNet-34 NBt1D, using the command in the last of Readme file, the test miou is 0.5041. It is different from the paper——0.5097, though I repeated the training process three times. Did I do something wrong ?

This should not happen. I will run a test training to double-check this.

Ok, I did some test trainings and was able to almost reproduce the reported results in a more recent environment:
                                       task: ['semantic', 'scene', 'instance', 'orientation']
                             task_weighting: [1.0, 0.25, 3.0, 1.0]
                         instance_weighting: [2, 1]
                                         lr: 0.03
                                      wandb: EMSANet-nyuv2-r34nbt1d-testruns astral-firefly-6 (2tnzlo26)
                                  wandb_url: https://wandb.ai/nicr/EMSANet-nyuv2-r34nbt1d-testruns/runs/2tnzlo26
                                  epoch_max: 499

valid_panoptic_all_with_gt_deeplab_pq (447)
      valid_instance_all_with_gt_deeplab_pq: 0.6060
               valid_orientation_mae_gt_deg: 18.4523
              valid_panoptic_all_deeplab_pq: 0.4324
      valid_panoptic_all_with_gt_deeplab_pq: 0.4324
      valid_panoptic_all_with_gt_deeplab_rq: 0.5183
      valid_panoptic_all_with_gt_deeplab_sq: 0.8253
       valid_panoptic_deeplab_semantic_miou: 0.5123
             valid_panoptic_mae_deeplab_deg: 16.1432
                           valid_scene_bacc: 0.7684
                        valid_semantic_miou: 0.5083

Note that the learning rate is slightly lower than the reported value in the paper: 0.04 (paper) vs 0.03 (here). However, as the environment is different, I enqueued runs with 0.02, 0.03, and 0.04. The best result is shown above. It was at epoch 447 based on valid_panoptic_all_with_gt_deeplab_pq.
Training was done on an A100 40GB with driver 470.63.01. Please find below additional details on the environment.
conda list | grep -e torch -e cuda
cuda                      11.7.1                        0    nvidia
cuda-cccl                 11.7.91                       0    nvidia
cuda-command-line-tools   11.7.1                        0    nvidia
cuda-compiler             11.7.1                        0    nvidia
cuda-cudart               11.7.99                       0    nvidia
cuda-cudart-dev           11.7.99                       0    nvidia
cuda-cuobjdump            11.7.91                       0    nvidia
cuda-cupti                11.7.101                      0    nvidia
cuda-cuxxfilt             11.7.91                       0    nvidia
cuda-demo-suite           11.8.86                       0    nvidia
cuda-documentation        11.8.86                       0    nvidia
cuda-driver-dev           11.7.99                       0    nvidia
cuda-gdb                  11.8.86                       0    nvidia
cuda-libraries            11.7.1                        0    nvidia
cuda-libraries-dev        11.7.1                        0    nvidia
cuda-memcheck             11.8.86                       0    nvidia
cuda-nsight               11.8.86                       0    nvidia
cuda-nsight-compute       11.8.0                        0    nvidia
cuda-nvcc                 11.7.99                       0    nvidia
cuda-nvdisasm             11.8.86                       0    nvidia
cuda-nvml-dev             11.7.91                       0    nvidia
cuda-nvprof               11.8.87                       0    nvidia
cuda-nvprune              11.7.91                       0    nvidia
cuda-nvrtc                11.7.99                       0    nvidia
cuda-nvrtc-dev            11.7.99                       0    nvidia
cuda-nvtx                 11.7.91                       0    nvidia
cuda-nvvp                 11.8.87                       0    nvidia
cuda-runtime              11.7.1                        0    nvidia
cuda-sanitizer-api        11.8.86                       0    nvidia
cuda-toolkit              11.7.1                        0    nvidia
cuda-tools                11.7.1                        0    nvidia
cuda-visual-tools         11.7.1                        0    nvidia
cudatoolkit               11.3.1               h2bc3f7f_2
ffmpeg                    4.3                  hf484d3e_0    pytorch
pytorch                   1.13.0          py3.8_cuda11.7_cudnn8.5.0_0    pytorch
pytorch-cuda              11.7                 h67b0de4_0    pytorch
pytorch-lightning         1.5.8                    pypi_0    pypi
pytorch-mutex             1.0                        cuda    pytorch
torchaudio                0.13.0               py38_cu117    pytorch
torchmetrics              0.10.2                   pypi_0    pypi
torchvision               0.14.0               py38_cu117    pytorch

I hope this helps.


[SUPPORT] Failed to build hudi 0.12.0 with spark 3.2.2

Describe the problem you faced
Failed to build hudi 0.12.0 with spark 3.2.2
To Reproduce
Steps to reproduce the behavior:
mvn clean package -DskipTests -Dscala-2.12 -Dspark3.2 -Dspark32.version=3.2.2

Environment Description

Hudi version : 0.12.0

Spark version : 3.2.2

Stacktrace
[INFO] --- scala-maven-plugin:3.3.1:compile (scala-compile-first) @ hudi-spark3.2.x_2.12 ---
[INFO] /root/hudi-release-0.12.0/hudi-spark-datasource/hudi-spark3.2.x/src/main/java:-1: info: compiling
[INFO] /root/hudi-release-0.12.0/hudi-spark-datasource/hudi-spark3.2.x/target/generated-sources/antlr4:-1: info: compiling
[INFO] /root/hudi-release-0.12.0/hudi-spark-datasource/hudi-spark3.2.x/src/main/scala:-1: info: compiling
[INFO] Compiling 32 source files to /root/hudi-release-0.12.0/hudi-spark-datasource/hudi-spark3.2.x/target/classes at<PHONE_NUMBER>623
[WARNING] /root/hudi-release-0.12.0/hudi-spark-datasource/hudi-spark3.2.x/src/main/scala/org/apache/hudi/Spark32HoodieFileScanRDD.scala:21: warning: imported `HoodieUnsafeRDD' is permanently hidden by definition of trait HoodieUnsafeRDD in package hudi
[WARNING] import org.apache.hudi.HoodieUnsafeRDD
[WARNING]                        ^
[ERROR] /root/hudi-release-0.12.0/hudi-spark-datasource/hudi-spark3.2.x/src/main/scala/org/apache/spark/sql/execution/datasources/Spark32NestedSchemaPruning.scala:92: error: not enough arguments for method apply: (schema: org.apache.spark.sql.types.StructType, output: org.apache.spark.sql.catalyst.expressions.AttributeSet)org.apache.spark.sql.catalyst.expressions.ProjectionOverSchema in object ProjectionOverSchema.
[ERROR] Unspecified value parameter output.
[ERROR]         val projectionOverSchema = ProjectionOverSchema(prunedDataSchema)
[ERROR]                                                        ^
[WARNING] one warning found
[ERROR] one error found

ProjectionOverSchema.scala:
//spark 3.2.1
case class ProjectionOverSchema(schema: StructType) {}

//spark 3.2.2 and spark 3.3.0
case class ProjectionOverSchema(schema: StructType, output: AttributeSet) {}

Spark32NestedSchemaPruning.scala:
      if (countLeaves(dataSchema) > countLeaves(prunedDataSchema)) {
        val prunedRelation = outputRelationBuilder(prunedDataSchema)
        val projectionOverSchema = ProjectionOverSchema(prunedDataSchema)

        Some(buildNewProjection(projects, normalizedProjects, normalizedFilters,
          prunedRelation, projectionOverSchema))
      }

Spark33NestedSchemaPruning.scala:
      if (countLeaves(dataSchema) > countLeaves(prunedDataSchema)) {
        val prunedRelation = outputRelationBuilder(prunedDataSchema)
        val projectionOverSchema = ProjectionOverSchema(prunedDataSchema,AttributeSet(output))

        Some(buildNewProjection(projects, normalizedProjects, normalizedFilters,
          prunedRelation, projectionOverSchema))
      }

In spark 3.2.1, ProjectionOverSchema has a argument. But in spark 3.2.2 and spark 3.3.0, ProjectionOverSchema has 2 arguments.  Spark32NestedSchemaPruning.scala is not compatible with spark 3.2.2.

@xushiyan you can assign this one to me

Created HUDI-4899 to track. We can close this one

Will be addressed in https://github.com/apache/hudi/pull/6755

i'm still having this error in spark 3.3.1 and 3.3.2 (most recent Feb-23 release!) with hudi-spark-bundle_2.12:0.13.0.
Should i downgrade to 3.2.1?

Yes, you should.

Got it working with hudi-spark3.2-bundle_2.12:0.13.0
hadoop-aws:3.2.4
spark-avro_2.12:3.2.4
Spark 3.2.4 and python 3.9

I can't find any combination that doesn't give:
Caused by: java.lang.ClassNotFoundException: org.apache.spark.sql.execution.datasources.Spark32NestedSchemaPruning


Modify control plane logging levels with istioctl

Currently we have istioctl pc log for Envoy. It would be useful to have this for Istiod as well (through controlz interface)

I'd like to work on this if possible and if this is not urgent. Still learning the project so it might take some time.

Sure, sounds great. One thing I realized is that the proxy-config subcommand is for proxy configuration.. which Istiod is not. Not sure how we should organize it. @esnible ?
But basically the implementation is to hit the localhost:9867 endpoint and then I think there is some endpoint there that will allow this through the API - currently there is just a UI

curl localhost:9876/scopej/ads -X PUT -d '{"output_level":"debug"}' is the api

curl localhost:9876/scopej/ads -X PUT -d '{"output_level":"debug"}' is the api

Yep, I think I have all I need. I'll post some code during the weekend (not working on Istio fulltime). Thanks.

For 1.8, the ControlZ :9876 port will be protected by JWT and TLS.
This means this command should use the pattern of experimental proxy-status and generate and use a token.

For 1.8, the ControlZ :9876 port will be protected by JWT and TLS.
This means this command should use the pattern of experimental proxy-status and generate and use a token.

@esnible do you refer to this PR https://github.com/istio/istio/pull/26726 ?

At a recent meeting, someone (@costinm ?) said that port 9876 would not be exposed plaintext.  We need to coordinate with the control plane.  The changes should go into the servers and istioctl at around the same time.
It is your choice if we should add a --plaintext flag, they way we do in the PR you mention, to allow us to invoke control-z on 1.7 and 1.8-pre-alpha control planes.  We probably don't need this, as it is a rarely-used feature.

I do not agree @esnible . Unlike other debugging tools, this one should be touched exclusively by the istiod owner. This means, for a "out of cluster istiod", this command would never be used. Exposing 9867 on TLS/JWT doesn't make sense to me -- its already localhost, and should continue to be.

@howardjohn Should this item be part of milestone 1.8?  Let's assume port :9867 is not exposed, how should istioctl modify control plane log levels?

@esnible I am a bit confused. AFAIK this is done: https://github.com/istio/istio/pull/25276. It works exactly how I would expect. What work do you think should be done for 1.8?


Add Scheduling & Handle Holiday Punch Card URL Return

This will add scheduling for a random hour between 7-10 at a random min for the next day.
This will also handle the current holiday punch card random return URL happening from Microsoft.

I have an error in this will resubmit


feature: Add support for lsp zero

Did you check the docs?

[X] I have read all the LazyVim docs

Is your feature request related to a problem? Please describe.
Collection of functions that will help you setup Neovim's LSP client, so you can get IDE-like features with minimum effort.
Describe the solution you'd like
An extra or something to use lsp zero.
Describe alternatives you've considered
N/A
Additional context
No response

Try to use :LazyExtras for this
For example
https://www.lazyvim.org/extras/lang/python
(in left side you can see other langs presets)

LazyVim pretty much already does everything lsp zero does.
You can use mason to install an lsp and it will work out of the box

LazyVim pretty much already does everything lsp zero does.
You can use mason to install an lsp and it will work out of the box

Not on NixOS which is how I found this thread.
https://nix.dev/guides/faq#how-to-run-non-nix-executables


Make aio an optional feature

I use nix in a shared library and nix requires aio and aio lives in -laio as opposed to stdlibc. That results in my binaries having an additional dependency on aio even though I don't actually use aio.

Nix uses POSIX aio, not libaio.  POSIX aio merely needs librt.  libaio is a separate beast.  Something else in your application must be pulling it in.

Definitely not, I established a minimal pair with nix. Removing nix fixed the problem.
Many errors of this form:
... .a(nix-d2f66c26b23178b3.nix.e8pnq1ld-cgu.2.rcgu.o):nix.e8pnq1ld-cgu.2:function nix::mqueue::mq_open: error: undefined reference to 'mq_open'

... .a(nix-d2f66c26b23178b3.nix.e8pnq1ld-cgu.7.rcgu.o):nix.e8pnq1ld-cgu.7:function nix::sys::aio::LioCb::error: error: undefined reference to 'aio_error'

mq_open and aio_error are both part of librt, not libaio.

Then shouldn't those two be optional features so that my library which used to not need librt still doesn't?

There would be no point, because event Rust's standard library depends on librt.  You could try building with lto, which might remove it.  For that matter, those libraries should get linked automatically.  Are you building without Cargo or something?

I'm building into a static library which then gets linked into a C++ program. None of my program depends on librt so my C++ program shouldn't need to either.

What's the actual issue here? Is librt not available on your target platform? Do you care about the extra time to load an additional library? Do you care about the space?
On November 18, 2018 10:14:29 PM GMT+01:00, Kalle Samuels<EMAIL_ADDRESS>wrote:

I'm building into a static library which then gets linked into a C++
program. None of my program depends on librt so my C++ program
shouldn't need to either.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/nix-rust/nix/issues/976#issuecomment-439726403

Try building with LTO.  I think that will strip the offending symbols, if they're unused.


Very Slow Insertion on Windows

Hi,
I am using MapDB and I experience strange behavior on Windows platform. Here is my experimental setup:
I run the same program (see below) on Linux (Fedora 20), and Windows 7. On fedora the execution time is fast and everything behave as expected. However the execution time becomes very slow when I move to windows (I stopped it after around 10 minutes, and only 25% of the elements were inserted).
Note that I perform these two experimentations on the same computer to have the same hardware capabilities. I also asked other people to run it to see if this is only related to my computer or if it is a general issue, and the results are the same.
More surprising, if we execute this code on windows but inside a docker running a linux instance then the performances are good as expected.
On the same idea, if I run the experimentation from Linux but writing the database on the windows partition everything is fine too (this shows that the file system type is not the problem)
I am wondering if there is some windows system setting to take into account, or any windows related stuff. For now I am investigating on the Java implementation, and the way each systems manage memory mapped files but I didn't find an answer.
I am not trying to have the best possible performances for this toy application, I just want to understand why is there such a difference between Linux-based and Windows-based platforms.
I am running MapDB 3.0.2, with JDK8. JVM parameters used: -Xmx8g -XX:+UseConcMarkSweepGC -XX:MaxDirectMemorySize=3G
Thank you!
Gwendal
public static void main(String[] args) throws IOException {
	DB db = DBMaker.fileDB(new File("test")).make();
	HTreeMap<String, String> map = (HTreeMap<String, String>) db.hashMap("test").createOrOpen();

	for(int i = 0; i < 4000000; i++) {
		map.put(UUID.randomUUID().toString(), UUID.randomUUID().toString());
		if(i % 100000 == 0) {
			db.commit();
			System.out.println("commit " + i);
		}
	}
	db.commit();
}

File sync, and the OS / File system settings related to it, can have a massive difference in performance (and durability / corruption if the process or OS crashes).
The first thing to do is compare the I/O per second and the I/O utilization on disk in your two cases.  I suspect that in the windows case it is forcing a flush to disk on each commit, and the linux case it is not.
Also, try disabling memory mapping.  Compare memory mapped (fileMmapEnable) to file channel (fileChannelEnable).  In my experience the RandomAccessFile is horribly slow (and it is single threaded, synchronizing all access).
One can mount a file system in Linux such that it won't properly sync file to disk on sync, which will make it rather fast but also corrupt or lose data on a crash.

It doesn´t matter whether you are using memory mapped store or file channel. The performance on windows 10 / windows 7 with jdk8u152 is about 1/3 the speed compared to linux and macOS. I had to use a memoryDirectDB store on windows just to achieve a usable performance. File based store is alsmost unusable on windows :(


Fix boolean, int, and float parsing. Improve decimal parsing for hive

This depends on https://github.com/NVIDIA/spark-rapids-jni/pull/797
This fixes #7085
It also adds in a bunch of checks to fall back to the CPU if we see a hive table that we might not be able to support because of configs.

build

build


Helm chart prep

Add namespace support
remove AWS hardcoded image names, deployment commands
allow specifying IMAGE_NAME NAMESPACE when running make

@mateuszdrab , would you please explain the use case for your last commit ?

Damn, I meant to commit it to a different branch. Either way, I had a use case where I had to write out the value of the region node label to a file to be included in a dns zone file by bind9 and I achieved that through an init container but the feature wasn't there so I added it.

@mateuszdrab , I captured the gist of your changes (i.e. namespace parametrization and init container support) in #7, since this one has a number od changes that are unrelated. Will close this PR and I will add helm support in a different commit (I have that WIP).


x/tools/gopls: panic in Analyze with patch version in go.mod file

gopls version: v0.15.2/go1.20.4
gopls flags:
update flags: proxy
extension version: 0.41.2
environment: Visual Studio Code darwin
initialization error: undefined
issue timestamp: Sat, 30 Mar 2024 00:43:17 GMT
restart history:
Fri, 29 Mar 2024 22:57:47 GMT: activation (enabled: true)
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.

panic: invalid Go version "go1.22.1" (should be something like "go1.12")

goroutine 191 [running]:
go/types.NewChecker(0x140002ba5d0%3F, 0x140004b60c0, 0x140001e9310, 0x0%3F)
	  check.go:237  0x1e8
golang.org/x/tools/gopls/internal/cache.(*analysisNode).typeCheck(0x140003a8000, {0x14000292410, 0x1, 0x1})
	  analysis.go:1028  0x5fc
golang.org/x/tools/gopls/internal/cache.(*analysisNode).run(0x140003a8000, {0x101c1e998%3F, 0x14000497e30})
	  analysis.go:810  0x1d4
golang.org/x/tools/gopls/internal/cache.(*analysisNode).runCached(0x140003a8000, {0x101c1e998%3F, 0x14000497e30})
	  analysis.go:672  0x104
golang.org/x/tools/gopls/internal/cache.(*Snapshot).Analyze.func6.1()
	  analysis.go:398  0xa4
golang.org/x/sync/errgroup.(*Group).Go.func1()
	  errgroup.go:78  0x5c
created by golang.org/x/sync/errgroup.(*Group).Go
	  errgroup.go:75  0xa0

gopls stats -anon
{
  "DirStats": {
    "Files": 29,
    "TestdataFiles": 0,
    "GoFiles": 1,
    "ModFiles": 1,
    "Dirs": 20
  },
  "GOARCH": "arm64",
  "GOOS": "darwin",
  "GOPACKAGESDRIVER": "",
  "GOPLSCACHE": "",
  "GoVersion": "go1.20.4",
  "GoplsVersion": "v0.15.2",
  "InitialWorkspaceLoadDuration": "55.90625ms",
  "MemStats": {
    "HeapAlloc": 2758320,
    "HeapInUse": 5218304,
    "TotalAlloc": 12841176
  },
  "WorkspaceStats": {
    "Files": {
      "Total": 2,
      "Largest": 57,
      "Errs": 0
    },
    "Views": [
      {
        "GoCommandVersion": "go1.22.1",
        "AllPackages": {
          "Packages": 1,
          "LargestPackage": 1,
          "CompiledGoFiles": 1,
          "Modules": 1
        },
        "WorkspacePackages": {
          "Packages": 1,
          "LargestPackage": 1,
          "CompiledGoFiles": 1,
          "Modules": 1
        },
        "Diagnostics": 1
      }
    ]
  }
}

OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
<OPTIONAL: ATTACH LOGS HERE>

For now, a viable workaround is to install gopls with go1.21+.
However, since this version of gopls nominally supports being build with 1.20, we should fix the crash.

Thanks for the tip, it rarely crash though, looking forward to the fix


[website] Make the Core page refer to Material UI

[x] I have followed (at least) the PR section of the contributing guide.

The current Core page is confusing as it mainly refers to Material UI, which is not a synonym for MUI Core. As we get closer to "officially" introducing (as in stable) Base UI as part of the Core product group offering, that confusion is even more highlighted. To alleviate it, and to also better sit on the same level as the to-be-launched Base UI page (https://github.com/mui/material-ui/pull/36622), this PR changes the wording of this page to refer to Material UI directly. In the meantime, we'll be missing a Core-focused page, but it is even to be discussed if we really need it.
By the time this and the Base page PR are merged, we'll have marketing pages for two Core products.
Tasks

[x] First pass at adjusting the copywriting.
[ ] Copywriting review.
[ ] Adjust page name & routing.
[ ] Verify SEO-related implications to make sure we're not damaging anything there.

@samuelsycamore just an FYI that I was pulling text changes from the Material UI Overview page! Totally down for new stuff if we feel like revamping them a bit for marketing purposes.


Replaces the header logo with original ZF logo (SVG)

Before

After

@froschdesign I tried the SVG logo locally but it has some issue with the size, see the attached image. Can you check please? Thanks!

@ezimuel

Can you check please?

Sure!

@froschdesign Thanks!


Switch back to feature/body branch

Switch back to feature/body branch, pull changes using git pull.

Test comment


Failed to compile CursorPlugin

Helo!
First sorry for my english and thanks for making this tool available.
I use the wavesurfer.js in my vue project. This is instaled with npm.
The wavesurfer is work just with a little problem in load the waveform for some audios.
But my realy probelm is with CursorPlugin.
On add import CursorPlugin from 'wavesurfer.js/src/plugin/cursor.js' in my component, return this:

Failed to compile.
./node_modules/wavesurfer.js/src/plugin/cursor.js 71:18
Module parse failed: Unexpected token (71:18)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|      * @type {CursorPluginParams}
|      */

defaultParams = {

|         hideOnBlur: true,
|         width: '1px',

I tried add import CursorPlugin from 'wavesurfer.cursor.js' but not exist wavesurfer.cursor in node_modules
Exists other way to use CursorPlugin in my vue.js project?
Thanks!

[x] I have checked the FAQ and it doesn't solve my problem.
[x] I have checked the documentation and it doesn't solve my problem
[x] I have searched for already open issues which desribe my problem.
[ ] The issue I'm having is related to and caused by wavesurfer.js, not by other software (which maybe packages and uses wavesurfer incorrectly) – In that case you should open the issue on the respective project pages.

Please make sure you provide the following information (if applicable):
Wavesurfer.js version(s):
3.2.0
Browser and operating system version(s):
Ubuntu 18.10 and Crhome  78.0.3904.87
Code needed to reproduce the issue:
I'm not allowed to publish
Use behaviour needed to reproduce the issue:
import CursorPlugin from 'wavesurfer.js/src/plugin/cursor.js' in vue.js component

Import it from dist instead:
import CursorPlugin from 'wavesurfer.js/dist/plugin/wavesurfer.cursor.js'

Importe-o de dist em vez disso:
import CursorPlugin from 'wavesurfer.js/dist/plugin/wavesurfer.cursor.js'

Thanks!
It worked


Duplicate projects on $bloop project --verbose

For some reason test projects are listed twice on bloop
$ bloop projects --verbose
[D] Projects loaded from '/home/chris/dev/bitcoin-s-core/.bloop':
bench
bench-test
bitcoindRpc
bitcoindRpcTest
bitcoindRpcTest-test
bitcoins
bitcoins-test
chain
chain-test
chainTest
chainTest-test
core
coreTest
coreTest-test
dbCommons
dbCommons-test
doc
doc-test
eclairRpc
eclairRpcTest
eclairRpcTest-test
node
node-test
nodeTest
nodeTest-test
secp256k1jni
secp256k1jni-test
testkit
wallet
wallet-test
walletTest
walletTest-test
zmq
zmq-test
[D] Elapsed: 9.210596 ms

That's because bloop separates projects based on test/compile scope. I removed non-test modules from test scope (https://github.com/bitcoin-s/bitcoin-s-core/blob/a48147a12534a33553bef44c47e768c2bb4df5b8/build.sbt#L122), but if we do the same for test modules (remove the compile scope), we get compiler errors. So that seems to be a limitation we have to live with for now.


Bump to OPA v0.62.1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 15 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.09%) to 25.191%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

build.go
0
15
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.09%

Covered Lines:
362

Relevant Lines:
1437

💛  - Coveralls


Unknown encoding of isco88 column

When reading the data to convert the isco08 to isco88, the read_pdf() function works really well, except that the data in the pdf itself seems to be randomly encoded.
> isco88_08_raw$isco88 %>% head()
[1] "\022\023\024\024" NA                 NA                 NA                 NA
[6] "1222"

I know for a fact that [1] should be a character encoded number, like [6].
> Encoding(isco88_08_raw$isco88) %>% head()
 [1] "unknown" "unknown" "unknown" "unknown" "unknown" "unknown"
> utf8::as_utf8(isco88_08_raw$isco88) %>% head()
 [1] "\022\023\024\024" NA                 NA                 NA
 [5] NA                 "1222"

Over half of the isco88 vector is read in this "unknown" encoding. @gronert-m Do you know what this encoding is? I'll send you a link with the output file separately so you can see. My guess is that it the root of the issue is how pdftools::pdf_data() reads the page, since this is the base of the whole function. The column that causes troubles is written in a slightly different font -- this could be the issue....

superseded by #149


Dropdown should ignore clicks on s (and s?) within the dropdown

Hello.
I tried to use dropdown plugin like a special area for options (some radio buttons) and found a strange behavior. You can see it here (try to click on select tag or labels for radio buttons): http://jsbin.com/jorota/edit?html,output
There is a simple check in bootstrap.js in this plugin
/input|textarea/i.test(e.target.tagName)

this behavior can be fixed by adding new tags through the '|'
/input|textarea|select|label/i.test(e.target.tagName)

is it possible to add this fix to release? or this is not a type of regular using of this plugin? but in this case: why there is 'textarea' in condition? :)
thank you :) and sorry for my bad english

Hi again :)
this fix was added in version 3.3.5 but was lost it in 3.3.7
are you going to support this in 3.x.x? :)

Bootstrap 3 is no longer being officially developed or supported.
All work has moved onto our next major release, v4. As such, this issue or pull request is being closed as a "won't fix." For additional help and support, we recommend utilizing our community resources. Thanks for your understanding, and see you on the other side of v4!
<3,
@mdo and team


cmctl: 1.8.2 -> 1.9.1

Description of changes
https://cert-manager.io
Updates cmctl to version v1.9.1.
Changes the way completions are written in order to capture runtime
completion of sub-commands and flag.
To inspect upstream changes

Release on GitHub
Compare changes on GitHub

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin
~- [ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)~

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[x] (Package updates) Added a release notes entry if the change is major or breaking
[x] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module
[x] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofek @superherointj anything left for me to do?

@ofek @superherointj anything left for me to do?

Yes.

Why were we pinged? 🤔

Why were we pinged? thinking

Because @JoshVanL mentioned you?

Right, why?

Sorry! Looks like I fat fingered the @ 🙂

I've gone ahead and added myself to the maintainers list and added myself as a maintainer to the cmctl package.
I personally use nixos and am a maintainer of cert-manager.
Packaging and releasing cert-manager is part of my day job :slightly_smiling_face:

I've gone ahead and added myself to the maintainers list and added myself as a maintainer to the cmctl package.
I personally use nixos and am a maintainer of cert-manager.
Packaging and releasing cert-manager is part of my day job slightly_smiling_face

Great.
I gave you feedback 4 times. I haven't heard from you on any of them.
For example, you are using Go style indentation instead of Nix indentation (nixpkgs-fmt).
Or, shell completion is it really not working? I asked. No answer.
If you just do what I said (4 things), I think we are good to go.

I gave you feedback 4 times. I haven't heard from you on any of them.
For example, you are using Go style indentation instead of Nix indentation (nixpkgs-fmt).
Or, shell completion is it really not working? I asked. No answer. Note, that you are changing code that I'm not sure is the problem you pointed out. So I want to confirm that.
If you just do what I said (4 things), I think we are good to go.

Hi @superherointj, sorry- I can't see any of that review from my side. It might be a case that that the GitHub review is still pending and needs to be "submitted"?

Hi @superherointj, sorry- I can't see any of that review from my side. It might be a case that that the GitHub review is still pending and needs to be "submitted"?

Thanks for pointing out problem here. Sorry about that. On my POV you were just ignoring my comments. :D

Thanks for pointing out problem here. Sorry about that. On my POV you were just ignoring my comments. :D

No wozza! :slightly_smiling_face:
I'll get those fixed up.

@superherointj, hopefully fixed all of your review comments. PTAL

Result of nixpkgs-review pr 183093 run on x86_64-linux 1

1 package built:

cmctl


[BUG] OpenSearh buffer.constants is undefined error in my VUEJS Project

Hi, everyone. When I try to use opensearch library in my VueJS Project, I got a problem.
Firstly, I installed npm install @opensearch-project/opensearch. When I build, I got V8 error below.
This dependency was not found: v8 in<EMAIL_ADDRESS>To install it, you can run: npm install --save v8 Error from chokidar (C:\node_modules): Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp' PS C:\Users\tt\Desktop\repo\TMS\tms-web-ui> npm install --save v8
End then, I installed "npm install --save v8". After the installing, my project was successfully build but when I run serve, my browser said buffer.constants are undefined. Error is below.
Uncaught TypeError: buffer.constants is undefined     <anonymous> webpack-internal:///./node_modules/@opensearch-project/opensearch/lib/Transport.js:53     <anonymous> webpack-internal:///./node_modules/@opensearch-project/opensearch/lib/Transport.js:734     node_modules opensearch-project/opensearch/lib/Transport.js@http://localhost:8080/js/chunk-vendors.js:719     __webpack_require__ http://localhost:8080/js/app.js:849     fn http://localhost:8080/js/app.js:151     <anonymous> webpack-internal:///./node_modules/@opensearch-project/opensearch/index.js:35     <anonymous> webpack-internal:///./node_modules/@opensearch-project/opensearch/index.js:354     node_modules opensearch-project/opensearch/index.js@http://localhost:8080/js/chunk-vendors.js:671     __webpack_require__ http://localhost:8080/js/app.js:849     fn http://localhost:8080/js/app.js:151     <anonymous> webpack-internal:///./src/tms/open_search_api.js:2     js http://localhost:8080/js/app.js:2169     __webpack_require__ http://localhost:8080/js/app.js:849     fn http://localhost:8080/js/app.js:151     <anonymous> webpack-internal:///./src/tms/index.js:9     js http://localhost:8080/js/app.js:2145     __webpack_require__ http://localhost:8080/js/app.js:849     fn http://localhost:8080/js/app.js:151     <anonymous> webpack-internal:///./src/main.js:8     js http://localhost:8080/js/app.js:2073     __webpack_require__ http://localhost:8080/js/app.js:849     fn http://localhost:8080/js/app.js:151     1 http://localhost:8080/js/app.js:2470     __webpack_require__ http://localhost:8080/js/app.js:849     checkDeferredModules http://localhost:8080/js/app.js:46     <anonymous> http://localhost:8080/js/app.js:925     <anonymous> http://localhost:8080/js/app.js:928
I must to use opensearch library in my project. Can you help me to fix this problem?

Can you explain your overall architecture a little? The client is a node.js client and isn't designed to talk to an OpenSearch cluster directly from a browser. Usually you proxy browser requests through a web server.

I am trying to send request directly from my UI which works on VueJS environment. I did not use any proxy to redirect my requests.

@zeynep-turker I don't think this is an issue specific to OpenSearch. Have you tried solutions proposed one StackOverflow?

When I created the project again, the problem was solved interestingly. Before that, I remember trying the solution  on StackOverflow, but it did not work. Thanks anyway.

We used the node.js project to use OpenSearch. Before this, I remember trying the solution on StackOverflow but it didn't work. Thanks anyway.


Report conflicting explicit bindings

Not Slang's fault, but it would be great if it will report conflicts in external bind locations.
For example:
layout(set = 0, binding = 0) uniform texture2D gTexture;
layout(set = 0, binding = 0) uniform sampler gSampler;

The shader compiles successfully. I don't know if it's a valid GLSL shader or not, perhaps the correct place for this issue is glslang.

This has some overlap with #38.
I'd like to make this a warning (two parameters with different names and overlapping bindings), with an option to make it trigger an error. This hasn't bubbled up to the top of the priority list yet.
As far as I understand, this is valid GLSL. It is okay to define overlapping bindings, so long as a given compiler shader ("version") only uses one or the other (I don't know if that is a static constraint or a dynamic one).

Is it valid even if the declarations are in the same shader?
Issue #96 both the constant-buffer and sampler are bound to the same location and are being used in the shader, I don't see why this is valid.
I'm not suggesting Slang is doing anything wrong. Either glslang has a bug or GLSL has a bug.

Do we get errors reported from the driver?
I would need to comb the spec carefully to know what is or isn't valid.

I implemented a basic version of this in #118. I'll close this if/when I get confirmation that it seems to meet requirements (and doesn't give false positives).

I've seen this trigger now in cases where it should, and nobody has reported false positives (yet), so I'm going to consider this good.


new raw blocks: listen, frontend, backend

Proper formatting of indented multiline configurations, new raw blocks: listen, frontend, backend.

thank you :+1:


feat: change jinja block/start delimiters for renovate support

This changes the jinja delimiters so that renovate doesn't choke when parsing these files

<% ... %> -> #% ... %#
<< ... >> -> {% ... %}

LGTM


feat: print diff resource as yaml

AS-IS
Output diff data in text format
{data={key1=val1}, metadata={ownerReferences=[{name=kube-root-ca.crt, uid=1ef74cb4-dbbd-45ef-9caf-aa76186594ea, apiVersion=v1, kind=ConfigMap}]}}

{metadata={ownerReferences=[{apiVersion=v1, kind=ConfigMap, name=kube-root-ca.crt, uid=1ef74cb4-dbbd-45ef-9caf-aa76186594ea}]}, data={key1=different value}}

problem : It's difficult to compare

TO-BE
Output diff data in yml format
data:
  key1: "val1"
metadata:
  ownerReferences:
  - name: "kube-root-ca.crt"
    uid: "1ef74cb4-dbbd-45ef-9caf-aa76186594ea"
    apiVersion: "v1"
    kind: "ConfigMap"

 ---
metadata:
  ownerReferences:
  - apiVersion: "v1"
    kind: "ConfigMap"
    name: "kube-root-ca.crt"
    uid: "1ef74cb4-dbbd-45ef-9caf-aa76186594ea"
data:
  key1: "different value"

If the user sorts fields through Jackson settings .enable(SerializationFeature.ORDER_MAP_ENTRIES_BY_KEYS)
it will look much better because the keys will be displayed in sorted order.

As mentioned above, users can configure Jackson to sort field keys when logging YAML files by enabling the SerializationFeature.ORDER_MAP_ENTRIES_BY_KEYS setting
This ensures that the YAML fields are ordered alphabetically, making the log output more readable and consistent

Thank you @10000-ki !

Hi @10000-ki. Thanks for the PR!
I think printing the whole actual and desired resource is a bit inconvenient since we still need to copy and paste it into other tools to get the real diff. How about improving the logging logic to directly print the actual diff, like shown below?
2024-10-02 14:30:29,489 1 i.j.o.p.d.k.SSABasedGenericKubernetesResourceMatcher [DEBUG] Diff between actual and desired state for resource: Deployment with name: test in namespace: default is:
---
+++
@@ -15,1 +15,1 @@
-      - image: "nginx:1.17.0"
+      - image: "nginx:1.17.1"

Hi @bachmanity1,
I was kind of thinking the same thing but seeing the resource in YAML format is already helpful. We'd happily consider a PR to output the actual diffs! Keep in mind, though, that we want to keep this output as efficient as possible so it should probably be only activated via a flag.


Unique Block Producers stat is awkwardly located in blocks GQL endpoint

While the stat of unique block producers in last x blocks is related to blocks, it is awkwardly located within the blocks query. It might be more suitably located in the summary endpoint, as it is a stat on blocks as a whole.

https://github.com/Granola-Team/mina-indexer/pull/1326#issuecomment-2245092745

https://github.com/Granola-Team/mina-block-explorer/pull/949/files
This PR should have been one or two lines of code. If this pattern continues, we can expect each new state to require 50+ lines of code instead of a single one or two.


Add ISSN to list of digital identifiers

needed by the "publications" module, to identify journals
https://www.issn.org
https://en.wikipedia.org/wiki/International_Standard_Serial_Number
The pattern should be something like ^[0-9]{4}-[0-9]{3}[0-9xX]$

@apdavison yes. I'll prepare a PR for you to review.

That was quick! Many thanks @lzehl !


WFLY-10026 Clustering TS: replace multicast-based discovery protocol (MPING) with static discovery (TCPPING)

Let's see if this helps at least partially.
Jira
https://issues.jboss.org/browse/WFLY-10026

retest this please

Replaced with https://github.com/wildfly/wildfly/pull/11011


Doesn't reload on Added Javascript

When Changing new JS it doesn't reload the whole page

JS has the same configuration as Sass and templates. This seems to be an Operating System problem. Will open this ticket when working with Docker.


Enable parsing of steps from remote files

e.g. https://gitlab.com/iidsgt/biocwl/blob/master/Workflows_Release/DAPHNI-DNA.cwl
via Evan Clark

PS. The above file contains files referenced as https://gitlab.com/iidsgt/biocwl/raw/master/Tools/BWA-Mem.cwl but this is out dated so this link will fail with a 404 error


Expose flow control logic in the response object

The DeviceFlowResponse object is passed back to the callback and is
used as a message channel between the consumer and this library. This
remove threading requirement from the library and the consumer will be
repsonsible for proper threading.
The logic is added to DeviceFlowResponse class to maintain backward
compatibility.

Hi @yacaovsnc, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Yang Cao (VSNC)). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

Looks good to me.


Help Wanted

Can you email me a special tutorial? I want to make a modded Just Dance game called Just Dance INFINITY.

Just curious, will this mod basically have every Just Dance song?

I am trying to make a version with a bunch of songs, so perhaps we could try to make it together? I'm still pretty new to modding Just Dance though lol

Okay.
On Sat, Oct 15, 2022, 15:32 DEMONITIZED BOI @.***>
wrote:

I am trying to make a version with a bunch of songs, so perhaps we could
try to make it together? I'm still pretty new to modding Just Dance though
lol
—
Reply to this email directly, view it on GitHub
https://github.com/wukko/ubiart-secure-fat/issues/1#issuecomment-1279816908,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATKMOCBXENZNYXOSSOEDLT3WDMBDHANCNFSM6AAAAAAQWKTFLU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Do you know where I can find IPK files of the songs I mentioned?

Do you know where I can find IPK files of the songs I mentioned?

half of the songs aren't even in jd, so finding ipks for those would be impossible

not an issue related to the tool

yeah my house burned with my old laptop
On Fri, Oct 14, 2022, 22:41 DEMONITIZED BOI @.***>
wrote:

Just curious, will this mod basically have every Just Dance song?
—
Reply to this email directly, view it on GitHub
https://github.com/wukko/ubiart-secure-fat/issues/1#issuecomment-1279639477,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATKMOCG6YDEFWZ6I5LTIOS3WDIKV7ANCNFSM6AAAAAAQWKTFLU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Register error: Failed to join multicast group on all interfaces !

I am running the consul discovery service as needed, however when creating even an example service I get thrown the following message in the console.
Server go.micro.srv.hello-151a8cbb-bab6-4a61-88f9-08bca64b4259 register error: Failed to join multicast group on all interfaces!
I don't know if its a consul problem with registering on the network or something to do with the service.

this issue comes from fact, that go-micro initialize defaults for registry, and default registry is mdns. When you import registry package you always have mdns registry. And if it can't start this error happens.

@djboboch if you want to use consul registry you need to explicitly "request" it by setting MICRO_REGISTRY=consul environment variable. Otherwise the default registry is used like @vtolstov says.

Thank you setting the variables and restarting the machines has solved the problem.