Xcake 0.7.X Roadmap

Here are at 6 Months after Xcake's release and we have just pushed the last version of 0.6.x
This has been our most successful release ever, Spanning 25 minor versions, 6 Months and over 1,000 Downloads. We've had our most number of external contributions to this version as well.
In this series we overhauled the entire generator system in order to easily control what happens in each order via a dependency graph, reduced them so that each generator handles a small part of the project to increase testability and introduced a context object to remove many of the hacks used to get additional information needed during generation for the project (For example when setting up XCConfig Files).
However there comes a time where the creaks start to show and I believe we have reached this with 0.6.x. So what's planned for 0.7.0:
New File Reference And Build Phase Generators
This will be the large portion of the work, the system for creating file references and creating build phases is fragmented and handled by multiple classes. The goal for us will be similar to the recent refactor of the generator system:

Break the system up into smaller components.
Abstract them in a way so each phase only needs to do the minimum to achieve it's goal and it can be reusable by other parts of the code.
Simplify the system so they no longer have to use hacks or complicated logic.

So how will we achieve this with 0.7, well let's first look at the issues with the current system:

File References outside of include_files rely on hacks or duplicating behaviour (i.e for XCConfig or Info.plist).
Adding support for Variant Groups (i.e for Localised files) relied again on hacks or duplicate behaviour.
The file installers rely on a few tricks to make sure they add the files to the correct build phases in the right order which could be simplified - they both classify and install files which is two concerns.
The user can't define their own build phases (Except run script)  and any code inside of the system has to duplicate the code to create their own.
It can be difficult to get an existing File Reference for a file.
The code for creating Groups in the project has grown very complex. (i.e to handle variant groups and to handle setting the correct target for a group).

So how can we resolve these issues? Well we will break these down into phases and individual generators, so here are the phases in order:
Phase 1: File Reference Generator

Add Groups / Variant Groups with correct path so that it opens in Xcode, Have right Name and Target.
Add File Reference to project

Phase 2: Run Any Generators That May Create Build Phases.

For example we create build phases to embed a watch app (Although this could be potentially moved to being created in the DSL).

Phase 3: File Reference Build Phase Association Generator

Collect all files in include_files which aren't referenced in another build phase.
Use File Classifiers to figure out which build phase they belong to.
Tweak DSL so that they are added to a build phase.
This could potentially be done as part of the DSL instead.

Phase 4: Build Phase Generator

Take Build Phases defined in DSL, Create Them and add any File References they refer to. (DSL will be extended to allow users to define all types of build phases)

Feature-wise this will:

Simplify way groups and files are added.
Allow files to be added easily from other sources not just include_files.
Simplify way build phases are created, open it up to other generators and the user.
Extend build phase types that can be created by the user in the DSL.
Potentially Fix https://github.com/jcampbell05/xcake/issues/92

Aggregate Targets
Add the ability to specify aggregate targets, this would involve creating a new type of target since Xcodproj uses a different class for this.
UI Tests
Add the ability to implement UI Tests, this will involve extending support for multiple testing targets for each target.
Other Goals
To resolve all outstanding Github Issues before 0.8.0 and publish some documents on the internal structure of Xcake to help contributors out :)

Sounds like a great direction.
The Ello app also needs Share Extension target support, so if that's easy to accomplish during this refactor, it would make it easier for that project to adopt xcake!

@colinta I can look at how Xcake pull's that off. I'm sure we should be able to do it since the Watch app is already an extensions and Xcake already supports that.

@colinta  so the initial file installer refactor has been implemented which simplifies the system. One side effect is xcode now selects the right groups when adding to a group
I think next I'll work on adding Extensions, UI Testing and Aggregate Testing Support.
After some testing I think 0.7will be good to go.

You've been busy! I'll try out what you've uploaded so far.

On Jul 12, 2016, at 3:24 AM, James Campbell<EMAIL_ADDRESS>wrote:
@colinta so the initial file installer refactor has been implemented which simplifies the system. One side effect is xcode now selects the right groups when adding to a group
I think next I'll work on adding Extensions, UI Testing and Aggregate Testing Support.
After some testing I think 0.7will be good to go.
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@colinta Great, any feedback or regressions let me know. It's not pushed yet so you should be able to install from master.

Should be releasing this week @maximkhatskevich  @colinta

0.7 is released, just need to get a test passing for https://github.com/jcampbell05/xcake/pull/103 @maximkhatskevich - Will push this in a 7.1

Great! Thanks, dude!

@maximkhatskevich  UI Tests should be pushed in 0.7.1 :) Will close this and start working on all the issues you've raised :)


[BUG] Station Assembler Crash

Version of Advanced Rocketry

