Showcase video scene creation and tutorial demonstrating open land

I think making a complete scene creation tutorial would help get more people interested in open land.  Something high quality like the Australia project that was just released on the market place.  Of course not as big just a small scene with trees, grass, cliff, river, mountains all using 8k textures from mega scans.  The scene should showcase the use of the paint layers such as mud, sand, snow and so on.  The current default map is a nice place to start but it would be cool to showcase a photo realistic beautiful scene and how easy it is to make with open land.    Cheers!

A tutorial creating a scene like https://vimeo.com/539122659 would be a wonderful showcase of what open land can do.  When all the features are available to create this.

Oh yes, that's on the horizon for sure. The default one is just to get started & to learn.
I was talking to some people about getting some help too.
I will ping you when there's something on that.

One more thing to point. Here's why I am not rushing on this yet.
OpenLand still needs some key features like biomes, mods support, etc.
So, in the meantime, we will do some major changes.
If we create a tutorial like this, then some of those will be outdated.
I want to OpenLand to be a bit stable on the feature side & once it's there I am planning to create a FREE course on creating something like that. That's where I talked to some people about doing some collab. Maybe you can join me too :D


Highlighting vs GitHub

The changes I've made to add more nested scopes and details to matching has caused some problems. GitHub, specifically, adds weird colors to classes that Sublime don't touch in standard color schemes.
I think the best route might be to isolate github coloring to its own repo.
Alternatively separate a "simple" and "advanced detail" syntax.
Prio 1 now, I will roll back to just having bug fixes and no additions until I (or anyone else) can take time to figure out a more cross-viewer scope/class compatible naming scheme.

I think I've said this before, bit of not, I'll state it here: The syntax definition files for NimLime are not tied in any way with Github's highlighter.

Aha, ok, I thought they were the basis. They are separate? Because it seems just a day or so ago github started highlighting nim differently (?)
In any event the PR cleans up a bit more for NimLime. I found one highlight bug in one file yesterday, so I'm gonna squash that one too, but maybe after the weekend. So I think the PR is better pulled then not atm.


[tcp] improve logging in TCPlp

This pull request improves logging in TCP, by doing the following:

Avoid calling printf from TCPlp code, even for error handling, and instead use OpenThread's logging
Omit newlines in TCPlp log messages, since OpenThread's logging adds a newline already
Add a new call, tcplp_sys_panic, to use to handle assertion failures in TCPlp

In removing printf from TCPlp, this pull request resolves openthread/ot-qorvo#210.

@samkumar , thanks for submitting this PR.
I can confirm that this change addresses the build issue raised in https://github.com/openthread/ot-qorvo/issues/210.
Build logs: https://github.com/jwhui/ot-qorvo/actions/runs/1774854431


Allow customer password to be nullable like the definition states

1. Why is this change necessary?
Guest customers have no password. The customer definition does not require the password to be set. The customer entity instead does.
2. What does this change do, exactly?
Make the property and its getters and setters nullable.
3. Describe each step to reproduce the issue or behaviour.

Have plugins installed that process customer logins

4. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

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

thanks for your contribution @JoshuaBehrens  :+1: :tada: :blue_heart:

You're welcome 💜


加载错误

2021-12-26-10.log.gz

[14:40:04 INFO]: Plugins (39): ActionAnnouncer, AdvancedEnchantments, AuthMe, BetterRTP, BetterRTPAddons, CMI, CMIEInjector*, CMILib, CoreProtect, DecentHolograms, DeluxeCommands, DeluxeJoin, DeluxeMenus, Elevator, HeadDatabase, HolographicDisplays, LuckPerms, mcMMO, MessageAnnouncer, MiniMOTD, Multiverse-Core, NBTAPI, OpenInv, PlaceholderAPI, PlayerParticles, PlayerPoints, PlotSquared, ProtocolLib, QuickShop, Residence, Shopkeepers, spark, TAB, UberEnchant, UltimateTimber, Vault, VisualFileEditor, WorldEdit, WorldGuard

paper-1.18.1-101
ocjdk17.0.1

请测试 https://github.com/FlickerProjects/TrChat/actions/runs/1633767026 是否还有此问题


Vault can't be migrated

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "Canutin.dev.vault" at "file:../Canutin.dev.vault"

