fix: Correct data-widgetid

replace data-widgetId with data-widgetid to resolve console warning: act_devtools_backend.js:2655 Warning: React does not recognize the data-widgetId prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase data-widgetid instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Description
Resolves #22301
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual

Test Plan
Start new page
Add container widget
Open browser console
Reload page
Inspect error messages
Issues raised during DP testing
Checklist:
Dev activity

[x ] My code follows the style guidelines of this project
[ x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

Developing a custom widget and seeing all the time, annoying mostly, but
not my code....
On Tue, 18 Apr 2023, 2:26 pm Ashok Kumar M, @.***>
wrote:

@.**** requested changes on this pull request.
In app/client/src/widgets/ContainerWidget/component/index.tsx
https://github.com/appsmithorg/appsmith/pull/22302#discussion_r1169474292
:

@@ -130,7 +130,7 @@ function ContainerComponentWrapper(
? "auto-layout"
: ""
}`}

 data-widgetId={props.widgetId}

 data-widgetid={props.widgetId}

@nzidol https://github.com/nzidol I don't see it used anywhere, lets
remove it and check if the tests run fine.
—
Reply to this email directly, view it on GitHub
https://github.com/appsmithorg/appsmith/pull/22302#pullrequestreview-1389266170,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADH46HPL5XBI3JHHTAYMAJDXBYJXNANCNFSM6AAAAAAW267BRM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Make scanner launch Tor for itself

Merging this closes #77
Note how most of the options in the [tor] section will go away. Your [tor] section in the config will most likely be empty now. @juga0, I highlight you because AFAIK you're the only other person running sbws occasionally.

@juga, fcac281 addresses your suggestion on IRC to move as many torrc options as possible to a global variable.
I looked at using chutney when writing the stuff in tests/testnets/. Here are some of the reasons I didn't go with chutney

It's another dependency
It's harder to control the chutney version the user is using. It's easier to just have the test network generation scripts source-controlled right with the sbws code.
Chutney is complex, especially in the torrc templating. It's complex because it wants to be flexible. I don't need flexible. I just want reproducible. I thought I could implement only the things I need in a couple of scripts and have those scripts be significantly easier to grok than chutney. IMHO, I succeeded. (But I also wrote them, so I'm heavily biased)

@juga0, feel like this is merge ready now?

This branch was already merged.
Re. chutney, realized there isn't doc for testnets (i know i could look code...).
Is it possible right now to connect to the a running Tor (initiated by testnets) to run a unit test?

Re Chutney dependency and versions: in bwscanner it was only being retrieved automatically by travis from git to run tests, so normal installation would not install/make use of chutney.

Is it possible right now to connect to the a running Tor (initiated by testnets) to run a unit test?
sbws scanner first tries to connect to a running Tor.
yeah, i meant unit tests, not the scanner. Rephrasing:
"Is it possible a unit test connect to a running Tor"?
I'm working on figuring out a good way to have the unit tests launch Tor for testing. For example, each test should not necessarily have to launch Tor for itself because that would take a very long time.
Exactly, i said "connect to", and i noted that launching Tor would be slow and not reliable in: https://github.com/pastly/simple-bw-scanner/pull/174/commits/832e33902c0ecc445629a23e743c8d6760cdc435#diff-814ac08b96f7b5924db4cc9038327f11R5

I found this very easy to do with chutney


geting crop transformation to use it for any other image

Hey Dev, i have multiple images of same resolution, i want to crop only one of them and use the same pattern to crop any new image , is there any way i can do that?

Not out-of-the-box but you can look how BitmapUtils.cropBitmap() works.
There is a bunch of code to support the library features which I'm sure you don't need all of them.
I don't think this capability is common enough to be added to the library.
But if you do it a PR is always welcome.


Properly secured but not useful when debugging

I see a lot of improvement in security and gives me a lot of useful information about certificate errors. I like that. However, it has become unusable to me when I use this app for debugging a REST service with certificate not properly configured. I'd like to request a similar option in the chrome browser where you are able to "proceed (unsafe)" when there is certificate problems and continue with the transaction.

Hi,
Thank you for your thoughts.
Please refer to the discussion in crbug (https://bugs.chromium.org/p/chromium/issues/detail?id=603104) where I discussed this issue with Chromium team.
As per referenced discussion I'd be inclined to close this issue as wontfix/wai.

Another REST app that is running as an "app" does not have this issue. This app has been helpful and a preference to me for more than a year now, this issue is preventing me to continue using this app. I will come back to this app once this issue is fixed. Thanks.

@cpoblete if the certificate error is caused by self-signed certificate, you can install it in chrome settings and the app will work as usual.
Any other error means that the certificate is invalid. According to my discussion with Chromium team there will be no fix for apps to allow them to accept invalid certificates. If this is possible you should install valid certificate on your dev server (either self-signed or from free services like letsencrypt.org)

It is fixed by https://github.com/jarrodek/ChromeRestClient/commit/89973b258fe80f0bcc33814111917d6ef272617c

I see the fix. Thanks!


Not the same Issue to install project

when I run pnpm dev
when I open the link to see, in compile moment
Error: Could not find the module "/Users/aimadyahyaoui/Documents/DEV/ReactJS/NextJS#2/nextjs-dashboard/node_modules/.pnpm/next@15.0.0-canary.28_@babel+core@7.24.6_react-dom<EMAIL_ADDRESS>in the React Client Manifest. This is probably a bug in the React Server Components bundler.
at stringify ()

#759 the same pb

I had a similar issue within a vscode devcontainer. It worked on the MacOS machine itself though.

I had a similar issue within a vscode devcontainer. It worked on the MacOS machine itself though.

Ok it could be a problem with my mac...
it work on Windows so..
I have remove all node from my mac and reinstall but still have the issue.
I just have to Reset my mac. Have fun 🙃


List Cell UI Changes

Add an arrow on the right side of the list view to indicate it can be clicked on to open the list. Experiment with putting it left or right of the "update" and "delete" buttons.
Make list name font size bigger (same font size as item names).
Below the name, display the list type ("To-Do" or "Shopping"), followed by a bullet character, followed by the number of items in the list. For example: To-Do • 5 items.

For the count, do not use the quantity.

#15 needs to be completed first.
#40 completes 2 and items count in 3. Currently blocked by a bug (see #40 for details).

Bug in #40 resolved here: Commit: https://github.com/johneastman/todo/commit/d384f261a265f6c3add510e50de7167bfb58e495
However, the item count does not update.

For the list type, I'm hard-coding "Shopping" for now, but that will be changed in #15.

Commit: https://github.com/johneastman/todo/commit/b5a3a8229d19d7876dc638afc2b0cfbd0c616384


Make binaries available as part of releases [Feature]

Thanks for the exporter, super useful now the old alternative was deleted!
Would be great if you could add pre-built binaries for all the supported archs to the Github Releases, making it easier to grab them directly instead of having to grab the source and compile.

@4d62 feels a little rich to call an open source mostly set and forget project "unmaintained" after only a few months of no commits, I have more faith than that, life happens :)

Yeah, not much activity on this as there's not a huge amount to do really without any bug reports. Not sure why goreleaser didn't upload the binaries to the last release properly, but the latest release has them uploaded


Test the multi-plate case of create_cellvoyager_ome_zarr_init

It's been there before, not sure how well tested it is

This has been tested and now works well (see https://github.com/fractal-analytics-platform/fractal-tasks-core/pull/812)


DSL precondition to avoid creating orphan processes - Invalid

PR description
Sanity check to ensure that the non-unique node name (the is being used as a key in a map) does not inadvertently orphan an existing process sharing the same name
Fixed Issue(s)

Messed up the reference test submodule


Form submit at end of TextBoxFor

Is there a way to add the form submit button to the end of the input box using TBSMVC, like in the example below:

I have this so far:
@using (var f = Html.Bootstrap().Begin(new Form()))
{
    @f.FormGroup().TextBoxFor(x => x.SearchTerm).Placeholder("Zip or City").PrependIcon("fa fa-search fa-fw").Label().LabelText("")
}

I want to send the SearchTerm to another View ("SearchResults") when the "Go!" button is clicked.
Apologies for using "issues" so such questions.

Here is an example taken from BMVC Docs:
@(Html.Bootstrap().TextBoxFor(m => m.Amount)
    .Placeholder("amount in dollars")
    .Prepend("$")
    .Append(".00")
    .Append(Html.Bootstrap().Button().Text("Save")))

My goodness... How did I miss that example from the first page of the documentation!!?!?!  Apologies for the oversight Dmitry and many thanks indeed for your rapid response.


Exponents Are Ignored

Some sfz libraries converted from SoundFonts using Sforzando, contain exponents in their opcode values. These exponents are ignored by sfizz, and only the base is read. One such library, is the NS_Kit7 Free Lite drumkit by Douglas Whates. An ampeg_attack opcode used throughout that library is given the value 6.02385e-009. Sfizz reads this as 6.02385 seconds, and very little sound is produced from a drum beat after six seconds.

I'll check it out, thanks for the report !


chore: add rule and test

I noticed that risinglight uses egg for CBO optimization, but it looks violent at the moment. I will try to optimize it.

cc @wangrunji0408 If you have time, could you help me review this PR? Thank you.

@wangrunji0408 PATL，thank you

@wangrunji0408 I would like to ask a question, can egg+sql optimization be extracted into a separate framework and then integrated with calcite? Do you think this is feasible?

can egg+sql optimization be extracted into a separate framework and then integrated with calcite? Do you think this is feasible?

I'm not sure as the Calcite is written in Java while egg is designed for Rust. Besides, what's the purpose of doing this? As far as I know, the Calcite itself is a framework for optimization. I have always thought of egg as a Rust alternative of Calcite.

I'm not sure as the Calcite is written in Java while egg is designed for Rust. Besides, what's the purpose of doing this? As far as I know, the Calcite itself is a framework for optimization. I have always thought of egg as a Rust alternative of Calcite.

I think it is a bit complicated to expand an optimization rule in Calcite at present, and it is not as convenient as egg. My original intention is to make Calcite more convenient to use.


Add ssh_keyfile as an optional argument.

Also change optional_args to default to an empty dict.
This is for issue/FR: #143

I added a couple of comments about fixing the optional_args=None change. Also unit test failures need fixed.
Did you test validate that this change works using SSH keys.
Does Juniper support key authentication and then password authentication (i.e. can you provide both the keys and the username password)? And will it do key authentication first.

Coverage decreased (-0.06%) to 83.898% when pulling 9a2ff79110a78e805b21d11346525162dad5e4a9 on stiltzkin10:feature/junos_ssh_key into ebc02218348c21d8e8beaf46c3f14beff1d556cf on napalm-automation:develop.

Got it. Reverted back to optional_args=None. Thanks!
I have tested this and it works fine on the JUNOS devices I have access to.
To my knowledge the API does not support fall back to username/password.

Okay, I added one more comment about self.port missing at one point. I also think we should make the optional argument be key_file for consistency with the other drivers.

Agree. Updated.

@stiltzkin10 This looks good to me.

Yep, no worries. Thanks!

Coverage decreased (-0.06%) to 83.898% when pulling 7c8d9670774d528dd50283f03968b767a7696c31 on stiltzkin10:feature/junos_ssh_key into ebc02218348c21d8e8beaf46c3f14beff1d556cf on napalm-automation:develop.

Coverage decreased (-0.06%) to 83.898% when pulling 7c8d9670774d528dd50283f03968b767a7696c31 on stiltzkin10:feature/junos_ssh_key into ebc02218348c21d8e8beaf46c3f14beff1d556cf on napalm-automation:develop.

I don't use juniper devices anymore but I could confirm with TestJunOSDriver.py::TestConfigJunOSDriver that this PR works fine. If you have the key in the ssh-agent works as usual and if you don't you can pass the key_file arg. and work as promised.
Thanks! :)

Oh, just one thing. Would you mind updating the optional_args documentation in the napalm docs, please? Once that PR is sent link it here and I will merge both. Thanks again!

Sure, I created napalm-automation/napalm#368. I actually create sub bullets since vyos/junos are slightly different.

Awesome, thanks!


documentation of a significant jq/gojq inconsistency re $-variables in function definitions

jq handles "$-arguments" in function definitions as implicit "as" statements,
whereas gojq does not.  This introduces a source of potential inconsistency.
Consider for example:
def prod: .[0] * .[1];
def prodEqual($p): prod == $p;

This works as expected in both jq and gojq.
However, if prodEq were defined as:
def prodEq($prod): prod == $prod;

then we would see the discrepancy, as jq implicitly expands
the definition of prodEq to
def prodEq($prod): prod as $prod | prod == $prod;

Because of shadowing, in jq, prodEq would therefore always returns true!
For example:
[1,1] | prodEq(0) #=> true using jq
[1,1] | prodEq(0) #=> false using gojq

I know this is a wired behavior of jq, and sometimes causes confusing behavior (https://github.com/stedolan/jq/issues/2039), so fixed in gojq.

@itchyny - I'm a bit confused by your comment.  I was asking that the discrepancy (between gojq's non-weird behavior and jq's weird behavior) be documented as a difference, but as far as I can tell, you've closed the issue without updating the README.
On the other hand, if by "fixed in gojq" you mean you intend to change gojq so that it mimics jq's (weird) behavior, I would have expected the closure of this issue to be linked, as you usually do, to the corresponding commit.
Not that it much matters, I'm fine with the discrepancy, and I'd be fine with gojq tracking jq on this particular discrepancy, but as with all important discrepancies, I'm hoping that it will be clearly documented.   Not least because this particular discrepancy bit me.
Btw, I'm assuming that by "wired" you mean "weird" ....

Sorry, I thought I've written in README before but was not written. And this behavior looks on the edge of jq bad parts and jq bugs. I'm totally knocked down by the weather right now, so judge later.

When I implemented the compiler I thought this behavior is a jq bug, but since the issue is labeled as not a bug by nico, unlikely fixed in the future, and fixing in gojq simplifies the compiler a bit. I decided to fix this to match the behavior of jq, but it has some runtime cost (a value argument requires two local variables, also difficulty in optimizing constant arguments).

@itchyny - Thanks for the elaboration.  I've added some references to gojq on the jq FAQ and would ask you to let me know if you have any suggestions, though of course you're also free to make changes yourself.

On further reflection, it is apparent that the weird behavior of jq
(as illustrated quite nicely by the prodEq example) is actually a bug,
as I will hopefully prove to your satisfaction in a moment. I've also
come to the conclusion that although there is obviously a case to be
made for mimicking some of jq's flaws, in this particular case a
stronger argument for not doing so can be made.
The evidence that it is really a bug is right there in the manual,
where it is explicit that:
 def addvalue($f): ...;                   #1

is short-hand for:
def addvalue(f): f as $f | map(. + $f);   #2

This was the intent all along (I participated in the discussions
leading up to this feature), but unfortunately, the implementation
failed to adhere to this specification -- the point being that in #2,
the shadowing mechanism that is at the heart of jq is operative,
whereas that was lost in the implementation.  QED.
(So the only mystery that remains is why Nico added the "not-a-bug" tag.
I think he either meant:
a) it won't be fixed in version 1.x;
or
b) the intention to achieve the equivalence of #1 and #2 is not a bug.)
Whether it's called a bug or not, jq's current behavior is clearly
undesirable at best, which leads to the question: should gojq
implement the clean/intended/desirable behavior?
My argument in favor of fixing the problem has several facets, but at
its core is the idea that gojq has an extremely useful role to play in
developing jq programs.  Let me illustrate with a recent experience of
mine, when I had a program that I was fairly certain was correct, but
for which jq did not produce the expected results.  So I spent quite a
lot of time verifying that the program was correct, and then further
time checking that I was not overlooking some well-known jq bug.  It
was only when I was able to verify that gojq produced the expected
(correct) result that I was able to track down the source of the
problem.


Add basic auth

Allow adding basic auth to be used when running an OSS instance of airbyte with docker compose

todo: bump version and add tag


delete tileset editor edit button

Godot version:

3.1
followup on #27625
tool_workspacemode[WORKSPACE_EDIT] in https://github.com/godotengine/godot/blob/master/editor/plugins/tile_set_editor_plugin.cpp
Iv'e asked around on the discord and irc, nobody who responded knows what it does. and from what i can see in the source, this button does in fact do nothing.
https://github.com/godotengine/godot/blob/c2c11fc063e723c41579e6307e40fd16ac5334c4/editor/plugins/tile_set_editor_plugin.cpp#L2929
This is where it would actually do something. But it just gets set to pressed. At no point in this file does the button become unpressed. And pressing it just runs code that presses it again.

I answered on IRC to your question. This buttons allows quitting the "New Single Tile", "New Autotile" pr "New Atlas" modes, that's all.

I answered on IRC to your question (Edit: you likely did not see my message). This button allows quitting the "New Single Tile", "New Autotile" or "New Atlas" modes, that's all. :)

That's not really obvious from the name of the button and its lack of tooltip though.

That's not really obvious from the name of the button and its lack of tooltip though.

I completely agree, the UI in this area needs a serious rework.

So after closing the last two issues trying to figure this button out, maybe we should open a new one about what needs to be done, or repurpose and reopen one of them?

maybe we should open a new one about what needs to be done, or repurpose and reopen one of them?

As you want. :)
Or maybe we can add the suggestion to #21384 (and eventually make it a tracker) ? That might make more sense since I feel that there is quite a lot of room for improvements there.

I answered on IRC to your question (Edit: you likely did not see my message). This button allows quitting the "New Single Tile", "New Autotile" or "New Atlas" modes, that's all. :)

@akien-mga
But that is not it's current behaviour. The buttons you describe only create new tiles, they do not change the editors mode. You can edit any type of tile at any time. Looking at the source, the only real effect of the editor button currently, is verifying that everything about the current texture is still in order (it's not been deleted, etc.) and then it immediately turns the button back on. (The function that runs when you press the button, is literally incapable of leaving it unpressed.)
It seems the behavior you describe might have existed during one of the 3.1 betas. But was definitely no longer present in the later alphas.

Yes, the button should not be unpressed by itself, it works like a combobox with the other buttons. So if you click on "new atlas" for example, the edit button gets unpressed and you can create a new atlas tile. If you don't want to create a new atlas tile anymore, you can click the edit button again.

@groud I have followed your use case and can confirm this button does not behave as you describe. Below is a walk-though demonstrating that it does nothing.

Open New Tileset

Add Spritesheet

Click "New Atlas" Button

Select Region (by using cursor)

:warning: Repeatably click on edit button. Observe that nothing happens. :warning:

Select a Different Region (by using cursor)

Click "New Atlas" Button

Select An Additional Region (by using cursor)

Please... I said "If you don't want to create a new atlas tile anymore, you can click the edit button again."

So :

You click on "New single tile" -> Notice the edit button is not pressed anymore, and the "new signle tile is"
You click "Edit" -> Notice the "New single tile" is not pressed anymore, and the "Edit" button is.

Those buttons act as like "tabs", two of them cannot be pressed at once. And yes, once you have selected the region, the "Edit" button become active again since we went back automatically to the "Edit" mode. So in the end, this button looks only useful to cancel the "New [...]" actions.

In that case.
https://streamable.com/lbmxu
Rename the button to Cancel. Move it somewhere more sensible, the top left of editors is historically where you find highly important dropdown menus. (Godot follows this convention elsewhere.) Give it the tooltip: Stop the creation a new tile, and return to edit mode. And make it so the button only appears when you are actually eligible to cancel out of the creation of a new tile.
Btw. You can't actually make multiple tiles while in the "new xtile" "tabs", so the button is barely necessary.

Well, IMHO the UI needs a full rework. We could at least replace what the button do by a right-click anywhere, or a second click on the button could cancel the action instead. That's likely a good short-term solution.
If it's ok with Akien, maybe you could update the issue comment with possible suggestions and we reopen it.

Well then, here my redesign proposal. With descriptive labels and tooltips explaining what each interface is meant to do.
TILESETEDITOR.zip

Well, IMHO the UI needs a full rework.

I agree.  IMO the tileset editor is the weakest feature in Godot.  I'm new to the engine and honestly it was quite the mystery to figure out the editor (thankfully there are some youtube videos out there) so I can see it as a hurdle for a lot of people.  After some time with it I'm able to do most everything I need to do but it can be frustrating at times.


rearrange services page

move ports/protocols to the bottom and addresses to the bottom of the 6 panels, moving posture checks/identity 'above'. then allow the ports/address to flow better. perhaps stack the ports/addresses? UX needs to have boundaries pushed to find ugliness :) super long addresses, 100 addresses on a service, 100 ports on a service

Complete in Commit #6174ea7


Please allow to query for several features at once and show the union result.

Say I use getUserMedia and Data URIs in my application and want to see the percentage of supported browsers with both features available. Currently there is no way to express such a query on http://caniuse.com.
This feature seems to be partly implemented already. When you look for something general with several matches like data, you'll see the stats for each match and a summary at the end of the page for all matches combinded.
It would be very helpful if the website would support a syntax that allows to combine features myself, like: getUserMedia, Data URIs.

While there's no UI for this, it's technically already possible to see this with comma-separated feature IDs, e.g. http://caniuse.com/#feat=stream,datauri

The beta site (https://beta.caniuse.com) now adds UI for this, you can star features to add them to a saved list, which includes a "Feature summary" table with multiple views for the combined support data (including a Union option).
Will close this issue once it's on the main site.

This is now available on the main site.


SetMetadata/SetMetadataAsync do not allow newline characters ('\n')

In Azure Storage Explorer, I can assign a newline character ('\n') to a blob Metadata value without any issues.  However, when I call cloudBlockBlob.SetMetadata() or cloudBlockBlob.SetMetadataAsync() with a value containing the newline character, it fails.
Someone else reproduced the same issue in this SO thread, but the documentation referenced in one of the comments does not exist anymore.
The current documentation indicates that any ASCII characters should work for Metadata values, and a backslash and 'n' would both be considered valid ASCII characters.

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

ID: 84ac5495-fab7-02a9-37d9-dde1e463cb4a
Version Independent ID: 48fc73ee-bb7a-6175-e962-31731b795d31
Content: Set and retrieve object properties and metadata in Azure Storage
Content Source: articles/storage/blobs/storage-properties-metadata.md
Service: storage
GitHub Login: @tamram
Microsoft Alias: tamram

Hi @TracyGH ,
What specific Azure Storage library version are you using when getting this error message ?
The list of Libraries and newest versions can be found here , Let me know if you are using the latest then i'll route it as a doc/product issue.
Thanks,
Adam

@Adam-Smith-MSFT

Thank you, @TracyGH, I have confirmed with the Azure Storage engineering team that this is a bug in the SDK. They are tracking the issue and will address it in a future release. I'll update this issue once it's fixed.
@Adam-Smith-MSFT - FYI.
#please-close

@tamram @Adam-Smith-MSFT Adding metadata using CloudBlockBlob.Metadata.Add also throws exception upon uploading the blob when the value contains any of the following characters:

\r
\n
\r\n

Thanks!

@gojanpaolo - Thank you, I will let the engineering team know.

Was this issue fixed?  Works fine if set from Azure Storage Explorer.

@chrisjshields - Could you please open this issue against the .NET SDK (assuming you're using .NET)?
https://github.com/Azure/azure-sdk-for-net/issues
Thanks!

@chrisjshields @TracyGH @gojanpaolo - I received confirmation from the SDK team that this is by design in the SDK and will not be changed:
Azure Storage Explorer is likely using base64 encoding to substitute out the newline character and replace it on download. The SDK cannot afford to make such assumptions about customer data. The customer can base64 encode their own data if they wish and decode on read.


Fix the unhealthy backend by adding backend config healthcheck.

This was caught in the internal bug http://b/184422201.

https://cloud.google.com/endpoints/docs/openapi/get-started-kubernetes-engine-espv2?hl=en

Trying this on autopilot running 1.18.16-gke.302, the deployment end up with a broken load balancer with unhealthy backend.
After some investigation, this is because the health check configured is sending an HTTP GET / - that returns "404 - The current request is not defined by this API" - as configured.

To fix it you have to modify the health check to send HTTP GET /healthz A possible fix is to add a backend config to the manifest.

@qiwzhang thanks for the quick review.


ugrep: 2.5.3 -> 2.5.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Genivia/ugrep/releases.
meta.description for ugrep is: "Ultra fast grep with interactive query UI"
meta.homepage for ugrep is: "https://github.com/Genivia/ugrep"
meta.changelog for ugrep is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.5.5 with grep in /nix/store/g45izin2llzb3p19mfrlk6b68pvi5pbg-ugrep-2.5.5

directory tree listing: https://gist.github.com/8dc50edc0cf9aacdc4fd1347bf462fbe

du listing: https://gist.github.com/dac82d1ed14021f8da19e3b903dcf1fd

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
ugrep

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/g45izin2llzb3p19mfrlk6b68pvi5pbg-ugrep-2.5.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ugrep https://github.com/r-ryantm/nixpkgs/archive/6f7120772ef869e5c3850b2584fad556e7de21ee.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/g45izin2llzb3p19mfrlk6b68pvi5pbg-ugrep-2.5.5
ls -la /nix/store/g45izin2llzb3p19mfrlk6b68pvi5pbg-ugrep-2.5.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

ugrep

Maintainer pings
cc @numkem for testing.

@GrahamcOfBorg eval


Index on encrypted fields possible?

Is it possible to use encryption on indexed fields, like an email?

This lib encrypts data before it is sent to mongodb. As such, you can add index on encrypted fields, but it doesn't make any sense, as mongodb will see garbage only, and you won't be able to do search on these (that's the idea of encryption, eh :D )
What you can do: store the non-indexed encrypted field normally, and store an indexed hash of the email. When you need to search by the email, hash it again and search on that in the db; if you'd encounter multiple hits, read those from mongo and match the decrypted email to find the document you were looking for.

Thank you for the tip with hashing, works like a charm!

Thanks, I've added a section in the doc to cover this question.


added checked-in builders counter

Description
A simple PR to add the counter for the checked-in builders to the main page.
Additional Information

[x] I have read the contributing docs (if this is your first contribution)
[x] This is not a duplicate of any existing pull request

Related Issues
Closes #6
Note: If your changes are small and straightforward, you may skip the creation of an issue beforehand and remove this section. However, for medium-to-large changes, it is recommended to have an open issue for discussion and approval prior to submitting a pull request.
Your ENS/address:
0xdfaA26eeE0d9Ed0dB940191014872bE40D2F3Ae5

Looks good to me

Thanks and merged!
Pls always remind to attach an image to the description (especially when you are working on a front end task)


How do I select another theme css

I tried to change the theme from default to paper. I saw in the partials that the variable is Site.Params.theme.name.
In settings I tried with
[params]
theme = "paper"
and also
[params]
[theme]
name = "paper"
and my last try:
under [params]
theme.name = "paper"
What is the right combination?
Last test with: theme = "paper.css" under [params]
Error:
ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in theme/partials/base/imports.html ERROR: 2016/02/13 template: theme/partials/base/imports.html:8:69: executing "theme/partials/base/imports.html" at <.Site.Params.theme.n...>: can't evaluate field name in type interface {} in ```

I think you have a bug in the layouts/partial/base/imports.html file:
<link rel="stylesheet" href="{{ "/css/theme/" | absURL }}{{ .Site.Params.theme.name }}.css">

It should be:

Then it is possible to add under:
[partials]
theme = "paper"

@appernetic Did you try? If not, could you try and let me know if it works?
[params.theme]
  name = "cosmo"

I am closing this, feel free to reopen if the issue is not yet resolved

Hi, thanks,
It works! I hadn't got time to test your last suggestion before now.
I have now forked your theme and did small changes in the styles.css so that the right sidebar is not to close to the top menu when using the Paper theme. I also added a lite more space between the bottom and the copyright text.
To have my users understand how it works I also added instructions to the READMe.md file and added a new screenshot.
Other than that my fork will work both in Hugo and Appernetic.io

I aso added so that images is responsive:
img {
  display: block;
  max-width: 100%;
  height: auto;
}

I have also removed .clearfix in the sidebar links, it was not working in Firefox, the link appeared below the dot.


Request for a method to wrap executing @block in Endpoint

Hi, I work on the Elastic APM Ruby agent. We've recently added support for instrumenting Grape apps and it will be released in our next minor version.
Right now, we do not have backtraces for spans with Grape because using caller in our ActiveSupport::Notifications subscriber will not show a backtrace leading to the user's code. It instead shows this (note this isn't the complete backtrace, just the top ~20 lines):
/Users/emily/.rvm/gems/ruby-2.6.2/gems/activesupport-6.0.1/lib/active_support/notifications/fanout.rb:156:in `start'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/activesupport-6.0.1/lib/active_support/notifications/fanout.rb:58:in `block in start'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/activesupport-6.0.1/lib/active_support/notifications/fanout.rb:58:in `each'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/activesupport-6.0.1/lib/active_support/notifications/fanout.rb:58:in `start'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/activesupport-6.0.1/lib/active_support/notifications/instrumenter.rb:36:in `start'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/activesupport-6.0.1/lib/active_support/notifications/instrumenter.rb:22:in `instrument'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/activesupport-6.0.1/lib/active_support/notifications.rb:180:in `instrument'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/grape-1.2.4/lib/grape/endpoint.rb:243:in `run'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/grape-1.2.4/lib/grape/endpoint.rb:318:in `block in build_stack'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/grape-1.2.4/lib/grape/middleware/base.rb:31:in `call!'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/grape-1.2.4/lib/grape/middleware/base.rb:24:in `call'
/Users/emily/Code/apm-agent-ruby/fork/apm-agent-ruby/lib/elastic_apm/middleware.rb:20:in `call'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/grape-1.2.4/lib/grape/middleware/error.rb:37:in `block in call!'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/grape-1.2.4/lib/grape/middleware/error.rb:36:in `catch'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/grape-1.2.4/lib/grape/middleware/error.rb:36:in `call!'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/grape-1.2.4/lib/grape/middleware/base.rb:24:in `call'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/rack-2.0.7/lib/rack/head.rb:12:in `call'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/grape-1.2.4/lib/grape/endpoint.rb:227:in `call!'
/Users/emily/.rvm/gems/ruby-2.6.2/gems/grape-1.2.4/lib/grape/endpoint.rb:221:in `call'

