Objects with semi-transparent PNGs are not semi-transparent

Hi,
I'm trying to create a leaf, which is typically a rectangle with a semi-transparent PNG texture.
I have the following node setup:

And while it looks correct within blender (with viewport alpha: alpha blend):

It looks very strange after exported:

Not only it's not transparent where it should be, but my guess is that the R and G channels are swapped for some reason.
Am I doing something wrong with the node setup? Or is it something else?
Here's the blend file, if anyone wants to test:
test.zip

Definitely a bug, but I don't think it's related to transparency.  I re-exported your PNG on a white background with no transparency, plugged it straight into the Base Color node and I still get funky colors.

Definitely a bug, but I don't think it's related to transparency. I re-exported your PNG on a white background with no transparency, plugged it straight into the Base Color node and I still get funky colors.

Oh, thanks for checking. This gradient color gave me an idea, it might have vertex colors, so I checked, and it does!
Removing the vertex colors solved this "funky-color-issue", but it's still not transparent where it should be. Any idea on that?

Ah good. I've tried a few things but nothing working so far.  I think that the exporter only really works with the Principled BSDF node, and anything like a mix shader that comes after that isn't exported.  That's my understanding anyway.  I notice that the BaseColor input for the principled node accepts RGBA values, not just RGB.  I can't figure out how to recombine the RGBA from the Image Texture node using its 'Color' and 'Alpha' outputs. I might be heading in the wrong direction here anyway!

From the docs, here's an example for a basic node setup for gltf: https://gltf-blender-io-docs-gbueavkvns.now.sh/_images/addons_io-gltf2-material-principled.png
So I guess transparency should work in a similar way to emission. I know we still have problems with emission as well, so I guess we have to wait (or contribute) to get these things done.

I hadn't seen this manual.  What route did you use to get to that image?  The addons -> glTF 2 section is a 404 at the moment.

I hadn't seen this manual. What route did you use to get to that image? The addons -> glTF 2 section is a 404 at the moment.

I've found it among the issues, right here: https://github.com/KhronosGroup/glTF-Blender-IO/issues/97
This is the link for the current prototype of the docs: https://gltf-blender-io-docs-fuznnktuig.now.sh/addons/io_gltf2

Docs are now live, here: https://docs.blender.org/manual/en/dev/addons/io_gltf2.html
Are you using the Alpha Clip mode on the material? I think you'll need that.

Oops, should have said using Alpha Clip mode, and also setting a clip threshold >0. With 0.5, and vertex colors disabled, I see:

... the edges are  a bit rough, but adjusting the clip threshold should resolve that.

Oh, you're right, it works that way. So is it the correct behavior? I guess this method only works if I want fully opaque, or fully transparent pixels. But what if I want a semi-transparent look on some parts?

If you want semi-transparent pixels, use the Alpha Blend mode instead. But note that semi-transparency will be subject to various limitations in realtime engines (example, example) – for cutout/mask shapes like leaves on a tree, Alpha Clip will be much better.
This exporter cannot parse nodes like Mix Shader, so the alpha mode must be set appropriately.

Ok, thanks!


I have AS+ working in client, but not on local forge server

---- Minecraft Crash Report ----
WARNING: coremods are present:
FMLPlugin (InventoryTweaks-1.59-176.jar)
CCLCorePlugin (CodeChickenLib-1.8-<IP_ADDRESS>-universal.jar)
CodeChickenCorePlugin (CodeChickenCore-1.8-<IP_ADDRESS>-universal.jar)
CCCDeobfPlugin (unknown)
NEICorePlugin (NotEnoughItems-1.8-<IP_ADDRESS>-universal.jar)
Contact their authors BEFORE contacting forge
// You're mean.

I even tried to copy the configs/files from my client to the local server and also tried to remove them to get new defaults, no change.

This was fixed  a while back with some mixins updates.


Test unification + RFC232/268 support

This is still a WIP (see "To Do" below), so don't merge it yet! It should be fully working actually, as I have been using this branch successfully for migrating a big (mocha-based) test suite. But not yet ready for prime time... But I would certainly love some feedback asap, as so many things have changed! 😬
So, this needs some explanation...
What problems it solves

