sharedown: unbreak build

Description of changes
fixes the following error message:
$ node-gyp rebuild
info This package requires node-gyp, which is not currently installed. Yarn will attempt to automatically install it. If this fails, you can run "yarn global add node-gyp" to manually install it.
[1/4] Resolving packages...
error Failed to auto-install node-gyp. Please run "yarn global add node-gyp" manually. Error: "Couldn't find any versions for \"node-gyp\" that matches \"latest\" in our cache (possible versions are \"\"). This is usually caused by a missing entry in the lockfile, running Yarn without the --offline flag may help fix this issue."
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

https://hydra.nixos.org/build/239684452
ZHF #265948
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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.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.

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

1 package built:

sharedown

Runs fine on my machine, I love PRs with a net LoC removal


Vim's map function sometimes does not report error E1012 (vim9script)

Steps to reproduce
Using the code below, call Using_Fctn_Arg()
vim9script
def g:Using_Fctn_Arg()
var lNumber: list
lNumber = map(range(1, 4), 'NbrToStr(v:val)')
enddef
def NbrToStr(n: number): string
return printf('%3s', n)
enddef
This generates the following runtime error:
Error detected while processing function Using_Fctn_Arg:
line    2:
E1012: Type mismatch; expected list but got list
The range function is documented to return list and so map() should also return list but apparently returns list.
If the range() call is replaced by a variable of type list:
def g:Using_Var_Arg()
var lNumber: list
var mapIn = range(1, 4)
lNumber = map(mapIn, 'NbrToStr(v:val)')

enddef
Vim correctly generates the following error:
Error detected while processing function Using_Var_Arg:
line    4:
E1012: Type mismatch; expected number but got string in map()
Expected behaviour
Invoking Using_Fctn_Arg() should fail with error E1012 in the same way as Using_Var_Arg().
If mapnew() is used instead, an error is not generated, as one would expect.
Version of Vim
9.1.901
Environment
Windows 10
Logs and stack traces
No response

My apologies.  Apparently the markdown feature removed constructs such as <string> and <number>.  I suggest closing this report and I will resubmit with the missing information.


feature request: provide input files as input parameters

Hello,
I would like to request a feature, where it will be possible to provide manifests and kustomization file as input parameters. This would allow to build kustomization for use-cases where the manifests are coming from other providers' data sources.
For kustomization_build:
2 input parameters, one for original manifests and one for kustomization definition.
New parameters could be mutually exclusive with the existing path input parameter.
For kustomization_overlay:
1 input parameter for original manifests.
New parameter could be mutually exclusive with the existing resources input parameter.
I am currently using local_file as a workaround, but it is causing noise in TF plans.

This is not in scope for the provider. More information on the topic can be found here: https://github.com/kbst/terraform-provider-kustomization/issues/114


DO_NOT_MERGE Np 9554/remove old signin signup

merge after
https://github.com/kgrgreer/foam3/pull/2678
https://github.com/nanoPayinc/NANOPAY/pull/16407

Another PR covering this pulled into


Sen0395 improvements

adding distance zones

You have to copy this file manually into your esphome folder before testing this PR: https://github.com/Schluggi/AIOsense/blob/df1e9c9895ff962b8346af271b451c054600fbb0/esphome/packages/lib/sen0395_distance.h

Closed because #125 is now part of #123.


Patch 1

Solving Issue on Source code:
https://github.com/MicrosoftDocs/azure-docs/issues/30743
On PR #236

@sptramer

@j0rt3g4 Please only submit pull requests where you have completed the checklist. This is a requirement, as outlined in the PR template. My time is so limited for PR processing that I can't devote time to examining or testing that people have followed the basic requirements for submission.

Reopening at request of @cynthn.

@j0rt3g4 Thank you for the contribution! I'll work with my team to get this fix merged into the script file :)

I'm sorry @sptramer my time is valuable as well and I honestly don't know what you're talking about.

Description
Customer helped by removing random characters and fixing an issue with the the reference to the storage type.
Checklist

[x] This pull request was tested on both of:

[x] PowerShell 5.1 (Windows)
[x] PowerShell 6.x (Latest PowerShell)

[x] Scripts do not contain static passwords or other secret tokens.
[x] All Azure resource identifiers which must be universally unique are guaranteed to be so.

Testing information

Platform:
Powershell version: $PSVersionTable.PSVersion
Major  Minor  Build  Revision

5      1      18362  145
Major  Minor  Patch  PreReleaseLabel BuildLabel

6      2      2
Az version: (Get-InstalledModule -Name Az).Version
PS Azure:> (Get-InstalledModule -Name Az).Version
2.6.0
Major  Minor  Build  Revision

2      5      0      -1

@sptramer Tested it locally and in CloudShell. See checklist above for details.

Sorry, that was much too snarky. The checklist is part of the pull request template and this is a standard process for any github repo that has requirements for beginning pull processing.

@cynthn Is this ready to be merged or any update needed? Let me know. Thanks :)

@sptramer I'm not understanding where you hit an issue. I tested this myself, using an existing snapshot, and it worked fine in both CloudShell and locally. Can you send me the version of the script you used?

@sptramer Sorry, tested the wrong version... yes, there is something wrong with this and I'm trying to track it down. There were 2 separate scripts (one was OS disk and the other was just a disk) with similar issues and similar syntax. You are correct, this one still isn't working. I will pull this over into my fork and try to find the issue. Sorry for the mis-direction!

#please-close @sptramer I found the issue and filed a PR that has the changes from @j0rt3g4 plus an additional fix to update the parameter for specifying the storage type. The new PR is: https://github.com/Azure/azure-docs-powershell-samples/pull/238


Dragonfire ward

🐛 Bug Report
Tried selling a dragonfire ward to a friend using both item ids 22002 and 22003. Neither work to trade the item even though I have 2 dragonfire wards.

resolved


usage

Could you tell me the steps to run these codes, I got a little confused.

Hi, sorry about that. I made it clearer now - if you want to just run the code, see the instructions at the beginning of the Training section.
After training, you can run your model on any image by following the instructions in the Inference section.

If you have any questions, let me know.


Init ScrollMonitor after ajax page load

Hello,
I set up a little script to init ScrollMonitor with Masonry and ImagesLoaded to have a full Lazy Loaded Masonry. Everything works as expected when the page loads :)
But, when i navigate to an another page, then i go back to the curent masonry/scrollmonitor page, all watchers are OK, but elementWatcher.enterViewport() does not fire anything. I have to scroll to launch elementWatcher.enterViewport, i tried elementWatcher.update() and elementWatcher.triggerCallbacks() as well, but both methods doesn't do anything.
I'm using Barba.js to handle ajax pages. Here is a look of what i've done:
masonry.js https://gist.github.com/proov/94c3955de351bff8cfb45d38a84d11b2
ajax-pages.js https://gist.github.com/proov/eff481d5fd6156c7753ade272343a146
I'm a designer, not a developper, be indulgent with my code :D
Any Idea ?
Many thanks! :)

are you destroying then recreating the elements? If so you'll also need to destroy and recreate the watchers.

As i can see, the problem does not come from ScrollMonitor but from Barba.js. If i reinit the function a bit later when the view is ready (after transition ended), then it's working as expected :)
I'm gonna ask some help from the author of Barba.js :D
Thanks again for scrollMonitor, it's really easy to use, even for a newbie developper like me :D


fix: Disable the default timeout for requests on the LU build

Description
This removes the timeout behavior on the /build endpoint, which can result in a network error when publishing a large language model. By default, Node's HTTP server class is set to timeout after 2 minutes.
https://nodejs.org/dist/latest-v6.x/docs/api/http.html#http_server_settimeout_msecs_callback
Task Item
fixes #4294

Although this addresses #4294, we should attempt to refactor this endpoint to better fit long processes, like polling or web socket.

I agree @a-b-r-o-w-n and have a proposal that I will follow up with ASAP.
In short: we already implement a polling procedure for the publishing. I would like to formalize this so that publishing, provisioning, and building can take advantage of the same subsystem.

@benbrown that's good to hear.

Test environment is failing with:
TypeError: req.setTimeout is not a function
  325 |
  326 |   // Disable Express' built in 2 minute timeout for requests. Otherwise, large models may fail to build.
> 327 |   req.setTimeout(0, () => {
      |       ^
  328 |     throw new Error('LUIS publish process timed out.');
  329 |   });
  330 |

Maybe we need to shim this api in the test runner?

@benbrown i don't know why tests are failing but it seems specific to this change

@cwhitten I think I found it. Just pushed a small change to the test.

Coverage decreased (-0.0004%) to 54.766% when pulling 76a4d0176bc0ae27a5e9de1863b77ea0cfee7179 on benbrown/fix4294 into b9172b14ea25fa6d2a3188d77f2b892388129752 on main.


Issue 13942 decreate version for ok http

The purpose of this PR is to address the jar version problem:

sdk depends on okhttp 4.8.1
spring framework depends on okhttp 3.14.9

After discuss with @chenrujun, we agree that downgrade okhttp version is not an ideal solution here, so close this PR.


Deploy CoreServiceRest links

Add links to the core service rest swagger UI and specs (both deployed at developers.rws.com)

@mpanhuijsen looks like the PR was closed but not merged, should I create another PR instead?


Mitigate Spyder wiping users' files with more robust saves and fail-safer autosaves

Problem Description
What steps reproduce the problem?

Save file to disk with connection issues (confirmed)
Crashes during runfile or during saving immediatly prior (reported 2x)
Other problems during saving???

Given we've publicly advertised the autosave feature as the solution to the reports we've been getting of Spyder completely wiping users' files on occasion e.g. @ccordoba12 in #6571:

I don't understand how Spyder can delete your script, but we're working to provide autosaving functionality for our next major release (Spyder 4).

and particularly now that our own developer @jnsebgosselin is regularly experiencing a such a problem and can reproduce it, we should ensure autosave is reasonably "fail-safer" in the event that saving the file normally fails (silently or otherwise) and wipes or corrupts the file on disk. As currently implemented by @jitseniesen following his hard work in #7660 , the feature is reasonably sophisticated with a nice UI. However, as an initial implementation, it does leave open several significant opportunities for catastrophic data loss in several major scenarios:
Failure mode:
Saving may fail silently, or in flushing the data to the storage medium, which would result in the autosave still being deleted and the save being corrupted or wiped (or at least out of date). This would possibly apply to the repeated instances of files being wiped that @jnsebgosselin is experiencing (depending on exactly how the failure occurs).
Mitigations:

Hardening the e.g. FileInfo._write_to_file() function, e.g. with <file>.flush() then os.fsync(); switching to the more modern io.open() on Python 2 and making sure files are explicitly closed might help a little too
Adding a readback check (at minimum, that the file reads without error and is the correct length, and perhaps comparing the first line), though this could be user-optional if its not determined to be critical or it takes a non-trivial amount of time
Temporarily disable autosave if a save failure is detected, and notify the user of this; only re-enable once a manual save is successful

Failure Mode:
Users could save more frequently than the designated interval (as is often a good habit to avoid the very data loss autosave is intended to prevent) or only have made new changes within that interval before the save,  and thus no autosave would be available to recover from if the save failed. Related to the above, if the user makes a change, no matter how small just before running a file, and if it was either unmodified before or had previously been saved, running the file triggers a save and thus could (and did in at least two cases, #6567 and #6571 )
Mitigations:

Make autosaves persistent during a session, i.e. not removed due to a user-triggered save, only on exit if Spyder quits cleanly with everything successfully saved
Have the FileInfo.save() function itself trigger a temporary autosave before it executed if none existed already, then save the main file (if the autosave was successful), and then delete it after if no errors were detected (perhaps with a user-optional readback check)

Failure mode:
The autosave itself could fail, either due to the same or different cause as the main save failing
Mitigations:

Ensure the user is given a clear and easy to interpret warning if autosave fails
Don't directly overwrite the old autosave; rather, write the new save to a new file (either a temporary one in the same location that's later moved to the old one's name, or one with an incremented number, updating the mapping accordingly), and only delete the old one autosave file success of the new. (Doing the latter, if it wouldn't add extra effort, would be a natural first step to the implementation of a simple versioning system down the road, by just not deleting the old autosave file and keeping an ordered list of the old autosave files matched to each source file in the mapping. Even better, instead of using the existing incremented number, a date could be appended to each autosave file name, making it easy for users to distinguish which files match with which even without the mapping and without creating a fancy UI for it. But I digress... :) ).

Failure Mode:
Another application, thread, VCS or the OS could modify, wipe or corrupt the file (or in turn break Spyder's saving), which Spyder would not not only not trigger the autosave to back up the current version, but assuming it detected the modification, it would automatically replace the contents in memory with the wiped/corrupted/reset/etc. version and possibly (not sure about this—@jitseniesen how does autosave behave when an external change is detected?) even delete any existing autosave and/or think the file is now unmodified.
Mitigations:

Ensure the original file being modified/wiped/moved/etc. externally doesn't trigger autosave deletion (I don't know if it does now; haven't tested)
When a file is externally changed and the version in Spyder's memory updated, ensure the "modified" flag that triggers autosave is unset, flag, so autosaves are not made unless and until the user makes intentional modifications

I've included the full form of the discussion between various parties on this issue below, for reference in one place.

The initial discussion on Gitter with me and @jnsebgosselin :
@jitseniesen I can do some functional testing too, hopefully tomorrow.
I haven't gone over the code in detail nor yet tested this behavior, but given we've advertised this feature as the solution to the reports we've been getting of Spyder completely wiping users' files on occasion (including multiple times to our own @jnsebgosselin ), I wanted to cross-post the relevant parts of the discussion @jnsebgosselin and I had a couple weeks ago on Gitter about how autosave should work, in order to "fail safe" and properly mitigate such issues (one of, if not the primary motivation to add it currently), to make sure that's included here:
@jnsebgosselin said:

I'm wondering about something regarding the auto-save functionality @jitseniesen is implementing.
This is also related to what people are saying in spyder-ide/spyder#2111 and spyder-ide/spyder#4409 . I'm saying this because on my new laptop, I have a small SSD and a large secondary HDD. I have a problem currently with the secondary HDD. From time to time, it simply disconnect. Du to this, it happened a couple of times that Spyder would wipe entirely the files that were opened when trying to save them or running them. Not only the unsaved changes were lost, but the entire content of the files were gone. I'm wondering if some of the people reporting in the aforementioned issues are experiencing that also.

@CAM-Gerlach said:

I've seen a number of similar reports, that we typically dismissed as isolated incidents, user error or not Spyder related at the time. That's the real value of the autosave functionality, not just for the unsaved changes but having an extra, separate backup copy that gets touched separately to the main one and, to provide the best protection against this issue, is persistent during a session (not being overwritten/removed after a user-triggered save, only on exit if Spyder exits cleanly with everything successfully saved) and not being directly overwritten during each autosave, but rather an (e.g. timestamped) new version is saved, and the old one only deleted until after confirming the new autosave was fully successful, with perhaps a few second delay to ensure everything is flushed to disk).

@jnsebgosselin said:

OK, that's what I was wondering.  If that's the case, we should change the title of the PR to take that into account because I think this is really important.

@CAM-Gerlach said:

I have no idea if that's exactly how it works. That's my naive suggestion of how it should work to start, to minimize the chance of data loss like you and others have described. The recovery UI is pretty neat though, and is an important part of it. A more advanced version of the feature, not really in scope for that PR, would save multiple versions of the document on a timer or every time it was saved, like most other editors and IDEs (NP++, Sublime, Pycharm, Eclipse, etc) offer.

@jnsebgosselin said:

Ah ok thanks! I agree with you on this. Anyway, I have a mean to reproduce the total wiping of file content until I send my laptop for repair if needed

@CAM-Gerlach said:

Yeah, the versioning would be nice. But just making the basic implementation of the autosave itself work like I described (not overwriting/removing the autosave when the file is saved by the user, only on a clean Spyder exist, and writing to a new file each time and only on confirmed success deleting the old, or warning the user that it failed) should (if I understand the failure mode correctly) ensure at least one good copy exists for the great majority of these events other that specific corner cases or user mistakes.
To really be safe against the file blanking problem, you would also want to include a check before deletion of an old autosave file and after writing the new one (or main copy, for when the autosave is deleted on a clean Spyder exit or manually closing a file in the Editor) that reads back the new/main one and refuses to delete the old/autosave and warns the user if either any error occurred during the test read of the new/main, or if the new/main save has >= ~3 bytes of content while the old one has e.g. > ~100 B; unless the user wiped an entire file of more than a few lines and left the empty file for some reason without deleting it entirely this would properly prevent meaningful data loss due to the file blanking problem and many other causes with few to no false positives; otherwise, the autosave feature might not protect against at least certain incarnations of the problem it was supposed to stop in cases where the error occurred silently, only to the main file or after the last autosave, was accidentally overwritten or corrupted, was due to some external hardware or software interaction with the file after save, etc.

@jitseniesen 's response:

It's an autosave, it's not a backup. It is inspired by the autosave system in Emacs, though I think most autosave systems work similarly (or they save periodically to the actual file opened without user interaction, which I think would be against what our users expect).
Work can be lost in all kind of ways and autosave does not protect against all failure modes. From the reports, the main failure mode (apart from user error) is that Spyder / the OS / the computer crashes and the user loses unsaved files. This should help against it.
It may not help against hard disk errors. Specifically, if Spyder saves the file and it thinks this is done succesfully, then the autosave file is deleted. So this autosave feature does not help if due to a hardware failure the file did not really save but Spyder thinks it did save. This may be what @jnsebgosselin experienced: Spyder think it saved the file, but in fact the file got wiped. I am not sure how often this happens, it seems pretty rare (I don't remember any report apart from his), but I think the solution would be hardening the save function, perhaps add an fsync or try reading back the file or I don't know.
Keeping the autosave file after the file is saved makes everything more complicated. I'm not sure it's worth the effort, and in any case I think it's best left to another iteration.

@ccordoba12 's responce:

Keeping the autosave file after the file is saved makes everything more complicated

I don't like this either because it pollutes your filesystem with backup files. I also agree with @jitseniesen that we need to leave that for another PR and it needs to be opt-in, not opt-out.

My response:

It's an autosave, it's not a backup.

Which technically is a backup, just a particular type of one (and not a substitute for a traditional one), intended specifically to protect against data loss or corruption due to application/OS hangs, crashes, power failure, and other such instances outside the user's control. From that viewpoint, crashes that wipe the data in user's open file(s) are intimately part of that narrow scope (as opposed to e.g. versioning, persistent backup, or other such protection against hardware failure or user error, etc).

I am not sure how often this happens, it seems pretty rare (I don't remember any report apart from his)

Aside from the multiple times he experienced it, there were at least two others, #6567 and #6571 , and I'm pretty sure I saw at least one or two more in another thread. In both of those, the error occurred when running a file, before which all files are automatically saved by default (putting them all potentially at risk), and if the fatal crash occurred anytime after the FileInfo._write_to_file() call returns, then the autosave will fail to protect against this. Furthermore, it also isn't any help in any situation where the crash/bad write occurs when on or around a save where the autosave file had been removed by a previous save and not regenerated (the file was previously saved less than 60 seconds ago, or if the file was only modified in the 60 seconds before save).
Although this is certainly rarer than just loosing unsaved work, the consequences are vastly more severe (total data loss of one or more entire files) and for a non-VCS managed project (or one that is not committed frequently), and the same good user habits (saving frequently) that insure against the former type of data loss not only give no protection for this, but actually make it more likely (more saves, and less likely for autosave to kick in.

I think the solution would be hardening the save function

Yes, we should certainly implement that as well, but it doesn't cover the window where the file is saved after Spyder has deleted the autosave and not regenerated one. Aside from not deleting the autosave copy after saves and only when Spyder is closed cleanly, a solution would be to have the save() function itself trigger an autosave before it executed if none existed already, do the save with flush and fsync, and then delete it after if no errors were detected (perhaps with a user-optional readback check).

I don't like this either because it pollutes your filesystem with backup files.

That's not really true for @jitseniesen 's implementation, since autosave files all go in the autosave directory under the hidden Spyder config directory, not scattered throughout the filesystem. Furthermore, they are still deleted on a clean exit and the only case where they are retained under our proposal relative to currently is if a file is saved, and then Spyder crashes sometime within 60 seconds (or before the user makes more changes), which is generally when a file wipe would be most likely to occur anyway.

I think it's best left to another iteration.

we need to leave that for another PR

Okay, sure, I guess. Perhaps @jnsebgosselin could do it if he has the time, since he's the one who can actually test if it works.

it needs to be opt-in, not opt-out

Perhaps readback verification could be opt-in, but the changes necessary (more robust saves as described above, and/or not removing the autosave files after save until clean exit) to protect against Spyder completely wiping users' files on save should be at least opt-out, since as a rare but potentially catastrophic problem users are unlikely to know to enable it until its too late, and I haven't seen any reports of this happening in other major IDEs.

@jnsebgosselin 's response:

I support @CAM-Gerlach view on this. Being able to protect against data corruption (backup & restore) seems like a very important feature to have. Even though it is not a frequent issue, when this happens, the consequences are  absolutely disastrous.

Don't directly overwrite the old autosave; rather, write the new save to a new file (either a temporary one in the same location that's later moved to the old one's name [..]

This is actually something we should probably do when saving the original file: do not overwrite the file, but save to a temporary file and then rename it over the original file.
Some relevant links:

http://stupidpythonideas.blogspot.com/2014/07/getting-atomic-writes-right.html
https://blog.gocept.com/2013/07/15/reliable-file-updates-with-python/
https://stackoverflow.com/questions/2333872/atomic-writing-to-file-with-python

@jnsebgosselin When your file got truncated, how did you find out? Did Spyder crash, did you get any error message, or were your files silently truncated?

Another application, thread, VCS or the OS could modify, wipe or corrupt the file (or in turn break Spyder's saving), which Spyder would not not only not trigger the autosave to back up the current version, but assuming it detected the modification, it would automatically replace the contents in memory with the wiped/corrupted/reset/etc. version and possibly (not sure about this—@jitseniesen how does autosave behave when an external change is detected?) even delete any existing autosave and/or think the file is now unmodified.

At the moment, if Spyder detects that the file on disk is changed and there are no changes in Spyder, the file is silently reloaded. If Spyder detects changes on disk and the user also changed the file in Spyder, then the user is given the choice to either reload the file from disk or continue with the changes made in Spyder.
So there are three cases. Autosave as currently implemented behaves as follows:

If there never were any changes in Spyder, there is no autosave file. Spyder reloads the file from disk and does not create an autosave file.
If there were changes in Spyder but the user chooses to reload the file from disk, then Spyder deletes the corresponding autosave file and now thinks the file is unmodified, so no new autosave file would be created until the user makes further changes to the file.
If there were changes in Spyder and the user chooses to keep them, then Spyder will keep the autosave file. When Spyder next saves the file, it will overwrite the changes made externally (and then delete the autosave file).

This is actually something we should probably do when saving the original file: do not overwrite the file, but save to a temporary file and then rename it over the original file.

Yep, makes sense—I didn't suggest this earlier since I wasn't sure a replace operation could be atomic. It essentially achieves the same thing as triggering an autosave first, but in-place, more reliably and more cleanly (especially once we drop Python 2 support in a year). I'll update the above accordingly.

Some relevant links:

Thanks, great resources!

http://stupidpythonideas.blogspot.com

So it seems the basic outline is:
with tempfile.NamedTemporaryFile(dir=os.path.dirname(original_file_path),
                                 delete=False) as fout:
    <the write>
os.replace(fout.name, original_file_path)

with the caveat being that os.replace is Python 3 only; we can substitute rename() on non-Windows platforms if replace is not found but we will need to depend on pywin32 on Windows (its already in the defaults channel and installed by default) to get MoveFileEx to do the same thing on Windows.

https://blog.gocept.com

If we don't worry about multiple Spyder processes for now, the main relevant piece here is the necessity to do
dirfd = os.open(os.path.dirname(original_file_path), os.O_DIRECTORY)
os.fsync(dirfd)
os.close(dirfd)

to flush the replace changes to the directory to disk.

@jnsebgosselin When your file got truncated, how did you find out? Did Spyder crash, did you get any error message, or were your files silently truncated?

Yes, this is quite important—if we can't trust the OS to raise an error if something goes wrong during the write to the tempfile, then we would presumably want to do at least a basic readback check, that e.g. the file length is the same as the version in memory and not 0, and that e.g. the first and last lines agree (or perhaps something more sophisticated; that's just a naive suggestion).

So there are three cases.

Thanks for the detailed explanation! The only potential issue, then, is the first case, where if we didn't persist the autosave file after saves. it would be nice to trigger an autosave of the existing in-memory content before it is replaced, but if we did persist the autosave the behavior is perfect.

Instead of rolling something on our own to make saves more reliable, we could just use the atomicwrites package. Its already on conda defaults and its what pytest uses.

@ccordoba12 Sure, I can take a crack at it, but it might be a bit since I have a few other PRs in the queue, a big course project due next Monday, the website to finish and some catch up to do on my research.

@dalthviz, please help us with this one. The idea is to use the atomicwrites package to save files from the Editor to disk. We could also use it to save our config files, but in a first attempt let's try to use it only on the Editor.

For the record, my config file has gotten wiped a few times, although that's less critical since there's a backup and I'm not 100% sure it was caused by a failed write. Also, we should probably save autosave files by the same mechanism (if they aren't already being done by the same save function that would use atomicwrites), to prevent them from being corrupted when they are needed.
@ccordoba12 Do you want me to split the other autosave-related stuff off to a separate issue, keeping this one more tightly focused on just the robust saves that using atomicwrites will mitigate?

Do you want me to split the other autosave-related stuff off to a separate issue

You mean the backup stuff?

The persistent autosave, etc. stuff, which is (hopefully) mostly unnecessary now to avoid this specific problem if the  atomicwrites approach fully avoids overwriting and blanking files, and whose functionality could be rolled into a simple timestamped backup system (each autosave being timestamped on creation, not deleted on save, and the last n files kept) to be much more useful.

@ccordoba12 Thanks; I've opened the issue as #8323 and removed the rest from here.

Thanks!


listorg and listbibl empty exports

as can be seen here, these lists are empty (0KB)
https://pmb.acdh.oeaw.ac.at/media/

this is strange: yesterday when we looked there were several exports, incl. the professions. just now the two lists are empty again and the other exports missing:


[AUTOMATIC] Release/0.7.0

This is an automatic release.
New Features

Add amountMicros to Price interface (#170) via Toni Rico (@tonidero)

Dependency Updates

Bump svelte from 4.2.12 to 4.2.19 (#168) via dependabot[bot] (@dependabot[bot])

Other Changes

ECO-1398: Added the possibility to pass a currency in the demo app query string params (#167) via Nicola Sacco (@nicfix)

Will hold this for now until #169 is merged


EC:<IP_ADDRESS> xref

EC:<IP_ADDRESS> is for "Protein-serine/threonine phosphatase":
https://enzyme.expasy.org/EC/<IP_ADDRESS>
But it's currently the xref for the parent term in GO:
id: GO:0004721
name: phosphoprotein phosphatase activity
xref: EC:<IP_ADDRESS>
instead of being on the specific serine/threonine term:
id: GO:0004722
name: protein serine/threonine phosphatase activity
Can you move the xref to GO:0004722 please?

Moved and Also added two rhea children
+id: GO:0106306
+name: protein serine phosphatase activity
+id: GO:0106307
+name: protein threonine phosphatase activity

Thanks Harold.
Two related things I just noticed:
i) "EC:<IP_ADDRESS>" appears to be given as a reference for the definition of "phosphoprotein phosphatase activity" and for 5 of its synonyms.  Should/could these occurrences of "EC:<IP_ADDRESS>" on the wrong term also be removed?
ii) The current def of GO:0004722 is:
def: "Catalysis of the reaction: protein serine phosphate + H2O = protein serine + phosphate, and protein threonine phosphate + H2O = protein threonine + phosphate." [GOC:bf]
I think that "and" should be changed to "or", or at least "and/or".

I saw that for 4722 and thought it was a very odd way of wording it. I'll fix later this AM

done


DOC-2 and DOC-3 (INFO) not reported consistently

The two info messages for mimetype and version (DOC-2 and DOC-3) are not reported consistently, and I am not sure of the pattern of when they are and are not reported.
DOC-3 is reported in most cases regardless of other output and regardless of whether the validator is run with or without -p. However, occassionally as in example 1, it is not reported. The scenario is a basic .fods file which should validate correctly without -p and should fail validation with -p.
DOC-2 is not reported very often.
Example 1: Run with -p
C:\odf\odf-validator-main>odf-validator.bat -p "filer/testfiler/T001.fods"
APP-1: [INFO] Validating filer\testfiler\T001.fods.
APP-5: [INFO] DNA ODF Spreadsheets Preservation Specification Profile report for filer\testfiler\T001.fods.
PKG-1: T001.fods [ERROR] An OpenDocument Package SHALL be a well formed Zip Archive.
POL_2: T001.fods [ERROR] Standard Compliance | The file MUST comply with the standard "OASIS Open Document Format for Office Applications (OpenDocument) v1.3".
NOT VALID, 2 errors, 0 warnings and 0 info messages.
Example 2: Run without -p
C:\odf\odf-validator-main>odf-validator.bat "filer/testfiler/T001.fods"
APP-1: [INFO] Validating filer\testfiler\T001.fods.
APP-4: [INFO] Validation report for filer\testfiler\T001.fods.
DOC-2: filer\testfiler\T001.fods [INFO] OpenDocument version 1.3 detected.
DOC-3: filer\testfiler\T001.fods [INFO] OpenDocument MIMETYPE application/vnd.oasis.opendocument.spreadsheet detected
VALID, no errors, no warnings and 2 info message found.

Hi @maria-messerschmidt. I'll take a look at this and see if I can reproduce it and fix quickly if possible.

Thanks! Let me know if you need anything from me.

Tested. Works ok. Closing

...


[WIP] NormaliseEvent pipe

This sets up the NormaliseEvent pipe which can handle flat Events/OnDemandEvents and anything with subEvents of type Event/OnDemandEvent.
Also has a lot of the boilerplate needed for the other pipes.
WIP:

provenanceInformation is not filled in yet
empty values and invalid properties are not corrected yet
there's a bug in the normalise-data pipe runner where it gets stuck in the while loop if there are no normalisedEvents to store (I think)

(current failing tests are expected due to first two points)

 Normalisations


Issue 39 test case

Refs #39

@evansiroky, is there any more action needed here (i.e., do we need to fix this test case)?

I spent a while debugging this whole thing. It turns out the test case data is flawed and has a place with a missing longitude that is throwing things off. This PR does have code that generates code coverage reports, but I don't think we need that at this time, so I'm closing.


[Missing SNMP Polling Profile] Barracuda CloudGen Firewall F380b

Device Vendor: Barracuda Networks
Device Model: CloudGen Firewall F380b
System Object Identifier (SysOID): .<IP_ADDRESS>.4.1.10704.1.10
List of critical metrics that you expect in the profile (does not need to be all-inclusive, just a general idea of your expectations):

Hardware Sensors (CPU / MEM util, disk space, temperatures)
Licensing (ok/expired/grace period)
Concurrent VPN Users Online
interface throughput

If there is a New Relic technical support case related to this request, please provide the case number:
Please provide a public gist with a sanitized (sensitive information removed) SNMP walk of the device. Providing MIB files is not a substitute for an SNMP walk and failure to provide one here will result in delays for closing this issue. The output of these commands shows the "true story" of what a device will respond to in SNMP and is used to ensure that our profiles are efficient and accurate for your devices.
Gist Link: https://gist.github.com/neonunit/2ed765af7c771886a3b024ec82b6a249

Example SNMP walk commands:
# v2c example
snmpwalk -v 2c -t 10 -On -c $COMMUNITY_STRING $IP_ADDRESS . >> snmp_walk.out

# v3 example
snmpwalk -v3 -t 10 -l authPriv -u $USERNAME -a MD5|SHA -A $AUTH_PASS -x DES|AES -X $PRIV_PASS -ObentU -Cc $IP_ADDRESS . >> snmp_walk.out

MIB descriptions: https://campus.barracuda.com/product/cloudgenfirewall/doc/95259178/phion-mib-field-descriptions/

Thanks! Looks like the device is now recognized. However, some data fetched don't seem to be correct, for example memory utilization:
From New Relic:

From Firewall Admin management app:

There's some UI work to do on the NR side since this is a new device family.  If you email me at<EMAIL_ADDRESS>I can take a look at the data in your account and update the widgets to display the right OID's for this device.


Fix schema:fetch when record type has no fields

The old behavior is that the fields key contains
null value if the record type has no fields. This
is because the slice is not initialized to empty slice.

Picked as 4b81eab.


Update

@vnlitvin need to test with this option

@vnlitvin need to test with this option

pls do :)


CLI is built with go 1.20, but apk add go install go 1.19 in Dockerfile

In the multistage Dockerfile that is used to build the official release of the image there is a problem with go versions:
Under the first scope (FROM golang:1.20-alpine AS dev) go 1.20 is used, but under the second scope:
FROM alpine:latest AS cli
...
RUN apk --no-cache --update add go

Alpine will resolve to go version 1.19 today.
It is probably good to be explicit about what version of go to install, rather than rely on whatever is distributed through Alpine right now.
This affects the resolution-cmd branch.

https://github.com/debricked/cli/pull/54/commits/1860ce6100079f55b737a632e6a8554087643b04


Replacing all references of qbarrand with rh-ecosystem-edge.

The project was migrated from github.com/qbarrand/gitstream to github.com/rh-ecosystem-edge/gitstream, therefore, all import path were needed to be updated.
Also building the new ghcr.io/rh-ecosystem-edge/gitstream image.
--
/cc @yevgeny-shnaidman @TomerNewman

Fixes https://github.com/rh-ecosystem-edge/gitstream/issues/140

/hold
I wish to make sure that the new image quay.io/edge-infrastructure/gitstream:latest is being created.

/cc @mresvanis

/unhold
The image exists and can be pulled:
ybettan release (master) $ podman pull quay.io/edge-infrastructure/gitstream:latest
Trying to pull quay.io/edge-infrastructure/gitstream:latest...
Getting image source signatures
Copying blob 417aaa7ce275 skipped: already exists
Copying blob 6e5015e02423 done   |
Copying config 7cdbf6d0a6 done   |
Writing manifest to image destination
7cdbf6d0a679c513a835722144b52a205f38000d52e8be773ea2b4b509069a9d

/lgtm

/lgtm


Suggested International Compatible UX + Mega Step Count Support

Reasons

In order to provide internationalization by default, the controls can be changed to icons.
In order to support a larger number of steps, the dots can be replaced with numbers, ex: (3 / 12)

Suggestions

[ ] End tour button is replaced with an "X" icon
[ ] Next / Prev controls are forward / backward arrow icons
[x] Dots are replaced with [current step]/[total steps]

with >5 pages

with <=5 pages

as a note, this can also be overridden by providing HotspotProvider with a custom actionBuilder

going to leave these strings but they are overridable now by providing HotspotProvider with eg actionBuilder: HotspotActionBuilder(doneText: "Fin!"). And as always you can provide your own actionBuilder.
As a note, I did like the icon idea, but material doesn't really have a strong concept of a raised icon button that I'm aware of.


Add createdDate column in InventoryCountImportItem table

Add createdDate in InventoryCountImportItem table. As some nifi flows are dependant on the "Created Stamp" (auto generated field of OFBiz) field and from new Cycle count app (based on Moqui) it is not set.

Changes are merged now. Closing the ticket.


should implement logging

It would be very useful to have python logging with log levels, redirection, etc.

Team agreed to start this as part of Task 9

We'll need to update the documentation and example as well once this is implemented

I am working implementing standard python logging with facility for user to configure log levels, file output, etc from logging.yaml file in configs dir.
Currently going through and replacing most existing print statements with logger calls with appropriate severity levels, etc.

Team agrees logging looks good - https://github.com/UDST/activitysim/wiki/Project-Meeting-2016.06.15


Remove unreachable condition when write host list

Remove unreachable condition when write host list.

What is this change used for? Let torch.distributed mode support different pattern?


feat: Completa código de vista principal del curso

Esta es la página en la que los usuarios van a pasar la mayor parte del tiempo.
Algunos ejemplos:
Udemy:

Edutin:

Moodle:

TalentLSM:

Codecov Report

Merging #2 (d727a83) into main (43a1916) will increase coverage by 1.66%.
The diff coverage is 95.83%.

@@            Coverage Diff             @@
##             main       #2      +/-   ##
==========================================
+ Coverage   70.76%   72.43%   +1.66%
==========================================
  Files           3        3
  Lines         325      341      +16
==========================================
+ Hits          230      247      +17
+ Misses         95       94       -1

Impacted Files
Coverage Δ

now_lms/__init__.py
73.00% <95.83%> (+1.71%)
:arrow_up:

Continue to review full report at Codecov.

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


Issue in opening the local apps

I will make an optimal way to open the application on any one computer
As a participant of GSsOC '22, I would like to work on it.

Please assign this to me so that I can start working on it.

@Umesh-01 haven't assign the GSSoC22 and level labels in pr #47


Custome Domain within Amplify and Route53 not redirecting to Cloudfront

d3vs58t9vnm0c1:
US-WEST-2:
Custome Domain not redirecting to cloud front:
Status

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
I have route 53 domain name with hosted zone and updated NS. When I add the domain in domain management under Amplify console after status becomes available for the domain, cloud front url that amplify provides does not work.

Domain name does not work but the amplify urls work

those cloud front urls dont resolve either, thats what amplify puts in route 53. So im guessing this is where the issue is but i dont know how to resolve it
Route 53 configuration

This issue was resolved automatically after 24 hours. I guess dns took a while to update.

This issue was resolved automatically after 24 hours. I guess dns took a while to update.


can't create a Virtual Network Gateway in Microsoft Azure

I'm trying to create a Virtual Network Gateway but getting the error "The operation failed because the network security group NSG-centralus can not be associated to the GatewaySubnet. Please remove the network security group associated to the GatewaySubnet. No changes have occurred on the gateway at this time."
I've tried to remove NSG from the default subnet of the virtual network but when I click to save the subnet with NSG section as None, it comes back reflecting the default NSG.
I tried creating a new subnet with NSG-None but it gets saved with default NSG.
I'm unable to figure out what to do to fix this.

@RajaPrasadShaw, Thanks for reaching out. We will investigate and update this thread.

@RajaPrasadShaw, I was wondering if you have had a chance to look over our previous reply yet? Let us know if you have any query or input for us or if we good to close this issue.

@RajaPrasadShaw, since we have not heard back from you, we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


How to use this library?

I looked at the documentation and was not sure on how to use it in my application. Once I run userStore.init(), does it automatically request a JWT from the web server? If so, how does it know what the server address is?
Thanks.

The library assumes that the JWT is stored on a cookie under the key, XSRF-TOKEN. This can be overridden by passing cookie on the options hash:
  let userStore = require('react-jwt-store')({ cookie: 'NOT-XSRF-TOKEN'});


Update the nested lists for better readability

On the rendered page the bullets are all at the same level and don't show nested, making it slightly difficult to understand the hierarchy. This edit fixes this.
What's changed, or what was fixed?

Nested lists were fixed

Fixes: n/a
Target Live Date: n/a

[x] I have run gulp test locally and all tests pass.
[x] I've staged the site and manually verified that my content displays correctly.

CC: @petele

:tada: This has been pushed live to https://developers.google.com/web/


1.16.5 backport?

Hello! I really love the concept of this mod, and especially the textures that you've made for it! What I don't love as much is that it can only be played on 1.17 snapshots, which not all Fabric mods currently support, and which, being snapshots, can have various stability issues, and can also receive sweeping changes to gameplay at unexpected times. As such, I would like to humbly ask if it would be possible for you to backport this mod to 1.16.5 in addition to its snapshot release, so that players stuck in this version because of other mods or who don't want to play on snapshots can play with it. If not, that is totally cool.~
Also, I apologise for opening an issue for a request; Discussions are not open on this repository.

Yup, it's planned. No ETA.

Yup, it's planned. No ETA.


feat(rm): allow more than one chart removal

This addresses #217.

This should also add a multiple-chart test to remove_test.go.


Allow reading from catalog for document

Fixes #57
First shot at adding support for providing a catalog file as input.
Things that you might want me to change:

using col.lower() - I had to use it to make the code work with my own project on Snowflake where the YML files are defined with lowercase columns but are stored as uppercase in catalog.json
the parameter name called --catalog-file or how we want users to be able to pick between offline (catalog) vs online (connecting to the warehouse)
how I handle parts to match the function parameter and catalog file

Here is some case sensitivity leaking into our inheritance.

@b-per
I am thinking we merge your branch as-is and I will make a follow-up issue/PR with my notes above to fix up column comparison.
A second follow up issue will be on preferring the catalog path. The obvious consideration is that you would not want to pursue the on-the-fly catalog path if you are running a subset of models. So maybe we consider the # of queued models based on the selection criteria and decide then.
LMK if you have any thoughts or objections.

@z3z1ma
Here is another spot where there is a case sensitive comparison.
Should also apply self.column_casing(col) to yaml_columns_ordered to avoid adding the case logic to all of the comparisons?

I think we want a dedicated Column class that all columns are marshaled into. From there we can define a custom __eq__ method which accounts for the target.type
(IE the adapter). In this way we can preserve whatever casing the user is using but compare columns in sets / loops / c in cols / etc without mutating what we have in memory as the source of truth for whatever the user has. I can tackle that as soon as I merge this.
# The advantage to this approach other than being very simple is that it should work with sets, lists, in / not in, and so on without having to call some special casing func everywhere or needing more list comprehensions.

class Column:
    def __init__(self, name: str, db_type: str | Enum):
        self.name = name
        self.db_type = db_type

    def __eq__(self, other: Column):
        if self.db_type == types.Snowflake:
            return self.name.upper() == other.name.upper()
        return self.name == other.name

    def __hash__(self): ...

While the handling of different casing definitely needs to be enhanced, I agree with you that it can be done in a separate issue. It shouldn't be too much work to then refactor what I added.
If you are ok with it, I can add the new flag to the refactor function and we could then consider this one closed and merge it.
On the topic of getting the columns for each model or using the adapter capability to run dbt docs generate, in my mind, it would depend on the number of models that need to be documented. dbt docs generate can start taking some time on larger projects and we might not want to run it all to just document a handful of models.

@b-per
Agree on both. There is a sweet number somewhere before the docs generate would be faster. I will try to find a sane default and otherwise expose it as an env var for user modification in a follow-up issue.
Once you add to refactor, I will merge.

Done, I have added the config for refactor 😃


Fixed dead assignment and quiz link

Fixed non working 404 error visual studio and quiz link

Closing PR as changes not currently needed.


remove auto sign in link from new user email

Closes https://github.com/covidwatchorg/portal/issues/377 (see comment)

I don't see anything of issue here.
Without testing it, I'm assuming the functions.config().client.url on line 183 returns the staging or prod URLs, right?

Yep


Add support for another products (PyCharm etc.)

All JetBrains products are similar so it will be not so hard to add support for another products. Thank you:)

It should be available soon.


More codegen fixes

This PR fixes:

Improve how we unwrap types
Add support for booleans

/pre-release

Pre-release
:wave:
Releasing commit [b57ed971c048c9ac333b0f6c8196ee03a4d22826] to PyPi as pre-release! :package:

/pre-release

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release fixes a couple of more issues with codegen:

Adds support for boolean values in input fields
Changes how we unwrap types in order to add full support for LazyTypes, Optionals and Lists
Improve also how we generate types for unions, now we don't generate a Union type if the selection is for only one type

Here's the preview release card for twitter:

Here's the tweet text:
🆕 Release (next) is out! Thanks to @patrick91 for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)