Error: Migration engine exited.
Error: command failed with exit code 1
    at runPrismaMigrate (file:///home/srg/canutin/server/chunks/prisma-a4d71516.js:58:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async validateVaultMigration (file:///home/srg/canutin/server/chunks/prisma-a4d71516.js:71:3)
    at async load (file:///home/srg/canutin/server/chunks/20-1f136ca9.js:9:22)
    at async load_server_data (file:///home/srg/canutin/server/index.js:1547:18)
    at async file:///home/srg/canutin/server/index.js:2430:18
Error: command failed with exit code 1
    at runPrismaMigrate (file:///home/srg/canutin/server/chunks/prisma-a4d71516.js:58:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async validateVaultMigration (file:///home/srg/canutin/server/chunks/prisma-a4d71516.js:71:3)
    at async load (file:///home/srg/canutin/server/chunks/20-1f136ca9.js:9:22)
    at async load_server_data (file:///home/srg/canutin/server/index.js:1547:18)
    at async file:///home/srg/canutin/server/index.js:2430:18

This was a permission issue, fixed it by:

chmod 755<EMAIL_ADDRESS>


81updates

some updates based on feedback from matt and the addition of the auto-complete in the address book of federated sharing ID's

Moving to staging now.


Where is .cls file?

I tried git clone the repo and ran the command, then I ran into bug report:
Qt: Untested Windows version 6.2 detected!
This is XeTeX, Version 3.1415926-2.3-0.9997.5 (MiKTeX 2.9)
entering extended mode
(...\xduts\xduts.ins
! I can't find file `ctxdocstrip'.
l.1 \input ctxdocstrip

Hmm, looks like .cls file is already added to .gitignore, should it be provided?

ctex-kit/ctxdocstrip.tex at master · CTeX-org/ctex-kit

Don't use CTEX!


Some UFL bug fixes

This PR fixes the following:

Sort on reference number not working on decision list pages
Conclusion showing as a sort option on decision pages (now removed, no pages benefit from this)
Conclusion showing as a sort option on review pages (now a filter)
get_continuation_display being a bit eager in predicting the result of a review before it has been concluded
Inconistant usage of 'stage' vs 'phase'

Lastly, this branch targets the release version of UiL Core, which has some additional bug fixes. The only relevant fix is the search bar no longer crashing and burning if it can't find a specific attribute.

Also changed Frans' email adress to the right one. I added this here, as merging locale files is annoying and this avoids that whole thing.


More setup and update readme

What?

After generating a new app with the rails template a few changes were needed, db setup, update gems, etc.

Change considerations

Added other things like factory-bot, brakeman, view_components, etc
I might have missed a few things when generating the app so please feel free to add any comments and suggestions.
People from placement, do you mind adding some description for your service as a comment to this PR? If not we can leave it blank.
Please also have a look at the initial commit

I can see a bunch of these quotation marks have changed from double (") to single (') quotes.
Was that done automatically by rubocop?
It looks like some of them are still double quotes (e.g. files in the spec/ directory). I'm wondering if that's an inconsistency introduced by us, or by rubocop 🤔

It's us. I don't think rubocop is looking at quotes. When it comes to the gemfile. The rails template uses double quotes but the apply_for_teacher_training gem file is using single, so I thought people prefer single quotes.
That said, I forgot to run bin/lint, which will make robocop change some things but not the double quotes

The linting issue has been fixed in this PR https://github.com/DFE-Digital/itt-mentor-services/pull/3#pullrequestreview-1765201287


Communicating version change magnitude

For those who have not been following (if you have you can skip down past the horizontal line), the question of whether we can include full JSON Schema compatibility in the next release and call it OAS 3.1 has been brought up.  Proper JSON Schema compatibility would require:

exclusiveMinimum and exclusiveMaximum are numbers rather than booleans, and function independently from minimum and maximum
readOnly and writeOnly cannot change the meaning of required based on whether they are in a request or response, or based on HTTP method

This means that for a 3.0.3 spec that uses boolean exclusive* or relies on combinations of *Only and required being HTTP-context-aware, changing the openapi property to 3.1.0 would result in an invalid spec file, contradicting the Semantic Versioning policy for minor versions.
The options are:

Stop short of full JSON Schema compatibility
Call this OAS 4.0.0 and do some additional communication explaining that it's not that big of a change
Discard SemVer, call this OAS 3.1.0, and do some additional communication explaining that it's not quite backwards compatibile
Discard SemVer, call this OAS 3.5.0 to indicate it's bigger than one minor version, and do some additional communication explaining what "bigger than one minor version" means
Discard X.Y.Z entirely and do some additional communication explaining what the new thing is

I don't think anyone is pushing hard for option 1, although I'm not 100% sure everyone's up to speed on the breakages so I don't want to assume.  But if we go with any of the others (that last one is unlikely but included for completeness), we need extra communication and that's what this issues is about.  I'll personally be fine with any of 2-5, but I understand why just calling this OAS 4.0.0 is undesirable for most people in the conversation so far.

I propose prominently featuring a table listing which Objects (or other major things that aren't directly associated with a single Object) have changed, and the magnitude of the changes: clarification, compatible, or incompatible.  Clarifications need only be mentioned if users are likely to have misinterpreted the unclear prior version and used it incorrectly.
Here are examples for three releases.  This shows how the tables make the distinction between "incompatible, but in a limited way" and "you're going to have to basically rewrite everything."
There is no table for a purely backwards compatible (but more than clarification) release, because we haven't had one yet, but hopefully it's obvious how that would show up and be clear.
OAS 3.0.2 => 3.0.3
You can see immediately that there's nothing but clarifications:

Object
Magnitude
Fields
Notes

Server Variable Object
clarification

enum should not be empty, likely to be a MUST NOT soon

Paths Object
clarification

paths start with /, clarified parameter matching

Path Item Object
clarification
$ref
sibling field behavior

Operation Object
clarification
callbacks
clarified map structure

Schema Object
clarification
pattern, nullable
clarified valid regex patterns, clarified underspecified nullable behavior

OAS 3.0.3 => ?3.1.0? ?3.5.0? ?4.0.0?
You can see immediately that it's not fully compatible, but that the incompatibilities are contained within the Schema Object and even then only a few keywords.

Object
Magnitude
Fields
Notes

Schema Object
incompatible
exclusiveMinimum, exclusiveMaximum, minimum, maximum
exclusive* now numeric rather than boolean, and independent from minimum and maximum

Schema Object
incompatible
readOnly, writeOnly, required
required is no longer conditional based on *Only plus HTTP request vs response context

Schema Object
incompatible
format
no longer validated by default (although note that few validators ever did this reliably), byte and binary deprecated in favor of new content* keywords

Schema Object
compatible
many new keywords
All draft 2019-09 keywords supported

Discriminator Object
compatible
^x-
extensions now allowed

Reference Object
compatible
summary, description
also other fields allowed for $ref in Schema Objects

OpenAPI Object
compatible
paths, webhooks
new webhooks feature, paths now optional if webhooks or components present

Info Object
compatible
summary, description
summary added, longer description allowed

Security Scheme Object
compatible
securitySchemeType
"mutualTLS" added

Security Requirements Object
compatible
{name}
scopes array usable in more cases

OAuth Flow Object
compatible
oauthFlowAuthorizationUrl
"implicit" to be deprecated by OAuth2

Operation Object
compatible
requestBody
request bodies allowed but discouraged for GET and DELETE

Media Type Object
compatible
encodingStyle, encodingExplode, encodingAllowReserved
improved multipart/form-data support

OAS 2 => OAS 3
It would not even be possible to write out such a table, because the entire format was refactored, as were many of the objects in ways too major to break down to just a few keywords.  Or maybe it would be possible, but it would be nearly as large as the spec so there wouldn't be much point!

In the last call we discussed how people were fearful of going to v4 - people being mostly end users, not tooling vendors.

That's how you solve it, clearly communicating "narrow" breaking changes, an that they could effect you. OpenAPI needs a blog, with an excellent DevRel writing it, then it's a non issue.

And the winner is:

Discard SemVer, call this OAS 3.1.0, and do some additional communication explaining that it's not quite backwards compatibile

As with most things in programming, there are lots of awful choices with lots of pros and cons, so let's not dwell on decisions that have been made. None of them were perfect.


2 files found with path 'lib/arm64-v8a/libquickjs.so' from inputs:

I try to run my project on my Android phone, but it fails with error:
2 files found with path 'lib/arm64-v8a/libquickjs.so' from inputs:
 - C:\Users\Terry\.gradle\caches\8.8\transforms\d815028faf901d4d4975b34335a30e4f\transformed\quickjs-release\jni\arm64-v8a\libquickjs.so
 - C:\Users\Terry\.gradle\caches\8.8\transforms\c5c5b7415d5b142347150f6c559b9ab3\transformed\zipline-release\jni\arm64-v8a\libquickjs.so
If you are using jniLibs and CMake IMPORTED targets, see
https://developer.android.com/r/tools/jniLibs-vs-imported-targets

Yes, It uses the same name 'libquickjs' as Zipline, so it's incompatible with Zipline, this can't be avoided IMO.
If there is a solution please let me know.

I clear all built caches, and it works now.
I have been using ZiplineJS in my project until I can't stand its weird StackOverflow exceptions anymore. ZiplineJS has few documents, and it doesn't support Windows as well.
So I am on this library now.

I see, Zipline is great and it inspired this library, but I can't set it up without Kotlin/JS, so I gave it up😥.


Add support for Pushed Authorization Requests

Feature Request:
Thanks for this library, it's been incredibly useful over the last few weeks. I'm starting to look into using Pushed Authorization Requests which might be a nice new feature for this library? If not full support for PAR then perhaps just exposing the /authorize query params? As these query params are required for a Pushed Authorization Request
https://datatracker.ietf.org/doc/html/draft-ietf-oauth-par#section-2.1
https://darutk.medium.com/illustrated-par-oauth-2-0-pushed-authorization-requests-652d71ed5cfb
Many thanks

An interesting proposal, indeed. From a cursory glance at these new flows I wonder if/how a public client (and as such: this library) would be involved to support this? Either way, we'd have to wait and see the IETF Draft be finalized before implementing it here?
Seems sensible to have this issue open to track any details or thoughts. Thanks for suggesting it!

FYI just for the sake of clarity, since September 2021 the RFC has been released: https://datatracker.ietf.org/doc/html/rfc9126


uploaded inference script using qlora

Uploaded a QLoRA version of "inference.py" named "inference-qlora.py". After testing on my machine, it appears to be functioning correctly.

Many thanks for your contribution. I have merged this PR into the main branch.


CAJAL test failures/warnings

I did the following:

Downloaded CAJAL master
Added toolbox to path
Changed server to http://brainviz1.cs.jhu.edu on line 17 of testOCP.m
ran 'testOCP.m'

The following test failures exist.  Recommend addressing prior to merge.
@kunallillaney @alexbaden @jovo @j6k4m8 @randalburns
Starting test run with 67 test cases.
....F...............
..........F.........
FWarning: At least 1 of the provided global coordinates are outside the local volume.
> In RAMONVolume/global2Local (line 236)
  In testOCP>testCutoutvsDenseSingleSlice (line 1978)
  In FunctionHandleTestCase/runTestCase (line 112)
  In TestCase/run (line 74)
  In TestSuite/run (line 85)
  In initTestSuite (line 56)
  In testOCP (line 21)
F..................
.......
FAILED in 374.158 seconds.

===== Test Case Failure =====
Location: /Users/graywr1/Downloads/CAJAL-test/test/matlab/api/testOCP.m
Name:     testUploadDownloadProbMapCutout

/Users/graywr1/Downloads/CAJAL-test/api/matlab/ocp/OCP.m at line 1905
/Users/graywr1/Downloads/CAJAL-test/api/matlab/ocp/OCP.m at line 1232
/Users/graywr1/Downloads/CAJAL-test/test/matlab/api/testOCP.m at line 254

The class eRAMONChannelType has no property or method named 'probmap'.

===== Test Case Failure =====
Location: /Users/graywr1/Downloads/CAJAL-test/test/matlab/api/testOCP.m
Name:     testAnnotationSlice

/Users/graywr1/Downloads/CAJAL-test/test/matlab/api/testOCP.m at line 1383

Inputs are not equal.

First input:
[880x1 double]

Second input:
[725x1 double]

===== Test Case Failure =====
Location: /Users/graywr1/Downloads/CAJAL-test/test/matlab/api/testOCP.m
Name:     testCutoutvsDense

/Users/graywr1/Downloads/CAJAL-test/test/matlab/api/testOCP.m at line 1890

Inputs are not equal.

First input:
     0

Second input:
     1

===== Test Case Failure =====
Location: /Users/graywr1/Downloads/CAJAL-test/test/matlab/api/testOCP.m
Name:     testCutoutvsDenseSingleSlice

/Users/graywr1/Downloads/CAJAL-test/test/matlab/api/testOCP.m at line 1979

Attempted to access s1.data(50,20,2); index out of bounds because size(s1.data)=[100,80,1].

Can you run against openconnecto.me as well?

probmap was deprecated, and CAJAL was never changed. You can still write probmap data, just use float32 and image instead. If that needs to be updated in CAJAL, I can look at it later.
On the second failure, notice the following:
http://brainviz1.cs.jhu.edu/ocp/ca/kasthuri11/info/ shows kasthuri11 as being:
            "0": [
                21504,
                26624,
                1851

whereas ocp shows:
            "0": [
                21504,
                26624,
                1850
            ],

I may have messed up transcribing kasthuri11 over. There are also test failures using CAJAL against the current master. That's the nature of a lot of these CAJAL tests (they don't transfer between servers well, you have to blank the DBs, etc). So, I'd be curious to see how CAJAL does against the current master.

Hey - thanks for looking into this - patching probmap is probably a good idea bc of existing downstream usage.
Here's what I get when I run same test suite on openconnecto.me.  To my knowledge this is a new bug, and possibly related to databases not being cleared.

>> testOCP
Starting test run with 67 test cases.
....................
....................
....................
..F....
FAILED in 512.043 seconds.

===== Test Case Failure =====
Location: /Users/graywr1/Downloads/CAJAL-test/test/matlab/api/testOCP.m
Name:     testIDFilterSlice

/Users/graywr1/Downloads/CAJAL-test/test/matlab/api/testOCP.m at line 2896

Inputs are not equal.

First input:
     2

Second input:
     3

...in any case, this is a different failure than the ones I sent previously.  :)

@willgray Are we good to go?

I think all of these need to be fixed before we push.  I haven't run any subsystem or deploy tests, so we are counting on this stuff to work.

I'm having a lot of trouble replicating the bugs above (locally, on dsp029, on brainviz, etc). I think, because the unit tests rely heavily on kasthuri11, that we should try the following:
Merge ndio into master and deploy on some agreed date. After deployment I'll immediately run tests and see what tests fail. From there we can either update CAJAL and/or update the datascopes as necessary. It will result in some "downtime", but it's the best way to make sure everyone is working off the same page. Every time I try CAJAL on a different server I get a different result!

i don't hate this idea if you are committed to fixing things that are broken in short order?  worst case, these bugs suggest that data isn't being posted or returned right, so could be a huge deal.  But could be a server thing as you point out, and is probably a fairly quick adjustment.  I don't have much bandwidth on my end, but will do what I can.

Yeah, we can work out the scheduling details offline (maybe in slack?).

It works!!!
First test failure is expected and should probably be deprecated.
Starting test run with 67 test cases.
F...................
....................
....................
.......
FAILED in 2994.733 seconds.

===== Test Case Failure =====
Location: /Users/graywr1/Downloads/CAJAL-test/test/matlab/api/testOCP.m
Name:     testInit

/Users/graywr1/Downloads/CAJAL-test/test/matlab/api/testOCP.m at line 49

Expected exception "OCP:ServerConnFail", but none thrown.

will is SOOO :gruntled: right now :+1:


ARTEMIS-3729 Fix JMS CORE client commit after async sends

@brusdev it looks good to me. If the test suite is happy, I am happy !  :)

@clebertsuconic the test suite wasn't so happy 😅 but now it LGTM 🎉


Test: Cleanup unused kubectl helpers.

Delete unused kubectl actions that are not used right now in favour to
other options

Signed-off-by: Eloy Coto<EMAIL_ADDRESS>

This change is

test-me-please

test-me-please


Nested Smart Groups

Smart Groups that are nested in other Smart groups show up as not being linked to any Policies.
Jamf (depending on your version) will prohibit the deletion of groups that have other Smart Groups dependent on them.  For these reports though, it makes it seem like certain smart groups are unused or not scoped when in actuality they can be by association with the parent Smart Group

Makes sense, will look into adding this functionality!
Thanks!

This has been fixed in ef67d8835844e6c79baba1afbb4b95e46827ad15

This is great news! Just curious; how many iterations does it go through to look for nesting? In my internal scripts I go three-deep, because I didn't find any instances where there were groups more nested than that.

Hi @grahampugh!
My implementation is quite naive: I am looking for Computer Groups or Mobile Device Groups where the value is a "member of" a particular Smart Group. Anything that matches is deemed linked / in-use.
Example where all Smart Groups are linked / in-use (more or less the same as my unit tests):

Smart Group 1: Random criteria, in scope of multiple policies
Smart Group 2: Criteria is Name "Computer Group" type "member of" value "Smart Group 3"
Smart Group 3: Criteria is Name "Computer Group" type "member of" value "Smart Group 2"

Example where Smart Group 3 is not linked / in-use:

Smart Group 1: Random criteria, not in scope of any policies
Smart Group 2: Criteria is Name "Computer Group" type "member of" value "Smart Group 1", in scope of multiple policies
Smart Group 3: Random criteria, not in scope of any policies

So in answer to to your question, 1 level deep? Am I missing some additional criteria / steps that I should be testing against?
Happy to be schooled educated by someone that might use Jamf Pro more than I do these days 😃

Ah, actually thinking about it, of course that's enough for finding unused groups. I was thinking about the scripts that I wrote for copying a group or policy to a new Jamf instance with all its dependencies - completely different thing! Sorry, pre-coffee nonsense.


⚠ Nebulance has degraded performance

In b6922f0, Nebulance ($NBL) experienced degraded performance:

HTTP code: 200
Response time: 1419 ms

Resolved: Nebulance performance has improved in 09ae9a5 after 10 minutes.


frontend :fix look of import and export

we need to rewrite code for frontend part:
in this issue we can fix the look of import and export button like this

hi @Fuji-P
Yes sure. I will update the README as soon as possible. There I will mention all the steps to set up this project :)

@Fuji-P  check this out

@vivekiet22
npm start dev→send→Connection was refused by the server.

@Fuji-P Can you tell me what error it shows on the console?

@Fuji-P , Run npm i nodemon and then try npm run dev command again.
if any other error occurs please send the error message :)

Hi @Fuji-P ,
I have deployed the project. You can access those from here or you can check the about section of this repo.


IFF - Can't parse file

I found a sample iff file that from what I read can be opened with Photoshop, but DPaint-js produces random pixels instead.
I don't have PhotoShop so I could not see the expected output.

Deluxe Paint can't open that file as well. (I guess software from the early 90's also isn't supposed to open 3840x5760 24 bit images :-) )
PhotoShops IFF implementation is - I assume - mostly targeted towards Maya.
it certainly is not compatible with anything Deluxe Paint related. (Photoshop can't read Deluxe Paint IFF files and vica versa)
I'll take a quick look what causing it, but as IFF is by design a container format where every program can define it own chunks, it's probably Photoshop specific, and probable a bit out of scope.
But still ... could be easy to implement.

Oh Interesting! I didn't know Maya supported IFF.
Btw I was unable to find grayscale IFF files (these don't have a CMAP chunk and are usually 8 bpp or less from what I could read). Any idea where I could find or how to generate one?

Oh Interesting! I didn't know Maya supported IFF.
Btw I was unable to find grayscale IFF files (these don't have a CMAP chunk and are usually 8 bpp or less from what I could read). Any idea where I could find or how to generate one?
Couldn't Deluxe Paint V open IFF-24 pictures? I thought so. I'll dig up my original CD to find out.

Yes Deluxe Paint V can open IFF-24 bit pictures (and so can dpaint.js)
But this is not a standard one.

Interestingly, some Amiga 24-bit image editors open it with the exact same garbled pixels as dpaint.js, so at least there's some consistency. :-)

And double interestingly: if the latest IFF datatypes are installed, multiview on Amiga CAN open it ... (and surprisingly fast)

OK, I'm intrigued.
Time is limited this week, but I'll figure it out next week.

Hmm.. that's interesting.
ffmpeg also outputs garbage. I wrote an ILBM decoder for SerenityOS: I'll
see what happens there.
Nicolas RAMZ - http://www.warpdesign.fr/
AthenaJS - https://athenajs.github.io
On Mon, Jun 24, 2024 at 1:24 PM Steffest @.***> wrote:

Yes Deluxe Paint V can open IFF-24 bit pictures (and so can dpaint.js)
But this is not a standard one.
image.png (view on web)
https://github.com/steffest/DPaint-js/assets/763047/d60241d4-b98b-4c79-8673-7232e3cfba48
Interestingly, some Amiga 24-bit image editors open it with the exact same
garbled pixels as dpaint.js, so at least there's some consistency. :-)
image.png (view on web)
https://github.com/steffest/DPaint-js/assets/763047/f3039cab-6400-482e-a59a-57144074f494
And double interestingly: if the latest IFF datatypes are installed,
multiview on Amiga CAN open it ... (and surprisingly fast)
image.png (view on web)
https://github.com/steffest/DPaint-js/assets/763047/3a705213-7771-4f82-aa61-3afd5af8c211
OK, I'm intrigued.
Time is limited this week, but I'll figure it out next week.
—
Reply to this email directly, view it on GitHub
https://github.com/steffest/DPaint-js/issues/27#issuecomment-2186343519,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABQXYCA42OC77KGETJAZZ3ZI76XFAVCNFSM6AAAAABJYXQ7B6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWGM2DGNJRHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

That may be a hint: some 24bit ILBM files may be encoded using a different
ordering:
R7 G7 B7 R6 G6 B6 R5 G5 B5 R4 G4 B4 R3 G3 B3 R2 G2 B2 R1 G1 B1 R0 G0 B0
instead of
R0-R7,G0-B7,B0-B7
Nicolas RAMZ - http://www.warpdesign.fr/
AthenaJS - https://athenajs.github.io
On Mon, Jun 24, 2024 at 2:48 PM Nicolas Ramz @.***> wrote:

Hmm.. that's interesting.
ffmpeg also outputs garbage. I wrote an ILBM decoder for SerenityOS: I'll
see what happens there.
Nicolas RAMZ - http://www.warpdesign.fr/
AthenaJS - https://athenajs.github.io
On Mon, Jun 24, 2024 at 1:24 PM Steffest @.***> wrote:

Yes Deluxe Paint V can open IFF-24 bit pictures (and so can dpaint.js)
But this is not a standard one.
image.png (view on web)
https://github.com/steffest/DPaint-js/assets/763047/d60241d4-b98b-4c79-8673-7232e3cfba48
Interestingly, some Amiga 24-bit image editors open it with the exact
same garbled pixels as dpaint.js, so at least there's some consistency. :-)
image.png (view on web)
https://github.com/steffest/DPaint-js/assets/763047/f3039cab-6400-482e-a59a-57144074f494
And double interestingly: if the latest IFF datatypes are installed,
multiview on Amiga CAN open it ... (and surprisingly fast)
image.png (view on web)
https://github.com/steffest/DPaint-js/assets/763047/3a705213-7771-4f82-aa61-3afd5af8c211
OK, I'm intrigued.
Time is limited this week, but I'll figure it out next week.
—
Reply to this email directly, view it on GitHub
https://github.com/steffest/DPaint-js/issues/27#issuecomment-2186343519,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABQXYCA42OC77KGETJAZZ3ZI76XFAVCNFSM6AAAAABJYXQ7B6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWGM2DGNJRHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Feature: compressed performance budgets 🎉

Hello!
Webpack has a great performance budgeting feature that tracks whether chunks or entry modules exceed a size limit. The one missing piece for folks like me is that bundle size is generally measured in terms of bytes-over-the-wire, and generally that means compressed size.  I took the opportunity to build on @TheLarkInn's awesome work, adding gzipped size calculations to the performance feature.  The result is that performance budgetings are measured against compressed size, which matches up nicely with Alex's original blog post on the subject.
What kind of change does this PR introduce?
A new feature.
Did you add tests for your changes?
I updated the tests to reflect the changes.
Does this PR introduce a breaking change?
No.
What needs to be documented once your changes are merged?
Just the new configuration property and default values.

This could interest @addyosmani

@developit This looks really good. I think it'd work really well with my PR as well (after solving conflicts that is)! https://github.com/webpack/webpack/pull/7769

I'm 100% supportive of this change.

Really keen about this change getting merged. Thanks for the hard work.

@developit could we address the conflicts in this PR?
@TheLarkInn would be great to get your gut-check on the feasibility of this change landing once Jason tackles the above.. :)

@sokra Is there interest in landing this change?


Docker development

Doing tasks from here

@VsIG-official
Should we have two different containers and merge this branch or rewrite to one and merge it?

@mezgoodle
I think, that We need to leave it, as it is now. Maybe in future We will do the same for Discord-Bot and Application and separate docker files would be nice, in My opinion

Yeah, as for some users, who wants have separate apps as containers


Improve AI topics for nextflow workflows

Description
Improve AI topics for nextflow workflows by using the main script content as the primary descriptor instead of the nextflow.config.
I have also added a url column to the output CSV file that contains the raw GitHub url of the descriptor file used to generate the topics so that we can easily view the descriptor content.
This PR re-generates the AI topics for all entries, so you will see changes for all rows in the results file. I have highlighted the rows that contain Nextflow workflows.
Review Instructions
Not user-facing, no review instructions
Issue
dockstore/dockstore#5748
DOCK-2495
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that you pass the basic style checks and unit tests by running mvn clean install in the project that you have modified (until https://ucsc-cgl.atlassian.net/browse/SEAB-5300 adds multi-module support properly)
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] If you are changing dependencies, check with dependabot to ensure you are not introducing new high/critical vulnerabilities
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

Looks good. If we're at all concerned about cost, might include a hash of the input in the output CSV so that we can avoid regenerating next time if the content hasn't changed.

I added the file checksum to the output CSV. I didn't implement checking the checksum because I don't think we're quite there yet, but the info is there for when we are


Sway should have options to accept a vendor specific swagger schema

Why am I asking this?
We have developed our (vendor) extensions and have added that to the swagger schema. We want to take advantage of the z-schema validator.
This is the link to our swagger schema with extensions.
How it will benefit the community?
It would be nice if Sway would provide an option

to accept a different swagger schema than the one it is using right now.
to set remote references for the external schemas used in our scehma. This is required by the z-schema validator.

If Sway can expose the validator so that customers can add external references to it then that would be fine as well.

If nothing is provided then by default Sway will use the current one it is using right now.
This will help us take advantage of the z-schema validator. I tried playing with it by locally modifying couple of lines in the validator.js and helper.js and it worked like a charm. The tool was not giving any warnings for our extensions and it also threw an error when i tried to use an extension incorrectly.
What do you think about this?

I'm not sure I want to support custom Swagger documents.  I'm not completely against it but since we already give you APIs for registering custom validators and will soon have an API for registering custom format validators and  an API for registering custom format generators, is there really a need for this?

Open-API allows us to provide extensions on any part/artifact of the swagger spec. The extensions are not limited to being used for "types" and "formats".
For example: we have an extension to describe a "long-running/asynchronous" operation and an extension to describe a "pageable" operation. We also have an extension for specifying examples.
All the extensions are described/added in the swagger schema which was derived from the actual swagger schema.
I believe, exposing an option to add a custom schema will only add value. The default behavior would still be the original swagger schema. If the customer is using his/her custom schema then he/ she would be responsible for any undesired outcome. Sway is no way responsible for anything over there.
By providing a mechanism to add the custom schema, we get the z-schema validation for free. It reduces an extra pass of validation in the end.
I am sure you would have valid concerns as you know the tool better than anyone else. If possible can you please list those concerns? This will help us better understand the tool.

The point I made is that sway already has an API to register custom validators, so validations for custom extensions and other stylistic checks that are not covered by the Swagger specification itself.  I'm not saying sway doesn't support custom Swagger documents, I'm saying that all extension support Swagger supports sway does, other than the two open issues.
What isn't working like you want?  If you are using vendor extensions, just register a custom validators to perfo m the validation you want.

To me, I read your request as you saying you've taken the JSON Schema file from Swagger, altered it and want sway to read it in as the JSON Schema for Swagger.  If that's the case, that is not a supported Swagger approach.
I'm going to get @webron's eyes on this too.

Yup I was looking at that. We do like that in our CI.
First set all the remote references and then
Validate the spec against the schema.
I want to start using Sway in our CI. It is definitely a value add. I was thinking if I can do the structural and semantic validation in one pass then that would be awesome. Hence filed an issue with the request.

We are not modifying the swagger schema in any way, as that would be against the rules. We are simply adding schema for our extensions so folks in Azure get intellisense experience for the custom extensions and can get validation errors if they are used incorrectly.

So what doesn't work like you want?  If you can register a custom validators for the document, what is missing?  I'm missing something or overlooking it in your original message.

I am sorry. I replied to your second comment.

To me, I read your request as you saying you've taken the JSON Schema file from Swagger, altered it and want sway to read it in as the JSON Schema for Swagger. If that's the case, that is not a supported Swagger approach.

Yes, I meant that. We have not altered the schema. We have simply extended it to add schema for our custom extensions. Then I gave an example of how we are doing it in our CI.
//Setting the remote references
validator = new z({ breakOnFirstError: false });
var valid = validator.validate(parsedData, extensionSwaggerSchema); // our version of the swagger schema
var error = validator.getLastErrors();

The above code is very similar to what is happening in Sway at

instantiating the validator

[helper.js L104 - var validator = new ZSchema({
    breakOnFirstError: false,
    ignoreUnknownFormats: true,
    reportPathAsArray: true
  });](https://github.com/apigee-127/sway/blob/master/lib/helpers.js#L104)

actual validation

[helper.js L443 - if (!validator.validate(value, schema)) {
    response.errors = _.map(validator.getLastErrors(), function (err) {
      normalizeError(err);

      return err;
    });
  } in validateAgainstSchema()](https://github.com/apigee-127/sway/blob/master/lib/helpers.js#L443).

It's an interesting situation. Sway, as far as I understand, allows you to provide custom code validations (and uses some of its own), but at the core uses a JSON Schema to validate the spec.
@amarzavery is asking for a way to use an altered (sorry, @amarzavery, any kind of mutation is altering, even if just adding) version of the schema to validate additional vendor extensions added within the scope of Azure (which is exciting!).
I get why @whitlockjc is a bit wary of this because that's a core functionality and there's a way to extend validations. I imagine you can even write a custom validator that would run against the altered JSON Schema and provide the same feedback, but a - it would come at a performance cost (especially if it's all the schema and not just the added extensions) and b - it would serve as a maintenance burden for the user. I'd say it could be an advanced feature that Sway provides, but I can't say whether it's something Sway should provide or not.
That's my 2c :)

Well, I'm not interested in supporting custom Swagger documents primarily because that is not the way to extend Swagger.  Swagger supports vendor extensions to extend Swagger without the need to customize its core JSON Schema.  On top of that, Sway has support for registering custom validators which will let you validate these vendor extensions any any other stylistic things you'd gain by modifying the Swagger JSON Schema.
To me, it just doesn't seem necessary and I just don't think extending Swagger this way makes sense.

@whitlockjc I believe they are using vendor extensions, they're just using a modified json schema to validate their own vendor extensions. Azure specs are by all means valid Swagger specs - they're not customizing it beyond.

I didn't see mention of vendor extensions being used, that's why I suggested them.  Regardless, Sway allows you to write your own validators and they can validate anything you want them to, including vendor extensions.


Unable to run the server.js

Following this for testing an open AI plugin  MS documentation:
https://learn.microsoft.com/en-us/copilot-plugins/get-started
referred  https://github.com/MicrosoftDocs/mslearn-copilot-plugins/tree/main/contoso-real-estate for cloning the code.
After cloning, following Readme , installed modules, and then trying to run the
Get this error on node server.js
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".json" for C:\Users\vinjamos\OneDrive - Jabil\Desktop\Copilot\plugin samples\M365 OpenAIAPI\mslearn-copilot-plugins\contoso-real-estate\listings.json    at new NodeError (node:internal/errors:371:5)
at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:87:11)
at defaultGetFormat (node:internal/modules/esm/get_format:102:38)
at defaultLoad (node:internal/modules/esm/load:21:14)
at ESMLoader.load (node:internal/modules/esm/loader:359:26)
at ESMLoader.moduleProvider (node:internal/modules/esm/loader:280:58)
at new ModuleJob (node:internal/modules/esm/module_job:66:26)
at ESMLoader.#createModuleJob (node:internal/modules/esm/loader:297:17)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:261:34)
at async ModuleWrap. (node:internal/modules/esm/module_job:81:21) {
code: 'ERR_UNKNOWN_FILE_EXTENSION'
}
Tried  node --experimental-json-modules server.js but just get a warning but doesn't execute.

Closing it , because it seems like the localhost:8080 actually is running even with the error and I do get response when hitting something like http://localhost:8080/get-listings?city=Atlanta.

That's odd. I don't understand where this error could be coming from.
Good to know that it's working anyway. But it would be good to fix the error still. When does it occur exactly? Right when you start the server with node server.js? Or later when you access the API via your browser?
What version of Node.JS are you using?

It happens on node server.js .. when I run the node --experimental-json-modules server.js  , I get a warning
node:51172) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
(Use node --trace-warnings ... to show where the warning was created)
I updated my node version to latest and now I don't have to pass the -experimental-json-modules and just use node server.js . it runs but i still see the warning
ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
(Use node --trace-warnings ... to show where the warning was created)

Oh I see. This warning occurs because of this line of code:
import listings from "./listings.json" assert { type: "json" };
This makes it possible to read JSON data without having to first fetch it and parse it. Instead, you can just import it like any other module, but with the addition of the assert statement.
This syntax is relatively new, and NodeJS prints a warning for people to know that it's still experimental.
That said, it's already at the stage 3 of the TC39 process, which means that the spec is complete and signed off. I think it's fairly safe to use, especially in a demo repo like this one, where we can always change it to something else, should the spec change.


Allow load tests to run with hostNetwork pods

To allow load tests to bypass CNI plugin.
/cc @wojtek-t @mm4tt

/lgtm
/approve


Dx 245 ambient temp

Add ambient temperature state

Let's chat with Alex, but I'm pretty sure we shouldn't default temp values to any numerical value. These should probably show up as null if for some reason it's not available.

This is a good discussion topic. We have to consider the data types carefully at this level since this SDK is more concerned about parsing and encapsulating device data directly from the platform but not concerned about what shows up at the UI level.
For example, we should agree on whether to use nullable variables or not to represent things like Temperature set point. Once we agree on the approach, we can cascade null values safely to the device-widgets SDK and handle those null values in a general way.


Add 23 technologies blogs

How to categorize this PR?

/area documentation
/kind enhancement
What this PR does / why we need it:
This PR adds the 23Technoloies blogs to the public website.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

NONE

Why do we copy the content? We should rather add links to their blogs and not duplicate it?

Why do we copy the content? We should rather add links to their blogs and not duplicate it?

23Technologies have stated that they want to handover their documentation to us, so that we are responsible for maintaining it.

I will look for a suitable place to reference the blog posts. As such, I will be closing this PR.


Bytea, HStore and JSONB columns?

I'm using Rust Nightly so that I could us the diesel codegen. Problem is that I get:
<diesel macros>:36:1: 36:47 note: in this expansion of column! (defined in <diesel macros>)
<diesel macros>:15:1: 17:58 note: in this expansion of table_body! (defined in <diesel macros>)
<diesel macros>:5:1: 6:2 note: in this expansion of table! (defined in <diesel macros>)
<diesel macros>:2:1: 2:64 note: in this expansion of table! (defined in <diesel macros>)
src/schema.rs:2:1: 2:40 note: in this expansion of table! (defined in <diesel macros>)
src/lib.rs:11:1: 11:23 note: in this expansion of include!
src/lib.rs:1:1: 1:1 help: run `rustc --explain E0412` to see a detailed explanation
src/lib.rs:1:1: 1:1 help: no candidates by the name of `Bytea` found in your project; maybe you misspelled the name or forgot to import an external crate?
src/lib.rs:1:1: 1:1 error: type name `Bytea` is undefined or not in scope [E0412]
src/lib.rs:1 #![cfg_attr(feature = "nightly", feature(custom_derive, custom_attribute, plugin))]

<diesel macros>:15:1: 17:58 note: in this expansion of table_body! (defined in <diesel macros>)
<diesel macros>:5:1: 6:2 note: in this expansion of table! (defined in <diesel macros>)
<diesel macros>:2:1: 2:64 note: in this expansion of table! (defined in <diesel macros>)
src/schema.rs:2:1: 2:40 note: in this expansion of table! (defined in <diesel macros>)
src/lib.rs:11:1: 11:23 note: in this expansion of include!
src/lib.rs:1:1: 1:1 help: run `rustc --explain E0412` to see a detailed explanation
src/lib.rs:1:1: 1:1 help: no candidates by the name of `Hstore` found in your project; maybe you misspelled the name or forgot to import an external crate?
src/lib.rs:1:1: 1:1 error: type name `Hstore` is undefined or not in scope [E0412]
src/lib.rs:1 #![cfg_attr(feature = "nightly", feature(custom_derive, custom_attribute, plugin))]
             ^
<diesel macros>:36:1: 36:47 note: in this expansion of column! (defined in <diesel macros>)
<diesel macros>:15:1: 17:58 note: in this expansion of table_body! (defined in <diesel macros>)
<diesel macros>:5:1: 6:2 note: in this expansion of table! (defined in <diesel macros>)
<diesel macros>:2:1: 2:64 note: in this expansion of table! (defined in <diesel macros>)
src/schema.rs:2:1: 2:40 note: in this expansion of table! (defined in <diesel macros>)
src/lib.rs:11:1: 11:23 note: in this expansion of include!
src/lib.rs:1:1: 1:1 help: run `rustc --explain E0412` to see a detailed explanation
src/lib.rs:1:1: 1:1 help: no candidates by the name of `Hstore` found in your project; maybe you misspelled the name or forgot to import an external crate?
src/lib.rs:1:1: 1:1 error: type name `Jsonb` is undefined or not in scope [E0412]
src/lib.rs:1 #![cfg_attr(feature = "nightly", feature(custom_derive, custom_attribute, plugin))]
             ^
<diesel macros>:15:1: 17:58 note: in this expansion of table_body! (defined in <diesel macros>)
<diesel macros>:5:1: 6:2 note: in this expansion of table! (defined in <diesel macros>)
<diesel macros>:2:1: 2:64 note: in this expansion of table! (defined in <diesel macros>)
src/schema.rs:2:1: 2:40 note: in this expansion of table! (defined in <diesel macros>)
src/lib.rs:11:1: 11:23 note: in this expansion of include!
src/lib.rs:1:1: 1:1 help: run `rustc --explain E0412` to see a detailed explanation
src/lib.rs:1:1: 1:1 help: no candidates by the name of `Jsonb` found in your project; maybe you misspelled the name or forgot to import an external crate?
src/lib.rs:1:1: 1:1 error: type name `Jsonb` is undefined or not in scope [E0412]
src/lib.rs:1 #![cfg_attr(feature = "nightly", feature(custom_derive, custom_attribute, plugin))]
             ^

Is there a way to just "ignore" those columns?

Bytea should be working fine in 0.6.1.
To answer your more general question, there's no way to ignore them, but you can call the table! macro directly for those tables, and then call infer_table_from_schema! for the rest of the tables, instead of infer_schema!

Closing this as there's nothing actionable. If this didn't sufficiently answer your question, feel free to ping me here or in gitter (and if Bytea isn't working in 0.6.1 that is definitely a bug)

Were you ever able to confirm that at least Bytea was working correctly for you?

@sgrif it works!
Still missing JSONB and HSTORE :(

:+1: Yeah, need to add support for those types (will likely be a separate crate actually). Still unresolved questions, but if you're interested in working on it let me know and I'd be happy to help. Tracking issue: https://github.com/diesel-rs/diesel/issues/44


Add config validation for Citadel deployment.

Describe the feature request
This is motivated by https://github.com/istio/istio/issues/13354, where there are two Citadels running in one cluster, and those two Citadels are not properly configured which causes a race condition. One Citadel keeps overwriting workload certificates generated by the other, and vise versa.
To avoid such kind of issue, we could enhance our config validation at Galley to guarantee that
(1) Only one Citadel will be deployed in a cluster; and
(2) If multiple Citadels are deployed, command flags --read-signing-cert-only and --server-only are properly set.
It is also recommended to deploy one Citadel per cluster, as Citadel is not running in a critical path. Unless there are special needs, one Citadel is sufficient to provision certificates for all workloads.

https://github.com/istio/istio/pull/13519

Regarding to "enhance our config validation at Galley to guarantee that (1) Only one Citadel will be deployed in a cluster; and (2) If multiple Citadels are deployed, command flags --read-signing-cert-only and --server-only are properly set.", currently Galley only validates CRD and doesn't do validation at the deployment level.

Given #13519, can we close this issue or is there more work we want to do?

Closing this issue sounds good to me.


Fix nav-tabs on small screens

Prevent items from overflowing to next line, add scrolling behavior instead.

Codecov Report

Merging #108 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #108   +/-   ##
=======================================
  Coverage   62.96%   62.96%
=======================================
  Files          20       20
  Lines         243      243
=======================================
  Hits          153      153
  Misses         90       90

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 10aeb37...085d076. Read the comment docs.


Building wheel for llama-cpp-python (pyproject.toml) did not run successfully.

Expected Behavior
Able to select llama-cpp-python binding without errors
Current Behavior
Building wheels for collected packages: llama-cpp-python
Building wheel for llama-cpp-python (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for llama-cpp-python (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [72 lines of output]
-- Trying 'Ninja' generator
Not searching for unused variables given on the command line.
-- The C compiler identification is unknown
CMake Error at CMakeLists.txt:3 (ENABLE_LANGUAGE):
No CMAKE_C_COMPILER could be found.
    Tell CMake where to find the compiler by setting either the environment
    variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
    the compiler, or to the compiler name if it is in the PATH.

  -- Configuring incomplete, errors occurred!
  -- Trying 'Ninja' generator - failure
  -- Trying 'Unix Makefiles' generator
  CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.Not searching for unused variables given on the command line.

  -- Configuring incomplete, errors occurred!
  -- Trying 'Unix Makefiles' generator - failure
  --------------------------------------------------------------------------------

                  ********************************************************************************
                  scikit-build could not get a working generator for your system. Aborting build.

                  Building Linux wheels for Python 3.10 requires a compiler (e.g gcc).
  But scikit-build does *NOT* know how to install it on ubuntu

  To build compliant wheels, consider using the manylinux system described in PEP-513.
  Get it with "dockcross/manylinux-x64" docker image:

    https://github.com/dockcross/dockcross#readme

  For more details, please refer to scikit-build documentation:

    http://scikit-build.readthedocs.io/en/latest/generators.html#linux

                  ********************************************************************************
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for llama-cpp-python
Failed to build llama-cpp-python
ERROR: Could not build wheels for llama-cpp-python, which is required to install pyproject.toml-based projects
Steps to Reproduce
Please provide detailed steps to reproduce the issue.

Launch Ubuntu-22.04 WSL
run git clone ...
cd into gpt4all-ui
./setup.sh
Browse to <IP_ADDRESS>:9600
Click Settings
Click Binding zoo
Click llama_cpp_official

Possible Solution
Add warning in description to binding, that c compiler and make are required
Context
Please provide any additional context about the issue.
Screenshots
If applicable, add screenshots to help explain the issue.

I found a possible solution....
activate environment using the scripts directory sh file
when environment is active install Llama_cpp from wheel V1.49
pip install https://github.com/abetlen/llama-cpp-python/releases/download/v0.1.49/llama_cpp_python-0.1.49-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Go to the releases to find the relevant arch wheel if needed.
Rerun the webui.sh file to start the site


ST board Id: Alignment with mbed-os-tools v1.8.6

Alignment with mbed-os-tools v1.8.6

Same action done in mbed-os-tools: https://github.com/ARMmbed/mbed-os-tools/pull/262
@JeanMarcR


Max Sessions

Any way to limit the maximum number of simultaneous sockets...so not to tax a server?

-maxforks= is there but apparently not in help... will keep ticket open to fix that.

Thanks! That works perfectly.


Change text in 'step 3' on How we work

Make it more immediate and operational. Something like:
Humanitarian organisations are using the map data to respond to disease outbreaks and disasters, and to plan risk reduction which saves lives.

@pedrito1414

Modified the text slightly to keep it in the present tense.

Thanks!


Updated Version of Tagging Tool

I have updated the tagging tool so that the image displayed has the full image size.
Noticed while tagging that 500px may not be sufficient while tagging
Please review the new commit: tagging_tool.py
e.g. Now it looks like this:

Enlarging image size helps for sure.
Is the image a little too close to the choices? Can you change it to "<style> img { max-width: 98%; height: auto; } </style>" to add some margins?

Do you want to try to center crop?

Enlarging image size helps for sure. Is the image a little too close to the choices? Can you change it to "<style> img { max-width: 98%; height: auto; } </style>" to add some margins?

Yes, let me edit and try that.

Do you want to try to center crop?

I wonder why would we want to do that. We did that for model training, but for actual tagging, I do not see the motivations here.

Now it has been updated


Refactor existing HuggingFace support to a more robust one

Current status: WIP
The PR motivation started from this issue: #1018
What this PR do?
We have an existing HuggingFace model integration on DsPY. However developers can not use this class with much flexibility. So the goal of the PR is to provide a balanced abstraction such that developers can

add their own model object
or add just different configs and arguments while instantiating, example: quantization_config, lora_config directly in the dspy.HF class
make it also directly compatible with the finetuning procedures (might not be applicable now)

The reason is, HuggingFace is very popular for sometimes writing out entire lifecycle. So writing entre pipelines with huggingface and dspy might need to have almost all the supported configs and HF's own addons (like bitsandbytes, peft etc), so that they can focus more on dspy instead of finding wayaround on how to add this or that with dspy huggingface.
Todos

[X] Initial working draft implementation
[X] Testing the implementation passing HF models object
[X] Testing the implementation passing HF models object as string
[X] Testing the implementation passing HF models with quantization support
[ ] Testing the implementation passing HF models with multi-gpu support (currently not have multi gpu settings)
[ ] Refine the code (check once more, typos, check on some todos I wrote inside the code etc)
[ ] Write good tutorial like documentation for this
[ ] Fininshing (link etc)

cc: @okhat, let's discuss more about this approach and feel free to provide feedbacks :)

Hi would love to get your thoughts on this, so that according to the feedbacks I can move forward. Thanks
cc: @arnavsinghvi11

Current status: WIP
The PR motivation started from this issue: #1018
What this PR do?
We have an existing HuggingFace model integration on DsPY. However developers can not use this class with much flexibility. So the goal of the PR is to provide a balanced abstraction such that developers can

add their own model object
or add just different configs and arguments while instantiating, example: quantization_config, lora_config directly in the dspy.HF class
make it also directly compatible with the finetuning procedures (might not be applicable now)

The reason is, HuggingFace is very popular for sometimes writing out entire lifecycle. So writing entre pipelines with huggingface and dspy might need to have almost all the supported configs and HF's own addons (like bitsandbytes, peft etc), so that they can focus more on dspy instead of finding wayaround on how to add this or that with dspy huggingface.
Todos

[x]  Initial working draft implementation
[x]  Testing the implementation passing HF models object
[x]  Testing the implementation passing HF models object as string
[x]  Testing the implementation passing HF models with quantization support
[ ]  Testing the implementation passing HF models with multi-gpu support (currently not have multi gpu settings)
[ ]  Refine the code (check once more, typos, check on some todos I wrote inside the code etc)
[ ]  Write good tutorial like documentation for this
[ ]  Fininshing (link etc)

cc: @okhat, let's discuss more about this approach and feel free to provide feedbacks :)

Hi just wanted to check on whether we can move forward with this PR or not, else we can close it. Thanks :)

Hi @Anindyadeep , thanks for this PR refactor of HF! This looks great!
I anticipate this PR will eventually replace hf.py so it would be great to either build on the existing file if possible. It would also be easier to understand what’s being retained and any additional differences. Following the leftover todos and testing, let me know if you have any comments/additions to review.
Looking forward to the next stage of this PR!

Hi @Anindyadeep , thanks for this PR refactor of HF! This looks great!
I anticipate this PR will eventually replace hf.py so it would be great to either build on the existing file if possible. It would also be easier to understand what’s being retained and any additional differences. Following the leftover todos and testing, let me know if you have any comments/additions to review.
Looking forward to the next stage of this PR!

Hey thanks for the reply, on a second though I feel this PR is a very big addition so in that case, I could re-start from the PR implementation, where I can break into smaller parts (which could be easier for you all as well for review) and doing changes from hf.py. Does that sounds good to you?

Hi @Anindyadeep , thanks for this PR refactor of HF! This looks great!
I anticipate this PR will eventually replace hf.py so it would be great to either build on the existing file if possible. It would also be easier to understand what’s being retained and any additional differences. Following the leftover todos and testing, let me know if you have any comments/additions to review.
Looking forward to the next stage of this PR!

Hey thanks for the reply, on a second though I feel this PR is a very big addition so in that case, I could re-start from the PR implementation, where I can break into smaller parts (which could be easier for you all as well for review) and doing changes from hf.py. Does that sounds good to you?

Let me know your thoughts @arnavsinghvi11 whenever you find some bandwidth, thanks :)

I could re-start from the PR implementation, where I can break into smaller parts (which could be easier for you all as well for review) and doing changes from hf.py. Does that sounds good to you?

Yes that would be great!

Excellent effort here! Tagging @dilarasoylu and @isaacbmiller

I wonder how much of this can we delegate to an opinionated tool like axotol or torchtune or something btw?

I wonder how much of this can we delegate to an opinionated tool like axotol or torchtune or something btw?

Well, it depends, I mean sure, we can go for axotol or torchtune, but then it would be less coupled with native hf scripts imo. However let me know what do you think on this and we can go accordingly.

My only goal is to support most useful models & quantization settings & loss functions (DPO etc) with as little code as possible. Do you think HF is still the best path for that?

If HF is still best, let's stick to it! Thanks for the amazing work here @Anindyadeep !

My only goal is to support most useful models & quantization settings & loss functions (DPO etc) with as little code as possible. Do you think HF is still the best path for that?

 (Putting it into draft now)


RTCConnection.onopen not fired

Hey,
after doing some connection tests, I run into the following issue:
I've tried to call my Android 6.0 device via Mac (Cordova + Chrome).  Calling the smartphone from the Mac worked fine without problems. It seems like there is an issue if we change initiator and receiver too often? There are no error logs in the console. The only thing I know is that
RTCConnection.onopen

wasn't fired (because it will show a call dialog).

My fault, I had opened 2 tabs...


nbdev_export does not export functions to none-default python module

nbdev version: v2.2.8
I want to export a function to a python module other than the default_exp. In nbdev v1, it can be achieved by # export [python_module].
However, I cannot do the same in v2.
To reproduce my error
My code repo: https://github.com/BirkhoffG/cfnet/tree/344a29ba4aed065abb3337ab45599e4b20b1927d

I want to export make_model and init_net_opt written in nbs/03_training_module.ipynb into cfnet/utils.py.
nbdev_export
These functions are not exported to the desired locations (i.e., cfnet/utils.py).

Dupe of #742


Make unionCondition public

The function is useful outside of StatusSyncer controller. Added two flavors, depending if the caller needs OperatorCondition or
ClusterOperatorStatusCondition.

/assign @deads2k

/lgtm


Is it possible to make it work on a private network with arcgis portal for arcgis server

I'm trying to make this work on a private network with no connection to the internet. Is this possible?

Absolutely, Map Tour is included with Portal for ArcGIS starting at version 10.2.1.
If you are using an earlier version you will find the information in the FAQ.
The most recent version may not be compatible with the oldest version of Portal for ArcGIS. If you experience issue, please try to deploy Map Tour version 2.2.3 that should work.


Allow allow-2119 on an ancestor

Would be nice for the Infra Standard.

The "only on parent" thing is intentional right now; it avoids a document doing something like putting it on the root to silence the warning, and then accidentally adding bad 2119 usage and it doesn't get caught.

It would be nice if you didn't close issues until you heard back from the reporter. E.g., what if I suggested we allowed it on ancestors that also contained the class "example"?

That doesn't address my objection, it just makes it slightly less bad.  You can still put it on the example container to handle the one 2119 violation you see now, and then a later edit can introduce another violation that's now hidden.
(Theoretically this can happen even today - you could put it on a paragraph and then make the edit. But it's as tight as I can make it without requiring, say, the parent to contain only the 2119 keyword in question (that is, require may), which seems like too much of an annoyance.)


Cannot run bat files

Describe the bug
I've found this issue, but it's closed and marked as "Solved", but it's not.
I can't run my .bat files
To Reproduce
Steps to reproduce the behavior:

Double-Click on a '.bat' file
The file is not executed

Expected behavior
Execute the bat file
Desktop (please complete the following information):

OS Version: Windows 10 Pro 2004 19041.450
App version: v<IP_ADDRESS>

@Sav22999 Have you tried running them as administrator?

@yaichenbaum Ok, basically after I've executed it as administrator, it worked. And now works also without admin permissions.


ISSUE: Delviering Count

Describe the bug
For one package that is delivering then delivered, expecting in transit to reduce to 0 after delivery. sensor.mail_usps_packages, sensor.mail_packages_in_transit, sensor.mail_usps_delivering show unexpected numbers.
Environment (please complete the following information):

OS: [e.g. HassOS/Raspbian/CentOS]
Type of device: [e.g. RPi3/NUC/Synology]
Home Assistant version: [e.g. 0.105.5]
Hassio/Docker/Core?
Component version: [e.g. 0.1.2]

Logs
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 Item Delivered
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 Item Delivered results: b'284'
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Sensor: usps_delivering
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 Expected Delivery on
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Searching for Your item is out for delivery in 3 emails
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Debug: 1
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Found Your item is out for delivery in email matches: 1
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 Expected Delivery on results: b'282'
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Searching for tracking numbers for usps
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] No tracking number found for usps
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Info: {'count': 2, 'tracking': []}
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] info[ATTR_COUNT]: 2
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Delivered: 1
2020-07-25 23:19:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] total: 1

Screenshots
3 USPS Emails today. 1  Informed Delivery, 1 Expected Delivery, and 1 Delivered

Additional context

Sensor
Count

sensor.mail_packages_delivered
1

sensor.mail_packages_in_transit
1

sensor.mail_updated
Jul-25-2020 11:01 PM

sensor.mail_usps_delivered
1

sensor.mail_usps_delivering
1

sensor.mail_usps_mail
1

sensor.mail_usps_packages
2

Trying to follow the new code and figure out why this is returning a count of 2.
https://github.com/moralmunky/Home-Assistant-Mail-And-Packages/blob/6881c643c1b51fb0113fffb195cafd30bc7be15b/custom_components/mail_and_packages/sensor.py#L152
DEBUG: Info: {'count': 2, 'tracking': []}
I would expect it to be a count of 1 then when the delivered is subtracted in the next line it would be 0
https://github.com/moralmunky/Home-Assistant-Mail-And-Packages/blob/6881c643c1b51fb0113fffb195cafd30bc7be15b/custom_components/mail_and_packages/sensor.py#L153
DEBUG: total: 1

Is the 2 count that it found a delivering and a delivered?

Shouldn't be, I'll check it out in the morning.

Found the problem: found = pattern.findall(email_msg), I have adjusted it and about to commit a update now

Is this at all like https://github.com/moralmunky/Home-Assistant-Mail-And-Packages/issues/92 ?  Because I'm getting double counts again on my USPS sensors.  Just updated/restarted for 0.2.2-b14 and am getting 4x packages out for delivery but only 2 are...

Yes @FuzzyMistborn it's similar, but it should have been fixed.

Here's the debug:
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 Your package has been delivered
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 Your package has been delivered results: b''
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 Delivery scheduled for today
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 Delivery scheduled for today results: b''
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 2 Your package is scheduled for delivery today
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 2 Your package is scheduled for delivery today results: b''
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 Your UPS Package was delivered
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Searching for Tracking Number in 0 emails
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 Your UPS Package was delivered results: b''
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 UPS Update: Package Scheduled for Delivery Today
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 UPS Update: Package Scheduled for Delivery Today results: b''
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 2 UPS Update: Follow Your Delivery on a Live Map
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 2 UPS Update: Follow Your Delivery on a Live Map results: b''
2020-07-30 10:07:36 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 Item Delivered
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 Item Delivered results: b''
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 Expected Delivery on
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Searching for Your item is out for delivery in 7 emails
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] find_text Debug: <re.Match object; span=(1580, 1609), match='Your item is out for delivery'>
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Found Your item is out for delivery in email
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] find_text Debug: <re.Match object; span=(1580, 1609), match='Your item is out for delivery'>
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Found Your item is out for delivery in email
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 Expected Delivery on results: b'513 514'
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Searching for tracking numbers for usps
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] No tracking number found for usps
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Found usps tracking number in email: XXXXXXXXXXXXXXXXXXX
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Attempting to find Informed Delivery mail
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Cleaning up image directory: /config/images/mail_and_packages/
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Informed Delivery email found processing...
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Extracting image from email
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Removing duplicate images.
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Removing USPS announcement images.
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Image Count: 1
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Resizing images to 724x320...
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Creating array of image files...
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Generating animated GIF
2020-07-30 10:07:37 INFO (SyncWorker_2) [custom_components.mail_and_packages.sensor] Mail image generated.
2020-07-30 10:07:37 DEBUG (SyncWorker_2) [custom_components.mail_and_packages.sensor] Updated scan time: Jul-30-2020 10:07 AM

But here's what shows up in the sensor:

I did reboot this morning AFTER the emails were sent if that matters at all.

Oooof, I'm gonna adjust the debug messages a touch to make it easier too, lemmie see what i can dig up.

Ok.  And to clarify (now that I'm looking at my post) only one of the two tracking numbers shows up for the sensor.  Which is weird.

Also adding a few more debugs should help too

@FuzzyMistborn if you have time could you give this sensor.py a go?

Tried it, still seeing 4 packages in the sensor.
2020-07-30 11:30:17 ERROR (MainThread) [frontend.js.latest.202007160] https://smarthome.weyl.casa/frontend_latest/chunk.cf565e41b8a8dce0642a.js:133:204 TypeError: this.shadowRoot.querySelector(...) is null
2020-07-30 11:30:23 ERROR (MainThread) [frontend.js.latest.202007160] https://smarthome.weyl.casa/frontend_latest/chunk.cf565e41b8a8dce0642a.js:133:204 TypeError: this.shadowRoot.querySelector(...) is null
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 Your package has been delivered
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 Your package has been delivered results: b''
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 Delivery scheduled for today
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 Delivery scheduled for today results: b''
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 2 Your package is scheduled for delivery today
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 2 Your package is scheduled for delivery today results: b''
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 Your UPS Package was delivered
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Searching for Tracking Number in 0 emails
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 Your UPS Package was delivered results: b''
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 UPS Update: Package Scheduled for Delivery Today
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 UPS Update: Package Scheduled for Delivery Today results: b''
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 2 UPS Update: Follow Your Delivery on a Live Map
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 2 UPS Update: Follow Your Delivery on a Live Map results: b''
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 Item Delivered
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 Item Delivered results: b''
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 Expected Delivery on
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Searching for Your item is out for delivery in 7 emails
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] find_text Debug: <re.Match object; span=(1580, 1609), match='Your item is out for delivery'>
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Found Your item is out for delivery in email
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] find_text Debug: <re.Match object; span=(1580, 1609), match='Your item is out for delivery'>
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Found Your item is out for delivery in email
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 Expected Delivery on results: b'513 514'
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Searching for tracking numbers for usps
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] No tracking number found for usps
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Found usps tracking number in email:XXXXXXXXXXXXX2485
2020-07-30 11:32:45 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Attempting to find Informed Delivery mail
2020-07-30 11:32:46 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Cleaning up image directory: /config/images/mail_and_packages/
2020-07-30 11:32:46 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Informed Delivery email found processing...
2020-07-30 11:32:46 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Extracting image from email
2020-07-30 11:32:46 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Removing duplicate images.
2020-07-30 11:32:46 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Removing USPS announcement images.
2020-07-30 11:32:46 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Image Count: 1
2020-07-30 11:32:46 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Resizing images to 724x320...
2020-07-30 11:32:46 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Creating array of image files...
2020-07-30 11:32:46 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Generating animated GIF
2020-07-30 11:32:46 INFO (SyncWorker_1) [custom_components.mail_and_packages.sensor] Mail image generated.
2020-07-30 11:32:46 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.sensor] Updated scan time: Jul-30-2020 11:32 AM

Weird, and you restarted HA after placing the new file?

Tried the actual one (thanks for editing, I was driving myself crazy trying to figure out the differences).
Here's the log:
2020-07-30 12:24:56 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 (Your package has been delivered)
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 (Your package has been delivered) results: b'' count: 0
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 (Delivery scheduled for today)
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 (Delivery scheduled for today) results: b'' count: 0
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 2 (Your package is scheduled for delivery today)
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 2 (Your package is scheduled for delivery today) results: b'' count: 0
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 (Your UPS Package was delivered)
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Searching for (Tracking Number) in (0) emails
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Search for (Tracking Number) count results: 0
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 (Your UPS Package was delivered) results: b'' count: 0
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 (UPS Update: Package Scheduled for Delivery Today)
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 (UPS Update: Package Scheduled for Delivery Today) results: b'' count: 0
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 2 (UPS Update: Follow Your Delivery on a Live Map)
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 2 (UPS Update: Follow Your Delivery on a Live Map) results: b'' count: 0
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 (Item Delivered)
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 (Item Delivered) results: b'' count: 0
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject 1 (Expected Delivery on)
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Searching for (Your item is out for delivery) in (7) emails
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] find_text Debug: <re.Match object; span=(1580, 1609), match='Your item is out for delivery'>
2020-07-30 12:24:57 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Found (Your item is out for delivery) in email
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] find_text Debug: <re.Match object; span=(1580, 1609), match='Your item is out for delivery'>
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Found (Your item is out for delivery) in email
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Search for (Your item is out for delivery) count results: 2
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Search for<EMAIL_ADDRESS>with subject 1 (Expected Delivery on) results: b'513 514' count: 4
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Searching for tracking numbers for (usps)
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] No tracking number found for usps
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Found (usps) tracking number in email: (XXXXXXXXXXX2485)
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Attempting to find Informed Delivery mail
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Cleaning up image directory: /config/images/mail_and_packages/
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Informed Delivery email found processing...
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Extracting image from email
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Removing duplicate images.
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Removing USPS announcement images.
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Image Count: 1
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Resizing images to 724x320...
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Creating array of image files...
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Generating animated GIF
2020-07-30 12:24:58 INFO (SyncWorker_6) [custom_components.mail_and_packages.sensor] Mail image generated.
2020-07-30 12:24:58 DEBUG (SyncWorker_6) [custom_components.mail_and_packages.sensor] Updated scan time: Jul-30-2020 12:24 PM

