WATSON_USE_INTENT not working

Following the guide from 10 Minutes: Codeless Test Automation for IBM Watson Chatbots,  I was able to import watson-intents and create testcases to test intents but recently, I have not been able to do so - I set WATSON_USE_INTENTS to true, but it continues to return me the whole text when I run the testcases.

It is only five days ago that this bug has been fixed. did you upgrade to the latest build ?

I did a fresh install and its working again - sorry about that.  I swear I had updated though...

np
glad to help


Modified hello_quantum.py to make it compatible with the textbook

Please notice I did not add it to the TOC.

👍


Set-of-emails logo

Coverage remained the same at 95.02% when pulling 67bcfd3d6614835a6f6dbd48432c84e69fd64267 on batarian71:master into 7ff2618e34ec53a77616ae495304238ff105a505 on sisimai:master.


dss

Environment (please complete the following information):

OS (e.g., Windows 10):
Extension version (e.g., 1.2.3):

Describe the bug:

Repro steps:

Expected behavior:

Additional context:

Thanks for reaching out, unfortunately this issue does not contain enough information for us to investigate the problem.
I will close it for now, but feel free to come back with more information.


test: add wait time on subs e2e

add a wait time after setting up a subscription to avoid hanging
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2560 into master will increase coverage by 0.43%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2560      +/-   ##
==========================================
+ Coverage    65.4%   65.83%   +0.43%
==========================================
  Files         200      194       -6
  Lines        9697     9633      -64
  Branches     1973     1959      -14
==========================================
  Hits         6342     6342
+ Misses       3080     3017      -63
+ Partials      275      274       -1

Impacted Files
Coverage Δ

...plify-appsync-simulator/src/velocity/util/index.ts

...ync-simulator/src/mqtt-server/abstract-listener.ts

...-appsync-simulator/src/velocity/util/list-utils.ts

.../amplify-appsync-simulator/src/mqtt-server/util.ts

...sync-simulator/src/velocity/value-mapper/mapper.ts

...es/amplify-appsync-simulator/src/velocity/index.ts

...s/amplify-appsync-simulator/src/resolvers/index.ts

...ages/amplify-appsync-simulator/src/server/index.ts

...amplify-appsync-simulator/src/mqtt-server/index.ts
0% <0%> (ø)

...tor/src/velocity/util/transform/dynamodb-filter.ts
0% <0%> (ø)

Continue to review full report at Codecov.

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


Do not treat handlers actions that have not been implemented as a dispatch failure

If a handler raises a NotImplementedError for a given action, Magpie will consider that a webhook failure.
This is misleading because the webhook didn't actually fail, there was simply nothing to do since the action isn't implemented.
This PR changes the webhook dispatcher to treat handler actions that raise NotImplementedErrors as a noop instead of as an error.
For example:

when a user is created, the Nginx.user_created handler is triggered, this method raises a NotImplementedError  which is reported to Magpie as a webhook failure.
Admins who are then looking at the user status think that there is a cowbird error and that the user was not properly created. In fact, the user was properly created since all webhooks that are implemented ran with no errors.

Other possible solutions to this problem:

instead of raising a NotImplementedError, concrete implementations of the Handler class can simply pass instead
instead of raising a NotImplementedError, abstract methods in the Handler class can simply pass instead (all concrete implementations can then optionally override these methods if needed)

I'd argue that if a webhook was configured to point at some action leading to an NotImplementedError, this is potentially not the intended action/resolution.
I would prefer the other proposed solution that the concrete implementation does an explicit no-op. It could also log that it was a no-op, so there is some traceability of the invoked handlers and actions performed.
The NotImplementedError are there really to raise that missing implementation, which was identified here because it was not silenced.

@fmigneault
Alright, I've updated the concrete classes. Let me know what you think.
Also: is debug an appropriate log level?

Oh wow. I didn't realize there were this many still unimplemented.

debug an appropriate log level

Mixed answer.
I'd say the ones with FIXME should probably be WARN since they should really be implemented at some point to "fix" misfired events to retry via Cowbird's API.
The ones under Magpie should probably be ERROR and even leave the intended raise NotImplementedError, since I don't see why Magpie user create/delete events triggered by Magpie would send a webhook to Cowbird. That is almost certainly a misconfiguration.
The others with INFO, since it can make sense that they would have "nothing to do", depending on the integration each service/event combination implies with the others, but we should still inform about the events happening so it's easy to tail the Cowbird logs and inspect the operations performed, without need to change the default logging level.
Personally, I would leave DEBUG only for cases where debugging is involved, such as intermediate steps and such.

I'll update the log levels to your suggestions.

leave the intended raise NotImplementedError, since I don't see why Magpie user create/delete events triggered by Magpie would send a webhook to Cowbird. That is almost certainly a misconfiguration.

Ok but I don't know how you can configure this so that Magpie user/delete doesn't trigger when a user is created/deleted. Is it possible to enable a handler only for certain events but not others?
If not, then we'll end up with the exact situation that we're trying to avoid... an error is raised every time a user is created or deleted and Magpie thinks that the webhook failed.

@mishaschwartz
Good point. If you can validate that the current configuration when creating a Magpie user ends up calling Cowbird's Magpie handler "on user create" event, then using an appropriate WARN message indicating why it is discarded instead of the raise NotImplementedError is adequate.

Yes I can validate that this is the case.
From the cowbird logs when a user is created:
[2024-12-18 18:05:46,960] INFO       [ThreadPoolExecutor-0_0][cowbird.api.webhooks.views] Dispatching event [Handler) -> None] for handler [Magpie].
[2024-12-18 18:05:46,960] ERROR      [ThreadPoolExecutor-0_0][cowbird.api.webhooks.views] Exception raised while handling event [Handler) -> None] for handler [Magpie] : [NotImplementedError()].
Traceback (most recent call last):
  File "/opt/local/src/cowbird/cowbird/api/webhooks/views.py", line 35, in dispatch
    handler_fct(handler)
  File "/opt/local/src/cowbird/cowbird/api/webhooks/views.py", line 66, in handler_fct
    handler.user_created(user_name=user_name)
  File "/opt/local/src/cowbird/cowbird/handlers/impl/magpie.py", line 293, in user_created
    raise NotImplementedError
NotImplementedError

https://github.com/Ouranosinc/cowbird/tree/2.5.0 is pushed with the merged PR
the docker should be ready soon enough


Move  Prefect  from  HTTP to HTTPS

Running prefect1 for the time being.
Every env will have its own complete set up.
https://prefect2.hedwig-workflow-api.niaiddev.net/
Will be the dev HTTPS set up, etc.


Deployment template and Installation instructions

https://github.com/Azure/application-gateway-kubernetes-ingress/issues/33

https://github.com/akshaysngupta/application-gateway-kubernetes-ingress/blob/deploymentTemplate/docs/install-new.md

@akshaysngupta Tried the revised simplified instructions with ARM templates.
Works great ! Thanks.


pre-requisite to tun./JioTV on Linux (Ubuntu Touch)

Hello, as you advise earlier to run this project on Linux, I am able to run this on my Ubuntu laptop.
but not able to run it on Ubuntu Touch phone.
please advise any pre requisite for this project
example reference
Then type chmod +x JioTV
Then type ./JioTV

If your using Ubuntu Touch, you need follow How To Use (From Source) .

I am closing this ticket, feel free to open it again.


[SPARK-19219][SQL] Fix Parquet log output defaults

What changes were proposed in this pull request?
Changing the default parquet logging levels to reflect the changes made in PR #15538, in order to prevent the flood of log messages by default.
How was this patch tested?
Default log output when reading from parquet 1.6 files was compared with and without this change. The change eliminates the extraneous logging and makes the output readable.

Test build #71345 has started for PR 16580 at commit cb80164.

Link to this JIRA issue: https://issues.apache.org/jira/browse/SPARK-19219
Link to original issue: https://issues.apache.org/jira/browse/SPARK-17993

So the change here is really to turn up the log level for non-test code, not just the test code? it seems possibly reasonable but are there important warnings this would suppress for users?

That's possible. We could narrow the scope a bit and instead just set log4j.logger.org.apache.parquet.CorruptStatistics=ERROR log4j.logger.parquet.CorruptStatistics=ERROR,
which also fixes the problem.

Test build #71345 has finished for PR 16580 at commit cb80164.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71345/
Test PASSed.

@nicklavers yeah narrowing the scope seems more conservative and desirable. Do the test configs need to be changed similarly to match your newer proposal?

Test build #71459 has started for PR 16580 at commit c7df9ac.

Test build #71460 has started for PR 16580 at commit cb80164.

I don't see why not

Test build #71462 has started for PR 16580 at commit 6788987.

Test build #71459 has finished for PR 16580 at commit c7df9ac.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71459/
Test PASSed.

Test build #71462 has finished for PR 16580 at commit 6788987.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71462/
Test PASSed.

Test build #71460 has finished for PR 16580 at commit cb80164.

This patch fails from timeout after a configured wait of `250m`.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71460/
Test FAILed.

Merged to master


Install and import xgboost in Python Azure Function app doesn't work

The deployment of a python function on Azure Function app (which works on a local host) doesn't work because of the import of the xgboost package. The error is :
Exception: XGBoostError: XGBoost Library (libxgboost.so) could not be loaded.
Likely causes:
OpenMP runtime is not installed (vcomp140.dll or libgomp-1.dll for Windows, libgomp.so for UNIX-like OSes)
You are running 32-bit Python on a 64-bit OS
Error message(s): ['libgomp.so.1: cannot open shared object file: No such file or directory']
This thread adresses the issue : #493
We tried to put the .whl directly in the function folder and install the package from there, which didn't work.
I opened this thread where I was told by @anirudhgarg  to open a new issue here as it seems that the issue comes from the libcomp.so library.
I was also told by @mike-urnun-msft to open this thread on msdn forum.
Thanks !

