feat: implement opentsdb query

Rationale
Opentsdb write protocol is already supported, this PR implement query protocol.
Detailed Changes

Convert opentsdb query requests into datafusion logical plans
Convert the RecordBatch format of the query results into the return response format of the opentsdb query requests

Test Plan

Existing tests
add new unit tests

There are some conflicts now, will now new PR to fix this.


Aligned baselines of location and jobs in job-list.

The goal was to make the baseline of the H2 text (the location of the jobs) and the first row of job card text to the right be aligned.
After some trial and error, I found that switching to flexbox to do the layout was the only way the align-items: baseline; had the desired effect consistently in Chrome, Firefox and Safari.
Maintaining the CSS grid-based layout didn't work everywhere. Only having flex on the outer job-list component but continuing to use CSS columns on the job cards didn't work in Firefox. etc.

@danbull Good spot! I've just pushed a fix for that issue


Exception thrown when loading DPDB (cross origin error)

I am getting an exception thrown when webvr-polyfill tries loading the online DPDB. The browser throws a CORS exception and the polyfill fails to load. To make the code more robust, I suggest wrap a try and catch around the code, ie:
function Dpdb(fetchOnline, onDeviceParamsUpdated) {
  // Start with the offline DPDB cache while we are loading the real one.
  this.dpdb = DPDB_CACHE;

  // Calculate device params based on the offline version of the DPDB.
  this.recalculateDeviceParams_();

  // XHR to fetch online DPDB file, if requested.
  if (fetchOnline) {
    // Set the callback.
    this.onDeviceParamsUpdated = onDeviceParamsUpdated;

    try {
      var xhr = new XMLHttpRequest();
      var obj = this;
      xhr.open('GET', ONLINE_DPDB_URL, true);
      xhr.addEventListener('load', function() {
        obj.loading = false;
        if (xhr.status >= 200 && xhr.status <= 299) {
          // Success.
          obj.dpdb = JSON.parse(xhr.response);
          obj.recalculateDeviceParams_();
        } else {
          // Error loading the DPDB.
          console.error('Error loading online DPDB!');
        }
      });
      xhr.send();
    } catch(e) {
      // Error loading the DPDB.
      console.error('Error loading online DPDB!');
    }
  }
}

Hum. No longer able to reproduce this error. Maybe the problem has been corrected on the server, or maybe I was mistaken about the symptoms.

I am seeing this error again. I suggest implementing the fix above as the server seems to occasionally reject CORS requests for the PBDB.

Where is the line that's throwing? Maybe an error handler xhr.addEventListener('error', ...) would work, I'm surprised the try/catch block solves this

I have tried reproducing this error on numerous browsers and I have been unable to reproduce it using a cross-origin request. I believe you are correct, my explanation does not seem to be correct.
What is strange is that on at least two occasions I have had my WebVR apps crash and adding the try/catch has enabled them to work again. I recall seeing the CORR warning on the browser console, but perhaps something else unrelated is triggering that.
Given that this problem seems to occur infrequently, it's very hard to troubleshoot, but I will keep an eye out for it. At the moment, all I can think of is that maybe the transfer is succeeding but the data is bad and perhaps JSON.parse is throwing an exception?

It's possible we could be getting back some non-JSON parseable object which would throw, but that still wouldn't be catchable due to async XHR call. An example of try/catch wrapped around an async call that is not caught:
function test () {
  try {
    setTimeout(function(){ throw new Error('not caught!') }, 10);
  } catch(e) { console.error('caught!!!!') }
}

Do you see any other errors logged while encountering it? Does it always crash whenever you do encounter the CORS warning?

Closing this issue -- please reopen if you see this issue again or have more information -- thanks!


Retrieve link HTML title

When shortening an URL, Firefly should try to retrieve the remote HTML page and extract the title for display in the admin panel.

I'll do this one if you don't mind.

Go right ahead! Feel free to discuss options first here or on gitter.

My first thought was just to use nokogiri in ItemRepository#create_from_url. However, that might slow down the create action noticeably.  We could also put the process in a worker along with any re-hosting tasks created at a later point. The problem with that, however, is that it might make it more difficult to deploy and less beginner friendly.

Note that nokogiri is already a dependency in firefly.

I think workers will be needed anyway, especially when we're going to re-host images. Sidekiq is my favourite as it's fast and not too much rails-oriented. We can figure out deployment later. Nokogiri seems like a good choice.

Ok, I'll go for Sidekiq + Nokogiri then.


fix: Misleading Withdraw Amount wording in Offers

PR Type

[ ] Bugfix
[ ] Feature
[x] Refactoring

Context
❗pls don't merge without @exezbcz 's green light
if the trade is active: Cancel Offer/Swap
if the trade is expired: Withdraw Amount has been changed to Withdraw Offer/Swap, should this also be red ?

[x] Closes #11237

Screenshot 📸

[x] My fix has changed something on UI;

QA
https://github.com/user-attachments/assets/04ff5edf-df8f-418a-86af-95a79653e3db
https://github.com/user-attachments/assets/fa20e62f-2c9a-4a2f-9c99-66d666b24466

looks good! thank you


feat: track memory consumers for GreedyMemoryPoolState

Which issue does this PR close?

Closes #6934
Rationale for this change

What changes are included in this PR?

Modified GreedyMemoryPool and FairMemoryPool to keep track of all it's consumer such that they can be dumped for debugging.
The output for the debug looks as follows:

Are these changes tested?

Are there any user-facing changes?

This looks very cool!

