Proposal: Implement an OpenAI-compatible endpoint for the gateway

Motivation
LLM users and existing tools most commonly use the OpenAI API. TensorZero currently has an API that maps onto our internal representations, but we should also offer an OpenAI-compatible endpoint that still allows us to provide as much of the TensorZero functionality as possible.
Interface
Background
As shown below, the OpenAI client allows for message content of the form of a list containing a dict, so we can support Input as in TensorZero with some type-casting. We can pass additional data to the server using the headers and parse them server-side.
    response = await client.chat.completions.create(
    messages=[
        {
            "role": "user",
            "content": [{
                "x": "y",
                "a": "b",
            }],
        }
    ],
    model="tensorzero",
    extra_headers={
        "episode_id": "...",
        "function_name": "write_haiku",
    },
)

## Body on server side of this request
# {"messages": [{"role": "user", "content": [{"x": "y", "a": "b"}]}], "model": "tensorzero"}
# Also should include the headers passed in `extra_headers`

Proposed Interface input
We need a layer mapping the OpenAI-compatible interface on the server-side to our typical Input.
Here's the set of request parameters our current inference endpoint expects along with where we expect to take them from in this proposal:
/// The expected payload is a JSON object with the following fields:
#[derive(Debug, Deserialize)]
#[serde(deny_unknown_fields)]
pub struct Params<'a> {
    // the function name
    function_name: String, // headers with parameter function_name (required)
    // the episode ID (if not provided, it'll be set to inference_id)
    // NOTE: DO NOT GENERATE EPISODE IDS MANUALLY. THE API WILL DO THAT FOR YOU.
    episode_id: Option<Uuid>, // headers (optional)
    // the input for the inference
    input: Input,  // constructed from messages (see below)
    // default False
    stream: Option<bool>, // from OpenAI request parameter
    // Inference-time overrides for variant types (use with caution)
    #[serde(default)]
    params: InferenceParams,  // from OpenAI request parameters (chat completions only)
    // if the client would like to pin a specific variant to be used
    // NOTE: YOU SHOULD TYPICALLY LET THE API SELECT A VARIANT FOR YOU (I.E. IGNORE THIS FIELD).
    //       ONLY PIN A VARIANT FOR SPECIAL USE CASES (E.G. TESTING / DEBUGGING VARIANTS).
    variant_name: Option<String>,  // from headers (optional)
    // if true, the inference will not be stored
    dryrun: Option<bool>,  // from headers (optional)
    // dynamic information about tool calling. Don't directly include `dynamic_tool_params` in `Params`.
    #[serde(flatten)]
    dynamic_tool_params: DynamicToolParams,
    // `dynamic_tool_params` includes the following fields, passed at the top level of `Params`:
    // If provided, the inference will only use the specified tools (a subset of the function's tools)
    // allowed_tools: Option<Vec<String>>, // Assumed to be empty
    // If provided, the inference will use the specified tools in addition to the function's tools
    // additional_tools: Option<Vec<Tool>>, // from tools parameter in OpenAI API
    // If provided, the inference will use the specified tool choice
    // tool_choice: Option<ToolChoice>, // from tool_choice parameter in OpenAI API
    // If true, the inference will use parallel tool calls
    // parallel_tool_calls: Option<bool>, // from parallel_tool_calls parameter in OpenAI API
    // If provided for a JSON inference, the inference will use the specified output schema instead of the
    // configured one. We only lazily validate this schema.
    output_schema: Option<Value>, // optional request header
    #[serde(default)]
    credentials: InferenceCredentials<'a>,  // optional request header
}

Proposed Interface Output mapping
I'll comment what I think we should put in each field and how we'll get it.
{
  "id": "chatcmpl-123456", # Inference ID
  "object": "chat.completion", # hardcoded
  "created":<PHONE_NUMBER>, # timestamp
  "model": "gpt-4o-2024-08-06", # function_name
  "choices": [
    {
      "index": 0, # hardcoded
      "message": {
        "role": "assistant",
        "content": "Hi there! How can I assist you today?", # Text content blocks
        "refusal": null,
        "tool_calls": [{"id": "tool_call_id", "type": "function", "function": {"name": str, "arguments": str}] # Array of Tool calls if applicable
      },
      "logprobs": null, # Always null
      "finish_reason": "stop" # alwasy
    }
  ],
  "usage": {
    "prompt_tokens": 19, # As needed
    "completion_tokens": 10,  # As needed
    "total_tokens": 29, # As needed
    "prompt_tokens_details": {
      "cached_tokens": 0
    },
    "completion_tokens_details": {
      "reasoning_tokens": 0
    }
  },
  "system_fingerprint": "fp_6b68a8204b"
}

Streaming output:
{
  "id": "chatcmpl-8sn4n2n3j2n3j2n3",  # Inference id
  "object": "chat.completion.chunk", # hardcoded
  "created":<PHONE_NUMBER>, # timestamp
  "model": "claude-3-sonnet-20240229", # function_name
  "system_fingerprint": "fp_44795b6733", # idk
  "service_tier": "standard", # idk
  "choices": [
    {
      "index": 0, # hardcoded
      "delta": {
        "content": "Here's how you can calculate", # text content if present
        "role": "assistant", # hardcoded
        "tool_calls": [
          {
            "index": 0, # hardcoded
            "id": "call_4k2j34k2j34k2j", # from ToolCall content block
            "type": "function",
            "function": {
              "name": "calculate_average", # from ToolCall content block
              "arguments": "{\"numbers\": [1, 2, 3, 4, 5]}" # from ToolCall content block
            }
          }
        ],
        "refusal": null # hardcoded
      },

        ]
      },
      "finish_reason":null # hardcoded
    }
  ],
  "usage": {
    "prompt_tokens": 156,
    "completion_tokens": 423,
    "total_tokens": 579
  }
}

Testing
First, write tests with OpenAI client in Python to cover every case in /gateway/tests/e2e/inference.rs that makes sense using dummy models and assertions. Here are the cases we should tackle:

simple inference request
simple streaming inference request
inference params request
tool use additional tool
tool use tool choice (each kind)
streaming tool use
multiturn tool use
parallel tool use
parallel streaming tool use
json function
dynamic json function
streaming json function

SGTM


Update CITATION.bib to remove entanglement forging authors

This is a follow up to #580.  This removes six additional authors who only contributed to entanglement forging and have made no direct contributions to circuit cutting to the best of my knowledge.
I've also reformatted with one author per line.
A diff that ignores whitespace can be generated by running git show --color-words on this branch.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.493%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3496

Relevant Lines:
3661

💛  - Coveralls


Refactor project level prometheus

We need to deploy prometheus per project to match the new design

The project level monitoring is tested and existing and new-found bugs are tracked by their own issues.
The issue is closed.


Create new error message for invalid property type

Solves #22. Added additional unit tests, 2 cover the addition of the invalidPropertyType error, and its edge cases. The cannotAssignProperty error was missing unit testing coverage for Values, and since this PR addresses issues with the cannotAssignProperty error, I added additional coverage for Values. (note, here by Values I mean the Value class of Fusion. This distinction is helpful because I added ObjectValue unit testing to check for edge cases)
Something I would like to note is that as I kept adding more unit tests, cleanupOnDestroy.spec's unit tests started throwing errors. It would appear that it depends on the speed of the rest of the unit testing and needs to be looked into. I temporarily circumvented this problem by bumping its timeout to 3 seconds instead of 2. I also opened an issue for this (#101).
Unit testing for this passed: https://github.com/nottirb/Fusion/runs/4571710080?check_suite_focus=true

Pushed fixes for all of the requested changes. You can view the new unit testing run here: https://github.com/nottirb/Fusion/runs/4575395416?check_suite_focus=true


Add sponsors name

@TanuMalik would like to include name of the sponsors in addition to their logos:
Here is a full list: Inria, Rennes Metropole, Region Bretagne, Université de Rennes and Sandia National Laboratory.
@msimonin would you be willing to create a PR for this?

I'm on it here: https://github.com/msimonin/ACM-REP-2024/tree/dev/fix-69


Fix overrides of runner parameter attributes

Validate that only a selected set of attributes can be overriden for any runner parameters. It does't make sense to let an action parameter override the type in the runner parameter. Also, this will fix a bug where a partial dict in the action parameter will completely override the runner parameter. In the case where type is not defined in the action parameter, the runner parameter will no longer have a type after the override.

I think I'm missing a bit of context. It would be great if you could update PR description with some more information (and it's also good for other non-stormers).
Which parameters were causing a problem and are not supposed to be overwritten (position, anything else)?

Re backward incompatibility of this change (from slack) - for the actions which override parameters which are not supposed be overridden with the same values - is it possible for us to detect that (overridden value is the same as the parent one) and not throw (I know it might require us to refactor a bunch of code and pass a lot of state around so it might not be possible, at least with reasonable effort)?
This would allow us to make it mostly backward compatible and we can drop that code in 1.4 (or in the next major release).

@Kami: the code here is looking to see if the value differ for unpermitted overrides before throwing an exception.

@Kami: I updated commit message.

I am ok with the change. Atleast the expected behavior is coded up deterministically now.
I suspect there will be some regressions as there always are when basic things like these change. We will have to watch out and squash those asap.

