add DNSSEC-Support to DNSMASQ

As dnsmasq provides more possibilities within the dns-server as unbound, please also add dnssec-support to it.

@ruggerio thanks! do you have a reference to a setup document or the relevant config knobs in Dnsmasq?

Hi,
Man-Page From thekelleys.org:
http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
The gentoo-site explains it easy (as i hope):
https://wiki.gentoo.org/wiki/Dnsmasq (see the DNSSEC-section)

@ruggerio very helpful, thanks! :)

just ping if you need Support :)

@ruggerio sorry for the delay, it will be in the upcoming development version of 18.7.9


SORT_ORDER set to name not working

Directory Lister Version
3.8.3
PHP Version
7.4.23

Internally Directory Lister uses strcmp() which sorts things "perfectly" alphabetical (e.g. file1.txt, file10.txt, file2.txt) by default. Try natural to sort strings  with the natural sort order algorithm instead (e.g. file1.txt, file2.txt, file10.txt).


create profile validator module to validate json profile files against schema (E:35)

Feature Request
Description of Problem:
DataHelix generator should validate json profile files against the DataHelix Profile Schema
use one if the following libraries for validation to allow us to use draft-7 of the JSON schema:

[ ] everit-org/json-schema
[ ] leadpony/justify

Acceptance Criteria:

[ ] Code changes made to validate the input profile against the schema
[ ] Documentation for the validator updated to show the use of the schema
[ ] Error messages describe clearly the error/mistake in the profile
[ ] JSON schema is bundled with release JAR (for now) so no need for internet access when running the generator

Would be nice if this could be a separate library/submodule, so aid it's use in future enhancements (like an editor/gui)
also, if it is a library then a customer could take it and call it from their own software

the kotlin based Medeia validator was chosen as it gave the most accurate results and is easy to implement.


[Routable] clarify error messages change/pop/push

I had to look twice to know why the "... change ..." error was raised while the changeRouteSegment method was defined. I hope this clarifies the error.

Nice fix. Thank you!


Copy cat CPM's as CAM's

Add the CPM's support to the copycat (called "its-client" for now) binary

Using the reworked copycat example from 2.0.0 CPM from vehicles should be working fine
CPM from road side unit does not work yet because the example only process messages on which as_mobile() returns Ok


Add export options --export-if-newer, --resume

Add ability to resume a cancelled/failed export and option to only export files if newer than destination (e.g. update an export)

checkpoint settings in .osxphotos?

also add --update-metadata that would only update metadata if changed? If user used --exiftool, check to see if metadata changed and if so update with exiftool, for --sidecar, rewrite all the sidecars

this could be useful to avoid the re-copy of the files if already in the destination! for an "incremental" scenario for big archives is great!

Thinking of an interface like this:
osxphotos export --update --exiftool /path/to/export
If --update, check to see if photo exists and if so, is the one in Photos newer. If newer, export it.
If --exiftool or --sidecar, would also check to see if any metadata changed and if so, write new metadata

I think that in this way is totally modular, like the rest of the options! If added --exiftool or --sidecar, if a file already exist the procedure will check only the metadata, and if different update it, not re-copy the entire file, right?

@NiccoStar86 yes, intent with update would be to not re-copy the entire file.  However, to update exifdata embedded in the file it must be re-written using exiftool.  It would still be faster because the current export does 2 copies -- one to get file out of the library then a second to apply metadata.  This same interface could be used to stop and re-start an export.  For example, if you needed to cancel out of a long-running export, you could use --update to re-start where you left off.

@RhetTbull Perfect explanation! The new option --update will make osxphotos even better. Waiting to test it :)

Thanks for the pointer @RhetTbull. Is there a technical / architectural design gating this e.g. re figuring out how to efficiently cache do the metadata comparison? And I assume there is no way to dereference the photo directly within the library and skip that first copy step you describe in https://github.com/RhetTbull/osxphotos/issues/100#issuecomment-623127493

@felciano no particular technical issues, just time to implement.  I've actually started working on the design.   I'll likely add this as an option to PhotoInfo.export().  Comparing the files is straightforward -- filecmp.cmp is probably sufficient.  However, if the user applied metadata with the --exiftool option, the files won't be the same so I'll then need to read the exif data from the destination file and compare it to the exif data in the Photos library, again not difficult, just need to think through the implementation.  For example, using the --keyword-template option, the user can apply additional keywords such as album, person in image, etc. to the destination file's exif data.  I'll need to compute the keywords that would have been written and ensure they're identical to the keywords in the destination file.
Regarding your question about the first copy step, I don't think there's any easy way given current design to do this.  Exporting a photo with --exiftool option looks like this now:

Copy file out of Photos to destination path using ditto command which preserves extended attributes and other metadata about the file.
Use exiftool to modify the exif data.
exiftool creates a temporary copy, rewrites the data with the new exif header, then removes the original copy and renames the file to the original name

I don't think exiftool has an option to specify the destination file which I think is what you're referring to thus the initial copy still needs to be done.
There is a new option to use hardlinks when exporting which avoids the initial copy.  However, if this is used with --exiftool, exiftool still creates the duplicate file which breaks the hardlink (this is a bug in implementation I need to work through).

I also don't know if exiftool preserves all the metadata (extended attributes, resource fork) associated with the file when rewriting.  Need to check this (I bet it does not preserve the data).  If not, I could use osxmetadata to rewrite the extended attributes but the resource fork would be lost.

I have this mostly implemented but have run into an issue that will take some engineering to resolve.  It is possible for a file in Photos to have the same original name as another file (this is quite common, e.g. two files named IMG_0001.JPG).  If these happen to be in the same export directory, osxphotos will normally detect a collision and increment the second file: e.g. it will be exported as IMG_0001 (1).JPG, IMG_0001 (2).JPG, and so on.  However, with --update, osxphotos has no way of associating the exported image with the original image in the case where more than one image of the same name is in the same directory.
To fix this, osxphotos will have to associate some sort of metadata with each exported image to map it back to the original file in the Photos library.  In Photos 5, Photos writes an extended attribute com.apple.assetsd.UUID to the original file which is preserved in the export and could be used to map back but this does not apply to the raw photo and doesn't work on earlier versions.  One option is to create a file in each export directory, for example .osxphotos that preserves some state information about the export, e.g. the original UUID mapped to the exported file name.  Another option is write custom metadata via an extended attribute (e.g. com.osxphotos.uuid to do the mapping.
The extended attribute is probably the most elegant and transparent but would be more difficult to implement because of the extra steps involved with checking every file increment.  Using a dot-file, I could simply write out a serialized json dictionary mapping {uuid: exported_filename}.

The option to create a ".osxphotos" file inside each directory would be great, but how do you manage the case of two photos with the same filename? Adding a progressive counter IMG_0001 (1).JPG, IMG_0001 (2).JPG, and so on? If this is easy to implement should work well.
Another fastest solution could be that when the option --update is used, osxphotos force the filename of the files exported to "photos_uuid.exstension" to have the uniqueness assured. Not very elegant but works :)

Il giorno 16 mag 2020, alle ore 19:25, Rhet Turnbull<EMAIL_ADDRESS>ha scritto:
I have this mostly implemented but have run into an issue that will take some engineering to resolve. It is possible for a file in Photos to have the same original name as another file (this is quite common, e.g. two files named IMG_0001.JPG). If these happen to be in the same export directory, osxphotos will normally detect a collision and increment the second file: e.g. it will be exported as IMG_0001 (1).JPG, IMG_0001 (2).JPG, and so on. However, with --update, osxphotos has no way of associating the exported image with the original image in the case where more than one image of the same name is in the same directory.
To fix this, osxphotos will have to associate some sort of metadata with each exported image to map it back to the original file in the Photos library. In Photos 5, Photos writes an extended attribute com.apple.assetsd.UUID to the original file which is preserved in the export and could be used to map back but this does not apply to the raw photo and doesn't work on earlier versions. One option is to create a file in each export directory, for example .osxphotos that preserves some state information about the export, e.g. the original UUID mapped to the exported file name. Another option is write custom metadata via an extended attribute (e.g. com.osxphotos.uuid to do the mapping.
The extended attribute is probably the most elegant and transparent but would be more difficult to implement because of the extra steps involved with checking every file increment. Using a dot-file, I could simply write out a serialized json dictionary mapping {uuid: exported_filename}.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/RhetTbull/osxphotos/issues/100#issuecomment-629679805, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3T4ZFKD2NENDSLWWVGBKLRR3EAVANCNFSM4MGZKIXA.