allow to use ember-cli-yadda with Ember's new testing API (RFC232 / RFC268 based)
adds possibility for custom test setup and teardown (fixes #47)
unifies previous separate test runners (acceptance, component) to a single one, allowing you to run any kind of tests: acceptance (application), component (rendering), unit etc.

Solution

As the new testing APIs don't use any custom moduleFor* functions anymore to create the module and  setup the test, instead they only use the standard module/test or describe/ it from 'qunit' itself or mocha respectively and some setup*Test functions for test setup, this allows us to have a unified test runner, but requires some means for custom test setup.
For the custom test setup, I extended the runtime annotations feature, added by @sfbwalder in #52. Specifically I introduced two new hooks in yadda-annotations.js: setupFeature and setupScenario. This allows the user to provide any kind of custom test setup and teardown logic, as this module lives in user land and can be modified in any way.
The default yadda-annotations.js (created by the blueprints) would be extended with a default setup implementation (see https://github.com/albertjan/ember-cli-yadda/compare/master...simonihmig:test-unification?expand=1#diff-396322b0f44cb1c286e305423d02b02eR50), that adds support for 3 setup related annotations:

@application: will call the RFC268 setupApplicationTest() for an application tests (formerly acceptance)
@rendering: will call the RFC232 setupRenderingTest() for a rendering tests (component)
@context: will call the RFC232 setupTest() for any kind of other Ember test (unit, model)
a feature/scenario without any of these tags would run a plain test without any Ember specific integration

These default setup implementations can be changed and extended at will, e.g. to extend the @application setup with additional setup logic (see example below), or additional annotations could be implemented, e.g. a @mirage tag to call setupMirage() (required for the new testing APIs with the latest Mirage release)

Caveats

The unified test runner does not support any tests requiring a custom moduleFor* function, i.e. is not compatible with old school tests. So this is a breaking change! The old testing API will only work with previous releases. We probably have to maintain those for eventual bug fixes, until users have migrated their test suites to the new APIs
The previously available "separate steps" mode for mocha-based tests has been removed for these reasons:

it would not work with the unified test runner (has to wrap a scenario in describe() and each step in it(), so would require a specialized one
the test setup would have required some "unique" workaround, i.e. use before/after instead of beforeEach/ afterEach. But the provided setup functions do not allow this, as it would be error prone (see https://github.com/emberjs/ember-mocha/pull/196). And requiring the user to implement all the setup logic with the base framework integration function from @ember/test-helpers (rather than the convenient setupApplicationTest() from qunit/mocha) would be very inconvenient, hard to maintain and also error prone (see https://github.com/emberjs/ember-mocha/blob/70cc221ac76d9a170191ab8a4ece7c853975ca49/addon-test-support/ember-mocha/setup-container-test.js#L12-L54)
there might be a way to achieve the desired effect (better traceability of failing steps) by some other means, maybe by some custom chai plugin to automatically prefix error messages with the step name they occured!? If not, users should probably use this.step for their custom error message, as it is used in this test suite also

the annotations feature (i.e. the default implementation in yadda-annotations.js) seemed to ignore any tests with an annotation, if that annotation was not present in ENV.annotations, especially when ENV.annotations was simply not used. Not sure what the exact reasoning for this was, but at least the annotations feature was focusing only on skipping tests previously, while now it is used for totally different purposes also (i.e. test setup). The previous logic was very confusing in this context, as any test tagged with e.g. @application would simply be ignored by the default checkAnnotations() implementation (https://github.com/albertjan/ember-cli-yadda/blob/master/tests/helpers/yadda-annotations.js#L29-L30). This has been changed now ( another breaking change!) as follows:

if ENV.annotations is used, only tests with the listed tags are run (same as before)
otherwise run all tests, regardless of their annotations!
this makes ENV.annotations effectively a "filter by tag" function (so no filtering applied if not used). I would think this is a common feature, at least I know this from other BDD frameworks (behat --tags=...)

Implementation details

the test runner is now a static module (in the addon-test-support tree), that it just imported from the generated test files, and not duplicated anymore for each test
Increased the minimum node version to 6, as it will hit end of life anyway this month IIRC, so we don't have to do another breaking change release for the node update
Updated this addon's test suite

use new testing API (e.g. use helpers from @ember/test-helpers and async/ await insteqd of andThen()
removed the unnecessary done() callback for sync tests

added some additional tests for @rendering and @context

Examples
Real world example of customized application setup + Mirage  + custom test reset (clear localStorage etc.) for Mocha based tests:
...
import resetState from './reset-application-test';
import { setupApplicationTest, setupRenderingTest, setupContainerTest } from 'ember-mocha';
import setupMirage from 'ember-cli-mirage/test-support/setup-mirage';

...

function setupYaddaTest(annotations) {
  if (annotations.application) {
    return function() {
      let hooks = setupApplicationTest();
      hooks.beforeEach(resetState);
      setupMirage(hooks);
    }
  }
  ...
}

To do

[ ] wait for the final API for ember-mocha to be clarified (https://github.com/emberjs/ember-mocha/issues/198), and ember-mocha to be released with RFC268 support
[ ] Update blueprints (as a separate PR probably)

I think I have addressed all the feedback so far.
For the remaining toDos, the mocha API has been finalized, but there's not yet a release of it. However I don't think we have to wait for it to merge this. For the blueprints I would like to tackle this as a separate PR.
So from my PoV, this is ready to be merged, if you all approve this!
Before this happens, I think we should publish the current master as 0.3.0, create some kind of "legacy"  branch to allow us to fix issues regarding the 0.3.x versions. Then we can merge this and any following PR for the new testing API (blueprints as mentioned) and later release this as a (breaking change) 0.4.0. As suggested here
What do you think?

I like your thought to publish the backwards compatible version as 0.3.0.  When we have breaking changes, I think we should go to 1.0.0 to follow semantic versioning 2.0 guidelines for breaking changes.

I think we should go to 1.0.0 to follow semantic versioning

I think my suggestion is in line with SemVer. 1.0.0 would suggest we are committed to a stable API, which I don't know if we really are. But that's a different topic.
For 0.x.y I think we can break whenever we want to, see https://semver.org/#spec-item-4. However I think it's best practice to do such a thing in a minor release (i.e. 0.4.0, as opposed to just a patch release). With a package specifier such as ^0.3.0 in your package.json (which covers 0.3.x, but not 0.4.0), that would prevent the user from accidentally getting in the breaking change.

Sure, that is fine.  Ready to publish current master as 0.3.0?

@sfbwalder I think so! 👍

0.3.0 is published.  I upgraded one of our apps to use it and it installed and ran green.

@sfbwalder great, thanks!

I prepared another PR to update the blueprints, that builds on top of this one. So, @albertjan @sfbwalder ok to merge?

I've just tried this out and it works nicely for me.
This definitely needs more documentation. This is the yadda-annotations snippet that worked for me with Mirage:
  if (annotations.application) {
    // From "Examples" here: https://github.com/albertjan/ember-cli-yadda/pull/65
I've just tried this out and it works nicely for me.

This definitely needs more documentation.

This is the `yadda-annotations` snippet that worked for me with Mirage (note that it differs from top post):

```js
  if (annotations.application) {
    return function (hooks) {
      setupApplicationTest(hooks)
      setupMirage(hooks)
      return hooks
    }
  }

This definitely needs more documentation.

Absolutely! But you are using the bleeding edge here, not released code, not even merged to master yet. So you should be warned! 😜

Minor comment... Currently the 3 default setup type annotations are application, rendering, context.  These blend in with other annotations.  They may be easier to reason about if they included "setup" or "test" like:

application-test, rendering-test, context-test

or

setup-application-test, setup-rendering-test, setup-context-test

Thoughts?

Yeah, that seems reasonable. To reduce the "mental gap", maybe we should name them the same as the functions they actually call. Also users probably know them already when using regular tests (non-yadda). So that would be:

@setupTest (see https://github.com/emberjs/rfcs/blob/master/text/0232-simplify-qunit-testing-api.md#setuptest)
@setupRenderingTest (see https://github.com/emberjs/rfcs/blob/master/text/0232-simplify-qunit-testing-api.md#setuprenderingtest)
@setupApplicationTest (see https://github.com/emberjs/rfcs/blob/master/text/0268-acceptance-testing-refactor.md#setupapplicationtest)

@sfbwalder Agree?

Yes, that will be good.

Reducing mental gap sounds good. Like the idea of lining those up.

Ok, just renamed those as proposed!
Feel free to merge at your will! :)


Update docs in using_doctr

This PR aims to:

modify dead links from the documentation in https://mindee.github.io/doctr/using_doctr/using_models.html such as https://mindee.github.io/doctr/using_doctr/models.html#doctr.models.detection.linknet_resnet18.
add db_resnet50_rotation and linknet_resnet18_rotation in https://mindee.github.io/doctr/modules/models.html
update one code block with 4 spaces

@frgfm @charlesmindee I think something went wrong on GitHub page deployment. It seems that it has not been updated because links are still broken.
I tested it locally before and here is the output:

You can see that there is a light blue background on each hyperlink on the screenshot. This is due to :py:meth:. This is not the case on the public docs:

Moreover, I added doctr.models.detection.linknet_resnet18_rotation and doctr.models.detection.differentiable_binarization.pytorch.db_resnet50_rotation in doctr.models in Package reference and there are still not present on public docs.
Also, I just noticed that Choose a ready to use dataset and Share your model with the community pages are not published. Is it expected ?

@odulcy-mindee my apologies, I selected the wrong version!
I realized this seeing your comment that the changes hadn't taken effect
By default, the documentation leads you to the last stable release. So to get the latest build, you need to select "latest", and now this works :)
https://mindee.github.io/doctr/latest/using_doctr/using_models.html
All good then!

@frgfm Oh cool ! Thanks for the tip haha ! :sweat_smile:


Create a section for the report banner and Hawaii values

Dependency:
Story #288 to be done
Business Context:
I want to display the banner with the public report and the Hawaii values below the navigation menu.
In Scope

Create a banner for the section with the annual report link, with the images and copy provided on the mockups
Link: https://hcsoc.hawaii.gov/wp-content/uploads/2023/01/2022-HCSOC-Annual-Report-FINAL.pdf
Create the "values" section

All above should be done for the 3 breakpoints supported: mobile, desktop, tablet.
Out of Scope

Open Questions

Mockup for the values icon section for mobile
Photo for the banner
Icons for the values section

Acceptance Criteria

Scenario:
Given
When
Then

Scenario:
Given
When
Then

Mockups
https://www.figma.com/file/SHMDMgzr7damRoT12ToEz5/Hawaii-CSOC-Advocacy--2?type=design&node-id=265-3755&t=ODfe3QQ4Bzg1AmxQ-0
Checklist (should be reviewed before grooming as the BA or Pair are writing the card—NOT reviewed for the first time at grooming)

[ ] Ensure to include all necessary mockups to this card.
[ ] Discuss what success/failure user feedback messages would be present, if any occur (front end/back end).
[ ] Discuss Feature Flag: Where could a development flag go to flag off incomplete work? Do we want to keep the flag long-term?
[ ] If this card is part of a sequence of cards, discuss if this card should be blocked until the testing of previous cards in the sequence have been finished.
[ ] Have we added edge cases as ACs that we're considered from a QA perspective
[ ] Should the new functionalities be offered only to users with certain permissions?
[ ] How should this functionality differ between different orgs, and if it does differ, what is the hinge point we should use for that functionality?

Notes:

Media-Query Breakpoints
mobile: 360px max-width
tablet: 834px max-width
desktop: 1920px max-width

Media Queries with React/MUI - https://mui.com/material-ui/react-use-media-query/


Add "Continue into SAP objects" to the main configuration screen

and pass to find

after https://github.com/abaplint/abaplint-sci-client/pull/134


Error with song 2

Describe your bug here.
I say it again. The song crashes! Again when I launch it! it used to work fine! But now some is bullshit!
Files:
events . JSON
fate . JSON
script . LUA
script . LUA :
function opponentNoteHit()
health = getProperty('health')
if getProperty('health') > 0.3 then
setProperty('health', health- 0.015);
end
end
Command Prompt/Terminal logs (if existing)
PlayState.hx (line 2641)
PlayState.hx (line 2570)
PlayState.hx (line 1086)
flixel/FlxGame.hx (line 637)
flixel/FlxGame.hx (line 724)
flixel/FlxGame.hx (line 677)
flixel/FlxGame.hx (line 545)
openfl/events/EventDispatcher.hx (line 402)
openfl/display/DisplayObject.hx (line 1399)

Uncaught Error: Null Object Reference
Please report this error to the GitHub page: https://github.com/ShadowMario/FNF-PsychEngine

> Crash Handler written by: sqirra-rng

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
I edited the song by reducing health!

Not a bug
Remove philly lights from your chart


Weird drop shadow

The tabs have this weird drop shadow (affects all themes) -> probably ok to simply add display: none; ?

EDIT: this does the trick for example
.monaco-icon-label-container::after { display: none !important; }

My vscode:
Version: 1.92.2 (system setup)
Commit: fee1edb8d6d72a0ddff41e5f71a671c23ed924b9
Date: 2024-08-14T17:29:30.058Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631

what is the name of your vs code theme ?

The default one with some color customizations
It looks like the drop shadow is related with the default tab color as these affect it:
"workbench.colorCustomizations": {
    "tab.inactiveBackground": "#ffffffb0",
    "tab.activeBackground": "#007acc48",
 }

I guess is something they added on top of the base backround color for pinned/read-only tabs, but weirdly it also shows for regular tabs.
IMO we either modify its color or hide it as I said

I wasn't able to reproduce the issue. I tested multiple themes with the settings you provided but had no success. Could there be another factor at play, such as a conflicting VS Code extension or a specific setting?

Okay I just did a binary search with the default settings and turns out it was this setting:
// Controls the size of editor tabs. This value is ignored when `workbench.editor.showTabs` is not set to `multiple`.
//  - fit: Always keep tabs large enough to show the full editor label.
//  - shrink: Allow tabs to get smaller when the available space is not enough to show all tabs at once.
//  - fixed: Make all tabs the same size, while allowing them to get smaller when the available space is not enough to show all tabs at once.
"workbench.editor.tabSizing": "shrink",

So whenever it is not set to "fit" the shadow is added (even when there is enough space to fit them)


Regex for phpunit --filter option

Also included some additional tests if they're helpful

Fantastic thanks so much for the PR


Add propagated error to the registration.txt output

Current registration.txt output ends with
RMSEs:
X = +/-0.488,
Y = +/-0.805,
Z = +/-0.861,
3D = +/-1.276

If we assume 3m spherical error of the photogrammetrically derived foundation DSMs, then the total error is computed as
Total Error = SQRT(3^2 + 3D_RMSE^2)

In the case above, that equates to 3.26 m.
We had discussed potentially breaking that into horizontal and vertical components, but that can be added at a later time. (We'd either need a provider to specify their estimated horizontal and vertical error, or we could break down the spherical down based on some Gaussian assumptions.)
Maybe this is best shown as a new block, summarizing the assumptions and equations used, e.g.,
PROPAGATED ERROR
----------------
Assumed global 3D error = +/-3
3D_RMSE = +/-1.276
Total Error is computed as SQRT( global_3D_error^2 + 3D_RMSE^2 )
Total Error = +/-3.260

Is the 3m spherical error of photogrammetrically derived DSMs a default value or is this coupled to the resolution?

The decision was made to just use a static value for now. In reality, it is obviously more complex than this. If a user knows more about a particular dataset, they can recalculate the propagated error.


[BUG] Azure event hub lib (3.3) - Messagging factory thread keeps running after application stop

Describe the bug
at com.microsoft.azure.eventhubs.impl.MessagingFactory$RunReactor.run (MessagingFactory.java:784)
This thread keeps running in JVM after we stop the connection with event hub.
Exception or Stack Trace
at sun.nio.ch.EPollArrayWrapper.epollWait (EPollArrayWrapper.java:-2)
at sun.nio.ch.EPollArrayWrapper.poll (EPollArrayWrapper.java:269)
at sun.nio.ch.EPollSelectorImpl.doSelect (EPollSelectorImpl.java:93)
at sun.nio.ch.SelectorImpl.lockAndDoSelect (SelectorImpl.java:86)
at sun.nio.ch.SelectorImpl.select (SelectorImpl.java:97)
at org.apache.qpid.proton.reactor.impl.SelectorImpl.select (SelectorImpl.java:126)
at org.apache.qpid.proton.reactor.impl.IOHandler.handleQuiesced (IOHandler.java:57)
at org.apache.qpid.proton.reactor.impl.IOHandler.onUnhandled (IOHandler.java:390)
at org.apache.qpid.proton.engine.BaseHandler.onReactorQuiesced (BaseHandler.java:87)
at org.apache.qpid.proton.engine.BaseHandler.handle (BaseHandler.java:206)
at org.apache.qpid.proton.engine.impl.EventImpl.dispatch (EventImpl.java:108)
at org.apache.qpid.proton.reactor.impl.ReactorImpl.dispatch (ReactorImpl.java:324)
at org.apache.qpid.proton.reactor.impl.ReactorImpl.process (ReactorImpl.java:292)
at com.microsoft.azure.eventhubs.impl.MessagingFactory$RunReactor.run (MessagingFactory.java:784)
at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
at java.util.concurrent.FutureTask.run (FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201 (ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run (ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
at java.lang.Thread.run (Thread.java:748)
To Reproduce
Creating connections to azure and keep running the application for long duration
Code Snippet
to make the connection -
final ScheduledExecutorService scheduledExecutorService = Executors.newSingleThreadScheduledExecutor(
new ThreadFactoryBuilder().setNameFormat(threadNamePattern).build()
);
this.scheduledExecutorService= scheduledExecutorService;
return EventHubClient.createFromConnectionStringSync(connStr.toString(), scheduledExecutorService);

}
While closing the connection-
-> eventHubClient.close();
Expected behavior
All thread should get closed
Screenshots

Setup (please complete the following information):

OS: [e.g. iOS]
IDE: [e.g. IntelliJ]
Library/Libraries: azure-eventhubs-3.3.0.jar
Java version:  8
App Server/Environment: [e.g. Tomcat, WildFly, Azure Function, Apache Spark, Databricks, IDE plugin or anything special]
Frameworks: Java

If you suspect a dependency version mismatch (e.g. you see NoClassDefFoundError, NoSuchMethodError or similar), please check out Troubleshoot dependency version conflict article first. If it doesn't provide solution for the problem, please provide:

verbose dependency tree (mvn dependency:tree -Dverbose)
exception message, full stack trace, and any available logs

Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added
[x] Setup information Added

@conniey could you please help route this Track 1 EH github issue?


[NLU-3681] Fix for infinite loop issue in BaseDateParser

This is a fix for an issue found in the BaseDateParser.parse_implicit_date method.
Within the method there is a section responsible for parsing dates in the format of <weekday> <day> such as “Saturday 30”. It looks for past and future dates that correspond to the extracted weekday and day values, iterating through months starting with the current one.
The function relies on the datedelta library for date calculations. There's a bug (unexpected behaviour) in the datedelta library - in some cases it does not subtract the entire month. For example, when subtracting one month from the 30th of March, the library returns the 1st of March instead of the expected 28th of February. This causes an infinite loop as the month remains unchanged within the loop.
The pull request fixes the issue by replacing the datedelta library with the python-dateutil library which works as expected.

Pipeline run: https://jenkins.ininica.com/job/NLU/job/Recognizers-Text/245/


Example spark-submit using spark-s3-shuffle whilst running with Dynamic Allocation

It would be good to include an example in the readme. Whilst it maybe obvious what is required for some developers, others maybe unsure.
Using the spark-s3-shuffle whilst running an application with dynamic allocation may trip some people up. Typically when dynamic allocation is enabled you are also required to enable the shuffle service. This may not be available when running spark on kubernetes and executors will fail to register with the external shuffle service. The workaround for this is to enable shuffle tracking and configure the shuffle tracking timeout to ensure executors can be gracefully removed.
For example some additional configuration required:
--conf spark.executor.extraClassPath=some.jar      # this is required so executors are aware of the S3ShuffleManager etc
--conf spark.dynamicAllocation.enabled=true
--conf spark.dynamicAllocation.shuffleTracking.enabled=true

Good point! Thank you! These parameters are very well documented on the Spark Configuration page.
You might also need to set ```
--conf spark.dynamicAllocation.shuffleTracking.timeout=0
since the stale executors might be kept around otherwise.

I need to spend some time on this.


Create area for user-submitted examples

Adding an examples.md linked from readme so kbct users can share their keyboard remap examples

Hi @seltzered and thanks for a good idea. It will definitely be helpful for some people.


Update htmllint dependency

There are 95 commits on htmllint since 0.6.0 : https://github.com/htmllint/htmllint/compare/v0.6.0...master
Happy New Year !
Sebastien

This is covered by #25.


Change link to privacy policy on appstore

Apple
Pls change link to developers privacy policy https://library.threefold.me/info/legal/#/legal__privacypolicy

I have updated the privacy policy link but it will take some time to reflect

Not reflecting yet

Not reflecting yet

yes, still under review from the app store side. I'll keep the issue updated once they finish

available now on the app store


Doxygen Tweaks

This PR is for making tweaks to the doxygen configuraiton.
So far:

[x] Strips absolute paths to be FLAMEGPU_ROOT relative i.e. in diagrams /home/user/path/to/flamegpu/include/flamegpu/model/AgentFunctionDescription.h becomes include/flamegpu/model/AgentFunctionDescription.h

I'd also suggest:

[ ] restricting the number of layers to which diagrams are generated to 1 via set(DOXYGEN_MAX_DOT_GRAPH_DEPTH   1).

This greatly simplifies the include dependency diagrams so they are actually legible, but does lose some information on dependency chains.
Links are generated so that you can easily follow dependency chains through (red boxes).
I.e. for AgentFunctionDescription.h:
With DOXYGEN_MAX_DOT_GRAPH_DEPTH = 0

And with DOXYGEN_MAX_DOT_GRAPH_DEPTH = 1

And with DOXYGEN_MAX_DOT_GRAPH_DEPTH = 2

Less sure about the depth limit, a depth limit of 1 seems little better than just checking the includes on the files directly.

That's partially why i included the 2 option as an example. Any choice is a compromise between the diagram being readable and  how much informationit conveys. Another option would be to just disable the dependency graphs, as full graphs are illegible and small graphs are (somewhat) pointless.

Not too sure what this comment is supposed to mean, could be clearer
# Select diagram output format {png, YES/NO}, {svg, YES}, {svg, NO}

a quick way of suggesting pairs of parameters for the related options. I'll be more verbose.

Set to MaxDepth 1 and then OK to merge.


the ES2019 provided Object.fromEntries

Convert headers into an object, with Object.fromEntries (ES2019).

any reviews?

Thanks for the PR @t829702!


Authentication error once when the API is set up. (Securing your API section)

Hi, I have added the attributes to secure the API but once I have done that the application throws a 401. I have been trying to fix this but I'm not sure where I went wrong. It would be great if anyone could go through my code and see what have I missed or done wrong.
https://github.com/Harrish-Selvarajah/OAuth2AndOIDC
Thanks in advance for your help!

Found the solution.
remove  //ValidTypes= new[] { "alt+jwt" } from Program.cs in tokenvalidation params


Decide on whether to publish lib to npm or Github package registry

https://blog.bitsrc.io/github-package-registry-is-it-worth-trying-out-62163aa3d518
https://github.com/features/packages

Sticking with npm for now, can revisit as needed.


What model did you used in the paper?

What model did you use to get histograms of Fig 5 in the paper? I used magface_epoch_00025.pth on LWF and got this histogram, where the magnitude values are lesser than what Fig 5 reports.

Hi,
Fig 5 is based on a very early model whose parameters are set empirically.  The range of the magnitudes can differ (e.g., the magnitudes increases if we use large lambda_g) when parameters change.
The released model is well tuned for recognition performances. The magnitudes are smaller but the overall trends on datasets should be the same.
Best,
Qiang

it means, I'm not doing it wrong at inference. Thanks @IrvingMeng


⚠ Spryr has degraded performance

In 06003da, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3377 ms

Resolved: Spryr performance has improved in 976cf60 after 7 minutes.


Remove duplicate code from wfe.js, closes #1673

Pull Request Test Coverage Report for Build 4090

0 of 0   changed or added relevant lines in 0 files are covered.
86 unchanged lines in 6 files lost coverage.
Overall coverage increased (+0.01%) to 69.249%

Files with Coverage Reduction
New Missed Lines
%

core/src/main/java/com/netflix/conductor/core/config/Configuration.java
7
78.13%

cassandra-persistence/src/main/java/com/netflix/conductor/dao/cassandra/CassandraEventHandlerDAO.java
8
68.42%

cassandra-persistence/src/main/java/com/netflix/conductor/dao/cassandra/CassandraMetadataDAO.java
8
55.44%

server/src/main/java/com/netflix/conductor/jetty/server/JettyServer.java
19
35.48%

es5-persistence/src/main/java/com/netflix/conductor/dao/es5/index/ElasticSearchRestDAOV5.java
21
76.06%

es5-persistence/src/main/java/com/netflix/conductor/dao/es5/index/ElasticSearchDAOV5.java
23
81.2%

Totals

Change from base Build 4030:
0.01%

Covered Lines:
12318

Relevant Lines:
17788

💛  - Coveralls


Flutter Desktop app's debug build without Dart VM running, cannot be invoked by Google Chrome extension's Native Messaging

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Let app_exec_file_path = /Users/<user>/Desktop/desktop_app/build/macos/Build/Products/Debug/desktop_app.app/Contents/MacOS/desktop_app
If I double click my Flutter Desktop app's Unix executable file in app_exec_file_path, this is the flow:

It opens a terminal and starts a Dart VM
The desktop app opens

Approach 1:
The problem is, if I use app_exec_file_path as path in the Native Messaging host file like so:
{
  "name": "com.test.desktop_app",
  "description": "Open Desktop app",
  "path": "/Users/<user>/Desktop/desktop_app/build/macos/Build/Products/Debug/test_desktop.app/Contents/MacOS/desktop_app",
  "type": "stdio",
  "allowed_origins": ["chrome-extension://<extension_id>/"]
}

what happens is the following flow:

I click open my extension and press the button
It will open the Flutter Desktop app briefly but then closes right away

One thing I think is the reason, the extension only opens the desktop app's executable file directly without a Dart VM running.
See the 1st log below for the errors...
Approach 2:
So what I did was, I created a combination of workarounds and use either shell script or executable file but basically its content is:
#!/bin/bash
osascript -e 'tell app "Terminal" to do script "/Users/<user>/Desktop/desktop_app/build/macos/Build/Products/Debug/test_desktop.app/Contents/MacOS/desktop_app"'

This file is called open_app and is a Unix executable file. Essentially, the 2nd line is a 1 liner command line that does the following in order:

Opens a terminal first (this will serve as the Dart VM)
Open the Flutter Desktop app's executable file (make it stay running together with the Dart VM)

Now, going back to the manifest.json, I replaced the path of open_app so Native Messaging would now invoke the script I just created to open Dart VM then the Desktop app (hoping it won't close right after).
See the 2nd log below for the errors...
Expected results
I have a Chrome extension that uses runtime.connectNative and runtime.sendMessage to communicate to my Flutter Desktop app that should listen to any message from the extension.
The expected flow:

I click open my extension and press the button
It will open the Flutter Desktop app and see the received message in my logs

Actual results
Flutter Desktop app crashes or closes right away if its debug build - Unix executable file is invoked using Chrome Native Messaging.
To summarize:
Approach 1:
When I used the debug build's Unix executable file of my Flutter Desktop app as path value inside the Native Messaging host file, it opens the Desktop app briefly then closes right away because there's no Dart VM opened.
Approach 2:
When I used the shell script or executable file I created as path value inside the Native Messaging host file, it doesn't open the Desktop app at all.
From the 2nd log error message, it seems that Native Messaging can only open binary and not just any executable file.
Makes me wonder what is the standard way of communication between Chrome extension and Flutter Desktop apps, how do they send message to the app or even just invoke its method?
Any opinion would be greatly helpful.
Code sample
Native Messaging host file
  {
    "name": "com.test.desktop_app",
    "description": "Open Test Desktop",
    "path": "/Users/<user>/Desktop/desktop_app/open_app",
    "type": "stdio",
    "allowed_origins": ["chrome-extension://<extension_id>/"]
  }

Chrome extension's popup.js
  let btn = document.getElementById("my_app");

  btn.addEventListener("click", () => {
    port = chrome.runtime.connectNative("com.test.desktop_app");
    console.log("Test Desktop clicked");
  });

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
1st log:
Also, since I enabled logging using the command:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-logging --v=1
I tailed the logs inside Library/Application Support/Google/Chrome/chrome_debug.log.
Here are the errors I got:
"Test Desktop clicked", source: chrome-extension://<extension_id>/popup.js (33)
Native Messaging host tried sending a message that is<PHONE_NUMBER> bytes long.
"Unchecked runtime.lastError: Error when communicating with the native messaging host.", source: chrome-extension://<extension_id>/popup.html (0)
"Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.", source:  (0)

Which means the connection is interrupted as the Desktop app has just closed.
2nd log:
Here's the new error if I click the button in my extension:
    "Test Desktop clicked", source: chrome-extension://<extension_id>/popup.js (33)
    Found manifest, but not the binary for native messaging host com.<user>.desktop_app. Host path specified in the manifest: /Users/<user>/Desktop/desktop_app/open_app
    "Unchecked runtime.lastError: Specified native messaging host not found.", source: chrome-extension://<extension_id>/popup.html (0)

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.10.6, on macOS 13.4.1 22F770820d darwin-arm64, locale en-SG)
    • Flutter version 3.10.6 on channel stable at /Users/<user>/tools/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (10 days ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /Users/<user>/Library/Android/sdk
    • Platform android-33, build-tools 33.0.2
    • ANDROID_HOME = /Users/<user>/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.80.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.68.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 13.4.1 22F770820d darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 115.0.5790.102

[✓] Network resources
    • All expected network resources are available.

• No issues found!

the extension only opens the desktop app's executable file directly without a Dart VM running.
[...]

Opens a terminal first (this will serve as the Dart VM)

It is not clear what this means; Flutter applications do not run in an external VM, nor is Terminal a Dart VM.
According to Chrome documentation a messaging host cannot log anything to stdout that doesn't conform to the protocol, which means that debug Flutter application cannot possibly be a valid target, due to the logging that it does.

Makes me wonder what is the standard way of communication between Chrome extension and Flutter Desktop apps

I would not expect a GUI application, Fluter or otherwise, to be the standard target for a Chrome extension. I would recommend a forum for Chrome extension development in general for advice on how to make a non-GUI binary that does IPC communication with a GUI application, as that wouldn't involved anything Flutter-specific.
Closing as this is not a Flutter bug.

It is not clear what this means; Flutter applications do not run in an external VM, nor is Terminal a Dart VM.

The 1st screenshot is from DEBUG CONSOLE tab from VS Code, while the 2nd screenshot is the terminal that opened when double clicking the debug executable file. This is what I meant as the terminal that serves as Dart VM.

I would not expect a GUI application, Fluter or otherwise, to be the standard target for a Chrome extension.

How about use cases where Flutter is used to create a Chrome extension and a Desktop app and these 2 apps communicate to each other. For example, to be able to use extension further, it should open the Desktop app when not opened and invoke its authentication functionality? I just think it might come up sooner than we thought as Flutter targets different platforms.
Thanks for the suggestion also, will open a forum at Chromium issue filing: https://bugs.chromium.org/p/chromium/issues/wizard

This is what I meant as the terminal that serves as Dart VM.

The terminal is showing you the stdout from the application, including the logging from the application about where the debug VM service within the application is listening for connections. It is not a VM.

How about use cases where Flutter is used to create a Chrome extension and a Desktop app and these 2 apps communicate to each other. For example, to be able to use extension further, it should open the Desktop app when not opened and invoke its authentication functionality?

I would expect that to be mediated by a non-UI binary that is specifically designed to conform to the requirements of the Chrome native messaging protocol, and which in turn communicates with the (in this case Flutter) GUI application through some mechanism other than stdin/stdout, as I described above.

Thanks stuartmorgan for the suggestion also, will open a forum at Chromium issue filing: https://bugs.chromium.org/p/chromium/issues/wizard

I don't see any evidence of a Chromium bug here; my suggestion was to find a forum for asking questions about Chrome extension development to get advise about communicating with an application from an extension.


Refactored your code

Refactored your code (40%)

so cute : )

so cute : )

0.0

qwp That's a really good project


P4042

please use those g flags present in main branch, it helps to store more roms in server storage


cStringIO cannot handle some Unicode strings.

@cjw296
First, thanks for the awesome tool.
I encountered errors such as the following.
# -*- coding: utf-8 -*-
from testfixtures import OutputCapture

with OutputCapture() as output:
    print(u"こんにちわ")

error
UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-4: ordinal not in range(128)

The cause of this error is because cStringIO cannot handle some Unicode strings well.
see also https://docs.python.org/2.7/library/stringio.html?highlight=cstringio#module-cStringIO
I have changed cStringIO to StringIO. Please feel free to merge it.

Sounds good, but please can you change the test so the encoding isn't required. You only need one character in each stream so it shouldn't be too bad...

@cjw296  Thanks for your checking it.
I've removed the encoding at the top.
Please checkt it again.
thx


Errors for Swift 3

I am attaching the image which shows the list of errors I'm getting.

Use latest version that supports swift 4

Which version supports Swift 3 ?


Water isn't rendered

Here is another problem where I'm not sure if it has always been this way or only been introduced by recent changes. Water isn't loaded or rendered anywhere in the world. Neither the surrounding ocean nor lakes or small bodies of water.
The ocean between Las Venturas and Los Santos:

The east coast of Las Venturas:

In front of a Las Venturas casino:

Compare that to the same spot in the original game: :smile:

I've tried my Mac Steam version and a Windows version of the game files, so it shouldn't be a problem with them... Any ideas? Could it be another path issue? As far as I can tell from the code, it seems as if the water should be loaded?

There is integrated support for water. You just have to assign your water game object to World->Water->Water Prefab

Ah, yes, I just did get that far myself after writing the initial issue. I've now tried the included water prefab from the Unity Standard Assets. It's not working with all of them, only WaterBasicDaytime looks acceptable. Any reason why no water prefab is included with the project? As far as I can tell, including parts of the Unity Standard Assets shouldn't be a problem. Otherwise, we could create our own that matches the original look more closely.

There's a big performance hit when using the advanced water prefabs, however. I'm not sure why or how this could be fixed.

Yeah, I just tried it.
First I put water pro daytime, and couldn't even move a mouse :D. Then I switched to basic, and it worked fine.

Advanced waters try to reflect everything in the scene, that's why they are so demanding. A simple fix would be to enable/disable reflecting based on distance from camera.

Any reason why no water prefab is included with the project?

Well to be honest, it never came up to me to add water to the scene. Thanks for bringing it up :D.
I'll try to add it soon.

Speaking of water. You guys are using water location from water.dat file
right?
On Mon, Mar 27, 2017 at 1:32 AM, in0finite<EMAIL_ADDRESS>wrote:

There is integrated support for water. You just have to assign your water
game object to World->Water->Water Prefab
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/in0finite/SanAndreasUnity/issues/3#issuecomment-289308623,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUQvyPjF6p6_boj3Cq3OlM0I7WiyNsPzks5rpr1IgaJpZM4MpjG5
.

I'm not sure. You can check the source to find out.


Unable to create DaemonSet that connect to docker endpoint

Version

Karpenter: v0.0.0

Kubernetes: v1.0.0
Expected Behavior

I'm unable to deploy papertrail on node created by the Karpenter autoscaler. However, if i deploy the papertrail demonset on the managed nodegroup it works.
Error logs
2022/04/25 23:51:36 # jobs    : pump routes http[routes,health,logs]:80
2022/04/25 23:51:36 # routes  :
2022/04/25 23:51:36 pump ended: cannot connect to Docker endpoint

Karpenter uses containerd as the container runtime by default except for a few special cases.  Does papertrail work with containerd?

Thank you for your help. I was able to resolve the paper trail issue by switching to rkubelog (https://github.com/solarwinds/rkubelog) from logspout.  rkubelog supports containerd.

Glad to hear it!


How do I get the timetable for today with the specific rooms?

I can't find any solution for that. Is there one? If so how would i achieve this?

You can use this method: https://webuntis.noim.me/WebUntis.html#getTimetableFor
The WebUntisElementType for rooms is 4. You can get the rooms with https://webuntis.noim.me/WebUntis.html#getRooms


Upgrade opentelemetry

https://github.com/tokio-rs/tracing-opentelemetry/pull/155

https://github.com/ymgyt/syndicationd/commit/b2def9c07c1dc2f50987831cdbac1bdc4be44791


securing oauth2 credentials

I am using rclone between AWS and GCP. I would like to have multiple users run rclone on a server.
I don't like the idea of sharing a service account credential json file on my server, as I wouldn't want other users to extract it and reuse it elsewhere.
I also don't like the idea of sharing client_id, client_secret and refresh_token with all my users. They could reuse those credentials elsewhere as well.
So I am using simple user account auth, without providing client_id and client_secret in the rclone.conf file. Rclone works fine until my token expires, at which point it fails because it cannot renew the token on it's own.
My thoughts are to provide the auth_token through an http auth proxy, and update rclone.conf myself on regular basis.
Does anyone have thoughts on this? Am I not right in trying to hide the client_id and client_secret from my users? Is there a better approach?

Are you letting users use rclone directly or are you scripting it for a specific task.  If the latter then you should probably run the rclone job as a separate unix user (or even root) so the user won't be able to read any of the config.

Unfortunately my users are running rclone directly.
So I have setup an "http service" on another box that responds with an auth_token, expiry and refresh_token.
I have scripted to update the rclone.conf file on regular basis. This way I am not sharing client_id and client_secret with my users.
If rclone was running in GCE, it might be possible to make it use the token found in the instance metadata server (same with an instance IAM role - or even assume role - In which case support for an external token refresh command might be handy).
My use case is very specific, and probably won't interest too many people.

So running rclone as root (say) doing something simple like rclone lsd remote: to refresh the token, then editing the rclone.conf removing the secret stuff except for the token and copying that .rclone.conf into the users home directories.  That should work just fine I would have thought.  If the users are doing really long transfers which span the hour of the token lifetime then rclone won't be able to refresh it though.

I hope that was of some help!


postgis: 2.4.4 -> 2.4.5

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/postgis/versions.
meta.description for postgis is: '"Geographic Objects for PostgreSQL"'.

Checks done (click to expand)

built on NixOS
Warning: no invocation of /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/bin/pgsql2shp-2.4.5 had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/bin/raster2pgsql-2.4.5 had a zero exit code or showed the expected version
/nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/bin/shp2pgsql-2.4.5 passed the binary check.
Warning: no invocation of /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/bin/raster2pgsql had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/bin/pgsql2shp had a zero exit code or showed the expected version
/nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/bin/shp2pgsql passed the binary check.
2 of 6 passed binary check by having a zero exit code.
0 of 6 passed binary check by having the new version present in output.
found 2.4.5 with grep in /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5
directory tree listing: https://gist.github.com/f8b38a2f12597890eaf92802bb0b9cc0
du listing: https://gist.github.com/1d16de0361ea81768d3449a31716b15d

Instructions to test this update (click to expand)

One-time optional setup to skip building using Cachix:

Install cachix from https://cachix.org/
Use r-ryantm's cache:cachix use r-ryantm

Test this update by entering a nix shell, seeing what is inside the
result, and if applicable, running some binaries:
nix-shell --pure -I nixpkgs=https://github.com/r-ryantm/nixpkgs/archive/17467c549be5d7f988a62447dea2be6502403aef.tar.gz -p postgis
ls -la /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5

cc @marcweber for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: postgis
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: postgis
Partial log (click to expand)
shrinking /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/bin/shp2pgsql
shrinking /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/lib/liblwgeom-2.4.so.0.0.0
shrinking /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/lib/postgis_topology-2.4.so
shrinking /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/lib/rtpostgis-2.4.so
shrinking /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/lib/postgis-2.4.so
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/lib  /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5/bin
patching script interpreter paths in /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5
checking for references to /build in /nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5...
/nix/store/zll9685m545xlcn7vhxmfkhdsk24jmfp-postgis-2.4.5

Timed out, unknown build status on aarch64-linux (full log)
Attempted: postgis
Partial log (click to expand)
                                         ^~~~~
                                         int
/build/hdf-4.2.14/hdf/src/dfkswap.c:144:9: error: unknown type name 'VOIDP'
 DFKsb4b(VOIDP s, VOIDP d, uint32 num_elm, uint32 source_stride,
         ^~~~~
/build/hdf-4.2.14/hdf/src/dfunjpeg.c:58:66: error: unknown type name 'int32'; did you mean 'int'?
building of '/nix/store/k2n0n7sfk1cz5qjj80adqx82sr67frm3-hdf-4.2.14.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/6crj09pvjs4qlmaki552jwq2xb86z5jh-gdal-2.3.1.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/awac21qzys9prszzw9m4sy8a4qd5hw3a-postgis-2.4.5.drv': 1 dependencies couldn't be built
error: build of '/nix/store/awac21qzys9prszzw9m4sy8a4qd5hw3a-postgis-2.4.5.drv' failed


Different requirements in podspec and readme

The readme indicates iOS version 8.0+ is required, while the podspec file indicates 9.0.

thanks for reporting the issue.


OpenSSL 3 is not yet supported. Please use OpenSSL 1.x

When the environment is started with 'bash webui.sh', OpenSSL 3.x will be set up automatically in python 3.10.x
Could fix this please, thx very much

please use another branch bugfix/gradio_api_incompatibility to see whether the issue above is gone.
cd <your_stable_diffusion_directory>/extensions/miaoshouai-assistant/
git checkout -b verfication origin/bugfix/gradio_api_incompatibility
git pull --rebase -p

change the 'disable_log_console_output" from true to false to switch on log output to console, so we can get detailed info.
vim <your_stable_diffusion_directory>/extensions/miaoshouai-assistant/configs/settings.json

{
   ....
   "disable_log_console_output": false,
   ....
}

and after then, please restart your webui again
If the issue still be present, please give us the detailed log output to help us to address this issue.


Move Resource in bevy_ecs crate

Move Resource, Res, ResMut, NonSendMut to bevy_ecs::resource.
Motivation for this PR is:

Resource and ResMut live in separate mods (system, change_detection), while they are related, making hard to find one from another when looking at public API
moreover ResMut is exported twice is public API (in both system and change_detection)
internally it's better when related code is closer
system/mod.rs is 1700 lines of code, too long
event has in a separate mod, why not resource?
resources are not necessary tied to systems

This is my subjective opinion how code should be organized, I spent like 15 minutes on this PR, no hard feeling if this is not considered useful.

If NonSendMut is moved, NonSend might as well be moved with it.

Didn't know Resource doesn't have a dedicated file.
However, the PR name makes it look like it is currently outside bevy_ecs. It should mention instead that we're moving it to a dedicated module.

Clarified the name just a bit further :)


Added a format method for OpenCL expressions in elementwise operations

@karlnapf looks way much cleaner now, a la @lisitsyn.

Coverage increased (+0.0%) to 74.76% when pulling 08bbbba62f6c7c0db0073c7222a54715e27a2400 on lambday:develop into 308e63ca874ca9af1449d2bf76712fa4918a622c on shogun-toolbox:develop.

Coverage increased (+0.01%) to 74.76% when pulling eb5515f589755f5e2d32a5a24c99be5f4aa2147d on lambday:develop into 308e63ca874ca9af1449d2bf76712fa4918a622c on shogun-toolbox:develop.

Lookz cool

@lisitsyn merging it then.
@karlnapf Please have a look when you're free :)

Good stuff, thanks!


Upgrade Matrix authorization plugin in jenkins

We had some concerns over some of the things in the release notes which prevented us from doing the upgrade of this plugin. It was last updated some time ago so we need to schedule some time to look at doing an upgrade and resolving any problems to keep it up to date.

We are currently at 3.1.5 which is the latest one that is compatible with our jenkins server. This was installed during the attempted upgrade last week.
It was previously running 2.6.6 (Based on the .bak file on the jenkins server).


PEAR-1866 -Browse Annotations - Filters persist when user leaves page and comes back

Description
Checklist

[x] Added proper unit tests
[x] Left proper TODO messages for any remaining tasks
[x] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)

looks good.
qn: is it possible not to clear the filters on refresh, but to clear them on leaving the page and returning? Or are they both the same "mechanism"? for example, the projects app doesn't clear filters on refresh, only on closing the app and returning, but I get that maybe it's different cos it's an app and this is a page.

Hi @wteouchicago, I could set the annotation app to persist the filters through refresh. Though the way I'm clearing the filters at the moment, it would have the same issue noted in this ticket: https://gdc-ctds.atlassian.net/browse/PEAR-1763. There may be a different approach to clearing filters that will solve that issue, I haven't looked into it yet.


clarify kube-controller-manager/kube-scheduler skew support and upgrade order

Follow up from https://github.com/kubernetes/website/pull/11060, tracked in https://github.com/kubernetes/website/issues/12329
Supported skew and upgrade order for kube-controller-manager/kube-scheduler is not clear in user-facing documentation:

[ ] is a specific upgrade order between kube-controller-manager and kube-scheduler required? @kubernetes/sig-api-machinery-pr-reviews, @kubernetes/sig-scheduling-pr-reviews

Page to Update:
https://kubernetes.io/docs/setup/version-skew-policy/

/wg lts

The scheduler is a controller. There should not be an ordering requirement; it's easy to imagine ways of getting an ordering requirement, but I consider them all to be bugs (e.g., scheduler depends on semantics of a particular controller at the same version).

/language en

/priority backlog
Is that OK?

/remove-lifecycle rotten

/reopen
/remove-lifecycle rotten
/lifecycle frozen

/triage accepted

Reached out in #sig-scheduling chat to potentially get some movement on this and determine what update is needed (either clarify that upgrade order of kube-controller-manager and kube-scheduler doesn't matter, or clarify what the order should be)
/assign

Answer: there must not be a specific ordering needed between those two components. In practice, they get locks independently and the most common way of upgrading them (a VM at a time) means all four combinations of versions are possible, and a single upgrade could even see splits both ways.

Thanks @lavalamp!


train two classes how to change code?

hello , I want to train two class ,but loss = 0 ,i set  "batch_k": 4,  "batch_p": 2,
how to change the code to train normally ?  thanks!

@pvoigtlaender @francisengelmann @lucasb-eyer @Pandoro


[BUG] A check within an registered IP range is not showing as green

Describe the bug
From a support discussion:

Regarding the Green Web Checker, I checked your website myself, and it is indeed turning up grey. This is strange, because the underlying IP address (<IP_ADDRESS>) is included in the IP ranges that were approved as green.

This start happening in the last day or so. I'm not sure why.
To Reproduce
Check the url using the 'debug' checker
https://admin.thegreenwebfoundation.org/admin/try_out/
Expected behavior
A clear and concise description of what you expected to happen.
It should resolve to a green result.
Actual behavior
A clear and concise description of what actually happened.
We see a grey result.
Additional context
Add any other context about the problem here.
We have developer facing documentation explaining how our green check system works.
https://greenweb.readthedocs.io/en/latest/how-we-check-for-green.html

 Serversaurus IPs not working?

OK, this was actually a typo in the end, where the IP range had been entered incorrectly through the admin, but it it did highlight a need for validation.
@tortila and I have spoken about this, and we it makes sense to add the validation at the GreencheckIP model linked below:
https://github.com/thegreenwebfoundation/admin-portal/blob/master/apps/greencheck/models/checks.py#L153
Adding model-level validation ought to cascade up through the form submission lifecycle, and show up in the admin, but also give us a way to use the same model level checking for any other import we do, like via the API, or through a CSV import.

The PR I linked to this issue solves the IP range validation for ModelForms, e.g. used in the Django admin. There are possibly other places where this model is saved without checking if it's valid, e.g. CSV import: https://github.com/thegreenwebfoundation/admin-portal/blob/bff33eb980b74073d065e47861aff05962996d25/apps/greencheck/bulk_importers.py#L54-L57
I also found out that for the REST API, the serializer defined for GreencheckIp model already has similar validation logic implemented: https://github.com/thegreenwebfoundation/admin-portal/blob/9d261aaa36b86aa6d786aa92203f429576190d19/apps/greencheck/serializers.py#L73-L84.


Fixed ESP-12e extra I/O pins (wrong order).

The ESP-12e library package has mixed I/O pins (17-22), that do not match to a real ESP-12e device.
Providing a pull that fixes these pins.

Merged in Tomazas' updates to fix the pin order along the bottom of the module.  Thanks Tomazas!

Tomazas,
Please forgive my very, very belated reply to your pull request.
I just wanted to say "Thank you!" for taking the time to fix the pins
(and to add the "restrict" on the antenna end).  Despite my tardiness, I do
appreciate it and your changes are now committed to the master.
Thanks again,
                                            -John-

On 30 November 2015 at 07:37, tomazas<EMAIL_ADDRESS>wrote:

The ESP-12e library package has mixed I/O pins (17-22), that do not match
to a real ESP-12e device.
Providing a pull that fixes these pins.
You can view, comment on, or merge this pull request online at:
https://github.com/PuceBaboon/Share_the_Warmth/pull/3
Commit Summary

Fixed ESP-12e extra I/O pins (wrong order).

File Changes

M eagle/ESP8266-ESP12E.lbr
https://github.com/PuceBaboon/Share_the_Warmth/pull/3/files#diff-0
(94)

Patch Links:

https://github.com/PuceBaboon/Share_the_Warmth/pull/3.patch
https://github.com/PuceBaboon/Share_the_Warmth/pull/3.diff

—
Reply to this email directly or view it on GitHub
https://github.com/PuceBaboon/Share_the_Warmth/pull/3.


WIP - Blob file

It would be nice to be able to move files around without understanding their file type.  This is particularly useful for the type modifiers like ssh, s3, and hdfs.
This is preliminary.  I may want to be more clever.

I would definitely use this for the URL routing as well

If someone wants to own this please feel free to reopen.


Update scale-set-agents.md

three typo's in the custom script extension for Linux section
missed backslash after --publisher
missed dot before /myScript.sh
fileUris is camel-case, (F was caps)

@tvdvoorde : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Dependency updates

@hudakdidit I had to make a few additions to package.json to get npm install working.

@hudakdidit Some of the issues may have been because of the just-released React 0.14.6, which has some version bumps in its dependencies, especially history.


Encrypt  the HTTPBody when make a request and decrypt the HTTPBody when receive a response

Hello, my server is not over SSL so I want to know how  to

Encrypt  the HTTPBody when make a request.
Decrypt the HTTPBody when receive a response.

Thanks.

You'll need to do that at the AFNetworking level.
GitHub Issues is for reporting bugs in RestKit and discussing changes to RestKit itself. Please check the documentation, wiki, and existing issues before opening a new issue.
Additionally, please do not post general usage questions to Issues, but instead take them to Stack Overflow.


Wrong style on new layer with data import

Steps to Reproduce

Create a map with any dataset.
Click "Add" (layer).
Select "Connect dataset" and drag a new file with polygons such as guess_country_reduced.csv.zip.

It gets imported with blue:

Nevertheles...
Current Result
Fill is yellow-ish.

Expected result
Blue-ish.
cc @xavijam

I feel it is a frontend problem, taking a look.

Hey guys, is it possible that table endpoint has changed something? @CartoDB/builder-backend

We're constantly changing a lot of core stuff. Nothing specifically for this comes to my mind, but the change that broke #11800 might've broken this as well. If you can't find the problem, we'll take a look later.

No, problem found, I'll describe in the PR. And, as a 🎁 , I'll request your CR :joy:.

Deployed


Build against PHP 7.2 with lowest dependencies

To make this possible I had to upgrade php-cs-fixer to v2.
By building against lowest dependencies we can prove that code indeed works with them (otherwise we're only testing against latest versions). A good thing to do here is to take the latest PHP version with lowest dependencies. This way the most critical path is covered without having to run all the combinations.
I also took the courtesy to disable XDebug so composer is more happy (faster). Coverage can be easily generated with php-dbg. I also added a filter to phpunit.xml.dist so the coverage is actually generated (it hasn't been before).

Thanks @jakzal :)


Headless via Python: Deactivating large amount of analysis options always has some left activated

Describe the bug
I am running Ghidra in headless mode and using a Python prescript to deactivate all but 4 analysis options.  However, the following 5 are always turned on even when I set (and confirm) they are set to "false".  Even if I programmatically set every option to "false" these are still run:

Call-Fixup Installer
Function Start Search
Shared Return Calls
Stack
X86 Function Callee Purge

If I open the project in the GUI, I can see everything is not checked in the analysis options, or off, as expected.  If I try to only turn off one or a few of these options above (everything else default) then they are turned off as expected.  I tried both the setAnalysisOptions() and setAnalysisOption() API.
This is the simple Python code I used in my prescript to attempt to turn them all off as a test to verify nothing should be run:
analysis_opts = getCurrentAnalysisOptionsAndValues(currentProgram)

for key,value in analysis_opts.items():
    if "true" in analysis_opts[key]:
        analysis_opts.update({key: "false"})

setAnalysisOptions(currentProgram, analysis_opts)

If run getCurrentAnalysisOptionsAndValues() I can verify they are all set to "false" after I run this code.  However, the analysis still runs those 5 above.
Environment:

OS: Windows 10
Java Version: JDK - 17.0.2, JRE - 1.8.0_331
Ghidra Version: 10.1.4
Ghidra Origin: official release

I'm having trouble reproducing this.  I am running headless in debug mode with a breakpoint at the start of each of those analyzers you've listed.  If i run your prescript no breakpoints hit, and if i comment out the part of your script that sets everything to false, the breakpoints hit.  Maybe I need your binary?

I'm having trouble reproducing this. I am running headless in debug mode with a breakpoint at the start of each of those analyzers you've listed. If i run your prescript no breakpoints hit, and if i comment out the part of your script that sets everything to false, the breakpoints hit. Maybe I need your binary?

I did some more investigation and I think it is relating to other code I am doing in the prescript.  I am essentially doing the exact same thing as the Ghidra built-in script "ImportSymbolsScript.py" to import my gcc symbols.  I made a standalone version to not do the GUI part and pass in what I needed as parameters, however, other than the GUI it is exactly the same.  But it seems like this code is triggering some extra analysis?  If I comment out this code and only disable the analysis then nothing runs as expected.
Also, I noticed if I run the original symbol import script above from within the GUI instead of headless then it looks like it does some extra things other than just setting names to addresses from the table.

@RedOctober45 Did you ever get this sorted out?  Can we close this ticket?

Something I've noticed just recently that while createFunction does trigger disassembly of the functions created, it does not seem to trigger full auto-analysis. I have a preScript that is based on this API and is run with -noanalysis.
However, when you reopen the database, you'll be prompted to run auto-analysis, even though the functions that symbols were created for have had initial disassembly done. I haven't tested this, but if you only want the labels added and not trigger the initial function disassembly that happens, maybe switching out the createFunction call for createLabel will have the desired effect.

@RedOctober45 Did you ever get this sorted out? Can we close this ticket?

Yes, thank you


[CI] mesheryctl not being released

Current Behavior
The latest Meshery releases are missing mesheryctl.
See error - https://github.com/meshery/meshery/actions/runs/5884206332/job/15958482281

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation
Meshery documentation site and source
🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack
🧪 Meshery Test Plan Spreadsheet

This seems a problem related to Homebrew 👀💀

I think this was solved by @theBeginner86

Yes fixed here: https://github.com/meshery/meshery/pull/8518.


[WIP][spaceship] Initial new API requests but need to implement into pilot yet

Fixes #14033
Description
Private API deprecated some review and testing info for TestFlight Beta apps so now need to use new AppStore Connect API
Example lane that does all the things (for now)
lane :space_connect do                                                                                [1462/1962]
    fastlane_require 'spaceship'
<EMAIL_ADDRESS>    Spaceship::Tunes.select_team(team_name: 'some team name')

    app = Spaceship::Tunes::Application.find("com.some.bundle")
    app_id = app.apple_id
    puts "app_id: #{app_id}"

    build = Spaceship::TestFlight::Build.latest(app_id: app.apple_id, platform: 'ios')
    resp = Spaceship::ConnectAPI::Base.client.get_builds(filter: { expired: false, processingState: "PROCESSING,VALID", version: build.build_version })
    build_id = resp.first["id"]
    puts "build_id: #{build_id}"

    client = Spaceship::ConnectAPI::Base.client

    #
    # App reivew detail
    #
    attributes = {
      contactEmail<EMAIL_ADDRESS>      contactFirstName: 'Connect',
      contactLastName: 'API',
      contactPhone: '5558675309',
      demoAccountName<EMAIL_ADDRESS>      demoAccountPassword: 'somepass',
      demoAccountRequired: true,
      notes: 'This is api connect fastlane notes'
    }
    app_review_detail_patch = client.patch_beta_app_review_detail(app_id: app_id, attributes: attributes)
    puts "app_review_detail_patch: #{app_review_detail_patch}"

    #
    # App test information
    #

    localizations = client.get_beta_app_localizations(filter: {app: app_id})
    puts "localizations: #{localizations}"
    localization_id = localizations.first["id"]
    puts "localization_id: #{localization_id}"
    attributes = {
      feedbackEmail<EMAIL_ADDRESS>      marketingUrl: "https://joshholtz.com/marketingfromapi",
      privacyPolicyUrl: "https://joshholtz.com/policyfromapi",
      #tvOsPrivacyPolicy: nil
      description: "description from new api",
      #locale: nil
    }
    localizations_patch = client.patch_beta_app_localizations(localization_id: localization_id, attributes: attributes)
    puts "localizations_patch: #{localizations_patch}"

    #
    # Build test information
    #
    localizations = client.get_beta_build_localizations(filter: {build: build_id})
    puts "localizations: #{localizations}"
    localization_id = localizations.first["id"]
    puts "localization_id: #{localization_id}"
    attributes = {
      whatsNew: "something new from api"
    }
    localizations_patch = client.patch_beta_build_localizations(localization_id: localization_id, attributes: attributes)
    puts "localizations_patch: #{localizations_patch}"
  end

          1 Warning

:warning:
Pull Request is Work in Progress

  Generated by :no_entry_sign: Danger

👍 nice!

This would explain the errors related to "notes". Thanks!


Image as input

Steps for Simple Image-Based Analysis:
1. Preprocessing:

Obtain a clear outline image of the Lego castle with distinct shapes representing each block level. Ensure the outline is well-defined and easily distinguishable.

2. Block Detection:

Divide the image into sections corresponding to different block levels or distinct parts of the castle (e.g., the 5x1 block, 3x1 block, 1x1 block).
Define criteria or thresholds to detect each block's outline by recognizing patterns or shapes that represent individual Lego blocks.

3. Matching Algorithm:

Develop a matching algorithm to fit the detected outlines to predefined shapes representing Lego blocks (e.g., rectangles for blocks of different sizes).
Use geometric transformations (like rotation, translation, scaling) to match the detected outlines to the predefined block shapes.

4. Hierarchical Assembly Interpretation:

Based on the matched shapes and their positions, infer the hierarchical structure of the castle.
Define rules or algorithms to interpret the relationships between detected block outlines to determine their hierarchical assembly order (e.g., bottom-up approach).

5. Planning Robotic Actions:

Translate the interpreted hierarchical structure into actionable instructions for the robot arm.
Generate a sequence of pick-and-place actions based on the interpreted assembly order and block positions.

6. Testing and Validation:

Test the algorithm with various castle outlines to verify its accuracy and robustness in correctly identifying the block levels and their relationships.

7. Iterative Refinement:

Refine the algorithm based on testing results and edge cases encountered during analysis to improve accuracy and reliability.

Example Approach:
For instance, if the outline represents a 3-level castle with a 5x1, 3x1, and 1x1 block:

Divide the outline into segments corresponding to the expected blocks.
Develop an algorithm that compares these segments with predefined shapes and sizes of Lego blocks.
By assessing how well the segments fit the predefined block shapes, determine the probable order and orientation of these blocks within the castle structure.

Considerations:

Algorithmic Precision: This approach heavily relies on the accuracy of outline detection and the matching algorithm's precision. Any noise or deviations in the outline might affect the accuracy of block recognition.
Scalability and Adaptability: Ensure the algorithm can handle variations in block arrangements and shapes, as well as different castle configurations.

While this method aims for precision without machine learning or 3D understanding, it requires robust image processing and shape-matching algorithms to accurately interpret the outline and infer the assembly sequence. Testing with various outlines and refining the algorithm iteratively will be crucial to achieving reliable results.

Template matching:

Create for each block sample a template image. Consider 2 version: first one is the full block, second is the cut out of the top connector.
Apply template matching using OpenCV. Consider Alpha-Dependent Template Matching and Multi-scale Template Matching.
Using width and height info result to calculate the floor of the construct.
Using the block X1-Y1-Z2 as a core to calculate other references (eg: 4 blocks X1-Y1-Z2 at the same floor can be 1 block X1-Y4-Z2)


Wrong .bower.json

missing "main": "instafeed.min.js", for wiredep work. in bower installation

Sorry @octavioamu, not sure I follow. What issue are you having?

The bower package have the .bower.json like this:
{
  "name": "instafeed.js",
  "homepage": "https://github.com/stevenschobert/instafeed.js",
  "version": "1.3.2",
  "_release": "1.3.2",
  "_resolution": {
    "type": "version",
    "tag": "v1.3.2",
    "commit": "148b6dec6eceeb8a5512e815a82ba7869beb3197"
  },
  "_source": "git://github.com/stevenschobert/instafeed.js.git",
  "_target": "~1.3.2",
  "_originalSource": "instafeed.js"
}

And should be like this:
{
  "name": "instafeed.js",
  "homepage": "https://github.com/stevenschobert/instafeed.js",
  "version": "1.3.2",
  "main": "instafeed.min.js",
  "_release": "1.3.2",
  "_resolution": {
    "type": "version",
    "tag": "v1.3.2",
    "commit": "148b6dec6eceeb8a5512e815a82ba7869beb3197"
  },
  "_source": "git://github.com/stevenschobert/instafeed.js.git",
  "_target": "~1.3.2",
  "_originalSource": "instafeed.js"
}

Because grunt wiredep ( a plugin to automatic injection of the bower packages into the html) need this to know how to create the link inside the html files.
For example in this case the plugin will create the link
<script src="bower_components/instafeed.js/instafeed.min.js"></script>

This was an issue for me as well. Added the "main" and it worked fine afterwards.
Running gulp command wasn't building it into main.js.
File updated was: /bower_components/instafeed.js/package.json

@davidyeiser recommend you to use the bower overrides in bower.json of your project and not inside bower_components.
The way you do gulp will override in any npm update of the project or when you decide to install again etc. Yo never should modify anything inside "bower_components" this can be overrided in many situations, instead write this in /bower.json :
"overrides": {
    "instafeed.js": {
      "main": [
        "instafeed.min.js",
      ]
    }
  },

Ah, good to know, this is very helpful. Thank you for taking the time to mention it.

Thank you guys! This fixed my issue with gulp wiredep perfectly. This is an awesome tool @stevenschobert!

specs about main https://github.com/bower/spec/blob/master/json.md#main
Again, this is "recommended" but must be required since a lot of tasks runners need it to know what files to inject in the project for the plugins works fine, otherwise people need to write the calls manually.


Add MiscellaneousDocument model and upload script

Resolves https://github.com/opensyllabus/osp-pipeline/issues/147.

Implements a MiscellaneousDocument model based on the approach where the filenames of the documents are md5sums.  The model and corresponding load_* job is a simpler version of the BenningtonDocument model; no entry in sources is required because the model is just two entries, data_md5 and data, and correspondingly, MiscellaneousDocument.from_source is very straightforward.
Adds a script for extracting files from a zipfile and saving each in either an S3 bucket or a local directory.  Files are saved with their md5sums as the filename, and stored flatly (no subdirectories).

I've already used the script to upload the two current batches of miscellaneous documents to the bucket "osp-miscellaneous-docs".
The tests for this are pretty limited at the moment.  I've updated the merge_documents.py tests accordingly, but with the current approach, testing load_miscellaneous_documents.py is blocked in the same way that testing the other load_* jobs is blocked.  I could build around it (and I have kind of done some of that work already in the classifier module tests), but it might be more expedient to just try running the job on a cluster and seeing if it works.
Question: Should the model be named MiscDocuments or something instead of MiscellaneousDocuments?  I wanted to be clear and "proper", but I realize that 'miscellaneous' is kind of hard to spell...

@wearpants I changed the names to be based on 'manual' instead of 'miscellaneous', as discussed.  I don't really like that name, but I couldn't think of another name that felt both descriptive and convenient to use (assorted docs?  random docs?  md5 docs?).

Also, I can spin up a cluster and try running the job before merging if that's appropriate.

I ran and the job and verified it against extractions in a local directory.  After one small fix everything seems to be working.
@wearpants One thing I thought of is the rows_per_output_partition class variable.  I just copy-pasted the one from BenningtonDocument, but should it be any different?

How many manual docs are we talking about?
On Feb 27, 2018 8:41 PM, "jodizzle"<EMAIL_ADDRESS>wrote:

I ran and the job and verified it against extractions in a local
directory. After one small fix everything seems to be working.
@wearpants https://github.com/wearpants One thing I thought of is the
rows_per_output_partition class variable. I just copy-pasted the one from
BenningtonDocument, but should it be any different?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/opensyllabus/osp-pipeline/pull/151#issuecomment-369091012,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAe2AJRJyvSb8cbNosxtYvr_67XO0n6Gks5tZK6zgaJpZM4STz5O
.

At the moment there are 17379.

Seems fine
On Feb 27, 2018 10:01 PM, "jodizzle"<EMAIL_ADDRESS>wrote:

At the moment there are 17379.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/opensyllabus/osp-pipeline/pull/151#issuecomment-369105504,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAe2AEPuCbfsE9tLEMkWw2NuPFmLZbhrks5tZMGPgaJpZM4STz5O
.

Alright, gonna go ahead and merge.


February 2024 NPM Security Vulnerabilities Resolution

This PR is to resolve security vulnerabilities.
Note that the Lerna package was updated from v6 => v8. As of Lerna v7, the bootstrap package management command was deprecated. We are now not utilizing Lerna's bootstrap command, and are now relying on 'yarn install' to install the dependencies for each sub-package in the project (see the new 'workspaces' field in package.json. More information can be found here).
Validation steps:

yarn install
yarn audit
Ensure there are 0 vulnerabilities found
yarn run test
Ensure that all 12/12 test suites are passing

Coverage remains the same before and after changes. See below for specific coverage reports for each sub-package.
Coverage before changes:

Coverage after changes:

Moved to #350


Add support for Debezium read operations

This PR adds support for read operations found in Debezium CDC topics treating them as create

 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.

@meegoo PTAL


Some invalid instances of valid schemas do not display in the output of elyra-metadata list CLI

When I run the elyra-metadata list command I get the following output:
elyra va$ elyra-metadata list code-snippets
[E 2020-05-15 14:57:33,386.386] Schema validation failed for metadata 'project-snippet' in namespace 'code-snippets' with error: 'display_name' is a required property.
Available metadata instances for code-snippets (includes invalid):
Schema         Instance        Resource
------         --------        --------
code-snippet   common-imports  /Users/va/Library/Jupyter/metadata/code-snippets/common-imports.json
code-snippet   create temp     /Users/va/Library/Jupyter/metadata/code-snippets/create temp.json
code-snippet   is_even         /Users/va/Library/Jupyter/metadata/code-snippets/is_even.json
code-snippet   js-test         /Users/va/Library/Jupyter/metadata/code-snippets/js-test.json

The project-snippet instance fails the validation check (with error: 'display_name' is a required property) and the instance does not get listed in the table. I was expecting for it to be in the table but include the **INVALID** (ValidationError) disclaimer (as seen in #524).

Thanks for catching this.  It turns that that the lack of a display_name was also causing the creation of the Metadata instance itself to fail - which occurs after validation.  That subsequent failure was preventing the invalid instance from being added to the result set (when include-invalid = True).  This has been fixed in my work for #483 which should be ready shortly.


Duplicate files created

Hi! Not sure if I'm missing something very obvious here, but sometimes after building and deploying, duplicate files will be created that then cause problems the next deployment.
For example, in addition to 1-project.md it will create a 1-project 2.md in the same folder. A similar thing happened for all of my images: 1-img.jpg became 1-img 2.jpg and so on.

Apologies; this seems to be an iCloud issue that i assumed was an issue w/ this repository because I had only seen it pop up using this.


Automate ConMon scanning

In order to save time and assure accuracy, we want to automate ConMon scans via a headless OWASP Zap container running on a Concourse worker
Acceptance Criteria

[ ] GIVEN ConMon Scans are due
WHEN a member of the compliance team wants to get the results
OR the JAB wants to audit the scans
THEN a member of the compliance team can find the results of a Concourse pipeline (storage TBD maybe S3?) \

Security considerations
The security consideration is that the results will support the POAM requirements from the JAB
Implementation sketch

[ ] Create a functional OWASP Zap container and make sure it runs the ConMon scans
[ ] Create or use an existing Concourse pipeline to run the OWASP Zap container

This issue is being closed as it is a duplicate of https://github.com/cloud-gov/product/issues/2561 which is the more recent story.


[WIP] First golden test for google_maps plugin

Still needs to connect to CI
Still needs to hook up to a device etc.

Once #1342 lands your driver test will run on Cirrus automatically. However you probably will have different results on iOS and Android so you should probably use the device_info plugin to figure out what device you're connected to and choose the appropriate golden to compare against.


Nodes and Nps are not updated when the engine doesn't report them alongside with PV

When playing, my UCI engine doesn't send the number of nodes alongside with PV, but reports it separately. For example, the output may look as follows:
go infinite
...
info depth 11 time 1160 pv d2d4 g8f6 b1c3 d7d5 g1f3 b8c6 e2e3 c8f5 f1d3 f5d3 d1d3 score cp 57
info depth 12 time 2996 pv e2e4 e7e5 g1f3 g8f6 b1c3 b8c6 f1d3 f8d6 e1g1 e8g8 c3b5 d6c5 score cp 16
info nodes 18567391 time 3010 nps 6166569
info depth 13 time 4993 pv e2e4 e7e5 g1f3 d7d5 f3e5 b8d7 e5d7 c8d7 e4d5 f8d6 f1c4 d8h4 d1e2 score cp 42
info nodes 36638104 time 6022 nps 6083159
info nodes 54337370 time 9004 nps 6034702

Still, web UI shows Nodes: 0.00 instead of the reported number.
I am not sure whether it's an issue in node-tlcv or the underlying TLCV server.

TLDR This is an issue with the server.

The nodes and time come on the PV command from the server. My imagination is that the pv command is sent whenever a pv is printed by the engine, but not for other cases, thus resulting in the behavior you see.
I cannot confirm this as I do not own the server code.

I can confirm now that it's really the issue with TLCV server, as other clients also do not show Nodes and Nps for me. Sorry for disturbing.


Permission configured per tag doesn't work

The new feature Permission can now be configured per tag doesn't seem to be working as intended.
I tried to set my permissions in a way, that private discussions are restricted to a specific tag (lets call it private). I tried those two options:
a) Restrict privat discussions globally and allow it individually for the private tag.
b) Allow privat discussions globally and restrict it individually for all but the private tag.
Option a) seems to me the most intuitive way to do it, but neither a) nor b) achieves what I want. In both cases, the global setting overrides the tag setting leaving privat messages generally disallowed in a) and allowed in b), the tag doesn't make a difference.
An issue with the core seems related to this observation: https://github.com/flarum/core/issues/1146
What I would like to see in a perfect world (in my case scenario) is the following:
When a user starts a new Discussion and selects a tag differently from private, the recipients selector should be greyed out. If he selects recipients first (also in the case of the link from the usercard), the tag input should only allow private (or the tag should be selected automatically).
One thing, I didn't make up my mind about yet: If a user selects two tags, one with the permission to open a private discussion, one that doesn't allow it, which setting should precede?

Can you make a distinction between:

Primary tags
Secondary tags
Helper tags (that's what I call secondary not under any primary)

That clarification might help me understand your situation better.

That's interesting.
Case 2 doesn't make a difference compared to 1. Case 3 however ist different. I made private a helper tag und followed the Route a) of my initial report:
a) Restrict privat discussions globally and allow it individually for the private tag.
Unfortunately I now have to select another (primary) tag as well defeating my intended use case. But apart from that, this setup allowed to open a private discussion and thus overrule the global rule.
Which as well gives an answer to my last thougth in my initial report. If two tags are selected, one allowing private discussions and one forbidding them, allowance will be granted.

Sorry, I have to correct myself. Case 3 is not different at all. My false impression resulted from myself acting as admin, who obviously couldn't be restricted globally. As a normal user I was not able to open a private discussion in the described way, with or without the private tag, from the Start a new Discussion as well as from the usercard.
So, there is no indication, that the global setting could be overruled by a helper tag.

Any news on this, we are facing the same issue!

@glowingblue not yet, I haven't been able to look into it. Any further investigation might help solve this sooner. I'm a little stuck with other responsibilities, but once Flarum beta 8 is out all Flagrow extensions will be revisited and bugs/features taken care of. Byobu will be one of the first.

Closing this now as byobu no longer uses tags in any way


Quoting strings

I am currently reviewing True's code to understand how it works, and it occurred to me it would be easier to read if strings were quoted.
If you feel like it would be nice to have all strings quoted, I would be happy to submit a pull request doing just that, @ericam. :)

hmmmm, I tend to think of quotes as clutter — like adding () to all your lists. But if you made a PR, I probably wouldn't reject it. :)

I'll give it a go. ;)

Done in v3.

@HugoGiraudel I think you are confusing Susy and True. Maybe it is time for a True v3 though?

I did a final sweep. All strings should be quoted now. I wish we could lint for that.


Fix hover

Hover sometimes doesn't return the correct value.
f : Bool -> Bool
f = \case
    True => False
    False => True
          *  ^

If a save, then hover over ^ I get Prelude.True : Bool. However, if I hover over * then hover over ^, I get Test.case block in f : Bool -> Bool. If this to overlapping ranges being added to the cache?
Also, for a better user experience hover should return a range.
I tried to fix this at one point but ran into https://github.com/idris-lang/Idris2/issues/1506 and https://github.com/idris-lang/Idris2/issues/1543
Additionally hover should show documentation. There also is probably a better way to handle hiding/showing implicit arguments.

If anyone else is having an issue with this, I've found a quick way to 'reset' is to just edit the line (I add a space and remove it), save the file again, and then move up and down to get it to reload the arguments.


Azure Decision Tree - "loud optimized" .. should be "cloud optimized"

Hey folks,
looking at the doc, I think the decision title for one line is incorrect .. Start -> Migrate -> "loud optimized" I think should be "Cloud Optimized"

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

ID: 510808e8-db5d-6b07-9a04-6edb743a2dfc
Version Independent ID: 20d098aa-ef31-cb26-d677-765cfc9a7164
Content: Choose an Azure compute service - Azure Architecture Center
Content Source: docs/guide/technology-choices/compute-decision-tree.yml
Service: architecture-center
Sub-service: azure-guide
GitHub Login: @EdPrice-MSFT
Microsoft Alias: architectures

@garyciampa Thanks for the feedback. We will review and update as appropriate.

Tagging @seanli1988 for awareness

I pushed a PR fix: AAC - compute decision tree by stephen-sumner · Pull Request #8135 · MicrosoftDocs/architecture-center-pr (github.com)


Add Dockerfile for E2E tests

Summary

Adds a Dockerfile for building an image through which to run the E2E tests in k8s.
Ticket Link

Part of MM-38160

Force-push is just a fix to the commit message itself; I typed the wrong version into the commit message :facepalm:


PHPLIB-1569: Implement $$matchAsDocument and $$matchAsRoot

https://jira.mongodb.org/browse/PHPLIB-1569
https://jira.mongodb.org/browse/PHPLIB-1577
POC for https://github.com/mongodb/specifications/pull/1706
Includes an extra test for numeric comparisons, which can be removed when PHPLIB-1577 is addressed.

Note: I'll rebase and merge this after https://github.com/mongodb/specifications/pull/1706 is closed.


Unsupported class file major version 65

When I execute gradle test --stacktrace, I have the following exception.
Caused by: BUG! exception in phase 'semantic analysis' in source unit '/Users/i303937/SAPDevelop/easy-extensions/helloworld/src/main/groovy/com/sap/cx/boosters/easy/extension/helloworld/easyrest/controller/HelloWorldController.groovy' Unsupported class file major version 65

java -version shows I'm using version 17.
openjdk version "17.0.9" 2023-10-17 OpenJDK Runtime Environment Homebrew (build 17.0.9+0) OpenJDK 64-Bit Server VM Homebrew (build 17.0.9+0, mixed mode, sharing)
gradle -version shows the Gradle used JVM 21.0.1.
------------------------------------------------------------
Gradle 8.4
------------------------------------------------------------

Build time:   2023-10-04 20:52:13 UTC
Revision:     e9251e572c9bd1d01e503a0dfdf43aedaeecdc3f

Kotlin:       1.9.10
Groovy:       3.0.17
Ant:          Apache Ant(TM) version 1.10.13 compiled on January 4 2023
JVM:          21.0.1 (Homebrew 21.0.1)
OS:           Mac OS X 14.0 aarch64

./gradlew -version shows the Gradle used JVM 17.0.9.

As a workaround, I added the section below to build.gradle
java {
    toolchain {
        languageVersion = JavaLanguageVersion.of(17)
    }
}

fixed #65

Another workaround is to run gradle wrapper and then ./gradlew test