Allow setting subdivisions in calibration raster layout

So I've been setting up my projector setup anew this weekend, in a more permanent way. I  have what is probably the most pathological setup that is possible; see pictures below. Not only is my projector mounted off-center in both X and Y axis directions (by an extreme amount in the X), it is also rotated around the Z axis (although I will print a new, hinged mount for my projector so I can fix this last issue in meatspace rather than software) and the Z distance (i.e. distance between lens and cutting mat) is only just within the manufacturer recommended distance, and then only because I project at an angle. And all of this with a 80 euro Yoton Y3 projector.
Despite all of that - it works great! The projection matrix is so extreme that I have to go into full screen mode to be able to move my top left corner enough (look at the distortion in that last pic down below!), but when I do that it's all spot on! And the moving of the corners with the keyboard arrows and tab works just chef's kiss. Great job. This is going to open up a lot more choice in projectors for people, this literally enables things that weren't possible before, not just 'makes things easier'.
Anyway, my setup involves an Ikea tabletop fixed onto an Ikea convertible couch/bed using 3d printed brackets (my 'sewing room' is really a half finished attic room that doubles as a guest room). This table top is awkwardly sized for cutting mats, at least for cutting mats big enough to cut an entire cloth width (1m40) at once; so what I did instead is order a custom sized cutting mat that is 1m80 wide and 60cm high. Because I don't have a grid on this cutting mat (it's transparent), I used masking tape underneath the cutting mat to draw a 80x40 cm rectangle on it, subdivided every 20 cm horizontally and every 10 cm vertically. Now, I can enter 80x40 in the raster size in PP, but then I get grid lines every centimeters (see pic 2 below). It would be nice to have some way to make a coarser grid.
There are several ways to go about this, including one where you can specify in each direction every how many units you want a line, but I think this makes the UI much more complicated than need be. If there were one more unit in the unit drop down, dm (decimeter), then the logic could still be that it draws grid lines on every unit, but when dm is selected (in my case I would then fill in 8 in the width and 4 in the height), that would mean a grid line every 10 cm.
This way it would not be possible to have custom distances like every 5 or 20 cm or every 3 inch or whatever, but I think this is a fair tradeoff against how much this will complicate the UI. For people like me who calibrate on their own reference grid, having a line every centimeter is too much, but 10 cm seems like a workable amount.

Woot woot! Your setup looks great!
I’m not sure about dm. I feel like that one could confuse people. What about something like major and minor lines. Like thicker lines every 10cm/5 inches or something like that? That sort of scheme seems common on mats.

What about something like major and minor lines.

Was exactly what I was thinking.
@roel-v that’s pretty awesome. What a cool testament to the capabilities of this tool! This is why I love software development.

Yes I thought about major/minor at first too, but I'm not sure having the major ones wider is as comfortable when calibrating, as then you start to have to line up the middles of two lines rather than the lines being narrow enough to not really have a width at all, if that makes sense. And having the minor lines be a lighter color than the major ones risks them not being visible enough at all. Do you use the minor lines when calibrating, or are they there more to make the projected pattern look like the cutting mat as much as possible? If it's only for the 'feel', maybe the minor lines not being all that visually when you focus on them isn't a big deal. I was thinking about it, and I think I prefer the look and feel of the 'fully' filled in grid (i.e. minor lines showing, or at least a hint of them), even if those lines aren't really actively used when calibrating.
Or if we can afford another toolbar button, it could be one that toggles the minor lines color state between full color (i.e. same as major)/lighter color/off, maybe with the default being 'lighter'?

I made a PR with major and minor lines because I think this one is best tested out to see if we like it. I'm having a hard time knowing if I'd want thicker lines or not. I don't have time to check with the projector this morning but maybe I'll cut something later today and see how it feels. I really like having all the lines because when you're calibrating on a mat with grid lines and get it just right, there a shing moment when everything lines up perfectly that I love. Lol, shing is probably not the best word but I'm not sure how to describe it. https://pattern-projector-git-lines-courtney-pattisons-projects.vercel.app/en/calibrate Let's see if we like this and if it's no good we can consider adding in the toolbar button as you suggested.

Sorry, I forgot to change the settings! https://pattern-projector-git-lines-courtney-pattisons-projects.vercel.app?_vercel_share=NcPMXWMwj5AsVdVhf6xlifGA7d6gUnX5

Just tried it on my setup:

Was the green-on-black during calibration already there yesterday? I'm not a fan, I much prefer black on white, but I have a black on white reference grid, whereas I assume you (and most others) have a black on green cutting mat? Would be useful to have the color selector also there on the calibrate page, except there it would apply to the raster not the pdf.
The difference between minor and major lines is much better visible on the projected image than it looks on screen.
But the important part - when projecting in cm, it still looks very crowded, even with minor/major. I think it's just the nature of working in cm where you'll always have 2.5 timer higher line density. The toolbar I was talking about won't help with that.

Yeah that's what I do; I have a grid 40x80 drawn with pencil on masking tape underneath the transparent cutting mat, with additional lines every 10 cm horizontally and every 20 cm vertically. Those are just there because it seemed like a good idea, but tbh I haven't used them the few times I've calibrated now. Or do you mean I'd make a separate calibration sheet, that I remove from the work surface before cutting, and I can replace onto the fabric to double check?

No, I think you are doing what I was thinking you could do. I'm just trying to think through/justify this issue and potential solution. I have personally found that my "inner lines" don't always match up because my surface is not perfectly level. It's not enough to really affect most projects, in my opinion, so to me those additional lines are just "nice to haves" vs. being the actual calibration I am doing (which is on the outermost box).

Also, I've done a quick informal inventory of metric cutting mats available online, and they all use the same major/minor gridding, except that they all have major lines every 5 centimeters unlike the 10cm that is in the Vercel link above. So if you decide the major/minor should stay, making the majors line up with what it looks like IRL is probably the way to go.

Also, I've done a quick informal inventory of metric cutting mats available online, and they all use the same major/minor gridding, except that they all have major lines every 5 centimeters unlike the 10cm that is in the Vercel link above.  Such a good idea to check that out!
I have a few ideas all of which include keeping the major grid lines, because I like those!

Add ticks around the grid for the minor lines
Make a dot grid for the minor lines
Make a cross grid for the minor lines (+ at every minor line intersection)

Okie doke, I've tried a dot grid as well and felt like it was less intuitive. I switched the colour back to white lines and agree that looks so much better. I'm thinking just add in the major lines. I tested it on the cm side of my mat and although it's a bit busy, but it matched my mat so I'm pretty happy with it. The PR preview has the style I'm thinking works. What do you folks think?

Haven't tried on a projector, but looks great from the browser.


chore: Update TestSuiteRun, TestSuiteRunSummary, Note, and associated redux files to TypeScript with useSelector/useDispatch hooks

Description:
TestSuiteRun and TestSuiteRunSummary component files:

Converted to TypeScript
Replaced connect from react-redux with hooks useSelector and useDispatch

Redux files associated with TestSuiteRun.tsx and TestSuiteRunSummary.tsx converted to TypeScript:

Action files: errorNotificationActions, keystoreActions, testRunActions, testSuiteRunActions
Reducer files: keystoreReducer & testSuiteRunReducer
Selector files (created): keystore & testSuiteRun

Note.tsx component file:

Replaced connect from react-redux with hooks useSelector and useDispatch

No functional changes were made, only refactors. Screenshots below demonstrate no visual changes before vs. after.
Before:

After:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Does this PR fix an open issue?

[ ] Yes
[x] No

Hi @hwinsby!
I'm so sorry I let this hang for so long. I've been working to get all the open source code migrated over to a new monorepo. I believe this will make the development experience much smoother, especially if you want to start digging into any of the bitcoin libraries as well. Good news is that I suspect that most of your changes here should be transferrable to the new code base though, so hopefully that's not too much trouble. I'll hold off on reviewing until it's in the new repo so we keep any conversation logs.
To get started just clone https://github.com/caravan-bitcoin/caravan, install dependencies and run npx turbo run dev (or install turbo globally. You'll see the coordinator app in apps/coordinator and the rest of the code in there should be pretty familiar. Please let me know if you run into any bumps in the developer experience (or submit a PR with readme updates). I definitely am hoping it's as smooth a transition as possible and ideally easier to work with!

Hey @bucko13, I'm so sorry for the late response here! I'm hoping to get working on this next week.


Enable ffmpeg, for Direct (/dev) Stream

Hi,
I think this one is a screw up by me - confused a bit by "stream" ... as there is streaming from the source, and then of course from fHDHR to the client. In the code currently ffmpeg is sort of "tied" to rtp, but not sure that makes sense. And really - direct from /dev to ffmpeg would be very handy => encode (possibly in HW), on the source side, reduce the bit rate to the client.
I did hack this up here, and can make it work, but I would appreciate your thoughts, @DanAustinGH. I can see a couple options,

