Explicitly use utf-8 encoding for everything

Fixes #57
On Windows, open("r") and open("w") default to Windows-1252 encoding. It makes sense that we should explicitly always use UTF-8 instead.

nbconvert always writes text as UTF-8
Python 3 source files are supposed to always be UTF-8 (for when we register the post-save hook in the Jupyter config file)
JSON files are supposed to be UTF-8 (for nbautoexport.json config file)

We probably have gotten lucky before that this never caused any problems, probably because we're only using ASCII characters. For whatever reason, using nbconvert v6.0 broke HTML exports specifically—either they were mistakenly written in Windows-1252 before, or nbconvert v6.0 introduces a non-ASCII character to the template. Likely it was the latter, because nbconvert v6.0 changed the default HTML style to a new one based on Jupyter Lab.
Confirmed to pass tests for both nbconvert v5.6.1 and for nbconvert v6.0.

I'm definitely not an expert on encodings, but I'm curious if we lose anything by being explicit everywhere. Encodings seem like one of those places where edge-cases abound, so I'd prefer if we don't have to think about it explicitly.
For example, our config json is likely to be hand-edited. What if a user's text-editor happens to not encode it as UTF-8? Also, we store folder names in our json—not sure what the implications are on the character set for different operating systems in terms of what is allowed.
Does open do best guess right now and we lose that if we are explicit? Agreed things should be utf-8, just not sure that they always will be and if it actually matters to our code to enforce it everywhere.
I guess the questions is: is this fixing just the nbconvert issue? If so, I'd consider something more targeted to just a workaround there. If the other explicit encodings fixes other bugs that we didn't know we had, then we can decide if it is worth it.
Thoughts?

Does open do best guess right now and we lose that if we are explicit?

No, open's default is to get it from locale.getpreferredencoding , which fetches the default encoding from the user's system. This is UTF-8 for POSIX and CP-1252 on Windows normally, unless the user has changed it, or unless they are running Python in UTF-8 mode (using -X utf8 or setting the PYTHONUTF8 env var) which is new as of Python 3.7.

LGTM. I do wonder if there's a way to set the default behavior for opening files so we don't have to write this out every time, but I'm also fine with this implementation.

So AFAIK there isn't anything we can do to set any default behavior for open. I think this kind of makes sense, because we wouldn't want to change open's behavior outside of cloudpathlib. Only a user can change their default, as described above.

is this fixing just the nbconvert issue? If so, I'd consider something more targeted to just a workaround there. If the other explicit encodings fixes other bugs that we didn't know we had, then we can decide if it is worth it.

So there are three places where we read/write files:
1. Notebook exports
nbconvert AFAICT normally writes out UTF-8, so we should set UTF-8 here to be consistent with them. This is the nbconvert bug we ran into.
2. jupyter_notebook_config.py for post-save hook
This is a Python source file. Python 3 defaults to UTF-8 for source files everywhere, so I think we should explicitly use UTF-8 here. I would consider this a "bug we didn't know we had".
In theory, users can explicitly declare their source file encoding at the top of their source file per PEP 263, so the ultimate solution would be to check for a PEP-263-spec declaration. This is an edge case that I'd be very surprised to run into though.
3. .nbautoexport config file
I think this one is less clear, as pointed out. Details about specific considerations below. Given the details, I'm still leaning that we should go with UTF-8 here.

not sure what the implications are on the character set for different operating systems in terms of what is allowed.

Windows actually has a default file-system encoding of UTF-16LE. From this perspective, it actually would make more sense for us to have our config be UTF-8. Since CP-1252 only has a subset of unicode characters available, a CP-1252 file wouldn't be able to represent all possible characters that filenames might use. This actually appears to be the motivation for PEP 529 which in Python 3.6 changed the byte representation of Windows file paths to use UTF-8.

For example, our config json is likely to be hand-edited. What if a user's text-editor happens to not encode it as UTF-8?

Apparently, many text editors on Windows default to UTF-8 already. This includes Atom, VS Code, and even Notepad in Windows 10 as of May 2019.
Not sure about PyCharm or Notepad++. These may still be CP-1252.
(Aside: a long and somewhat interesting thread discussing proposed PEP 597 for setting UTF-8 as default text encoding for everything. )

Well, I definitely learned a ton. Thanks for doing all that research @jayqi


Typo in repository URL / pypi homepage

https://github.com/hpeyerl/venstar_colortouch/blob/175042b091b814c8e118780c032f1e9ebbc2426c/src/venstarcolortouch/__init__.py#L5
is missing the underscore. This makes the homepage link on https://pypi.org/project/venstarcolortouch/ wrong.

Thanks.  Fixed in 0.14.


Making SpriteComponent and SpriteAnimationComponent follow the same standard for empty constructors

Description
SpriteComponent and SpriteAnimationComponent had a similar behavior on allowing an empty initialization, which is very useful because allows the component to load itself using it's onLoad method. But they had the constructors using different patterns. This PR simple makes both component follow a similar pattern so it will be easier for the user to use.
After this proposal is accepted I intend on doing a similar thing on all of our components that requires assets, like Parallax, SpriteBatch, etc.
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:
If something is unclear, please submit the PR anyways and ask about what you thought was unclear.

[x] This branch is based on the latest master
[x] I have added an entry under [next] in CHANGELOG.md
[x] I have formatted my code with flutter format
[ ] I have made corresponding changes to the documentation
[ ] I have added examples for new features in doc/examples
[x] The continuous integration (CI) is passing

Looks good! Maybe the Sprite argument should be before the size?

I have a vague remembering that @luanpotter asked for the size to first on a previous refactor, but I am not 100% sure, do you remember anything Luan? Otherwise I can change the order

Looks good! Maybe the Sprite argument should be before the size?

I have a vague remembering that @luanpotter asked for the size to first on a previous refactor, but I am not 100% sure, do you remember anything Luan? Otherwise I can change the order

Looks good! Maybe the Sprite argument should be before the size?

I have a vague remembering that @luanpotter asked for the size to first on a previous refactor, but I am not 100% sure, do you remember anything Luan? Otherwise I can change the order

Gonna merge this PR so I can start working on the other components, @luanpotter if you remember anything about about that let me know and I can do a follow up.

Looks good! Maybe the Sprite argument should be before the size?

I have a vague remembering that @luanpotter asked for the size to first on a previous refactor, but I am not 100% sure, do you remember anything Luan? Otherwise I can change the order

Gonna merge this PR so I can start working on the other components, @luanpotter if you remember anything about about that let me know and I can do a follow up.


Decide on CaseOp/IfOp/WhileOp taking/producing tuples

Given that custom_call can produce tuples, I think that control flow ops should be able to do that as well, unless I'm missing something.

The same argument applies to OptimizationBarrierOp.


Add components llvm-tools-preview and rustc-dev

Resolves #2088
r? @jyn514

May I ask, how often is doc.rs the website updated from the GH source code?
Put another way, after when will I be able to tell whether this actually resolved #2088?

👍 Thank you very much for your help, @jyn514.

:tada: https://docs.rs/dylint_linting/2.1.8/dylint_linting/
Thanks again, @jyn514!


Delete tag API

Resolves #12913
Allows deletion of tags via API, but only if they are not attached to a release. If a release is attached, the user will have to call the API to delete the release, then call this API.
I considered allowing a query parameter or request body with the delete release API, however from my cursory searches it seems as though both would be undefined behavior with the DELETE method, so instead I opted for this approach.
cc @6543

    release_test.go:59:
        	Error Trace:	release_test.go:59
        	            				release_test.go:86
        	Error:      	Not equal:
        	            	expected: 2
        	            	actual  : 3
        	Test:       	TestCreateRelease

    release_test.go:59:
        	Error Trace:	release_test.go:59
        	            				release_test.go:95
        	Error:      	Not equal:
        	            	expected: 2
        	            	actual  : 3
        	Test:       	TestCreateReleasePreRelease

    release_test.go:59:
        	Error Trace:	release_test.go:59
        	            				release_test.go:104
        	Error:      	Not equal:
        	            	expected: 2
        	            	actual  : 3
        	Test:       	TestCreateReleaseDraft

Hah, that's what I get for running only specific #Tests locally.

Codecov Report

Merging #13358 into master will increase coverage by 0.02%.
The diff coverage is 55.55%.

@@            Coverage Diff             @@
##           master   #13358      +/-   ##
==========================================
+ Coverage   42.10%   42.12%   +0.02%
==========================================
  Files         689      689
  Lines       75862    75879      +17
