setup local otel dashboard

aspire is more than just this dashboard, but this lets us view traces as they happen when doing local dev, it's not used anywhere else

For comparison I just tried out zpages, which is an otel extension for debugging. I thought it was more of a trace viewer, but I guess not:

I'm not sure if that would add any value, but I like the screenshot you shared of aspire 🚀

I'm getting:
 - languagedepot:deployment/lexbox: container otel-collector in error: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "--config": executable file not found in $PATH: unknown
    - languagedepot:pod/lexbox-bc464bdb9-5skbw: container otel-collector in error: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "--config": executable file not found in $PATH: unknown
 - languagedepot:deployment/lexbox failed. Error: container otel-collector in error: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "--config": executable file not found in $PATH: unknown.

Also, I think you would want/need to list the port for the infra and no-frontend skaffold profiles as well.

@myieye take another look, I fixed the startup issue, I also added in the k8s node as that's something I'd like for our hg performance tracking.


Add minZoom and maxZoom properties for android and ios

Adding ability to set minZoomLevel and maxZoomLevel for both iOS and Android (GMaps included for iOS).
Need maybe some review for iOS, as i did a dumb implementation of https://github.com/johndpope/MKMapViewZoom .

Well yeah which is quite logic. What will happen is that, if the required zoom to fit your markers is more than the maxZoomLevel, you will have your map at this maxZoomLevel (same case for minZoomLevel).

Then this PR is very good. What if I want to use fitToMarkers with different min zoom level? I guess this setting is global 🤔

This is a global setting for the map yeah, but something which has to be tested is to set the max/min possible zoom values in case you do a fitMarkers by settings the props with a state value.

PR updated, i forgot to add some things to the AIRMap.h, and GMaps for iOS was not working correctly

Corrected that, i got confused when merging some branches, but it's ok now

I'm using react-native-maps 0.17.1. I set maxZoomLevel=10 and minZoomLevel=8, but I still can zoom in/out like nothing is limited. Does anyone have same problem?

Strange behavior on Android.
You should place maxZoomLevel props in the end of MapView declaration to make it works.
<MapView
     style={{ flex: 1 }}
     showsUserLocation={true}
     showsMyLocationButton={true}
     mapType={this.state.mapType}
     ref={(ref) => { this.mapRef = ref; }}
     onLayout={() => this.mapRef.fitToCoordinates(markers)}
     maxZoomLevel={17}>

Maybe conflicts with onLayout props?


CSV parser always converts a non-quoted empty string to null regardless of null_string

Discussion continued from https://github.com/embulk/embulk/pull/432.
Currently, there is no way not to convert a non-quoted emtpy string to null.
Even if we specify null_stirng: "NULL" or something else, a non-quoted emtpy string is always converted into null. We need an option to keep a non-quoted empty string as an empty string.

CSV parser plugin converts a non-quoted empty string to null but quoted empty string is kept an empty string.

Keeping this default behavior is fine.

Keeping this default behavior is fine, and this behavior must be written on the document
Sounds good. Let's take these ways.

Thanks. And. my problem is not for the default behavior. The problem appears when we specify null_stirng: "NULL" or something. It still converts a non-quoted empty string to null.

ok. it was unclear from the PR that changes the default behavior.
I think the easiest implementation is to change the meaning of null_string: option so that default behavior (null_string: null) makes non-quoted strings to NULL, setting empty string (null_string: "") makes any empty strings to NULL regardless of quotation, and setting other strings (null_strings: abc) makes the string to NULL regardless of quotation.

Agree with the specification. I will resend PR.

ok. it was unclear from the PR that changes the default behavior.

yep, I mistakenly changed the default behavior with #432 because I did not know CSV parser plugin converts a non-quoted empty string to null but quoted empty string is kept an empty string. was its specification.


Issues with this extension on Dropbox

I'm unable to cope+paste text on plain text documents on Dropbox, and context menu is completely disabled also so I can't even Ctrl+C selected text.
here's one example - https://www.dropbox.com/s/8o5zyxplj9xrkwm/TPHD_BetaQuest_2.0.zip?dl=0&file_subpath=%2FTPHD_BetaQuest%2FReadme.txt

@Alkaris, you're right  that Dropbox does seem to be preventing the copying of text (I haven't been able to reproduce it preventing paste). When this extension is active on Dropbox then I am able to copy text, I'm able to do that with both Command+C (macOS) and with Edit -> Paste from the browser's main menu.
Can you provide the pattern you are using in order to activate the extension on Dropbox?

I've used this pattern https://www\.dropbox\.com

@Alkaris, weird. It's possible they are preventing copy by intercepting the keyboard events of Ctrl+C. I inspected their code to determine if they were doing this and found nothing, but I could have missed it. Can you see if using Edit -> Copy works when the extension is active?

Closing due to inactivity.


fix: legend filter text

Checklist

[x] npm test passes

Description of change
https://github.com/ant-design/ant-design-charts/issues/2665

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 86.694%

Totals

Change from base Build<PHONE_NUMBER>0:
0.003%

Covered Lines:
10557

Relevant Lines:
11802

💛  - Coveralls


Tailwind breaks svelte-calendar's css

I have been using Tailwind with svelte-calendar quite happily for a while, but since the theming changes have been added, it no longer works correctly. It looks like some of the Tailwind utility selectors may be conflicting with this component now.
I stripped it back to a basic app:
<script>
  import { Datepicker } from "svelte-calendar"
</script>

<Datepicker />

<style global>
  @tailwind base;
  @tailwind components;
  @tailwind utilities;
</style>

It looks like I can get around this by prefixing every Tailwind selector but that's a massive task to get a component that was previously working fine to display correctly again.
Is there a known way to avoid this?

Hey @mtrevor - thanks for using the calendar and sharing your experience.  The latest updates were intentionally versioned as a major release to warn of possible breaking changes as it was completely rewritten.  However, I'd love to figure out what's going on for you as I know tailwind is fairly popular.
I have not used tailwind myself, though.  Is there any chance you could provide a minimal replication of the bug via the svelte repl or a small example repository?


Can't Log in

When trying to log in I get an error saying it cant find my User ID. When I refresh the page the same error appears.

Chatterino version: Chatterino 2.2.2-fix (commit a82f57f94)
Operating system: Windows 10

What browser are you using to login? Can you try a different one?

What browser are you using to login? Can you try a different one?

What browser are you using to login? Can you try a different one? Do you have any privacy extensions installed?

Using Chrome, I'll try another.

What browser are you using to login? Can you try a different one? Do you have any privacy extensions installed?

Using Chrome, I'll try another.

Didn't work. Same message

Didn't work. Same message

Do you have any privacy extensions installed?

The only 'privacy' extension I have is Ublock Origin

Do you have any privacy extensions installed?

The only 'privacy' extension I have is Ublock Origin

Turns out it was my antivirus doing something. I turned it off and it worked.

Turns out it was my antivirus doing something. I turned it off and it worked.

ref #487

ref #487


BUG: Fix link libraries.

Fix link libraries: remove the variable that made the module being linked
to itself and make it link to ITK libraries.
The module does not depend on external libraries.

CI is failing because the test is unable to include the header file:
CMakeFiles/RobustPredicateTestDriver.dir/predicates_test.cxx.o: In function
 `test(double, double, int)':
predicates_test.cxx:(.text+0x7d): undefined reference to `orient2d'
predicates_test.cxx:(.text+0x9a): undefined reference to `orient2dfast'
predicates_test.cxx:(.text+0xb0): undefined reference to `incirclefast'

Wondering whether the extern "C" should be removed.


V0.3.0 rc.1

-
-

Issue
https://github.com/cycle-five/cracktunes/issues/XXX

Dependencies

Decisions

Codecov Report
Attention: 48 lines in your changes are missing coverage. Please review.

Comparison is base (d42eaf5) 4.46% compared to head (54ec5e2) 4.83%.

Files
Patch %
Lines

crack-core/src/commands/admin/mod.rs
0.00%
22 Missing :warning:

crack-core/src/commands/music/play.rs
0.00%
7 Missing :warning:

crack-core/src/sources/ytdl.rs
81.81%
4 Missing :warning:

crack-core/src/commands/admin/delete_channel.rs
0.00%
3 Missing :warning:

crack-core/src/commands/admin/role/delete_role.rs
0.00%
3 Missing :warning:

crack-core/src/errors.rs
0.00%
2 Missing :warning:

crack-core/src/lib.rs
0.00%
2 Missing :warning:

crack-core/src/commands/admin/mute.rs
0.00%
1 Missing :warning:

...rack-core/src/commands/settings/set/set_premium.rs
0.00%
1 Missing :warning:

crack-core/src/messaging/message.rs
0.00%
1 Missing :warning:

... and 2 more