add a new configuration variable, for direct => to go through ffmpeg or not. Basically, allow direct from /dev to be transcoded (vs. now, where it's tied to direct read only)
no new variable, rather in the pcie case, always get the stream from /dev ... never use rtp for the (internal) HW. I'm almost thinking this one makes more sense => why add rtp "overhead" for the pcie card

Somewhat thinking out loud here, please do comment. I can set this up either way, and don't have a real strong preference ... but would like to be able to transcode on the source end, really for a couple reasons,
a. I am seeing less dropped packets if I lower the bit rate to clients (like ffmpeg, Plex). And really, why waste the BW.
b. if I already transcode before going to Plex => Plex doesn't need to transcode (i.e. I have more manual control), and recordings are already in the format I want. No post-processing to transcode!
Again, please let me know your thoughts. Thanks!

I favor option 2.  I do/did feel that RTP should work, but that does not mean it makes sense to use it.  I think one of the early tests we had ffmpeg reading from the device.  Couple that with the quality settings that @deathbybandaid has already added and I think you are pretty close to this goal.  With option HW acceleration you could shoot for real-time H264 or even H265 and seriously trim the bandwidth to emby/plex and the clients.

OK, I'll modify the code here then, go with Option 2 - it's your plugin, want to make sure you're happy with any mods! And agree rtp is cool, but not really necessary for the pcie card, extra overhead (and adding extra config variables is more confusing). I'll try to get you a PR to look at a bit later today.

With option HW acceleration you could shoot for real-time H264 or even H265 and seriously trim the bandwidth to emby/plex and the clients.

With my hacks, I actually had that running overnight (h.264_nvenc), to test it out => I ran 2 tuners / clients in parallel, ffmpeg to show me stats. Dropped packets was fine (no increase), and bit rate was ~ 2.5 Mbps, down from the raw ~ 16 Mbps. Then Plex ... no transcode, recordings are real time ready. Life is good 😄.
Again, will try to get you something a bit later today to shoot arrows at.

Meh.  I was in line to buy the new HDR 6 tuner that Silicon Dust killed off before shipping.  I found a Ceton 6, and actually was quite impressed with the build quality.  Sadly software was non-existent and not supported by Emby.  I found a windows only emulator, but don't use Windows on my media server, so I tweaked it to run in Wine, which was a pain since my server is headless.
That code is in delphi and to my eye very hard to read, so I fired up a copy of wireshark and documented the API calls from the emulator to the Ceton, which then let me tweak one of @deathbybandaid plugins to provide basic functions.  I am not a developer and had not worked with Python before.  The fact I have ben able to use it for 6 months to watch and record TV has been way more than I expected.
All that is a long-winded way to say I won't be overly critical and hugely appreciate your efforts.  I am only aware one one other user of this plugin and if we three are happy, all is good.

Sounds great, thanks!
OK, I think I have it all working here - just pushed #29. Please take a look, comment by all means! I did check both "direct" and "ffmpeg", and they work with pcie => but I can't test external of course. A few notes to help understand,

I left (on purpose) rtp and /dev detection in ... that way other clients using the HW are detected still.
startstop is still there, just based on HW type (i.e. don't start rtp, but now on pcie only, vs. "direct" ... which is a stream_method)
if you add transcode_quality in the [ceton] section ... it pulls and uses it. You can use one of the already defined ones, or I can share with you my "test" (HW encoding) one. Just let me know. But that said, I do have it running right now with h.264_nvenc!

Thanks!

Oh, and I do notice ... when HW transcoding is enabled on fHDHR / ceton, it is a bit slower to start up. I think it's just the HW setup, etc. To me, not a huge deal, a few seconds. But so you know.

I would be interested to see what your custom profile looks like.

Sure, NP at all! I added a new one, just hacked in for now, and set this in config.ini,
        elif stream_args["transcode_quality"] == "nvenc720":
            ffmpeg_command.extend([
#                                    "-hwaccel", "cuda",
#                                    "-i", "pipe:",
                                    "-c:v", "hevc_nvenc",
                                    "-s", "hd720",
                                    "-c:a", "copy",
                                    "-f", "mpegts",
                                    ])

Had to fiddle a bit, output file format and codec seem to have to play nicely (or not 🤣) with ffmpeg, Plex (clients). It's running right now, codec confirmed in ffmpeg. Bit rate is ~ 2-3 Mbps.
Give it a try? You can also select one of the options already in the file, SW transcoders. Should also work - just add to the [ceton] section (my case),
transcode_quality = nvenc720

BTW, @DanAustinGH - close this one now, with the recent merge?
Thanks!

Sure!


refactor(semantic): move Counts code into counter module

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5703
#5710  👈
#5709
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


Add initializer spec

Description
This PR adds the independent management of the initializer pod spec to the K6 object spec.
Motivation and Context
The initializer pod has different requirements than the runner pods.
In this case it doesn't need the Istio sidecar, but I would like to have it for the runner.
fixes #172
How Has This Been Tested?
I only adapted the current unit test to make it pass, wanted to see the reception of PR first. I can make a more complete unit test suite if required.
I ran a manual test in my own k8s setup with Istio.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks, @13013SwagR :slightly_smiling_face:
Initializer was deliberately set to use the runner's spec because they're both running k6, unlike the starter. I.e. one needs an image with k6 for both initializer and runner while starter doesn't depend on k6, at least at the moment. So initializer was set to use runner's spec in order to minimize entities and keep configurations simple. Normally, a user of the operator shouldn't even bother with initializer, unless there are errors in the script and initializer terminates with an error. I think if we are to change this and put initializer into a separate spec, we should be more clear on why we're doing that.
So one case is with dapr, described in #164, but I'm not fully clear dapr usage really depends on a separate spec for initializer or if it was resolved with container specification fix. I'd like to confirm this first. Sadly, I didn't have time to test this myself yet.
Are there other cases?
PS this discussion is more fit for an issue and not a PR I guess :see_no_evil:

So one case is with dapr, described in #164, but I'm not fully clear dapr usage really depends on a separate spec for initializer or if it was resolved with container specification fix. I'd like to confirm this first. Sadly, I didn't have time to test this myself yet.

As I described there, "the problem" here is related on how kubernetes understand that a given job is completed.
Since dapr is a sidecar (i.e one more container within the same pod) and the annotations for the runners and initializers are the same, the sidecar will be present in both, runners and initializers. The big difference is because when using runners I'm able to call the dapr shutdown using its api (see one example at dapr) but as the initializers are totally out of my control I can't call shutdown, meaning that from the kubernetes point of view, the initializer job as a whole still pending even when the initializer container actually was successfully executed (because daprd still running). Furthermore, the operator leverages the kubernetes status to make sure the job is completed, see here.
Conclusion: The operator will not work when the initializer job has sidecar containers because the job isn't considered completed until all the containers are exited with code 0.

Thank you for the clarifications, @mcandeia!

Furthermore, the operator leverages the kubernetes status to make sure the job is completed, see here.

This part is unlikely to change even with resolution of #138. So yes, some alternative is clearly needed.
@13013SwagR,

I think the initializer Job should really be just an init container on the Starter Pod which solve my issue and the dapr one for the initializer.

This pod is required for the k6 Cloud output support. It can't be merged with the starter: these are clear separate stages that must be executed sequentially.
I've tested this with Envoy / scuttle: there's actually another bug which was also reported recently in #179 - I added the fix in PR #182.
To sum up, enabled Envoy will work with disableLogging: true. Otherwise, initializer output will be polluted with sidecar's logs and cannot be processed. This is "expected behaviour" at the moment. This is true regardless of initializer job being separate or not.
As for request to make initializer job separate, we have three cases so far:

dapr sidecar shutdown
disabling Istio for initializer only but keeping it for runners
downloading the script in init container of initializer (also connected to #118)

Given that, I think it makes sense to make initializer job separate at this point of time. More complex logic would be to make initializer job run only for specific cases but that requires some more thinking, esp. given the limitation with the logs (described above with Envoy).

Hello @13013SwagR, This issue with initializer job got a higher internal priority lately. No pressure but could you please let me know if you'll be able to work on this PR in the coming weeks? Thank you!

Hey sorry for the late response, will update in the next days.

Hey @yorugac,
Did the rebase and implemented your suggestions
Let me know if there's anything else
Thanks


Don't fail if "users" data bag doesn't exist

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@FlorentFlament

Please sign the CLA here.

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.

Hey, I've just once again stumbled upon this. Any other way to let the users::sysadmins recipe not fail, if the test-kitchen suite does not have the users data bag?
Otherwise I'd be happy, if you could merge this.

@FlorentFlament If this is still a change you'd like to make please rebase the PR and I'll make sure to get it merged in.

I'm going to close this out since the change has diverged from master and we haven't heard back about a rebase. If this is still something you want to get merged in please open a new PR against the  current master state.


Datetimepicker not working properly

{
column_number: 0,
filter_type: "range_date",
datepicker_type: 'bootstrap-datetimepicker',
date_fotmat: 'dd/mm/yy HH:mm:ss',
filter_plugin_options: datetimepickerOptions
}

Filter like this breaks, when using both lower and upper datetime bound.
Reason:
function rangeDateKeyUP(table_selector_jq_friendly, date_format, event)
is using $.datepicker.parseDate to parse the given date.
$.datepicker.parseDate can parse only year, month, day data but not hour, minute, second.
As a result, min instanceof Date and max instanceof Date are always false.
Exception from $.datepicker.parseDate: Unexpected literal at position 11

Hi, please provide a jsbin / etc' link with this issue

I'm sorry but I have no time to create the sample.
I can also provide the information that $.datepicker.parseDate comes from
project 'jqueryui' and the working alternative of the same function can be found in
'jqueryui-timepicker-addon' project, named $.datepicker.parseDateTime

Ok.
Feel free to reopen this issue with a proper test case of your issue.


[PORT] Remove code coverage w coverlet yamls

Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/3336

Description
This PR removes the YAML files for code coverage using Coverlet.
Changes made
Removed the YAML files for code coverage with Coverlet. These files can only be used in a single project and we currently have a complete code coverage reported using coveralls.

n/a


finishTransaction and getReceiptIOS don't work

Hello, I have a bug with finishTransaction and getReceiptIOS for IOS, these modules are not working.., I'm on the latest version of react-native-iap.

react-native-iap: 12.4.4
react-native: "0.69.7
Platforms (iOS, Android, emulator, simulator, device): iOS

https://github.com/dooboolab/react-native-iap/issues/2110


 Simply enough but an educational experience for me to work with github's graphql api and helped me better understand this project as a whole.
I may have defiantly looked over best practices or did some no no's so please review. thank you for your help.

@mndowne nice PR! left a few comments :)

last review items! looks solid otherwise!


Error with url link nadag

Im trying to run Craigs script to get all projects in NADAG that overlaps with the NGU survey area, but get the error below connected to libnadagclient url. The notebook I am using is here: /Volumes/GoogleDrive/Shared drives/PROJECTS/Projects/22017_NO_NVE_Interpretation on NGU data/02_Interim/09_Interpretation/01_Code/22017_001_get_overlapping_projects_NADAG.ipynb
---------------------------------------------------------------------------
HTTPError                                 Traceback (most recent call last)
Input In [8], in <cell line: 1>()
----> 1 geotech_sources_0 = libnadagclient.get_project_ids_from_bounds(areas[0].bounds)

File /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/libnadagclient/__init__.py:35, in get_project_ids_from_bounds(bounds)
     28 def get_project_ids_from_bounds(bounds):
     29     """Look up project id:s using a geographical bounding box.
     30
     31     bounds is (minx, miny, maxx, maxy) in crs 25833
     32
     33     Returns a dictionary of {project_id: projectnr}
     34     """
---> 35     wfs11 = WebFeatureService(url=WMS_SERVER, version='1.1.0')
     36     c = crs.Crs(CRS)
     37     srsname = c.getcodeurn()

File /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/owslib/wfs.py:52, in WebFeatureService(url, version, xml, parse_remote_metadata, timeout, username, password, headers, auth)
     48     return wfs100.WebFeatureService_1_0_0(
     49         clean_url, version, xml, parse_remote_metadata,
     50         timeout=timeout, headers=headers, auth=auth)
     51 elif version in ['1.1', '1.1.0']:
---> 52     return wfs110.WebFeatureService_1_1_0(
     53         clean_url, version, xml, parse_remote_metadata,
     54         timeout=timeout, headers=headers, auth=auth)
     55 elif version in ['2.0', '2.0.0']:
     56     return wfs200.WebFeatureService_2_0_0(
     57         clean_url, version, xml, parse_remote_metadata,
     58         timeout=timeout, headers=headers, auth=auth)

File /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/owslib/feature/wfs110.py:84, in WebFeatureService_1_1_0.__new__(self, url, version, xml, parse_remote_metadata, timeout, headers, username, password, auth)
     68 """ overridden __new__ method
     69
     70 @type url: string
   (...)
     81 @return: initialized WebFeatureService_1_1_0 object
     82 """
     83 obj = object.__new__(self)
---> 84 obj.__init__(
     85     url,
     86     version,
     87     xml,
     88     parse_remote_metadata,
     89     timeout,
     90     headers=headers,
     91     username=username,
     92     password=password,
     93     auth=auth,
     94 )
     95 return obj

File /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/owslib/feature/wfs110.py:135, in WebFeatureService_1_1_0.__init__(self, url, version, xml, parse_remote_metadata, timeout, headers, username, password, auth)
    133     self._capabilities = reader.readString(xml)
    134 else:
--> 135     self._capabilities = reader.read(self.url, self.timeout)
    136 self._buildMetadata(parse_remote_metadata)

File /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/owslib/feature/common.py:54, in WFSCapabilitiesReader.read(self, url, timeout)
     43 """Get and parse a WFS capabilities document, returning an
     44 instance of WFSCapabilitiesInfoset
     45
   (...)
     51     A timeout value (in seconds) for the request.
     52 """
     53 request = self.capabilities_url(url)
---> 54 u = openURL(request, timeout=timeout, headers=self.headers, auth=self.auth)
     55 return etree.fromstring(u.read())

File /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/owslib/util.py:214, in openURL(url_base, data, method, cookies, username, password, timeout, headers, verify, cert, auth)
    211     raise ServiceException(req.text)
    213 if req.status_code in [404, 500, 502, 503, 504]:    # add more if needed
--> 214     req.raise_for_status()
    216 # check for service exceptions without the http header set
    217 if 'Content-Type' in req.headers and \
    218         req.headers['Content-Type'] in ['text/xml', 'application/xml', 'application/vnd.ogc.se_xml']:
    219     # just in case 400 headers were not set, going to have to read the xml to see if it's an exception report.

File /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/requests/models.py:1022, in Response.raise_for_status(self)
   1017     http_error_msg = (
   1018         f"{self.status_code} Server Error: {reason} for url: {self.url}"
   1019     )
   1021 if http_error_msg:
-> 1022     raise HTTPError(http_error_msg, response=self)

HTTPError: 404 Client Error: Not Found for url: http://geo.ngu.no/geoserver/nadag/wfs?service=WFS&request=GetCapabilities&version=1.1.0
``

There is no error, you need to pull the latest libnadagclient and re-setup. I can do this with you tomorrow :)


Problem when trying to add two SpectroMSMeasurement objects

I came accross a problem before when importing data since SpectroMSMeasurement was merged (we discussed this on Slack). Now I ran into it again, and it seems to be a problem when trying to add something to a SpectroMSMeasurement  object (I tried adding a second SpectroMSMeasurement or a plain MSMeasurement.  I suppose this is not expected and a bug? @ScottSoren?

I am getting this error as well when I am running external tests. The problem is in Measurement.from_dict() where measurement variable is not initialized, but it is trying to be used. Lines 225-238
There is just a print in the except block, but it should be raise which would stop the program, because it failed to create a new object. And it is not a user's problem, so I am in doubt whether the message should be there in this case.
In Anna's case, this method is used internally by ixdat while creating a new object from the two. That is one thing. Then it also complain that SpectroMeasurement must be initialized with spectrum_series and spectrum_id, which are probably not provided when creating the SpectroMeasurement.
In my case, it is the tests, because some of the datasets contain mass scans and then it fails, because of this spectra addition. The exception I am getting is: "Measurement.__init__() got an unexpected keyword argument 'ec_technique'"

Looks like there is a lot of fixes to be done plus @KennethNielsen the CI is not working as intended, because it should be running the external tests and this problem would had been caught already before.

I agree there are obviously bugs here. Adding two SpectroMSMeasurements should probably be allowed (maybe under certain constrictions), but I'm unsure if we ever decided what should happen if you add a SpectroMSMeasurement with a MSMeasurement (since they are sort of orthogonal in nature). I think this is a question that @ScottSoren already raised, but I don't think we made a decision.
@matenestor I will make a separate issue concerning the CI and look into it. It was always the intention that pre-commit and local tests would make tests based on external data optional but that they should of course always be run in CI. Thanks for catching it.

Seems this is a priority for the next ixdat release.
I think there are a couple things to fix here, all easy to fix but hard to find:

MSSpectroMeasurement.extra_column_attrs is {'ms_measurement': ('tspan_bg',)}, not {"spectro_measurements": {"spectrum_id"}} as we want it to be. The former should be deleted anyway with the coming background overhaul. But the underlying problem is that inheritance does not work with serialization as well as it should. This is what #75 aims to address. The fix for now is just explicitly saying what extra_column_attrs should be in the SpectroMSMeasurement class rather than relying on inheritance. This resulted in spectrum_id being left out of the dictionary which, as @matenestor noticed, causes some of the errors. It also makes it so that you can't even cut a SpectroMSMeasurement!
We'll need an extra line or two of code ensuring that the spectrum_series attributes are appended when two SpectroMeasurements are appended. This will go here.
Adding an ECMeasurement and a SpectroMSMeasurement is indeed not implemented. We will need a new class named ECSpectroMSMeasurement or something like that. Personally, I think it's not a problem - the user does not need to know the name of the calss and if we fix all this ORM inheritance stuff (#75!) then it's cheap to make new classes like this - not much goes in them since they inherit everything, and the most new code that needs to be written is probably just the plotter. (The quicker fix is just to hard-code that we want a plain EC-MS measurement in this case for now.)

I can do a PR with the above three points tomorrow. If you'd like to be sure your exact scripts generating the bugs will run, send or point me to them and the needed data!
A few additional comments here on addition of (Spectro)Measurement objects in ixdat:
The class when adding measurements is determined via the technique, using get_combined_technique.
First, I think we need to improve that error message (the one in Anna's opening comment) so that it says what technique it tried to find a class for. Second, we just need to implement some rules for adding techniques with spectra.
if "X" and "Y" are measurement techniques, then:

"X_spectra" and "Y_spectra" are, by convention, the name of the corresponding spectral techniques, if they exist. There's an "MS_spectra" technique, but no "EC_spectra" technique. (Unfortunately, the class naming is inconsistent: there is a SpectroECMeasurement which has the same name structure as SpectroMSMeasurement but is in fact something different (the spectra are not EC in SpectroECMeasurement)... I think the way to fix this would be to refactor SpectroMSMeasurement to MSSpectroMeasurement`. If there are no objections, I will do so in the PR addressing this issue.)
"X" + "X_spectra" --> "X-X_spectra". this is normal hyphenation, and the reason for an annoyingly-named "MS-MS_spectra" technique in TECHNIQUE_CLASSES.
If two measurements of the same technique are added, the resulting measurement will always also be of that technique by this code in get_combined_technique.
"X" + "X-X_spectra" should give "X-X_spectra" by this code in get_combined_technique . So adding two MSSpectroMeasurements should give a MSSpectroMeasurement .
Nothing is implemented yet for Y + X-X_spectra, so we'll need to modify in get_combined_technique as well to get addition of ECMeasurement and MSSpectroMeasurement (to a ECMSSpectroMeasurement class) working.

Okay, I now think I have mostly solved this on the spectromeasurements  branch. I've done points 1, 2, and 4 from my earlier message.
It's demo'd here: https://github.com/ixdat/ixdat/blob/spectromeasurements/development_scripts/reader_demonstrators/demo_zilien_spectrum_reader.py
@AnnaWiniwarter , can you send me data with which to debug point 3? I need sumultaneous EC data (biologic) and MS data with spectra (zilien). I think I have time to do everything but the plotter, so it'll be just normal EC-MS plots that come from an ECMeasurement + MSSpectroMeasurement.
@KennethNielsen and @matenestor , all of my development scripts are running on the spectromeasurements branch, but some of the --external tests are still failing. I'm inclined to blame the tests. I think you test for a lot of stuff that isn't important, like whether "Ns=0" gets appended to a series list (that has nothing to do with this Issue, but resulted from #134 - I think it's not a problem because e.g. append_ec_files runs as it did before). I'll have to take time for each of these failed tests to figure out whether it's overtesting (doesn't matter) or whether something was wrong before or whether something is wrong now. If you have time to diagnose the failing tests with this in mind, that would be greatly appreciated!
In the meanwhile, since I'm also not great at the logic of unit tests, I will prioritize "EC" + "MS-MS_spectra" for Anna, and then the other issues labeled spectra, some of which should be quick fixes, to include in the PR.

@AnnaWiniwarter ,
Should work now with the code on the[spectromeasurements]https://github.com/ixdat/ixdat/tree/spectromeasurements) branch:
ms = Measurement.read("my_zilien_data_with_spectra.tsv")    # an MSSpectroMeasurement
ec = Measurement.read("my_ec_data.mpr")   # a ECMeasurement
ecms = ec + ms      # an ECMSSpectroMeasurement
ecms.plot()              # a normal EC-MS plot
ecms[1].plot()          # a mass spectrum

@KennethNielsen , check out this deleted mess, and this class which works as intended despite being completely empty! This is a result of the MemoryBackend in action, and inheritance actually working just as we want it to at least as far as arguments to __init__ go. Yours truly, - Happy Developer :)

@ScottSoren tests are now passing in #165. However, using Measurement.read(technique="EC") (with include_mass_scans set to True by default) now raises TechniqueError.

@KennethNielsen , I think you're right. That would reduce the explosion of classes, and technique names. I can try and make that change in the open PR.
The only challenge that comes to mind right now is the plotter, since these are definitely not empty classes. Should an MSMeasurement check whether it has a spectrum_series to decide whether it initiates with an MSPlotter or a MSSpectroPlotter?


Packages incorrectly classified as non-research

Hello,
Some more academic projects that were not correctly classified:
http://depsy.org/package/python/Dialogs
http://depsy.org/package/python/minimalKB
http://depsy.org/package/python/pykb

Also http://depsy.org/package/python/deepTools

http://depsy.org/package/python/pysam

http://depsy.org/package/python/spglib


Add Open Graph image generator

Includes the previously-separate Open Graph image generator. This required reconfiguring Sentry because it doesn't play nicely with Webpack + NFT.

Currently testing by creating new Vercel projects for all three, please hold.

@mehulkar It is indeed better to inline this, but fighting with Sentry was a stumbling block.


Godotengine master

Please do not open any more merge attempts like this, it's easy to make mistakes, but no more 🙂


Simplify IsValidStakeLimitKey

#1292  👈
feature/proof-of-stake

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @lazynina and the rest of your teammates on  Graphite


🪲 Bug Report - False Positive for Configure DDoS Protection on the Azure Firewall VNet due to character case

Describe the bug
The KQL query for Configure DDoS Protection on the Azure Firewall VNet produces a false positive if there are upper\lower case inconsistencies in the VNET IDs being joined.  For example the join in the KQL query will fail to recognize the following difference in the IDs being joined:
/resourceGroups/my-resource-group-1/
/resourceGroups/MY-RESOURCE-GROUP-1/
To Reproduce
Expected behaviour
The join should disregard case of the ID
Screenshots 📷
Additional context
I suggest changing the query to make the ID lowercase before performing the join.  Something like this:
// Azure Resource Graph Query
// List all in-scope Azure Firewall resources, where the VNet is not associated to a DDoS Protection Plan
resources
| where type == "microsoft.network/azurefirewalls"
| mv-expand properties.ipConfigurations
| project name, firewallId = id, vNet = tolower(substring(properties_ipConfigurations.properties.subnet.id, 0, indexof(properties_ipConfigurations.properties.subnet, "/subnet") - 7)), tags
| join kind=fullouter (
resources
| where type == "microsoft.network/ddosprotectionplans"
| mv-expand properties.virtualNetworks
| extend vNet = tolower(tostring(properties_virtualNetworks.id))
| project ddosProtectionPlan = id, vNet
)
on $left.vNet == $right.vNet
| where ddosProtectionPlan == ''
| project recommendationId = "1b2dbf4a-8a0b-5e4b-8f4e-3f758188910d", name, id = firewallId, tags, param1 = "ddosProtectionPlan:false"

@Azure/aprl-networking please review

Fixed #67


Requester node TLS support

Enable the requester node to serve endpoints over TLS. This should work for clients on both public and private networks.
### Tasks
- [x] Requester node should support --tlscert and --tlskey to for TLS config
- [x] Requester node should support --autotls to use ACME for certs.
- [x] Update client to support TLS (with optional --cacert)
- [x] Client should support --insecure for self-signed server certs
- [ ] Document usage in server (and client)
- [ ] Fix developer experience

This was done in separate PRs and documented at https://docs.bacalhau.org/running-node/configuring-tls


Add support for Ed25519 pubkeys

Coverage increased (+0.1%) to 34.27% when pulling adab98f9b95c9c136bfcb720121e26b443406120 on kruton:exp-ed25519-native into a5191879d155dcdea3452dded71fd319a1a34a90 on connectbot:master.


Fix GOMAXPROCS for K8s

GOMAXPROCS was not respecting cgroup limits when running on K8s which resulted in getting wrong number of available CPUs (it sees all node CPUs). That had effect on number of parallel copiers that write to DB.
Note: I've built and tested new image on K8s. Worked well.

bors r+

bors r+


Save State Issue with BottomNavigation item click Listener

Save state does not work when the bottom navigation item is clicked.
How to replicate:
Steps:

Go to search Fragment
type something on edit text
click the notification icon
click the search icon

Save state only works when pressing the back button

Hi @nawinkhatiwada , the main idea on this project is faking multiple back stack. It just works for back press. When you click on a menu item, navigation every time creates new instance of a fragment.
I think you must use this behaviour : Navigation Advanced Sample

thanks


Command Sequences from provided Dataset into CAD

Hello,
I've successfully set up and executed the Fusion360 Python plugin available at AutodeskAILab/Fusion360GalleryDataset. However, I am encountering two challenges:
Dataset Compatibility: I'm unsure how to modify the Fusion360GalleryDataset so that it becomes compatible with the format you require for your plugin or tool. Could you provide a step-by-step guide or outline the necessary transformations?
Command Sequences to CAD: I need detailed instructions on how to take the command sequences from the dataset provided and use them to generate the corresponding CAD models in Fusion360. A walkthrough on this process would be greatly appreciated.

Please take a look of the issues from the Fusion360 dataset (#60 - #63), you may find it helpful. For example: https://github.com/AutodeskAILab/Fusion360GalleryDataset/issues/60


Update readme to include a section about cancelling subscriptions

As stated here: https://github.com/dooboolab/react-native-iap/issues/679#issuecomment-527155320

As stated here: #679 (comment)

Could you please change Linking.openUrl to Linking.openURL
thank you

Sorry about that!
https://github.com/dooboolab/react-native-iap/pull/689


add requirement for minimal version of setuptools

This tools doesn't work with old verisons of setuptools, due to an old version of the pkg_resources library.
Here's an error I get after running: sudo pip install --upgrade setuptools==20.1.1
Traceback (most recent call last):
  File "/usr/local/bin/pip-compile", line 11, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/piptools/scripts/compile.py", line 223, in cli
    reverse_dependencies = resolver.reverse_dependencies(results)
  File "/usr/local/lib/python2.7/dist-packages/piptools/resolver.py", line 273, in reverse_dependencies
    return self.dependency_cache.reverse_dependencies(non_editable)
  File "/usr/local/lib/python2.7/dist-packages/piptools/cache.py", line 139, in reverse_dependencies
    return self._reverse_dependencies(ireqs_as_cache_values)
  File "/usr/local/lib/python2.7/dist-packages/piptools/cache.py", line 163, in _reverse_dependencies
    for name, version_and_extras in cache_keys
  File "/usr/local/lib/python2.7/dist-packages/piptools/utils.py", line 192, in lookup_table
    for value in values:
  File "/usr/local/lib/python2.7/dist-packages/piptools/cache.py", line 164, in <genexpr>
    for dep_name in self.cache[name][version_and_extras])
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3047, in parse
    req, = parse_requirements(s)
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2991, in parse_requirements
    "version spec")
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2967, in scan_list
    raise RequirementParseError(msg, line, "at", line[p:])
pkg_resources.RequirementParseError: Expected ',' or end-of-list in funcsigs>=1; python_version < "3.3" at ; python_version < "3.3"

With the next available version of setuptools (20.2.2), it works normally.

Might be better to use packaging https://packaging.pypa.io/en/latest/requirements/ instead, which is safe to depend on.

This is something that has been in the back of my head for a while, but I'm not sure it's that straightforward.
By depending on the internals of pip, and not being able to specify the required pip version, we end up depending on setuptools in the cases where the version of pip installed uses pkg_resources instead of packaging (see that function key_from_req we have in utils.py).
I'm worried about the effect of setting a lower bound on setuptools, especially for users with older versions of pip that might not be able to update setuptools.
The only "easy" way I see out of this is when we'll drop the support of old pip versions, and we could then move to packaging and try to be as clean as possible. But as a lot of users use the version of pip distributed by their linux distribution, many of which are lagging behind.
Now if I missed something that actually makes all of this way easier than that, correct me, I'll be pleased.

Closing this, as a simple lowerbound will not cut it.
If we end up vendoring pip 9.0.1 we might be able to do something like that.


Fixed examples.

So this script runs without error against Powergate Localnet v0.3.0. However, in each instance the wallet balance is 0 instead of the default<PHONE_NUMBER>.

you need to wait for a brief time after creating the ffs and then query
balance in order for the transaction to complete
On Sun, 2 Aug 2020 at 01:08, peterVG<EMAIL_ADDRESS>wrote:

So this script runs without error against Powergate Localnet v0.3.0.
However, in each instance the wallet balance is 0 instead of the default
4000000000.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pygate/pygate-gRPC/pull/28#issuecomment-667603046,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMFDUPSFWIDDZQ5YHL2YA3R6SVAJANCNFSM4PRT44OQ
.

--
Wang (Leonard) Ge
Imperial College London 2021
<EMAIL_ADDRESS>+44 -<PHONE_NUMBER>4

Yup. That fixed it. Thanks Leonard. PR ready for merge approval.


added tools

Added the Base64 page in src/pages.
Added the Cloud Code page in src/pages.
Added the JSON Validator page in src/pages.

Added the Base64 page in src/pages. Added the Cloud Code page in src/pages. Added the JSON Validator page in src/pages.

Hey @sibylobodoekwe Great first contribution. I need some clarification on these new features you're proposing.
Ideally, this should be discussed first in the issue you create before working on a PR, but, nvm, that's my fault for not adding a guide.

Base64 encoder/decoder: What does this do? and how useful is it? I tried to play with the utility and don't know what it does.
Cloud Code: Same as above. What does this do?
JSON Validator: Sadly there is a JSON viewer already which does validation

Let me know what the other two really do, and we can see how to modify them together.

hi @risenW, thank you so much for the feedback.. here's a small description of base64 and cloudcode

Base64 encoder/decoder is an encoding scheme for converting binary data into a text format that can be safely transmitted over text-based protocols. Represents binary data in an ASCII string format.
Cloud Code is a server-side code or scripts running on cloud computing platforms for scalable and managed execution of server-side logic. Allows developers to build/deploy server-side logic; handling API requests, data processing, background tasks, etc in a scalable and managed environment provided by the cloud platform.-

i see they also need add placeholders descriptions added to their index.tsx as well.
They are open for improvements/contributions as i only built simplified versions of them as i expected only 1 or 2 to be approved so yea i agree the validator is not a great contender.
Happy to work on modifications, thank you.
(i've added a concise description of all 3 to the PR comment as well)

Cloud Code is a server-side code or scripts running on cloud computing platforms for scalable and managed execution of server-side logic. Allows developers to build/deploy server-side logic; handling API requests, data processing, background tasks, etc in a scalable and managed environment provided by the cloud platform.-

Okay, a couple of things for you to do:

Take out the JSON validator, as it already exists
Cloud code is not useful for this app, so take it out as well.
You can keep the base64 encoder, but adjust the image so it's the same size

alright great,  i'd get on it right now.

Here are the changes i made;

I modified and improved on the base64 features on src/pages
I adjusted image size for base64 on src/index
deleted unapproved tools (cloudcode and jsonvalidator) features and images from  random abc folder

Thank for your feedback and the opportunity, happy to make any improvements or modifications needed.

I went through your PR again. Here are some things to improve:

Use AntD components for things like Button, Form Input etc. See examples on other pages
Update page style and format. Make it similar to the other pages. That is options can be on the left or right and input boxes can be on either side.  Something like the following:

Always refer to the existing page/style, and try to match them. You can copy an existing style and just add your new features

Oh thanks, just saw this, would get on it and update.


Update CI, fix wrong argument name

Codecov Report

Merging #6 (448bad4) into master (60c0215) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #6   +/-   ##
=======================================
  Coverage   77.38%   77.38%
=======================================
  Files           4        4
  Lines          84       84
=======================================
  Hits           65       65
  Misses         11       11
  Partials        8        8

Flag
Coverage Δ

unittests
77.38% <ø> (ø)

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

Impacted Files
Coverage Δ

tracker.go
0.00% <ø> (ø)

Continue to review full report at Codecov.

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


Out of memory when compiling Unreal 5.1.0

Output of the ue4-docker info command:
ue4-docker version:         0.0.102 (latest available version is 0.0.102)
Operating system:           Linux (Ubuntu 22.04.1 LTS, 6.0.10-x64v1-xanmod1)
Docker daemon version:      20.10.21
NVIDIA Docker supported:    Yes
Maximum image size:         No limit detected
Available disk space:       221.01 GiB
Total system memory:        31.15 GiB physical, 2 GiB virtual
CPU:                        16 physical, 24 logical (x86_64)

ue4-docker version:         0.0.102 (latest available version is 0.0.102)
Operating system:           Linux (Ubuntu 22.04.1 LTS, 5.15.0-53-generic)
Docker daemon version:      20.10.21
NVIDIA Docker supported:    No
Maximum image size:         No limit detected
Available disk space:       176.07 GiB
Total system memory:        31.14 GiB physical, 2 GiB virtual
CPU:                        8 physical, 16 logical (x86_64)

I am trying to compile UE 5.1.0 on a 22.04 image and it runs out of memory in the compiling shaders stage of the build. I have tried two different machines with their stats above. I've not had any issue compiling 4.27 on these machines either. A bit confused as to what's going on here given what I thought was enough
Dec 01 20:47:32 gr-sim kernel: Out of memory: Killed process 1933 (Xorg) total-vm:27061256kB, anon-rss:48kB, file-rss:9220kB, shmem-rss:0kB, UID:127 pgtables:756kB oom_score_adj:0
Dec 01 20:47:32 gr-sim kernel: ShaderCompileWo invoked oom-killer: gfp_mask=0x140dca(GFP_HIGHUSER_MOVABLE|__GFP_COMP|__GFP_ZERO), order=0, oom_score_adj=-500
Dec 01 20:47:32 gr-sim kernel: CPU: 14 PID: 1925783 Comm: ShaderCompileWo Tainted: P           OE      6.0.10-x64v1-xanmod1 #0~20221126.015abb0
Dec 01 20:47:32 gr-sim kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D25/PRO Z690-A WIFI DDR4(MS-7D25), BIOS 1.30 03/18/2022
Dec 01 20:47:32 gr-sim kernel: Call Trace:
Dec 01 20:47:32 gr-sim kernel:  <TASK>
Dec 01 20:47:32 gr-sim kernel:  dump_stack_lvl+0x44/0x5c
Dec 01 20:47:32 gr-sim kernel:  dump_header+0x45/0x1fa
Dec 01 20:47:32 gr-sim kernel:  oom_kill_process.cold+0xb/0x10
Dec 01 20:47:32 gr-sim kernel:  out_of_memory+0x1f8/0x4d0
Dec 01 20:47:32 gr-sim kernel:  __alloc_pages_slowpath.constprop.0+0xafc/0xcb0
Dec 01 20:47:32 gr-sim kernel:  __alloc_pages+0x2b5/0x2d0
Dec 01 20:47:32 gr-sim kernel:  __folio_alloc+0x12/0x40
Dec 01 20:47:32 gr-sim kernel:  ? policy_node+0x4c/0x70
Dec 01 20:47:32 gr-sim kernel:  vma_alloc_folio+0x83/0x300
Dec 01 20:47:32 gr-sim kernel:  __handle_mm_fault+0x901/0xf30
Dec 01 20:47:32 gr-sim kernel:  handle_mm_fault+0xd6/0x2c0
Dec 01 20:47:32 gr-sim kernel:  do_user_addr_fault+0x1b0/0x610
Dec 01 20:47:32 gr-sim kernel:  exc_page_fault+0x64/0xb0
Dec 01 20:47:32 gr-sim kernel:  asm_exc_page_fault+0x22/0x30
Dec 01 20:47:32 gr-sim kernel: RIP: 0033:0x7f265eb7ff27
Dec 01 20:47:32 gr-sim kernel: Code: Unable to access opcode bytes at RIP 0x7f265eb7fefd.
Dec 01 20:47:32 gr-sim kernel: RSP: 002b:00007ffcc9d824e8 EFLAGS: 00010207
Dec 01 20:47:32 gr-sim kernel: RAX:<PHONE_NUMBER>010000 RBX:<PHONE_NUMBER>fffff8 RCX:<PHONE_NUMBER>000020
Dec 01 20:47:32 gr-sim kernel: RDX:<PHONE_NUMBER>003fb8 RSI:<PHONE_NUMBER>cb00c0 RDI:<PHONE_NUMBER>4b0040
Dec 01 20:47:32 gr-sim kernel: RBP: 00007ffcc9d875c8 R08: ffffffffffffffc0 R09:<PHONE_NUMBER>010000
Dec 01 20:47:32 gr-sim kernel: R10:<PHONE_NUMBER>0032d7 R11:<PHONE_NUMBER>000000 R12: 00000605d0810000
Dec 01 20:47:32 gr-sim kernel: R13:<PHONE_NUMBER>010000 R14: 00007ffcc9d875b0 R15:<PHONE_NUMBER>fffff8
Dec 01 20:47:32 gr-sim kernel:  </TASK>
Dec 01 20:47:32 gr-sim kernel: Mem-Info:
Dec 01 20:47:32 gr-sim kernel: active_anon:4040489 inactive_anon:3595915 isolated_anon:0
                                active_file:193 inactive_file:256 isolated_file:0
                                unevictable:2360 dirty:0 writeback:0
                                slab_reclaimable:239872 slab_unreclaimable:90061
                                mapped:143 shmem:2607 pagetables:25101 bounce:0
                                kernel_misc_reclaimable:0
                                free:83700 free_pcp:62 free_cma:0
Dec 01 20:47:32 gr-sim kernel: Node 0 active_anon:16161956kB inactive_anon:14383660kB active_file:772kB inactive_file:1024kB unevictable:9440kB isolated(anon):0kB isolated(file):0kB mapped:572kB dirty:0kB writeback:0kB shmem:10428kB shmem_thp: 8192kB s>
Dec 01 20:47:32 gr-sim kernel: Node 0 DMA free:11264kB boost:0kB min:28kB low:40kB high:52kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15360kB ml>
Dec 01 20:47:32 gr-sim kernel: lowmem_reserve[]: 0 925 31819 31819 31819
Dec 01 20:47:32 gr-sim kernel: Node 0 DMA32 free:125304kB boost:0kB min:1964kB low:2908kB high:3852kB reserved_highatomic:0KB active_anon:400832kB inactive_anon:468648kB active_file:188kB inactive_file:16kB unevictable:0kB writepending:0kB present:1069>
Dec 01 20:47:32 gr-sim kernel: lowmem_reserve[]: 0 0 30894 30894 30894
Dec 01 20:47:32 gr-sim kernel: Node 0 Normal free:198232kB boost:193272kB min:258856kB low:290488kB high:322120kB reserved_highatomic:0KB active_anon:15761784kB inactive_anon:13914428kB active_file:208kB inactive_file:1628kB unevictable:9440kB writepen>
Dec 01 20:47:32 gr-sim kernel: lowmem_reserve[]: 0 0 0 0 0
Dec 01 20:47:32 gr-sim kernel: Node 0 DMA: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 1*1024kB (U) 1*2048kB (M) 2*4096kB (M) = 11264kB
Dec 01 20:47:32 gr-sim kernel: Node 0 DMA32: 60*4kB (UME) 73*8kB (UME) 166*16kB (UME) 169*32kB (UME) 143*64kB (UME) 112*128kB (UE) 69*256kB (UE) 29*512kB (UE) 3*1024kB (U) 2*2048kB (ME) 13*4096kB (UM) = 125304kB
Dec 01 20:47:32 gr-sim kernel: Node 0 Normal: 424*4kB (UME) 5085*8kB (UME) 4596*16kB (UE) 2508*32kB (UE) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 196168kB
Dec 01 20:47:32 gr-sim kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
Dec 01 20:47:32 gr-sim kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
Dec 01 20:47:32 gr-sim kernel: 13225 total pagecache pages
Dec 01 20:47:32 gr-sim kernel: 10175 pages in swap cache
Dec 01 20:47:32 gr-sim kernel: Free swap  = 0kB
Dec 01 20:47:32 gr-sim kernel: Total swap = 2097148kB
Dec 01 20:47:32 gr-sim kernel: 8334302 pages RAM
Dec 01 20:47:32 gr-sim kernel: 0 pages HighMem/MovableOnly
Dec 01 20:47:32 gr-sim kernel: 168932 pages reserved
Dec 01 20:47:32 gr-sim kernel: 0 pages hwpoisoned

I am doing a build with vm.overcommit_memory=2 and a ratio of 100 to see if that fixes the issue.

Unfortunately, Unreal Engine 5 has notoriously high memory requirements when building the DDC and compiling shaders. The required memory scales largely based on the number of ShaderCompileWorker processes that run in parallel, which is determined by the number of CPU cores/threads. I've had plenty of builds fail during the DDC step due to OOM errors on machines with 8c/16t and 32GiB of RAM, although it's worth noting that the scaling isn't exactly linear, since I've run plenty of successful builds on machines with 16c/32t and 64GiB of RAM. It seems that a 2:1 ratio of RAM to CPU threads is fine, but only so long as the total amount of system memory is sufficiently large that any fixed overheads (e.g. memory used by system processes) represent a negligible percentage of memory use.

Thanks for that @adamrehn. I was wondering if that was the case re ShaderCompilerWorker being naive in its memory allocation.
I attempted to circumvent this with this patch https://github.com/Greenroom-Robotics/ue4-docker/commit/19dd5f5d0c8d04a3ca03786c9d654ab690caf817#diff-2faa50ca4c6d80d7dd0e093c700a90935e359adf3b9ea640a108c2b8d1cbd9edR596 but it doesn't look like it made any difference. nproc returns the correct number but llvm seems to be reporting 24 parallel actions regardless of the cpus set. I am not going to wait until the compile steps are done to find out it made no difference.

From Engine/Config/BaseEngine.ini
; Percentage of your available logical cores that will be reserved and NOT used for shader compilation
; 0 means use all your cores to compile Shaders
; 100 means use none of your cores to compile shaders (it will still use 1 core).
PercentageUnusedShaderCompilingThreads=50

I am going experiment with tweaking this value to see what happens.

I'd ask whether you actually need DDC. Maybe --exclude ddc and move on. The thing with shared DDC is that it becomes useless as soon as you change a single rendering option in your game.

I'd ask whether you actually need DDC. Maybe --exclude ddc and move on. The thing with shared DDC is that it becomes useless as soon as you change a single rendering option in your game.

Very valid point. I think you're right. I'm not terribly familiar with the build steps of the engine so I was under the impression it was required (hence it being default).


Upgrading Google Cloud Dependencies

Test case changes are due to https://github.com/google/google-api-java-client/issues/1151

Build break caused by https://github.com/travis-ci/travis-ci/issues/10055

Resolves #204


Can konga configure kong in kubernetes?

How does konga associate operations in the current kong deployment in kubernetes?

Perhaps using decK? https://github.com/Kong/deck


Set parent last for instances created with Utility.Create

See
http://devforum.roblox.com/t/psa-dont-use-instance-new-with-parent-argument/30296

https://github.com/ROBLOX/Core-Scripts/blob/master/CoreScriptsRoot/Libraries/RbxUtility.lua#L916
Should also update this one


iceberg fails to display information on a local repository

I created a local repository in Iceberg. The code was already loaded in the image with Metacello (github repo).
When I click on the newly created repository, I get a red morph.
The problem is that Iceberg cannot get information on the current version of packages in the image because the local repository is one version below than the current version loaded.
Maybe Iceberg should do a fetch on the local repo to get latest versions before trying to get the version.

As of https://github.com/npasserini/iceberg/commit/1b4d870ef948137cf0eecda45a53e52168ebe3a2 does not seem to fail, added test testImportOutdatedLocalRepository


Crash of markdownlint-cli2 and vscode-markdownlint on invalid markdown

Ran a big codebase of markdown through the linter, and found an edge case that results in the parser crashing and unable to process the remainder of the files for linting. This happens both from the cli version and the vscode version (since it seems like the vscode one just uses this lib internally)
Output from linter is:
[1:27:05 PM] ERROR: Exception while linting with markdownlint-cli2:
TypeError: e[n].slice is not a function

example markdown that reproduces:
1. some text
   :::note

inner text

:::

2. some more text

It appears to be related to a :::note style callout existing within an ordered list.
Some more versions that reproduce the crash:
- some text
   :::note

inner text

:::

- some more text

* some text
   :::note

inner text
:::

* some text
   :::note

a

Thank you for reporting this! It looks like an issue with the micromark parsing library. I've opened an issue for them here: https://github.com/micromark/micromark/issues/173.

I've made a PR to the micromark-extension-directive project which should prevent this crash once merged, released, and incorporated: https://github.com/micromark/micromark-extension-directive/pull/27

v0.15.0


IC2-111: fix setBond

remove uDiff from GetUnbondingInfo return value
compare stake with voting after account.bond and account.unbond updated
unbond Expire will be updated when unbond value increase
unbond Expire will not be updated when unbond value decrease

please, refer to test_BOND.py::test_stake_bond_unbond_delegation, which I wrote as it is in the document(ICON2 Design - Stake, Delegation, Bond). #15 fails.


✨ Add support for user-mounted widgets

Category: Feature

Overview
Just an idea...
This PR would allow a user to mount a custom widget.
Usage:
Create a widget, and mount it into the Widgets directory.
Sub-folders are allowd, so can be mounted as directory.
Then list that widget under appConfig.customWidgets, like:
appConfig:
  theme: colorful
  customWidgets:
  - identifier: my-component  # How the component should be referenced
    component: MyComponent    # Must match the widget component's file name

Then use it like normal:
sections:
- name: Example Section
  widgets:
  - type: my-component

Limitations:

Rebuild is required
Currently, must be placed within Components/Widgets directory
Typo in configuration (file name or identifier) will throw error not handled by UI

Todo:

Bit more research, to see if there is a better option
If proceeding, then add docs and update schema

Issue Number this comment
New Vars
// TODO
Screenshot N/A
Code Quality Checklist (Please complete)

[X] All changes are backwards compatible
[X] All lint checks and tests are passing
[X] There are no (new) build warnings or errors
[ ] (If a new config option is added) Attribute is outlined in the schema and documented
[ ] (If a new dependency is added) Package is essential, and has been checked out for security or performance
[ ] Bumps version, if new feature added

This looks great. We could modify the COMPAT object to have the full path to the component. 'adguard-dns-info': '@/components/Widgets/AdGuardDnsInfo.vue',. Then when declaring customWidgets the component could be component: @/any/src/NewWidget.vue so you are not locked to any directory. Maybe that means you could mount something pre-compiled in node_modules and it might work? My docker dev machine is currently down so I can't test yet.
I think technically you don't need to define customWidgets as the code currently reverts to this.widget.type when detecting the type. This means you could do something like -type: @/any/src/NewWidget.vue and it should work. But maybe it would be better UX having to define customWidgets so you could output an error if the widget doesn't exist rather than fall back to this.widget.type and assume it is a path.
This might address 2 out of 3 limitations. Maybe 3 if its possible to precompile and mount that instead.

I experimented with the vue bundles a little bit trying to figure out the precompiled route. I tried exporting as wc and a lib. Because of the optimizations and bundle chunking I don't think it would be easy to inject that into the page, not without being too hacky. I am not sure https://github.com/FranckFreiburger/vue3-sfc-loader could work for more complex components that have dependencies.
I am thinking the build is probably unavoidable at this point with this approach. The upside is everything is minified and chunked as expected which will probably come in handy with multi-page support and dynamically loading only the chunks that are necessary.

@Lissy93 Would you be able to share some insight as to why this was closed? No longer interested in the feature, pursuing a different implementation, etc? Thanks!


Forcing.h is unguarded

Forcing.h is unguarded, so it is possible to run into errors where a subclass might define it more than once and run into errors.
There should just be an #ifndef guard around it.

Thank you for finding this @christophertubbs. I will fix @jdmattern-noaa .


[WIP] Phabricator remote integration

This is currently work in progress. I have started to integrate phabricator as a remote into drone. The authentication already works, but now we need to find ways to add the other missing parts as well.
The client parts are taken from the Gitlab client.

 You should sign our Contributor License Agreement in order to get your pull request merged.

It still doesn;t really work is much more complicated. As nobody requested that I will close that for now.

I would really like to be able to integrate Phabricator with Drone somehow.

Cool, I might look into that after 0.9 comes out, then. :slightly_smiling_face:

@bradrydzewski I suppose should be https://github.com/drone/drone-scm

oops, it is https://github.com/drone/go-scm


Missing Issue: The subscription is not registered to use namespace 'Microsoft.AzureActiveDirectory'

I encountered the error:
The subscription is not registered to use namespace 'Microsoft.AzureActiveDirectory'. See https://aka.ms/rps-not-found for how to register subscriptions.
When attempting to make a Customer Tenant in Entra. But this issue is not listed here.

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

ID: bc2ab43e-b864-aabd-9952-798e2af66264
Version Independent ID: 7064e4cd-4e84-0597-400a-71698b16bc6e
Content: Troubleshoot common Azure deployment errors - Azure Resource Manager
Content Source: articles/azure-resource-manager/troubleshooting/common-deployment-errors.md
Service: azure-resource-manager
Sub-service: troubleshooting
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

solution is to add said provider:
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider-1

@fei0x Thanks for your comment! We will review and provide an update as appropriate.

@fei0x Yes, adding the said namespace as provide is solution. The referred document mentions about the said error not directly but in many places as shown in below screenshot. Detailed explanation is provided in this document which is referred in that document.


Unable to form nuget packages when referencing 3.1.0 EfCore.BulkExtensions

When referencing latest EFCFore.BulkExtensions, we are unable to create packages via NuGet pack. This happens because of EFCore 3.1.0 sub dependencies inside bulkextensions package. This on the other hand is due to known issues within NuGet itself, which were handled in EFCore 3.1.1 packages.
More information can be found from here:
https://github.com/dotnet/efcore/issues/19542
NuGet pack exception 'The DateTimeOffset specified cannot be converted into a Zip file timestamp.' seems to be thrown because of following assemblies:

Microsoft.Data.Sqlite.dll
Microsoft.EntityFrameworkCore.Sqlite.dll

Lib updated to 3.1.1.


Add a message

https://github.com/control-toolbox/CTBase.jl/blob/d2aa9b48ef2a799e921d7fc1e49276ef8b2c64ce/src/init.jl#L60
Add a message when a key is given but has no meaning.

This is related to https://github.com/control-toolbox/CTBase.jl/issues/173.

This is related to #173 🤭

Done with https://github.com/control-toolbox/CTBase.jl/pull/184


MH-12603, Take 'ng' out of the youtube composite operation

remove ng- prefix from exception-handler-workflow
MH-12603 Take 'ng' out of the workflow filenames

@reiferschris Since this is a bugfix, can you please redirect the pull request to r/5.x?

@staubesv i hopefully redirected it to r/5.x, now I'm wondering why all the previous commits are in this pull requests history? Did I mess up?

@reiferschris You probably need to rebase your commit on 5.x or your gonna introduce all the commits that aren't in 5.x.

@staubesv i hopefully redirected it to r/5.x, now I'm wondering why all the previous commits are in this pull requests history? Did I mess up?

The reason is that your patch was based on a newer branch and by simply changing the target branch you are telling Github that you want the other branch plus your patch to be merged into r/5.x. What you need to do additionally to changing the target branch here in Github is to rebase your source branch using git. What you essentially need to do is:
git checkout develop
# Your develop since that is the branch your patch is in

git fetch upstream
# assuming that upstream is your remote name for the Opencast repo

git rebase -i upstream/r/5.x
# This will ask which patches you want to add to `r/5.x`
# Delete everything except your patch

git push -f origin develop
# Overwrite your remote branch

In general, I recommend to always create a branch as first step since having a develop which really is a r/5.x plus a patch can be confusing although it is no technical problem.

@reiferschris Sorry for the trouble my request has caused... but for low-risk bugs like this, it makes sense to include it in all supported version - otherwise, another person might raise another pull request to fix it in older versions.
In case you are unfamiliar with git command line, you can also just close this pull request, redo the change (but this time branching away from r/5.x) and raise another pull requests.

@staubesv I will close this pull request and raise a new one from my own fork. Thank you for being so patient with me, I am indeed new to this. Hopefully next time I will make fewer mistakes. I fully understand your reasoning for the request.
Also thanks to @lkiesow and @KatrinIhler for explaining what I could do to fix this, next time I will create a new branch first, so I don't run into issues later.

@reiferschris Thanks a lot for contributing to Opencast!


evaluate observability env var before disabling metrics collection

#1522  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Reduce useless resolutions

Some resolutions might be useless + I didn't update the lockdir (because I am on the github's web editor)
Apply on top of #1082

Error in the CI https://dev.azure.com/onivim/oni2/_build/results?buildId=8220&view=logs&j=ca1de7b4-19db-5646-f7fe-ed7c2dd3de8a&t=4542f74c-da99-569e-bca0-ee14ffe6ea2f&l=14 but should be in other issue/PR

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: bryphe:x: Et7f3You have signed the CLA already but the status is still pending? Let us recheck it.

/azp run

/azp run

CI failure looks unrelated to this, so could we get this merged once the CLA stuff is sorted with @Et7f3?
I'm hitting issues adding resolutions to various things (i.e. testing the textmate changes) unless I have these changes applied locally.

CI failure looks unrelated to this, so could we get this merged once the CLA stuff is sorted with @Et7f3?

For this change - I'm OK bringing it w/o a CLA (since it's just a couple of package.json changes).

I'm hitting issues adding resolutions to various things (i.e. testing the textmate changes) unless I have these changes applied locally.

Sure thing, I just checked the latest build and you're right - seems unrelated. I'll override and bring in now 👍


Dangling "pick-right-solution" references - Indonesian

This is a Bug Report
Problem:
The link from "Cluster Administration Overview" to " Picking the Right Solution" is a 404.
docs/setup/pick-right-solution/ does not exist, as it was removed as a redundant page.
Proposed Solution:
Update the stale links to point to Setup page
The references on this page point both too the root of the pick-right-solution page, but also to various IDs that no longer exist, there may be better pages to point those links to.
Page to Update:
https://kubernetes.io/id/docs/setup/
https://kubernetes.io/id/docs/concepts/cluster-administration/cluster-administration-overview/

/good-first-issue
/language id


jsontogeojson: Add docs

Please can we add helpstrings for the command and its arguments.

Just to be clear, what do you mean by helpstrings - stuff that comes up when you pass --help to the cli?
Tho yes, any docs here are better than the current first commit!

Yep, I was thinking that if we add the docs directly in the code that will be easier for users and maintainers as the docs will be proximate to the use of the tool and the actual code.
As much as possible, we can then reuse that documentation in the https://ofdskit.readthedocs.io/en/latest/


Change restriction mode of user/last_email_sent

see https://github.com/OpenSlides/OpenSlides/issues/6723


Tidy up suggestions

Hey man, here are some tidy up suggestions. I haven't looked at the "meat" of the functionality but just quickly picked off some superficial improvements that I think improve readability.

Main changes:

use environ to pull out environment variables
use clojure.tools.logging rather than println
try to avoid threading macros when you only have two items to thread
closing parens always group together on the final line
used IntelliJ / Cursive's alignment tools to tidy up alignment


Add about CVAT

Added about CVAT - tool name, description, server version, core version, a link to gitter chat and a link to forum on intel developers zone.
As of now, both the "What's new?" and "License" haven't been linked to anything. Kindly let me know how do you want to change the md files to html. I was thinking of using react-markdown to achieve this.

As of now, both the "What's new?" and "License" haven't been linked to anything. Kindly let me know how do you want to change the md files to html.

Right now I think it would be enough, just to open a new tab in a browser with github URL of CHANGELOG.md and LICENSE correspondingly.

@LiSa20120
Hi, thanks for the pull request
There are some issue in the code, mine and codacy. Could you please fix them?
Also speaking about design, what do you think about the screenshot below?

I've done next things to achieve it:

Added property:

            okButtonProps: {
                style: {
                    width: '100px',
                },
            },

to Modal.info({

Changed versions like:

                        <Text strong>
                            Server version:
                        </Text>
                        <Text type='secondary'>
                            {` ${serverInfo.version}`}
                        </Text>

                        <Text strong>
                            Client version:
                        </Text>
                        <Text type='secondary'>
                            {` ${core.client.version}`}
                        </Text>

Changed justify type from 'center' to 'space-around'
Removed all span props from Col elements.

Yes, I will make the changes suggested.

@bsekachev I have made the changes. Could you please let me know if this is fine?
Thank you :)

@LiSa20120
Great,
Will look it on Monday :)
There are some code issues found by a static linter.
Issues like Unable to resolve path to module don't matter. But also there are some minor issues about codestyle and unused imports, could you please fix them?

@LiSa20120
Hi, works great!
Just a couple of comments.
And static linter still shows several minor issues, could you please look at them?

Hi @bsekachev
Is there anything I can do to rectify the codebeat review

@LiSa20120
Do not worry about codebeat

Alright
Thank you :)