@NiccoStar86 because I know the UUID of the photo prior to export, it would be possible to create a dictionary that maps from UUID to filename, for example:
{"UUID1": "filename.jpg",
 "UUID2": "filename (1).jpg"
}

Your idea to add uuid to the filename would work but I want the user to be able to have control over the destination filename -- for example, I intend to extend the templating system currently used for --directory to allow user to specify output file with a template.  Also, I want --update to work even if user didn't specify --update in initial export.  For example:
osxphotos export ~/path/to/export
then later
osxphotos export ~/path/to/export --update
would only update new files
In the first case, if a collision is detected, osxphotos automatically increments the filename and so the second case will need a way to know this when doing the update.
I'll experiment with a couple different ways of storing the mapping from UUID to filename and hopefully get this implemented soon.  The rest of the --update code appears to be working.

@RhetTbull as usual, very clear explanation! Yes, my idea was quite "crude" ;) but I understand the clear vision of the project and the endless possibilities of "customization" that you want to give to everyone. Thank you

I have --update working for photos, now working on updating metadata (--exiftool, --sidecar).  I settled on writing the UUID of the photo to a custom extended attribute com.osxphotos.uuid upon export so osxphotos can map the exported image back to original.  This should work on all Mac filesystems and be completely transparent to the user with no need for additional files to store state.

How would this work for files on e.g. a NAS? Would using the rsync -X option preserve this new attribute?

Good question, which interests me too @felciano ... My destination is a folder on a Synology mounted via SMB on my iMac, and during the previous test I used the option --no-extended-attributes because without I have received an error during the export!

Good question.  If the NAS supports extended attributes, this should work fine.  If not, then --update as currently implemented wouldn't work.
@felciano rsync -E will preserve extended attributes and I just confirmed it does preserve the custom xattr.  If this is a big issue, I'll come up with another solution for --update.  I implemented this in a way that it's not difficult to re-engineer a new solution.  The code requires 2 methods: get_uuid_for_file and  set_uuid_for_file.  Those could be refactored to use a serialized dictionary or even a sqlite database to store the data.
@NiccoStar86 take a look at this article; another osxphotos user found it helpful for configuring SMB so he didn't need to use --no-extended-attributes

I've rewritten the UUID check for --update to use a sqlite file which will be created in the export destination.  Currently it's called /path/to/export/.osxphotos_export.db.  Though I like the elegance of the extended attributes solution, it may cause problems for those exporting to NAS volumes.  Having a full database associated with the export will provide a means to add other functionality in the future, e.g. perhaps to remember to all the options the original export was called with and re-use those automatically.
For example, you could do:
osxphotos export /path/to/export --directory "{created.year}/{created.month}" --keyword-template "{person}" --keyword-template "{label}" --exiftool
then later, simply
osxphotos export --update /path/to/export
and all the settings would be read from the database

@RhetTbull love the idea. How would it work for directory trees? For example, if the intent is to create a fairly common YYYY/MM/DD tree structure for the files, would there be an .osxphotos_export_db at each level or just the root? And would it contain metadata just for the photo files immediately within that directory, or for those within subdirectories as well?

@felciano for simplicity and performance I think a single database at the top level of the export is best so we don't have to have possibly hundreds of file handles open.  My plan is to store the relative path to the files from the top level export.  So if export structure looks like this:
/path/to/export/2020/05/16/IMG_002.JPG
/path/to/export/2020/05/15/IMG_001.JPG
...and so on

the database would be:
/path/to/export/.osxphotos_export.db
and each file, uuid pair would be stored as:
2020/05/16/IMG_002.JPG: UUID
2020/05/15/IMG_001.JPG: UUID
That way, if you moved the entire export tree, everything would still work transparently to the user.

Got it. And would the .osxphotos_export_db contain just the UID-to-filename mappings, or would it contain additional metadata information such as faces etc?

Right now I only plan to store the UUID to filename mapping and in the future, possibly the options that osxphotos was called with.  I'm not sure what the utility of storing the other metadata would be as it wouldn't be easily accessible to the user.  Do you have a use case in mind?  If the user wants to preserve the metadata, I recommend either doing this in the EXIF headers using --exiftool or in a JSON or XMP sidecar file using the --sidecar option.

@RhetTbull great idea to use a sqlite, and expandable for the future ;) ... Now I'll read and test the link suggested, thank you!

Do you have a use case in mind?

A few use cases to think through based on my experience with similar approaches elsewhere. I hesitate to call these "use cases" -- they are more "edge cases" to think through because someone will do them, so should have clarified system behavior as such:

If I do osxphotos export /path/to/export etc at one point, and then at another point someone (maybe me) does osxphotos export /path/to/export/subdirectory .... This would likely result in 2 SQLite files at different levels of the hierarchy with different metadata caches. A simple solution is to forbid this: walk up the tree and fail the command if you find another .osxphotos_export.db upstream. A more elegant (but harder) solution might be to make sure both databases are in sync somehow, but I'm not sure it is worth the effort.

Similarly, perhaps refuse to accept a given destination root path if that path already exists and has a metadata database in one of its subdirectories. That would indicate that you are syncing to the parent of a previously existing destination, and you'd need to clarify which database has precedence (and whether your overwrite/delete the existing one).

Similarly, someone will at some point copy just one subdirectory (e.g. the 2020/05 directory in your example) to a new location, and thus disconnect it from the metadata stored at the root. If the only information lost are the UUIDs and the only consequence is no longer being able to efficiently do a diff then that sounds like a reasonable tradeoff provided it is documented. If more information/capabilities are lost for a user that does such a copy, then the design might be worth revisiting, but it doesn't sound like that is the case.

Again, I don't think these are true use cases, but probably worth clarifying the behavior for users in the docs.

Thanks @felciano -- all good edge cases.  I'll consider adding an issue to perform the check for existing database file and warn user if one is found.  However, in all these cases the worst thing that happens is the user re-exports a bunch of photos, possibly in the wrong location which isn't critical but in all cases, does add complexity to the code.  Another similar case is the user runs an update in the same directory but with different options, or example, --directory "{created.year}/{created.month}" the first time then --directory "{album}" the second time.  This might be intentional but might not so I plan to eventually store the arguments that osxphotos was called with in the database to be able to warn the user if they are updating with different options.   Of course, that has all sorts of edge cases too, for example, the user might have exported without metadata the first time then wants to update but add metadata via --exiftool.  In this case the "correct" behavior is to not re-export the photo but to apply the metadata in-situ.
In the same vein of helping the user do the right thing, would you prefer the database file be hidden (e.g. .osxphotos_export.db) or not (e.g. osxphotos_export.db).  My expectation is the person who's running a python app from the terminal is savy enough to understand about dot files (and the cognizant of the fact these won't show in the Finder) but perhaps that's expecting too much?

@RhetTbull I vote for the "hidden" database, if only to avoid the mistake of deleting it ... Then in the documentation you can explain in detail what is saved in the database and where it is, but I would avoid leaving it easily "accessible" via Finder

My expectation is the person who's running a python app from the terminal is savy enough to understand about dot files (and the cognizant of the fact these won't show in the Finder) but perhaps that's expecting too much?

This seems like a reasonable explanation. Probably also willing to RTFM so as long as the edge case behavior is documented I suspect you'll be fine.

This is getting closer.  I've added checks to try to find matching files in the destination if there is no DB that way if user ran --update against a library previously exported with older version of osxphotos or if the DB file got deleted, the update still works without having to re-export everything (and builds the DB in the process).  Now working on the metadata update.

Working on the metadata cache to compare metadata.  Instead of reading metadata directly from each file to compare, which will be slow, I've experimenting with caching a JSON representation of everything known about the photo in the export database.  This adds about 2kB per photo exported which seems reasonable.  Access will be much quicker than reading EXIF data directly from each file.

This is going to be more complex than I thought.  If user uses --exiftool, the destination file will always be different than the source file due to being re-written by exiftool and so the file comparison will fail and the file will get updated every time --update is run.  In addition to comparing the cached metadata, I'll also have to cache and compare a hash of the file before and after it's been written to by exiftool and use those for comparison.

I think this is done in version 0.29.0!  It took significant re-factoring to make this work but I believe it's working now and all tests passing for expected edge cases.   Thanks much @felciano and @NiccoStar86 for the feedback during the development process.  Let me know if you encounter any issues.

Thank you to you @RhetTbull for this great job! I'll test the new version asap and I'll update you!