@cconcordet thanks for opening. Do you by any chance have a sample app that we can try to repro this.

I am sorry I can't share my code but it seems that the error comes from the following line
import xgboost
I can try to produce a sample if that is not enough information ?

Any updates ?

I have similar problem with lightGBM.
That is, libgomp seems to be missing in Azure Functions Runtime like in xgboost case.
Code to reproduce libgomp missing problem with lightGBM
import logging
import lightgbm
import azure.functions as func

def main(req: func.HttpRequest) -> func.HttpResponse:
    logging.info('Python HTTP trigger function to get lightgbm version.')
    lgb_version = lightgbm.__version__
    return func.HttpResponse(f"lightgbm version is {lgb_version}!")

requirements.txt:
azure-functions
lightgbm

Error:
Result: Failure
Exception: OSError: libgomp.so.1: cannot open shared object file: No such file or directory
Stack:   File "/azure-functions-host/workers/python/3.6/LINUX/X64/azure_functions_worker/dispatcher.py", line 242, in _handle__function_load_request
    func_request.metadata.entry_point)
  File "/azure-functions-host/workers/python/3.6/LINUX/X64/azure_functions_worker/loader.py", line 66, in load_function
    mod = importlib.import_module(fullmodname)
  File "/usr/local/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 941, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/site/wwwroot/HttpTriggerTestFunc/__init__.py", line 2, in <module>
    import lightgbm
  File "/home/site/wwwroot/.python_packages/lib/python3.6/site-packages/lightgbm/__init__.py", line 8, in <module>
    from .basic import Booster, Dataset
  File "/home/site/wwwroot/.python_packages/lib/python3.6/site-packages/lightgbm/basic.py", line 33, in <module>
    _LIB = _load_lib()
  File "/home/site/wwwroot/.python_packages/lib/python3.6/site-packages/lightgbm/basic.py", line 28, in _load_lib
    lib = ctypes.cdll.LoadLibrary(lib_path[0])
  File "/usr/local/lib/python3.6/ctypes/__init__.py", line 426, in LoadLibrary
    return self._dlltype(name)
  File "/usr/local/lib/python3.6/ctypes/__init__.py", line 348, in __init__
    self._handle = _dlopen(self._name, mode)

Hello @anirudhgarg ,
Any updates ?


28986 - Yaqui

898 is longer version of 164 - so 164 should be removed. The two are coded differently, so could be worth recoding the track. Spelling for recorder surname is Yurchenko (though the album cover says Urchenko).
899 is recorder by Laura C. Boulton, as indicated in the album.
society centroid could be move closer to songs and EA and GeLaTo centroids. EA Yaqui is 28, -110.

Looking into this-- audio for 898 actually seems to be incorrect. It shouldn't be the same song as 164. Coding and metadata are correct. Replaced with correct audio file.
Corrected spelling of Henrietta Yurchenko for song 164.
898 and 899 should both have recordist name as Laura Boulton. Correction implemented.
Recording location for 898 and 899 is indeed Tlaxcala, but the liner notes clarify that this is where Yaqui people have been displaced to due to being enrolled in the Mexican army, and emphasizes their connection to their homeland in Sonora. I am changing location name to "Yaqui Valley, Sonora, Mexico [Recorded in Tlaxcala, Mexico]" and moving lat-lons to Yaqui Valley.
Changed society centroid to lat-lon of all songs (27.36, -110.16), which is closer to EA centroid as well.


feat(pointcloud): Support displaying status on hover

:tada: This PR is included in version 1.13.0-alpha.3 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.20.0-alpha.3 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.17.0-alpha.4 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.13.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.20.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.17.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


feat: Write integration tests for improving the API coverage.

Closes https://github.com/bvanelli/actualpy/issues/7

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Tooltip is not tracking trigger element when resizing window

Relevant issue: https://github.com/ReactTooltip/react-tooltip/issues/1057

Thanks for the contribution.
Have you seen the autoUpdate() function function? I believe we should use it.
For now, I suggest the options to be set ancestorResize, elementResize, and layoutShift.
Don't forget to call the cleanup function on the useEffect() return.

I see you're still making some adjustments, but at first glance it looks ok.
Will review sometime this week.
Thanks again for the contribution!

We may need to mock ResizeObserver to get the tests to pass
https://stackoverflow.com/a/67006794
@Tanmayshetty no need to worry about this. I'll get to it when I have the time to fully review this later.

@Tanmayshetty made some adjustments, and everything's looking good!
Will wait for @danielbarion's review, then we'll merge and release this soon.


Add support for parsing packets consisting of arbitrary data followed only by a terminator.

ORSSerialPacketDescriptor's design was driven by a desire to design a system that is robust against dropped or corrupted data. As such, it currently only supports describing and parsing full-specified packets. That is packets whose start and end (at least) can be clearly determined from the data alone.
However, it is fairly common for serial data to come in line by line where the data is arbitrary bytes followed by a terminator. A complete packet in this case is just all the data that has come in since the last packet finished (ie. terminator was received). As it stands, ORSSerialPacketDescriptor and the packet parsing API can't handle this kind of data.
It may require adding a special case for this in the packet parsing logic.

You might also consider allowing a packet to be described by a suffix and/or prefix and a fixed number of bytes. For example, 22 bytes starting with a prefix of <12 d3 6a>. This can be done with a PacketEvaluator however that requires a lot of code for such a simple requirement.

On Oct 7, 2015, at 1:43 PM, Andrew Madsen<EMAIL_ADDRESS>wrote:
ORSSerialPacketDescriptor's design was driven by a desire to design a system that is robust against dropped or corrupted data. As such, it currently only supports describing and parsing full-specified packets. That is packets whose start and end (at least) can be clearly determined from the data alone.
However, it is fairly common for serial data to come in line by line where the data is arbitrary bytes followed by a terminator. A complete packet in this case is just all the data that has come in since the last packet finished (ie. terminator was received). As it stands, ORSSerialPacketDescriptor and the packet parsing API can't handle this kind of data.
It may require adding a special case for this in the packet parsing logic.
—
Reply to this email directly or view it on GitHub https://github.com/armadsen/ORSSerialPort/issues/89.

Thanks for the comment, Clark. I agree. However I do want any solution for this to be more general. This issue was partly prompted by a user of ORSSerialPort writing an app that receives packets where the length is arbitrary.

I'd definitely put in a plug for something along these lines. I've been interacting with an Arduino sketch that has a predetermined protocol, and it uses just a packet terminator (\r\n), so I have not been able to make it work with ORSSerialPacketDescriptor. I am going to try and implement a work around myself, which I will mention in a pull request, although it may not be the best solution. And I would totally understand if you opt not to merge it given your 3.0 rewrite.
(Thanks for the great framework!)


IGAPP-669: Native file structure

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.

TODO:

[ ] adjust documentation
[ ] routes file structure?
[ ] services?

Best checkout this branch and have a look at the new file structure and let me know if you don't like something/have better ideas.
Things I am not sure about:

Quite some stuff in services, should we split that further? Do you think some files do not belong there?
Do the folders redux and navigation make sense as they are currently?
Should we move all components from routes to components, i.e. just keep one container/component per route?

Imo there are still a few files which could move from routes to services/utils (getNearbyPlaces/openProvacyPolicy/...).
For now I would flatten the routes to e.g. routes/offers/{Offers.tsx, OffersContainer.tsx}, as those components should not be used anywhere else. However I would refactor some components to the components directory such as EastereggImage or SearchInput.


Re-enable coveralls

Fixes #7

lgtm

i have no idea why coveralls isn't showing any data. i will try this again tomorrow to see if it's just a transient failure.

Looks like coveralls is having a bad day: http://status.coveralls.io/

Their queue is growing which is why the results aren't showing. As I suspected earlier, this repo is set up fine. I've subscribed to their status updates and will bump this PR when coveralls is working again.

@sectioneight What is the status of this?

coveralls outage is ongoing. following their status updates.


Undefined errors on windows server 2012

C:\gocode\src\github.com\Sirupsen\logrus\terminal_windows.go:22: undefined: io in io.Writer
C:\gocode\src\github.com\Sirupsen\logrus\terminal_windows.go:23: use of .(type) outside type switch
C:\gocode\src\github.com\Sirupsen\logrus\terminal_windows.go:24: undefined: os in os.File

It looks like terminal_windows.go didn't import both io and os. Should use the auto-importer when coding.

Same issue in Win10, your fix seems to work here also.

Thanks for the quick fix. Merged.


lock mode

Thank you for the plug-in that makes my switchbot work well.
Can you support the lock mode in homkit?
Thanks again

Thank you for your comment.
I'm interested in supporting lock mode and other modes, but I can't devote much time to this project as I'm developing it hobby.
For this reason, there are no plans at this time.


Serverside error: bad argument #2 to 'max' (number expected, got nil)

Serverside error:
lua/includes/extensions/math.lua:52: bad argument #2 to 'max' (number expected, got nil)
   0.  unkown - [C]:-1
    1.  max - [C]:-1
     2.  Clamp - lua/includes/extensions/math.lua:52
      3.  clampForce - addons/wire/lua/wire/wireshared.lua:998
       4.  CalcForce - addons/wire/lua/entities/gmod_wire_thruster.lua:142
        5.  unkown - addons/wire/lua/entities/gmod_wire_thruster.lua:242

Not sure how to replicate it sadly, but it's been happening in large volume

I think that means you had another addon's InitPostEntity hook error so wire's didn't run and thus the errors.

Something was breaking the hookchain, external issue indeed. Thanks for checking out anyway!


Online/Web Editor Default Project Directory is bad

Godot version:

Godot Web Editor 3.2.4 beta 4 https://godotengine.org/editor/latest/godot.tools.html (Currently b5e8b48bb)
OS/device including version:

Windows 10 1909, Google Chrome
Issue description:

the Default Path When Creating a new Project is "/home/web_user" however creating a new project at "/home/web_user/New Game Project" results in the new going bye bye the moment it is created.
Default Path Should be "/home/web_user/projects" instead of "/home/web_user" as "/home/web_user/projects" keeps the projects and doesn't instantly discard them.
Steps to reproduce:

Load the Web Editor, Make a New project with the default path
Wait like a second, after that the New project will be missing

Minimal reproduction project:

Cannot make MRP

Yeah, I can  confirm this. It was originally done to avoid storing the cache in the IndexedDB to save space, but in the end I opted to include it too (so opening projects is faster).
I'll try to come up with a better solution for the next version. I wonder if we can add boundaries to the project manager too (so it won't allow creating a project in /home/MyProject either).


Client library incorrectly returns error when FLAC is used with long-running-recognize

The client library incorrectly returns an error when anything other than LINEAR16 is used for a long-running recognize request:
https://github.com/GoogleCloudPlatform/google-cloud-python/blob/master/speech/google/cloud/speech/sample.py#L173
The v1 server support all encodings so this breaks functionality.
In general, the client library should almost never do it's own validation; it should always delegate to the server to be sure that that behavior and error messages are consistent across APIs.

In general, the client library should almost never do it's own validation; it should always delegate to the server to be sure that that behavior and error messages are consistent across APIs.

I am +(a million) on this.


Behavior subject's value is not updated correctly within the tap operator

Bug Report

Current Behavior
Every time when selectedPageSize$ emits a new value, state is updated with loading set to true, then the data is taken from todosService and state is updated with new data and loading set to false:
this.selectedPageSize$
  .pipe(
    tap(() => this.patchState({ loading: true })),
    switchMap(pageSize => this.todosService.getTodos(pageSize)),
  )
  .subscribe(todos => this.patchState({ todos, loading: false }));

As you can see in the screenshot, it works fine on first emission, but on each subsequent emission, when loading is set to true within the tap operator, it is immediately set to false.
Reproduction

Clone https://github.com/markostanimirovic/rxjs-state-mgmt-bug
Run npm install and ng serve --open
Repeat the steps from the screenshot above

Expected behavior
loading should not be set to false immediately after it is set to true.
Environment

Node v12.18.2
RxJS v6.6.0
Angular v10.2.0

Possible Solution

Open todos.facade.ts file. Comment out all expressions above the /** workaround **/ comments, uncomment all expressions bellow the /** workaround **/ comments.

Hi @markostanimirovic . I am not a maintainer.  It interesting. I would be easier to look at and less time consuming if it was online on codesandbox/stackblits.

Hi @markostanimirovic . This case is very curious. I'm not a maintainer either, but I'd say it works as intended.
You emit values from the subscription handler, which leads to this behavior and this is rather a bad design, that a problem in RxJS.
After some debugging I found out the following behavior:

