make find_package(Zephyr...) REQUIRED

... because it is (required).
This makes a difference when building with CMake and forgetting
ZEPHYR_BASE or not registering Zephyr in the CMake package registry.
In this particular case, REQUIRED turns this harmless looking log
statement:
-- Could NOT find Zephyr (missing: Zephyr_DIR)
-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- Check for working C compiler: /usr/bin/cc
-- ...
-- ...
-- ...
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:8 (target_sources):
  Cannot specify sources for target "app" which is not built by
  this project.

... into this louder, clearer, faster and (last but not least) final
error:
CMake Error at CMakeLists.txt:5 (find_package):
  Could not find a package configuration file provided by "Zephyr" with
  any of the following names:

    ZephyrConfig.cmake
    zephyr-config.cmake

  Add the installation prefix of "Zephyr" to CMAKE_PREFIX_PATH or set
  "Zephyr_DIR" to a directory containing one of the above files.  If
  "Zephyr" provides a separate development package or SDK, be sure it
  has been installed.

-- Configuring incomplete, errors occurred!

Note: The CI will fail due to timeout because of amount of projects touched.
@nashif @carlescufi This is safe to merged, even if CI times out.

This is timing out on CI. I am merging this since the changes are extremely well localized (i.e. same line changed over and over) and thus I see no potential for interaction with anything else.

wow, that was a very quick turnaround for a PR changing over 500 files 1 week before a release...

wow, that was a very quick turnaround for a PR changing over 500 files 1 week before a release...

+1. I wonder how those 500 lines were verified for containing "extremely well localized" changes. I may imagine following process: independent party (from the original submitter) wrote a script which performed verification. Then another independent party verified that the script is correct.
But don't listen to me - just merge one of my next patches (of my choosing) in the same way :-D.

For the record I didn't realize it was only 1 week before release when I submitted this. I also didn't care at all whether it would be merged before or after release. Sorry for not paying attention to the release cycle.
I obviously didn't type these changes, they were performed by a one-line script[*] and the result was carefully  reviewed line by line by me and I'm pretty sure by other reviewers. Doing such a throrough review is actually very easy and very quick if you try because it's 500 times the exact same, one-word and obviously very low risk change. The human vision is very good at detecting irregularities. Just try it: open the "Changes" tab and scroll down, you'll see how little time it takes. Even faster with the git show HEAD~x commands that I used.
By now I probably spent almost as much time writing and proof-reading this comment as very carefully reviewing this PR, so I'm going to stop, sorry for any typos left in the comment :-)
[*] I considered adding a new "layer of indirection" to have all find_package options in one place and avoid the duplication but AFAIU find_package is the "bootstrap" command so I don't think it is possible.

just merge one of my next patches (of my choosing) in the same way :-D.

I'm afraid one line of C code can have much wider ranging and subtle or even "undefined" consequences than one extra keyword in a plain CMake command. The number of lines matters but it's not everything.

wow, that was a very quick turnaround for a PR changing over 500 files 1 week before a release...

+1. I wonder how those 500 lines were verified for containing "extremely well localized" changes. I may imagine following process: independent party (from the original submitter) wrote a script which performed verification. Then another independent party verified that the script is correct.

@pfalcon Doing a:
git fetch zephyr pull/25808/head; git checkout FETCH_HEAD; git diff HEAD~3

and then verify this PR doesn't take long.
Especially when knowing what the REQUIRED flag does, and why it is important.


[DEBUG]  Bridge withdraw/Transfer fixes

Summary of changes

Reference issue to close (if applicable)

Closes #789

Code Checklist

[ ] Tested
[ ] Documented

I had to redeploy contracts with this patch. You will need to update the anchor and bridge addresses once new packages are published for solidity contracts v0.5.2.
Use notion doc for deployment details

Closing in favour of #850


Defaults ObservedGeneration to -1 and sets LastHandledReconcileAt

closes #825 #3199
Defaults ObservedGeneration to -1 and sets LastHandledReconcileAt

I generally just use ["Squash and Merge" button]

In terms of keeping a reasonable git history, this is OK for small changes (and I think this PR is borderline). But in general it's not much help for reviewers and other readers of the code, who will often want to look at individual commits to see changes in isolation. It also means you, as the author, are not obliged to "show your working" (because it'll all get squashed together so whatever).
As a frequent reviewer I much prefer it when people use the commit history to explain their change. Have a look at https://github.com/weaveworks/engineering-handbook/blob/main/standards/git.md and https://github.com/weaveworks/engineering-handbook/blob/main/standards/code-review.md#preparing-a-pull-request.


MAPL 2.7.0 and MAPL 2.7.1 non-zero diff with OPS emissions

When MAPL was upticked to 2.7.1 it was found that GEOS went non-zero diff when using the OPS emissions. On investigation I did find very subtle differences (in the order of the 5 or 6th decimal place in the mantissa) in the emissions in ExtData between MAPL 2.7.0 and 2.7.1 when using the OPS emissions. After much work I traced it down to the fact that two different input files used in the OPS emissions the QFED real time emissions and the "HTAP" emission, both on 3600x1800 DE/PE lat-lon grids have ever so slightly different lon/lat values.
In one the lons are
-179.95, -179.85, -179.75 .... 179.75, 179.85, 179.95
In the other the lons are
-179.949996948242, -179.850006103516, -179.75 ....<PHONE_NUMBER>96484, 179.75,<PHONE_NUMBER>03516,<PHONE_NUMBER>48242
likewise for the lats.
Now when both files are opened by the Lat-Lon grid factory, it determines that both are 3600x1800 PE/DE regular grids based on the currently logic, but uses the lons and lats from the file.
Now the upshot is, whichever file gets opened first wins and the 3600x1800 PE/DE grid has the lats/lons from that file.
Well of course the the logic change I made to ExtData in MAPL 2.7.1 causes the order of which file gets opened first with the result that the 3600x1800 PE/DE grid is now slightly different which means the route handle for the regriding is slightly different, which means slightly different emissions and non-zero diff.
So on the one hand there is no reason that this could not in principle happen again, a user changes the RC file, new things are being provided by ExtData.
So what are the options

Do nothing
Modify the equals overload in the factory so it would have caught and made two different grids
If it detects that the grid one of our "standard" grids PC/PE/DC/DE ignore the values in the file and have the factory compute them.

The GEOSgcm gatekeeper was not in favor of 1 because what would prevent this from popping up again potentially and flagging a non-zero diff we have to track down.

I am not in favor of 1) either. But if we do 2) chances are we still will get non-zero diffs because one way or the other, in the past we were using coordinates from a single grid (whichever the first file happen to be). 3) is a good option, and with some luck it might be zero diff against older tags

Either way, this is a non-zero diff once going forward, the question is what can we do to ensure than something like this will not happen again.

Both options: 2 and 3, will guard against similar occurrences. I have mixed feelings choosing between the two. On one hand, 3) is forcing the "right" thing, on the other, the coordinates in the file might have been used to compute some on the data in the file (I am almost sure this is the case for QFED emissions)

I vote for 3, the fact is to be detected as a regular standard PE/PC/DE/DC, you must be awfully close to that in the first place.

I too like 3 the most. Let me double check this with Tom early next week, and if he agrees too, I will modify the grid factory

Highest priority is of course to enable reproducibility under reordering of entries in ExtData.   Both 2 and 3 achieve that, but 2 does it in a rather brute force manner that is probably not the intention.   I doubt we'd have any real problems with memory footprint with (2),  but it just feels wasteful.
What I want is a nuanced combination of 2 and 3.     There should be a default tolerance that decides whether the file grid is close enough to the lat lon factory grid and we would use the latter if the difference is less than the tolerance.      When the difference is more than 0, but less than the tolerance an informative warning message should be emitted indicating that the grid is being adjusted.
The tolerance above should be able to be set globally for all of ExtData.   And then it should be possible for each entry in the resource file to set a separate tolerance for that particular field.


Robots.txt not found

The robots.txt is not found for any website!!!!!!

Same 😐😐

您的邮件我已收到，我将及时查看！谢谢！


InstrumentedList has no attribute 'paginate'

hi, there is a stranger problem.
when i run app, it raise error:
InstrumentedList has no attribute 'paginate':
pagination = user.followers.paginate(.....)
i use type function to check the type of user.followers, it's InstrumentedList instead of BaseQuery class.
i have seached google for several days, but have no idea.
anybody can help me?thanks

i forgot add lazy option in relationship() about followers.


How to test on my own dataset?

Hi,
As I see, both thedemo.pyand test.py use the trimap to output the results:
 trimap = generate_trimap(alpha)---demo.py(it seems trimap generated from ground truth)
 ap.add_argument("-t", "--trimap", help="path to the trimap file")---test.py(load from existed file)
so, how to get the trimap of my own dataset and test on the pretrained model?
thanks~

Semantic-segmentation? E.g. if foreground is person this project may help: https://github.com/foamliu/Look-Into-Person

Hi
foamliu, thanks for your quickly response, but the pretrained model provided by the project https://github.com/foamliu/Look-Into-Person do not match the model.  Someone has mentioned the load error, hope you can help us~ thanks~


Remove varargs from Handler and Pipe creation

I don't think these serve any purpose except and I made a mistake in adding them. Let's get rid of them!

I find the option of having an default value on a Handler useful in setting an initial state for the UI before anything else gets emitted to change that state.
I don't think we need varargs for that, one initial value should be enough (but I don't see any problem with the varargs option either).