@LiSa20120
But here are some unresolved issues :)


conda-forge UnsatisfiableError on windows

Hi,
for some reason, if I want to install mapclassify with python3.7 on windows from conda-forge, I'll get UnsatisfiableError (https://ci.appveyor.com/project/martinfleis/momepy/builds/28862313). In the environment is nothing else:
name: test
channels:
  - conda-forge
dependencies:
  - python=3.7
  - mapclassify

If I unpin python, I get python3.8 but mapclassify 2.0.1. So I sense the issue with scikit-learn, but I have no clue why this happens. The same situation is with pysal.
Edit: If I keep mapclassify only, you get 2.0.1, if I pin mapclassify to 2.1.1 I get the error.

The issue is caused by scikit-learn as installing that only gives the same behaviour. So I will close this as it is not mapclassify issue, but at least you are aware of it.


Clappr -> clappr

Clappr name is lowercase https://www.npmjs.com/package/clappr
This cause failure on webpack build

Hey, please merge this PR! Very useful!


django-autocomplete-light and jquery compatibility

I'm using often autocomplete light in my projects and I'm trying to use it with mezzanine.
First at all, I've noticed that the jquery loading broke the admin panel: you can't execute any action to selected rows, the event simple wasn't fired. No javascript errors or logs.
Just add this line to your admin/base_site.html
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.9.0/jquery.js" type="text/javascript"></script>