Main app tests

@mattheuslee If you can create a stub for XmlEntryBookStorage (check StorageManager) it would be better, but this one works fine.
I just realized it'll be very hard to test for IOException in the initModelManager, might get build error in AppVeyor

@akd13 okay, I'll take over from here

Coverage increased (+0.1%) to 92.445% when pulling 4398cbf14967230499bc2d04e2af7da2492f5462 on MainAppTests into 3721858e3bdeae40ab46eaff0edac8038bc5c9be on master.

Coverage increased (+0.2%) to 92.553% when pulling b3f19d9a028185e78d2235e821074a77fc881d66 on MainAppTests into 3721858e3bdeae40ab46eaff0edac8038bc5c9be on master.

@CS2103JUN2017-T2/developers Not sure how to test the rest of MainApp, open to suggestions

@mattheuslee aah much easier to understand how test stubs work lol. you can delete my method and collation tag!

@akd13 It's alright, I can just leave it in 😄


Possible issue with NoCodeSign.xcconfig

Hey,
I made a PR lately to fix a weird signing issue with the ios-nocodesign-* toolchains. While it worked on pretty much all of our CI jobs, one failed when CMake tried to check whether the compiler was okay. I think the problem is due to one extra line in the NoCodeSign.xcconfig file, but I’m unsure and I don’t know whether others reproduce.
The line I deleted on a local fork is:
CODE_SIGN_ENTITLEMENTS=""