[AdvancedRocketry-1.16.5-2.0.0-12-universal.jar

Have you verified this is an issue in the latest unstable build

[x] Y

Version of LibVulpes

LibVulpes-1.16.5-1.0.2-25-universal.jar
Version of Minecraft

1.16.5

Does this occur without other mods installed

[x] No, Needs mekanism

Crash report or log or visualVM (if applicable)
http://pastebin.com is a good place to put them
crash reports that are put in the issue itself are
hard to read

https://pastebin.com/ad0ZxxGx

Description of the problem

When using the mekanism universal power cables in a build for the station assembler, it crashes servers. Not tested if this happens in single player.

Did you try to assemble cables? If so, that's your issue. Some tiles simply cannot properly be assembled.


correct answers are not showing after submission

show a correct answer after submit

May I work on this issue?

Yes you can work on that
Thanks for contributing

The correct answer should be display below the quiz box after pressing the submit button?

I have stored the correct answer in an array

I can't find that array, but I solved the issue by fetching the correct answer from the api directly when the submit button is pressed. Is that okay?

Hey, actually I misunderstood the issue. The MAIN issue here is that the question that is being displayed on the page is not correct, the options are correct.
Just so to confirm, was this the main issue?
Because I thought you wanted something like this:

Change the font family

Use the one used for question

Hey, actually I misunderstood the issue. The MAIN issue here is that the question that is being displayed on the page is not correct, the options are correct.
Just so to confirm, was this the main issue?
Because I thought you wanted something like this:

I don't understood what you mean

Hey, actually I misunderstood the issue. The MAIN issue here is that the question that is being displayed on the page is not correct, the options are correct.
Just so to confirm, was this the main issue?
Because I thought you wanted something like this:

Oh jus

PR sent! Please do check.

Okay

Hey @CH1NRU5T
Please make the changes
Remove new answer ui
And make the correct answer in green color and red for wrong in the question itself
It can be done by settimeout for the whole elements in submit function showing the exact      answer for only 2 seconds

On it!

Done @johnbabu021 , PR sent!


Improve queue dispatcher

in Aggregation, Switchboard

working on a new class:
class IsBackend t where
    typeof :: BackendKind
    setup :: Configuration -> IO ()
    terminate :: t -> IO ()
    pass :: t -> NamedLogItem -> IO ()
    passfrom :: forall s . (HasPass s) => t -> NamedLogItem -> s -> IO ()
    default passfrom t nli _ = pass t nli


Use zuilnt for linting.

I have mostly moved the code around to make it compatible with zulint style.
One important change I would like to mention is, now ./tools/lint also runs ./tools/run-mypy. I can easily disable it too.

@andersk updated with requested changes!

@amanagr do you have a chance to update this?

I am getting an error based on this issue.
pep8      | /Users/amanagrawal/python-zulip-api/zulip-api-py3-venv/lib/python3.7/site-packages/pycodestyle.py:113: FutureWarning: Possible nested set at position 1
pep8      |   EXTRANEOUS_WHITESPACE_REGEX = re.compile(r'[[({] | []}),;:]')

The solution is to upgrade pycodestyle to v2.4 or above. While this fixes the warning we get, it introduces around 100 new errors due addition of new rules to it. I will upgrade it perhaps in a different new PR.

Sorry I missed your reply!  Looking now.


Created Install Script for Debian

Motivation
I looked at the Ubuntu script created by Howard and I made one main modification to make it work for Debian. In the Debian repos the LLVM and Clang packages are old. To solve this issue I grabbed the LLVM and Clang packages directly from the LLVM repo. For the reviewer checking this... the original source for the LLVM part of the script is below.
Source: https://apt.llvm.org/llvm.sh
I made some minor modifications to the above script and Howard's Ubuntu Script to create a working Install Script for Debian.
I also added Debian Install instructions to the Docs and I added a Beta tag next to the Debian instructions in the Docs for clarity.
Test Plan
I have tested the script multiple times in Debian with no errors. I purged all installed packages and re-ran the script multiple times and got almost exactly the same output that you get when you run the Ubuntu Script in an Ubuntu OS.
Related PRs
(Link any related PRs here)

Hi, thx for taking the time to make this. However, this is based on an older version of the ubuntu script. It's better form to only require root for the actions that need it (installing packages, firewall rules), and not for the build. This was updated a few days ago for the ubuntu script. Note that the ufw commands were removed, and it's left up to the user to make sure these ports are open.
So please rebase your branch to bring it in line with the current script. I'll also add some comments on specific lines.

Yes this seems like a better approach. I'm not sure we should bundle llvm.sh with snarkOS though.

The file build_debian.sh should be committed with 755 permissions.

@fabrinasr can you re-target to the staging branch please?


mobile text selection

Great to find this project! Any thoughts on if/how to support selection popover on mobile?

Haven't looked into that much. If you figure it out would definitely accept a PR :)

Cool! I'm not sure if I'll be looking into it, but I'll let you know if I do.


RemovedInDjango110Warning: SubfieldBase has been deprecated. Use Field.from_db_value instead.

Please, check your social.apps.django_app.default.fields.JSONField and refactor code, need to remove usage of SubfieldBase...
https://docs.djangoproject.com/en/1.8/releases/1.8/#subfieldbase
Tested on Django1.9a1, Python 3.5

Also I suggest to use https://docs.djangoproject.com/en/1.9/ref/contrib/postgres/fields/#django.contrib.postgres.fields.JSONField
if Django >= 1.9 and django.contrib.postgres in installed apps...

With the Django 1.10 dev this gives a error indeed, when you try to create the migrations.

I'm getting the same error twice when starting the development server. I'm using python-social-auth (0.2.14) and Django (1.9.1).

Also fixed by #813

when is this releasing?

News on this topic?

I get this warning on latest 0.2.21 version, so not yet fixed.

I can see warnings with the Django 1.9.11

This got fixed.


Wa/mobile/feature/follower pop up 266

Did the changes for following pop up in this branch because it was too related. #273

it works fine


Had to input SSH password several times

According to https://github.com/trufflesuite/truffle/issues/893#issuecomment-381379183, I had to several times insert my SSH password to be able to meta git update Truffle.
This is really annoying.

I'm usning windows 10, and I was cloning via ssh actually.
I mainly use Powershell. But the same behavior happened with Ubuntu inside windows. I was actually  using Meta to build truffle as you can see in my previous message.


Allow custom model for mobile devices (repurpose gear wheel as setting button)

In master the custom model is only active if the custom model box is visible which leads to bugs:

We disabled custom model for mobile devices (small screens) as the app would become unusable with an open custom model box. And so links with a custom model in the URL will (silently) show the wrong route on mobile devices as the custom model is removed.
switching between mobile and desktop sizes does not work as the custom model gets lost
custom model gets lost or encoded values are not properly initialized when minimizing (with the x button) and then showing the sidebar again (hamburger button)

In this PR changes I basically moved the custom-model object state from the custom-model-editor into the SettingsStore that lives regardless of the UI component.
And so we can change how the gear wheel button works: the button now just opens a new settings box where we can change the miles/kilometer settings and also if the custom model is enabled or not. (A small shadow under the gear wheel is shown when the custom model is enabled. I'm open to suggestions to make it more obvious.)
And because the custom model editor does no longer store the custom model itself and also not if the custom model is enabled we don't have to always show the custom model editor and the above problems for small screen sizes disappear and we can additionally support custom models for mobile devices. Furthermore we can easily add new settings (like the dark mode option) without adding more stuff to the main view.

[x] trigger routing if "custom_model" in URL parameter (but keep settings box closed). For that I had to use and extract the validateJson method from the custom model editor.
[x] avoid route re-calculation if settings box is shown (with enabled custom model box)
[x] make json invalid -> hide settings box -> now default custom model example is shown instead of invalid (completely different) custom model before -> for now fixed it and closing the settings box means "reset to custom model before invalidated one". Is different than before but IMO makes sense now.
[x] fix a tricky problem with jest and ES6 modules.
[ ] remove QueryStoreState.customModel as we have it in the SettingsStore?

You can try it out here.

switching between mobile and desktop sizes does not work as the custom model gets lost
custom model gets lost or encoded values are not properly initialized when minimizing (with the x button) and then showing the sidebar again (hamburger button)

This is a little bug we introduce when we added the custom model examples: We overwrite the current custom model with the default example, even when we entered our own model before. It can be fixed like this:
https://github.com/graphhopper/graphhopper-maps/commit/b2263608d98fddd9180f0e42fefffba87227f01c


Was the name of the generator generated?

Dear @zivlakmilos
how did you come up with the name?

ChatGPT. Every serious programmer use it. 😀


Subexpense: Savings

Dont just show savings like all expenses!

Realistically, I don't think I'll be adding features anytime soon.


Automated Shipit deploys

Overview
Yesterday we had to backfill the releases that should have been deployed in https://github.com/Shopify/quilt/commit/c17467957eaa0fe82a7b71c0f7319885453601ef. This is because in Shipit, we had forgotten to deploy c17467957eaa0fe82a7b71c0f7319885453601ef in the queue before deploying subsequent "Publish" commits.
When commits pile up, it can be easy to miss "Publish" commits. Ideally, the author of that "Publish" commit deploys on shipit, but sometimes we forget (slow CI, jumping into meeting/interviews, etc). When this happens we have to manually find out what went wrong, which packages to backfill etc. Even backfilling has it's flaws because the latest tag on the package is updated to the backfilled version.
What to do?
We should explore & builds tooling to support automating monorepo deploys on Shipit.

Continuously Deploy (release packages) on tagged "Publish" commits with passing CI.
Noop on "Publish" commit tags

Reading through slack messages in #shipping-pipeline, we do something similar for gems

It triggers a deploy for every pushed commits, however if the commit doesn't bump the genspec version it simply noop.

Moving out of this sprint


Escaped macros and 'end'

In the code below some ends have had to be replaced by {{"end".id}} or it wouldn't compile. In comments there's the error that the compiler gives if you switch the latter for the former.
macro open_record(name)
  class {{name.id}}
    macro method_missing(name, args, block)
      \{% if name.split("").last == "=" %}
        @\{{name.id}} \{{args.argify}}
      \{% else %}
        @\{{name.id}}
      \{% end %}
    {{"end".id}} # expecting token 'EOF', not '%}'

    def to_h
      \{% if @type.instance_vars.any? { |var| var } %}
        {
        \{% for ivar in @type.instance_vars %}
          \{{ivar}}: @\{{ivar}},
        \{% end %}
        }
      \{% end %}
    {{"end".id}} # expecting token 'EOF', not 'end'
  {{"end".id}} # expecting token 'EOF', not 'end'
end

It appears that the more methods with escaped macros I add to the main macro, the more ends need to be changed to {{"end".id}}: If I add another method with an escaped macro it won't compile no matter how many ends I change. And if I remove #to_h, the end of the class doesn't need to be {{"end".id}}.
This started to happen with the release of 0.7.1.

I think these are just macro parsing bugs. They will eventually be fixed.
As a side note, I wouldn't advice having macros inside macros. In your case you could use a module:
module OpenRecord
  macro method_missing(name, args, block)
    {% if name.split("").last == "=" %}
      @{{name.id}} {{args.argify}}
    {% else %}
      @{{name.id}}
    {% end %}
  end

  def to_h
    {% if @type.instance_vars.any? { |var| var } %}
      {
        {% for ivar in @type.instance_vars %}
          {{ivar}}: @{{ivar}},
        {% end %}
      }
    {% end %}
  end
end

class Foo
  include OpenRecord
end

foo = Foo.new
foo.x = 1
foo.y = 2
p foo.to_h

However, I don't think that to_h method is a good choice. Why do you need that? Ruby tends to use arrays and hashes for everything, in Crystal that usually doesn't work because of the static types.

Ah, and note that that to_h method is broken, it should be a macro def but there's no way to know the return type. That's why I'm suggesting not having code like that.

It's sample code to illustrate the bug. Of course it won't win any contests :stuck_out_tongue_closed_eyes:

@Exilor This if fixed in HEAD now, you can try it. The above snippet works with regular "end" now (it stops working with the hacky "end"). If you find more of these, please report them too :-)

Nice :D


ProtocolError: invalid serialization of WAMP message

I'd like to send a string by wamp, like this: "¬4薚b".
Payload is dumped to this:
S'[70,9,{},[{"retcode":200,"data":[{"dev_id":"\u00004\xe8\x97\x94\xe5\x90\x84"}]}]]'.
Crossbar will produce failure. The detail is following:
Traceback (most recent call last):
File "/Users/erlang/anaconda/lib/python2.7/site-packages/autobahn/wamp/websocket.py", line 88, in onMessage
for msg in self._serializer.unserialize(payload, isBinary):
File "/Users/erlang/anaconda/lib/python2.7/site-packages/autobahn/wamp/serializer.py", line 106, in unserialize
raise ProtocolError("invalid serialization of WAMP message ({0})".format(e))
ProtocolError: invalid serialization of WAMP message ('ascii' codec can't encode character u'\xcb' in position 1: ordinal not in range(128))

you need to send (unicode) strings, not binaries


Support Context Menu/Actions for Values in the Debug Hover

This is the debug hover:

I think it would be great if each value has a context menu (or inline buttons) to trigger (contributable) actions.
Built-in actions could be:

copy value
copy expression
watch

Actions contributed by extensions could be:

visualize 😉

This is already supported in the sidebar:

@hediet good overall idea and I like it. I think we could implement it fairly easily by adding a new menu type to the hover tree. We can even open it for extensions as you suggested.
However I would be interested in what other apps do you know that have a context menu on the hover? Might this be a sort of an anti pattern? I know that the debug hover is a bit heavy and a context menu might fit well there, but I would be interested in how other products do it. Maybe try out Visual Studio, Chrome Dev Tools and others...
fyi @misolori

I do believe that's using the tree widget, which supports inline actions:

I'd assume either a ellipsis (though there is quite a bit already in these views) orgear:

@hediet good overall idea and I like it. I think we could implement it fairly easily by adding a new menu type to the hover tree. We can even open it for extensions as you suggested.
However I would be interested in what other apps do you know that have a context menu on the hover? Might this be a sort of an anti pattern? I know that the debug hover is a bit heavy and a context menu might fit well there, but I would be interested in how other products do it. Maybe try out Visual Studio, Chrome Dev Tools and others...
fyi @misolori

VS has quite a few nested context menus :D

I'd assume either a ellipsis (though there is quite a bit already in these views) orgear:

I like that really much! Would be awesome if extensions could introduce top level actions (that would be useful for a "visualize" action :D), but I understand if that is costs too much space.

I think that would be possible since it's a toolbar, we do show more inline actions in peek/diff views:

Cool ideas. Maybe just a right click context menu might work best.
But an additional gear on the end to make it discoverable will help. Ellipsis look good in the example you provided but in practice we have a lost of overflowing text and it is all shown with ellipsis, so I think it would be very confusing, as some ellipsis would be clickable and some not...
@misolori is right, it can be made possible if we make it a toolbar, however I would be worried about opening inline actions to extensions since horizontal space is already limited. I would first only open secondary actions - the one behind a context menu. Though I am flexible.

@hediet can you verify this one? 🙂


Refresh page from server upon submit

This is in response to @luc-ass / Issue #6.
Adding line 273 refreshes the page (from the server, not from the cache) when the "Generate" button is pressed. This resets the form values, preventing web browsers from retaining cached information and producing duplicate profiles (even when the form input is changed by the user).
I have tested creating numerous profiles with this change, and all have been produced as intended. After your testing, I believe this bug can be resolved.

Couldn't this, in theory, cause the page to reload before the rest of the javascript (which creates the profile, prompts for download) executes?
Perhaps this should be placed AFTER the download line.. (:338)

Either way! In my testing it did not, but I understand that it some browsers may react that way. Good call!

Thank you @antoniodowling !


Merge / project more samples onto one sample.

Yes just that one ;-)

ZarrMerge and run_unified_umap both now  support multiple objects. Feel free to try them.

I'm closing this cause I believe this has been solved.
If not, then please feel free to reopen this issue.


Use systemd/sd-daemon.h headers for systemd presence

Finding systemd devel packages using libsystemd does not work as
in RHEL based distro the package name is systemd-devel and for
deb/ubunutu it is libsystemd. It is also giving false result when
podman rpm is built with systemd but hack/systemd_tag.sh does not
return anything.
Moving to systemd/sd-daemon.h header files which comes from devel
packages fixes the issue.
Signed-off-by: Chandan Kumar (raukadah<EMAIL_ADDRESS>

/ok-to-test

LGTM but would like someone more familiar with shell to double-check

/approve

@mheon @haircommander @sshnaidm Thank you for the review, For RHEL based system, we need to install system-devel, which is fixed in current patch.

/lgtm


Radar rawdata structure

Thanks for the mini dataset you released.
I have a question.
1) Looking at the radar raw data, it has 8 values as shown in the picture below.

What does each mean?
2) How many frames of radar raw data have you accumulated?

