Slow login page

Hi, I couldn't help but notice when I try to log in to the Pling store, the login page takes a while to load, I think it's related to all the images being loaded in the background, behind the login form.
Maybe you guys can pre-render an image and have it load that, instead of streaming a lot of tiny images to fix this performance issue?

Sorry I thing i got the wrong repo.


Missing required adGroupId field in /sp/campaignNegativeTargets/list

this api response needs to have adGroupId field in the docs. It is exists in the actual responses.
https://advertising.amazon.com/API/docs/en-us/sponsored-products/3-0/openapi/prod#/CampaignNegativeTargetingClauses/ListSponsoredProductsCampaignNegativeTargetingClauses

Hi @vitamon, could you confirm you are seeing this behavior for campaign-level negative targeting clauses?
Note that we support both campaign-level negative targeting and ad group-level negative targeting. adGroupId is expected to be present when using ad group-level targeting (POST /sp/negativeTargets/list), but would not be expected when using campaign-level product targeting (POST /sp/campaignNegativeTargets/list).

Thank you for quick response. Indeed, everything is ok in the docs.


Include Discrete Progress Reports in Terminal Operations

Hi guys, a big thank you to the Awesome brains behind Flutter. Keep up the good work.
However, I was thinking , would it be possible for the flutter team to include discrete progress reports during terminal operations.
For Example..Initializing Gradle.....10%..  is better of than just Initializing Gradle... So that I know what's going on. I am saying this because I am currently stucked atInitializing Gradle...for the past 4hrs. I have no idea what is going on...

It sounds like gradle wandered off into the weeds in this case. FYI @blasten. I'm reluctant to optimize for the case where operations take this long, since it likely indicates a bug somewhere. Instead, I think we should move toward having timeouts for child processes of the tool: https://github.com/flutter/flutter/issues/39141.


Update rubygem version

The functionality to use AWS profiles was added. We are bumping the version
to 0.3.0 before publishing to rubygems.

:+1:


[consensus] derive ValidatorSet from genesis txn instead of config

Motivation
This changes enable us move away from reading ValidatorVerifier from config, instead we unified with how reconfiguration works.
Genesis blob will have the ValidatorSet, the LedgerInfo commits that would include it.
Have you read the Contributing Guidelines on pull requests?
Y
Test Plan
Existing tests
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

@bors-libra r=dmitri-perelman

:pushpin: Commit 053312d has been approved by dmitri-perelman

:hourglass: Testing commit 053312d99e39323d1ff92091d77c2db6fd563d98 with merge 5af857b4e9dedb41ea4031c2a18371a1fc81ad85...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: dmitri-perelman
Pushing 5af857b4e9dedb41ea4031c2a18371a1fc81ad85 to master...


Extension Methods without CanBuildFrom?

(Maybe I'm late to the party on this. I've been a bit checked out from mailing lists and such. Sorry if so!)
I'm curious about the future of ergonomic generic extension methods in the new collections library, at least if CanBuildFrom is removed entirely.
For instance, in our codebase, we've introduced a method flatCollect, which we frequently find useful. (I noticed collect's missing, I assume that's just because it's relatively uninteresting, in terms of design.) It has the obvious meaning, with signature:
def flatCollect[Result, B](f: PartialFunction[A, TraversableOnce[B]])
                              (implicit cbf: CanBuildFrom[Coll, B, Result]): Result

We also have toMultiMap, which is an efficient implementation of xs.groupBy(_.a).eagerMapValues(_.map(_.b)) (as mentioned in #42 but using our own eagerMapValues because of frequent unintended consequences of the lazy variant).
implicit class ScEnrichColl[Coll <: Traversable[_], A, B](val __this: Coll)(implicit view: Coll <:< Traversable[(A, B)]) {
  def toMultiMap[Result](implicit cbf: CanBuildFrom[Coll, B, Result]): Map[A, Result] = ???
}

Maybe I'm being insufficiently imaginative, but it's hard for me to see how to implement them in the new approach where they maintain the same level of ergonomics as before. It's possible it's worth the reduction in complexity, but it makes me somewhat sad.
One answer is "use views and use to/FromIterable" at the end, but I don't think that handles the toMultiMap case particularly nicely. Another is to have CBF, but only for these cases. (This can be largely done via an external library, possibly.) Is there another?

Basically, what's sad about this is that you lose the ability to extract methods for common patterns like toMultiMap, without giving up the more precise types. You can do toMultiMap(_: FromIterable[B]), of course, but:

the API is a bit less fluent (imho), and
that implementation of toMultiMap I think has to make unnecessary intermediates that would not be required using CBF.

In the current state, this kind of use of CanBuildFrom would be replaced by an implicit Builder factory, as in this example.
The limitation is that we can not define a flatCollect method that is polymorphic over the kind of the collection type constructor (said otherwise, you can not write a single flatCollect method that works both with Map[_, _] and List[_]).

Maybe this kind of use cases would justify to introduce a CanBuild[-A, +Repr] thing.

@julienrf what would be the difference between this CanBuild[-A, +Repr] and the current Builder[-A, +To] in terms of API?
I also have similar facilities that rely on CBF. For example:
def mapSplit[B,C,Left,Right](f: A => Either[B,C])
                            (implicit bfLeft:  CanBuildFrom[Repr, B, Left],
                                      bfRight: CanBuildFrom[Repr, C, Right]): (Left, Right)

I knew it worked with things like String (producing Strings), but I did not even realize that it also worked with Map types... Now I'm even more impressed with the old design 😅
But however technically impressive, I'm still not convinced this was worth the complexity, or even a good idea at all: to me it's based on a false premise –– that the user of a collection usually wants collection transformation operations to result in the same type as the original collection.
In my personal experience however, the usage I make of the transformed collection is almost always what dictates what I want the end result type to be. If I'm going to test existence I want to transform into a Set; if I want random access, into a IndexedSeq; if I want mapping, into a Map; if I want List-like analysis, into a LinearSeq, etc., etc. It rarely (if ever) seems to be the case that I want the data source to retain its original collection type (which is usually irrelevant and merely incidental).
This means I'm usually just writing xs.iterator ... .toX or xs.view ... .toY (or I should be, if I'm concerned with performance). Does anyone have examples to contradict this impression?

Oh you’re right, CanBuild[-A, +Repr] is equivalent to an alias to () => Builder[A, Repr], so there would be no difference… I will try to think of a nice solution for the kind polymorphism issue.

@julienrf ok thanks, I'm a bit less worried, though still somewhat sad.
@LPTK I definitely can see the logic that the old system's complexity may be too much to justify the flexibility it gives you. And I also agree that . Especially now that views are getting improved.
I do still think it's bad there's now an "abstraction penalty" in terms of preciseness of types: if you have an expression like (just a random thing, not a real thing I find myself doing):
x.map(_.swap).flatMap { case (k, vs) => vs.map(k -> _)}

that you see repeated in a few places, sometimes with Seq, sometimes with Set, sometimes with Map, you can't extract a single method that abstracts it and preserves the old result types, because overload resolution doesn't preserve across generic boundaries without type classes. (I think?)
Similarly with Set/Bitset.

@julienrf kind of hijacking this to say that, if you're going to introduce CanBuild or a similar mechanism (I'm all for that, it's hugely useful to me), would it be possible to give some thoughts to making it serializable?
This might seem a bit weird, but when working with Apache Spark or similar frameworks, you need all your values to be serializable. With type class and other implicit parameters, it's really easy to find yourself in a situation where your value holds non-serializable data without realising it. Specifically, the current CanBuildFrom is not, or not often, serializable, which break a lot of existing libraries (my specific example is kantan.csv, but I'm sure there are other - you'll find hacks to work around this in popular libraries like shapeless).

I’m closing this issue since the use cases given here are now parts of our tests.

thanks! I appreciate it. Great work, btw
On Fri, Jun 30, 2017 at 2:21 AM, Julien Richard-Foy <
<EMAIL_ADDRESS>wrote:

I’m closing this issue since the use cases given here are now parts of our
tests.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scala/collection-strawman/issues/44#issuecomment-312219572,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAloVJ4IPN7Ubh5mF9xYyoSRRqiCiYIks5sJL4BgaJpZM4MWbsb
.


[BUG-1.16.1] Stopping server doesn't actually stop it. (server hangs.) (read desc)

What happened?

Trying to stop the server and it doesn't actually stop.

What should happen?

Server stops as it should normally.

Steps to reproduce

Have DCIntegration hooked up to a bot and is connected to a chat in Discord.
Stop the server and it hangs for a couple of minutes.

Version

1.16.1

Mod version 1.3.1
Config file

https://hastebin.com/nucuhejexu.shell

Crash report if available. No Crash but some Logs;
Console Log:

https://hastebin.com/gimigilipu.cs

Duplicate of #58

So looking through that issue, there appears to be no fix?

Not yet, no

So by actually just disabling the "Server Stopped & Server Started, Server Starting.." messages, (making them blank). The server Hang doesn't happen anymore. It just throws an error in console because of the messages being blank but it still works like normal.
https://hastebin.com/uduzakufic.pl