Benchmark results (I don't really see any noticeable change). Not sure why it looks like this branch is faster in some cases. I'll rerun to double check
--------------------
Benchmark tpch_mem.json
--------------------
┏━━━━━━━━━━━━━━┳━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┓
┃ Query        ┃ main_base ┃ df-mem-pool_6934_debug-dump-memory-pool ┃        Change ┃
┡━━━━━━━━━━━━━━╇━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━┩
│ QQuery 1     │  209.82ms │                                208.29ms │     no change │
│ QQuery 2     │   42.70ms │                                 43.69ms │     no change │
│ QQuery 3     │   76.14ms │                                 76.32ms │     no change │
│ QQuery 4     │   74.19ms │                                 73.08ms │     no change │
│ QQuery 5     │  120.29ms │                                118.37ms │     no change │
│ QQuery 6     │   16.58ms │                                 15.76ms │     no change │
│ QQuery 7     │  310.74ms │                                300.37ms │     no change │
│ QQuery 8     │   74.19ms │                                 74.38ms │     no change │
│ QQuery 9     │  124.90ms │                                123.22ms │     no change │
│ QQuery 10    │  150.40ms │                                147.62ms │     no change │
│ QQuery 11    │   34.56ms │                                 34.43ms │     no change │
│ QQuery 12    │   66.94ms │                                 64.90ms │     no change │
│ QQuery 13    │   83.11ms │                                 84.24ms │     no change │
│ QQuery 14    │   24.58ms │                                 24.65ms │     no change │
│ QQuery 15    │   55.08ms │                                 54.35ms │     no change │
│ QQuery 16    │   45.64ms │                                 45.04ms │     no change │
│ QQuery 17    │  169.01ms │                                158.65ms │ +1.07x faster │
│ QQuery 18    │  462.15ms │                                448.99ms │     no change │
│ QQuery 19    │   63.04ms │                                 58.88ms │ +1.07x faster │
│ QQuery 20    │  114.51ms │                                113.25ms │     no change │
│ QQuery 21    │  350.09ms │                                344.54ms │     no change │
│ QQuery 22    │   31.29ms │                                 29.17ms │ +1.07x faster │
└──────────────┴───────────┴─────────────────────────────────────────┴───────────────┘
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━┓
┃ Benchmark Summary                                      ┃           ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━┩
│ Total Time (main_base)                                 │ 2699.94ms │
│ Total Time (df-mem-pool_6934_debug-dump-memory-pool)   │ 2642.17ms │
│ Average Time (main_base)                               │  122.72ms │
│ Average Time (df-mem-pool_6934_debug-dump-memory-pool) │  120.10ms │
│ Queries Faster                                         │         3 │
│ Queries Slower                                         │         0 │
│ Queries with No Change                                 │        19 │
└────────────────────────────────────────────────────────┴───────────┘

┏━━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┓
┃ Query        ┃  main_base ┃ df-mem-pool_6934_debug-dump-memory-pool ┃        Change ┃
┡━━━━━━━━━━━━━━╇━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━┩
│ QQuery 0     │     0.90ms │                                  0.93ms │     no change │
│ QQuery 1     │    91.92ms │                                 86.94ms │ +1.06x faster │
│ QQuery 2     │   193.55ms │                                192.43ms │     no change │
│ QQuery 3     │   202.04ms │                                194.44ms │     no change │
│ QQuery 4     │  2035.67ms │                               2064.17ms │     no change │
│ QQuery 5     │  2634.69ms │                               2710.60ms │     no change │
│ QQuery 6     │    80.50ms │                                 83.28ms │     no change │
│ QQuery 7     │    96.91ms │                                 91.12ms │ +1.06x faster │
│ QQuery 8     │  3141.36ms │                               3072.50ms │     no change │
│ QQuery 9     │  2238.23ms │                               2249.01ms │     no change │
│ QQuery 10    │   778.65ms │                                805.28ms │     no change │
│ QQuery 11    │   851.89ms │                                892.85ms │     no change │
│ QQuery 12    │  2480.74ms │                               2476.18ms │     no change │
│ QQuery 13    │  4782.56ms │                               4655.77ms │     no change │
│ QQuery 14    │  2708.77ms │                               2730.93ms │     no change │
│ QQuery 15    │  2265.00ms │                               2311.53ms │     no change │
│ QQuery 16    │  5628.48ms │                               5469.02ms │     no change │
│ QQuery 17    │  5499.17ms │                               5365.51ms │     no change │
│ QQuery 18    │ 11546.73ms │                              11089.49ms │     no change │
│ QQuery 19    │   160.21ms │                                156.05ms │     no change │
│ QQuery 20    │  2627.86ms │                               2683.35ms │     no change │
│ QQuery 21    │  3367.59ms │                               3493.11ms │     no change │
│ QQuery 22    │  9249.51ms │                               9366.63ms │     no change │
│ QQuery 23    │ 21063.00ms │                              21867.58ms │     no change │
│ QQuery 24    │  1325.68ms │                               1395.85ms │  1.05x slower │
│ QQuery 25    │  1149.54ms │                               1184.26ms │     no change │
│ QQuery 26    │  1461.56ms │                               1491.37ms │     no change │
│ QQuery 27    │  3855.43ms │                               3903.53ms │     no change │
│ QQuery 28    │ 30624.92ms │                              27627.27ms │ +1.11x faster │
│ QQuery 29    │  1061.67ms │                               1031.11ms │     no change │
│ QQuery 30    │  2473.21ms │                               2359.27ms │     no change │
│ QQuery 31    │  3170.14ms │                               3067.15ms │     no change │
│ QQuery 32    │ 16379.80ms │                              15484.19ms │ +1.06x faster │
│ QQuery 33    │ 12534.18ms │                              11905.42ms │ +1.05x faster │
│ QQuery 34    │ 13092.84ms │                              12631.76ms │     no change │
│ QQuery 35    │  3839.99ms │                               3575.27ms │ +1.07x faster │
│ QQuery 36    │   414.06ms │                                434.18ms │     no change │
│ QQuery 37    │   253.10ms │                                245.90ms │     no change │
│ QQuery 38    │   195.16ms │                                191.95ms │     no change │
│ QQuery 39    │  1094.19ms │                               1051.57ms │     no change │
│ QQuery 40    │    84.61ms │                                 86.44ms │     no change │
│ QQuery 41    │    81.51ms │                                 79.40ms │     no change │
│ QQuery 42    │    89.56ms │                                 89.58ms │     no change │
└──────────────┴────────────┴─────────────────────────────────────────┴───────────────┘
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━┓
┃ Benchmark Summary                                      ┃             ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━┩
│ Total Time (main_base)                                 │ 176907.09ms │
│ Total Time (df-mem-pool_6934_debug-dump-memory-pool)   │ 171944.20ms │
│ Average Time (main_base)                               │   4114.12ms │
│ Average Time (df-mem-pool_6934_debug-dump-memory-pool) │   3998.70ms │
│ Queries Faster                                         │           6 │
│ Queries Slower                                         │           1 │
│ Queries with No Change                                 │          36 │
└────────────────────────────────────────────────────────┴─────────────┘

Benchmark results (I don't really see any noticeable change). Not sure why it looks like this branch is faster in some cases. I'll rerun to double check

I am also surprised this branch is faster.
Thank you for the review. Will address the comments shortly.

I reran the benchmarks and basically they showed similar results: performance differences that were likely mostly noise

Marking as a draft so it is clear this PR is not waiting on reviews for now. I am trying to keep our review backlog down. Please mark this as ready for review when it is ready for another look

@alamb a soft bump on this PR for another review.

Thansk @asimsedhain  -- sorry I was out last week. I will put this on my review queue for tomorrow

Thanks @asimsedhain -- this looks great. My only concern is about using saturating_sub rather than checked_sub as it could potentially mask bugs, but otherwise I think this PR looks good to go.
Sorry again for the delay in review

True, I didn't consider that it could mask potential bugs. Replaced it with checked add.
Thank you for the review!

Thanks @asimsedhain

I believe I found the reason why the CI is failing after adding the checked_sub calls.
I traced out all the calls issued to memory pool in the test aggregate_source_with_yielding_with_spill .
    1 Register: GroupedHashAggregateStream[0]
    2 GroupedHashAggregateStream[0] about to grow. additional: 120 before grow used: 0 after grow used: 120
    3 GroupedHashAggregateStream[0] about to shrink. shrink: 120 before shrink used: 120 after shrink used: 0
    4 Unregister: GroupedHashAggregateStream[0]
    5 Register: GroupedHashAggregateStream[0]
    6 Register: GroupedHashAggregateStream[0]
    7 GroupedHashAggregateStream[0] about to grow. additional: 208 before grow used: 0 after grow used: 208
    8 GroupedHashAggregateStream[0] about to grow. additional: 120 before grow used: 0 after grow used: 328
    9 GroupedHashAggregateStream[0] about to shrink. shrink: 48 before shrink used: 328 after shrink used: 280
   10 GroupedHashAggregateStream[0] about to shrink. shrink: 40 before shrink used: 280 after shrink used: 240
   11 GroupedHashAggregateStream[0] about to shrink. shrink: 120 before shrink used: 240 after shrink used: 120
   12 Unregister: GroupedHashAggregateStream[0]
   13 GroupedHashAggregateStream[0] about to grow. additional: 348 before grow used: 0 after grow used: 468
   14 GroupedHashAggregateStream[0] about to grow. additional: 1248 before grow used: 0 after grow used: 1716
   15 GroupedHashAggregateStream[0] about to grow. additional: 120 before grow used: 0 after grow used: 1836
   16 GroupedHashAggregateStream[0] about to shrink. shrink: 36 before shrink used: 1836 after shrink used: 1800
   17 GroupedHashAggregateStream[0] about to grow. additional: 36 before grow used: 0 after grow used: 1836
   18 GroupedHashAggregateStream[0] about to shrink. shrink: 36 before shrink used: 1836 after shrink used: 1800
   19 GroupedHashAggregateStream[0] about to shrink. shrink: 12 before shrink used: 1800 after shrink used: 1788
   20 GroupedHashAggregateStream[0] about to shrink. shrink: 56 before shrink used: 1788 after shrink used: 1732
   21 GroupedHashAggregateStream[0] about to shrink. shrink: 1596 before shrink used: 1732 after shrink used: 136
   22 GroupedHashAggregateStream[0] about to shrink. shrink: 136 before shrink used: 136 after shrink used: 0
   23 Unregister: GroupedHashAggregateStream[0]

On line 5 and 6, two consumers register themselves with the same name (these 2 aggregation happen here].
Seems like assuming each consumer to have a unique name is not correct.
Another approach I can think of right now is to store a Weak ref to the memory consumer but I believe that might change the MemoryPool Api.
@alamb could you let me know if you have any suggestion on how to proceed forward?

Hi @asimsedhain  - I have this PR on my list to review, but I sadly have limited bandwidth this week

Hi @asimsedhain - I have this PR on my list to review, but I sadly have limited bandwidth this week

No worries @alamb. Whenever you get the free time.
I will try to see if I can implement the approach I mentioned above.

Seems like assuming each consumer to have a unique name is not correct.

Introduce an ID field to the memory consumer, track memory usage with consumer ID, and do ID -> Name conversion at the time of usage dump?

I am sorry @asimsedhain  -- I am struggling to find the contiguous time needed to review this PR as it makes changes that look potentially disruptive in a very important subsustem (the memory manager)
I actually think it is a really important debugging feature (e.g. @westonpace  was just asking me the other day about where the memory was going when a query hit the greedy pool's memory limit)

Yes, I'll chime in a bit as I did end up finding the root issue.  My plan had both SortExec and SortPreservingMergeExec and I had incorrectly assumed SortPreservingMergeExec was not a spillable operator and so I was confused why I was getting out-of-memory errors.  Having a tool like you've shown that would help to visualize memory usage would have allowed me to figure that out more quickly.
Also, we have some customers that want to know, in great detail, why various operations need RAM and what the limits of that RAM will be.  I think this could be just a start into greater RAM observability.

Converting to draft -- I am sorry this one never quite made it in.

Note that the need for some tracking of memory consumers has been raised again. Not sure if we plan on reviving/reusing some of the work done already here by @asimsedhain  as a first step.

My concern with this PR was that I could not quite convince myself / find the time to ensure the complexity was necessary... I feel bad we didn't find time to get it over the line. Maybe we can revive it


Add/Fix History Section in IEx Reading

The History Section of the IEx reading was not working correctly.
History
You can retrieve previously run commands in the IEx shell by pressing the Up and Down arrow keys.
Each IEx session stores its history but not the history of previous IEx sessions.
If you would like to preserve history between IEx sessions, you can run the iex command
with the --erl flag.

$ iex --erl "-kernel shell_history enabled"

Alternatively, refer to the Shell History documentation
to enable shell_history for your whole system.
It needs to be redone.

Deciding to omit this, as it's extra setup and not 100% necessary for most students to complete.


feat: Consider primary and secondary rate limits when choosing tokens

What does this PR do?:
Alternate to https://github.com/redhat-appstudio/application-service/pull/307. Instead of using a callback function to handle the secondary rate limiting, we check the response from GitHub, and manually handle it there.
This PR adds checks for Primary and Secondary rate limits when choosing tokens.
When HAS goes to initialize a new GitHubClient object, it now does the following:
For Primary Rate Limits:

HAS will now check the Core and Search limits for the user associated with the client
If the Core limit has less than 10 available requests (out of 5000), or if the Search limit has 0 or 1 available requests (out of 30), HAS will attempt to select another token
If there are no further tokens available that aren't rate limited, an error will be returned

For Secondary Rate Limits:

A new field has been added to the GitHubClient struct, SecondaryRateLimit
When go-github-ratelimit detects a secondary rate limit, the SecondaryRateLimit rate limited field will be set to true

By way of a custom callback function

When a token is selected, after checking the primary rate limit, HAS will check the SecondaryRateLimit field.

If it's true, HAS will attempt to retrieve another token until there are no more un-ratelimited tokens available
If it's false, the token is returned

Which issue(s)/story(ies) does this PR fixes:
https://issues.redhat.com/browse/DEVHAS-344
https://issues.redhat.com/browse/DEVHAS-345
PR acceptance criteria:

[x] Unit/Functional tests

[ ] Documentation

[ ] Client Impact

How to test changes / Special notes to the reviewer:

This likely isn't needed anymore, but keeping this PR open as an alternate for the meanwhile


please stop doing no sense commits and updates

Due Diligence

[X] I have done my due diligence

What can we help you with?
you are sending multiple useless updates, just don't do useless commits

I will do what I please.

They are not useless. Every Raspotify update may also represent updates in the librespot fork, which are not a part of this repo. What may look like stupid updates are actually needed otherwise if a change happens in the librespot repo I can not do a new release unless there is a change in the Raspotify repo.

okay, sorry for the issues, still thanks for the great tool, and good luck :)


Some instructional links or tutorial videos?

Hello! I'm curious about how QGIS makes map elements. Can you share instructional links or tutorial videos? Thank you!

@yulpun Hello! I'm sorry but there is no instruction, and unfortunately, this repository is inactive... We are currently using Lanelet2.


Ability to search movies by actor name

This change adds the ability to find movies with actors in the cast as specified by the user input.
Changes:

Added the ability to search for movies with specific actors in them
Added the ability for users to choose this option on the menu

Good job


Chinese Traditional Translation

Details of Changes
Add details of changes here.

Updated the translation file

Validation
How did you test these changes?

[x] Built and ran the app

I'm sorry for I accidentally deleted the repository :(

The file is a txt

Fixed

Are you sure? I see that the new file is a txt again

Thank you!


Bump active_utils dependency

We have moved some logic from Shopify to ActiveUtils here and now in order to remove it from Shopify we need to bump this gem's dependency as well.

:+1:

ddooiitttt

Is there a plan to bump active_utils in shopify? With this PR offsite_payments requires a newer version than shopify is using cc @ThereExistsX


How to pass headers while using getServerSideProps

We want to prefetch data by using getServerSideProps. Do we really need to pass headers directly to graphql.request function? Is it possible that following code may work?
export const getServerSideProps = (async context => {
  const { id: postId } = context.query;

  const headers = context.req.headers;
  const accessToken = headers['app_header'];

  context.res.setHeader('new_header', accessToken);

  const data =  await graphQLClient.request(query, { postId });

  return data;
}) satisfies GetServerSideProps;

I wouldn't like to pass headers as second argument to the function, since we use react-query ( and we would need to disable eslint deeps rule ).

If someone is interested, I noticed that graphql-request adds possibility to setHeader directly to the object..
export const getServerSideProps = (async context => {
  const { id: postId } = context.query;

  const headers = context.req.headers;
  const accessToken = headers['app_header'];

  graphQLClient.setHeader('new_header', accessToken); <--- this line

  const data =  await graphQLClient.request(query, { postId });

  return data;
}) satisfies GetServerSideProps;

Closing this issue :)

If someone is interested, I noticed that graphql-request adds possibility to setHeader directly to the object..
export const getServerSideProps = (async context => {
  const { id: postId } = context.query;

  const headers = context.req.headers;
  const accessToken = headers['app_header'];

  graphQLClient.setHeader('new_header', accessToken); <--- this line

  const data =  await graphQLClient.request(query, { postId });

  return data;
}) satisfies GetServerSideProps;

Closing this issue :)