Additional details and impacted files
@@            Coverage Diff            @@
##           master    #156      +/-   ##
=========================================
+ Coverage    4.46%   4.83%   +0.37%
=========================================
  Files          70      71       +1
  Lines        4571    4587      +16
=========================================
+ Hits          204     222      +18
+ Misses       4367    4365       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Stat level mods calculated incorrectly

The (vanilla) implementation of stat_level_get for stat_X_mod seems to not take into account bonuses/penalties, including racial bonuses/penalties. This appears to be because StatLevelGetAbilityScoreMod uses ObjStatBaseGet to get the base ability score, not the current ability score.
It doesn't seem like there are many calls to the former function, so this would be most likely to affect scripts, I think. Perhaps more places should use it, though. For instance, TripCheck just calculates the mod itself from the ability score, but that means encumbrance isn't factored in to the dexterity modifier (if it's chosen).
I suppose, in addition, StatLevelGetAbilityScoreMod is factoring in the max dex bonus from encumbrance, but not armor. Perhaps it should do the latter as well.

Hmmm, i think trip check factors in encumbrance from the abilityCheckMod dispatch.
Otherwise I think most of the time you just calculate stat level get directly and subtract 10, no?

That doesn't seem to be the case. If I pump a character up to 30 dex, then make them encumbered and have another character try to trip them, the roll screen still says they're getting +10. Same if I have them wear full plate.
I know it's possible to cap the overall bonus on a bonus list, but I'm not sure doing it via the ability check modifier bonus list would be correct in this situation. I think encumbrance and armor impose a cap on the dexterity modifier contribution to the check, not on the bonus to the ability check from all sources. If this were the approach, too, then the decision making between strength and dexterity in TripCheck would still be wrong. It's supposed to use the stat with the higher modifier (which would be most advantageous), but it's just checking which stat is highest, without considering that an encumbrance/armor penalty could make the strength modifier better than the dexterity modifier.
It's true that all this complication applies only to dexterity, as far as I know. I can't think of any mechanisms that cap other ability score modifiers.


Add download subcommand

With this commit we add a new subcommand download to Rally that can be
used to download a binary. This can be useful in automated workflows
that still want to abstract how the download artefact is actually
retrieved (this has to be handled differently for different releases).

Thanks for the review! :)


PokoGenerator - support Any type for additionalProperties values

What does this PR do?
This PR adds a new capability to the PokoGenerator to be able to use Map<String,Any?> types when declaring the additionalAttributes into the json schemas.
Motivation
We needed this new capability to be able to generate internal model like the UserInfo from the PokoGenerator and to rely on the generated methods for deserializing/serializing the model instances.
Additional Notes
Please note that because Any is not a valid json schema type we could not validate the TypeDefinition (Company) generated from the additonal_props_any.json schema but another test class was provided were we test the serialization/deserialization methods.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #501 (3fcee1c) into master (59b0700) will increase coverage by 0.10%.
The diff coverage is n/a.


handle the webpack 5 default devtoolModuleFilenameTemplate format