You call the user's code on this line so I'm asking if you can maybe wrap that in another method. That way, we can alias the method, grab the stacktrace with caller, then call the original method.
If you have other ideas on how to expose the stacktrace, we are open to hearing them. Let me know what you'd prefer and I'm happy to open a PR.
Thanks in advance!

I don't see a problem with moving that whole block into a method @estolfo, but since it's not an interface it will be hard to guarantee this moving forward. How do others solve this? NewRelic agent is OSS too. Do you really need the stacktrace - users want to know which API this is I think and it's something you can get from ENV or context.

Hi @dblock, thanks for your response.
New Relic doesn't use ActiveSupport::Notifications (perhaps because they support back to a version before Grape introduced it?). They instead use the alias strategy that we also use for other frameworks. I could be missing it, but it doesn't appear that they take stacktraces either.
We realize the instability of relying on internal gem methods but sometimes it's all we can do = )
One option for us is to get a single-item stacktrace that consists of the source_location from the payload[:endpoint].source. That would be a compromise for us if there is no other way to get to the @block.call(self) line.
What do you think?

One option for us is to get a single-item stacktrace that consists of the source_location from the payload[:endpoint].source. That would be a compromise for us if there is no other way to get to the @block.call(self) line. This is used to show the source code to the user.
What do you think?

