Display filters in search summary in order of application

Why these changes are being introduced:
The search summary currently displays filters in alphabetical order by key. This is confusing, as one would expect them to show up in the order they were applied.
Relevant ticket(s):

GDT-224

How this addresses that need:
Many (if not all) Rails helpers pertaining to URLs (to_query, to_params, routing helpers, etc.) sort their inputs lexicographically. This means that we cannot use any of these methods, or the params object, to pass query params into the Enhancer, as they will not remain ordered and will instead be alphabetized everywhere in the application.
This commit seeks to fix this problem by passing
request.original_url into the Enhancer and building filter URLs manually. It's messier than using the Rails convenience methods, particularly because we're now mostly working with strings rather than hashes, but it felt less complex than the other approach considered of storing filter order in a cookie.
Prior to this change, both the Enhancer and QueryBuilder iterated over arrays of supported params and added them to the query if they showed up in the params object. This is now reversed: the extraction methods in both models now iterate over the URL params and confirm that they exist in the list of supported params before adding them to the query. The reason for this change is to ensure that filters (and other params) are added to the query in the order in which they appear in the original URL, not the order in which they are listed in the array of supported params.
Side effects of this change:

Fixes a bug in the filter helper that prevents single-valued filters from being applied. Currently, the only single-valued filter we have is literaryFormFilter, which is not used anywhere, but it makes sense to support all fields that TIMDEX API provides.
Updates several tests to accommodate the refactored Enhancer and QueryBuilder.
Moves the constants that recur in the Enhancer and QueryBuilder into a new module, QueryElements.
Moves all of the filter helper methods related to adding/removing filters next to each other for better readability.
Regenerates several cassettes. (It's possible that not all of these needed to be regenerated; I erred on the side of more.)

Developer
Accessibility

[x] ANDI or WAVE has been run in accordance to our guide.
[ ] This PR contains no changes to the view layer.
[ ] New issues flagged by ANDI or WAVE have been resolved.
[ ] New issues flagged by ANDI or WAVE have been ticketed (link in the Pull Request details above).
[x] No new accessibility issues have been flagged.

New ENV

[ ] All new ENV is documented in README.
[ ] All new ENV has been added to Heroku Pipeline, Staging and Prod.
[x] ENV has not changed.

Approval beyond code review

[ ] UXWS/stakeholder approval has been confirmed.
[x] UXWS/stakeholder review will be completed retroactively.
[ ] UXWS/stakeholder review is not needed.

Additional context needed to review
In terms of confirming functionality: ensure that filters from every category (including literaryFormFilter) can be added and removed successfully, and appear in the search summary panel in the order you add them.
In terms of the code: one thing I am particularly interested in is where this is adequately documented. Please let me know if (and where) you'd like to see additional explanation.
Code Reviewer
Code

[ ] I have confirmed that the code works as intended.
[x] Any CodeClimate issues have been fixed or confirmed as
added technical debt.

Documentation

[ ] The commit message is clear and follows our guidelines
(not just this pull request message).
[ ] The documentation has been updated or is unnecessary.
[ ] New dependencies are appropriate or there were no changes.

Testing

[ ] There are appropriate tests covering any new functionality.
[ ] No additional test coverage is required.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

73 of 74 (98.65%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 99.284%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/helpers/filter_helper.rb
26
27
96.3%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
555

Relevant Lines:
559

💛  - Coveralls

I noted this in JIRA, but there's a bug in this PR that still allows filters to be displayed out of order.

I noted this in JIRA, but there's a bug in this PR that still allows filters to be displayed out of order.
In the query object, multiple filters in the same category are assigned to the same key, since keys are unique in Ruby hashes.
This means that when we apply the filters in the example below (subject: transportation, then place: massachusetts, then subject: maps), the query is built like so:
{
  subjectsFilter: ['transportation', 'maps'],
  locationsFilter: ['massachusetts']
}

And when we iterate through that hash, the filters get inevitably grouped by key:
[{ subjectsFilter: 'transportation', subjectsFilter: 'maps', locationsFilter: 'massachusetts' }]

I think we need to rework our approach to this problem. It's likely a good use case for cookies, as we've discussed elsewhere.


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>
.travis.yml

chore(travis): remove node versions 10.6.0
chore(travis): add node versions 10.7.0

Coverage remained the same at 83.983% when pulling 9568acb52c0abe64b1bbba7b1560de76f71440cb on template-sync-1 into 9133fb340deac0bdd03afc19a5ed8160134e14ff on master.


Learning ignite by integrating "page swiper component"

[x] ignite base application
[x] ignite the cli
[x] ignite generated code

Here is my first test case in integrating ignite with swiper component. feel free to give feedback and any feedback is welcome or feel free to tell if it is not the right direction.

Currently react native swiper has 1469 stars.
https://github.com/leecade/react-native-swiper
Here are the steps
1. Importing react native swiper library to ignite-base/package.json{dependencies}
2. Need to decide if it is component or container or screen?
- since the swiper library can contain other components or screen but at the same time it will not occupy the whole screen, then it can be categories as "container"
3. To create a new container generator, it can follow LoginScreen.js container
- ignite generate container IntroPage
-- above line create two files
create App/Containers/IntroPage.js
create App/Containers/Styles/IntroPageStyle.js
4. Import "react-native-swiper" library into IntroPage.js
import Swiper from 'react-native-swiper'
5. add swiper to IntroPage.js

		          Hello Swiper

		          Beautiful

		          And simple

6. add style to /IntroPageStyle.js
  slide1: {
      flex: 1,
      justifyContent: 'center',
      alignItems: 'center',
      backgroundColor: '#9DD6EB',
    },
    slide2: {
      flex: 1,
      justifyContent: 'center',
      alignItems: 'center',
      backgroundColor: '#97CAE5',
    },
    slide3: {
      flex: 1,
      justifyContent: 'center',
      alignItems: 'center',
      backgroundColor: '#92BBD9',
    }

7. integrate drawer on the left side to call Intro Page and here is the gist
https://gist.github.com/steve21124/f8e2ad1e34d06e8e3db68a4b5380f2ff

IntroPage and IntroPageStyle gist
https://gist.github.com/steve21124/f8e2ad1e34d06e8e3db68a4b5380f2ff

8. the screenshot of functional intro page tour
https://giphy.com/gifs/xT0GquNnoIMhzSUkG4

9.===> Next step is ==> Ideas in how to make this as part of generator component
10. There are 2 files  to make swiper component to work
App/Containers/IntroPage.js
App/Containers/Styles/IntroPageStyle.js

11. Swiper type/parameters as component
- Number of slide
- Type of slide (horizontal slide, vertical slide, header slide, whole page slide)

12. Finally, is all these above necessary to create it as a component? may be it just too much customization for generator and less priority

@steve21124  - I think RN just merged a swiper though.
Look at swipable list view:  https://github.com/facebook/react-native/releases/tag/v0.27.0

btw, awesome doc and action steps.

Good catch. I did not know there will be Swiper soon in RN. so I can close this then... let RN do the job :)


Update vegas.min.js

Enabled initial slide parameter when shuffle is also set to True. Did not account for user input errors where the value of initial slide is outside the range of available slides. Perhaps a todo for later.
If user sets initial slide value to -1, then all slides are shuffled.
Because I beautified the code, the diff isn't showing what I actually changed.
I modified shuffle and added genRan
        // Shoutout to https://stackoverflow.com/a/27406684/5437832         genRan: function generateRandom(min, max, depth) {             if(depth>10) { return 1; }             var num = Math.floor(Math.random() * (max - min + 1)) + min;             if (this.settings.slide != -1) {                 return (num === this.settings.slide) ? generateRandom(min, max, depth+1) : num;             } else {                 return num;             }         },         shuffle: function() {             for (var t, s, i = this.total - 1; 0 < i; i--) {                 console.log( 'In for loop with i = %d', i);                 console.log( 'this.settings.slide = %d', this.settings.slide);                 if (this.settings.slide != -1) {                     console.log( 'In the if section casue slide value is different than -1');                     if (i == this.settings.slide) {                         console.log( 'Skipping this loop cause i = our initial slide value.');                         continue;                     }                     s = this.genRan(0,this.total-1,10),                     t = this.settings.slides[i],                     this.settings.slides[i] = this.settings.slides[s],                     this.settings.slides[s] = t                 } else {                     s = Math.floor(Math.random() * (i + 1)),                     t = this.settings.slides[i],                     this.settings.slides[i] = this.settings.slides[s],                     this.settings.slides[s] = t                 }             }         },

Hello and thanks.
However I can't do anything with the minified code. It will be overwritten by the real source code at the next release.
I plan to work on Vegas V3 (without jQuery) at the beginning of next year . I will add this feature then.


0 Results

No results!

I will look

I fixed it with v1.5.5. Problem was, Google changed content of the page. A little fix fixed it but module may be slow and can find unexpected results. I will look after.


HEIF/HEIC

Description of the new feature / enhancement
Hi,
love your tool. I wish Remote Desktop could interact more friendly with it.
My suggestion today is with the "Extension for Explorer". You have put SVG which is great, but recently, the one giving us headaches is HEIF file image extension, more precisely the HEIC from Apple iOS. I know we can fix this with an extension download codec, but wouldn't it be easier if it was already with Powertoys? :-) Me I think so. I hope to see this feature someday.
Thank you to all the team for the great work
Kind regards,
Mike
Scenario when this would be used?
Sometimes we receive files from poeple and we can't preview them.
Supporting information
Pretty self-explanatory. :)

Duplicate of #3990

Thanks for your suggestion! This issue is a duplicate.
I'm linking this issue to #3990 to centralize the discussion thread, please go to that thread for discussion.
Thanks for your help to make PowerToys a better piece of software!


Add XHTML/XML option

This may not be worth it, but here goes…
E.g. … → U+0085 in XHTML, while in HTML it’s U+2026.
http://www.w3.org/TR/xml/#d0e3895
Entities for these symbols are allowed in XML: http://www.w3.org/TR/xml/#NT-Char