1）It means [x,y,z,Vr,range,power,alpha,beta], and we only used the dimensions of [0,1,2,3,5].
2) The 4D radar frames are accumulated in provided SDK, the number of frames is not specified in the technical document. Maybe I'll ask technical support later.

@TJRadarLab
Does the dataset provide annotation about the target's compensated velocity taking into account ego motion?

@TJRadarLab
Does the dataset provide annotation about the target's compensated velocity taking into account ego motion?

Hello, the dataset can provide the raw relative radial velocity as well as the radial velocity compensated after estimating the ego motion using 4D radar point cloud.

@TJRadarLab
Does the dataset provide annotation about the target's compensated velocity taking into account ego motion?数据集是否提供有关考虑自我运动的目标补偿速度的注释？

Hello, the dataset can provide the raw relative radial velocity as well as the radial velocity compensated after estimating the ego motion using 4D radar point cloud.您好，该数据集可以提供原始相对径向速度以及使用 4D 雷达点云估计自我运动后补偿的径向速度。

Hollow,请问4D 雷达点云估计自我运动后补偿的径向速度在哪里？


Sema: Don't set 'validation started' bit on ParamDecls from validateDecl()

Otherwise, when the horrible ExprCleanser comes along, it will set
the interface type of the ParamDecl to nullptr. However there is
no way to clear the 'validation started' bit, so the next time
validateDecl() is called on this ParamDecl we will just return,
causing crashes downstream when callers expect it to already have
an interface type set.
Fixes rdar://problem/38189778 and possibly some instances of
rdar://problem/36434823.

@swift-ci Please smoke test

@slavapestov did you mean to include all three commits here (two of which are in https://github.com/apple/swift/pull/16160)?

@rudkx No, but I just merged the other PR also :)

@swift-ci Please smoke test

@swift-ci Please smoke test


Add buttons to right of textbox

Hi! Thanks for creating this library, it's really useful and easy to implement. One question: how are you able to add the speech-text microphone icon on the right, as well as the second menu pictured below?

Solved by adding menu to searchView and adding
app:showAsAction="always"
as a property to the item.


Bump: package version to 0.4.4

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

Coverage data is based on head (8832878) compared to base (7199a62).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #50   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines          125       125
  Branches        34        34
=========================================
  Hits           125       125

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

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


Transfer Modal Copy upgrade

The new Transfer button which brings up the Modal still Says Withdraw funds in it
Need to change Withdraw to Transfer

fixed - closing


"View Command Output" should close the quickpick

Testing #141339

Run "Run Recent Command"
Click the "Show Command Output" button
The editor opens behind the quick pick and I have to dismiss the quickpick manually to see the editor

I guess this is because I have workbench.quickOpen.closeOnFocusLost disabled. Would be helpful if you dismiss the quickpick manually for me.

"Run Recent Command" is broken now - it reveals the terminal but does not show the quickpick


Separate disks for data and logs?

If I provision two P30 disks for SQL data, which configuration is recommended? One disk for data and TempDB files and the other disk for log files, or stripe the two disks using Storage Spaces and place all files on the same drive?

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

ID: 139dc620-240c-779f-1eed-c12accfe2ef6
Version Independent ID: a6deda7b-8361-2e2c-808a-48c047bae7a1
Content: Performance best practices for SQL Server in Azure | Microsoft Docs
Content Source: articles/virtual-machines/windows/sql/virtual-machines-windows-sql-performance.md
Service: virtual-machines-sql
GitHub Login: @rothja
Microsoft Alias: jroth

@drcrader We are looking into this question and will get back to you.

@drcrader Thanks for the question. When you provision a new VM and allow the portal to make this choice for you, it creates multiple disks and uses striping (your second option). Doing this should give you great performance, because you allow the underlying storage architecture to abstract the details. Using two separate disks would probably give you similar performance, but I don't have exact numbers. Almost everything in the performance topic is "subject to testing based on your workload". We are getting lots of questions on this part of the guidance, so I'll provide your question as feedback to the rest of the team and we'll try to make this as clear as possible. Thank you for the question. I'm going to close this issue now, but please respond if you have further questions on this answer and we can continue to discuss. Thank you!

#please-close

Rothja,
You wrote that using separate disks would probably give similar performance.
If you're using disk stripping, isn't this supposed to always give higher iops because of the pool of disks?
Can you get any more information about this regarding performance?
I have a client that I've recommended then to use a separate disk just for log files.
Today, I have discovered that they have a storage pool of 3 disks for data files.
In another article, I read that you should place data and log in the same drive while using Storage Spaces, but if you're saying the performance is similar, I don't know what to recommend then.
If you guys have any guidance it would help a lot.
Thanks.


fix(PageLayout): restore main landmark

Follow-up to: https://github.com/primer/react/pull/3675
Currently, we have teams in a couple of situations where either:

A team makes use of a main landmark and therefore runs into the duplicate landmark violation
A team uses the default main landmark from PageLayout.Content

When removing the main landmark, teams in the latter are impacted. In this PR, we introduce an as prop to allow for teams in the first example to change the semantics of this component to as="div" as they already have a main defined.
Rollout
This is an incremental rollout strategy if our ideal here is to remove main as a landmark from PageLayout.Content. With this path, we could swap teams to use as="div" before removing the main support and also dropping as="div"

With this path, we could swap teams to use as="div" before removing the main support and also dropping as="div"

(not for this PR, but for after) How do you feel about this slight change:
Right now, the default element is main. If we want to change the default to div, folks that do not have duplicate main, would then need to wrap PageLayout.Content in a <main>
How do you feel about supporting the as prop on PageLayout.Content with just 2 options: main | div.
So, changing the default from main to div would still be a breaking change, but it can be accompanied by a codemod that adds as="main" for instances that do not have as="div" already.

@siddharthkp I like it, works for me!


Support nested child action creation

A Flux-ism is to have a single global list/registry of actions.  When you have a single list, it's useful to have several levels of nesting.  I would love to have something like:
var actions = Reflux.createActions({
  foo: {
    children: [
      'subFoo1',
      {
        actionName: 'subFoo2',
        children: ['subFoo2a', 'subFoo2b']
      }
    ]
  },
  baz: 'baz'
});

so that I could call something like actions.foo.subFoo2.subFoo2a(...)
The action creator does recursively iterate, but the key is just the json-ification of the Object -- the subaction exists, but it's at actions.foo['[object Object]'].subFoo2a()
Probably a one-liner at: https://github.com/reflux/refluxjs/blob/v0.2.11/src/createAction.js#L44 -- just change it to var name = _.isObject(definition.children[i]) ? definition.children[i].actionName : definition.children[i];  Haven't tested extensively though

While this does generalize action creation in an interesting way, I personally think this makes the API more confusing than necessary.  I would personally push back against this feature, but I'd like to open the discussion up again.  This sounds like a good Reflux plugin or helper.


Add clothes type preset for Clothing Store preset

As of this writing, the clothing preset appears like this figure 1. I propose adding the clothes=* (wiki) key in the style iD uses for things like restaurant cuisine (see figure 2).
As of 2017-07-12 the counts for these tags are in table 1 (via tag info)
Sorry about the @2x screen grabs 🤓

Figure 1

Figure 2

category
count

women
2674

underwear
1379

children
1024

men
1011

wedding
545

yes
323

sports
299

workwear
193

babies
159

denim
156

lingerie
140

fur
116

fashion
112

hats
112

suits
107

leather
72

Table 1

Thanks!  I just added this field to Clothing Store (shop=clothes), and I also added it to the presets for shop=boutique and shop=fashion, because even the osm wiki admits that it's unclear what the difference is between all of these.


Claudie application metrics

Feature for Claudie to expose application-level metrics, that can be monitored with, for example, Prometheus. This feature should allow us to have more in-depth visibility of what Claudie is doing. Example metric ideas:

number of concurrent jobs executed by a service
number of clusters/inpuitmanifest currently managed
number of warnings/errors on which base alerts can be created

I'll add a bit more context to this task.
The high-level goal is to provide visibility into the internals of Claudie. So if an enterprise customer adopts this solution, they would like to have a confidence that it operates well and once it breaks, they get alerted appropriately. The observability should be work on from these angles, IMHO:

functional monitoring (metrics on clusters being operated, nodes being operated, the diffs - clusters/nodes added/removed, error rates, infra modification latencies,...); things to give us useful functional insights into what Claudie is doing
technical monitoring (metrics on API calls, rates, service latencies, transaction error rates); aspects to give us insights into how Claudie is doing technically
alerting on the key selected metrics from above
out-of-the-box dashboard on the above

Exit Criteria:

[ ] metrics for technical monitoring is proposed and implemented
[ ] functional monitoring proposed and implemented
[ ] alert rules proposed
[ ] dashboard created


Implement assign command

Codecov Report

Merging #87 into master will increase coverage by 4.18%.
The diff coverage is 92.85%.

@@             Coverage Diff              @@
##             master      #87      +/-   ##
============================================
+ Coverage     64.87%   69.06%   +4.18%
- Complexity      486      522      +36
============================================
  Files            87       89       +2
  Lines          1640     1671      +31
  Branches        182      187       +5
============================================
+ Hits           1064     1154      +90
+ Misses          521      460      -61
- Partials         55       57       +2

Impacted Files
Coverage Δ
Complexity Δ

...main/java/seedu/address/commons/core/Messages.java
0.00% <ø> (ø)
0.00 <0.00> (ø)

...u/address/logic/commands/catalogue/AddCommand.java
100.00% <ø> (ø)
8.00 <0.00> (?)

...address/logic/commands/catalogue/ClearCommand.java
100.00% <ø> (ø)
2.00 <0.00> (?)

...ddress/logic/commands/catalogue/DeleteCommand.java
100.00% <ø> (ø)
7.00 <0.00> (?)

.../address/logic/commands/catalogue/EditCommand.java
97.33% <ø> (ø)
12.00 <0.00> (?)

.../address/logic/commands/catalogue/FindCommand.java
100.00% <ø> (ø)
6.00 <0.00> (?)

.../address/logic/commands/catalogue/ListCommand.java
100.00% <ø> (ø)
2.00 <0.00> (?)

...address/logic/commands/catalogue/StartCommand.java
100.00% <ø> (ø)
7.00 <0.00> (?)

...edu/address/logic/commands/global/ExitCommand.java
100.00% <ø> (ø)
2.00 <0.00> (?)

...edu/address/logic/commands/global/HelpCommand.java
100.00% <ø> (ø)
2.00 <0.00> (?)