leaving the file as:
CODE_SIGN_IDENTITY=""
CODE_SIGNING_REQUIRED="NO"
CODE_SIGNING_ALLOWED="NO"

I’m currently testing my patch before  opening a new PR. What do you think?

I’m currently testing my patch before opening a new PR. What do you think?

The version before https://github.com/ruslo/polly/pull/300 worked fine for my local machine and on Travis machines. The https://github.com/ruslo/polly/pull/300 patch seems to be fine there too. So it's hard to say :)

I made a PR lately to fix a weird signing issue with the ios-nocodesign-* toolchains. While it worked on pretty much all of our CI jobs, one failed when CMake tried to check whether the compiler was okay

It does make sense to save the error message that you have for the history. What error message was before the https://github.com/ruslo/polly/pull/300 was applied and what error message do you have now?

Prior to #300, we had the binary on simulation signed and we had to manually remove the signature after the build. After #300, we had this:
-- Check for working C compiler: /Applications/Xcode-10.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -- broken
CMake Error at /usr/local/Cellar/cmake/3.13.2/share/cmake/Modules/CMakeTestCCompiler.cmake:52 (message):
  The C compiler

    "/Applications/Xcode-10.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang"

  is not able to compile a simple test program.

…

builtin-productPackagingUtility -entitlements -format xml -o /Users/distiller/****/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug-iphonesimulator/cmTC_235b1.build/cmTC_235b1.app-Simulated.xcent
    warning: Falling back to contents of entitlements file """" because it was modified during the build process. Modifying the entitlements file during the build is unsupported.error: The file “""” couldn’t be opened because there is no such file.

    ** BUILD FAILED **

I confirm my patch fixes it. I’ll do another PR if you want.

Prior to #300, we had the binary on simulation signed and we had to manually remove the signature after the build.

Can you post step by step instructions with all details: CMake version, Polly toolchain, Xcode version, log with sign instruction line, the code itself.

Hello,
I’m not sure what to do with the details since it’s code from work. It’s open-source though so I guess it should be okay. I’m adding @KhalilBellakrid and @pollastri-pierre to the discussion for this purpose.
The failible job can be found here.

I’m not sure what to do with the details since it’s code from work.

There is no need to show the whole project, of course only minimal example would be nice to have.

The failible job can be found here.

Okay, at least some info :) It's Xcode 10 and we are failing while checking that C compiler is not broken.

Yes, and I think it’s due to the empty entitlements. I only a few about iOS, so I wrote a sed line to fix that in our circle-ci job. I just wanted you to know. :)

I've added iOS tests to CI: https://github.com/ruslo/polly/commit/b14ab7b3b24865df4a6269a489b042cd027badf9
CMake 3.13.2, ios-nocodesign-11-4-dep-9-3-armv7, Xcode 9.4.1:

https://travis-ci.org/ruslo/polly/jobs/470130472

CMake 3.13.2, ios-nocodesign-12-1-dep-9-3-armv7, Xcode 10.1:

https://travis-ci.org/ruslo/polly/jobs/470130473

The failible job can be found here.

I've noticed that you've used this line:

-G Xcode -DCMAKE_BUILD_TYPE:STRING=Release -DBUILD_TESTS=OFF
-DCMAKE_OSX_ARCHITECTURES:STRING=x86_64 -DCMAKE_MACOSX_BUNDLE:BOOL=ON
-DCMAKE_OSX_SYSROOT:STRING=iphonesimulator -DCMAKE_TOOLCHAIN_FILE=/Users/distiller/lib-ledger-core/toolchains/polly/ios-nocodesign-11-2-dep-9-3.cmake

CMAKE_OSX_ARCHITECTURES and CMAKE_OSX_SYSROOT should not be used here. If you want to limit architectures to 64 bit variants then you should use another toolchain like ios-10-3-dep-9-3-x86-64-arm64. Also last time I've tried simulator-only toolchain I had CMake issues, so all Polly toolchains with simulator have ARM-device part.

Interesting, thanks for your feedback!

Closing inactive discussion.


So sorry to reach out through here!

Unfortunately github doesn't have messages so I hope this is okay.
I am looking for anyone who has shown recent interest in PyQt5.
Me and a small group of others are working on a productivity tool using PyQt5. Our goal is to create a tool that can help others in any industry. Specifically we are creating a feature heavy productivity tool. I think this could be a good opportunity to add on to your portfolio, learn something new and work in a team setting. We need any help we can get :)
https://github.com/derto42/FlowBuddy
Please add the discord if interested: https://discord.gg/ahvpBbXG

Looks interesting, but I don't have the bandwidth for this. Good luck!


Add handled/unhandled properties to payload

Added handledState object argument to sendToBugsnag() detailing:

severity
unhandled
severityReason

payload.defaultSeverity is set based on whether the user sets severity (or changes it via beforeNotify callback) such that payload.severity === handledState.severity.

Coverage increased (+0.1%) to 76.326% when pulling c142edb6949263311811a5f4584dc7588e6e9188 on handled-unhandled into c62d51a47538303e143d884507497c630cae91fa on master.

We might also need to change the code in the wrap function to report severity_reason timer_callback and pass the attributes required along as well

It's certainly possible that would have to wait until we re-architect the lib too though.

We need to make some changes to the unhandled promise listener stuff though I think

Good spot, I missed this. Added in 296e1b4.

Coverage increased (+1.1%) to 77.316% when pulling 296e1b4d61b922daf4d36294bab059735e4e95ba on handled-unhandled into c62d51a47538303e143d884507497c630cae91fa on master.

I think 7b34982 addresses the wrap() issue. However I think exception_handler is not the most appropriate severity reason, but it's the best we have right now.

Coverage increased (+0.9%) to 77.068% when pulling 011e934af4b1da9590fcfd08298b9ae5bae2c0a0 on handled-unhandled into c62d51a47538303e143d884507497c630cae91fa on master.

Coverage increased (+0.9%) to 77.068% when pulling 011e934af4b1da9590fcfd08298b9ae5bae2c0a0 on handled-unhandled into c62d51a47538303e143d884507497c630cae91fa on master.


flavored-markdown lists don't properly handle CRLF line terminators

Background knowledge
Unix and DOS based systems use different line terminators:

Unix: \n (newline)
DOS: \r\n (carriage-return line-feed, CRLF)

Describe the bug
The regex used to identify markdown lists doesn't properly handle /r/n line terminations, causing unintended behavior in our flavored-markdown.
To Reproduce
I found this issue while working on Vantage Console in-product help, which utilizes Covalent markdown-navigator & flavored-markdown.
We want to display relative and external links within help .md files. However, the links in some files are not rendering as intended. (See screenshot below).

In other cases, both relative and external links are working fine:

The difference is caused by the line termination on these two files. The improper, first screenshot has only \n unix-style line terminators, while the properly displayed API guide has \r\n.
Looking at the code, the intention is for flavored-markdown to identify markdown lists and convert them to the cfm-list component. But, the cfm-list only displays the raw list item content; It doesn't identify and convert links to <a> tags.
When processing a markdown file with CRLF line termination, the regex used to identify markdown lists doesn't return any matches, so flavored-markdown doesn't convert markdown lists to the custom cfm-list component. Those links are rendered properly with the vanilla showdown link styling.

Expected behavior
flavored-markdown should accept markdown with either unix or dos style line termination, and should render links in lists properly
Suggested fix
Remove the cfm list entirely, and just use the default list built into showdown. Then all line termination styles will be properly rendered.
Alternatively, we could update the regex to match both \n and \r\n, and add logic to convert md links to <a> tags in the cfm-list component. This requires significantly more engineering effort.
@owilliams320 @jeremysmartt is there a reason to keep the cfm-list component? Or can we remove and use the default showdown styling?

This is fixed under #1984


fixing typo - publically to publicly

Hi @karann-msft, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;


using .pkl file in global directions

i have custom dataset and i used stylegan for image generation and now i have pretrained .pkl file. how can i use this file to generate images from text using global direction?
thanks in advance

I used the .pkl file in this project and I feel the key point is load the model with the correct way like--  with open('your model path','rb') as f: g_ema = pickle.load(f)['G_ema'].cuda() somthing like that. Nothing special


Implement Event Tracking on Slide-in Footer Buttons

Requesting implementation of event tracking on the buttons on our slide-in footer. The slide-in footer appears when someone is viewing a project but is not logged into the OSF:

Event tracking (more here: https://developers.google.com/analytics/devguides/collection/analyticsjs/events) can tell us, via Google Analytics, when users click "Create an Account," "Learn more," or "dismiss this message" (or the x in the top right corner). This will help us evaluate effectiveness of the footer. We cannot understand user flow this way currently because there is at least one other way to get to "create an account" or "learn more" on each page (rather than from the footer buttons). This is in support of community priorities for this spring -- converting observers of the OSF into users of the OSF.

@lyndsysimon Any chance you can / should knock this one out? -- or is it Intern worthy? Thanks!

any updates/further thoughts on this?

@saradbowman I'll find someone to put on this one and get it done

@HarryRybacki Can you take a look at this? TY

Thanks!
On Fri, Feb 6, 2015 at 10:02 AM, LarryB<EMAIL_ADDRESS>wrote:

@saradbowman https://github.com/saradbowman I'll find someone to put on
this one and get it done
—
Reply to this email directly or view it on GitHub
https://github.com/CenterForOpenScience/osf.io/issues/1521#issuecomment-73249245
.

Yep!


Reimplement rendering using X11

It does not look we can get good performance using SDL2. The main reason is SDL2 does not allow to us to disable double buffering. I suggest reimplement rendering using X11 for Linux. For Mac we can use X11 as temporal solution and later move to some native API.

Won't implement.


Cross-Browser Support

Enhance the project for it to be used in different browsers other than chrome, for example Firefox.

Completed, extension works in FireFox now.


Surface config override parameters simplify calling scripts

A simple parameter override simplifies scripting in large workflows.
Currently, the only way to build a surface model for a new wavelength grid is to write out a new .json formatted configuration file.  This minor change allows the surface_model() function call to overwrite wavelength file and output file locations, so we can create new surface models dynamically without having to parse/write a JSON file.

This makes sense, especially for notebook-style implementations.  Thanks!


Add cache support #376

This pull request adds support for cache operations to the DataSet object.
See issue #376

If possible I would like to backport this to a version that supports Spark 3.4 as well.  My current project is on Spark 3.4 because the infrastructure it runs on does not support 3.5 yet.
The code changes in this PR should work on Spark 3.4 and prior versions without modifications.
I would appreciate advice on how the project maintainers would prefer the backport to be done.

Thanks @jonmcleaJo, this is a really useful contribution!
Wrt backporting, it should already work with spark 3.4 out of the box. We don't really explicitly test older versions of spark in the cicd because we don't expect any trouble there. Of course, if you do see a reason why we'd need to do so, we can easily add that. Let me know what you think!
Happy to merge this btw!

Let's go ahead and merge.  I reviewed the changes over the last few releases and there does not appear to be anything specific to Spark 3.5.

Thank you for your contribution!


build(pyproject): pin all current dependencies to >=min,<max ranges (#1119)

Description

Related issue: #1119
probably need to be rebased after https://github.com/rdmorganiser/rdmo/pull/1106
Motivation and Context

How has this been tested?

Screenshots (if appropriate)
Types of Changes

[ ] Build related changes

Checklist

[ ] All new and existing tests passed.

rebased to dev-2.2.0

this one was already approved and it's only been rebased to include some updates by the dependency-updates branch so i'll merge this one now as well


React Native compatibility

I saw a previous issue related to this, but to add to this, I would love to see React Native compatibility for this project.
At current, it looks like the big issue is that PDFKit requires a Writeable Stream which React Native doesn't implement.

You could try running Browserify on the code and using the built file... I don't have much experience with React Native though. Let me know if it works!

@nullfox do you have a feedback on your experience trying to generate PDFs with React-native using pdfkit ? or something else ?


Add Blackjack

Add Blackjack to README.

I don't see the need of waiting the 30 days in this case, WDYT @veelenga?

@hugoabonizioI think this section is exceptional and doesn't require that.


Correct Prost build issue.

Using the current main branch, if the Cargo.lock file is removed the build fails with the error:
error[E0277]: the trait bound `celestia_tendermint_proto::v0_34::types::ValidatorSet: prost::Message` is not satisfied
    --> target/debug/build/celestia-proto-d9e58f87878dccfd/out/header.pb.rs:5:28
     |
5    | #[derive(Clone, PartialEq, ::prost::Message)]
     |                            ^^^^^^^^^^^^^^^^ the trait `prost::Message` is not implemented for `celestia_tendermint_proto::v0_34::types::ValidatorSet`
     |
     = help: the following other types implement trait `prost::Message`:

The issue comes from the fact that the crate celestia-tendermint-proto use the post version 0.13.3 and the proto crate the version 0.12.6.
I've changed the dependencies version to 0.13.3 but kept the build-dependencies to the old one because otherwise, build.rs  doesn't build.

Yeah, we saw it. The issue is that the celestia-tendermint-proto doesn't follow semver. We were discussing it and unless it's an issue for you, we'd fixing it by merging #

Ok I see. No need to merge if you have another plan to correct it. For now, we'll use our fork and when it will be solved, we'll switch. I'm little surprised that no other users find this issue. Perhaps it's still hidden for them, but you're going to have more and more user that get it.


TrainSplit eval_size can be set during init as train_split_eval_size.

To change the eval_size of TrainSplit, it is no longer necessary to import it first. Instead of
from nolearn.lasagne import TrainSplit
net = NeuralNet(..., train_split=TrainSplit(eval_size=0), ...)

it is now possible to do:
net = NeuralNet(..., train_split_eval_size=0, ...)

This is consistent with setting other parameters, such as those of layers or of objective. The old way should still be possible, though.

There's BatchIterator which works the same way: you have to pass an instance instead of class + args separately.  That's for better or worse, but so TrainSplit isn't the only inconsistency.  I think this is a minor wart, and doesn't warrant introducing a change + code to stay backward compatible.

Okay, I can see that. The question is where do you draw the line for what is treated which way? Why is TrainSplit treated differently than objective?

I'm afraid there is no clear line.  :-/

Hmm, that's too bad, maybe there should be one.


text fields not showing typed characters

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
text fields not showing typed characters
a snap shot of these fields and all of those has value but they are invisible even in setting view

.

Steps to Reproduce

oppening atom
try to find something by pushing Ctrl + f
start typing

**Expected behavior: to show characters
**Actual behavior: fields seems has value but they are invisible
**Reproduces how often: always
Versions
Atom    : 1.25.1
Electron: 1.7.11
Chrome  : 58.0.3029.110
Node    : 7.9.0
Additional Information
I have virtual mac on my machine and i'm not sure if it's related to that one or not. I had older version of atom and was working properly after updating to last version happened to me.

Can you follow the steps in the Debugging section of the Flight Manual to check if this is a GPU related issue?

I tried to turn off gpu no different

So to be sure, you are closing all instances of Atom, and launching it with atom --safe --disable-gpu and are still seeing this?

this one worked so what should I do to fix it ?

that command worked!! So how can I disable gpu permanently?

I did it in additional information , By the way it's mac :)

I am seeing this issue on Atom 1.27.2 on Mac OS 10.12.6 on a Mac Pro 5,1, with GT120 graphics. Reinstalled atom, no change.
atom --safe --disable-gpu works around the issue.
as does
atom --disable-gpu
How can I set this permanently?
And can we get this fixed :)

@mrstux you can use alias http://osxdaily.com/2017/05/22/how-make-shortcut-alias-mac/

@bidva AFAIK you can't specify command line arguments/flags in an Alias, unlike in a Windows shortcut. Its much more like a soft symbolic link.

I am having this same issue on Mac Pro (early 2008) OS X 10.11.6
Graphics NVIDIA Quadro FX 5600 1536 MB
I can start atom by using
atom --disable-gpu
However, that is not a viable solution. Will there be an update?

Made a patch for permanent gpu disable support, but discovered that similar PR #17699 was already rejected.

Here is a solution for those who use bash.
In your ~/.bashrc or ~/.bash_aliases type this, after this run source command
Run atom without gpu acceleration
function runAtom {
atom $@ --disable-gpu
}
alias atom=runAtom


byte order mark becomes space before first field in header when exporting from excel

I think that's what's happening, anyway. When saving a sheet as CSV from Excel, my default is UTF-8. and if the first column header is "name" it becomes " name" in the schema.
My workaround: Save as CSV (MS-DOS). 😱

@judell Thanks for the feedback. We will check this out.

@judell I exported one of the google worksheets to CSV, could not replicate the same. Did you try with any MS Excel files?  That might be causing the issue? I can give it a try from a windows PC / apple-store MS excel may be.


Chore/1214 reboot upgrade tika spring

Checklist

[x] the [contributor license agreement][] is signed
[x] commit message follows [commit guidelines][]
[ ] tests are included
[ ] screenshots are included showing significant UI changes
[ ] documentation is changed or added

Description of change
Initial effort to upgrade oEQ to Spring 3, and the latest Tika and CXF.

interesting - compile succeeded locally, but I guess installerZip was a better / more complete option.  I've replicated the failure locally and will investigate.

interesting - compile succeeded locally, but I guess installerZip was a better / more complete option. I've replicated the failure locally and will investigate.

Yes, I recommend the team always do at least an installerZip, but even better do a smoke test via sbt cleanrun and at least log in. ;)

Thanks for this @cbeach47
I see it's all nice and green, so I'll jump in for a review tomorrow.

re: cleanrun - that's interesting.  I did a compile > equellaserver/run.  I'll try cleanrun next time.
Note this is just the Spring portion - upgrading CXF threw a bunch of deduplication errors that I'll be wading through shortly and push out to this branch.

After further review, some of the changes weren't needed for a clean build, so I rolled those back.  I attempted to specify the merge strategies for the overview.html by testing for org.springframework, but couldn't get it to work (it acted like the merge strategy wasn't even in place).  Since it's a documentation file, I'm not going to worry too much about it.  If the CI builds with the latest commit, then I plan to merge this to focus on the meat-n-potatoes of CXF and Tika.

I attempted to specify the merge strategies for the overview.html by testing for org.springframework, but couldn't get it to work (it acted like the merge strategy wasn't even in place). Since it's a documentation file, I'm not going to worry too much about it.

So is this why you only rolled back one, but left three? If so, as per the feedback on the other, could you perhaps add a comment to say which dependency triggered the issue?
Also, not sure I follow what you mean about 'a documentation file'. Do you mean, you're not concerned if the wrong overview.html gets merged?

I added some comments to the build.sbt files on the dedup error driving the merge strategy.
It is an assumption that overview.html is documentation, and that due to the nature of how oEQ is using the Spring deps, it won't matter if the 'wrong' overview.html file is included.   Interested if that assumption holds water with you.
I've considered other merge strategies, such as renaming the duplicate file, and have considered if we are now specifying too many spring deps, and should specify less. Initial tests show that we are not specifying too many spring deps, but I'm not 100% sure yet.

Hmmm - there was a linting error that was fixed in develop.  After rebasing, it pulled in the other commits.  I'm thinking I just need to rebase the component branch directly on the openEQUELLA repo, so just the upgrade deps commits are showing up here.

I rebased the component branch from develop, and pushed it, but the other community commits are still showing up in this PR.  I'm thinking I may have messed up the branching rebases, and may just have to create a new PR with the needed commits to make it clean again.

Heya @cbeach47
Typically we:

always merge from develop to component/xyz
(if needed) merge from component/xyz into our feature/xyz if feature/xyz has been pushed. Otherwise, we rebase feature/xyz.

That should help you next time.

Recently, we decided to aim for Spring 5 instead of 3.  I'm going to close this PR, and take the lessons learned forward into Spring 5's upcoming PR against it's component branch.  If the Spring 5 effort proves to expose too much risk, I'll recreate this Spring 3 PR, just with better rebasing/merging management.


New device - Radar sensor zy-m100

I have been using this for a few months now and all seems to work correctly. I have postponed this pull request as my previous pull request  wasn't merged but rewritten to the SDK3 branch. Which removes my contribution from git history and basically erases the time I spent building it. I don't mind contributing but in this way it feels I don't get anything from it. Hope you understand. But feel free to do with the PR what you want, I wish everyone as much enjoyment of this sensor as I've had in the last months.

Hi @BertvanHoekelen, big thanks for this PR. Merged.
Sorry you feel you did not get credit for your last PR, I don't remember why I implemented it instead of merging it but I made sure to give you credit in the Readme file. I have nothing to gain from not crediting someone, if anything I am more than happy for any and all help I get and working PR's are awesome!
// Johan


Add phone mask to the tel TextInput

Related Issue or Background Info

Fixes #871

Changes Proposed

Add mask for all tel inputs

Screenshots / Demos

I don't think we want input masking while you're typing (the first screenshot) b/c of usability issues with input masking. When you click off that should be fine, but we may want to double-check.


NativeScript 6 + nativescript-bluetooth-v2.0.0-beta doesn't work

Recently I upgraded to NativeScript 6 - I came across the error :
JS: 'Error in Bluetooth.startScanning: TypeError: Cannot read property \'ContextCompat\' ofundefined'````
I found the apparent solution to upgrade to the nativescript-bluetooth beta via
npm i install nativescript-bluetooth@beta
My package.json file has been altered like so
"dependencies": { "nativescript-bluetooth": "^2.0.0-beta.23" }
However whenever I run tns run android I get the error
Cannot read property 'isBluetoothEnabled' of undefined
Any thoughts to why this might be happening?

Can you share your package.json

Sure!

{
"nativescript": {
"id": "org.nativescript.application",
"tns-ios": {
"version": "6.0.1"
},
"tns-android": {
"version": "6.0.0"
}
},
"dependencies": {
"install": "^0.13.0",
"nativescript-bluetooth": "^2.0.0-beta.23",
"nativescript-cardview": "^3.2.0",
"nativescript-vue": "^2.0.0",
"tns-core-modules": "6.0.1",
"vuex": "^3.0.1"
},
"devDependencies": {
"@babel/core": "^7.0.0",
"@babel/preset-env": "^7.0.0",
"babel-loader": "^8.0.2",
"babel-traverse": "6.26.0",
"babel-types": "6.26.0",
"babylon": "6.18.0",
"clean-webpack-plugin": "^0.1.19",
"copy-webpack-plugin": "^4.5.2",
"css-loader": "^1.0.0",
"lazy": "1.0.11",
"nativescript-dev-webpack": "1.0.1",
"nativescript-vue-template-compiler": "^2.0.0",
"nativescript-worker-loader": "~0.9.0",
"node-sass": "^4.9.2",
"sass-loader": "^7.1.0",
"terser-webpack-plugin": "^1.1.0",
"vue-loader": "^15.2.6",
"webpack": "^4.16.4",
"webpack-bundle-analyzer": "~2.13.1",
"webpack-cli": "^3.1.0"
}
}

@RyanH1234 what device are you running this on? What os version?

Samsung A5 running Android 8.0.0

@RyanH1234 Can you share the full log of the error? need to know where it happens in the code

The logs say "project successfully built", the elements are all rendered and then I run into this....

System.err: An uncaught Exception occurred on "main" thread.
System.err: Calling js method run failed
System.err: TypeError: Cannot read property 'isBluetoothEnabled' of undefined
System.err:
System.err: StackTrace:
System.err:     Frame: function:'', file:'file:///app\pages\Connection.vue:53:0
System.err:     Frame: function:'invoke', file:'file:///node_modules\tns-core-modules\timer\timer.js:52:47
System.err:     Frame: function:'run', file:'file:///node_modules\tns-core-modules\timer\timer.js:56:12
System.err:     at com.tns.Runtime.callJSMethodNative(Native Method)
System.err:     at com.tns.Runtime.dispatchCallJSMethodNative(Runtime.java:1242)
System.err:     at com.tns.Runtime.callJSMethodImpl(Runtime.java:1122)
System.err:     at com.tns.Runtime.callJSMethod(Runtime.java:1109)
System.err:     at com.tns.Runtime.callJSMethod(Runtime.java:1089)
System.err:     at com.tns.Runtime.callJSMethod(Runtime.java:1081)
System.err:     at com.tns.gen.java.lang.Runnable.run(Runnable.java:17)
System.err:     at android.os.Handler.handleCallback(Handler.java:789)
System.err:     at android.os.Handler.dispatchMessage(Handler.java:98)
System.err:     at android.os.Looper.loop(Looper.java:164)
System.err:     at android.app.ActivityThread.main(ActivityThread.java:6944)
System.err:     at java.lang.reflect.Method.invoke(Native Method)
System.err:     at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
System.err:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)

@RyanH1234  Do you know if that isBluetoothEnabled call is from your code or you don't ever call isBluetoothEnabled?
If you do call it, can you share the code? (i need to see the call and the creating of the object you are calling this on).

So I'm using nativescript-vue : I import the plugin like so

import bluetooth from "nativescript-bluetooth";

and call the following

bluetooth.isBluetoothEnabled().then(enabled => {
// logic
});

Within the mounted() function
The imported "bluetooth" is null - hence the error
I saw somewhere that importing plugins has changed in NativeScript 6 - that you need to use absolute paths, not sure what the absolute path would be?

import bluetooth from 'node_modules/nativescript-blueooth'

The above doesn't work either

@RyanH1234 That explains it!
do it like this for now. will fix the beta:
import { Bluetooth } from 'nativescript-bluetooth';
const bluetooth = new Bluetooth();
...
bluetooth.isBluetoothEnabled()

@farfromrefug It works! Thanks so much!

dear @farfromrefug, my device is not discovering any near by devices.. Following the same NS6+2.0.0-beta.23..

"dependencies": {
"install": "^0.13.0",
"nativescript-bluetooth": "^2.0.0-beta.23",
"nativescript-theme-core": "~1.0.6",
"nativescript-vue": "~2.4.0",
"tns-core-modules": "~6.0.0"
},
Only NativeScript App is not discovering, native bluetooth scan discovering, how come this??
What I am doing is, created fresh NS-Vue install using sidekick, installed npm i install nativescript-bluetooth@beta, then added following lines in app.js

import { Bluetooth } from 'nativescript-bluetooth';
global.bluetooth = new Bluetooth();

then, i run it on my real device (ASUS Zenfone Max M1 Pro - Android 9) using sidekick, enabled debugger.. Once installed on device, i tested methods like isBluetoothEnabled,hasCoarseLocationPermission etc etc, all working as per documentation, but startScanning->onDiscovered  not working..
Please help, I am in the last phase of  a project, without this I can't move a bit forward!!


Improve tiltrads main menu user experience

Yup, this has nothing to do with jukeboxes yet

Making the comments more sentence like really adds noise to the review. @jt-moriarty how do you feel about this one? I'll wait for your approval before merging

Sorry, I meant to make it a separate commit but forgot to do so

Un-doing multi-purpose branch


Leonardo Ui through Bower?

Will Leonardo ever be offered via bower?  We use bower for our front end modules and npm for backend.

@goldbergjeffrey There are no current plans to support Bower. As I understand you can use Github URL:s to install packages. Could this be an option? If so, what would we have to do to support it?

We can close this, I am using it through npm fine.


Fix resource corrupts caused by update indexRule operation

Fix

[ ] Add a unit test to verify that the fix works.
[ ] Explain briefly why the bug exists and how to fix it.

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes https://github.com/apache/skywalking/issues/.
[x] Update the CHANGES log.

Codecov Report

Merging #272 (c6f12c1) into main (e6d8953) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #272      +/-   ##
==========================================
- Coverage   46.51%   46.48%   -0.03%
==========================================
  Files          89       89
  Lines        9315     9321       +6
==========================================
  Hits         4333     4333
- Misses       4577     4582       +5
- Partials      405      406       +1

Impacted Files
Coverage Δ

banyand/metadata/schema/index.go
71.07% <0.00%> (-3.71%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


MEGAsync: Update to 4.0.2

When megasync's hash changes, one should check if its version number has changed... MEGAsync's sourcecode in github may change after its binary changes.

@r15ch13 The autoupdate server change version back to <IP_ADDRESS>... So let it be, or may we delete autoupdate and bump the version when download hash check failed?


FN on CEX funding - Fixed float

Opening this issue in order to flag this tx which was not flagged by the Cex funding bot. Address was funded by fixed float and then deployed the malicious smart contract.
The funding tx was run against the CEX bot locally and there were 0 findings. I am assuming here that something in the logic of the bot is not working properly.

Adding this one as well.
https://etherscan.io/tx/0xddc95468ee754d7ad062c353ff7ae2d0fecaae35b2dac0fe22b370b3fb49a078
which the cex funding bot did not alert

Fixedfloat bot created - to be deployed to beta alt

Deployed to prod.


High response times with istio 1.21.0-rc1 on ingress gateways

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
When upgrading istio using helm chart from version 1.21.0-rc.0 to 1.21.0-rc.1 our kubernetes cluster suddenly had large response times on the ingress gateway.

The above chart is practically a get request going to our homepage periodically every 30s.
A downgrade to 1.21.0-rc.0 brings back the normal behavior.
Version
Control-plane:  `1.21.0-rc.1`
Gateway: `1.21.0-rc.1`
Kubernetes: `1.29.1`
Istio-sidecars running as k8s native sidecars

Additional Information
We use the default gateway helm chart only with the additional podAnnotation:
proxy.istio.io/config: '{"gatewayTopology" : { "proxyProtocol": {} }}'

In the istiod helm chart we only have a difference compared to the default values that we use the distroless variant.
We do not have istio CNI installed.
Besides that I do not see any error messages or warnings in istiod or gateway, it is just very slow sometimes.
Let me know if and how I can provide additional information if needed.
Thanks in advance!

It looks like the issue resolved itself, I deployed the release 1.21.0 and it behaves okay now! Thanks nonetheless.


SPIFFS_write function does not work when SPIFFS_APPEND is specified

I'm on Mac OSX 10.11.1, and I'm using the spiffs framework with sming to program an ESP201
I ran into a problem where I was unable to write to a file (using SPIFFS_write) I had opened with the SPIFFS_APPEND flag called. I was getting the error SPIFFS_ERR_NOT_WRITABLE with the error code -10021. After some testing I discovered that the root of the problem seems to be this section of code,
if ((fd->flags & SPIFFS_WRONLY) == 0) {
  res = SPIFFS_ERR_NOT_WRITABLE;
  SPIFFS_API_CHECK_RES_UNLOCK(fs, res);
}

I believe this code dictates that SPIFFS_write will only work if opened when the flag is set to SPIFFS_WRONLY this becomes a problem when calling SPIFFS_write when a file is opened in SPIFFS_APPEND
If I change the bitwise operation in the if clause's condition to
(fd-> flags & (SPIFFS_WRONLY | SPIFFS_APPEND)) == 0
I am able to append to the file I opened, and my code behaves as it should.

Hmm.. The code looks correct to me (though I have not slept enough ;))
Did you open the file with only SPIFFS_APPEND? You probably want to open it with (SPIFFS_RDWR | SPIFFS_APPEND) or (SPIFFS_WRONLY | SPIFFS_APPEND). Specifying only SPIFFS_APPEND when opening the file would lead to a file that cannot be read nor written.

Ah I see. In the Sming repository code only SPIFFS_APPEND is used. It sounds like there was a miscommunication on how to set the flags, I'll discuss with them.

Yes, I tried opening a file on linux with only O_APPEND and only got a bad
filedesc in return.
But thanks for the heads up!
Den 17 nov 2015 5:50 PM skrev "Alex"<EMAIL_ADDRESS>
Ah I see. In the Sming repository code only SPIFFS_APPEND is used. It
sounds like there was a miscommunication on how to set the flags, I'll
discuss with them.
—
Reply to this email directly or view it on GitHub
https://github.com/pellepl/spiffs/issues/58#issuecomment-157428490.


feat: add owner path attribute

Closes https://github.com/ibm-telemetry/telemetry-internal/issues/201
Changelog
New

added analyzed.owner.path attribute to the collected project attributes

Changed

updated test snapshots
updated @ibm/telemetry-attributes-js to v4.0.1

Testing / reviewing
ran npm run test

@mattrosno yes i believe so! should be just like we've been testing with the endpoint


Create a preview view for markdown

An optional split screen preview for the markdown

Let's see how far we can get with inline content


Should http_if_terminated by false by default?

The http_if_terminated property on the API object is true by default, but maybe it should be false to reduce the surface of attack if a client maliciously decides to send X-Forwarded-Proto: https.

I believe this is already addressed in next via the trusted_ips property?

But should security settings be permissive by default, or restrictive by default?

As already discussed f2f:

for 0.10, it makes sense to set http_if_terminated to false by default since we trust any downstream client; a simple precautionary measure, which while still naive would still be preferable than the current default.
for 0.11, which has the trusted_ips property, which is less naive and restrictive by default. As such, it would also make sense to have a false default for http_if_terminated, in respect with this new "restrictive by default" policy as well.

Additionally, utils.check_https should also respect trusted_ips in 0.11, it doesn't seem to currently.

(My initial response was predicated on the assumption that assessment of upstream TLS respected the trusted_ips value)

@thefosk ^ these PRs handle this ticket, care to look? :)


loyalty enchantment villagerRoller.getMaxLevel() error

villagerRoller.getMaxLevel() returns 2 for the loyalty enchantment. should be 3

it is 3 for me

damn, ig it just made an error or something idk.
¯_(ツ)_/¯


[dist] Deploy fluss-dist package with start scripts and config files included

Purpose
Package start shell scripts and config files into the fluss-dist jar package, and deploy fluss-dist to maven central when releasing. This allows companies to directly use the source code of shell scripts and config files and package their own enterprise Fluss distribution by extracting the scripts and conf files from the fluss-dist jar.

Tests

API and Format

Documentation

@luoyuxia thanks, comments addressed.


Error on  training when used preprocess_shards

Due to large training dataset I had to use the preprocess_shards in order to split it. When running the train.lua i get the following error:
loading data...
/home/sergio/torch/install/bin/luajit: /home/sergio/torch/install/share/lua/5.1/hdf5/group.lua:312: HDF5Group:read() - no such child 'num_source_features' for [HDF5Group 33554432 /]
Seems like 'num_source_features'  is used in preprocess but not in shards.
Could you please advice? Thanks

Unfortunately, preprocesor-shards.py still lags behind in terms of features due to heavy code duplication with preprocess.lua. In the mean time, you can use the updated implementation from @mdasadul:
https://github.com/mdasadul/seq2seq-attn/blob/bcd899ec990da6b2c5c616aab5ac77b5c7760dc6/preprocess-shards.py
See #49.

Thanks!


[feature] check redis auth failed

You'll have to remove the redis config - it shouldn't be present by default.
Also, we use tabs for indentation, not spaces. Please read our styleguide. A changelog entry should be added as well.


[Task] HPO experiments of retrieval models with REES46 dataset for KDD tutorial

Description
Performing HPO experiments of REES46 datasets for retrieval models, for both finding best hparams for the KDD tutorial and for with results from other datasets (e.g. H&M, LastFM, AliCCP)

Marc's idea: Try attention to weight different features


Deduplicate Email Addresses

Currently, we can add a seller with the same email address but a DIFFERENT phone number as an existing buyer. This should not make sense since a client's email should be unique to him.
This issue fixes this issue by ensuring that the email field specified in addbuyer and addseller are "deduplicated" following this logic:
for addbuyer
No duplicate emails are allowed. Duplicate emails are detected if
1. there is a buyer with the same email already in the client book.
2. there is a seller with the same email but a different phone number in the client book. Having the same email address as an existing seller with a different phone number is not allowed as emails should be unique to a client.

catching a duplicate email in addbuyer because there is a seller (client number 5) with a different phone number but the same email

for addseller
**Duplicate Emails**: No duplicate emails are allowed, following the same logic as the `addbuyer` command:
1. A seller cannot share the same email as another seller.
2. A seller cannot have the same email as a buyer with a different phone number. Email uniqueness is enforced per client.

catching a duplicate email in addseller because there is a buyer (client number 6) with a different phone number but the same email

Good catch! I think the proposed fix makes sense!


Replace deprecated usage of pkg_resources with importlib.resources

Fixes #66.

pkg_resources no longer exists in GitHub Actions's Ubuntu 22.04 containers with Python 3.12.
https://github.com/wpilibsuite/styleguide/actions/runs/6461655009/job/17541789753?pr=263

Thanks @calcmogul for the PR. Testing the change now: https://github.com/ssciwr/clang-tidy-wheel/actions/runs/7485613763

Looks like the new importlib API was added in Python 3.9.


Touched is not effected to react-final-form

Environment

Tech
Version

material-ui-pickers
1.0.0-rc.9

material-ui
1.0.0

React
16.4.0

Browser
Chrome

Platform
Sandbox

Steps to reproduce

Tab over the a required date picker
meta.touched did not become true.

Expected behavior
meta.touched should become true when user visited and exited a required date picker.
So a validation message can be shown immediately when user skips a required date picker.
Actual behavior
meta.touched stays as false even when the user visited and exited a required date picker.
Live example
https://codesandbox.io/s/0y12x6j19l
For reference, I added a custom dropdown component that uses material-ui + react-final-form. The active, touched, visited are effected to react-final-form's meta object.

Here's the material-ui-pickers' DateTimePicker that uses material-ui + react-final-form. The active, touched, visited are not effected to react-final-form's meta object.

Hi,
Is there particular issue with material-ui-pickers itself (without other libraries)?
Please try to reproduce issue without any 3rd-party libraries.

Closing the issue, no problem with material-ui-pickers. Just need to add onBlur from react-final-form's Field tomaterial-ui-pickers's onBlur to effect true to meta.touched.


[FancyZones] Reorder taskbar icons to reflect relative zone assignment

I'd like to see an option to where taskbar icons would automatically reorder based on the zone a program was placed in. For example, if I use a FancyZone layout divided into four quadrants and place a program into zone 1 (upper-left quadrant), the taskbar icon for that program should end up in the first position after the start menu.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

i don't think there are public APIs to adjust taskbar icon placements.
What is the use case for this.  Doing this would help solve what problem?

what happens if something isn't in Zone 1?