https://stackstorm.slack.com/archives/stackstorm/p1452198230021316

This breaks st2-register-content on actions, see build:
https://circleci.com/gh/StackStorm/st2/296

That's correct behavior.  Whatever action it fails on shouldn't override type on a runner param.

https://github.com/StackStorm/st2/pull/2362 is going to fix the st2-register-content error (basically fixing the override for the headers parameter in the http-request runner).

@m4dcoder Thanks for updating the description and clarifying things.
#2361 is not a duplicate of this issue since it fixes a different problem - the problem in that case it's not type overwriting, but that we don't perform a correct deep runner and actions parameters merge which will cause validation to fail since if the action parameter which is overriding runner one doesn't explicitly provide a type, it will assume to a default type of string.

Having said that, it looks like #2361 fixes the real underlying problem so the question is do we even need this PR?
It seems like it introduces some potential braking changes which could cause issues.

Here is my monologue from Slack:
kami [08:35]
@m4dcoder: https://github.com/StackStorm/st2/pull/2359#issuecomment-169917841 sorry for the late feedback, but I didn't fully understand the underlying issue at first. If I do understand it correctly now (maybe I still dont), it seems to me that this PR is not really needed and we only really need just https://github.com/StackStorm/st2/pull/2361

[08:35]
or am I missing something?

[08:36]
since yeah, your PR does introduce some more strict parameter overwrite handling - previously we didn't have any rules for that so everything worked, but if I understand it correctly the actual problem and bug lives elsewhere and that's what my PR is fixing

kami [08:37]
and I think it would be good to figure out if i'm correct and that's indeed the case because your PR is introducing some potentially breaking changes which I dont think we need when we merge #2361

[08:40]
checked your PR again, so it looks like part of our changes are the same - the deep merging issue, so yeah, that's the actual fix. but i dont think we need the "only allow to override those attributes" and this is a breaking change

I think it would be good to come to the bottom of this and figure out if we really do need the "only allow to override those parameters" part which is a breaking change.
In general I'm all for explicit rules and strict validation (previously we had no rules and validation on that so everything was allowed), but this could potentially cause a lot of issues to the users (we also don't allow overriding enum attribute now and some other attributes and this will likely cause issues to the users).
And if we decided that we indeed want this change we also need to explicitly document those override rules.

https://stackstorm.slack.com/archives/stackstorm/p1452274858021695

@Kami: IMO, deep merge will fix the surface problem. but the deeper problem here is that action shouldn't be overriding certain attributes (type) of the runner parameters. going back to fix some of the packs is necessary as they were wrong to being with (i.e. http-request runner has the headers param type WRONG and then the core.http action corrected it.  that's just silly.)

@m4dcoder I don't think it's a surface problem - it's the actual underlying bug.
As far as what is correct and what is wrong is to be decided since before those changes, we had no rules about that (well, it was decided in the PR which was merged).
In general, I do think it's a good idea to not allow users to overwrite "position" and "type" but besides that, I think everything else should be fine (we also don't allow overriding enum right now).


  The code now is supposed to push all the thunks for meanings of builtins outside if the main loop, so that they're only created once, but either I've failed at that (I should try using some trace or something, it's hard to figure out what's going on from reading Core) or the cost of converting from BuiltinMeaning to BuiltinRuntime on the fly is just that high, which seems unlikely.

Ok, I'm pretty clueless as to what's going on here. The thing is, we might be having the same problem at startup currently without knowing it. Whatever is slow here is quite likely also slow during the initial traversal where we compute the BuiltinRuntime for each builtin in master. This certainly needs to be investigated, but I'm gonna postpone that for now.

The thing is, we might be having the same problem at startup currently without knowing it.

That's true. However, if that's the case we can certainly address it on the ledger side by ensuring that that is only done once and is then cached.


Update ingest-data-one-click.md

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

@TzviaGT  - please make requested change. Thanks!

@TzviaGT change made in PR: https://github.com/MicrosoftDocs/azure-docs-pr/pull/97494
#please-close


Generic type param used as generic type constraint causes variance issues?

TypeScript Version:  3.5.1, 3.6.3, Nightly

Search Terms:
generic type parameter, generic type constraint, variance
Code
declare const x0 : <InT extends boolean|null>(arg : InT) => boolean;
//Expected: Error
//Actual  : Error
const x1 : <InT extends string>(arg : InT) => boolean = x0;

type Y<In, Out> = <InT extends In>(arg : InT) => Out;
declare const y0 : Y<boolean|null, boolean>;
//Expected: Error
//Actual  : OK
const y1 : Y<string, boolean> = y0;

Expected behavior:
y1 = y0 assignment should fail
Actual behavior:
y1 = y0 assignment passes
Playground Link:
3.5.1 Playground
3.6.3 Playground
Nightly Playground
Related Issues:

Seems like the type inference is OK, though,
/**
 * type test0 = [boolean | null, boolean]
 */
type test0 = typeof y0 extends Y<infer In, infer Out> ?
    [In, Out] :
    never;

/**
 * type test1 = [string, boolean]
 */
type test1 = typeof y1 extends Y<infer In, infer Out> ?
    [In, Out] :
    never;

3.5.1 Playground

Duplicate of #31006 and fixed by #31029.

It's not in the nightly builds?


Updated README.md & CITATIONS.md & added workflow images

PR checklist

[x] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/phageannotator branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[x] README.md is updated (including new tool citations and authors/contributors).

Is this new workflow schematic more what you were looking for?

Not really, the global size hasn't changed, check in the file changes tab here on github, you might see what I'm talking about there.

Sorry, but I'm still missing something! I can see the transparent outlines, but am unsure what you mean about resizing the page. Are you recommending that I crop any borders in the image? Thanks for bearing with me!

I made screenshots from the Files Changed tab here on GitHub.
So first the PNG, you have a small transparent border on the right and upper side:

Second the SVG, the document size compared to the image size doesn't really compare, lots of empty space on top and on the bottom:

Another basic question: Do I set up and run checks on my end, or is that something done on the nf-core side? Right now it seems as though I can't start workflows


tests: check whether re-adding event-loop into fixture fixes broken t…

…ests

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@bfa8e68). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #1   +/-   ##
=======================================
  Coverage        ?   98.66%
=======================================
  Files           ?       11
  Lines           ?     1052
  Branches        ?      170
=======================================
  Hits            ?     1038
  Misses          ?        6
  Partials        ?        8

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 bfa8e68...33dc809. Read the comment docs.


[ASCII-1533] Add security-agent config by-source subcommand and api endpoint

What does this PR do?
https://datadoghq.atlassian.net/browse/ASCII-1533
similar to the work done in https://github.com/DataDog/datadog-agent/pull/26129 and https://github.com/DataDog/datadog-agent/pull/26056
This PR adds a metadata payload for the security-agent process configuration by layers to send to the backend

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

diagnose show-metadata security-agent works
configuration from the security-agent process is accurate
security-agent.yaml is correctly added to the flare

/merge


Implement addModel feature

Coverage increased (+0.04%) to 98.689% when pulling 94fdbaf400047c270b7a0888a2ca4ba739a60ace on MattMcFarland:master into f3656d5357988540922b3a1f22a61b2161546677 on yoshuawuyts:master.

Coverage increased (+0.04%) to 98.689% when pulling 47502e1198473c4bb84548b5b383cc3dfde52bd1 on MattMcFarland:master into f3656d5357988540922b3a1f22a61b2161546677 on yoshuawuyts:master.


Browser "can't connect to the Server" when launching Beaker Notebook

I'm new to Python and want to try out Beaker Notebooks so downloaded and installed the app. When I launch it, Safari (Mac OS 10.10.2) launches a blank page with the message "Safari can't connect to the server. Safari can't open the page '<IP_ADDRESS>:8801 because Safari can't connect to the server '<IP_ADDRESS>'"
I have iPython installed and that runs fine. I've tried searching for others having similar issues but couldn't find anything.
Ideas?
Thanks.

Thanks for the report.  We fixed a couple of bugs that caused this for some users.
You can try the workaround here: https://github.com/twosigma/beaker-notebook/issues/982
Or it might have been this: https://github.com/twosigma/beaker-notebook/issues/824
Your best option might be to just try our prerelease of v1.2 which has both of these fixes and many more.  See the last question at the bottom of our FAQ: http://beakernotebook.com/faq

Thanks for the quick reply. I installed v1.2 and was able to connect, however the screen is blank. Using Chrome works though.
Thanks again!

xlnt.
just tried it with safari on 10.10.1 and it was fine.  who knows.
glad you persisted -- and thanks for coming back to close it.


[YBUG.IO] Wen I  switch to staking tab, my...

Wen I  switch to staking tab, my wallet stops connectio.
Re-engaging my wallet many times really annoying me.
Browser
Metamask
Google Chrome
Thank you
Source url: https://live.sovryn.app/wallet
Reported by<EMAIL_ADDRESS>Reported at: 16 Apr at 01:11 UTC
Location: JP, Shizuoka, Shizuoka
Browser: Chrome 89.0.4389.114
OS: Windows 10.0
Screen: 1536x864
Viewport: 2304x1083
Screenshot:

For more details please visit report page on Ybug:
https://ybug.io/dashboard/reports/detail/5fp1wzssfd5t4mn8pyrn

It's because staking/bitocracy is on different page.


Make CupertinoTabBar and TabBar (and scaffolds) more customizable

CupertinoTabBar always have a top border. So you cannot use this for making a more flat iOS design even though this is typical.
BottomNavigationBar only shows labels when type = fixed, but then background color is not customizable - even though a customer very typically requests this.
BottomNavigationBar only allows background color customisation when type = shifting, but then labels are not always visible - even though a customer very typically requests this.
The above combinations makes it impossible to create a very typical flat look - from simply using the standard tabbar widgets and/or scaffolds.
It would be nice to avoid the (dreaded!) situation in Xamarin Forms where you constantly have to make a renderer just to remove a border, add a color or the like.
In Flutter terms this means copying the code and remove the border, add the background color or the like. This is what I currently have to do!
So please allow for more customisation option in these top widgets (and scaffolds).

I think it's reasonable to extract some common parts of the BottomNavigationBar and CupertinoTabBar out to a barebones common element in the widgets layer.
Though the common code is fairly short and may not satisfy everyone. Our primary goal is to make the creation of custom look and feels tab bar so easy it's 'affordable' to do for every app.

@timahrentlov @fmatosqg, can you guys give us a mock-up or an image of the visual effects you're trying to achieve? So we can get a better idea of whether it's something that's better served with a customizable Material/Cupertino widget or an 'unskinned' widget.

I'm not visualising anything specific, I guess this would be an approach to designing widget's apis that would help achieve both high level and high tweaking. A successful example would be having both the material button and at the same time the material, inkwell, button widgets separately.

How about CupertinoTabScaffold and associated TabBar but with the TabBar having a Material graphical design? I want a hybrid between the two. Specifically, the indicator on the Material TabBar is what I'm after while maintaining the Navigation of a CupertinoTabScaffold having tabviews that are rendered off screen while also keeping a separate navigation history between tabs. I want the iOS Human Interface rules but with Material options. Make sense?

I would add 'Allow hiding item's title" to the list :) It's common practice to hide titles on the bottom tabBar.

Closing this since you patched this @artrmz


Improve test case scenarios for STEP_IN and STEP_OUT debug operations

Description:
$subject
With the changes https://github.com/ballerina-platform/ballerina-lang/pull/27914, STEP_IN and STEP_OUT test cases are passing. But when we test manually these operations are failing(not working as expected)
Affected Versions:
Ballerina Swan Lake Preview 9 SNAPSHOT
Language specification v2020-12-17
Update Tool 0.8.11-SNAPSHOT

STEP_IN and STEP_OUT debug operations are working as expected in the latest master.
This behaviour is observed with the change https://github.com/ballerina-platform/ballerina-lang/pull/27914.
The behaviour mentioned in the issue is not reproducible now and it should have been fixed with https://github.com/ballerina-platform/ballerina-lang/pull/28238. Therefore no need to improve the current test scenarios. Hence closing the issue.


Correct a typo on the async-std version

Correct a typo on the async-std version in the Cargo.toml file of the documentation.

You're welcome !


Problem with tags (not?) being case-sensitive

It would be nice if tags were case-sensitive. Now it appears they are not: new tags are converted to all-lowercase. There is however one existing tag with an uppercase letter, Radboud_sign. But when I apply that to a new sign, the system creates a new tag that is all-lowercase. So on the one hand the tags appear case-sensitive (one uppercase letter is saved and correctly displayed), but applying it to new signs leads to the creation of a lowercase variant.

This was incredibly easy to fix, but incredibly hard to find. The tagging functionality is provided by an external module, so I couldn't directly edit the code. However, Google told me that the behavior to force lowercase was not standard, so there must be some code somewhere that made everything lowercase (or so I thought). I looked at numerous places, doing tests to pinpoint the exact location where it happened, and was about to give up... when I suddenly noticed a setting in the settings file 'FORCE_LOWERCASE_TAGS'. When I set that to False, everything worked :P.
I also removed the lowercase variant of Radboud_sign and added the uppercase one here http://signbank.science.ru.nl/dictionary/gloss/3269/

:-)


Use EnsureRemoveAll

Use EnsureRemoveAll to recursively umount and remove container and sandbox directory.
This function will also be useful during checkpoint recovery.
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

Will do.

@mikebrow Done.


support statistics?

I have a lot of json data, so I need to calculate the error rate for each field, or validator can throw errors for all fields. how to do?

Hi. Sorry you're having trouble.
Please use either Slack, IRC, the Mailing Lists, or StackOverflow for support, these issues are for bugs or feature requests.


PDF417 Barcode format

Hello,
From what I have observed the PDF417 format is not supported.
Do you have plans to implement PDF417 support in your library?
Thanks.
Regards,
Jose A.

So......????

Apparently no plan to support lol


