Implement instance-level $validate and enforce mode binding

Is your feature request related to a problem? Please describe.
In #2905 we added partial support for the mode input parameter on the $validate operation.
Specifically, when this parameter is set to create or update, we will validate the passed resource by using the corresponding fhir-server-config settings under resources/<resourceType>/profiles.
However, https://www.hl7.org/fhir/operation-resource-validate.html defines mode with a required binding to https://www.hl7.org/fhir/valueset-resource-validation-mode.html whereas our implementation allows any string that would be a valid code.
Specifically, in addition to create and update modes, it defines:

a profile mode that it says should only apply to a resource "nominated by id, not provided as a parameter"
a delete mode that only makes sense against a previously-ingested resource

But our implementation doesn't even support validation against existing resources in the db.
If you try invoking it at this level, it fails with a 400 Bad Request error that says:

"Input parameter 'resource' is required for the $validate operation"

Describe the solution you'd like

Support (and advertise support for) resource-instance level $validate (at [base]/[resourceType]/[id]/$validate)
Ensure that only valid "mode" codes are accepted by the $validate operation... if an invalid code is sent then return a 400 Bad Request with a reasonable error

Ensure delete is only ever invoked at the resource-instance level (although I have no clue when we'd say that a given delete is "invalid"...I guess never?)
I don't understand why profile wouldn't be used when validating a passed resource against a particular profile.  I think this matches our current behavior if the 'profile' parameter is passed in and that seems fine to me.

Describe alternatives you've considered
Acceptance Criteria

GIVEN [a precondition]
AND [another precondition]
WHEN [test step]
AND [test step]
THEN [verification step]
AND [verification step]

Additional context

I found a couple of possible issues:

Minor. If a resource is delete, if you try to delete it again you get 200 OK with an OperationOutcome indicating that the resource is already deleted (the operation is idempotent). However, validate mode=delete will give you a 404 for a resource which is currently deleted. So that's a slight discrepancy.
The validate mode create/update/delete appear to ignore the allowed interactions configuration. For example, I think if we disable delete, then validate mode=delete should also say that the resource cannot be deleted.
Validate mode=create indicates no error when the resource currently exists. I'm struggling with what should be the correct behavior for this one because the spec says: "and then checks that the content would be acceptable as a create (e.g. that the content would not violate any uniqueness constraints)"
With updateCreateEnabled set to false, the validate mode=update operation reports NoError even when the resource does not exist
Validate mode=create shows no error if no resource parameter value is provided.
Validate mode=update shows no error if no resource parameter value is provided.

In addition, during team discussion we agreed that the validation should always be on the resource provided in the incoming content.

GIVEN fhir-server-config disallows a particular interaction type (e.g. create)
WHEN $validate is invoked with the corresponding mode (create)
THEN a 200 OK is returned with an OperationOutcome with issueType ERROR not-supported

GIVEN fhir-server-config with updateCreateEnabled=true (the default)
WHEN $validate is invoked at the instance level with mode=create
AND the instance is valid
THEN 200 OK is returned with no errors in the OperationOutcome

GIVEN fhir-server-config with updateCreateEnabled=false
WHEN $validate is invoked at the instance level with mode=create
THEN 200 OK is returned with an OperationOutcome with issueType ERROR not-supported

WHEN $validate is invoked at the instance level with mode=create
AND a resource already exists at that endpoint
THEN 200 OK is returned with an OperationOutcome with issueType ERROR not-supported

GIVEN fhir-server-config with updateCreateEnabled=false
WHEN $validate is invoked at the instance level with mode=update
AND no resource instance exists at that endpoint
THEN 200 OK is returned with an OperationOutcome with issueType ERROR not-supported

WHEN $validate is invoked at the type level with mode=create
AND the interaction is allowed
AND the instance is valid
THEN 200 OK is returned with no errors in the OperationOutcome (irregardless of server config)

WHEN $validate is invoked when mode=create or update
AND no resource parameter value is provided
THEN 400 Bad Request is returned with an OperationOutcome that includes information which states the 'resource' parameter is required when mode is create or update

WHEN $validate is invoked at the type level with mode=update or delete
THEN 400 Bad Request is returned with an OperationOutcome that includes information which states the 'resource' parameter is required when mode is create or update

profile mode is supported at both levels?

Failing AC2. With fhirServer/persistence/common/updateCreateEnabled equal true and Patient ValAdaDaugherty already existing, the request is failing, contrary to the requirements of AC2:
HTTP/2 200
content-type: application/fhir+json
date: Wed, 31 Aug 2022 10:07:03 GMT
content-language: en-GB
content-length: 585

{
  "resourceType": "OperationOutcome",
  "id": "Error",
  "text": {
    "status": "additional",
    "div": "

ERROR

"
  },
  "issue": [
    {
      "severity": "error",
      "code": "invalid",
      "details": {
        "text": "Patient with id 'ValAdaDaugherty' already exists"
      }
    },
    {
      "severity": "warning",
      "code": "not-supported",
      "details": {
        "text": "Profile 'http://hl7.org/fhir/StructureDefinition/Patient' is not supported"
      },
      "expression": [
        "Patient"
      ]
    },
    {
      "severity": "warning",
      "code": "invariant",
      "details": {
        "text": "dom-6: A resource should have narrative for robust management"
      },
      "expression": [
        "Patient"
      ]
    }
  ]
}

I agree AC2 is underspecified.
2. GIVEN fhir-server-config with updateCreateEnabled=true (the default)
WHEN $validate is invoked at the instance level with mode=create
AND the instance is valid
THEN 200 OK is returned with no errors in the OperationOutcome

should probably be split into the two cases.
2a.  GIVEN fhir-server-config with updateCreateEnabled=true (the default)
AND a resource exists with id=123
WHEN $validate is invoked at the instance level with id=123 and mode=create
THEN 200 OK is returned with an OperationOutcome with severity ERROR and code not-supported
2b. GIVEN fhir-server-config with updateCreateEnabled=true (the default)
WHEN $validate is invoked at the instance level with mode=create
AND the instance is valid
THEN 200 OK is returned with no errors in the OperationOutcome
For AC3, I think the 2 errors is fine.
The first one is saying that it couldn't be created because
The second one is saying that create-on-update isn't supported. Its for this funny case where you invoke $validate at the instance level but set mode=create. We decided that should return an error if create-on-update is not supported.
So "Create for this resource type is supported, but only when the resource currently doesn't exist." is not right.

I've updated the acceptance criteria to break things out a little more cleanly and will post the results here:
AC1: PASS
AC2: PASS
AC3:
AC4:
AC5:
AC6:
AC7:
AC8:
AC9:
AC10:
AC11:


Expose toJSONSerializationValue

Seems reasonable to expose 'toJSONSerializationValue' in case a user wants to create an object that can be serialized with JSONSerialization as part of another process, instead of having to use serialize().
Having that need with Moya right now.

@sprynmr Sorry for the lack of response on this. Do you still think this is an issue? Sounds like you have a particular use for it, but no-one else has indicated the same need.

Closing due to inactivity and the general state of the repo.


Fix ssh cloned git url not matched

Fixes #6

Tested here regexr.com/5dfqa

the proposed regex also captures .git as part of the repo name, which conflicts with how already existing repos and other github integrations operate (as they assume the repo name does not include .git). I suspect having the .git as required doesn't do any harm (since both cloning via https and ssh from github you will have the .git as the origin address on your cloned folder).
@uloco could you please revert that bit so I can merge your PR? I could fix that manually and add this fix via another commit, but it is better if contribution history is kept properly.

Sure. There was already a git suffix in your regex before, so I thought I fixed an issue by making it optional. Too much regex magic for me I guess :D

Sure. There was already a git suffix in your regex before, so I thought I fixed an issue by making it optional. Too much regex magic for me I guess :D

yeah it also took me some head-scratching to realize why it was being captured (making the suffix optional simply allows repo capture group to include the suffix without invalidating the match).

published via<EMAIL_ADDRESS>(you can update by running codedoc update)


Properly exit PhantomJS when running from command line

I added some success and failure handling to quit out of PhantomJS once the specs are done running. This issue was manifesting itself if I ran rake spec:javascript from the command line. Note: I am on a Windows PC, but I don't think that would matter here.
This fixes #155.

I'm still trying to figure out why you're experiencing this and not others

That's fair... I spent a day and a half looking for a configuration issue on my machine because I didn't think it could be a bug - no one else has reported it. But after stepping through the entire code path between jasmine-rails, jasmine, and PhantomJS I couldn't find a place where jasmine-rails actually told PhantomJS to exit. As soon as I added the explicit exit calls then it worked as desired.
Do you recall where these exit commands are supposed to come from?

I should add - running the jasmine specs in the browser works just fine and that is how we've been using it. The reason we need the command line interface to exit is so that we can use the tests on our continuous integration server.

PhantomJS typically exits when the script is finished. I suspect the reason that phantomjs is not exiting is because you have either production code or test code that is leaving something on the event loop that isn't clearing (perhaps a setInterval or a hanging XHR?)?
If you go back and comment out or exclude all your JS code & tests, does this behavior persist? If you try a new empty project on your machine, does the same behavior persist?

I think you're right... I found the specific spec that was hanging. We are using the lodash debounce to avoid making a function call with every key press on a text field that has a $watch. In the spec, it looks like we are trying to override the _.debounce with a setTimeout:
beforeEach inject ($compile, $rootScope) ->
    jasmine.clock().install()
    # override to use fake setTimeout, since lodash is loaded before the fake clock
    _.debounce = (fn, waitMillis) -> return () -> setTimeout fn, waitMillis

Then in an example spec:
 describe 'typing in dates', ->
     it 'updates timeRangeFrom on scope when the date is valid', ->
       ctrl.textRangeFrom = @oct_15_text
       ctrl.textRangeTo = @oct_16_text
       ctrl.$digest()
       ctrl.tick(1000)
       expect(ctrl.timeRangeFrom.valueOf()).toEqual(@oct_15_value)

I'm not in contact with the code author, so I'm not exactly sure what the reasoning is here. I did find this good StackOverflow explanation of how various timeout methods interact with Jasmine.
I have a hunch that the issue here is that the setTimeout specified here is messing with the setTimeout in jasmine-runner.js. That seems like the piece of code that would normally exit PhantomJS:
setTimeout(function() {
    window.callPhantom({
       event: 'exit',
       exitCode: exitCode
    });
 }, 1);

I will try to investigate more and come to a definitive result.

Ah, that certainly makes more sense. I'll close for now unless your issue is broader than we suspect.

I wanted to add what I found here in case anyone else ever runs into this. I needed to do two things to fix the issue. First, the jasmine.clock() was not being uninstalled after use in an afterEach block. So, I needed to add this to the hanging specs:
afterEach ->
  jasmine.clock().uninstall()

The _.debounce was also giving me a little trouble, but for a different reason. The jQuery datetimepicker that we were using was choking when trying to render the calendar. This was causing the specs to fail. I'm not exactly sure why, but since that wasn't at all the unit under test for our specs, I spied on the datetimepicker and returned an empty div.
spyOn($.fn, 'datetimepicker').and.returnValue('

')
With those two fixes, the test suite now executes and exits properly.

Hey Jack, thanks for the follow-up. The in-browser jasmine runner just doesn't handle async (like _.debounce) very well, especially when you don't wrap affected tests in either the 1.x or 2.x async APIs.


fix(data-table-v2): fix the undefined method called when press in escape key

Resolves #674
Description  of the function  _batchCancel called when press in escape key
Added
Removed
Changed
Testing / Reviewing

Hi @asudoh, thank's you for your return, I cann't see too much the relaton with the function  _selectAllToggle()

Hi @rezak-otmani let me try to articulate what I meant - IIUC _batchCancel() is for making all table rows unselected. OTOH _selectAllToggle() is for making all table rows selected or all unselected, depending on the checked status of “select all” checkbox. That’s why I tried to do one-to-one comparison between those, and I see we’ll need https://github.com/rezak-otmani/carbon-components/blob/06f7450cb1ec239e6e7cddd839965bad19bfe469/src/components/data-table-v2/data-table-v2.js#L115 line for _batchCancel(), too. Please don’t hesitate to speak up if you think I’m wrong here - Thanks!

Hi @asudoh thanks for your feedback
IIUC  the contents of _batchCancel()  become the same as the function _actionBarCancel then we can directly call this function instead of declare  _batchCancel().

Thanks @rezak-otmani thank you for your thoughts here! Using _actionBarCancel() directly makes sense to me.


Port from odbc-safe to odbc-api ?

odbc-safe is no longer maintained and suggests using odbc-api which appears to be an easier to use higher level interface.  Has there been any consideration for migrating?  I've poked at it a little and unfortunately it does not look straightforward, but perhaps such a project would simplify ibm_db internals by abstracting more odbc details (and re-align ibm_db with odbc-* future strategy).

Hi @rredburn thanks for pointing this out. Let us look into this and get back to you on it's possibility.


scope~

Guis like sliders and stuff just freeze and don't get updated when calcount is too low - this is because it's too heavy somehow.

see this: https://sourceforge.net/p/pure-data/bugs/1210/
and this: https://github.com/electrickery/pd-miXedSon/commit/38c48e802e102eb8fe98a4af499682a9a0bb0114

another tcl issue is if you create the object in a subpatch and make it 'gop'

show inlets when in edit mode (like we have to do with [comment])
include a receive name
make it resize in every corner

tcl/tk errors / blows up:
when you get into zoom mode while the object is selected, it triggers a tcl/tk code -not sure if we introduced this one.
check "vis"

if the object is resized in a GOP but out of bounds, I also get tcl/tk errors
and Pd blows up if it has signals connected to the object and it is also out of bounds in a GOP...


Crash in phonopy-qha (1.11.2)

Hi Togo,
sometimes a crash can occur with phonopy-qha due to a cv of 0.
This can be fixed (hopefully) with the attached patch file. The error must be catched and treated, but then I dont know if a gamma of Zero is bad or not. Have a look at the patch...
phonopy-1.11.2_iac_rwth.zip

Hi beeck,
Thanks. I applied your patch, 59f9dfd2630e10d8023fc3722f2ff0c3787e8714. I think gamma = 0 is a good choice.


Possible to link to website/blog from readme?

Thanks @fharper for this great initiative.
Thanks for linking to LinkedIn. Is it possible to also link to our website we added? It might help people get a sense, scanning my blog, what I might be helpful with.
🙏🏻

Yeah, it's in my todo list https://github.com/fharper/coffeechat/issues/26, but I just didn't have the time yet to prioritize that.
PR are always welcome :)


introduce "pathMapping" as a more powerful replacement for "remoteRoot/localRoot"

Currently the node/chrome debuggers support two models of mapping paths between the backend/runtime and the VS Code workspace:

Node Debug: "remoteRoot/localRoot"
Debugger for Chrome: "pathMapping"

Since the "pathMapping" supports multiple mappings and users are asking for it, we should support this across the board.
/cc @roblourens

Will pathMapping support wild cards? i.e.
"pathMapping": {
"/src/*/some-folder": "${workspaceRoot}/some-folder/src/"
}
Where the * would be for example a commit id

yes, I think we would go with glob patterns.

I have the same desire. What is the status of this issue?

@connor4312 with the advent of js-debug the old JS debuggers have become obsolete, so I leave it up to you to decide whether there is a need for a generalized path mapping.

This would be a really useful generic feature for remote debugging scenarios or debugging inside of a container where the paths need to be mapped.
At Arm we have implemented this twice in our debug adapters and I see the PHP debug adapter does the same:
https://github.com/xdebug/vscode-php-debug/blob/0a7a83731aa3279f1140f1c626a41da59b04c96e/src/paths.ts
This could be implemented as a nice transform layer for paths as data is passed from VSCode to the adapters and back.


Infer.py function “annotate_sent” has a problem.

The original function has a problem. If "E1" is "the apple" and "E2" is "the banana", "E2" cannot be annotated because of "continue" in "E1" annotation section.
For example, how about "I prefer the banana to the apple."?
E1 == apple ,E2 == banana here.
The word "the" in E2"the banana" wouldn't be recognized instead of detection of E1"the apple".
That's why I changed the function not to avoids the problem. New function is below.
My function may be a bad code and increase execution time, but it can improve E2 detection.
def annotate_sent(self, sent_nlp, e1, e2):
        annotated = ''
        e1start, e1end, e2start, e2end = 0, 0, 0, 0
        for i,token in enumerate(sent_nlp):
            if not isinstance(e1, list):
                if (token.text == e1.text) and (e1start == 0) and (e1end == 0):
                    e1spos=i
                    e1epos=i
                    e1start, e1end = 1, 1
            elif len(e1) == 1:
                if (token.text == e1[0].text) and (e1start == 0) and (e1end == 0):
                    e1spos=i
                    e1epos=i
                    e1start, e1end = 1, 1
            else:
                if (token.text == e1[0].text) and (e1start == 0):
                    e1spos=i
                    e1start += 1
                elif (token.text not in [i.text for i in e1]) and (e1start == 1) and (e1end == 0):
                    e1start = 0
                elif (token.text == e1[-1].text) and (e1end == 0) and (e1start == 1):
                    e1epos=i
                    e1end += 1

            if not isinstance(e2, list):
                if (token.text == e2.text) and (e2start == 0) and (e2end == 0):
                    e2spos=i
                    e2epos=i
                    e2start, e2end = 1, 1
                    continue
            elif len(e2) == 1:
                if (token.text == e2[0].text) and (e2start == 0) and (e2end == 0):
                    e2spos=i
                    e2epos=i
                    e2start, e2end = 1, 1
                    continue
            else:
                if (token.text == e2[0].text) and (e2start == 0):
                    e2spos=i
                    e2start += 1
                    continue
                elif (token.text not in [i.text for i in e2]) and (e2start == 1) and (e2end == 0):
                    e2start = 0
                elif (token.text == e2[-1].text) and (e2end == 0) and (e2start == 1):
                    e2epos=i
                    e2end += 1
                    continue
        for i,token in enumerate(sent_nlp):
            if i == e1spos:
                annotated += ' [E1]'
            if i == e2spos:
                annotated += ' [E2]'
            annotated += ' ' + token.text + ' '
            if i == e1epos:
                annotated += '[/E1] '
            if i == e2epos:
                annotated += '[/E2] '

        annotated = annotated.strip()
        annotated = re.sub(' +', ' ', annotated)
        return annotated

Thanks, this is for inference. Appreciate if you could send a PR


About training data of embedding

Hello. I see that in the toy_data of embedding, each query have several negative samples, while when I download MEDI2 (parquet), each query has only one negative sample. I want to know which setting is used for training? The MEDI2.parquet can be directly used for training, or I should take additional actions?

We use only one hard negative during training. This is controlled via --train_group_size 2 where if it is 2 then only 1 hard negative will be chosen. You can directly use it for training.

OK, I just notice this option. Thank you for your kind reply.


Double the read-only cache's cache line width

Increase the read-only cache's line width and the number of supported address regions.

[ ] The latest version of Verible seems to screw up the formatting of structs that have comments in them and introduces a lot of whitespace changes. Which version of Verible are you using? Does someone have the CI's version 0.0-807-g10e7c71 working at ETH? Because this version does not work on my machine...

That should be better documented:
https://github.com/pulp-platform/snitch/blob/9be73c476e6667299eb3df14f6bfd25fff5d1fe4/.github/workflows/lint.yml#L10

Thanks, I saw that the CI uses this version, but it didn't work on my machine initially. I got it to work now and all the whitespace changes are gone.
And yes, the only 'real' change is in the occamy_cfg.hjson, the rest is generated and that worked fine.


Allow config for showing letters under keypad numbers

@davec proposed:

See image of an example security alarm keypad here - https://goo.gl/images/8fKdwb 24
I was trying to suggest that like a PIN number for your credit card you may use a word that translates to numbers on a keypad, such as you would find on some alarm panels and most phones.
Your access card is still a sequence of numbers, the letters on the buttons are simply a reminder of what key is what letter.

I have refactored the code I wrote to be able to show alpha. Work to do to actually show them. Needs some HTML and CSS to do so. On my github repo.

@gwww would you be ok to merge the two cards?

Yes, please merge

@gwww have a look here: https://github.com/ciotlosm/custom-lovelace/tree/alarm_refactor/alarm_control_panel-card

hi have input the files in WWW folder and on lovelace ui yaml i have this :+1:
name: My Awesome Home

resources:
  - url: /local/monster-card.js?v=1
      type: js
  - url: /local/gauge-card.js?v=1
      type: js
  - url: /local/thermostat-card.js?v=1
      type: js

views:
    # The name of a view will be used as tab title.
    # Might be used for other things in the future.
  #- name: Home
  ######################################################################################################################  Home
  - title: Home
    icon: mdi:home-assistant

but love lace don't start, says "reload ui-lovelace.yaml"
what i'm doing wrong?
best regards

@vuiperez Please follow lovelace docs to get started with lovelace, and then go through the FAQ here: https://github.com/ciotlosm/custom-lovelace/blob/master/README.md#faq to get more things setup.
Bust first thing is to follow official docs (https://www.home-assistant.io/lovelace) and have a working lovelace UI.


From where can I get Turbotax phishlet for evilginx2 plz

DO NOT ASK FOR PHISHLETS.
DO NOT ASK FOR HELP CREATING PHISHLETS.
DO NOT ASK TO FIX PHISHLETS.
DO NOT ADVERTISE OR TRY TO SELL PHISHLETS.
EXPECT A BAN OTHERWISE. THANK YOU!
REPORT ONLY BUGS OR FEATURE SUGGESTIONS.

icq: @loggerjacky


Incorrect inclusion due to header file name clash

./mbed-os/core/hal/api/critical.h clash with an header file in an external module https://github.com/ARMmbed/atomic-queue/blob/master/source/critical.h.
./mbed-os/core/hal/common/Ticker.cpp includes the wrong file without warning. Fail to find symbols.
This is a common scenario and there should be a strategy in place in mbed tools to avoid these situation from happening.

yes, we could rename it, prefix core_util as API is, to overcome this. As it's already used by some software, we could do a warning in the current critical.h for some period of time to enable users to start using a new one. However , this is just one file, we got more in the code base and renaming does not look as a backward compatible solution :sob:
One would be to use absolute paths that would work outside of mbed lib (mbed library is flatten aka all headers from common/api are in mbed folder - something we can consider changing or start using as mbed/critical.h).
any suggestions welcome.

I think to solve the problem once and for all. Compile mbed-os into a library, expose only the API headers to outside mbed-os. Properly namespace the API headers, for C as well as CPP.

To solve this problem, the files in each directory need to be compiled separately, so that local includes always take precedence.
Include order must also be different for each directory. For example, suppose I have four 3rd party libraries: a, b, c, d. a depends on b::foo, and c depends on d::foo. If the include order is wrong, then there will be more faults like this.

@screamerbg @mjs-arm @sg-

To solve this problem, the files in each directory need to be compiled separately, so that local includes always take precedence.

Include order must also be different for each directory. For example, suppose I have four 3rd party libraries: a, b, c, d. a depends on b::foo, and c depends on d::foo. If the include order is wrong, then there will be more faults like this.

How to enforce this in the IDEs? They provide options to change project settings for a virtual folder or a file. that would mean that each directory or a separate module would need to be in its own virtual folder with own settings. I know that IAR and uvision support overriding settings per file/virtual folder, not sure about the rest of IDEs.

When each module is built separately, this is the responsibility of the module developer to ensure the correct include order. When all modules are built together, it is the responsibility of the build tool to answer this question.

When you try to support multiple build systems, you cannot expect all of the features of the build systems to match up perfectly. This is not the reason for keep mbed minimal. Just because uvision ignores this problem, does not mean that we should. If mbed offers more features than uvision, how is this a problem?

@LiyouZhou I don't think it's as simple as that - we want mbed to be as useful to as many people as possible - there's a balance between features and availability of tools - lots of developers like using uvision and if they can't use mbed with it, they might not use mbed at all. I think we need to keep 'core' behaviour working in our main export IDEs and there can be some features/niceities/extra tools that are specific to each IDE.
I think the problem this bug is discussing is large enough that we need to find a solution that works across the tools.
It's worth noting that the behaviour you describe is more-or-less what happens with the online IDE's .bld files at the moment, so not out of the question to extend to other tools.
@sg- and @0xc0170 and @screamerbg - we'll need to work out some mechanisms for this

Header files need to be name spaced to avoid collision, build tools won;t save you.  There are are two approaches to name spacing:

#include "foo/bar.h"
#include "foo_bar.h"

We are already, so far as I can see, already heading down route 1)

Header files need to be name spaced to avoid collision, build tools won;t save you

+1.

The other issue here to keep in mind is that (I suspect) Liyou and Brendan may be seeing this problem while building software that actually needs to be widely portable to many platforms (i.e. update client).
Build tool centric work arounds for name space collision won;t help from a portability perspective. Portable code needs to make sensible decisions about namespace pollution.

@mjs-arm
I don't see how this can save you from incorrect include order in 3rd party modules. This was a failure caused in a local include.
Supposed I have:
module_a/foo.h
module_a/foo.c:
#include "foo.h"

module_b/foo.h
module_b/foo.c:
#include "foo.h"

The build tools must not break this

Third party software integrated into the tree is not exempt from managing their name space pollution.

Third parties are only subject to this requirement if they explicitly support mbed OS. This will be limiting for our users when they want to incorporate third-party software.

@bremoran this issue is not unique to mbed-os.  Managing name space is a problem that everyone writing code with the objective of portability needs to face up to. Code that is developed that does not manage  its namespace effectively is inherently not portable.  The two options  I listed above are not mbed-os centric solutions, they are off the shelf standard practice and have been since the dawn of time.

Writing portable C:

Externally facing APIs and files should be namespaced.
Internal APIs not marked static should be namespaced if static linking is expected

Include files that are only for local use should not be exposed to the include search path. This also is standard practice since the dawn of C (I won't claim time on this one). For example, see the omnipresent config.h.

Hi everyone, this discussion has settled a bit, so I'd like to get a set of naming guidelines in place to give this issue resolution. I'm going to toss out a proposal based on what exists in the current codebase, feel free to criticize and discuss.

Modules
First thing to note, even as one codebase, mbed is composed of a set of modules (hal, rtos, nsapi, lwip, nanostack, uvisor...). Each module should have a unique name to avoid naming conflicts with other modules. No other folder in the codebase should share a name with a module to avoid include conflicts.
Files
All includes must have the path from the containing module to properly namespace header files. For example rtos/Thread.h or hal/api/DigitalIn.h. This is the 1st option pointed out by @mjs-arm and matches the include pattern used in mbed 3. Internal module headers must also include this namespace.
Having the build system architected such that internal module headers are correctly included would be nice for the reasons put forward by @bremoran, but this is currently unsupported and I believe this feature is not currently planned. If this is needed we should raise a separate issue against the tools.
Module Header
Currently several modules have a centralized module header (mbed.h, rtos.h, nsapi.h). This helps alleviate issues with unintended header inclusions that can cause subtle problems with perfect backwards compatibility. If the module header is unique across all headers in the codebase, no namespace is needed.
Namespaces
This concept hasn't been discussed much, but we do have an existing pattern in our codebase. Using namespaces allows us to use classes between different modules without cluttering the global namespace. Currently several modules impose namespaces on all of their contained classes with the same name as the module. For C files this namespace is imposed through a common prefix of the same name. For convenience the namespace is unwrapped in the centralized module header.

ARM Internal Ref: IOTMORF-164


Use targeted database for BigQuery profile

Fixes #102, the diffs in this PR are from the pre-commit black formatter, when it was actually only a single line update. I tested and it works as expected, though not sure if we want to default to the service-account project if db_name is None.

@jbandoro wanted to confirm this value would be the equivalent of a GCP project_id, but your change will make it configurable, correct?

@jbandoro wanted to confirm this value would be the equivalent of a GCP project_id, but your change will make it configurable, correct?

yes that's correct. ATM the target GCP project_id is that of the GCP service account, and this PR will allow the project_id (dbt database) to be specified in dbt_args, for the case where a service account has access to many GCP projects.

@jbandoro cool, I think it makes sense to defer a project_id (or database) from the service account when the db_name isn't specified, which is why I added that last commit. Thank you for this contribution; it makes a lot of sense and is much appreciated! I will have @jlaneve take a look before we approve, just so that my commit is also getting reviewed. Once we get his 👍 then we can merge!


Customizing or hiding Benchmark.ips's output format

Benchmark.ips always prints its result to STDOUT in a nicely formatted table:
Benchmark.ips do |b|
  b.report("foo") { Array.new(1000, 0) }
  b.report("bar") { Array.new(5000, 0) }
end

foo   2.33M (429.67ns) (± 1.14%)  3.96kB/op        fastest
bar 906.57k (  1.10µs) (± 0.81%)  19.5kB/op   2.57× slower

But often I want to use those numbers somewhere else, e.g. plotting a graph, and to avoid parsing the above table again, I take the returned Benchmark::IPS::Job (the docs don't really mention this) and post-process the items into a JSON:
ips = Benchmark.ips { ... }
j = JSON.build do |json|
  json.object do
    json.field "items" do
      json.array do
        ips.items.each do |item|
          json.object do
            json.field "label", item.label
            json.field "mean", item.mean
            json.field "stddev", item.stddev
            json.field "bytes_per_op", item.bytes_per_op
          end
        end
      end
    end
  end
end

IMO this is still not straightforward enough, because I don't want to pollute STDOUT at all. It would be nice if Benchmark.ips itself supports those alternative formats out of the box. So I suggest implementing any of the following:

Add a boolean parameter to suppress the interactive and final printing of results in Benchmark::IPS::Job#execute and #report, respectively.
Allow passing an IO to Benchmark.ips and perform all the printing on that IO. Then one can pass File.open(File::NULL, "w") or a custom no-op IO to suppress the output.
Create some kind of reporter interface and delegate printing to that. Something like:module Benchmark::IPS
  module Reporter
    abstract def report(items : Array(IPS::Entry), interactive : Bool) : Nil
    abstract def interactive? : Bool
  end

  class TableReporter
    include Reporter

    getter? interactive : Bool

    def initialize(@io : IO = STDOUT, @interactive : Bool = true)
    end

    def report(items : Array(IPS::Entry), interactive : Bool) : Nil
      # ...
      @io.print "\e[#{items.size}A" if interactive
    end
  end

  class Job
    property reporter : Reporter

    def initialize(calculation = 5, warmup = 2, interactive = STDOUT.tty?)
      # ...
      @reporter = TableReporter.new(STDOUT, !!interactive)
    end

    def report : Nil
      @reporter.report(ran_items, interactive: false)
    end

    private def run_calculation
      @items.each do |item|
        # ...
        if @reporter.interactive?
          run_comparison
          @reporter.report(ran_items, interactive: true)
        end
      end
    end
  end
end

Then I could write:class MyJsonReporter
  include Benchmark::IPS::Reporter

  def initialize(@io : IO = STDOUT)
  end

  def interactive? : Bool
    false
  end

  def report(items : Array(IPS::Entry), interactive : Bool)
    JSON.build(@io) { ... }
  end
end

Benchmark.ips do |b|
  b.reporter = MyJsonReporter.new
  # ...
end

Additionally, TableReporter and MyJsonReporter are both testable in isolation, without needing to mock a full benchmark run.

Similar points probably hold for Benchmark.bm as well.

I slightly question the exposure of raw Array(IPS::Entry) rather than something that would allow a replacement of the inner structures.
That said it would be really cool if it were easier to export it to hdr histogram format so that it can be put into plotter .

Benchmark::IPS::Entry is "public" insofar as it isn't marked as :nodoc:. Indeed a lot of things under Benchmark should have been protected or hidden.
ran_items is always a fresh Array, but the entries themselves are mutable and have reference semantics, so perhaps they have to be duplicated.

I like the reporter pattern. It enables different formats.


extraneous characters in captions

<<<<<<< HEAD

b8c928582c3cdd2b14b8f121c23e440fabcf9005

These are showing up in the plot captions.

update infographiq and regenerated graphs.


NameError: name '_C' is not defined

Error:
NameError: name '_C' is not defined
Full traceback:

warnings.warn(
/home/alabl0a/miniconda3/envs/detgpt/lib/python3.9/site-packages/torch/utils/checkpoint.py:31: UserWarning: None of the inputs have requires_grad=True. Gradients will be None
warnings.warn("None of the inputs have requires_grad=True. Gradients will be None")
Traceback (most recent call last):
File "/home/alabl0a/miniconda3/envs/detgpt/lib/python3.9/site-packages/gradio/routes.py", line 393, in run_predict
output = await app.get_blocks().process_api(
File "/home/alabl0a/miniconda3/envs/detgpt/lib/python3.9/site-packages/gradio/blocks.py", line 1108, in process_api
result = await self.call_function(
File "/home/alabl0a/miniconda3/envs/detgpt/lib/python3.9/site-packages/gradio/blocks.py", line 915, in call_function
prediction = await anyio.to_thread.run_sync(
File "/home/alabl0a/miniconda3/envs/detgpt/lib/python3.9/site-packages/anyio/to_thread.py", line 33, in run_sync
return await get_asynclib().run_sync_in_worker_thread(
File "/home/alabl0a/miniconda3/envs/detgpt/lib/python3.9/site-packages/anyio/_backends/_asyncio.py", line 877, in run_sync_in_worker_thread
return await future
File "/home/user/miniconda3/envs/detgpt/lib/python3.9/site-packages/anyio/_backends/_asyncio.py", line 807, in run
result = context.run(func, *args)
File "/user/user/DetGPT/demo_detgpt.py", line 165, in run_grounding
boxes, logits, phrases = predict(detector, image_tensor, categories, box_threshold, text_threshold,
File "/user/user/DetGPT/GroundingDINO/groundingdino/util/inference.py", line 66, in predict
outputs = model(image[None], captions=[caption])
File "/home/user/miniconda3/envs/detgpt/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/user/user/DetGPT/GroundingDINO/groundingdino/models/GroundingDINO/groundingdino.py", line 313, in forward
hs, reference, hs_enc, ref_enc, init_box_proposal = self.transformer(
File "/home/user/miniconda3/envs/detgpt/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/user/user/DetGPT/GroundingDINO/groundingdino/models/GroundingDINO/transformer.py", line 258, in forward
memory, memory_text = self.encoder(
File "/home/user/miniconda3/envs/detgpt/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/user/user/DetGPT/GroundingDINO/groundingdino/models/GroundingDINO/transformer.py", line 576, in forward
output = checkpoint.checkpoint(
File "/home/user/miniconda3/envs/detgpt/lib/python3.9/site-packages/torch/utils/checkpoint.py", line 249, in checkpoint
return CheckpointFunction.apply(function, preserve, *args)
File "/home/user/miniconda3/envs/detgpt/lib/python3.9/site-packages/torch/autograd/function.py", line 506, in apply
return super().apply(*args, **kwargs)  # type: ignore[misc]
File "/home/user/miniconda3/envs/detgpt/lib/python3.9/site-packages/torch/utils/checkpoint.py", line 107, in forward
outputs = run_function(*args)
File "/home/user/miniconda3/envs/detgpt/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/user/user/DetGPT/GroundingDINO/groundingdino/models/GroundingDINO/transformer.py", line 785, in forward
src2 = self.self_attn(
File "/home/user/miniconda3/envs/detgpt/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/user/user/DetGPT/GroundingDINO/groundingdino/models/GroundingDINO/ms_deform_attn.py", line 338, in forward
output = MultiScaleDeformableAttnFunction.apply(
File "/home/user/miniconda3/envs/detgpt/lib/python3.9/site-packages/torch/autograd/function.py", line 506, in apply
return super().apply(*args, **kwargs)  # type: ignore[misc]
File "/user/user/DetGPT/GroundingDINO/groundingdino/models/GroundingDINO/ms_deform_attn.py", line 53, in forward
output = _C.ms_deform_attn_forward(

https://github.com/IDEA-Research/GroundingDINO/issues/8#issuecomment-1541892708
This solution fixed it for me.

This occurs because as it says in code it fails to load custom C++ ops. Check your virtual environment carefully. Or make new one and use command "pip3 install -q -e ." to install every module and stuff needed


sprockets deprecation: Extra .css in SCSS file is unnecessary

While upgrading an application from Rails 3.2 -> 4.2, we started to receive the following deprecation warning:
DEPRECATION WARNING: Extra .css in SCSS file is unnecessary. Rename
vendor/bundle/ruby/2.1.0/gems/entypo-rails-2.2.2/app/assets/stylesheets/entypo-fonts.css.scss to
vendor/bundle/ruby/2.1.0/gems/entypo-rails-2.2.2/app/assets/stylesheets/entypo-fonts.scss.

Uh oh, thanks for reporting.

FYI, 3.0.0.pre.rc.1 has been released to rubygems with a fix for this warning.


Refactoring

Move clients to class model
Support timing out unresponsive minions and failing build
Allow variable for batchsize
Allow suppressing output
Initial pipeline support

Move clients to class model
Support timing out unresponsive minions and failing build
Allow variable for batchsize
Allow suppressing output
Initial pipeline support

@mchugh19 Did this cover everything needed, i.e. did you solve all problems including UI? Any chance we could get a tutorial/how-to out of this?

Everything needed? The intent behind this work was to move from custom nonsense to using classes for a dropdown and included jelly. This further allowed work to start pipeline support. So that's all good and working. Next step before release is trying to figure out how to get output saved from a pipeline task as mentioned in issue #33
I'd happily write up a tutorial about anything, but as a very much not expert, it would be good to have someone look it over.


Can Safety-Gymnasium run on the SSH Server[Question]

Required prerequisites

[X] I have read the documentation https://safety-gymnasium.readthedocs.io.
[X] I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
[ ] Consider asking first in a Discussion.

Questions
Hi, a quick question does safety-gymnasium have to run in the local environment? Can we run it on the SSH Server?
I'm having the following bug report from glfw package running the toy example provided in the example folder on the SSH server:
.local/lib/python3.8/site-packages/glfw/__init__.py:912: GLFWError: (65544) b'X11: Failed to open display :0.0'
.local/lib/python3.8/site-packages/glfw/__init__.py:912: GLFWError: (65537) b'The GLFW library is not initialized'
python: /builds/florianrhiem/pyGLFW/glfw-3.3.8/src/monitor.c:445: glfwGetVideoMode: Assertion 'monitor != ((void *)0)' failed. Aborted (core dumped)
Or, is there any way we can bypass the GUI initiation and run the safety-gymnasium GUI-free?

Yes, simply change render mode to anything except 'human'.


command q on electron

what is the desired behavior of this command. To quit everything?

right.  i think it already actually but it has some problems, like if you have multiple unsaved notebooks open, then all the save/cancel dialogs open at the same time.

still broken, not sure of the circumstances though.


[Refactor][UI] Refactor time display of token manage use datatable render function

Purpose of the pull request
ref: #11076

Codecov Report

Merging #11078 (0820393) into dev (25ded1e) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev   #11078      +/-   ##
============================================
- Coverage     40.30%   40.28%   -0.03%
  Complexity     4854     4854
============================================
  Files           943      943
  Lines         37055    37055
  Branches       4073     4072       -1
============================================
- Hits          14935    14927       -8
- Misses        20612    20619       +7
- Partials       1508     1509       +1

Impacted Files
Coverage Δ

...erver/master/processor/queue/TaskEventService.java
69.64% <0.00%> (-10.72%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

...r/plugin/task/sqoop/parameter/SqoopParameters.java
53.33% <0.00%> (-1.34%)
:arrow_down:


make z-index bigger

I'm often having components rendered inside nested modals which have big z-index-es. It is very inconvenient for me to not be able to quickly hover over an component inside vue-devtools and not get a nice-looking hightlight (it is just hidden behind my modals). This pull request fixes that, probably in a dumb way.

Thanks!


Show error message from completions in the tooltip

There is a symbol inserted when an error occurred ("⚠"). It has a generic tooltip, that could show specific information about the error.

It could be in a better layout, but it works.


CSP selector and values.yaml cleanup

Thank you community users @papanito and @Baykonur for this suggestion. This PR supersede PRs #225 and #218 in addition to:

Cleaning up the default values file and table by organizing variables alphabetically.
This change does not alter the current behavior of the chart and users need to selectively disable the unwanted CSPs.
The flavor variable was not used anywhere in the chart. Removed.

Signed-off-by: Michael Mattsson<EMAIL_ADDRESS>

Thanks @datamattsson for me that looks very good. Will close my PR


Is it possible to get an achievements' image?

Hello,
First off, I love the package works great for me.
Secondly, I was wondering if it was possible for to get the image location for an achievement? Like the ones shown on Steam Community for each achievement.
Thanks!

So, from the base API call this is not possible.  However, there is a secondary API call that I didn't know existed that will get the achievement icon url.  I will work on adding this in.

This has been added to master.  I will tag a release once I get the back port to L4 done.

https://github.com/syntaxerrors/Steam/blob/master/examples/user/stats/GetPlayerAchievements.txt
For reference on the new return object.

 Thanks now I can show the achievements much better.

I'd love to see what you do with it.  If you'd be willing to send a link.

http://www.gamejerks.net request an invitation and I'll send one.


edit find

The edit-find window appears off screen.  I figured out how to bring it back, but when I click find next, it moves off the screen again.  Does anyone know how to fix this

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

ID: 5883370e-e55a-78f6-9ab0-4e83f054e81d
Version Independent ID: 9cdf0ca9-9787-34b5-a3bf-560ec30eef6b
Content: Find Command (Edit Menu)
Content Source: Language/Reference/User-Interface-Help/find-command-edit-menu.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

@rtgjeg
Thanks for your feedback. We use Github issues for documentation bugs, not for developer support. Please try the VBA developer community on Stack Overflow (https://stackoverflow.com/questions/tagged/vba) where you can get help from actual developers. If you find a bug in our documentation, please let us know! Thanks!


Removing quotes from udf_metadata_key

Replacing udf_metadata_key from string_literal to ID_LITERAL
	modified:   evadb/parser/evadb.lark
Removed .value from key_value_pair[0] post the change in type
	modified:   evadb/parser/lark_visitor/_functions.py
Replaced string key to ID_LITERAL in test query
	modified:   test/unit_tests/parser/test_parser.py
Solves #1010

Once tests and all work, will go ahead and change the docs as well

Ran the integration test for training the model. It parsed the query correctly and invoked training but gave the following error
ERROR    evadb.utils.logging_manager:plan_executor.py:182 Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu! (when checking argument for argument weight in method wrapper_CUDA__native_batch_norm)
Traceback (most recent call last):
  File "/home/hershd23/Desktop/evadb/evadb/executor/plan_executor.py", line 178, in execute_plan
    yield from output
  File "/home/hershd23/Desktop/evadb/evadb/executor/project_executor.py", line 34, in exec
    batch = apply_project(batch, self.target_list, self.catalog())
  File "/home/hershd23/Desktop/evadb/evadb/executor/executor_utils.py", line 42, in apply_project
    batches = [expr.evaluate(batch) for expr in project_list]
  File "/home/hershd23/Desktop/evadb/evadb/executor/executor_utils.py", line 42, in <listcomp>
    batches = [expr.evaluate(batch) for expr in project_list]
  File "/home/hershd23/Desktop/evadb/evadb/expression/function_expression.py", line 129, in evaluate
    outcomes = self._apply_function_expression(func, batch, **kwargs)
  File "/home/hershd23/Desktop/evadb/evadb/expression/function_expression.py", line 188, in _apply_function_expression
    return func_args.apply_function_expression(func)
  File "/home/hershd23/Desktop/evadb/evadb/models/storage/batch.py", line 173, in apply_function_expression
    return Batch(expr(self._frames))
  File "/home/hershd23/Desktop/evadb/evadb/udfs/abstract/abstract_udf.py", line 36, in __call__
    return self.forward(args[0])
  File "/home/hershd23/Desktop/evadb/evadb/udfs/ludwig.py", line 33, in forward
    predictions, _ = self.model.predict(frames, return_type=pd.DataFrame)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/api.py", line 895, in predict
    predictions = predictor.batch_predict(
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/models/predictor.py", line 142, in batch_predict
    preds = self._predict(batch)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/models/predictor.py", line 188, in _predict
    outputs = self._predict_on_inputs(inputs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/models/predictor.py", line 324, in _predict_on_inputs
    return self.dist_model(inputs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/models/ecd.py", line 136, in forward
    combiner_outputs = self.combine(encoder_outputs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/models/ecd.py", line 81, in combine
    return self.combiner(encoder_outputs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/combiners/combiners.py", line 451, in forward
    hidden, aggregated_mask, masks = self.tabnet(hidden)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/modules/tabnet_modules.py", line 113, in forward
    features = self.batch_norm(features)  # [b_s, i_s]
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/torch/nn/modules/batchnorm.py", line 171, in forward
    return F.batch_norm(
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/torch/nn/functional.py", line 2450, in batch_norm
    return torch.batch_norm(
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu! (when checking argument for argument weight in method wrapper_CUDA__native_batch_norm)

Ran the integration test for training the model. It parsed the query correctly and invoked training but gave the following error. Creating an issue for this
ERROR    evadb.utils.logging_manager:plan_executor.py:182 Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu! (when checking argument for argument weight in method wrapper_CUDA__native_batch_norm)
Traceback (most recent call last):
  File "/home/hershd23/Desktop/evadb/evadb/executor/plan_executor.py", line 178, in execute_plan
    yield from output
  File "/home/hershd23/Desktop/evadb/evadb/executor/project_executor.py", line 34, in exec
    batch = apply_project(batch, self.target_list, self.catalog())
  File "/home/hershd23/Desktop/evadb/evadb/executor/executor_utils.py", line 42, in apply_project
    batches = [expr.evaluate(batch) for expr in project_list]
  File "/home/hershd23/Desktop/evadb/evadb/executor/executor_utils.py", line 42, in <listcomp>
    batches = [expr.evaluate(batch) for expr in project_list]
  File "/home/hershd23/Desktop/evadb/evadb/expression/function_expression.py", line 129, in evaluate
    outcomes = self._apply_function_expression(func, batch, **kwargs)
  File "/home/hershd23/Desktop/evadb/evadb/expression/function_expression.py", line 188, in _apply_function_expression
    return func_args.apply_function_expression(func)
  File "/home/hershd23/Desktop/evadb/evadb/models/storage/batch.py", line 173, in apply_function_expression
    return Batch(expr(self._frames))
  File "/home/hershd23/Desktop/evadb/evadb/udfs/abstract/abstract_udf.py", line 36, in __call__
    return self.forward(args[0])
  File "/home/hershd23/Desktop/evadb/evadb/udfs/ludwig.py", line 33, in forward
    predictions, _ = self.model.predict(frames, return_type=pd.DataFrame)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/api.py", line 895, in predict
    predictions = predictor.batch_predict(
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/models/predictor.py", line 142, in batch_predict
    preds = self._predict(batch)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/models/predictor.py", line 188, in _predict
    outputs = self._predict_on_inputs(inputs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/models/predictor.py", line 324, in _predict_on_inputs
    return self.dist_model(inputs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/models/ecd.py", line 136, in forward
    combiner_outputs = self.combine(encoder_outputs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/models/ecd.py", line 81, in combine
    return self.combiner(encoder_outputs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/combiners/combiners.py", line 451, in forward
    hidden, aggregated_mask, masks = self.tabnet(hidden)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/ludwig/modules/tabnet_modules.py", line 113, in forward
    features = self.batch_norm(features)  # [b_s, i_s]
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/torch/nn/modules/batchnorm.py", line 171, in forward
    return F.batch_norm(
  File "/home/hershd23/Desktop/evadb/env/lib/python3.10/site-packages/torch/nn/functional.py", line 2450, in batch_norm
    return torch.batch_norm(
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu! (when checking argument for argument weight in method wrapper_CUDA__native_batch_norm)

Thanks for creating an issue! Do you run the experiments on ada-00 or ada-01?

Actually I ran it on my personal machine which has a GPU card

We can merge this PR. We can investigate the GPU issue in #1028. Thanks!

Come into my mind that you may also need to update the hugging face functions.

Come into my mind that you may also need to update the hugging face functions.

Oh okay @xzdandy. Will check for that today

@xzdandy @gaurav274 can you take a look at the changes, have incorporated the changes for HuggingFace UDFs as well

I also see some change changes in the docs causing the docs CI to fail. Should I try to fix them (best effort) in the PR?

Hi @xzdandy have made the following changes

removed .lock_preprocessing which was created unknowingly
Coverted CACHE and BATCH to UID structure in tests

For the other two issues

I think the Ludwig issue has been separately pointed out by you in #1036, I think the issue is not unique to my PR rather an issue in itself that you yourself have pointed out
test_create_udf_with_relational_api is actually a little tricky. Let me try and explain the issue to you.

We have made all udf_metadata_keys into UIDs. Once parsed these are processed and ultimately stored as lowercase strings in the metadata_map. What this test is trying to do is trying to convert the query and args from the API to the QUERY itself. To solve this I need to find the query builder for this which converts the API constructs to an SQL type query. I guess @gaurav274 mentioned that there are some usecases where python API data is converted to query and then run to leverage the optimizations built on the query.
Can you point me to the query builder code. I'll try and correct this there

@xzdandy made the changes can you take a look

Are we good to go with this? Can we merge or waiting for @gaurav274 's review.

I am fixing all merge conflicts now.

Done done, I have fixed merge conflicts

One minute to update the forecasting feature to use the new UDF syntax

Thanks @xzdandy for all your help!


Allow @Null*arked to target a field [working decision: no]

So far: no (#50).
#50 also said "no" to method parameters and local variables. I don't want to encourage us to revisit those parts.
I do want to revisit fields, though not urgently.
We've compiled at least 3 reasons against @NullMarked/@NullUnmarked on fields:
(1) We didn't use to even support METHOD and CONSTRUCTOR, and clearly the case for FIELD was worse than for those.
But now we've reversed that and allowed METHOD and CONSTRUCTOR. So we can consider FIELD, too, while still recognizing that its case is weaker than those.
(2) From bytecode, we can't tell what was done inside a field initializer.
But that's OK if we consider @NullMarked on a field to affect only the type of that field, not anything done in the initializer (e.g., inside an anonymous class).
This does mean that tools that read source code will have to be careful not to over-apply the effects of @NullMarked on a field.
Beyond that, annotating a field is just weird:

It's weird because fields don't count as "enclosing elements" the way that @NullMarked's other targets do.
It's weird that the annotation means something there but not what users might naively expect. (Hopefully most users just don't care about this at all, since they won't annotate fields and/or won't annotate fields with initializers and/or won't think or care about how the annotation affects those initializers.)

(3) We didn't have particularly compelling use cases.
I wouldn't call what I'm about to say "compelling," but I can give a less uncompelling variant of my earlier argument.
One of the things we've been doing is annotating classes in the JDK. That includes putting @NullMarked on JDK classes. But what happens when we provide annotations for the Java 11 version of a class and someone tries to use them with Java 17? Our annotations might say that JDK class Foo is @NullMarked, but they won't have any information about a field Foo.addedInJava17 (https://github.com/jspecify/jspecify/issues/94).
The conservative thing for tools to do is to treat Foo.addedInJava17 as @NullUnmarked. And if the tool reads the JDK annotations directly, it can do that.
However, we've been talking about providing a tool to rewrite JDK jars to actually include the annotations. That means that Foo would end up with an actual @NullMarked annotation in its class file. And then we need a way for the tool to tell nullness checkers "but addedInJava17 is @NullUnmarked"... like, say, by automatically putting a @NullUnmarked annotation on it :)
Really, I might discourage users from writing these annotations on a field themselves. But having the ability to insert them (mainly @NullUnmarked) with a tool might be valuable.
Or this might be too niche to care about: Our tool could already label methods as @NullUnmarked. How often would there be an API that is (a) newer than our JDK annotations that is (b) a public field  that (c) needs @Nullable or another annotation? It's probably rare. Hopefully we'll actually try this and get some real data someday.

It's weird because fields don't count as "enclosing elements" the way that @NullMarked's other targets do.

Fun times:
private String foo = switch("You've") {
    default -> {
        class GottaBe {
            ...
        }
        yield "KiddinMe";
    }
};

That is NOT a compelling use case for the feature. :-)
I do think in most ways allowing it on FIELD should be harmless.
But I do have one subtle concern. Right now the @Null*arked and the @Nullable/@NN annotations don't tread on each other's turf much at all... with the exception that they could mix it up in and around method modifiers (google-java-format, for one, fixes that).
Their domains being neatly partitioned might be helpful to novice users keeping the "big and clear" difference between them straight. I think if they see @Null*arked on a field or just that it can go there it might muddy the waters a bit. A field, unlike a method, really feels like the kind of "single unit" that would only have a type-use annotation (even though we know it has type components, and the code above notwithstanding).
Again, subtle.

And then we need a way for the tool to tell nullness checkers "but addedInJava17 is @NullUnmarked"... like, say, by automatically putting a @NullUnmarked annotation on it :)

Sufficiently edgecasey and generally user-invisible that perhaps a tool-specific @ImpliesNullUnmarked would serve?

If it turns out that we care about this for types in the JDK or other types that we want to annotate, then we may want it to work across tools. But now that you mention it, maybe we'd only really need it to work Kotlin, since that's the main tool that inserts runtime checks? If so, we may be able to satisfy it with a @TypeQualifierNickname approach. (In doing so, we'd be defining and using a type-use @UnspecifiedNullness annotation :\ But we can hold our noses, since, again, it would be a tool-specific annotation, one that we could avoid exposing to end users. It wouldn't be the first time :))
As for the concern: I'm not sure how much differently users will see fields and methods. But I definitely grant that, between the two of them, the field looks more like a "single unit," And methods will always be the more compelling use case.
Primarily, I'm holding out hope that my proposed problem scenario is rare enough that we'll find it easiest to just manually annotate any public fields that need @Nullable.

I also see a slight connection to another idea that I think has come up, the idea of annotating only the user-visible parts of a class. For that purpose, it could be nice to be able to annotate a class (or enclosing package/module) as @NullMarked and then put @NullUnmarked on all its private and package-private members—including fields. (This reminds me of Spring's @NonNullApi/@NonNullFields distinction.)
This just came up because AutoValue annotates its user-facing APIs but not its fields. That said, we're likely going to just get AutoValue to address that :) Plus, for obvious reasons, most tools don't care about the private members of a class in the first place, so incorrect annotations there usually don't matter (though they do in the unusual case we got a report about).
I still don't see this as an important reason to have FIELD as a target. If anything, it is a slight motivation for opening an actual issue about "only the user-visible API is @NullMarked," except that that feels pretty iffy to me, too. If anyone really wants to do that, it's mostly possible to put @NullUnmarked on the class (if necessary to override an enclosing @NullMarked annotation) and then put @NullMarked on each user-visible method. The complicated case would be a generic class, but even that is still workable as long as each type-parameter bound can be declared as extends @Nullable Something or extends @NonNull Something (as opposed to <T ..., U extends T>).

To be clear about my little gotcha
@NullMarked
private String foo = switch("You've") {
    default -> {
        class GottaBe {
            ...
        }
        yield "KiddinMe";
    }
};

I am saying that I think if we allowed it, it has to make the GottaBe class null-marked as well.

Yeah. While I am happy to have spent November with this bouncing around in my brain, I think it's clear that some new information would have to surface for us to consider it worthwhile.
I agree that the gotcha is bad (though hopefully very unlikely to come up). I might be willing to accept it if we saw an actual, significant need for this (like in my JDK example above), but that need itself seems very unlikely to come up.
As a further point against this, I'd note that I wrote my comment about annotating user-visible APIs as if @NullMarked would affect only API signatures. But in fact we've said that it affects implementation code, too (though doing anything with annotations in implementation code in bytecode is unlikely to go well, anyway). So anyone who does what I said in that comment would likely already be "lying" a bit, and it's hard to get excited about adding a footgun feature to help them lie slightly less in one case.

I am still happy with the answer of "no" here. But I'll note for the record that I just ran into a bug that was manifesting only when a particular field was recognized as non-nullable, and it would have been convenient to be able to use @NullUnmarked on that field.
That said, we have the workaround of applying @NullMarked to all other members of the class instead. And also, the bug is in a tool that doesn't support @NullUnmarked yet, anyway... :)

Current decision: @NullMarked and @NullUnmarked cannot target fields because they do not enclose other nonlocal declarations. No compelling use case has emerged that requires such annotation targets. In any case, we could always add such target validity in the future, compatibly, if such a case is described.
Argument for changing: Fields do kind of enclose their initializers, and so @NullMarked and @NullUnmarked could be used to mark local classes or type arguments within them. However, that is an infrequent case, and could be considered implementation-only and outside the required scope of JSpecify.
Timing: This must be decided before version 1.0 of the jar.
Proposal for 1.0: Finalize the current decision. If you agree, please add a thumbs-up emoji (👍) to this comment. If you disagree, please add a thumbs-down emoji (👎) to this comment and briefly explain your disagreement. Please only add a thumbs-down if you feel you can make a strong case why this decision will be materially worse for users or tool providers than an alternative.

Decision: @NullMarked and @NullUnmarked do not target fields.


Update Muffy guide with new research

Revamped Muffy guide
Added a short section to the Celia guide, and made minor wording improvements
Updated the dolphin-memory-engine file with new addresses to watch

I am also submitting a run demonstrating this route.


tty-share: Initial release with v0.6.2

Add tty-share - a tool to share tty sessions via webbrowser.
Motivation for this change
Add a missing tool
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Rebased, added the suggestions, changed the commit messages and updated from 0.6.2 to 2.0.0.

Result of nixpkgs-review pr 98558 run on x86_64-linux 1

1 package built:

tty-share


What's the purpose of zero_token and the difference with initial_token?

Due diligence

[X] I have done my due diligence in trying to find the answer myself.

Topic
Other / All
Question
One place to use zero_token still overrides it later. So could any help to explain when it's used? Should the delayed audio token be filled with initial_token or zero_token? As input or output? Thanks.
https://github.com/kyutai-labs/moshi/blob/67f594d9438effea997adf13a1dd8061b8737a47/moshi/moshi/models/lm.py#L246-L260

The delayed audio should be filled by the initial tokens (in the released version of moshi: 32000 for text, 2048 for audio). zero is actually only used for some full_like in this _get__initial_token function - most likely this is because we extracted this code from a larger codebase and didn't take the time to clean this bit.

Thanks for the reply. I just though zero_token works together with zero_idx in ScaledEmbedding to let Helium could mask out zero codes to still be able to generate text after per-training stage.


Unable to setup SSL

Using Windows 10 19041.1415 (2004) with TiddlyServer 2.1.4 and OpenSSL 1.1.1m.
Followed instructions in documentation and https.js to create keys.
Command
openssl req -x509 -sha256 -nodes -newkey rsa:2048 -days 365 -keyout tiddlyserver.key -out tiddlyserver.cer
works but
openssl req -x509 -out localhost.cer -keyout localhost.key -days 365 -newkey rsa:2048 -nodes -sha256 -subj '/CN=localhost' -extensions EXT -config <( printf "[dn]\nCN=localhost\n[req]\ndistinguished_name = dn\n[EXT]\nsubjectAltName=DNS:localhost\nkeyUsage=digitalSignature\nextendedKeyUsage=serverAuth")
fails with error "specified file cannot be found".

I am also trying to do this.
The documentation refers to https.js but I've never been able to find it.  Where is it?

Those instructions are old, I guess. The current docs are "read the source" for that, unfortunately. In short, you set config.bindInfo.https to a JS file relative to the settings file (as shown below), and export the function serverOptions (as shown second).
"bindInfo": {
    "https": "./relative to this file.js",
  },

/// each function call exports the create server options object
exports.serverOptions: = (host) => {
  //
};


Use of .net 3.1
What is the new behavior?
.net core 6 support
update Azure function version
update linux donet version ( for host serverfarm linux )
fix error in arm ( sitename / function name)
Checklist
Please check if your PR fulfills the following requirements:

[ ] Documentation has been added/updated
[ ] Automated Unit / Integration tests for the changes have been added/updated
[ ] Contains NO breaking changes
[ ] Updated the Changelog
[ ] Associated with an issue

Other information

I think we should reword commits to apply conventional commit pattern


Fix typo in exposed LANA helper

Fixes a typo in an exposed method for LANA
window.lana.setClientdId -> window.lana.setClientId

This is a breaking change for anyone that is already using this method, I'm not sure if it's already used - if yes, we can also support both the version with and without the typo

cc @chrischrischris @auniverseaway


[bugfix] dedup groupby columns in Deck visualizations

When specifying the same column twice as a Extra Data for JS and
Categorical Color, an error is issued. This addresses this issue.

Codecov Report

Merging #4801 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #4801      +/-   ##
==========================================
+ Coverage   72.33%   72.34%   +<.01%
==========================================
  Files         208      208
  Lines       15516    15517       +1
  Branches     1201     1201
==========================================
+ Hits        11224    11225       +1
  Misses       4289     4289
  Partials        3        3

Impacted Files
Coverage Δ

superset/viz.py
78.95% <100%> (+0.01%)
:arrow_up:

Continue to review full report at Codecov.

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

Didn't want to risk it, the set and list api are not the exact same, not sure if we handle the conversion on json.dump for instance. Didn't want to risk it...


Question: UTF-8 without a BOM

Does Brakets is compatible with "UTF-8 without a BOM"
If so where can it be set?
Thanks

Brackets currently supports UTF-8 without a BOM only, so you should be good to go.

Closing as answered.


Dev-branch

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (refactoring and improving code)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

Description

Additional context

@vatsala-singh please use the chirpy starter template instead of forking


RangeError appears if ibm-dropdown-list has all disabled items

carbon-components: 10.56.0,
carbon-components-angular: 4.58.3
"RangeError: Maximum call stack size exceeded" while rendering  that has only disabled items in the list

Actual result: RangeError appears in the DevTools Console
Expected result: this type of lists renders without any errors

This issue was resolved in 4.73.1 - See PR  https://github.com/carbon-design-system/carbon-components-angular/pull/2524


Create splitAt() and asyncSplitAt()

Fixes https://github.com/sithmel/iter-tools/issues/134
Discuss:

[x] What should asyncSplitAt() return?

a tuple of 2 async iterators
a tuple of 2 promises of arrays
a promise of a tuple of 2 arrays

Close in favor of https://github.com/sithmel/iter-tools/pull/181


Ignore soft hyphens, word breaks & zero-width stuff

Please add support for highlighting content that includes a soft hyphen (), a word break opportunity HTML tag (<wbr>) or a zero-width space ().
In this demo, I added a , <wbr> and  at various locations inside of the word "Lorem". And when using mark.js to highlight "Lorem", only two out of the five results are marked. Performing a browser search reveals all five matches.
I believe this applies to all browsers, but I did test and got the same results in the latest versions of Chrome & Firefox (Windows 10) with mark.js version (8.1.1).
References:

http://www.quirksmode.org/oddsandends/wbr.html
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/wbr
http://www.fileformat.info/info/unicode/char/200b/index.htm

I also found that zero-width non-joiner () and zero-width joiner () also produces the same result. Odd that they aren't discussed as much... I guess because these last two are joiners don't appear work with css hyphens - demo modified from this page.

Thanks for submitting @Mottie.
I didn't know these things yet. They don't seem to be really known. In all previous situations I needed to wrap words I just used CSS3 hyphenation in combination with the "lang" attribute on the <html> element.
If this doesn't require a lot of code we can support this. I'm not sure why  and  don't work, as they will be removed in the DOM. But <wbr> will probably only work when acrossElements is set to true, as the text will be continued in a different text node.

They don't seem to be really known.

I'm all about weird stuff. Like me! 😀

If this doesn't require a lot of code we can support this.

I've already got something working. The regular expression starts to look really ugly, so I think disabling this option by default would be preferred.
So what would you want to name this option? I started out with ignoreWhitespace but that isn't accurate enough. It only applies to soft hyphens and some zero-width characters.

Ok, I think I'm going to go with ignoreJoiners because my other idea of using killWhitey didn't seem too appropriate either.
I've started working on tests, and I have an odd question - why does the across elements filter file not have any elements to span across?

I'm all about weird stuff. Like me! :grinning:

:laughing: That's true. What gives you this idea?

I've already got something working. The regular expression starts to look really ugly, so I think disabling this option by default would be preferred.
So what would you want to name this option? I started out with ignoreWhitespace but that isn't accurate enough. It only applies to soft hyphens and some zero-width characters.

I should point out that mark.js already ignores whitespace by default (multiple blanks will be merged). So if it would be possible with a small change, I'd prefer integrating it by default too. How would a RegExp look in your solution?

This is a search for "Lorem" with only debug and ignoreJoiners set to true:

mark.js: Searching with expression "/()([lłŁ][\u00ad|\u200b|\u200c|\u200d]?[oÒÓÔÕÖØòóôõöøŌō][\u00ad|\u200b|\u200c|\u200d]?[rřŘ][\u00ad|\u200b|\u200c|\u200d]?[eÈÉÊËèéêëěĚĒēęĘ][\u00ad|\u200b|\u200c|\u200d]?m)/gim"

https://jsfiddle.net/Mottie/q7a8x80o/

I've started working on tests, and I have an odd question - why does the across elements filter file not have any elements to span across?

Because it doesn't matter. The specs for acrossElements are mostly necessary to make sure things are handled equally as without – in this case it's just necessary to make sure that filter is called at all. Checking if a spanned match is found is part of the main spec.

This is a search for "Lorem" with only debug and ignoreJoiners set to true

Ufff... definitely nothing that should be enabled by default :bowtie: So this just adds a check for the named joiners after each character?

So what would you want to name this option?

You are the native speaking American, so I guess ignoreJoiners is fine.

So this just adds a check for the named joiners after each character?

Yep, that's it. Maybe there is a better solution?
Within the code I call two functions:

Setup (after synonyms are added)
setupIgnoreJoinersRegExp(str) {
    // adding a "null" unicode character as it will not be modified by the
    // other "create" regular expression functions
    return str.split("").join("\u0000");
}

Create (before the accuracy regex changes)
createIgnoreJoinersRegExp(str) {
    // u+00ad = soft hyphen
    // u+200b = zero-width space
    // u+200c = zero-width non-joiner
    // u+200d = zero-width joiner
    return str.split("\u0000").join("[\\u00ad|\\u200b|\\u200c|\\u200d]?");
}

I tried using \ufffd (unicode replacement character), but the build process removed it and left an empty string. Do you think \u0000 is a good alternative? At least it works.


MacOS tool is not working

Hi, I have installed all the required dependencies mentioned in the readme file. However, when I run the tool, it shows an error that I am unable to debug. I need some help with this.
error :
blutter.py /Users/pavel/Documents/blutter/lib/arm64-v8a build\vs --vs-sln
Dart version: 3.1.5, Snapshot: 85db978ceb98b8ae97a75e17b3bdc693, Target: android arm64
flags: product no-code_comments dwarf_stack_traces_mode no-lazy_dispatchers dedup_instructions no-asserts arm64 android compressed-pointers null-safety
CMake Error at /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Failed to find all ICU components (missing: ICU_LIBRARY
_ICU_REQUIRED_LIBS_FOUND) (found version "72.1")
Call Stack (most recent call first):
/opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
/opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/FindICU.cmake:333 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:20 (find_package)
-- Configuring incomplete, errors occurred!
Traceback (most recent call last):
File "/Users/pavel/Documents/blutter/blutter.py", line 168, in
main(args.indir, args.outdir, args.rebuild, args.vs_sln, args.no_analysis)
File "/Users/pavel/Documents/blutter/blutter.py", line 130, in main
fetch_and_build(dart_version, arch, os_name, has_compressed_ptrs, snapshot_hash)
File "/Users/pavel/Documents/blutter/dartvm_fetch_build.py", line 120, in fetch_and_build
cmake_dart(ver, arch, os_name, has_compressed_ptrs, outdir)
File "/Users/pavel/Documents/blutter/dartvm_fetch_build.py", line 110, in cmake_dart
subprocess.run([CMAKE_CMD, '-GNinja', '-B', builddir, f'-DTARGET_OS={os_name}', f'-DTARGET_ARCH={arch}',
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/pavel/anaconda3/lib/python3.11/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['cmake', '-GNinja', '-B', '/Users/pavel/Documents/blutter/build/dartvm3.1.5_android_arm64', '-DTARGET_OS=android', '-DTARGET_ARCH=arm64', '-DCOMPRESSED_PTRS=1', '-DCMAKE_BUILD_TYPE=Release', '--log-level=NOTICE']' returned non-zero exit status 1.

I guess the issue cause is HOMEBREW_PREFIX environment (in current CMakeLists.txt) is used for finding ICU library. I will fix this issue when I get my hand on macbook.
You can workaround by export HOMEBREW_PREFIX=$(brew --prefix) and remove build directory. The, run the command again.

In latest commit, it should work without setting HOMEBREW_PREFIX environment.
If an error still occur, try deleting "build" directory first.

Thanks @worawit


Add https protocol to SRC_URI of eglstreams-kms-example

Most other recipes use https and it is needed for downloading through company firewall.

@Schlumpf I'm fine with the change, but could you reformat the commit message and add a signoff as described here?

done


Reset to previous state

Description
There is a select_static action block that will trigger user/action_x, on validation it will open an error (Through a modal because its an home view #968 )
On error the select should be reverted to its previous value.
There seem to not have a current value to update in client.view and in the doc its stated that you cannot publish home view more than 5time every 30min so updating it with it seems not the way to go.
Im basically looking for something like this
ack({ revertToPreviousValues: true })

How to cancel user action and revert the select to the previous value
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[ ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[ ] I've read and agree to the Code of Conduct.
[ ] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
node version:
OS version(s):
Steps to reproduce:

Expected result:
What you expected to happen
Actual result:
What actually happened
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.

Hi @adelin-b, thanks for asking the question.
I'm not sure I fully understand what you mean by the description yet, but if you are looking for a way to change an end user's selected items in a static_select block element from your Bolt app's app.action listener side, unfortunately, the platform does not offer anything for it. Thus, there is no way to do so from your Bolt app. One thing I can suggest is to open a modal to show error messages in the case where the selection event in the block happens and the selected item has something wrong.
If you meant something else, may I ask you to elaborate a bit more with details?
I hope this was helpful to you.

OK, so I would have a feature request then :
Everywhere where inputs of any sort is possible there is a way to do field validation with error in field. Not only in input inside popup

@adelin-b Thanks for your reply here. We will share your feedback with the appropriate teams.
We are unable to track the progress of the server-side updates in this issue tracker. I know that this issue still remains to you but let us close it now. To check the latest progress of this issue, please contact your customer support team (by either running /feedback in your workspace or submitting an inquiry from https://my.slack.com/help/requests/new). We would appreciate it if you could understand this.


Add support for displaying Favorites in HTML New Tab Page

Task/Issue URL: https://app.asana.com/0/72649045549333/1208246350498753/f
Description:
This change implements NewTabPageFavoritesClient that connects HTML NTP to favorites.
The client talks to the NewTabPageUserScript, and it uses a newly added NewTabPageFavoritesModel,
which provides favorites array from BookmarkManager and delegates favorites-related actions
to NewTabPageFavoritesActionsHandler.
Favicons are provided by FaviconsManager but need to be delivered to the web UI as "web assets"
which means they're handled in DuckURLSchemeHandler.
Steps to test this PR:

Clear app data
Run the app from Xcode, and become internal user.
Using Debug Menu -> Feature Flag Overrides enable htmlNewTabPage.
Import bookmarks and verify that favorites view on the NTP is populated.
Verify that collapsing/expanding favorites view works and is remembered between app sessions.
Open another window with NTP and verify that changes in one window are applied in the other.
Verify that moving favorites works.
Verify that opening favorites using left mouse click works.
Verify that all context menu options work as expected (note: the implementation of the actions, e.g. all dialogs, wasn't changed so you don't have to pay extra attention to verifying if behavior is 100% the same as in native NTP).
Open bookmarks bar; verify that you can't drag and drop a favorite onto bookmarks bar.
Verify that "Add favorite" button works as expected.

Definition of Done:

[ ] Does this PR satisfy our Definition of Done?

Internal references:
Pull Request Review Checklist
Software Engineering Expectations
Technical Design Template
Pull Request Documentation

One thing that is different from the current production build is that in the production build, we are limited on how many favorites we can add; here, there is no limit. Is that on purpose?

@jotaemepereira sorry to only reply now to you about it. This seems to be done on purpose - the FE always offers to add a new favorite. This is currently being ship-reviewed for Windows and wasn't protested. We may still change this behavior going forward but for now, the native side doesn't have control on whether or not the "add favorite" and ghost buttons are displayed.


fix(AsideElement): top alignment

Related Ticket(s)
Content block aside elements not aligning correctly #3454
Description
Changed a lot of spacing so I can achieve the top position of aside element (Link List component), in other words, it can be aligned with the text right before it and changed other spacing to be according what designers would.
I talked to Lara offline and she said me:

When there isn't the stacked Link List, in other words, when Link List isn't below everything should have 160px padding after the card. But on medium it should be 96px and smaller resolutions should be 64px. However LinkList starts to be stacked on large breakpoint that's why on the code 96px of padding is applied on large breakpoint and 64px of padding is applied on medium breakpoint, because the carbon--breakpoint-down mixin didn't handle small breakpoint.

When there are links that stack at the bottom on smaller breakpoints, it should have the same top and bottom padding as the other designs. 64px top, 96px bottom.

Updated PR https://github.com/carbon-design-system/ibm-dotcom-library/pull/3845


Selection does not contain Main class

When i import code in eclipse it says there is no main class and i build path as main and error and weird locating appears if you can tell me why  is this happening. Thank you.

Hi Admir,
sorry I’ve never built this app using Eclipse. As a Java FX file you won’t find a main.

I tryed to open it in NetBeans 8.0.2 But still no success i keep clicking opening project as folder and it just won't open as folder, tryed as zip file stuck on 88% and says No netbeans project added.
I am doing research work for my college as final exam so i need to have like this simple with database and recognition and there is so low tutorials online. Any  help i appreciate. Thank you


Update ex11_27_28_29_30.cpp

Correct initialization，because  you can't use a map in this way  after It has been initialized.

Thx


MathJax not rendering

doesn't render TeX

Go to your hexo root folder than install the hexo majax plugin:
npm install hexo-filter-mathjax --save

seems to still not have rendered.

Then use mathjax syntax. I use hexo default plugin to support this, avoiding extra runtime rendering.

fixed!


[QA-1837] Move jest-junit config

Jest's configuration are defined in the package.json file and jest.config.js file. Either file is fine but I feel it's wrong to be in  both files.
Clean up package.json, move jest-junit config to jest.config.js.
https://broadworkbench.atlassian.net/browse/QA-1837

Thank you so much, @kyuksel @petesantos


[SU-25] Refactor EntityEditor

The data table allows editing the value of an attribute using the EntityEditor component. This splits up EntityEditor and extracts the form for entering the attribute's value/type so that they can be reused for adding new rows.

Sorry, should have clarified. This is in support of SU-25 and adding new rows would be added in a future PR. This PR should have no user-visible changes.


Remove update repaint method in build window

Overview
With build window visible and project running, developers notice massive performance drop. Even without play mode, this window is repainting itself more than necessary due to update() method.
This change just removes the excessive repaint
Changes

Fixes: #5003

Verification
Opened window with game mode and noticed perf drop in half. Now fixed
Close & open window fine
Select buttons to switch tabs
Build worked

/azp run mrtk_pr

I was initially concerned about what would happen if we removed this, but from testing a few of the common scenarios, it looks like this is fine - I thought that this was causing some bug where Open APPX Packages Location wasn't un-greying out after building the appx, but it turns out, it's just an existing bug.

Same sentiment Will, I think it was just left over and isn't needed for proper unity editor window behavior

/azp run mrtk_pr


feat: FluentVersion object in get_fluent_version()

Return FluentVersion object in get_fluent_version().
>>> from ansys.fluent.core import launch_fluent
>>> solver = launch_fluent()
>>> solver.get_fluent_version()
<FluentVersion.v242: '24.2.0'>
>>> solver.get_fluent_version().value
'24.2.0'

>>> meshing = launch_fluent(mode="meshing")
>>> meshing.get_fluent_version()
<FluentVersion.v242: '24.2.0'>
>>> meshing.get_fluent_version().value
'24.2.0'

Added @iboyd-ansys and @ochernuk so that the system coupling integration can be checked when the PR is ready.

We can get the following behaviour by adding a __repr__ method to FluentVersion:
>>> solver.get_fluent_version()
"24.2.0"

We can get the following behaviour by adding an __repr__ method to FluentVersion:
>>> solver.get_fluent_version()
'24.2.0'

Done. Thank you.