Goal
Fix broken github links in stack frames in the dashboard by taking into account that webpack inserts a so-called namespace into source paths in the source map file. The format, at least for webpack 5 is webpack://[namespace]/[resource-path]?[loaders].
Design
Simple whilst maintaining backward compatibility.
This handles the most common use-cases but would not work for cases where output.devtoolModuleFilenameTemplate is customized. (https://webpack.js.org/configuration/output/#outputdevtoolmodulefilenametemplate)
Changeset

Added unit test coverage for the case where [namespace] is not an empty string, which is when the project has a package.json file.
Changed the regexps to handle the webpack://[namespace]/[resource-path]?[loaders] format
Fixed the e2e tests

Testing

Add a new test project fixture, webpack-2 with the only difference being that this project has a package.json file, which is sufficient to cause the sources in the built output to include the pkg.name, e.g. "webpack://this-package-name-is-used-in-the-source-paths/./lib/a.js"
Corrected the expectations in the e2e tests
Depended on this PR in a dashboard-js test branch and deployed to staging and verified the Github links are now working

I've tested the latest changes against the dashboard and with/without nosources, all working as expected.


Fix :& parsing

Subj :shrug:

Thank you

CI failing for an unrelated JRuby regression

Released as v.1.15.2!


Framework Detection Dialog: Irritating. Spurious? Useless?

Previously, I installed Android SDKs and components for the build tools, as well as Android platforms using the SDK manager via Android Studio.
Now, create a new cross-platform project in RVM Studio 1.5.0.
Popup appears:
Frameworks detected
Android framework is detected in the project Configure
Now, I click the Configure link, and a popup appears:
Framework detection
No frameworks are detected

This has been fixed in IntelliJ IDEA 15 as well as the latest RoboVM Studio.


About Boundary Loss

Nice work! Thank u for releasing this repo!
I would like to ask a few questions about BoundaryLoss~

Does BoundaryLoss consume a lot of time in your experiments? In my experiments, computing the Boundaryloss consumes a lot of GPU memory and triples the training time.
I don't use the range image method to represent the point cloud, but use the BEV two-dimensional representation, could the BoundaryLoss be used to train the network?

Thanks in advance for your reply!

Hi.
For 1: In my experiments, it does not take up too much video memory (10.9→11.5) or adds  too much  training time (15min→17min).
For 2: Although I doubt the validity of bd loss, it deserves to be useful from a visualization point of view. I updated the code for bd loss, you can vis GT and Pred edges from it. Where classes from 0→20 corresponds to 20 seg_cls of SemanticKITTI. (unlabeled, car, bicycle and etc.)
https://github.com/huixiancheng/SENet/blob/438d8093c7e5c65158c2e84901e57b7d8519abb8/modules/losses/boundary_loss.py#L58-L65
Some visualization of GT edges:

I think if you can see clear boundaries in the BEV view, you can take a try.

Thank you for your reply! It helped me a lot.

Hi!
How much mIoU improvement does the boundary loss bring? @huixiancheng
It doesn't seem to converge for my experiments (0.97 -> 0.72 for 24 training epochs).

@jialeli1
I tested it on other models and it brought about 1.8miou improvement. In my experiments, this loss decreases from 0.99 to 0.55 in 30 epochs. Perhaps the weighted value is a matter to consider.


patch: use autobatching by default on CP submission

Patch on the version 0.21 to use autobatching at compute plan submission
When merged, will do a patch release, following this process:

Create a support branch on the version, e.g. support/0.12.x for the version 0.12.0.
Like for a regular feature of bug-fix, create a branch from the support branch for the patch, and then a PR targeting the support branch.
Test the patch by launching the e2e tests for all repos (including frontend and substrafl) to ensure that they are compatible with the patch version. If not, patch them too.
Once the patch has been tested and approved, merge it into the support branch
Create a release from the support branch (use the same process as for any release, except that it is based on the support branch)
The support branch is deleted when support for that version end.
⚠ Don't forget, if necessary, to create a second PR targeting main to integrate the fix in the latest developments. (It most cases a simple cherry-pick is enough)

You may want to patch substra with that commit, I think it's faster with bigger batch size owkin/substra@4d9233b

good point, thank you, will do!


jsonmerge: skip failed tests

Description of changes

Skip failed test in jsonmerge.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

4 packages built:

apio
python310Packages.jsonmerge
python39Packages.jsonmerge
tinyprog

Result of nixpkgs-review pr 191624 run on aarch64-darwin 1

4 packages built:

apio
python310Packages.jsonmerge
python39Packages.jsonmerge
tinyprog


Changes to schema_migrations schema causes migrations to fail in existing applications

The commit 40ddec217ea0ede4df848552518b1f0f50b7239f introduces timestamps to the schema_migrations table. If an ecto application was already in production (or any environment where the database is not frequently dropped / recreated), the schema_migrations table would have already been generated without the inserted_at column and further migrations would fail to run because of a non-existent inserted_at column at the time of row creation (at the end of the migration run).
Considering that the library is pre-1.0, the solution here might just be to manually update the table in your application (that's what I did). In the future, it might be good to consider a solution for seamlessly upgrading old versions of the schema_migrations table.

Yup, I later added a note to the CHANGELOG but we should definitely avoid
it in the long term.
--
José Valim
www.plataformatec.com.br
Skype: jv.ptec
Founder and Lead Developer


on demand feature

I prepared code with on-demand service. What do you think about that?
Changes:

We need ObservableCollection as ItemSource to use automatic refresh.
I keep IList as Type but we need ObservableCollection or derived class for on-demand feature
ItemSource will contain only recent items on begining and all other items will be loaded later.
In example we use list in memory so it's not briliant example but if we use db as source then we should see impact.
everyone who want to use on demand feature need to implement IOnDemandService interface.
There is a problem to inject items to ItemSource from VM (VirtualizingStackPanel issue) so VM will return new data and combobox will add this items using dispather. I enabled this feature by default in example.
I don't found any problems after implement everything in example app.

There is one problematic thing.
When we start example app, type "Eng", remove text and expand the list then order of the items depends on order of the add operation.

in some point control don't control sort so it's not direct issue
we can't add SortDescriptor directly to CollectionViewSource because it will reorder items when user scroll down list so it will be confusing and user can miss some position
to workaround this user can bind property from VM to IsDropDownOpen property and sort observablecollection when it's collapsed. Something similar to this:

static class ObservableCollectionExtension
{
    public static void Sort<TSource, TKey>(this ObservableCollection<TSource> collection, Func<TSource, TKey> keySelector)
    {
        List<TSource> sorted = collection.OrderBy(keySelector).ToList();
        for (int i = 0; i < sorted.Count(); i++)
            collection.Move(collection.IndexOf(sorted[i]), i);
    }
}

Anyway I think that this is correct direction of the changes.

Hi @danielklecha, love the work you have done with this OnDemand service.
My initial feedback, as follows:
It is important that we have a complete working example to demonstrate the implementation of all features and not just the feature that you are working on. I recommend Including a parameter to attach/detach this OnDemand service.
I would also recommend to include a complete working example of recovering this data from a db, which might seem more appropriate in demonstrating the potential of this feature, as opposed injecting the collection from memory.
Apart from the issues that you listed above, there might be another issue where the collection is not populated automatically when dragging the scrollbar as opposed to navigating list with key down etc…

@Impertatore

I added option to disable/enable "on demand" service
There is no problem with order of the items because on each change of the pharase we will clear items list
I tested this version using keys and using scroll and everything goes fine
I think that many people (also me) will load items from db but in this demo I used list in memory to use consistent data

Hi @danielklecha, can you pull the latest changes from this branch, as there seems to be conflicting files with the latest changes to your PR

Hi @danielklecha, @safi-07
As much as I like this OnDemand concept and immediatly see potential benefits, I can’t approve this PR for a few reasons.
There are far too many changes that are proving difficult to understand the key changes you implemented that are relevant to the OnDemand feature.  I realize that this is largely because another team were integrating production changes from the time you initially created your PR and then pushing changes on top of that over the last months has made it difficult to keep the changes in sync.

It would be useful if you cloned the current version of the Master branch as there have been quite a few changes over the last months and create a new clean PR with only relevant changes in a single changeset.

I did however get an opportunity to download and compile your branch locally to identify possible issues in runtime that you might find useful.
General Observation
I see that you have introduced a new textbox control that is visible and takes focus when you detach the existing integrated textbox feature from the Selected Items panel.  This is a different UX experience to one we are enabling with this control in general and I’m not entirely sure that this is the direction we want to take in introducing this type of feature.

What I’d recommend is that you try integrate with the existing UX and not extend with a new textbox control that evidently causes more complexity, especially related to focus.

Issue 101
Bug where the items presented in the recently selected group are duplicated when you uncheck the new option that you introduced “Enable on demand service”
Prerequisite:

Enable on demand service (not checked)
Detach AutoComplete Filter box (not checked)

Steps

Put focus on the Selected Items panel
Type: Italian
Actual Result: You will see that the items in the Selected Items panel are duplicated.

Issue 102
Some behaviors seems inconsistent -> comparing against the existing features for this control, especially when you hit the return key and you have checked the new option that you introduced ‘Detach AutoComplete Filter box’.   The more you play around with this implementation, the more evident issues related to focus become.
Prerequisite:

Enable on demand service (not checked)
Detach AutoComplete Filter box (checked)

Steps (102.a)

Put focus on the Selected Items panel
It immediately changes from readonly to the edit state
The new filter textbox control is visible and focus is moved to it.
Items are already populated in the Dropdown Menu.
Use the arrow key to select a few items and add them to the Selected Items panel.
Now, hit the return key a few times…
Actual Result: Items in the Selected Items panel are removed unexpectedly.

.
Steps (102.b)

Put focus on the Selected Items panel
It immediately changes from readonly to the edit state
The new filter textbox control is visible and focus is moved to it.
Items are already populated in the Dropdown Menu.
Use the arrow key to select a few items and add them to the Selected Items panel.
Now, hit the delete key

Actual Result: Focus remains in the new Filter text box, but items in the Selected Items panel are deleted, which seems unexpected.
Observation: You might need to revise this workflow and use-case in general with this new textbox filter control.


Move cloud auth files into the config directory

Documentation for https://github.com/api3dao/airnode/issues/1329

@kolenic-martin I am in process of updating the tutorial zip file for this change as well. You will see it come across in GitHub issue https://github.com/api3dao/api3-docs/issues/900

Hi @wkande, I've checked the preview site but I do not seem to see the changes - everything is supposed to be in the root directory, correct?

@kolenic-martin those screenshots are from v0.7 Airnode not v0.8

That was the preview site, which only has v0.7 as the latest version, the
live version seems fine now that I checked. Sorry about the confusion.
Dňa st 20. 7. 2022, 9:24 Derek Croote @.***> napísal(a):

@kolenic-martin https://github.com/kolenic-martin those screenshots are
from v0.7 Airnode not v0.8
—
Reply to this email directly, view it on GitHub
https://github.com/api3dao/api3-docs/issues/892#issuecomment-1189923726,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGYB46ZV2Y4M4YH2SNE22DVU6SUNANCNFSM53OAO2OQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

That was the preview site, which only has v0.7 as the latest version

It's true that v0.7 is the latest on the preview site, but for testing it does have v0.8, you just have to edit the URL manually in the address bar.

Tbh that is not the most intuitive method to test but you're right, I don't
know why I didn't realize that before since I'd done that previously.
Morning brain I guess.
Dňa st 20. 7. 2022, 9:32 Derek Croote @.***> napísal(a):

That was the preview site, which only has v0.7 as the latest version
It's true that v0.7 is the latest on the preview site, but for testing it
does have v0.8, you just have to edit the URL manually in the address bar.
—
Reply to this email directly, view it on GitHub
https://github.com/api3dao/api3-docs/issues/892#issuecomment-1189930349,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGYB457E4DQ3FFOJLOTI7LVU6TRPANCNFSM53OAO2OQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Updating cache - Arrays of object in store - after removing array item an empty object remains

I'm updating query of parent component after removing an item. The problem I'm facing is with updating store: removed item is deleted, but the index in array remains (screenshots below). This causes a lot of problems with rerendering components (Chrome dev-console also attached).
After all deleted component stays rendered.
Code:
          // inside component method
          const parentDirQuery = {
            query: directoryQuery,
            variables: {
              id: this.file.parentId
            }
          };
          this.$apollo.mutate({
            mutation: removeFileMutation,
            variables: {
              input: {
                id: fileId
              }
            },
            update(store, { data: { removeFile }}) {
              try {
                const storeData = store.readQuery(parentDirQuery);
                const newAssets = storeData.getDirById.assetsPage.assets.filter((file) => {
                  return file.id !== removeFile.id;
                });
                storeData.getDirById.assetsPage.assets = newAssets;
                storeData.getDirById.assetsPage.totalCount = storeData.getDirById.assetsPage.totalCount - 1;
                parentDirQuery.data = storeData;
                store.writeQuery(parentDirQuery);
              } catch (err) {
                console.log('err', err);
              }
            },
            optimisticResponse: {
              removeFile: {
                id: fileId,
                __typename: 'RemoveFilePayload'
              }
            }
          }).then((response) => {
            console.log(response, 'res');
          }).catch((error) => {
            console.error(error, 'error');
          });

Screenshots:
Before removing 16:

After removing 16:

Probably related to: https://github.com/apollographql/apollo-client/issues/899

I think it could be related to fetchMore feature.  When I'm trying to update query data I'm using this:


systemd: add environmentfile

Addresses the issue raised in #14663 by sourcing and using the environment variable defined in /etc/sysconfig/docker.
Fixes #14663

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix/systemd-service-environmentfile" git@github.com:BrianHicks/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

sorry this has been opened numerous times we are going to rewrite docs to talk about using a systemd dropin file instead so we do not have to maintain seperate systemd fines with everyonnes flavor on env file

@jfrazelle I'm not sure what you mean. This is using the environment file that ships with the Docker RPM, it's just ignored right now for some reason. Not a bug?

we do not ship an env file
On Mon, Jul 27, 2015 at 11:29 AM, Brian Hicks<EMAIL_ADDRESS>wrote:

@jfrazelle https://github.com/jfrazelle I'm not sure what you mean.
This is using the environment file that ships with the Docker RPM, it's
just ignored right now for some reason. Not a bug?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/15043#issuecomment-125296911.

you can see comments here for more information
https://github.com/docker/docker/pull/14513#issuecomment-125009350
On Mon, Jul 27, 2015 at 11:30 AM, Jessie Frazelle<EMAIL_ADDRESS>wrote:

we do not ship an env file
On Mon, Jul 27, 2015 at 11:29 AM, Brian Hicks<EMAIL_ADDRESS>wrote:

@jfrazelle https://github.com/jfrazelle I'm not sure what you mean.
This is using the environment file that ships with the Docker RPM, it's
just ignored right now for some reason. Not a bug?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/15043#issuecomment-125296911.

Well, ok, I get the deal now. That's fine, and I can deal with that on our end. Drop ins are easier than scripting regex replacements anyway :+1:
But, you do ship an environment file. rpm -ql docker-engine lists /etc/sysconfig/docker, which is where other_arg is coming from. This is from the docker-engine 1.7.1-1 package that's in the shiny new RPM remote. Would it help for me to open a separate issue to see about removing that file? I'm not familiar enough with the packaging process to remove it properly myself.

ping @jfrazelle about /etc/sysconfig/docker - it's shipped in your package, should I open another ticket?

Where is it shipped
On Wednesday, September 9, 2015, Brian Hicks<EMAIL_ADDRESS>wrote:

ping @jfrazelle https://github.com/jfrazelle about /etc/sysconfig/docker

it's shipped in your package, should I open another ticket?

—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/15043#issuecomment-138905759.

The official 1.7.1 Docker package has /etc/sysconfig/docker as a listed file. Verify with rpm -qlp docker-engine-1.7.1-1.el7.centos.x86_64.rpm. The 1.8.1 package has this file as well. I believe these files are managed by docker-engine.spec, but don't know enough about the Docker build system to submit a patch myself.

Yes remove it then
On Wednesday, September 9, 2015, Brian Hicks<EMAIL_ADDRESS>wrote:

The official 1.7.1 Docker package
http://yum.dockerproject.org/repo/main/centos/7/Packages/docker-engine-1.7.1-1.el7.centos.x86_64.rpm
has /etc/sysconfig/docker as a listed file. Verify with rpm -qlp
docker-engine-1.7.1-1.el7.centos.x86_64.rpm. The 1.8.1 package
http://yum.dockerproject.org/repo/main/centos/7/Packages/docker-engine-1.8.1-1.el7.centos.x86_64.rpm
has this file as well. I believe these files are managed by
docker-engine.spec
https://github.com/docker/docker/blob/634a848b8e3bdd8aed834559f3b2e0dfc7f5ae3a/hack/make/.build-rpm/docker-engine.spec,
but don't know enough about the Docker build system to submit a patch
myself.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/15043#issuecomment-138947739.

It's still shipped because it's used by sysvinit so our RPMs still need to
include it, IIRC.

Oh ya that's why
On Wednesday, September 9, 2015, Tianon Gravi<EMAIL_ADDRESS>wrote:

It's still shipped because it's used by sysvinit so our RPMs still need to
include it, IIRC.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/15043#issuecomment-138949382.

ah, in that case I’ll leave it alone. Thanks for the info, @tianon.

We can add an if for not with_systemd that var is already populated and not
add the file
On Wednesday, September 9, 2015, Jessie Frazelle<EMAIL_ADDRESS>wrote:

Oh ya that's why
On Wednesday, September 9, 2015, Tianon Gravi<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

It's still shipped because it's used by sysvinit so our RPMs still need to
include it, IIRC.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/15043#issuecomment-138949382.

ok then i will make a patch with the if ;)
On Wed, Sep 9, 2015 at 8:41 AM, Brian Hicks<EMAIL_ADDRESS>wrote:

ah, in that case I’ll leave it alone. Thanks for the info, @tianon.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/15043#issuecomment-138950341.

thanks, I appreciate it. I'm glad we could come to a resolution on this. :+1:


Converted the file system console methods to be engine-based

Converted the file system console methods to be engine-based that the console functions call to. This doesn't impact usage or functionality, but enables the functions to be used in the engine as well.

@Areloch I think we should leave this out of 3.8. Needs fixing but it's not critical.

Yeah, we can bump it to 3.9.

This needs to be re-implemented.


Doesn't boot on my PC.

It works fine on the vm and I love the system. I wanted to install it on my PC.
I tried also the ISO on sourceforge and also creating my own by cloning the repo and all.
Same problem:
An error occurred in stage 1 of the boot process, which must mount the root filesystem on /mnt-root and then start stage 2.
Press one of the following keys:
i) to launch an interactive shell
f) to start and interactive shell having pid 1 (needed if you want to start stage 2's init manmually
r) to reboot immediately
*) to ignore the error and continue