fix: change compatibility target for the final bundle (#409)

fix: change compatibility target for the final bundle
close #409

This has been fixed in https://github.com/kamranahmedse/driver.js/pull/422/files -- thank you for the PR! Let me know if you face any issues.


CallableStatement: using named parameters to specify only certain parameter values

(ref: this Stack Overflow question)
Section 13.3.2 of the JDBC 4.2 specification says

Named parameters can be used to specify only the values that have no default value.
In CODE EXAMPLE 13-21, the procedure COMPLEX_PROC takes ten parameters, but only the first and fifth parameters, PARAM_1 and PARAM_5, are required.
CallableStatement cstmt = con.prepareCall("{CALL COMPLEX_PROC(?, ?)}";
cstmt.setString("PARAM_1", "Price");
cstmt.setFloat("PARAM_5", 150.25);

I just tried this with 6.3.4.jre8-preview.jar and I couldn't get it to work. It seemed that I had to provide a parameter placeholder for every possible parameter, ((?,?,?,?,?,?,?,?,?,?) in the above example), and I didn't see a way to specify DEFAULT for a parameter that I would have otherwise simply omitted.
In other words, it seems like named parameter support for CallableStatement in mssql-jdbc is currently limited to allowing us to specify the parameters in any order, but not to "pick and choose" the parameters we actually supply.
Have I missed something?

Hi @gordthompson ,
Thank you for creating the issue, I can confirm that this is a deficiency in the implementation.  #547 is potentially related, we will address the issue once/when the PR is merged.

@cheenamalhotra  It looks like it is in progress for more than two years. Is there any progress?

Any update on whether this will be addressed soon?

hi @kliakos
Sorry to report that this issue is still in our backlog it didn't make it to the top of the list in triage.


Add the performance viewer data collector

This PR adds the performance viewer data collector, and new interfaces to support this collection of data. We use a data structure as follows to store the datasets.
export interface IPerfDatasets {
    /**
     * The ids of our dataset.
     */
    ids: string[];

    /**
     * The data to be processed by the performance graph. Each slice will be of the form of [timestamp, numberOfPoints, value1, value2...]
     */
    data: DynamicFloat32Array;

    /**
     * A list of starting indices for each slice of data collected. Used for fast access of an arbitrary slice inside the data array.
     */
    startingIndices: DynamicFloat32Array;
}

We store an array of ids for cross reference for what offset belongs to which id. We do not allow removal of individual performance strategies because of this.
We use the data property to store all of our data in the shape as described by the comment. This allows us to eliminate redundant timestamp data being stored, and allows us to only have a single array which stores all our data.
We use the startingIndices array for fast lookup on where each slice begins.
This overall will decrease memory consumption from the previous method of collecting data as an array of IPerfPoints and having a separate array for each dataset, and it will also increase performance! Finishes the create data collector task in #10566

Just had a quick pass at the PR, I will run over it again tomorrow morning to see if I missed something. Just a few questions actually :-)

@sebavan - yes, we want the data collection process to be a part of core and not a part of an external project. this way we can have different views of the same data (and other devs will be able to implement their own perf analyzer without importing an external project).


Busy.org German translation error in main navigation

Expected behavior
The navigation menu on the left side used to distinguish between trending and your feed.
Before it was translated to "Feed" for your feed from your followers and "Neuigkeiten" for the trending page.
Finding a good translation here is difficult but I would suggest:
Keep "Neue Posts" or "Neue Artikel" for the Feed from accounts you follow. And used "Trending" on the trending page also in German.  This would be in line with German translations of other big platforms.
Actual behavior
Now both menus are translated with "Neuigkeiten" As you can see in the screenshot. This requires improvement as it is difficult to use. "Neuigkeiten" also is not a word you would use stand alone as this describes neither the trending page correctly nor your news feed correctly.
How to reproduce
Logon to busy.org and switch languages to German.
Recording Of The Bug

Posted on Utopian.io -  Rewarding Open Source Contributors

I suggest to simply translate "News" as "Trends" as it is the trendingpage.
Feed -> Neuigkeiten
News -> Trends
https://crowdin.com/translate/busy/22/en-de#1088

Translations are handled on CrowdIn.

Hello, even though I myself do speak some languages I'd love to promote steemit/busy etc. to friends who dont speak English, but i can't simply find German, Spanisch, French interfaces, also not on Busy.org - how can I access a Spanish Busy.org interface? Or is it not public? Is help needed? I do translations sometimes. I've seen that translations are hanled on CrowdIn - does it makes sense I do register there in order to help?


python bindings?

We do not offer Python bindings yet.

Would love to contribute if python bindings are a potential project. The pycolmap library is excellent.


Add channel range tool for new VD coldbox CRPs

Channel range and group tools were created for the the first coldbox run period (Nov 2021 - June 2022) but the CRPs are very different for the new CRPs (CRP2, CRP3, ...) and we need a new tool to describe those.

The new CRP layout and channel mappings are described in
https://indico.fnal.gov/event/55195/contributions/245292/attachments/156692/204617/vg_crp2_cmap.pdf
I see Slavic proposes updating the VDColdboxChannelRangeTool in that talk.
@vgalymov have you done anything with that code? If not, I propose to create an new class, perhaps CrpChannelRangeTool with mappings for u, v x instead of u, y, x. LMK if this is ok with you.

have you done anything with that code? If not, I propose to create an new class, perhaps CrpChannelRangeTool with mappings for u, v x instead of u, y, x. LMK if this is ok with you

No, I have not done anything. The name is good.

OK, I will begin work on that. Your talk gives the plane channel counts for a 3072-channel CRP while mentioning the CDR calls for 3200. Is CRP2 already 3072 channels and is this the current baseline for ProtoDUNE-2V?

Your talk shows the mapping of wires to electronics but i also need the mapping of wires to offline channel numbers. Where can I find those? I add @tomjunk  here who also may be able to answer or at least confirm that the decoder is using those same assignments.
I need these for top and bottom CRP's in the coldbox (after CRP1). It would be nice to also have this for ProtoDUNE-2V so I can ensure the code will also handle that. I will add fcl params to handle variations between these detectors.

OK, I will begin work on that. Your talk gives the plane channel counts for a 3072-channel CRP while mentioning the CDR calls for 3200. Is CRP2 already 3072 channels and is this the current baseline for ProtoDUNE-2V?

Yes, the info in CDR is already out-of-date. The CRP channel count was optimized to make the best use of FEMB channels. So there should not be any ghost channels for BDE anymore, since the number of boards will be exact per CRP.

The mapping of wires to offline channels follows basically the same idea U, V, Z. I put some details in docdb 26181. Basically:

U wires go to channels 0 - 951
V wires go to channels 952 - 1903
Z wires go to channels 1904 - 3071

Normally the scheme should be valid for both top and bottom.
 I would advocate using 0-6143 for A, 6144-12287 for B, etc. This way you do not have to know how many TPCs there are to convert a channel number to a TPC number and strip location.

OK. I am writing the CrpChannelRangeTool with this convention.

I completed a first pass at CrpChannelRangeTool. From the unit test, here are the ranges defined for the coldbox:

crdet: [0, 3072) CRDET
cruC: [0, 3072) CRU-C
cruCu: [0, 952) CRU-CU
cruCv: [952, 1904) CRU-CV
cruCz: [1904, 3072) CRU-CZ

and for ProtoDUNE-VD:

crdet: [0, 12288) CRDET
crt: [0, 6144) CRT
crb: [6144, 12288) CRB
crtA: [0, 3072) CRT-A
crtB: [3072, 6144) CRT-B
crbA: [6144, 9216) CRB-A
crbB: [9216, 12288) CRB-B
crtAu: [0, 952) CRT-AU
crtAv: [952, 1904) CRT-AV
crtAz: [1904, 3072) CRT-AZ
crtBu: [3072, 4024) CRT-BU
crtBv: [4024, 4976) CRT-BV
crtBz: [4976, 6144) CRT-BZ
crbAu: [6144, 7096) CRB-AU
crbAv: [7096, 8048) CRB-AV
crbAz: [8048, 9216) CRB-AZ
crbBu: [9216, 10168) CRB-BU
crbBv: [10168, 11120) CRB-BV
crbBz: [11120, 12288) CRB-BZ

Th three fields are the name, channel range and primary label.

If I understand correctly the crt is for top CRPs while crb is for bottom ones for protodune vd. If this is so, then the names for the channels ranges must be swapped. The bottom CRPs occupy [0, 6144) channel range while the top ones [6144, 12288).

Oops. Thanks I fixed that. Here are update ranges for ProtoDUNE-VD:

crdet: [0, 12288) CRDET
crb: [0, 6144) CRB
crt: [6144, 12288) CRT
crbA: [0, 3072) CRB-A
crbB: [3072, 6144) CRB-B
crtA: [6144, 9216) CRT-A
crtB: [9216, 12288) CRT-B
crbAu: [0, 952) CRB-AU
crbAv: [952, 1904) CRB-AV
crbAz: [1904, 3072) CRB-AZ
crbBu: [3072, 4024) CRB-BU
crbBv: [4024, 4976) CRB-BV
crbBz: [4976, 6144) CRB-BZ
crtAu: [6144, 7096) CRT-AU
crtAv: [7096, 8048) CRT-AV
crtAz: [8048, 9216) CRT-AZ
crtBu: [9216, 10168) CRT-BU
crtBv: [10168, 11120) CRT-BV
crtBz: [11120, 12288) CRT-BZ

We also want a channel range group tool. Range groups are collections of ranges and allow us to group non-contiguous channels. I am adding the tool CrpChannelGroups to return such groups by name. To start, there is simply one group for each range.
I want to test the channel group tool with the same ranges used to test the channel range tool. To avoid code duplication, I moved the test code to a shared file test/crpChannelRangeTests.h.

ChannelRangeGroups is pushed.

I am renaming the CRP1 and  adding CRP2+ channel range and group tool configs to vdcb_tools.fcl:

##### Channel ranges, groups and map for CRP1

tools.channelRangesVdcb1: {
  tool_type: VDColdboxChannelRanges
  LogLevel: 0     # To remove noise in pdChannelRange
  GhostRange: [3200, 3392]
}

tools.channelGroupsVdcb1: {
  tool_type: VDColdboxChannelGroups
  LogLevel: 0     # To remove noise in pdChannelRange
}

tools.onlineChannelMapVdcb: {
  tool_type: VDColdboxOnlineChannel
  LogLevel: 1
}

##### Channel ranges, groups and map (not yet) for CRP2+

tools.channelRangesVdcb2: {
  tool_type: VDColdboxChannelRanges
  LogLevel: 0     # To remove noise in pdChannelRange
  GhostRange: [3200, 3392]
}

tools.channelGroupsVdcb2: {
  tool_type: VDColdboxChannelGroups
  LogLevel: 0     # To remove noise in pdChannelRange
}

##### Default channel ranges and groups

tools.channelRanges: @local::tools.channelRangesVdcb
tools.channelGroups: @local::tools.channelGroupsVdcb

The last lines here still need to be changed.
I propose to remove the last two lines and put them in separate files for the two data-taking periods:

vdcb1_tools.fcl
vdcb2_tools.fcl

with those to include vdcb_tools.fcl and to be included instead of that file in the reco config files.
I will start on this Monday. Comments welcome before then.
Next step is to modify the CRP2+ reco files to use the new channel ranges. I

I begin by looking where vdcb_tools.fcl is used:

duneproc> fclgrep vdcb_tools.fcl
/home/dladams/proc/build/dev01/workdir/localProducts_dunesw_v09_63_00d00_e20_prof/duneprototypes/v09_63_00d00/fcl/hdcoldbox_dataprep.fcl:#include "vdcb_tools.fcl"
/home/dladams/proc/build/dev01/workdir/localProducts_dunesw_v09_63_00d00_e20_prof/duneprototypes/v09_63_00d00/fcl/vdcoldbox_dataprep.fcl:#include "vdcb_tools.fcl"
/home/dladams/proc/build/dev01/workdir/localProducts_dunesw_v09_63_00d00_e20_prof/duneprototypes/v09_63_00d00/fcl/vdcoldbox_raw_dataprep.fcl:#include "vdcb_tools.fcl"
/home/dladams/proc/build/dev01/workdir/localProducts_dunesw_v09_63_00d00_e20_prof/duneprototypes/v09_63_00d00/fcl/vdcoldbox_raw_dataprep_reco.fcl:#include "vdcb_tools.fcl"
/home/dladams/proc/build/dev01/workdir/localProducts_dunesw_v09_63_00d00_e20_prof/duneprototypes/v09_63_00d00/fcl/vdcoldbox_raw_tdedataprep.fcl:#include "vdcb_tools.fcl"
/home/dladams/proc/build/dev01/workdir/localProducts_dunesw_v09_63_00d00_e20_prof/duneprototypes/v09_63_00d00/fcl/vdcoldbox_raw_tdedataprep_reco.fcl:#include "vdcb_tools.fcl"
/home/dladams/proc/build/dev01/workdir/localProducts_dunesw_v09_63_00d00_e20_prof/dunedataprep/v09_63_00d00/fcl/vdcb_tools.fcl:# vdcb_tools.fcl
./vdbproc-cnr.fcl:#include "vdcb_tools.fcl"
./vdbproc-cnrw.fcl:#include "vdcb_tools.fcl"
./vdbproc.fcl:#include "vdcb_tools.fcl"
./vdtproc.fcl:#include "vdcb_tools.fcl"
/cvmfs/dune.opensciencegrid.org/products/dune/dunesw/v09_63_00d00/fcl/crpcb_top_process.fcl:#include "vdcb_tools.fcl"
/cvmfs/dune.opensciencegrid.org/products/dune/dunesw/v09_63_00d00/fcl/vdcb_tools_dune.fcl:#include "vdcb_tools.fcl"
./vdbproc-cnr.fcl:#include "vdcb_tools.fcl"
./vdbproc-cnrw.fcl:#include "vdcb_tools.fcl"
./vdbproc.fcl:#include "vdcb_tools.fcl"
./vdtproc.fcl:#include "vdcb_tools.fcl"

The first file, hdcoldbox_dataprep.fcl int't even VD. I modify it to instead include HD tools and use an HD bad channel list. Only after the change, the fcl can be parsed.

The next five are top-level VD. I think all are CRP1 except for vdcoldbox_raw_dataprep_crp2.fcl which is CRP2+. It includes the correponding CRP1 top-level reco and I break that dependency by copy the code. The tool definitions in vdcb_tools.fcl are being split as described in dunedataprep issue 12 and I modify all the top-level files here to use one of the split files.

I did the splitting and remove content from the old file except for a comment and something to trigger a fcl failure. The fcl files including those from this package have been modified to include the new tools files and verified to parse. We check that reconstruction is still working.
Before pushing that change, we also need to fix the dunesw files seen in the fclgrep above. I split vdcb_tools_dune.fcl into vdcb1_tools_dune.fcl and vdcb2_tools.dune.fcl. Fclgrep shows the original file was not included elsewhere so no further mods are required.
File crpcb_top_process.fcl looks like it is top-level config for CRP2/3 reco and so I switched vdcb_load_tools.fcl include  to vdcp2_load_tools.fcl. I did not turn up any users of the original fcl with fclgrep so no further changes are needed.

There is more work to do but the final reco fcl config should be as it was. I verified that the unit tests and duneTestFcl run successfully. I will push the mods now so we can run the CI tests to check reco. Note the mods of all three:

dunedataprep
duneprototypes
dunesw

must be run together.

No complaints and so I am closing this.


USB Device Not Detected

import visa
rm = visa.ResourceManager("@py")
print rm.list_resources()

returns:
(u'ASRLCOM1::INSTR',)

But using the ni driver:
import visa
rm = visa.ResourceManager()
print rm.list_resources()

returns:
(u'USB0::0x0957::0x0509::MY42403191::INSTR', u'ASRL1::INSTR', u'ASRL3::INSTR')

Why doesn't the pyvisa-py driver detect the USB device? It is an E5071B Agilent Network Analyzer.
here is my debug:
Machine Details:
Platform ID:    Windows-XP-5.1.2600-SP3
Processor:      x86 Family 6 Model 14 Stepping 8, GenuineIntel
Python:
Implementation: CPython
Executable:     C:\src\venv\Scripts\python.exe
Version:        2.7.9
Compiler:       MSC v.1500 32 bit (Intel)
Bits:           32bit
Build:          Dec 10 2014 12:24:55 (#default)
Unicode:        UCS2
PyVISA Version: 1.6.3
Backends:
ni:
Version: 1.6.3 (bundled with PyVISA)
#1: C:\WINDOWS\system32\visa32.dll:
found by: auto
bitness: 32
Vendor: National Instruments
Impl. Version: 5243905
Spec. Version: 5243136
#2: C:\WINDOWS\system32\visa32.dll:
found by: auto
bitness: 32
Vendor: National Instruments
Impl. Version: 5243905
Spec. Version: 5243136
py:
Version: 0.1
ASRL INSTR: Available via PySerial (N/A)
TCPIP INSTR: Available
USB INSTR: Available via PyUSB (1.0.0b2). Backend: N/A

You have not installed a Backend for PyUSB. Checkout the PyUSB documentation.
Within PyVISA we are trying to provide a better error message for this.
See #23  and https://github.com/walac/pyusb/issues/95


Logic inverted in running services as root vs user

When running as root, you need to add the UserName key to the plist, however, the key is being added when running as local user, and not when running as root, causing almost (if not all) services to fail.

https://github.com/Homebrew/homebrew-services/pull/39

I've copied your description to the PR, and will close this issue in favour or the pull request.


Server Update timings?

Been using Azure AD Domain Services for over two years. My AADDS is on a classic network. Infrequently at random times my global catalog server is unavailable and I can't use my Azure Windows Server running NPS to login my users. So I have about 15 minute outages on user logins. We should be able to block out times for not running the Windows updates on these servers, like only at 2am on weekend? Both GC servers show under nslookup gc._msdcs.mydomain.com. During the outages i always get error Event ID 6274 The Active Directory global catalog cannot be accessed. Are you running same Windows Update settings on these two Windows AD boxes?

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

ID: 1ac3ceff-f36d-91b3-c722-a7a280cc17c4
Version Independent ID: 32420f48-3d50-1e20-a994-66230dc3a00f
Content: FAQs - Azure Active Directory Domain Services
Content Source: articles/active-directory-domain-services/faqs.md
Service: active-directory
Sub-service: domain-services
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

More investigation: The outage of the GCs appear to be the same time within the minute that your backup is taken.  When I look under Monitors on the portal for this AADDS> Last backed up on

@rudischmitz71 Thanks for your feedback! We will investigate and update as appropriate.

Hey @rudischmitz71  are you still having this issue?

Yes. It happened this morning for about 15 minutes. Then the global catalog
servers are back and my NPS server can do radius after that. It only
happens intermittently, so i haven't had a change to track it down. After
seeing the azure "backup time" coinciding with the outage I see it might be
that.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/37431?email_source=notifications&email_token=ADSAZIMUK3LINWIX6BQXVBDQFRZE3A5CNFSM4INXLAY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4X44MI#issuecomment-523226673,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADSAZINUJQTTDQ57WFZL6VLQFRZE3ANCNFSM4INXLAYQ
.

@rudischmitz71 I see...
So it looks like it might be a backup issue that's causing users not to be able to login in regards to this.
How would you like to proceed in regards to the scope of this doc github issue?

@rudischmitz71 I'm following up on this issue, can you please respond in regards to the previous replies on this thread? Thanks

No need for a follow up. Thanks. If it happens again I will put in a
Support ticket on my Azure account.
On Wed, Aug 21, 2019 at 12:02 PM Frank Hu<EMAIL_ADDRESS>wrote:

@rudischmitz71 https://github.com/rudischmitz71 I'm following up on
this issue, can you please respond in regards to the previous replies on
this thread? Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/37431?email_source=notifications&email_token=ADSAZIMXCKG4R4PF6OPUORDQFVYIVA5CNFSM4INXLAY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD42MODY#issuecomment-523552527,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADSAZILG6TURWHHI5STPMZDQFVYIVANCNFSM4INXLAYQ
.

@rudischmitz71 Please let us know if there are anymore questions within the scope of this git issue. If not, I will be closing out this git issue by end of day today. Please reopen this git issue if you have anymore concerns. Thanks


Schema keys are case-insensitive, but only in one direction?

I'm trying to autogenerate links for ticket numbers which look like ABC-123. So I added a schema that I thought would match this:
markdown.linkify.add('ABC-', {
	validate: /[0-9]+\b/,
	normalize: match => match.url = `/bug/${match.url}`,
})

But this doesn't seem to work. After a lot of head-scratching, I discovered that it works if I make the key lowercase, like 'abc-', and this also matches the uppercase prefixes in my document. I don't really mind the case insensitivity, but it's very confusing that it only works one way, and having uppercase in keys just fails silently.
(I was also very confused by the docs for key, which say "Only whitespaces and punctuation allowed." even though the example skype: has alphabetic characters. After staring for a while I think this sentence fragment is referring to the previous sentence, which should maybe be rephrased as “linkify-it makes sure that this prefix only matches if it is preceded by whitespace or punctuation, not with alphanumeric characters or symbols.” Though it's still not entirely clear to me what the difference between a "punctuation" and a "symbol" character might be.)

http://www.unicode.org/reports/tr44/#General_Category_Values - see unicode docs for "categories" definitions.
This package designed to search URI-like patterns, and may have specific behaviour. Your ticket pattern is not URI-like. It may work, but i can not guarantee/predict anything.
In general, i'd suggest to dig /index.js if any questions about logic (how schemas are compiled). It's quite simple (if you don't try to understand /lib/re.js)

This package designed to search URI-like patterns, and may have specific behaviour.

Well, I was going off of the “Example 2” from the README, and the ticket IDs aren’t any less URI-like than a Twitter handle, really. Having had another poke at it, even for URI-like things (like the git: handler mentioned in the docs) there's still an undocumented requirement that the key is lowercase. I presume the intention is that the schema name as passed to .add() is already in canonical form, but that’s not really obvious as documented.

You can suggest docs update via PR id you wish.


[C++] Use DeserializePlan instead of DeserializePlans in Substrait Testing

Describe the enhancement requested
Some of the existing test cases use the DeserializePlans method where it could be now replaced with DeserializePlan.
In such cases, the DeserializePlan method must be used.
Component(s)
C++

take

I am removing my assignment, since I am mostly maintaining Arrow Java.


Automated Regression test for multiple credential request (Walk & Run)

Walk
Multiple credentials revokable and non-revokable in the proof request with a proof of non-revocation for the revokable one
Run
Multiple credentials with the same conditions as above, but on separate ledgers.
Related Stories
#614
#676
#46

closing as stale


New Crowdin updates

Pull Request Test Coverage Report for Build 590135401

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

Totals

Change from base Build 590116863:
0.0%

Covered Lines:
440

Relevant Lines:
2256

💛  - Coveralls


App won’t load white screen

Whenever I try to launch the app it’s just a white screen a doesn’t load I’ve tried downloading it again and same outcome I’m on iPhone 11 Pro Max on 13.3

Reboot and retry solved my issue. Same issue on iPad Air 3 13.3 Jailbroken.

#32


Use position: static

Isn't it possible to use the spinner with position: static?
I cannot use it as absolutely positioned and I cannot find any options to change it.

The position has to be absolute, fixed or relative since the child elements (the lines) are absolutely positioned. Wouldn't { position: 'relative' } work too in your case?

yes, position: relative would probably work as well. how can I set it to relative?

It's a config option.
Martin<EMAIL_ADDRESS>schrieb am Fr., 13. Nov. 2015 um 15:21:

yes, position: relative would probably work as well. how can I set it to
relative?
—
Reply to this email directly or view it on GitHub
https://github.com/fgnass/spin.js/issues/307#issuecomment-156445055.

Sorry. Just found it in https://github.com/fgnass/spin.js/blob/master/spin.js. Thanks


[Tree Borrows] Dealing with Interior mutability (Cell).

Add support for interior mutability, corresponding to Part 4: Dealing with Cells (interior mutability)

Closing due to changing #221 to a PR for the "Full Support"


Refine the document for getting start

For requirement: https://kubernetes.slack.com/archives/C019ZRGUEJC/p1600182959018100

Add Want to contribute block more in the main README
Add more install and deployment related info in deploying.md
Change deploying.md to the DEVELOPMENT.md
Remove the Features block in the main README because it is already out-of-date

Hi Sascha,
What should I add in the header?
I also view other DEVELOPMENT.md, some of them are similar, such as knative/serving md:
https://github.com/knative/serving/blob/master/DEVELOPMENT.md
They all follow the similar way.
I am not sure if we also need to add the other license for the md format?

Hi Sascha,
What should I add in the header?
I also view other DEVELOPMENT.md, some of them are similar, such as knative/serving md:
https://github.com/knative/serving/blob/master/DEVELOPMENT.md
They all follow the similar way.
I am not sure if we also need to add the other license for the md format?

I would change the file header to:
<!--
Copyright 2018, 2020 The Tekton Authors
Copyright The Shipwright Contributors

SPDX-License-Identifier: Apache-2.0

Documentation inspired from https://github.com/tektoncd/pipeline/blob/ce7591acec8a6aa726d88e5cc057588665881ace/DEVELOPMENT.md
-->

Hi Sascha,
I also correct the Copyright

Hi @SaschaSchwarze0 , @adambkaplan or all,
Do you have any suggestions?
If no other suggestion, I will go ahead to merge this PR.
Thanks!

Hi, you just mentioned me. Please be aware that I am on vacation and come back October 5th.

/lgtm

/approve


docs: add warning to openshift and rss3

Check List
Please read and check followings before submitting a PR.

[ ] I want to publish my theme on Hexo official website.

[ ] I have read the theme publishing doc.
[ ] name is unique.
[ ] link URL is correct.
[ ] preview URL is correct.
[ ] preview URL web site is rendered correctly.
[ ] Add a screenshot to source/themes/screenshots.
[ ] Screenshot filename is same as value of name.
[ ] Screenshot size is 800 * 500.
[ ] Screenshot file format is png.

[ ] I want to publish my plugin on Hexo official website.

[ ] I have read the plugin publishing doc.
[ ] name is unique.
[ ] link URL is correct.

[x] Others (Update, fix, translation, etc...)

Languages:
[x] en English
[x] ru Russian
[x] zh-cn simplified Chinese
[x] zh-tw traditional Chinese

Note
No need to translate ko, pt-br, th languages if you submit a PR for documentation.

Warning
ko, pt-br, th languages document are inactive. Please, submit issue if you want to continuous contribution to them.

https://github.com/hexojs/site/pull/2111#issuecomment-1871723971


Move binary logs to google cloud object storage

Storing the files in a public cloud storage bucket prevents the messiness of keeping them in the git repo while ensuring the file is accessible by the test both in open source and when running internally.

No unchanged relevant lines lost coverage.
Overall coverage remained the same at 52.141%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1668

Relevant Lines:
3199

💛  - Coveralls

Can you delete this file too?
https://github.com/openconfig/featureprofiles/blob/main/.gitattributes


Crash after adding dadbattle lights / philly glow?

Describe your problem here.
idk how this stuff works or why this is bugged, but I don't wanna lose 2 hours of my life charting because of this. I can't load the chart from debug, same error. Anyone more experienced know a way to fix this from the .json itself?

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

dadbattle spotlight only works on week1, & philly glow only works on week 3, get this through your dumb brain

dadbattle spotlight only works on week1, & philly glow only works on week 3, get this through your dumb brain

Makes sense
Was charting using week 3 as a base
Doesn't solve my problem

well that's just how it works

Listen if you can't help me stop responding. Calling me dumb doesn't fix anything.

that's your fix, just don't use them on other weeks, other then the appropriate weeks

So your fix is to not use them in the first place?
Too late buddy.  That's why I'm asking for help! Too bad you're the only one here. I'll wait until tomorrow to see if anyone has anything helpful to say :)

you can't use dadbattle spotlight on any other week then week1, & philly glow can only be used on week3, that's how it fucking works

The error you posted is missing chart

The error you posted is missing chart

Added a drive link

the song is called pico, not pico-hard

the song is called pico, not pico-hard

Ah, I was choosing normal diff. in freeplay when I went to change the song via debug, wasn't aware that you don't put the -hard at the end in that case.
Thanks for the helpful reply!


Add inputs label checker

This pull request adds a new checker (#4). Input label checker checks if inputs (text fields, checkboxes, radio buttons, switches) have semantic labels.
Example of a failing check:
TextField()

Example of a passing check:
TextField(
    decoration: InputDecorartion(
        hint: 'This is hint',
    ),
)

In the latter example hint becomes a semantic label and is visible to screen readers. Text fields may use hint, labelText or label and these work fine with the checker which is demonstrated in input_label_checker_test.dart
Note: this new checker is on by default
In addition, checkers now have to provide resolution guidance with example on how issues could be fixed (#26).
Closes #4
Closes #26

Found an issue when no issue found for ToggleButtons with icons (and perhaps some other form widgets with missing semantic labels). Added a test and fixed the issue in 48c3b60693325435c1bc4d1bee01a8d6333b17fb

Latest change seems to work also with ToggleButtons


inserMany and updateMany should also cascade relations

Currently, only insertOne, updateOne, removeOne are cascading relations, this should also be possible via *Many methods.

Done


how to set on-off auto indentation?

Thanks.

I must've missed this at the time, but indentation for your particular editor is not handled by this library, but by your editor plugin instead.


Error loading shared library ld-linux-aarch64.so

Hey all,
I'm working on an npm package that uses node-ffi to load a binary .so file. This works fine on Heroku and in a Docker container built from the node:boron image, but loading the lib fails on a now.sh deployment (using package.json) with the following error:
Dynamic Linking Error: Error loading shared library ld-linux-aarch64.so.1: No such file or directory (needed by /home/nowuser/src/node_modules/envkey/ext/envkey-linux-arm64.so)

The problem seems similar to this issue, but with a different missing dependency. Any ideas? Thanks!

Not sure where your .so file comes from, but apparently its linked to an ARMv8 ld library. It seems that the SO files is improperly compiled for x64-bit linux operating systems.

@TooTallNate Thanks for the reply. To add some context, I'm using a try/catch to attempt to load two different .so files on 64-bit linux platforms: first attempt is a linux-amd64.so, and then if that fails I attempt to load a linux-arm64.so file.
The linux-amd64.so file fails with the following error:
 Dynamic Linking Error: Error relocating /home/nowuser/src/node_modules/envkey/ext/envkey-linux-amd64.so: __vfprintf_chk: symbol not found

The linux-arm64.so file fails with the ld-linux-aarch64 error I posted.
Perhaps the first failing .so is the more relevant one? Does that error message bring anything to mind?
These .so files are in an ext directory inside my package. I'm constructing the path like this:
path.join(__dirname, "ext", filename)

Indeed the first failing error is more relevant in this case. We use Alpine Linux for Now deployments which includes a libc compatibility layer, but it seems that __vfprintf_chk is not included in that.
If you have control over the native code and can figure out where that is used and remove it then that might work. Or statically compiling glibc to the SO file might work as well.
In general running binaries between Alpine (which uses MUSL) and more "common" distros (that use glibc) like Debian/Ubunutu gets pretty tricky fast.

Another possibility is to use a Dockerfile using a glibc based distro as the base image for your application. That way, you would be more in control over which libc is used.


SqlServer: Literals with real type is always considered float type

In SSMS
SELECT SQL_VARIANT_PROPERTY(0E0, 'BaseType')
//Result: float

We generate literal for real (C# single) & float (C# double) as 0E0 format. By default SqlServer assumes it to be float type. This forces upcasting when used inside SQL functions which causes runtime InvalidCastException.
Example:
public class Blog
{
    public int Id { get; set; }
    public float? Value { get; set; }
}

var query = db.Blogs.Where(b => b.Id == 1).Select(b => b.Value ?? 0).SingleOrDefault();

Throws
 An exception occurred in the database while iterating the results of a query for context type 'EFSampleApp.MyContext'.
      System.InvalidCastException: Unable to cast object of type 'System.Double' to type 'System.Single'.
         at lambda_method(Closure , QueryContext , ValueBuffer )
         at Microsoft.EntityFrameworkCore.Query.ExpressionVisitors.Internal.ProjectionShaper.TypedProjectionShaper`3.Shape(QueryContext queryContext, ValueBuffer valuUnhandled Exception: eBuffer)
         at Microsoft.EntityFrameworkCore.Query.Internal.QueryingEnumerable`1.Enumerator.BufferlessMoveNext(Boolean buffer)
         at Microsoft.EntityFrameworkCore.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state, Func`3 operation, Func`3 verifySucceeded)
         at Microsoft.EntityFrameworkCore.Query.Internal.QueryingEnumerable`1.Enumerator.MoveNext()
         at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)
         at lambda_method(Closure , QueryContext )
         at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.<>c__DisplayClass17_0`1.<CompileQueryCore>b__0(QueryContext qc)

Generated SQL
SELECT TOP(2) COALESCE([b].[Value], 0E0)
FROM [Blogs] AS [b]
WHERE [b].[Id] = 1

Value column is mapped to real data type in server. But 0E0 is taken as float literal. COALESCE function uses the highest precedence data type for final result type. Which makes result of type float. But C# expects single instead of double hence fails.
There can be few more functions/cases like this.

The second issue was handled for case of bitwise & for Enum.HasFlag in #8851
We should consider generating the literal value with explicit casting to avoid such issues.

@smitpatel  [closed-fixed] but not closed?

Solution: Hard casting to real type for SqlServer.
Filing separate issue for bigint/numeric.


Some users were confused not to see ‘bus passes’ in the list of Verify services provided in the hub.

Impact: These users were then more confused about why they were being asked to use Verify.
Evidence: When trying to understand the role of Verify, some users looked into the list of services provided in the hub, but were unable to find anything relating to concessionary travel.

Note: As far as I know only 1 person has said this so far.

Yes, only one reported incidence of this so far

When it's live we can add it...?


create-react-app failing

If you are reporting a bug, please fill in below. Otherwise feel free to remove this template entirely.
Can you reproduce the problem with latest npm?
Many errors, especially related to "missing modules", are due to npm bugs.
If you're using Windows, follow these instructions to update npm.
If you're using OS X or Linux, run this to update npm:
npm install -g npm@latest

cd your_project_directory
rm -rf node_modules
npm install

Then try to reproduce the issue again.
Can you still reproduce it?
Yes
Description
I am trying to use create-react-app to create a react app using command create-react-app work.  My OS is Windows 7 64 bit, npm version is 4.5.0, node version is v7.8.0, I tried with earlier npm and node versions as well and still unable to use create-react-app
What are you reporting?
Expected behavior
The command above should be able to create react app.
Tell us what you think should happen.
Actual behavior
Tell us what actually happens.
It aborts with following messages.
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\react-scripts\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
Aborting installation.
npm install --save --save-exact react react-dom react-scripts has failed.
Deleting generated file... node_modules
Deleting generated file... package.json
Deleting work/ from C:\anil\business
Done.
Environment
Windows 7 64 bit
Run these commands in the project folder and fill in their results:

npm ls react-scripts (if you haven’t ejected):
C:\anil\business
`-- (empty)

node -v:
v7.8.0

npm -v:
4.5.0

Then, specify:

Operating system:
Windows
Browser and version:
NA

Reproducible Demo
Please take the time to create a new app that reproduces the issue.
Alternatively, you could copy your app that experiences the problem and start removing things until you’re left with the minimal reproducible demo.
(Accidentally, you might get to the root of your problem during that process.)
log.txt
Push to GitHub and paste the link here.
By doing this, you're helping the Create React App contributors a big time!
Demonstrable issues gets fixed faster.

Can you post output of create-react-app --version?

1.3.0

We made a mistake of deleting npm log files so we can't really tell what happened 😞
I think we should remove *.log files from this line and instead add them here. This way you'll have the log file remaining in the folder that would tell us what went wrong.
Can you try to do these changes to your local create-react-app (run which create-react-app to learn where it is) and then post npm-debug.log in the folder?
Sorry for the trouble.

I did the above changes and could not see any files generated. Looks like I have to finally learn webpack :(

Well, the issue is clearly with npm. Can you run
mkdir test
cd test
npm i react-scripts react react-dom

and post the output? I'd assume it would also fail.

I ran the above commands and did not see any error. A folder called node_modules was created with various modules and a .bin folder. I got the following warnings, but overall the operation was successful
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\react-scripts\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN enoent ENOENT: no such file or directory, open 'C:\anil\business\gargi\test\package.json'
npm WARN test No description
npm WARN test No repository field.
npm WARN test No README data
npm WARN test No license field.

Okay, thanks for trying.
Can you put a console.log before this line?
    child.on('close', function(code) {
      console.log(code); // <--- add this
      if (code !== 0) {
        reject({
          command: command + ' ' + args.join(' ')
        });
        return;
      }
      resolve();
    });

and try again?

Actually can I ask you to run create-react-app qwerty --verbose? I forgot we have this flag.
Then could you paste the output in a gist and link it from here.

@anilpank I guess issue is with fsevents, I have encountered same problem in windows while working on different package.
https://github.com/gulpjs/gulp/issues/1810

I have the exact same problem =(

I guess issue is with fsevents, I have encountered same problem in windows while working on different package.

It’s not an issue though. npm warns about an optional dependency, but it should not cause any errors. We have a continuous integration test that runs on Windows, and it works fine.
If you still have issues please run the command with --verbose flag as I asked earlier, and provide the output. Thanks!

I have the same problem. How can I fix this? node -v 7.10.0 npm -v 4.2.0

@SeducerStar based on this
npm ERR! EPROTO: protocol error, symlink '../acorn/bin/acorn' -> '/app/my-react/node_modules/.bin/acorn'

npm fails to create a symlink for acorn. Do you run create-react-app in a linux vm for a shared folder in a windows host?

@viankakrisna
yes! I use docker.

yeah there's an issue with symlink and shared folder if your host is windows. I'm not aware any solution for this, so instead i just install and run node / npm / cra from the host machine.
I don't know if this issue also exists in linux / macOS though, because of the windows experience when i'm switching to mac i just install node and npm on the host machine.

@gaearon

can I ask you to run create-react-app qwerty --verbose?

create-react-app verbose exit code 1.txt

I have the same issue. What is interesting, sometimes it completes successfully (especially when running with --verbose flag). node-gyp and fs-events are always pain.

There is a new fs-events release that might fix the issue on Windows. Let's see when create-react-app will use this: https://github.com/strongloop/fsevents/releases/tag/v1.1.2

I am having the same issue with fsevents! But for me it never works even with --verbose.
Running on Windows 10<EMAIL_ADDRESS><EMAIL_ADDRESS>Does anyone has a solution for that?

npm 5.x is very buggy at this moment. Please revert to npm 4.x in the meantime.

G:\GURU\WORK-BENCH\PROJECTS\ReactJS>create-react-app --version
1.4.3
G:\GURU\WORK-BENCH\PROJECTS\ReactJS>create-react-app my-app
Creating a new React app in G:\GURU\WORK-BENCH\PROJECTS\ReactJS\my-app.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts...
npm ERR! Unexpected end of JSON input while parsing near '...lugin-flowtype","dist'
npm ERR!      C:\Users\Bharat Moger\AppData\Roaming\npm-cache_logs\2017-12-29T10_13_00_967Z-debug.log
Aborting installation.
npm install --save --save-exact --loglevel error react react-dom react-scripts has failed.
Deleting generated file... package.json
Deleting my-app / from G:\GURU\WORK-BENCH\PROJECTS\ReactJS
Done.

@guru9
I think I had the same problem. I did this command line
npm i -g npm@latest
and then
create-react-app my-app
worked.

I had the same problem running on Virtual Linux Machine.  The host ran out of memory.  Bumped up the RAM and it worked.

use create-react-app projectname  --save
or  create-react-app projectname  --save-exact and start again

I switched to next.js and my problem is solved now.


AutoFill on page load

AutoFill upon page load is a feature of ChomeIPass:

Automatically fill-in single credentials entry.
If chromeIPass does only receive a single entry from KeePassHttp it automatically fills this credentials into the found credential fields.

It would be good to replicate that functionality in CKP.

Upvote!

I dislike this idea.
CKP uses a less dependable ranking algorithm for suggesting entries to fill.  Depending on how you've named your entries, whether or not you supply full URLs, etc. CKP might suggest credentials that don't really belong to the site you're on.  I like this because I (like the majority of users) don't always name my entries perfectly or supply the exact right url, so CKP's best guess usually finds what I need.
False positives, combined with some malicious intent (like accidentally landing on a PayPal spoof site that AJAX's it's username and password fields) would roughly equate to CKP helping you automate the process of having your passwords stolen.

@subdavis the fact that the feature does not fits your personal needs, does not mean many other users could actually like this features a lot. If it is an option inside CKP, which you could turn on or off, it would not bother users like u.
In terms of mistakes, the recognition of the website could be done solely using the main domain name of the website. If you don't use the correct URL's than it's your personal problem. I believe most of the users do. If the user himself don't register a fake (phishing) url than CKP would never commit a mistake, it would actually save us in case we end up in a phishing URL.

Finally I would like to add one extra idea to this "Issue" conversation. Instead of a AutoFill feature, an option to AutoFill could be added to the "Right-click Menu" like this CKP would only AutoFill if the users asks to.

@pedrosimao thanks for your reply.
My issue with this feature is not so much of a reflection of my personal needs, but rather a fundamental security vulnerability surrounding the idea as it was originally proposed.
I am fairly confident in my original assumption that the majority of users do not supply URLs in every case.  Most of them are likely not security conscious.
I see no problem with basing the auto-auto-fill solely on a 100% perfect domain match.  In that case, I worry more about possibly confusing users who don't know how everything works.
Imagine a user who says:

I don't understand why on facebook.com, my username and password always magically fill themselves, but on reddit, I have to open the menu and fill them myself.  This extension is frustrating and complicated..."

Your suggested change of adding a right click option, on it's face, seems less problematic.  You've already got a separate issue open for that in #154, so discussion about that is probably better directed to that page.
My goal was not to smite the idea, but rather to address possible negative repercussions of the feature.  You're welcome to submit a pull request, but this isn't a feature I'm interested in adding myself.

@subdavis I understand your comments. I myself don't have the time to implement such a function, as I have only basic experience with javascript. It could be a good opportunity to learn more about Node and so on. But I am currently finishing other paid projects with mobile apps, which I do have experience with. Maybe in the future I will have the time. I really like CKP and I am not willing to go back to some paid / closed source alternative. But I do miss the time when I used PasswordBox, and everything was auto-filled automatically. Also PasswordBox would always suggest me to automatically add new passwords to the database when I login in a site that is not already in my db. Having to add all passwords to KeePass manually is a bit tedious. But this would be a third issue. Do you know if someone is currently working on it? (auto-saving passwords to the DB)

No, CKP currently has read-only access.
Adding new entries is the oldest active issue on this extension, #9.  Nobody is working on it and it doesn't look like that will be a feature any time soon.


Problems with external domains

Hi,
We are using your library to swap between normal and Retina images.
But, our users uploads their images to an external domain, and it causes a problem to us, because on Retina.js you created this function:
RetinaImagePath.prototype.is_external = function() {
  return !!(this.path.match(/^https?\:/i) && !this.path.match('//' + document.domain) );
};

Why did you choose to don't swap the image src when the image is on a external domain?
Thanks

I also have the problem when using retina.js with external CDN source. Probable it the same problem.

Temporarily, we included retina.js directly on our project, and withdrew this function, because we did not understand its reason. =(

There might be a reason for excluding external sources:

Browsers will not load images from external serves as long as there is no CORS configuration on the external server

You can patch retina.js like this to load images from you own external domain:

RetinaImagePath.prototype.is_external = function() {
// mod: do not return false if domain is .mydomain.com
return !!(!this.path.match(/^(https?:(.)mydomain.com|//)/i) && !this.path.match('//' + document.domain));
};

But need to add correct CORS header to your server config as well. For nginx add this to your server {} section:

allow do to load retina images via CORS by retina.js

add_header 'Access-Control-Allow-Origin' "https://www.mydomain.com";


Fix build error on ubuntu

Fix #380
Changes:

Add LLVM as a submodule

It looks like there's a regression with MacOS in the linkage stage, so I'm going to open an issue and merge this PR because it's starting to go off topic.


Feedback regarding lesson: Abstractions 1

It's very difficult to understand the distinction between the different kinds of abstraction made in this lesson. I'm not sure what to suggest, but it's not at all clear which one to pick in each situation (other than for direct quotes, that's clear enough). In general "as an event" and "as a predicate" are not meaningful distinctions to me at this stage. Maybe expand on that?
Context
For context, this feedback refers to the lesson "Abstractions 1" in the course "Getting started with Lojban (alpha)".

Thank you! I really appreciate the feedback.
Based on discussion here and on #ckule, it seems that many other students are having difficulty with this part of the lessons. I will think carefully about how to better explain the distinction between "nu" and "du'u" and then update the lesson accordingly. This might take some time. I will also check if more experienced Lojbanists have suggestions on how to improve this.
Meanwhile, to unblock your studies, I suggest reading about abstractions from the UnCLL Chapter 11.

I too had a similar difficulty regarding abstractions. I would be willing to help in any way I can.

Thank you, Ethan! Any help would be appreciated :)
Feel free to propose improvements here or even submit a PR changing the lesson.

Consider the following example:
{mi djuno lo nu gleki lo mlatu} versus {mi djuno lo du'u gleki lo mlatu}
The first example states, "I know the event of me liking cats". That doesn't sound right. Taken from UnCLL Chapter 11.7:

Events are actually or potentially physical, and can't be contained inside one's mind, except for events of thinking, feeling, and the like...

Perhaps it would be beneficial to note that "nu" represents a physical event that can/may occur in real life, and because of this, cannot be restricted to the mind.
Thus, we need another abstraction to make claims about the world that aren't physical. The second part of the example means, "I know the predication that I like cats". Significantly better. Using words like "knowing, believing, learning, seeing, and hearing" restricts an event to the mind and requires {du'u} to represent the abstraction.
Next time, ask yourself, Does the selbri represent a physical event or a mental event?
I may be going off on a tangent here, but predication can be split into two separate categories: ontological (where predicates pertain to things) and logical (where predicates are something that is said of things). Hence, ontological predication may be {lo nu}, while logical predication may be {lo du'u}.

If the above comment has helped @xoltar I would love to submit a pull request (assuming my statements are accurate).

After asking #ckule for clarification on the issue, {nu} designates a spatio-temporal event; {du’u} designates a raw proposition:
du'u
Unlike my previous conclusion, {du'u} represents a "proposition of".
Proposition: claim that is either true or false
Example: {mi djuno lo du'u do ctuca mi} or "I know that you taught me"
The second place of {djuno} is always a true proposition because the knower regards their facts as true. This can be easily explained with:
I | know | the proposition of | you teaching me (is true)
It would make no sense to have {mi djuno lo nu do ctuca mi} because no one can know an event. It is a mess semantically.
nu
{nu} represents an "event of".
Event: Something that happens, whether it happens or could happen physically and/or spatially
Example: {do nupre lo nu dunda lo mlatu} or "You promised to donate the cat."
Someone promises to do a physical and/or spacial event. This can be explained with:
You | promise | the event of | donating the cat
Of course, you would promise an event instead of a proposition.

Thank you!
That sounds great, please feel free to submit a pull request :)

Will do. ETA 5:00 UTC

I just submitted a PR. I can also include flash cards if it is helpful.

@xoltar has this helped with your understanding of abstractions?

@emorchy I think the distinction between "nu" and "du'u" is much clearer now, very nice revision.

Indeed, the lesson is much clearer now :)
I am closing this issue, but anyone please feel free to open a new open if they believe the lesson is still confusing.
Thanks again @emorchy!


Make circuit breaker more modular

Description
Overall goal of this PR is to make our Circuit Breaker more modular. With that, it refactors the CircuitBreaker to avoid singleton pattern and use injection. This will make testing easier as the project scales.
Additionally, it groups circuit breaker related functionality into single service. This will give components one centralized place to interact with the circuit breaker. Along with this, it migrates some of the utility functions away from the KNNSettings.
Lastly, rename the circuit breaker from KNNCircuitBreaker to NativeMemoryCircuit breaker to be more descriptive. Related to this, move the NativeMemoryCircuitBreaker into the memory package in its own sub package.
Additionally, this PR adds unit test tests for the NativeMemoryCircuitBreakerService.
Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #774 (31243ae) into main (78c4f65) will decrease coverage by 0.08%.
The diff coverage is 85.56%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main     #774      +/-   ##
============================================
- Coverage     85.40%   85.32%   -0.08%
+ Complexity     1084     1080       -4
============================================
  Files           151      151
  Lines          4370     4395      +25
  Branches        390      394       +4
============================================
+ Hits           3732     3750      +18
- Misses          463      466       +3
- Partials        175      179       +4

Impacted Files
Coverage Δ

...ain/java/org/opensearch/knn/index/KNNSettings.java
86.17% <66.66%> (-0.54%)
:arrow_down:

...ory/breaker/NativeMemoryCircuitBreakerService.java
75.92% <75.92%> (ø)

...nsearch/knn/index/mapper/KNNVectorFieldMapper.java
84.33% <100.00%> (+0.52%)
:arrow_up:

...opensearch/knn/index/mapper/LegacyFieldMapper.java
100.00% <100.00%> (ø)

...opensearch/knn/index/mapper/LuceneFieldMapper.java
75.00% <100.00%> (+0.58%)
:arrow_up:

...opensearch/knn/index/mapper/MethodFieldMapper.java
85.71% <100.00%> (ø)

.../opensearch/knn/index/mapper/ModelFieldMapper.java
71.42% <100.00%> (ø)

...rch/knn/index/memory/NativeMemoryCacheManager.java
96.06% <100.00%> (+0.86%)
:arrow_up:

...main/java/org/opensearch/knn/plugin/KNNPlugin.java
100.00% <100.00%> (ø)

...java/org/opensearch/knn/plugin/stats/KNNStats.java
100.00% <100.00%> (ø)

... and 6 more

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

@navneet1v  I refactored the NativeMemoryCircuitBreakerService into 2 classes: NativeMemoryCircuitBreaker and NativeMemoryCircuitBreakerMonitor. This resolves the circular dependency issue.
I left out 2 changes that I think we will want to do eventually:

Make settings update call synchronous
Move the Circuit breaker setting definition out of KNNSettings and into NativeMemoryCircuitBreaker

I decided to leave these 2 out to keep this PR simple. I will take them up in a future PR.

Closing for now. Might come back to this later.


no-file-name-articles: forbid "teh"

It is sometimes used as an alternative to "the", so no-file-name-articles rule should probably also forbid it when forbidding "the".
Wiki reference: https://en.wikipedia.org/wiki/Teh.
:wink:

Awesome, I’m 👍 with that.
Could you add a test though? They’re embedded in each rule, so I’m looking for something like this.

@ChALkeR Oh and thanks for your first PR to a remark-related project ❤


refactor(app):  Replaced Flex tag by Banner component

Overview
Fix #9998

Changelog

Added Banner to U2E Adapter Information section
Replaced Text by StyledText
fixed typo of one setting name

Review requests

Risk assessment
low

This looks good to me 👍 . My PR #9997 changes the interface to Banner by using children instead of the now overloaded title prop. If that interface works for you, you'll have a quick conflict to fix up before merging this one in.

Sounds good and using children instead of title makes more sense to me.

[ ] update Banner code after #9997


type of 'bypass_session_save_file_types' unclear

The README.md says boolean: https://github.com/rmagatti/auto-session/blob/da03666a61af32eb0f57b37f18c020a3a33a44d4/README.md?plain=1#L137
doc/autosession.txt says string: https://github.com/rmagatti/auto-session/blob/da03666a61af32eb0f57b37f18c020a3a33a44d4/doc/auto-session.txt#L22
But the code is a table?
https://github.com/rmagatti/auto-session/blob/da03666a61af32eb0f57b37f18c020a3a33a44d4/lua/auto-session.lua#L197
I can make a PR to update, but figured I'd ask to confirm.

You're right 🤦 probably a result of many updates over time and a bit of a lack of attention on my part, PR with fix incoming 👍


Refactored by Codermar. Corrected issues with minification and strict DI

Refactored by Codermar. Corrected issues with minification and strict DI. Unit test for the original file did not actually run. The code is essentially the same. I just added explicit injection and just code styled it.

There are no issues with minification. I provided a minified file if you don't have the ability to add the annotations at build time yourself.
So beyond that, can you explain what these changes are attempting to do?

Looks a lot like https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md
(...which is a good thing)

Yes, I did code styled it based on those guidelines. I added explicit injection so we don't have to rely on running ngAnnotate on it. When I was minifying my app I was running into the error "is not using explicit annotation and cannot be invoked in strict mode" https://docs.angularjs.org/error/$injector/strictdi. It's running fine now with my changes.

@Schlogen there seems to be quite a difference between different projects; some prefer handing injecting dependencies manually and some use ngAnnotate (esp. when their projects grow bigger).
I guess simple having them added like they're added in this PR would be a simple handout for those people not using ngAnnotate, and it doesn't really hurt to have them there.
Also ngAnnotate is trying to guess where to inject stuff, but without explicit /* @ngInject */ it's gonna be just a guess. Perhaps you should add those to guide it, at least?

@simison It is true there are differences. That is why I included a minified version so it will work regardless of the setup. In my opinion, it hurts readability. It is also adds slightly more work while adding features/functionality. It isn't code, it's extra fluff that serves no purpose.

Also, ngAnnotate is trying to guess where to inject stuff, but without explicit /* @ngInject */ it's gonna be just a guess.

That is simply not true. I've used several annotation preprocessors and they have all worked in the vast majority of cases without the use of explicit /* @ngInject */

@Codermar Thank you for contributing to this project. In order to meet your needs of using strict DI, I would advise you add an annotation preprocessor to your build, or use the minifed version of the module. I appreciate your contributions in the area of code styling, however that is a purely subjective matter and it is my opinion that the way the code was styled previously is easier for me to read and understand. If you wish to contribute in the future, feel free to open an issue to discuss the changes before you spend time making changes.

I use an annotation preprocessor but it is my opinion that a public library should not need it, especially if you have a clear way to avoid it like explicit injection.


Replace asserts with appropriate error types

Asserts don't always run, don't fit well with other python code, and aren't informative.

I had always preferred assertions because of test coverage, but you're right, it's bad practice. I'll fix that and throw proper meshio errors.

Great! Happy to help out if it'd be useful.


feat(workerd): use new transport

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#144  👈
#140
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @hi-ogawa and the rest of your teammates on  Graphite


Add new workshops and update aws logo to CED page

Fixes: https://github.com/pulumi/pulumi-hugo/issues/2065

Thanks Zack!


Make ExpandablePageLayout#pullToCollapseInterceptor nullable

This should make it easier for library users to unregister the interceptor if needed.

@zacsweers do you want to test this branch with CatchUp or will a snapshot build be easier for you?

Snapshot would be easier, but this change is also trivial enough on its own
that I think it's safe from eyeballing it alone 👍
On Tue, Jul 23, 2019 at 8:35 PM Saket Narayan<EMAIL_ADDRESS>wrote:

@ZacSweers https://github.com/ZacSweers do you want to test this branch
with CatchUp or will a snapshot build be easier for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/saket/InboxRecyclerView/pull/29?email_source=notifications&email_token=AAKMJPXYBIT6GUDKDORROETQA6IV5A5CNFSM4IGKW4A2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2UXGHA#issuecomment-514421532,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKMJPWOU44MYWJA3GWYL5LQA6IV5ANCNFSM4IGKW4AQ
.

@ZacSweers done!
https://github.com/saket/InboxRecyclerView/releases/tag/v1.0.0-rc2


OpenRoberta/openroberta-lab#1171: removes hide attribute when port isn't hidden

This PR fixes the OpenRoberta/openroberta-lab#1171 issue.
Error
Sensor with hidden port is selected -> hide attribute is added to the block
Sensor with no hidden port is selected -> hide attribute is still present and overwrites the correct sensor port with the previous one
Fix
When a sensor with no hidden port is selected, it checks if the hide attribute is present. If yes: It will be removed

Merged with https://github.com/OpenRoberta/blockly/commit/45c54f951ce84313dcc260296e28bf2202e335b8


[Feature] Headless browser (chrome/chromium/firefox)

I'd love if I could add a headless browser to my dev container using the dev container features.
"features": {
  "headless-chrome": "latest",
  "headless-chromium": "latest",
  "headless-firefox": "latest",
}

All (that I know) JS/TS testing frameworks need it. Manually adding it without having to resort to --no-sandbox is very complicated. I have yet to succeed at it 😞
--no-sandbox is considered insecure and strongly discouraged.

I agree, this sounds like an awesome Feature to add!
Not exactly the same as what you're looking for, but want to point you to the existing desktop-lite Feature, that spins up a basic desktop environment that one can connect to via VNC. (https://github.com/devcontainers/features/tree/main/src/desktop-lite)
I'm not sure if this is something that would interest you in implementing, but we have starter code for self-authoring Features
https://github.com/devcontainers/feature-template
Useful Feature collections can then be registered via PR and will appear in our tooling for the rest of the community to enjoy (see some existing community Features at the bottom of this list 😃 https://containers.dev/features)

@joshspicer thanks for the links. I gave it a shot. But it seems there's an issue with running the tests. Not sure what is going on.
https://github.com/snebjorn/devcontainer-feature/actions/runs/3193079539/jobs/5211272135
When running locally I get this error:
root ➜ /workspaces/devcontainer-feature (main ✗) $ devcontainer features test --features chromium --base-image mcr.microsoft.com/devcontainers/base:ubuntu .

┌ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ┐
|    dev container 'features' |
│           v0.19.0           │
└ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ┘

>  baseImage:         mcr.microsoft.com/devcontainers/base:ubuntu
>  Target Folder:     /workspaces/devcontainer-feature
>  features:          chromium
>  workspaceFolder:   /tmp/devcontainercli/container-features-test/1665008951184

⏳ Building test container...

[1 ms] @devcontainers/cli 0.19.0. Node.js v18.9.1. linux <IP_ADDRESS>-microsoft-standard-WSL2 x64.
[518 ms] Start: Run: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.19.0-1665008951744 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/base:ubuntu --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-1665008951184-78f48eade62e871b44e50fb7260d24e9-features -f /tmp/devcontainercli-root/container-features/0.19.0-1665008951744/Dockerfile.extended /tmp/devcontainercli-root/empty-folder
[+] Building 16.8s (10/12)
[+] Building 17.0s (11/12)
 => [internal] load build definition from Dockerfile.extended              0.1s
[+] Building 17.1s (11/12)
 => [internal] load build definition from Dockerfile.extended              0.1s
[+] Building 17.3s (11/12)
 => [internal] load build definition from Dockerfile.extended              0.1s
[+] Building 17.4s (11/12)
 => [internal] load build definition from Dockerfile.extended              0.1s
 => => transferring dockerfile: 550B                                       0.0s
 => [internal] load .dockerignore                                          0.1s
 => => transferring context: 2B                                            0.0s
 => resolve image config for docker.io/docker/dockerfile:1.4              16.0s
 => CACHED docker-image://docker.io/docker/dockerfile:1.4@sha256:9ba7531b  0.0s
 => [internal] load .dockerignore                                          0.0s
[+] Building 17.5s (12/12) FINISHED
 => [internal] load build definition from Dockerfile.extended              0.1s
 => => transferring dockerfile: 550B                                       0.0s
 => [internal] load .dockerignore                                          0.1s
 => => transferring context: 2B                                            0.0s
 => resolve image config for docker.io/docker/dockerfile:1.4              16.0s
 => CACHED docker-image://docker.io/docker/dockerfile:1.4@sha256:9ba7531b  0.0s
 => [internal] load .dockerignore                                          0.0s
 => [internal] load build definition from Dockerfile.extended              0.0s
 => [internal] load metadata for mcr.microsoft.com/devcontainers/base:ubu  0.2s
 => [context dev_containers_feature_content_source] load .dockerignore     0.1s
 => => transferring dev_containers_feature_content_source: 2B              0.0s
 => [context dev_containers_feature_content_source] load from client       0.1s
 => => transferring dev_containers_feature_content_source: 20.01kB         0.0s
 => CACHED [dev_containers_target_stage 1/3] FROM mcr.microsoft.com/devco  0.0s
 => [dev_containers_target_stage 2/3] COPY --from=dev_containers_feature_  0.1s
 => ERROR [dev_containers_target_stage 3/3] RUN cd /tmp/build-features/ch  0.6s
------
 > [dev_containers_target_stage 3/3] RUN cd /tmp/build-features/chromium_1 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh:
#0 0.496 ===========================================================================
#0 0.496 Feature       : ./chromium
#0 0.496 Description   : Chromium
#0 0.496 Id            : Unknown
#0 0.496 Version       : 1.0.0
#0 0.496 Documentation :
#0 0.496 Options       :
#0 0.496
#0 0.496 ===========================================================================
#0 0.506 ./devcontainer-features-install.sh: 26: ./install.sh: not found
#0 0.506 ERROR: Feature "./chromium" (Unknown) failed to install!
------
ERROR: failed to solve: executor failed running [/bin/sh -c cd /tmp/build-features/chromium_1 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh]: exit code: 127
[-] Failed to launch container:

Command failed: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.19.0-1665008951744 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/base:ubuntu --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-1665008951184-78f48eade62e871b44e50fb7260d24e9-features -f /tmp/devcontainercli-root/container-features/0.19.0-1665008951744/Dockerfile.extended /tmp/devcontainercli-root/empty-folder

Also where is the docs for dev-container-features-test-lib?

I'm not sure about the local test execution, but the one in the action shows the following error: https://github.com/snebjorn/devcontainer-feature/actions/runs/3193079539/jobs/5211272135#step:4:151
./install.sh: 15: Bad substitution
That maps to this line in the install script: https://github.com/snebjorn/devcontainer-feature/blob/main/src/chromium/install.sh#L15, so I think the $PATH substitution is not working properly in the script.

I copied the script from here https://github.com/devcontainers/features/blob/main/src/dotnet/install.sh#L33-L64
Does it not work or do I need to something to make it work?

Hi @snebjorn, were you able to fix the test? Happy to take a look.

Hi @samruddhikhandale I don't recall what was the error when running the test on github.
But running it locally still doesn't work.
vscode ➜ /workspaces/devcontainer-feature (main) $ devcontainer features test --features chromium --base-image mcr.microsoft.com/devcontainers/base:ubuntu .

┌ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ┐
|    dev container 'features' |
│           v0.23.2           │
└ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ┘

>  baseImage:         mcr.microsoft.com/devcontainers/base:ubuntu
>  Target Folder:     /workspaces/devcontainer-feature
>  features:          chromium
>  workspaceFolder:   /tmp/devcontainercli/container-features-test/1667775773667

⏳ Building test container...

[1 ms] @devcontainers/cli 0.23.2. Node.js v18.10.0. linux <IP_ADDRESS>-microsoft-standard-WSL2 x64.
[535 ms] Start: Run: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-vscode/container-features/0.23.2-1667775774241 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/base:ubuntu --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-1667775773667-83cc0998fc3c2516bd20909e8508216e-features -f /tmp/devcontainercli-vscode/container-features/0.23.2-1667775774241/Dockerfile.extended /tmp/devcontainercli-vscode/empty-folder
[+] Building 11.5s (13/15)
 => [internal] load build definition from Dockerfile.extended              0.1s
 => => transferring dockerfile: 1.02kB                                     0.0s
 => [internal] load .dockerignore                                          0.1s
 => => transferring context: 2B                                            0.0s
[+] Building 11.7s (13/15)
 => [internal] load build definition from Dockerfile.extended              0.1s
 => => transferring dockerfile: 1.02kB                                     0.0s
 => [internal] load .dockerignore                                          0.1s
 => => transferring context: 2B                                            0.0s
[+] Building 11.8s (13/15)
 => [internal] load build definition from Dockerfile.extended              0.1s
 => => transferring dockerfile: 1.02kB                                     0.0s
 => [internal] load .dockerignore                                          0.1s
 => => transferring context: 2B                                            0.0s
[+] Building 11.9s (14/15)
 => [internal] load build definition from Dockerfile.extended              0.1s
 => => transferring dockerfile: 1.02kB                                     0.0s
 => [internal] load .dockerignore                                          0.1s
 => => transferring context: 2B                                            0.0s
[+] Building 11.9s (14/15)
 => [internal] load build definition from Dockerfile.extended              0.1s
 => => transferring dockerfile: 1.02kB                                     0.0s
 => [internal] load .dockerignore                                          0.1s
 => => transferring context: 2B                                            0.0s
 => resolve image config for docker.io/docker/dockerfile:1.4              10.5s
 => CACHED docker-image://docker.io/docker/dockerfile:1.4@sha256:9ba7531b  0.0s
 => [internal] load build definition from Dockerfile.extended              0.0s
 => [internal] load .dockerignore                                          0.0s
 => [internal] load metadata for mcr.microsoft.com/devcontainers/base:ubu  0.9s
 => [context dev_containers_feature_content_source] load .dockerignore     0.1s
 => => transferring dev_containers_feature_content_source: 2B              0.0s
 => [context dev_containers_feature_content_source] load from client       0.1s
 => => transferring dev_containers_feature_content_source: 22.08kB         0.0s
 => [dev_containers_feature_content_normalize 1/3] FROM mcr.microsoft.com  0.0s
 => CACHED [dev_containers_feature_content_normalize 2/3] COPY --from=dev  0.0s
 => CACHED [dev_containers_feature_content_normalize 3/3] RUN chmod -R 07  0.0s
 => CACHED [dev_containers_target_stage 2/4] COPY --from=dev_containers_f  0.0s
 => CACHED [dev_containers_target_stage 3/4] RUN echo "_CONTAINER_USER_HO  0.0s
 => ERROR [dev_containers_target_stage 4/4] RUN cd /tmp/build-features/ch  0.5s
------
 > [dev_containers_target_stage 4/4] RUN cd /tmp/build-features/chromium_1 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh:
#0 0.427 ===========================================================================
#0 0.427 Feature       : ./chromium
#0 0.427 Description   : Chromium
#0 0.427 Id            : Unknown
#0 0.427 Version       : 1.0.0
#0 0.427 Documentation :
#0 0.427 Options       :
#0 0.427
#0 0.427 ===========================================================================
#0 0.437 ./devcontainer-features-install.sh: 27: ./install.sh: not found
#0 0.438 ERROR: Feature "./chromium" (Unknown) failed to install!
------
ERROR: failed to solve: executor failed running [/bin/sh -c cd /tmp/build-features/chromium_1 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh]: exit code: 127
[-] Failed to launch container:

Command failed: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-vscode/container-features/0.23.2-1667775774241 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/base:ubuntu --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-1667775773667-83cc0998fc3c2516bd20909e8508216e-features -f /tmp/devcontainercli-vscode/container-features/0.23.2-1667775774241/Dockerfile.extended /tmp/devcontainercli-vscode/empty-folder


[BD-46] fix pathing in the CLI for replacing usage of SCSS variables

Description
Include a description of your changes here, along with a link to any relevant Jira tickets and/or Github issues.
Deploy Preview
Include a direct link to your changes in this PR's deploy preview here (e.g., a specific component page).
Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[ ] Does your change adhere to the documented style conventions?
[ ] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[ ] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @viktorrusakov!
When this pull request is ready, tag your edX technical lead.

:tada: This PR is included in version 22.0.0-alpha.5 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Let shdcn-svelte be used in non typescript projects too.

Describe the feature
Currently shadcn-svelte could only be intialized in projects with typescript. Can this requirement be removed? Thanks.

This isnt true. https://github.com/huntabyte/shadcn-svelte/releases/tag/shadcn-svelte%400.7.0


Publish 0.26.0 on crates.io

Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
crates.io latest version is 0.25.2
https://crates.io/crates/async-stripe

Done. Unfortunately the tool that manages releases crashes frequently before completing the publish step.