and just to show there is a second package out today

I think I see where it's double counting. Give me a few.

This one should fix it for you completely. Likely to be b15 release for this. Thanks again for your help.

Bingo, back down to 2 packages.  Still only seeing 1 tracking number but that's a separate issue ;-)

Bingo, back down to 2 packages. Still only seeing 1 tracking number but that's a separate issue ;-)

Likely the tracking number didn't match the regex.
USPS_TRACKING_PATTERN = "9[24]\d{15,22}"
Should start 92 or 94 then 15-22 numbers after.

That'll do it, mine started with "93" (93001XXXXXXXXXXXX51760).

Interesting, I'll update the pattern.

Confirmed today received a package, all the counts lined up.


Respect trigEngine.

Hi!
There were some additions to luasnip, some time ago actually, where lua-pattern-triggers may now be defined via trigEngine. I think it would make sense to handle snippets where it is set to "pattern" like those where regTrig is set, the other predefined ones could (with lots of effort) be handled similarly, but I don't think that's really worth it.
For this to work, luasnip needs some so cmp_luasnip can tell whether a snippet has a lua-pattern as its trigger (because trigEngine is just some function, and I don't think it should be exposed)
I can implement this, but pretty busy right now, so will take some time.

Hiya - I'll have a look over the weekend :)


⚠ Bofrost.si has degraded performance

In 29844b4, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 5456 ms

Resolved: Bofrost.si performance has improved in 1bc264b after 6 minutes.


Update index.html

added 14 pixels as option for height
added 28 pixels as option for width

approved


[dv] refactor reggen for on-the-fly ral generation

refactored ral template to encapsulate classes within _ral_pkg
package

modified flow to generate above package in scratch area

removed hw/ip/uart/dv/env/uart_reg_block.sv and made associated
changes in that area to support this change

CAVEAT

Need to figure out how to insert this auto-generated pkg file as
dependency in fusesoc

currently, implemented a workaroud that hacks the fusesoc generated
filelist to insert the ral pkg ar the right place

Need to figure out how to insert this auto-generated pkg file as
dependency in fusesoc

Most likely fusesoc generators are the answer here. I can follow up with a more concrete example. Can you let me know how you'd like the core file to roughly look?

Hey Phil,
I would expect it to look something like this:
CAPI=2:

name: "lowrisc:dv:autogen_ral_pkg"
description: "Autogenerated UVM RAL package"

filesets:
  files_dv:
    depend:
      - lowrisc:dv:dv_lib
    files:
      - uart_ral_pkg.sv
    file_type: systemVerilogSource

targets:
  default:
    filesets:
      - files_dv

The assumption here is this core file would be placed along side the register package (in the scratch area).
Thanks
Sri

Hey Phil, I'll appreciate some help here. Thanks!

Closing this PR - I have opened #875 which re-creates this.


Is there a compelling reason to keep package name length to 50 characters or less?

https://github.com/bower/bower/blob/d405917b4a6efdeeb24a2087680fd4163896ab8e/packages/bower-json/lib/json.js#L144
A colleague ran into this today. I don't see any reason to make the package name so limited. NPM limits package names to 214 characters (which is such a weird number that I have to assume there's a strong reason for it): https://docs.npmjs.com/files/package.json