On inlines elements, autocomplete override the "add new" on bottom, but it is broken because of the override made from mezzanine.
This third-part app works fine in grappelli, could you try to make it usable in mezzanine?

Please post this to the mailing list.


fix: Resend Welcome Email

Fix: Resend Welcome Email

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 3

See the complete overview on Codacy


CreatorName and CreatorEmail fields incorrectly populated

With the latest version of Management Shell the CreatorName and CreatorEmail fields are populated with the O365 Members Group, not the person who called the site design.

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

ID: 1afac891-6cf5-1746-6392-8cb61a441770
Version Independent ID: b5d1f95b-f40b-8d0c-7334-7608a3add9ff
Content: Using site designs and Power Automate to track site creation requests
Content Source: docs/declarative-customization/site-design-trigger-flow-tutorial.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Hello @Squiggleh
I have been able to reproduce the reported issue. According to my Flow's history, the issue has been there since April. During my tests, I got the following values:

CreatorName: {GroupDisplayName} Owners
CreatorEmail<EMAIL_ADDRESS>
Regards,
Jarbas

This forum is for SharePoint development issues so I'm not sure it's the right place for SPO Mgmt Shell bugs to be reported. I've asked MSFT where they would recommend where to post issues... likely TechCommunity... I'll leave this open until I have more details.