Local ddb

local-ddb flag. Blatantly flag local usage; don't support running ddb instances on other ports.
/cc @ejconlon

yeah, this is more what I had in mind as well
:fried_shrimp:


Break Classes Into Individual Files

Each class should exist as individual files (Sprite.coffee, Viewport.coffee, etc.). When we do the build process (using Node), it will compile the individual coffee files into a single minified js.

Classes have been broken into individual files with commit 0c6598dfa361d77afec6825cc3d88c6adc97bf84

Minification has been added with commit dc19cb2256db1ee901ac1306371948f46cd37b10


CA OSANG LLC API Onboarding

ReportStream API – format CSV
Q: What is your expected message volume?
A: 10,000 daily
Q: Are you currently reporting to any other states outside of your state?
A: Not yet
Q: What is your current process for reporting COVID-19 data?
A:  Our current system is designed to support manual self-reporting to STLT in an arbitrary manner, but we plan to change the system to enable  automatic reporting using the authorized LIVD mapping code.
Q: What state do you report to?
A: CA
TO DO

[ ] create individual tickets to for this epic (BX can work on doing this)

Stacy 8/18 12:50pm
We want to request adding a new device OHC COVID-19 Antigen Self Test.
Line 316 on LIVD-SARS-CoV-2-2022-04-27

OSANG LLC kickoff meeting scheduled for 8/24/2022 @ 1:30pm ET w/ @sarahnw @BerniXiongA6 @jbiskie

@sarahnw is this on your radar?

@BerniXiongA6 no I'm not really sure what we do here? the description may be misleading. I'm going to update with the meeting info from the Help Desk.

@sarahnw @BerniXiongA6 Hello, is this Genabio? I think this may be a duplicate ticket.

Hi @sliu1000 this should not be the same as Genabio -- we met with Genabio last week for kickoff. The kickoff for Osang LLC is scheduled for this Wednesday with Stacy Kim at Osang LLC. cc: @sarahnw

Osang asking for an update. I advised them that it looks like we are still waiting to recieve a test file. @BerniXiongA6

Will forward previous emails to @MauriceReeves-usds as we wait for Osang to send over test files. @sarahnw told them it may take up to 2 weeks to validate due to our current backlog.

Updates 9/19/2022: Stacy from Osang followed up today on status. Will let her know @MauriceReeves-usds  is working on it. cc: @sliu1000

From StoneLabs inc in cooperation with Osang:
Dear Maurice,
This is Eric Song from StoneLab Inc. in cooperation with OSANG LLC for the development of myHomeTest mobile app using ReportStream.
I apologize for the late reply to your request.
Below I attach the sample output data from myHomeTest in CSV format.
Consequently, we would like to request your review and the technical guideline for the next steps,
e.g. API share secret key/token, directed URL.
We will be attentive to your instructions in order to meet the FDA's requirements for successful test result reporting on the app to ReportStream.

I would like to involve two more engineers of StoneLab Team in assisting or cooperating with you: Farid Talibli (Senior SW Engineer), Alexander Sharipov (Junior SW Engineer)

Thank you very much for your help in advance.
Best regards,
Eric

Hi Eric,
Thank you for the clarification.  We'll provide you with an update once our Engineer finishes reviewing your sample CSV Test file.
Best regards,
Sharon
The ReportStream Support Team
Contact us at<EMAIL_ADDRESS>Support hours:  8:00 am through 9:00 pm Eastern time
Monday-Friday, excluding US public holidays
From: StoneLab Inc<EMAIL_ADDRESS>Sent: Tuesday, September 27, 2022 8:41 PM
To: Report Stream (CDC<EMAIL_ADDRESS>Dear Sharon,
Thank you for your inquiry as well.
I would like to clarify that Osang and StoneLab are independent companies and StoneLab has assisted Osang for software development and technical support.
All the operation, including reporting, shall be performed by Osang as the virtual CLIA after the launch of the app.
Thank you.
Best regards,
Eric

Eric (Mingoo) Song

Sender Requesting an API Key:
I wonder if we could have any updates on the API key.
Otherwise, scheduling would be greatly appreciated as the FDA has been urging us to enable self-reporting from our app, myHomeTest, via ReportStream at earliest.
In more detail, this is in accordance with our description on the app that self-reporting is expected to go through ReportStream in the software development plan.
Thank you for your cooperation!

Update from Sender:
Needs to submit their data no later than November 5, 2022.  They missed their last deadline and was given an extension.
Communication:
Thanks for your prompt response.
And absolutely we have not enough time for our software (SaMD = mobile medical application) validation until due date given by FDA.
Our original due date was overed already. So, FDA gave one more chance about submission due date until 5th November.
For this due date, we should perform the validation in next week using your API key and our system definitely. We have no way further more.
So, please support us to give the API Key to StoneLab & OSANG Healthcate in this week clearly for our final software validation about system stream reporting.
It is very urgent.
I am sorry to push and bother you and thanks for your support in advance.
Best regards,
Philip Choi
OSANG HealthCare

Dear Joel,
Good day. Thanks for your prompt response about API Key.
And I have question about your API Key.
Is this whether Test verion API key or real version rkey? (This is our partner question.)
Please kinldy inform me of that.
Thanks & Best reagards,
Philip Choi


Provide support for Perses dashboards in Mixins.

Is your proposal related to a problem?

Perses is an open-source project aimed at simplifying the creation and management of dashboards for observability and monitoring. It offers a more flexible and modern alternative to existing solutions like Grafana.
Recently, Perses was accepted into the CNCF Sandbox, marking a significant milestone for the project. Given this momentum, we believe now is the perfect time to start incorporating support for Perses dashboards into the existing monitoring Mixins.
Currently, Perses dashboards can be created using the Perses GoLang SDK, as we do not support Jsonnet at the moment.
I’d love to hear your thoughts on this approach.
Describe the solution you'd like

(Describe your proposed solution here.)
N/A

N/A
Additional context

N/A

Is Perses not compatible with Grafana dashboard JSON definitions?

Perses provides a different JSON definition for the dashboard and provides a migration system to convert the Grafana dashboard to the Perses one.
But I would say on a long term, it's better to provide the Perses definition directly. Like @nicolastakashi mentioned, you can code your dashboard with the Go SDK that Perses is providing

and FYI, Perses doesn't provide any support for Jsonnet


Add docs about concepts

What is the purpose of the change
Add docs about concepts
Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@478a276). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@          Coverage Diff           @@
##             dev     #374   +/-   ##
======================================
  Coverage       ?   67.04%
======================================
  Files          ?      172
  Lines          ?     9829
  Branches       ?     1286
======================================
  Hits           ?     6590
  Misses         ?     2904
  Partials       ?      335

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

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


Make file watching events distinguishable

From @andriysavin on Monday, September 19, 2016 2:11:49 AM
While IFileProvider was apparently designed for ASP.NET stack needs and fits them, it's a separate set of packages which looks to be usable outside of ASP.NET. However, besides other issues, its IFileProvider.Watch functionality, being a convenient abstraction over FileSystemWatcher, is very limited if you try to use it instead of the latter. The action called via IChangeToken seems to be rather useless since it gives no context at all about what has changed. Maybe, its enough to just rescan whole directory content for MVC needs, but definitely not for every other use case. This essentially prohibits using these nice packages.
My thoughts are that these packages should be either named in such way that its obvious they're ASP.NET-bound to avoid confusion, or this functionality should be enhanced to support wider range of scenarios.
More thoughts: IChangeToken was designed, as it seems to me, to notify about some single event about single entity. When dealing with file system notifications we obviously need to handle many events about many entities most of the time, so maybe this interface doesn't fit good as a notification mechanism for this area.
Copied from original issue: aspnet/FileSystem#234

From @muratg on Friday, September 23, 2016 2:16:56 PM
This is an interesting idea. However this would be a breaking change in 1.*.

From @dazinator on Friday, March 3, 2017 6:42:38 AM
Just saw this, think it ties with #241 and #253


[ffmpeg] update to upstream version 4.4

What does your PR fix?