... and 20 more

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 be478f7...647c1d9. Read the comment docs.


Default API token authentication mechanism

API authentication will be via Authorization: Bearer XXX request headers.
I'm inclined to add a default token mechanism to Datasette based on tokens that are signed with the DATASETTE_SECRET. Maybe the root user can access /-/create-token which provides a UI for generating a time-limited signed token? Could also have a datasette create-token command for creating such tokens at the command-line.
Plugins can then define alternative ways of creating tokens, such as the existing https://datasette.io/plugins/datasette-auth-tokens plugin.
Originally posted by @simonw in https://github.com/simonw/datasette/issues/1850#issuecomment-1289706439

Maybe these tokens can be restricted to specific databases and tables when they are first created?
Since they're signed tokens, I could bundle a bunch of extra stuff in them - this token is allowed to do these permissions against these tables/rows for example.
General wisdom seems to be that 8KB is a sensible maximum length for this kind of token, which is easily long enough to fit in a bunch of database / table / permissions.

Token design concept:
{
    "t": {
        "a": ["ir", "ur", "dr"],
        "d": {
            "fixtures": ["ir", "ur", "dr"]
        },
        "t": {
            "fixtures": {
                "searchable": ["ir"]
            }
        }
    }
}

That JSON would be minified and signed.
The "t" key shows this is a token that as a default API key.
"a" means "all" - these are permissions that have been granted on all tables and databases.
"d" means "databases" - this is a way to set permissions for all tables in a specific database.
"t" means "tables" - this lets you set permissions at a finely grained table level.
Then the permissions themselves are two character codes which are shortened versions - so:

ir = insert-row
ur = update-row
dr = delete-row

Here's what that example looks like signed:
from datasette.app import Datasette
ds = Datasette()
ds.sign('{"t":{"a":["ir","ur","dr"],"d":{"fixtures":["ir","ur","dr"]},"t":{"fixtures":{"searchable":["ir"]}}}}')

.eJxTqo5RKolRsgJSiUAqOkYpsyhGSSdGqRRCpQCpWBANUZOWWVFSWpRajFNprQ7cPCS1QF5xamJRckZiUk4qQm9sLRAoAQCC8yph.O0Gaej6-VOLbbtPq7xU6T77jEO0

That's 129 characters.
Note that Datasette doesn't have its own mechanism for signing things for a specific duration yet: https://docs.datasette.io/en/stable/internals.html#sign-value-namespace-default
So I'll need to add a "e":<PHONE_NUMBER> field with the UTC timestamp at which the token should expire.

If you start Datasette without providing a DATASETTE_SECRET environment variable of --secret option it creates a random signing secret that only lasts for the lifetime of the server.
This means any signed API tokens you create will stop working if the server restarts.
I think the /-/create-token UI should know when this happens and show a warning message about it, to avoid confusion.

... also, maybe there should be a UI (perhaps on that page) for resetting the Datasette secret? Useful for emergency invalidation of all tokens.
No, I'm not going to build that unless someone asks for it. Restarting the server with a fresh secret should be easy enough.

Might be neat for API tokens to be signed with an additional secret than can be rotated independently of DATASETTE_SECRET itself, in order to invalidate all tokens without needing to invalidate logged in users too.
But again, I don't want to implement something like that until I see an actual need for it.

I'm going to implement the first version of this token mechanism using permissions that exist already. Right now that's:
https://docs.datasette.io/en/0.62/authentication.html#built-in-permissions
Here are the shortcuts I'll use for them:

view-instance - vi
view-database - vd
view-database-download - vdd
view-table - vt
view-query - vq
execute-sql - es

Datasette currently defaults to having everything public-readable by default, unless a permission plugin changes that default.
In thinking more about this API mechanism, I realized that it might be good to have a mode where Datasette doesn't default to public everything. Maybe datasette --private to start it like that?
Might even be an opportunity to get rid of the current slightly confusing mechanism where permission checks can announce that they should default to true:
https://github.com/simonw/datasette/blob/c7dd76c26257ded5bcdfd0570e12412531b8b88f/datasette/views/database.py#L152-L154

Interesting challenge: what permissions should users be allowed to grant to tokens?
Clearly a user should not be able to create a token with a permission that the user themselves does not have.
And should there be a permission that allows people to create tokens? I think so.

... so maybe there's a way to create a token that inherits the exact permissions of the actor that created the token? That could even be a default mode for tokens, with an option to then further restrict permissions if desired.

In which case the token would need to duplicate the current actor and then add extra constraints. So maybe the token design looks like this:
{
  "actor": { "copy_of": "actor_creating_token"},
  "perms": { "t": "... the thing designed earlier" },
  "expires": "integer timestamp when token expires"
}

I'm going to build an initial /-/create-token interface which just bakes a token with the current actor in it and an optional expiry timestamp. I'll try the limited permissions thing later.

A /-/debug-token page that can take a token and decode it to show you how long until it expires, what actor it represents and the permissions it has will be useful as well.

Demo:

If you click "Create token" for "Token never expires" multiple times you currently get exactly the same token each time, since it's just a signed token containing a copy of your actor dictionary.
I'm not sure if I like that. I could give each token a random ID (maybe using secrets.token_hex()) such that different tokens have different identities, which would be useful for logging and auditing and maybe even revocation at some point in the future.

Demo is now live at https://latest-1-0-dev.datasette.io/-/create-token - visit https://latest-1-0-dev.datasette.io/login-as-root first to sign in.

If I'm going to have a setting to disable this feature I need to decide what it will be called.

Other options:

--setting default_api_tokens off
--setting signed_api_tokens off

These feel inconsistent because they don't use the allow_ prefix - but they're also a bit less ugly to look at.

If I'm going to change the naming conventions for settings I should do it before Datasette 1.0.

Next step: make these tokens actually do something.

Another thought about tokens that can act on behalf of the user.
Imagine a user has permission to access a table. They create a token that can create that table... but then their permission is revoked. It would be bad if they could still use that token they created earlier to access that table!
On that basis, I think the model described above where tokens mainly work to provide an "act on behalf of this actor" - but with optional additional constraints - is a good one.

Tests failed because I added a view without also adding documentation!

On that basis, I think the model described above where tokens mainly work to provide an "act on behalf of this actor" - but with optional additional constraints - is a good one.

This is what we do for Sandstorm essentially and I fully agree it's the right way to do API tokens in multiuser systems.
Constraints will definitely be important though. I know I want a token to submit error reports programmatically, but I wouldn't want that token to convey my right to delete tables and records, Little Bobby Tables is out there somewhere, and he's all grown up now.

Rather than duplicating the entire actor into the "a" field, maybe just copy the actor ID?
Would need to restrict token creation to just actors with an ID set.

The tokens also need something that can be used to differentiate them from alternative token mechanisms that other plugins might provide.
Maybe a prefix before the signed value.
Prefixes are also useful for scanning to check they were not accidentally committed to source control.

Prefix: dstok_ - for Datasette signed token.

Implemented that dstok_ prefix and the thing where only the actor["id"] is copied to the "a" field.

Built a prototype of the actor_from_request() hook for this and now:
% curl http://<IP_ADDRESS>:8001/-/actor.json -H 'Authorization: Bearer dstok_eyJhIjoicm9vdCIsImUiOm51bGx9.6O1OxgNTFkAU6uw7xNcmXYX949A'
{"actor": {"id": "root", "dstok": true}}

I'm going to split the remaining work into separate issues:

[ ] Implement setting for disabling API signed token mechanism
[ ] Ability to create API signed tokens with a reduced set of permissions

Documentation: https://docs.datasette.io/en/1.0-dev/authentication.html#api-tokens


training error

Noise training throws an error. Seems to be line 113 in lib/pairwise_transform.lua:
113. x:samplingFactors({1.0, 1.0, 1.0})
Currently found no use for this line - commenting it out allowed for a successful train.

Please update the graphicsmagick package.
sudo luarocks install graphicsmagick


[Monitor] harden async try/catch

This PR looks great but can we wait until after #12417 goes in so we don't accidentally lose the changes?

Some CI failues:
FAILURE (1)
================================
@microsoft/opentelemetry-exporter-azure-monitor (13.93 seconds)
An invalid connection string was passed in. There may be telemetry loss instrumentationkey=foo-ikey
[@microsoft/opentelemetry-exporter-azure-monitor] Returned error code: 1
An invalid connection string was passed in. There may be telemetry loss instrumentationkey=foo-ikey
An invalid connection string was passed in. There may be telemetry loss instrumentationkey=foo-ikey
An invalid connection string was passed in. There may be telemetry loss instrumentationkey=foo-ikey
An invalid connection string was passed in. There may be telemetry loss instrumentationkey=foo-ikey
An invalid connection string was passed in. There may be telemetry loss instrumentationkey=foo-ikey
{ [Error: ENOENT: no such file or directory, scandir 'C:\Users\VSSADM~1\AppData\Local\Temp\ot-azure-exporter-abc']
  errno: -4058,
  code: 'ENOENT',
  syscall: 'scandir',
  path:
   'C:\\Users\\VSSADM~1\\AppData\\Local\\Temp\\ot-azure-exporter-abc' }
{ [Error: ENOENT: no such file or directory, scandir 'C:\Users\VSSADM~1\AppData\Local\Temp\ot-azure-exporter-abc']
  errno: -4058,
  code: 'ENOENT',
  syscall: 'scandir',
  path:
   'C:\\Users\\VSSADM~1\\AppData\\Local\\Temp\\ot-azure-exporter-abc' }
================================

@xirzec: Could we get these fixes tagged in a release on NPM? Thanks!


SNAPSHOT build

I had an issue from the build.
It looks like this.
Error:Failed to resolve: com.android.support:support-v4:22.2.1
Install Repository and sync projectOpen FileShow in Project Structure dialog
i think i am using
compile 'com.android.support:support-annotations:22.2.0'
compile 'com.android.support:support-v13:22.2.0'
compile 'com.android.support:appcompat-v7:22.2.0'

for all my modules.
what do i need to change in order to match to your configuration?

I think you just need to update the Android Support Repository and Android Support Library in your SDK Manager

)

i have notice that. Do I need to change all other library uses com.android.support:* as dependencies to 22.2.1 ?

Sorry for the late reply. No, I don't think you should have to change your other dependency versions, however you probably should to get the bug fixes and patches in those update versions.


Improve compatibility, switch to typescript, etc

use ctx.respond to skip koa2 finalize render
use response#close/finish event to detect middleware finished
use typescript to compile compatible code with node 4
examples and tests bugfix: koa2 middleware should return next() while without async keyword

@cyrilluce you've changed package name and package author. I think it's a good indicator that this shouldn't be merged