Yeah, I've also been looking where to post this for more clarity from a
technical perspective.
But if it's not a bug and is now the intended functionality, this will need
to be updated.
On Fri, 5 Jun 2020, 18:59 Andrew Connell<EMAIL_ADDRESS>wrote:

This forum is for SharePoint development issues so I'm not sure it's the
right place for SPO Mgmt Shell bugs to be reported. I've asked MSFT where
they would recommend where to post issues... likely TechCommunity... I'll
leave this open until I have more details.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SharePoint/sp-dev-docs/issues/5817#issuecomment-639669963,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE24YXIQPFGMUVBEVNOHIALRVEW7ZANCNFSM4NQV4M2A
.


unable to upload media other than PNG

when trying to upload an asset folder with paired GIF/JSON files, after running Metaplex upload I am receiving an error that the amount of JSON files is not corresponding with the amount of PNG files
I've tried making changes to the CLI.ts file to allow different media and remove the check on PNG and running yarn build, but it still throws the same error - so it seems to be running a cached version of CLI.js which I cannot change (?)
Edit - I have also tried deleting cache

I also tried deleting cache ^

I don't think you can upload any format other than .png but i think if you want you add file with any other format, you'd have to include if under the properties key in the token metadata and use a .png as the cover. But I haven't tried this.