I think you should do both this for older versions and PR a change so we can help you with future versions. Also open for something that looks more like an interface with tests so we don't break it moving forward.

Ok, I think what we'll do is:

Have a single-line stacktrace for older versions as proposed above.
Open a PR to move @block.call(self) to its own method so we can overwrite it.
Later, open a PR proposing an interface, as approach (2) is not sustainable.
Let me know if that sounds good. Thanks!

sounds good to me


I dont understand what's happening in the README gif

I am a developer and I dont understand what's happening in the README gif.
Can you please upload another one clearly shows the use case ? Or rather upload one more gif that simply shows the use case of web app automation.

Thanks @mayuroks for your feedback. I see, the gif show the process of recording a series of steps using the Chrome extension, then made a simple edit to wait for few seconds, and finally playing the automation flow. Specifically, the steps are to sign up for accounts automatically in bulk. However, I stop at the submit step in order not to spam the website with garbage accounts.
I have problem going for longer duration for clear video, because the only way to embed video directly on the GitHub repo page is using a GIF. But file size will be huge, for example this one running for a minute takes 25MB. If it is too long, may be costly for some users for their mobile data. If embed using image with link to YouTube, users need to click in order to view the video, that will be very disruptive in reading the README.md.
I will check the video description at the bottom and make it clearer. There is also another example with details under HOW IT WORKS section. Appreciate your feedback and feel free to share your inputs on this issue page or to<EMAIL_ADDRESS>