Dear @RhetTbull I tested the --update option and works very well! But during the execution I receive some "WARNING" that I believe related to the export of some files. Even if I use the --verbose option in the log I don't find any errors. Is there any test that I can do to try to find out more precisely, what generates these errors? Thank you!

@NiccoStar86 thanks -- the .tiff warnings can be ignored -- I'll add a fix for those so you don't get the warning.  Has to do with sometimes Photos saves as .tiff and sometimes as .tif.  This also happens with .jpg and .jpeg.  However, the warning on the JPG being saved as PNG indicates a bug.  I'll add some debug code and push a new version if you don't mind trying it.

Absolutely @RhetTbull, I will gladly a try as soon as the new version is available.


Collision detect between ifc elements

Description 📝
I'm looking for a tool to detect all the collisions present on the model like on Bim Collab.
Model without filter:

Model with filter:

Suggested solution 💡
Actually i use Mesh.geometry.boundsTree.intersectsGeometry to check if a object is colliding with another, but only works comparing the meshes 1 by 1
const elementBase = parseInt(ifcItem.id);
const sub1 = getSubsetDataFromId(elementBase);
sub1.geometry.computeBoundsTree();

const sub2 = getSubsetDataFromIds(elementosIds);
const sub2Geometry = mesh2.geometry;
sub2Geometry.computeBoundsTree();

const transformMatrix = new Matrix4().copy(mesh1.matrixWorld).invert().multiply(mesh2.matrixWorld);
const hit = mesh1.geometry.boundsTree.intersectsGeometry(mesh2Geometry, transformMatrix);

Alternative ⛕
No response
Additional context ☝
No response
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.

Hey, you should check this out with Garret, as he is the author of the BVH library. We are not planning to implement clash detection features in our library for now (although you can do it yourself using Garret's and Three's APIs), so this issue is out of our scope. Cheers!


[RHEL 9.4] disable dracut for ostree based systems on rpm installation (RHEL-63058)

Backport of #895 to RHEL 9.4 for https://issues.redhat.com/browse/RHEL-63058.

Testing changes still need a bit of work.  Gotta trim the dependencies (btrfs etc), add compile flags to make them unneeded, and remove the aws-cli stuff in the gitlab pipelines.  It's ok to ignore build result caching for this branch.

All green now!


please consider adding "alkenyl benzene(s)"

We have a data set with "alkenyl benzene" (benzene ring with an attached alkenyl group, e.g. CHEBI:51324 or CHEBI:4917) as term and like to use a ChEBI identifier. We note similar items, like vinyl arene and alkylbenzene.

An entry for alkenylbenzene (CHEBI:195237) has now been created


Host the new bot.

Target Discord Servers for bot are:
SD League -- mbetts has elo data, ScoutSpirit is point server admin.
SD2 Bootcamp -- mbetts has elo data, Rooster is point server admin.

Bot "Bleeding Edge" hosted @ https://discord.com/channels/813599951761178655/813601611905630218/826254606459469875

Hosted on Azure, in production


A word of appreciation

I rarely see projects that tackle such a complex problem maintaining the kind of quality you did. The idiomatic Go code itself, the comments, the documentation. A lot of respect.

Thank you very much @rollulus! I hope this repo continues to be useful for quite a while (and that I iron out all bugs eventually). Thanks again for the appreciation :)


Add the Azure Boards badge to the README

Add the Azure Boards badge for the board used to track the work for this repository. Fixes AB#413. See the status badge configuration documentation for more information.

@armanrahman22 should we close this one or abandon?


docs(docs): :memo: just test deploy

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


feat(#947): Disable XMIR Verification by Default

In this PR I disable XMIR verification by default for both goals disassemble/assemble.
Now, in order to enable it we need to use the following config:
<configuration>
  <xmirVerification>true</xmirVerification>
</configuration>

btw, the xmir verification is still active for the most of the integration tests. The only test, where it's disabled, is spring-fat.
We did it intentionally, because XMIR verification takes unreasonable amount of time. You can read more about this problem here:
https://github.com/objectionary/lints/issues/133
Closes: #947.

@yegor256 Could you review these changes, please?

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here.

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 14min).


Add functionality to work with new tracker using pages.py

This PR replace old functions with pages.py in an attempt to fix all current commands, so far I only tested the load command and it works.
Changes to config.toml to make this work:

assignment is split into category-task and category-description

To install this version without waiting to the PR being merged:
pip install git+https://github.com/miguel550/timetracker.git@feat/new-timetracker

To uninstall:
pip uninstall timetracker-cli

@miguel550 is this PR ready to merge?

@fboaventura I would test all the existing functionality first to make sure it's ok to merge, I can test all the remaining functionality tomorrow and then let you know

Hi @fboaventura, I updated the readme and fixed the show command table not showing the new table schema. I also tested the load-csv command and it works. The PR is ready for review and for merge.


Navigator, view mounted but not rendered

Hi,
I come across a very weird bug: I use Navigator to push a child view, and see log shows the view is rendered but simulator doesn't. Before, I meet this situation too, and finally find some minor errors in the child view file. I am wondering if there is some tool to find out the bug more quickly?
Thanks.

Could you provide an example of your code and the bug that you are receiving?

@iceNuts - closing this because we haven't heard a followup, feel free to ping me if you're still having this issue, and if you can please post a runnable example repository or app on rnplay.org, thanks!


feat: Add-blockscout_params

fix #837
the default blockscout image version does not work on my machine.
so i added the blockscout_params for blockscout service.  now user can customize the image versions they want to use.
it contains two params:
blockscout_params:
  # blockscout docker image to use
  # Defaults to the latest image
  image: "blockscout/blockscout:latest"
  # blockscout smart contract verifier image to use
  # Defaults to ghcr.io/blockscout/smart-contract-verifier:v1.9.0
  verif_image: "ghcr.io/blockscout/smart-contract-verifier:v1.9.0"

i already tested it on my machine and it worke well.

The newest version of blockscout also has a frontend image.
Also currently their latest image is incompatible with kurtosis.

The newest version of blockscout also has a frontend image. Also currently their latest image is incompatible with kurtosis.

updated to "blockscout/blockscout:6.8.0"

could you please run a linter?
kurtosis lint --format


Using the library

Hello! This library has the potential of being very useful, nicely done!
I am trying to use it but I am stuck. I have XBRL reports in .zip format in an 'archive' folder, but can you provide a bit more details on exactly how we can use the library to export the results? I tried to run it but it seems that it always finds 0 files, even if I place the files in an archives folder.

