[BUG]: After compiling turbo application, autowire imports from the wrong location.

Describe the bug
After you compile a Turbo application, autowire will import from the wrong location /src instead of the compiled location.
To Reproduce
Compile any turbo application that has at least one controller with autowire enabled.

Reopening because it is based on itself, so when checking for compilation it is checking for files that exist for itself as itself is compiled.

Reopening, yet again :( Looks like when registering files it is also trying to register .d.ts files, which of course is wrong, will ignore .ts files in production.


Tool-bar on the left position messes up Tree View right border position on rezise

With the tool-bar positioned on the left, when I try to re-size the Tree View pane, the right border of the Tree View, which is being dragged, moves from under the mouse pointer to the right, possibly by the same amount of the tool-bar size.
I'm using:
Atom 0.210.0
tool-bar 0.1.7
tool-bar-main 0.0.8

Noticed this too before. Actually this is a Atom issue, but haven't had the time to report a proper bug report.
var x = document.createElement('div');
x.appendChild(document.createTextNode('test'));
atom.workspace.addLeftPanel({item:x,priority:10});

Upstream: https://github.com/atom/tree-view/issues/533

Fixed by atom/tree-view#534


Disallow editing dedicated servers

Just in case, could be nice to still be able to rename a dedicated server club activity, because it's not possible from the game


Label selector

Moving from custom tag filtering to label selector
Basically moving from --tags=installation=test to --selector=installation=test, where --selector is the standard kubernetes label selector from https://pkg.go.dev/k8s.io/apimachinery/pkg/labels#Selector, allowing for any label selector we are used to.
Before
$ ./silence-operator sync --dir ./test --kubernetes.kubeconfig "$(cat ~/.kube/config)" --tag installation=gauss
{"caller":"github.com/giantswarm/k8sclient/v6/pkg/k8srestconfig/rest_config.go:131","level":"debug","message":"creating REST config from kubeconfig","time":"2022-04-20T16:16:58.443043+00:00"}
{"caller":"github.com/giantswarm/k8sclient/v6/pkg/k8srestconfig/rest_config.go:139","level":"debug","message":"created REST config from kubeconfig","time":"2022-04-20T16:16:58.444199+00:00"}
{"caller":"github.com/giantswarm/silence-operator/cmd/sync/runner.go:225","level":"debug","message":"silence `gauss-wrongtarget` does not match environment by `installation` key [regexp: `wrong`, value: `gauss`]","time":"2022-04-20T16:16:59.824704+00:00"}
{"caller":"github.com/giantswarm/silence-operator/cmd/sync/runner.go:117","level":"debug","message":"creating desired silence CR `gauss-goodtarget`","time":"2022-04-20T16:16:59.824758+00:00"}
{"caller":"github.com/giantswarm/silence-operator/cmd/sync/runner.go:124","level":"debug","message":"desired silence CR `gauss-goodtarget` has been created","time":"2022-04-20T16:16:59.947656+00:00"}

After
$ ./silence-operator sync --dir ./test --kubernetes.kubeconfig "$(cat ~/.kube/config)" --selector=installation=gauss
{"caller":"github.com/giantswarm/k8sclient/v6/pkg/k8srestconfig/rest_config.go:131","level":"debug","message":"creating REST config from kubeconfig","time":"2022-04-20T16:37:23.790887+00:00"}
{"caller":"github.com/giantswarm/k8sclient/v6/pkg/k8srestconfig/rest_config.go:139","level":"debug","message":"created REST config from kubeconfig","time":"2022-04-20T16:37:23.792208+00:00"}
{"caller":"github.com/giantswarm/silence-operator/cmd/sync/runner.go:196","level":"debug","message":"silence `gauss-wrongtarget` with labels `installation=wrong` does not match `installation=gauss` selector","time":"2022-04-20T16:37:24.920613+00:00"}
{"caller":"github.com/giantswarm/silence-operator/cmd/sync/runner.go:100","level":"debug","message":"creating desired silence CR `gauss-goodtarget`","time":"2022-04-20T16:37:25.040498+00:00"}
{"caller":"github.com/giantswarm/silence-operator/cmd/sync/runner.go:107","level":"debug","message":"desired silence CR `gauss-goodtarget` has been created","time":"2022-04-20T16:37:25.152684+00:00"}

Not working on this anymore.


Exclusivity refactor and fixes.

Refactor exclusivity logic in preparation for exhaustive round-trip verification.
This also makes the code more robust and enables a fix for rdar://36989789 [SR-6862]: "Unexpected partial_apply use" in SILOptimizer/Mandatory/DiagnoseStaticExclusivity.cpp.

@swift-ci test.

@swift-ci Test Source Compatibility

@swift-ci Test Source Compatibility


Bleson thread crashes on some malformed packet (?)

I'm using Bleson 0.1.8 on Linux (Debian 10 w/ kernel 5.12.0) with a small daemon that silently fails after a couple of days.
The issue seems to come from some kind of malformed packet (or maybe an empty one?).
Anyway, here is the trace back. I'm not sure what can be done at application level, except restarting the thread. It would be nice to discard invalid packet rather than crashing the processing thread.
Thanks.
Exception in thread HCISocketPoller:
Traceback (most recent call last):
  File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.7/threading.py", line 865, in run
    self._target(*self._args, **self._kwargs)
  File "/home/eblot/.local/lib/python3.7/site-packages/bleson/providers/linux/linux_adapter.py", line 59, in _socke
t_poller
    self._on_data(data)
  File "/home/eblot/.local/lib/python3.7/site-packages/bleson/providers/linux/linux_adapter.py", line 268, in _on_d
ata
    self._handle_meta_event(hci_event_packet)
  File "/home/eblot/.local/lib/python3.7/site-packages/bleson/providers/linux/linux_adapter.py", line 248, in _handle_meta_event
    advertisement = AdvertisingDataConverters.from_hcipacket(hci_packet)
  File "/home/eblot/.local/lib/python3.7/site-packages/bleson/core/hci/type_converters.py", line 101, in from_hcipacket
    return cls.from_hcipayload(hci_packet.data)
  File "/home/eblot/.local/lib/python3.7/site-packages/bleson/core/hci/type_converters.py", line 160, in from_hcipayload
    raise ValueError("PAyload is not divisible by 2 for UUID16")
ValueError: PAyload is not divisible by 2 for UUID16

Are you sure you're using 0.1.8?  0.1.8 ignores all exceptions in _on_data, ever since https://github.com/TheCellule/python-bleson/commit/e4f10bea80bb3a955b7f2d6ef7003a841a975191


Is mmcv-full compatible with jetson tx2?

Just don't know how to install mmdetection on an ARM computer(nvidia jetson tx2).
Any instructions?
Thanks a lot.

It is not supported yet. But PRs are welcome!


adding mima

This is a no frills mima integration.
I wanted to do something a bit more fancy then just copy/pasting and changing the dep for the mima setting, but wasn't sure if it was super necessary.  I was going to use an implicit class on project that exposed a new function withMima(...) which would allow each project to opt into mima, and that function could generate the setting.  This is probably good for now, but if we want to start tracking more than just one pervious version, we might want that function at some point.

Codecov Report

Merging #583 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           develop    #583   +/-   ##
=======================================
  Coverage     84.9%   84.9%
=======================================
  Files           99      99
  Lines         4431    4431
  Branches       367     356   -11
=======================================
  Hits          3762    3762
  Misses         669     669

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 6073ed8...b265627. Read the comment docs.

I noticed that we have cross publishing for only 2.11 and 2.12, we dropped 2.10 now, right? It looks like we haven't yet published anything for 2.12, is that right?  If I try to run mima using 2.12 artifacts, I get failures.  I can, for now, change this a bit so that it only generates the setting for 2.11, and when we publish 2.12 artifacts, remove that restriction.
Something along the lines of:
def withMima(versions : String*) : Project = {
      project.settings{
        mimaPreviousArtifacts := (if(scalaBinaryVersion.value == "2.11") {
          versions.map{ v =>
            organization.value %% s"${moduleName.value}" % v
          }.toSet
        }else{
          Set.empty
        })
      }
    }

After we publish 2.12, we can then remove that if statement.

So, let me clarify my previous comment :).
Currently, the scala version of Colossus is set to 2.12, and we cross publish to 2.11.  Since we have not published anything yet(from what I can tell), mima fails since it cannot find the 2.12 artifacts.  However, if I run +mimaReportBinaryIssues, it will run that for all scala versions listed, and work for 2.11.  I just need to disable it for 2.12 until we publish artifacts


some UI feature

I have 3000 and more spam numbers.
Maybe to hide all spam numbers from 'settings - list'. And to make a special list only for spam numbers.

No matter how many numbers, it won't exceed 60% of the screen height, and in the latest version there are scrollbars, they are scrollable, I don't think it's necessary to hide them.

Supported in the action build: https://github.com/aj3423/SpamBlocker/actions/runs/10957829013
A new context menu item "Search Rule".

Good idea, currently it's swipe left, but I'll change it to close on losing focus, it'll more convenient and intuitive.

No need to support swipe left since it will disappear when losing focus.
The description is supposed to be simple, one line is enough. But the regex can be very long, it's displayed in multi-lines, up to 10 lines.

I try to scroll the settings down. I must catch the narrow string "Message Rules" when scrolling down.

Try the scrollbar, put your finger at the most right edge of the screen and start dragging up/down.

You don't sort 'Message Rules'. Why?

Actually they are sorted, in the order of:  priority -> description -> regex
BTW, those regex like 0800.... will never work, the leading 0 is ignored, unless the regex flag "Raw Number" is set. I suppose these rules were imported, not manually added, why not import them as a single rule, why 2000 rules?

Yeah, it looks like (11|22|33...),  I mean the feature "Import .csv as a single rule" by long pressing the "New" button.
2000 numbers should be fine, but you don't want to edit it later, since it's super long.

Added in the action build: https://github.com/aj3423/SpamBlocker/actions/runs/11033104414
"Delete All(30) Rules" and "Delete Duplicated Rules"