Task3 done

Issue: #3

Task 3
We want the contents of the folder in the path variable, not the value of  path itself which is trivial.
Also this commit also includes task 2 so fix that too.

@rakim-0  i updated it please review it

LGTM so yeah just fix task 2 and then I can merge this. The way GitHub works is that if the same commit overlap in two PRs then merging one would merge the other one so yeah.


Average and max seem to be switched

They are not :D Just French people that couldn't read English numbers :D


implemented promise.all

There you go -
For issue #7
Now each file is created in parallel.

Thanks for your contribution! Do give this repo a star if you find it useful, so that it can reach out to other developers. :)


adding first iteration of stat_daemon service

@mistercrunch.  It works basically like we discussed (about the same as Airflow.)  I will commit a job definition file and company-specific plugins to our internal repo for separate review.

@artwr removed the s3 plugin for now.  We can add back later.

Closing this out for now, will add it to the new repo in a way we decide is appropriate.

Let's use this as a use case for the plugin architecture I'll write soon.

Sounds good.


aa

Closes #
📑 Description

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

ℹ Additional Information

Deploy preview for jayantgoel001-github-io ready!
✅ Preview
https://jayantgoel001-github-a15nlny4f-jayantgoel001.vercel.app
Built with commit e0fd9115afe45972aadd8313c95381e15e59809e.
This pull request is being automatically deployed with vercel-action

🚦 Running Lighthouse audit...

⏱ Running budget checks...


JobSchedule de-serialization should respect the default initial delay

If you de-serialize JobSchedule from JSON or YAML, and do not provide an initial delay, the resulting instance has a null value for initialDelay, which should never happen. But today it did happen to me when  I was changing some configuration on a service in order to test some things.
This happens because JobSchedule has Lombok annotations on it for @Builder, @NoArgsConstructor and @AllArgsConstructor. Unfortunately, while the no-args constructor and the generated builder code respect the default value for initialDelay, the all-args constructor does not. This is true when there is only an @Builder annotation or whether using @AllArgsConstructor, i.e., the generated constructor looks like:
@java.beans.ConstructorProperties({ "initialDelay", "intervalDelay" })
JobSchedule(Duration initialDelay, Duration intervalDelay) {
    this.initialDelay = initialDelay;
    this.intervalDelay = intervalDelay;
}

Therefore, when a de-serializer (Jackson) de-serializes from JSON or YAML using the all-args constructor, and there is no value specified for initialDelay, it results in a null value.
To make this work one would expect, we unfortunately need to add an all-args constructor which sets a default initialDelay if necessary. And, we need to move the @Builder to this constructor. So inside this constructor, we'll need to do something like:
this.initialDelay = isNull(initialDelay) ? DEFAULT_INITIAL_DELAY : initialDelay;

This negates Lombok's code generation, but it needs to work as you would expect.

I am pretty sure this could also be solved by adding Lombok's @Jacksonized annotation to the class, which clearly would only work with Jackson de-serialization. In this case, only the @Jacksonized annotation needs to be added.
However, @Jacksonized is an experimental Lombok feature, which makes me a bit uneasy using it. (And of course some would say never use Lombok in the first place, but whatever.) So, in addition to the fact that @Jacksonized only works with Jackson, and it is experimental, makes me think we should (for now) just use the explicit constructor.

I suggest using Jacksonized for now. Most of kiwi right now depends on Jackson and it is the cleaner fix with that assumption.

And in addition this is a Dropwizard-specific library so of course it uses Jackson!


🚀 Feature: [Docs] Guide for setting up and using OpenTelemetry metrics and traces

🔖 Feature description
As there are more and more metrics and traces being setup in Backstage it would be really helful to have a guide that shows you how to set up and use OpenTelemetry
🎤 Context
We'd like to use the metrics and traces that have been added but it feels very open as to how one would set things up and start using them
✌ Possible Implementation
This could be as simple as a Contrib guide like the one for Prometheus here: https://github.com/backstage/backstage/blob/master/contrib/docs/tutorials/prometheus-metrics.md
But it would be even better if it was part of the main Documentation under the Tutorials heading here: https://github.com/backstage/backstage/tree/master/docs/tutorials
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

@awanlin thanks for raising this! Yep indeed, we should have docs around this. I'm hoping to also throw together an RFC for a metricsApiRef for plugins to use and promote the use of these OT metrics more, so it's looking like it's going to become pretty useful to have this indeed :tada:

Oh, a metricsApiRef for plugins to use sounds very nice! Would be happy to help just a bit slammed these days

I am very much interested in docs for openTelemetry and a metricsApiRef for plugins 🙂

@awanlin I guess this one should remain open as you requested

Not stale, some updates going on here: https://github.com/backstage/backstage/pull/22648

Fixed!


'glog/logging.h' file not found

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: (4) x64 Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz
      Memory: 6.74 GB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 10.13.0 - /usr/local/bin/node
      Yarn: 1.12.3 - /usr/local/bin/yarn
      npm: 6.4.1 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
    IDEs:
      Xcode: 10.0/10A255 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.3 => 16.6.3
      react-native: 0.58.0-rc.1 => 0.58.0-rc.1
    npmGlobalPackages:
      react-native-cli: 2.0.1

Description
I just tried to create a new project using react-native init<EMAIL_ADDRESS>for testings about this issue but i face this problem! I guess this is a regression!
Reproducible Demo

react-native init MyTestingProject<EMAIL_ADDRESS>cd MyTestingProject/ios
open MyTestingProject.xcodeproj
File / Project Settings... / Build System => Legacy Build System / Done
Product / Clean
Product / Clean Build Folder
Build