Ah yeah I did update the json metadata also but sing .png caused the gif to become a sequence of PNGs so I thought that wouldn't work. However,  are you suggesting that if it's uploaded that way, the altered metadata will cause it to be displayed successfully as a gif on arweave?

You may use the ?ext={file_extension} query to provide information on the file type.
Try this.

Hi. @robindunkerley
Did you resolve this issue yet?
I tried to upload mp4 file as well, but I can not upload the mp4 without the png.
thank you in advance.


Default Embedded format

This PR introduces a default embedded view that is capable of rendering differently based on the container size that is yielded to it. Note that the large thumbnail design has some fundamental issues regarding the integrity of the card boundary, so i eschewed the current design and did my best to make something tasteful at the large thumbnail breakpoint.

This is what it looks like for cards without a thumbnail image:

we still have issues like this that we need to sort thru where in the places that the embedded cards are being rendered we are not catering for the new design. Note that the smalled embedded card format is a bit too large to fit in the form's grid, as well as the border for the embedded card clashes with the form

Note that the percy diffs are worth noting. I'm gonna just leave them there so people can see how this have changed. There are a few diffs with missing stuff that I'm still working thru. One of the main things tho are some card boundary integrity issue--specifically padding and borders. that used to be drawn outside of the card for the embedded view. we are gonna have to now handle that inside of the card for embedded view. the percy diffs illustrate how for the non-default embedded cards, they were relying on padding and borders being provided by the system that now are up to the embedded template.