dev: Remove block_hash from outpoint

[x] resolves #232
[x] follows contribution guide
[x] code change includes tests

@lomasson pls also remove block_hash from the header (and revert block hash validation to the state at https://github.com/keep-starknet-strange/raito/blob/851e34779645bf4996a79ac6630c3770b4f70b93/packages/consensus/src/validation/work.cairo#L6)

validate_proof_of_work

@m-kus please remind me why do we keep hash in the Header in the first place? Seems superfluous.

@m-kus Can you check if I've make what you want me to do, I'm not sure because a test doesn't pass, and I'm not very sure if i take the right way to resolve that.

@m-kus please remind me why do we keep hash in the Header in the first place? Seems superfluous.

It was used for Utreexo leaf hashing (not anymore)

@m-kus Can you check if I've make what you want me to do, I'm not sure because a test doesn't pass, and I'm not very sure if i take the right way to resolve that.

@lomasson I see that CI is green, which test are you talking about? The diff looks ok to me

@m-kus i don't how ci has green but somes testes don't pass(verification of utreexo_169 and  outpoint_poseidon_hash), i have fix them and now i think its good, wdyt ?


Issue with tus.upload Redirecting from HTTPS to HTTP, Causing an Error

Question
The issue is as described in the title. When attempting to upload files from the same or a different domain, the file transfer works fine in local and HTTP environments. However, when using HTTPS, the upload request is redirected to HTTP, causing an error.
httpStack.js:64 Mixed Content: The page at 'https://mydomain.io/pop' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://mydomain.io/f/files/c4b535d051e35cfeb87e000286adbf39'. This request has been blocked; the content must be served over HTTPS.
Below is the relevant portion of my Nginx configuration, where only domain-related information has been modified.
server {     listen 80;     server_name mydomain.io;     client_max_body_size 10240m;     return 301 https://$host$request_uri;  } server {     listen 443 ssl;     server_name mydomain.io;     client_max_body_size 10240m;     ssl_certificate /etc/ssl/certs/star__io.crt;     ssl_certificate_key /etc/ssl/private/star__io.key;     ssl_protocols TLSv1.2 TLSv1.3;     ssl_prefer_server_ciphers on;     ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH";     location / {         proxy_pass http://$backend;         proxy_set_header Host $host;         proxy_set_header X-Real-IP $remote_addr;         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;         proxy_set_header X-Forwarded-Proto $scheme;     } }
Here is the code related to @tus/server and @tus/file-store in my Node.js application:
`const { Server: TusServer, EVENTS } = require('@tus/server');
const { FileStore } = require('@tus/file-store');
const tusServer = new TusServer({
path: '/f/files',
datastore: new FileStore({
directory: uploadPath,
maxSize: 10 * 1024 * 1024 * 1024 // 10GB
}),
maxUploadSize: parseInt(process.env.TUS_MAX_UPLOAD_SIZE, 10) || Infinity,
chunkedTransferDecoding: process.env.TUS_CHUNKED_TRANSFER_DECODING === 'true' || false,
threadLocalCache: process.env.TUS_THREAD_LOCAL_CACHE === 'true' || false,
});
router.all('/files', (req, res) => {
tusServer.handle(req, res);
});
router.all('/files/*', (req, res) => {
console.log(Received request: ${req.method} ${req.originalUrl});
tusServer.handle(req, res);
});
tusServer.on(EVENTS.POST_FINISH, async (req, res, upload) => {
console.log("-----------------------------------Upload complete event triggered");
try {
~~~~
} catch (error) {
console.error("Error during POST_FINISH event processing: ", error);
}
});`
And here is the tus.upload code:
`
Array.from(files).forEach(file => {
const fileSize = file.size;
let upload = new tus.Upload(file, {
endpoint: 'https://mydomain.io/f/files',
metadata: {
filename: file.name,
filetype: file.type,
filesize: fileSize.toString()
},
retryDelays: [0, 1000, 3000, 5000],
onError: function (error) {
console.log('Failed because: ' + error);
},
onProgress: function (bytesUploaded, bytesTotal) {
const percentage = (bytesUploaded / bytesTotal * 100).toFixed(2);
progressBar.style.width = ${percentage}%;
progressBar.setAttribute('aria-valuenow', percentage);
progressBar.innerHTML = ${percentage}%;
},
onSuccess: async function () {
// Success logic
}
});
upload.start();

});`
Additionally, the upload works correctly when sending to https://master.tus.io/files/.
Setup details
Runtime Environment: ubuntu 22.04, Chrome, Node.js 20.17.0, Express.js, EJS
Used tus-js-client Version: 4.1.0
Used tus Server Software: @tus/file-store 1.4.0, @tus/server 1.7.0
I apologize for any formatting issues; I'm still getting the hang of using GitHub.

I found the reason for the error. During the merge process, a colleague made changes to the file settings where the meta tags are stored.
<meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests" />

I think this is caused by not setting the respectForwardedHeaders in tus-node-server: https://github.com/tus/tus-node-server/tree/main/packages/server#example-use-with-nginx
Using the meta tag just covers the symptoms (insecure requests) instead of addressing the root cause (why is tus-node-server returning insecure URLs)?

However, I had already configured it before discovering that the meta code had been modified, but that solution didn't work. Does it need to be used together with the meta code?

Using Content-Security-Policy: upgrade-insecure-requests is not necessary (neither via the meta tag or as a HTTP header) to get tus uploads working if the tus server and proxy are configured properly.


Generalize consistent hashing

So it can be used outside the context of cluster resource mapping

Rebasing off Master should restore green CI builds.

If this PR is still relevant, then please fix conflicts, rebase and get a green CI build.
If the PR is no longer relevant please close.
This PR will be closed at the end of January 2021 otherwise.

If this PR is still relevant, then please fix conflicts, rebase and get a green CI build.
If the PR is no longer relevant please close.
This PR will be closed at the end of January 2021 otherwise.


TypeError: descriptor 'property' requires a 'kivy._event.EventDispatcher' object but received a 'method_descriptor'

I am building an android app using kivy and buildozer. App crashes on start and I found this TypeError. So iget the logs using logcat and so this error after some lines from traceback. I'm using Kivy 1.9.0 and Python 2.7.9 Is there a way to fix this ? Please tell me how to fix this one. Thank you. T_T
TypeError: descriptor 'property' requires a 'kivy._event.EventDispatcher' object but received a 'method_descriptor'
main.py, main.kv, log(from logcat), buildozer.spec
mycodes.zip
Thank you so much for your time T_T

There is multiple issue with your code, like starting a Thread that change the text of widget. This is forbidden to change the state of Widget that may have an impact of OpenGL then crash.
This is not the crash you have, but unless you have a reproducible code, this issue came from your app.
Aka somewhere you set a method instead of a value (int/str/etc)


Use more ES6 features

Let me know if there are any issues.

This conflicts with the latest update for looping audio. Could you fix and squash commits here?

Updated it, let me know if there are any other issues, there is a bug in the pause functionality I'm trying to work through.

Sorry for the delay - did you still want to merge this or submit another PR with more changes?

You can merge if you want

I can't reopen this PR since you deleted your fork.

The fork was also deleted locally, the PR will have to come some other time.


add RProject.Rtools 4.0.1

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@ItzLevvie I am not sure about the PackageVersion: 4.0 as opposed to PackageVersion: 4.0.1, since this is a new version of Rtools4 and 4.0.0 already exists in winget-pkgs. So 4.0 seems confusing IMHO. What do you think?

@jeroen Would it be possible to use semantic versioning for Rtools everywhere? On https://cran.r-project.org/bin/windows/Rtools/ the latest version's file name is rtools40v2-x86_64.exe and in Windows > Apps & Features it shows up as Rtools 4.0 (<IP_ADDRESS>). This is a slightly confusing, see above.

IMHO it would be better to name it rtools-4.0.1-x86_64.exe and Rtools 4.0.1, respectively (cf R-4.1.0-win.exe for base R).

@ItzLevvie thanks! An Rtools 4.0 package is indeed the proper solution

Updating the manifest seems to be the right solution in this particular case since the version tag is not properly set in the installer.
In general, though, I still think it would be better to have a manifest for every (proper) version. At least this is how I read @denelon's advice to "create a new manifest (assuming the URL is unique to a specific version)" for new versions of packages and "to retain manifests for every valid version that may still be installed".
Older versions of RTools are still available back to RTools26 at the source, Chocolatey for example also lists multiple versions. Why should this be any different with winget? The default winget install rtools command (i.e. without the --version tag) or winget upgrade ensure that users get the recommended latest version. But if they need to get an old version for e.g. debugging they still can.
@ItzLevvie While I agree with the solution, I have to say that I am puzzled by your style. Maybe it's just me, but it feels quite insincere to have the moderator open another PR (#16740 by the way) without notice instead of waiting for the OP to react to and fixing the issue. Even more so when it's done with a second account with the stated goal "to merge my own PRs to make my changes available to production as soon as possible." Is this a race somehow?

This feels like volunteer contributions are not valued very much here. I am not sure whether this is the sentiment you want to convey.

I'm sorry if that's what you think - anyone is free to contribute to the catalog and that's why this repository was open-source to begin with. Without anyone's help, it wouldn't be a "package manager" as it wouldn't have that many applications.
The second account wasn't made to "race" with anyone. It was created merely to create "own" PRs and get it merged faster into master without waiting for another moderator's approval as I put out hundreds of PRs to fix, update or remove manifests and it may take hours or days for it to be merged, not to mention that it also has to be tested to see if it shows up currently in winget list, etc.
I'm in the process of installing 1900+ applications on a virtual machine and fixing some of the versions, names, and publishers, so even if the account and this PR wasn't created, the problem with this manifest would've been noticed by me and fixed.
It was only several weeks ago that I realized how important it is to update values to match what's shown in Control Panel's ARP. Unfortunately, I don't use Chocolatey, so I don't know how their system works in terms of what they do to see if a particular application is installed, so it's not really my fault if application developers aren't showing a proper version or updating it, etc.

I'm sorry if you feel that way, and not notifying you about the PR I had created was a mistake on my end and I deeply apologize for that.

Thank you, that's all I needed to hear! 😃
As for the second account: I understand the reasons for creating it. This workaround just looks weird from the outside and it sounds to me like processes are not optimal yet. But I am sure you and the winget team will find a good solution here.
Thanks for your work!

@dpprdan we are working to improve all of the end to end scenarios. Moderation is a very recent necessity to help ensure a high quality catalog of packages in the community repository.  At present, there are only three community moderators fielding hundreds of submissions from the community, and trying to keep up with "Help-Wanted" asks. We have been balancing direct community support against fixing bugs, and building new features. These are exciting times.
We sincerely appreciate contributions!

Feedback
Feature Requests
Package Submissions
Manifest improvements
Bug Reports
Discussions
PRs on documentation
PRs on code

The last couple of weeks have been a bit chaotic with the number of new users and newly identified edge cases. Many of them were known, but many of them and several new ones have finally become reproducible.
Feedback is critical to our success. We believe in transparency and we rely on support from the community of customers, publishers, and ISVs to help us build the best product possible.


fixed yaml block so it renders

If a code block is underneath a bullet, and not properly indented, it does not render. (potentially a more strict check was introduced with blackfriday v1.5.3, that came with the Hugo 0.57.x upgrade)
Indenting blocks underneath bullets fixes this problem.

Before
After

More context: https://kubernetes.slack.com/archives/C1J0BPD2M/p1572286360131000

/assign

Great catch!  Renders much better now! :-)
/lgtm
/approve


Handle

I believe that this commit fixes #290, transparently handling

Coverage remained the same at ?% when pulling 2dbfcb144252cb2119e5a352dc664f4a2429d6e8 on squadette:script-async into e86090fbd4f2f97f349c25b8d993cc7c4f0f5070 on shakacode:master.

Possibly related links:

https://github.com/turbolinks/turbolinks/pull/274/files
https://github.com/turbolinks/turbolinks/issues/278
https://github.com/turbolinks/turbolinks/issues/281

@nateberkopec, any chance that you can help us review this one?
@alexeymohnatkin can you provide more examples of this and documentation?
Can you demonstrate the fix working and not working? Maybe modify the spec/dummy app and add the async tags?
How about https://github.com/shakacode/react-webpack-rails-tutorial? Can you demonstrate what would be the effect with and without this little change?

Reviewed 2 of 2 files at r1.
Review status: all files reviewed, 1 unresolved discussion (waiting on @squadette)

node_package/src/clientStartup.js, line 214 at r1 (raw file):

            'NOT USING TURBOLINKS: DOMContentLoaded event, calling reactOnRailsPageLoaded',
          );
          reactOnRailsPageLoaded();