I can boot and install the normal nixos just fine. Is  there any solution to this problem or any way at all to maybe install snowflake using the nixos' iso to boot fist?
Thank you very much.
I would also very like to contribute to the project as I love rust...

No worries. The iso didn't boot and show that error with ventoy on a 128gb card.
Using balenaetcher and putting it in a 8gb usb card everything works fine. You can close I guess.
Sorry to have bothered


PicoW does not properly set hostname

The pico hostname is not currently being set to atomvm-{MACADDRESS} as it should be. The hostname is always being set to PicoW. The same behavior is observed if a hostname is supplied in the wifi config. This is consistent when in STA and STA+AP mode.
This situation makes for routing problems if multiple picow are on the same network.

After some investigating, I realize this feature has not yet been enabled on the picow. I saw the get_default_device_name function an assumed it was used later to set the hostname. In fact this is only used as the default ssid in AP mode if no ssid is supplied.

I'm not sure what setting the hostname means. Do we run mDNS on the Picow?

Sorry, I am referring to the DHCP client hostname, the name that resolves to the assigned IP address.

When there are multiple pico connected to a wireless network, they all request the same hostname ("PicoW") from the DHCP server, so pinging a pico by name will not work, it will only work if you use the assigned IP.


OCPBUGS-12699: Set lowercase proxy env vars also

/jira refresh

/hold
depends on https://github.com/openshift/api/pull/1659

/retest

/close

/open

Opening this back up

/help

/reopen


GitHub Api Limit reached

I got an Error 500 while logging into solder:
exception 'Github\Exception\ApiLimitExceedException' with message 'You have reached GitHub hour limit! Actual limit is: 5000' in C:\Users\lawall\Desktop\laravelTests\TechnicSolder\vendor\knplabs\github-api\lib\Github\HttpClient\Listener\ErrorListener.php:46

This is probably due to you installing and rate limiting yourself. Try again tomorrow. I will in the meantime have to catch the error so the application will at least be useable in the future

This should be resolved now as of v<IP_ADDRESS>


int64

Hi,
Your code uses methods "writeUInt64BE" and "writeInt64BE" (with matching read methods) for the buffer object, but this is not part of the nodejs standard buffer object. I think your tests don't actually hit those lines of code because all int64 objects get treated as if they are doubles.
var a = Date.now();
console.log("using a bit operator");
console.log("%j is a double: %j", a, (a << 0) !== a);
console.log("using Math.floor");
console.log("%j is a double: %j", a, Math.floor(a) !== a);
I'm not sure of the correct work around for this since javascript doesn't really support uint64 out of the box...

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

under the 'encode' method, you see the following code. This doesn't work for ints over 32bits, probably because bit shift operators are meant for 32bit values (or so I've heard. I'm no expert).
// Floating Point
if ((value << 0) !== value) {
buffer[offset] =  0xcb;
bops.writeDoubleBE(buffer, value, offset + 1);
return 9;
}
Anyway, if you comment that out, and add a Math.floor for safety, you can then use the following code to encode ints up to +- 2^53-1 as 64bit uints and 64bit ints. I have  forked version at https://github.com/parnesen/msgpack-js that implements this, though it sacrifices support for floats, since I don't need them and I haven't sorted out a proper floating point test.
var bytePositions = [
0x1000000000000,
0x10000000000,
0x100000000,
0x1000000,
0x10000,
0x100,
0x1
]
/** reads an unsigned int of max value 2^53-1 from a uint64 binary representation **/
function readUint53(bytes, offset) {
var value = 0;
for(var ii = 1; ii < 8; ii++) { //we can skip the most significant byte
value = (value * 0x100) + bytes[offset + ii];
}
if (value ><PHONE_NUMBER>740991) throw "Overflow";
return value;
}
/** reads an signed int of max/min value +- 2^53-1 from a big endian two's complement int64 binary representation **/
function readInt53(bytes, offset) {
var num;
if(isNegative(bytes, offset)) {
var copy = copyBytes(8, bytes, offset);
negate(copy, 0);
var absValue = readUint53(copy, 0);
num = -absValue;
}
else {
//we can treat bytes this as a UINT because in two's complement notation, positive numbers much
//smaller than MaxUint64 are represented as just themselves.
num = readUint53(bytes, offset);
}
return num;
}
function writeUint53(value, buffer, offset) {
value = Math.floor(value);
if (value ><PHONE_NUMBER>740991) throw "Overflow";
buffer[offset] = 0x0; //most significant bit is always zero
var accumulator = 0;
for(var ii = 1; ii < 8; ii++) {
buffer[offset + ii] = Math.floor((value / bytePositions[ii - 1]) - accumulator);
accumulator = (accumulator + buffer[offset + ii]) * 0x100;
}
}
function writeInt53(value, buffer, offset) {
if(value >= 0) {
//we can treat this as a UINT because in two's complement notation, positive numbers much
//smaller than MaxUint64 are represented as just themselves.
writeUint53(value, buffer, offset);
}
else {
writeUint53(-value, buffer, offset);
negate(buffer, offset);
}
}
function copyBytes(count, buffer, offset) {
var bytes = new Array(count);
for(var ii = 0; ii < 8; ii++) {
bytes[ii] = buffer[offset + ii];
}
return bytes;
}
/** determines whether the given big endian, two's complement byte representation of a 64 bit integer is negative **/
function isNegative(bytes, offset) {
//check the most significant bit.
return (bytes[offset] & 0x80) !== 0;
}
/** negates the given big endian byte representation of a 64 bit integer by taking the two's complement **/
function negate(bytes, offset) {
var overflow = 1;
for(var ii = 7; ii >= 0; ii--) {
var byte = bytes[offset + ii];
var onesCompliment = ~byte & 0xFF;
var twosComplement = onesCompliment + overflow;
overflow = (twosComplement & 0x100) == 0 ? 0 : 1;
var negated = twosComplement & 0xFF;
bytes[offset + ii] = negated;
}
}