you emit value from updateSelectedPageSize method
this causes selectedPageSize$ observable to emit as well (there are 6 observers listening to the store BehaviorSubject and selectedPageSize$ is the first of them, so it's being called as the first)
this causes patchState to be called and emit another value (so now we are in the nested handling cycle)
all 6 observers are being notified about this change
the nested cycle finishes and other 5 observers of the first change are being notified

That's why you first get loading: true and right after it loading: false, although the actual value in the store is still true.
As another workaround you could call the nested patchState asyncronously, like this
this.selectedPageSize$
      .pipe(
        tap(() => **setTimeout**(() => this.patchState({loading: true}), 0)),
        switchMap(pageSize => this.todosService.getTodos(pageSize)),
      )
      .subscribe(todos => this.patchState({todos, loading: false}));

I'll close as above answered adequately. RxJS currently does not guarantees synchronous reentrant and caller should take care of escaping it explicitly.

I'll close as above answered adequately. RxJS currently does not guarantees synchronous reentrant and caller should take care of escaping it explicitly.


feat(DDIDS-1152, DDIDS-1213): Table component number column styling

TIcket
https://goa-dio.atlassian.net/browse/DDIDS-1152
https://goa-dio.atlassian.net/browse/DDIDS-1213
Changes

Added a new package to support the use of :global with svelte custom components. Details

[x] Will update the storybook docs once https://github.com/GovAlta/ui-components/pull/1025/ is merged

The height of the row is increased after adding class "goa-table-number-column" to a td cell (Refer to the second row in the below example).

:tada: This PR is included in version 4.0.0-alpha.113 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.153 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-alpha.12 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.21 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


how to render a planar coordinate FlatGeobuf data?

I have stored some planar coordinate data using FlatGeobuf, which can be understood as CAD data. Can it be rendering by OpenLayers? I understand that GIS tools like OpenLayers require coordinate information.
From what I understand, to display planar coordinates using OpenLayers, the coordinates need to be converted to the UTM coordinate system first. However, my data is just regular planar coordinates and cannot be converted. Is it any way to show the planar coordinate geometry.

You can initialize the ol/View with a custom ol/proj/Projection, you don't have to convert the coordinates.
An ol/layer/Vector then will display your features without a transform.
import Map from "ol/Map.js";
import VectorLayer from "ol/layer/Vector.js";
import VectorSource from "ol/source/Vector.js";
import View from "ol/View.js";
import { Projection } from "ol/proj.js";

const projection = new Projection({
  code: "your-custom-cad",
  units: "m",
  extent: [-1000, -1000, 1000, 1000],
});

const source = new VectorSource({
  features: [/* your features here */],
})

new Map({
  view: new View({
    projection: projection,
    extent: projection.getExtent(),
    multiWorld: false,
    center: [0, 0],
    resolution: 1,
  }),
  layers: [
    new VectorLayer({
      source: source,
    })
  ],
  // ...
})

i will try it later, thanks very much.


Question about the usage of the renderer

Hi @kyle-mccarthy! Thanks for sharing this module.
I have a use case where I don't want to descriminate the pages in the controller that uses the renderer. I want it to be a catch all.
At first sight, it seems as everything was ok, but then I noticed that the assets were not being served.
A little investigation led me to learn that next's render method is only suited for pages although it also serves assets if they are from _next or from static folder.
With the advent of the public folder this behaviour broke because the render method does not cater to it.
I am left with two solutions.

Enumerate all possible routes in the controller and let the filter catch the rest
Use the RenderService's getRequestHandler which is an all purpose method.

I'm going with the latter which brings me to the question. Why not use it always and avoid the filter?

Hey thanks for checking it out. I don't exactly have a solution for you but can give you some more info and potential problems you may encounter.
So how the package currently works is that nest is responsible for the http server and initially handles the incoming request and performs all the routing. If the request doesn't have a route then nest throws an NotFoundException. That is where the RenderFilter comes into play because next's internal urls like /_next/* or /_static/* don't have a matching route as far as nest is concerned but they do with next so the request is forwarded on to next. If the request doesn't match an internal next url then there is some processing done on the error to remove anything that can't be serialized and then calls next's error handler and then nest is done with that request. So some sort of filter is needed so next can get the requests for it's internal assets.
One possible solution I can think of is in the filter have it call next's request handler for any error that has a status of 404 or is an instance of NotFoundException. However, this will break any 404s that you intentionally throw. So if you have an api route like /user/5 and there isn't a user with id 5 and want to throw a 404 via nest, it would still go onto be handled by next.
One other possibility wouldn't involve the nest-next package but could still work. Instead of having nest be responsible for the routing/initial entry point, you could reverse it have next handle it and then use nest's standalone application to access nest's infrastructure. Then you could use next's built in api routing and the newly added getServerSideProps function and get an instance of your nest app.
The second idea could be interesting since you wouldn't have to do a custom server, but you would lose out on things that best automatically handles for you, specifically as far as the routing goes.

Thank you for your explanation on the inner workings of the module.
As for the proposed solutions, I am actually keener on the first. My reasoning is that:

I prefer nest on the front and next as a catchall
the 404 handled by next makes sense to me even if an API route is called. My use case is not of a pure API server. I have an app which has an API for app consumption. The format of the 404 response is not relevant.

But the solution I currenlty have is, on a nest catch all controller to handle the response by relaying it to the the module's render service getRequestHandler.
This covers all my needs as the catch all is added as the last route. As such, all routes I need to declare are fully functional, all else is handled by next.
I actually think that you could have this as a rule for all response handling in the module and remove app.render as it is too specific for pages. the requestHandler handles all cases.
This would remove the need for the filter. Users of the module would not need to use the render method of the response and just return the result of the handler. It deviates from nest's structure of MVC but still adheres to the concept.
In any case, it is just a use case and the solution works for me. Maybe it would work for others.
Thanks for the awesome work!


generate csv: support manifests/ format with --make-manifests

Description of the change: generate csv --make-manifests will generate a manifests/ directory at <deploy-dir>/olm-catalog/<operator-name/manifests or, if --output-dir is set, <output-dir>/manifests. Previous behavior is the same, except setting --output-dir will direct the generator to check if a CSV bundle exists in the output directory before checking the default <deploy-dir>/olm-catalog/<operator-name> directory.
hack/tests: add generate csv subcommand tests that check behavior and not content of generated files (this is done in unit tests)
Motivation for the change: The new manifests/metadata format is supported by operator-sdk bundle create. generate csv should align in a backwards-compatible way so operator authors can choose between versioning their bundles on disk vs. in VCS. Explicitly setting --make-manifests accomplishes this. The only change to previous behavior ensures you do not have to maintain both a default bundle location and an output directory.
Relates to #2746
/kind feature

What do you think about aggregating generating the CSV with generating the
bundle? Both are really only useful when they appear together.
On Fri 3. Apr 2020 at 22:30, Eric Stroczynski<EMAIL_ADDRESS>wrote:

@estroz commented on this pull request.
In internal/generate/olm-catalog/csv_go_test.go
https://github.com/operator-framework/operator-sdk/pull/2776#discussion_r403310419
:

@@ -16,16 +16,14 @@ package olmcatalog

Most changes to this file are cosmetic except for setting
bundleGenerator.noUpdate, which prevents the generator from reading a CSV
to update from so we can check a newly-generated CSV against the expected
CSV in testdata.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/operator-framework/operator-sdk/pull/2776#pullrequestreview-387560437,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADAT2NP7EFM6JBBFJB57KX3RKZBNJANCNFSM4L4KJEWA
.

--
Daniel Messer
He / Him / His
Product Manager OpenShift
Red Hat GmbH https://www.redhat.com/
Wankelstrasse 5
70563 Stuttgart
<EMAIL_ADDRESS>https://red.ht/sig

@dmesser totally possible and is amenable to a followup. That's effectively the same as:
$ operator-sdk generate csv --csv-version 0.1.0 --make-manifests \
	--output-dir /tmp/foo
$ operator-sdk bundle create quay.io/example/memcached-operator:v0.1.0 \
	--directory /tmp/foo/manifests
$ rm -rf /tmp/foo

If we can eventually persist all UI-centric information to disk, ex. in a config file + doc.go files, CSV generation can be completely in-memory.

@estroz For the sake of simplicity, could we not imagine bundle create being capable of doing both in one step? e.g.
operator-sdk bundle create --version 0.1.0
which creates the bundle layout, annotaitons and CSV metadata on disk (in a default directory or specified by --directory). Followed-up by a:
operator-sdk bundle build quay.io/example/memcached-operator:v0.1.0
which is equivalent to
podman build -f bundle/Dockerfile bundle/
to support pipelines without daemons.

For the sake of simplicity, could we not imagine bundle create being capable of doing both in one step?

We've been own that road with operator-sdk build (see #1600). Makefile is a great way to solve this. For example:
BUNDLE_IMAGE="quay.io/example/test-operator-bundle"
OPERATOR_VERSION="v0.1.0"

.PHONY: csv bundle-image bundle-push scorecard

csv: manifests # manifests target generates CRDs, roles, etc.
	operator-sdk generate csv --version=${OPERATOR_VERSION} --make-manifests

bundle-image: csv
	operator-sdk bundle create ${BUNDLE_IMAGE}:${OPERATOR_VERSION} \
		--directory ./deploy/olm-catalog/test-operator

bundle-push: bundle-image
	docker push ${BUNDLE_IMAGE}:${OPERATOR_VERSION}

scorecard: bundle-image
	operator-sdk scorecard --bundle=${BUNDLE_IMAGE}:${OPERATOR_VERSION}

Run make bundle-push and you're done :)
We would theoretically be able to inject extra targets into the Makefile generation of operator-sdk init to give users the "best practice" make targets for OLM integration, but then users could tweak to their heart's content without us having to support every conceivable tweak to the workflow.
I think this would also help us focus more on the UX of the individual commands, which would ideally be simple on their own AND be able to be composed into really powerful workflows.


fix bug when remove images

Reference Issues/PRs
None
What does this implement/fix? Explain your changes.

There is no image_id attribute for dep, which type is string and it's the image id. So removing this will eliminate the bug
Any other comments?
🧡 Thanks for contributing!

Thanks so much for the catch @yitianlian and @klieret for the approval! Just merged.


Allow host search by UUID

When searching hosts, querying the fleet using hostnames and/or IPs may lead to inconsistent results since these can easily vary in time. On the other hand, UUIDs should be a much more "static" way to identify a device.
This change implements search by UUID for the MySQL and in memory datastores.
Side question: I'm not a MySQL performance expert, but is there a reason for using subqueries to search in the hosts tables (since we are querying results from the same table)? Directly having the condition in the top level WHERE clause feels more efficient to me.

 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.

I just realized I need to update the MySQL schema, working on it (weirdly make test succeeded locally).

Please ping when you have updated this and are ready for review :)

Hi @zwass, I already did in 3a30930, it's ready to be reviewed,sorry for forgetting to comment.


My texture is not loading

Hi @pepcots ,
I was trying to implement my Component Pattern and during this I don't know why the textures are not loading anymore. Even if I try to use the same functions before implementing the Component Pattern it doesnt print my texture. I don't know why is this happening, when I debug my code it says that the texture exists and is entering the texture.bind() but the texture does not appear. Why is this happening?
Thanks
https://github.com/CITM-UPC/Badass-Engine/blob/c41fca0aa856619742e98094082fc183274691f9/Maker/Engine/GameObject.cpp#L16-L36

Hello! I've seen it is working now?


Add extra compile flags for building on ARM

fixed my issue with raspberry pi

flags from seal's android example
https://github.com/microsoft/SEAL/blob/main/android/app/build.gradle

Did you test Pyfhel with it? (installing Pyfhel on ARM and running test.py)

@andrew-ma I created a new pull request (#72 ) starting from yours updating the dockerfile in order to install tools that said are necessary in you test repository. But it still doesn't work for me, can you give a look at this?


Fix to nn.Parameter arguments in 01_pytorch_workflow.ipynb

The requires_grad parameter of nn.Parameter is being discussed in the video, but in the notebook it is the requires_grad parameter of the tensor that is being set.

Thank you very much!


Calling ServiceError#message raises undefined method error

I'm getting an error when I try to access the message method on any error. I believe it's due to the conditional:
if @response.present?
Error:
undefined method `present?' for #<HTTParty::Response:0x00abcdefgh>

Fixed by #198


AWS Access management workshop: finding which permissions apply to each account

Describe the issue
Currently there are at least three levels of policies that apply to the workload account

AWS General policies/ AWS. SEA (https://github.com/aws-samples/aws-secure-environment-accelerator/blob/main/reference-artifacts/SCPs/ASEA-Guardrails-Part0-CoreOUs.json)
GoC policies (https://github.com/cds-snc/check_guardrails. ?)
BCGov policies (https://github.com/bcgov/cloud-guardrails. ?)

I have found references to the Service Control Policies, but I can not access them from my workload account and I do know  how they relate to the Guardrails
These policies are grouped into roles, and one or more roles are assigned to the workload accounts.
In addition, some policies apply to resources, others to users...( see document https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html)
We also have roles https://us-east-1.console.aws.amazon.com/iamv2/home#/roles (filter by BCGoc)that have policies associated to them, however, these policies are not the same than the ones Warren indicated in a text message. For example, the Viewer role has the following policy associated arn:aws:iam::aws:policy/job-function/ViewOnlyAccess but the Viewer role has this other policy https://us-east-1.console.aws.amazon.com/iam/home#/policies/arn:aws:iam::aws:policy/job-function/ViewOnlyAccess$jsonEditor and I do not know if both. policies. apply, if they are. complementary. or. how they relate to each other
In this context, I would suggest a workshop (by Warren? Bruce? Julian:....) to make sense of what a workload account is allowed/denied. This will allow to create a baseline of permissions that can be used as a reference after the SEA has been updated/upgraded/modified.
Additional context
Using my workload account BCGOV_WORKLOAD_admin_umafubc9/crochcun@idir I tried to use the following AWS CLI command

$ aws list-policies-for-target --target-id<PHONE_NUMBER>12

But it does not work as expected (even after adding a filter like  --filter SERVICE_CONTROL_POLICY)
I also tried the   list-user-policies flag , but I require the user name for the account, and I am unable to get the user name.
Using the above account, I can not start a CloudShell session, the error is

Unable to start the environment. You don't have required permissions. Ask your IAM administrator for access to AWS CloudShell. System error: User: arn:aws:sts::534823255669:assumed-role/BCGOV_WORKLOAD_admin_umafubc9/crochcun@idir is not authorized to perform: cloudshell:CreateEnvironment on resource: arn:aws:cloudshell:us-west-2:534823255669:* with an explicit deny

However, in IAM>policies I can find policy AWSCloudShellFullAccess(https://us-east-1.console.aws.amazon.com/iam/home#/policies/arn:aws:iam::aws:policy/AWSCloudShellFullAccess$jsonEditor)
that seems to suggest the account can start a CloudShell session
Definition of done
The goal of this workshop is to be able to list the policies that are associated to each account so that it is possible to have a clear idea of what the account is able or unable to do.
Another goal is to clarify the language by defining the exact meaning of Guardrails.

Another area I would like to cover is to deconstruct the following terraform script
https://github.com/BCDevOps/terraform-aws-keycloak-lz-sso-setup/blob/a185c0cfca1299ddc5ada1551767a5291002a0f7/main.tf
I would like to know

What exactly does
Where the policies it creates (sid) are then stored in the accounts.

Superseded by tickets #1702 and #1765, so closing it.


Support for non-primitiveish types in custom binders

Currently the auto-generated binders only work for "simple" properties (non-arrays and non-generics). Easiest to do and having the biggest impact would be String[] and List|Collection<String> (e.g. so you can bind DataSourceProperties in PetClinic).

Support for collections and arrays of String added in ca5121e


sqlitestudio: 3.4.5 -> 3.4.6

v3.4.6 contains bugfixes only.
Diff: https://github.com/pawelsalawa/sqlitestudio/compare/3.4.5...3.4.6
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 359730

x86_64-linux

:white_check_mark: 1 package built:

sqlitestudio


Retain synchronicity of resolvers

Introspection queries should always resolve synchronously, and this wrapper causes them to be async. This causes problems when used in conjunction with Apollo.
This is a proposed fix, not actually tested. I used something similar for my wrappers.

I really want to use this, can you package an npm version so I can better try this out?

With that fix I managed to get it to work, however on startup this is spammed into the console
Cannot read property 'then' of undefined: 970516bc-4254-4f9f-8452-753291397f90
Cannot read property 'then' of undefined: 16901f6d-3ef8-450c-a7a7-b948c750b583
Cannot read property 'then' of undefined: 0d1e478f-4277-4120-b66c-4f049af07e11
Cannot read property 'then' of undefined: 478aaff1-5c17-4db9-ac61-a8fd6c401eb6
Cannot read property 'then' of undefined: 98a318d8-ac25-4f60-b039-931ddb7c6d2a
Cannot read property 'then' of undefined: 0b9e549a-d3e5-4b1c-9b76-12624591cf44
Cannot read property 'then' of undefined: 8e1f5bb5-ac2a-4c44-84b7-9df2b9f72993
Cannot read property 'then' of undefined: 47d66cf4-63c0-4500-9692-166a2b880135
Cannot read property 'then' of undefined: c595ffe6-beee-44a3-b24e-87d0f9721bef
Cannot read property 'then' of undefined: 1d84d871-f746-4c84-8afe-f2f8b1ebae39
Cannot read property 'then' of undefined: 917dbf91-e4cf-4bad-9d14-325828b1f74b
Cannot read property 'then' of undefined: 0fc46380-2a7a-4600-bb68-81511a246dba

@LennyPenny 	should be fixed now

I will try this out tomorrow and report back, had to also do some other adjustments on my local fork but they might not really matter.
@arunoda get ready to merge ;)

Hi, when do you spect to have this merge and publish? I'm having this issue because I'm using graphql in conjunction with apollo.
Thanks


Bug: After link input the formatting is lost

Hello everyone,
there is a formatting bug that happens when a link is added. This bug already exists in the Lexical-playground.

does anyone have a solution?

Hey! I have been able to replicate this. And working on a solution! Cheers!

Hi guys, I have modified the setting element format structure in this PR. Basically, when a link is formatted the format is added to the parent paragraph node instead of the link node. This is the generic functionality in all of the format setting.
So I have added a check for the link node, and if it is a link node a matching parent is picked and the format is applied. This fixes the issue that is being displayed above.
Would love a review on this.
Regards
Tahir
https://github.com/facebook/lexical/assets/20771570/bfaf7122-ca42-4b06-aa69-5720db238d03

Thank you, Sir!


Add swap table

The table definition
CREATE TABLE spacebox.swap
(
    `timestamp` DateTime,
    `height` Int64,
    `batch_index` UInt32,
    `pool_id` UInt32,
    `swap_requester` String,
    `offer_coin_denom` String,
    `offer_coin_amount` Float64,
    `demand_coin_denom` String,
    `exchanged_demand_coin_amount` Float64,
    `transacted_coin_amount` Float64,
    `remaining_offer_coin_amount` Float64,
    `offer_coin_fee_amount` Float64,
    `order_expiry_height` Int64,
    `exchanged_coin_fee_amount` Float64,
    `order_price` Float64,
    `swap_price` Float64,
    `success` Bool
)
ENGINE = MergeTree
ORDER BY (
 timestamp,
 height,
 pool_id,
 swap_requester,
 offer_coin_denom,
 demand_coin_denom
)
SETTINGS index_granularity = 8192;

can be found in the end_block_events

at raw_block_results

inside end_block_events, the event type is swap_transacted
the rpc example is /block_results?height=13509655

try switch warp dex api to this API


Why nested query works but not nested mutations ?!

For example nested objects like the following does appear in query schema

But not appearing in create or update mutation schema like the following

The lib maps directly to the underlying sqlalchemy schema.
When mutating an object, if you updated fields on the related tables, you would be updating data on a table/instance different from the method used to mutate data.
when selecting, the relationships are provided since the links are already available and you are not mutating any data.

Can this be supported ?

It cannot be supported in any stable way because editing other related objects would break the proper scoping of your call.
if you are mutating "X" object, it would not be okay to have access to also edit "Y" structures (that might be linked to other objects).


fix: update gateway only when all teams are ready to fight

Right now the gateway is updated just after the user set the desired movement for a single robot, that makes the robot moves even when the 'fight' button havent been pressed.
The rules of the game said that the robot should move only when all the teams are ready to fight.
To accomplish that rule, the notification to the gateway have been removed when the user set the desired movement for a robot and insteand do it when all the teams are ready to fight
Co-authored-by: Kaja Koren<EMAIL_ADDRESS>

This solution may change based on this answer here https://github.com/NordicPlayground/robot-war-app/issues/53#issuecomment-1219415631
cc: @Semikaja

This removes the opportunity for clients to react on changes. Imagine a second admin view that visualizes the changes made by the admin.
It's the responsibility of the persistence layer to decide when to update the underlying store. That part needs to be changed.

What we did notice was that the teams couldn't react to the changes, because the data got sent after all robots were moved on the application (game page, not admin). So the fight button wasn't working as intended, it really had no function at all.
Me and Mauro are also a bit confused with what you tried to explain in the above comment. I This isn't changes made in admin, but when the teams are moving the robots.


[Feature] Allow configuring the window's appearance

It would be nice if the user could change some simple things about the window, e.g.

the window border style
the window highlights etc.

For example, in my case I change the border of all floating windows by all plugins to match my desired custom window border and tweak the highlights to match, but currently this isn't possible.
Also, as you can see in the screengrab the signcolumn is coloured which is probably because I highlight the background of diagnostic signs but not the sign column itself, but the highlights are probably taken from the signs themselves

For example, in my case I change the border of all floating windows by all plugins to match my desired custom window border and tweak the highlights to match, but currently this isn't possible.
For now you can work around this by defining a highlight named CodewindowBorder before you open the minimap (so probably before setup).

but the highlights are probably taken from the signs themselves
Indeed, they are just DiagnosticSignWarn and DiagnosticSignError. I'll probably put in highlight groups that by default link to these two, but can be overwritten.

Sounds great @gorbit99, tbh I meant the highlight specifically, but both are good since generally I change the border of all my floating windows to a custom style and since it's not currently possible to do this at the vim level it's good to have the option in a plugin

Added in https://github.com/gorbit99/codewindow.nvim/commit/b412f022df7282ef91d922385c62c58bb9b03d0e
You can change the highlights by defining the highlight groups CodewindowBackground, CodewindowBorder, CodewindowWarn and CodewindowError, and you can change the border style with the window_border config option

@gorbit99 I just tested this out and I don't think it works for the code window border because that highlight is used for VertSplit in the winhighlight not for the FloatBorder. I think VertSplit should be changed to FloatBorder since atm the CodewindowBorder highlight does not affect the border highlight

Ah, actually, I did test it and it worked, but it's probably because FloatBorder (in my case) is linked to VertSplit. I'll change it to that in a sec.

Awesome that works great now 👍🏿

👋🏻 Sorry I wasn't able to follow along that well, but I didn't want to open a separate issue just in case my issue was related.
In the below screenshot you can see that some dots have highlights (at the top some are green, a little bit below that there are some orange and blue dots) and I'm not sure why?

In other files this can be a bit more distracting...

Now at first, I thought maybe the dots were being coloured somehow in relation to the code syntax highlighting but now I think this actually has something to do with highlight groups (as I'm guessing the dots are using some kind of diagnostic 'sign' symbol maybe).
Is this the case? How can I get rid of these additional colours if they are indeed meaningless in relation to what minimap is displaying (don't want to break any diagnostic stuff that my current buffer's LSP might be using for example).
Thanks!

@Integralist Please open a new issue, it's better to close that in case it is related, than dealing with separate issues in the same bugreport


[MM-20599] Removed state variable from action creator functions

Summary
Avoid passing global state into actions
Ticket Link
https://mattermost.atlassian.net/browse/MM-22995

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich

/update-branch

@marianunez and @devinbinnie kind remind to help with reviews :)

Removing my review request why still WIP. Feel free to request review when ready 👍

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook

Hi @diode, can you clarify if this PR is still a work in progress, or ready for review?


Log exceptions with logger.exception

Addresses #41

Coverage remained the same at 90.164% when pulling dca675320761a7ab351687eba4290d1105a17af1 on bokchan:iss41-use-logging-exception into 3c0c32758dcf2162f71588e8023e71b6cc46c7c1 on GDay:master.


Code needs housekeeping and refactoring.

Description
Currently main.py is riddled with various commands and their implementation. The code also seem to be very repetitive with a lot of recurring if else statements. I think a better approach would be to move all the commands and their respective implementations to lets say a structured directory like roBOT/core/commands/ and subsequently import the commands and their functionalities in the main.py file. Overall this would make it a lot easier for contributors as well as maintainers to keep track of all the current commands and potentially the newer ones which have been planned for the future.

much needed!


Switch to Renovate

Fix #1316
Based on https://docs.renovatebot.com/upgrade-best-practices/ and the go-contrib configuration: https://github.com/open-telemetry/opentelemetry-go-contrib/blob/91a1588d44a691c9568f88a2d9a8efb0158663b7/renovate.json
This requires enablement via the OpenTelemetry org once this is merged.

Follow up: Based on the new tracking issue, it looks like this was configured correctly to handle Docker and GitHub actions:

No need to update the config :tada:


encoded_inputs["attention_mask"] = encoded_inputs["attention_mask"] + [0] * difference OverflowError: cannot fit 'int' into an index-sized integer

re-download models, OK!

re-download models, OK!

So, the problem is the project huggingface?


Software Plurals?

So, last week (commit 1f1d89cf5c5670206469c764c058e6d3e525225) I changed some terms in Drasil\Concepts\Software so that they were singular instead of plural.  However, I could not find any changes to the resulting output after I did so and could only find references to the items in functions labeled makeImpModule in the Module.hs files in GlassBR, HGHC and SWHS.  To this end, I was wondering what the makeImpModule actually pulls from the terms and what modifications (if any) need to be made to accommodate for the pluralization.

This is basically because the stuff related to modules has not have had their keywords pulled out.  And quite a bit of this will need some fixing.  It's not really a design issue.  You are quite right to point this out though.

Non issue?

Ironically, we just found what this did.  Apparently the makeImpModule function pulls out the term (e.g. input parameter) to use as a title.  There are a number of items in the logs (which are now easier to see now that so many lines have been cleared) that directly relate to this change.  To this end, is it more correct to leave the term itself as a singular and adjust the makeImpModule function to pluralize said terms or leave the terms as plural and simply view them as names to a singular entity?

Leave the term as singular, definitely.  Yes, adjust makeImpModule, but don't fuss about it too much, as that is likely to change very soon.

I'm assuming this issue is closed now (especially with the code gen changes that have been made), unless anyone says otherwise.

This issue is still not fixed.

Wait, my mistake, misread the log. Looks like someone fixed this issue (I hope?).


Why does horizontal form have padding-left?

This is the most annoying thing in bootstrap. Why does it not align with the left side?
If we have the following:

Foo

<form class="form-horizontal">

  Title

     <input type="text" name="title" class="form-control" />

</form>

I want the "T" of "Title" to align with the "F" from "Foo". I'm very surprised this is not the default behavior.

The labels are right-aligned by designed. Override if you need to with text-align: left;.


must provide way to configure format and fail condition for eslint

currently this is hardcoded and cannot be configured, that severely reducing usefulness.

can you please expand on this, it's not quite clear what feature / bug is trying to be reported.  Are you speaking to the ability to configure the linting rules, that are provided by default with this pipeline in the bundled eslintrc?  if so, it is (intended to be) configurable.
https://github.com/kenzanlabs/pipeline-validate-js/#usage
Please let me know if this helps address your issue.

stream = lazypipe()         .pipe(eslint.format)         .pipe(eslint, config)         .pipe(eslint.failOnError);
this is what is done to configure gulp-eslint, basically hardcoded.
according to gulp-eslint,

format can be: https://github.com/adametry/gulp-eslint#eslintformatformatter-output
fail can be: https://github.com/adametry/gulp-eslint#eslintfailonerror

@paul-barry-kenzan
Something you can look into?

@obuckley-kenzan
Will look into today.


Few suggestions (Pythonic style, display and exception)

if is_true(father): to replace it with if father: or if father.empty: like Pandas DataFrame .empty

format_name(father >= "NAME") to father.name()

Can we function that computes the level against one person (default):

-1 (children's)...
0 (same level, siblings, cousins), 1 (parent, uncle, aunt, etc.)
2 (grand-parents)
if possible relationship tag (father, mother, uncle, cousin, 2nd cousin, 3rd cousin removed...)

Display as graph of the family tree

When I call get_stepsiblings I get this error:

    106 def get_stepsiblings(self, indi: IndiRef) -> list[IndiRef]:
--> 107 	parent_family = self.get_parent_family(self.document.level0_index[indi])
    108 	father, mother = self.get_parents(indi)
    109 	unions: list[TrueLine] = []

TypeError: unhashable type: 'TrueLine'

I can't tell you how happy I am to see someone using something I've programmed and with whom I can interact, thank you!

if is_true(father): to replace it with if father: or if father.empty: like Pandas DataFrame .empty

I like the idea. And I even know how to implement it. Not sure about the named however. I prefer line.exist or line.exists as the payload can be empty. I assume that also mean that I can remove is_true (an acceptable backward compatibility rumpture I hope).

format_name(father >= "NAME") to father.name()

This would be handy for sure, but I don't see a convenient implementation for it.
My proposal would be to make a class derived from TrueLine (or Record, they are the same) named IndiRecord which would have a name() or get_name() method. As the code is procedural rather than object-oriented, I am not sure I would want that. Nevertheless, I am open to other implementation ideas and I will keep track of features that would encourage such a change.

Can we function that computes the level against one person (default):

-1 (children's)...
0 (same level, siblings, cousins),
1 (parent, uncle, aunt, etc.)
2 (grand-parents)

if possible relationship tag (father, mother, uncle, cousin, 2nd cousin, 3rd cousin removed...)

A general function to do various request. Why not! However I don't understand how your "relationship tag" works.
The way I see it is as follow:
def get_relatives(indi: IndiRef, ascending_degree: int = 0, horizontal_degree: int = 0) -> list[Record]: ...

get_relatives(person, 1) -> parents
get_relatives(person, 2) -> grandparents
get_relatives(person, -1) -> children

get_relatives(person, 0, 0) -> siblings (and stepsiblings)
get_relatives(person, 0, 1) -> cousins
get_relatives(person, 0, 2) -> second cousins (cousins with a degree of two)

get_relatives(person, 1, 1) -> siblings of the parents (i.e. oncles and aunts)
get_relatives(person, 2, 1) -> siblings of the grandparents
get_relatives(person, 1, 2) -> cousins of the parents

get_relatives(person, -1, 1) -> cousins of the children (i.e. niece or nephew)
get_relatives(person, -2, 1) -> cousins of the grandchildren
get_relatives(person, -1, 2) -> second cousins of the children

I am not familiar with the notion of degree. My reference: https://en.wikipedia.org/wiki/Cousin
I may learn it in the hope that getting people of the 3rd degree can be easily be done using that function. I am a bit afraid of the implementation of it. I will see.
I don't rate this function as a high priority.  I am not aware of any major applications.

Display as graph of the family tree

This is a visualization issue. The library is intended to remain focused on the manipulation of gedcom data.
You don't explain what kind of graph. If it doesn't require much third-party library, if any, we could put it as an example.

When I call get_stepsiblings I get this error:

The function take an IndiRef like "@I1@" as the other methods of FamilyAid.  Still not sure on the name! lol
According to the error message, you passed the TrueLine of the person (or Record, they are the same). You will need to use the payload or the tag of the line, whichever the one holds the reference of the person.
family_aid = FamilyAid(document)
me = document["@I1@"]
my_father, my_mother = family_aid.get_parents(me.tag)
my_uncles_and_aunts = family_aid.get_siblings(my_father.tag) + family_aid.get_siblings(my_mother.tag)
print([p >= "NAME" for p in my_uncles_and_aunts])

I intend to share some usage examples in the near future. Thanks again for your feedback!

if is_true(father): to replace it with if father: or if father.empty: like Pandas DataFrame .empty

I like the idea. And I even know how to implement it. Not sure about the named however. I prefer line.exist or line.exists as the payload can be empty. I assume that also mean that I can remove is_true (an acceptable backward compatibility rupture I hope).

Unfortunately, the Python type system doesn't support TypeGuard on self. See https://github.com/python/mypy/issues/14425. But I succeed to make it work with mypy (not with pyright unfortunately).
I let the is_true function as it is the intended way of doing the type check and I add my version of exists for what it is worth.
Note:  if line: ... and bool(line) were and will remain a correct way to do it when type-checking is disabled

I implemented the get_relatives() method we discussed. I also plan to implement a get_with_degree() method based on the definition of kinship degree found here https://heirbase.com/degrees_of_kinship_chart/.

Why haven't I thought of this before? To differentiate TrueLine and FakeLine, the boolean check is enough. With the proper overload of __bool__, it works with typecheckers. Same principle as for the previous exists attribute, but applied to the __bool__  method.


Add Spacetux - Unmanned Contracts from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of linuxgurugamer, to add Spacetux - Unmanned Contracts to CKAN.
Please direct questions about this pull request to linuxgurugamer.

Can this be resubmitted, the problem was fixed.

#rebuild

Deleted as per request of author on forums http://forum.kerbalspaceprogram.com/threads/100067-The-Comprehensive-Kerbal-Archive-Network-(CKAN)-Package-Manager-v1-6-5-6-Mar-2015?p=1794659&viewfull=1#post1794659


horrible documentation

specially the readme file. purely horrible. devs making docs for robots

This isn't actionable feedback. Maybe you could recommend rearranging a specific section or rewording a sentence.

Thanks @samuelrey.  @josersleal are you trolling?  I've spent a good amount of time working on the README.  I've got a bunch of changes coming hopefully later today.  I'm always happy to continue iterating and improving but feedback like this only upsets me.  I'll close this ticket for now and reopen if you actually provide useful feedback.


Fix even more line ending issues

Pulled in. Give the repos a while to sync.

Why is this commit now twice in the history, once with your sign-off, and once without?

I missed the sign-off on the first time and did an amend to add it.

Well, that's exactly my point. You did not amend your local commit in the sense of git commit --amend, but you created an alternative history and merged them.


Chapter 6, build_interface() is missing some defaults/good coding form practices

As per Title, in Chapter 6, the new local function build_interface() should set the enabled tag for the slider and textfield to the current player_global.controls_active, since otherwise the default might be changed, and the controls should be deactivated but are still enabled in the GUI by default.

Hi, appreciate the comment. That would indeed be better, I'll be sure to change it, thanks.

Fixed


spfx project add devcontainer

Usage
spfx project devcontainer add
Description
Adds the .devcontainer files for the current project
Options

Option
Description

Additional Info
This command would add the .devcontainer folder and the files needed to launch the project in a container. Currently, @hugoabernier has been adding these files manually to the PnP Samples repositories. We have tested webparts, but am not sure about other SPFx project types.
The command would install the files specific for the SPFx "version" and "componentType" in the yo-rc.json file.
I would love to have more conversations about this and help implement.

Thank you for reaching out @DonKirkham, I absolutely love this idea and can see the immediate benefit this could bring ❤
Do you have a sample that uses a dev container that we could use as a candidate for replicating using this command?
I think it makes sense to centralise the dev container files in there own repo, so we have a version for each SPFx version, we can then just reference these in the command code.
The process seems fairly straightforward however, unless I'm missing something.

Execute the command in an SPFx project
Identify the project version
Handle if project version is not compatible
Read central repository of dev container files for SPFx project version
Create files in the local repository

Great idea like you mentioned @garrytrinder! I'd however like to propose that we keep the devcontainer files inside CLI for Microsoft 365. If we maintain them separately then we could have discrepancy between the containers in the external repo and what's supported by the CLI. Having everything in one place would allow us to validate integrity of the command.
Also, I updated the spec to put the verb at the end and align the command with our naming convention.

@DonKirkham in the spec you mentioned:

The command would install the files specific for the SPFx "version" and "componentType" in the yo-rc.json file.

The devcontainer.json is the same for every SPFx solution, with the exception of the SPFx Docker container version that we are pointing to.
In our current implementation, we call a spfx-startup.sh after the container is built to load all dependencies. There are two versions; one for SPFx versions pre-1.12.1, one for SPFx 1.12.1 and later.
The spfx-startup.sh is also where we can make customizations for each solution.
As far as I'm concerned, in addition to the steps outlined above, we need to

detect if there is a .devcontainer folder
if there isn't one, look the version of SPFx in package.json and create the appropriate devcontainer.json and spfx-startup.sh

Other things to consider;

at some point, should think about adding parameters to support additional remote container types. or things like CodeSpaces vs Docker desktop
the upgrade command should add steps to upgrade the devcontainer.json if applicable.

All of the above are excellent suggestions.
As far as how to best get the version of SPFx, I defer to those that are more knowledgeable about how SPFx versions are tracked in a project. I always use package.json, since yo-rc.json make not have been updated. But I noticed that upgrade command always instructs that yo-rc.json be updated.
I love the idea that the spfx project upgrade command would have instructions to update the devcontainer files too.  Could we also add "spfx doctor" checks to see if the devcontainer files match the SPFx version?
RE @hugoabernier's comment about different container types. My experience so far is that Codespaces use the exact same container functionality as Docker desktop.  i.e.,, if you can open a project in a Docker container, you can also open that github repo straight into Codespaces. (If you watch how Codespaces are named, you will see it's the same as Docker. hmmmm
The big difference right now is that Codespaces uses the .devcontainer folder at the root of a repo only. It does not work for big monorepos, like our samples repos.  Docker, however, looks for the .devcontainer of the folder loaded in the project and offers the option to rebuild the container using that configuration. An enhancement had been submitted to the Codespaces team to allow this functionality.
Thanks for everyone's feedback and willingness to help.  As I originally mentioned, I would love to help with this implementation. I have not worked with the project before, so I will definitely need some guidance.

The spfx-startup.sh is also where we can make customizations for each solution.

@hugoabernier, could you tell us more what customizations we do and how we could spec if for this command?

at some point, should think about adding parameters to support additional remote container types. or things like CodeSpaces vs Docker desktop

Is there a difference between the two? I thought that Codespace is using the devcontainer and there's nothing specific to it. Is there more to Codespaces after all?

the spfx project upgrade command should add steps to upgrade the devcontainer.json if applicable.

Oh, that's a very good point! Could you please create a separate issue so that we won't lose track of it?

My experience so far is that Codespaces use the exact same container functionality as Docker desktop.

This is also my understanding from implementing the dev container for the CLI.
For “local” use you need to have Docker running and the Remote Container extension installed in VSCode, however this is provided for you in the Codepace.
The extension will detect the devcontainer file in the repo and prompt to build the container from the specified image, which can be either a remote or local Docker image and executes the container.

Very interesting idea this! I added an extra issue for a related type of command.

@martinlingstuyl what's the difference between spfx project devcontainer add and spfx project devcontainer init?

With add you would add the files to an existing SPFx project. With init you would start from scratch: initialize a new devcontainer in an empty folder with all required dependencies

What's the difference between adding devcontainer files to an existing SPFx project or an empty folder?

@martinlingstuyl I am also confused as to why there would be different containers. The container is specifically built for the version of SPFx, so it is set. Users always have the option to change the container in the .devcontainer configuration files after the initial creation, but not sure why you would do that. Only scenario I can come up with is if you upgrade the SPFx version in your project. And if you do that using the CLI for Microsoft 365 tool, I bet the guys who write that tool will have instructions on how to change the dev container.

I think I caused a bit of confusion when using the word 'container' @DonKirkham? 😇
What I mean to say is that we have two scenario's:

we have an existing project. And we want to add devcontainer files. What .devcontainer.json / dockerfile is needed should be decided by the CLI based on the existing files, right? That's the current issue that you raised.

we don't have an existing project but instead we have an empty folder and we want to start by adding a .devcontainer.json / dockerfile, so we can then start creating the SPFx project from within the devcontainer.

Let's phrase it as a question:
Should we cover both scenario's with one command, or is it better to have a second command for scenario 2?
E.g: spfx project devcontainer init --version 1.15 or something like that. It's obvious you would need more options for scenario 2 than for scenario 1.
I hope it's clear what I mean!

Ok, that clears it up. However, I don't think scenario 2 is a viable use case. Just my opinion. You should create the project first, then run the devcontainer add command. I guess I don't see the value of creating the project from withing the devcontainer. My understanding is that, currently, the devcontainers we are using are locked, so you would still need to install the project in your local file system. I may be wrong on that and @waldekmastykarz can answer better since we are "borrowing" the devcontainers he has been building for years.

If I need to create the project first, I still need to install the right versions of node and the yeoman SPFx generator (etc) on my source system. I generally don't do that.
I'm not sure how you use it, but I use the .devcontainer.json/Docker setup to separate my dependencies. And the yeoman generator is part of that, so when I start a new SPFx project, I always start from within a devcontainer that has all my required dependencies setup.
To take care of that in my organization, we have an Azure DevOps 'template'-repo with only the devcontainer/Docker files. We clone that first and then switch remotes to start building. (We usually have 1 SPFx project in 1 repository)
That's not ideal though. It would be easier if I could just run a CLI command to provision the files for me. The only thing I need to do then, is to open the folder in vs code Remote container.
Maybe it's good to note: I'm on a windows machine here, though I create the SPFx projects on wsl to speed up docker.

I think I caused a bit of confusion when using the word 'container' @DonKirkham? 😇
What I mean to say is that we have two scenario's:

we have an existing project. And we want to add devcontainer files. What .devcontainer.json / dockerfile is needed should be decided by the CLI based on the existing files, right? That's the current issue that you raised.
we don't have an existing project but instead we have an empty folder and we want to start by adding a .devcontainer.json / dockerfile, so we can then start creating the SPFx project from within the devcontainer.

Let's phrase it as a question: Should we cover both scenario's with one command, or is it better to have a second command for scenario 2? E.g: spfx project devcontainer init --version 1.15 or something like that. It's obvious you would need more options for scenario 2 than for scenario 1.
I hope it's clear what I mean!

What's the difference in the output between 1 and 2? In both cases you mention .devcontainer.json/dockerfile, so I'm not sure why we'd need two separate commands.

The output is the same, the input is different though.
But OK, I'll let it rest. In that case this command might need a few extra properties though.

Option
Description

-v, --version [version]
The version of SPFx to initialize a devcontainer for.

-g, --generator [generator]
The SPFx generator to use to initialize a devcontainer with. Allowed values: Official, PnP.

Understood. In that case having one command with options would be clearer indeed. I'd suggest we spell official (all lowercase)

Shall we consolidate #3098 and #3460?


[Doc] Add Android documentation on how to compile and load models

📚 Documentation
As part of https://github.com/mlc-ai/mlc-llm/pull/1248#issuecomment-1811622752, I was looking to see which parts of the documentation needing updates but now noticing we don't have any concrete docs on how to compile models and deploy them on an Android application. Creating this issue to track the addition of this documentation.

Hi @tobrun, thanks for the suggestion! The Android flow and documentation was updated quite a lot recently via https://github.com/mlc-ai/mlc-llm/pull/1494.
Closing this issue for now; but definitely feel free to open another one!!


Please add powerStaking to testnet genesis validators

Maybe third time's a charm..

first pr https://github.com/anoma/namada-testnets/pull/684

second pr https://github.com/anoma/namada-testnets/pull/895


Remove Migrated from

Feature Description

Source: Benjamin_Loison/PRNU_extraction_private/issues/35#issue-1474
I woult like initial simpler:

Source: Benjamin_Loison/PRNU_extraction/issues/35#issue-820320
Screenshots
No response

Related to Benjamin_Loison/codeberg/issues/3.


Don't run unnecessary tasks by default

The gradle build runs a few unnecessary tasks by default:

javadoc
shadowjar

These take a long time so should only be run on request.

Perhaps already on your mind, but in addition, publishToMavenLocal probably shouldn't publish the shadowJar. We call out publishToMavenLocal in our guide and I think most users won't need the shadow JAR, so we don't want them to pay the cost for those tasks by default.

Fixed in
https://github.com/googleads/google-ads-java/pull/474
https://github.com/googleads/google-ads-java/pull/475


Possible to select multiple Dates

Hey there,
thank you very much for your library!!
I was just wondering if it's possible to select multiple dates?
Thank you

not at this point, no

@abrajoe: Thanks for using CVCalendar! We'll provide such a feature in v2.0.0!

I want it urgently. Please help.

Any update on this multiple date selection?


chore(chore): add github stale bot

Added stale.yml file to configure stale options
GH-70
Description
Adding stale bot app and yml file to configure issue and PR stale
Issue - 3 months
PR - 2 months
Fixes #70
Type of change
Please delete options that are not relevant.

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

Checklist:

[x] Performed a self-review of my own code
[x] npm test passes on your machine
[ ] New tests added or existing tests modified to cover all changes
[ ] Code conforms with the style guide
[ ] API Documentation in code was updated
[ ] Any dependent changes have been merged and published in downstream modules

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


energy predictions | carnot

hey
energy_predictions.yaml
I had to change the code to match langauge (I use english)
but more importantly the data generator didn't fit:
  var data = entity.attributes.prognose.map((start, index) => {
    return [new Date(start["date"]).getTime(), entity.attributes.prognose[index]["value"]/1000];

I had to change the above to
  var data = entity.attributes.predictions.map((start, index) => {
    return [new Date(start["dktime"]).getTime(), entity.attributes.predictions[index]["prediction"]/1000];

because the rest-sensor returns dktime, utctime as the time placeholder and predition holds the price.
my rest sensor looks like this:
- platform: rest     resource: https://whale-app-dquqw.ondigitalocean.app/openapi/get_predict     name: elprognose_carnotdk     scan_interval: 3600     headers:       Accept: application/json       apikey: !secret carnotdk_token       username: !secret carnotdk_username     params:       daysahead: 7       energysource: spotprice       region: dk1     json_attributes:       - predictions     value_template: "{% if value_json is not none %}OK {{value_json.predictions[0].addedtime}}{% else %}Unavailable{% endif %}"

this is mostly a FYI :)

this is mostly a FYI :)

Thanks for the information @Symbiot78 :)
I actually use nodeRED to pull the data from the Carnot API and also use the "dktime" values. However, I change that to "date" in the data returned to align with data from other sources (e.g. Grønnere Elforbrug).
I also change the "prediction" field to "value" for the same reason.

Closed

Closed


Section 3 Test

test 3 links to test1 answer sheet.

Hey @pete-reis I am so sorry for the inconvenience, I dont have the tests for this one populated yet so everything in there is just placeholder now. I realized I didnt have the fact they arent ready yet marked clearly enough so I tried to put an extra statement clearly on each test to make sure people know.
That being said, I should have the tests ready within the hour so I will let you know. Sorry again for the inconvenience and thanks so much for your feedback!


[BEAM-6011] Docs: Add a paragraph about Nexmark Phrase triggering

@echauchot could you take a look (a quick one)?

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
 I was not aware of the nexmark wiki pages. Thanks!

Normal, it was a direct discussion with Kenn yesterday ;) not yet public


how we can enforce user to crop the image?

Platforms
Android, iOS
Description
how do we force users to crop the image in the aspectRatios which we have given to them?
cropRotateEditorConfigs: CropRotateEditorConfigs(
              initAspectRatio: dimension == ImageDimension.square ? 1 : 4 / 3,
              canChangeAspectRatio: false,
              aspectRatios: [
                dimension == ImageDimension.square ? squareRatio : postRatio,
              ],
            ),

Why
No response

hello @hm21
can you please take a look at this?
Thanks!

Do I understand you correctly that you want to open the normal editor with all the subeditors (like paint or filter editor), but you want to initialize the editor with the specific size?
If so, you have now two options:
Option 1 Easy
You open first the crop-rotate-editor as a standalone editor example and after your user crop the size he wants, you open the main-editor with all other editors, like the filter editor.
Option 2 Hard
You can set the transform configs manually when you open the editor. The complicated case here is that you need to calculate your image size, and it's scale factor, to fit it to the screen. Below is a small example.
callbacks: ProImageEditorCallbacks(
  mainEditorCallbacks: MainEditorCallbacks(
    onAfterViewInit: () {
      editorKey.currentState!.stateHistory.first.transformConfigs =
          TransformConfigs(
        /// Set the required scalefactor that it fit to the screen
        scaleUser: 1.2,

        /// Set the aspect ratio
        aspectRatio: 1,

        /// Set your crop size
        cropRect: Rect.fromLTWH(
          0,
          0,

          /// The crop size
          MediaQuery.of(context).size.width,
          MediaQuery.of(context).size.width,
        ),

        /// Ignore stuff below
        angle: 0,
        originalSize: Size.infinite,
        scaleRotation: 1,
        cropEditorScreenRatio: 0,
        flipX: false,
        flipY: false,
        offset: const Offset(0, 0),
      );
    },
  ),
),

Btw, I will move your question to the Discuss tab in the Q&A category because that tab is better for questions.


Add support for header parameters in service store

Summary
Add support for header parameters in service store.
Ref - https://swagger.io/docs/specification/describing-parameters/
Depends on - https://github.com/finos/legend-engine/pull/591

How did you test this change?

[X] Test(s) added
[ ] Manual testing (please provide screenshots/recordings)
[ ] No testing (please provide an explanation)

@hardikmaheshwari it's filing engine test, let's not merge till we get engine through

I converted this to draft as the corresponding engine's PR is in draft mode and not yet merged. Please feel free to switch back when engine change is in! Thanks!

I converted this to draft as the corresponding engine's PR is in draft mode and not yet merged. Please feel free to switch back when engine change is in! Thanks!

@akphi Engine changes were merged as part of another PR. Can you please review this?


Security exceptions when working with databrick unity catalog

What happens?
When working on cluster which are in shared mode on unity catalog, splink throws py security exceptions
To Reproduce

OS:
databricks
Splink version:
pip install splink==2.1.14
Have you tried this on the latest master branch?

[x] I agree

Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

[x] I agree

@aamir-rj I'm afraid we don't have access to databricks so can't really help out with these sorts of errors.  There are various discussions of similar issues that may (but may not) help:
https://github.com/moj-analytical-services/splink/discussions/2295
Thanks @fscholes!.   Incidentally, If you ever have chance to mention it to databricks, it'd be great if they could simply add a couple of (fairly simple) functions into DataBricks itself so the custom jar was no longer needed.   it causes people a lot of hassle due to these security issues. The full list of custom udfs is here:
https://github.com/moj-analytical-services/splink_scalaudfs
But probably jaro-winkler would be sufficient for the vast majority of users!

Are you aware Databricks has an ARC module, based on Splink?
https://www.databricks.com/blog/linking-unlinkables-simple-automated-scalable-data-linking-databricks-arc

Thanks for replies
I spoke to databricks and they asked to run on single user cluster which
works for fine.
Thanks
On Thu, 10 Oct 2024 at 11:18 AM fscholes @.***> wrote:

Incidentally enough, just yesterday I was talking to Databricks about
this, and it's because Splink uses custom jars that aren't supported on
shared mode/serverless clusters. They told me it is on the roadmap.
The current way around it, other than redeveloping Splink to remove the
custom jars, is to use a single-user cluster on Databricks
—
Reply to this email directly, view it on GitHub
https://github.com/moj-analytical-services/splink/issues/2459#issuecomment-2404257929,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2FVYNUKZ5DAFHGGRBPPVILZ2YS6BAVCNFSM6AAAAABPT5M3RKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBUGI2TOOJSHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Another possible way around this for anyone using splink >= 3.9.10 is an option to opt-out of registering the custom jars. In Splink 4 this looks like:
...
spark_api = SparkAPI(spark_session=spark, register_udfs_automatically=False)
linker = Linker(df, settings, db_api=spark_api)
...

See issue #1744 and option added in #1774.

I used the below option but always gets this error
nam alt is not defined.
Tried installing alt but still same issue
On Mon, 14 Oct 2024 at 1:05 PM ADBond @.***> wrote:

Another possible way around this for anyone using splink >= 3.9.10 is an
option to opt-out of registering the custom jars. In Splink 4 this looks
like:
...spark_api = SparkAPI(spark_session=spark, register_udfs_automatically=False)linker = Linker(df, settings, db_api=spark_api)
...
See issue #1744
https://github.com/moj-analytical-services/splink/issues/1744 and
option added in #1774
https://github.com/moj-analytical-services/splink/pull/1774.
—
Reply to this email directly, view it on GitHub
https://github.com/moj-analytical-services/splink/issues/2459#issuecomment-2410522648,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2FVYNSXAYMJKLKVMOFJNDLZ3OCPLAVCNFSM6AAAAABPT5M3RKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJQGUZDENRUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I used the below option but always gets this error nam alt is not defined. Tried installing alt but still same issue

From the image it looks like you are mixing Splink 2 (splink.Splink) and Splink 4 (splink.SparkAPI) code. The option register_udfs_automatically is only available in Splink 4 and later versions of Splink 3 - there is no equivalent in Splink 2.
If you are able to upgrade then I would recommend moving to Splink 4, as then all of the documentation will be applicable.
If you are not able to upgrade then you will need to stick to the single user cluster workaround.

Nope ,I used splink 4 only.
On Wed, 16 Oct 2024 at 2:22 PM ADBond @.***> wrote:

I used the below option but always gets this error nam alt is not defined.
Tried installing alt but still same issue image.png (view on web)
https://github.com/user-attachments/assets/d7f152da-9289-4592-b369-28b674816a02
From the image it looks like you are mixing Splink 2 (splink.Splink) and
Splink 4 (splink.SparkAPI) code. The option register_udfs_automatically
is only available in Splink 4 and later versions of Splink 3 - there is no
equivalent in Splink 2.
If you are able to upgrade then I would recommend moving to Splink 4, as
then all of the documentation
https://moj-analytical-services.github.io/splink/getting_started.html
will be applicable.
If you are not able to upgrade then you will need to stick to the single
user cluster workaround.
—
Reply to this email directly, view it on GitHub
https://github.com/moj-analytical-services/splink/issues/2459#issuecomment-2416375641,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2FVYNT5UQNFSMVPGBF4RTDZ3Y44RAVCNFSM6AAAAABPT5M3RKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJWGM3TKNRUGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

What I mean is that the code you appear to be running is not valid Splink 4 code - there is no longer an object Splink to import, nor a method get_scored_comparisons(). You will need to adjust your code to something like:
from splink import Linker, SparkAPI

...
spark_api = SparkAPI(spark_session=spark, register_udfs_automatically=False)
linker = Linker(df, settings, db_api=spark_api)

df_dedupe_result = linker.inference.predict()

As to your error, it appears that you do not have the requirement altair installed, which is why you get the error name 'alt' is not defined. If you install this dependency the error should go away.

@aamir-rj and anyone else who stumbles across this error, I've had the same problem with importing altair, the solution was to restart the python kernel after installing splink, like this:
%pip install splink

dbutils.library.restartPython()


Broken xref

The xrefs weren't generated correctly. Please look to see if I added the correct syntax because previews don't show docfx output.

Contributes to issue #3682


[DS-6483][MasterServer] upgrade the druid and mysql connector version

this pr close #6483

Purpose of the pull request

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Good job!

I will fix the missing Notice issue.