Thank you for your feedback!
I updated the readme with some additional information. In case it still doesn't work, can you please provide me with a link to the file you're trying to parse (if it's in the public domain)?


[BUG] relative links on the index page don't always work

Description

When accessing the docs' index directly (as /user-guide/install.html), relative links no longer work correctly (i.e. the links to Home Manager Usage and Standalone Usage).
Minimal, Reproducible Example (MRE)

Visit https://nix-community.github.io/nixvim
Click a relative link
Everything works
Open ☰ (ToC sidebar)
Click "Installation"
Repeat step 2 (click relative link)
This time the link is broken (points to e.g. /user-guide/modules/hm.html, note the extra /user-guide prefix)

I guess we could work around this issue by having a separate index page that isn't install.html?

We may be able to leverage mdbook's special handling of README files?

Links to README.md will be converted to index.html. This is done since some services like GitHub render README files automatically, but web servers typically expect the root file to be called index.html.
https://rust-lang.github.io/mdBook/format/markdown.html#links


Most slots missing in tf/2017/gloss.tf

I noticed the 2017 version of gloss.tf seems to be missing most glosses. Is there a reason for this?
~/github/etcbc/bhsa$ wc -l tf/4b/gloss.tf tf/2017/gloss.tf
 435818 tf/4b/gloss.tf
   9245 tf/2017/gloss.tf

Hi Rúbio,
yes, at some point we decided that is was redundant to have the glosses on all word nodes, since they are a lexeme property. So in 2017 only lexeme nodes carry the gloss feature.
Then we discovered that in some situations it is very convenient to have the gloss nodes on all occurrences, so in version c we added them back. I hope there will be a brand new data version 2021 soon, and then we will put them back also there.
In the meanwhile, could you explain how the lack of gloss on word nodes is problematic for you? Maybe I can help with a workaround!

Thank you for the prompt answer! The problem is that the gloss.tf file for version 2017 only has 9245 lines, while the old 4b version has 435818. I guess this may be unintentional.
On a side note it's great to know there's a new version coming soon. Thank you for all the hard work!

I see oslot.tf does the linking between words and lexemes, but it is possible to do that out of the big table?

It should, but it was very unthoughtful of me to not to include the column that you need for this, namely a column that gives the lexeme node for every word.
However, it turned out extremely easy to add that column, which I did.
You can recreate the table by means of this notebook: https://nbviewer.jupyter.org/github/ETCBC/bhsa/blob/master/programs/bigTables.ipynb
And then (for Pandas), this one https://nbviewer.jupyter.org/github/ETCBC/bhsa/blob/master/programs/bigTablesP.ipynb
and for R this one https://nbviewer.jupyter.org/github/ETCBC/bhsa/blob/master/programs/bigTablesR.ipynb
(if you need them).
Make sure you have the latest version (git pull https://github.com/ETCBC/bhsa) and the latest version of Text-Fabric (pip3 install text-fabric).
I just generated the big table without issue.
Just curious, do you work in Pandas or R or with other ways to deal with the big table?

Thank you, this solves my problem beautifully.

Just curious, do you work in Pandas or R or with other ways to deal with the big table?

I'm running the big table through a Perl script, but that's because I'm more comfortable with Perl.


What is the outgoing flag for GET /ob/chatconversations

When doing GET /ob/chatconversations I was surprised to see the outgoing flag. What does it mean? Aren't conversations both ways (outgoing and ingoing)?
GET /ob/chatconversations?
null [ { peerId: 'Qmc7M36cnHr7LiqNXdxqgsEdCArhU2dTetYKK64NrNmRfo',
    unread: 0,
    lastMessage: '',
    timestamp: '1970-01-01T01:00:00+01:00',
    outgoing: false } ]

Outgoing is your own messages.

Are we talking about messages or conversations? I thought chatconversations was about conversations.

That API returns the last message in each conversation. The outgoing flag tells you who sent the message, you or the other guy.

Ok, cool. I don't really understand why the outgoing flag is there but not things like the message ID, but I'm probably not really understanding the use case properly.


Can the data be split into trajectories?

I  am currently attempting to divide the data into trajectories for my replication of decision transformer is there any way i can do this?
Thanks a lot

I think you can use the 'terminal' dimension to split

@GilgameshD is right. Please split trajectories based on terminal flags.


Feature suggest: Mask secrets in apply stdout

Currently, if we run tk apply somewhere in CI, job logs will contain all secret value that was added in this apply.
I think we can mask these values in stdout

This would be great, but if I understand it correctly the best place to put this masking is in kubectl diff, which tanka calls to produce diffs: https://github.com/kubernetes/kubernetes/issues/87840.
My team has very recently started parsing the output of tanka diff, apply, and parse, redacting diff hunks that correspond to k8s Secret objects: https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/tanka-deployments/-/blob/master/suppress-secrets/main.go
I've opened a tanka PR to separate diff and non-diff output onto stdout and stderr, assisting piping into a tool that parses diffs: https://github.com/grafana/tanka/pull/537.

#537 was merged (release coming soon), which should help to resolve this in a custom setup.
@craigfurman Tanka generally just passes along the output from kubectl. Another option would be to use KUBECTL_EXTERNAL_DIFF and obfuscate secrets through that.
I'm going to close this as I think this is not a problem Tanka should solve.

This was addressed in upstream kubectl: https://github.com/kubernetes/kubernetes/pull/96084.


Automatically discard task result objects once received by the client

Currently, results data is kept by the scheduler until the client it's associated disconnects.
Ideally, we could discard the task result once received by the client:
In [1]: import math

In [2]: from scaler import Client

In [3]: client = Client("tcp://<IP_ADDRESS>:60338")

# ScalerTop shows 1 scheduler object (the serializer)

In [4]: future = client.submit(math.cos, 0)

# ScalerTop shows 4 scheduler objects (the serializer, the function, the function argument and the return value).

In [5]: future.result()
Out[5]: 1.0

# ScalerTop still shows 4 objects, while the scheduler could clear the task's result data as it reached the client's future.

In [6]: client.disconnect()

# ScalerTop shows 0 scheduler object

Note that the client cannot send a delete request when receiving an result object, as this result object might be required by another dependent graph task.


Game broken

When attempting to access this at https://githubschool.github.io/github-games-harrisdwork/, I am getting a 404. This could be caused by a couple things:

GitHub pages needs to be enabled on master. You can fix this in the repository settings.
the index.html file is incorrectly named inde.html. We will fix this together in class.

Can you please fix the first bullet @harrisdwork?

@githubteacher first bullet is complete.

Still unable to load game.  Re-opening this issue.


Updating docker image name in RCs

This p/r is to update the docker image names in Replication Controllers.

Merged. Thanks!


Adding a first version

Subjets added:
Planning
Requirements
Desing pattterns
UML diagram(tried)

PR of lab 1


JSON Serialization issues

I'm having a little trouble with JSON serialization. It was working when i initially set my project up, but now - after updating to newer versions - it seems to have changed somewhere along the way. Specifically I see two issues:

The /env endpoint complains that No formatter has been registered. See App.Metrics.Formatters.Ascii for example. Looking through the source, it looks like the call to AddJsonSerialization() has been changed to be a wrapper around several subroutines; and when calling it without passing in a JsonSerializerSettings object, it looks like it doesn't call AddJsonEnvironmentInfoSerialization(...). Is that functionality supposed to be missing?

The /metrics and /metrics-text endpoints appear to be returning the same data - a large JSON blob - whereas before, the /metrics-text endpoint was more human-readable. Is there some new configuration setting I need to include to get that back to working the way it was before?

@TaffarelJr

Yeah that's a bug, for now just call AddJsonEnvironmentInfoSerialization as well - https://github.com/alhardy/AppMetrics/blob/dev/src/App.Metrics.Formatters.Json/MetricsHostExtensions.cs#L25

If you're just calling AddJsonSerialization, yes both /metrics and /metrics-text will use the same formatter, try using AddAsciiMetricsTextSerialization for the more human-readable version of the metrics data. http://app-metrics.io/web-application-monitoring/formatters/ascii-formatter.html

Thanks, that's what I needed. I'll just take the approach of adding specific formatters per endpoint instead of relying on the catch-all.

2.0 updates on this here https://www.app-metrics.io/web-monitoring/aspnet-core/endpoint-middleware/


Add devworkspace condition for failed startup

What does this PR do?
Add a condition that can be used to communicate to the user reasons why a devworkspace cannot start (if e.g. a plugin cannot be found, the controller is misconfigured, etc.)
What issues does this PR fix or reference?
Required for https://github.com/eclipse/che/issues/17326
Is your PR tested? Consider putting some instruction how to test your changes
With changes, a failed workspace can be investigated, e.g.:
❯ kc get devworkspace cloud-shell -o yaml | yq -Y '.status'
conditions:
  - lastTransitionTime: "2020-07-18T01:02:10Z"
    message: Devworkspace was created without creator ID label. It must be recreated
      to resolve the issue
    status: "True"
    type: FailedStart
phase: Failed
workspaceId: workspace818ff97fbf7741fb

Docs PR
Unsure if docs are required for this, will provide if needed.

I'm also wondering if specific conditionType constants should be in this repo at all -- there's no hard-and-fast rule about where they're defined (you can basically supply any string) and so implementations of controllers may want to use their own instead of the ones included here.
cc: @davidfestal WDYT?

I'm also wondering if specific conditionType constants should be in this repo at all -- there's no hard-and-fast rule about where they're defined (you can basically supply any string) and so implementations of controllers may want to use their own instead of the ones included here.
cc: @davidfestal WDYT?

Conditions are especially useful when using kubectl wait, for example in:
kubectl wait workspace java-mysql --for=condition=Ready

So I'm not against providing some flexibility for implementors to add condition types, but I'd probably be against any implementation change that would change typical condition semantics and expectations, and thus might break the way their are useful in either kubectl wait or the Openshift console for example.
OTOH condition types somehow define lifecycles step of the workspace, so I still think it might be useful to have them be part of the specification, at least the basic conditions we think will always make sense.


Update playnite.json

Update to 10.20

Closes #XXXX

Relates to #XXXX

[ ] I have read the Contributing Guide.

/verify


PhantomJS Backbone.History Issues

When trying to run a spec through PhantomJS I am running into an issue that doesn't happen with Backbone proper:
mocha-phantomjs --setting localToRemoteUrlAccessEnabled=true --setting webSecurityEnabled=false test/index.html --hooks ./hooks.js --timeout 25000
TypeError: 'undefined' is not a function (evaluating 'this.checkUrl.bind(this)')

  file:///Users/matthew/dokidoki/_site/assets/backbone/exoskeleton.js:1570
  file:///Users/matthew/dokidoki/_site/assets/backbone/exoskeleton.js:1769
  file:///Users/matthew/dokidoki/_site/assets/backbone/exoskeleton.js:23
  file:///Users/matthew/dokidoki/_site/assets/backbone/exoskeleton.js:1771

PhantomJS has a known issue in that it doesn't support Function.protype.bind. We pollyfill it in one of our test helpers.
I'm not sure what you're running into though, the tests seem to be running fine for me.

Okay thanks!


Unicode 15 is released

Updated in commit https://github.com/hardboiled65/seshat-unicode/commit/eacb64f390374bc45094fa1034a7828afc68a928 (v0.1.0)


The same error message for adding firewall rules that are invalid for different reasons

The same message pops up at the bottom when different mistakes allowed when rules creating:

invalid IP
Expected result: Invalid IP address

start port > end port
Expected result: Start port is greater then End port

duplicated rule
Expected result: The rule already exists

Actual result for all cases:

Connected feature ID:
firewall_rules_edit
vm_firewall_rules_edit

will be resolved in 997


Add support for CentOS podvm image

Fixed via - https://github.com/confidential-containers/cloud-api-adaptor/pull/434


Cannot click/scroll at all in Chrome/Windows

Simplebar seems to be working fairly well in most every browser, but I've found that it doesn't respond at all in Chrome on Windows 8 or 10. The  window I have simplebar used on does not scroll via mouse, nor will it allow me to click/drag on the sidebar to scroll that way.
I've tested on Mac using FF, Chrome, Safari, and on Windows using FF and IE... all function properly. Chrome on Windows is the only one that doesn't work. Any idea why this would be?
Thanks for any help!

Hey,
I just tested on Browserstack (I don't have a PC) on Windows 10, latest Chrome and it seems to be working fine for me. Do you have an existing environment where I could test it and see it not working?
Thanks

Thanks for your reply! Yeah, got a little help from our Dev team here at work, and we determined that the issue is probably coming from people using older versions of browsers. We tried it on an older version of FF, it didn't work, then updated to the latest version, and the scrolling worked. So that may be the issue. If you don't have a PC, I'm not sure I can show it not working to you, because I can't even reproduce it myself unless I'm on a colleague's PC.
Aside from that little hiccup, it's really cool stuff you've put together, thanks for sharing it! And thanks again for responding!

Thank you for the nice words :)
I'll take a look on older browsers versions then as I only tested on latest!

No problem, I really do appreciate your work! I'm on a Mac too, and it's fantastic on all Mac browsers, just the older PC versions of FF and Chrome seem to not recognize the scrolling, not sure why. Thanks again!

What versions of old browsers did this not work in?

Chrome on Windows 8 and 10, and older (but fairly recent) versions of Firefox on PC only. Mac versions worked fine.

Hey,
So I just tested on Browserstack with Windows 8 on Firefox 50 (currently it's 57) and Chrome 56 (currently it's 63) and it worked as expected.
I'll close now, you can comment if you have more details about a precise browser version. It's probably a polyfill missing.


Moving to Poetry for Dependency Management

To simplify the process of packaging and distribution to PyPI, we'd like to switch to Poetry for our dependency management. While this doesn't have priority at the moment, this is something we're planning for the near future.

Per https://github.com/python-discord/organisation/issues/132, at this time we're not interested in proceeding with this.


[MM-50976] - Contact Support to redirect to Zendesk and pre-fill known information

Summary
Makes changes such that all "Contact support" ctas redirect to zendesk and "Contact sales" ctas redirect to mm.com
Ticket Link
https://mattermost.atlassian.net/browse/MM-50976
Related Pull Requests
https://github.com/mattermost/customer-web-server/pull/1114
Release Note
NONE

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

Hi @AGMETEOR ,
was seeing this error on the spinwick,

/e2e-test

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

/e2e-test

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

Hi @AGMETEOR @marianunez
should we wait till this MM-51018 is merged ? Currently, not seeing the form filled when clicked on contact sales

Hi @AGMETEOR @marianunez should we wait till this MM-51018 is merged ? Currently, not seeing the form filled when clicked on contact sales

@emdecr will be working on supporting these params in mattermost.com side. We can still move forward with completing the work here and if this is used before that ticket is complete they will still be redirected to the correct form but without the field pre-populated. I don't think this is a blocker for this change. We can do the full validation of the prefilled info once published in mm.com

Thanks @marianunez 👍
@yasserfaraazkhan I can send you a URL and creds for our development site if you want to check what the the decode looks like. I'll send a DM. I've got a in-progress branch up there.


OR error

i run the python file and i do option 2 for OR then i get an error when i select payloads/or.txt

thanks

reinstall tool and try again
-cyberpro010

Hello,
This issue is related to character encoding, because the tool is attempting to read payloads/or.txt with a default encoding that doesn’t support certain characters in the file.
For now, try using the default payload list we provide, which should work without issues.
I’ll work on a fix to handle potential UTF-8 encoding errors in custom lists tomorow
hexsh1dow

Update:
It looks like you are already using the default file You can try putting the or.txt file in the root of the tool | try updating the code and make sure you install all the requirements
hexsh1dow

hi, just reinstalled everything and ran the code but i still get the same error even after i put or.txt in the root, is there any fix to this?

Hello,
try to create a short list to see where the problem is, from my side everything works so try this and tell me
hexsh1dow

so i deleted all special characters from or.txt and it doesnt give me that error but now it says this

Hey,
So yes, there is a problem, are you in a sandbox or something like that ?
hexsh1dow

no i am using my main windows pc with no sandbox i am using cmd to run the file

bro it is linux compatible

your pc have issues not or.txt

ohhhh ill try on linux

how do i fix this then?

Hello,
It seems that you have not installed the correct version of Chrome driver, you can directly find the correct one in the readme file.
hexsh1dow

i run the python file and i do option 2 for OR then i get an error when i select payloads/or.txt  thanks

Hello,
We have patched the issue. Can you confirm that the issue has been fixed?

how do i fix this then?

Make sure all requirements installed as detailed in the README.md, remove existing chrome from the $PATH and install the README.md mentioned version of chrome
Let us know if you continue to experience the same issues
Regards

hi, so i want to use the tool in windows, i have install all requirements and everything is up to date i have even re downloaded just now the loxs tool but i still get this error

hi, so i want to use the tool in windows, i have install all requirements and everything is up to date i have even re downloaded just now the loxs tool but i still get this error

Hello,
We will try to resolve this issues, let you know after a fix
Best regards,
Haq

bro it is linux compatible

LOXS is a cross platform compatible tool, so you can run in any OSes
Even you can try it in termux (Make sure all requirements are installed)

bro it works best on linux

bro it is linux compatible

LOXS is a cross platform compatible tool, so you can run in any OSes
Even you can try it in termux (Make sure all requirements are installed)

bro it works best on linux

Hello,
You can run it on Linux as well, but that doesn’t mean loxs isn’t compatible with other operating systems.
Regards


[CI] Try to fix label bot

Purpose of the pull request
try to fix label bot
test successfully in https://github.com/SbloodyS/dolphinscheduler/pull/3

Codecov Report

Merging #10852 (d7243d2) into dev (c829738) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev   #10852      +/-   ##
============================================
- Coverage     40.66%   40.66%   -0.01%
+ Complexity     4826     4825       -1
============================================
  Files           913      913
  Lines         36306    36304       -2
  Branches       3989     3985       -4
============================================
- Hits          14765    14763       -2
+ Misses        20068    20067       -1
- Partials       1473     1474       +1

Impacted Files
Coverage Δ

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

...pache/dolphinscheduler/common/utils/DateUtils.java
75.16% <0.00%> (-0.17%)
:arrow_down:

.../dolphinscheduler/plugin/task/datax/DataxTask.java
0.00% <0.00%> (ø)

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 c829738...d7243d2. Read the comment docs.


Falsy bouncer - incorrect solution passes

Challenge Bonfire: Falsy Bouncer has an issue.
My code:
function bouncer(arr) {
  // Don't show a false ID to this bouncer.
  function value(val) {
    return val != false && typeof val != undefined && val != 0 && val != null;
  }

  arr = arr.filter(value);
  return arr;
}

bouncer([7, "ate", "", false, 9], "");

My code passed but as you can see does not deal empty strings or NaNs.

That's because you are not strictly comparing false with false.

@awesomeaniruddh Exactly, @richyvk's code shouldn't pass, but does.
This is really strange, since NaNs, empty strings, and undefineds were added to the tests by @abhisekp in #3124. Must've gotten lost somewhere along the line.. I'll create a PR that fixes it again.

Also this following code also passes. I wrote nothing to filter the values.
function bouncer(arr) {
  function valid(data) {
    return data;
  }
  return arr.filter(valid);
}


if else for get_magic_quotes_gpc usage

get_magic_quotes_gpc is deprecated since php7.4
https://www.php.net/manual/en/function.get-magic-quotes-gpc.php
With an if else condition, could this method used by 7.4 and greater ...

The Slim 2 release cycle has been closed for a few years now. We will unfortunately not be merging this in.
Please upgrade to Slim 4 or fork and patch yourself.
Thank you


Generate more than one QRCode on the screen.

Is it possible to generate more than one QRCode on the screen without them grouping together alone?
Because I have a loop with several QRCodes that should be inside each card, but I realized that they all carry them inside the tag

Even though I force it via CSS, they don't stay in the correct position.

Which CSS framework are you using?

Which CSS framework are you using?

I forced it using bootstrap and the qrcodes are inside a loop

Could you please share the HTML code along with the CSS classes that you used to render the QR code? This will help us identify the issue you are facing.

I have used Bootstrap version 5.1.3 and attempted to reproduce this issue, but it is working as expected. Please refer to the snapshot below for confirmation.

Below is the HTML code which I have used

QR code

                                <asw-qr-code #parent [qrData]="qrdata" [width]="option.width" [height]="option.height"
                                    [outerMargin]="option.outerMargin" [type]="option.type" [allowEmptyString]="true"
                                    [logo]="option.logo" (click)="customizeDesign()"
                                    [density]="option.density" [backgroundColor]="option.backgroundColor"
                                    [logoStyle]="option.logoStyle" [middleShape]="option.middleShape"
                                    (qrCodeURL)="getScan($event)"
                                    [cornerInnerShape]="option.cornerInnerShape" [cornerOuterShape]="option.cornerOuterShape">
                                </asw-qr-code>


Add olm test libs for Windows/Mac/Linux

Add olm test libs to run JUnit tests quickly, do you think this is a good suggestion?

Hey @brevilo，your efforts of fixing these bugs are greatly appreciated. Respecting your work of jolm, we’d like to sponsor somehow. Please kindly let’s know how.

Let's discuss the sponsoring topic in #17 as it's completely independent of this one. Thanks.

What exactly do you mean by adding "olm test libs" and what's the goal you want to achieve?
FYI, unit tests are already run automatically using GitHub's CI workflows (on push and for PRs). Granted, eventually it might be a good idea to run those unit tests on other platforms than just Linux.
If your question is about including or building upstream libolm as part of the jOlm installation or its unit test setup, then I can say that I considered that (see last point of the status report) earlier. However, thinking a bit more about it, I don't see this as a useful feature anymore. The reason is that no one should trust me (or jOlm) to safely and securely provide the upstream libolm library. It's very important that users/developers get their copy of libolm from their preferred secure, trusted, standard software source since it's the central component for all Matrix E2EE features. That means users should either get the sources directly from upstream and compile them themselves or use binary packages provided by their preferred distribution channel (typically via a package manager like apt, yum, homebrew). If we agree on this then it doesn't make much sense to test against our own copies of libolm by shipping those with jOlm. We ought to run the tests against whatever a jOlm user has installed on their concrete system since that's what jOlm will call and thus depend upon after all.
Cheers

I see, please forget this ticket.


Is there a chance to ignore error and reject reason separately?

When a promise is failed, we call reject(reason). However then the two global error catchings are hit both. But I don't want log them twice. So I want to know is there a chance to ignore error and reason separately? Perhaps we need a hook called ignoreReason?
Ember.onerror = (error) => {
  if (this._ignoreError(error)) {
    return;
  }
}

RSVP.on('error', (reason, label) => {
  if (this._ignoreError(reason)) {
    return;
  }
}

#103


where is the place that cache to use? disk or memory?

where is the place that cache to use?
use a temp local disk or a fix size memory?

goofys does not explicitly cache data, and relies on OS buffer cache

goofys does not explicitly cache data, and relies on OS buffer cache

NAME:
   goofys - Mount an S3 bucket locally

USAGE:
   goofys [global options] bucket[:prefix] mountpoint

VERSION:
   0.24.0-45b8d78375af1b24604439d2e60c567654bcdf88

GLOBAL OPTIONS:
   -o value            Additional system-specific mount options. Be careful!
   --cache value       Directory to use for data cache. Requires catfs and `-o allow_other'. Can also pass in other catfs options (ex: --cache "--free:10%:$HOME/cache") (default: off)
   --dir-mode value    Permission bits for directories. (default: 0755) (default: 493)

--cache
is it a disk cache, and how it works ?


Upgrade to Spring Boot 3 / Spring Security 6

Spring Security 7 is already on its way, while our driver still relies on version 5: migrating to 6 (-> Spring Boot 3) is then starting to be an option.
Here's some useful information:

Spring Security: Migrating to 6
Spring Boot 3.0: Release Notes

Consider also re-using existing JWT Bearer token management Spring implementations:
https://docs.spring.io/spring-security/reference/servlet/oauth2/resource-server/jwt.html#oauth2resourceserver-jwt-minimaldependencies


Code cleanup: remove OPCODE/OPCODE_CHAIN macro and move macro to 3dos.h

This, IMHO, improve the readability of the code.

Gonna start working on this again, so I'm going to merge this finally.
Thanks!


moveto: fix case-insensitive same remote move

Fixes #3104

What is the purpose of this change?
Fix a bug where moveto would delete a file when trying to change the case of a name on a remote that is case insensitive.

Was the change discussed in an issue or in the forum before?
#3104

Checklist

[x] I have read the contribution guidelines.
[x] I have added tests for all changes in this PR if appropriate.
[x] I have added documentation for the changes if appropriate.

[x] I'm done, this Pull Request is ready for review :-)

I'll try to write a test for this. Give me a bit to figure it out, I'm kind of busy at the moment and I'm not sure how to write a test for this scenario.

I'll try to write a test for this. Give me a bit to figure it out, I'm kind of busy at the moment and I'm not sure how to write a test for this scenario.

No worries!
I'd start by copying this test (or maybe adding a bit to the end of it) which tries to do the move from "upper" to "UPPER" and make sure the right thing happens.  This will get run on the integration tests and check all the different backends.
https://github.com/ncw/rclone/blob/99bc013c0a23d9dd5062600429a1488ae00cd277/fs/operations/operations_test.go#L713

Okay, so while writing the test, I noticed the issue does not seem to be fully resolved. It turns out this is not quite as simple to solve. It will require changes to a lot of functions. A lot of functions can't handle this situation. moveOrCopyFile needs to be changed to know that a move operation does not necessarily mean the source can be deleted. Move still needs the above change. NeedTransfer needs a case for when the dst and src are the same file but with different case. On top of all that, even once everything else is fixed, OneDrive will return a nameAlreadyExists error when attempting to move a file in this way. I wouldn't be surprised if other issues come up as well. It may be easier to add a special case for changing the case of files on a remote.

If this can't be fixed before the next release, maybe a temporary error should be added for this case?

I think a partial fix is better than no fix :-)
Maybe we should merge your original code as it prevents data loss and think more about the other cases.
The NeedsTransfer case is probably less important because the march routine should be doing case insensitve/case sensitive match-ups as appropriate already.

Maybe we should merge your original code as it prevents data loss and think more about the other cases.

The current version seems to still delete files. I'm about to push a change that at least prevents data loss. It still cannot rename the file though.

The NeedsTransfer case is probably less important because the march routine should be doing case insensitve/case sensitive match-ups as appropriate already.

I thought it needs to be changed because even once the deleting issue is solved, this is shown:
019/05/20 11:32:18 DEBUG : testfile.txt: Size and modification time the same (differ by 0s, within tolerance 1s)
2019/05/20 11:32:18 DEBUG : testfile.txt: Unchanged skipping

I was thinking a bit of a messy way to get by the issue was to rename the file to a random name then move it back. That would also avoid the nameAlreadyExists issue.

Is this ready to merge - what do you think?

At the moment, this kind of just pushes the problem back to be dealt with later.
What would you think about having this case simply move the file twice to rename? The idea would be to find a random file name that is not used, move it there, then move it back with the proper capitalization. It's messy but it would work.

At the moment, this kind of just pushes the problem back to be dealt with later.

OK.

What would you think about having this case simply move the file twice to rename? The idea would be to find a random file name that is not used, move it there, then move it back with the proper capitalization. It's messy but it would work.

I think that would be fine.  I'd probably take the existing name and add some random junk on the end for the first rename so if it went wrong half way through the user wouldn't be completely lost.  Do do the move recursing is probably the best thing to do.

The most recent commit can now handle case insensitive renames and includes a test to ensure the issues does not happen again.

Also, I'm not sure why but the build is complaining about an ineffectual assignment in the box backend?

That was a short lived update from golang-ci which has now been reverted.  I've kicked the build again!

@ncw
Looks like the build was successful this time.
The pull request is ready to be reviewed.

This looks good now - thank you very much :-)
I'll merge it now.


Ecosystem testing

See for example https://github.com/mosuem/ecosystem/actions/runs/11857905123/job/33047326462
cc @devoncarew

[ ] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.
Most changes should add an entry to the changelog and may need to rev the pubspec package version.
Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

A few in-line comments, mostly to help me get context on the PR.

Yeah, sorry for the complete lack of documentation - this is not ready for review yet.

I hadn't considered this mechanism - a re-usable workflow. With this, any repo could set up a mini-corpus to test what a package upgrade might do to their apps under test.

Yes, that's the idea. This way, any package might have "their" set of packages they care about, so we could

I think another - perhaps less flexible solution - would be thuswise:

have a standalone repo for testing package upgrades (this would be useful for testing highly used packages, but not general packages)
have a corpus of apps defined declaratively
have a PR somehow indicate which package upgrade to test (modifying a specific file?) the system would likely use this to generate dependency override files

So I would have to file a PR with that repo in addition to the PR in the repo of the package-to-be-upgraded?

attempt to shard the PR's workflow into multiple jobs, one per app in the corpus. then failure of a specific corpus app is easier to investigate

I originally had in mind to create multiple jobs, but could not find a way to collapse the list of jobs in the Github action view, the"Some checks were not successful"-thing. If run in a separate repository as you are proposing here, that is fine, but running it together with other checks would not work, as it would produce dozens of checks.

have the workflow collate all job status info into a markdown table that it appends to the PR; this might show info like which apps changed state from 'pub get' working to 'pub get' failing; similarly for analysis and test

Yes, that would also be added here, kind of instead of having multiple Github jobs. That way the user still gets to see which app failed easily. For debugging, we could output the logs to different workflow artifacts, and link those - that would make it very easy to investigate.

The markdown table lets you see at a glance which apps were adversely affected by the package upgrade.
Thoughts?

I think (IIUC) that filing a separate PR in another repo might be more work than running this reusable workflow "on command", either by hand or by labeling the PR with something like ecosystem-<packagename>-upgrade.


Parse EventPipe payloads for DiagnosticSourceEventSource events

NetPerf and NetTrace v1 format don't support serializing array typed parameters.
DiagnosticSourceEventSource declares well known events that use array typed parameters
and the runtime serializes EventPipe metadata which claims the events have no parameters.
This is a targetted fix so that EventPipeEventSource will recognize these well-known events
and ignore the empty parameter metadata provided in the stream, treating the events
as if the runtime had provided the correct parameter metadata.
I am concurrently working on a runtime fix and updated file format revision which can
correctly encode these parameter types. However for back-compat with older runtimes we
need this.

@brianrob @josalem @sywhang - code review please : )
cc @karpinsn @davidmikh - This is the TraceEvent change that should unblock your VS 16.4 work once checked in.

We're still seeing some issues with our scenario, for our nettrace file at least we still aren't able to get the parameter metadata. From what I was able to see we don't seem to be hitting any of the code that was changed here when opening a nettrace file that has the DiagnosticSource events we need, though I didn't dig deep enough to figure out why.
I sent an email with additional information and the actual nettrace file I used to test this change with but figured I'd post it here too

Talked offline with @davidmikh - the issue he mentioned above was resolved, no change to the PR needed.


examples change to sklean dataset load method

The same to #7310 but change the commit account.
change tf.contrib.learn.datasets.load_dataset('boston') to sklearn.datasets.load_boston()
change tf.contrib.learn.datasets.load_dataset('iris') to sklearn.datasets.load_iris()
because when run examples/learn/iris.py and examples/learn/boston.py with python35, errors like followings occurs:
UnicodeEncodeError: 'utf-16-le' codec can't encode character '\udcds' in position 166: surrogates not allowed
so it's better to change sklearn's method.

Can one of the admins verify this patch?

Great, CLA looks good, thanks.  We're quite busy through tomorrow, but we'll look at this soon.

Based on the discussion at https://github.com/tensorflow/tensorflow/pull/7310, it sounds like we should fix the unicode compat bug in tf.contrib.learn.datasets.load_dataset rather than adding more dependencies on SKLearn. @hevensun can you take that on?

@dandelionmane  first I want to fix this unicode error using sklearn's datasets load  method for other users to use, then I will deep into the unicode compat bug in tf.contrib.learn.datasets.load_dataset to if I can fix it.

Jenkins, test this please.


Latex math broken in the encoding chapter

Possibly due to jupyterbook update.

Hi,
the equations in the current version of the encoding tutorial look ok. I'm thus closing this issue for now but please feel free to re-open if needed.
Cheers, Peer


JSX + React

Extracted from #1216, this implements client-side support for JSX with React. It looks like this:
```jsx
import {Counter} from "./components/Counter.js";

display(<Counter title="Hello, JSX" />);
```

In JSX blocks, you can only display one thing at a time; subsequent calls to display will replace whatever was displayed previously. Also, you can only display React elements.
TODO:

[x] JSX code blocks
[x] JSX modules
[x] React built-in
[x] Handle syntax errors during JSX transpilation
[x] Implicit (singular) createRoot within display
[ ] Documentation
[ ] Tests

Future work:

Allow JSX in inline expressions ${<Component />} (requires acorn-jsx)?
Allow JSX in Markdown directly (à la MDX)?

Fixes #971.

Hmm, I found a bug where if you move a JSX block to a new location during preview, it doesn’t get relocated (because we do the special treatment for root._nodes but that doesn’t apply to root._root). I think/hope I can fix that pretty easily though.


Import Issues

When trying to import CSV file into the library, it errors out. I have created some example entries under "fuel" and exported to CSV file from lubblogger website, then proceeded to delete the entries and tried to import from the previously exported CSV and it fails with error message:

any help would be greatly appreciated.
Helio2k

Any chance you can attach the CSV that is error'ing out?

Ah I was able to recreate the bug, this is now fixed, please test.

Yes, now it's working just fine.
Thank Your this fast fix.


User categorize setting ignored

If a user has NO in UI settings / categorize modules, modules get categorized in spite.
You should  also check if global categorizing setting works properly.

Could you please explain more of what you mean, I didn't quite understand? Where the those settings?

each user has its own UI settings.
Webmin users /  / User interface options / Categorise modules?

D-github ate <user>

Oh, man.. ok... Thanks..

Alright, it will be fixed shortly in version 10.3. Thanks for pointing out!


Reader_File: Fix crash in case of request to read a big count of bytes

Fix https://github.com/MediaArea/MediaInfoLib/issues/1030


webkitgtk_4_1: incorrect rendering

Describe the bug
When using webkitgtk_4_1 rendering seems to be broken in some way:

(webview on the left and Firefox on the right)
This applies to a number of different things, from fonts being the wrong size to the checkboxes not even appearing in the webview.
I first encountered this in some rust code, but have been able to reproduce the same result in python.
Steps To Reproduce
Steps to reproduce the behavior:

Create the following script:

import webview

webview.create_window("Hello world", "http://localhost:2323/")
webview.start()

Load anything on localhost.

Make sure you have the required dependencies (some of these might not be needed):
nix-shell --command zsh -p gtk3 python312Packages.pygobject3 python312Packages.pywebview python312 python312Packages.typing-extensions  webkitgtk_4_1

Run python main.py

Expected behavior
The result in webview should be rendered properly, similar to how firefox displays it. This is what happens on other distros, which is why I think the issue might have to do with nix/NixOS.
Screenshots

Additional context
I have encountered this issue on both my nix machines and not any other machines.
I don't have this issue on Arch Linux, and I also know this doesn't happen on Fedora.
Also see this post on the NixOS discourse: https://discourse.nixos.org/t/tauri-dev-build-not-rendering-correct/57136
If you want a more fleshed out example, you can try out either creating a fresh tauri project and seeing what the demo pages looks like in comparison to what it should or try running igneous-md.
Metadata

 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.63, NixOS, 25.05 (Warbler), 25.05.20241209.a73246e`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.24.10`
 - nixpkgs: `/nix/store/yw6kg4rb9v8s3ypjbpspig5r81m4lr5s-source`

Notify maintainers

@NixOS/gnome, @dasj19, @bobby285271

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

The stylesheet looks like it comes from GitHub, maybe you are missing glib-networking, which is required for TLS support. See also GIO modules section of the Nixpkgs manual.

Thank you so much.
All I needed to do was to use wrapGAppsHook4.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/tauri-dev-build-not-rendering-correct/57136/3


Propose already set values when initialized is triggered again

When user triggers initialization a second time (on an already existing box project), the defaults are now selected such that they represent the previous defaults. This allows for faster re-initalization, where the user only has to change the value that should be changed.

Codecov Report
Attention: Patch coverage is 96.36364% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 98.92%.  Consider uploading reports for the commit 00c85c3 to get more accurate results

Files
Patch %
Lines

src/box/initialization.py
92.85%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #26      +/-   ##
==========================================
+ Coverage   98.78%   98.92%   +0.13%
==========================================
  Files          19       19
  Lines        1072     1118      +46
==========================================
+ Hits         1059     1106      +47
+ Misses         13       12       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Media queries and other conditional selectors before the rules they overwrite

Implements #180
I wanted to add a test for this, but looks like with the current test setup it is hard to verify the scenario, because jss.generateClassName() always generates class names with the same suffix: https://github.com/jsstyles/jss/blob/master/tests/utils.js#L44 . Please let me know if you'd like to still have a test for it and advise how to overcome the aforementioned issue.

Is something wrong with the PR? I don't see how the implementation should work ...

What it does is just checks if we already have generated class name for a particular "selector", if so uses that in the consequent places:
{
  '@media print': {
    app: { ... }  // generated className is .app-jss-001
  },

  app: { ... } // use previously generated className here (.app-jss-001)
}

Yeah, but look at the diff here on github ... it's almost empty

It is actually a one-line-fix)

haha nice, didn't realize that's all we need, we need to add tests though

you can make sheet.toString() and see everything is generated properly

Here is a good place https://github.com/jsstyles/jss/blob/master/tests/integration/sheet.js#L108 for this test

There is an issue with testing that as I mentioned in the PR description, looks like in every test we mock jss.generateClassName() method that is responsible for generating the unique class names. In mocked version, it always appends the same suffix to the selector name (e.g. "a" -> ".a-id"). Having this, it is impossible to test if the generated class name for root app selector is the same that the one for app within @media block because they will always be same ('app-id').
I should probably just override jss.generateClassName() just for a single test to implement "random" version

You can create an own jss instance, generateClassName won't be mocked then.

import jss, {Rule,} from 'jss' -> import jss, {create, Rule} from 'jss'

ok, I'm gonna add the test

@kof, added, plz check

merged thanks, also use linter next time) npm run lint


Client to one IP

is there a way to make it where the client can access one ip address??

Do you mean the client uses the VPN for 1 IP only (called split-tunneling) or that when the clients connects he can't access the LAN or other VPN users?


Release 0.10.2

<!-- Make sure you have read http://napalm.readthedocs.io/en/latest/contributing/index.html --!>

Pending https://github.com/napalm-automation/napalm-junos/pull/169 and https://github.com/napalm-automation/napalm-junos/pull/170

Coverage increased (+0.09%) to 83.594% when pulling b019279c9687d65068636f80e00722a8168d5411 on develop into db47aee5e46ad304b67580d95bbbd0a474890e7e on master.

Coverage increased (+0.09%) to 83.594% when pulling b8e892be28f101701adefbf08bcde51fd475ab1b on develop into db47aee5e46ad304b67580d95bbbd0a474890e7e on master.

Coverage increased (+0.09%) to 83.594% when pulling b8e892be28f101701adefbf08bcde51fd475ab1b on develop into db47aee5e46ad304b67580d95bbbd0a474890e7e on master.


fix: Add zod schema tests for mock response

Context
AI/gen-ai-hub-sdk-js-backlog#117.
Zod schema check for responses are added in the unit tests for openai and orchestration.
Notice: zod schema check is currently missing for embedding response. Once we generate types from spec for embedding, we can add this check to avoid duplicated effort.
Definition of Done

[X] Code is tested (Unit, E2E)
~[ ] Error handling created / updated & covered by the tests above~
~[ ] Documentation updated~
~[ ] (Optional) Aligned changes with the Java SDK~
~[ ] (Optional) Release notes updated~

Now after the separation, I generate config and schema in this test package. I don't want the config generation part to be spread everywhere when openapi generator is called.
The configs are still generated every time before test execution. Because we need schemas to run the tests, and schemas need to be generated separately via each ts-to-zod.config.cjs for each client.
Notice that ts-to-zod only works with the ts-to-zod.config.cjs in the package root. I thought about creating just one config file for all generated clients, but it feels a bit too complicated to modify the script, and semantically, the generated zod schemas for each client should also be separated.
Anyways, it would make more sense if we can integrate this kind of test in e2e. But at least we now have some checks for mock response as well.

I still feel this test should not run with every build. Ideally only when we update a client and want to test the new types. But for now its okay

I still feel this test should not run with every build. Ideally only when we update a client and want to test the new types. But for now its okay

Ideally, we could have a workflow to (detect updates of specs and auto) generate clients. After that, we should run schema test + (e2e if we integrate zod also there). But this will also bring complexity.


[New Port Request] mysql-connector-cpp

Library name:
mysql-connector-cpp
Library description:
MySQL Connector/C++ is a MySQL database connector for C++. It lets you develop C++ and C applications that connect to MySQL Server.
Source repository URL:
https://github.com/mysql/mysql-connector-cpp
Project homepage (if different from the source repository):
Anything else that is useful to know when adding (such as optional features the library may have that should be included):
I need the latest version and version 1.1
(https://github.com/mysql/mysql-connector-cpp/tree/1.1)

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now, consider making a pull request instead.


s_client -showcerts man text misleading: "all certificates in the chain"

The text of man openssl-s_client reads in part:

-showcerts
display the whole server certificate chain: normally only the server certificate itself is displayed.

However, when I use s_client -showcerts, the certificate chain does not include the CA certificate.
% openssl s_client -connect openssl.org:443 -showcerts
CONNECTED(00000003)
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify return:1
depth=0 CN = openssl.org
verify return:1
---
Certificate chain
 0 s:/CN=openssl.org
   i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
-----BEGIN CERTIFICATE-----
... [snip]...
-----END CERTIFICATE-----
 1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
   i:/O=Digital Signature Trust Co./CN=DST Root CA X3
-----BEGIN CERTIFICATE-----
... [snip]...
-----END CERTIFICATE-----
---

Note that the certificate chain does not include an entry for CN = DST Root CA X3. My understanding of "the whole server certificate chain" is that it includes the certificate of the Root Certificate Authority (CA).
I suspect what is happening is that s_client is showing those certificates which the server sends. This is a reasonable choice, but different from "the whole certificate chain". The server is usually configured to not send the Root CA certificate, because there is not much point. The user won't trust such a certificate just because a server sends it, and the server admin assumes that the user already has a copy in their local store of trusted certificates.
This misunderstanding appears from time to time in user forums about openssl. People expect "the whole chain" to include the CA cert, and it doesn't.
Suggested fix: clarify the wording to say that -showcerts only shows what the server sent.
Also, it would help perhaps to put output in the bottom of the "Certificate chain" section to note that the CA certificate was found in the trusted collection. For example, something like:
... [snip]...
-----END CERTIFICATE-----
 2 s:/O=Digital Signature Trust Co./CN=DST Root CA X3
   Found in trusted certificate at /opt/local/etc/openssl/cert.pem
---

Diagnosis: This man text appears to come from openssl/doc/man1/s_client.pod.

I wrote a branch with documentation clarifications to openssl/doc/man1/s_client.pod at https://github.com/JDLH/openssl/tree/s_client-showcerts-doc . I haven't yet made this a pull request, because I need to look at the contributor agreement etc.

I was trying to vouch that a server was sending a correct certificate chain, and the wording of the man pages confused me as well.