Should we warn when users are creating component without using an observer method ? is is even possible ?

Thanks. At least when doing so would skip optimizations that are likely to cause issues.


Accessing AppWindow property on Window is expensive

Describe the bug
The Window class doesn't cache the AppWindow object, so this is showing up in our app traces
for an app that needs to access the actual HWND it is necessary to get the AppWindow object so that you can go from WindowID -> HWND
Steps to reproduce the bug

write an app
access AppWindow on the window

Expected behavior
i would expect this to be a simple property access and just add ref the pointer it has
Screenshots

NuGet package version
WinUI 3 - Windows App SDK 1.4.4: 1.4.231219000
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

Out of curiosity, how does this compare to using IWindowNative to get the handle? This would be WinRT.Interop.WindowNative for C#.


doesn't work in browserify environment

I'm trying to use the plugin with browserify, without much success, though.
The reason, seems to be, that in browserified apps root is not a window, but rather module object.
Here the .addEventListener is always undefined, so plugin in not initialized correctly. My naive try to change to window.addEventListener didn't help, since root used in many other places.
 Maybe there are some workarounds with browserify-shim or something?

Known issue. root SHOULD be window. Working to figure out how to address this, as Browserify is the one outlier here. Other UMD modules work fine, and the model for this script wrapper is based on the official UMD spec on GitHub.
See also: https://github.com/cferdinandi/smooth-scroll/pull/160

So far, my solution is. I've added browserify-shim, with following configuration,
  "browser": {
    "smooth-scroll": "./node_modules/smooth-scroll/dist/js/smooth-scroll.js"
  },
  "browserify-shim": {
    "smooth-scroll": "smoothScroll"
  },

my code,
var $ = require('jquery');
var smoothScroll = require('smooth-scroll');

$(function () {
	smoothScroll.init({
		speed: 700,
		easing: 'easeInOutCubic',
		updateURL: false
	});
});

<a data-scroll href="#get-started" class="btn btn-xlg btn-green">...</a>

Works as expected. But it's a more workaround, rather the solution.
From my side, root is window in UMD is wrong. As I mentioned above, root is module not window. With browserify-shim this is actually windows, that's why it works fine.
The package has to be corrected to use windows explicitly. If you are fine with that, I can submit a PR.

Sorry, I miswrote. You are correct. this should be passed in as window in Browserify, and it's not. The shim strikes me as something folks who want to Browserify should implement themselves.

I'm not sure that #160 is exactly right since it changes UMD signature.. But it almost does what it says, changes the root to window. But, it should not be done this way..

I agree, @alexbeletsky. It also breaks other uses of UMD. One shouldn't redefine root in the module.

Possible solution:
Source: https://gist.github.com/ifandelse/4617996

See also:

http://stackoverflow.com/questions/19946705/advice-to-resolve-window-dependency-when-running-in-node-js
http://stackoverflow.com/questions/28610796/browserify-universal-module-definition-browser-node-different-dependencies

Yeah, it's actually quite a smart trick and really easy to integrate!
+1 for it :)

Yeah, it's actually quite a smart trick and really easy to integrate!
+1 for it :)

Since I don't use Browserify myself, could you do me a HUGE favor and test it for me? If it works, I'll incorporate into the official script.

Submitted #164

I just saw. Thank you so much!

@alexbeletsky Thanks again for your help with this. All merged in and set to go. I added you to the list of contributors in the readme file.
Quick question: I've have some folks say they can't use this module with AMD/Common JS module tools because I don't currently have tagging enabled, but you seem to using it without issue. Is there something else I need to be doing? How did you make things work?

@cferdinandi you are welcome, thanks a lot for the great library!
I'm using that without issues, fetching your package not from npm but github directly, exactly as it's in your README file,
$ npm install cferdinandi/smooth-scroll

Then, in my package.json I have something like
    "smooth-scroll": "git://github.com/cferdinandi/smooth-scroll"

What I think guys are talking about is semver support. As soon as you upload the new version, you need to tag it and push that tags. For the current version, all you need to do is,
$ git tag v5.3.7
$ git push --tags

Each time you upgrade, you should not forget to push new tag :)
ps. Will try new version tonight.

@alexbeletsky Thanks! I'm going to have to retroactively add some tags. Cheers!


Story source shows wrong info when addon is used

Whenever I use a storybook-state addon in my storybook, Story Source field shows information about the state instead of showing the info about the code.

Actual Story Source
.add(
    'Checkbox',
    withState({ checked: false })(({ store }) => (
      <Checkbox
        label={text('Label', 'Example label')}
        onChange={checked => store.set({ checked })}
        checked={store.state.checked}
        disabled={boolean('Disabled', false)}
        description={text('Description', 'Example description')}
      />
    ))
  );

Any updates on this?

Is there a fix or workaround for this?

I'm also having the same issue...

Is there a fix or workaround for this?
You can use useState hook inside stories


Investigate switching to vscode proper

A lot of features related with search are supported by vscode. We should investigate if it is possible to implement the platform specific parts of vscode to run completely in the browser.

#36 - Workspace symbol provider
#20 - Search by filename
#29 - basic UI and start page
Tabs
File browser

A good starting point seems to be https://github.com/spiffcode/ghedit

It would be really nice to get tabs + file browser, so big 👍 from me. However, I don't know how complicated this would be to add to our build.

Is this a realistic goal? I believe it might be better to investigate how to create "Open file" actions that open the same search bar as the DocumentSymbolProvider.


Locking resource groups

Is there any chance that the Java SDK will support adding and removing locks on Azure resources ?
/Dev

may be able to take a look when looking into Monitor + policy

done for v1.4


⚠ SceneTime has degraded performance

In 3acf923, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 2031 ms

Resolved: SceneTime performance has improved in c7c621f after 14 minutes.


Respect capitals

Introduce the metadata table to persist information of original entity attributes names. This same table will be used for different metadata associated to each table.

codeclimate is my fault :)

Closes #30


RN 0.56 - issue For components that can render Text