it's a magic number, one rarely needs more. one reason to limit length is because some systems (windows) have limit on path size (250 characters or so).

So why not make it the same as node? If it's arbitrary at least pick a
number that someone else in the same ecosystem picked.
On Wed, Mar 22, 2017, 2:49 PM Adam Stankiewicz<EMAIL_ADDRESS>wrote:

Closed #2440 https://github.com/bower/bower/issues/2440.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bower/bower/issues/2440#event-1011353315, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AArAAkUTf15rt1uUD_HYAReij_AowMjwks5roZdJgaJpZM4Mlu2L
.

I didn't pick it and there's not enough reason to change it

@sheerun that's wrong, Windows 10 removed that limit last year.


add 1.x case vid int case of lookup and index

Good job. what’s progress? any issue please let me know.


If I wanted to omit closed and resolved queries, how would I go about doing so.

Hello again,
This may be very simple but when I try to add AND [System.State] <> 'Closed' OR [System.State] <> 'Resolved'  like such:
{
"ObjectType": "VstsSyncMigrator.Engine.Configuration.Processing.WorkItemRevisionReplayMigrationConfig",
"Enabled": true,
"PrefixProjectToNodes": true,
"UpdateSoureReflectedId": false,
"QueryBit": "AND [System.State] <> 'Closed' OR [System.State] <> 'Removed' AND [ReflectedWorkItemId] = '' AND [System.WorkItemType] IN ('Shared Steps', 'Shared Parameter', 'Requirement', 'Task', 'User Story', 'Bug', 'Feature', 'Test Suite', 'Test Plan', 'Test Case')"
},
The application crashes while attempting to run it.  This is probably an easy fix but as I am still inexperienced a nudge in the right direction would be greatly appreciated.
Regards,
Jacques