Added filtering to appleseed.studio unit tests (Issue #1359)

Primary changes:

Unit tests in appleseed.studio are filtered by regex in realtime (new feature).
const-corrected TestWindow class.
Removed unused header files in TestWindow.h/.cpp.
Various minor fixes to code layout to keep things consistent.

Screenshot of relevant UI changes (I tried to follow the same layout from the main window):

Thanks for the super nice PR! The code is extremely clear and I have literally nothing to complain about in this area.
A few remarks on the UI/UX front:

For the sake of consistency with the project explorer and the color/texture picker (two places where filtering is available), I would suggest placing the textbox and button above the unit test list rather than below.

Another thing to consider is whether we should add a way to check/uncheck the tests that are shown in the list after filtering. What do you think?

Another thing to consider is whether we should add a way to check/uncheck the tests that are shown in the list after filtering. What do you think?

In terms of convenience I really like that. Are you suggesting adding buttons to select/de-select all items presently shown in the list (as opposed to toggling all loaded tests)? It would be very easy to implement, but wouldn't that clutter the UI though?

Maybe we should actually modify the existing buttons to operate on the shown tests instead of the whole test suite?

Merged, thank you!


FI-3069: Full EHR QuestionnaireResponse verification

Summary

Replace attestation tests with tests that use a QuestionnaireResponse input for basic conformance and workflow correctness.

Includes adding the necessary methods to DTRQuestionnaireResponseValidation. This adds some duplication of logic and error messages between this and the pre-population validation. I tried for a while to refactor things to reduce this duplication, but I was struggling to reach a solution that was adequately clear and simple, so I ultimately decided the duplication was preferable.

Remove erroneous IG version suffix in origin extension URL
Rewrite Fixutres and FixtureLoader modules.

This wasn't strictly necessary to fulfill this task, but it came about as part of my attempt to refactor DTRQuestionnaireResponseValidation, and I much prefer it this way.
FixtureLoader has too much logic and information in it. It was meant to be a simple mechanism to minimize file IO during running tests. I moved the test-fixture mapping to Fixutres (not the perfect place for it either, but it's fine, see comment).
The Fixtures interface was unnecessarily complicated so I simplified it to 3 public methods.
Fixtures now offers class methods rather than instance methods. This is more appropriate given how it works. And I like the added clarity in calling code when you have to reference Fixtures. when using it.

Move Respiratory Assist Device fixtures into a subdirectory like we have with the other fixtures.
Remove unused group: client_groups/resp_assist_device/dtr_full_ehr_questionnaire_workflow_group.rb.
Improve implementation of MockPayer#questionnaire_package_response

As discussed offline with @karlnaden.
This was also not necessary for this task, but it was something I noticed while refactoring the Fixtures module.

Testing Guidance

Run the new tests in the FullEHR suite. Use the QuestionnaireResponses in the Postman collection to test both expected success and expected failures
Run the SMART App Test Suite to confirm nothing is broken. There shouldn't be any difference in behavior.

rspec failure due to removed test:
cannot load such file -- /Users/knaden/Documents/Inferno/source/davinci-dtr-test-kit/lib/davinci_dtr_test_kit/client_groups/dinner_static/dtr_full_ehr_prepopulation_representation_attestation_test


duplicate module when use async import

Bug report
Files
// components/common.js
export function test() {
  console.log('commonjs')
}

// src/main1.js
import { test } from './components/common'
test()

// src/main2.js
import { test } from './components/common'
test()

// src/main.js
const a = () => import('./main2')
const b = () => import('./main3')
console.log(a);
console.log(b);

What is the current behavior?
main1.js bundled to 1.js, main2.js bundled to 2.js,
but commonn.js bundled to both 1.js and 2.js
What is the expected behavior?
commons.js should be bundled to component.js

Other relevant information:
// webpack.config.js
const path = require('path')
module.exports = {
  entry: './src/main.js',
  output: {
    path: path.join(__dirname, 'dist')
  },
  optimization: {
    minimize: false,
    splitChunks: {
      cacheGroups: {
        components: {
          name: 'components',
          priority: 30,
          minChunks: 1,
          reuseExistingChunk: false,
          test: 'components'
        },
      },
    },
  },
}

this is by design (note: modules executed once), @sokra please help with opt-out

@vankop it is a bug in webpack-4 or feature in webpack-5 ?

webpack 4 and 5 work nearly identical here.
The source code of small common modules is duplicated in each chunk. To deduplicate the modules an additional request would be needed and that's not worth it. You can take a look at the optimization.splitChunks configuration to change this behavior. Look at minSize.

Answer above, feel free to feedback


Background tasks to update stats

This addresses issue #79 as well as issue #95.
This uses the WebBackgrounder and WebBackgrounder.EntityFramework packages to run background tasks coordinated across all web servers in a web farm with the simple task (as of now) of updating package download stats. :)

I think I wanted to keep the IPAddress column so I wouldn't have a migration to remove it and then another one to add it back later. Let me follow up on the privacy concerns before I remove it.

I merged this in already with changes due to code reviews.


upadte gem farm

It would be wonderful to have this feature.

I have the similar tool that support bot gem farming, rss farming. Inbox me on telegram: t.me/autorok

Can you send it to me?


"Object" Class conflicts with ES methods

Hi everyone,
"Object" class defined in namespace Speckle.Core.Api conflicts with ES  Object*.defineproperty(exports, "__esmodule", { value: true });   and causes circular dependency problem.
You can reproduce the issue by generating a typescript client which contains an endpoint with stream response(which contains "Object" as a property" and by using following compiler options in tsc:
"compilerOptions": {
    "strict": false,
    "jsx": "preserve",
    "importHelpers": true,
    "moduleResolution": "node",
    "module": "commonjs",
    "target": "es6",
     ....

If you try to import your typescript client in another typescript file or any vue component.
You will get ES reference error :
Cannot access 'X' before initialization in following line:
**Object**.defineproperty(exports, "__esmodule", { value: true });
I renamed "Object" class as "SpeckleObject" to solve issue locally.

Hey @barisbs thanks for this!
I'm not a typescript expert so I have a couple of questions for now until the rest of the team will back me up:

we don't have a Speckle.Core.Api.Object class definition, we do have an Objects namespace (notice the s), but that's outside Core. So I'm not sure where that error is originating from! Maybe It's somehow referring to the C# Object type?
could you give us a bit more context around what you're building? I'd help us understand how to better improve our codebase and SDks

Thanks!

Hey @teocomi

we don't have a Speckle.Core.Api.Object class definition, we do have an Objects namespace (notice the s), but that's outside Core. So I'm not sure where that error is originating from!

Actually you have in .NET SDK:
https://github.com/specklesystems/speckle-sharp/blob/master/Core/Core/Api/GraphQL/Models.cs line 171
We have our own ASP .Net Core Server for leaDE on the front of Speckle server and some of endpoints produces some response types like Stream which has Object class (line 171)  as a property:
Please see https://github.com/specklesystems/speckle-sharp/blob/master/Core/Core/Api/GraphQL/Models.cs line 115.
We have also a Vue application and we generate a typescript client from swagger definition of our ASP. Net Core Server which generates also this "Object" class. Compiled js defines export in the first line of the files as below:
Object.defineproperty(exports, "__esmodule", { value: true });`
So the browser can't understand the difference between js Object and speckle Object and throws an error on the first line of the files as above and means that we may not access Object which is not initialized yet.
We thank you :)

Gotcha, I missed that!
I think it's very sensible to rename it, it's should be a minor change on our side and it'd remove a potential confusion in C#-lang as well. I'll discuss it internally and get back to you!

Fixed! If you're relying on our nugets, we'll publish new ones tomorrow or on monday.
Thanks for the report!


[POC] pr-checks: add CHANGES or No Issue on check_commit failure

When the check_commit check fails, this reads the PR description and comments to find any AAH references,
when found, creates CHANGES/$number.misc, containing the PR title
when not found, commits an empty commit with the no issue comment
(testing if this works from a pull_requrest action, may need pull_request_target for the push)

Randomly commenting AAH-1106 to try that path.
If that works, only the push is a problem.


Atom - beautify

Hello guys, i had problem with atom - beuatify, i reinstalled windows for other reason and problem is the same as before... What should i do ? I found that it is because i have space between my windows name
`
<EMAIL_ADDRESS>postinstall C:\Users\DAVIDU~1\AppData\Local\Temp\apm-install-dir-117029-920-9p0ji7\node_modules\atom-beautify
npm run build-options
C:\Users\DAVIDU~1\AppData\Local\Temp\apm-install-dir-117029-920-9p0ji7
`-- (empty)
npm WARN deprecated<EMAIL_ADDRESS>use uuid module instead
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>use uuid module instead
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
'C:\Users\David' is not recognized as an internal or external command,
operable program or batch file.
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\DAVIDU~1\AppData\Local\Temp\apm-install-dir-117029-920-9p0ji7\package.json'
npm WARN apm-install-dir-117029-920-9p0ji7 No description
npm WARN apm-install-dir-117029-920-9p0ji7 No repository field.
npm WARN apm-install-dir-117029-920-9p0ji7 No README data
npm WARN apm-install-dir-117029-920-9p0ji7 No license field.
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Users\David Ďurčo\AppData\Local\atom\app-1.13.1\resources\app\apm\bin\node.exe" "C:\Users\David Ďurčo\AppData\Local\atom\app-1.13.1\resources\app\apm\node_modules\npm\bin\npm-cli.js" "--globalconfig" "C:\Users\David Ďurčo\.atom\.apm\.apmrc" "--userconfig" "C:\Users\David Ďurčo\.atom\.apmrc" "install" "C:\Users\DAVIDU~1\AppData\Local\Temp\d-117029-920-69ic0l\package.tgz" "--runtime=electron" "--target=1.3.13" "--arch=ia32" "--global-style"
npm ERR! node v4.4.5
npm ERR! npm  v3.10.5
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>postinstall: npm run build-options
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'npm run build-options'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the atom-beautify package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build-options
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs atom-beautify
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls atom-beautify
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\DAVIDU~1\AppData\Local\Temp\apm-install-dir-117029-920-9p0ji7\npm-debug.log
npm ERR! code 1
`

I have the same problem but I'm getting this error. I installed Atom for the first time and went to install beautify, the newest release. I'm being presented with this error. Does not let me format my code. Is this a current issue at the moment?
module.js:457
Hide Stack Trace
Error: Cannot find module 'event-kit'
at Module._resolveFilename (module.js:455:15)
at Module._resolveFilename (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\electron.asar\common\reset-search-paths.js:35:12)
at Function.Module._resolveFilename (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\src\module-cache.js:383:52)
at Function.Module._load (module.js:403:25)
at Module.require (module.js:483:17)
at require (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\src\native-compile-cache.js:50:27)
at Object. (file:///C:/Users/Owner/.atom/packages/atom-beautify/src/beautify.coffee:7:25)
at Object. (file:///C:/Users/Owner/.atom/packages/atom-beautify/src/beautify.coffee:2:1)
at Module._compile (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\src\native-compile-cache.js:109:30)
at Object.value [as .coffee] (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\src\compile-cache.js:216:21)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.require (module.js:483:17)
at require (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\src\native-compile-cache.js:50:27)
at Package.module.exports.Package.requireMainModule (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\src\package.js:796:27)
at Package.module.exports.Package.activateConfig (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\src\package.js:266:12)
at PackageManager.module.exports.PackageManager.packageHasSettings (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\settings-view\lib\package-manager.js:51:14)
at PackageCard.module.exports.PackageCard.hasSettings (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\settings-view\lib\package-card.js:728:34)
at PackageCard.module.exports.PackageCard.updateSettingsState (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\settings-view\lib\package-card.js:402:16)
at PackageCard.module.exports.PackageCard.updateInterfaceState (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\settings-view\lib\package-card.js:395:12)
at PackageCard.module.exports.PackageCard.initialize (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\settings-view\lib\package-card.js:243:19)
at PackageCard.View [as constructor] (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\space-pen\lib\space-pen.js:184:25)
at new PackageCard (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\settings-view\lib\package-card.js:20:48)
at PackageDetailView.module.exports.PackageDetailView.completeInitialzation (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\settings-view\lib\package-detail-view.js:152:28)
at PackageDetailView.module.exports.PackageDetailView.loadPackage (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\settings-view\lib\package-detail-view.js:171:21)
at PackageDetailView.module.exports.PackageDetailView.initialize (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\settings-view\lib\package-detail-view.js:146:12)
at PackageDetailView.View [as constructor] (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\space-pen\lib\space-pen.js:184:25)
at PackageDetailView.ScrollView [as constructor] (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\atom-space-pen-views\lib\scroll-view.js:12:47)
at new PackageDetailView (C:\Users\Owner\AppData\Local\atom\app-1.14.0\resources\app.asar\node_modules\settings-view\lib\package-detail-view.js:38:54)

Have you  gone  through the checklist ? 😄
Checklist

[ ]  Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[ ] Reloaded(or restarted) Atom to ensure it is not a caching issue
[ ] Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues so I know this is not a duplicate issue
[ ] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[ ] Generated debugging information by executing Atom Beautify: Help Debug Editor command in Atom and added link for debug.md Gist to this issue

Ran into this issue today, got it Fixed 🎉  going through the checklist 👍

I've merged https://github.com/Glavin001/atom-beautify/pull/1598 which should resolve these issues.
Published to v0.29.21.


Pointers cannot be removed (but can be added!) from the Input System Profile; need to explicitly drill into the Pointer Profile

Describe the bug
I noticed that I wasn't able to remove pointers from the input profile directly (but I can add one!) because I cannot select any of them. I had to go into the pointer profile to do that 🤦♂.
While the documentation does states that:
https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/Input/Pointers.html
Its not intuitive because the editor UI gives all the visual ques that you can remove pointers.
To reproduce
Steps to reproduce the behavior:

Go to the MRTK Profile
Click on Input
Scroll down to Pointers
See +|-. Clicking on + works to add a new pointer
Attempt to select an existing profile

Expected behavior
Able to select pointer but can't.
Screenshots
If applicable, add screenshots to help explain your problem.
Your Setup (please complete the following information)

Unity Version [e.g. 2018.3.11f1]
MRTK Version [e.g. v2.0]

Target Platform (please complete the following information)

HoloLens
HoloLens 2
WMR immersive
OpenVR

Additional context
Documentation:
https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/Input/Pointers.html

Yes this is a known bug. Dupe of #5004


vite.config.js

Good day sir,
Thank you for the amazing work!
I am trying out 2 things
first is changing root directory
I would want something like
everythingElse
-- dist
-- entry
-- pages
etc...
node_modules
vite.config.js
package.json
this is my vite.config.js
import viteCompression from 'vite-plugin-compression';

export default: {
        root: 'everythingElse'
        plugins: [viteCompression()],
};

second is to be able to generate gz and br files and serve them instead of an on the fly compression.
It seems like it is not working. Or i might be wrong in my vite.config.js
Is this how it should look like?
Proxy on the otherhand works fine.
This is my first time using vite and fastify.
Any help is deeply appreciated.
Thank you

Hey there @stephenjason89 thanks for trying out fastify-vite at such an early stage!
Changing root directory should be possible via the root option in latest release.
Also for compression you need to do it on Fastify's side via fastify-compress, because in fastify-vite, we're only using Vite's built-in server middleware for development, not production.
In any case, if you provide me with a GitHub repo for your attempt, I can look at it and get it working/fixed this coming weekend. On weekdays I'm afraid I'm too swamped with my day job.
Cheers!

Thank you so much @galvez,
Tried out fastify-compress and it is working pretty good. I will use this instead of vite-compress.
However, I can't seem to make the root option to work. I'm currently using fastify-vite: 2.1.3
Should it be set in vite.config.js like this?

Hey there @stephenjason89 thanks for trying out fastify-vite at such an early stage!
Changing root directory should be possible via the root option in the latest release.
Also for compression you need to do it on Fastify's side via fastify-compress, because in fastify-vite, we're only using Vite's built-in server middleware for development, not production.
In any case, if you provide me with a GitHub repo for your attempt, I can look at it and get it working/fixed this coming weekend. On weekdays I'm afraid I'm too swamped with my day job.
Cheers!

Any reason not to use Vite middleware for production? I was experimenting and wondering why not?

@ivanjeremic Vite's middleware is only useful for development purposes. It would be unnecessary overhead.

@ivanjeremic Vite's middleware is only useful for development purposes. It would be unnecessary overhead.

Ok so if I understand correctly if I want to build a nextjs like framework, It would make sense to use Vite built-in server only for development and fastify for production correct?

@ivanjeremic Vite's middleware is only useful for development purposes. It would be unnecessary overhead.

Ok so if I understand correctly if I want to build a nextjs like framework, It would make sense to use Vite built-in server only for development and fastify + vite build step for production correct?

@ivanjeremic that's what fastify-vite does already — it'll use the appropriate renderer package for production.

Hey guys. I faced the issue as well at least for version "fastify-vite-vue": "2.2.0-beta.2".
vite-plugin-compression is not working, looks like even not being called.
fasitfy-compress is not working for me. I would prefer to have static compressed files rather than to compress it on a fly.
So, I created a compression assets script which I integrated to our CI pipeline. I just created a scripts command in my package.json file:
"compress": "node compress-assets.js",
Thus, after running npm run build you may run npm run compress to generate gzip and brotli compressed files.
The script is written on NodeJS 14.x
compress-assets.js
const {createGzip, createBrotliCompress, constants} = require('zlib');
const {pipeline: pipelineStream} = require('stream');
const {promisify} = require('util');
const {createReadStream, createWriteStream} = require('fs');
const {opendir} = require('fs/promises');
const {join, extname} = require('path');

const pipeline = promisify(pipelineStream);

function changeExtension(filepath, toExt) {
    return `${filepath}${toExt}`;
}

async function compressAssets() {
    const assetsPath = './dist/client/assets';
    const dir = await opendir(assetsPath);

    for await (const dirent of dir) {
        if (!dirent.isFile()
            || extname(dirent.name) === '.br'
            || extname(dirent.name) === '.gz') {
            continue;
        }

        console.log(`Start processing ${dirent.name}`);

        const filepath = join(assetsPath, dirent.name);
        const outputGzipFilepath = changeExtension(filepath, '.gz');
        const outputBrotliFilepath = changeExtension(filepath, '.br');

        const gzip = createGzip({
            level: constants.Z_BEST_COMPRESSION
        });
        const brotli = createBrotliCompress({
            level: constants.Z_BEST_COMPRESSION
        });

        await pipeline(
            createReadStream(filepath),
            gzip,
            createWriteStream(outputGzipFilepath)
        );

        await pipeline(
            createReadStream(filepath),
            brotli,
            createWriteStream(outputBrotliFilepath)
        );

    }
}

compressAssets()
    .then(() => console.log('Assets have been compressed'));


Add Nucleo F446ZE port to FreeRTOS_apps

A port similar to the Olimex FreeRTOS example but for the Nucleo F446 board.
The project structure is the same, except:

the FreeRTOS-POSIX plugin is moved to a lib folder.
the serial_transport.h/.c files are moved in a separate folder to highlight that their excluded from the firmware build and are only copied over to XCRE
Recommended change: move the arm toolchain installation outside of the firmware folder, or have it as a prequisite since it is used by most boards.

Very nice contribution. Thank you very much, @alsaibie. This will take a bit longer to review. I'll ask @pablogs9 for that.

You're most welcome. I have a nucleo F3 and L4, would you care to have them ported as well? Or having a porting guide under README.md would do, since other Nucleo board setups are very much the same?
Will wait for the review first.

@ralph-lange It looks good to me, but we don't have any Nucleo F446ZE here for test... do you have any? If not I proposed to merge this PR since it only modifies a F446ZE-related folder.
Once merged, we have to check this other PR: https://github.com/micro-ROS/micro-ros-build/pull/139

@ralph-lange It looks good to me, but we don't have any Nucleo F446ZE here for test... do you have any? If not I propose to merge this PR since it only modifies a F446ZE-related folder.
I have none either, but I agree to merge.


feat: add protobuf 3.22.3 release

update protobuf with release 3.22.3

:tada: This PR is included in version 1.108.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


nz-list cannot use an ellipsis instead of an overflow by  css style

Version
1.0.0
Environment
angular/cli: 6.0.8
Reproduction link
https://ng-zorro-antd-start-udv4tt.stackblitz.io/
Steps to reproduce
:host ::ng-deep .ant-list-item-content{
overflow: hidden;
white-space: nowrap;
text-overflow: ellipsis;
}
What is expected?
show an ellipsis
What is actually happening?
the excess content is hidden , but the ellipsis is not show
Other?

放在弹框上动态渲染数据的时候闪屏非常严重

text-overflow: ellipsis; won't work in display: flex;
basic css problem closed.

@smile2014 出现闪屏仔细看 angular 关于 ngFor 的文档


Several warning and errors when running tools

# ./src/bpftrace ../tools/tcpconnect.bt
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:26:42: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:28:2: warning: implicit declaration of function 'WRITE_ONCE' is invalid in C99 [-Wimplicit-function-declaration]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:28:17: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:26:42: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:29:6: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:26:42: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:38:15: error: unknown type name 'bool'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:38:44: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:42:9: error: use of undeclared identifier 'true'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:44:15: error: unknown type name 'bool'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:44:50: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:46:9: error: use of undeclared identifier 'true'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:56:38: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:63:6: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:56:38: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:64:5: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:56:38: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:65:5: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:56:38: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:66:2: warning: implicit declaration of function 'WRITE_ONCE' is invalid in C99 [-Wimplicit-function-declaration]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:66:17: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:56:38: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:77:36: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:79:28: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:77:36: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:91:41: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:93:22: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:91:41: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:103:38: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:105:6: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:103:38: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:106:2: warning: implicit declaration of function 'WRITE_ONCE' is invalid in C99 [-Wimplicit-function-declaration]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:106:17: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:103:38: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:115:44: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:120:18: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:115:44: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:120:31: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:115:44: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:123:36: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:125:19: warning: incompatible pointer types passing 'struct list_head *' to parameter of type 'struct list_head *' [-Wincompatible-pointer-types]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:115:55: note: passing argument to parameter 'entry' here
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:126:7: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:123:36: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:127:7: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:123:36: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:137:40: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:140:5: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:137:40: note: forward declaration of 'struct list_head'
fatal error: too many errors emitted, stopping now [-ferror-limit=]
Unknown identifier: 'AF_INET'
Unknown identifier: 'AF_INET6'
Unknown identifier: 'AF_INET'

I thought it was something on my machine, but then I got back to the last commit I knew this was working, and:
# ./src/bpftrace ../tools/tcpconnect.bt
Tracing tcp connections. Hit Ctrl-C to end.

    [ RUN      ] basic.libraries under /usr/include are in the search path
    [       OK ] basic.libraries under /usr/include are in the search path
    [ RUN      ] basic.non existent library include fails
    [       OK ] basic.non existent library include fails
    [----------] 17 tests from basic
    [...]
    ```

:040000 040000 28b8fa26e39c2ff7fb154cad4d8cd9cd642e5bcf 73b20cdb11e57843ae3e4fd0496e317543296743 M      src
:040000 040000 7bcc8adc429f822299d6d3043b18e0182dedd2ba 25b2d047f8014b6346ebb057ceaa9b6562053919 M      tests

Anyone else having this problem?

@mmarchini I think this PR fixes this problem:
https://github.com/iovisor/bpftrace/pull/657

@mmarchini Yeah, my bad :cry: Will submit a PR to detect this kind of bugs in the future. Created #655 to keep track of it :)

It would be detected by the tools-parsing-test suite, but since we can't run it on Travis it's easy to miss.

Did not know this script, seems very useful, thanks! Unfortunately it would not have shown this issue I think:
$ sudo src/bpftrace -d ../tools/tcpconnect.bt |& grep -i error | head -3
/lib/modules/4.16.4-1-ARCH/build/include/linux/list.h:28:17: error: incomplete definition of type 'struct list_head'
/lib/modules/4.16.4-1-ARCH/build/include/linux/list.h:29:6: error: incomplete definition of type 'struct list_head'
/lib/modules/4.16.4-1-ARCH/build/include/linux/list.h:38:15: error: unknown type name 'bool'

$ sudo src/bpftrace -d ../tools/tcpconnect.bt > /dev/null 2>&1
$ echo $?
0

#653 to track this (context)

Probably an environment difference, because on my machine clang crashes due to too many errors:
sudo src/bpftrace -d ../tools/tcpconnect.bt
...
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:26:42: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:28:2: warning: implicit declaration of function 'WRITE_ONCE' is invalid in C99 [-Wimplicit-function-declaration]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:28:17: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:26:42: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:29:6: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:26:42: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:38:15: error: unknown type name 'bool'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:38:44: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:42:9: error: use of undeclared identifier 'true'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:44:15: error: unknown type name 'bool'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:44:50: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:46:9: error: use of undeclared identifier 'true'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:56:38: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:63:6: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:56:38: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:64:5: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:56:38: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:65:5: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:56:38: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:66:2: warning: implicit declaration of function 'WRITE_ONCE' is invalid in C99 [-Wimplicit-function-declaration]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:66:17: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:56:38: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:77:36: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:79:28: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:77:36: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:91:41: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:93:22: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:91:41: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:103:38: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:105:6: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:103:38: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:106:2: warning: implicit declaration of function 'WRITE_ONCE' is invalid in C99 [-Wimplicit-function-declaration]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:106:17: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:103:38: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:115:44: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:120:18: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:115:44: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:120:31: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:115:44: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:123:36: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:125:19: warning: incompatible pointer types passing 'struct list_head *' to parameter of type 'struct list_head *' [-Wincompatible-pointer-types]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:115:55: note: passing argument to parameter 'entry' here
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:126:7: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:123:36: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:127:7: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:123:36: note: forward declaration of 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:137:40: warning: declaration of 'struct list_head' will not be visible outside of this function [-Wvisibility]
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:140:5: error: incomplete definition of type 'struct list_head'
/lib/modules/4.15.0-47-generic/build/include/linux/list.h:137:40: note: forward declaration of 'struct list_head'
fatal error: too many errors emitted, stopping now [-ferror-limit=]
Unknown identifier: 'AF_INET'
Unknown identifier: 'AF_INET6'
Unknown identifier: 'AF_INET'

$ echo $?
1

Fixed by #657


Set the base branch to test against with a .rubocop_lineup.yml file

We just changed the base branch of our main project from master to main and need a way of manually setting this now so that we don't mess other downstream users up.
Example .rubocop_lineup.yml file:
---
:base_branch: "main"

The failing tests aligned with failing tests from our last master build when we fixed a security vuln and it does not seem related to tests.

Fixes #1


why pretrain from encoder_q?

Yes,i have a question is that：in liner fine turning period，why pretrain from encoder_q instead of encoder_k？

来信收到，谢谢！


🐛 [firebase_analytics] Doesn't log entire route with GoRouter

If you add FirebaseAnalytisObserver to GoRouter, it doesn't log the entire route path. This makes it hard to understand what screen you are viewing
final navigationRouter = GoRouter(
  observers: [
    FirebaseAnalyticsObserver(analytics: FirebaseAnalytics.instance),
  ],
);

pushed (expected)
logged
working

/
/
✅

/foo
foo
❌

/settings/user
user
❌

/user
user
❌

Thanks for the report @lukepighetti
Can you take a look at go_router's location property to get to the current location in your app for logging and see if it helps in your case ?


Trouble loading the pretrained models

Hi,
Can you please let me know the exact procedure to follow when trying to load the pretrained weights?
I have downloaded them and tried keeping in the base folder as well as in the segan_V1 folder, but I am getting the following errors:
DataLossError (see above for traceback): Unable to open table file segan_V1/SEGAN-41800.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
Would be great if you can throw some light on this.
Regards
Nabarun

Ok, got it to work. Closing this issue.


Change cocoapods version from 1.6.0.rc.2 to 1.6.0.

@wilhuff The faulty tvOS Travis build configuration exposed by CocoaPods 1.6.0 needs to be addressed first.


Version Issue

We are currently in version 1.1.1
but in the readme.md and security.md it's still written 1.1.0

Done but I forgot to link the commit


ADD 'Edit Element' actions to CMS Preview Pane

This PR is a work-in-progress. Designs and functionality are not yet fully implemented, and it requires testing across a broad set of projects to ensure compatibility.
This PR introduces an interactive layer to the Preview Pane when editing a page with Elemental blocks on it. When hovering over a block in the preview, it will be outlined and have an 'Edit' button visible. Clicking this button will expand the associated block in the Element Editor UI.
This is currently at the PoC stage, and it needs some testing across different sites to ensure the styling is resilient and non-breaking. It also needs some work to support touch-based devices, as the hover state is not available. @newleeland has produced designs for the intended flow and functionality.

cc @silverstripeux for review when you have a chance

Cool, @Cheddam (or @robbieaverill if quicker) do you want to grab someone from our team when you have time to do a walkthrough?

Hi,
Awesome initiative. Is there any reason this is only on the preview pane (which I have never seen working ... )?
See: https://github.com/dnadesign/silverstripe-elemental/issues/745 for context.

which I have never seen working
@sunnysideup you have never seen the preview working, or never seen the links in the preview working? Elemental blocks (3 of the base blocks) should display as part of the page preview, they don't have individual previews. Blocks like Userforms still link deeper unfortunately as its a lot more work to get those working.

I have NEVER seen a preview work (and I have worked for various dev agencies in a wide variety of constellations)

Perhaps try out this demo https://www.silverstripe.com/silverstripe-cms/demo/

done ;-) lets see what happens ... THANK YOU Paul.  I always really appreciate your input.

@clarkepaul , i did all this. Signed up for a test site, but no luck!

I can not see any preview option at all. I was thinking that perhaps in split mode it would scroll down to element when you clicked on it.

I think we are talking about different things maybe. There isn't any edit icon in the preview yet, nor does it scroll to the right location on the page when a block is opened as yet—but these are the things which we would like to build in with this issue https://github.com/dnadesign/silverstripe-elemental/pull/621 (it's in concept phase).
BTW I see that your "view mode" toggle is displaying weirdly which must be a bug (I don't see it like that in Chrome).

we are on Chrome.
So there is no preview? With preview I'd like to see what the changes in the CMS mean before they go live. Is there another meaning for preview?

The preview is on the right of your screen, our definition of preview must be different.

This pull request hasn't had any activity for a while. Are you going to be doing further work on it, or would you prefer to close it now?

It seems like there's going to be no further activity on this pull request, so we’ve closed it for now. Please open a new pull-request if you want to re-approach this work, or for anything else you think could be fixed or improved.

The preview is on the right of your screen, our definition of preview must be different.

This is a generic preview of the page and not a preview of a specific block AFAIK.

@brynwhyman @Cheddam I'd really like to see how much effort it would take to get this over the line. It would be game changer for users.
As a side note @sunnysideup might release a similar thing as a module here https://github.com/dnadesign/silverstripe-elemental/issues/745 but I'm unsure if it includes inline blocks and scrolls/opens the blocks.


Button animation on Page Load

Buttons seem to scale from small to normal size on page load.

Thanks Again!


CNF-12206: introduce new .status.history field to understand timing of each stage and their phases

Background / Context
A new status history field is added to understand when and for how long each stage may run successfully.
Solution / Feature Overview

History is reset when Idle.
Each history entry on the list will appear chronologically and will have startTime to indicated when a stage was called for the first time. Optionally completionTime will appear when the stage is successful.
A stage may have a one or more Phase to help understand important tasks that were performed. Similar to history entries, each Phase will have a startTime and optionally a completionTime.

'Prep' stage entry will have the follow:

Stateroot: Time taken to create the new stateroot.
Precache: Time taken to pull all images specified by the image list built into the seed image.

'Upgrade' stage entry will have the follow:

PrePivot: Time taken complete all the steps before reboot is called
PostPivot: Time taken complete all the steps after a reboot to a new stateroot
Reboot time can be calculated with PrePivot completionTime and PostPivot startTime.

Other Information

/cc @Missxiaoguo @jc-rh @donpenney

/test integration

/lgtm

/cherrypick release-4.16


Version 1.3 issue on Wordpress multisite (MU)

I just upgraded from version 1.2.1 to version 1.3 of the Wordpress plugin on a multisite website (MU). Although I'm only using the plugin on one of the sites, Wordpress MU has a special directory structure for uploads (such as images uploaded via the plugin). Files get uploaded into a path similar to this:
/www/wp-content/blogs.dir/1 (and each site gets a numerical directory, so 2, 3, 4, etc.)
I had no issues with version 1.2.1, but on version 1.3, although the images DO get uploaded to the correct place, the front end looks for the images in an incorrect directory. Instead of preserving the MU directory structure (see above), it adds the site's sub-folder to the path; for example:
/www/MYSITE/wp-content/blogs.dir/1
I re-installed 1.2.1 on the meantime.
Thanks!

Ok thanks for the heads up. Will have a look.

Found a dirty work around for this in MU.
In the plugin editor (or however you choose to edit the file) nivo-slider-for-wordpress/nivoslider4wp.php file edit the line(s) that tell the nivo uploader to send to the default (non-WPMU) "uploads" folder to "files". Since the plugin automatically appends the site_url (and blog.dir) path you need only to continue the desired file upload location.
------------- OLD ---------------------------
function nivoslider4wp_install() {
$nivoslider4wp_files = ABSPATH."wp-content/uploads/nivoslider4wpfiles";
$nivoslider4wp_files_old = ABSPATH."wp-content/nivoslider4wp_files";
image path yields - http://siteurl.com/wp-content/uploads/nivoslider4wpfiles/image_name.jpg
------------ NEW ---------------------------
function nivoslider4wp_install() {
$nivoslider4wp_files = ABSPATH."files";
$nivoslider4wp_files_old = ABSPATH."files/nivoslider4wp_files";
image path yields - http://siteurl.com/files/image_name.jpg

Of course you can adjust your file structure anyway you need.
Sorry i generally suck at explanations... hopefully the example will help.


Can't update remote settings (URI, user, etc)

Abstract
Once set I can't edit the remote settings, such as the URL or the user or password. I changed the domain name for my CouchDB instance and I can't edit the settings to hit it.
Expected behaviour
Fields in the remote settings section are all editable.
Actually happened
Remote settings are greyed out / unchangeable.
Reproducing procedure

Configure LiveSync as in the attached material.
Go to settings & try to change the remote URI
Notice how it is greyed out and can't be changed.

Screenshots

You should stop syncing first. In "Sync Settings"，set the "Presets" to "Disable all automatic", then try again.

That worked, thank you.
On Sun, Jun 23, 2024 at 2:00 AM Lraxer @.***> wrote:

You should stop syncing first. In "Sync Settings"，set the "Presets" to
"Disable all automatic", then try again.
—
Reply to this email directly, view it on GitHub
https://github.com/vrtmrz/obsidian-livesync/issues/456#issuecomment-2184909427,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6NPROM37BFU67OFBANSP3ZI2FDBAVCNFSM6AAAAABJU4QTUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBUHEYDSNBSG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thank you for opening the issue!
I am so glad it has been resolved. But sorry for being late!
However, I think that some notes should be displayed. It will be implemented in a while.
I would love to thank you all for your contributions. This issue is closed with all respect and gratitude.


bug: calculate camera param in augmentation

https://github.com/Megvii-BaseDetection/BEVDepth/blob/a030aae76f5c74830f0707db4b10136adf3bcaea/dataset/nusc_mv_det_dataset.py#L75
Maybe should be changed to ida_mat[:2, 2] = ida_tran.

In theory, there is no doubt that ida_tran should be placed in [:2, 2], but I also used visualization to verify, and the visualization results of the modified version are in line with expectations.
Raw:

Wrong:

Right:

The matrix we use is 4x4, that's why we use ida_mat[:2, 3] = ida_tran.

I use 4x4 matrix too. Here:
The final lidar2img = ida_mat @ cam_in @ cam_out
And the points in visualization is calculed by pts2d = pts4d @ lidar2img.T and divided by pts2d[:, 2] where pts2d[:, 2] > 0, which pts4d is (N, 4) in format (x, y, z, 1).
Is there anything wrong?

I meet the same question and it works to change ida_mat[:2, 2] = ida_tran.


add symbol name to error message

add symbol name to error message
https://github.com/dmlc/mxnet/issues/3391

This only works for legacy op. It should be put into nnvm's infershape pass

@piiswrong  ok move to nnvm  https://github.com/dmlc/nnvm/pull/69


Don't install it on the same machine as Power BI gateway

A recommendation is that the SHIR should not be installed on the same server as the Power BI gateway. Why is this? I want to install it on an on prem server so the ADF can access on prem datasources. My understanding is the communication is outbound on 443 so it's not listening like a server with inbound traffic.
We have a Datagateway installed on the machine as well as a Hybrid Relay. They both poll on 443 to the Azure relay, but there is no recommendation stating these shouldn't be installed together. I would have expected the same for the SHIR. Just wondering how it is different.
Regards,
K

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

ID: 32785d15-8202-6e44-f1d2-420ef0600f3f
Version Independent ID: 3af5fa49-7bd4-18ce-f8dc-aa4a2b8c6478
Content: Create a self-hosted integration runtime - Azure Data Factory & Azure Synapse
Content Source: articles/data-factory/create-self-hosted-integration-runtime.md
Service: data-factory
Sub-service: integration-runtime
GitHub Login: @lrtoyou1223
Microsoft Alias: lle

@k-harrington
Thanks for your feedback! We will investigate and update as appropriate.

Appreciate it, thank you!

Hello @k-harrington
The suggestion to avoid installing the Self-Hosted Integration Runtime (SHIR) on the same server as the Power BI gateway is mainly because of potential port conflicts. Both the SHIR and Power BI gateway use port 443 for communication, and if they are on the same server, there's a risk of conflicts causing issues.
Please go through this below link for your reference.
https://learn.microsoft.com/en-us/azure/data-factory/create-self-hosted-integration-runtime?tabs=data-factory#installation-best-practices:~:text=their firewall configuration.-,Note,the main ports being used by Power BI gateway as well.,-Self-contained interactive
In simple terms, it's not a good idea to put SHIR and Power BI gateway on the same server due to potential port problems, but it's safe to install Data Gateway and Hybrid Relay together. Let me know if you have more questions.


Filter out look-a-likes (?) from popular tokens

Still need to filter out the boosted pool bpt's correctly...

Tokens need to be blacklisted in cms.


build(IE): better pipeline

v13.5.1 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.


Data: project addition (Netflix Clone)

Add a new project to the list
@priyankarpal i want to add my project in your website
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Sure
On Thu, 8 June 2023, 1:48 pm github-actions[bot], @.***>
wrote:

This issue has been automatically marked as stale because it has been open
for few days with no activity. It will be closed in next 1 days if no
further activity occurs.
—
Reply to this email directly, view it on GitHub
https://github.com/priyankarpal/ProjectsHut/issues/1095#issuecomment-1582118055,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4UJ2WQDPJKGX5ADYA6H2G3XKGDENANCNFSM6AAAAAAYZ3M7NA
.
You are receiving this because you were assigned.Message ID:
@.***>


Routing: Does not minimise total distance for fleet

When I optimise a route with 1 vehicle, I get a shorter total route compared to when I add vehicles. It seems to prefer routes of equal distance, instead of assigning the most efficient route to a single vehicle.
Optimisation with 1 vehicle:
tsp_order = tsp(osrm_dist, num_vehicles=1, max_duration=4*60*60)

Route for vehicle 0:
0 -> 1 -> 3 -> 4 -> 5 -> 6 -> 2 -> 29 -> 28 -> 34 -> 33 -> 32 -> 43 -> 44 -> 42 -> 36 -> 37 -> 35 -> 38 -> 39 -> 41 -> 40 -> 31 -> 30 -> 100 -> 99 -> 98 -> 97 -> 88 -> 92 -> 90 -> 89 -> 91 -> 93 -> 94 -> 95 -> 96 -> 70 -> 71 -> 69 -> 68 -> 67 -> 66 -> 65 -> 64 -> 7 -> 14 -> 13 -> 11 -> 10 -> 9 -> 8 -> 24 -> 23 -> 22 -> 20 -> 12 -> 18 -> 17 -> 16 -> 15 -> 21 -> 19 -> 73 -> 75 -> 74 -> 72 -> 77 -> 76 -> 79 -> 78 -> 84 -> 80 -> 81 -> 82 -> 83 -> 86 -> 85 -> 87 -> 46 -> 53 -> 51 -> 50 -> 54 -> 52 -> 56 -> 55 -> 49 -> 48 -> 47 -> 45 -> 57 -> 61 -> 58 -> 60 -> 59 -> 62 -> 63 -> 27 -> 26 -> 25
Route duration: 3:12:15

100/100 points used
Total duration: 3:12:15

Optimisation with 4 vehicles:
tsp_order = tsp(osrm_dist, num_vehicles=4, max_duration=4*60*60)

Route for vehicle 0:
0 -> 3 -> 4 -> 5 -> 6 -> 2 -> 87 -> 85 -> 79 -> 78 -> 77 -> 76 -> 73 -> 75 -> 74 -> 72 -> 84 -> 80 -> 81 -> 82 -> 83 -> 86 -> 57 -> 61 -> 58 -> 59 -> 60 -> 62 -> 63
Route duration: 1:40:52

Route for vehicle 1:
0 -> 46 -> 52 -> 54 -> 50 -> 51 -> 53 -> 47 -> 48 -> 49 -> 55 -> 56 -> 45
Route duration: 1:43:21

Route for vehicle 2:
0 -> 29 -> 28 -> 34 -> 33 -> 32 -> 44 -> 43 -> 42 -> 37 -> 36 -> 35 -> 38 -> 39 -> 41 -> 40 -> 31 -> 30 -> 97 -> 98 -> 99 -> 100 -> 89 -> 90 -> 92 -> 95 -> 96 -> 91 -> 93 -> 94 -> 88 -> 1
Route duration: 1:26:01

Route for vehicle 3:
0 -> 12 -> 18 -> 17 -> 16 -> 15 -> 21 -> 19 -> 24 -> 23 -> 22 -> 20 -> 8 -> 9 -> 14 -> 13 -> 11 -> 10 -> 7 -> 64 -> 68 -> 67 -> 69 -> 71 -> 70 -> 65 -> 66 -> 27 -> 25 -> 26
Route duration: 1:31:52

100/100 points used
Total duration: 6:22:06

The distance matrix used (with seconds as units) is the same in both cases, but as the optimiser forces to have routes of similar length for each vehicle, the total distance is actually twice longer. Is this intended? Is there a way to minimise the total distance for a fleet?
In the code below, I use penalties to allow dropping of points that would make the solution infeasible taking into account the maximum length of each vehicle route. However, additionally I would like to know if there is a way to force points to be in, and others that would be optional to fill the route.
The ortools version i am using is 7.0.6546 and here is the complete code.
Thanks in advance for your help and thank you for the amazing work put into this library.
from __future__ import print_function
from ortools.constraint_solver import routing_enums_pb2
from ortools.constraint_solver import pywrapcp
import numpy as np

def tsp(dist_df, num_vehicles=1, max_duration=3 * 60 * 60):

    # Instantiate the data problem.
    data = create_data_model(dist_df, num_vehicles)

    # Create the routing index manager.
    manager = pywrapcp.RoutingIndexManager(len(data['distance_matrix']),
                                           data['num_vehicles'], data['depot'])

    # Create Routing Model.
    routing = pywrapcp.RoutingModel(manager)

    def distance_callback(from_index, to_index):
        """Returns the distance between the two nodes."""
        # Convert from routing variable Index to distance matrix NodeIndex.
        from_node = manager.IndexToNode(from_index)
        to_node = manager.IndexToNode(to_index)
        return data['distance_matrix'][from_node][to_node]

    transit_callback_index = routing.RegisterTransitCallback(distance_callback)

    # Define cost of each arc.
    routing.SetArcCostEvaluatorOfAllVehicles(transit_callback_index)

    # if num_vehicles > 1:
    # Add Duration constraint.
    dimension_name = 'Distance'
    routing.AddDimension(
        transit_callback_index,
        0,  # no slack
        int(np.round(max_duration)),  # vehicle maximum travel distance
        True,  # start cumul to zero
        dimension_name)
    distance_dimension = routing.GetDimensionOrDie(dimension_name)
    distance_dimension.SetGlobalSpanCostCoefficient(1000)

    # Allow to drop nodes.
    penalty = int(np.sum(np.sum(dist_df)))
    for node in range(1, len(data['distance_matrix'])):
        routing.AddDisjunction([manager.NodeToIndex(node)], penalty)

    # Setting first solution heuristic.
    search_parameters = pywrapcp.DefaultRoutingSearchParameters()
    # search_parameters.time_limit.seconds = 30
    search_parameters.first_solution_strategy = (
        routing_enums_pb2.FirstSolutionStrategy.PATH_CHEAPEST_ARC)

    # Solve the problem.
    solution = routing.SolveWithParameters(search_parameters)

    # Print solution on console.
    if solution:
        index_order = print_solution(data, manager, routing, solution)
        return {
            vehicle: dist_df.index[order].values
            for vehicle, order in index_order.items()
        }
    else:
        return "Could not optimise"

def create_data_model(dist_df, num_vehicles=1):
    """Stores the data for the problem."""
    data = {}
    data['distance_matrix'] = dist_df.round().astype(int).values
    data['num_vehicles'] = num_vehicles
    data['depot'] = 0
    return data

def print_solution(data, manager, routing, solution):
    from datetime import timedelta
    """Prints solution on console."""
    index = routing.Start(0)
    index_order = {}
    vehicle_distance = []
    for vehicle_id in range(data['num_vehicles']):
        print('\nRoute for vehicle {}:'.format(vehicle_id))
        index = routing.Start(vehicle_id)
        route_distance = 0
        index_order[vehicle_id] = []
        while not routing.IsEnd(index):
            index_order[vehicle_id].append(manager.IndexToNode(index))
            previous_index = index
            index = solution.Value(routing.NextVar(index))
            route_distance += routing.GetArcCostForVehicle(
                previous_index, index, 0)

        print(' -> '.join(map(str, index_order[vehicle_id])))
        print('Route duration: {}\n'.format(
            str(timedelta(seconds=route_distance))))
        vehicle_distance.append(route_distance)

    print('{}/{} points used'.format(
        np.sum([len(v) - 1 for k, v in index_order.items()]),
        data['distance_matrix'].shape[0]-1))
    print('Total duration: {}'.format(
        str(timedelta(seconds=int(np.sum(vehicle_distance))))))
    return index_order

this is because you use distance_dimension.SetGlobalSpanCostCoefficient(1000) whose the goal is exactly to minimize the longest route.
see https://developers.google.com/optimization/routing/vrp#distance_dimension
ref: https://github.com/google/or-tools/blob/39f44709bba203f5ff3bc18fab8098739f189a6d/ortools/constraint_solver/routing.h#L1833-L1839

Indeed this has fixed it, thank you so much @Mizux for your quick reply! I was not actually sure what the restriction did.
Referring to the variable penalties, I only seem to go from including all the points or none of them. Would you have an example where different penalties per point are used?
The main problem I am trying to solve is an optimisation within a full week, where different points (waste containers in this case) have different collection frequencies. As it is not possible to pass multiple frequencies to the optimiser, I thought that I could iteratively organise the routes within the week where, depending on the frequency, containers would be mandatory for a certain route/day.
I understand you may want me to reformulate this in a new issue, but did not want to flood the issue listing either.
Best wishes

not sure to well understand  but you can duplicate your node and supposing you have node A twice a week, and B four time a week you could add drop penalty like this
A1 penalty 50000
A2 penalty 50000
B1 penalty 25000
B2 penalty 25000
B3 penalty 25000
B4 penalty 25000

i.e. dropping a visit (B) with high frequency has less impact (25000) than dropping a visit (A) with less frequency.


Create a form for configuring an evaluation

All current evaluation runners rely on strict JSON for evaluation configuration. In the case of the UI, a barebones code editor is provided with the option to load previous work. This is not particularly workable if you're not intimately familiar with how the configuration is put together. Instead, there needs to be a (relatively) straightforward form that provides help and restricts options.

#103
Describes the UI step


Fixed crit hack (i think)

Crithack should now allow forcing crits.


Vue not preserving background-related inline styles after component redraw

Version
2.6.8
Reproduction link
https://jsfiddle.net/5x81bd6z/
Steps to reproduce
Just wait 10s for the setTimeout to kick in.
The problem is that after the component is redraw, only the background: url(img) is preserved, but the other background-related inline styles are ignored. For example "background-size: cover".
You will see that after 10s, not only the order of
 elements will change, but the backgrounds will change too.
What is expected?
Change the order of
 elements and preserve all inline styles.
What is actually happening?
Only part of the inline styles of
 are preserved after component redraw.

background is a shorthand property, when set it overwrites all other background related properties. Using an object, iteration order is not guaranteed (depends on browser), so the behavior cannot be consistent.
Use background-image instead.

@yyx990803 I think you are addressing slightly different problem.
This part of code is generated by vue template upon the component mount

This is the same part after changing the value of instance property (array stuff in the example)

After the partial redraw, some of the inline css properties are missing for no reason.


fuzz: remove invalid characters from cluster header names

Removes invalid characters from header names in route_fuzz_test
Risk Level: Low
Testing: Corpus entry added
Fixes Issue:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15241
Signed-off-by: Asra Ali<EMAIL_ADDRESS>

/azp run