@alexeymohnatkin is this related? an example? https://github.com/turbolinks/turbolinks/pull/274/files
Previous code always waited for the event.
Any more comments on why this fix works?

Comments from Reviewable

I don't think so.  This code was lifted straight from jQuery 3, I assume
they're doing the right thing.  The rest of the condition seems to handle
"not loading", that is "interactive".
On Thu, Jun 21, 2018 at 3:14 PM Nate Berkopec<EMAIL_ADDRESS>wrote:

@nateberkopec commented on this pull request.
In node_package/src/clientStartup.js
https://github.com/shakacode/react_on_rails/pull/1099#discussion_r197127404
:

@@ -196,6 +196,27 @@ export function clientStartup(context) {

debugTurbolinks('Adding DOMContentLoaded event to install event listeners.');

window.setTimeout(() => {
if (!turbolinksInstalled() || !turbolinksSupported()) {

 if (document.readyState === 'complete' ||

Will this break if the readyState is interactive?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/shakacode/react_on_rails/pull/1099#pullrequestreview-130808780,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAL7CeUhUz2MaEGbTtCHsXjwYG5B3dfks5t-5xFgaJpZM4Ug7gK
.

--
Alexey Makhotkin

@nateberkopec Do you feel OK with @squadette's suggestion?
@squadette, is there any chance that we could make an adjustment to the /spec/dummy app to verify this? If you tell me manually, I'll try it out. Like set some script to async?

Maybe changing these 2 lines
  <%= javascript_pack_tag('vendor-bundle', 'data-turbolinks-track': true) %>
  <%= javascript_pack_tag('app-bundle', 'data-turbolinks-track': true) %>

Also, how does the browser and webpack know that the second file app-bundle has to load after vendor-bundle.

Closed in #1107.

@justin808, I've missed your question about splitted bundles.  I don't know exactly how Webpack splitted bundles work, but if they depend on global names then splitted bundles will not work with async (but will work with defer).


Enhance/Refactor E2E tests for  RBD deployment functions

Describe the feature you'd like to have
Looking at the E2E, our deployment model for E2E RBD and CephFS is bit clumsy,  Repeated code and the sequential lay out of the code make very difficult to folllow and also make it hard to add more deployment logic in future. This is an enhancement request to make it more modular and clear.

Indeed! There are also several tests that modify the StorageClass with additional/different options. This should get simplified so the deletion and re-creation of the StorageClass is not so bulky anymore.
I suggest doing something like:
By(...) ... {
    withStorageClass(..., options map[string]string) ... {
        ...
    }
}

Where withStorageClass() then deletes the existing default StorageClass, and recreates it with the given options, runs the inner function and restores the original StorageClass.
Not sure what you are planning for other deployment options, but maybe you can use the same workflow as the e2e framework does.

@nixpanic looking at the E2E code, I see a good room for improvement which is really required anyway.  I will start one by one and would like to refactor it one by one.  The first PR I am planning to place it for RBD deployment from templates, that part itself looks clobbered. May be I will quickly drop a PR for it , so that we can have further discussions an continue improving one by one.

Sure, lots of improvements can be made. It helps to create a list of them in the issue description and be able to

[x] check them (#2180)
[ ] when they are done

Just make sure to not use Fixes: #2178 in the PR description or commit message, use Updates: #2178 instead.
In general, the e2e testing code should have the same quality standard (including linters that suggest simplification) as the rest of the project.

@nixpanic @Madhu-1 2180 is ready for review which addresses first 2 check boxes here in this issue. Please take a look :+1:


Add containers with other compilers and MPI providers

The only container recipe available right now uses gcc and openmpi. It would be good to also test container builds with:

[x] clang with mpich
[x] Intel with Intel MPI

The work for Intel is covered in #279 - therefore the rest of this issue is for clang with mpich

PR https://github.com/NOAA-EMC/spack-stack/pull/338 provides updates to previous PRs on the clang/gnu containers, and will close this issue as completed.


Drop torch 1.6 support

What does this PR do?
We have a 4 PyTorch version policy. With the release of 1.10, that means we can drop 1.6
[1.6, 1.7, 1.8, 1.9, 1.10] -> [1.7, 1.8, 1.9, 1.10]
Part of #10075
Does your PR introduce any breaking changes? If yes, please list them.
None
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[n/a] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you list all the breaking changes introduced by this pull request?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

@justusschock we could do that but would complicate CI a bit since we would need logic to handle 1.7 and 1.7.1 separately, additionally, we would need to generate both docker images.
I think 1.7.1 is fine looking at the release notes: https://github.com/pytorch/pytorch/releases/tag/v1.7.1
and download stats per version: https://pepy.tech/project/torch?versions=1.7.0&versions=1.7.1&versions=1.10.0&versions=1.6.0
And technically this should have been done before the 1.5 release, because now that supports 1.6-1.10 (5 versions)
so we should actually drop 1.7 too before the 1.6 release

Does this mean we can also deprecate the following lines and remove it in pl v1.7, right?

yes, in #10390

@carmocca I would rather keep it on master as we are going to merge bug fixes which will be conservatively cherry picked to release/1.5.x where we still support PT 1.6

@Borda This PR should have landed with 1.5 already to comply with the 4 torch versions window.
Still, this can be merged to master and the milestone changed if you want to land a specific fix for 1.5.0 with 1.6


[Bug]: TestExtractor_TraceOutputFileError testcases fail on Power

What happened?
Tests in uiconv module failing on ppc64le due to panic: runtime error: invalid memory address or nil pointer dereference
Power_Logs.txt
Steps to reproduce
git clone https://github.com/jaegertracing/jaeger.git
cd jaeger
git checkout v1.40.0
go install
go test -v ./...
Expected behavior
Any Information regarding the same will be helpful. Thanks
Relevant log output
--- FAIL: TestExtractor_TraceOutputFileError (0.00s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x3717c4]

goroutine 20 [running]:
testing.tRunner.func1.2({0x3c5680, 0x714070})
	/usr/local/go/src/testing/testing.go:1396 +0x1fc
testing.tRunner.func1()
	/usr/local/go/src/testing/testing.go:1399 +0x364
panic({0x3c5680, 0x714070})
	/usr/local/go/src/runtime/panic.go:884 +0x240
github.com/jaegertracing/jaeger/cmd/anonymizer/app/uiconv.TestExtractor_TraceOutputFileError(0x0?)
	/jaeger/cmd/anonymizer/app/uiconv/extractor_test.go:86 +0x344
testing.tRunner(0xc0001b91e0, 0x45f318)
	/usr/local/go/src/testing/testing.go:1446 +0x11c
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:1493 +0x36c
FAIL	github.com/jaegertracing/jaeger/cmd/anonymizer/app/uiconv	0.374s

Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response

ppc64le which run on IBM POWER8 are end of support going into 2024. I do not see this one being addressed.


zenoh: disable all tests

Many tests rely on networking and fail in the build sandbox and on Hydra. The list of tests individual tests has become too long.
After the last PR attempting to fix the problem more tests are now failing on Hydra (see https://hydra.nixos.org/build/282321806/nixlog/1/tail)

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@GrahamcOfBorg build zenoh


STFL Parser error near '' with musl-libc

Janko on IRC reported this.
When converting forms to STFL's internal widechar representation, we specify //TRANSLIT to ensure that as many users as possible see something meaningful in place of characters that their locale encoding can't represent. However, musl doesn't implement transliteration, causing Newsbeuter to crash with STFL Parser error near ''. (The call to stfl_ipool_towc returns empty string.)
Three solutions were proposed:

Remove //TRANSLIT altogether. The world moved on, new systems use UTF-8 (but we didn't find any statistics on that).
Use #ifdefs to figure out what libc we're dealing with, decide to include //TRANSLIT based on that. There's a slight problem there: musl doesn't define any macro. We'll have to do it autoconf-style: compile a testing binary, run it, look at the exit code and figure out things from there.
Do runtime check to see if //TRANSLIT results in stfl_ipool_towc returning empty string. If so, don't use //TRANSLIT anymore.

Since the problem depends on libc, i.e. something that doesn't change at runtime, the third option is out.
Out of the first two, the first is the best maintainability-wise, but will break things for people who run Newsbeuter on older systems with non-Unicode locales. Thus it looks like we'll have to go with option 2.
Implementation might proceed as follows:

[ ] write a small C++ program that will check if current libc and iconv provide //TRANSLIT support. The result should be returned via exit code.
[ ] edit config.sh to compile and run the test program. Depending on the result, some flag shall be put into config.mk (see how DEFINES is used in check_ssl_implementation()).
[ ] edit all the places where //TRANSLIT is used so that //TRANSLIT is excluded if there's no support from libraries.
[ ] try and test it on other platforms, including Linux with glibc and some BSD systems (just to make sure nothing was broken).

Why not at runtime, see if iconv_open fails when //TRANSLIT is used and then retry without it? Also, always omit //TRANSLIT when dest charset is UTF-8 since it's meaningless in that case (UTF-8 can represent everything).

The reason musl does not support //TRANSLIT, btw, is that its contrary to the requirements of the standard. POSIX specifies that an argument to iconv_open containing / is to be treated as a pathname to a charmap file. Implementations are not required to support charmap files (musl doesn't) but in this case the open needs to fail to indicate that they aren't supported.
glibc is also wrong to produce an error when //TRANSLIT is omitted. POSIX requires iconv to perform an implementation-defined conversion of characters that are not present in the dest charset. Replacing them with ?'s or transliterating them would be conforming options.

Why not at runtime

Because the behaviour doesn't depend on information that's only available in runtime. Implementing this as a runtime would be just bad taste, IMHO.
Thanks for the notes on how different libc implementations should and do behave—it's the first time I deal with this stuff. I'll edit the issue to say "check if //TRANSLIT is necessary" instead of "if current libc and iconv provide //TRANSLIT support".

My view is that runtime checks/fallbacks are not bad/dirty/wrong for behavior that can't be statically determined without execution. The only way to do build-time checks for them would be to hard-code assumptions about specific targets (bad/dirty/wrong) or execute a test at build time (precluding cross compiling). The runtime fallback is simple and inexpensive.

Janko also adds: "if musl or something else decides to implement TRANSLIT, you wouldn't have to recompile newsbeuter", which is a very good argument.

Yes, it is. And if that happens, if you did a test at build-time with a new version of libc and found support for //TRANSLIT, the resulting binary would run (because there's no missing symbol) but fail to work right with older libc. This is another reason why, in general, it's best to do runtime checks for things you can't test just by compile/link tests. Another big class to which that applies is checking for behavior that depends on the kernel; someone who compiled a program on a newer kernel might still end up running it on an older one.

Okay, you persuaded me. I'm going to rewrite the plan to implement runtime check instead.

No, I'd rather keep the original text as context for the discussion. Let's have new plan here instead.
Implementation might proceed as follows:

[ ] we seem to just append //TRANSLIT to things, so let's define a function const char* f(const char* std) that will do just that;
[ ] use f  everywhere where we mention //TRANSLIT at the moment. Check if anything broke;
[ ] make f check if our iconv supports //TRANSLIT and only append the string if it does;
[ ] make result of the check a static variable since it can't change during runtime for sure.


Signal can not create case automatically

Hi Everyone,
I added signal definition and checkbox create case, however when I use api to create a single instance, response is 200 ok, however only create a signal on Dispatch, did not create case, did everyone knows what happened?  from web logs, shows only create signal api, did not have trigger any api about case

http://localhost:8000/api/v1/default/signals/instances
{
"project": {
"name" : "default"
},
"raw" : {
"name" : "UAT1 down",
"security" : "high",
"owner"<EMAIL_ADDRESS>"description": "UAT1 down, please take a look"
}
}

@wssheldon i saw this pr https://github.com/Netflix/dispatch/pull/4982 where you did some changes to that
I suppose main_processing_loop should iterate through signals and process them, but I did not find any usage of that function. or maybe it's supposed to work other way
Anyway, I have the same problems. Cases are not created when signal instance is created

Hello, @andrewboxonko and @tiankai0114
You may need to enable the signal processor, which you can do via the CLI:
dispatch signals process
This command will continuously read signal instances (that have no associated case or filter action) from the database and send them through the signal_instance_create_flow function.
Without any output from either this process or the web server it will be hard to know why the case is not being created as it could be for many different reasons.

Hi. @wssheldon ,
I execute command dispatch signals process in docker, it can create case depends on signal, however, I need to manually enter docker and execute this command to start the work. Do you know how to keep this automatic running? Is it related to scheduler, thanks.

Glad to hear you got the case creation going. dispatch signals process will continue to run after you execute it, just like the web server itself. You should run this command in your production deployment to enable signal processing. You may want to run dispatch signals process on a separate container or instance.

Your JSON payload likely does not match a signal definition and is getting dropped. Make sure the external id/variant match a defined signal instance.

@wssheldon just checked, they are matching, but still the same result

Try adding a variant for good measure

@wssheldon Thanks, I was able to create a case after signal processing. But I have an additional question and It would be awesome if you could help since I did not find much in the docs, unfortunately. I am interested in using custom data for incident/case. I saw you have entities which can be used for that purpose, I was able to get created entities from my signal based on the JSON path. I would like to know if there is the possibility of assigning an entity to a case/incident. Ideally, I would like to create an incident with custom data directly. Maybe the is a way to do that or you can advise another way if that's possible. Thanks!

Entities are currently only associated with Signal Instances. I would be interested in understanding more about your use case, re:

I am interested in using custom data for incident/case

Could you provide a practical example of what you'd like to do, your specific domain, and what the inputs/outputs are?

@wssheldon We are currently in the initial stage and aiming to create basic incidents. We plan to develop our UI based on the dispatch API. Our use case scenario involves creating incidents based on real issues that could occur in the physical place/building/store. So for that reason, we would like to add information about where exactly the problem happened. That's why I am interested in having custom data. By custom data, I meant the possibility of creating incidents and having some custom attributes linked to them, such as an address, building/store name and so on. In the future, we also would like to use signals, but for now, we need to finalize the first stage

@wssheldon what do you think is it possible to achieve?

@andrewboxonko You should be able to leverage the Tag construct, to build up a corpus on tags that are relevant to you, and tag your incidents with those tags.

@wssheldon, yeah, the usage of tags looks fine. Thanks a lot. Also, I have an additional question regarding logs. Is it possible to store the changes that could be made to an incident in dispatch? For example, would you like to store and get the data (log) about changes made to an incident (edit of name, reporter and so on)? Would it be possible to achieve this using dispatch?

@wssheldon could we somehow use custom events for that purpose?

@wssheldon I'm also interested in custom events. Is there a way to add them somehow?


Bootsy not updating the input's value until there is a text change

I'm having two problems, although I think if I solve the first one, the second one becomes moot.

I'm trying to use Bootsy in an interface with a live preview. This works by binding a change event to the hidden value field, which Bootsy updates with content changes. The downside is that the value isn't updated until the field loses focus, so the interface isn't as reactive as it could be. Is there a callback that Bootsy utilizes for change events? I've tried attach a keypress event to the iframe to no avail. I believe this is due to a preventDefault preventing the action from bubbling up.

The only time the value seems to update is if you change the actual text in the field. If you just change the color or format the text (underline, bold, etc) it doesn't seem to update the field. However, once you change the text and lose focus, everything updates as you'd expect.

Do you have some suggestions on how to get around these issues? Thanks so much for a great package.

Hi, thanks for using Bootsy!
I'm afraid there's no good way to achieve that due to limitations on the JS library we use. See https://github.com/xing/wysihtml5/issues/52
I hope I'll be able to replace it with something better in the future.
For now my only suggestion for you would be to try adding a "Preview" button if possible.

@volmer Thanks for the response. I think a preview button is a good move, considering the limitations. However, what about the color/formatting changes that aren't being updated until a text change is made? Would you consider that expected behavior? Thanks again!

Yes, IIRC those changes are applied only when the form is submitted. You can do that with a button too.

@volmer As it stands, they are updated only when the text content is updated, which is odd behavior and hard to account for. Are you suggesting a button to pull not from the hidden value, but rather from within the iframe? It seems like an odd workaround.
Let me clarify the workflow.

Make changes to text in field.

Lose focus

Changes are made to the hidden value field.

Make changes to formatting.

Lose focus

Nothing happens to the hidden value field.

Make changes to formatting

Change text

Lost focus

Both text changes AND formatting changes are made to the hidden value field.

It would seem to me that both formatting and text changes should propagate to the hidden value field equally. I don't mind adding a button to trigger the update, but the different behavior whether it's a text change and formatting change is odd.
Thanks for your consideration.

I totally agree, it is very odd indeed. But that's unfortunately how whysihtml5 works 😢
there's no consistency in events nor in when the commands are applied to the actual textarea. The only moment I think you can use the output safely is after submit.


update docs for API.search_tweets

The method search_tweets is not present in the API class, even though it shows up in the docs.
I found that It is replaced with the method seach.
check the following screenshot:

I'm unable to reproduce this with Tweepy v4.0.0:
>>> import tweepy
>>> 'search_tweets' in dir(tweepy.API)
True
>>> 'search' in dir(tweepy.API)
False

Tweepy v4.0.0, which renamed API.search to API.search_tweets, was released yesterday.
Since this is the latest release, it is now the version that the stable version of the documentation refers to and is documenting.


Contact information

@r1cebank How may I contact you in private? The e-mail at your website is not working.

This is unrelated to the sega-nu repository. The website lists the email as<EMAIL_ADDRESS>however the personal github page of r1cebank lists an email as<EMAIL_ADDRESS>which seems to be correct as elica.io does not exist and r1ce.net is their website. Please consider exploring these avenues before filing issues unrelated to github projects.
If the information is regarding the sega-nu project, I suggest you elaborate a bit on why a private inquiry is necessary, such as documentation or non-public files related to the project.

@biggestsonicfan This is related to the repository, I will try to contact him over that e-mail, thank you.

Sorry about the late reply, that was an old domain that got expired.

Sorry about the late reply, that was an old domain that got expired. Will update my website later today.

E-mail sent.


cmd/compile: go build -buildmode=c-shared -linkshared produces .so that isn't loadable by dlopen

What version of Go are you using (go version)?
go 1.17
Does this issue reproduce with the latest release?
Yes, tried with 1.19 and 1.20
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/kluke/.cache/go-build"
GOENV="/home/kluke/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/kluke/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/kluke/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go-1.20"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.20/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.20.4"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/kluke/test/go.mod"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build788265043=/tmp/go-build -gno-record-gcc-switches"

What did you do?
We have a project that builds multiple plugins using c-go and -buildmode=c-share. We would like to use -linkshared to reduce the total disk usage of the plugins.
So I suppose I should start with the question, is this a reasonable thing to try and do?
$go install -buildmode=shared -linkshared std // To install golang shared libs
$go build -buildmode=c-shared -linkshared -o ./myplugin.so ./pluginsource
What did you expect to see?
Expected ./myplugin.so to be produced that is linked to stdlib.so and also be loadable by dlopen.
What did you see instead?
The plugin compiles successfully but is not loadable by dlopen.
Example
// main.go
package main

func main() {}

// cstuff/cstuff.go
package cstuff

import (
  "fmt"
  "C"
)

//export TestFunction
func TestFunction() {
  fmt.Println("Hello World")
}

// test.py
from ctypes import *
test = cdll.LoadLibrary("./test.so")
test.TestFunction()

Steps:
go install -buildmode=shared -linkshared std
go build -buildmode=c-shared -linkshared -o test.so .
# Library looks OK
❯ ldd ./test.so
	linux-vdso.so.1 (0x00007fff59d19000)
	libstd.so => /usr/lib/go-1.20/pkg/linux_amd64_dynlink/libstd.so (0x00007f6a9b394000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6a9b168000)
	libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f6a9b14c000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6a9b146000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f6a9b123000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f6a9e0dc000)

❯ python ./test.py
Traceback (most recent call last):
  File "./test.py", line 3, in <module>
    test = cdll.LoadLibrary("./test.so")
  File "/usr/lib/python3.8/ctypes/__init__.py", line 451, in LoadLibrary
    return self._dlltype(name)
  File "/usr/lib/python3.8/ctypes/__init__.py", line 373, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: /usr/lib/go-1.20/pkg/linux_amd64_dynlink/libstd.so: undefined symbol: main.main

CC @golang/compiler.

So I suppose I should start with the question, is this a reasonable thing to try and do?

As you may have thought of, currently the c-shared build mode and -linkshared don't work together. And there is no plan to support that. Thanks.

@cherrymui could you elaborate as to why building c-shared libs in -linkshared mode isn't supported?
Is it a matter of difficulty, or is there an architectural reason to not support that mode of operation?

As far as I can see, it's not inherently impossible.  But in general -buildmode=shared is not well supported (see #47788) and nobody has worked on making -buildmode=shared and -buildmode=c-shared work together.

Shouldn't the unsupported buildmode option combinations result in error or warning messages to avoid generating invalid .so files?


[auto-merge] bot-auto-merge-branch-24.02 to branch-24.04 [skip ci] [bot]

auto-merge triggered by github actions on bot-auto-merge-branch-24.02 to create a PR keeping branch-24.04 up-to-date. If this PR is unable to be merged due to conflicts, it will remain open until manually fix.

SUCCESS - auto-merge


USHIFT-375: fix capitalization in show-config output

/assign @fzdarsky
/type bug

LGTM

/hold
Needs a few further changes so loading of configs also work correctly.

/hold cancel

/lgtm

Looks like the unit tests for configuration are broken. I've opened USHIFT-383 and create a PR. Once that's fixed, this PR should merge automatically.

Looks like the unit tests for configuration are broken. I've opened USHIFT-383 and will create a PR. Once that's fixed, this PR should merge automatically.

I can't reproduce that failure locally.

/hold cancel

/retest


testing travis for 0843

General Recommendations & Version Control
Generally, keep both Pipfile and Pipfile.lock in version control.
Do not keep Pipfile.lock in version control if multiple versions of Python are being targeted.
https://pipenv.readthedocs.io/en/latest/basics/#general-recommendations-version-control


Write documentation on test resources

A bit more explanation what this mean for us that don't know exactly what test resources are

It's the reason I would like to write a page for it but I need to find the time.
Test resources is a resource of SUnit that can be linked to a test case.
It will be setup before running any test, and will be tear down after the tests are finished.
Compare to the #setUp and #tearDown method, it is setup/teardown once for all the tests of the test resource. This can be an equivalent to the @beforeClass and @afterClass of JUnit kind of.
It is useful when you have a resource taking some time to setup and that is used in read only and never updated.


项目不提示，打开父文件就提示，是什么原因

🚨 The issue tracker is not for questions 🚨
If you have a question, please ask it on https://stackoverflow.com/questions/tagged/visual-studio-code.

Please explain your issue in more detail


Response codes in chart are wrong

Hi all,
I believe that the status codes for requesting the twin documents and updating reported properties are switched.
In the case of "GET"ing the twin doc, the response code will be a 200 instead of the listed 204 since the returned body will contain the twin document. Link here.
In the updated reported properties, the response code will be a 204 since it is merely acknowledging an updated prop and there is no body. Link here

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bcf2a86a-1de0-2786-db87-58279ceffb22
Version Independent ID: 7e43624f-a87d-1c4d-94e6-e38c1d42686f
Content: Understand Azure IoT Hub MQTT support
Content Source: articles/iot-hub/iot-hub-mqtt-support.md
Service: iot-hub
GitHub Login: @robinsh
Microsoft Alias: robinsh

@danewalton Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

#reassign @JimacoMS3

Hi @danewalton -- thanks for your feedback!
I think I agree with on GETing the twin doc. It does seem like the status code should be 200 since the twin doc is returned.
I'm not sure about the Update reported properties call. It looks like the Etag is returned in the response body. I'm guessing that the status code should be 200 for this request too.
I'm not super knowledgeable here. @rezasherafat can you please confirm?
Thanks,
Jimaco

@rezasherafat Can you please confirm the above? Thanks!

Thanks again, @danewalton, the topic has been updated and published. I'll go ahead and close this issue. Please @-comment me if you think there is more needed here.

#please-close


Add create-job-from command only supported cronJob

What this PR does
Added kubectl fuzzy create-job-from command.
I want to create job from cronjob by fuzzy finder which is equivalent to following kubectl command.
kubectl create job my-job --from cronjob/my-cronjob

to
// generated job name from cronjob
kubectl fuzzy create-job-from cronjob
// create job by specified job name
kubectl fuzzy create-job-from cronjob my-specified-job-name

Demo

Special notes for review
1. command name
I'm not sure this command name is good.
I made this kubectl fuzzy create-job-from-cronjob first, but if create job command will be supported other than cronjob, it will have to add another command. So I passed resource as argument.
2. default preview mode
When I created a job from a cronjob, I thought it was better to see only the information that get cronjob had, rather than looking at the cronjob yaml.

@mpon
Thanks for your contribution! Sorry for the delay in replying.
I had a hard time designing the subcommands, but I think better to kubectl fuzzy should be able to use the same interface as kubectl interface.
For example, I think it would look something like this:
kubectl fuzzy create job foo --from=cronjob
The --from the option will be required in this case, which may compromise usability, but it will be the same interface as kubectl, so you won't have to learn a new command.
Also, about the preview option.
I want to be consistent in this plugin so the default is no preview, and show YAML /JSON in -P or —preview option.
I think the preview you proposed is useful, but we will have to discuss what to show on objects other than Kubernetes' CronJob to keep it consistent.

Thank you for your consideration.
I think it's good to follow the kubectl interface and also the consistency of options in this plugin.
I'll try to modify subcommands and preview options.


remove useEffect from RedirectToEtterlevelseDokumentasjonPage

... and remove jumpToHash, since it's only used once I've moved the code where it's needed.

bare merger inn


Can deletion of Nextflow 'work' directory be automated?

Arising from #228...
When we scale up to more datasets, we will need to delete the work folder and intermediate files if the job completes successfully with no errors.

Could that be an option in the job submission script?
Does it belong somewhere else, i.e. in nextflow pipeline? Is there a Nextflow option?
What if the job completes successfully with no errors but on inspection the results are invalid somehow? The work directory, and intermediate files, will be lost.

Only a specific user can tell if it is safe to delete intermediate files, and that can only be done after they've inspected them. After that, no solution will be quicker than rm -rf work.

Mike's view was accepted; we are not able to automate.


NIST 800-63C FAL

Is there any guidance that can be shared on how to configure the federations with AAD to achieve the different federation assertion levels levels 1-3?
https://pages.nist.gov/800-63-3/sp800-63c.html#fal

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7b1d9428-2dbb-c80b-c2cd-b4841d3d8bd3
Version Independent ID: 20af5f8d-479c-66ec-aacd-d3f9cb79c814
Content: Set up direct federation with an identity provider for B2B - Azure Active Directory
Content Source: articles/active-directory/b2b/direct-federation.md
Service: active-directory
Sub-service: b2b
GitHub Login: @msmimart
Microsoft Alias: mimart

@Jackson-Miller Thanks for your feedback! We will investigate and update as appropriate.

Hey Jackson, I'm following up on this, we're currently looking into this issue and will let you know once we have an update. Thanks!

@Jackson-Miller
Currently there is no way to go beyond FAL1 for any federated setup.
Azure AD does not access incoming encrypted assertions from the federation provider.
That includes regular federation and direct federation.
I apologize for the inconvenience, please let me know if there are anymore questions within the scope of this thread, otherwise I will be closing it out by end of day today.

I will be closing this out now, please let us know if you have anymore questions by reopening this,

Frank,
Has the status changed? I found the following that says AAD accepts encrypted tokens, but does not check signatures. Are these up-to-date?
Token encryption is an Azure Active Directory (Azure AD) premium feature.
https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/howto-saml-token-encryption
Signed requests are accepted, but the signature isn't verified.
https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/migrate-adfs-apps-to-azure
Thanks in advance,
Bill


Add support for older version of typescript

Add supports for older versions of typescript.
#217 added param type inference from path. This feature is only supported by Typescript >= 4.1.
This PR is adding support for both the new versions and older versions of typescript.
It also add the missing types and tests for preact.
Also resolves #218

👍

Hi @graphman65, sorry I was having a 3 weeks off, just got back. The proposed change looks great, I was first confused with the approach of having two almost identical type sets for different TS versions and was hoping that there is some shortcut like preprocessor conditions, but seems like the only proper way is indeed through typesVersions. I have some plans on rewriting the library in TS in the next major release, since supporting types separately is becoming a chore. I wonder how would we support two versions in that case.

@molefrog
Should we publish a new alpha version with the changes?

Yes, sorry, the alpha.2 is live now.

So, has anyone tested this released on a real project yet?

Hey @molefrog,
I personally tested the react and preact versions on my projects.
I also tried using older versions of typescript and it switched to the correct types successfully.
Still would be good if someone else could test the new release as I'm probably not using all the features.


Fixing version v2-d

Here the fixing to gather all the updates related the plotting and the data access. Targeting the release of a version aligned with OceanClimate v2

@mdrudi I upload some commits to this branch:

mtplot is enable
update daccess to latest version from OceanClimate
update mtplot to latest version from OceanClimate

To consider the possibility to document here the Inderface Definition Language which is used to define the interface of a specific method implementation. An additional aspect to describbe is the format of the output log, that in the future should become W3C-PROV complinat. This is something to verify when the code is stable after the inprogress review for the methods Ocean Patterns/Regimes Indicators and Storm Severity Index

An additional aspect to describbe is the format of the output log

About this I have some updates. With the last updates I improve also this code section.
Now there is a python class that handle all the json sections and with a next update in this class will appears also the output format of the json following this syntax:
https://github.com/CMCC-Foundation/medpetra/blob/0271b32af5018db4b8faa51ae3d038ef0a086067/aux/archpack/src/file.py#L43
On the other hand, we can think to prepare a specific documentation to document the json format and also a simple documentation to explain how to use the relative module

Question: what attributes are mandatory in the output log ? Requirements of the web app ?

To add into the repository an example of output log (json file) and in case also the python module which is able to manage the creation of this output file

Question: what attributes are mandatory in the output log ? Requirements of the web app ?

Required info are the mandatory as specificed here https://github.com/CMCC-Foundation/bluecloud-mockup_method/tree/fix_v2/log

To consider the revision of this package to make it not strictly related to BlueCloud

Question: what attributes are mandatory in the output log ? Requirements of the web app ?

Required info are the mandatory as specificed here https://github.com/CMCC-Foundation/bluecloud-mockup_method/tree/fix_v2/log

[ ] to explain in few words why we assume to be mandatory the two info related the error log and the end time


physicalplan: make OrderedAggregate work in the presence of dynamic columns

This required adding some more fields to the OrderedAggregate to keep track of which columns we have/have not seen.

Looks like CI found a flake, will investigate and fix.

The flake was due to expecting ordering due to map iteration. This is now fixed.


Add Window button in Keyboard Manager

Description of the new feature / enhancement
My Window button on my Laptop's keyboard is broken but  Keyboard Manager does not have Win button to remap
Scenario when this would be used?
Remap to another button
Supporting information
No response

@thanhudanchi As the screenshot below, there is an option for Win key. Please double-check your options. Or you can use the function Type to type and press the Win button.


Questions

###Question 1
Is the functionName completely reliant on targetFuncName in the locator?
Question2
What is the addr is traceTree.info is it always the to address?
Question3
How do we track functioncalls within the contract itself i.e opcode = JUMP.
Question4 How far does can we track externalCalls?

Question 5:
metaTraceTree vs TraceTree?

Question 6: What does splitTraceTree function do?
It is like searching a contract in Phalcon, we split the trace tree to parts that we like to look at (for specific information);

Question 7: What is track function is used for?
This function implements a dynamic flow and taint analysis tool


Add Web developer specific apps

Needed

postgres
redis
Heroku
AWS CLI
Github CLI
imagemagick
docker
yarn
nvm

Who Benefits?
Web chapter

Knowing that all our apps use Docker, does it make sense to add postgres and redis for example?

@hoangmirs I think we don't need Postgres as we use Docker for it.
How about adding
1/ rvm
2/ elixir
3/ go?
4/ Phrase app cli
5/ AWS CLI

I heard that Omise didn't use Docker, I'm not sure for now
But I also prefer to remove it

Some clients indeed do not use Docker so I recommend to keep Postgres via brew services. Redis could be removed.


chore: rename automatically generated equational theorems

cc @nomeata

This renaming implicitly says “these theorems are no longer internals, you can use them”, right?
In that case I think we should also have a nicer way of making sure they exist reliability. If we can't afford to generate them always because it's too expensive for definitions nobody wants to prove anything about, can we add an attribute maybe?
(Doesn't have to be part of this PR of course.)


Don't log database password and other credentials from sequencer

I am interested in working on this one. I made a draft PR with how I am planning to hide the credentials. I would like to get suggestion from the team. https://github.com/worldcoin/signup-sequencer/pull/498. thank you!


Introduce automated repositories

Automated repositories are built from a Dockerfile stored inside of a
remote repository (e.g. a Git repo).
Signed-off-by: Flavio Castelli<EMAIL_ADDRESS>

I'm a bit in a rush now. It's a public holiday in Italy and I gotta go to have fun up in the mountains with the rest of my family. I'll attach the screenshots this evening (unless you are faster with the review).

Ok, so before looking into the code too much I have some questions:

I thought that we wouldn't have the concept of "automated build repositories" :D What I thought is that we would provide a link in the repositories#show page, in which we would allow the user to provide the info about how to build that repo/tag from a Dockerfile. That being said, I'm not against the "automated build repositories", but I'd also like to see this other method of setting this up.
From the previous point, there's no link to the repositories#edit page. Or at least I couldn't find it :) If you want to keep the idea that only repos that have been created with the "automated build repositories" form can be edited, then you should filter this also in the controller. Otherwise, you could just provide a link to the edit page for any repo, and then my first point would just disappear :)
How do you handle the Catalog job ? Note that the catalog job removes dangling repos (repos with no tags in the registry, and this will happen when you create an "automated build repository" always). You could update the code so the catalog job takes into account repos with the "source_url" column set.

I thought that we wouldn't have the concept of "automated build repositories" :D What I thought is that we would provide a link in the repositories#show page, in which we would allow the user to provide the info about how to build that repo/tag from a Dockerfile. That being said, I'm not against the "automated build repositories", but I'd also like to see this other method of setting this up too.
From the previous point, there's no link to the repositories#edit page. Or at least I couldn't find it :) If you want to keep the idea that only repos that have been created with the "automated build repositories" form can be edited, then you should filter this also in the controller. Otherwise, you could just provide a link to the edit page for any repo, and then my first point would just disappear :)

I forgot to add some UI files to the PR. Everything is solved with them as we discussed on IRC.

How do you handle the Catalog job ? Note that the catalog job removes dangling repos (repos with no tags in the registry, and this will happen when you create an "automated build repository" always). You could update the code so the catalog job takes into account repos with the "source_url" column set.

I didn't, thanks for pointing that out. I updated the PR accordingly.

Besides that comment, LGTM

Fixed, merging.


URL in description and README broken

The URL in the repository description and README are pointing to teradyne-dev-workshops's copy of the game instead of yours.
Please fix both, so they point to your copy of the game at https://teradyne-dev-workshops.github.io/github-games-jgtres.

Solved already

fixed already


Integration not loading after recent HA and Integration update

Describe the bug
Integration no longer loading devices after HA update 2024.3.3
To Reproduce
Steps to reproduce the behavior: udated HA 2024.3.3 with Cloud connection to M30 devices
Expected behavior
The integration is no longer loading after the recent HA update. I'm not sure if it is the update or something else, but restarts of HA and the integration do not resolve it.
Screenshots/Logs
2 error logs pasted below:
#1
This error originated from a custom integration.
Logger: custom_components.lennoxs30
Source: custom_components/lennoxs30/init.py:383
integration: Lennox S30/E30 (documentation, issues)
First occurred: 11:23:26 AM (2 occurrences)
Last logged: 11:29:56 AM
async_unload_entry call to hass.config_entries.async_unload_platforms returned False

#1
This error originated from a custom integration.
Logger: homeassistant
Source: custom_components/lennoxs30/device.py:281
integration: Lennox S30/E30 (documentation, issues)
First occurred: March 31, 2024 at 2:23:18 PM (1 occurrences)
Last logged: March 31, 2024 at 2:23:18 PM
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/lennoxs30/init.py", line 687, in initialize_retry_task
await self.s30_initialize()
File "/config/custom_components/lennoxs30/init.py", line 548, in s30_initialize
await self.create_devices()
File "/config/custom_components/lennoxs30/init.py", line 673, in create_devices
z.register_device()
File "/config/custom_components/lennoxs30/device.py", line 281, in register_device
name=self.system.name + "" + self._zone.name,
~~~~~~~~^
TypeError: can only concatenate str (not "NoneType") to str

Version

Home Assistant: 2024.3.3
This Integration: 2024.3.0

**Integration Configuration **

Cloud or Local Connection: Cloud
Inverter or Sensor Diagnostics Enabled: no

Additional context
Add any other context about the problem here.

I found another log, seems to indicate connection issues:
This error originated from a custom integration.
Logger: custom_components.lennoxs30
Source: custom_components/lennoxs30/init.py:953
integration: Lennox S30/E30 (documentation, issues)
First occurred: March 31, 2024 at 11:20:08 PM (4 occurrences)
Last logged: 10:54:06 AM
messagePump communication error host [None] Code [11] Reference [300] [messagePump failed - Communication TimeoutError exceeded configured timeout [https://icretrieveapi.myicomfort.com/v1/messages/retrieve]]
messagePump communication error host [None] Code [11] Reference [400] [messagePump Client Connector Error - failed due host not reachable url [https://icretrieveapi.myicomfort.com/v1/messages/retrieve]Message ConnectionKey(host='icretrieveapi.myicomfort.com', port=443, is_ssl=True, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=None)Message SSL handshake is taking longer than 60.0 seconds: aborting the connection]

I'd like to see the sequence of errors.  Stop home assistant, restart it, wait 5 minutes, grab the home-assistant.log and attach it to this issue.

I tested the cloud connection to my S30 using ha 2023.3.0 and 2023.3.0 of this integration and it works for me.
we should enable debug logging on your system so we have all the details, info on how to configure is here:
https://github.com/PeteRager/lennoxs30?tab=readme-ov-file#reporting-bugs
Also check the internet connection on the thermostats.  Are you able to connect using their mobile app?
How are you running HA?

Thanks for confirming. I'll gather some additional information.  I'm running HA x86 on metal. The M30 devices are fine in the native app with cloud connection. My integration stopped working sometime while updating my various HACS components (including this one) and HA upgrade from 2024.3.1. to 3.3.  I'm not sure exactly of the sequencing or when it failed. Nothing else purposely changed other than the system and component updates.

Well, after several reboots and setting up logging settings, the integration began to work eventually this final time. Apologies for opening the issue, but my prior attempts over the last couple days had failed. I'll include the final log here for your review if you'd like to retro anything.
home-assistant.log


Debugging inside a container: debugger does not hit breakpoints anymore

Type: Bug

Behaviour
Expected vs. Actual
Context: Debugging code inside a container
Expected: breakpoint are hit when code is executed.
Actual: breakpoints are not hit, and when the debug session the Debug Console shows:
pydev debugger: unable to find translation for: "c:\dev\qxc\model-sample\qxc\app\run.py" in ["C:\dev\qxc\model-sample/qxc/", "C:\dev\qxc\model-sample/qxc"] (please revise your path mappings).

Worth mentioning: rolling back to version v2022.18.2 of the extension fixes the problem without any change in the path mappings. Those mappings were defined weeks ago, and just stopped working with the latest release.
Steps to reproduce:

Configure a project to run and debug inside a container
Set some breakpoints
Run the project
Observe the warning describe above in the Debug Console, and verify that breakpoints are not hit

What seems strange from the message above is that the path inside the container c:\dev\qxc\model-sample\qxc\app\run.py looks like a Windows path, but the container I'm running is from a Linux-based image. I'm on a Windows box with Docker Desktop on WSL2.

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.7.4
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Global
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings

languageServer: "Pylance"

Extension version: 2022.18.2
VS Code version: Code 1.74.0 (5235c6bb189b60b01b1f49062f4ffa42384f8c91, 2022-12-05T16:38:16.075Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)

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

Load (avg)
undefined

Memory (System)
31.86GB (11.04GB free)

Process Argv
--folder-uri file:///c%3A/dev/qxc/model-sample --crash-reporter-id d3ea3600-8e75-4ca7-a1d1-6a498426b4ab

Screen Reader
no

VM
0%

@paulacamargo25 Can you verify that this is set correctly? This used to be set in the config resolver.

Seems to be a recurring issue with almost every new version of the extension. It was working perfectly fine last night, woke up to realize my debug points are not being hit. My current version is v2022.20.2. Rolling back to v2022.20.1 seems to resolve the issue.
It happened a week earlier as well, around VSCode 1.74.0 which force updated this extension version. Had to roll back VSCode version to roll back extension version.

I'm having a similar issue. I run a aws python lambda image on docker, the debug is being attached but the code doesn't stop in the breakpoints :/

This is also an issue when using the Python debugger not in a container, but with Remote SSH. If I use a launch configuration like the following in Run and Debug using SSH to my backend, setting any breakpoint causes that run to spin indefinitely. It will run to completion if no breakpoints are set, however.
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "justMyCode": true,
        }
    ]
}

This fails consistently (100% of the time) in v2022.20.2 and the current Pre-Release version (v2023.3.10451008). Rolling back to v2022.20.1 works consistently.
I also tried setting clientOS to unix or windows, but it doesn't unbreak debugging with breakpoints.

+1 for https://github.com/microsoft/vscode-python/issues/20407#issuecomment-1430101764
MacOS 13.2 using "Remote - SSH" v0.96.0 (to an Ubuntu 22LTS remote) and VS Code 1.75.1. This started consistently breaking with the v2022.20.2 and also consistently breaks with v2023.2.0. This setup has previously been stable / usable for a while with previous versions.
Setting breakpoints and then attempting to debug a python file with the same launch.json as above fails on breakpoints. I get "The editor could not be opened because the file was not found" where the file / breakpoint should be displayed in the editor window.
Using a remote user 'user' with a home directory of '/home/user', a project directory of '/home/user/project' and attempting to debug 'thing.py' with 'foo/bar.py' as the file with the breakpoint, the top-left of the editor window (above the error) shows a path of 'user/project/foo/bar.py' . This does not work as an absolute path or as a path relative to the file being debugged. '/home/user/project/foo/bar.py' or 'foo/bar.py' would be "correct" in this example.
Have not yet managed to revert the python extension back to to v2022.20.1 - mostly due to trying to remove the extraneous jupyter-related extensions that get installed on the remote with v2023.2.0. A guide to reverting back correctly from a fresh install with this setup would be helpful.

@jonathonfletcher Does "clientOS" make any difference for you?

@jonathonfletcher Does "clientOS" make any difference for you?

Hi, thanks for the suggestion. I just tried with
"clientOS": "Unix",

in the launch.json. I get a yellow squiggly underneath and the setting seems to be ignored.
Unrelated, but potentially interesting, if I add
"env": { "PYDEVD_DEBUG": "True" },

in the launch.json, I see a possible different between the paths of files that do open vs ones that do not in the pydevd output.
I get some references to (e.g.): /home/user/project/thing.py which is the main that I am debugging. This is the only editor tab open when I start with F5 for debugging. The python package foo/bar.py appears in the pydevd output as //home/user/project/foo/bar.py - double / at the beginning. This is a valid unix path but is it possible that this is tripping up some url-opener (i.e. file:////home/user/project/foo/bar.py instead of file:///home/user/project/foo/bar.py) ?
Again, I'm just noticing this / vs // difference. May be not relevant.

Earlier, you've mentioned that the path that the editor shows is "user/project/foo/bar.py" - without the leading slash. That would seem to imply that it's getting a relative path from somewhere and failing to properly translate that to an absolute path. If you print(__file__) inside bar.py, what does that show under the debugger?

Thanks for the message. The "user/project/foo/bar.py" shown in the editor (top-left) is shown with the "The editor could not be opened because the file was not found" error.
pydevd's debug shows the file as "/home/user/project/foo/bar.py" and print(__file__) will show "/home/user/project/foo/bar.py".
I am beginning to suspect that this is actually a "Remote - SSH" extension bug and not a "Python" extension bug because the "The editor could not be opened because the file was not found" error's "Create File" button has the wrong url for the file: vscode-remote://ssh-remote+server/user/project/foo/bar.py should be vscode-remote://ssh-remote+server/home/user/project/foo/bar.py
If I force a workaround on the remote host with sudo ln -s /home/user / in order to make the vscde-remote url "valid" on the remote (ie /user/project/foo/bar.py -> /home/user/project/foo/bar.py) then the editor window comes up with the correct file and the python debugger stops and renders at the breakpoint.

I had the same problem with breakpoints not working and this was fixed by rolling back to v2022.20.1.
From a windows 11 system I am trying to debug python code running in a linux container.  My application runs correctly in the container (except one bug that appears only under linux).  Break on raised exception works and drops me into the current code.  However, line breakpoints are ignored.  Toggling a breakpoint shows the "not really ready" image.
At session start, the debug console gives these errors for every file with a breakpoint:
3.68s - pydev debugger: unable to find translation for: "c:\Users\tunge\Documents\intg\intg-core\modules\CE_TO_CEN.py" in ["C:\Users\tunge\Documents\intg\intg-core/", "C:\Users\tunge\Documents\intg\intg-core"] (please revise your path mappings).

0.01s - pydev debugger: unable to find translation for: "c:\Users\tunge\Documents\intg\intg-core\modules\mq_receive.py" in ["C:\Users\tunge\Documents\intg\intg-core/", "C:\Users\tunge\Documents\intg\intg-core"] (please revise your path mappings).

It looks like the list of target directories is incorrect.
pathMappings in launch.json appear to be correct and is what is shown in the documentation:
      {
            "name": "Docker: modules/mq-receive CE_TO_CEN docker",
            "type": "docker",
            "request": "launch",
            "preLaunchTask": "ce-to-cen-docker-run: debug",
            "python": {
                "pathMappings": [
                    {
                        "localRoot": "${workspaceFolder}",
                        "remoteRoot": "/app"
                    }
                ],
                "projectType": "general"
            }
        },

Environment where breakpoints don't work is:

Windows 11 Pro (recently updated)
VS Code 1.74.3 (because of bug #3823 in 1.75.1)
Python extension v2022.20.2
Docker extension v1.23.3
Container is based on python:3.10

In python extension version v2022.20.2 I tried setting "clientOS": "Unix", but this resulted in the debugger not starting.

this resulted in the debugger not starting

This is concerning, since it would likely do the same once VSCode starts supplying this setting automatically. Can you please share the error message that it produces, if any?

Running with extension v2022.20.1
"clientOS": "Unix",

results in the error "clientOS" must be one of "windows" or "unix".   Different than before so that casts doubt on previous results.
When I change the value to "unix" the debugger runs, but does not stop at breakpoints.
Remove the setting and the breakpoint works again.
With extension version v2022.20.2
With the setting, the debugger runs but does not stop at break points.
Without the setting, the debugger runs but does not stop at break points.
(Back to v2022.20.1 without the setting and breakpoints work again.  That's my cozy place for development.)

My apologies, I should have caught this earlier - since your VSCode is running on Windows, it should correspond to "clientOS": "windows" for proper path mapping.

Ah, thanks.  With the correct value, extension version v2002.20.2 will stop at breakpoints.

Thank you for confirming!

We need to set clientOS flag in all scenarios (launch and attach) in the debugOptions.

Hey, I'm running into this issue when upgrading to v2023.4.1 or the latest v2023.6.0
I'm getting the following error when trying to attach to a remote process using the following configurations
Error:
pydev debugger: unable to find translation for: "d:\vscode-init\debuger-test\main.py" in ["D:\vscode-init\debuger-test/", "D:\vscode-init\debuger-test"] (please revise your path mappings).
Launch.json
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Debug",
            "type": "python",
            "request": "attach",
            "clientOS": "windows",
            "connect": {
                "host": "localhost",
                "port": 5678
            },
            "pathMappings": [
                {
                    "localRoot": "${workspaceRoot}",
                    "remoteRoot": "/app"
                }
            ]
        }
    ]
}

Environment Information:

Windows 10 Enterprise
vscode-python v2023.4.1

NOTE: It works with/without using "clientOS": "windows" when using v2023.4.0

@rjra2611 I created https://github.com/microsoft/debugpy/issues/1257 on debugpy, please follow up there on this issue.


Use metadata batch callouts in client_auth_filter.

As discussed in #14615.

****************************************************************

libgrpc.so

     VM SIZE                                                             FILE SIZE
 ++++++++++++++ GROWING                                               ++++++++++++++

 -------------- SHRINKING                                             --------------
  -0.0%    -107 [None]                                                   -539  -0.0%
  -3.8%    -125 src/core/lib/security/transport/client_auth_filter.cc    -125  -3.8%
     -27.5%    -237 auth_start_transport_stream_op_batch                     -237 -27.5%
     -17.9%     -17 destroy_call_elem                                         -17 -17.9%
      -8.7%      -6 [Unmapped]                                                 -6  -8.7%

  -0.0%    -232 TOTAL                                                    -664  -0.0%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE                                                             FILE SIZE
 ++++++++++++++ GROWING                                               ++++++++++++++

 -------------- SHRINKING                                             --------------
  -0.0%    -107 [None]                                                   -531  -0.0%
  -3.8%    -125 src/core/lib/security/transport/client_auth_filter.cc    -125  -3.8%
     -27.5%    -237 auth_start_transport_stream_op_batch                     -237 -27.5%
     -17.9%     -17 destroy_call_elem                                         -17 -17.9%
      -8.7%      -6 [Unmapped]                                                 -6  -8.7%

  -0.0%    -232 TOTAL                                                    -656  -0.0%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE                                                             FILE SIZE
 ++++++++++++++ GROWING                                               ++++++++++++++

 -------------- SHRINKING                                             --------------
  -0.0%    -107 [None]                                                   -531  -0.0%
  -3.8%    -125 src/core/lib/security/transport/client_auth_filter.cc    -125  -3.8%
     -27.5%    -237 auth_start_transport_stream_op_batch                     -237 -27.5%
     -17.9%     -17 destroy_call_elem                                         -17 -17.9%
      -8.7%      -6 [Unmapped]                                                 -6  -8.7%

  -0.0%    -232 TOTAL                                                    -656  -0.0%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

[microbenchmarks] No significant performance differences


Improve appearance of forbidden pages

From @ironfroggy report.  Forbidden pages are a part of the platform to be expected to hit when some operations happen, like trying to access a resource that has been made private and to which you do not have access. Unfortunately, no information is given to the user about why they are seeing this error. It is likely the user had a typo the name of a resource, or forgot to log into the website first, or has more than one account and is using the wrong one, or that the owner intended to give access to the resource but neglected to do so.
Recommendations:

Show the normal site template for the 403 pages
Include helpful message about the name of the resource being accessed
Include the current account which does not have access and link to login
Include a brief explanation about why access is denied
Include a prompt to ask the Resource owner to share access to the resource

@dtarb @horsburgh I have created a forbidden 403 page to improve its appearance. Since we don't have page resource context passed in to a forbidden page, this page template does not know anything about the forbidden resource such as its title, its owners, etc., and I don't think it is a good idea to expose resource detailed info to a user who does not have permission to view the resource. So here is what I have right now. If a user is not signed in, the user will see a page like the following:

If a user has logged in but does not have proper access permission to this resource, the user will see a page like the following:

Please correct the wordings as needed and let me know whether this is sufficient for appearance improvement without requiring too much work.

@dtarb - I'm having vague recollections that you wrote down at one point what you wanted to display is a user is not authorized to view a resource. Am I remembering wrong?

@horsburgh you are remembering right.  I suggested that as a matter of policy the resource title, owners and GUID are public information.  The rest of the information on the resource is subject to access control rules.  This means that anyone hitting a link that has a GUID embedded in it get a small landing page that gives this information.  The owner name (or owners if there are multiple owners) is to be provided with a link to their HydroShare profile so that a registered HydroShare user can send them an email to request access.  Only registered users get to see the mailto link for other users.  I do not know if/where this is written, but the above is the gist of it.
I suggest a page similar to the following if the user is not logged in (most common case if someone has been sent a GUID to a private resource shared with them).  If they are logged in shorten the words to: "The resource you have attempted to access is private.  You can request access from the owner."

@dtarb Can you verify this on beta and close it if it works? If you want that nice-to-have redirect to resource landing page after signing in, you can create a new issue.

Thanks.  Closing.


xSQLServerSetup: Added support for vNext CTP 1.4

Pull Request (PR) description

Changes to xSQLServerSetup

Added support for vNext CTP 1.4 (issue #472).
Some minor style changes.

This Pull Request (PR) fixes the following issues:
Fixes #472
Task list:

[x] Change details added to Unreleased section of CHANGELOG.md?
[ ] Added/updated documentation, comment-based help and descriptions in .schema.mof files where appropriate?
[ ] Examples appropriately updated?
[x] New/changed code adheres to Style Guidelines?
[x] Unit and (optional) Integration tests created/updated where possible?

This change is

Codecov Report

Merging #474 into dev will increase coverage by <1%.
The diff coverage is 83%.

@@         Coverage Diff          @@
##            dev   #474    +/-   ##
====================================
+ Coverage    73%    73%   +<1%
====================================
  Files        32     32
  Lines      3426   3428     +2
====================================
+ Hits       2519   2521     +2
  Misses      907    907

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 c60d876...881b7e8. Read the comment docs.

Reviewed 1 of 3 files at r1, 2 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


_checkStatus does not check all statuses

Currently _checkStatus will just check the first status it finds, but a VC could have more than one status. Instead of calling getCredentialStatus, it should iterate through the statuses and check if they are applicable to StatusList2021 and, if so, check them.

@dlongley need to know how to handle this test case now:
https://github.com/digitalbazaar/vc-status-list/blob/d057c0304772ddad6553c646b62b490e8f59300e/tests/30-main.spec.js#L156-L183
If a status has a type that is not in the StatusList2021 spec, should we just ignore it?

My understanding is that it should still fail. There's a statusTypeMatches helper that would be called from a custom check status function (if more than one status type is supported in a system) that would ensure the type matches before passing to this library's checkStatus. Therefore, if that doesn't happen -- and the VC is passed to this library's checkStatus function, it should fail, i.e., this library's checkStatus should make sure the status type is acceptable.

To be more clear on what should happen here -- there should be at least one credentialStatus that matches. If not -- as here in this test, it should fail.

To be more clear on what should happen here -- there should be at least one credentialStatus that matches. If not -- as here in this test, it should fail.

So if there is one matching and one non-matching ignore the non-matching, but check the matching status?

So if there is one matching and one non-matching ignore the non-matching, but check the matching status?

Yeah, I think that's the only way we could make it work.

closing as this has been addressed


Add option to include/exclude binary files

This is how I implemented #48, not quite as you suggested, but with a Boolean parameter that indicates whether the tool includes or excludes binary files by default.
Please take a look and I will rework as required.
Once the code is done to your satisfaction, I'll update the docs.

Thanks. But I'm not sure I understand your comment about sift.
Wouldn't the configuration for sift be similar to that for grep?
'opt_str_binary_switch': '--binary-skip'
'opt_bool_binary_excluded_by_default': '0'
Perhaps I misunderstand something
MV

Also, do you want a separate PR for adding the new option to the docs, or just update this one?

My mistake, you're correct. This works nicely. A separate PR for the docs would be good.


Says I have the latest version, but I don't

me@host:~$ ./OldImageMagick-git.7a48608-x86_64.AppImage --appimage-updateinformation
gh-releases-zsync|probonopd|ImageMagick|continuous|ImageMagick*-x86_64.AppImage.zsync

AppImageUpdate version 1-alpha (commit 48d9713), build 119 built on 2017-11-07 02:37:53 UTC says that I already have the latest version, except that it isn't:

(Zipped for GitHub Issues)
OldImageMagick-git.7a48608-x86_64.AppImage.zip

In this case, the files are equal content wise, but the filenames on the server and locally differ.
As discussed elsewhere, AppImageUpdate should issue a warning whenever the filename on the server changed.

AppImageUpdate behavior has since changed (in positive ways), hence closing here. Thanks!