Did you try the ole rm -rf ~/.rncache node_modules/react-native/third-party/*?

Did you try the ole rm -rf ~/.rncache node_modules/react-native/third-party/*?

Yep but no result!

I'd prefer to have some repro steps before reopening.

i'm getting the same error in xcode 10.1, i'm trying to upgrade a project from version 57 to 58.5, did anyone fix this ?

I fixed it by deleting the podlock file, sharing here so that it might help someone

Well, i know this is a weird solution but it works!
I edited ../node_modules/react-native/scripts/ios-install-third-party.sh and deleted these lines:
fetch_and_unpack glog-0.3.5.tar.gz https://github.com/google/glog/archive/v0.3.5.tar.gz 61067502c5f9769d111ea1ee3f74e6ddf0a5f9cc "\"$SCRIPTDIR/ios-configure-glog.sh\""
fetch_and_unpack double-conversion-1.1.6.tar.gz https://github.com/google/double-conversion/archive/v1.1.6.tar.gz 1c7d88afde3aaeb97bb652776c627b49e132e8e0
fetch_and_unpack boost_1_63_0.tar.gz https://github.com/react-native-community/boost-for-react-native/releases/download/v1.63.0-0/boost_1_63_0.tar.gz c3f57e1d22a995e608983effbb752b54b6eab741
fetch_and_unpack folly-2<IP_ADDRESS>.tar.gz https://github.com/facebook/folly/archive/v2<IP_ADDRESS>.tar.gz fb8cdf8962d8c9d0c20a150b6ec3b75d1fa50696

then i copied the whole third-party folder from another project which is "react-native": "0.57.7" and its working!
Please consider that i ran ./configure and make in the project of "react-native": "0.57.7" too!
I guess there's a problem in the GitHub files!
@hramos (BTW, Happy New Year 😁 🎉 )

You saved my day!!! Thanks

I have solved this problem today
https://github.com/facebook/react-native/issues/24990#issuecomment-495493250

I have tried all the above solutions.
config.h & loggin.h files are also generated.
But when I run 'react-native run-ios' in the terminal OR when I build the project from Xcode 10.1, config.h file, logging.h file are somehow deleted.
I don't know what's going on.
How are you guys able to solve everything? I am trying every solution that I possible could since many months.
Please help.

@KushalDesai1 I've also encountered this issue and could not get any of the proposed solutions to work. However, I did find one that did. I copied ios-configure-glog.sh from the<EMAIL_ADDRESS>project to my current project<EMAIL_ADDRESS>It turns out that in my case it wasn't a corrupted install of glog or double-conversion. The issue was with the following code in the script:
# Prepare exported header include
EXPORTED_INCLUDE_DIR="exported/glog"
mkdir -p exported/glog
cp -f src/glog/log_severity.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/logging.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/raw_logging.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/stl_logging.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/vlog_is_on.h "$EXPORTED_INCLUDE_DIR/"

Try removing that if it exists in your current project. Hopefully that works for you.

Same issue happened to me after cancelling build in xcode and running it again (xcode v10.2.1, rn 0.59.10). I used Product->Clean Build Folder and puff, it fixed the problem.

same issue with RN 0.60.5 and Xcode 3 any update?

Hope this help.
info Fetching system and libraries information...
System:
OS: macOS 10.14.6
CPU: (8) x64 Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz
Memory: 680.81 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.8.1 - /usr/local/bin/node
Yarn: 1.17.3 - /usr/local/bin/yarn
npm: 6.10.3 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
IDEs:
Xcode: 10.3/10G8 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.5 => 0.60.5
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7
react-native-macos-cli: 2.0.1
=====================================

rm -rf node_modules/ && yarn cache clean && yarn install
rm -rf ~/.rncache
cd node_modules/react-native/scripts
./ios-install-third-party.sh (install folly-2<IP_ADDRESS> double-conversion glog)
cd /node_modules/react-native/third-party/glog*
./configure
Xcode clean (Cmd + Shift + K) and build (react-native run-ios).

thanks @guruparan it works for me.
just delete  the podlock file, and run pod install

fix here https://github.com/facebook/react-native/pull/26300
if you get 'glog/logging.h' the third party libraries are failed to install.
the podspec script launch is not throwing any error.
if you are on appcenter you need to update the pods on pre-build
https://gist.github.com/thisisablock/b57185cc3657d4e0252960a0bd7cf0a9

Just run "ios-configure-glog.sh" from glog dir.
After comment all 4 last lines - fetch_and_unpack ... in "ios-install-third-party.sh"
And run in XCode or rn cli.

@AlexArtisan yep it’s workaround but it didn’t fix the origin. The issue is that the ios-install fails to install glog because it’s calling the the installer from a wrong workdir. On pod install it not throwing any error because cocoapods sadly is not able to throw an exception here.
But it’s not safe because on every fresh npm install  (for example on appcenter) the dependencies are not downloaded and will not be included inside pod install.

In my case the root cause was the space in "Xcode 10.1" app name. Maybe it will help someone.

@marcin-modestowicz Could you tell what space you mean exactly? And how did you fix it?

@artechventure I installed Xcode in Applications under XCode 10.1 directory (with space) and it broke compilation process. Renaming to XCode10.1 fixed the issue.

@marcin-modestowicz thanks. saved my time

I had the same issue. I copied MyProjectName/node_modules/react-native/third-party/glog-0.3.5 from a different working project and replaced the version of glog-0.3.5 in the non-working project and now it seems to be ok.


[InstantNGP] File Not found error

Hi,
I am trying to train my model using instant-ngp on nerf synthetic lego dataset using the following command ns-train instant-ngp --data data/nerf_synthetic/lego and i face the following issue. No such file found "/data/nerf_synthetic/lego/train/r_0" though r_0.png exists. Please let me know what can be done here. Thanks in advance for your help.

Thanks for the quick reply. I tried training with ns-train instant-ngp-bounded --data blender-data and i get the following error ns-train: error: argument {nerfacto,instant-ngp,mipnerf,semantic-nerfw,vanilla-nerf,tensorf,dnerf,phototourism}: invalid choice: 'instant-ngp-bounded' (choose from 'nerfacto', 'instant-ngp', 'mipnerf', 'semantic-nerfw', 'vanilla-nerf', 'tensorf', 'dnerf', 'phototourism')  and my git version is 2.25.1  I also tried training with ns-train instant-ngp --data blender-data but got the following error `FileNotFoundError: [Errno 2] No such file or directory: 'blender-data/transforms.json' Can you please let me know how to proceed ahead. Thanks for the help @tancik

I was also curious @tancik https://docs.nerf.studio/en/latest/nerfology/methods/nerf.html if you could share few examples to reproduce the benchmarks as stated in https://docs.nerf.studio/en/latest/nerfology/methods/nerf.html#blender-synthetic using nerfstudio.

@tancik i also tried to download blender data using ns-download-data blender and i am redirected to a google drive link:  https://drive.google.com/uc?id=18JxhpWD-4ZmuFKLzKlAw-w5PpzZxXOcG and also throws an error FileNotFoundError: [Errno 2] No such file or directory: 'data/blender_data.zip' Using the google drive link data throws the error: FileNotFoundError: [Errno 2] No such file or directory: 'blender-data/transforms.json`

Thanks @tancik for the quick reply. Do you know which of these methods is the fastest on blender-data as training seems to be taking time using instant-ngp. Thanks.

How long is a "long time"? You should expect to see good results after a couple of minutes. Note the base instant-ngp model won't produce good results for the blender scenes, you will need to use the bounded version.

@tancik 27% training time is taking 2 hrs nearly with instant-ngp. Am i doing something wrong? i am building the docker file from the main branch and just doing ns-train instant-ngp --data data/nerf_synthetic/lego blender-data on the terminal. Please let me know if you need more details. Thanks @tancik for quick reply.

This is what I get after 500 iterations (~10 seconds of training)

This is using the following training command
ns-train instant-ngp-bounded --pipeline.model.background-color white --data data/blender/lego blender-data

ok i am just using instant-ngp and nothing shows up in the viewer (I have changed port, i hope this doesn't matter). Will check on this thanks @tancik

This is what I get after 500 iterations (~10 seconds of training)  This is using the following training command
ns-train instant-ngp-bounded --pipeline.model.background-color white --data data/blender/lego blender-data

@tancik thanks for the reply. Can you please share GPU configurations you used to achieve this speed, Is this multi-gpu setting?

This is one 3080 GPU

Thanks @tancik is training by chance slower on synthetic/blender data than nerfstudio data.

The example I shared above is blender synthetic data. If anything it is faster in the synthetic data.

@tancik thanks for the trouble. i am using a A100 GPU and 17% (% done) training is taking 2 hours on synthetic lego data and nothing shows up on viewer apart from images. Please let me know.

This is one 3080 GPU

Can you please let me know the tinycudann version you are using @tancik

My tinycudann version is 1.6. You should ignore the % done for the blender scenes. It should look basically done after a couple %. My guess is that it is working, but just not showing up in the viewer. This is an issue for some users, it seems to depend on network setting (firewalls, vpn, corp restrictions). You can try running with the extra argument --viewer.skip-openrelay True to see if that fixes it.

Also consider joining our discord to ask these troubleshooting questions. They can get lost pretty easily in these github issues, especially now that the issue has diverged from the title issue. I'm going to close this for now, feel free to reopen if you think appropriate.

Hi, may I ask what is difference between instant-ngp and instant-ngp-bounded version?

There is some info here - https://github.com/nerfstudio-project/nerfstudio/issues/1099

There is some info here - #1099

Thanks!


doge house 🐕🏠...

You could also change the file name to 🐕.🏠, if you wanted to.

Merge? 👍 / 👎

Originally the file was a gigabyte of doges but GitHub wouldn't let me push it because of a file limit. We either go big or small and because we can't go big with the gigabyte of 🐕 we should keep it small and simple with a singular 🐕 emoji in the file.

tg it didn't

that would be a big problem


Added tests for file-upload-assessment-dashboard component

Checklist

[X] Client: I added multiple integration tests (Jest) related to the features (with a high test coverage)

Test Coverage
Test Coverage is only around 62% as most methods are private. Will be enhanced by implicit testing in future followup

closing for now, please reopen it when it is ready to merge


Checkboxes not visible unless checked

My users do not like the behavior of the check boxes. They do not look like the screenshots. The check boxes are invisible until checked. It actually took us a while to realize we could even touch in that area to select a file.
I recommend you make the check boxes visible even when not checked. Either that or make the selection by clicking the file, but that would mess with the directory selection. Easiest way is to make all check boxes visible.
I know how to do it, but I am not sure how to recompile the library with my changes. I messed with android studio all day today and can't figure it out.
If you do this change then I would LOVE to use your library.
EDIT:
I should probably have mentioned... GREAT WORK!!! This library is awesome either way and looks great. It will be a huge time saver for me and looks better than some other ones I have seen. Just need this ooooooone tiny thing changed.

Hi, the check box is not visible because of theming issues, however it has been fixed in version 1.0.3, are you using a version that is lower than this?

Oops I was using 1.0.2. That is what I copied from the read-me.
I'll try that out. Thank you! I tried a few other libraries and definitely like yours the best.


Docma CLI --base  overwrite option

The docma serve command can have a --base option that is very useful to test locally when you have a app.base specified. However, the main Docma CLI doesn't have a --base option that allow us to overwrite what is specified on app.base.
This poses a challenge to publish different module versions to our internal manuals which has the version as part of the base path (as /view/module-name/doc-type/version/). Ideally we would like to overwrite the  base with a command line argument. This way we would use package.json vars to build documentation for multiple versions.
Is that something that interest you? I can send a PR for it.

Thanks but docma serve command already has it. See docs here.

Sorry, maybe my message wasn't clear. I know docma serve has it, but the main docma command doesn't. I would like a way to override app.base at the time we are generating docs to publish in a static server, because our manual server put the version as part of the URL. Without it, every time we are publishing a new version we need to modify docma.json app.base to have the new version and can't rely on automated tools for publishing the library.

actually, nevermind... I can create a script that modifies docma.json and call it on prepublishOnly. doesn't need to be part of docma.

I see what you mean. Yes --base option would be very useful for that kind of use-case. You're welcome if you still want to send a PR. I'll re-open this as a feature-request now. Thanks.

Thanks. I opened #79 with the changes. Currently there isn't a great way to test CLI without change some of the current behavior (like passing argv as a parameter to to updateConfig and exporting the method), but I didn't want to make such a huge change for something so small. If you like I can make another PR to enable CLI testing.

No problem. Thanks


[SidePanel]: Scrolling behavior breaks when panel loads without a scrollbar and the screen height shrinks

What package(s) are you using?

[x] Cloud & Cognitive
[ ] Legacy/CDAI
[ ] Legacy/Security

Detailed description
I see this in my program as well as in the latest Cloud & Cognitive storybook here.
When the SidePanel is first loaded at full height without a scrollbar, the scrolling behavior for the panel's title breaks when the resizing the window height.
I do not see this issue when the SidePanel is first loaded with a scrollbar, and later adjust the window height.
I see this in Chrome & Firefox.
Steps to reproduce the issue

In the C&CS Storybook under SidePanel > Panel with Second Step: Open the SidePanel so it loads at full height without a scrollbar
Shrink your window height smaller until a scrollbar within the panel appears
Scroll the panel and notice the panel's title is no longer shrinking and transitioning as intended

Additional information
https://user-images.githubusercontent.com/3118961/126699308-0fe9c83a-3ecf-4821-9a0c-0d04542fcfe8.mov

Hey @lily-peng, this will be addressed with https://github.com/carbon-design-system/ibm-cloud-cognitive/pull/1064

Fix is released is version<EMAIL_ADDRESS>Feel free to reopen if you run into any other issues @lily-peng

Hi @matthewgallo, thanks for fixing it so quickly. However, I still see the same issue from my recording in the storybook (and in my application). Unless I am missing something, I don't think this issue was fixed?

Ok, this should be fixed this now @lily-peng. Thanks for bringing it back up<EMAIL_ADDRESS>As always, if this isn't behaving as expected please reopen!


AllocString implementation for FlycatcherString

Currently, the AllocString implementation looks like this;
/// A general purpose string that implements the `FlycatcherString` trait.  It uses the global
/// allocater to allocate memory for the string.
pub struct AllocString {

}

It does not implement the FlycatcherString crate and therefore isn't usable.  This will be a commonly used struct, so this should be higher priority, especially since it is needed for the flycatcher-lexer crate.

The standard library shall be enabled from this point on.


Django 1.8: ImportError: No module named related

  File "/Users/thekgf/CentriFile/allay/venv/lib/python2.7/site-packages/simple_history/models.py", line 13, in <module>
    from django.db.models.related import RelatedObject
ImportError: No module named related

Django 1.8 has made some changes here and removed the RelatedObject API. More details are here: https://docs.djangoproject.com/en/dev/releases/1.8/#model-attribute-on-private-model-relations

Yeah. I've looked a little at it, but I haven't figured out what the solution is yet. If anyone else would like to try, please feel free! @treyhunner and I will both be at PyCon in Montreal in April as well. We talked a little about doing some sprints while we're there if this isn't fixed by then.

Hey guys, I was wondering if this change is appropriate to fix it, and if not, what the issue is with it? I see some warnings that it degraded the quality of the build, but can't find what it degraded.
https://github.com/treyhunner/django-simple-history/pull/157

I know the comments are mostly from Landscape, but it's only testing code
style. It's breaking all of the builds in travis:
https://travis-ci.org/treyhunner/django-simple-history/builds/53095209
Unless those all pass we can't merge it.
On Thu, Mar 19, 2015 at 12:56 PM TheKGF<EMAIL_ADDRESS>wrote:

Hey guys, I was wondering if this change is appropriate to fix it, and if
not, what the issue is with it? I see some warnings that it degraded the
quality of the build, but can't find what it degraded.
#157 https://github.com/treyhunner/django-simple-history/pull/157
—
Reply to this email directly or view it on GitHub
https://github.com/treyhunner/django-simple-history/issues/156#issuecomment-83738844
.

FYI - I fixed another app for this with these steps:
In the imports section
-from django.db.models.related import RelatedObject
+
+try:

from django.db.models.related import RelatedObject as ForeignObjectRel
+except:

django 1.8 +

from django.db.models.fields.related import ForeignObjectRel

the replace all RelatedObject with ForeignObjectRel

Thanks Phoebe... Our situation was a little more complex, but it looks like
we will able to remove use of related completely (#160).
On Apr 8, 2015 1:39 PM, "Phoebe Bright"<EMAIL_ADDRESS>wrote:

FYI - I fixed another app for this with these steps:
In the imports section
-from django.db.models.related import RelatedObject
+
+try:

from django.db.models.related import RelatedObject as
ForeignObjectRel +except:

django 1.8 +

from django.db.models.fields.related import ForeignObjectRel

the replace all RelatedObject with ForeignObjectRel
—
Reply to this email directly or view it on GitHub
https://github.com/treyhunner/django-simple-history/issues/156#issuecomment-91030594
.

Good!

Looking forward to have this packaged, this incompatibility is preventing our migration to 1.8, we are using simple-history as a third party app.

+1, looking forward to an update. Thanks for the awesome module. :+1: :octocat:


No access to field types for a query result

In mysql2, a result has a field_types method to get access to the field types of the result. Trilogy doesn't seem to provide any way to get access to these in the Ruby layer. The C driver does provide it, but it's not exposed in Ruby.
The Ruby driver does use it for casting purposes, so it's internally available. See also:
https://github.com/trilogy-libraries/trilogy/blob/640f990f26c12564935af16a96d9a9bf294d0a1d/contrib/ruby/ext/trilogy-ruby/cext.c#L738-L742
There the data is read into column_info but that data is ephemeral for the result object and not included in the final result.
We were looking to move to Trilogy, but we do need access to this field type information in some way or another. From purely that perspective, it doesn't have to be compatible 1:1 with how mysql2 works, as long as it's available in some way.
I'm happy to contribute a PR to add this, but I don't really know what the preferred way of adding this would be. Should it be for example to column_info and then lazily create entries in a field_types method? Or should we build field_types directly like fields is built (although often it won't really be needed, as is clear since it's not present yet and already extensively used with Rails).
Or should there be a totally different function than field_types that returns the types not as strings like mysql2 does, but with integer constants + any of the additional flags / size attributes etc. for the type? If there's any preference with how to make this available, I'm also able to start a PR for that then.

I'd be in favor of an API that exposes all of the column info available from the C API.
Maybe something like Result#columns which returned an array of Result::Column classes that had those attributes like name, type, flags, etc. And yeah, having this method create the array of Result::Column's lazily would be ideal. This would sorta duplicate what's already available via the fields attribute, but maybe that could be removed in a future release, in favor of this new columns method, to avoid making a breaking change all at once?


No information on how to generate code coverage

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x ] feature request

Versions.
@angular/cli: 1.2.0
node: 6.11.0
os: win32 x64
@angular/animations: 4.2.5
@angular/common: 4.2.5
@angular/compiler: 4.2.5
@angular/compiler-cli: 4.2.5
@angular/core: 4.2.5
@angular/forms: 4.2.5
@angular/http: 4.2.5
@angular/platform-browser: 4.2.5
@angular/platform-browser-dynamic: 4.2.5
@angular/router: 4.2.5
@angular/material: 2.0.0-beta.8
@angular/cdk: 2.0.0-beta.8
@angular/flex-layout: 2.0.0-beta.8
@angular/cli: 1.2.0

Repro steps.
When we run the ng test --code-coverage --reporters=coverage-istanbul --watch=false It will generate a coverage folder and index.html file which contains only the test.ts and pollyfill.ts but doesn't report test coverage of any file/modules in src folder (unless there is *.spec.ts).
The log given by the failure.
Desired functionality.
Expecting a way to generate the complete report of all the *.ts file under src folder that have *.spec.ts show percent covered and which doesn't have should show 0% coverage etc...
Mention any other details that might be useful.
I used the ng new myproject generate the project.

I have a project with the following hierarchy:

Using Angular CLI 1.3.0-beta.1, I ran:
ng test --code-coverage --watch=false

And then I got coverage folder with an index.html that looked like:

Opening each folder shows the files in it, like:

Which also show the coverage of each file:

So, it seems to be working for me.

@Meligy I think you didn't get my point here. It shows the coverage only if there is *.spec.ts file but it doesn't show source files that don't have *.spec.ts associated with it. Essentially we can't generate the full report which show how much code one has covered in the project. It is easy to deceive by developer to show the code is tested (it will never show in the coverage report) unless there is *.spec.ts file.
If we could generate the report which show no coverage or no *.spec.ts file yet to any of the code then it make more sense.

@manju-reddys You can do this by changing context regex in src/test.ts. I.e. change
const context = require.context('./', true, /\.spec\.ts$/);

to
const context = require.context('./', true, /\.\/app\/.+\.ts$/);

This will essentially include every .ts. file in you app folder into test bundle and therefore they will be included in the coverage report. But note that doing so will slow down test run quite significantly in some cases.

@devoto13 Thank you for the tip. I agree it take longer to run the tests but it will be run before production build. Developer will continue to use const context = require.context('./', true, /\.spec\.ts$/);


Remove extra close from attach resize channel

We already close the resize channel in the goroutine we spawn to forward signals. There is a potential race where a terminal resize event is received after the attach finishes and attachCtr closes the channel, but before the remaining cleanup occurs, allowing the goroutine to send a signal along the (now-closed) channel and causing a panic. Let the goroutine manage the lifetime of the channel to avoid this.

bot, retest this please

LGTM
@baude @umohnani8 PTAL

LGTM

LGTM

@rh-atomic-bot r=umohnani8


add linux arm nif build support

This PR adds support for aarch64 NIF support Ockam release
closes https://github.com/build-trust/ockam-artifacts/issues/95

After this change is released, https://github.com/build-trust/ockam/pull/3873 needs to be merged to point to the new lib locations.

@Mergifyio rebase


fetchgit: use buildPackages's git

Motivation for this change
fetchgit is to use buildPackages's git for the same reason why fetchurl uses buildPackages's curl: to work smoothly in code blocks like
stdenv.mkDerivation {
   src = fetchgit { # <- here git of buildPlatform is expected to work
.............
   };
}

Is nativeBuildInputs not splicing it correctly? That should work in this case.

Is nativeBuildInputs not splicing it correctly? That should work in this case.

No :( And fetchurl in all-packages.nix also explicitly uses buildPackages.curl

Sounds like a bug in handling nativeBuildInputs to me. What's the use of nativeBuildInputs if you have to explicitly feed it buildPackages.foo ?

I guess it is only because the override in all-packages.nix

Sounds plausible. That would mean you must always override nativeBuildInputs with buildPackages.xxx - guess we should document that somewhere.
An alternative solution to this PR would be to use gitMinimal as a argument to fetchgit instead of injecting it. Is there any use case of fetchgit where gitMinimal is not sufficient?


dropMessagesInSession for clientId

clear the m_persistentMessageStore should use message guid to clear the map,not use clientId to clear the map,because we put message in the map use guid for the key

Your assumption is incorrect, if the broker has a retained message, if the publishing client disconnects, the message has to still be persistent for future. Please next time, if you find something that doesn't work,  open an issue and discuss on it before wasting time.


Heron 2d debug2d feature conflict

very simillar to the bevy_conosole issue #126 , when using Heron 2dDebug feature flag, there is a conflict with a shapes stage
thread 'main' panicked at 'Stage already exists: Shape.',

this conflict occurs with Heron 3.0

This has been solved on the master branch by #163. I'll release a new version when Bevy 0.8 comes out.


What is textureData?

Where is textureData defined here? How is it loaded? Where is it loaded? What data structure holds it?

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

ID: d54624b3-5d20-80db-2092-a8850ceaeb45
Version Independent ID: 67dfbf9f-c38d-92e9-f421-d94d75571853
Content: Apply textures to primitives - UWP app developer
Content Source: windows-apps-src/gaming/applying-textures-to-primitives.md
Product: uwp
GitHub Login: @eliotcowley
Microsoft Alias: elcowle

Hi, @KBarrDev, it looks like there's a typo in the code. I've just made a change to the code, which should be live today, but in the meantime, here's how the code should look. I'll leave this issue open, please let me know if you run into any other issues with it.
auto loadTDTask = DX::ReadDataAsync(L"texturedata.bin");

auto constructSubresourceTask = loadTDTask.then([this](const std::vector<byte>& textureData)
{
    D3D11_SUBRESOURCE_DATA textureSubresourceData = {0};
    textureSubresourceData.pSysMem = textureData.data();

   ...
}

The function DX::ReadDataAsync, as you know, is a generic "read a binary file" function. It's used to read the compiled shader objects, too. So we can use it here to load a texture image file. The .then is a continuation, and it takes whatever the async operation (in this case, a call to ReadDataAsync) generated. The call to ReadDataAsync generated a vector of bytes, of course, containing the bytes that were in the binary file. So we just grab the data from that vector and use it to prime the D3D11_SUBRESOURCE_DATA.
Thanks! ~Steve

Hi, @KBarrDev, I'll go ahead and close this issue now since it's been a while, and it feels resolved. Please reopen if I made a mistake in closing. ~Steve


nfs: memleak w file_data

https://redmine.openinfosecfoundation.org/issues/4895
https://redmine.openinfosecfoundation.org/issues/4894

Replaced w #715


Tokenzier special chars

https://github.com/turboderp/exllama/pull/195#issuecomment-1649736282
Hello! :) Per your request:

I.e. you should just be able to add  and  at arbitrary places in the input string, as well as any other custom special tokens any given model requires. Ideally it would work when decoding as well.

I added your functionalities just like you described. One can now choose to encode/decode special characters.
This PR is based or rather dependent on the other PR ( #195 ) (because locally I need both and I don't know GitHub well enough to merge both)
Example:
The string: <s><s>Hello</s><unk> <s>World</s></s>
encodes to: tensor([[    1,     1, 15043,     2,     0,   259,     1,  2787,     2,     2]]) (I verified all IDs manually)
(without encode_special_characters: tensor([[  529, 29879,  5299, 29879, 29958, 10994,   829, 29879,  5299,  2960,  29958,   529, 29879, 29958, 14058,   829, 29879,  2565, 29879, 29958]]))
Decoding these IDs results in:
<s><s>Hello</s> <s>World</s></s>
Which is correct! (<unk> is the same id as the padding token, 0. If you want, I can also include every 0 to be a <unk>)
If you want to test and verify, here is the snippet that I put into the tokenizer init for debugging:
        text = "<s><s>Hello</s><unk> <s>World</s></s>"
        print("encoding: " + text)
        print(self.encode(text, encode_special_characters=True))
        print(self.encode([text, text, text, text], encode_special_characters=True))

        ids = self.encode(text, encode_special_characters=True)
        idsb = self.encode([text, text, text, text], encode_special_characters=True)
        print(f"decoding: {self.decode(ids, decode_special_characters=True)}")
        print(f"decoding batch: {self.decode(idsb, decode_special_characters=True)}")

I would be happy if you accepted both pull requests and I hope this PR aligns with your intents :)

Also, #195 s existence is justified because when creating a chatbot and one provides some HTML tags or something, one really doesn't want that to be encoded as special tokens just to make the backend prompting easier

I'll have to give this a good look a little later. There's currently no code for actually loading all the specific tokens a model might define. Some add like five new tokens and use a vocabulary size of 32005, then define those tokens in a bunch of extra config files packaged with the model, with each having options for how spaces should be encoded before and after those tokens.  I can work on an auto loading of added_tokens from the tokenizer.json if you want that, but if some models use extra configs that are not standardized it seems rather difficult to implement
And regarding #195 , I wanted to kindly ask if you intent to merge it? This way I would not have to base my branches off of the boseos branch and it's just an optional parameter anyways that doesn't break anything

I'll merge #195 when I have a moment to test it. It seems fine. This one is probably good too.
As for those extra tokens, you can take a look at this HF model for instance, based off of OASST.
added_tokens.json (note that the highest token ID defined is 32004, even though the vocabulary is extended to 32006)
{
  "<|assistant|>": 32004,
  "<|prefix_begin|>": 32000,
  "<|prefix_end|>": 32003,
  "<|prompter|>": 32002,
  "<|system|>": 32001
}

special_tokens_map.json (note how pad_token == eos_token for some reason)
{
  "additional_special_tokens": [
    "<|prompter|>",
    "<|system|>",
    "<|prefix_begin|>",
    "<|prefix_end|>",
    "<|assistant|>"
  ],
  "bos_token": {
    "content": "",
    "lstrip": false,
    "normalized": true,
    "rstrip": false,
    "single_word": false
  },
  "eos_token": "</s>",
  "pad_token": "</s>",
  "sep_token": "<s>",
  "unk_token": {
    "content": "",
    "lstrip": false,
    "normalized": true,
    "rstrip": false,
    "single_word": false
  }
}

tokenizer_config.json (tokens have empty context here for some reason)
{
  "add_bos_token": true,
  "add_eos_token": false,
  "bos_token": {
    "__type": "AddedToken",
    "content": "",
    "lstrip": false,
    "normalized": true,
    "rstrip": false,
    "single_word": false
  },
  "clean_up_tokenization_spaces": false,
  "eos_token": {
    "__type": "AddedToken",
    "content": "",
    "lstrip": false,
    "normalized": true,
    "rstrip": false,
    "single_word": false
  },
  "model_max_length":<PHONE_NUMBER>000000019884624838656,
  "pad_token": null,
  "sp_model_kwargs": {},
  "tokenizer_class": "LlamaTokenizer",
  "unk_token": {
    "__type": "AddedToken",
    "content": "",
    "lstrip": false,
    "normalized": true,
    "rstrip": false,
    "single_word": false
  }
}

The model's config.json also defines token IDs for EOS, BOS, and PAD, and supposedly strings are also defined in the binary, tokenizer.model. So you see it gets a bit complicated and it's very unclear what to even do with the conflicting definitions. It has a lot of early web vibes, from back in the day when there really weren't any standards other than "the standard is whatever happens to work in IE6".


Hard to determine what file code samples are shown

It would be easier if the file names for the sample code are shown, so it's easier to follow and find right away without digging into the entire source.

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

ID: 0fc28a40-716e-22bc-8944-15f0a8b0d5c2
Version Independent ID: 86252b0d-94e2-2ea6-ed17-fc32ae38e6fc
Content: Get notification from bots - Bot Service
Content Source: articles/v4sdk/bot-builder-howto-proactive-message.md
Service: bot-service
Product: bot-framework
GitHub Login: @JonathanFingold
Microsoft Alias: jonathanfingold

will be fixed shortly


Potential caching improvement

In the provided caching example
      - name: Cache pnpm modules
        uses: actions/cache@v2
        with:
          path: ~/.pnpm-store
          key: ${{ runner.os }}-${{ hashFiles('**/pnpm-lock.yaml') }}
          restore-keys: |
            ${{ runner.os }}-