Another XML vs. HTML issue is how to encode using only named XML entities (i.e. &, <, >, ' and "). Don't think this is possible in the API today, but perhaps it should be? Just a very minor issue of course.
Ended up with a few extra lines of JS to work-around this:
    const ENTITIES = ['&', '"', ''', '<', '>'];
    const recode = (s) => he.encode(he.decode(s), { decimal: true });
    const fix = (s) => ENTITIES.reduce((s, e) => s.replaceAll(recode(e), e), s);


Update built-in-components.js

@bnau @c3dr0x The goal is to allow the use of refContainer in list mixin


Add Arapahoe County Public Health to referrer dropdown menu in MFB

Add Arapahoe County Public Health to referrer dropdown menu in MFB.
Show up if referrer = acph

Will automatically appear in dropdown menu if users come to MFB via this link - https://screener.myfriendben.org/step-1?referrer=arapahoectypublichealth&utm_source=acph&utm_medium=website&utm_campaign=acph&utm_id=acph.
Asking county if they want a separate UTM link for flyers - will update ticket after determining this.

@sydney-devine @CalebPena This looks good. Wondering if, at some future point, we should talk about the order in which these all appear. Seems a bit random - but good to release today.


Tweak ETCD Too Large alert

Towards: https://github.com/giantswarm/giantswarm/issues/26054
The alert has not fired during the incident hence we probably have to tweak it a bit

yes, but we agreed not during the night

let's discuss it during standup

Do we also want to add this for MC's? I introduced the change for MC and WC.
Also does it make sense to remove the out of office rule? I think it's reasonable to page also in the night? WDYT


query macro: the trait Encode<'_, Sqlite> is not implemented for u64

Bug Description
I'm using the macro with cargo sqlx prepare and the following error appears:
    |
113 | /                 query!(
114 | |                     "
115 | |             INSERT INTO DependencyChanges (hash, name, change, timestamp)
116 | |             VALUES (?,?,?,?);
...   |
121 | |                     dc.timestamp
122 | |                 )
    | |_________________^ the trait `Encode<'_, Sqlite>` is not implemented for `u64`

Its complaining about dc.hash which is a u64. I thought sqlx supported it? I'm getting errors for char as well but this seems more concerning.
Minimal Reproduction
the struct:
pub struct DependencyChanges {
    hash: u64,
    name: String,
    change: char,
    timestamp: i64,
}

the code:
query!("
            INSERT INTO DependencyChanges (hash, name, change, timestamp)
            VALUES (?,?,?,?);
            ",
                    dc.hash,
                    dc.name,
                    dc.change,
                    dc.timestamp
                )
                .execute(&conn)
                .await?;

it should be fairly easy to reproduce. Here's the table definition if that matters:
    CREATE TABLE IF NOT EXISTS DependencyChanges (
        hash TEXT NOT NULL,
        name TEXT NOT NULL,
        change CHAR(1) NOT NULL,
        timestamp INTEGER NOT NULL
    );

Info

SQLx version: 0.7.2
SQLx features enabled: "runtime-tokio", "sqlite", "chrono"
Database server and version: SQLite <3.43.1>
Operating system: GNU/Linux
rustc --version: 1.70.0

Not a bug. u64 does not have a direct mapping to a SQLite type since it does not support unsigned integers.
Try dc.hash.to_string().


The license monitoring still not work

@AndreyVMarkelov The jira_license_expiry_days_gauge still return 0, although the license is valid.

The JIRA is connected to the Marketplace.

It my fault because I check only CORE license. I will fix it introducing
labels for: CORE, SOFTWARE and SD
2018-06-07 11:04 GMT+03:00 hfuhuang<EMAIL_ADDRESS>
@AndreyVMarkelov https://github.com/AndreyVMarkelov The
jira_license_expiry_days_gauge still return 0, although the license is
valid.
[image: screen shot 2018-05-29 at 14 22 45]
https://user-images.githubusercontent.com/230489/41086353-166018e2-6a3a-11e8-83fa-abfde3acb1b6.png
[image: screen shot 2018-05-29 at 14 23 31]
https://user-images.githubusercontent.com/230489/41086355-16887a44-6a3a-11e8-92bf-d93de330714a.png
The JIRA is connected to the Marketplace.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AndreyVMarkelov/jira-prometheus-exporter/issues/29,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB92cNoYraAFDwXhzDaRb5AHsBsj-a7hks5t6N6lgaJpZM4Ud7To
.

--
-- Andrey Markelov

Now there is label with license type. Choose appropriate.


Use AsRef generic type parameter instead of &str or &Path

For filename operations, it might be better to accept anything that is AsRef<Path> instead of limiting input to only &stror &Path.
As a bonus directory argument of find() function is not mut anymore.

This makes a lot of sense to me. However, it implies a change in the public API, so I'd love to hear some feedback from others on whether it's worth it. @casey @daboross thoughts?

Sure. Please note that it changes public API in a backward compatible fashion - since AsRef<Path> is implemented for str and Path

I'm in support of accepting AsRef<Path>, but could we do it without allocating a PathBuf? Storing &'a Path should work just as well as &'a str did before.
If there's a concrete advantage to the PathBuf I'd be OK with that, but right now it looks like the only advantage is not needing 'a.
This isn't technically a breaking change, but it can be one in a lot of cases anyways. This will break any places where the compiler relied on concrete &str or &Path arguments to infer some other type. Still in support of changing this, just wanted to make that note.

PathBuf was already in use by Finder.directory. I was considering replacing it with Cow but decided to experiment with it later.

This seems like a good change to me. There are some cases where it won't be backwards compatible, but I think this is worth the version bump.
I agree with @daboross that if filename can be a &Path it probably should be.

Converting filename back to &Path becomes surprisingly convoluted and calls for other visible API change. Anyway, long-time keeping &Path which is created from a parameter that is AsRef<Path> is not trivial, since it will outlive the parameter itself (not necessarily the value it represents).

Ah right, I ran into that recently myself. An example which shows the problem:
use std::path::{Path, PathBuf};

struct Foo<'a> {
  path: &'a Path,
}

impl<'a> Foo<'a> {
  fn new<P: AsRef<Path> + 'a>(path: P) -> Foo<'a> {
    Foo {
      path: path.as_ref(),
    }
  }
}

fn main() {
  let p = PathBuf::new();

  // `p` is passed by value, and so no longer exists when the call to new returns
  // which prevents Foo from retaining a reference to the path created by `as_ref`
  let foo = Foo::new(p);
}

It should be possible to have Finder::filename take filename: &'a P instead of filename: P to resolve any lifetime problems with AsRef. It'll force the actual value to be borrowed from outside, so it will live long enough. Not an ideal API, but it's internal-only, so it seems fine?
Here's a patch to do this which should compile and pass tests: https://gist.github.com/daboross/346bc99b070d61d08ec638cd38215bc7. Feel free to incorporate and/or use as a reference if needed.
Glad to see this API change - I just don't want it to be at the cost of efficiency.

@daboross Here we go. Appreciate your persistence!

Thanks @imp! I'm good with this PR now if @purpliminal and @casey are.

Looks good to me! Finder.directory was there from a previous iteration where you could set the directory to begin searching from, but it was unnecessary so I pushed a commit removing it.

@casey Good. I was thinking about removing Finder.directory, but wasn't sure whether it is here for a future expansion or just a leftover from the previous iteration.

Maybe it'll be used eventually, if someone ever wants a feature to set the directory that dotenv searches from, but for now it's just cruft :P

So, is there any outstanding issues with this PR?

I don't think so! Merging. 💯

Thanks!


Code panel opacity on focus?

Very cool project! It'd be great, for readability, if the code panel's background went white (or at lease more opaque) when you're focused on it. And maybe the ability to fold the panel away with a little tab (much like the one on the other side of the screen)? Just thoughts :)

@josephrocca thanks for the feedback.
The "editor" has a tab which can be clicked on. This should fold to the right.
I agree about the "opacity" of the editor. It's difficult to read when extended. We can probably do better.


Improvement add default_value column for result of show_variables stmt

make it easy to find out which variables are changed
easy to set back to default value

Proposed changes
Issue Number: close #xxx

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

run buildall

run buildall

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 45.98 seconds
stream load tsv:          540 seconds loaded<PHONE_NUMBER>9 Bytes, about 132 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.6 seconds inserted 10000000 Rows, about 337K ops/s
storage size:<PHONE_NUMBER>2 Bytes

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 48.89 seconds
stream load tsv:          541 seconds loaded<PHONE_NUMBER>9 Bytes, about 131 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.0 seconds inserted 10000000 Rows, about 344K ops/s
storage size:<PHONE_NUMBER>7 Bytes


Tensorrt  specified container port, which will not work with logger

What this PR does / why we need it:
Container port specified with logger will not work. For built in frameworks it's always 8080 so we need not specify it. For custom spec the correct solution would be issue #594
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

This change is

/retest

/approve

/lgtm

/retest

/retest

/retest

/retest

/retest

@pugangxa Please rebase to fix the ci problems, thanks.

/lgtm
/retest


Grant abstract is not correct?

Describe the bug
@brynnz22 attempted to validate and upload this Grant manifest to Synapse via the MC2 DCA, and she was able to successfully get through all of the steps, save for the uploading step.  I looked at the logs and saw:
2022-06-15T17:56:02.283856+00:00 shinyapps[5992584]: Warning: Error in py_call_impl: KeyError: 'GrantAbstract'
2022-06-15T17:56:02.285392+00:00 shinyapps[5992584]: Detailed traceback:
2022-06-15T17:56:02.285996+00:00 shinyapps[5992584]:   File "/srv/connect/apps/csbc_data_curator_staging/.venv/lib/python3.8/site-packages/schematic/schemas/explorer.py", line 332, in explore_class
2022-06-15T17:56:02.283986+00:00 shinyapps[5992584]:
2022-06-15T17:56:02.285522+00:00 shinyapps[5992584]:   File "/srv/connect/apps/csbc_data_curator_staging/.venv/lib/python3.8/site-packages/schematic/store/synapse.py", line 843, in associateMetadataWithFiles
2022-06-15T17:56:02.286158+00:00 shinyapps[5992584]:  [... truncated]
2022-06-15T17:56:02.285592+00:00 shinyapps[5992584]:     annos = self.format_row_annotations(se, row, entityId, useSchemaLabel, hideBlanks)
2022-06-15T17:56:02.286231+00:00 shinyapps[5992584]:   [No stack trace available]
2022-06-15T17:56:02.285667+00:00 shinyapps[5992584]:   File "/srv/connect/apps/csbc_data_curator_staging/.venv/lib/python3.8/site-packages/schematic/store/synapse.py", line 684, in format_row_annotations
2022-06-15T17:56:02.285747+00:00 shinyapps[5992584]:     elif isinstance(anno_v,str) and re.fullmatch(csv_list_regex, anno_v) and 'list' in se.get_class_validation_rules(anno_k):
2022-06-15T17:56:02.285828+00:00 shinyapps[5992584]:   File "/srv/connect/apps/csbc_data_curator_staging/.venv/lib/python3.8/site-packages/schematic/schemas/explorer.py", line 431, in get_class_validation_rules
2022-06-15T17:56:02.285909+00:00 shinyapps[5992584]:     class_info = self.explore_class(class_label)
2022-06-15T17:56:02.286083+00:00 shinyapps[5992584]:     if "subClassOf" in self.schema_nx.nodes[schema_class]:

From the logs, we're thinking this is a data model error?
To Reproduce
Steps to reproduce the behavior:

Go to the DCA > Submit & Validate Metadata
Upload Grant manifest as a CSV > Validate Metadata
Scroll down past the file preview, then click on Submit to Synapse
See error (hidden under the Waiter window)

Priority (select one)

[ ] Minor ⬇
[ ] Major 📢
[x] Critical 🆘

Also tagging @afwillia @mialy-defelice for guidance :pray:

@vpchung Yes this looks like this might be a Data Model error. Can you send me the data model you are working with?

@mialy-defelice the jsonld is found here. The csv in this repo is slightly different right now, but here is the google sheet.

Small update: @brynnz22 attempted to upload the manifest directly with schematic CLI and it worked 🎉 :
$ schematic \
  model --config ($pwd)/schematic/config.yml \
  submit --manifest_path ~/Desktop/Grant.csv \
  --dataset_id syn31974175
Starting schematic...
The (model > input > location) argument with value '/Users/bzalmanek/Documents/csbc_schematic/schematic/tests/data/csbc.model.jsonld' is being read from the config file.
The (model > input > file_type) argument with value 'local' is being read from the config file.
 [####################]100.00%   1/1   Done...
Downloading  [####################]100.00%   23.6kB/23.6kB (307.0kB/s) SYNAPSE_TABLE_QUERY_97472742.csv Done...
    Associated manifest file with dataset on Synapse.

##################################################
 Uploading file to Synapse storage
##################################################

##################################################
 Uploading file to Synapse storage
##################################################

Uploading [####################]100.00%   35.0kB/35.0kB (22.7kB/s) Grant.csv Done...
    File at '/Users/bzalmanek/Desktop/Grant.csv' was successfully associated with dataset 'syn31974175'.

I then tried to upload the manifest again via the DCA -- hoping that it'll work too -- but to no avail.  Not sure if this is possibly an issue with schematic versioning?

Closing this for now until we try again with the new GrantsView manifest.


Port code to PyMC3

PyMC3 is coming along quite nicely and is a major improvement upon pymc 2. I thus think a port of PPfH to PyMC3 would be very useful, especially since pymc3 is not well documented yet. All examples should be easy to port.
I don't think such a PR should be merged into master as pymc 2 is probably still around to stay and much more stable. But having a forked book would be quite nice. Certainly this point is up for debate.

Any news here ?

@hadim Interested in leading the charge here?

Well I already did it for chapter 1 but I just see that it is already done in https://github.com/CamDavidsonPilon/Probabilistic-Programming-and-Bayesian-Methods-for-Hackers/tree/pymc3.
I am sorry but for the others chapters I don't have neither the time and the knowledge to do it in a short term.
Maybe you could add a "call for contributor" on the README of the master branch about the porting to pymc3. You could also open a PR against pymc3 to track progress.

Please see #268.
(this issue can be closed)


Change default status of My Project Activity Notifications

[x] Project published
Mail: checked, editable
DAPP: checked, editable

[x] Your project update
Mail: unchecked, non-editable
DAPP: unchecked, editable

[x] Project Likes:
Mail: unchecked, not-editable
DAPP: checked, editable

[x] Project boost status
Mail: unchecked, not-editable
DAPP: checked, editable

[x] Your project status
Mail: checked, editable
DAPP: checked, editable

[x] Donations
Mail: checked, editable
DAPP: checked, editable

[x] Donation received
Mail: checked, editable
DAPP: checked, editable

@maryjaf  It's on staging, can you test this?

@maryjaf It's on staging, can you test this?

Thanks @mohammadranjbarz I checked and it's OK


Delete spatialRegistration.jsonld

final step in openMINDS to solve #81. "spatial registration" is already added as synonym in "image registration".
EBRAINS cleanup is in prep. This PR does not depend on the EBRAINS cleanup.

@UlrikeS91 or @MaaikevS could you review / merge this PR? I might need help from you two as well for the EBRAINS cleanup.


Add test to cover new array url encoding.

What's this PR do?
Add test to cover new array url encoding.
Background context
Follow up work to this work:
https://github.com/urlbox/urlbox-python/pull/37

Codecov Report

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

@@           Coverage Diff           @@
##             main      #40   +/-   ##
=======================================
  Coverage        ?   99.10%
=======================================
  Files           ?        9
  Lines           ?      448
  Branches        ?        0
=======================================
  Hits            ?      444
  Misses          ?        4
  Partials        ?        0

Flag
Coverage Δ

unittests
99.10% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 92dacbd...4ec79a8. Read the comment docs.


modulesync 4.1.0

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

Replaced by #59.


Implement a logical term conflict validation post processing step

A term should not have a deprecated <termNotation>, that is an allowed <termNotation> of another term. This should be validated after the preprocessing phase.
term 1
<fullForm language="en-GB" usage="notRecommended">
   <termVariant>foo</termVariant>
</fullForm>

term 2
<fullForm language="en-GB" usage="preferred">
   <termVariant>foo</termVariant>
</fullForm>

implemented as part of the termstats


Update nodejs-sdk.md

Propose the command to launch the file updated, maybe duplicate on other languages ?

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

The following users don't have valid GitHub IDs, or are not collaborators on this repo: microsoftdocs/public-repo-pr-review-team

@aahill - can you confirm/approve/ or sign off?
@tejaswikolli-web - PRMerger will only accept sign off from the listed 'author'. However, if you are a Microsoft employee authorized to update this content, you can send a request to<EMAIL_ADDRESS>for this PR to be merged.  Include your role, and an explanation of why the PR should be merged without approval from the listed author.

#sign-off

Thanks @jakaruna-MSFT , @aahill


PortalContentPost.py failing with "Invalid group capability" error

Used PortalContentExtract.py script to export user content against 10.4 portal. Used PortalContentPost.py to import to 10.4.1 portal and when the script tries to create groups for users the script fails with the following error:
Creating groups ...
Creating '2' group(s) for user 'user'...
... group 'Gallery App Group'
ERROR:portalpy:Unable to create group.
ERROR:portalpy:Invalid group capability '[]'.
Traceback (most recent call last):
File "C:\ops-server-config\Publish\Portal\PortalContentPost.py", line 1079, in
main()
File "C:\ops-server-config\Publish\Portal\PortalContentPost.py", line 177, in main
publish_portal(target_portal_address, contentpath, adminuser, adminpassword, users, hostname_map, specified_groups, id_mapping_file)
File "C:\ops-server-config\Publish\Portal\PortalContentPost.py", line 261, in publish_portal
newGroups = publish_user_groups(portaladmin, contentpath, userinfo, users)
File "C:\ops-server-config\Publish\Portal\PortalContentPost.py", line 641, in publish_user_groups
portal.reassign_group(groupId, username)
File "C:\ops-server-config\Publish\Portal\portalpy_init_.py", line 1263, in reassign_group
resp = self.con.post('community/groups/' + id + '/reassign', postdata)
TypeError: cannot concatenate 'str' and 'NoneType' objects

The issue is that the createGroup endpoint in the portal sharing api only accepts form-data and not json. So the capabilities and tags list properties had to be converted to comma delimited strings.

Fixed. Change in master.


Have an indicator of where in the list of cards you are

Something that gives you a sense of where you are in the list of cards (even if the drawer is hidden).

Think of it as a collapsed version of card-drawer


Check format of examples

We can run terragrunt hclfmt on the examples to check the engine. There are yaml formatters for policygen, or we can reuse terragrunt if we migrate policygen to hcl.

Also check https://github.com/apparentlymart/terraform-clean-syntax for cleaning deprecated quoted refs.

Duplicate of #175


SMPP Telegram Bridge

A SMPP Simple Telegram bridge.

[ ] Email Archive.
[ ] Local database archive (searchable)
[ ] Message-based Sent message to remote.
[ ] Webpage-based Sent message to remote.
[ ] Custom-able user template for receiver.
[ ] Rule-based automation add tag
[ ] Mainland China SMS Signature Extractor (106x prefix only).
[ ] Naive Bayes Classifier for Spam.

References

https://core.telegram.org/widgets/login
https://core.telegram.org/api/url-authorization
https://cloud.tencent.com/document/product/382/39022

CC @hexhu @lty1993 @Jamesits @difanz @shiyunjin @OtakuNekoP


Display the status of declarations (methods, subset types, etc) that require verification

Use the VSCoded testing API to show a list view of declarations from the Dafny programs that require verification. These are declarations like: methods, function, subset types, newtypes, datatypes, iterators, constants.
For each item in the list, show its current status:

Stale: should be run, but is not queued to run (can occur when verify on save is on)
Queued: waiting for resources to run
Running
Verified: completed without errors
Failed: completed with verification errors

For running items, show how long they have been running. For verified or failed items, show how long they took to complete after they started running.
Use-cases
(Identify slow running proofs) One user complaint we’ve received is that verification in the IDE sometimes becomes unresponsive. One possible cause of this may be a proof that requires a long time to verify. The customer should know which proof this is so they can change the proof and make it faster to verify, and they should be able to cancel the slow running verification after patching the proof.
(Identify resources constraints) If declarations are often queued to be verified, the customers might want to configure Dafny's IDE to use more cores.
(Estimate time to verify) If a user makes a change to their Dafny program that affects the verification of multiple proofs, and verification of those proofs is running, we would like to enable the customer to estimate how long until verification for all proofs is completed, by showing them all proofs that still need to verify, how many are verifying in parallel, and how long verification of these proofs took previously.
Dependent issues

https://github.com/dafny-lang/ide-vscode/issues/97
https://github.com/dafny-lang/ide-vscode/issues/96

Related PR: https://github.com/dafny-lang/dafny/pull/2094/files#

I think this is now fixed, thanks !


Introduce suspenders:setup generator

Replaces the default setup script provided by Rails. The trade-off being
that the implementation is simple, but the cost is we risk drifting from Rails.
After attempting to use gsub_file and insert_into_file, it felt simpler
to just override the file completely.
Uses Homebrew Bundle in combination with asdf to install system and tool
dependencies locally.
Re-introduces dev:prime to seed development data on top of seed data
necessary for production.
Clobber and precompile assets during setup if using Sprockets. This
is helpful in cases where one might switch branches frequently, which
can result in broken assets.
Additionally, we setup the test environment to avoid issues with asset
compilation in tests.

@mike-burns

This feels like it conflates system setup with app setup. I'm not sold on mixing the two.

Is the concern that this setup script seems to favor MacOS? Or, even if it were more agnostic, would you rather see the Hombrew and asdf sections removed?
Should those be the responsibility of something like Laptop

Should those be the responsibility of something like Laptop

The system setup has traditionally been the responsibility of the Laptop script, yeah. Not sure why we would duplicate it here.


docs: Update docs after release 3.9.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4116

Relevant Lines:
4616

💛  - Coveralls


Elastalert-  Load rules from configmap

What happened:
How to load rules from configmap rather then polluting values.yaml file? Is there a way?
Created a folder rules and added rule files here and tried something like this
kubectl create configmap elastalert-elastalert-rules --from-file rules/ --namespace platform  -o yaml --dry-run | kubectl apply -f -
But that doesn't work becuase deployment chart in the template has this

name: rules
configMap:
name: {{ template "elastalert.fullname" . }}-rules
items:
{{- range $key, $value := .Values.rules }}
- key: {{ $key }}
path: {{ $key}}.yaml

Is there a cleaner way to do this? When I create a configmap from not using values.yaml, the key and path is not populated since values.yaml doesn't have it. Is there a better solution for this?

I'd also like to know this.

I could use it as well.


Add Sorry

Sorry provides a single, uniform interface to ask for iOS permissions. I love PermissionScope but it's sometimes too opinionated about your interface...
The simplest example:
let permission = Permission(.Contacts)

permission.request { status in
    print(status)
}

Configure the alerts:
permission.configureAlert(.Denied) { alert in
    alert.title = "You denied access to your contacts"
    alert.message = "Please allow access in the settings app"
    alert.cancel = "Cancel"
    alert.settings = "Settings"
}

Sorry has some helpers too :)
let button = PermissionButton(.Contacts)

button.setTitles([
    .Authorized: "Authorized",
    .Denied: "Denied"
])

// etc.

And you can create some permissions set
Let's say you want to know if the user allowed access to both your photos and your events:
let photos = PermissionButton(.Photos)
let events = PermissionButton(.Events)

let permissionSet = PermissionSet(photos, events)

More in the README

Nice lib. Thanks!

Thanks :smile:


Lofreq patch

Pull Request Checklists
Checklist for Updated Module
See Changelog.

I believe this is ready for re-review, @lkhilton


Update Landing Page per feedback

https://www.notion.so/olympusdao/c11e21b1256b40efb234eee9380956ea?v=2d843d3d8c034942ab78bc5277f65ef1

I put this on the dapp frontend repo just bc we don't have a good place for landing page issues...

This is done.


csharp for osx

The csharp wrapper can't be built on OSX because it seems to rely on Visual Studio and won't use Mono.
If you have access to Windows, there is a workaround found here (https://communities.intel.com/thread/122475), but folks with only OSX can't build the necessary wrappers/csharp/Intel.RealSense/Intel.RealSense.csproj for the workaround.
Please provide a way to build on Mono, or include the prebuilt dll and bundle  in the repo.
Thanks!

Although not ideal for those who want to use Mono, there is a free Community Edition of Visual Studio for OSX.
https://visualstudio.microsoft.com/vs/mac/
For Windows users who have been having trouble with compiling the DLLs for use in Unity, the method of dragging-and dropping the pre-built DLLs in the bin folder instead of compiling from source does seem to be working consistently.  I have no information about whether the drag-and-drop technique is effective on OSX though.

[Realsense Customer Engineering Team Comment]
hi @bleppie,
do you need more support on this topic?

I tried Visual Studio for Mac but unfortunately the cmake files have
hard-coded checks to prevent csharp builds on Mac. I tried removing them
and wrestled with it a bit but couldn't get it to work. I've now moved
Development over to Windows so this isn't a pressing issue for me, but I
would still like to see support for Mac users.
Thanks
On Thu, Aug 9, 2018 at 1:50 AM RealSense Customer Engineering <
<EMAIL_ADDRESS>wrote:

[Realsense Customer Engineering Team Comment]
hi @bleppie https://github.com/bleppie,
do you need more support on this topic?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/2107#issuecomment-411644531,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjNBUA-2s5429hFQgqS337c7XHjpm-dks5uO82SgaJpZM4VYXm8
.

--
www.blep.com

[Realsense Customer Engineering Team Comment]
hi @bleppie,
yes, i have a try too and can't make it work on Mac either.
i think this is good to have, and we will improve the wrappers time to time.
let me close this ticket for now and please feel free to open new ticket if any question.


settings: Increase max-width for search inputs of tables.

This is a temporary commit to make sure that placeholder does not cut off at larger font sizes, though it is not reproducible for everyone. A long term fix would be to use flex layout.
Fixes #30670.

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@alya can you test this?

Why is the fix not to convert this width to em?

Hm, it doesn't seem to help for me:

Yes, should have used em here, but was not sure what value to set as I was not able to reproduce. Also, we have limited space for some tables because we show "Saving" indicator for some of them, but should be fine for 16px atleast. Have set the value in em for now according to the previous value of 160px for 14px font size.
@alya can you check this again?

Still seeing this at 16px:

I did not get why I am not able to reproduce this. I can see decent enough space after the "users" word even on 18px.

@amanagr are you able to reproduce? It seems hard to work on this without being able to see it.

Ah! This is a pixel issue. I can reproduce the bug at some zoom levels while not at others. This is due to calculated with of the input being 152.5px for deactivated users here by the auto function of the browser.  I don't think is worth spending a lot of time on but maybe @karlstolley has other ideas here.

Picking up on this old PR...really, placeholder is being used incorrectly here. That should be an example of input, not a label for input. For that purpose, one would use the <label> tag. I could imagine a pattern where we use CSS grid to overlay the label and help expand the input to the size needed. When the field is activated, the label is hidden or removed--and replaced when the input is empty and the field no longer active.


Storage and Crafting Terminal do not work on MC 1.21 Fabric (SERVER)

SMP on a Fabric server with Fabric API 0.100.7 on MC 1.21. TSSM 2.0.7.
Right clicking on the storage connector shows the correct amount of connected devices. There are even some resources shown in the Jade-tip.
However, when connecting the crafting terminal to the connector it just stays empty. Same with connection cable.
I used this mod in SSP and there it just worked fine. The problem seems to be the server part. There is no crash. Do you still want latest.log?

Im having the same problem, but im playing on single player mode and its bugged. Crafting and Storage Terminals are not working at all.

I just see there is a new version 2.0.8 from today. @pkyios can you test it?

I just see there is a new version 2.0.8 from today. @pkyios can you test it?

tested it right now, works like a charm.

Yay! I'll update my client and server modpacks and report here.

It still not works on server. Now with TSSM 2.0.8, both on client and server. The screenshots with the empty GUIs still apply. I cannot close this issue.
:(

I can shift click stacks into the left crafting terminal. They are not seen there, the GUI still stays empty. However, the items are stored savely into the storage system and can be found when clicking through all the chests.

You no longer need the Inventory Cable Connector behind the terminal, that won't work anymore in 2.0.0 updates.
You can just place the terminal on an inventory cable.

Thank you. The one that reacted to shift clicking was the one directly applied to the storage connector cube. I removed the other crafting terminal. The inventory cable connector did not have a default tool when removing it, i noticed.

After re-checking server files: I did not really update the 2.0.7 version. It was still there.
So: All is my fault. Sorry for insisting on a non existant bug: 2.0.8 did fix it, also in multi player.


macOS raylib installation

This allows installation on macOS (as mentioned in https://github.com/raysan5/raylib/issues/840)

On hold until I can confirm #8 works as intended.

I think this can be closed.
The library should work as normal on MacOS on version v0.4.0


Easy tables binding with authentication

Consider that I have an existing easy table that I am using with my mobile apps, which I have protected with authentication because an API key IS NOT a security token since it's getting distributed with my mobile apps onto devices and it can be obtained.
How can I get my Azure Function to access my easy table by using authentication, or will this never be a supported scenario?

Currently, it can't. The API key exposed by Functions is to support integration scenarios with trusted systems and it is to be kept private/secure. The API key support added to easy tables is to validate requests from Azure Functions. We should not recommend using either of those keys on any mobile or any other distributed client applications.
Keep in mind that mobile clients can continue to use the Mobile Apps APIs following the standard authentication process. Enabling API key use on a particular table doesn't mean that the clients need to use that key for auth.
Easy Auth support and improving how the tokens flow to work into easy tables is definitely the goal, but those are backlog items at this point.

Closing the issue from on this repo. discussing offline with fabio. This would require an update to https://github.com/Azure/azure-webjobs-sdk-extensions to be consumed by https://github.com/Azure/azure-webjobs-sdk-script/. Filing an issue in the script sdk repository. https://github.com/Azure/azure-webjobs-sdk-script/issues/233


Add files via upload

ftf stands for Physics and Technology Faculty

@LightFleet Pull request merged. Thank you!


[Bug]: Build from source but got unexpected symbol

Your current environment
WARNING 06-13 04:15:46 _custom_ops.py:11] Failed to import from vllm._C with ImportError('/data/libs/vllm/vllm/_C.abi3.so: undefined symbol: _ZN5torch7LibraryC1ENS0_4KindESsSt8optionalIN3c1011DispatchKeyEEPKcj')```

<img width="1384" alt="image" src="https://github.com/vllm-project/vllm/assets/168061642/122ce5c3-7155-430b-9efd-3b1874301002">

### 🐛 Describe the bug

git clone xxx && pip install -e .

Already cleaned old build, actually this is a fresh clone.

Please add your environment details following the issue template :)

this issue is not raised once noticed there are many since yesterday please take a look
---- Replied Message ----
| From | @.> |
| Date | 06/13/2024 12:35 |
| To | @.> |
| Cc |<EMAIL_ADDRESS>|
| Subject | Re: [vllm-project/vllm] [Bug]: Build from source but got unexpected symbol (Issue #5486) |
Please add your environment details following the issue template :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Error handling for @app.call

Thank you for your development. rack-ltsv_logger is nice logging tool.
When error occurred in calling @app.call, then nothing logged. I want Application Logger working (logging) in anytime.

ensure error in @app.call. (then, [status, headers, body] will be [nil, nil, nil])
status will be 500 for logging, not overwrite.
headers allows nil, not overwrite.

thanks!

0.0.2 is released!

Thank you!


Create a module for Header metadata retrieval

Purpose of this module will be to create the main functionality to retrieve the "header" level metadata for a YouTube video. Specifically, we want to build a module which, given a list of YouTube video ids, it will be able to retrieve a collection of information, such as:

Video_id
Video Title
Channel/Creator who uploaded the video (channel_id, channel_name)
Video Description
Date posted (upload date)
Genre/Video Category
Locations that it is available
Duration

did you mean migrate func main's code to dataretriver.go ?

did you mean migrate func main's code to dataretriver.go ?

The initial plan was to migrate some code that I already have in a private repository - but i think it's better to re-write the logic as I want to have the data retrieval module in Golang for learning + performance purposes.


Multi scale axis (-- extends right-y-axis)

This fork is a branch which is on top of the right-y-axis branch.  This means it adds everything that the right-y-axis branch does PLUS a new axis type (multiscaling linear y axis).
This new axis is used to represent multiple scales on the same axis.  Both this and the right-y-axis feature are coded in such a way as to not affect any existing deployments unless they choose to use the new features.
Jaime -- if you would like I would be happy to walk you through these changes, how to configure the new chart types, and what the new chart types look like (and do)

Give me some time to review all the changes and then maybe we can walk through all of it. I'm a bit concerned that now all visualizations need to be aware of the left/right axis difference and the amount of code that is now dependent on knowing the difference between left/right axes. I always thought we could do it by configuring a new axis and abstracting how/what the visualizations use, so this.yScale returns the correct axis for the visualization. Maybe even something like:
new Contour({...})
  .cartesian()
  .line(data)
  .rightAxis()
  .line(dataForRightAxis)
...

but maybe this is not possible with the current structure.

Definitely review, take your time -- there are many changes.
To clarify -- what the visualizations really need to know is what is the
proper scaling function.  In the end the visualizations care nothing for
the axis -- the question they need to answer is 'What scale function should
I apply to this scalar value Y from this series S?'  You'll see this when
you look into how the multi-scale-linear axis works.
Your code proposal could potentially work for the distinction between y
axes, but wouldn't work for multiple scales on the same axis.
On Thu, Mar 12, 2015 at 12:53 PM, Jaime del Palacio <
<EMAIL_ADDRESS>wrote:

Give me some time to review all the changes and then maybe we can walk
through all of it. I'm a bit concerned that now all visualizations need to
be aware of the left/right axis difference and the amount of code that is
now dependent on knowing the difference between left/right axes. I always
thought we could do it by configuring a new axis and abstracting how/what
the visualizations use, so this.yScale returns the correct axis for the
visualization. Maybe even something like:
new Contour({...})
.cartesian()
.line(data)
.rightAxis()
.line(dataForRightAxis)
...
but maybe this is not possible with the current structure.
—
Reply to this email directly or view it on GitHub
https://github.com/forio/contour/pull/209#issuecomment-78525487.

If I were to make this branch cleanly merge again would you accept it?
If not is it the feature you don't want (right y axis, and multi-scale y axis)? Or the implementation?  If it is the feature unfortunately I require both and can't see how I could do it without modifying contour, but if its the implementation I am glad to hear how you would like to see it structured.
I would like to get this merged upstream sooner rather then later.  Since it is such a wide change the older it gets the harder it gets to merge.

Hey, so far my thinking is that the multiple axes is not something I specially want to support (bad practice and all that :), but I want to make it easy for you to have a specific extension that allows for that. My concern with the current implementation is that the concept of the multiple axes get's leaked into every part of cartesian() and the visualizations. So give me a few days to come up with a solution that does not involve so much dependencies in the axes and I'll let you know. How does that sounds?
OTHO, I made a few changes to master that relate to jshint and code standards, and also fixed some tests that were broken.

Honestly I am a bit dubious about how we could achieve your desire to
cleanse cartesian and the visualizations of the notions of multiple scales
while still supporting multiple scales and multiple axes.
With that said I understand not wanting to support multiple axes/scales
because it is such bad practice, but I don't have that choice I have to
support this stuff for better or worse.
Starting with your pseudo code which you attached above.  It could
theoretically work for leftYAxis/rightYAxis but I can't see how it could
work with many scales on a single axis (which is a requirement for me).
The fundamental issue is that I need the ability to apply a different scale
to each and every individual series on a cartesian chart, which means at a
bare minimum that each cartesian visualization will need to pass the series
to get the scale.
Now with all that negative stuff out of the way I am very interested to
hear what you come up with, and I too will spend time thinking about how I
could refactor this stuff so it doesn't affect cartesian and the
visualizations so much.
Another bit of "good" news in all of this is that line, scatter, column,
and bar (non-stacked) are the only chart types I would ever need to do this
for -- everything else (that I can think of) can't support multiple scales
or I don't need to support multiple scales with.  Therefore, I do think I
have fully completed the use-case and these are the only visualizations
that need to have 'multiple scale smarts'.  So while it is true that
multiple scales have leaked into the visualizations -- its not all of the
visualizations -- its not even apart of any new visualizations its just the
visualizations I have modified.  Of course this does nothing for your
concerns about the impact on cartesian...
Now as a starting point I could imagine making a subclass of cartesian
called complexCartesian (which would be used in place of cartesian) which
adds in the multi-scaling (and right y axis) code.  This though still
leaves all of the changes to the visualizations and the axis-scale-factory,
and the inclusion of the multi-linear-y-axis file.
I am still drawing a blank though about how to get around the conundrum of
visualizations which know nothing about multiple scales that support
multiple scales -- the only way I can think of to do that is to make it so
that the y function is a method on cartesian (or complexCartesian) which
takes as arguments the point (array element) to plot AND the series name OR
to make sure that the point always contains the series name plus this new y
method would also have to take a function which describes how to combine
d.y, d.y0 etc etc into a value to pass to a scale function.  Something like
this
complexCartesian.supportsMultipleScales = function() { return true; }
complexCartesian.y = function(d, modDfn) {
var which = this.axisFor(d);
return this.which + 'Scale';
}
line.y = _.bind(function(d) {
return this.y(d, function(d) { return d.y + (d.y0 || 0); }) + 0.5
}, this)
line.render = function() {
var data = ....
if (this.supportsMultipleScales())
data = data.map(function(series) { return
series.data.map(function(pt) { pt.name = series.name return pt; })})
........
}
Therefore I guess if you are willing to bear with the changes to
axis-scale-factory and to include my multi-linear-y-axis file I could strip
most of the changes out of cartesian.js into complex-cartesian.js.  I could
also then modify the visualizations I mentioned to always include the
series name in the point data if and only if complexCartesian is
constructed.
That is the best that I can think of at the moment.
On Mon, Mar 16, 2015 at 6:16 PM, Jaime del Palacio<EMAIL_ADDRESS>
wrote:

Hey, so far my thinking is that the multiple axes is not something I
specially want to support (bad practice and all that :), but I want to make
it easy for you to have a specific extension that allows for that. My
concern with the current implementation is that the concept of the multiple
axes get's leaked into every part of cartesian() and the visualizations. So
give me a few days to come up with a solution that does not involve so much
dependencies in the axes and I'll let you know. How does that sounds?
OTHO, I made a few changes to master that relate to jshint and code
standards, and also fixed some tests that were broken.
—
Reply to this email directly or view it on GitHub
https://github.com/forio/contour/pull/209#issuecomment-81964410.

Hi Billy,
After some refactor of cartesian(), I think I found a way of creating a multiAxes component that would work for multiple axes on the left or right sides, without leaking into cartesian or the visualizations. Take a look at branch 'axes' (https://github.com/forio/contour/tree/axes).
I added the code for the multiAxes component in the file examples/multi-axes.html
I'm sure there's still things to work out to make it resize and re-render correctly. Let me know what you think.

This structure does show promise and definitely solves my right axis
problem (esp when finished to support resizing, new data etc etc).
I think this solution could also be used as a basis to solve my multiple
scales on a single axis problem, but I think to do that either the
axis-scale-factory has to be opened up to external components OR my
multi-linear-y-axis needs to be a part of the contour project.
I have included an image of what I mean when I say multiple scales on a
single axis.
[image: Inline image 1]
On Wed, Mar 18, 2015 at 1:52 AM, Jaime del Palacio<EMAIL_ADDRESS>
wrote:

Hi Billy,
After some refactor of cartesian(), I think I found a way of creating a
multiAxes component that would work for multiple axes on the left or right
sides, without leaking into cartesian or the visualizations. Take a look at
branch 'axes' (https://github.com/forio/contour/tree/axes).
I added the code for the multiAxes component in the file
examples/multi-axes.html
I'm sure there's still things to work out to make it resize and re-render
correctly. Let me know what you think.
—
Reply to this email directly or view it on GitHub
https://github.com/forio/contour/pull/209#issuecomment-82757381.

Take a look at my latests commits in the axes branch, I think that change would allow you add any axis constructor to the _.nw.axes namespace and then use it as a type for the axisFactory, that way you can specify it in the type for the multi axis component...

Yes -- that works.
Do you want me to make this all work with resizing, and setting new data or
is that something you are planning on doing?
On Wed, Mar 18, 2015 at 4:28 PM, Jaime del Palacio<EMAIL_ADDRESS>
wrote:

Take a look at my latests commits in the axes branch, I think that change
would allow you add any axis constructor to the _.nw.axes namespace and
then use it as a type for the axisFactory, that way you can specify it in
the type for the multi axis component...
—
Reply to this email directly or view it on GitHub
https://github.com/forio/contour/pull/209#issuecomment-83158049.

Ok, let me merge that branch into master and then you can take it from the to do the work on the 'multiAxies' component. How's that?

Yes -- that works for me.  I assume from the way you are talking that you
want to keep all of the multi axis stuff out of the actual contour project,
instead making it something that I maintain externally? Or have I
mis-understood your intent?  I am happy to do it either way.
On Wed, Mar 18, 2015 at 5:24 PM, Jaime del Palacio<EMAIL_ADDRESS>
wrote:

Ok, let me merge that branch into master and then you can take it from the
to do the work on the 'multiAxies' component. How's that?
—
Reply to this email directly or view it on GitHub
https://github.com/forio/contour/pull/209#issuecomment-83185282.

Yes, that's exactly the idea. the multi-axes would be an external component that you can keep separate from the core contour repo, the idea is at some point to have a repository for people to contribute those external components if they like.


Use Terminal to print output instead of println in the space create command

Current behavior
The space create command is using println to print the command's output, which is a strategy that is being deprecated.
Desired behavior
Instead, the Terminal struct should be used to handle the output of every command.
Implementation details
The following snippet should be refactored:
https://github.com/build-trust/ockam/blob/1ab8c42659b9851384e0d523fc24522c7d674150/implementations/rust/ockam/ockam_command/src/space/create.rs#L66
You have to use the Terminal struct as follows to print the command output:
opts.terminal
    .stdout()
    .plain(space.output()?)
    .json(serde_json::json!(&space).into_diagnostic()?)
    .write_line()?;

Some tips for newcomers:

Create a new branch for the issue you are working on (don't push directly to your fork's develop branch)
Run cargo fmt. You can configure the editor to run it automatically everytime a file is saved
Run cargo clippy to make sure the code compiles + follows rust standards/best practices
You don't need to keep your branch updated with develop until there is a merge conflict. If you still want to update it, use git rebase develop instead of gir merge develop

We love helping new contributors! ❤
If you have questions or need help as you explore, please join us on Discord. If you're looking for other issues to contribute to, please checkout our good first issues.

Can I work on it?

@Tashuuuu That's awesome, this is all yours. Please let us know if you have any questions as you explore. You can also ask questions on the contributors discord https://discord.gg/RAbjRr3kds


linux/mac bots fail on 64-bit run-pass/bind-native-printf

http://<IP_ADDRESS>/logs/2011/10/30/2011-11-30T19:28:06Z-b5dfb73e-bf33-45bf-bfd2-4da8cce1d4c3.html

This test cases isn't about variadic arguments at all, so we can just pick a different native to use.

I have a fix for this, just haven't pushed it yet (pending try build).

Fixed in @fdebd1e2ef440312ac791d505af7dd089efa2499

Pushed.


Use path.sep and replace it to '/' in windows

Closes: https://github.com/metarhia/impress/issues/1441

[x] tests and linter show no problems (npm t)
[x] code is properly formatted (npm run fmt)
[x] added to changelog

Landed in https://github.com/metarhia/impress/commit/16f2d4760845d7c95e230641b0b5ebbe518724e2

Landed in https://github.com/metarhia/impress/commit/16f2d4760845d7c95e230641b0b5ebbe518724e2


Sweep Clock Color Themes

The sweep hand clock now has a number of colouring themes and saves the preferences to memory.

Nice - thanks!


GlyphLayout, improved glyph run bounds and whitespace wrapping.

Improves glyph run bounds
The bounds can still overlap due to kerning, but they are no longer off by an entire character. Instead of using a low x and higher xadvance to position the glyph in the right place, we now increase the x position to the start of the glyph and decrease the xadvance. The test was changed to help differentiate bounds from different runs.
Before:

After:

Fixes bounds when whitespaces wraps
This text has "T e". When the wrapping occurs so the space wraps, the bounds of the first wrapped glyph can be wrong. This was because the if (wrapIndex == 0) code path is taken instead of wrap() and it didn't clear lastGlyph.
Before:

After:

Fixes wrapping whitespace before a newline
This text is "AA BB \nEE". When the wrapping occurs so the space after "BB" wraps, a blank line appears. This was because we moved down a line for the wrapping, then newLine was true and moved down an extra line.
Before:

After:

Would be great to get eyes on this before merging. Maybe @TCreutzenberg and @tommyettinger are interested?

All the commits in the PR show I clearly don't know what I'm doing (guess I should have squashed before the PR), but the 2 files changed is right. We'll just be sure to squash before merging!

It looks like this definitely helps with word wrapping when there's a line break. What if there are two or more line breaks where it wraps? I'd think the initial whitespace would be ignored and later line breaks should be respected, right? The rest of this seems to clean up bounds all over, which may help so we don't need a patchwork of fixes with epsilon and font metrics. I like this whole PR, I'll probably approve in a review.
I always have a ton of commits backlogged in anything I do too. Not sure how to get Git to avoid that...

@NathanSweet Just tried it with my fonts and it works great. Yes, the kerning-overlap can't be avoided.
Code looks good.
If I may make one suggestion, I'd change the text in BitmapFontTest to:
text = "AA BB    [RED]EE[] T [GREEN]e[] V[YELLOW]a bb[] ([CYAN]5[]FFF)";
This includes a color-run with a space in it and the color-run which made problems for me 2 days ago. So basically it would cover more edgecases and past problems.

@NathanSweet I just created a new PR (https://github.com/libgdx/libgdx/pull/6582https://github.com/libgdx/libgdx/pull/6582) before looking at this one, it may lead to merge conflicts with this one, so you may want to include the comments into yours, then I can just close mine?

What if there are two or more line breaks where it wraps?
She works properly in that case. Eg for two newlines you get one newline taken care of by the wrapping, then the other one gives a blank line as normal.

I can't quite follow the logic when reading it as a git diff.
Indeed, it's hard to follow in an IDE with a debugger!

Oh, and thank you btw!
Sure, no problem! Glad to have more eyes on this code.

I wish we could have an elegant way of fixing this one:
https://github.com/libgdx/libgdx/issues/4672


Include logs to a custom location

This is for https://github.com/brson/rust-cookbook/issues/97

Thanks! Can you check why the Travis build is failing? The code might not compile.

I had to add extern crate log4rs in Cargo.toml.


Serve theme documentation from this repository and add PR previews

Currently, we store the documentation for our bundled myst themes in the mystmd repository. The documentation in this repository is a demo site of components for references.
By having the documentation for the theme in a separate repository, we have a few downsides:

Changes in functionality to this theme will require changes to documentation in a different space (mystmd.org).
Changes in functionality to this theme aren't easily previewed in PRs, because no local documentation is built as a preview.

I propose that we do the following things:

move all documentation that is related to the bundled myst themes into this repository (in docs/)
move the components site to a sub-directory like docs/components/
add a netlify PR preview for the documentation that uses the latest theme build in this repository
keep templating/theme documentation in mystmd if it is about web templating in general, and not these themes specifically.
embed the documentation for these themes into the mystmd.org docs so that it functionally looks the same that it does now (perhaps with "myst default themes" having a dedicated page)

I think you've identified some good points of improvement for our two-repo ecosystem. At the heart of this issue is the fact that we have three kinds of documentation:

MyST documentation (CLI)
MyST theme documentation
MyST theme component documentation

The problems we need to solve are:
We're currently taking the approach that most users should just go to mystmd.org for documentation in this ecosystem -- a departure from the JB1 approach which has docs split around the ecosystem. That introduces two problems; fragmentation and repetition of information and fragmentation of resources (i.e. multiple sites in your search engine).
However, this does mean that the coupling between components in terms of where the code lives is not so obvious.
So, my summary of the problems we need to solve in this space is:

We should not bless our own web themes too much; we want it to be obvious that developers can add their own and users can look for them.
We should have theme component documentation (Storybook)
We should make it possible to preview changes to our theme components
We should have documentation on our pre-designed themes
We should make it possible to preview changes to our pre-designed themes

It might not be super easy to solve all of these; there may be some trade-offs. But, I'll take a stab at something and see where we end up.

Just noting that I generally agree with all of the above, and: I suggest that we take an MVP approach here. For example if moving the docs over here would be complicated, it could be helpful to at least run a docs preview in our PRs of the mystmd.org/guide docs that use the latest assets in this repository so that we can see things. Then we could decide/deal with moving documentation later.

@choldgraf took the words right out of my mouth! I think this is actually the right step; figuring out the higher level changes will probably need to wait until the rest of the team are present.


Add versioning into tt-mlir

We need a strict versioning in format
major.minor.release (release is sometimes also called patch)

Major and minor versions will be deliberately tagged into the tree by user

when we release, we tag a commit vmajor.minor
Release number is a make custom command that auto-calculates the release number, which is the number of commits on top of tag vmajor.minor

to do:
tag head as release v0.0
add custom cmake option to auto-calculate # of commits on-top of major.minor version
create workflow that will tag commits with full release number eg. v0.0, the release/patch number is always auto-calculated
references
github workflow files
github tagging mechanism

Merged: c6b37f95ba1c09a6a8b75616508c4c3b964fd141


Histogram from values (or intervals) and counts

From Ani:
Is it possible to have hist draw a histogram based on a distribution table?
E.g. the inputs are intervals and the proportions in each interval (adding up to 100%). Output is a histogram.
At the moment hist takes the raw data as its input. We could simply generate the right number of values at the center of each interval, and provide that as the dataset.
I'm asking because it will be very helpful when students find bad histograms in the newspaper or journal articles and try to fix them. They won't have the raw data. They'll just have the distribution, badly represented. To fix the representation, they could work with the distribution by hand as in Stat 2/20/21, but could we do better in our course?
See the following for an example; scroll down till you see the bar graph.
http://www.cdc.gov/mmwr/preview/mmwrhtml/rr58e0821a1.htm

Yes, we can add a method to build a histogram from one column of values and one column of counts. I think that's sufficient.

I got close — you can now build a histogram from counts.
https://github.com/dsten/datascience/blob/master/datascience/tables.py#L880
However, we still need a way to generate two histograms from two columns of counts, and I'm not sure what the syntax should look like. E.g., imagine a three column table of ages, the counts of males by age and the counts of females by age. What expression should compare them?

Was talking with Ani today and she mentioned the same thing.
Let's suppose we have a table like this:
Age  | Male Counts | Female Counts
10   | 2           | 3
20   | 13          | 10
30   | 8           | 13
40   | 5           | 12
50   | 3           | 2
60   | 2           | 0
70   | 0           | 0
80   | 1           | 0
What if we instead of counts='Male Counts'to specify that the Male Counts column are the count values we have something like count_bins='Age'? Essentially, passing in the column used for bins instead of passing in the column used for counts? Then hist would produce two histograms in this case where the bins are the ages and the counts are the male/female counts.
This would also make the overlay argument more consistent.

Table.hist used to return a histogram as a table.  That was very handy.  Bins becomes one of the columns.  Then normalizing it by the total count gives a discrete probability distribution.  Total variational distance doesn't make much sense on histograms.  Right?

See #83 for my current take on this -- sounds very similar to what David Culler is talking about.

There is a version in table2hist branch.  See if you like it.   des ja
vous...  It is back to what hist used to do.  With the overlay, it creates
a column of the bins.  Otherwise, it creates a bin column for each
histogram.  Thus the table contains just what is in the pictures.  It
generates names for the columns similar to what pivot does.
David E. Culler
Friesen Professor of Computer Science
Electrical Engineering and Computer Sciences
University of California, Berkeley
On Fri, Sep 25, 2015 at 11:24 PM, davidwagner<EMAIL_ADDRESS>wrote:

See #83 https://github.com/dsten/datascience/issues/83 for my current
take on this -- sounds very similar to what David Culler is talking about.
—
Reply to this email directly or view it on GitHub
https://github.com/dsten/datascience/issues/54#issuecomment-143403258.

The counts is still there.  It just passes through to pyplot.hist.  You can
also pass normed=True and it will normalize it and produce the discrete
distribution.  Are friends at scipy already thought through all this.  We
pretty much just needed to not get in the way.  numpy.histogram does all
these things too.  pyplot.hist passes them through because you need them...
yep sure do.
I also through in Table.bar so that you could do something reasonable with
plotting the resulting tables.
David E. Culler
Friesen Professor of Computer Science
Electrical Engineering and Computer Sciences
University of California, Berkeley
On Sat, Sep 26, 2015 at 1:15 AM, David Culler<EMAIL_ADDRESS>wrote:

There is a version in table2hist branch.  See if you like it.   des ja
vous...  It is back to what hist used to do.  With the overlay, it creates
a column of the bins.  Otherwise, it creates a bin column for each
histogram.  Thus the table contains just what is in the pictures.  It
generates names for the columns similar to what pivot does.
David E. Culler
Friesen Professor of Computer Science
Electrical Engineering and Computer Sciences
University of California, Berkeley
On Fri, Sep 25, 2015 at 11:24 PM, davidwagner<EMAIL_ADDRESS>wrote:

See #83 https://github.com/dsten/datascience/issues/83 for my current
take on this -- sounds very similar to what David Culler is talking about.
—
Reply to this email directly or view it on GitHub
https://github.com/dsten/datascience/issues/54#issuecomment-143403258.


Stub api calls

Stub (do not mock)  all the calls related to the API, and configure the component so it only changes the base url.

What do you think about this http://sinonjs.org


APK size increases by 300MB+ when importing a library (flutter).

Good afternoon! I am writing an application on Flutter and decided to use your library: https://pub.dev/packages/google_ml_kit.
Before importing the library, the application size was 149MB. After importing and building the APK, the size increased to 420MB.
Question: if the download limit for Google Play is 150MB for APK, then how can I use the plugin? Can it be compressed?

Did you read our readme? There we explain that google_ml_kit is the umbrella plugin and there are also individual plugins for each API you can use: like face detection or text detection, etc. Depending of your app you should used one of those individual plugins and that will reduce the size of unnecessary APIs and models, unless your app uses all the APIs then you will need to use the umbrella plugin. Please check out our documentation.


how to configure client properties files under consul  in spring config server application

I am new to Consul and Cloud concepts in Spring. I am unable to configure properties under consul i.e. From client end whenever it fetching showing as in Logs "Located property source: CompositePropertySource {name='configService', propertySources=[MapPropertySource " but actually I want to get same properties as "Located property source: CompositePropertySource {name='consul', propertySources=[ConsulPropertySource"

That is from a different project, spring cloud consul

Do you want me to add another  spring cloud consul dependency in Config Server application level to get it as counsul service ?
In forums I am seeing as  default location is /config and all. Where should we create this /config folder i.e. inside server application resources folder?
Do weh ave any sample application for reference ?

There is no support for consul in config server.

Thank you @spencergibb.
Precisely my requirement is , I want to load  properties as
name='consul', propertySources=[ConsulPropertySource" .
How can I achieve this ?

You cannot thru config server right now.

You can do it without config server https://github.com/spring-cloud/spring-cloud-consul/blob/master/docs/src/main/asciidoc/spring-cloud-consul.adoc#distributed-configuration-with-consul

Thank you @spencergibb for your time and data.


Cannot load page after too much changes

Description
When I am changing pages in default Jaspr template too fast so page loading is too long.
Steps To Reproduce
https://github.com/schultek/jaspr/assets/2686906/6e68d38b-5dd3-4a98-bcb7-b6514ea5a4f4
Doctor Output
martin at Martins-MacBook-Air jaspr_project >>> jaspr doctor
[✓] Jaspr CLI (Version 0.12.0)
  • Dart Version 3.4.0 (stable) (Mon May 6 07:59:58 2024 -0700) on "macos_arm64" at /Users/martin/fvm/versions/3.22.0/bin/cache/dart-sdk/bin/dart
  • Running on macos Version 14.1 (Build 23B74) - Locale en-CZ
  • Analytics: Enabled

[✓] Current Project
  • Dependencies on core packages:
    • jaspr: ^0.12.0
    • jaspr_builder: ^0.12.0 (dev)
    • jaspr_web_compilers: ^4.0.9 (dev)
    • jaspr_router: ^0.4.1
  • Rendering mode: server
  • Uses jaspr compilers: true
  • Uses flutter embedding: false

Expected Behavior
Change pages without long loading.
Additional Context
Here are steps of project creation:

I could trace it to some weird behaviour of shelf when piping through the sse connection to the build_web_compilers server. I don't know how to fix it though.
However this only happens during development and not production.


nmstatectl: Allow to set multiple states

Signed-off-by: Till Maas<EMAIL_ADDRESS>

Coverage increased (+0.003%) to 65.898% when pulling e8725628eee44052c813a7704b21da3475768c77 on tyll:multiple_states into 118dac5f8621344efc3a18d55287091e992cba64 on nmstate:master.

ci test please

ci test please


Debug issue with typescript, nodemon, and external projects

Type: Bug
Thank you for anyone who is able to offer some insight about what is going on. VS Code debugging has always been finicky, but I've got a situation that I think should work and it isn't.
Issue:
I can set breakpoints in typescript and debug in 2 of my projects (server and common-internal), but not the 3rd (common-external). Why can't I debug common-external, and how do I set it up so I can? VS Code cannot find the source to bind the breakpoint.
I've created a simple repo to reproduce the issue I'm seeing: https://github.com/snotmare/debug-issue
Steps to reproduce:

Clone repo
Run 3 init tasks (for common-internal, common-external, and server)
Run 2 watch tasks (for common-internal and common-external)
Run the start server task
Run the debugger by attaching to the process
Set a breakpoint in server/src/index.ts (works)
Set a breakpoint in common-internal/src/utils.ts (works)
Set a breakpoint in common-external/src/external-utils.ts (does not work)

Project setup:

Typescript project with a utils class (common-internal).
NodeJS server project that imports common-internal and common-external.
Both of these projects are within the same folder, with a .vscode folder at the same root for task and launch config.

External project setup:

Typescript project with utils class (common-external).
This is setup exactly the same as common-internal, just renamed.
This has its own .vscode folder for task config.

The server project depends on the 2 common projects like this:
"dependencies": {
    "common-internal": "file:../common-internal",
    "common-external": "file:../../common-external/common-external",
    "express": "4.18.2"
},

I believe the issue is related to the folder structure, which looks like this:
root folder
- test-app
- - .vscode
- - common-internal
- - server
- common-external
- - .vscode
- - common-external

The folder structure needs to be this way because I want test-app to be in a git repo while common-external is in a separate git repo.
When I debug the server, why can't I set a breakpoint in common-external and debug it? Thank you for your help!
 I was able to make a change in my launch.json file that helped. I overwrote the outFiles section like this...
			"outFiles": [
				"${workspaceFolder}/**/*.js",
				"${workspaceFolder}/../common-external/**/*.js",
				"!**/node_modules/**"
			]

The trick was to point go up a folder to point to the external project. I found this by accident, so could the documentation on this be improved? It would be helpful to better understand the internal workings.
In my larger project, I made this same change and was also able to debug. However, it's hit and miss when it comes to debugging. Sometimes it works, but mostly it doesn't. I restart vs code, restart my projects, etc. When it doesn't work, it says it can't find the source code even though it's there. I also see the message that "It's taking a while to configure your breakpoints. You can speed this up by updating the 'outFiles' in your launch.json". I've done that similar to the code above.
My real project is a bit of a mono-repo. It contains 4 typescript projects, 5 nodejs servers, and an angular app. I usually have tsc --watch enabled for the typescript projects and use nodemon on the servers.
Is there an upper limit on the number of files that vs code can handle with debugging? Are there some performance metrics I could run to see why the debugger can't find the source files?

Yea, the outFiles change is what you need. By default, only sourcemaps within the workspace folder (excluding node_modules). We do have a docs section on source map discovery: https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_source-map-discovery

Is there an upper limit on the number of files that vs code can handle with debugging? Are there some performance metrics I could run to see why the debugger can't find the source files?

There is no upper limit. I would check to make sure that you didn't accidentally include any big extraneous folders in your outFiles -- and ensure the negation for node_modules is still there.
Logs might help...
/jsDebugLogs

Please collect trace logs using the following instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.
⚠ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to<EMAIL_ADDRESS>

Thanks for your help Connor! I did find that link explaining the sourcemap files. Perhaps the piece I was missing is where "workspaceFolder" actually points to. I had assumed it was one level higher than it was, but it turns out it points to the folder containing the .vscode folder.
I've run the debugger with the trace and attached that file. This is from the larger project, not the sample repo I originally posted about.
I did notice one thing earlier that helped. The nodejs server that I'm running uses our shared code from the other typescript projects. The package.json for our server contains dependencies like this:
"shared": "file:../shared",
"shared-server": "file:../shared-server",

If I start vs code and simply run the server, the debugger cannot find any breakpoints. However, if I start vs code, start the watch process for our shared typescript projects...
tsc --watch

... and then start the server, I have a much higher chance of vs code finding my breakpoints. I've attached a trace for the one that works as well (second attachment with the "-works" in the file path.
Thank you! I'd love to know more about how this works so I can improve our environment.
vscode-debugadapter-3ecd154d.json.gz
vscode-debugadapter-7613a7c0-works.json.gz

Does adding an extra negation for !../ts-base/**/node_modules/** resolve the issue?

Hey, that did help some! It definitely performs better, good call!
I am now seeing my breakpoints find the source a little over half the time. I managed to get a trace for both when it worked (first link) and when it was broke (2nd link).
vscode-debugadapter-e619ebd7.json.gz
vscode-debugadapter-0bc7bab9-broken.json.gz

Good to know. The glob behavior is something we can improve as well; automatically applying it if we see a relative pattern navigates outside the workspace folder.

I managed to get a trace for both when it worked (first link) and when it was broke (2nd link).

Are you sure you're connecting to the right process in the broken one? Looking at the scripts loaded by the runtime in the trace log, they're mostly from node_modules/nodemon, while in the working one there's no nodemon sources at all.

Ok, you're right. I wasn't paying attention to that before, but this is tied to which process you pick. I was always picking the top process (assuming it was the most recent). After paying attention more, I noticed the order of the top 2 processes changes (see screen shot)...

I tested the following scenarios and found these results:

Restart server, pick nodemon process (broken)
Restart server, pick not nodemon process (works)
Leave server running, pick nodemon process (still works)
Restart server, pick nodemon process (borken)
Leave server running, pick not nodemon process (still broken)

Is there a way to weed out the processes from this list I should not be using for debugging? If you want any traces with these scenarios, I'll be happy to provide them.
Thanks again for all your help!

Leave server running, pick not nodemon process (still broken)

I think this one is still unexpected. I've opened issues to track the other two improvements we've talked about.

Ok, I've run through those scenarios and generated traces. The file labels match these scenarios:

Restart server, pick nodemon process (broken)
Leave server running, pick not nodemon process (still broken)
Restart server, pick not nodemon process (works)
Leave server running, pick nodemon process (still works)

[vscode-debugadapter-ff37efdf-1-nodemon-broken.json.gz](https://github.com/microsoft/vscode/files/10231173/vscode-debugadapter-ff37efdf-1-nodemon-
vscode-debugadapter-79a57277-2-not-nodemon-broken.json.gz
broken.json.gz)
vscode-debugadapter-2b780da5-3-not-nodemon-works.json.gz
vscode-debugadapter-18c76ecb-4-nodemon-works.json.gz

Leave server running, pick not nodemon process (still broken)

This looks like Nodemon again 😬  you can also see the scripts if you use the Loaded Sources view.

Ya, that makes sense. It appears that if I debug the wrong process to begin with, I have to restart my server before attaching to the correct process. Now that I know this, I feel better about debugging. Thanks for your help!

No problem, thanks for your patience and info 🙂  I will close this out since I captured the work in the aforelinked issues.


Problem with schema registry cache- Workaround

Hi,
I realized a very low number of messages produced  when using avro with schema registry with 30 vu (less than 100 per second):
My config looks like
  writer.produce({
    messages:messages,
    //this option generate magic number error valueSchema:valueSchema ,
    config:kafkaConfiguration
  })
}

where kafkaConfiguration is:
export const kafkaConfiguration = {
  consumer: {
    keyDeserializer: STRING_DESERIALIZER,
    valueDeserializer: AVRO_DESERIALIZER,
  },
  producer: {
    keySerializer: STRING_SERIALIZER,
    valueSerializer: AVRO_SERIALIZER,
  },
  schemaRegistry: {
    url: schemaRegistry,
    tls: {
      enableTls: enableTlsSchemaRegistry,
      insecureSkipTlsVerify: true,
      clientCertPem: "/certs/cert.pem",
      clientKeyPem:  "/certs/cert.key",
      serverCaPem:   "/certs/rootg3_b64.cer",
    },
  },
};

Taking a look to the library github.com/riferrei/srclient v0.5.4 I realized this behaviour in the cache of schemaRegistyClient.go:
func (client *SchemaRegistryClient) getVersion(subject string, version string) (*Schema, error) {

	if client.getCachingEnabled() {
		cacheKey := cacheKey(subject, version)
		client.subjectSchemaCacheLock.RLock()
		cachedResult := client.subjectSchemaCache[cacheKey]
		client.subjectSchemaCacheLock.RUnlock()
		if cachedResult != nil {
			return cachedResult, nil
		}
	}

RLock has this doc:

// RLock locks rw for reading.
//
// It should not be used for recursive read locking; a blocked Lock
// call excludes new readers from acquiring the lock. See the
// documentation on the RWMutex type.

So I decided to modify a bit schema_registry.go like this and now woks with more than 2000 per second with the same 30vu
var cache = make(map[string]*srclient.Schema)

// GetSchema returns the schema for the given subject and schema ID and version.
func GetSchema(
	client *srclient.SchemaRegistryClient, subject string, schema string, schemaType srclient.SchemaType, version int,
) (*srclient.Schema, *Xk6KafkaError) {
	// The client always caches the schema.
	var schemaInfo *srclient.Schema
	var err error
	// Default version of the schema is the latest version.

	value, isMapContainsKey := cache[subject]

	if isMapContainsKey {
		return value, nil
	}

	if version == 0 {
		schemaInfo, err = client.GetLatestSchema(subject)
	} else {
		schemaInfo, err = client.GetSchemaByVersion(subject, version)
	}

	if err == nil {
		cache[subject] = schemaInfo
	}

	if err != nil {
		return nil, NewXk6KafkaError(schemaNotFound,
			"Failed to get schema from schema registry", err)
	}

	return schemaInfo, nil
}

I tested it in local

Hey @oscar067,
I am refactoring this feature in this branch completely, and removing many of these nuisances. It's still WIP.

I was checking the changes, but at some point, if tests makes use of the schema registry cache, the problem still be there.
Solution can be to github.com/riferrei/srclient v0.5.4 changing it's implemetation or a similar , to the proposed, cache mechanims is in place.
Problems I had not were only permrfomance of the tests exceptions like were in place.
time="2022-08-05T10:44:10Z" level=warning msg="Failed to create or get schema, manually encoding the data" error="Failed to get schema from schema registry, OriginalError: %!w(*url.Error=&{Get

Interesting! Maybe we should ask the author of the original package for his opinion here?
@riferrei
What do you think about this? Should this change land in your library instead?

So what is the proposal here? Remove the usage of the caching from the library?
Apropos, it is possible to programmatically disable the caching, so all interactions with SR happen without any locks. That way you can remove it from the critical path. That said; it is a bit weird having the srclient in the critical path of highly concurrently applications. Ideally, the schema should be managed before any interaction with producers/consumers and then once the schema is fetched — it is used within the concurrent transactions.
Let me know how can I help. I welcome changes in the project. If none of this help, we can think of a PR to change the caching behavior. 🙂
— @riferrei

Cached is needed,
I'll try to test the code with https://pkg.go.dev/sync#Map, and let you know the results, If not sucessfull for the xk6 kafka plugin I would recommend the workaround.
"The Map type is optimized for two common use cases: (1) when the entry for a given key is only ever written once but read many times, as in caches that only grow, or (2) when multiple goroutines read, write, and overwrite entries for disjoint sets of keys. In these two cases, use of a Map may significantly reduce lock contention compared to a Go map paired with a separate Mutex or RWMutex."
Many thanks fro the answer


Make clear where to run DDC commands

Fixes #792

Deploy preview ready!
Built with commit 0ffee96b0a1b01fe4512ae0e2c8a0da50359aff6
https://deploy-preview-855--docker-docs.netlify.com


Developing locally requires a page refresh to render styles

As I'm developing locally, I need to always do a full page refresh the first time I'm visiting a page that hasn't been visited before. I see the following message in the terminal:
[ event ] client pings, but there's no entry for page: /login
[ event ] build page: /login

So, I assume that it needs to compile the first time and there may be some sort of race condition or delay when it comes to styling?! Any thoughts on how to resolve this?
My next.config.js:
const withSass = require('@zeit/next-sass');
module.exports = withSass();

Some of the scripts inside of package.json:
  "scripts": {
    "dev": "node server/server.js",
    "build": "next build",
    "start": "cross-env NODE_ENV=production node server/server.js",
    "lint": "eslint ./components/*/*.js "
  },

My server.js file:

const next = require('next');
const express = require('express');
const nextI18NextMiddleware = require('next-i18next/middleware');

const { PORT, IS_PROD } = require('../__config__/env');
const nextI18next = require('../i18n');

// create the express and next instances
const server = express();
const app = next({ dev: !IS_PROD });
const handle = app.getRequestHandler();

// start the app
app.prepare()
  // start Express server and serve the
  .then(() => {
    server
      .use(nextI18NextMiddleware(nextI18next))
      .get('*', handle)
      .listen(PORT, (error) => {
        if (error) throw error;
        console.info(`\nServer listening on: http://localhost:${PORT}\n`);
      });
  })
  .catch((ex) => {
    console.error(ex.stack);
    process.exit(1);
  });

I believe this is related to/is #445/#449, seems CSS files generally doesn't get transpiled on/for the server for some reason so it doesn't get loaded until page refresh.

@timneutkens This is an exact duplicate of #482.

Yup, @bryandowning! Mainly because I'm not sure which repo this should be handled in... Feel free to close the incorrect one.

I believe this is covered in #282
I was having the same issue and this fixed it for me (it's definitely a hack, but acceptable IMO for local dev while the problem gets resolved):
// This is a bit of a hack to ensure styles reload on client side route changes.
// See: https://github.com/zeit/next-plugins/issues/282#issuecomment-480740246
if (process.env.NODE_ENV !== 'production') {
  Router.events.on('routeChangeComplete', () => {
    const path = '/_next/static/css/styles.chunk.css'
    const chunksSelector = `link[href*="${path}"]`
    const chunksNodes = document.querySelectorAll(chunksSelector)
    const timestamp = new Date().valueOf()
    chunksNodes[0].href = `${path}?${timestamp}`
  })
}

Nice! Thanks for the quick workaround, @bryandowning!  Much appreciated


ResourceToken test for Bounded and Strong consistency

We have bug in barrier request where resource token is not supported. We have to run ResourceToken test against Bounded and Strong consistency.

@jeet1995  can you please test this out, thanks!


feat: transpile dependencies in node_modules

TODOs:

[x] A simplified dependencies babel preset for node_modules, to reduce the performance overhead I don't think there will be much overhead because the default preset only adds very few custom features. It would also be against the users' intention if they choose a different preset for their project
[x] Decide whether to opt-in or opt-out of this feature Should be opt-out. And we should continue improving the cache configuration to speed up incremental builds.
[ ] Test cases
[ ] Revise the transpileDependencies documentation
[ ] Mention this feature in the migration documentation

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Other information:

🤔 I think it might make more sense to reuse the existing transpileDependencies option than to add a new command-line flag.
I'll work on a new PR to just accept transpileDependencies: true as an option to transpile all dependencies.