Expose hoverRenderer label background as setting

Feature request
Is your feature request related to a problem? Please describe.
I don't believe there is a way to change the background color of a label you hover, unless you override the drawHover hoverRenderer. Changing this color is necessary if you want to change the label text color to any lighter colors (to appear on a darker background).
Describe the solution you'd like
It would be helpful to expose the label background variable as a setting. It appears to be hardcoded in the default drawHover code to #FFF.
Describe alternatives you've considered
I'm currently just overriding the whole drawHover function to change this color. If there's a better method than adding a setting, would be happy to try.
Additional context
N/A

Hi @xShields,
Writing your own drawHover function is actually currently the idiomatic and expected way to solve that issue, and I think I want to keep it that way.
I think it's good that we keep the default label and hover renderers as light as we can, so that people understand how it works and want to overload them. Personally, I override them in almost every projects with sigma. Sometimes I want to remove the shadow to fit the rest of the page's style, sometimes I want to add subtitles (like in the website's demo), or even just write the label using two different colors.
I'm afraid that if we start adding new features in those default renderers, they will become harder to "fork", and people will want to add features in them even more.

Thank you for the fast response. I definitely see where you're coming from now, if that's actually intended as the solution. I'll just roll with that methodology as I keep testing features out.
The only question then I have left would be what the distinction is between drawLabel, which has the labelColor setting available, and drawHover. I suppose some of the confusion just comes as I learn more about the library, trying to infer things from the codebase itself and demos, so thank you for your patience with some of these types of questions.

@xShields both drawLabel and drawHover have access to settings and any node data as reduced. One thing that might help you is that the default drawHover actually uses drawLabel under the hood to display the hover label on top of the shadowed box.

I agree that having labelColor exposed might make people want more, but I think it's not that much of an issue at the moment - since there is an idiomatic way to customize labels rendering.
I close this ticket, and I hope in the future as we find the good way to publish a proper documentation it will become more clear to developers.

Can someone please explain what and where these 'drawHover' and 'drawLabel' functions are? Thank you.

Please where these respective functions are and how do we override them.
This link https://www.sigmajs.org/demo/index.html is the exact use case I'm looking for.
Can you fork it in a sandbox please?

Both function are part of the sigma settings : https://github.com/jacomyal/sigma.js/blob/7b3a5ead355f7c54449002e6909a9af2eecae6db/src/settings.ts#L60-L61
So to override them is easy :
new Sigma(
  myGraph,
  myHTMLContainer,
  {
   labelRenderer: (context,  nodeData, settings) => { ... }
   hoverRenderer: (context,  nodeData, settings) => { ... }
);

You can take a look at their default implementation here :

https://github.com/jacomyal/sigma.js/blob/7b3a5ead355f7c54449002e6909a9af2eecae6db/src/rendering/canvas/label.ts
https://github.com/jacomyal/sigma.js/blob/7b3a5ead355f7c54449002e6909a9af2eecae6db/src/rendering/canvas/hover.ts

And if you want to see what we did for the demo : https://github.com/jacomyal/sigma.js/blob/7b3a5ead355f7c54449002e6909a9af2eecae6db/demo/src/canvas-utils.ts#L34-L114

Both function are part of the sigma settings : https://github.com/jacomyal/sigma.js/blob/7b3a5ead355f7c54449002e6909a9af2eecae6db/src/settings.ts#L60-L61
So to override them is easy :
new Sigma(
  myGraph,
  myHTMLContainer,
  {
   labelRenderer: (context,  nodeData, settings) => { ... }
   hoverRenderer: (context,  nodeData, settings) => { ... }
);

You can take a look at their default implementation here :

https://github.com/jacomyal/sigma.js/blob/7b3a5ead355f7c54449002e6909a9af2eecae6db/src/rendering/canvas/label.ts
https://github.com/jacomyal/sigma.js/blob/7b3a5ead355f7c54449002e6909a9af2eecae6db/src/rendering/canvas/hover.ts

And if you want to see what we did for the demo : https://github.com/jacomyal/sigma.js/blob/7b3a5ead355f7c54449002e6909a9af2eecae6db/demo/src/canvas-utils.ts#L34-L114

Thanks a lot bro really helped me.

The hoverRenderer not available anymore. Does anyone have an idea how a custom drawHover function works in Sigma version 3? Unfortunately, I don't understand the note in the changesets:

Moves labelRenderer, hoverRenderer and edgeLabelRenderer from settings to each renderer (https://github.com/jacomyal/sigma.js/blob/main/CHANGELOG.md)

The hoverRenderer not available anymore. Does anyone have an idea how a custom drawHover function works in Sigma version 3? Unfortunately, I don't understand the note in the changesets:

Moves labelRenderer, hoverRenderer and edgeLabelRenderer from settings to each renderer (https://github.com/jacomyal/sigma.js/blob/main/CHANGELOG.md)

You'll find how to customize your hoverRenderer in sigma v3 in this documentation page about how to migrate from v2 to v3:
https://www.sigmajs.org/docs/advanced/migration-v2-v3#canvas-labels-and-hovered-nodes-rendering

Perfect, thanks a lot. It's working.


502 Bad Gateway

Hi Miguel. I have now followed your tutorial to the end. Money very well spent. Congratulations on an excellent book. I have encountered a problem on deployment (I am using Linux/Ubuntu on Digital Ocean) & I will be grateful for any pointers you can give. This is a completely new area for me.
I have followed the tutorial exactly, but always get a bad gateway notification at the end, when I try to look at the website on the browser. I have purchased a URL, because I thought that might be the problem, but it hasn't helped.
Today, I think I narrowed it down slightly. I can start the app manually, with this script:
(venv) $ gunicorn -b localhost:8000 -w 4 microblog:app, The website is available in the browser. But when I try to supervisor take over, by saving the config file with this:
[program:microblog] command=/home/ubuntu/microblog/venv/bin/gunicorn -b localhost:8000 -w 4 microblog:app directory=/home/ubuntu/microblog user=ubuntu autostart=true autorestart=true stopasgroup=true killasgroup=true
I get the bad gateway error. I have been trying to resolve this myself, but no luck so far. Any pointers will be truly appreciated. Thanks

Hello. Finally resolved this, in case it helps anyone. I had saved the config file as microblog.config:
Removed the colon at the end at it worked.


[ASK] how do i append some file using it.

Hi @tanin47
i would like to ask you, how do i changed or append some file using javaparser.rs or is there any plan for this?
Thanks

Could you elaborate more? What do you mean by appending some file?

hmmm, i have some java file, then i would like to change. in my case (in android), i have Base Android Activity, then i would like to change to new Base Android Activity.

is it possible or do you have any plan for this?

Oh you mean like a tool to rename a class name? I don't think we have a plan for it.
A refactoring tool would require the semantics part to be done first as well.


Date Format for Schedule

I'd love to change the date format for the schedule

Check the Readme. It's already an option

I see the date_locale option.  I was hoping to be able to manually change the schedule to MMM DD rather than what gets preset by the locale

Nope sorry, this is way more error safe


3d vs reprojection error

Thanks for the wonderful work.
One question on the implementation, bpnp.py, line 86
r = pts2d_i*Si-proj_i[0:2,:]
This seems to be a 3d error instead of reprojection error, which does not match eq.5 in paper. Could you please provide more details on this? Thanks

It's the reprojection error. Normally it would be
r = pts2d_i - proj_i[0:2,:]/Si
but to make it numerically more stable, we use
r = pts2d_i*Si - proj_i[0:2,:]
It is still reflecting the reprojection error, not 3d error.


Attempt to fix circle ci builds for API

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This PR only targets api -- working on datastore ut test in a separate PR

LGTM! Can probably combine this with https://github.com/aws-amplify/amplify-ios/pull/282


Split core.py into individual files

As discussed in ev3dev/ev3dev#937, it would be helpful for many reasons to split each class or area into its own file.
The primary difficulty here is that we want to wait until all outstanding work is merged so that we don't accidentally lose anything. Naturally, git will treat all of these changes as deletions and creations rather than a clean delta.

Once the Infrared PR is in I will not have any more EV3-G APIs in progress so I could pause on that front so we can split up core.py.

We should go ahead and figure out what we want the ev3dev directory structure to be.  Today we have
dwalton@laptop ~/l/ev3dev-lang-python> ls -l ev3dev/
total 212
-rw-rw-r-- 1 dwalton dwalton   1033 Sep 22 15:21 auto.py
-rw-rw-r-- 1 dwalton dwalton   2713 Sep 22 15:23 brickpi.py
-rw-rw-r-- 1 dwalton dwalton 135150 Sep 25 10:32 core.py
-rw-rw-r-- 1 dwalton dwalton   6118 Sep 22 15:23 ev3.py
drwxrwxr-x 2 dwalton dwalton  12288 Sep 20 15:08 fonts/
-rw-rw-r-- 1 dwalton dwalton  18404 Sep 22 15:23 GyroBalancer.py
-rw-rw-r-- 1 dwalton dwalton   6637 Sep 25 10:28 helper.py
-rw-rw-r-- 1 dwalton dwalton      0 Sep 22 15:21 __init__.py
-rw-rw-r-- 1 dwalton dwalton  22396 Sep 22 15:23 webserver.py
dwalton@laptop ~/l/ev3dev-lang-python>

and we are about to add evb.py and pistorms.py.  Brainstorming....
Platforms
Maybe it is time for a platforms sub-dir to hold

brickpi.py
ev3.py
evb.py
pistorms.py

Moving ev3.py would make me a little nervous because so many people import it instead of auto.py.  But if we were ever going to move it this would be the time.
Sensors
Have a sensors sub-dir? class Sensor could go in its init.py and then all of the other sensor classes could go in individual files.  We could move all of the code that is in GyroBalancer.py to a gryo.py that holds class Gyro
Motors
Have a motors sub-dir?  We could move the RemoteControlledTank class in helper.py to a motors/tank.py and get rid of helper.py (I don't think we need much of the other code in there at this point).

I'm going to have to claim ignorance here... I know almost nothing about the Python module/import system. Can you confirm/correct these beliefs? When importing a module...

If there's a directory by that name within the python path list its init.py is evaluated and the result imported
If a matching file is found, it is evaluated and the result imported

WRT your proposals, that sounds good. However, I have one question:
Imagine I have code which only uses motors and I want it to be cross-platform. If I import auto, as I understand it it'll have to load all of the individual components. Is that a significant perf hit? I presume if the pyc file is cached or we ship it pre-compiled, this won't be an issue, but I'm not sure of that.
Otherwise, I think the discussion about moving the platform files is interesting... at a minimum, we need to make sure we produce an "upgrading guide" with any and all changes explained with specific modifications one must make. I don't have an opinion on whether we should make that change yet.

Here's how I would do it (assuming breaking imports is not a concern)...
|-- __init__.py
|-- _platform
|   |-- __init__.py
|   |-- brickpi.py
|   |-- brickpi3.py
|   |-- ev3.py
|   |-- evb.py
|   |-- pistorms.py
|   `-- travis.py
|-- button.py
|-- control
|   |-- __init__.py
|   |-- gyro.py
|   `-- rc_tank.py
|-- display.py
|-- led.py
|-- motor.py
|-- port.py
|-- sensor
|   |-- __init__.py
|   |-- dexter.py
|   |-- hitechnic.py
|   |-- fatcatlab.py
|   |-- lego.py
|   `-- mindsensors.py
|-- sound.py
`-- util.py

Key points:

There is one module for each major component, sensors, motors, lights, sound, display, etc.
There are lots of sensors, so there is a module for each vendor.
There is a platform module. It is private because now that there is /sys/class/board-info, all platform stuff can happen automagically. There is no more auto module.
Group all of the composite control classes/modules in to a control sub-package (composite meaning it uses both sensors and motors to create some sort of control system)

Other points:

There can be fake platforms as well, for example a travis platform that sets up fake sysfs for testing (detected by the travis environment variable).
util module contains things like debug_print() that prints to stderr for VSCode extension compatibility
Module names are singular (this doesn't seem to be in PEP8, but I read it from some python guru somewhere recently and it sounded like a good idea at the time).

If there's a directory by that name within the python path list its __init__.py is evaluated and the result imported

True

If a matching file is found, it is evaluated and the result imported

True
Also, modules are only imported once, so if two files in the same program import the same module, the module is not re-evaluated.

If I import auto, as I understand it it'll have to load all of the individual components. Is that a significant perf hit?

If you turn it around so that each core module imports _platform (the new auto), then you get the efficiency of only importing the modules you are using.

I have to say, I really like @dlech's proposal (which is pretty much a superset of @dwalton76's). Some questions:

If I import the root module, does it import _platform and all the sub-modules?
If I import _platform, does it import all the other modules? This is what auto currently does.

In my opinion, the answers should be 1) yes and 2) no, but that's just a preliminary thought.

For code varies by platform (take buttons for instance), will the user do from ev3dev import button and that in turn determines the platform and imports the appropriate platform/XYZ.py or will all button code for all platforms live in button.py?  If the latter would we even need the platform dir?  If its the former it might get a little confusing for the button code to be spread out in different directories.
For
|-- display.py
|-- led.py

How about
|-- display
|    |-- led.py
|    |-- screen.py

that way we are setup for anything that comes down the road (hdmi maybe).
For
|-- sensor
|   |-- __init__.py
|   |-- dexter.py
|   |-- hitechnic.py
|   |-- fatcatlab.py
|   |-- lego.py
|   `-- mindsensors.py

Would it be overkill to have each vendor have its own directory and then have a file per sensor?

|-- display
|    |-- led.py

😕 um... why are the LEDs under "display"? I view those as quite different things ("display" being the display) and have often used LEDs but almost never used the display.

Maybe visualoutput instead of display is a more descriptive (but way too long to actually use) way of describing how I group them together in my head :)

If I import the root module, does it import _platform and all the sub-modules?

It could

If I import _platform, does it import all the other modules? This is what auto currently does.

Nope. The _platform module figures out which platform and imports the appropriate submodule. e.g.
if platform == 'brickpi':
    from ev3dev2._platform.brickpi import *
elif platform -- 'ev3':
    from ev3dev2._platform.ev3 import *
elif...

The other modules would use _platform to get things like paths and port names.

Maybe visualoutput instead of display is a more descriptive (but way too long to actually use) way of describing how I group them together in my head :)

HDMI on RPi already should work with the existing display class. It provides an fbdev, the same as all of the other displays that we use.
So, I don't really forsee any possible expansion in the visual output devices category. Better to keep it flat.

Would it be overkill to have each vendor have its own directory and then have a file per sensor?

Yes. Way overkill.

Nope. The _platform module figures out which platform and imports the appropriate submodule. e.g. ... The other modules would use _platform to get things like paths and port names.

How does the user access the OUTPUT_* and INPUT_* constants?

How does the user access the OUTPUT_* and INPUT_* constants?

First, I would suggest allowing the names 'A', 'B'... 1, 2... to be automatically converted to the correct port name. It's much shorter and pretty obvious.
Since the constants refer to ports, they should live in the port module. So the user might do this.
from ev3dev2.port import OUTPUT_A

And the implementation in port.py might look like this...
from ev3dev._platform import PORT_NAMES

INPUT_1 = PORT_NAMES['1']
...
OUTPUT_A = PORT_NAMES['A']
...

For code varies by platform (take buttons for instance), will the user do from ev3dev import button and that in turn determines the platform and imports the appropriate platform/XYZ.py or will all button code for all platforms live in button.py? If the latter would we even need the platform dir? If its the former it might get a little confusing for the button code to be spread out in different directories.
I'm still trying to get my head wrapped around what will live where for this scenario.

As far as I can tell, the platform-specific part for buttons is just the path to the device node (/dev/input/...), so that is what would be be importing from _platform. The way I envisioned it is that the platform files are for the most part, just a bunch of names of things that are different between platform. The travis platform file might have more code for faking things for testing.


soft tweak falloff in 2022

the falloff of soft tweak doesnt work in maya 2022.
setting the falloffAroundSelection Attr on the deformer to ZERO seems to fix it.

the issue was fixed in this ticket https://github.com/mgear-dev/mgear4/issues/188


Prevent rotation

Thanks for the great library.
I'm trying to prevent my bodies to rotate. It would be a "unary" constraint. I've looked at the code and issues but it looks like it's not possible currently. If not, I'd be happy to submit a PR if you can put me on the right track!

Try set inertia to Infinity when you create your body.

Awesome! Thanks a lot.

Does that still work?  I tried setting my player object's inertia property to Infinity and it still tips over.  I tried both:
player.body.inertia = 'Infinity';

And
player.inertia = 'Infinity';

The object still tips over.  Note this is with a Phaser JS app using the Matter JS physics engine.

@roschler it needs to be the word Infinity without any quotes as it's a value in JS, then it should work.

@roschler you can use setFixedRotation func
player.setFixedRotation();

@roschler Also be sure to set player.inverseInertia=0.


Expand guidance on checkpointing long-running transactions

This PR carries over the guidance from the autoscaling page. While it might be even better to create a new design pattern for checkpointing, move the content there, and link to it from both places, I figured that would be more disruptive and we should possibly wait until there is a 3rd place that would require this info.
Let me know what you think.

Learn Build status updates of commit 4a0a101:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/guide/design-principles/self-healing.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@EdPrice-MSFT
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@EdPrice-MSFT  - Could you review this proposed update to your article and enter #sign-off in a comment if it's ready for merge?
Thanks!

Learn Build status updates of commit 01be664:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/guide/design-principles/self-healing.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

#Sign-Off


cmd/go: merge coverage profiles from subprocesses

According to this snippet, initCoverProfile clears the coverage profile on every run:
https://github.com/golang/go/blob/4b36e129f865f802eb87f7aa2b25e3297c5d8cfd/src/cmd/go/internal/test/cover.go#L23-L24
That seems counterproductive when we're collecting coverage from a test that runs a binary multiple times (such as the tests for cmd/go itself), or from a test that invokes itself as a subprocess.
Instead, I suspect that we should use OS-level file locking so that we can merge coverage from multiple invocations.
If we do that, I'm not entirely sure when we should remove the previous profile, though.
(CC: @ianlancetaylor @rsc)

This is also annoying when testing exiting code using a subprocess, as in this technique by @adg https://talks.golang.org/2014/testing.slide#23

@thanm, is this done automatically with the new coverage support enabled?

At least in the cmd/go case, yes, this is already taken care of by the new implementation, yes.


TextEdit: added redo option to the context menu

This PR adding  redo option to the context menu for the TextEdit node, because a LineEdit has this option.
Or we can delete redo menu option from the LineEdit node to be consistent?

Makes sense, especially since redo is already implemented (but hardcoded).

Thanks!


enhance header section dark mode nav kept at right place

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]
Fixes:  #(#2455)
Description
enhance header section dark mode nav kept at right place
Type of PR

[ ] Bug fix

Screenshots / videos (if applicable)
Before:-

After:-

Checklist:

[x] I have made this change from my own.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

@huamanraj , this workflow requires your approval to proceed. Could you please review and approve it?


Unresolved reference: Parcelize

The latest version (0.7.0) shows the Parcelize annotation red with this error message: "Unresolved reference: Parcelize" in IntelliJ Ultimate 2022.3.1
This is NOT urgent as the project builds fine, just a little annoying.
Version 0.6.0 doesn't have this problem.

That might be an issue with IDEA. You can try deleting the .idea folder and reopening the project, and see if this helps. Also what Kotlin version you are using? Can you try Kotlin 1.7.21? Do you have a reproducer project?

I have just checked, it works just fine for me:

IntelliJ IDEA 2022.3.1 (Ultimate Edition)
Kotlin 1.7.20
Kotlin IntelliJ IDEA plugin 223-1.7.21-release-272-IJ8214.52

I tried deleting the .idea folder but that didn't help.
I'm using Kotlin version 1.7.22
I don't really have a reproducer project, but this is the project I'm facing this issue. (compose branch)
It's not that small so for explanation:

model module depends on essenty
model api's essenty to other modules like app module

Example class having this issue dev.datlag.burningseries.ui.screen.home.HomeScreenComponent

Thanks! Looks like it was broken in #73. Parcelize annotation was marked as @OptionalExpectation and removed from all non-Android targets. Since you are using only android and jvm targets, it resolves to the jvm artifact (not common) which doesn't have Parcelize anymore. I will revert this particular change.

I think this happens because Kotlin commonizer doesn't support sharing android and jvm source sets yet. So it defaults to just jvm.

Looks like we can't use @OptionalExpectation at all, I will avoid it completely for now.
Cc: @sellmair

Version 0.7.1 is released and should fix this issue. Please allow ~2 hours for artifacts to fully propagate.

Works like a charm, btw I just check the artifact availability here https://repo1.maven.org/maven2/com/arkivanov/essenty/parcelable/

Yeah, it's often faster than 2 hours. But there are more target-specific artifacts, they are synchronized in batches, so some targets may be still missing. https://repo1.maven.org/maven2/com/arkivanov/essenty/

The issue can still be reproduced on latest version 1.1.0 for nested classes.

Can you share a reproducer?


Nuxt Build Error. Seems to fail on trying to compile Sass for VuetifyJS

Running the npm run dev works perfectly, BUT
About a dozen of these errors on the npm run build
There is something that nuxt does not like, this should not happen, you are testing locally and when you go to build it fails??
You go through hours possibly days of building, and yet when you actually want to finish your project and start setting up  towards production. you cant... This is not good for Nuxt.
All these errors are coming from files I do not modify or access.
ERROR in ./node_modules/vuetify/src/components/VGrid/_grid.sass (./node_modules/css-loader/dist/cjs.js??ref--6-oneOf-1-1!./node_modules/postcss-loader/src??ref--6-oneOf-1-2!./node_modules/sass-loader/dist/cjs.js??ref--6-oneOf-1-3!./node_modules/vuetify/src/components/VGrid/_grid.sass)
Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
ValidationError: Invalid options object. Sass Loader has been initialized using an options object that does not match the API schema.
 - options has an unknown property 'prependData'. These properties are valid:
   object { implementation?, sassOptions?, additionalData?, sourceMap?, webpackImporter? }
    at validate (/Users/..../Documents/Development/node_modules/sass-loader/node_modules/schema-utils/dist/validate.js:104:11)
    at Object.loader (/Users/...../Documents/Development/node_modules/sass-loader/dist/index.js:30:29)
 @ ./node_modules/vuetify/src/components/VGrid/_grid.sass 4:14-204
 @ ./node_modules/vuetify/lib/components/VGrid/VContainer.js
 @ ./node_modules/vuetify/lib/components/VGrid/index.js
 @ ./pages/settings/general.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi<EMAIL_ADDRESS>./.nuxt/client.js

Just to rule out any of the project code, I deleted all the pages except the index.vue which I placed a simple div that says test, I removed all components, and simplified the default.vue layout. I removed all plugins, and middleware. I do not use SCSS/SASS. so that part cant even be me.
This is the second time I've seen build problems with Nuxt. its becoming an issue. You can not work on the dev site and then move to production build and then everything fails. That makes no sense. This build process needs to be trusted.

I'm starting to think its related to wepback in some missing dependency. Looking at package.json and comparing it to fresh nuxt builds, its identical. I have added packages previously which I removed, that was a while ago, could be related. But still doesnt make sense.

After further investigation and testing. I cleared out the node_modules and ran a fresh install of dependencies. It looks like previously something happened with a sass package (probably from another npm package) and installing from package.json didnt solve the issue, had to completely clear out the node packages, makes no sense why it was caught up in some mysterious problem unrelated to anything I was working on. I'll close this, doesn't look like its directly impacted from Nuxt.


AdminSite site title

when using django-admin-bootstrapped site title in not customizable using AdminSite, take a look here please
https://code.djangoproject.com/ticket/24740#comment:4

If you look at the source code here you'll see how to override that
https://github.com/django-admin-bootstrapped/django-admin-bootstrapped/blob/master/django_admin_bootstrapped/templates/admin/base_site.html#L4
Please note that this feature is deprecated and has been removed from documentation. In 2.5.1 we'll switch to behave like upstream django.

ok, I'll wait for 2.5.1 thanks

@drakkan could you please check git master that works for you? thanks!

it works now, thanks!


Move to quickjs-ng

quickjs is too long to release , maybe we should move to quickjs-ng  https://github.com/quickjs-ng/quickjs

好像qjs今年更新到ES2022了


Compilation fix on linux platform with clang

What version of clang emits a warning here?

clang 8.0


1/3rd less instructions than match

If you look in the std lib we do these tricks in to_digit.
Smaller wasm is a good thing... (godbolt: https://godbolt.org/z/vocdaKW9x )
I know speed is not the prime reason for the crate, but bench showed a 20% speedup of hex::encode when I ran them.
(The rest of the benches looked no different.)

Smaller wasm is a good thing... (godbolt: godbolt.org/z/vocdaKW9x )

Hey! I found this also makes the instructions smaller.
Same speed but more readable.
fn is_hex_ascii(byte: &u8) -> bool {
	let byte = byte | 0b10_0000;

	matches!(byte, b'0'..=b'9' | b'a'..=b'f')
}

Short and sweet, I like it.


illegal instruction zed-python-api on jetpack 4.5, sdk 3.4, Xavier AGX

Hi
I have followed the installation instructions and consistently get illegal instruction error with the python samples and tutorials. This happens both in the directly installed sdk as well as the various docker images.
Does this need to be updated for either sdk 3.4 or Jetpack 4.5?
The c++ examples and tools all work fine.
Thanks
bb

Hi
Could you post more details about this error (a screenshot, the exact message, and configuration) and a simple case to reproduce it, maybe the docker image and commands used?
The only thing that came to mind with this message and mixing aarch64 and x86 docker images or maybe installers (this shouldn't be possible). It may be on our side during the compilation of the cython wrapper but this error was not reported before.

Hi
Sorry not to provide more details. I am running on an Xavier AGX with
Jetpack 4.5. The error occurs both within docker (which I will walk though
below) and if I do a direct install. I assumed that it was an issue with
Jetpack 4.5 since the only docker image is for jp4.4, but as I said, I also
saw this when I did a direct install and followed the same steps in a clean
python3 environment. Thanks for your help!!!
bb
Reproduce on Docker
Docker command
docker run -it --runtime nvidia --privileged -e DISPLAY --network host
--device /dev/video0 -v /tmp/.X11-unix:/tmp/.X11-unix
stereolabs/zed:3.3-tools-devel-jetson-jp4.4
Install necessary python libraries etc.

apt-get update
apt-get install python3-pip
pip3 install --upgrade pip
python3 -m pip install cython numpy opencv-python pyopengl
python3 get_python_api.py

Try the first tutorial:
root@bruce-ai:/usr/local/zed/samples/tutorials/tutorial 1 - hello
ZED/python# python3 hello_zed.py
Illegal instruction (core dumped)
I have attached the output from the terminal for your reference as well.
On Mon, Feb 8, 2021 at 4:54 AM Aymeric Dujardin<EMAIL_ADDRESS>wrote:

Hi
Could you post more details about this error (a screenshot, the exact
message, and configuration) and a simple case to reproduce it, maybe the
docker image and commands used?
The only thing that came to mind with this message and mixing aarch64 and
x86 docker images or maybe installers (this shouldn't be possible). It may
be on our side during the compilation of the cython wrapper but this error
was not reported before.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stereolabs/zed-python-api/issues/167#issuecomment-775020110,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWPS2UQSDDNCCUOCFVCPS3S56YFDANCNFSM4XGUQU5Q
.

As a test, I tried building zed-python-api within the docker container, and got the illegal instruction as well:
root@bruce-ai:/zed-python-api/src# python --version
Python 2.7.17
root@bruce-ai:/zed-python-api/src# python3 --version
Python 3.6.9
root@bruce-ai:/zed-python-api/src# python3 -m pip install cython numpy
Requirement already satisfied: cython in /usr/local/lib/python3.6/dist-packages (0.29.21)
Requirement already satisfied: numpy in /usr/local/lib/python3.6/dist-packages (1.19.5)
root@bruce-ai:/zed-python-api/src# python -c "import platform; print(platform.architecture())"
('64bit', '')
root@bruce-ai:/zed-python-api/src# python3 setup.py build
Illegal instruction (core dumped)

Ok thank you for all the information, that's very helpful. We'll look into it and try to reproduce and find a solution. We'll get back to you as soon as we have news.

I got the same problem with Jetpak 4.4 and ZED SDK 3.4
    Python 3.6
    ZED SDK 3.4

Sorry to bug you, but is there any chance that someone could look into this? This is a blocker for anyone who wants to use python and the sdk on the jetson family. Thanks.

Thank you for your patience, we tried different combinations and it seems the python binary of the system doesn't have this issue, only when using virtual env or conda somehow.
Since even compiling the Cython project trigger the error we can rule out our CI/packaging or an error within the code. From our testing, this fixes https://forums.developer.nvidia.com/t/illegal-instruction-core-dumped-xavier/166278/4 (OPENBLAS_CORETYPE=ARMV8 before the python executable) found by another user on nvidia forum seems to solve the problem.
Could you test it and see if it also fixes the issue on your side?

The workaround did fix the problem, and when I am running natively (outside
of docker) I am using virtualenvwrapper. So, BIG THANKS!
I also tried running on the stereolabs/zed:3.3-tools-devel-jetson-jp4.4
docker image, and it fixes the problem there, but I am getting other errors
there (for example, running the depth sensing example, I get:
File "depth_sensing.py", line 49, in
viewer = gl.GLViewer()
File "/zed-lab/depth sensing/python/ogl_viewer/viewer.py", line 218, in
init
self.camera = CameraGL()
File "/zed-lab/depth sensing/python/ogl_viewer/viewer.py", line 459, in
init
self.setDirection(tmp, tmp2)
File "/zed-lab/depth sensing/python/ogl_viewer/viewer.py", line 513, in
setDirection
if(sl.Translation.dot_translation(self.vertical_, self.up_) < 0.):
AttributeError: type object 'pyzed.sl.Translation' has no attribute
'dot_translation'
root@bruce-ai:/zed-lab/depth sensing/python# python3 -m pip install pyopengl
Requirement already satisfied: pyopengl in
/usr/local/lib/python3.6/dist-packages
When I tried stereolabs/zed:3.3-py-devel-jetson-jp4.4 docker image, I
didn't need to use the OPENBLAS... work-around but got the same error as
above. But that is for a different ticket I guess.
Thanks again for your help. It is much appreciated.
On Tue, Feb 23, 2021 at 4:58 AM Aymeric Dujardin<EMAIL_ADDRESS>wrote:

Thank you for your patience, we tried different combinations and it seems
the python binary of the system doesn't have this issue, only when using
virtual env or conda somehow.
Since even compiling the Cython project trigger the error we can rule out
our CI/packaging or an error within the code. From our testing, this fixes
https://forums.developer.nvidia.com/t/illegal-instruction-core-dumped-xavier/166278/4
(OPENBLAS_CORETYPE=ARMV8 before the python executable) found by another
user on nvidia forum seems to solve the problem.
Could you test it and see if it also fixes the issue on your side?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stereolabs/zed-python-api/issues/167#issuecomment-784050030,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWPS2UH7OKOYDA4TTZTKLDTAN35DANCNFSM4XGUQU5Q
.

Glad to hear this workaround is fixing the problem. Openblas is used by the ZED SDK so I guess it's required for some version of the package when using the SDK.
The missing "dot_translation" is our fault, that's because the docker images contain the ZED SDK 3.3.0 and the python wrapper was improved in later patches (3.3.1 and 3.3.2). The python samples with OpenGL display are expecting a ZED SDK >= 3.3.1
I'll fix this by regenerating the 3.3 docker images.


Allow for copy/paste of multiple rows+columns

I'd like to see essentially the exact same thing as this person is requesting here: https://github.com/adazzle/react-data-grid/issues/86

I'd like to be able copy & paste a range of rows and columns, similar to what you can do in Excel at the moment.
this could be copying between cell ranges on the same grid, between two separate grid instances, or from somewhere off-grid (e.g. Excel).
https://cloud.githubusercontent.com/assets/2393035/10424809/3fc45d68-70ca-11e5-907a-38d63878d50a.gif

Would this be possible to do with this component? If so it would be awesome!
Thanks!

Hey @tnrich - neat idea, sounds super useful. I probably won't have the time to implement it myself, but I'd gladly merge if somebody would send me a pull request for such a feature!

@tnrich Have u got any idea on this copy & paste a range of rows and columns, similar to what you can do in Excel at the moment.

Did anyone find a solution?

Did anyone find a solution?


[Chore] Fix azd provision to honor stripe as optional.

How do I provision in such as way that Stripe is optional? Without it, the provision fails.
(x) Failed: Container App: ca-stripe-vyc7ius4wwiya

ERROR: deployment failed: failing invoking action 'provision', error deploying infrastructure: deploying to subscription:

Deployment Error Details:
InvalidParameterValueInContainerTemplate: The following field(s) are either invalid or missing. Field 'configuration.secrets' is invalid with details: 'Invalid value: "stripe-public-key": Secret value and keyvaulturl cant be empty at same time'; Field 'configuration.secrets' is invalid with details: 'Invalid value: "stripe-secret-key": Secret value and keyvaulturl cant be empty at same time'; Field 'configuration.secrets' is invalid with details: 'Invalid value: "stripe-webhook": Secret value and keyvaulturl cant be empty at same time';.

TraceID: ec1ed82715e7823765e73d38564a974a

One option to fix this issue is to update the Bicep template to avoid creating secrets if the env variables aren't set.

From @sinedied:

[10:49 AM] Yohan Lasorsa
AFAIK, azd uses current exported env variables for deployment, and some of these values are used as parameters for the Bicep templates

This fix as merged into main worked for me. Thank you.


Uncaught TypeError: Cannot read property 'func' of undefined

Getting an error inside the browser console:
'Uncaught TypeError: Cannot read property 'func' of undefined;'
and in bundled index.js there is a line where app fails:
var func = _react.PropTypes.func,
File index.js
`import React from 'react';
import ReactDOM from 'react-dom';
import { Provider } from 'react-redux';
import { createStore, applyMiddleware } from 'redux';
import { Router, browserHistory } from 'react-router';
import reducers from './reducers';
import routes from './routes'
const createStoreWithMiddleware = applyMiddleware()(createStore);
ReactDOM.render(

, document.querySelector('.container'));
`
File ./src/routes.js
`import React from 'react';
import { Route, IndexRoute } from 'react-router';
import App from './components/app';
export default (

);
`
Versions of the packages:
"react": "16.3.2",
"react-dom": "16.3.2",
"react-router": "^2.8.1",
Unable to understand what is the actual reason and how can I solve this?

You need a newer version of React Router, at least 3.2.0.

Getting an error inside the browser console:
'Uncaught TypeError: Cannot read property 'func' of undefined;'
and in bundled index.js there is a line where app fails:
var func = _react.PropTypes.func,
File index.js
`import React from 'react';
import ReactDOM from 'react-dom';
import { Provider } from 'react-redux';
import { createStore, applyMiddleware } from 'redux';
import { Router, browserHistory } from 'react-router';
import reducers from './reducers';
import routes from './routes'
const createStoreWithMiddleware = applyMiddleware()(createStore);
ReactDOM.render(
, document.querySelector('.container'));
`
File ./src/routes.js
`import React from 'react';
import { Route, IndexRoute } from 'react-router';
import App from './components/app';
export default (
);
`
Versions of the packages:
"react": "16.3.2",
"react-dom": "16.3.2",
"react-router": "^2.8.1",
Unable to understand what is the actual reason and how can I solve this?

hi, It looks like a react-router bug (related to prop types.) It's working on react-router 3.2.0
i think you should sudo npm install --save<EMAIL_ADDRESS>it works! :) :)

Thank You. ... :)
On Fri, Oct 12, 2018 at 10:27 PM Muhammad Haris Baig <
<EMAIL_ADDRESS>wrote:

hi, It looks like a react-router bug (related to prop types.) It's working
on react-router 3.2.0
i think you should sudo npm install --save<EMAIL_ADDRESS>it works! :) :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ReactTraining/react-router/issues/6296#issuecomment-429391986,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AgD5Uitz1B3hBckUXTnMHMj4KpDU2KFmks5ukMoQgaJpZM4WB1It
.


GitHub Actions are broken for deployment

The azure/docker-login action is broken with the changes rolled out by GitHub Actions in November.

    branches: [
   # Lists ALL the branches

remotes/origin/awesome
remotes/origin/more-work
remotes/origin/new-main]

on:
  push:
    branches: [main]
  pull_request:
    # The branches below must be a subset of the branches above
    branches: [main]
  schedule:
    - cron: '0 13 * * 4'
jobs:
  analyze:
    name: Analyze
    runs-on: ubuntu-latest
    steps:
    - name: Checkout repository
      uses: actions/checkout@v2
      with:
        # We must fetch at least the immediate parents so that if this is
        # a pull request then we can checkout the head.
        fetch-depth: 2
    # If this run was triggered by a pull request event, then checkout
    # the head of the pull request instead of the merge commit.
    - run: git checkout HEAD^2
      if: ${{ github.event_name == 'pull_request' }}
    # Initializes the CodeQL tools for scanning.
    - name: Initialize CodeQL
      uses: github/codeql-action/init@v1
      # Override language selection by uncommenting this and choosing your languages
      # with:
      #   languages: go, javascript, csharp, python, cpp, java$ git branch -a
Lists ALL the branches

remotes/origin/awesome
remotes/origin/more-work
remotes/origin/new-main$ git branch -a

Lists ALL the branches

remotes/origin/awesome
remotes/origin/more-work
remotes/origin/new-mainHeadingshttps://docs.google.com/document/d/1yTSQyTfpS-JBV2kaYsnRygu8yv33F6m6hn7QzwGelzM/edit?usp=drivesdk&disco=AAAATAObPb4https://docs.google.com/document/d/1yTSQyTfpS-JBV2kaYsnRygu8yv33F6m6hn7QzwGelzM/edit?usp=drivesdk&disco=AAAATAObPbIhttps://docs.google.com/document/d/1yTSQyTfpS-JBV2kaYsnRygu8yv33F6m6hn7QzwGelzM/edit?usp=drivesdk&disco=AAAASzLo5nYДокументы Skip to content flow swiftkey to create an account for your own personal content and create your company and will continue my conte.        {} |¦^~™>¦¶§|;`55,8963257,-&🖱 @so [                                                                                @                                                                                @@                                                                                nt SwiftKey SwiftKey FlowOS is the microsoft.com for you and your company is the best option FSkippyor to content https://privacy.microsoft.com/en-gb/privacystatement<EMAIL_ADDRESS>
<EMAIL_ADDRESS>is a great place to work for and I am very excited to have Erik.valiahmetOver THE OPPORTUNITY TO work with you and your company and s functions on is not the same way you are the best option FSkCorrelatioand for WORK WITH YOU AND I LOOK FORWARD TO working with you and your company and s functions on is no secret to content SwiftKey Flow Windows OS Skip to content flow and to use web design for<EMAIL_ADDRESS>and I am very interested in the position of working with you and your company and will continue my content SwiftKey Correlation Id and to be a part of my team of the current user experience and of all the information that you businesses and the company are looking forward to content SwiftKey Flow Skip to content flow and to use web design for the most important thing to https://docs.google.com
/document/d/1yTSQyTfpS-JBV2kaYsnRygu8yv33F6m6hn7QzwGelzM/edit?usp=drivesdk&disco=AAAASzLo5k0
¿26D7 P52H PPS6 4G6T

verikflo220@gmail.comerikvaliahmetov523@gmail.comErik07.29.86@gmail.comhttps://docs.google.com/document/d/1yTSQyTfpS-JBV2kaYsnRygu8yv33F6m6hn7QzwGelzM/edit?usp=drivesdk&disco=AAAASzLo5nYДокументы Skip to content flow swiftkey to create an account for your own personal content and create your company and will continue my conte.        {} |¦^~™>¦¶§|;`55,8963257,-&🖱 @so [                                                                                @                                                                                @@                                                                                nt SwiftKey SwiftKey FlowOS is the microsoft.com for you and your company is the best option FSkippyor to content https://privacy.microsoft.com/en-gb/privacystatement<EMAIL_ADDRESS><EMAIL_ADDRESS>is a great place to work for and I am very excited to have Erik.valiahmetOver THE OPPORTUNITY TO work with you and your company and s functions on is not the same way you are the best option FSkCorrelatioand for WORK WITH YOU AND I LOOK FORWARD TO working with you and your company and s functions on is no secret to content SwiftKey Flow Windows OS Skip to content flow and to use web design for<EMAIL_ADDRESS>and I am very interested in the position of working with you and your company and will continue my content SwiftKey Correlation Id and to be a part of my team of the current user experience and of all the information that you businesses and the company are looking forward to content SwiftKey Flow Skip to content flow and to use web design for the most important thing to https://docs.google.com
/document/d/1yTSQyTfpS-JBV2kaYsnRygu8yv33F6m6hn7QzwGelzM/edit?usp=drivesdk&disco=AAAASzLo5k0
¿26D7 P52H PPS6 4G6T

For me it seems like this is fixed right?

azure/docker-login

@emmairwin ?

For me it seems like this is fixed right?

@emmairwin

I will close as it is two years old, and @jeffwilcox can open if he feels that's in error.


Update error message for daemon on Windows

When running chef-zero with the daemon option on Windows, the error message incorrectly says 'Process.daemon requires Ruby >= 1.9', even when Windows has Ruby 2.0+.

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

@aerii

Please sign the CLA here.

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

👍

👍


Feature/better scope

Hi @samansmink
Sorry for this change but after some usage I realized that the syntax<EMAIL_ADDRESS>is not really user friendly when you use wildcard and scopes. The way scope score is computed can lead to wrong best score matching... After some reflection and analyze I think that the syntax az://storage_account.domain/container/path will/is easier, in the code and in the syntax, note that there is no ambiguity on the two syntax because container names cannot contains dots

I let the PR in draft to discuss if you want or to make this change. I don't mind if at the end you prefer to discard this. If it discard I will try to improve the secret lookkup :)

Ok so once merge i will update the doc :)

thanks a lot again!


feat: use m_protxHash instead of masternodeOutpoint for hashing dsq and dstx after v19 activation

Issue being fixed or feature implemented
Should fix #5401 with minimal potential coinjoin service interruption (~1 minute around v19 fork point) for up to date clients. Fully backwards compatible prior to v19 activation. Old clients won't be able to mix after v19 activation though until they implement similar changes. And I think we should also be able to finally drop masternodeOutpoint from CCoinJoinQueue and CCoinJoinBroadcastTx once v19 is active because of that which would be a nice bonus.
cc @HashEngineering
What was done?
re-use v19 activation to switch GetSignatureHash logic
How Has This Been Tested?
mixing on mainnet
Breaking Changes
mixing won't work on current testnet until MNs are updated
Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation
[x] I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

Any reason to not make this backwards compatible based on PROTO version instead of hard fork status? Seems bad to break mixing for electrum clients for example (although likely not many people use this)

It's much worse to have a 19.1 vs 19.2 split in mixing pools imo cause less compatible MNs to mix at (and clients to mix with) means that mixing is going to be slower and less secure for both versions. Also, non-core mixing clients would have to update anyway cause bls sigs are going to change from legacy to bls too so they won't be able to verify dsqs/join mixing after v19 activation.


Disable linkify-user-location on own editable profile

Closes #2581.
I chose slightly different approach: instead of except: [features.isUserOwnProfile] it will skip editable nodes by using existing isEditable helper. That's because there are two sets of DOM nodes (display and form) on user profile and "Edit profile" button just toggles between those two.
This way displayed location will remain linkified, but editable field will be kept intact.

Thank you for contributing this bugfix and justifying your choice Roman!


chore(main): release taiko-client 0.24.0

:robot: I have created a release beep boop
0.24.0 (2024-05-30)
Features

taiko-client: improve chain head check in NeedReSync (#17431) (4dbe0af)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/taikoxyz/taiko-mono/releases/tag/taiko-client-v0.24.0 :sunflower:


adding mother

adding mother doesnot works.it doesnt display any node

+1

Ye issue sahi kar do

Kindly fix this issue.It is looking like incomplete.

Okay I will, may be this weak, thanks for pointing out.

Hello I hope you have added..

I have added but still it has bug, I am working on it, right now mother will add but if father is not already exist, in case father exist mother is adding as grandmother.
working on this issue

ok thanks

Noticed this bug as well... seems like the logic needs improvement. I will see if I can fork this and fix the issue.

Yes I agree on the point of logic, check the newway folder, I am trying different way to do things. It is still in under construction.


[az containerapp compose create] Docker Compose seems like not understand special variable: $AZURE_CONTAINERAPPS_ENV_DEFAULT_DOMAIN

Describe the bug
After run the az container compose create command with the following docker-compose file, the value of SERVER_HOST environment var hasn't been applied correctly. The result is SERVER_HOST => nginx. in Container App's environment variables.
version: '3.4'
services:
  app:
    image: 'ACR_NAME.azurecr.io/Repo_Name/Image_Name:Tag_Name'
    environment:
      - HOST=<IP_ADDRESS>
      - PORT=8080
      - SERVER_PROTOCOL=HTTP
      - SERVER_HOST=nginx.$AZURE_CONTAINERAPPS_ENV_DEFAULT_DOMAIN
      - SERVER_PORT=80
      - SERVER_PATH=/app

If it's updated as nginx.$$AZURE_CONTAINERAPPS_ENV_DEFAULT_DOMAIN => the result will be SERVER_HOST => nginx.$
Related command
az container compose create
Errors
##[error]time="2024-05-17T05:09:11Z" level=warning msg="The \"AZURE_CONTAINERAPPS_ENV_DEFAULT_DOMAIN\" variable is not set. Defaulting to a blank string."
Issue script & Debug output
##[error]time="2024-05-17T05:09:11Z" level=warning msg="The \"AZURE_CONTAINERAPPS_ENV_DEFAULT_DOMAIN\" variable is not set. Defaulting to a blank string."
Expected behavior
template:
    containers:
    - env:
      - name: HOST
        value: <IP_ADDRESS>
      - name: PORT
        value: '8080'
      - name: SERVER_PROTOCOL
        value: HTTP
      - name: SERVER_HOST
        value: nginx.xxxxxxxx-xxxxxxxx.southeastasia.azurecontainerapps.io
      - name: SERVER_PORT
        value: '80'
      - name: SERVER_PATH
        value: /app

Environment Summary
{
  "azure-cli": "2.60.0",
  "azure-cli-core": "2.60.0",
  "azure-cli-telemetry": "1.1.0",
  "extensions": {
    "aks-preview": "3.0.0b13",
    "azure-devops": "1.0.0",
    "containerapp": "0.3.50"
  }
}

Additional context
Reference: https://techcommunity.microsoft.com/t5/apps-on-azure-blog/accelerating-azure-container-apps-with-the-azure-cli-and-compose/ba-p/3516636#:~:text=There are also two special environment variables available at the time of evaluation that are specific to Azure Container Apps.  AZURE_CONTAINERAPPS_ENV_DEFAULT_DOMAIN contains the default domain name for a Container Apps environment.

Thank you for opening this issue, we will look into it.

Hi @vienleidl
Thanks for asking this question.
You can try: CONTAINER_APP_ENV_DNS_SUFFIX
Where did you get ##[error]time="2024-05-17T05:09:11Z" level=warning msg="The \"AZURE_CONTAINERAPPS_ENV_DEFAULT_DOMAIN\" variable is not set. Defaulting to a blank string."?
Please try CONTAINER_APP_ENV_DNS_SUFFIX and check if this error still there.
Thanks!

And for the template:
template:
containers:
- env:
- name: HOST
value: <IP_ADDRESS>
- name: PORT
value: '8080'
- name: SERVER_PROTOCOL
value: HTTP
- name: SERVER_HOST
value: nginx.xxxxxxxx-xxxxxxxx.southeastasia.azurecontainerapps.io
- name: SERVER_PORT
value: '80'
- name: SERVER_PATH
value: /app
 The env value will be show as what you set, for example: `nginx.$CONTAINER_APP_ENV_DNS_SUFFIX`


feat(Tree): left and right arrow keyboard navigation

Follows the ARIA design pattern https://www.w3.org/TR/wai-aria-practices-1.1/examples/treeview/treeview-1/treeview-1a.html
On Left Arrow, it should collapse tree if it is open. If it is closed, it should move focus to parent.
On Right Arrow, it should expand tree if it is closed and has subtree. If it is open, it should move focus to first child in subtree.
Also removed circular navigation provided by the FocusZone.
WIP: Unit Tests.

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


TS enforces left-hand side of instanceof must be an object type, but it can be any type.

🔎 Search Terms
"instanceof", "Symbol.hasInstance"
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about instanceof

⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.5.4#code/FAYw9gdgzgLgBAUQG4FMIDkCuBbARigJyjgF44BvYOOAbQGUBPPMAGwDoALAQygEloYXCCBQBdAFxwAFEklCGASlIA+ODAYAHFGABmcJKRJkA5BBz4CxuADJr+uAFI4AJkNwADMAC+AbmDAASz0pAGY4AIEhEV1EVAxzQiglSmpwaFYUNhYwAHMpY2wODjgAd24YAH5jBW9-IOkARndwyOFtPWQ0LDxE5Ko4NKgMrNypACIm8OIUOLGar2AgA
💻 Code
const EvenNumbers = {
  [Symbol.hasInstance]: v => typeof v === 'number' && v % 2 == 0
};

if (3 instanceof EvenNumbers) {
  console.log('mhh what?')
}

if (10 instanceof EvenNumbers) {
  console.log("10 is even")
}

🙁 Actual behavior
Typescript shows an error on the 3 and the 10:

The left-hand side of an 'instanceof' expression must be of type 'any', an object type or a type parameter. (2358)

🙂 Expected behavior
It should not show any error, because the code is valid JS
Additional information about the issue
After having support for hasInstance https://github.com/microsoft/TypeScript/pull/55052, this actually means that the left-hand side operand doesn't have to be an object anymore. It can perfectly be primitives, as shown by this example (albeit contrieved...)
The spec for relational expressions also allows any kind of relational expressions (which also includes anything that resolves in a primitive) as well https://tc39.es/ecma262/multipage/ecmascript-language-expressions.html#sec-relational-operators

I would hate to miss out on catching a certain class of errors just because of a technically-okay but extremely uncommon behavior.
For example:
function foo(value: string | number) {
  if (value instanceof Number) {
    // oops - never runs!
  }
}

Can you provide more details on why you want this behavior?

It's true that it's not a common pattern, and probably anyone doing it is abusing the language, but it's part of the spec and all runtimes support it.
I'm really not eager to have this fixed, and I perfectly understand if it's not prioritised or even if it gets closed. I just identified that this is actually valid JS, yet TS will not allow it, giving back an error that's actually incorrect. The left-hand side can be any value.

I would hate to miss out on catching a certain class of errors just because of a technically-okay but extremely uncommon coding patterns.

Fixing this doesn't mean removing the error altogether, which I agree it's very useful. A possible fix would be to allow for any type of value as long as the right-hand side is an object with Symbol.hasInstance.

I just identified that this is actually valid JS, yet TS will not allow it, giving back an error that's actually incorrect.

This isn't really the bar for what TS has to do. Math.max("hello", "world") is "valid" JS but it's still an error.

A possible fix would be to allow for any type of value as long as the right-hand side is an object with Symbol.hasInstance

But Number does have a Symbol.hasInstance property, which TS correctly models, and it returns sensible results for all inputs, so is modeled as taking any.
If this issue is just a "looking for problems and successfully finding one" thing then I think we should just close rather than spend time investigating possible options.

I just identified that this is actually valid JS, yet TS will not allow it, [..]

I mean, the very point of TypeScript is to prevent "valid" JavaScript.

This isn't really the bar for what TS has to do. Math.max("hello", "world") is "valid" JS but it's still an error.

There's a big difference though, which is that Math.max in this case will always return NaN. It was not meant to work with strings.
Now, if the spec for Math.max also included strings, or allowed some kind of configuration that would allow it, so that it returns the string furthest down the alphabet ("world") in this case, should TS forbid using strings because it says Math in it and it wasn't originally meant for that?
This is my point. The original example with even numbers is a valid case for hasInstance, if someone prefers the style for whatever reason. I could actually find a "divulgative" article of someone using them to check on primitive types.
Maybe another point of TS doing a good job that's actually a better one is in the following:
function foo() {
  return 3
}

if (foo) {
  // ....
}

Of course it's valid JS, yet TS will show an error. But this is because TS knows that the if is completely redundant, and nothing will change it. It knows how it's completely impossible for foo to be falsy, and being a function it will tell you "hey, did you meant to call it"?
But again, the big difference here is that EvenNumbers actually works, and gives you an expected result. For me, this error would be more suitable for a linter. Or the class of errors that TS reports when e.g. noFallthroughCasesInSwitch or noImplicitOverride is on (which IMO, Typescript compiler shouldn't really have because this should actually be the job of a linter)
I feel like I'm playing devil's advocate here. This is never a pattern I will find acceptable to use other than in playgrounds / experimental esoteric stuff. Feel free to reopen it if you actually see value in it, or someone comes with a non-contrived use case.


Rewrite tests with hypothesis

This pull request will improve the tests' quality by using the hypothesis library.
Progress:

[x] _test_printer
[x] test_customtype
[x] test_dict_struct
[x] test_list_struct
[x] test_str
[x] test_structure_check
[x] test_tuple_struct

Fixes issue #13

The same goes for some tests in test_list_struct.py. I'd like to get rid of them.

Done, please tell me if the tests I mentioned above can be deleted. After that we can consider the work done, I think.

@carlbordum You see, with the printer tests we do something like this:
assert pformat(dct) == '{a: int, b: str}'
In Python 3.5 and less it is not guaranteed that the order of keys will be the same, so this validation will fail because of this:
assert '{b: str, a: int}' == '{a: int, b: str}', which is obviously False, but that doesn't mean that the printer failed to do its job.
Because of that, I'd leave out Python 3.5 in tests, it's not like it makes a huge difference in the sense of test coverage.
As for the other things, I've addressed them in the recent commits to master.


fix: old deck reveal issue

Description
Fixed reveal issue for old decks and displaying no questions card for old decks.

@marvinmarnold can you please review this pr?

Can you provide instructions for testing this PR? I don't remember it exactly.

@marvinmarnold I just updated the PR description.


Use base image : openjdk-11

@NikishaPatil Did you mean to close the PR without merging?

I will raise a new PR as it has some conflicts


Add auth

https://www.authelia.com/integration/proxies/traefik/
https://www.authelia.com/configuration/methods/environment/
https://github.com/authelia/chartrepo/blob/master/charts/authelia/values.yaml
https://www.authelia.com/integration/proxies/traefik/
https://geek-cookbook.funkypenguin.co.nz/docker-swarm/traefik-forward-auth/ (based on authelia)

Ended up using https://github.com/lldap/lldap due to its simplicity and postgres storage backend


Radar unlocked twice

Radar is unlocked by both Radars and Military.

Although this is marked as part of the 0.5.13 milestone and closed as completed, it doesn't seem to have found its way from the dev branch to main and is not actually fixed in 0.5.13.

It's part of 0.5.14 which hasn't been released yet. Main branch should always match what is on the mod portal.


[Bug]: Page generated with data should be deleted when the datasource is deleted.

Is there an existing issue for this?

[X] I have searched the existing issues

Description
If there is a page generated wit data for a particular datasource, the page should be deleted if all its queries are deleted and the user deletes the datasource itself.
Steps To Reproduce

Create a datasource, Say Postgres
Use Generate page with data to auto-generate a page
Delete the queries related to the Auto-generated page
Now, Delete the datasource
Observe - The datasource get deleted, but the Auto-generated page still exists

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
1.9.12

No it should not. The page is independent of the datasource and queries and deleting one should not delete the other


[core] Fix Regular Expression Denial of Service (ReDoS) vulnerabilities

Fixes https://github.com/mui/material-ui/issues/44078

[x] I have followed (at least) the PR section of the contributing guide.

A comment above the changed regular expressions would be enough, I wouldn't add tests specifically for a DOS attack. We could add a link to a example of how it can be tested.

Modified as described above, removed the tests and added comment descriptions, not sure how you want to add the link? I think the 4 PoCs in issue https://github.com/mui/material-ui/issues/44078 are good enough as examples.
PoC_1.zip
PoC_2.zip
PoC_3.zip
PoC_4.zip


Update front page search bar

Move search bar out of the header and make prominent on the home page with placeholder text “Find help…”.

https://github.com/mozilla/kitsune/projects/3


Allow bibliography to follow heading with id of "refs"

(Follow-up to conversation in the group.)
Currently the bibliography can be moved from its default location at the end of a file, to somewhere else by the inclusion of a div with an id element of refs.
Since it's possible to give an id to a heading and since bibs are often introduced by headings, expand the insertion rule to include any heading with such an id element. This would avoid the use of raw html inside a markdown document and also leverage pandoc's ability to insert such id elements into headings.
So, this markdown heading would have a bibliography inserted after it:
# List of Readings {#refs}
EDIT: To be super clear, the heading level wouldn't matter; so even, e.g., H2 or H3 could signal the start of the bibliography.

Thoughts on this?

I like the idea, I just haven't had time to work on it.

Great.  Thanks for responding.

any progress on that?
I am trying to make pandoc-citeproc work with a complex latex template from my institute.. So an option like that would be highly appreciated...

ping @jgm
could you post some info that could guide a motivated user towards implementing this?

You'd want to look at insertRefs in src/Text/CSL/Pandoc.hs.
The changes needed aren't completely straightforward; let me
know if you get stuck.
+++ Oliver Schneider [Jul 20 17 08:20 ]:

ping [1]@jgm
could you post some info that could guide a motivated user towards
implementing this?
—
You are receiving this because you were mentioned.
Reply to this email directly, [2]view it on GitHub, or [3]mute the
thread.
References

https://github.com/jgm
https://github.com/jgm/pandoc-citeproc/issues/210#issuecomment-316632313
https://github.com/notifications/unsubscribe-auth/AAAL5HD8K_M_8JvUpmjlk4oT1oMWz_pPks5sPw3QgaJpZM4HLBR-


Infinite Recursion Error when trying to deepcopy QuamDict

When one tries to deepcopy the generated configuration object of type QuamBase, they run into a recursion error as seen below:
File c:\Users\Lab\Documents\GitHub\qm-2qb-feedback\qua-qLDPC\Lib\site-packages\quam\core\quam_classes.py:744, in QuamDict.__getitem__(self, i)
    [743](file:///C:/Users/Lab/Documents/GitHub/qm-2qb-feedback/qua-qLDPC/Lib/site-packages/quam/core/quam_classes.py:743) def __getitem__(self, i):
--> [744](file:///C:/Users/Lab/Documents/GitHub/qm-2qb-feedback/qua-qLDPC/Lib/site-packages/quam/core/quam_classes.py:744)     elem = super().__getitem__(i)
    [745](file:///C:/Users/Lab/Documents/GitHub/qm-2qb-feedback/qua-qLDPC/Lib/site-packages/quam/core/quam_classes.py:745)     if string_reference.is_reference(elem):
    [746](file:///C:/Users/Lab/Documents/GitHub/qm-2qb-feedback/qua-qLDPC/Lib/site-packages/quam/core/quam_classes.py:746)         try:

RecursionError: maximum recursion depth exceeded

This error specifically  is raised within the Bakery class provided by QM. The source of this error is due the way __getattr__ and __setattr__ are implemented, leading to infinite recursion when deepcopy attempts to copy the attributes of the object.
A very quick fix to this issue is the following modifications to the __getattr__ and __setattr__ functions within the QuamDict class:
    def __getattr__(self, key):
        if key in ["data", "_value_annotation", "_initialized"]:
            return self.__dict__[key]
        try:
            return self[key]
        except KeyError as e:
            try:
                repr = f"{self.__class__.__name__}: {self.get_reference()}"
            except Exception:
                repr = self.__class__.__name__
            raise AttributeError(f'{repr} has no attribute "{key}"') from e

    def __setattr__(self, key, value):
        if key in ["data", "parent", "config_settings", "_initialized", "_value_annotation"]:
            self.__dict__[key] = value
        else:
            self[key] = value

Thanks for raising this, I'll go ahead and investigate it. Do you have a code example that could reproduce this error?

Hi, sure, something like:
local_config = copy.deepcopy(config)
for a config object as attached
old_config.txt

Hi @melmatt7 I seem to be unable to reproduce the error. The config file you sent is of the qua config, not QuAM. Could you share the JSON file which results from QuAM.save()? Or alternatively the code you use to generate the QuAM structure?

@melmatt7 I'm closing this issue due to inactivity, please reopen if it's still an issue


Remove .intersect from AxisAlignedBoundingBox and BoundingSphere

For 1.13 release. Closes #2807. @pjcozzi

You have two failing tests:

Also, update CHANGES.md.

Thus proving it only takes 2 weeks for me to forget how to do things.
Fixed.


Added windows testing. Some cleanup.

bitHound failed six files, but it's test files and I'm still working on them.

bitHound failed six files, but it's test files and I'm still working on them.


Timestamps should default now()

This would make a lot of things easier, things like fixtures and SQL inserts would become simpler with this change.

Duplicate of https://github.com/gobuffalo/pop/issues/455 but the issue is still valid.

Oh. I'm circumventing this by using database defaults triggers to set timestamps and I've marked these columns as read-only with rw:"r" tag.


move node-sass-import-once to dependencies

@Addepar/ice

So we actually also import node-sass directly here to do that crazy wrapping thing: https://github.com/Addepar/ice-box/blob/master/index.js#L19
We should also move node-sass to dependencies, otherwise issues could pop up. It won't always happen, but it can


Quest tab filter & sort

Redoing PR #2770 after re-fork
NEW - Add data for quests and add ability to sort quest list

In action: https://streamable.com/0s7pn
The latest commit adds data for individual quests, including their name, type, difficulty, length, quest point reward, and requirements. With this information, quests you can't do because of unmet requirements can now be filtered from the list. (Note: Requirements do not currently consider the ability to boost stats)
The list can also be sorted by difficulty and length. Along with the difficulty and length sorting, users can choose to show the difficulty and length for each quest in the quest list. This is done by placing a colored letter at the start of the quest item name. Difficulty has letters (N - novice, I - intermediate, E- experienced, M - master, G - grandmaster) and length has letters (S - short, M - medium, L - long, V - very long). These values were obtained from the osrs wiki, and simplified so that each fit into one of the given categories.
The plugin is still very configuarable. All combinations of filtering and sorting are functional. To improve the configurability of the plugin, menu options have been added to the quest tab icon so that users do not need to navigate through the configuartion panel to change their settings.

I've made a version of this that doesn't depend on script 1351 -  QuestListItemInit.rs2asm - if that would be preferred. The issue with it though is that the scroll bar does not reflect the size of the list when filtering. I put it on a new branch so that it doesn't affect this PR for now: 6c477ea6f41276c6175a33e2d53605e822893bde

A taste of Hope is not included (new quest)
And if you change the filtering by rightclicking the quest icon, it doesn't set the checkmarks at the plugin settings. When I exit the client and start it again, the checkmarks are there and my quest filtering is as I had left it before logging out.
Quest filtering wise it is perfect. I'm a lvl39  ironman with around 1000 total so i don't meet the requirements for half the quests. I checked all the quests that came up with the "hide can't do" option set and it's 👍 👍 👍
Great plugin. I hope someone will review your code soon so we can see this added to the client asap

Looks very cool, especially useful for ironmen, hopefully gets merged soon!

A subset of this functionality was added in #8306 . Rebase+reopen with the other functionality and we can discuss that then.


Fault tolerance with conflicting destinations

Added fault tolerance when the server already has a subscription with conflicting Destination field.
The check happens before sending and not as response to an error, as the the responses from the BMC seem to vary between version/manufacturers, making parsing it trickier.

Is this ready to land ?


offline inventory enderchest

This issue was originally submitted by @02Miki in SpongePowered/SpongeForge#2281.

Idk if this is the right section, couldn’t create a new ticket in pull requests; can you add offline inventories for enderchest, like the same thing you did with player inventories

I moved the method from Player to User in API8
Maybe API7 too? @gabizou @Zidane

So being on User means the User would already be loaded right? There's no need to make like, an async request or something because they want offline access?

For Player nothing changes.
For User the inventory is loaded lazily when you request it.
Making changes to it marks it as dirty.
Dirty users are saved eventually but before the player joins.

request the user, or request the inventory?

User nbt is loaded into memory before.


Update CHANGELOG for docker.io fix

Fixes #1566.

Oh, should we update the jib-core log as well? Or was this a plugin-side change? I don't remember.

Oh, should we update the jib-core log as well?

Ah, good catch. Will update that.


[FT][Growth 1164] reduce gif quality

Issue #, if available:

GROWTH-1164
Added Support to reduce gif quality in SIH
Also added local compile support using docker
Description of changes:

Checklist

[x] :wave: I have added unit tests for all code changes.
[x] :wave: I have run the unit tests, and all unit tests have passed.
[ ] :warning: This pull request might incur a breaking change.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I would like for you to ensure that Product approves this change before it is deployed.

Yup done


add timestamp operator

Added timestamp operator.
Please, review
Thank you,
Grigoriy

Fixed tests for MSVC and a sample for Clang. Hope it works this time :)

Thank you!


Added EricEngle-NOAA to recipe maintainers

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

Eric is a primary developer of grib2io and expressed an interest in being a g2clib recipe maintainer.

Yes, please add me as a maintainer.


what is the url of admin portal?

I am unable to open admin page

Hello,
You could find it in routes ;)
url is .../admin


Reproduce results for FEDformer with wavelet

Hello,
I tried to reproduce the results of the paper with the mwt block on the traffic data set but was unable to do so. I ran the code with the following args set:

with the addition of "--version Wavelets" and changing the "--features" from S to M. However, the model MSE score reached only about 0.585 after even more than three epochs versus the 0.562 MSE score that was reported in the paper for prediction length of 96.
Are there any other parameters that need to be changed in order to reproduce the performance reported in the paper when using the wavelets?
Thanks in advance!

Turn on the MOE decomposed block will improve the performance. We turn off
it by default to speed up the calculation.
[image: image.png]
On Mon, Oct 24, 2022 at 8:40 PM camerons1967 @.***>
wrote:

Hello,
I tried to reproduce the results of the paper with the mwt block on the
traffic data set but was unable to do so. I ran the code with the following
args set:
[image: Screen Shot 2022-10-24 at 3 35 20 PM]
https://user-images.githubusercontent.com/71870987/197526876-c5030657-7f3e-4d38-b211-4b0acfddc771.png
with the addition of "--version Wavelets" and changing the "--features"
from S to M. However, the model MSE score reached only about 0.585 after
even more than three epochs versus the 0.562 MSE score that was reported in
the paper for prediction length of 96.
Are there any other parameters that need to be changed in order to
reproduce the performance reported in the paper when using the wavelets?
Thanks in advance!
—
Reply to this email directly, view it on GitHub
https://github.com/MAZiqing/FEDformer/issues/32, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3JGOY5EITYENLGEZQNMB3WEZ7SZANCNFSM6AAAAAARM57OJM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Refactor manifest handling around forc-pkg to accommodate virtual manifest files

closes #2893.
This is general refactoring for handling virtual manifest files and preliminary validation for them. For validation we are checking whether all members listed in the workspace are in fact reachable. After this PR we could start to implement logic for actually consuming the collected workspace information.
I will open a separate PR for changes in forc-client in its own repo.

Would love some input whether this is a good approach especially from @mitchmindtree, we could also separate Manifest and VirtualManifest completely rather than merging them in a single enum as different variants. 🤔

Thanks for diving into this @kaya!
It looks like the purpose of the "Virtual Manifest" is to act as a workspace manifest - is that right?

we could also separate Manifest and VirtualManifest completely rather than merging them in a single enum as different variants. thinking

After a quick first look I think this sounds a lot better. Currently in forc our Manifest type is very specific to an individual package. I think we should avoid conflating the package manifest with the workspace manifest and try to separate the concerns best we can.
Maybe we can also:

Rename the existing Manifest type to PackageManifest as it's specific to a single package.
Following suit, rename ManifestFile to PackageManifestFile.
Rather than using VirtualManifest, use WorkspaceManifest to refer to the workspace manifest.

Perhaps we can have a design chat before going any further? I'll message you on slack!

Hey @mitchmindtree, I couldn't decide whether to strip all forc-deploy changes (which is basically utilizing the WorkspaceManifest introduced in this PR to detect and deploy all of the workspace members in the order of their declaration) from this PR since this might still be an improvement for application developers while we are brewing the full workspace support. So leaving this decision up to you and marking this as ready to go!


CATE estimation conditioned on  a confounding variable?

Based on some tutorials, for example :https://microsoft.github.io/dowhy/example_notebooks/dowhy-conditional-treatment-effects.html
It seems to me that CATE is defined w.r.t effect modifiers. The effect modifiers are the ones that affect only to the outcome, eg. X0, X1 variables in the tutorial.
Can we compute CATE conditioned a confounding variable. For example, age variable can affect to the treatment and outcome, and we want to compute the CATE given a specific age range.
Thanks

yes, you can do that. Just add the variable age as both a common_cause and as a effect modifier.


Entropy bits should say 'at most'

The text for 'bits of entropy supplied' should have a warning saying 'at most X bits' since it's easy to supply entropy which has less entropy than the 'raw' numbers may otherwise suggest.

See https://github.com/iancoleman/bip39/commit/e5abab4253217ed2a0d75cb9efd1ffe425b14f85 - Bits of entropy has info about possible weaknesses
Would be better if the tooltip showed instantly on hover, perhaps by using bootstrap tooltip, but for now this is satisfactory.


Detect getters and setters

This rule is telling me I have to write my getters as arrow functions, which is impossible.

Hi, would you mind posting an example code snippet? These are the existing tests for getters/setters that are passing:
const foo = { get bar() { return "test"; } }
const foo = { set bar(xyz) {} }
class foo { get bar() { return "test"; } }
class foo { set bar(xyz) { } }

@TristonJ You're right it is actually detecting some getters/setters, but not this one:
  Object.defineProperty ( window, 'foo', {
    get () {
      return 123;
    }
  });

Thank you for the additional details @fabiospampinato. It looks to me like it is correctly reporting an error in that specific case. In your snippet, we are actually defining a property called get on an object that is passed into Object.defineProperty.
You can re-write that snippet of code as js Object.defineProperty ( window, 'foo', {     get: () => 123 }); which is entirely valid syntax.

Oh you're right! 🤦♂ Thanks!


Design Breaks

Path: Administrative Case >Search
Issue: Field Name and Button position is not correct,alignment is not correct. It breaks the design.

Since Bangla characters are a bit wider than English characters. So a little design issue will always be there.


Add Astra DB vector store implementation

Description
This adds support for Astra DB as vector store.
Checklist

[x] I have tested these changes locally.
[x] I have reviewed the code changes.
[ ] I have updated the documentation (if necessary).
[ ] I have added appropriate unit tests (if applicable).

@microsoft-github-policy-service agree company="DataStax"

Rebased to fix conflict.
@AlonsoGuevara @jgbradley1 is it possible to review this PR ?


data: non standard tags and subfields removal

Removes non standard tags and subfields.
(addresses inveniosoftware/invenio-marc21#3)

LGTM :shipit:

Actually, no, @hachreak could you please squash all into one commit :)
Then we can merge it.


How to provision an custom image and make use of user_data

Hello, I am building a custom image using Packer that I later want to provision with Terraform and make use of user_data when provisioning with Terraform.
However, seems the user_data has no effect when provisioning with Terraform.
Any way to get this to work?
Packer
We have something liek this for packer:
packer {
    required_plugins {
        upcloud = {
            version = "v1.2.0"
            source = "github.com/UpCloudLtd/upcloud"
        }
    }
}

source "upcloud" "vault" {
  username = "${var.username}"
  password = "${var.password}"
  zone = "fi-hel1"
  storage_name = "Debian GNU/Linux 11"
  template_prefix = "deb-hashi-vault"
}

build {
  sources = ["source.upcloud.vault"]
  // ... more provisioning stuff here
}

Terraform
And something liek this with Terraform:
resource "upcloud_network" "private_network" {
  name = "example_private_net"
  zone = "fi-hel1"

  # router = upcloud_router.example_router.id

  ip_network {
    address            = "<IP_ADDRESS>/24"
    dhcp               = true
    dhcp_default_route = false
    family             = "IPv4"
    gateway            = "<IP_ADDRESS>"
  }
}

resource "upcloud_server" "vault" {
  hostname = "vault-server"
  zone     = "fi-hel1"
  plan     = "1xCPU-1GB"

  template {
    # uuid of packer built image
    storage = var.custom_image
    size = 25
  }

  network_interface {
    type = "public"
  }

  // Simple user_data test
  user_data = "#!/bin/bash\ntouch /tmp/test.txt"
}

user_data does not work in a custom image unless you have specifically implemented it into your custom image. E.g. if you use our public template for Debian, user_data should work normally.
Are you handling the user_data field somehow in your image, or is your image based on one of our public templates by any chance? If you need to implement this into your custom image, you could for example try with cloud-init & our metadata API. UpCloud has a small tutorial for the metadata API: https://upcloud.com/community/tutorials/upcloud-metadata-service/ . The metadata API needs to be enabled on server creation.
Let me know if this helps :blush:

Thanks for the reply.
The base image for packer is one of your public templates Debian GNU/Linux 11, so this should work, right?
Do you need anything to reproduce this? I think my example should be pretty complete to reproduce it.
I also tested cloud-init with one of your public Debian images but wasn't sure what would need to be configured to make that work... It would be preferable if cloud-init could be "enabled" when using packer but I don't know the internals of all this, only have experience using cloud-init with other clouds. So if you have some pointers that'd be awesome!

Ahh, yeah, at least I was under the impression that it should work 😲  Weird! 😄  I will ask some UpCloudians if they know what's up & if someone could investigate this more deeply.

Hi @jlarfors
user_data is not exactly supported for custom images. However if the custom image is based on UpCloud official template, you could get this to work by:

Installing (or updating) cloud-init v21.1+
Removing /var/lib/cloud directory (to make sure cloud-init runs on the next boot)

The caveat with Debian 11 template is that there isn't a recent-enough cloud-init version available in main repository, so to get it working you might need to built cloud-init from source, or install from testing (which might have some side effects, so it's not really optimal production setup).
The following packer config worked for me:
packer {
    required_plugins {
        upcloud = {
            version = "v1.2.0"
            source = "github.com/UpCloudLtd/upcloud"
        }
    }
}

source "upcloud" "vault" {
  username = "${var.username}"
  password = "${var.password}"
  zone = "fi-hel1"
  storage_name = "Debian GNU/Linux 11"
  template_prefix = "vault-image"
}

build {
  sources = ["source.upcloud.vault"]

  provisioner "shell" {
    inline = [
      "cp /etc/apt/sources.list /etc/apt/sources.list.bak",
      "echo 'deb http://deb.debian.org/debian/ testing main' >> /etc/apt/sources.list",
      "apt-get update",
      "DEBIAN_FRONTEND=noninteractive apt -y install cloud-init=21.4-1",
      "rm -rf /var/lib/cloud",
      "cp -f /etc/apt/sources.list.bak /etc/apt/sources.list",
      # ... more provisioning stuff here
    ]
  }
}

And then with Terraform:
resource "upcloud_server" "vault" {
  hostname = "vault-server"
  zone     = "fi-hel1"
  plan     = "1xCPU-1GB"
  metadata = true

  template {
    # Custom image based on Debian 11
    storage = var.custom_image
    size = 25
  }

  network_interface {
    type = "public"
  }

  login {
    keys = [
      "my-ssh-pub-key"
    ]
  }

  // Simple user_data test
  user_data = "#!/bin/bash\ntouch /tmp/test.txt"
}

Note that metadata has to be allowed for the server for this to work.
Please also note that default cloud-init config disables root login and creates a debian user instead. So to be able to log into the server properly, you might need to tweak the /etc/cloud/cloud.cfg file for your custom image. I took a shortcut and set the SSH key via Terraform login block (which just works for debian user, but is not exactly optimal).
I hope this clears things out a bit, let us know if you have any other questions :)

Has there been any work on supporting user_data with custom images without doing strange hacks on the image size?
In our case we are just using the API. The API documentation describes metadata and user_data and it seems to imply that you just need to specify "metadata": "yes", "user_data": "<script>" to have the script run by root at initialization time, but this ticket seem to imply you actually have to SSH into the node, do some hacks and reboot to have cloud-init run the script?
We want to get rid of all SSH connections as root to our VMs for security reasons so that's not good enough for us.

I also haven't tried with Packer, but I can confirm user_data works with custom images in UpCloud API, if the custom image is built from one of UpCloud's more recent templates with cloud-init built-in! :) Need to use the cloud-init config (more examples: https://github.com/canonical/cloud-init/tree/main/doc/examples) with these.
I've personally used UpCloud's Debian 12, Ubuntu 22 and Ubuntu 24 templates to create the custom image, and then supplied user_data with a custom cloud-init config when creating a server from the custom image. That has worked for me nicely
For example, here's what I've supplied to the UpCloud API to create an app user with access to docke on server creation with my custom image:
{ "server": {
  ...
  "user_data": "#cloud-config
users:
- name: app
  groups: docker
  shell: /bin/bash
  ssh_authorized_keys:
    - ${SSH_KEY}"
}

Sorry, we are not actually using packer, I just thought that the underlying problem is the same we are having by pushing images directly via the UpCloud API.
We are building from scratch our images, we use the http_import functionality to copy the raw images to a storage from some bucket and then templatize it. So is this already supposed to work as you say? The templatize operation does not allow to specify a template_type: cloud-init AFAIK.

Yeah, I haven't used Packer lately either 😊
If you are using http_import then I'd suggest to try to add a cloud-init setup to the custom image. The cloud-init setup needs to match exactly as they are in UpCloud's own templates. Might be difficult to get it right. Easiest way to do this is to create a new custom image from UpCloud's Debian 12, Ubuntu 22 or Ubuntu 24 -template. Or try deploying one of those templates and copy & modify relevant bits from there into your custom image 😅
Note also that you need to have metadata enabled when you create the server.


Display Database Content and Run SQL Queries

Tutorials: https://developers.sap.com/tutorials/abap-display-data-queries.html
Hi,
I am unable to view data in Eclipse with ABAP Could Project - SAP BTP trial account. Error 'No authorization to view data'.
(Step 2: Select a database table.)
Please suggest how to add authorization.
Regards,

Requesting for suggestion.

Hi,
You need to fulfil the prerequisite: "You have a valid instance of an on-premise AS ABAP server, version 7.51 or higher "
You may not be able to do this tutorial on SAP BTP ABAP Environment.
BR Julie.

Hi Maulik, Try a different table: Search for /DMO/CUSTOMER.
BR Julie.


fix(DataStore): Cascade delete sync from children to parent models

Issue #, if available:
Description of changes:
Change the logic to align with JS's logic to "syncDeletions from children to parent" from previously "sync deletions from parent to children". And added unit testing around CascadeDeleteOperation
Check points: (check or cross out if not relevant)

[x] Added new tests to cover change, if needed
[ ] Build succeeds with all target using Swift Package Manager
[x] All unit tests pass
[ ] All integration tests pass
[x] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[x] PR title conforms to conventional commit style
[ ] ~If breaking change, documentation/changelog update with migration instructions~

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1731 (ae815e5) into fix/cascade-delete-2 (cabd9bf) will increase coverage by 5.02%.
The diff coverage is 88.67%.

@@                   Coverage Diff                    @@
##           fix/cascade-delete-2    #1731      +/-   ##
========================================================
+ Coverage                 53.28%   58.31%   +5.02%
========================================================
  Files                       623      666      +43
  Lines                     16163    20563    +4400
========================================================
+ Hits                       8613    11992    +3379
- Misses                     7550     8571    +1021

Flag
Coverage Δ

API_plugin_unit_test
62.51% <ø> (ø)

AWSPluginsCore
?

Amplify
46.86% <ø> (-0.02%)
:arrow_down:

Analytics_plugin_unit_test
71.76% <ø> (ø)

Auth_plugin_unit_test
78.74% <ø> (ø)

DataStore_plugin_unit_test
75.53% <88.67%> (?)

Geo_plugin_unit_test
52.12% <ø> (ø)

Predictions_plugin_unit_test
26.81% <ø> (ø)

Storage_plugin_unit_test
58.04% <ø> (ø)

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

Impacted Files
Coverage Δ

...ategoryPlugin/Storage/CascadeDeleteOperation.swift
75.47% <88.67%> (ø)

.../DataStore/Model/Internal/Schema/ModelSchema.swift
64.00% <0.00%> (-2.00%)
:arrow_down:

...ore/AWSPluginsCore/Auth/AWSAuthorizationType.swift

...PluginsCore/Sync/ModelSync/ModelSyncMetadata.swift

.../Auth/Provider/AmplifyAWSCredentialsProvider.swift

...luginsCore/Model/Decorator/AuthRuleDecorator.swift

...ync/MutationSync/MutationSyncMetadata+Schema.swift

...uginsCore/Model/Support/GraphQLDocumentInput.swift

...sCore/Model/Decorator/DirectiveNameDecorator.swift

.../Configuration/AWSAuthorizationConfiguration.swift

... and 135 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

Will merge this and https://github.com/aws-amplify/amplify-ios/pull/1730 together to main in this PR, and close out https://github.com/aws-amplify/amplify-ios/pull/1730 which has been reviewed


Updated test to JUnit5 to remove reference to Dialect subclass

Moved it back for now to the old location, since it fails with a (probably)
non-related error that will have to be looked at as soon as there is an
implementation for composite sub-types
Signed-off-by: Jan Schatteman<EMAIL_ADDRESS>

Thanks!


Revert "[opt] remove trivially dead instructions in mandatory combine"

Reverts apple/swift#30429
Testing to see whether this is a cause of SIL failure in source compatibility project Kingfisher.

@swift-ci please test source compatibility

Reverting this PR fixes Kingfisher project failures in debug configuration.

/cc @zoecarver @gottesmm

@swift-ci please smoke test

Looks like there is an unrelated break now related to MovieSwiftUI...

@xedin we tested fairly extensively (source compatibility and device filecheck preset). What's the error?

@zoecarver https://ci.swift.org/view/Source Compatibility/job/swift-master-source-compat-suite-debug/2848/artifact/swift-source-compat-suite/ (Kingfisher fails in 4 configurations).

Hmm I see. It might have somehow removed the destroy_addr. I'll play around with it a bit and see if I can make a reproducer.

Looks like the kingfisher build is now succeeding. Still no reproducer but, it was something to do with one of the enum operators.

@xedin I'll keep trying to debug why the crash happened but I'm beginning to suspect it wasn't this commit, actually. When building Kingfisher from master, it doesn't crash anymore but, when I checkout a5d1214220b8ddf29acf7c08c8bb42993ed56c54 and try to build I get the crash. Anyway, as I said, I'll keep trying to figure out what the cause is.

Ignore the last comment. I tracked down the issue, it was this commit (oops). Here's the following pattern that we incorrectly remove (unchecked_take_enum_data_addr):
%96 = alloc_stack $KingfisherOptionsInfoItem    // users: %111, %105, %98, %97
  copy_addr %13 to [initialization] %96 : $*KingfisherOptionsInfoItem // id: %97
  %98 = unchecked_take_enum_data_addr %96 : $*KingfisherOptionsInfoItem, #KingfisherOptionsInfoItem.downloadPriority!enumelt // user: %99
  %99 = load [trivial] %98 : $*Float


Update MNIST Colab notebook and its output models.

As part of this, I'm moving the full model with its weights (800KB) to iree/samples/models/ and removing the check lines from it. I'm keeping a version with dummy weights in iree/test/e2e/models/ for test coverage. These files should still be updated by running the notebook, not by direct edits.

looks good to me.

Thanks! Can you add a note that we should really figure out a way to not check this into source? The best note would be a link to an issue :-P

That's mentioned in the new README:
Note: Models placed here should be small enough to be stored comfortably in git.
If a model file has large weights, please store those outside of git and fetch
them on-demand.

(we don't actually have a way to do that yet though :P)


Fixed get_status to correctly assert if remote result file exists

[x] I have added the tests to cover my changes.
[x] I have updated the documentation, VERSION, and CHANGELOG accordingly.
[x] I have read the CONTRIBUTING document.

Codecov Report
Base: 50.00% // Head: 50.00% // No change to project coverage :thumbsup:

Coverage data is based on head (abbc5dc) compared to base (775fd59).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #43   +/-   ##
========================================
  Coverage    50.00%   50.00%
========================================
  Files            2        2
  Lines          160      160
========================================
  Hits            80       80
  Misses          80       80

Impacted Files
Coverage Δ

covalent_ssh_plugin/ssh.py
49.68% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.