From the boxel sprint planning:
cards do not draw their own borders, however cards do own the padding within the border

I took executive privilege regarding the design docs, and adjusted the "strip" style card layout to work with the edit format's form. this meant reducing the height of the strip style to 40px. We'll need to address this in the design doc

For these types of percy issues with the missing padding, instead of introducing padding into all the embedded templates (since the cards own the style within the card boundary), let's hold off until we have a way to request the prerendered CardDef embedded HTML to insert into the area yielded to the field. That should be a few PR's from now.

There are also percy diffs that look like this that appear to have missing content. I double checked, in actuality, the content is there, it's just that it is being rendered off the screen. this is more fallout from injecting styles (e.g. padding) within the card boundary. The solution here is just like that above, we need to render these fields using CardDef prerendered embedded templates that will have the consistency that we were previously trying to enforce in the delegated render of embedded cards.

I think we'll want to use the CardDef embedded fields for edit mode.

No need to change anything in this PR, but I'll note that I don't think this will be the case. I think in the case of a LinksTo field with the parent card in edit mode, we would want to use the Card's own embedded format, if it has one.


bug: React fragments not working

Describe the bug
As the title says react fragments are not working, both with  <> </> and <React.Fragment>  </React.Fragment>
To Reproduce
Steps to reproduce the behavior:
just add a react fragment anywhere in the project
Expected behavior
should handle React fragments
Screenshots