pnpm-lock.yaml hash is a part of the cache key. Does it need to be? It seems that packages stored in the cache are versioned. In the integration guide for Travis it looks like the cache directory is just shared across all the builds https://pnpm.io/pl/continuous-integration#travis

Does it need to be?

It doesn't. Adding hash of pnpm-lock.yaml is only beneficial when you undo a change to the list of dependencies. For example, one day you decide to remove react, and as a result, the cache size sinks by half (because this action has a post step that prune dependencies), but then you change your mind, adding react back, without the hash of pnpm-lock.yaml, your CI must fetch and install react and its dependencies again.

Thanks for the answer, wanted to be sure! Looks like it's also a default behavior when using setup node action with cache set to pnpm.


"Cannot find module" error when trying to run ./YesPlayMusic-0.4.8.AppImage

I'm on openSUSE 15.5, and I have failed to run the 0.4.8 version AppImage.
Full command and its outputs are as follows:
$ ./YesPlayMusic-0.4.8.AppImage
/usr/bin/AppImageLauncher: /usr/lib64/libcurl.so.4: no version information available (required by /usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Cannot find module '@unblockneteasemusic/rust-napi-linux-x64-gnu'
Require stack:
-<EMAIL_ADDRESS>- /tmp/.mount_YesPlao8Iryh/resources/app.asar/background.js
-
    at Module._resolveFilename (internal/modules/cjs/loader.js:887:15)
    at Function.n._resolveFilename (electron/js2c/browser_init.js:257:1128)
    at Module._load (internal/modules/cjs/loader.js:732:27)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
    at Module.require (internal/modules/cjs/loader.js:959:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/tmp/.mount_YesPlao8Iryh/resources/app.asar/node_modules/@unblockneteasemusic/rust-napi/index.js:184:31)
    at Module._compile (internal/modules/cjs/loader.js:1078:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1108:10)
    at Module.load (internal/modules/cjs/loader.js:935:32)

okay, that problem has been solved. but now I encountered a new issue:
$ ./YesPlayMusic-0.4.8.AppImage --trace-warnings
/usr/bin/AppImageLauncher: /usr/lib64/libcurl.so.4: no version information available (required by /usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)
[background.js] initializing
[NetEase API] initiating NCM API
[background.js] creating express app
server running @ http://localhost.localdomain:10754
[background.js] app ready event
[background.js] creating app window
[background.js] checkForUpdates
Checking for update
libva error: /usr/lib64/dri/i965_drv_video.so init failed
[globalShortcut.js] registerGlobalShortcut
(node:27687) UnhandledPromiseRejectionWarning: Error: Could not connect
    at Socket.o (/tmp/.mount_YesPla3Yg54M/resources/app.asar/background.js:2:3084317)
    at Object.onceWrapper (events.js:422:26)
    at Socket.emit (events.js:315:20)
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
(Use `yesplaymusic --trace-warnings ...` to show where the warning was created)
(node:27687) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:27687) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[background.js] window ready-to-show event
Update for version 0.4.8 is not available (latest version: 0.4.8, downgrade is disallowed).
checkForUpdatesAndNotify called, downloadPromise is null