@jaw2ay Are you happy to close this issue?

@MrHinsh apologies for the delay, yes feel free to close this issue.


#14762 - Migrate HTTP to the package model

Pull-request for issue #14762 created by @pasaperez-slingr
What it does?
Migrates the http endpoint to package.
How to test it?
Implement the flow steps of this package.
Implementation notes
There no implementation notes
Deployment notes
Register the package on Developer-Portal.

Merging so it is available in the release. Please update release notes.


Add supporting frameworks and configurations of them

:tada: This PR is included in version 0.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


don't show banner when tentative winner radio button is selected

don't show red banner when tentative winning outcome is selected.

it's same as market create Error.

the background looks off

I see the icon is off.


Facebook user's need to keep logging back in

User's that are logging in via Facebook seem to randomly become logged out even in the same session. There does not seem to be a pattern. Any idea why they keep need to keep logging back in?

Session handling is up your setup, once a user has loggedin using facebook, twitter, etc, it's up to django to keep the session, I don't see anything that could lead to the described behavior.

Any clue?

Still no idea.

The logout is on your site, right? Or the issue is that the token become invalid after a while?

Yes it's logging out on my site. Since it sometimes happens in the middle of an active session it makes me believe that it becomes invalid after awhile.
On Jan 20, 2012, at 4:48 PM, Matías Aguirre wrote:

The logout is on your site, right? Or the issue is that the token become invalid after a while?

Reply to this email directly or view it on GitHub:
https://github.com/omab/django-social-auth/issues/215#issuecomment-3591184