Additional context
Add any other context about the problem here.

I just realised that all the exmaples are in jsx and there is no mention of typescript in the project, so million doesn't support typescript ? :0 this error could be cuz of typescript

million supports typescript

Million doesn't support fragments AFAIK. Maybe we can start by implementing nested fragments, the n consider a performant way of creating top level fragments

Million doesn't support fragments AFAIK. Maybe we can start by implementing nested fragments, the n consider a performant way of creating top level fragments

This should be fun.

Any updates on this @aidenybai?

#316

Top level fragments should be explored in a new issue. For now, fragments should work within blocks: https://twitter.com/aidenybai/status/1650406345517199361?s=20


Importing RCT packages with React namespace to support react-native 0.40.0 on IOS

Updating namespaces to make material-kit compatible with react-native 0.40.0

Hi @ishabo,
Besides that this PR is duplicated, the new import statements should be with angle brackets (see https://github.com/facebook/react-native/commit/e1577df1fd70049ce7f288f91f6e2b18d512ff4d) like in https://github.com/xinthink/react-native-material-kit/pull/288.

Duplicate


Question on EOS

Hi all,
I'm trying to understand the concept of Kafka and EOS and I came across this library which should have full support as far as I understand. I looked at the examples provided with this repo, especially this one: https://github.com/twmb/franz-go/blob/master/examples/transactions/eos/main.go
I'm clearly missing some basic understanding and I guess I have many questions, but to begin with, does EOS require beginning and committing a transaction like in the provided example?

Probably not a question for this library, EOS is provided through transactions...so yes. The idea is that you when you consume a record, and during the processing you produce records on another topic, the 'commit' of the incoming records is in the same transaction as the records you produce on other topics....
So, anyone consuming the records you produce, will not see them until the transaction is complete (assuming your other consumer is configured correctly)...
If you error out before the transaction is complete, both the commit and produced records would be discarded.
Once you commit an offset, you will never read that offset again, so you will never produce any records for that offset again.
Hence Exactly Once
There is a bit of a misnomer here, as if you fail in the middle of a transaction, you will consumer the incoming record more than once.
Hope that helps