You might need to install your display card driver.

After updating to 0.4.8-2, the appimage is now functioning well without any black screen or failure, but the warning persists if I run it through terminal.
Maybe it's a minor problem since it now won't affect my use, but I'm quite sure that I've got my display driver right.


Looks like "--once" is reserved

The string:
foo

Usage:
  foo [--once]

Options:
  --once                run once then exit

fails with:
unmatched '[', expected: ']' got: ')'

Probably pebkac, I'll close until sure.


Add: Binh Duong TV 11

Channel Name
Binh Duong TV 11
Alternative Names (optional)
Bình Dương TV 11, Top Home Shopping
Network (optional)
No response
Owners (optional)
Binh Duong Radio and Television Station
Country
VN
Subdivision (optional)
VN-57
City (optional)
No response
Broadcast Area
c/VN
Languages
vie
Categories (optional)
shop
NSFW
FALSE
Launched (optional)
2008-09-22
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
http://www.btv.org.vn/
Logo
https://i.postimg.cc/W4s0ZhVg/BTV11.png
Notes
No response

Please update your request:

alternative names must be separated by ;

https://github.com/iptv-org/database/blob/master/CONTRIBUTING.md#channels


Changed interim 450k release to final release

I have made changes to the config.tomal file.

Thanks @deepgohil!