Updates to latest upstream version of ffmpeg.
Updates manifest to use the new json format.
Removed avresample as default feature (it has been a deprecated component for a very long time, is not built by default by the upstream configure file, and has been removed in the upstream ffmpeg master branch).
The libwavpack support was removed upstream in this version (there's a native codec so no loss in functionality), whence I've removed the related feature and patches correspondingly.

Which triplets are supported/not supported? Have you updated the CI baseline?
No changes.

Does your PR follow the maintainer guide?
Yes, to the best of my knowledge.

Yes.

Thanks for merging!


chore(ci): make wait_for_browser_provider time out after 2 minutes

Before, if something went wrong, wait_for_browser_provider.sh would
wait indefinitely, and logs would never get printed. Now, we'll bail
early, and get some actual logs on what the problem was.

LGTM - merging

and cherry-picked into 1.3.x


Fix youtube player x-overflow

Closes #408
https://files.ekzyis.com/public/sn/youtube-player-x-overflow.mp4

I don't remember closing this lol


Firebase Key

Hi,
I deployed the front in Firebase but appear the follow issue

I supouse the Firebase Configuration its in file envirment, but in tutorial don´t appear how i can get this data.

Can you help me?

Enter the firebase console: https://console.firebase.google.com/u/0/project//overview
Click in the apps icon:

Click the configuration icon of your app:

Scroll down until you see your app and then you will see the informations needed;
With this information in hand, go to frontend/src/environments/environments.ts file and input it there.


Is this still alive?

Hi,
I stumbled upon Repsond7 and really like the concept. But it seems like the founder moved on with his saas cms Fixture. Is respond still a way to go or won´t it be maintained in near future?
Best,
Mario

Hi Mario -
Yes, Respond is still being maintained.  The two products have a different focus.
Respond (https://respondcms.com) is focused on developers and enthusiasts that want a platform that they can build on and remix.  It has a focused feature set and I view it as mostly complete.  The technology stack is LAMP, so it requires ongoing maintenance.  My development time on Respond is focused on bug fixes, dependency upgrades, and issues raised in Github.
Fixture (https://fixture.app) is aimed at developers and entrepreneurs that are serious about building and reselling websites.  It is built in the AWS cloud.  So, it is easy to secure, maintain, and scale a fleet of websites.  It also has a much deeper feature set aimed at consumers.  It has deep e-commerce integration and a visual style that makes it easier for non-technical users to consume.
Regardless of your direction, both are being maintained going forward.  I hope this helps.
Thanks, Matt


ListOfResponseMessages is not remembered after bot restart.

KeywordsDictionary contains references to keyword values in ListOfResponseMessages when a ReponseMessage is added to the the list (when serialized to JSON)


Recommend Menloco as a good replacement for Monaco font

I couldn't help noticing this in .bash_prompt:
# iTerm → Profiles → Text → use 13pt Monaco with 1.1 vertical spacing.

A while ago I patched the Monaco font to use Menlo's box-drawing glyphs, which vastly improves the appearance of grids and tables in the terminal:

Since it's a commercially-licensed typeface, I couldn't upload the modified version without infringing on copyright. So I wrote a FontForge script that actually automates the modifications I made to Monaco... just to have prettier-looking borders. =)
https://github.com/Alhadis/Menloco
I don't know how or where you'd go about mentioning it (or if it's even worth mentioning at all), but I feel like bringing it up - since it's something I know many macOS users would enjoy, haha.

Woah, nice work @Alhadis!
Nowadays I use Source Code Pro. I should probably update the comment accordingly.

Haha, bedankt! :D
I use two fonts, myself. Menloco for terminal, and Menlig for Atom (which is basically Menlo with Hasklig-style ligatures and improved APL symbols). I've yet to write a FontForge script so I can share my work... it's such a pity my preferred coding-fonts are both commercially-licensed typefaces. 😢


Budget lines for ToR preparation

We need to finalise the proposed budget lines. There was some discussion on whether we should remain high level (so it is more relatable) or low level (so it is more informative). @fretchen Ronald doesn't have a GitHub account, right?

Items
Unit
Cost

Exploration/Analysis and Discovery Phase

Staff

Business analyst

Project manager

Lead developer / software architect

UI/UX Designer

Initial Implementation and Roll-out

Staff

Business Analyst / PO

Project Manager

Development Team incl. Lead Architect and UI/UX

Trainer and/or change manager

Subject matter expert (if not combined in one of the other roles or available at the client)

Infrastructure

Server/hosting

Possible additional hardware or network infrastructure needed (e.g. handheld devices, routers, wifi extensions)

Possible additional software needed

Maintenance Phase

Staff for

Administrator for bug fixing and maintenance

Trainer for retraining users

Possible future adaptations

Infrastructure

Server/hosting

Looks pretty exhaustive at first, but that is the idea behind it:

The budget structure tries to be somewhat exhaustive, just to help project management to think about possible cost elements from the start. In my opinion, anything that does not make sense in a specific project setup can easily be deleted.
For the staff costs/personnel costs budget lines in the build and run budget template, I have again detailed the possible roles to support whoever has to come up with budget planning/estimates.
So the idea is to be a bit more detailed, with the understanding that anything that is not needed in a specific context can be deleted or aggregated to a more general budget line.

Does this make sense?


Prisma support for Deno

Feature requests
Deno was released a few days ago, is there any plan to support it?
https://deno.land/v1

Duplicates of https://github.com/prisma/prisma/issues/2452

Hi,
Thanks for reporting this! It has already been reported before, so I am going to close this as a duplicate of #2452
Thanks @Sytten 🎉


Cannot render svg correctly

Update: I dig into it a little bit and found that the GraphicsData parsed by SVGScene will contain several points which is NaN, which is likely the reason that makes the filling wrong

Target:

Rendered:

The background color and the rotation angle can be safely ignored, the main issue lands on the incorrectness of filling the red color

Source SVG:
clampy.svg.zip

I also encountered the same problem, which is correct in the image rendering, but app.stage.children[0].children[0].root.children[0].children[0].children[0].children[0].geometry.points  is wrong.
From 882 to 889 are all NaN, which will affect my calculations.
point.svg.zip


MariaDB: VARCHAR not compatible with TEXT?

I'm using MariaDB, which I'm hoping is sufficiently equivalent to MySQL for the purposes of sqlx.
I'm working with a table that looks something like this:
CREATE TABLE userevent(uid int(11), data mediumtext, type int(11))
The data field can be a JSON encoded string, which is the case I'm currently working with. I'm representing the row as:
#[derive(Deserialize)]
struct SleepData { stages: Vec<[u64; 3]> }

#[derive(sqlx::FromRow)]
struct SleepRow { uid: i64, data: SleepData }

I've implemented Decode for SleepData by using serde to deserialize the string, and I've implemented Type for SleepData as:
fn type_info() -> <MySql as Database>::TypeInfo {
    <str as Type<MySql>>::type_info()
}

When I execute the query: SELECT uid, data FROM userevent WHERE type=3, I get an error:

Error: error occurred while decoding column "data": mismatched types; Rust type scrub_rs::db::sleep::SleepData (as SQL type VARCHAR) is not compatible with SQL type TEXT

My understanding is sqlx should understand that str is compatible with all the various text column types MySQL defines, what am I doing wrong?

Type has an optional Type::compatible that determines whether two types are compatible. For VARCHAR and TEXT this works:
impl sqlx::Type<MySql> for CustomType {
    fn type_info() -> MySqlTypeInfo {
        String::type_info()
    }

    fn compatible(ty: &MySqlTypeInfo) -> bool {
        String::compatible(ty)
    }
}

Related: https://github.com/launchbadge/sqlx/issues/1230


Switch to sigs.k8s.io/cluster-api

This repo was previously using github.com/openshift/cluster-api.  We
should be using the upstream version of cluster-api, and not the
OpenShift fork.
OpenShift has a fork of this repository where it can maintain changes
necessary to switch back to their copy of cluster-api.
Fixes #25.

@mhrivnak dep made a lot more changes to Gopkg.lock than I expected.   Can you look over that for me?  Maybe it's the version of dep I'm using compared to what generated it last?

@mhrivnak dep made a lot more changes to Gopkg.lock than I expected. Can you look over that for me? Maybe it's the version of dep I'm using compared to what generated it last?

Did you run dep ensure -update by chance without specifying a particular dependency?

Yes, I did.  I wanted to make sure it pruned the stuff that was no longer needed, so I just ran "dep ensure".

Ok, I'm guessing you have an older version of dep, perhaps prior to 0.5.0. When I check out your branch, grab the old Gopkg.lock, then run dep ensure. it keeps all the "pruneopts" and digest values that your branch removes. It's probably a good idea to update your dep install and run it again.

Ah ha, good catch.  I thought I had a new dep, but I also had an old system packaged version, and that's what got used.

@mhrivnak fixed.  looks better now!


inflectKeys behaviour on camelCase attributes

Hi, the README states

inflectKeys: camelize the field names per record. Default: true.

However, we've found that if the recordType attribute is already camelCase (e.g. phoneNumber ), it's transformed to phone-number via e.g. https://github.com/fortunejs/fortune-json-api/blob/2.1.2/lib/helpers.js#L213 ) so have set inflectKeys:false to preserve them , which makes the README seem misleading.
What's the intended behaviour for camelCase'd attributes?

Oops, it seems the README is misleading.

Fields on a record type should follow JS convention of camelCase in JS code, nothing unusual here.
Over the wire, it should use dasherized-attributes per the JSON API recommendation.

Member names SHOULD contain only the characters “a-z” (U+0061 to U+007A), “0-9” (U+0030 to U+0039), and the hyphen minus (U+002D HYPHEN-MINUS, “-“) as separator between multiple words.

I don't make those recommendations, and would have liked it if they made it less confusing.
I'd appreciate a PR to fix the README!


[Bug] Skip feature not working with Microsoft online voices

As the title says, skip feature doesn't work with Microsoft online voices
Tested with version 0.2.3

Thanks for investigating,

As for now, the SAPI5 skipping feature isn't supported by this engine (for any voice, not just online ones), and is listed here as an unsupported feature.
Unlike some features that are impossible to implement, this one is doable. If there are proper sentence boundary events, I can skip sentences based on their timestamps.
Do you think it's necessary to implement this? How many TTS clients (other than the test app) utilize this feature?

Do you think it's necessary to implement this? How many TTS clients (other than the test app) utilize this feature?

It will be great to support this. I found this issue while using PDF-XChange Editor(you can use it for free) btw


[FEATURE REQUEST] allow user to create wiki pages

Hello,
I've fixed issue https://github.com/kristapsdz/acme-client-portable/issues/21 and finally acme client works like a charm here on my Ubuntu Server with nginx:
https://brookframework.org
So it would be nice to publish at the acme-client-portable page the full steps to use it with nginx and Ubuntu.
I did some changes in the files config.h and http.c, but I need to recreate the steps from scratch to get the changes I've done and finally open a pull-request sending a patch.

Please let me know what these are so I can bundle them into the system itself instead of having it bit-rot in a wiki!


Unable to load attached Storage Account. Error: Cannot read property 'version' of undefined

Storage Explorer Version:
Build Number:
Platform/OS:
Architecture:
Regression From:
Bug Description

Steps to Reproduce

Expected Experience

Actual Experience

Additional Context

TRY WITH YOUR ACCOUNT FROM WHICH RESOURCE WAS CREATED


Please show the bicep for the Deployment and Service module!

Being able to import yaml files and convert them automatically to bicep is interesting feature but honestly, I don't care and probably will never use that. I'd much rather see the actual bicep file version and just make a note that you can also convert yaml into bicep below it.
To be honest, if I want yaml files I'll just keep using helm, and I'm super skeptical that you'll be able to convert my helmified-yaml files at all.
 It sucks so bad its to the point that the whole appeal of this experimental feature is so that I could use the bicep language to do the templating and logic instead of the horrid text templating language this is helm.
So with that in mind, the one thing I came here to see is missing from the docs! I want to see what it would look like to make a deployment and service in Bicep instead of yaml / helm. In fact this entire tutorial, as useful as a lot of these details are, starts out with a bunch of really complex details when all I want to see up front is how it will look to build a full chart in bicep.
Please front load that example right on the main page, this is how I'd organize the main page:

Overview of extensions and this extension
Simple elegant example of a Module which creates a Deployment and Service with some params
How to enable experimental mode...
Links to all the gory details.

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

ID: af166e8d-7290-eb55-7c0d-0e696bb4d842
Version Independent ID: 55284287-b1c5-c313-ba9c-1b2638fbec97
Content: Quickstart - Deploy Azure applications to Azure Kubernetes Service clusters using Bicep extensibility Kubernetes provider - Azure Kubernetes Service
Content Source: articles/aks/learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider.md
Service: azure-kubernetes-service
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

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

@justinmchase
I'm going to assign this to the document author so they can take a look at it accordingly.
@MGoedtel
please review it.

#reassign: schaffererin

Hi, @justinmchase. Thank you for your feedback and for your patience. For information on how to proceed through this process in Bicep, see Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using Bicep. To learn more about Bicep, I suggest visiting the Bicep documentation. Since this feedback isn't directly related to an issue with the article in question, I am going to close this GitHub issue. Thanks again! #please-close

Well actually it was related to that article, I think you misunderstood. The request is to show how to create Kubernetes resources (such as a Deployment) in Bicep, not how to create AKS itself!
The link you added is not related to the request.
In this link, in the original document:
https://learn.microsoft.com/en-us/azure/aks/learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider?tabs=azure-cli#add-the-application-definition
On step 1 it shows how to create kubernetes in resources in yaml, then how to convert them into Bicep... and my request is to just show the bicep. Skip the whole yaml thing, its not needed and the whole point of this document, in my opinion, is to see the kuberentes bicep example which is missing from the docs!
I think its still relevant and you incorrectly closed the task but /shrug


⚠ Secret Website 3 has degraded performance

In 6732110, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 21026 ms

Resolved: Secret Website 3 performance has improved in e199b8a after 1 hour, 6 minutes.


Added currency details

Description
Added world-wide currency details with symbols, names, abbreviations etc.
Issue Ticket Number
Fixes #155

Checklist:

[x] I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING.md
[x] I have cross-checked that the dataset I'm uploading is not present in the project
[x] I have cross-checked that the dataset is present in the correct folder

Good one @soustab10
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow these steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to the profile section from the top right-hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard!
And don’t forget to share your achievement with your friends.

@nikhil25803
Soustab Haldar


Info.plist Error

Info.plist: Merging CFBundleURLTypes: Property CFBundleTypeRole is required!

I manage to fixed this


feat: add warning for asyncModule

related to #11874
Downgrade the async/await is too hard, there must have a async function that capture the user's top-level-await, so I don't think there is a way to downgrade the code, which can capture the await and not using async function.
So this PR only add a warning for it.

What kind of change does this PR introduce?

Add output.environment.asyncFunction
Add warning for asyncModule (topLevelAwait, asyncWebAssembly) when the target environment doesn't support async/await

Did you add tests for your changes?
Add configCases/async-module/environment-not-support-async-warning

Does this PR introduce a breaking change?
No

What needs to be documented once your changes are merged?
Add output.environment.asyncFunction

Thank you

Downgrade the async/await is too hard, there must have a async function that capture the user's top-level-await, so I don't think there is a way to downgrade the code, which can capture the await and not using async function.

The async function can be transpiled to a generator: https://www.npmjs.com/package/transform-async-modules-webpack-plugin
@alexander-akait is there an easy way I can suppress this warning from inside my plugin?  I was looking to just apply an instance of IgnoreWarningsPlugin, but it looks like that may not be eexposed on the compiler instance somewhere (or maybe the types aren't)?

The async function can be transpiled to a generator: https://www.npmjs.com/package/transform-async-modules-webpack-plugin

Yes, it's easy to transpile it in renderModuleContent hook using babel, but without babel, I've consider to manually transpile it with Dependency and add a async_to_generator runtime to downgrade to es6, it's easy in some cases, but what really make it hard is for await, and downgrade to es5 is even harder.

@alexander-akait is there an easy way I can suppress this warning from inside my plugin?

apply(compiler) {
  (compiler.options.ignoreWarnings ??= []).push((warning) => warning.name === 'EnvironmentNotSupportAsyncWarning')
  // ...
}

this should work, but maybe apply IgnoreWarningsPlugin is a better way, I'm not sure should we expose it on the compiler? @alexander-akait

Another solution - new IgnoreWarningsPlugin(...options).apply(compiler); and pass options to ignore this error

Another solution - new IgnoreWarningsPlugin(...options).apply(compiler); and pass options to ignore this error

That's what I tried first, but that plugin is not exposed in the API.  The snippet from @ahabhgk does work though.  I had thought it was too late to manipulate options.
PS - Using ignoreWarnings makes it awkward or impossible to use stats.hasWarnings() because it still returns true even if they are all ignored.  Not sure if that's a bug or intentional.realize it wasn't too


"Empty archive" error when install formulas with tar.xz archives, after upgrading to Xcode 8

I have just upgraded to Xcode 8 and run xcode-select --install after the upgrading. I tried to reinstall all formulas I had. And I encountered errors as the following, for example, when installing git,
$ brew install git --verbose
==> Using the sandbox
/usr/bin/sandbox-exec -f /tmp/homebrew20160915-13630-1k3cym9.sb nice /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby -W0 -I /usr/local/Library/Homebrew -- /usr/local/Library/Homebrew/build.rb /usr/local/Library/Taps/homebrew/homebrew-core/Formula/git.rb --verbose
==> Downloading https://www.kernel.org/pub/software/scm/git/git-2.10.0.tar.xz
Already downloaded: /Users/Zhou/Library/Caches/Homebrew/git-2.10.0.tar.xz
==> Verifying git-2.10.0.tar.xz checksum
Error: Empty archive

This error only happens with formulas using a source packed as tar.xz instead of gz or bz2. I tried to manually uncompress the package via tar xf and it works fine.

Try to brew uninstall --force xz.

I already tried that before submiting this issue. xz just got reinstalled back as a dependencies for those formulas and the same issue persists.

Can you install the CLT, then brew reinstall xz, and try again? This is a problem caused by having Xcode 8 on 10.11 without the CLT, which we'll be adding a warning for (#965).

Both were done. The first thing I did was to install CLT even before I try to do anything with brew.

On Sep 15, 2016, at 17:37, Misty De Meo<EMAIL_ADDRESS>wrote:
Can you install the CLT, then brew reinstall xz, and try again? This is a problem caused by having Xcode 8 on 10.11 without the CLT, which we'll be adding a warning for (#965).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

What happens if you run xz on the commandline?

Or just brew test xz.

brew test xz fail with the following
$ brew test xz
Testing xz
==> Using the sandbox
==> /usr/local/Cellar/xz/5.2.2/bin/xz /tmp/xz-test-20160915-23199-1gis089/data.txt
Last 15 lines from /Users/Zhou/Library/Logs/Homebrew/xz/test.01.xz:
2016-09-15 17:47:00 +0800

/usr/local/Cellar/xz/5.2.2/bin/xz
/tmp/xz-test-20160915-23199-1gis089/data.txt

dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /usr/local/Cellar/xz/5.2.2/bin/xz
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /usr/local/Cellar/xz/5.2.2/bin/xz
  Expected in: /usr/lib/libSystem.B.dylib

Error: xz: failed
Failed executing: /usr/local/Cellar/xz/5.2.2/bin/xz /tmp/xz-test-20160915-23199-1gis089/data.txt
/usr/local/Library/Homebrew/formula.rb:1608:in `block in system'
/usr/local/Library/Homebrew/formula.rb:1545:in `open'
/usr/local/Library/Homebrew/formula.rb:1545:in `system'
/usr/local/Library/Taps/homebrew/homebrew-core/Formula/xz.rb:35:in `block in <class:Xz>'
/usr/local/Library/Homebrew/formula.rb:1446:in `block (2 levels) in run_test'
/usr/local/Library/Homebrew/formula.rb:775:in `with_logging'
/usr/local/Library/Homebrew/formula.rb:1445:in `block in run_test'
/usr/local/Library/Homebrew/extend/fileutils.rb:14:in `block in mktemp'
/usr/local/Library/Homebrew/extend/fileutils.rb:74:in `block in run'
/usr/local/Library/Homebrew/extend/fileutils.rb:74:in `chdir'
/usr/local/Library/Homebrew/extend/fileutils.rb:74:in `run'
/usr/local/Library/Homebrew/extend/fileutils.rb:13:in `mktemp'
/usr/local/Library/Homebrew/formula.rb:1439:in `run_test'
/usr/local/Library/Homebrew/test.rb:28:in `block in <main>'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
/usr/local/Library/Homebrew/test.rb:27:in `<main>'

However, uncompress seems to work just fine. For example cd ~/Library/Cache/Homebrew; tar xf whatever.tar.xz works just fine.

Your /usr/bin/tar has nothing to do with xz.
Typical Xcode 8 on El Cap debacle.
Please pour our bottle in the meantime rather than compile from source.

OK, I guess I have just to wait a few more days for the new OS. It sounds like Xcode 8 on Sierra is better and it is only a problem of Xcode 8 on Ei Cap

Here's some background reading: https://github.com/Homebrew/homebrew-core/issues/4809#issuecomment-247021138.
And https://github.com/Homebrew/brew/pull/970 will hopefully fix the problem.

I guess I have just to wait a few more days for the new OS.

By the way, be advised that if you need anything on this list you'd better hold out a little longer.

Anyone impacted should brew reinstall xz. This should be fixed by ILZ's sterling work in https://github.com/Homebrew/brew/pull/970, but you'll need to reinstall the broken xz.

Closing due to inactivity.


Give very entry/record in the catalog an identifier

that way you can track the information in the catalog over time more easily

I want a more stable data model first, otherwise I will have to re-assign identifiers anyway if I end up splitting keys from bibliographical information.


Can I use SharedAccessKey to connect to the broker (EventHubs)?

I'm unable to connect to my Azure EventHubs.
We use SharedAccessKey instead of SSL to get connected and I have this configuration to do it.
"EventBusConfig": {
"BootstrapServers": "useddissvcaeh01.servicebus.windows.net:9093",
"SecurityProtocol": "SaslSsl",
"SaslMechanism": "Plain",
"SaslUsername": "$ConnectionString",
"SaslPassword": "Endpoint=sb://anyname.servicebus.windows.net/;SharedAccessKeyName=anyname.;SharedAccessKey=CtDbJ/Kfjs7498s--anypassword--SkSk749/z2Z5Fr9///33/qQ+R6Cyg=",
"SocketTimeoutMs": "60000",
"SessionTimeoutMs": "30000",
"GroupId": "NameOfTheGroup",
"AutoOffsetReset": "Earliest",
"BrokerVersionFallback": "1.0.0",
"Debug": "cgrp"
}
But it seems I need the certification path (the pem file)

I want to produce a simple message like this

Thank you.

Hi everyone.
I was able to consume a topic like this

For this reason, Is there a way to set the property "EventHubConnectionString" in the Producer?

@rodrilink can i asked why you closed this? i was just about to start triaging it 😉

Hi @ryancrawcour :)
Well, I was having trouble when I started implementing this extension and realize that I need to download a CA certification to make the producer works.
To sum it up, I was able to produce and consume messages through this extension :)
I will take advance of this reply and ask you something, Is there any way that I can sort out the authentication as the consumer does just to setted the property EventHubConnectionString and use the SharedAccessToken?
Because the idea of having an unknown certificate is not an option in production and I don't think I can produce one.
Thank you.


game crash on start after crafting hammer

Modpack Enigmatica 2 Expert v1.20
java.lang.NoSuchMethodError: exnihilocreatio.registries.registries.HammerRegistry.registered(Lnet/minecraft/block/Block;)Z
https://pastebin.com/5xfvjM8F

Try updating your creation, I think I already released a hotfix for that...
Kenshij<EMAIL_ADDRESS>schrieb am Sa., 28. Apr. 2018, 12:50:

Modpack Enigmatica 2 Expert v1.20
java.lang.NoSuchMethodError:
exnihilocreatio.registries.registries.HammerRegistry.registered(Lnet/minecraft/block/Block;)Z
https://pastebin.com/5xfvjM8F
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/BloodWorkXGaming/ExNihiloCreatio/issues/82, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHwpZjW6KuSknWFNEjl-lLFL4y6_Skg0ks5ttElkgaJpZM4TrXCK
.

*creatio
BloodWorkXGaming<EMAIL_ADDRESS>schrieb am Sa., 28. Apr.
2018, 21:12:

Try updating your creation, I think I already released a hotfix for
that...
Kenshij<EMAIL_ADDRESS>schrieb am Sa., 28. Apr. 2018, 12:50:

Modpack Enigmatica 2 Expert v1.20
java.lang.NoSuchMethodError:
exnihilocreatio.registries.registries.HammerRegistry.registered(Lnet/minecraft/block/Block;)Z
https://pastebin.com/5xfvjM8F
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/BloodWorkXGaming/ExNihiloCreatio/issues/82, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHwpZjW6KuSknWFNEjl-lLFL4y6_Skg0ks5ttElkgaJpZM4TrXCK
.

ah ok thanks ^^ will handy update the mod

modepack uses latest version exnihilocreatio-1.12-0.2.1.jar
have delted the hammer from inventory trough ntbeditor, to continue playing
crash appears when you have the hammer in active slot and something (think it is waila harvestability) checks if you can break the block with the tool, have looked at a the tinker workbench, so yes your mod couse in the end the crash but don't know if not waila should fix this

ah, shit sorry, then I fixed it and forgot to release it to curse...
You can use a version from here till I upload it
https://ci.blamejared.com/job/ExNihiloCreatio/job/1.12/
Kenshij<EMAIL_ADDRESS>schrieb am Sa., 28. Apr. 2018, 23:57:

Reopened #82
https://github.com/BloodWorkXGaming/ExNihiloCreatio/issues/82.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/BloodWorkXGaming/ExNihiloCreatio/issues/82#event-1600296812,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHwpZh9h0wFFvp__dLoF5BFphGEZO5E3ks5ttOXDgaJpZM4TrXCK
.

That version does indeed fix it, thank you!


[stable/sonarqube]: Do not set targetPort for ClusterIP service

I am trying to deploy sonarqube with a Service of the kind "ClusterIP". With that type of service specifying a targetPort seems to be invalid. This change leaves out the targetPort if the type is set to ClusterIP and lets me deploy sonarqube as a service internal to a cluster.
The k8s docs say this field is ignored for services with clusterIP=None, and should be omitted or set equal to the 'port' field. At least on k8s 1.7 setting it to equal the port field makes helm throw this: "Error: UPGRADE FAILED: Service "prod-sonarqube-sonarqube" is invalid: spec.ports: Required value".
Please let me know if you consider this an error in either helm or k8s and I'll report it where needed. This fix was the fastest way to get sonarqube up and running with only a ClusterIP.

/ok-to-test

cc @rjkernick

LGTM

/test pull-charts-e2e

@unguiculus After rebasing on master everything is green.
I'm assuming that this was a flake. Do you need me to report it in some fashion?

/lgtm


Worker AMI ID is always the latest. Should be possible to pin it to a version

Currently the LC of worker groups will be automatically updated with new AMIs when they are released by AWS: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/data.tf#L24
This is great most of the time but sometimes we don't want this to be done automatically when terraform is run. For example when we want to be double sure the new AMI is stable in a test environment.
I proposed we add a new variable, e.g. ami_version_filter, that defaults to v*. This could be optionally set to a release from amazon-eks-ami, e.g. v20190220, to pin the version.
Any thoughts or objections?

You can achieve this pinning by setting ami_id in var.workers_group_defaults or var.worker_groups[*]
I don't know if the module needs more complexity when there is already a way to achieve the result

Yes but this problem with that is that you need to look up the AMI ID and it's different for every region. It's also impossible to know what version the AMI ID is for at a glance.

I don't know if the module needs more complexity when there is already a way to achieve the result

You could be right here. My assumption is that 95% of people are using the AWS AMI and therefore this change makes sense. But if it's considerably less than that then this change would be needless complexity...

I'd very much would support this feature, we just had some issues last Friday of our cluster breaking due to a new AMI release.

I've pinned mine like so:
  worker_template_defaults = {
    subnets = "${join(",", module.vpc.private_subnets)}"
    ami_id  = "${coalesce(var.ami_id, lookup(local.region_to_ami_id, var.region))}"
  ...

  # Available k8s 1.11 AMIs per region. This is to avoid accidental upgrade.
  # Not all regions support EKS
  # Source: https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-ami.html
  region_to_ami_id = {
    "us-west-2"      = "ami-0c28139856aaf9c3b"
    "us-east-1"      = "ami-0eeeef929db40543c"
    "us-east-2"      = "ami-0484545fe7d3da96f"
    "eu-central-1"   = "ami-032ed5525d4df2de3"
    "eu-north-1"     = "ami-0154b2479ba20f8bb"
    "eu-west-1"      = "ami-098fb7e9b507904e7"
    "eu-west-2"      = "ami-0d69ab00cb41d6eda"
    "eu-west-3"      = "ami-018ebb030cf6ae00b"
    "ap-northeast-1" = "ami-07fdc9272ce5b0ce5"
    "ap-northeast-2" = "ami-091e0e1906e653417"
    "ap-south-1"     = "ami-0b6f791fc54125a8a"
    "ap-southeast-1" = "ami-038d55c26bf01998f"
    "ap-southeast-2" = "ami-0e07b5081bb77d540"
  }

Clunky but works.

Clunky but works.

Exactly. With my idea we can just pin based on the Github release from AWS and not have to worry about AMI ID and region etc.

Having now seen a working example, I change my mind. I like Max's idea.

PR: https://github.com/terraform-aws-modules/terraform-aws-eks/pull/296
Please have a look 🙂

This is great! A complex module is difficult to manage and understand but I think the alternative of forcing consumers to accrue their own complexity as a cost of not doing it here (see @diversario 's solution), is a worse outcome.
Merged in your work @max-rocket-internet . Closing this out. Thanks for the input, @all.

why not just have ami_id? I need EKS-opitmized-ami with GPU support which can't be matched with the filter.

why not just have ami_id?

You can: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/workers.tf#L42

Thanks, I've seen your comment in the other issue.

FWIW we had to do this in 2 places to prevent breaking(?) runs.
Simplified for brevity sake:
local {
  workers_group_defaults = [
    {
      ami_id                                   = "ami-0200e65a38edfb7e1"
    }
  ]

  worker_groups_launch_template = [
    {
      ami_id                                   = "ami-0200e65a38edfb7e1"
    },
  ]
}

module "eks" {
  worker_groups_launch_template        = "${local.worker_groups_launch_template}"
  workers_group_defaults               = "${local.workers_group_defaults}"
}


self.unique - different on GitHub and pipy file

Hi!
I'm no expert on neither UMAP nor Python, but I have been using the UMAP extension on-and-off for the last 3 months. Previously I've had no error using it, but now a value error is appearing where I do not believe it should.
Using the "precomputed" metric, the following value error appears:
ValueError: unique is poorly defined on a precomputed metric
Looking at the code in umap_.py file on GitHub (https://github.com/lmcinnes/umap/blob/master/umap/umap_.py) row 1500 is states:
elif self.metric == "precomputed":
if self.unique:
raise ValueError("unique is poorly defined on a precomputed metric")
but in the pipy file (downloaded using pip install umap-learn, found https://pypi.org/project/umap-learn/) states:
elif self.metric == "precomputed":
if self.unique is False:
raise ValueError("unique is poorly defined on a precomputed metric")
The second statement seems contradictory to me. Since it says that unique is poorly defined for a precomputed metric it should logically be if self.unique like in the first case.
Is this an error?

I also received this error, for what it's worth.

Yes, I really need to roll out a new release. Sorry about that.

@lmcinnes -- no worries! The current version on GitHub works like a charm in this regard.


xarray.dot is now based on da.einsum

Closes #2074
Requires dask >= 0.17.3

It looks like the dot tests are now failing on test_dot because they don't find the right version of dask -- which makes sense because dask hasn't made the 0.17.3 release yet.
Let's wait until that happens (hopefully very soon: https://github.com/dask/dask/issues/3452) before merging this. But we should also add a conditional version check for test_dot with dask. Something like:
        if LooseVersion(dask.__version__) < LooseVersion('0.17.3'):
            pytest.skip("needs dask.array.einsum")

(The appveyor failures should be fixed if you merge in master.)

@shoyer integrated your suggestion

thanks @crusaderky !


New log channel: fatal_email

What's New?

Data migration to fix some malformed sequences.
Change default farmbot name to Farmbot.
Add a new log channel called fatal_email. These emails are different than standard emails because they are not put into a digest- they are sent to the end user immediately and have a more appropriate subject line.

Coverage remained the same at 89.883% when pulling 623f660ee6edb7ac67ba8d71bc006b96a3ee1ec7 on RickCarlino:fatal_email_channel into 5fc02d1031455dbe9c22a8eb83b09711589a29e5 on FarmBot:staging.


chore(cmake): Pull changes

Pull changes from https://github.com/Opentrons/cmake-utils/pull/14

If this was based off of #67, then can you make the base branch can-simulator-vcan? That way we can merge this into Amit's PRs and avoid a hairy rebase.

@Laura-Danielle of course


Setup "failed", but still works.

Something's wrong with the current installer, faulty stating that setup failed due to some exception, yet the program still works fine without any problems.
This is on a fresh Windows 10 Pro x64 version 1709(FCU)
Never had this issue on version 1703(CU)
Setup log:
https://pastebin.com/ZSXL35LQ

did you run it with admin access?

Yes i did, both get the same error.

Odd, it looks like something broke with the squirrels installer. Championify is currently a few versions behind, I can look in to updating it if it won't cause any issues.

Well, the tool works fine, it's just the installer that seems to think the program failed installing when after a second clicking away "Setup Failed" opens just fine, and the uninstaller still works fine too.

What i do not understand is this: "---> (Inner Exception #0) System.IO.IOException: The process cannot access the file 'C:\Users\notcy\AppData\Local\Championify\app-2.1.1\icudtl.dat' because it is being used by another process."
I made sure to delete this file prior to re-installation and it was gone, but after trying to install the program again this exception happens again.
What i think is the problem here is that Championify.exe is initialized too early and causes the file to lock-up before installation is finished.

Seems like Discord also uses Squirrel so i made a fresh log: https://pastebin.com/hkQm9g1A
It seems that literally nothing is out of the ordinary and it should never have popped the Setup Failed log.


Data read error during testing

FileNotFoundError: Caught FileNotFoundError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "E:\SoftWare\anaconda3\envs\lsomer\lib\site-packages\torch\utils\data_utils\worker.py", line 308, in _worker_loop
data = fetcher.fetch(index)
File "E:\SoftWare\anaconda3\envs\lsomer\lib\site-packages\torch\utils\data_utils\fetch.py", line 51, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "E:\SoftWare\anaconda3\envs\lsomer\lib\site-packages\torch\utils\data_utils\fetch.py", line 51, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "D:\Code\Anomaly_Detection\DDAD-main\dataset.py", line 67, in getitem
target = Image.open(
File "E:\SoftWare\anaconda3\envs\lsomer\lib\site-packages\PIL\Image.py", line 3227, in open
fp = builtins.open(filename, "rb")
FileNotFoundError: [Errno 2] No such file or directory: 'datasets/MVTec\bottle\test\broken_large\000_mask.png'
When I test mine, the above error occurs. There is no 000_mask.png under MVTec\bottle\\test\\broken_large\\path.

You can open dataset.py and remove "/"  in line 66 and 77.

You can open dataset.py and remove "/" in line 66 and 77.

Thank you very much, the error has been solved!


Text not centred until field is focus when using  --generate-appearances option

I need to fill out a form where text should be centered within its field. While filling the form isn't a problem, I prefer using the --generate-appearances option with QPDF to prevent Adobe Acrobat from generating its own appearance streams. However, when using --generate-appearances, the text in the field isn't centered (aligned to left) until the field is focused. I suspect this issue is because the 'Quadding' property is being ignored. Is it possible to add support for 'Quadding'? Thank you in advance!

I'll take a look at this next time I have a chunk of time for qpdf (hopefully soon). If your theory is correct, it may not be that difficult. One factor is that qpdf didn't know anything about font metrics, but since I wrote that code several years ago, I did an independent project that used font metric information, and it's code I can freely add to qpdf. No promises, but I'll take a look. Do you have a sample form that exhibits this behavior that you can share so I could see exactly what the form field/annotation information looks like? If you can't share the file, sharing the output of qpdf --json on the file will be most likely adequate.

That would be great, thank you so much for looking into it. I have created a dummy PDF with a single textfield with a field name "Text1".
Original form:
https://github.com/qpdf/qpdf/files/12889772/form_centered_text.pdf
Filled form with need appearance tag
https://github.com/qpdf/qpdf/files/12889757/form_centered_text_output.pdf
Used QPDF to generate appearance streams for the filled form
https://github.com/qpdf/qpdf/files/12889756/form_centered_text_output_NotCentered.pdf

I'm not going to prioritize this for now, but I have put a text label on it in case I reach a point where I'm ready to add more font/text awareness to qpdf.


Helpful-material page scroll up button

The Scroll upp button in helpful-material page is missing the arrow icon. Redesign it or add the arrow

@BennyCarlsson Can I take this?

@pawansingh972 Go ahead :)

resolved Good job :)

Glad to help :)


Update naming.md - fix data model hyperlink

The link led to a 404 github page. Fixed it to the correct location.

@RichiH

This is working as expected already; https://prometheus.io/docs/practices/naming/ links to https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels correctly for me.
What browser are you using? Any special plugins?
I am closing this as it's the same link format we use throughout the website, but feel free to reopen if I got this wrong.

I am using Chrome but checked in Firefox also, same behavior.
Take a look at the link that is about to open at the bottom of the attached screenshoot. I believe this is due to the fact that the used link is relative to the current URL.
Also tried from incognito (not logged in to Github), same behavior.
The link does not direct to https://prometheus.io domain but rather stays in the https://github.com/ domain.


Content in codeblock with data-ca-target-id triggers twig exception

I just started up a little dev blog about tips and whatnot for various platforms. Second article in, i was writing up how to make a wrapper for CS-Cart cm-dialog so that images could use them. Upon saving and visiting front end, an exception was thrown:

An exception has been thrown during the rendering of a template ("DOMDocumentFragment::appendXML(): Entity: line 1: parser error : Specification mandate value for attribute data-ca-targ") in "partials/blog_item.html.twig" at line 53.

The piece of content that triggers it is wrapped in a code block so it shouldnt even be triggering stuff. I tried both tabbing it in and wrapping it with backtick fences:
Click me to open

I am the contents of this dialog

Specifically, its the data-ca-target-id part. Is there something in twig that uses this data asset, or is it just hanging up somewhere or somehow else? Is there a way to escape data style attribs with markup/html?
Appreciate your time into this awesome platform. Thanks

Oh, this error is thrown in a blog list. The normal page itself renders fine. Thanks.

Can you please provide me a full example of the page's .md file so I try to replicate.

Sure man. I tried a test with a few things too trying to nail down what triggers it. In the process discovered that apparently partials/blog.html.twig is rendering the html inside code block in a list item summary. So something like this in a code block:
I should not be green

Would render the span literally "i should not be green" as green text, but inside a code block. That seems like a bug for sure, but i dunno about this one: the char limiter can cut off code blocks partially. I think maybe that is what is causing exceptions. I went through all sorts of variations of the md, tried to narrow it as much as i could to a specific attrib, but it eluded me.  Typing out some instructions for a new example, it happened...exception thrown. Tried some more examples, some would work some wouldnt, then tried just an extra long list of data/class/etc attribs to allow summary to get cut off. Bascially any code block attrib that gets cut off in the char limit will cause it. Here is a sample code block to try as a blog post, then visit the block list page:
<span data-anything="Blue bottle food truck truffaut echo park poutine keytar pop-up try-hard chillwave squid trust fund mumblecore Selvage lumbersexual keytar polaroid schlitz affogato williamsburg kale chips flexitarian hella cronut paleo synth ramps vice Irony kombucha green juice master cleanse chillwave Art party portland meh brunch farm-to-table hoodie.  What do you think? Could it be because blog list is rendering code blocks, or would that exception occur anytime a codeblock is cut off between some quotes? Im thinking maybe its due to rendering somehow, could be wrong though.
Thanks man!

I don't get any issue with that snippet in the text. Is that the whole markdown page content?

Closing to due to inactivity


4.2.0: WebAdaptor not upgraded or not installed

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request

Module Version

4.2.0

Affected Resource(s)

ArcGIS_WebAdaptor

Configuration Files

MapsStbDeploymentAnonymous_11_2.txt
Expected Behavior
Portal and Server WebAdaptor should be upgraded.
Actual Behavior
Portal and Server WebAdaptor remain at 11.1.
Steps to Reproduce
Run the configure file above with the flag " -Mode Upgrade"
Important Factoids
I carrefully read the new webadaptor format change available here and hope I did not miss anything:
https://github.com/Esri/arcgis-powershell-dsc/wiki/ArcGIS-Web-Adaptor-Node-Configuration
In the upgrade process logs, there is no mention of the WebAdaptor as if it had been completely discarded. WebAdaptor resources was never invoked.
Thanks !

My webadaptor configuration must be somehow wrong because even after having manually uninstalled the 11.1 webadaptors and running once again the configuration, 11.2 webadaptors are not installed.
In the log, I have the following:
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Set      ]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Resource ]  [[ArcGIS_Install]ServerInstall]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Test     ]  [[ArcGIS_Install]ServerInstall]
24.11.2023 17:20:14: [PORTAL01]:                            [[ArcGIS_Install]ServerInstall] Installed Version 11.2.49116
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Test     ]  [[ArcGIS_Install]ServerInstall]  in 0.2260 seconds.
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Skip   Set      ]  [[ArcGIS_Install]ServerInstall]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Resource ]  [[ArcGIS_Install]ServerInstall]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Resource ]  [[ArcGIS_InstallPatch]ServerInstallPatch]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Test     ]  [[ArcGIS_InstallPatch]ServerInstallPatch]
24.11.2023 17:20:14: [PORTAL01]:                            [[ArcGIS_InstallPatch]ServerInstallPatch] Installed Version 11.2.49116
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Test     ]  [[ArcGIS_InstallPatch]ServerInstallPatch]  in 0.0490 seconds.
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Skip   Set      ]  [[ArcGIS_InstallPatch]ServerInstallPatch]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Resource ]  [[ArcGIS_InstallPatch]ServerInstallPatch]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Resource ]  [[ArcGIS_Install]PortalInstallmapsportalstb03]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Test     ]  [[ArcGIS_Install]PortalInstallmapsportalstb03]
24.11.2023 17:20:14: [PORTAL01]:                            [[ArcGIS_Install]PortalInstallmapsportalstb03] Installed Version 11.2.49116 11.2.49116
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Test     ]  [[ArcGIS_Install]PortalInstallmapsportalstb03]  in 0.0150 seconds.
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Skip   Set      ]  [[ArcGIS_Install]PortalInstallmapsportalstb03]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Resource ]  [[ArcGIS_Install]PortalInstallmapsportalstb03]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Resource ]  [[ArcGIS_Install]WebStylesInstallmapsportalstb03]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Test     ]  [[ArcGIS_Install]WebStylesInstallmapsportalstb03]
24.11.2023 17:20:14: [PORTAL01]:                            [[ArcGIS_Install]WebStylesInstallmapsportalstb03] Installed Version 11.2.49116
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Test     ]  [[ArcGIS_Install]WebStylesInstallmapsportalstb03]  in 0.0070 seconds.
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Skip   Set      ]  [[ArcGIS_Install]WebStylesInstallmapsportalstb03]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Resource ]  [[ArcGIS_Install]WebStylesInstallmapsportalstb03]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Resource ]  [[ArcGIS_InstallPatch]PortalInstallPatch]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Test     ]  [[ArcGIS_InstallPatch]PortalInstallPatch]
24.11.2023 17:20:14: [PORTAL01]:                            [[ArcGIS_InstallPatch]PortalInstallPatch] Installed Version 11.2.49116 11.2.49116
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Test     ]  [[ArcGIS_InstallPatch]PortalInstallPatch]  in 0.0110 seconds.
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Skip   Set      ]  [[ArcGIS_InstallPatch]PortalInstallPatch]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Resource ]  [[ArcGIS_InstallPatch]PortalInstallPatch]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Resource ]  [[ArcGIS_Install]DataStoreInstall]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Test     ]  [[ArcGIS_Install]DataStoreInstall]
24.11.2023 17:20:14: [PORTAL01]:                            [[ArcGIS_Install]DataStoreInstall] Installed Version 11.2.49116
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Test     ]  [[ArcGIS_Install]DataStoreInstall]  in 0.0530 seconds.
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Skip   Set      ]  [[ArcGIS_Install]DataStoreInstall]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Resource ]  [[ArcGIS_Install]DataStoreInstall]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Resource ]  [[ArcGIS_InstallPatch]DataStoreInstallPatch]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Test     ]  [[ArcGIS_InstallPatch]DataStoreInstallPatch]
24.11.2023 17:20:14: [PORTAL01]:                            [[ArcGIS_InstallPatch]DataStoreInstallPatch] Installed Version 11.2.49116
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Test     ]  [[ArcGIS_InstallPatch]DataStoreInstallPatch]  in 0.0120 seconds.
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Skip   Set      ]  [[ArcGIS_InstallPatch]DataStoreInstallPatch]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Resource ]  [[ArcGIS_InstallPatch]DataStoreInstallPatch]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Resource ]  [[ArcGIS_InstallPatch]WebAdaptorIIS-InstallPatches]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Test     ]  [[ArcGIS_InstallPatch]WebAdaptorIIS-InstallPatches]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Test     ]  [[ArcGIS_InstallPatch]WebAdaptorIIS-InstallPatches]  in 0.0050 seconds.
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ Start  Set      ]  [[ArcGIS_InstallPatch]WebAdaptorIIS-InstallPatches]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Set      ]  [[ArcGIS_InstallPatch]WebAdaptorIIS-InstallPatches]  in 0.0090 seconds.
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Resource ]  [[ArcGIS_InstallPatch]WebAdaptorIIS-InstallPatches]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Set      ]
24.11.2023 17:20:14: [PORTAL01]: LCM:  [ End    Set      ]    in  0.8870 seconds.
24.11.2023 17:20:14: L’opération « Invoquer une méthode CIM » est terminée.

It mentions webadaptor patches (WebAdaptorIIS-InstallPatches) but not WebAdaptorIIS-Install.
Apologize in advance if I missed anything obvious !

OK, my bad. I updated the library without reloading Powershell GUI...
Sorry for the noise


PoC:  PackageNamingInfo - provide capability to rename archives based configuration values

This is to address #101 #193  and maybe help with #143
The goal is to allow all packaging rules to precisely name their output files in a way that is consistent with the naming conventions of the scheme, even if that requires pieces of the file name which can not be known until build time, such as cpu type.
The basic method is:

allow all rules to specify the name of the output archive with package_file_name, rather than using a default
create a PackageNamingInfo provider which specifies a map of values to replacements (e.g. {cpu:x86_64, copt:debug})
if apkg_ rule target  adds a naming_info attribute (which must provide PackageNamingInfo), the provided dictionary will be used for substitutions in package_file_name
pkg_ rules will also return a PackageArtifactInfo provider which will map target label to the file name actually generated. This is required in some situations when associated rules must know the exact name of the final package.

This PR provides a proof of concept of the idea for design discussion.  I intend to leave this open through July for comment, at which point I will make a choice to implement or not based on your feedback.

cc: @davschne @konste @kaorudev

I'd like to clarify the logic behind the new attributes - package_file_name and naming_info.
When neither of the two is specified the name of the rule is still used as the name of the package - this is for backwards compatibility.
Now what if only package_file_name is specified? This means instead of the name of the rule we need to take the string specified by package_file_name as the base for the package name. In many cases it is going to be sufficient and people don't need to mess with the new provider at all.
When both package_file_name and naming_info are specified it means: 1. name of the package should be taken from package_file_name and 2. package_file_name and other string typed attributes of the rule should be interpreted as the templates subject to expansion from the dictionary provided by naming_info.
Important points:

package_file_name can be specified without naming_info.
naming_info should affect not only package name, but also other string attributes. package_dir is especially important.

Do you agree?

On Sun, Jul 12, 2020 at 7:42 PM Konstantin Erman<EMAIL_ADDRESS>wrote:

I'd like to clarify the logic behind the new attributes -
package_file_name and naming_info.
When neither of the two is specified the name of the rule is still used as
the name of the package - this is for backwards compatibility.
Now what if only package_file_name is specified? This means instead of
the name of the rule we need to take the string specified by
package_file_name as the base for the package name. In many cases it is
going to be sufficient and people don't need to mess with the new provider
at all.

Yes. package_file_name should be sufficient for many use cases. You only
need a rule to provide naming_info if you need dynamic naming based on
configuration. This was your use case, and probably more cases as people
build for more execution platforms.

When both package_file_name and naming_info are specified it means: 1.
name of the package should be taken from package_file_name and 2.
package_file_name and other string typed attributes of the rule should be
interpreted as the templates subject to expansion from the dictionary
provided by naming_info.

Yes. That is the idea.

Important points:

package_file_name can be specified without naming_info.
naming_info should affect not only package name, but also other
string attributes. package_dir is especially important.

Do you agree?

It should work wherever it is reasonable. For tar and zip files, it would
only be the file name. For RPM, deb, and yet unsupported formats, we may
need to be able to work that into the expansion of the control files.  The
first implementations may only get a few of those but over time we can make
it uniform.
—

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_pkg/pull/198#issuecomment-657293388,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHHEH4N6LGYFKXTNICE3R3JC7BANCNFSM4OV46B7Q
.

For tar and zip files, it would only be the file name.

Wait, wait, what about package_dir attribute? Without it being dynamically configurable pkg_tar would still be unusable in our case.

cc/ @nacl
My question is if package_dir is the right abstraction.  Should we have the
packaging rules to the package redirection or should pkg_filegroup be the
place where that happens?
On Sun, Jul 12, 2020 at 10:41 PM Konstantin Erman<EMAIL_ADDRESS>wrote:

For tar and zip files, it would only be the file name.
Wait, wait, what about package_dir attribute? Without it being
dynamically configurable pkg_tar would still be unusable in our case.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_pkg/pull/198#issuecomment-657328372,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHHHVCULX2YRLD3BNLS3R3JX5JANCNFSM4OV46B7Q
.

Oh, this is deeper than I was thinking about it. When I discovered package_dir I liked it because it is easy to understand and does exactly what one would expect it to do. I was able to make it do what I need from the first try. When I figured we need it dynamic I dug further and found package_dir_file. It was not an elegant solution, but it worked and unblocked us, so ok.
Now you are talking about matters like package redirection and pkg_filegroup which I simply not aware of.
It would be a pity if in order to make things right we would make them harder to learn and use.
Hope we can keep an easy way for those who need just that and more powerful API for those who need more.

I want the fewest number of constructs that work similarly across all the rules.  If we want to build a binary that goes in /usr/lib/foo, it would be better to say "prefix everything with /usr/lib/foo" in one place (or at least with one syntax) rather than in every use of that place.

Unfortunately I don't quite understand your example. package_dir is about internal folder structure of the archive. I understand that there better be one way to specify that info across all packaging rules, but I am not aware of other possible ways besides package_dir.

cc/ @nacl My question is if package_dir is the right abstraction. Should we have the packaging rules to the package redirection or should pkg_filegroup be the place where that happens?

Sorry for the realllly long delays in responding to this.
In the purest possible sense, pkg_filegroups are intended to define structure, while the packaging rules themselves would be most interested in actually consuming pkg_filegroups and emitting various per-package metadata.
Something like a package_dir attribute is definitely convenient, though: it saves the package authors from potentially writing additional pkg_filegroup rules to define package prefixes.  As pkg_filegroup currently stands, we would need something like it (since it's not nestable), but if we happened to have something like what's mocked in #212, packaging rule attributes like package_dir attribute won't be necessary.
The pkg_filegroup design, therefore, should be given some strong scrutiny to make sure we get all the use cases ironed out.

Yes. I tend to forget the 'Info' when speaking about providers. It feels
redundant (and slightly wrong) unless adding "information" to the
description makes sense.
On Fri, Aug 28, 2020 at 11:58 AM Andrew Psaltis<EMAIL_ADDRESS>wrote:

@nacl commented on this pull request.
In pkg/providers.bzl
https://github.com/bazelbuild/rules_pkg/pull/198#discussion_r479394330:

+PackageNamingInfo = provider(

doc = """Metadata about a package artifact.""",
fields = {

   "values": "Dict of name/value pairs",

},
+)

Not a bad idea, although it wouldn't mesh all that well with the standard
that providers are named Info.
On further thought, would it make sense to use the builtin
TemplateVariableInfo
https://docs.bazel.build/versions/master/skylark/lib/TemplateVariableInfo.html
provider instead?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_pkg/pull/198#discussion_r479394330,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHHBBPDVYZKVSCSJTJFTSC7HZHANCNFSM4OV46B7Q
.

I have something now that I think I want to proceed with.
It demonstrates 3 key new features:

to have the file name created by a pkg_ rule be different from the label name
to allow variable substitution into that file name, where the variables can dynamically come from the build configuration
That downstream rules can, by default, consume the archive produced by a package using the label name even if the actual filename is different.

This PR does not

address the package_dir and package_dir_file attributes.  Those impact the paths created inside the archive. That is a wholly different set of features. That should be handled in pkg_filegroup.
do anything expect pkg_tar.  There is no point doing it everywhere before we nail down design.
try to dynamically use anything except the target cpu.  We can address other platform and toolchain provided values in followup CLs as needed.
deal with variables in rpm .spec file expansion. That should be relatively trivial one the infrastructure here is in place.

Thanks for the review. Back to you now.


Checkout text field text color, looks broken

swap tokens screen

How do I get to this screen? @oa-s And which colours are wrong? What are the correct colours?

How do I get to this screen? @oa-s And which colours are wrong? What are the correct colours?

Enable .isSwapEnabled in Features

tap ETH token
tap …
tap Swap
tap Native Swap
tap gear

If you look again before Vlad replies, you can compare it to the

Expected
Observed

I checked out e50d0b168 (creation of SwapOptionsViewController) and 27cc8e1c1d79710508d736f489c01513aff69d4f (before my changes to TextField) and they both have this. Do you want me to remove the azure highlights?