node, npm, react-native, react and native-base version
node v8.11.1, rn 0.56.0, react 16.4.1, NB 2.7.2
Expected behaviour
Able to pass strings directly to certain components, eg. `Text
Actual behaviour
Not able to do that - get a redbox error
Invariant Violation: Invariant Violation: Invariant Violation: Invariant Violation: Text strings must be rendered within a <Text> component.
Steps to reproduce should include code snippet and screenshot
attempt to reproduce, for example,  the Form examples from the documentation on RN 0.56
Is the bug present in both iOS and Android or in any one of them?
Both
Any other additional info which would help us debug the issue quicker.
This is NOT a dupe of the earlier issue (https://github.com/GeekyAnts/NativeBase/issues/186) seen by some people with accidental characters from copying and pasting. This is an issue introduce in RN 0.56, and which is causing issues for some other libs (https://github.com/iyegoroff/react-native-text-gradient/issues/11) too, See https://github.com/facebook/react/pull/13211, which hopes to resolve the issue. Until then, not sure there's much NB can do about it, but putting it out there for anyone googling for the issue and so the NB team is aware of it.
That same library linked above have a temporary patch to remove the error in the meantime, too, on their github readme, https://github.com/iyegoroff/react-native-text-gradient#usage-with-rn--0560

you need to share example

Closing this tomorrow in case of no response

Invariant Violation: Text strings must be rendered within a  component.
This issue still exists, please have a look into this.

Invariant Violation: Text strings must be rendered within a component.
This issue still exists, please have a look into this.

please delet
// Your main content goes here
.


AB#4960

Proposed changes

Related issues

Checklist

[x] I consider the submitted work as finished
[x] I tested the code for its functionality
[ ] I wrote test cases for the relevant uses case
[ ] I added/update the relevant documentation (either on github or on notion)
[ ] Where necessary I refactored code to improve the overall quality

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

The local build looks good, I think @DallasP9124 is out so @r-joyce check this out and merge if you can also delete the branch and close the related card: 4960. Thanks!

@r-joyce please merge this and please delete the branch after and close the related ticket 4690. Thanks!


Speaker info for WebVTT subtitles

We're using WebvttParser() to parse WebVTT transcripts, which internally uses WebvttCueParser() to parse cues.
While WebvttCueParser.parseCueText(...) provides the payload with style formatting, it removes the speaker identifiers or the TAG_VOICE.
Can we get an in-built support for speaker info within the cues of WebVTT transcripts?

I guess you're referring to this? https://www.w3.org/TR/webvtt1/#webvtt-cue-voice-span
We do have some code already that parses <v[voice="foo"]> tags in order to resolve the associated styles: https://github.com/search?q=repo%3Aandroidx%2Fmedia+path%3Avtt+voice&type=code
But the voice information isn't directly exposed in the resulting Cue object.
I suspect this would need to be exposed using a 'custom span' in Cue.text, like we do for Japanese rubies: https://github.com/androidx/media/blob/release/libraries/common/src/main/java/androidx/media3/common/text/RubySpan.java
I'll mark this as an enhancement. I'm afraid we are unlikely to work on this ourselves soon, but we would consider a high quality PR implementing this.

Closing this because https://github.com/androidx/media/pull/1652 has been merged - thanks!


Ability, Item, and Move Effect prose entries have "XXX" placeholder values

Some of the prose entries for abilities, items, and move effects are placeholder values. For example, in ability_prose.csv:
ability_id,local_language_id,short_effect,effect
233,9,XXX new effect for neuroforce,XXX new effect for neuroforce

Patches welcome :)

Yeah, I planned on submitting a patch, but I created this issue in case I forgot. What are the preferred data sources? I can copy them manually from Bulbapedia, unless there are better places.

It's good to look at a variety of sources. Smogon is generally pretty reliable for move effects. Bulbapedia is okay too, though take anything they say with a grain of salt. Manual testing may be in order if you find contradictory sources.
cc @eevee, who wrote most of the original effects.


Repeating timers use first node's duration when nodes were added via timer_set_script

This is because script execution fires after determining the next sequence duration in fuwa_run.

[057e452105e79ecad28316d3b21ce919eb3aff25]


Distinguishing between libraries or objects that have the same name

I was trying to use your app to find out who's using the JS components of Cascade Framework. Unfortunately, the results were useless :

Cascade Framework uses an object named App, which takes up the role of a front controller and is used mostly for centralized asynchronous JS loading (including polyfills for older browsers). As this is a pretty common name, the results were useless.
Cascade Framework uses an object named Detector, which is really just a merger of Modernizr and jQuery.browser. It is used mostly to detect which polyfills to load, to add helper classes to the HTML and to dynamically load either jQuery 1 or jQuery 2. As this is also a pretty common name, the results were useless as well.
Cascade Framework uses an object named $.fn.cascade. This object adds some JS behaviors to the DOM for eg. user interaction. I would have thought that this object was specific enough to Cascade Framework to only get correct results, but again the results were useless. For example, some of the results involved a WooCommerce plugin for Wordpress named Cascade Filter Importer.

While the current implementation may be useful to track use of libraries as popular as jQuery, Underscore, LoDash or Angular or libraries with very exotic names, I'd expect this issue to apply to most other libraries.
I believe libscore has a lot of potential, but only if this issue is solved. If not, the accuracy of the results will be too unreliable for most use cases for libscore to be useful.
Some suggestions on how to fix this issue :

Detect the presence of a version property, and authors property or any other property that provides meta-information about a library and compare its value with other occurrences of an object

Compare the number of properties between libraries

Test whether two libraries have the same first X properties.

Compare the filesize of libraries

Compare the Constructors or Prototypes of objects

Yup, good idea. Problem is that archiving and searching this requires quite a bit of server overhead. For the time being, if I see duplicates that are each sufficiently popular to warrant a distinction on Libscore, I'm happy to do it manually. I'll be doing this for underscore/lo-dash.
Thanks so much for this. Sorry about the slow response :)


[ffi] pthread_mutex_t variable defined in main causing dlopen failed: cannot locate symbol error

I loaded the pre-compiled libmylib.so  including the libc++_shared.so in flutter android.
Inside the main.cpp
I have a variable defined like the following.
pthread_mutex_t stratum_work_lock;
I created the ffi for main only.
int main(int argc, char *argv[])
When running the .so file, I got this error
 dlopen failed: cannot locate symbol "stratum_sock_lock"
I wonder what's causing the error or if I'm missing something.
I only need to exposed the main method as it's all I need to call.
Any pointers would be appreciated.

Thank you for the response. The variable is declared and defined.
The binary was working as expected using the Process library but the equivalent .so file is not. At first the DynamicLibrary complained that the libc++_shared.so cannot be found. Then I added the one from Android NDK, after running again, this is the error I got.


batch mutations are calling listeners with inconsistent state

Hello,
I'm trying to use the derive util but I've ran into an issue with the following code:
/* eslint-disable no-console */
import assert from 'assert'
import { derive } from 'valtio/utils'
import { proxy, subscribe } from 'valtio/vanilla'

const state = proxy({
  tree: {
    root: ['foo'],
    children: { foo: { type: 'bar' } } as Record<string, { type: string }>
  }
})

const derived = derive({
  list: (get) => {
    const tree = get(state.tree)
    return tree.root.map(r => tree.children[r].type)
  }
}, { sync: true })

const foo = JSON.parse(JSON.stringify(state.tree))
foo.children.bar = { type: 'foo' }
foo.root.unshift('bar') // this change his applied first, without the previous one, which cause the derived.list to crash
Object.assign(state.tree, foo)

// with sync:true, this assert is failing
assert.deepStrictEqual(derived.list, ['foo', 'bar'])

I need to use sync: true with derive; but with sync enabled, when applying mutations with Object.assign, Valtio is calling derived properties with inconsistent state (e.g. root updated, but children isn't) which cause the getter to crash.
Do you have any workaround to fix this issue?
Thank you

Well, that's why sync: false is default and recommended.
If you need sync: true for some reason, you want to memoize the derive function to avoid crashing.
const memo = (fn) => {
  let last
  return (...args) => {
    try {
      return (last = fn(...args))
    } catch {
      return last
    }
  }
}

const derived = derive({
  list: memo((get) => {
    const tree = get(state.tree)
    return tree.root.map(r => tree.children[r].type)
  })
}, { sync: true })

(untested)
Alternatively, you may want to try proxyWithComputed which is kind of "sync" by default.

Seems to work fine with memo or proxyWithComputed thank you


->download(xls) only downloads one file.

Hello, I am trying to download my excel sheets, but the problem is I have multiple. So I stored them in an array, however an issue is when I use my code like this
$sheets = $this->sheets; foreach($sheets as $sheet){  $sheet->download('xls'); }
It only downloads one. I have multiple sheets stored as LaravelExcelWriter in an array, but for some reason it only downloads one.

If you have multiple sheets, they are sheets within 1 file. You cannot download them as separate files. They only way you can do this is by storing multiple files and downloading them as a zip.


Updating Gradle to 2.1.3

@RoboErikG

This change is

Review status: 0 of 2 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Slack crashes with NIXOS_OZONE_WL=1 enabled

Describe the bug
Slack crashes with NIXOS_OZONE_WL=1 option activated
Steps To Reproduce
Steps to reproduce the behavior:

Start slack with option NIXOS_OZONE_WL=1
Start a call
Start screensharing and select a desktop
Slack crashes with libwayland: xdg_surface@78: error 3: xdg_surface has never been configured

Expected behavior
Screensharing starts.
Additional context
Log output
[07/08/22, 11:11:25:093] info: [SCREENS] (T8MMQ651A) Available screens:
-- | ----- | ------ | - | - | ----------- | --------
id | width | height | x | y | scaleFactor | rotation
-- | ----- | ------ | - | - | ----------- | --------
41 | 1920  | 1080   | 0 | 0 | 1           | 0
43 | 2560  | 1440   | 0 | 0 | 1           | 0

[07/08/22, 11:11:25:260] error: SCREENS (T8MMQ651A) Could not find matching display for screen 0 with id
[07/08/22, 11:11:25:266] error: SCREENS (T8MMQ651A) Could not find matching display for screen 1 with id
[07/08/22, 11:11:25:298] warn: (T8MMQ651A) No toast queue found for team T8MMQ651A
[07/08/22, 11:11:25:300] warn: (T8MMQ651A) No toast queue found for team T8MMQ651A
[07/08/22, 11:11:25:516] error: SCREENS (T8MMQ651A) Could not find matching display for screen 0 with id
[07/08/22, 11:11:25:518] error: SCREENS (T8MMQ651A) Could not find matching display for screen 1 with id
[07/08/22, 11:11:26:015] info: [API-Q] (T8MMQ651A) 16362376-1657271485.974 users.interactions.list called with reason: huddle-discovery-calls
[07/08/22, 11:11:26:015] info: [API-Q] (T8MMQ651A) 16362376-1657271485.974 users.interactions.list is ENQUEUED
[07/08/22, 11:11:26:015] info: [API-Q] (T8MMQ651A) 16362376-1657271485.974 users.interactions.list is ACTIVE
[07/08/22, 11:11:26:016] error: SCREENS (T8MMQ651A) Could not find matching display for screen 0 with id
[07/08/22, 11:11:26:017] error: SCREENS (T8MMQ651A) Could not find matching display for screen 1 with id
[07/08/22, 11:11:26:163] info: [API-Q] (T8MMQ651A) 16362376-1657271485.974 users.interactions.list is RESOLVED
[07/08/22, 11:11:26:461] info: [FREE-WILLY-SDK] (T8MMQ651A) API/DefaultAudioVideoFacade/d0f3f13a-bcd5-433f-8bcb-24c5e7120706/bfee086f-de20-7ffb-a39b-1cda5fd710cb/getRTCPeerConnectionStats null
[07/08/22, 11:11:27:263] info: [RTM] (T8MMQ651A) Processed 1 recent_status_changed event(s) over 60.30ms
[07/08/22, 11:11:27:265] info: [RTM] Setting a timeout of 34 ms to process more rtm events
[07/08/22, 11:11:27:300] info: [RTM] Waited 34 ms, processing more rtm events now
[07/08/22, 11:11:28:461] info: [FREE-WILLY-SDK] (T8MMQ651A) API/DefaultAudioVideoFacade/d0f3f13a-bcd5-433f-8bcb-24c5e7120706/bfee086f-de20-7ffb-a39b-1cda5fd710cb/getRTCPeerConnectionStats null
[07/08/22, 11:11:28:988] info: [(?)] Screenshare start: screen-picker, screenId = screen:424:0, zoomLevel = 0
[07/08/22, 11:11:29:008] info: [FREE-WILLY-SDK] (T8MMQ651A) API/DefaultAudioVideoFacade/d0f3f13a-bcd5-433f-8bcb-24c5e7120706/bfee086f-de20-7ffb-a39b-1cda5fd710cb/realtimeSendDataMessage
[07/08/22, 11:11:29:009] info: [FREE-WILLY-SDK] (T8MMQ651A) API/DefaultAudioVideoFacade/d0f3f13a-bcd5-433f-8bcb-24c5e7120706/bfee086f-de20-7ffb-a39b-1cda5fd710cb/chooseVideoInputDevice null
[07/08/22, 11:11:29:009] info: [FREE-WILLY-SDK] (T8MMQ651A) video send has ideal max bandwidth 1400 kbps
[07/08/22, 11:11:29:010] info: [FREE-WILLY-CONTENT-SH] (T8MMQ651A) Starting screen share with zoomLevel = 0
[07/08/22, 11:11:29:011] info: [FREE-WILLY-CONTENT-SH] (T8MMQ651A) Starting unconstrained content share with chime API's startContentShareFromScreenCapture
[07/08/22, 11:11:29:011] info: [FREE-WILLY-SDK] (T8MMQ651A) API/DefaultAudioVideoFacade/d0f3f13a-bcd5-433f-8bcb-24c5e7120706/bfee086f-de20-7ffb-a39b-1cda5fd710cb/setContentAudioProfile {"audioBitrateBps":128000}
[07/08/22, 11:11:29:012] info: [FREE-WILLY-SDK] (T8MMQ651A) API/DefaultAudioVideoFacade/d0f3f13a-bcd5-433f-8bcb-24c5e7120706/bfee086f-de20-7ffb-a39b-1cda5fd710cb/startContentShareFromScreenCapture
[07/08/22, 11:11:29:028] info: [FREE-WILLY-SDK] (T8MMQ651A) API/DefaultDeviceController/chooseVideoInputDevice null
[07/08/22, 11:11:29:029] info: [FREE-WILLY-SDK] (T8MMQ651A) API/DefaultAudioVideoFacade/d0f3f13a-bcd5-433f-8bcb-24c5e7120706/bfee086f-de20-7ffb-a39b-1cda5fd710cb/stopLocalVideoTile
[144006:0708/111129.079496:ERROR:wayland_event_watcher.cc(25)] libwayland: xdg_surface@78: error 3: xdg_surface has never been configured

Trace/breakpoint trap (core dumped)

Even if Slack is started with this command it crashes.
slack --ozone-platform=wayland --enable-features=UseOzonePlatform,WebRTCPipeWireCapture
Notify maintainers
@mmahut
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.50, NixOS, 22.05 (Quokka), 22.05.1490.316b762afdb`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.8.1`
 - channels(dschaefer): `"home-manager-22.05.tar.gz"`
 - channels(root): `"nixos-22.05, nixos-unstable"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I just tested it again with the following command and what should I write... it now works as expected and is stable :tada:
slack --enable-features=WebRTCPipeWireCapturer %U
Home Manager overlay to make it more convenient.
  nixpkgs.overlays = [(
    self: super: {
      slack  = super.slack.overrideAttrs (old: {
        installPhase = old.installPhase + ''
          rm $out/bin/slack

          makeWrapper $out/lib/slack/slack $out/bin/slack \
          --prefix XDG_DATA_DIRS : $GSETTINGS_SCHEMAS_PATH \
          --prefix PATH : ${lib.makeBinPath [pkgs.xdg-utils]} \
          --add-flags "--enable-features=WebRTCPipeWireCapturer %U"
        '';
      });
    };
  )];

I've came across the issue yesterday and made a PR for it, also I can't reproduce the problem issue of this issue anymore so when merged I would like to going forward, closing this? :)


Error during upgrade

Any ideas on why the /etc/gitlab/gitlab.rb is throwing a syntax error? During the upgrade process?

apt update
apt upgrade
dies with below error

I really need help getting this working again.
Installing Cookbook Gems:
Compiling Cookbooks...
Recipe: gitlab::default
  * directory[/etc/gitlab] action create (up to date)

  ================================================================================
  Recipe Compile Error in /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/recipes/default.rb
  ================================================================================

  SyntaxError
  -----------
  /etc/gitlab/gitlab.rb:760: syntax error, unexpected end-of-input, expecting '}'

  Cookbook Trace:
  ---------------
    /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/recipes/default.rb:35:in `from_file'

  Relevant File Content:
  ----------------------
  /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/recipes/default.rb:

   28:    group "root"
   29:    mode "0775"
   30:    action :nothing
   31:  end.run_action(:create)
   32:
   33:  Gitlab[:node] = node
   34:  if File.exists?("/etc/gitlab/gitlab.rb")
   35>>   Gitlab.from_file("/etc/gitlab/gitlab.rb")
   36:  end
   37:  node.consume_attributes(Gitlab.generate_config(node['fqdn']))
   38:
   39:  if File.exists?("/var/opt/gitlab/bootstrapped")
   40:  	node.set['gitlab']['bootstrap']['enable'] = false
   41:  end
   42:
   43:  directory "/var/opt/gitlab" do
   44:    owner "root"

  Platform:
  ---------
  armv7l-linux-eabihf

  Running handlers:
log writing failed. closed stream
  Running handlers complete
log writing failed. closed stream
  Chef Client failed. 0 resources updated in 07 seconds
log writing failed. closed stream
log writing failed. closed stream
log writing failed. closed stream
log writing failed. closed stream
dpkg: error processing package gitlab-ce (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up libcurl3-gnutls:armhf (7.35.0-1ubuntu2.8) ...
Setting up libcurl3:armhf (7.35.0-1ubuntu2.8) ...
Setting up curl (7.35.0-1ubuntu2.8) ...
Setting up linux-libc-dev:armhf (3.13.0-93.140) ...
Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
Errors were encountered while processing:
 gitlab-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

I was able to fix it.
I deleted and replaced my gitlab.rb, upgraded, then replaced the new gitlab.rb with my old one. I then did a reconfigure. It worked after the second attempt.


Fixed typos in code and man page files that were reported by (Debian) lintian

The changes here fix the following lintian reports:
I: s390-tools: spelling-error-in-binary "allow to" "allow one to" [usr/sbin/chreipl]
I: s390-tools: spelling-error-in-binary Unknow Unknown [usr/sbin/ziomon_mgr]
I: s390-tools: spelling-error-in-binary Unknow Unknown [usr/sbin/ziorep_traffic]
I: s390-tools: spelling-error-in-binary Unknow Unknown [usr/sbin/ziorep_utilization]
I: s390-tools: spelling-error-in-binary interal internal [usr/bin/cmsfs-fuse]
I: s390-tools: spelling-error-in-binary speficied specified [sbin/tape390_crypt]
I: s390-tools-zkey: spelling-error-in-binary explicitely explicitly [usr/libexec/zkey/zkey-ekmfweb.so]
I: s390-tools-zkey: spelling-error-in-binary faild failed [usr/bin/zkey]
I: s390-tools: typo-in-manual-page colums columns [usr/share/man/man8/lszdev.8.gz:89]
I: s390-tools: typo-in-manual-page occurence occurrence [usr/share/man/man8/zpcictl.8.gz:93]

Thanks @frank-heimes ! I'll pull the patch and take the liberty to adapt the commit message a little to not drag out his trivial PR too much. For future patches please use imperative mood in the commit description (e.g. "Fix typos in..."). See also https://docs.kernel.org/process/submitting-patches.html#describe-your-changes

Yes of course, please take the freedom to adapt.
(I did the PR a bit in a rush - imperative is what I / we usually use as well ...)

Reviewed-by: Steffen Eiden<EMAIL_ADDRESS>and picked.
Took the liberty to adapt the commit message.


Sending a message doesn't allow for "system" or custom types

Looks like the request to send a message doesn't include the Type field: https://github.com/GetStream/stream-chat-go/blob/v3.0.0/message.go#L76-L84
gz#6674

Agent comment from ferhat elmas in Zendesk ticket #6674:This is a readonly field which client shouldn't write.
However, it's used by server to acknowledge to clients such as pre-send hook prevented message to be sent.
For system messages, set silent property to true.

There is no custom type, but you can set custom fields on your message as you want.

Got it... ok. The docs mention that “The type of the message is set by the APIs or by chat bots and custom commands.” so I assumed it could be set by the server clients.
Seems like if I want to send system-style messages, such as what the React components do for messages of type “system”, I’ll need to reimplement the UI then....

You need to set silent to true for similar behavior while sending. You can read message.Type to customize your UI then.


Support default non-release version in build-controller-release.sh

Description of changes:

With the latest addition of presubmit 'release-test' job, service teams are required to execute 'build-controller-release.sh ' script for a successful PR build. 'build-controller-release.sh' script takes VERSION as required parameter.
Sagemaker team provided the feedback on how they do not want to worry about controller versions until they are doing an actual release. which is fair.
So this code change, introduces a default version 'v0.0.0-non-release-version' which allows for successful release-test for service teams without worrying about what VERSION to use until actual release.
This code change also adds the validation for the VERSION parameter.

Why not use something like git describe --tags --always --dirty to generate version ?

The git command works in most cases if the repository already has a legit semver tag. If that is not the case then we need to add additional handling to create an actual semver tag.
Instead of dealing with all the edge cases with above command, having a static non-release version gets the job done. Because it is really just a placeholder value for the release-test execution.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm


Enabling seed phrase several times

Problem
I managed to enable seed phrase several times. Sometimes while switching between accounts it shows that the seed phrase is disabled( in fact it is on). I attached a video with this, it is in low quality because I can't upload more than 10MB
Expected Behavior
It should be only one seed phrase
Steps to reproduce
seed phrase.mov.zip

Try to switch between accounts several times
Account which was previously with enabled seed phrase now has it disabled
Enable seed phrase
Now there are two seed phrases

@ihaid I've tried pretty hard to repro this without success. Is there any other info/tips you can give me to repro?

@Patrick1904 I will try once again to get to this state and then maybe I will have more info.

@Patrick1904 so just go to the https://wallet.testnet.near.org/setup-seed-phrase//phrase and follow the steps


Get test coverage of OCaml+Rust code

The only sources of SEGV issues so far were:

polars bugs
mis-specifying types on the OCaml side in externs

The second case is a bit scary, and I think a naive code coverage metric to ensure that all functions we expose are tested would ensure that we don't get surprised by anything like this. A lesser worry is if we, for example, say that an argument is an int option instead of an bool option I don't think we'll get a SEGV as long as we just pass a None, since the OCaml memory representation is identical. Perhaps OCaml tests -> Rust-side code coverage would solve this, though I'm not sure whether code-coverage tools support this kind of thing.

I'm looking into using kcov for doing this.


Fix collection template when no fields exist

Fixes https://github.com/ent/ent/issues/3464
When no fields exist in the schema, the gql generator creates unused variables. This wraps the variables in the same template conditional to avoid the unused declaration.

I resolved conflicts and merged your PR with https://github.com/ent/contrib/pull/483. Thanks for the contribution, @Adam-Mustafa


release new crates version with nalgebra 0.27

Hello,
Could you release a new version with nalgebra 0.27; I see it's in master, but crates does not appear to work with nalgebra 0.27
Thanks

I think I'll make a new release soon. For now, you can just point it to the GitHub repository and if you want you can specify a commit hash? For example
splashsurf_lib = { git = "https://github.com/w1th0utnam3/splashsurf", rev="08cfbea363874cb56dc05e26dde5460fe06205e5" }

to get the most recent commit at the moment.

Yea i generally prefer to not point at git; I can just wait for a new release, if it won't be a long time.

Today I published a new version, have fun!

thank you and thanks again for this library !

sorry it looks like 0.28 got released shortly after, and salva master is now on 0.28; is it possible to bump the crate again? alternatively, could explore api using mint: https://docs.rs/mint/0.5.6/mint/

ah i see your master is now on 0.28 too; it maybe good to wait until salva gets a crate release so this can be released with whatever nalgebra it has too? but also exploring mint might be a good idea as well :)

I can look into using mint to make this more explicit. In the meantime you could also use bytmuck (which you would need anyway with mint? At least if you wanted to avoid copies) to convert everything form splashurf::nalgebra to your nalgebra types. I think it's pretty much guaranteed to work across versions. Because it's also basically guaranteed that [T; 3] <-> Vector3 works.


Update docs to reflect recommended method for integrating with pebble log forwarding

Enhancement Proposal
Charmers will soon need to update their pebble layers with the loki push api.
Our docs should be ready for this.
Related: https://github.com/canonical/postgresql-k8s-operator/pull/486

We have docs for Pebble Log Forwarding now :)


Cheap-module-source-map not generated with correct source file.

Bug report

I create a project with Vue-Cli 3 and set webpack config devtool as cheap-module-source-map.
What is the current behavior?
The source map file generated just contain source content webpack:///webpack/bootstrap and content from node_modules, not with my actually source file.
If the current behavior is a bug, please provide the steps to reproduce.
Here a repository you can reproduce with:
https://github.com/icewind7030/sentry-vue-debug.git

I commit the generated webpack config file named config.js with vue inspect --mode production > config.js.
And I also commit the webpack build files in dist folder.
Please check the config file and the source map files.

What is the expected behavior?
cheap-module-source-map works like the webpack document says:

original source (lines only)

Show the source code error with line location.

Other relevant information:
webpack version:  4.26.0
Node.js version: 10.13.0
Operating System: macOS 10.14.1
Additional tools: VS Code 1.29.1

got the same bug

bump, need check

bump


pull request for e2e test at 01/14/2017 16:15:07

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Support request throttling and retry-after

Encountering massive amounts of HTTP 429 codes with a large size company Slack (8k+ channels). This change adds throttling based on Slack guidelines (1 RPS). Throttling starts once the rate limit has been hit for the first time. Retry logic respects the retry-after header that Slack API sends back. Requests are retried only one time.
https://api.slack.com/docs/rate-limits

In general we allow applications that integrate with Slack to send no more than one message per second. We allow bursts over that limit for short periods. However, if your app continues to exceed the limit over a longer period of time it will be rate limited.

If you go over these limits when using our HTTP based APIs, including Incoming Webhooks, Slack will start returning a HTTP 429 Too Many Requests error, a JSON object containing the number of calls you have been making, and a Retry-After header containing the number of seconds until you can retry.

nice! This looks like a reasonable PR. I actually just started hitting this in the last week. We're over 100 channels now. I have one small change in the comments of the code.

@JohnTheodore I don't think you completed the review. I don't see any code comments.

I tested this out, it's great to have a fix! thanks