Why is the name of every checkbox input in MultiSelect component the same as its label ?

On the MultiSelect component, every checkbox input has its name property set to the content of the label just beneath it (the displayed value of the choice in the list).
Shouldn't there be a itemToName prop exported like the itemToString prop, and take the item id by default for its name ?
This currently clashes hard with libraries such as Felte, where an object is built out of all the content of a form.
Right now, my workaround is to put my MultiSelect in a separate fieldset and delete those from my data object before submitting it, but I think I should be able to use the this component natively here.

It seems that React implementation actually no longer uses the input element for MultiSelect fields.
https://github.com/carbon-design-system/carbon/blob/5bf32f92f233f78823f8cf1b222cae038f3e13ef/packages/react/src/components/MultiSelect/MultiSelect.js#L301
I'll take a look into aligning this.

Interesting, I'm not too familiar with React so I wouldn't know why that is.
But it you're okay with the proposition I made I can maybe draft a PR and propose an alignment ?

PRs welcome

Supported in v0.58.0.
Use the itemToInput prop to customize the name, title, and labelText values.
<MultiSelect
  filterable
  titleText="Contact"
  label="Select contact methods..."
  itemToInput={(item) => ({
    name: "name: " + item.id,
    labelText: "label: " + item.text,
    title: "title: " + item.text,
  })}
  items={[
    { id: "0", text: "Slack" },
    { id: "1", text: "Email" },
    { id: "2", text: "Fax" },
  ]}
/>


Caching compiled code

At the moment it seems that even though wasmtime itself implements a very nice caching system that makes startup latency almost disappear in my application, wasmtime-py does not use it. Is this intentional, or is this just an oversight?
For now I was able to work around that with an intrusive patch that cuts down the application size to under 2 MB, which takes about 2 seconds to compile on a modern laptop, but that's a pretty significant limitation and I'm worried about the increase in latency on low-end hardware.

Turns out this actually isn't possible today with the C API, so I've opened up https://github.com/bytecodealliance/wasmtime/pull/1606 to start the process of getting that upstream here.

Thank you!


Add the ability to define the width of the popover in ComboBox/AutoComplete

Provide a general summary of the feature here
Pickers currently allow for a custom width using the menuWidth prop see docs
We want to allow this option in ComboBox and AutoComplete. It should always default to the width of the input, as it does now, however if the prop menuWidth is set, use that instead.
Note: menuWidth needs to be >= width of the input. If the prop is < the input, default to the min-width and ignore the prop.
🤔 Expected Behavior?
Allow the popover width to be customizable.
😯 Current Behavior
No option to control this
💁 Possible Solution
Similar to
https://github.com/adobe/react-spectrum/blob/5dac45cf72f92048aedf730abec8626eb6094cf6/packages/%40react-spectrum/picker/src/Picker.tsx#L137-L140
🔦 Context
Use case of combobox and autocomplete where the content of the options needs more room to display. Truncation might not always be the right answer.
💻 Examples

🧢 Your Company/Team
Adobe/Sign
🕷 Tracking Issue
No response

@dannify Hi! I want to take a stab at this.
By the way, just to make sure I understood everything correctly, by AutoComplete you mean SearchAutocomplete under  the pickers category in React Spectrum, right? I'm asking this because I don't see it under the pickers category in current docs, but I DO see it (tagged as alpha) when I run yarn start:docs on main branch.


Mixer EL should support string length function

Describe the feature request
The Mixer EL has some functions for strings to match them with a regex, and methods to check for prefixes, suffixes etc.
It would be nice if there would be a method to get the length of a string.
I.e. a match condition in a Rule like "abc".length() == 3 should evaluate to true.
Describe alternatives you've considered
An alternative could be to match against a regex like ^.{3}$, which is very bad performance-wise and not readable.

FWIW, CEL supports size function: https://github.com/google/cel-spec/blob/master/doc/langdef.md#functions.

Hm... both size("foo") and "foo".size() give me `unknown function: size.
Is there anything that I am doing wrong?
From the document I would assume that the first example should work.

Sorry, I didn't mean we support them! Thank you for making the contribution to add it. We do want some alignment between our IL and CEL. It's not on any short-term road map. Picking the same function names might just help in the longer term if we decide to extend IL to full CEL.

Ah ok, thanks for the clarification :-)
I was already on the way providing a PR for .length().
But I'll adapt it then to size(arg).

Looks like it is not that easy to add polymorphic functions.
I will need some more time to find out how that would work and to understand the whole architecture of that thing.

@robertpanzer are you working on this?

No, I am not working on this right now.
I was thinking about adding this to my other PR that extends the EL, but then decided to not let it grow too big.