Right, forgot to mention that, thanks @vkurchatkin. Please change the repository url, package name, author, and version number back to what they were before @cyrilluce.

@lourd
Thank you for encourage me to create pull request. at beginning I just want build next version, and change code very easy, so there are some big change(like typescript).

Yes, use typescript is to simplify the source code, and generate node v4 compatible build. Write compatible code is painful. I'm sorry for the lazy job. lol
You can remove markHandled and hasHandled
Maybe we can spend some time rewrite to compatible with node v4 without typescript.

@vkurchatkin I'm sorry for forgotten to restore package.json

You're welcome! Thanks for making it 😄
If you push new commits to the master branch on your fork GitHub will automatically update the pull request.
Totally understand wanting to use the newer JS features. Can't wait till async-await, spread, rest, all that good stuff is in Node LTS.
It's only a couple small changes to be v4 compatible:

Change the body of koaConnect to not use async-await:

return (ctx, next) => {
  ctx.respond = false;
  return handler(ctx, connectMiddleware)
    .then(goNext => {
      if (goNext) {
        ctx.respond = true;
        return next();
      }
    })
    .catch(err => {
      ctx.respond = true
      throw err
    })
}

Change connectMiddleware(...args) to connectMiddleware.apply(null, args)

Change
dummyRes[name] = (...args) => {
  res[name](...args)
}

to
dummyRes[name] = function() {
  res[name].apply(null, arguments)
}

@lourd updated.
But I got another issue, and don't know how to deal with.
In webpack-dev-middleware, there have codes:

// Express automatically sets the statusCode to 200, but not all servers do (Koa).
res.statusCode = res.statusCode || 200;