Yeah, to clarify I didn't mean get rid of startWith, but  it really should be one or zero arguments and varargs aren't the best way to represent that.

Varargs really make me headache when i start to use scala! ( I am a old haskeller) ,especially the _:* conversion

Fixed with #203


systemd: enable extra configuration to the [Service] section

Motivation for this change
Enable extra configuration to the [Service] section
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Is this not already addressed by serviceConfig?
E.g., the example usage for this option seems covered by
let # for syntax highlighting
serviceConfig = {
  PrivateTmp = true;
  /* ... */
};

and so on for any additional ServiceConfig one might wish to add.

Thank you, did not see this option.


Get application context in viewmodel

hello,
is there a way to get application context in the ViewModel

You can inject the application context into your ViewModel. See the wiki for direction on how: https://github.com/airbnb/MvRx/wiki/Advanced-Concepts#mvrxviewmodel


[Feature request] View space occupied by other apps

Functionality to view app size

There is unfortunately no official way to get this information
https://stackoverflow.com/questions/1806286/getting-installed-app-size


[WIP] Feat: Maintain archetype-catalog.xml for Maven

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

154 of 183 (84.15%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 82.048%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

charon/storage.py
11
13
84.62%

charon/pkgs/maven.py
141
168
83.93%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
1298

Relevant Lines:
1582

💛  - Coveralls


In strict mode code, functions can only be declared at top level or immediately within another function

Issue description:  The slider is working fine, but when I try to build with webpack in production mode I'm getting this error bellow:
ERROR in 62.9c41c87ccfbd7a77606b.js from UglifyJs
In strict mode code, functions can only be declared at top level or immediately within another function. [./node_modules/tiny-slider/src/tiny-slider.js:758,0][62.9c41c87ccfbd7a77606b.js:6177,6]
Any ideas?
Demo link/slider setting:  -
Tiny-slider version: 2.8.8
Browser name && version:  -
OS name && version:  Ubuntu 18.04.1 LTS

Created a merge request for this: #337

@FlorianKoerner  I just installed it via npm and the problem still exists.

@santamaria7 The fix has not yet been published. Did you replace the line in packages.json with the pull request?
    "tiny-slider": "https://github.com/FlorianKoerner/tiny-slider.git",

@FlorianKoerner  Actually no. I'll make the changes now. Thanks for your quick feedback.

Please check if this fix the issue.

Should work, too.

Same error
i use:
    "tiny-slider": "^2.8.8"
    "webpack": "^4.20.2"
    "uglifyjs-webpack-plugin": "^2.0.1",

npm versions 5.6.0 and 6.5.0
Solved the problem by adding external tiny-slider script.


Writing test

I've updated the two files as requested. I created these changes on the branch "patch-1", then created the "Writing-test" branch from there because i don't know how to rename the branch.
Thank you!
Dean

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: deanhaas sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Upgrade Gradle Version

Is your feature request related to a problem? Please describe.
Gradle 6 is incompatible with Java 17, which means it is annoying to develop on IntelliJ when working on Java 17 projects alongside DRES
Describe the solution you'd like
I'd like the Gradle version to be bumped to 7
Describe alternatives you've considered
The alternative is having to change some IntelliJ configurations everytime I work on DRES, which is more effort than bumping the Gradle version.
An even better option would be moving to Java 11+ and bumping the plugins which are used.

I just upgraded to the latest version of gradle (v7.3) on dev. So far, I didn't observe any issues with it, but I'd like to test this some more. If nothing comes up, this will go into the next release.
I don't currently see any benefit of increasing the java source compatibility to anything above 8, since there are currently no kotlin features that would benefit as far as I'm aware.


reverse filter should add a parameter to preserve keys

[array_reverse] (http://php.net/manual/en/function.array-reverse.php) receives the array and a $preserve_keys flag.
Currently there is no way to set the $preserve_keys flag on the Twig reverse filter.

fixed: 6e3a1c40160


Some fixes to allow for call instructions to name args, returns, and clobbers with constraints.

Allow early-pos uses with fixed regs that conflict with clobbers (which happen at late-pos), in addition to the existing logic for conflicts with late-pos defs with fixed regs.
This is a pretty subtle issue that was uncovered in #53 for the def case, and the fix here is the mirror of that fix for clobbers. The root cause for all this complexity is that we can't split in the middle of an instruction (because there's no way to insert a move there!) so if a use is live-downward, we can't let it live in preg A at early-pos and preg B != A at late-pos; instead we need to rewrite the constraints and use a fixup move.
The earlier change to fix #53 was actually a bit too conservative in that it always applied when such conflicts existed, even if the downward arg was not live. This PR fixes that (it's fine for the early-use and late-def to be fixed to the same reg if the use's liverange ends after early-pos) and adapts the same flexibility to the clobbers case as well.

Reworks the fixups for the def case mentioned above to not shift the def to the Early point. Doing so causes issues when the def is to a reffy vreg: it can then be falsely included in a stackmap if the instruction containing this operand is a safepoint.

Fixes the last-resort split-bundle-into-minimal-pieces logic from #59 to properly limit a minimal bundle piece to end after the early-pos, rather than cover the entire instruction. This was causing artificial overlaps between args that end after early-pos and defs that start at late-pos when one of the vregs hit the fallback split behavior.

This one is pretty subtle but perhaps one of @fitzgen, @elliottt, @jameysharp would be willing to review? I'm happy to do a live review / talk through it if that's easier.

Updated to be a little more generic with respect to safepoint handling (not special-casing early defs) as per suggestion by @jameysharp in offline discussion just now. Thanks! Should be ready to review now.

Another update pushed after finding a bug in the above changes while fuzzing locally.

Rebased to current main.


expose all

I think...
off(type) should remove all handlers for the given type
off() without arguments should just clear the all object completely
OR...
you can just expose all! it'll only be an addition of 4 chars, and I won't bother you anymore (or at least that's my story) ;P

Likely can't do either of the first features in such a small lib.
all is already exposed:
let all = {};
let e = mitt(all)
delete all.foo

@developit that's true today, but #19 changes that to use a private internal let all = Object.create(null).

Indeed. I'm fine exposing all, just whichever way is smaller.   Glad I brought it up though considering. Thanks 😀

@developit i was able to do it, but intentionally change that variant because the size limit. We could add it again but it cost 5bytes haha. :)

#19 also solves this. Even final size is 196b from few days :D

@tunnckoCore I can't remember - did we check the filesize difference between accepting all as an argument VS exposing it as a property?


SELECT ... ORDER BY query fails on data with int64 timestamp and timezone field

Describe the bug
When trying to query a Parquet file produced by Apache Flink I get an error:
ArrowError(InvalidArgumentError("column types must match schema types, expected Timestamp(Millisecond, Some(\"UTC\")) but found Timestamp(Millisecond, None) at column index 0"))

Output of Java parquet-schema:
message Row {
  optional int64 system_time (TIMESTAMP(MILLIS,true));
  optional int64 reported_date (TIMESTAMP(MILLIS,true));
  optional binary province (STRING);
  optional int64 total_daily;
}

To Reproduce
Download and extract the sample data: data.tar.gz.
Run:
use datafusion::arrow::util::pretty::print_batches;
use datafusion::prelude::*;

#[tokio::main]
async fn main() -> datafusion::error::Result<()> {
    let mut ctx = ExecutionContext::new();
    ctx.register_parquet("test", "flink.parquet")?;
    let df = ctx.table("test")?;

    //let df = ctx.sql("select * from test")?;
    let df = ctx.sql("select * from test order by reported_date desc")?;

    let records = df.collect().await?;
    print_batches(&records)?;
    Ok(())
}

Note that simple select works fine, but ORDER BY fails.
Expected behavior
Query executes without errors.

This is due to a limitation in arrow-rs that does not support timestamps with timezones: every timestamp that enters arrow-rs and is transformed is outputted as a timestamp without timezone. Because Timestamp(a,Some(b)) != Timestamp(a,None), the RecordBatch refuses to accept the transformed columns (as it expects one with timestamp).
A solution in DataFusion is to apply an extra cast after every operator from arrow to the expected schema, thereby converting the array back to the expected logical type (until the next operator hits). This implies not using operators that return RecordBatch such as batch_filter, etc. (since afaik they also error in arrow-rs).

Thanks for the prompt reply @jorgecarleitao.
I followed your advise of re-casting and this query works:
SELECT
  CAST(system_time as TIMESTAMP) as system_time,
  CAST(reported_date as TIMESTAMP) as reported_date,
  province,
  total_daily
FROM test
ORDER BY reported_date

Linking the corresponding arrow issue: apache/arrow-rs#393
I wonder if the impact of not having timezone support in Arrow can be minimized somehow, e.g. by treating Timestamp(a, None) as equal to Timestamp(a, Some("UTC")).
When reading parquet files produced by Spark the timestamps are being encoded as plain INT96 with no logical types, so it seems DataFusion already defaults to UTC?

Here is a related discussion on the mailing list: https://lists.apache.org/thread.html/ra4c0842067342056a64a8a13e03755d4be58e8dddfbb064ca92ed5a3%40<dev.arrow.apache.org>

Update: Latest datafusion no longer errors out on timestamps with time zones, but when printing out the column values it displays something like:
2022-12-20T00:17:00.207 (Unknown Time Zone 'UTC')

Thanks @sergiimk  -- I wonder if we need to update the arrow pretty printing code to handle that better 🤔

Seems to be working as expected now on latest main.
Via datafusion-cli:
❯ select * from '/home/jeffrey/Downloads/flink.parquet' order by reported_date desc limit 10;
+--------------------------+----------------------+----------+-------------+
| system_time              | reported_date        | province | total_daily |
+--------------------------+----------------------+----------+-------------+
| 2021-08-30T20:38:07.488Z | 2021-08-25T00:00:00Z | ON       | 807         |
| 2021-08-30T20:38:07.488Z | 2021-08-25T00:00:00Z | BC       | 719         |
| 2021-08-30T20:38:07.488Z | 2021-08-24T00:00:00Z | ON       | 634         |
| 2021-08-30T20:38:07.488Z | 2021-08-24T00:00:00Z | BC       | 708         |
| 2021-08-30T20:38:07.488Z | 2021-08-23T00:00:00Z | ON       | 509         |
| 2021-08-30T20:38:07.488Z | 2021-08-23T00:00:00Z | BC       | 559         |
| 2021-08-30T20:38:07.488Z | 2021-08-22T00:00:00Z | BC       | 465         |
| 2021-08-30T20:38:07.488Z | 2021-08-22T00:00:00Z | ON       | 489         |
| 2021-08-30T20:38:07.488Z | 2021-08-21T00:00:00Z | BC       | 563         |
| 2021-08-30T20:38:07.488Z | 2021-08-21T00:00:00Z | ON       | 681         |
+--------------------------+----------------------+----------+-------------+
10 rows in set. Query took 0.008 seconds.

❯

Can see it properly displays timezone with Z now
cc @alamb @sergiimk

Seems to be working as expected now on latest main.
Via datafusion-cli:
❯ select * from '/home/jeffrey/Downloads/flink.parquet' order by reported_date desc limit 10;
+--------------------------+----------------------+----------+-------------+
| system_time              | reported_date        | province | total_daily |
+--------------------------+----------------------+----------+-------------+
| 2021-08-30T20:38:07.488Z | 2021-08-25T00:00:00Z | ON       | 807         |
| 2021-08-30T20:38:07.488Z | 2021-08-25T00:00:00Z | BC       | 719         |
| 2021-08-30T20:38:07.488Z | 2021-08-24T00:00:00Z | ON       | 634         |
| 2021-08-30T20:38:07.488Z | 2021-08-24T00:00:00Z | BC       | 708         |
| 2021-08-30T20:38:07.488Z | 2021-08-23T00:00:00Z | ON       | 509         |
| 2021-08-30T20:38:07.488Z | 2021-08-23T00:00:00Z | BC       | 559         |
| 2021-08-30T20:38:07.488Z | 2021-08-22T00:00:00Z | BC       | 465         |
| 2021-08-30T20:38:07.488Z | 2021-08-22T00:00:00Z | ON       | 489         |
| 2021-08-30T20:38:07.488Z | 2021-08-21T00:00:00Z | BC       | 563         |
| 2021-08-30T20:38:07.488Z | 2021-08-21T00:00:00Z | ON       | 681         |
+--------------------------+----------------------+----------+-------------+
10 rows in set. Query took 0.008 seconds.

❯

Can see it properly displays timezone with Z now
cc @alamb @sergiimk

Thanks @Jefffrey
I also verified the query runs correctly using an explicitly created external table as well
❯ create external table test stored as parquet location 'flink.parquet';
0 rows in set. Query took 0.003 seconds.

❯ select * from test order by reported_date desc;
+--------------------------+----------------------+----------+-------------+
| system_time              | reported_date        | province | total_daily |
+--------------------------+----------------------+----------+-------------+
| 2021-08-30T20:38:07.488Z | 2021-08-25T00:00:00Z | ON       | 807         |
| 2021-08-30T20:38:07.488Z | 2021-08-25T00:00:00Z | BC       | 719         |
| 2021-08-30T20:38:07.488Z | 2021-08-24T00:00:00Z | BC       | 708         |
| 2021-08-30T20:38:07.488Z | 2021-08-24T00:00:00Z | ON       | 634         |
| 2021-08-30T20:38:07.488Z | 2021-08-23T00:00:00Z | ON       | 509         |
| 2021-08-30T20:38:07.488Z | 2021-08-23T00:00:00Z | BC       | 559         |
| 2021-08-30T20:38:07.488Z | 2021-08-22T00:00:00Z | ON       | 489         |
| 2021-08-30T20:38:07.488Z | 2021-08-22T00:00:00Z | BC       | 465         |
| 2021-08-30T20:38:07.488Z | 2021-08-21T00:00:00Z | ON       | 681         |
| 2021-08-30T20:38:07.488Z | 2021-08-21T00:00:00Z | BC       | 563         |
| 2021-08-30T20:38:07.488Z | 2021-08-20T00:00:00Z | BC       | 696         |
| 2021-08-30T20:38:07.488Z | 2021-08-20T00:00:00Z | ON       | 710         |
| 2021-08-30T20:38:07.488Z | 2021-08-19T00:00:00Z | ON       | 706         |
| 2021-08-30T20:38:07.488Z | 2021-08-19T00:00:00Z | BC       | 672         |
| 2021-08-30T20:38:07.488Z | 2021-08-18T00:00:00Z | ON       | 651         |
| 2021-08-30T20:38:07.488Z | 2021-08-18T00:00:00Z | BC       | 774         |
| 2021-08-30T20:38:07.488Z | 2021-08-17T00:00:00Z | BC       | 622         |
| 2021-08-30T20:38:07.488Z | 2021-08-17T00:00:00Z | ON       | 511         |
| 2021-08-30T20:38:07.488Z | 2021-08-16T00:00:00Z | ON       | 434         |
| 2021-08-30T20:38:07.488Z | 2021-08-16T00:00:00Z | BC       | 388         |
| 2021-08-30T20:38:07.488Z | 2021-08-15T00:00:00Z | ON       | 450         |
| 2021-08-30T20:38:07.488Z | 2021-08-15T00:00:00Z | BC       | 452         |
| 2021-08-30T20:38:07.488Z | 2021-08-14T00:00:00Z | BC       | 427         |
| 2021-08-30T20:38:07.488Z | 2021-08-14T00:00:00Z | ON       | 506         |
| 2021-08-30T20:38:07.488Z | 2021-08-13T00:00:00Z | ON       | 544         |
| 2021-08-30T20:38:07.488Z | 2021-08-13T00:00:00Z | BC       | 546         |
| 2021-08-30T20:38:07.488Z | 2021-08-12T00:00:00Z | BC       | 704         |
| 2021-08-30T20:38:07.488Z | 2021-08-12T00:00:00Z | ON       | 530         |
| 2021-08-30T20:38:07.488Z | 2021-08-11T00:00:00Z | BC       | 539         |
| 2021-08-30T20:38:07.488Z | 2021-08-11T00:00:00Z | ON       | 535         |
| 2021-08-30T20:38:07.488Z | 2021-08-10T00:00:00Z | ON       | 386         |
| 2021-08-30T20:38:07.488Z | 2021-08-10T00:00:00Z | BC       | 540         |
| 2021-08-30T20:38:07.488Z | 2021-08-09T00:00:00Z | BC       | 360         |
| 2021-08-30T20:38:07.488Z | 2021-08-09T00:00:00Z | ON       | 335         |
| 2021-08-30T20:38:07.488Z | 2021-08-08T00:00:00Z | BC       | 298         |
| 2021-08-30T20:38:07.488Z | 2021-08-08T00:00:00Z | ON       | 337         |
| 2021-08-30T20:38:07.488Z | 2021-08-07T00:00:00Z | BC       | 390         |
| 2021-08-30T20:38:07.488Z | 2021-08-07T00:00:00Z | ON       | 343         |
| 2021-08-30T20:38:07.488Z | 2021-08-06T00:00:00Z | BC       | 428         |
| 2021-08-30T20:38:07.488Z | 2021-08-06T00:00:00Z | ON       | 446         |
| .                                                                        |
| .                                                                        |
| .                                                                        |
+--------------------------+----------------------+----------+-------------+
1095 rows in set (40 shown). Query took 0.004 seconds.


Test vectors?

Not an issue, but a general question of relevance: Is there a test suite somewhere with a comprehensive list of half float values with their corresponding decimal values? The Wikipedia article has only a small handful of test vectors. I'm having trouble finding more samples, and I don't trust myself to calculate them by hand.
It doesn't have to be a test suite tailored to this library, but any one dealing with 16-bit IEEE floats. In particular, I'd like to see more corner cases involved with rounding to nearest.

Please, refer to upstream. This is a library we imported from https://sourceforge.net/projects/half/ and use in our projects.

Please, refer to upstream. This is a library we imported from https://sourceforge.net/projects/half/ and use in our projects.

Yes I know it's from Christian Rau and is hosted on SourceForge. I was just hoping that someone here knew of an existing test suite - any half float test suite.
I'll try asking the original author, but the academic types publishing these sorts of libraries aren't always willing/able to provide support to the general community.

Yes I know it's from Christian Rau and is hosted on SourceForge. I was just hoping that someone here knew of an existing test suite - any half float test suite.
I'll try asking the original author, but the academic types publishing these sorts of libraries aren't always willing/able to provide support to the general community.

Unfortunately, I do not know about any tests. We are happy that there is a freely available implementation that does (or seems to do) what it promises. IIRC, we use it only for converting between floats and half floats in our data formats.

Unfortunately, I do not know about any tests. We are happy that there is a freely available implementation that does (or seems to do) what it promises. IIRC, we use it only for converting between floats and half floats in our data formats.

I have found the following:

https://devblogs.microsoft.com/dotnet/introducing-the-half-type/
http://www.jhauser.us/arithmetic/TestFloat.html

While they don't have handy test vectors I can borrow, I can still use them to generate the 16-bit float representations of various corner cases. Alternatively, I could even generate test vectors for the entire set of all possible 16-bit float representations, seeing that there are "only" 65536 cases.

I have found the following:

https://devblogs.microsoft.com/dotnet/introducing-the-half-type/
http://www.jhauser.us/arithmetic/TestFloat.html

While they don't have handy test vectors I can borrow, I can still use them to generate the 16-bit float representations of various corner cases. Alternatively, I could even generate test vectors for the entire set of all possible 16-bit float representations, seeing that there are "only" 65536 cases.

The GetHashCode method of .NET 5's new Half struct returns the 16-bit integer representation of the number's bits.
The Half API does not seem to expose a direct way of initializing a number from raw bytes, so I had to use System.Runtime.InteropServices.Marshall (in lieu of unsafe pointer manipulations).
This works for me:
using System;
using System.Runtime.InteropServices;

namespace float16test
{
    class Program
    {
        static Half BytesToHalf(ushort bits)
        {
            byte [] bytes = new byte[2] {(byte)(bits & 0xff), (byte)(bits >> 8)};
            Half half = (Half)0;
            int size = Marshal.SizeOf(half);
            IntPtr i = Marshal.AllocHGlobal(size);
            Marshal.Copy(bytes, 0, i, size);
            half = (Half)Marshal.PtrToStructure(i, half.GetType());
            Marshal.FreeHGlobal(i);
            return half;
        }

        static void Main(string[] args)
        {
            Half half = (Half)0.33325195;
            Console.WriteLine("0x{0:X4}", half.GetHashCode()); // prints 0x3555

            Console.WriteLine(BytesToHalf(0x3555).ToString()); // prints 0.3333
        }
    }
}

I'll share my test vectors here when I come up with them. I hope this helps someone else in the same predicament as me.

The GetHashCode method of .NET 5's new Half struct returns the 16-bit integer representation of the number's bits.
The Half API does not seem to expose a direct way of initializing a number from raw bytes, so I had to use System.Runtime.InteropServices.Marshall (in lieu of unsafe pointer manipulations).
This works for me:
using System;
using System.Runtime.InteropServices;

namespace float16test
{
    class Program
    {
        static Half BytesToHalf(ushort bits)
        {
            byte [] bytes = new byte[2] {(byte)(bits & 0xff), (byte)(bits >> 8)};
            Half half = (Half)0;
            int size = Marshal.SizeOf(half);
            IntPtr i = Marshal.AllocHGlobal(size);
            Marshal.Copy(bytes, 0, i, size);
            half = (Half)Marshal.PtrToStructure(i, half.GetType());
            Marshal.FreeHGlobal(i);
            return half;
        }

        static void Main(string[] args)
        {
            Half half = (Half)0.33325195;
            Console.WriteLine("0x{0:X4}", half.GetHashCode()); // prints 0x3555

            Console.WriteLine(BytesToHalf(0x3555).ToString()); // prints 0.3333
        }
    }
}

I'll share my test vectors here when I come up with them. I hope this helps someone else in the same predicament as me.

For those following this, I discovered that the .NET 5 Half has a defect when converting Half subnormals to Single/Double: https://github.com/dotnet/runtime/issues/46515
The .NET 5 unit test for Half can be found here, which contains a few additional test vectors not found on Wikipedia: https://github.com/dotnet/runtime/blob/master/src/libraries/System.Runtime/tests/System/HalfTests.cs
I'll later share my test vectors here and will close this issue.

For those following this, I discovered that the .NET 5 Half has a defect when converting Half subnormals to Single/Double: https://github.com/dotnet/runtime/issues/46515
The .NET 5 unit test for Half can be found here, which contains a few additional test vectors not found on Wikipedia: https://github.com/dotnet/runtime/blob/master/src/libraries/System.Runtime/tests/System/HalfTests.cs
I'll later share my test vectors here and will close this issue.

As promised, here are my test vectors: https://gist.github.com/ecorm/3b5963749752f2cc2f96fb493d29fcba
16-bit float library authors and maintainers may use them as they see fit. Provided "as is" with no warranty.

As promised, here are my test vectors: https://gist.github.com/ecorm/3b5963749752f2cc2f96fb493d29fcba
16-bit float library authors and maintainers may use them as they see fit. Provided "as is" with no warranty.


v1.1.0

This PR represents v1.1.0

This release will include https://github.com/MetaMask/etherscan-link/compare/8a9f8aa...8f5eeda

A new version of the package etherscan-link (1.1.0) was published at 2020-04-06T14:00:00.180Z [...]. The shasum of this package was bc43cc517c7c07646e128874bd61afa0ca7f1746.


Rename OS X to macOS

Rename target Alamofire OSX to Alamofire macOS.
Rename target Alamofire OSX Tests to Alamofire macOS Tests.
Rename scheme Alamofire OSX to Alamofire macOS.
Replace os(OSX) with os(macOS).
Update CONTRIBUTING.md.
Update .travis.yml (also change xcpretty -c to xcpretty since -c is the default argument).

Alamofire: https://github.com/Alamofire/Alamofire/pull/1520
AlamofireNetworkActivityIndicator: no change needed

Thanks for putting this together @JustinJiaDev! 🍻


get alignments using attention

Hi,
With a trained model checkpoint, I evaluated it on a set of 'test' sentences. In the result, I get some <unk> tokens in translated sentences. Now, I'd like to solve this issue by figuring out which words in source sentence caused these unk tokens.
For this, as far as I understand, we can use the attention mechanism to get the word alignments? But, I'm not sure where exactly I should start doing this in the current NMT codebase. could someone please point out the exact point where such an implementation can be done?
Or is there any other way to get the alignment of words?
Interestingly, a dictionary can be extracted from alignment with scores as mentioned here: En-Vi alignment dictionary
It'd be nice to know how to get this dictionary. Maybe @lmthang can offer suggestions please?
Thanks!

Hi @kmario23 ,
We save the alignment as an image in the _sample_decode method if you don't use a beam search decoder with an attention model. The image can be visualized in tensorboard.
You can look at this method to see how we extract the alignment history from the final state.

Hi @kmario23 ,
Have you solved it?
Thanks

I do use a beam search decoder too, and also with num_translations_per_input > 1,
I am quite interested in getting the alignments too.
Can you point us to where to look at to get the alignments with a beam search decoder?
And when num_translations_per_input > 1, how to get the alignments of each output translation for a single input?

@oahziur, I see that they check if beam width is 0. Is there a reason? Does beam search prevent the alignment from happening?

I try to get alignment using beam width 0 but can't. Is there any way to visualize the alignment for a particular sentence?

Is there any progress in solving that issue?


Add light and Dark Mode Functionality

Description
Add dark and light mode functionality.

I an work on it. Please assign

@sumitkumarju Go ahead!


⚠ Bofrost.de has degraded performance

In 80e8051, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 915 ms

Resolved: Bofrost.de performance has improved in f9631b5 after 6 minutes.


Typo in install script - elaticsearch

CentOS 7 - updated
wget ht[ ]tps://files.molo.ch/builds/centos-7/moloch-1.1.1-1.x86_64.rpm
Installed, using DEMO elastic install
Error during install
/data/moloch/bin/Configure: line 151: /etc/elaticsearch/elasticsearch.yml: No such file or directory
Typo in "elaticsearch"
Appears this missed the index_not_found_exception flag not being configured, not sure what else was missed.

removing the file and just using what ships with elasticsearch now


flutter_gallery__transition_perf_e2e_ios32 failing

flutter_gallery__transition_perf_e2e_ios32 is failing in the devicelab:
2020-09-18T15:53:37.807818: stdout: flutter: > Grid@Material
2020-09-18T15:53:38.805892: stderr: Unhandled exception:
stderr: DriverError: Failed to fulfill RequestData due to remote error
2020-09-18T15:53:38.806006: stderr: Original error: JSON-RPC error -32000: Bad state: The client closed with pending request "ext.flutter.driver".
2020-09-18T15:53:38.806128: stderr: Original stack trace:
2020-09-18T15:53:38.806348: stderr: package:json_rpc_2/src/client.dart 123:62                       Client.sendRequest
stderr: package:json_rpc_2/src/peer.dart 98:15                          Peer.sendRequest
stderr: package:vm_service_client/src/scope.dart 64:23                  Scope.sendRequestRaw
2020-09-18T15:53:38.807074: stderr: package:vm_service_client/src/isolate.dart 361:19               VMIsolateRef.invokeExtension
stderr: package:flutter_driver/src/driver/vmservice_driver.dart 348:63  VMServiceFlutterDriver.sendCommand
stderr: package:flutter_driver/src/driver/driver.dart 503:45            FlutterDriver.requestData
stderr: package:e2e/e2e_driver.dart 73:42                               e2eDriver
stderr: ===== asynchronous gap ===========================
stderr: test_driver/transitions_perf_e2e_test.dart 7:24                 main
stderr: dart:isolate-patch/isolate_patch.dart 301:19                    _startIsolate.
stderr: dart:isolate-patch/isolate_patch.dart 168:12                    _RawReceivePortImpl._handleMessage
flutter_gallery__transition_perf_e2e_ios32_5c85803_2.log

Suspect https://github.com/flutter/flutter/commit/409e994cd03749d5a903f01cf4ec5b3ee074a2ee, will revert to see.

Or not, looks like https://github.com/flutter/flutter/pull/66123 fixed a different test failure.

Yes, this was a rather involved change that required various fixes over multiple commits. If at all possible, we should try and avoid reverting these commits and work on finding the cause of the issue or disable DDS for these tests.

Sorry, our tree hygiene policy means that we have to revert in situations like this. See https://github.com/flutter/flutter/wiki/Tree-hygiene for details.
I landed the revert here https://github.com/flutter/flutter/pull/66164, but the test continues to fail, so I filed an infra issue here https://github.com/flutter/flutter/issues/66166. There continue to be the same warning messages from DDS, but I'm not able to determine that that is the reason the test is failing.


Introduce memory file system, closes #6

Codecov Report

Merging #7 into master will decrease coverage by 1.48%.
The diff coverage is 95.45%.

@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
- Coverage   98.15%   96.67%   -1.49%
==========================================
  Files          13       16       +3
  Lines         163      361     +198
==========================================
+ Hits          160      349     +189
- Misses          3       12       +9

Impacted Files
Coverage Δ

tests/spike/test_memory_filesystem.cpp
100% <100%> (ø)

src/spike/memory_filesystem.cpp
91.89% <91.89%> (ø)

src/spike/memory_filesystem.hpp
95.65% <95.65%> (ø)

Continue to review full report at Codecov.

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


Contact Mechanics: Sometimes layout of E* line in form is broken

Sometimes there is an extra line in the form, because of an unexpected line break in the line for pressures:

This seems to be timing related, probably because the plot is not fully loaded yet.
When reloading the page it looks fine. I'll remove the milestone, let's see how this behaves in production.

Is this still relevant?

It now looks better.


python312Packages.alpha-vantage: 2.3.1 -> 3.0.0

Diff: https://github.com/RomelTorres/alpha_vantage/compare/refs/tags/v2.3.1...v3.0.0
Changelog: https://github.com/RomelTorres/alpha_vantage/releases/tag/3.0.0
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

4 packages built:

python311Packages.alpha-vantage
python311Packages.alpha-vantage.dist
python312Packages.alpha-vantage
python312Packages.alpha-vantage.dist


undefined sessionData for authenticate resolve with JWT authenticator

My goal is to get the token data after a successful authentication so I can extract a user ID and query my API to get more user information. My login controller has code that looks like:
this.get('session').authenticate('authenticator:jwt', credentials).then(
  (sessionData) => {
     console.log(sessionData); // Logs "undefined"
  },
  (reason) => {
    // not important for this issue
  });

I found this confusing because the authenticator passes sessionData to the resolve callback. To be sure, I tossed in a couple of console.log statements.
      this.makeRequest(this.serverTokenEndpoint, data, headers).then(response => {
        Ember.run(() => {
          try {
            const sessionData = this.handleAuthResponse(response);
            console.log(sessionData);
            console.log(this.getTokenData(sessionData.token));

            resolve(sessionData);
          } catch(error) {
            reject(error);
          }
        });

In Chrome, these log statements produced:

Perhaps I have a misunderstanding of the Ember run loop (or promises), but I assumed that the sessionData in the authenticator code would be the same as the sessionData in my resolve callback.
Any idea what's going on here? Is there another way possible to get access to the token data for the currently authenticated user? Thanks!

Shoot, sorry for the noise. I should have Googled it before wasting all this time writing an issue. authenticate is an ember-simple-auth API and it doesn't resolve with a value. Looks like the data is accessible via the session's authenticated property.

I have a question why is ember-simple-auth-token not returning the decoded token data?
There are many use cases when you want to use the claims directly from session.data.authenticated.

@GramozKrasniqi I think part of the problem is out of ember-simple-auth-token's hands. ember-simple-auth is what controls the return value of the authenticate promise. To deal with this, I imported the JWT authenticator into my app and called its getTokenData method. For me, that ended up looking like this:
import Ember from 'ember';
import JWT from 'ember-simple-auth-token/authenticators/jwt';

const { inject: { service }, isEmpty, RSVP } = Ember;

export default Ember.Service.extend({
  session: service(),
  store: service(),

  load() {
    return new RSVP.Promise((resolve, reject) => {
      const token = this.get('session.data.authenticated.token');
      if (!isEmpty(token)) {
        const userId = this.getUserIdFromToken(token);
        this.get('store').find('user', userId).then((user) => {
          this.set('user', user);
          resolve();
        }, reject);
      } else {
        resolve();
      }
    });
  },

  getUserIdFromToken(token) {
    const jwt = new JWT();
    const tokenData = jwt.getTokenData(token);
    return tokenData['user_id'];
  }
});

@mblayman yep this would be a solution, but the problem is that you wont be using only jwt authenticator and in that case it will fail (minght be that you have another encoding or it is encoded).
I changed the jwt implementation a bit and it seems that the changes are working thats why i asked if there were any reason why the jwt implementation is not returning the decoded token.
This is the code from the original jwt authenticator handleAuthResponse method.
'handleAuthResponse(response) {
const token = Ember.get(response, this.tokenPropertyName);
if (Ember.isEmpty(token)) {
  throw new Error('Token is empty. Please check your backend response.');
}

const tokenData = this.getTokenData(token);
const expiresAt = Ember.get(tokenData, this.tokenExpireName);
const tokenExpireData = {};

tokenExpireData[this.tokenExpireName] = expiresAt;

this.scheduleAccessTokenRefresh(expiresAt, token);

return assign(this.getResponseData(response), tokenExpireData);

},`
I changed the last line to
return tokenData;
and now i have the decoded token into the store.
P.S i am trying to find out if this solution creates any side effects.

Good points. 😄 I'm not sure of original author's intent here so it's an interesting suggestion. As someone else who would benefit from having the decoded data returned, I would love to know the reason too.

@mblayman  please dont use return tokenData;
instead use return assign(this.getResponseData(response), tokenData);
The first one dosent send the authorization header :D.


Homepage replicate across all pages

On our site all pages are the same copying the homepage but with different URL’s – the URL rewrite’s don’t seem to work.
We have disabled all plugins, updated Wordpress and eliminated hosting issues and .htaccess. If you swap to other themes it is fine. We have also simplified our site by removing the code in the header, footer and templates but the homepage still displays on all pages.
We have found various other articles referencing using wp_reset_query but these are already in place.
On the permalinks setting it works with plain ?p=123 so have set it to that but none of the other options work.

Are all your pages set to use the front template?

If yes, try using a different template (e.g the default template).

They are all using different templates

Can you try downloading a fresh install and see if your problem persists?

The error was in functions.php
commenting out the line add_filter( 'rewrite_rules_array', 'disable_embeds_rewrites' ); fixed it
many hours wasted on this

@fingomarketing I'm sorry you wasted many hours but that line of code isn't even in FoundationPress.

@fingomarketing : I also wasted time on an error that was not caused by FoundationPress. Which is just fine. No problem. But please do not pretend it's my fault that you have spent hours debugging your own code.

Thanks olefredrik wasn't saying it was your fault I was posting my solution in case others had a similar issue. Thanks for your help and the quick response.


docker registry endpoints should be prefixed with v1

It looks like repository.go uses version 1 of the docker registry api [1], but none of the endpoints are prefixed with /v1/.  Here's an example line from repository.go:
req, err := http.NewRequest("GET", "https://"+path.Join(registry, "repositories", appName, "tags"), nil)

The artifactory docker registry [2] requires that v1 be in the registry url just like the api spec says, but there is no way to specify it to docker2aci.
[1] https://docs.docker.com/v1.6/reference/api/registry_api/
[2] http://www.jfrog.com/confluence/display/RTF/Docker+Repositories

We add the /v1/ here: https://github.com/appc/docker2aci/blob/8ac8ccffacb8e2040cf94e3af9ca972766353d82/lib/backend/repository/repository.go#L347

@jaybuff are you seeing docker2aci fail against artifactory?
On Sep 17, 2015 03:07, "Iago López Galeiras"<EMAIL_ADDRESS>wrote:

We add the /v1/ here:
https://github.com/appc/docker2aci/blob/8ac8ccffacb8e2040cf94e3af9ca972766353d82/lib/backend/repository/repository.go#L347
—
Reply to this email directly or view it on GitHub
https://github.com/appc/docker2aci/issues/85#issuecomment-141033471.

Yes, pulling a docker image from artifactory using rkt-0.6.1 results in a 404.  0.6.1 has the line @iaguis references.  I'm investigating why it doesn't work.  Here's the actual command and error:
$ rkt --insecure-skip-verify fetch docker://registry.example.com/myns/myrepo:2.0
rkt: fetching image from docker://registry.example.com/myns/myrepo:2.0
error converting docker image to ACI: error getting ImageID from tag 2.0: HTTP code: 404. URL: https://registry.example.com/repositories/myns/myrepo/tags

Ah, artifactory 3.9.4 doesn't set the X-Docker-Endpoints header in response to the GET /v1/repositories/myns/myrepo/images.  I'm not sure if other versions of artifactory set it.

Hi all, I am still not able to fetch a Docker image via rkt from Artifactory 4.8.2.
CA Certificate has been added to CoreOS after:
/var/lib/rkt/rkt fetch docker://<artifactoryhost>:50000/coreos/etcd:v3.0.2 --insecure-options=image image: remote fetching from URL "docker://<artifactoryhost>:50000/coreos/etcd:v3.0.2" fetch: Get https://<artifactoryhost>:50000/v2: x509: certificate signed by unknown authority
After the CA certificate was added, I get:
/var/lib/rkt/rkt fetch docker://<artifactoryhost>:50000/coreos/etcd:v3.0.2 --insecure-options=all   image: remote fetching from URL "docker://<artifactoryhost>:50000/coreos/etcd:v3.0.2" fetch: unexpected http code: 400
With docker it works:
docker pull docker.wdf.sap.corp:50000/coreos/etcd:v3.0.2 v3.0.2: Pulling from coreos/etcd e110a4a17941: Already exists  31eef2201534: Already exists  a043d21891c5: Already exists  fd2d99e13d06: Already exists  Digest: sha256:d432e9d3a759eb599b075f92f32d661e5b2e6acaaa80377740fb55d474581f04 Status: Image is up to date for docker.wdf.sap.corp:50000/coreos/etcd:v3.0.2
Any idea on this?

does --debug give you any more information on which URL is 400ing?
On 18 August 2016 at 14:05, Stefan Vetter<EMAIL_ADDRESS>wrote:

Hi all, I am still not able to fetch a Docker image via rkt from
Artifactory 4.8.2.
CA Certificate has been added to CoreOS after:
/var/lib/rkt/rkt fetch docker://:50000/coreos/etcd:v3.0.2
--insecure-options=image
image: remote fetching from URL "docker://:
50000/coreos/etcd:v3.0.2"
fetch: Get https://:50000/v2: x509: certificate signed
by unknown authority
After the CA certificate was added, I get:
/var/lib/rkt/rkt fetch docker://:50000/coreos/etcd:v3.0.2
--insecure-options=all
image: remote fetching from URL "docker://:
50000/coreos/etcd:v3.0.2"
fetch: unexpected http code: 400
With docker it works:
docker pull docker.wdf.sap.corp:50000/coreos/etcd:v3.0.2
v3.0.2: Pulling from coreos/etcd
e110a4a17941: Already exists
31eef2201534: Already exists
a043d21891c5: Already exists
fd2d99e13d06: Already exists
Digest: sha256:d432e9d3a759eb599b075f92f32d66
1e5b2e6acaaa80377740fb55d474581f04
Status: Image is up to date for docker.wdf.sap.corp:50000/
coreos/etcd:v3.0.2
Any idea on this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/appc/docker2aci/issues/85#issuecomment-240703478, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACewN1kkKD1tsIwgiOM3ZyHAAZBQemG6ks5qhEqJgaJpZM4F-wZs
.

Also to give it a mention it does not work with docker2aci itself:
bin/docker2aci docker://:50000/coreos/etcd:v3.0.2 --debug -insecure-skip-verify=true -insecure-allow-http=true
Error: conversion error: unexpected http code: 400

Another hint probably:
docker save -o etcd_3.0.2.docker b1ef96aec70b docker2aci etcd_3.0.2.docker Error: conversion error: repositories file not found
While when running the pulled/saved image via docker it works properly.
With additional options:
./docker2aci -image=coreos/etcd:3.0.2 /tmp/etcd_3.0.2.docker -debug=true -insecure-skip-verify=true -insecure-allow-http=true Error: conversion error: repositories file not found

Made another test to verify where the problem really comes from:
Have been setting up nginx to proxy quay with following configuration which resulted in the same error:
`upstream docker-registry {
server quay-registry.s3.amazonaws.com;
}
server {
listen 6443;
server_name <IP_ADDRESS>;
ssl on;
ssl_certificate /etc/pki/tls/certs/<IP_ADDRESS>.pem;
ssl_certificate_key /etc/pki/tls/certs/<IP_ADDRESS>.key;
client_max_body_size 0; # disable any limits to avoid HTTP 413 for large image uploads
required to avoid HTTP 411: see Issue #1486 (https://github.com/docker/docker/issues/1486)
chunked_transfer_encoding on;
add_header Docker-Distribution-API-Version registry/2.0;
location / {
auth_basic off;
proxy_pass            http://docker-registry;
proxy_set_header      Host           $http_host;   # required for docker client's sake
proxy_set_header      X-Real-IP      $remote_addr; # pass on real client's IP
proxy_set_header      Authorization  "";  # see https://github.com/dotcloud/docker-registry/issues/170
proxy_read_timeout    900;
}
location /_ping {
auth_basic off;
proxy_pass            http://docker-registry;
proxy_set_header      Host           $http_host;   # required for docker client's sake
proxy_set_header      X-Real-IP      $remote_addr; # pass on real client's IP
proxy_set_header      Authorization  "";  # see https://github.com/dotcloud/docker-registry/issues/170
proxy_read_timeout    900;
}
location /v1/_ping {
auth_basic off;
proxy_pass            http://docker-registry;
proxy_set_header      Host           $http_host;   # required for docker client's sake
proxy_set_header      X-Real-IP      $remote_addr; # pass on real client's IP
proxy_set_header      Authorization  "";  # see https://github.com/dotcloud/docker-registry/issues/170
proxy_read_timeout    900;
}
location /v2/ {
# Do not allow connections from docker 1.5 and earlier
# docker pre-1.6.0 did not properly set the user agent on ping, catch "Go " user agents
if ($http_user_agent ~ "^(docker/1.(3|4|5(?!.[0-9]-dev))|Go ).$" ) {
return 404;
}
proxy_pass            http://docker-registry;
proxy_set_header      Host                            $http_host;   # required for docker client's sake
proxy_set_header      X-Real-IP                       $remote_addr; # pass on real client's IP
proxy_set_header      X-Forwarded-For                 $proxy_add_x_forwarded_for;
proxy_set_header      X-Forwarded-Proto               $scheme;
proxy_read_timeout    900;

}
}`

Latest information: nginx proxy does not work out properly for performing analysis as based on the command it delivers other results as artifactory.
If you want me to test some commands/binaries, don't hesitate to drop me a comment.
Thanks!

Nope, no information. Sorry.
Am Donnerstag, 18. August 2016 schrieb Jonathan Boulle :

does --debug give you any more information on which URL is 400ing?
On 18 August 2016 at 14:05, Stefan Vetter<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

Hi all, I am still not able to fetch a Docker image via rkt from
Artifactory 4.8.2.
CA Certificate has been added to CoreOS after:
/var/lib/rkt/rkt fetch docker://:
50000/coreos/etcd:v3.0.2
--insecure-options=image
image: remote fetching from URL "docker://:
50000/coreos/etcd:v3.0.2"
fetch: Get https://:50000/v2: x509: certificate signed
by unknown authority
After the CA certificate was added, I get:
/var/lib/rkt/rkt fetch docker://:
50000/coreos/etcd:v3.0.2
--insecure-options=all
image: remote fetching from URL "docker://:
50000/coreos/etcd:v3.0.2"
fetch: unexpected http code: 400
With docker it works:
docker pull docker.wdf.sap.corp:50000/coreos/etcd:v3.0.2
v3.0.2: Pulling from coreos/etcd
e110a4a17941: Already exists
31eef2201534: Already exists
a043d21891c5: Already exists
fd2d99e13d06: Already exists
Digest: sha256:d432e9d3a759eb599b075f92f32d66
1e5b2e6acaaa80377740fb55d474581f04
Status: Image is up to date for docker.wdf.sap.corp:50000/
coreos/etcd:v3.0.2
Any idea on this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/appc/docker2aci/issues/85#issuecomment-240703478,
or mute
the thread
<https://github.com/notifications/unsubscribe-auth/
ACewN1kkKD1tsIwgiOM3ZyHAAZBQemG6ks5qhEqJgaJpZM4F-wZs>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/appc/docker2aci/issues/85#issuecomment-240710345, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFI-HwGwSY-XVEugW6jPiyoee4Bbcf-yks5qhFJjgaJpZM4F-wZs
.


Add ubsan to CI

Change log:

Fix PollSet void* memory alignment ub check
Fix WriteBufferFromFiFoBuffer memcpy null pointer ub check
Add ubsan to CI

LGTM, pls reorganize commits

@JackyWoo done


Search is indexing only article's Titles

All indications are that the search function only looks for words from the Titles.
It does not index Author, Description, Text Body or even Tags.
I don't want to criticize here, the theme is really great 👍🏻
IMHO it's just not practical.
The user may need to search for articles by author.
Is there way to improve this?

Addressed via a new config

I am not quite sure, if this really works :-(

This is searching for titles only (still).  It's even evident within the demo.  Any plans to correct this?


testing: stack unavailable when a parallel test times out

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version devel +a2bd5c5 Thu Nov 24 03:48:45 2016 +0000 linux/amd64

What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/mvdan/go"
GORACE=""
GOROOT="/home/mvdan/tip"
GOTOOLDIR="/home/mvdan/tip/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build553187312=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"

What did you do?
Ran go test -short -timeout 1s with a new test case that I knew was going to loop forever and time out (trying to fix it).
What did you expect to see?
The go test timeout being hit and the panic with a useful stack trace shown.
What did you see instead?
panic: test timed out after 1s

goroutine 177 [running]:
testing.startAlarm.func1()
        /home/mvdan/tip/src/testing/testing.go:1041 +0xf9
created by time.goFunc
        /home/mvdan/tip/src/time/sleep.go:170 +0x44

goroutine 1 [chan receive]:
testing.tRunner.func1(0xc4200860e0)
        /home/mvdan/tip/src/testing/testing.go:655 +0x17e
testing.tRunner(0xc4200860e0, 0xc420039db8)
        /home/mvdan/tip/src/testing/testing.go:681 +0x149
testing.runTests(0xc4200cc180, 0x6bb720, 0x12, 0x12, 0x10)
        /home/mvdan/tip/src/testing/testing.go:906 +0x29d
testing.(*M).Run(0xc42003af20, 0x0)
        /home/mvdan/tip/src/testing/testing.go:841 +0xfc
github.com/mvdan/sh/syntax.TestMain(0xc420039f20)
        /home/mvdan/go/src/github.com/mvdan/sh/syntax/parser_test.go:66 +0x5d
main.main()
        github.com/mvdan/sh/syntax/_test/_testmain.go:82 +0xf7

goroutine 9 [chan receive]:
testing.(*T).Run(0xc4200862a0, 0xc420162bc8, 0x3, 0xc4201647e0, 0x0)
        /home/mvdan/tip/src/testing/testing.go:717 +0x2f1
github.com/mvdan/sh/syntax.TestParseErrBash(0xc4200862a0)
        /home/mvdan/go/src/github.com/mvdan/sh/syntax/parser_test.go:752 +0x23f
testing.tRunner(0xc4200862a0, 0x5d1ad8)
        /home/mvdan/tip/src/testing/testing.go:679 +0x13f
created by testing.(*T).Run
        /home/mvdan/tip/src/testing/testing.go:716 +0x2c7

goroutine 10 [chan receive]:
testing.runTests.func1.1(0xc4200860e0)
        /home/mvdan/tip/src/testing/testing.go:905 +0x47
created by testing.runTests.func1
        /home/mvdan/tip/src/testing/testing.go:905 +0xaf

goroutine 170 [running]:
        goroutine running on other thread; stack unavailable
created by testing.(*T).Run
        /home/mvdan/tip/src/testing/testing.go:716 +0x2c7
FAIL    github.com/mvdan/sh/syntax      1.015s

Note that this doesn't happen all the time. It happens often, though - about half of the times I run go test.
I don't know if this is by design. I can see the cause - the use of t.Parallel() - but I don't think its use should have this inconvenient.

For the sake of completeness, this is what the stack trace looks when it happens to be alright:
goroutine 170 [runnable]:
github.com/mvdan/sh/syntax.(*parser).wordPart(0xc420106000, 0x6a0fc0, 0xc427443a88)
        /home/mvdan/go/src/github.com/mvdan/sh/syntax/parser.go:537 +0x2041
[...]
github.com/mvdan/sh/syntax.checkError.func1(0xc42015ddc0)
        /home/mvdan/go/src/github.com/mvdan/sh/syntax/parser_test.go:731 +0xb4
testing.tRunner(0xc42015ddc0, 0xc4201647e0)
        /home/mvdan/tip/src/testing/testing.go:679 +0x13f
created by testing.(*T).Run
        /home/mvdan/tip/src/testing/testing.go:716 +0x2c7
FAIL    github.com/mvdan/sh/syntax      1.011s

I have a vague memory that setting GOTRACEBACK=crash might cause the omitted backtraces to be printed. But now I can't find any docs that say it.

That's right (setting GOTRACEBACK=crash will print all backtraces) but I
agree
this is not documented because it doesn't work on all platforms.
(More detailed explanations: with GOTRACEBACK=crash, because it's going
to crash anyway, the runtime can send signals to each thread and ask it to
dump stack trace. But this implementation obviously don't work on systems
without async signals.)

Maybe the testing package should automatically set GOTRACEBACK=crash?

Frustratingly, this happens 100% of the time when I do:
go test -short -timeout 1s -parallel 1 -run TestThatHangs

Surely this one is fixable? If -parallel 1 is given, I would assume that everything gets run on the main thread and this doesn't happen at all.

If -parallel 1 is given, I would assume that everything gets run on the main thread and this doesn't happen at all.

Running tests involves a fair amount of machinery. Running everything on the main thread is a hard enough problem that testing.M was introduced in large part to enable it. So the fix here is going to have to be general, not particular to the value of -parallel.

For future reference, I ended up opening https://github.com/golang/go/issues/19280 for forcing parallel tests to run sequentially.

Duplicate of #13161.


Fix Avalara crash with shipping methods webhook

This PR removes plugins call from checkout's subtotal calculation done for shipping methods webhook. This plugins call resulted in infinite recursion when both Avalara and webhook plugin are enabled.
This change is in line with what we are planning to do for discounts, and from my testing it doesn't affect tax amounts on checkout.
Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[x] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-5816 Assign shipping method crash with Avalara


Use PUSH security for regression

This PR applies PUSH security to the install of the managed beta in regression_org, meaning that new fields do not have FLS granted to all users.
Note that this does not completely solve the FLS management issue, as update_admin_profile will still run later and grant FLS to fields on selected standard objects. This is a first step.
Critical Changes
Changes
Issues Closed
Community Ideas Delivered
New Metadata
Deleted Metadata

I'm withdrawing this PR in favor of a more sophisticated reorganization of regression_org to suit this need.


Sort config map data by key alphabetically

This is done for ConfigMap printer, but not in the container printer which has a ConfigMap card.


Add unit test for bug fixed by PR #832

Link to PR: #832

it was hit by a case in  #831 - we should probably write unit tests for all the state_exts

closing as we now have unit tests for all state_exts in the sequencer


Iron MQ error 400 A reservation_id is required

Hi,
I'm using Laravel 5.1 and Iron MQ 4.0.1
I encountered error when calling $job->delete();
 [IronCore\HttpException]
  http error: 400 | {"msg":"A reservation_id is required"}

I've tried Iron MQ v 2 as suggested on Laravel 5.1 documentation, but I got error that I need to use v3 API, so I updated Iron MQ to 2.*
Thanks

We only work with the 2.x package.

The 4.x package must require that new field.

Maybe you need to enable the older version of the API on your control panel or something?

Ping @taylorotwell. You use IronMQ don't you?

I also am having this issue on Laravel 4.2 with Version 3.* of IronMQ. Can't seem to find a way to activate the legacy API for IronMQ so we can use a different branch either. It looks like the job can't be removed though!

I also am having this issue on Laravel 4.2 with Version 3.* of IronMQ.

You CAN NOT use 4.x in Laravel 4.2. You MUST use 1.x as documented.

It may be documented mate, but it doesn't work. I think IronMQ turned off anything that isn't API v3 from working. At least that was the response messages I was getting back.

but it doesn't work.

It's not meant to. API v3 can't be used on Laravel at all yet. Soon it'll be available on 5.1+.

Do you feel it may be better for me to not use IronMQ for this project then and to utilise SQS?

Graham plz

Sure try SQS.

Hah! Thanks T-dog.

Was this ever fixed? Why is it closed?

Cause programming ¯_(ツ)_/¯


Pre-filter stops working when you move to a next page

On this page (compose/ns/crm/pages/74992049056645144) we see all new leads. The pre-filter is set to: "Status = 'New' OR Status = 'Assigned'"

The first page shown is correct, but as soon as you move to the second page, the pre-filter is gone and all records are shown.

Commit: https://github.com/cortezaproject/corteza-webapp-compose/commit/ddb27ca28c1ba5b58420d97aaa9358b5aefdc6de


Move event hubs repo into this repo

The only new change is moving things into the packages/@azure/eventhubs folder

Need another change to disable auto publishing of the package

@AlexGhiondea  Service bus was moved under servicebus/data-plane. Should event hubs also be under "data-plane".

@ramya-rao-a when I moved Service Bus we had a different understanding of how the structure was going to look like -- the structure is now different. I wouldn't put it under the data-plane folder now.

Got it @AlexGhiondea

I made the change in the old PR but decided not to do it now as there is a guidance on the directory structure coming.


containerd tests are failing

The GitHub actions containerd tests are failing: https://github.com/kubernetes-sigs/cri-tools/actions/workflows/containerd.yml
It looks like sometimes they work, especially when retriggering a single test. Not exactly sure how to reproduce this, but it started to happen 2 days ago.

@mikebrow do you have some cycles to support us with that?


server : life-cycle-state type DEPRECATED in response header is as per ONF core-model : not filtered

The life-cycle state is an enumeration of values. In which "DEPRECATED" is a type.
Problem statement:
When the life-cycle-state is "DEPRECATED" for an operation-server or operation-client instance, the response header is producing the complete value present in load-file as "operation-server-interface-1-0:LIFE_CYCLE_STATE_TYPE_DEPRECATED". But it should be just "DEPRECATED".
Note: This filtering is working fine for other types of life-cycle-state.

Issue fixed in the pull request https://github.com/openBackhaul/ApplicationPattern/pull/277. Hence closing this issue.


refactored validators for config to allow the validator to change the value

this allows implementation of e.g. unit parsers in the validator. A
UnitValidator that makes use of this is also included
closes #280

Thanks for the review @graphaelli, great input as always!
I didn't really realize until now that renaming span_frames_min_duration_ms is backwards incompatible. That kinda sucks :/ We'll have to do a major version bump anyway for v2 and distributed tracing, but I hoped I could merge this before. Guess that's not going to happen then. I'll merge it into the v2-api branch.

Merged into #281, closing this one


[release-1.8] autoregister flag for workload entry command

This is an automated cherry-pick of #28449

@GregHanson @bianpengyuan – this is feature work but it helps simplify the docs for VMs associated with #27701

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
fbfc05082cc248a704c630fcb5fc64fd35e89765
link
/test unit-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
fbfc05082cc248a704c630fcb5fc64fd35e89765
link
/test unit-tests_istio_release-1.8

integ-pilot-k8s-tests_istio_release-1.8
fbfc05082cc248a704c630fcb5fc64fd35e89765
link
/test integ-pilot-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio_release-1.8
fbfc05082cc248a704c630fcb5fc64fd35e89765
link
/test integ-pilot-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Change email flow mixed up with membership flow

Problem
When a user changes their email address from the account page, this puts them into the same email verification flow that happens during new account creation.

They are redirected to a page that talks about verifying their account.
The link in the verification email takes them to a confirmation that says they have confirmed their account.
They get an email verified email that says the library team will confirm their membership within 72 hrs.
They get a welcome email that thanks them for applying for a membership and repeats the 72 hrs, plus asks them to bring in ID.

I don't think we can go live with this, it's potentially far too confusing for existing members who change their email address.
Suggestion
We should change the Auth0 email verification templates back to being just that - things that only mention verifying your email address, removing all mentions of library membership and not send the new member email.
We should treat new membership emails, including information about membership approval, as a separate problem that gets looked at as part of the membership work.

After some discussion in Slack: https://wellcome.slack.com/archives/CUA669WHH/p1635945645083300
Auth0's transactional emails have fixed behaviour:

a verification request email is sent after an account is created or its email address changes
a welcome email is sent after an email is verified

The result of this is that (a) verification emails are the same for existing and new users and (b) welcome emails are sent after a user changes their email address. This is the cause of the 'mixed up' flow.
As described in the Auth0 documentation (for verification emails and welcome emails), this behaviour can be changed by "outsourcing" the transactional emails to an external API, by storing state regarding whether emails have been sent in the user's metadata object, and then by using this state/API with business logic inside a rule that is triggered by verification events.
Implementing this would involve (at least) the following:

Writing a custom rule based on the above examples and managing its deployment and state through a combination of scripts and Terraform
Adding an endpoint to the identity API that would trigger the sending of a 'custom' welcome email.
Working out the permissions (probably a separate API key) for the API to be callable by the custom rule and not to be exposed to other API consumers.
Moving the welcome email templates (+ deployment) out of Auth0 into the existing templating framework of the identity API.

I think this is quite a lot of work, and quite a lot of disparate pieces to maintain - I'm strongly of the opinion that we shouldn't do this work right now, and instead we should look for copy changes we can make to cover the small minority of users who'll be affected by this. We may wish to return to this as we look to improve sign-up/onboarding journeys.

@cbowskill Did you mention this was ready to be worked on? Where can we find the updated email copy?

In discussions with Dom, my understanding is requesting won't change the current new member flow and therefore there shouldn't be anyone receiving a new auth0 version of new member email until we look at membership? (correct me if i'm wrong). Therefore we're happy to just have the same email for now which just covers confirmation of verifying your account (which is the verified email version that Dom has provided above)

Received a: 'Verify your email address' email, verified and then didn't receive a follow up email. Were we expecting to still see the follow up email just with the generic messaging? My understanding was this was sent by default (based on Jamie's comment) so i was expecting to see a secondary email once my new email address was verified.
With the email that was sent the wording is slightly different to what is specified in Dom's screens.
Dom's screens:

Confirm` your email address by clicking the button below. This link will expire in 24 hours

Email I received:

To activate your online account, please verify your email address below. This link will expire in 24 hours.

Related question - what happens if i don't activate my new email address within 24hrs? (I'll try it out)
@davidpmccormick - putting back into in progress

My understanding was this was sent by default (based on Jamie's comment) so i was expecting to see a secondary email once my new email address was verified

That's true, but that default is the result of the 'welcome' email being sent. I turned off sending of the welcome email altogether, so you wouldn't get a follow-up.
I think I might have misinterpreted that piece of the requirement then – do we still want to send a follow-up email, but have it be Dom's 'Email verified' screen above?
I think that would mean turning the 'welcome' email back on, but replacing its contents with the 'Email verified' screen, which will be ok for as long as we're not accepting new memberships.

I would say we leave it on and use it as a verification for email address changed for now, unless @DominiqueMarshall disagrees.

looks like the automation to move things to done if a PR says it closes an issue is a thing. I'll move this back to ready for review

Looks good!


Fix dataset in stable_diffusion_hybrid_quantization notebook

What does this PR do?
stable_diffusion_hybrid_quantization notebook started failing after the PR#638 was merged.
Fix:

Convert iterable dataset for quantization to list

Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Add mila sync code-extensions command, improve mila code extensions sync with DRAC clusters [MT-79]

preview:
https://github.com/mila-iqia/milatools/assets/13387299/1f56da91-faa8-42b1-a4c6-53553d68171d

Codecov Report
Attention: Patch coverage is 55.71429% with 186 lines in your changes are missing coverage. Please review.

Project coverage is 58.55%. Comparing base (7c733d1) to head (62419a2).

Files
Patch %
Lines

milatools/utils/vscode_utils.py
26.92%
133 Missing :warning:

milatools/utils/remote_v2.py
74.25%
26 Missing :warning:

milatools/cli/commands.py
42.30%
15 Missing :warning:

milatools/utils/parallel_progress.py
90.76%
6 Missing :warning:

milatools/cli/utils.py
80.00%
4 Missing :warning:

milatools/cli/remote.py
81.81%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #103      +/-   ##
==========================================
- Coverage   61.73%   58.55%   -3.18%
==========================================
  Files           9       12       +3
  Lines        1445     1759     +314
==========================================
+ Hits          892     1030     +138
- Misses        553      729     +176

Flag
Coverage Δ

integrationtests
?

unittests
58.55% <55.71%> (-3.18%)
:arrow_down:

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

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

For what it's worth, I'm not familiar with the code and I read the PR in diagonal to get a sense of what was in there. It looked alright in general. The main question that I would have is whether all the work for nice progress bars and whatnot will be obsolete when MFA kicks in? Can users log in manually once, perform the 2FA ritual, and then run this command without having to do it again?

For what it's worth, I'm not familiar with the code and I read the PR in diagonal to get a sense of what was in there. It looked alright in general. The main question that I would have is whether all the work for nice progress bars and whatnot will be obsolete when MFA kicks in? Can users log in manually once, perform the 2FA ritual, and then run this command without having to do it again?

Yes! The goal of this RemoteV2 is to use the ControlMaster directive of OpenSSH, so that the connection (and 2fa) is only performed once and a socket file is created. The connection is then reused.

@gyom Here's the flow with 2FA:
Notice how after the first interrupted run, there is no need to perform 2FA again:
https://github.com/mila-iqia/milatools/assets/13387299/662b6639-0b72-4de2-aeb3-6cf036dacd35


headless server with 2 factor auth?

How do I clone a repo on a headless Linux server?  I have no browser so I can't respond to the browser pop up that normally shows up.

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

ID: 6c2f260d-9321-d669-172d-01289c233263
Version Independent ID: 14e9ae18-df9d-7555-902c-3e8b4c2b2f22
Content: Connect to your Git repos using credential managers
Content Source: docs/repos/git/set-up-credential-managers.md
Product: devops
GitHub Login: @steved0x
Microsoft Alias: sdanie

Please accept our apology for the significant delay in addressing this issue.
It looks like you're working through an issue with the product itself, rather than an issue with the documentation. Here are a few options where you might consider asking your question:

Azure DevOps on Stack Overflow
Azure DevOps Support Bot


On porting all the plugins, tag as v1

Which makes it mandatory to get new plugins merged first, ofc I can work on branches ;)

First thing to get merged will be the ported plugisn

done :+1: https://github.com/coala/corobo/releases/tag/1.0


docs: improve migration from v2 guide

Description
I checked the commit log from 2.9.8 and added descriptions for breaking changes which was missing.
There are potentially breaking changes which I didn't include.

#5018

Transpile to ES5 is now necessary even if the user code only includes ES5. This is unlikely to happen.

#7877

/// <reference lib="dom" /> is removed from vite/client.d.ts. This only affects users who does not have either {"lib": ["dom"]} nor {"lib": ["webworker"]} in tsconfig.json.

#8139

exports field now exists. For example, it breaks if someone is importing vite/dist/node/cli.js directly which rarely happens.

#8280

server.force option was removed in favor of force option.

And some which only affects plugin/tool creators which I didn't include.

#5868

printHttpServerUrls is removed
server.app, server.transformWithEsbuild are removed
import.meta.hot.acceptDeps is removed

#7995

ssrLoadModule's fixStacktrace option's default is now false

#8178

formatPostcssSourceMap is now async
resolvePackageEntry, resolvePackageData are no longer available from CJS build (dynamic import is needed to use in CJS)

Also I didn't include breaking changes of plugins.

#5868

options.parserPlugins is removed

#8247

potentially: vite/legacy-polyfills in manifest is now vite/legacy-polyfills-legacy.
potentially: polyfills-modern.hash.js is now polyfills.hash.js.

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[x] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Thanks for the PR @sapphi-red 💚
About the ones you list in the description, I think it would be useful to have them in the migration guide in a new Advanced section. Maybe we could directly list the PR as you did here with a line each instead of a detailed explanation. And users can check the complete rationale and context in the PRs. What do you think?

I think it would be useful. I'll create another PR for that! 👍