==========================================
+ Hits        31943    31967      +24
+ Misses      38683    38667      -16
- Partials     5236     5245       +9

Impacted Files
Coverage Δ

modules/context/api.go
75.22% <ø> (ø)

routers/api/v1/repo/release_tags.go
53.57% <46.66%> (-7.97%)
:arrow_down:

routers/api/v1/api.go
79.50% <100.00%> (+0.05%)
:arrow_up:

services/pull/temp_repo.go
26.59% <0.00%> (-3.20%)
:arrow_down:

services/pull/check.go
48.90% <0.00%> (-2.92%)
:arrow_down:

services/pull/patch.go
53.97% <0.00%> (-1.71%)
:arrow_down:

modules/notification/webhook/webhook.go
49.65% <0.00%> (+0.34%)
:arrow_up:

services/pull/pull.go
41.27% <0.00%> (+0.49%)
:arrow_up:

modules/log/event.go
59.90% <0.00%> (+0.94%)
:arrow_up:

models/release.go
54.03% <0.00%> (+1.86%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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

Did this make it into v1.13.0? Merge date lets me think so, but milestone says otherwise..

You should compare merge date with v1.13.0-rc1 but not v1.13.0


[NUCLEO_F072RB/F091RC] adding target to rtos lib and exporter for coide and gcc_arm

[Nucleo_F072RB]
Every test (DTCT_1, EXAMPLE_1, MBED_xx, RTOS_x) is OK.

Can you ,please rebase also this PR to the latest master?

When it would be OK I'll wait with the rebase because after merging #818 there will be a new conflict.

Yes.
I usually resolve conflicts manually, but with all STM targets at the moment, it's becomes tricky in some cases. Thanks for your assistance.

818 was merged , so we can proceed with this one

I rebased it.

Thanks!


test_buttons should be renamed rc_test_buttons

Missed one:  https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/examples/rc_test_buttons/Makefile#L3

patched locally, so i can get a new image out tonight:
https://github.com/rcn-ee/repos/commit/ee84f31717940d1220f92a9efd66b309cd7de633


Fix IJwB UE integration test on prefetched extensions

See test failure in #1292
https://storage.googleapis.com/bazel-untrusted-buildkite-artifacts/074be68b-756b-4778-8be2-03e9c8a43f06/ijwb/integration_tests/attempt_1.log
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
Executing tests from //ijwb:integration_tests
-----------------------------------------------------------------------------
JUnit4 Test Runner
.log4j:WARN No appenders could be found for logger (#com.intellij.application.impl.ApplicationImpl).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Oct 18, 2019 6:57:56 PM java.util.prefs.FileSystemPreferences$1 run
INFO: Created user preferences directory.
.E
Time: 6.556
There was 1 failure:
1) testPrefetchedExtensions(com.google.idea.blaze.ijwb.prefetch.IntelliJBazelPrefetchFileSourceTest)
unexpected (6): js, html, css, gss, ts, tsx
---
expected      : [java, proto, dart]
but was       : [proto, dart, js, html, css, gss, ts, tsx, java]
	at com.google.idea.blaze.ijwb.prefetch.IntelliJBazelPrefetchFileSourceTest.testPrefetchedExtensions(IntelliJBazelPrefetchFileSourceTest.java:33)

FAILURES!!!
Tests run: 2,  Failures: 1

BazelTestRunner exiting with a return value of 1
JVM shutdown hooks (if any) will run now.
The JVM will exit once they complete.

-- JVM shutdown starting at 2019-10-18 18:57:58 --

Closing since https://github.com/bazelbuild/intellij/pull/1292 is closed as intellij-ue has a separate CI tests file now https://github.com/bazelbuild/intellij/commits/master/.bazelci/intellij-ue.yml


Switch from kindnetd to calico in local setup

How to categorize this PR?

/area dev-productivity security
/kind enhancement
What this PR does / why we need it:
With #5666 we had to disable the e2e CA rotation test because the local setup did not support rolling updates of worker nodes. Motivated by this, we are now switching to calico for both seed (kind) and shoot clusters. This enables NetworkPolicys (which was another limitation of the local setup) and allows us to re-enable the e2e CA rotation test.
⚠ Unfortunately, it introduces a new limitation (while eliminating two others) which is that the pod subnet for shoot clusters does not yet fully work. I.e., pods on different nodes cannot communicate with each other. @ScheererJ and @DockToFuture offered to take a look and help improving this. For now, this is still good enough as it unblocks us and even improves test accuracy by supporting the NetworkPolicys.
Which issue(s) this PR fixes:
Part of #3292
Special notes for your reviewer:
/cc @timebertt @ScheererJ @DockToFuture
Release note:

The local Gardener development setup now uses `calico` instead of `kindnetd` as CNI plugin for the seed and shoot clusters. This enables support for `NetworkPolicy`s and rolling updates of shoot worker nodes.

/cla

/retest


Milestone 3 Feedback

Congratulations on finishing milestone 3! We can see you put a lot of work into this project, nice work!
Below we list some specific feedback you can use to improve your project.
We provide tick boxes for you to use in the future as you address these concerns to improve the final grade of your project.
If anything is unclear, please feel free to ask questions in this issue thread.

R package
1. Write test cases and code iteratively
rubric={accuracy:20,quality:10,mechanics:10}
Well done!
Comments: Zero fails!
Python package checklist
1. GitHub actions workflow for continuous integration
rubric={mechanics:10}
Well done!
2. GitHub actions workflow for continuous deployment
rubric={mechanics:10}
Well done!
3. Documentation
rubric={reasoning:10}

[ ] There is no link on GitHub or in the README.md to ReadTheDocs - -2 reasoning

4. Specific expectations for this milestone
rubric={mechanics:10}

[ ] There are not issues in the project board added during this milestone. - mechanics -2

[ ] There isn't a milestone called milestone3. - mechanics -2

5. Submission instructions
rubric={mechanics:10}
Well done!

Thank you @negsadr for such a prompt review!
We did include a link to the readthedocs in our about section.

@dhruvinishar thanks for your message!
I modified the grading accordingly!


Add hint about sdkconfig.ci in IDF examples (IDFGH-5657)

Individual developers may not know about CI and may be confused by the sdkconfig.ci files in the examples.

Thanks for your contribution.

Thanks for your contribution, and sorry for late reply, we have put the changes into our internal review queue, and the PR will be updated once the changes are available on GitHub. Thanks.


add effects in the navigation bar and front page picture

I think there should be some changes in the top picture of the webpage and the about,team and support us rows. It would look much better is they are visible to the viewers and are systematically arrange.
Please sign me this task.

I think there should be some changes in the top picture of the webpage and the about,team and support us rows. It would look much better is they are visible to the viewers and are systematically arrange.
Please sign me this task.

Could you attach a screenshot with a rough sketch of your suggested changes or elaborate more or perhaps raise a PR so that we can review this more effectively and give feedback

okay sure! I will raise a PR .

I'm the Participant of GSSOC'21. Please assign me this issue.I would love to work on this.

I think there should be some changes in the top picture of the webpage and the about,team and support us rows. It would look much better is they are visible to the viewers and are systematically arrange.
Please sign me this task.

2 more days for this. After that @rk05-lenavo can take over

I think there should be some changes in the top picture of the webpage and the about,team and support us rows. It would look much better is they are visible to the viewers and are systematically arrange.
Please sign me this task.

Could you attach a screenshot with a rough sketch of your suggested changes or elaborate more or perhaps raise a PR so that we can review this more effectively and give feedback

Can I add a logo of DOC2PEN with different style? You can use it for the new webpage if you like.

This is the basic idea that I have in my mind. There are some things that I want to change (if you allow):-

The logo of doc2pen is very simple...we can something creative.
All the dropdowns will be visible on hover in the navigation bar.
The pic "type documents in your handwriting", the handwriting part is not so visible, so we can add something catchy caption.

I had almost made this section of the page, but if you want me to add or change something I will do it.
Please give your feedback about this idea @smaranjitghose !

@Smriti129 as far as the Nav Bar is concerned, I would like to keep it unchanged at least for the first phase of the program (It took a lot of time to reach there😅)
As far as the Home Page (To be specific the About Section) goes, yes we do need a revamp
Initially the project started out as my pet project to convert text into handwritten assignments. Hence the current descriptions are similar to that.
However, we now evolving with other features like Sketch, MediaManip, etc. So we do need to revamp the pitch.
(ofcourse the corresponding illustrations too)

If you have decent content writing skills, you can improve the readme and contributing guidelines as well

Okay, I understand that.
But I am a little bit concern about the About, Team and Support section, because they look like "odd ones out". So if you want to revamp that section where do you want to display it, if not in the navigation bar?
@smaranjitghose

If you have decent content writing skills, you can improve the readme and contributing guidelines as well

Yes, sure I can do that. Please do tell if you want any particular type of changes in this.

Okay, I understand that.
But I am a little bit concern about the About, Team and Support section, because they look like "odd ones out". So if you want to revamp that section where do you want to display it, if not in the navigation bar?
@smaranjitghose

if you want to go ahead with revamping it we can add an option of dropdown for the home page and there you do internal navigation. We don't want multiple pages as that confuses user to find the tab for the editor(which is the main purpose).

Okay.


Retemplate with new sunpy template - [merged]

In GitLab by @Cadair on Apr 2, 2020, 08:56
Merges retemplate -> master
Closes #47

In GitLab by @Cadair on Apr 2, 2020, 08:57
What I haven't done here is update the CI at all, or made the codestyle thing pass, I will push a new commit for that.

In GitLab by @Cadair on Apr 2, 2020, 09:41
added 1 commit
b83fcbd6 - make ci use tox
Compare with previous version

In GitLab by @Cadair on Apr 2, 2020, 08:59
added 1 commit
23bfa4d1 - Run the pre-commit on the whole repo
Compare with previous version

In GitLab by @Cadair on Apr 2, 2020, 09:44
added 1 commit
00fda891 - make ci use tox
Compare with previous version

In GitLab by @Cadair on Apr 2, 2020, 09:47
added 1 commit
bbc23ed4 - make ci use tox
Compare with previous version

In GitLab by @Cadair on Apr 2, 2020, 10:35
added 1 commit
8d1be392 - more doc reference fixes
Compare with previous version

In GitLab by @Cadair on Apr 2, 2020, 09:58
added 2 commits
1afcb257 - make ci use toxe2484ac3 - more remote data?
Compare with previous version

In GitLab by @Cadair on Apr 2, 2020, 10:13
added 1 commit
69b8ced4 - Mark all channel tests as online
Compare with previous version

In GitLab by @Cadair on Apr 2, 2020, 10:22
added 1 commit
33e16cb5 - pyyaml
Compare with previous version

In GitLab by @wtbarnes on Apr 2, 2020, 11:26
approved this merge request

In GitLab by @wtbarnes on Apr 2, 2020, 11:27
mentioned in commit 7535c7b184f887469b7fe6a7ce3a5422795b38c6

In GitLab by @wtbarnes on Apr 2, 2020, 11:27
merged


Separated workflow runs

This PR just separated Test workflow from Build

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.75%. Comparing base (b75d8fd) to head (cf3d221).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   89.75%   89.75%
=======================================
  Files          61       61
  Lines        3026     3026
  Branches      482      482
=======================================
  Hits         2716     2716
  Misses        222      222
  Partials       88       88

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


Fix typos and remove spelling suggestions in Gardener blog

Typo fixes

Email address
Footnote reference was rendered as link

Architecture picture fixes

Removed spelling correction suggestions (red underlines)

/assign @kbarnard10

/approve


Document CNI plugin range/routes support.

Description

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Semaphore failure is the bird certificates thingy


feat: port RingTheory.IntegralClosure

I tried to fix what I could, but this contains a lot of sorries!

@Ruben-VandeVelde I hope that you are not annoyed by the push-pull dance!  Anyway, I've been concentrating more on the later part of the file, once I saw that you were also working here.  Good luck to both!

No worries - I'll push a few more changes once the cache is available

bors merge


Component Delete and Owner Reference

Signed-off-by: Maysun J Faisal<EMAIL_ADDRESS>This PR adds the Component Delete logic whereby the gitops repository is updated and the component dir is removed & the parent kustomize file is updated.
If the git source is specified, the devfile project is removed, if the Component source is an image, the devfile attribute is updated
Component Owner Reference is also added. So when an Application is deleted, the control plane also removed the Component after removing the Component finalizer.

/retest

/retest

/retest

/retest


feat: adjust log level for easier debugging

Codecov Report

Merging #74 (8705eac) into master (bb4e9a9) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #74      +/-   ##
==========================================
- Coverage   88.54%   88.48%   -0.07%
==========================================
  Files          21       21
  Lines         524      521       -3
  Branches       85       85
==========================================
- Hits          464      461       -3
  Misses         60       60

Flag
Coverage Δ

unittests
88.48% <100.00%> (-0.07%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/command/post-manager/consumer-screenshot.ts
100.00% <100.00%> (ø)

src/command/post-manager/producer.ts
100.00% <100.00%> (ø)

src/services/notification/mail-service.ts
100.00% <100.00%> (ø)

src/services/rss/snowball/service.ts
100.00% <100.00%> (ø)

src/services/slack-service.ts
100.00% <100.00%> (ø)

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 bb4e9a9...8705eac. Read the comment docs.


How to include multiple jobs (promotion) from the same company?

I could not figure out how to show multiple jobs (maybe promotion) from the same company? I think Linkedin has a neat structure for this purpose. Is there any opinion for this?

The way I would do it by just having those several jobs even if the company/location is the same.

Yes, it's a solution. But I'm trying not to exceed 1 page, therefore looking for a more compact form such as:
Company Name                                 Location
Position 1                                           Date for Position 1
Details for Position 1
Position 2                                           Date for Position 2
Details for Position 2
I am playing with the code for this purpose. If I succeed, I will share.

Ah, I see! That would be nice indeed.

Hi I would also really appreciate this addition if anyone knows how to do it?

I guess the following command works for this purpose:

\newcommand*{\cventrytwopositions}[8]{%
  \vspace{-2.0mm}
  \setlength\tabcolsep{0pt}
  \setlength{\extrarowheight}{0pt}
  \begin{tabular*}{\textwidth}{@{\extracolsep{\fill}} L{\textwidth - 4.5cm} R{4.5cm}}
      \entrytitlestyle{#2} & \entrylocationstyle{#3} \\
      \entrypositionstyle{#6} & \entrydatestyle{#7} \\
      \multicolumn{2}{L{\textwidth}}{\descriptionstyle{#8}} \\
      \entrypositionstyle{#1} & \entrydatestyle{#4} \\
      \multicolumn{2}{L{\textwidth}}{\descriptionstyle{#5}}
  \end{tabular*}%
}

After adding this new command definition to awesome-cv.cls file, you can create an instance of it, for example in the experience.tex file. Here is the order of the fields:
\cventrytwopositions
    {Position1}
    {Company}
    {Location}
    {Date for position 1}
    {
      Details for position 1
    }
    {Position2}
    {Date for position 2}
    {
      Details for position 2
    }

Of course, order of the arguments could be altered. Let me know if this works or not, so that we can improve.

Not the best solution, but I fixed simply by adding two cventries without writing the organization and location of the oldest one.
Something like
`  \cventry
{Job title after promotion}
{Corporation}
{Location}
{August 2019 - now}
{
\begin{cvitems}
\item {Responsibilities}
\end{cvitems}
}
\cventry
{Job title before your promotion} % Job title
{} % Organization EMPTY
{} % Location EMPTY
{somewhere in the past - a while ago} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Old responsibilities}
\end{cvitems}
}`

I do the same as @mircoparello, but I defined a new command cvsubentry for this purpose:
% Sub-job entry - assumes the organization and place are specified in a preceding cventry
% Usage: \cvsubentry{<position>}{<date>}{<description>}
\newcommand*{\cvsubentry}[3]{\cventry{}{}{#1}{#2}{#3}}

I tried using @posquit0's cvsubentry thing as he used in https://github.com/posquit0/Awesome-CV/blob/master/examples/cv/experience.tex but XeLaTeX doesn't like that ("! Extra alignment tab has been changed to \cr.  \endtemplate").
So for now, I'm doing the same as @mircoparello which looks good enough.

This works if you are promoted in the same location, what if I was promoted in the same company but to a different work location?

@adnan-azmat This is how I solve it in my own CV:
% as \cventry, but squashed up to meet more recent role above; no company/location.
\newcommand{\cventryprevrole}[3]{
  \vspace{-3.0mm}
  \setlength\tabcolsep{0pt}
  \setlength{\extrarowheight}{0pt}
  \begin{tabular*}{\textwidth}{@{\extracolsep{\fill}} L{4.5cm} L{\textwidth - 4.5cm}}
    \entrydatestyle{#2} & \entrypositionstyle{#1} \\
    & \descriptionstyle{#3}
  \end{tabular*}
}

https://github.com/OJFord/curriculum-vitae/blob/0989831fb4810d1520bee67cbd93553458efafd5/cv.cls#L82-L91
This could easily be adapted to include (I deliberately removed it for my use) location. For comparison, here's \cventry:
https://github.com/posquit0/Awesome-CV/blob/db809982227ba6f24f2d0ec1c4f3893e99db2f41/awesome-cv.cls#L657-L670
I've been meaning to read through others' suggestions & implementations here and elsewhere before coming up with something to include in Awesome-CV itself to address this.


Delegate

https://kusama.subscan.io/extrinsic/17149409-6

Thank you for your request!
@paulormart
You can check how it will look like:

App screens


Laggy Animation

Hi, I have tried using this cool css lib on my asp.net MVC5 web page.
The animations does not seem smooth, as in very laggy so it doesnt have a "shake" effect at all it just seem odd, but on your example page it works perfect with the same browser.
So I am wondering what might be the cause for this laggy animation (not smooth) ?

Hi @furier ,
Could you make a pen or show code in some way?

I have only had this problem on my setup with asp.net mvc5 on windows server 2008 R2 virtual machine with remote desktop. I changed to using anijs instead, and using the rubberband animation instead, so now im unable to make a video to show you.

ok @furier feel free to comment to reopen this Issue in case you need.


Older conda versions install padloc v1.1.0 rather than padloc v2.0.0

For some reason, older versions of conda (possibly related to use of the older pycosat dependency solver) install padloc v1.1.0 rather than padloc v2.0.0 by default.

[!IMPORTANT]
To avoid this issue, you can specify padloc v2.0.0 during installation (this should work regardless of conda version)
create -n padloc -c conda-forge -c bioconda -c padlocbio padloc=2.0.0

[!NOTE]
To avoid future issues, you may also wish to:

Make sure your conda installation is up-to-date

conda install -n base -c defaults 'conda>=23.9.0'

Make sure the new libmamba solver is available and active

conda install -n base conda-libmamba-solver --solver=classic
conda config --set solver libmamba

Trying to install Padloc but the padloc database update command is not working


Respect non-enumerable properties

When creating a property like this:
Reflect.defineProperty(obj, 'foo', {
  configurable: true,
  enumerable: false, // <-- non-enumerable
  set: setter,
  get: getter
});

the property observer will add its own setter and getter (which is a good thing), but also sets the enumerable setting to true.
This PR makes the observer respect the existing setting.

@jdanyow Please review.

If we can get this in today, we can get the fix out tomorrow. Let me know.

I've updated the PR!

@jdanyow Can you do a final review?

looks good, merged. thanks @gingerik!


Home directory is gone after reboot

After rebooting the host system and running archboxinit, the home directory that was mounted from my host system is gone.

Okay, i fixed it. Running archboxinit as root and with the argument "start" will fix the issue. I would suggest to explain the archboxinit start and archboxinit stop commands in the readme, and mention that archboxinit needs to be run as root, since the mount command only runs with superuser privileges.
Here is my systemd service for those who want archboxinit to run at boot:
[Unit]
Description=Archbox init
PartOf=multi-user.target

[Service]
ExecStart=/usr/local/share/archbox/bin/archboxinit start
Type=oneshot
User=root

[Install]
WantedBy=multi-user.target

Ah yeah, i forgot to update readme when implementing this,


Feature: Ability to launch chrome with runtimeArgs

I need to launch chrome with command line flags (in particular --js-flags). Currently there is no way to add those.
It might be worth considering adding support for some other launch request options provided by vscode-chrome-debug such as userDataDir.

I second that, would have to add --allow-file-access-from-files. Still opening a new issue because - shouldn't that be a default for this extension?


update various language usage in docs

Just a lot of miscellaneous english usage and grammer errors.
Hopefully, I don't offend anyone.

No offense taken, those are great changes, thank you!


Handle newlines in filenames

find can be instructed to print matching files separated by null bytes rather than newlines via the -print0 action. read can be made to expect such delimiters with an empty -d flag. By their powers combined, bomr now handles filenames which contain newlines (and other mischievous characters).

Awesome, I was stuck on this before for a while. Thanks for contributing!


Error R14 (Memory quota exceeded)

Hello
I'm not sure if this is a problem in the free heroku dyno but I tried to use the wkhtmltopdf-buildpack and I didn't get success. This is my heroku logs:
	2015-07-31T02:06:52.005696+00:00 app[web.1]: Started GET "/orders/1.pdf" for <IP_ADDRESS> at 2015-07-31 02:06:52 +0000
	2015-07-31T02:06:52.162915+00:00 app[web.1]:   Rendered clients/_client.html.erb (85.3ms)
	2015-07-31T02:06:52.015043+00:00 app[web.1]: Processing by OrdersController#show as PDF
	2015-07-31T02:06:52.015049+00:00 app[web.1]:   Parameters: {"id"=>"1"}
	2015-07-31T02:06:52.071357+00:00 app[web.1]: ***************WICKED***************
	2015-07-31T02:06:52.309300+00:00 app[web.1]:   Rendered orders/_order_products.html.erb (145.6ms)
	2015-07-31T02:06:52.339531+00:00 app[web.1]:   Rendered orders/show.html.erb (267.2ms)
	2015-07-31T02:06:52.339015+00:00 app[web.1]:   Rendered orders/_order.html.erb (262.6ms)
	2015-07-31T02:07:12.162183+00:00 heroku[web.1]: Process running mem=662M(129.4%)
	2015-07-31T02:07:12.162183+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
	2015-07-31T02:07:22.005012+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/orders/1.pdf" host=mvbteste.herokuapp.com request_id=50f6840e-1907-4730-ab0d-1a6f415eb3db fwd="200.*.*.*" dyno=web.1 connect=3ms service=30001ms status=503 bytes=0

I'm not sure about how to debug this issue, but could you help? Is adding dynos an option in this case? Thanks

Using dynos with more memory would probably help alleviate your issue, but not all of the time. If you are generating PDFs of unbounded size any individual request could allocate all of the memory in the dyno.
I'd recommend generating all documents with a background worker, hosting the file elsewhere (S3, etc), and then sending a URL for the PDF rather than the file itself.


Add support for mobile surfaces in the Optimize SDK

Ref: [MOB-18127]

Provided new public APIs that support mobile surfaces

static func updatePropositionsForSurfacePaths(for surfacePaths: [String], withXdm xdm: [String: Any]?, andData data: [String: Any]? = nil)
static func getPropositionsForSurfacePaths(for surfacePaths: [String], _ completion: @escaping ([String: Proposition]?, Error?) -> Void)
static func setPropositionsHandler(_ completion: @escaping ([String: Proposition]) -> Void)

Deprecated the following APIs that use DecisionScope

static func updatePropositions(for decisionScopes: [DecisionScope], withXdm xdm: [String: Any]?, andData data: [String: Any]? = nil)
static func getPropositions(for decisionScopes: [DecisionScope], _ completion: @escaping ([DecisionScope: Proposition]?, Error?) -> Void)
static func onPropositionsUpdate(perform action: @escaping ([DecisionScope: Proposition]) -> Void)

Aligned Event data format with Android for Optimize response and notification events
Added unit, functional and integration tests

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@spoorthipujariadobe Thanks for your review. I've pushed the feedback updates to the pr.


METAR

Add version bounds to dependencies.
Turn on GHC warnings
The parser uses hackage/parsers library, so a user can choose the parser implementation e.g. attoparsec, parsec.
A METAR optionally ends in $ or = instead of necessarily.
Added a field to Weather for ending in $ (meaning the station requires maintenance).
Added classy lenses to the data types.
Updated the new noaa.gov METAR publication website for fetching.
Moved parseWeather over to the Fetcher module so the parser does not ever import attoparsec.
Make Station a newtype.

Awesome, thanks!


Add NEVM

Let me know if anything else is needed and if you have questions about the project.
Image is formatted according to your convention.

added manually as we undertook some code change

Announced here @bstr156
https://twitter.com/joelkite/status/1470487648502485005


Update Target SDK for Android

Due date Aug 31. https://developer.android.com/google/play/requirements/target-sdk

@tkiyohar  updates?

@a6wu No news to report as of now. Will be investigating issue and touching base with Maxim in the coming days.

Work on this issue is currently blocked pending the following:

[ ] Charles investigating ad permissions with new firebase version
[ ] New app builds are failing on code magic due to unrelated issue (see issue 2056)


Put Trident/7.0; in our browser's user-agent

TGUI, which is in many modern codebases, looks for the regex Trident\/(\d+).+?; in the browser's user-agent and refuses to work properly if it's not there. We should add it to ours to get it working.
From what I can tell this will require a change to RobustToolbox's WebView.

We'll likely end up copying a version of IE's user-agent entirely. Here's the one I get in BYOND:
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.2; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; Tablet PC 2.0; Zoom 3.6.0)

WCvars.UserAgentOverride now exists but we're blocked by https://github.com/space-wizards/RobustToolbox/issues/3703

The blocker is fixed in the latest version of RT, we just need to update.

RT is now updated


Generalise Tabs

At the moment, tabs are arranged in a one dimensional layout. There is no need to do so though. In principle, a tab could also be rendered as a small "badge" or whatever. I propose to add an option to Tabs that allows 2-dimensional layouts. Using grid instead of flex will also make it easier to hack into styles from the outside.

The current default is sensible I believe. If someone wants a different layout, they can simply override styles


Problem with Tensorflow version

Hi, I am trying to install and run your project and I have problems with the version of the TensorFlow. Any suggestions?

Hi,
I tested the code in the following tensorflow version:
tensorflow-gpu==1.2.0
tensorflow==1.2.0
It is an old project. So it is a relatively old tensorflow version.
best,
Yingxue


compiler/python_generator: fix inconsistent behavior when proto file …

fix https://github.com/grpc/grpc/issues/10790
bug poc repo https://github.com/biolee/grpc-python-bug-poc

Seems obsolete, closing.


Issue with transformer guide

URL(s) with the issue:
https://www.tensorflow.org/alpha/tutorials/text/transformer
Description of issue (what needs changing):
format and normalization layer.
Clear description

when describe the multi-head attention, there is this text in one line:  "Multi-head attention consists of four parts: * Linear layers and split into heads. * Scaled dot-product attention. * Concatenation of heads. * Final linear layer. "
I guess the * mean bullet items. It is not formatted correctly.
The EncoderLayer and DecoderLayer use LayerNormalization. There is no LayerNormalization in keras.layers. There is only BatchNormalization.
Evaluate step creates mask. No mask is needed since a) there is no padding for a single sentence. b) there is no look_ahead since we are trying to predict next words.

@jasonzhang2022 Thanks for finding this. First one  was already updated in master branch here and it will be correctly rendered when the update are pushed to website. We will take a look at the rest of the two issues. Thanks!

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

@jasonzhang2022 Regarding item(2), There is LayerNormalization here. There is a difference between LayerNormalization and BatchNormalization.
Regarding item(3), there is a look_ahead and the functionality was described in the tutorial
The look-ahead mask is used to mask the future tokens in a sequence. In other words, the mask indicates which entries should not be used.

This means that to predict the third word, only the first and second word will be used. Similarly to predict the fourth word, only the first, second and the third word will be used and so on.

I think this is not an issue. I am closing this, but please let me know if I'm mistaken. Thanks!


resource identifiers and resource linkage

define structure for resource identifiers and resource linkage, and specify relationship data as resource linkage.

@ngseer refs: https://github.com/DeanWay/pydantic-jsonapi/pull/3#pullrequestreview-296359513

definition and terminology taken from: https://jsonapi.org/format/#document-resource-object-linkage


Add a missing LICENSE file

There was an error with the build of #778:
License file given in about/license_file (/repo/recipes-tag/analysis/LICENSE) does not exist in source root dir or in recipe root dir (with meta.yaml)
ERROR:build.py:License file given in about/license_file (/repo/recipes-tag/analysis/LICENSE) does not exist in source root dir or in recipe root dir (with meta.yaml)

Let's try to fix it by adding the missing file.

Thanks @tacaswell, the package was successfully built!


Fix build script for windows-gnu

The pc-windows-gnu targets don't have these Debug/Release sub-directories.

:+1:


pyo3-arrow: return Bound<PyAny> over PyObject

Should make it easier for downstream libraries as the Python object is still bound to a py token.

Closed by #269


Add FailureReason to IntrospectionRequestValidationResult

I'd like to use the FailureReason in IntrospectionRequestValidationResult as in the previous version - I don't see a property for it, but the IntrospectionRequestValidationFailureReason enum still exists.

please elaborate

In 1.5.2 version, the IntrospectionRequestValidationResult class had a property:
public IntrospectionRequestValidationFailureReason FailureReason { get; set; }
Which is set by IntrospectionRequestValidator ValidateAsync method when there were errors, like missing token, invalid token, etc.
Currently, in 2.0.5, there is no more FailureReason property in the mentioned response class. As I see, the result contains error message in one case, when the token is missing: "missing_token". In other cases there is no error message and no reason of the error.
Currently, the IntrospectionRequestValidationResult.cs contains an enumeration called IntrospectionRequestValidationFailureReason, which was the type of FailureReason property in 1.5.2.

and how do you want to use that?

OK - I am still missing the big picture. Care to explain?

@gaborari -- did you do a PR for this?


Get annoying error warrning In vscode

Sorry to interrupt. I'm new to unity, so it's possible that this problem isn't caused by this tool, but still want some help.
I imported this tool into my project, and then vscode says, it can't find the namespace. But I had no trouble compiling and running the code. How do I let vscode know that the project includes this package or namespace.
Thanks in advance.

Well, I reloaded the sdk and it seemed to work, I'm not sure why.


Getting Error: Runner in Executor raised an exception in Ragas evaluate using Ollama and giving Nan value in df

I encountered an issue while evaluating a dataset using the ragas library with the Langchain LLM and Sentence Transformer embeddings. The process throws an exception during execution.
Steps to Reproduce:
Reading the DataFrame:
import pandas as pd
df = pd.read_csv("test_results_csv/test.csv")
df["contexts"] = df["contexts"].apply(lambda x: [x])
from datasets import Dataset
dataset = Dataset.from_pandas(df)
dataset[0]
Output:
{
'question': 'What are the major sources of carbohydrates in the traditional Hawaiian diet?',
'ground_truth': "The traditional Hawaiian diet was rich in carbohydrate sources primarily derived from 'uala (sweet potato), ulu (breadfruit), and kalo (taro). These foods were not only staple items but also provided a significant portion of the daily caloric intake. Sweet potatoes, breadfruit, and taro were cultivated extensively and formed the backbone of the Hawaiian nutritional intake, ensuring that the population had a steady and reliable source of energy. The high carbohydrate content of these foods supported the physical demands of daily activities and agricultural work.",
'answer': ' The majority of the diet was made up of these fiber rich carbohydrate foods.',
'contexts': ["['•  Describe the different types of simple and complex  carbohydrates  •  Describe the process of carbohydrate digestion and  absorption  •  Describe the functions of carbohydrates in the  body  •  Describe the body’s carbohydrate needs and how  personal choices can lead to health benefits or  consequences  Throughout history, carbohydrates have and continue to be a major  source of people’s diets worldwide. In ancient Hawai‘i the Hawaiians  obtained the majority of their calories from carbohydrate rich plants  like the ‘uala (sweet potato), ulu (breadfruit) and kalo (taro). For  example, mashed kalo or poi was a staple to meals for Hawaiians.  Research suggests that almost 78 percent of the diet was made up  of these fiber rich carbohydrate foods.1  Carbohydrates are the perfect nutrient to meet your body’s  nutritional needs.  Specifically, digestible  carbohydrates provide bulk in foods, vitamins, and minerals, while  1.\xa0Fujita R, Braun KL, Hughes CK. (2004). The traditional  Hawaiian diet: a review of the literature. Pacific Health  Dialogue, 11(2). http:/ /pacifichealthdialog.org.fj/ Volume2011/no2/ PHD1120220p2162022120Yamada20orig.pdf. Accessed  October 19, 2017.  230  |  Introduction']"]
}
Setting Up the Environment:
from langchain_community.embeddings.sentence_transformer import (
SentenceTransformerEmbeddings,
)
from ragas.llms import LangchainLLMWrapper
from ragas.embeddings import LangchainEmbeddingsWrapper
from langchain_community.llms import Ollama
llm = Ollama(model="mistrallite_Q2_K:latest", temperature=0)
embeddings = SentenceTransformerEmbeddings(model_name='all-MiniLM-L6-v2')
langchain_llm = LangchainLLMWrapper(llm)
langchain_embeddings = LangchainEmbeddingsWrapper(embeddings)
import nest_asyncio
nest_asyncio.apply()
from ragas import evaluate
from ragas.run_config import RunConfig
from ragas.metrics import (
faithfulness,
answer_relevancy,
context_recall,
context_precision,
)
result = evaluate(
dataset=dataset,
metrics=[
context_precision,
context_recall,
faithfulness,
answer_relevancy,
],
raise_exceptions=False,
llm=langchain_llm,
embeddings=langchain_embeddings
)
res_df = result.to_pandas()
Error
Runner in Executor raised an exception
Traceback (most recent call last):
File "/Users/xxx/miniconda3/lib/python3.12/asyncio/tasks.py", line 520, in wait_for
return await fut
^^^^^^^^^
File "/Users/xxx/miniconda3/lib/python3.12/site-packages/ragas/metrics/_context_recall.py", line 169, in _ascore
results = await self.llm.generate(
^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/xxx/miniconda3/lib/python3.12/site-packages/ragas/llms/base.py", line 93, in generate
return await agenerate_text_with_retry(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/xxx/miniconda3/lib/python3.12/site-packages/tenacity/asyncio/init.py", line 189, in async_wrapped
return await copy(fn, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/xxx/miniconda3/lib/python3.12/site-packages/tenacity/asyncio/init.py", line 111, in call
do = await self.iter(retry_state=retry_state)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/xxx/miniconda3/lib/python3.12/site-packages/tenacity/asyncio/init.py", line 153, in iter
result = await action(retry_state)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/xxx/miniconda3/lib/python3.12/site-packages/tenacity/_utils.py", line 99, in inner
return call(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/Users/xxx/miniconda3/lib/python3.12/site-packages/tenacity/init.py", line 398, in
self._add_action_func(lambda rs: rs.outcome.result())

While evaluating my dataset, I am encountering NaN values for the metrics faithfulness and answer_relevancy. However, I am successfully getting values for context_precision and context_recall.
I have increased the run configuration values to ensure the process has sufficient retries and wait times:
run_config = RunConfig(
    max_retries=15,
    max_wait=120,
    thread_timeout=500,
    log_tenacity=True
)

Output:
| question | ground_truth | answer | contexts | context_precision | context_recall | faithfulness | answer_relevancy
-- | -- | -- | -- | -- | -- | -- | -- | --
What are the major sources of carbohydrates in... | The traditional Hawaiian diet was rich in carb... | The majority of the diet was made up of these... | [['• Describe the different types of simple a... | 1.0 | 1.0 | NaN | 0.552834
Why are carbohydrates considered essential for... | Carbohydrates are essential for the human body... | Carbohydrates provide a ready source of energ... | [['Protein Necessary for tissue formation, ce... | 1.0 | 1.0 | NaN | NaN
Request:
Please guide on resolving the NaN values for faithfulness and answer_relevancy metrics.

@divrajput it will be most likely due to json following capabilites of the model. Do you have any tracing tools setup?


Newly added items in collection dont have refernce of parent.

Lets say I have a object A that contains property as Collection B. When I add new item to collection B, the newly added object does not have reference to object A.

Example : Lets say I have class Blog containing collection of Posts. If I add a new post, it should contain reference to the blog, but its null.

Okay Tony, I think I found the answer, I need to implement the fixup methods on parent classes.

Yes, that's it!  Fixup methods will provide what you want here.  Note, however, that these are not strictly necessary, because Entity Framework will fix up the references when retrieving or persisting entities.
Another thing to keep in mind is that you'll most likely want to leave reference properties null on newly created entities, so that only the foreign key value and not the reference entity will be written to the wire, resulting in better performance.  For example, if you have an Order class with Customer and CustomerId properties, only set CustomerId on a new order and leave Customer null.  Trackable Entities on the service-side will populate Customer and return it to the client (via LoadRelatedEntities).

Hi Tony,
The problem is we are executing some rules over the newly created entities,
for that we need to have parent references correctly formed way even before
persistence. You are correct that it will reduce packet size, but we have
some business logic in place due to previous STE.
Do you have T4 template which provides fixup methods ? Or should I write my
own ?
Thanks.
On Wed, Apr 22, 2015 at 2:08 PM, Anthony Sneed<EMAIL_ADDRESS>wrote:

Yes, that's it! Fixup methods will provide what you want here. Note,
however, that these are not strictly necessary, because Entity Framework
will fix up the references when retrieving or persisting entities.
Another thing to keep in mind is that you'll most likely want to leave
reference properties null on newly created entities, so that only the
foreign key value and not the reference entity will be written to the wire,
resulting in better performance. For example, if you have an Order class
with Customer and CustomerId properties, only set CustomerId on a new order
and leave Customer null. Trackable Entities on the service-side will
populate Customer and return it to the client (via LoadRelatedEntities).
—
Reply to this email directly or view it on GitHub
https://github.com/tonysneed/trackable-entities/issues/48#issuecomment-95077812
.

I think the simplest way would be, when creating a new child entity, set the parent property.  For example: new OrderDetail {Order = order}. I'm not sure if we had C# object initializer syntax when STE's were introduced, but it eliminates the need for adding an overloaded ctor to each child entity via a customized T4 template (which might not be too easy).
If you wanted to do this generically, you could write a method that uses reflection to dynamically set the parent property.  Not too difficult, but it would make a good Gist if you wanted to give it a try!

Reflection was overkill for this as while adding items, they don't have reference of collections.
I have solved this issue by taking the t4 template from old STE and merging all changes in trackable entities. As such, Fixup methods are available now.
Thanks.


Allow the use of nested resource key

Hello and thanks for your great work!
I have a little problem. We use a structure like this:
{
  "data": [
    {
      "id": 1,
      "name": "John"
    },
    {
      "id": 2,
      "name": "Jake"
    },
  ],
  "meta": {
    "total": 2,
    "page": 1
  }
}

Now I can write the structure in my generate.js with the "data" and "meta" keys and it return correctly when I call /user.
Anyway when I try to get a single element of the collection, say /user/1, it returns me an empty object with a 404 http code.
I understand that this is a non-conventional request, but do you think that a situation like that could be handled via some config file or options passed to the CLI?
Thank you.

Hi Ingro, always happy to know my projects are appreciated, thanks :)
Not really sure to undersdand your example, because I don't see user in your code? What does generate.js outputs and how do you get /user?

Oh I think I'm getting it. When you get /user, the response is the structure you've shown:
{
  "data": [
    {
      "id": 1,
      "name": "John"
    },
// ...

And because user list is in data, you can't get /user/1.

Yeah sorry it wasn't clear on the first thought, that was the response I expect from the server. I need the meta data to manage the pagination on the client application, but as you guessed I can't get a specific user structuring the data generation in this way.

Thanks, good choice for Radiohead :)
Unfortunately, I don't see a way to use that kind of structure with this project. It would mean creating some all new routes.
And POST, DELETE would need to update the meta properties too.
The current approach in JSON Server for pagination, is to use _start, _end query parameters and the X-TOTAL-COUNT header.
Sorry about that.
Maybe you can have a look at dyson or interfake.
Also, I think it wouldn't take too long to create a custom fake server using Express. Actually, if you look at src/router.js you'll see that the code is quite simple.
Hope it will help.

Well thanks for your suggestions, I will look at the resources you linked me, I think you can close this issue, keep up the good work! :D


Create CONTRIBUTING.md

Add a guide for contributing to the project
See https://github.com/dotnet/home/blob/master/guidance/repo-guide.md

Closed via #456


fix(CopyToClipboard): Ensure it can be shrunk as much as possible

:tada: This PR is included in version 1.0.0-alpha.49 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix hosting.config reload

This is an alternative to https://github.com/apache/trafficserver/pull/8664. That PR is fine in-itself and fixes a bug around the the atomic swap not actually reloading. But fixing that bug so that reloading hosting.config works exposes another deeper bug: the reloaded object has no synchronization around it.
Not only is the pointer itself never read with synchronization, even if it were, the object itself is never synchronized. So even if the pointer were atomic, the object reads could get different variables from different objects, when callers that need multiple variables really need them to come from a single object. Worse, if a request takes longer than the arbitrary delete timer, it could access freed memory.
This fixes the object to be synchronized, and all access behind a mutex. The reload swap and bad drive removal acquire a write lock, and all other accesses (none of which modify the object) acquire a read lock.
I really don't like adding a mutex to the request path. But the only other options I see are an incredibly complex and bug-prone lock-free solution, or not making it possible to reload hosting.config. As much as I dislike it, the mutex should never have contention except on reload or drive failure. So it's probably actually faster and fewer atomic instructions than even a lock-free solution.
This also adds some helper classes, to make it impossible to accidentally forget to acquire or release the mutex, or modify the object with a readlock, via RAII idioms.
Recommend backporting to 9.2.
Fixes #7220

[approve ci docs]

[approve ci autest]

[approve ci autest]

Cherry-picked to v9.2.x


Parse out positive and negative lookahead explicitly to fallback to GPU

In order to fallback properly to CPU for negative and positive lookahead, we still need to parse negative and positive lookahead in the regex parser and throw the appropriate unsupported exception. This PR adds support for that in RegexGroup.
Signed-off-by: Navin Kumar<EMAIL_ADDRESS>

build

Is this part of the work for issue https://github.com/NVIDIA/spark-rapids/issues/7001 ?

Is this part of the work for issue #7001 ?

Yes, this also solves a specific bug that happens when our regular expression parser considers the regex valid, and considers the ! in (! as a literal ! in the regular expression. For now, this will fallback the whole Project to CPU as would be expected.

build


Don't bundle React with the hooks package

I was unable to use the package directly, as you're bundling React with the package itself, and unfortunately, I'm still on React 17. This leads to a situation where the useRepo context provider always returns null. For now, I've copied the hooks into my repo.
In general, as a library author you typically don't want to bundle react with the package. This is typically accomplished via whatever you're using for bundling/building the lib. For Webpack, you can use the externals prop in webpack config. I see you're using Vite, and I believe there are plugins for vite and/or rollup, such as vite-plugin-externals

Hey, good call. Thanks! I'll fix this.

Actually, if you want to send a patch that solves the problem for you, I can test it as well. Otherwise I'll probably end up just guessing at the solution and then asking you to confirm anyway :)

https://github.com/automerge/automerge-repo/pull/241

This can be closed, right?

Hey @msakrejda, just got around to testing this. All works as expected, closing!


Refactor accounts_test to use ex_machina

Expected Behavior
The accounts context test currently is a generated test that would be very brittle to use due to the duplication needed, however, we can remedy this  by converting the Accounts context test to use ex_machina and also adding coverage for the user changesets to separate those two
Actual Behavior
At the moment the accounts_test is a generated test file that uses test fixtures.
Acceptance Criteria

[ ] Refactor the test to use ex_machina
[ ] Tests drive the user changesets

Specifications

Version: 0.0.1-rcauth

duplicate of #67


Should we mark significant versions?

We have started making heavy use of the following “client side” (i.e. code side vs SQL side) logic to find the (up to) three “significant versions” of a package:
    func releases() -> (stable: Version?, beta: Version?, latest: Version?) {
        guard let versions = $versions.value else { return (nil, nil, nil) }
        let releases = versions
            .filter { $0.reference?.semVer != nil }
            .sorted { $0.reference!.semVer! < $1.reference!.semVer! }
        let stable = releases.reversed().first { $0.reference?.semVer?.isStable ?? false }
        let beta = releases.reversed().first {
            // pick first version that is a prerelease *and* no older (in terms of SemVer)
            // than stable
            ($0.reference?.semVer?.isPreRelease ?? false)
                && ($0.reference?.semVer ?? SemVer(0, 0, 0)
                        >= stable?.reference?.semVer ?? SemVer(0, 0, 0))
        }
        let latest = defaultVersion()
        return (stable, beta, latest)
    }

As part of looking into “build reconciliation” in issue #561 it’s becoming increasingly awkward having to pull down all versions of a package and then identify the three ones we’re interested in. Since these significant versions never change on their own, we could simply set a flag on the version record as part of the analysis stage. This would make downstream selections a lot easier.

Something like

final class Version: Model, Content {
  …

  enum Kind: String {
    case latestRelease
    case latestDefaultBranch
    case latestBeta
    case generic
  }

  @Field(key: “kind”)
  var kind: Kind

  …
}

Not sure about the exact names.

Or maybe
final class Version: Model, Content {
  …

  enum Kind: String {
    case release
    case defaultBranch = ‘default_branch'
    case beta
  }

  @Field(key: “latest”)
  var latest: Kind?

  …
}

select * from versions where latest in (‘release’, ‘default_branch’, ‘beta’)

Or even easier
select * from versions where latest is not null;

I love this idea. I'm always a fan of letting the database take the load off, and this feels like a perfect situation. This data can never change anywhere apart from the analysis phase, and so it feels like a pretty safe thing to do.
👍 from me!

Excellent. I’ll tackle that next then, as it’s pretty much a prerequisite for the build trigger mechanism.


publish<EMAIL_ADDRESS>

Requested by: @whatyouhide
Merge target: (default)
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave a comment containing #retract under this issue to retract the release (original issuer only).
Targets

[ ] hex
[ ] registry
[ ] github

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

cc @stephanie-anderson @sl0thentr0py


Make const-fn default

At the moment the cortex-m still hides const versions of some functions (especially Mutex::new()) behind the const-fn feature, but these have worked on stable Rust for some time now.
It looks like this crate does not yet follow the WG MSRV policy so I'm not really sure what the MSRV even is, but perhaps we could allow it to be 1.31 and therefore either remove the const-fn feature or make it a default.
cc https://github.com/rust-embedded/book/pull/196

I filed a PR to bare-metal with this fix: https://github.com/japaric/bare-metal/pull/18


Document available keys

Closed by https://github.com/wlsf82/cy-press/commit/bf9bd2dc08f457c1c042769958d18190d888592b.


Questions on "Cherry Pick" :cherries:

Hiya! Per @jdolitsky email I went over the "Cherry Pick" :cherries: proposal and here are some quick questions:
Added annotations
So for annotations I noticed we are adding new ones:
https://github.com/opencontainers/wg-reference-types/blob/main/docs/proposals/PROPOSAL_E.md#annotations
But we aren't adding a simple one for something like "name." For a client that intends to store and retrieve, I think right now our main (only?) option is to save a custom annotation, but then it means it could be different based on the client. Would it hurt to allow adding a more official "name" annotation org.opencontainers.artifact.name to store an original basename, or a name relative to the upload root (no direct paths)?  It would be akin to org.opencontainers.image.title but title is weird for an artifact, so maybe just name.
Architectures
We are adding org.opencontainers.platform.architecture - is this a scoped set? Is architecture == microarchitecture? E.g., if this is the granularity I have:
https://github.com/archspec/archspec-json/blob/51f75b644a7efd6b2c4dc1a07542856ee2ba6229/cpu/microarchitectures.json
Is that going to be supported?
Referrers
"referrers" is really hard to say, and somehow reminds me of the word "furry" because of the two r's (no idea why, lol). Why can't it just be "refers" ? Also, is it one directional?
Pagination
Is it implied there is a ?page parameter included in Link? https://github.com/opencontainers/wg-reference-types/blob/main/docs/proposals/PROPOSAL_E.md#ordering-and-pagination so someone doesn't always have to start at 0? Might be good to mention.
Tags when referrers not supported
Is this done so you can push something to a registry (that doesn't support referrers) that you might want to eventually push to one that does support it? If objects are now like a graph, how are these basic operations done without losing important nodes?
And I didn't read through all the requirements - but those should be some questions to get us started!

Hiya! Per @jdolitsky email I went over the "Cherry Pick" cherries proposal and here are some quick questions:

Huge thanks for giving this a review @vsoch!

Added annotations
So for annotations I noticed we are adding new ones:
https://github.com/opencontainers/wg-reference-types/blob/main/docs/proposals/PROPOSAL_E.md#annotations
But we aren't adding a simple one for something like "name." For a client that intends to store and retrieve, I think right now our main (only?) option is to save a custom annotation, but then it means it could be different based on the client. Would it hurt to allow adding a more official "name" annotation org.opencontainers.artifact.name to store an original basename, or a name relative to the upload root (no direct paths)? It would be akin to org.opencontainers.image.title but title is weird for an artifact, so maybe just name.

Annotations are relatively painless to add. Do you have an example with a type, name, and description? In the use cases we've been thinking of, we had the type and description, so I'm curious how you'd use the name field in addition to those. We're also assuming artifacts will probably have type specific annotations, like a public key hash for image signing (to find signatures by someone you have in your trust store), or a SBOM format to know one is a cyclonedx-json and another is spdx-xml. If the name needs to be unique across the repository, we can also push an artifact by tag (that exists already even without this WG).

Architectures
We are adding org.opencontainers.platform.architecture - is this a scoped set? Is architecture == microarchitecture? E.g., if this is the granularity I have:
https://github.com/archspec/archspec-json/blob/51f75b644a7efd6b2c4dc1a07542856ee2ba6229/cpu/microarchitectures.json
Is that going to be supported?

These are based on the platform options in the config.json, so we could push for more options there if that's useful to you. Runtimes in the docker/k8s ecosystem wouldn't know how to use those, but you may have other runtimes that do. And since it's a string, there's nothing stopping you from setting your own values, you'll just want to coordinate with others that need that granularity.

Referrers
"referrers" is really hard to say, and somehow reminds me of the word "furry" because of the two r's (no idea why, lol). Why can't it just be "refers" ? Also, is it one directional?

The refers is one way, the signature refers to an existing image. Going the other way, we can already add more content into an image we are creating. Naming things is hard, and I'm trying to get some brainstorming to happen in #41.

Pagination
Is it implied there is a ?page parameter included in Link? https://github.com/opencontainers/wg-reference-types/blob/main/docs/proposals/PROPOSAL_E.md#ordering-and-pagination so someone doesn't always have to start at 0? Might be good to mention.

The Link header I believe comes from RFC5988, and the content of it is left up to registry implementations in that case. The tag listing API also uses this, but they included a way to pass the last parameter to request tags after a specific name. For the index, that might be a descriptor or digest value, but I'm not sure if that's useful (you'd need to know the digest in advance).

Tags when referrers not supported
Is this done so you can push something to a registry (that doesn't support referrers) that you might want to eventually push to one that does support it? If objects are now like a graph, how are these basic operations done without losing important nodes?

Exactly! Registries today don't have the new API, and I'm expecting it will be some time before not just the various SaaS registries are updated, but mainly the various self hosted registries, in large organizations, that are slow to upgrade. So we added the tag schema to allow the same image-spec artifact to be copied from registry to registry without needing any changes, it's just a different way to query it.

And I didn't read through all the requirements - but those should be some questions to get us started!

I make it a point to stop reading there myself. :)

Annotations are relatively painless to add. Do you have an example with a type, name, and description?

I do! So for oras-py (and oras proper too i suspect) when we push an artifact, we want to be able to pull it down to the same name. This is accomplished via https://github.com/oras-project/oras-py/blob/07ae3a1b46b245cb59dd390b50f3a900b07cd861/oras/defaults.py#L28-L29 here https://github.com/oras-project/oras-py/blob/dab9fb207009256b88553e8faca914412083c7ba/oras/provider.py#L563-L564. An interaction might look like this (for oras or oras-py)
$ oras-py push localhost:5000/dinosaur/artifact:v1 --insecure \
--manifest-config /dev/null:application/vnd.dinosaur.config \
./artifact.txt
Successfully pushed localhost:5000/dinosaur/artifact:v1

So I could (right now with the spec) keep a record of the media type, and then maybe I would have an annotation for a description. But where I'd run into trouble is pulling:
$ oras-py pull localhost:5000/dinosaur/artifact:v1

Since this is version 2 of me running this command later, there's no way in heck I can remember what I pushed to that URI! So what I need to do is run that command and then have artifact.txt appear magically, and that only works right now by hijacking this random annotation. So I think if the org.opencontainers.artifact.name was made a proper annotation, then oras (and other tools like  it) would consistently be defining the same thing to then be able to then pull the same thing (and have agreement on the annotation). Does that make sense?

These are based on the platform options in the config.json, so we could push for more options there if that's useful to you. Runtimes in the docker/k8s ecosystem wouldn't know how to use those, but you may have other runtimes that do. And since it's a string, there's nothing stopping you from setting your own values, you'll just want to coordinate with others that need that granularity.

I do think for us loners in HPC space (where many don't join the conversations here) we need the granularity. What would be the best way to go about this? Should I try to get a group together to propose extending platform options - or what about if there was an optional org.opencontainers.artifact.microarch annotation with a more refined set of strings? I could try to get a group to work on that - I think a few folks in HPC land are working on archspec as a root that could be a source of these strings.

Naming things is hard, and I'm trying to get some brainstorming to happen in https://github.com/opencontainers/wg-reference-types/issues/41.

I'll see if I can make some suggestions!

The Link header I believe comes from RFC5988, and the content of it is left up to registry implementations in that case. The tag listing API also uses this, but they included a way to pass the last parameter to request tags after a specific name. For the index, that might be a descriptor or digest value, but I'm not sure if that's useful (you'd need to know the digest in advance).

okay so to be more explicit - if I come back later to some initial query and I ask for the Link URL ?page=10, can I do that? And if so, should the page parameter not be documented? Or are you saying "That's totally up to the registry we can't control it?" Because that is kind of terrible - imagine trying to get a listing of stuffs and you got up to page 10 and then something was killed and you want to start at 11 but because it's not clear or not supported to provide page=, you have to start over.  Registries today don't have the new API, and I'm expecting it will be some time before not just the various SaaS registries are updated, but mainly the various self hosted registries, in large organizations, that are slow to upgrade. So we added the tag schema to allow the same image-spec artifact to be copied from registry to registry without needing any changes, it's just a different way to query it.

Gotcha, thank you!

Annotations are relatively painless to add. Do you have an example with a type, name, and description?

I do! So for oras-py (and oras proper too i suspect) when we push an artifact, we want to be able to pull it down to the same name. This is accomplished via https://github.com/oras-project/oras-py/blob/07ae3a1b46b245cb59dd390b50f3a900b07cd861/oras/defaults.py#L28-L29 here https://github.com/oras-project/oras-py/blob/dab9fb207009256b88553e8faca914412083c7ba/oras/provider.py#L563-L564.

Gotcha, since it's part of the descriptor and not the top level of the manifest, I think you have your choice of annotations, including the description. The use cases we've been looking at are the top level of the manifest since we want to pull those up for later filtering and UI's that list artifacts in a registry. If ORAS and others want to collaborate, we could probably agree on a filename annotation that all of the tools use for this.

These are based on the platform options in the config.json, so we could push for more options there if that's useful to you. Runtimes in the docker/k8s ecosystem wouldn't know how to use those, but you may have other runtimes that do. And since it's a string, there's nothing stopping you from setting your own values, you'll just want to coordinate with others that need that granularity.

I do think for us loners in HPC space (where many don't join the conversations here) we need the granularity. What would be the best way to go about this? Should I try to get a group together to propose extending platform options - or what about if there was an optional org.opencontainers.artifact.microarch annotation with a more refined set of strings? I could try to get a group to work on that - I think a few folks in HPC land are working on archspec as a root that could be a source of these strings.

I'd recommend getting that updated in the config.json and index.json descriptor specs, because I think this is needed for more than just artifacts, you also want your images themselves to have other platforms. This may be best handled as more platform variants and features so that we don't need to create new fields.

The Link header I believe comes from RFC5988, and the content of it is left up to registry implementations in that case. The tag listing API also uses this, but they included a way to pass the last parameter to request tags after a specific name. For the index, that might be a descriptor or digest value, but I'm not sure if that's useful (you'd need to know the digest in advance).

okay so to be more explicit - if I come back later to some initial query and I ask for the Link URL ?page=10, can I do that? And if so, should the page parameter not be documented? Or are you saying "That's totally up to the registry we can't control it?" Because that is kind of terrible - imagine trying to get a listing of stuffs and you got up to page 10 and then something was killed and you want to start at 11 but because it's not clear or not supported to provide page=, you have to start over. Being someone that has used many APIs in many contexts I value this little param guy :)

Right now we don't have that option. I think it would terrify some registry operators because paging support is a bit of a break glass scenario. The hope is for a single image, the descriptor list for associated artifacts to that image would fit in a single Index without breaking the 4MB limit. When thinking of a normal scenario, a descriptor is 100B, but I'll round that up to 500B for extra pulled up annotations, which means you can get ~8,000 artifacts associated with one image before needing a second page of results.

all of the above sounds good! Thanks @sudo-bmitch !

Thanks @vsoch - closing for now!


Allow including config files using relative paths

This pull request enables relative include paths (currently, a relative include path is prepended with a separator character). Following the convention of the C preprocessor, relative paths are interpreted from the directory of the including file (this is also how the terminal editor kitty does it).
The reason I wanted to add this was so that I could include files without needing the full path. It makes it easier to move configuration folders to different places or share them across machines with different directory layouts.
While I was making changes, I also added a few changes to the expand logic: it will expand variables anywhere in the path component, not just in the beginning, and it allows the use of braces (e.g. ${HOME} instead of $HOME). I added tests to verify the behavior, but to get the tests to build properly, I had to refactor the CMake logic a bit. (this might be a bigger change than the actual path logic).

Could you please open a new PR where you only have all the cmake changes. I want to nail those before continuing here. Also this PR does more than one thing (expand feature, non-trivial cmake refactoring) and that should be split up anyway.