And my 404 issue improve will cause failure, or we should force initial set it to 200? or even set it to undefined? (actually we don't compatible with Express, but just connect)

Closing this PR since it's gone a year without activity. Feel free to re-open if you're still interested


Set remote authority on frontend

This should resolve at least some of the port issues, if not all of them.
See the commit message for details.

They probably do serve it behind a reverse proxy but they will never need the port because they will always host on 443 and they will never need the path because they always serve at the root, so for them it is safe to just use the host header as-is.

They probably do serve it behind a reverse proxy but they will never need the port because the source is always 443 and they will never need the path because they always serve at the root, so for them it is safe to just use the host header as-is.

Ah! They're in control of these values so they don't need it to be as flexible as we do. Makes sense!


Failed to load Typescript Package - Cannot read property 'React' of undefined

Install version 5.2
Start Atom
Error message shown on startup

I have removed and reinstalled - no change
Atom Version: 1.0.2
System: Mac OS X 10.10.4
Thrown From: atom-typescript package, v5.2.0
Stack Trace
Failed to load the atom-typescript package
At Cannot read property 'React' of undefined

TypeError: Cannot read property 'React' of undefined
    at Object.<anonymous> (/Users/xxx/.atom/packages/atom-typescript/dist/main/tsconfig/tsconfig.js:75:20)
    at Module._compile (module.js:452:26)
    at Object.loadFile [as .js] (/Applications/Atom.app/Contents/Resources/app.asar/src/babel.js:162:21)
    at Module.load (module.js:347:32)
    at Function.Module._load (module.js:302:12)
    at Module.require (module.js:357:17)
    at require (module.js:376:17)
    at Object.<anonymous> (/Users/xxxx/.atom/packages/atom-typescript/dist/main/lang/projectService.js:9:16)
    at Module._compile (module.js:452:26)
    at Object.loadFile [as .js] (/Applications/Atom.app/Contents/Resources/app.asar/src/babel.js:162:21)

Commands

Config
{
  "core": {
    "themes": [
      "unity-ui",
      "solarized-light-syntax"
    ]
  },
  "atom-typescript": {
    "typescriptServices": "/Users/xxx/source/xxx/node_modules/typescript/bin/typescriptServices.js"
  }
}

Installed Packages
# User
.bin, vundefined
atom-typescript, v5.2.0
docblockr, v0.7.3
language-html-swig, v2.0.1
last-cursor-position, v0.9.0
less-autocompile, v1.0.0
linter, v1.2.4
pain-split, v1.4.0
project-manager, v1.15.11
unity-ui, v2.0.11

# Dev
No dev packages

Ignore this. It appears to be because I am using Typescript 1.5 beta. If I remove the reference to /Users/xxx/source/xxx/node_modules/typescript/bin/typescriptServices.js in atom-typescript configuration the problem disappears.
I'll leave this issue just in case anyone else encounters the same.

I'll leave this issue just in case anyone else encounters the same.

I'll close it as its a user configuration error, and will still be searchable by words of the error :rose:

This isn't a user configuration error, it's an issue with Atom and Typescript 1.5 beta. The configuration was working fine until I upgraded the version of Atom Typescript. Not sure when 1.5 is to going to be released but it's worth checking before it is.

I am not sure which version of typescript is shipped with atom-typescript.
In latest typescript 2.0.0 , there is some feature that i am trying to use. one of those feature is to give typeRoots and types in tsconfig
atom-typescript-version: 10.1.6
I am providing below configuration in tsconfig.json
"compilerOptions": {
"typeRoots": ["../node_modules/@types"],
"types": ["core-js", "jasmine", "node" ]
}
I am trying to use new feature of ts2.0.0 .
but when i build through atom-typescript, it throw a lot of error. like
can't find module 'promise' 'set' etc....and i m sure its due to atom-typescript is not recognizing those new option in tsconfig.json.
I also tried providing alternate tsc complier throug project setting like below, but did not work.
"atom-typescript":
typescriptServices: "/home/user/workspace/demo/node_modules/typescript/lib/typescriptServices.js"
But when i trying to compile from command line, then no error.
typescript installed through node is 2.0.0 but i m not sure of typescript shipped with atom-typescript
please help on this


Lock rainbow to ~> 2.1.0 in root Gemfile

ChefDK Verification fails due to rainbow 2.2.1 in the root Gemfile. This extends the constraint on rainbow to the root Gemfile as well.
Check List

[ ] New functionality includes tests
[ ] All tests pass
[ ] RELEASE_NOTES.md has been updated if required (not required for bugfixes, required for API changes)
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

it would probably be better to get onto rubygems 2.6.10 if we can
if the chef release you targetting doesn't have that, though, then we could do this, but we need to dig out from under this problem

@lamont-granquist Good idea. Hold caller.

This PR should be able to reverted when chef/omnibus-toolchain#45 is deployed to our builders.

can you get by with only pinning in acceptance/Gemfile?

No, that is what we were doing originally. This line installs via the root Gemfile, and that is where the failure is occurring.

Ugh, this is still failing ad-hoc builds.

yeah, i see why you have to pin multiple places, so 👍  whenever you greenify it

Updated the PR title/description based on new data.


localMedia option causes all Cosmicjs sources other than allCosmicjsLocalMedia to disappear from GraphQL

The attached screenshots show what happens when enabling localMedia vs leaving disabled. This issue can also be seen on the Gatsby Blog CosmicJS starter here: https://codesandbox.io/s/github/cosmicjs/gatsby-blog-cosmicjs

@justinradomski I looked at it. But it couldn't able to reproduce. Can you please let me know which version of Node & Gatsby are you using?

@jazibsawar
Gatsby: 2.23.3
Node: 12.14.0
Were you able to see the issue in the sandbox link for that cosmic blog starter?

Hey @justinradomski I installed your exact versions and tried and couldn't reproduce the issue as well. Can you tell me more information on what is going in our Slack channel? Please DM me and we'll get this sorted out. I'm thinking there may be an issue with your Bucket config or something. I'm closing this for now.

I'm reopening, because we have found the issue and are working on a fix. The next version includes a temporary fix.

Hey @justinradomski the issue has been fixed and the latest version has been published on NPM. Be sure to check out the latest version. Thanks


Add Windows support

Evidence Support for Windows
Closes #2
Closes #15
Closes #121
Changes:

Update Svelte, SvelteKit, and Typescript dependency versions
New SvelteKit version comes with an upgrade to Vite (version 2.7) which solves our SSR issues (#121), the major blocker for supporting Windows
Update styling to support browsers on Windows, including:

Custom scrollbars in the QueryViewer and QueryDataTable components
Updated sans-serif font stack

Change value component error state styling

Fantastic.


Chain4energy image update to 256x256

Chain4energy image update to 256x256

Looks ok to me. Please resolve conflicts

Conflict resolved.


[CLI] Support unnamed recursive inlining

The outputting is currently pretty restrictive as it seems to require explicit file naming. Would be fantastic if this package could support inlining files recursively and map them to an output directory. For example:
Given...
src/a/1.html
src/a/2.html
src/b/1.html
and command...
juice -r src dist
Juice look in the src directory for all html files, inline the CSS source and output it to the dist folder, nested respectfully. For example:
dist/a/1.html (css inlined)
dist/a/2.html (css inlined)
dist/b/1.html (css inlined)

Would also like this!
@yo-gi has a simple workaround in #374 🙌


Archive DD logs into S3

Problem
DD logs are deleted after 3 days
Impact
Affects reliability. Historical logs help understand the problem better
Proposed Solution
Enable archiving to S3 on DD for all production logs, including watcher.
Acceptance Criteria

[ ] Archive to S3 is enabled
[ ] Get rough estimate on additional cost
[ ] Historical logs > 3 days are accessible to the team

Maybe dupe of #1422


Revert "[pre-commit.ci] pre-commit autoupdate"

Reverts UCL-ARC/python-tooling#479
We don't want the alpha version

Another issue is this isn't going to update the template's ones. We don't want this on at all.

@renovatebot will do it in 3 days...

🤷
I'm ok with alphas. But if we decide never to take pre-commit autoupdates and only use @renovate: can we actually disable it in the ci: config, please? It's not immediately clear to me but I guess it's possible.

I've re-opened https://github.com/UCL-ARC/python-tooling/issues/463 to discuss, so we can make sure discussion is in one place for future reference

@paddyroddy could you post the issue you've found on this thread? I think they're spread around several PRs/issues at the moment, and I'm struggling to find them all 😄


update the menu design

Relevent discussion here.
The current three column layout is a lot of squishyness, it's worth looking at a simpler layout where we drop the right-hand-side summary menu (part of the Docsy default) and give the menu and contents more breathing room.

Good notion. Also, and this is a small point, when I click into a menu item, it seems like the left sidebar goes back up to the top or some such? I lose my place of where I was. Maybe that will be addressed or maybe it's out of scope, but figured I should mention. Thanks.

@bridgetkromhout that irks me too. Docsy auto renders the menu to focus on the current tree/section as you move around, I don't really like that UX as that behavior is more like a breadcrumb than what should be a static menu.
I will experiment with reconfiguring this (their docs show a way to freeze the menu via a ul_show param).

I will experiment with reconfiguring this (their docs show a way to freeze the menu via a ul_show param).

Awesome. I think that would be the one remaining menu design change to handle for this issue.

I forgot to detail that I included this change in #46 already, so it's in place. The menu tree will no longer change from subsection to subsection.


Connection Close After Around 2 minute Inactivity

Can anyone help me
Whatsapp backend closed connection itself after around 2 minute not doing anything

Confirmed.


Update _index.md

- Summary

- Test plan

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

👷 Deploy Preview for material20231 processing.

Name
Link

🔨 Latest commit
f0698292d5085e796e4a3667d14eb7e8de0ac8b8

🔍 Latest deploy log
https://app.netlify.com/sites/material20231/deploys/640e45ec3e8b1000087196a0


Improve error messages in BVH constructor and BVH::query()

As promised here https://github.com/arborx/ArborX/pull/111#issue-321706817
restoring the concept checks.

Ready for review/merge

I didn't want to but I need to add unit tests to demonstrate these actually work...

Added (partial) testing to demonstrate type support added works as intended.


3.0.1 version build errors

Hi,
I've tried to upgrade from 2.9.0 to 3.0.1 because when I use (lazyLoading: true) I get no data back.
After running yarn install and running the app I get this error while building:
ERROR in node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/clickOutside.ts(31,25): error TS6138: Property '_elementRef' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/clickOutside.ts(38,39): error TS6133: 'targetElement' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(1,40): error TS6133: 'NgModule' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(1,63): error TS6133: 'AfterContentInit' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(1,112): error TS6133: 'OnChanges' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(1,141): error TS6133: 'ViewEncapsulation' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(1,167): error TS6133: 'Output' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(1,175): error TS6133: 'EventEmitter' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(1,189): error TS6133: 'ElementRef' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(1,201): error TS6133: 'AfterViewInit' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(1,216): error TS6133: 'Pipe' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(1,222): error TS6133: 'PipeTransform' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(1,237): error TS6133: 'Directive' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(2,1): error TS6192: All imports in import declaration are unused.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/menu-item.ts(3,1): error TS6133: 'CommonModule' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/multiselect.component.ts(1,210): error TS6133: 'AfterViewInit' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/multiselect.component.ts(1,225): error TS6133: 'Pipe' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/multiselect.component.ts(1,231): error TS6133: 'PipeTransform' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/multiselect.component.ts(180,5): error TS7030: Not all code paths return a value.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/multiselect.component.ts(180,28): error TS6133: 'index' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/multiselect.component.ts(180,43): error TS6133: 'evt' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/multiselect.component.ts(212,21): error TS6133: 'c' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/multiselect.component.ts(261,15): error TS6133: 'index' is declared but its value is never read.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/multiselect.component.ts(293,5): error TS7030: Not all code paths return a value.
node_modules/angular2-multiselect-dropdown/src/app/angular2-multiselect-dropdown/multiselect.component.ts(441,9): error TS6199: All variables are unused.
If I can somehow show data (I have around 30k entries...) I would go back to 2.9.0 version.
Thank you in advance for any input.

Noted. There is a package error. Please wait for v3.1.0

Fixed. Please use v3.1.0


Adding latest version should not create a new version

I have uploaded 2 versions:
2.0 and 2.1
Then I used this command to mark 2.1 as latest:
curl -X PUT http://docs.roche.com/api/LabCore File Handling/2.1/tags/latest
This created a 3rd entry called "latest", which is fine, but in fact "latest" is a duplicated of "2.1".
2.1 version should just be marked as "latest"

Yes this is the intention of this feature. The idea of this is to generate a constant link. Meaning you can point your customers to something like the stable/latest/whatever version and update the content underneath the link.


After sending USD token, the "Account Activities" page is empty.

After sending USD token, the "Account Activities" page is empty. It should display the transactions i made.

resolved


Re: OnlyM issue #192

Just to say JwlMediaWin nicely fixes issue #192 raised on OnlyM.
Great work Antony
Thanks
Colin

@ColinAAvey Thanks for reporting back!


[FW-145][FW-149] Serialize packets

Create a Class to serialize the values received checking if the packet_id exists and the values are the same as the declaration of all the packets in the constructor.

Add a function to validate the input to serialize_packets and pay attention to the way the enums are represented, if you have any questions regarding the enums just tell me

Yes, I have because, as I knew an enum was an uint8_t, I don't know if the JSON_ADE let you use other type of enum.


As a [end user], I want tooltip icons to know there's a tooltip

Problem
It's unclear to the user what happens when, for example, the swap rate exceeds the slippage tolerance.
Proposed Solution
Hint/tooltip next to the tolerance setting should show something like "The transfer won’t go through if the bridge rate moves unfavorably by more than this percentage when the transfer is executed." (words from the user that suggested this). Things become weird when talking about a cross chain swap not going through. I believe @alexwhte had some similar suggestions listed about other settings.
Acceptance Criteria
From a user perspective, understand where my funds will end up and in what form (next assets, canonical assets).

@Tommy-R8 We have a tooltip, do we need tooltip icon? I am updating the text to be a little more like this though
Alex

Thinking about how many people will use mobile, an icon would probably be a good idea.

Good point

Added the tooltip icon to the mobile view.


Update Test-Network.ps1

More like a proposition to use system itself to tell us if it is connected to Internet. its quite fast!
Proposed Changes

replacing looped pinging with method available from Windows Vista/Windows Server 2008. System could tell if it has access to Internet or not.

Related Issues

none, I'm just blocking www.msftncsi.com and www.msftconnecttest.com in my network. Current method signals offline state and then WAU simply stops. With this method it will continue.

hm.. linter failed on file encoding..

original file was ANSI encoded and I took some parts from it (notifications).. I will recreate this function in separate Commit/PR.


Smart pointers and const correctness

Refactor code to use smart pointers and to be const-correct. I've already ran into a lot of issues using raw pointers. Const-correct code is less error prone and looks cleaner.

What was your issue with raw pointers? I agree that we should have const everywhere where it fits. For example every getter and functions which just print stuff to console or file should be obviously const.


[Servicebus] Eslint member ordering

As suggested opened a new PR for the member ordering rule
Referencing PR https://github.com/Azure/azure-sdk-for-js/pull/3005
@Azure/azure-sdk-eng @bterlson @ramya-rao-a

I'm assuming this is one that can be fixed automatically with the --fix flag? Seems like it should be.

Is the plan to merge this first, and then rebase #3005 so that the ordering changes are not included in that PR?


[W-10059979] Automate Release Gating Testing T-6883093

Critical Changes
Changes

Automated test scenario for release gating functionality in education settings.

Issues Closed

W-10059979

Testing Notes
T-6883093

It seems there were existing jest tests that already seemed to cover most of the test scenario. I added one more method to cover the clicking of the button/navigation.


Subcellular localization -- "no location" should be referred to as NaN

@brycehwang did you get a chance to look into this?

I believe this was done a while ago


Add Feedback/Rate Us section done ! #290

Hello, PR
Add Feedback/Rate Us section with star rating widget - #290
Done properly -
https://github.com/user-attachments/assets/24624dff-f436-4b54-8222-3cc82d6dca9b

✅ Checklist
Before submitting the PR, please make sure you have completed the following:

[x] I have followed all the guidlines mentioned in CONTRIBUTING.md.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation (if applicable).
[x] I have tested it locally and it works fine.
[x] Any dependent changes have been merged and published in downstream modules.

🏷 Types of Changes
What type of changes does your code introduce? (Check all that apply)

[ ] Bug fix (non-breaking change which fixes an issue) 🐛
[x] New feature (non-breaking change which adds functionality) ✨
[ ] UI enhancement (non-breaking change which enhances UI) 🎨
[ ] Documentation update 📚

@Harshdev098 sir done, please merge my PR with level 3, I also add a star rating widget with feedback form..
Thank You

@Harshdev098 sir

@Harshdev098 sir

I think you can make it more responsive

What ? I didn't understand ...
@Harshdev098 sir i added everything what i can do, Feedback form, toast message & also star rating widget...

If you check other projects, they give level 2/3 for feedback form and level 2 for star rating and another level 2 for toast message but I added everything in this PR because tomorrow was the last day, so...
@Harshdev098 sir please merge my PR 🙏🏻

@Harshdev098 sir done #375


Update the version in the response header

Linux Build 6760 is now running using a merge of 7d149c4e795b8c28c6649e4cd0db2aa228c4d7d9

Linux with security manager Build 1660 is now running using a merge of 7d149c4e795b8c28c6649e4cd0db2aa228c4d7d9

Windows Build 1834 is now running using a merge of 7d149c4e795b8c28c6649e4cd0db2aa228c4d7d9

Linux with security manager Build 1660 outcome was SUCCESS using a merge of 7d149c4e795b8c28c6649e4cd0db2aa228c4d7d9
Summary: Tests passed: 856, ignored: 322 Build time: 0:06:31

Windows Build 1834 outcome was SUCCESS using a merge of 7d149c4e795b8c28c6649e4cd0db2aa228c4d7d9
Summary: Tests passed: 2880, ignored: 395 Build time: 1:42:40

Linux Build 6760 outcome was FAILURE using a merge of 7d149c4e795b8c28c6649e4cd0db2aa228c4d7d9
Summary: Tests failed: 1, passed: 2878, ignored: 395, muted: 1 Build time: 1:42:38
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase(SYNC-tcp).testNoAuthSingleSignOn: <no details avaliable>


Stuck when a block in the log filter can no longer be found

As can be seen in these logs, it can happen that we request eth_getLogs for a block hash which the Ethereum node no longer considers valid, and we then retry indefinitely. It's not clear if this issue persists across restarts. We should handle that error in a more robust way.

Confirmed that the issue persists across restarts - I actually produced that log by rebooting the node so we'd handle it expediently.
I've got a nicely automated deploy pipeline in place for that node, let me know if there's anything you'd like me to try!

@iameli could you try syncing the same subgraph again, but with some whitespace change so that it generates a different hash, and see if the error still happens?

Sure.

Syncing now, will check back in in ~2 hours

Precisely the same result, got to block https://etherscan.io/block/8272429 and stopped. Logs: https://gist.github.com/iameli/b0f34f5f377168a7f6304db909944720

@iameli Thanks, this is worse than I thought then. Could you link to the commit from which the subgraph was built, so that we can try to reproduce?

It's off of the tip of livepeerjs master: https://github.com/livepeer/livepeerjs/tree/master/packages/subgraph
Here's the exact IPFS file that's being used: https://graph.livepeer.org/ipfs/QmY7EY26HdgTPw6pMXZqkRDuksYm78PoTJ3fe3TZPC11RV

Update: it does get unstuck eventually after many hours of being on a particular block — we've made it as far as https://etherscan.io/block/8301996

Update again: we're all the way to https://etherscan.io/block/8324330!
Happy to arrange access to the Parity node this thing is syncing to if that would be helpful for y'all.

This hasn't been reproduced in a long time so I'm closing.


Lightmap baking stops working when changing between Shadow Type

Sample Project: https://playcanvas.com/project/433362/overview/shadowmap-baking-bug
To reproduce:

Select light from scene
Change ShadowType from Variance Shadow Map (32bit) to Variance Shadow Map (8bit)
Rebake the scene (Ctrl + B)
Change ShadowType from Variance Shadow Map (8bit) to Variance Shadow Map (32bit)
Rebake the scene (Ctrl + B)
Shadow maps fail to generate and the following error appears on console:
[.Offscreen-For-WebGL-0x7fdcb1bd3000]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.

Video of bug can be found here: https://drive.google.com/file/d/0B-I0B3mugV-GMXlheURLTTFFMTA/view?usp=sharing

I tested this and it works without problem - must have been fixed already. Closing.


Add UI MockUp

This is the first low-fidelity wireframe for Version 2.0 of AddressBook Pro

Coverage remained the same at 90.858% when pulling 6af0689b17e5b6da82d2c09bea20c672ce8760e9 on zenghou:UIMockUp into ff131fd87cc2f7c9aed7ad919d13053d051e5a84 on CS2103AUG2017-F11-B4:master.


throttling

How do i specify throttling settings?

Posted too soon. Found this:
https://sites.google.com/a/webpagetest.org/docs/advanced-features/webpagetest-restful-apis

Specifying connectivity
If the connectivity is not specified, by default you will get the Cable (5/1 Mbps, 28ms RTT) profile. The connectivity is specified as part of the location in the format:
location:browser.connectivity
For example:
Dulles_IE7.DSL
Frankfurt.Dial
China.custom
Dulles:Chrome.DSL
The supported profiles for the public instance are:
DSL - 1.5 Mbps down, 384 Kbps up, 50 ms first-hop RTT, 0% packet loss
Cable - 5 Mbps down, 1 Mbps up, 28ms first-hop RTT, 0% packet loss
FIOS - 20 Mbps down, 5 Mbps up, 4 ms first-hop RTT, 0% packet loss (not all locations will get the full bandwidth)
Dial - 49 Kbps down, 30 Kbps up, 120 ms first-hop RTT, 0% packet loss
3G - 1.6 Mbps down, 768 Kbps up, 300 ms first-hop RTT, 0% packet loss
3GFast - 1.6 Mbps down, 768 Kbps up, 150 ms first-hop RTT, 0% packet loss
Native - No synthetic traffic shaping applied
custom - Custom profile, bandwidth and latency must also be specified using the bwIn, bwOut, latency and plr parameters

When I put for example ec2-eu-west-1:Chrome.3G in the Location field, it still gives the default Cable speed. What am I doing wrong

I've just tried the following in the location field and they both work OK
ec2-eu-west-1:Chrome.3G - http://www.webpagetest.org/result/160704_RZ_Y1E/
ec2-eu-west-1:Chrome.2G - http://www.webpagetest.org/result/160704_6N_Y1G/
Do any of the other default values work (list below)?
.Cable
.DSL
.Dial
.3G
.3GFast
.3GSlow
.Edge
.2G
.Native
.custom

thanks andy. Seems to be ok now
On Mon, Jul 4, 2016 at 8:09 PM, Andy Davies<EMAIL_ADDRESS>wrote:

I've just tried the following in the location field and they both work OK
ec2-eu-west-1:Chrome.3G - http://www.webpagetest.org/result/160704_RZ_Y1E/
ec2-eu-west-1:Chrome.2G - http://www.webpagetest.org/result/160704_6N_Y1G/
Do any of the other default values work (list below)?
.Cable
.DSL
.Dial
.3G
.3GFast
.3GSlow
.Edge
.2G
.Native
.custom
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/andydavies/WPT-Bulk-Tester/issues/15#issuecomment-230343179,
or mute the thread
https://github.com/notifications/unsubscribe/AMbZyBllw2bOpSVQV26UHK_rX8kOqsxXks5qSVprgaJpZM4JD-V3
.

--
Spencer Shaw | Chief Technical Officer
[image: Phone]:   020 7112 9321 | 07932 080811
[image: Streetlike Logo]
WeHub, 2A Redbourne Avenue, Finchley, London, N3 2BS


Analyzer allows re-use of part files from core libraries

Consider the following program:
library dart.async;
part 'dart:async/future.dart';
main() {}

This program should be rejected, since dart:async/future.dart is not the URI of any file that can be validly used by client programs.  However, as a side effect of the way analyzer resolves part declarations within the SDK, it considers dart:async/future.dart to be a valid pointer to the file lib/async/future.dart inside the Dart SDK, so it accepts this program without complaint.
Dart2js and the VM both correctly reject this file.

Just to elaborate: The URI dart:async/future.dart is bogus. It should not refer to anything, ever.
The dart scheme defines URIs that are not hierarchical. Resolving anything against a non-hierarchical URI is meaningless. The only dart URIs that have any meaning are the ones on the form dart:platform-library-name. Any other variant has no meaning, and should be rejected if anyone uses it as a URI.
If the analyzer uses such an URI-like-thing internally, it's obviously free to do so, but it must not leak in any way.

The analyzer still allows such a URI.


[disk module] Allow more than one drive?

There doesn't seem to be any options to add more than one disk to track on the status bar.

You can add multiple instance of a same module with different settings
c.f. https://github.com/Alexays/Waybar/wiki/Configuration#multiple-instances-of-a-module


Fix Psalm v4.21 compatibility

totallyTyped was deprecated in Psalm v4.21.0.
Drom the docs: totallyTyped="true" is equivalent to errorLevel="1" and totallyTyped="false" is equivalent to errorLevel="2" plus reportMixedIssues="false".

There was also an issue with MissingFile in ApplicationProvider that popped up since Psalm 4.21 now resolves __DIR__. This issue needs to be ignored, als the file is checked for existence.

Please see ##223 for the failing CS check.

thanks for the pr!


detection log

Hi, thank you for your outstanding work.
Can you provide the log of detection?

Hi,
ViT-S/16: det, seg
ViT-B/16: det, seg

Hi,
ViT-S/16: det, seg ViT-B/16: det, seg

Thanks!


Add support for UI For predict in container

I would like some env vars or flag when building a cog container to bake in the UI, probably some gradio or streamlit or something similar to what have in replicate hosted containers.
Basically that when running the container will also have path like /ui that serves a ui that i can use to call predict on the container instead trying some Curl or stuff like that.
This feature seems super useful in my own opinion, would be happy to discuss if needed.
Thanks!

I mean a UI not like openapi swagger, i mean ui that infers the predict types and renders correct element for it for example file type render to allow file uploads.

Hi @yairyairyair. Thanks for sharing your suggestion. There are a few projects that generate a UI for Cog models, including grog. But for now, we don't have any plans to build this into Cog directly.


Add implementation and tests for prelu op

@huningxin @Honry PTAL, thanks.

According to the comment for prelu's implementation https://github.com/webmachinelearning/webnn-baseline/pull/35#discussion_r1130403732, also update prelu tests here, thanks.


Build failures

The reason (at least some of) your build CIs fail is because you're using the imgui-provided example headers, which are missing proper or any include guards at all. This causes a problem, because a forward-declaration of a function with a default argument can only appear once, even if the argument in question is the same. Without include guards in upstream headers, it would require workarounds in the client code.
Luckily, someone just submitted a fix to imgui: https://github.com/ocornut/imgui/pull/2166, so whenever it gets accepted, please update the imgui submodule.
/home/janisozaur/workspace/OpenNFS/include/imgui/examples/imgui_impl_opengl3.h:30:79: error: default argument given for parameter 1 of ‘bool ImGui_ImplOpenGL3_Init(const char*)’ [-fpermissive]
 IMGUI_IMPL_API bool     ImGui_ImplOpenGL3_Init(const char* glsl_version = NULL);
                                                                               ^
In file included from /home/janisozaur/workspace/OpenNFS/src/RaceNet/../Renderer/RaceNetRenderer.h:14,
                 from /home/janisozaur/workspace/OpenNFS/src/RaceNet/TrainingGround.h:14,
                 from /home/janisozaur/workspace/OpenNFS/src/main.cpp:22:
/home/janisozaur/workspace/OpenNFS/include/imgui/examples/imgui_impl_opengl3.h:30:25: note: previous specification in ‘bool ImGui_ImplOpenGL3_Init(const char*)’ here
 IMGUI_IMPL_API bool     ImGui_ImplOpenGL3_Init(const char* glsl_version = NULL);
                         ^~~~~~~~~~~~~~~~~~~~~~

https://github.com/ocornut/imgui/blob/ed0f7004d02b39d69d9a658aac1aa270633923a8/examples/imgui_impl_opengl3.h#L30
I will post here once the PR in question is merged.

Upstream is fixed in https://github.com/ocornut/imgui/commit/2e6e1bec58d5b3c0fff59fd789311537abdf5f3e now.

Thanks! Updated in 8673b29c25cba66d896066ea2ab50944b0e11850


Update Submission

Hi thanks for the pull request but create a new one and mention the issue number at the starting.
Sorry for the inconvenience.


Compact git graph option

the display of each commit on the tree part is very large for nothing,
in my sense it will be grealy better if we can have a on-line display for each commit on the tree

hmm it look like i cannot delete issues


Electron support

Allows modules using prebuild-install (such as mongodb-js/node-keytar) to leverage prebuild binaries when users are building electron apps. If the user has the below .npmrc in the root of their electron app, prebuild-install just works:
disturl=https://atom.io/download/atom-shell
target=1.2.8
runtime=electron
abi=48

With this PR, the logs now look like:
> prebuild-install -d --verbose || node-gyp rebuild
prebuild-install info begin Prebuild-install version 1.1.0
prebuild-install info looking for local prebuild @ prebuilds/keytar-v3.0.0-electron-v48-linux-x64.tar.gz
prebuild-install info looking for cached prebuild @ /home/ubuntu/.npm/_prebuilds/https-github.com-mongodb-js-node-keytar-releases-download-v3.0.0-keytar-v3.0.0-electron-v48-linux-x64.tar.gz
prebuild-install http request GET https://github.com/mongodb-js/node-keytar/releases/download/v3.0.0/keytar-v3.0.0-electron-v48-linux-x64.tar.gz
prebuild-install http 200 https://github.com/mongodb-js/node-keytar/releases/download/v3.0.0/keytar-v3.0.0-electron-v48-linux-x64.tar.gz
prebuild-install info downloading to @ /home/ubuntu/.npm/_prebuilds/https-github.com-mongodb-js-node-keytar-releases-download-v3.0.0-keytar-v3.0.0-electron-v48-linux-x64.tar.gz.11965-197065c3e219a.tmp
prebuild-install info renaming to @ /home/ubuntu/.npm/_prebuilds/https-github.com-mongodb-js-node-keytar-releases-download-v3.0.0-keytar-v3.0.0-electron-v48-linux-x64.tar.gz
prebuild-install info unpacking @ /home/ubuntu/.npm/_prebuilds/https-github.com-mongodb-js-node-keytar-releases-download-v3.0.0-keytar-v3.0.0-electron-v48-linux-x64.tar.gz
prebuild-install info unpack resolved to /data/mci/f2a6737bee2732fb1833ab8dab04ed03/src/node_modules/keytar/build/Release/keytar.node
prebuild-install info unpack required /data/mci/f2a6737bee2732fb1833ab8dab04ed03/src/node_modules/keytar/build/Release/keytar.node successfully
prebuild-install info install Prebuild successfully installed!

That's great!
Though Electron support is already present in #19 which makes prebuild-install compatible with the latest release of prebuild. You can test this PR by using the @lgeiger/prebuild-install npm module.

Solved with #19

@lgeiger oh sweet! Thanks!


[libxmlmm] Fix exported config

The usage test passed on x64-windows (header files found):
libxmlmm provides CMake targets:

  # this is heuristically generated, and may not be correct
  find_package(unofficial-libxmlmm CONFIG REQUIRED)
  target_link_libraries(main PRIVATE unofficial::libxmlmm::libxmlmm)


fix: secure variable migration token

Description

Closes #3172
fix: add secure validation to migrationToken parameter
Implement input validation for the migrationToken parameter in the Bicep template to ensure only authorized tokens are accepted.
This prevents potential misuse of the parameter and enhances the security of the deployment process.
Pipeline Reference

Pipeline

Type of Change

[ ] Update to CI Environment or utilities (Non-module affecting changes)
[ ] Azure Verified Module updates:

[ ] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ ] Update to documentation

Checklist

[ ] I'm sure there are no other open Pull Requests for the same update/change
[ ] I have run Set-AVMModule locally to generate the supporting module files.
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings

Could you please run Set-AVMModule and add the readme to this PR? This is what makes your pipeline red.

@jceval
We have added examples for Bicep parameter files to the Readme. This has been applied to all published modules but needs to be done for PRs as well. Can you please run the Set-AVMModule utility as detailed here. It is required for the validation pipeline to succeed and the contribution to be published.
Please reach out if any support is needed.


fix: streaming response with content-length breaks local dev

Addresses https://linear.app/netlify/issue/COM-222/local-dev-cli-tries-to-compute-etag-on-streaming-response-breaks

this is related to some behaviour in the fetch spec, that we won't be able to change anytime soon. closing!


Add validate flavour

Implement https://github.com/ghc/ghc/blob/464396d00450efb58330987ebac4735902ba0f01/mk/flavours/validate.mk#L1-L11.
@snowleopard Can you help me double check if this translation is right?

@izgzhen Thanks! This looks fine. Does it reduce the number of validation failures even further?
Do we run Hadrian with both validate and --flavour=validate? It looks a bit awkward. Perhaps, the validate target should switch the default flavour from default to validate? This is quite similar to the documentation build rule, where we need to run Hadrian with docs target and flag --haddock, see #414.
Please also update doc/flavours.md.

 Interesting.

It is neither a subset or a super set of the previous log as in #299. Interesting.

Strange, this flavour even makes things worse?

Strange, this flavour even makes things worse?

Hard to say. It fixed some errors, while revealing some more others. I need a closer inspection.

See #299


Code fix missing method

Fixes #14329.
Changed the quickfix so it offers to implement the missing member as a method if possible, and offers implementations as property or index signature otherwise.
Should we offer options to implement as a method and a property (ie: one with a function type)?

Can you take a look, @vladima, @zhengbli, @mhegazy, @billti ?

Putting this on hold while we get createTypeNode functionality in.

closing in favor of https://github.com/Microsoft/TypeScript/pull/16045


Rewrite theme in kitty's template

This simply rewrites the theme to match kitty's template. This should make it easy to submit the theme upstream if you feel like it.
It additionally fixes the background color which had been previously set to #1E1E29. I however couldn't find this color in the palette, as showcased at catppuccin. Lemme know if it should be set to #1E1E29 again and I'll make that change.

I know that color is off by one number (so to speak), but that was on purpose. AFAIK there is this issue were if both NeoVim and Kitty have the same background color then it'll break the background (making it transparent).
Great idea tho! Using Kitty's default theme format.

As a long term kitty and Neovim user who has also used a plethora of colour schemes, I've never run into such an issue. I've always set the same background colour for kitty and Neovim. Could you point me to where this issue is tracked? I'm curious now.


How to handle TargetInvocationException?

When I call for many JsonRpcMethod, I receive after a while a TargetInvocationException exception, and the server fails.
Why this exception occurred? And how can I catch it (to restart the server for example)
Thanks!
The version used is <IP_ADDRESS>

Can you reproduce with <IP_ADDRESS> ? It's available on nuget, or as a tag here on github.

Also, could you post the stack trace for the exception please?

I found the issue:
The issue was that a AccessViolationException occurred on the JSonRpcMethod, and this AccessViolationException is not catched by a regular try-catch.
When it occurred, the RPC-JSON server fails.
System.Reflection.TargetInvocationException was unhandled
_HResult=-2146232828
_message=Exception has been thrown by the target of an invocation.
HResult=-2146232828
IsTransient=false
Message=Exception has been thrown by the target of an invocation.
Source=mscorlib
StackTrace:
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)

   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)

   at System.Delegate.DynamicInvokeImpl(Object[] args)

   at System.Delegate.DynamicInvoke(Object[] args)

   at AustinHarris.JsonRpc.Handler.Handle(JsonRequest Rpc, Object RpcContext) in d:\temp\tmp52ED\Json-Rpc\Handler.cs:line 320

   at AustinHarris.JsonRpc.JsonRpcProcessor.ProcessInternal(String sessionId, String jsonRpc, Object jsonRpcContext) in d:\temp\tmp52ED\Json-Rpc\JsonRpcProcessor.cs:line 107

   at AustinHarris.JsonRpc.JsonRpcProcessor.ProcessJsonRpcState(String sessionId, JsonRpcStateAsync async, Object jsonRpcContext) in d:\temp\tmp52ED\Json-Rpc\JsonRpcProcessor.cs:line 41

   at AustinHarris.JsonRpc.JsonRpcProcessor.<Process>b__2(Object _async) in d:\temp\tmp52ED\Json-Rpc\JsonRpcProcessor.cs:line 31

   at System.Threading.Tasks.Task.InnerInvoke()

   at System.Threading.Tasks.Task.Execute()

   at System.Threading.Tasks.Task.ExecutionContextCallback(Object obj)

   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)

   at System.Threading.Tasks.Task.ExecuteEntry(Boolean bPreventDoubleExecution)

   at System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()

   at System.Threading.ThreadPoolWorkQueue.Dispatch()

   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

InnerException: System.AccessViolationException
   _HResult=-2147467261

   _message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

   HResult=-2147467261

   IsTransient=false

   Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

   Source=System.Data.SqlServerCe

   StackTrace:

        at System.Data.SqlServerCe.NativeMethodsHelper.CompileQueryPlan(IntPtr pQpCommand, String pwszCommandText, ResultSetOptions options, IntPtr[] pParamNames, IntPtr prgBinding, Int32 cDbBinding, IntPtr& pQpPlan, IntPtr pError)

        at System.Data.SqlServerCe.NativeMethods.CompileQueryPlan(IntPtr pQpCommand, String pwszCommandText, ResultSetOptions options, IntPtr[] pParamNames, IntPtr prgBinding, Int32 cDbBinding, IntPtr& pQpPlan, IntPtr pError)

        at System.Data.SqlServerCe.SqlCeCommand.CompileQueryPlan()

        at System.Data.SqlServerCe.SqlCeCommand.ExecuteCommand(CommandBehavior behavior, String method, ResultSetOptions options)

       at System.Data.SqlServerCe.SqlCeCommand.ExecuteReader(CommandBehavior behavior)

        at System.Data.SqlServerCe.SqlCeCommand.ExecuteDbDataReader(CommandBehavior behavior)

        at System.Data.Common.DbCommand.ExecuteReader()

        at System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query, QueryInfo queryInfo, IObjectReaderFactory factory, Object[] parentArgs, Object[] userArgs, ICompiledSubQuery[] subQueries, Object lastResult)

        at System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query, QueryInfo[] queryInfos, IObjectReaderFactory factory, Object[] userArguments, ICompiledSubQuery[] subQueries)

        at System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query)

        at System.Data.Linq.DataQuery`1.System.Linq.IQueryProvider.Execute[S](Expression expression)

        at System.Linq.Queryable.Count[TSource](IQueryable`1 source)

        at DeviceSystemManager.DataLayer.DBPersistencyDbml.Select(SelectCommand dbSelect) in c:\Users\skoen\Documents\SVN\Src\C#\projects\EncoderDecoder\MediatorMain\DataLayer\DBPersistencyDbml.cs:line 249

        at DeviceSystemManager.RPC.DeviceSystemManagerRpcService.Select(Object selectJson) in c:\Users\skoen\Documents\SVN\Src\C#\projects\EncoderDecoder\MediatorMain\RPC\DeviceSystemManagerRpcService.cs:line 169

   InnerException:

From: Austin Harris<EMAIL_ADDRESS>Sent: Wednesday, February 18, 2015 10:35 AM
To: Astn/JSON-RPC.NET
Cc: samkoen
Subject: Re: [JSON-RPC.NET] How to handle TargetInvocationException? (#37)
Also, could you post the stack trace for the exception please?
—
Reply to this email directly or view it on GitHub https://github.com/Astn/JSON-RPC.NET/issues/37#issuecomment-74829513 .  https://github.com/notifications/beacon/AKi2cmZN_pLey6LovAOHcvSL-xzk2CkMks5ntEZFgaJpZM4Dh9no.gif

http://stackoverflow.com/questions/3469368/how-to-handle-accessviolationexception
Hmm..

From the above link:
In .NET 4.0, the runtime handles certain exceptions raised as Windows Structured Error Handling (SEH) errors as indicators of Corrupted State. These Corrupted State Exceptions (CSE) are not allowed to be caught by your standard managed code. I won't get into the why's or how's here. Read this article about CSE's in the .NET 4.0 Framework:
So this isn't something we can fix.