Switch to Go 1.19.

Go 1.18 requires a switch from 'go get' to 'go install' for the retrieval
of the controller-gen and kustomize tools.  This is taken from the makefile
boilerplate that is generated by the current kubebuilder tool.
Update the version of kustomize from 3.8.7 to 4.5.7, because the Go 1.19 'go
install' command does not find the earlier version when run on an M1.
Add some 'go fmt' fixups, from the Go 1.19 'fmt' command.
Signed-off-by: Dean Roehrich<EMAIL_ADDRESS>

Is this going to have any impact on my Cancel PR? #40

Is this going to have any impact on my Cancel PR? #40

You'll have to do some merging.  Let me merge this one first.  You'll have a bunch of  merging for all the stuff I've been doing this week.

Is this going to have any impact on my Cancel PR? #40

You'll have to do some merging. Let me merge this one first. You'll have a bunch of merging for all the stuff I've been doing this week.

Agreed. I already have some go.mod and vendor conflicts that I need to fix on my  PR.


Bug: TS2729: Property is used before its initialization.

Describe the bug
Inside classes, if you reuse properties inside other properties, the ordering will lead to an error depending on how they are named.
Code example
class TheClass {
  x = new XProperty()

  // Create model from properties
  model = [this.x]
}

will lead to
class TheClass {
   // Create model from properties
   // Error TS2729: Property 'x' is used before its initialization.
  model = [this.x]
  x = new XProperty()
}

ESLint version
v8.57.0
ESLint Plugin Perfectionist version
v2.7.0
Additional comments
I don't know if this is a good programming standard as I'm just using a framework that generates this kind of code OOB.
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Thank you for your issue!
This bug was fixed in 8c35a7dfbe9b841f86f303c4e9fd4170b47c9c0b and released in v3.0.0.
If you'd like, you can support the release with a retweet:
https://x.com/azat_io_en/status/1815367279191761054


Taiga grass colors are wrong

Source: https://twitter.com/harptheseal/status/1629912758773792773?s=46&t=pEHOD6689JdFEh3zhOAelw

More information: The problem is present in all seasons, although with somewhat different (all wrong) colors. Thanks to MintyCheddar on YouTube:

The purple coloration appears Summer, Fall and Winter, though the purple seems to brighten to magenta in Winter.

The purple discoloration in Taiga biomes can be seen in any season, except 'snowy_winter' when everything turns gray.

Traveled to Taiga biomes away from the spawn point and did not find the purple discoloration in the Taiga, Snowy Taiga, and other biomes there during the Summer season. However, the purple blocks persist in the snowy Groves near the spawn point. I will check the distant Taiga biomes again during Fall.


[AERIE-1744] (draft) Scheduler goal priority update SQL triggers

Tickets addressed: AERIE-1744
Review: By commit
Merge strategy: Merge (no squash)

Description
This PR implements a set of SQL triggers for inserting, updating, and deleting rows from the scheduling_specification_goals and scheduling_template_goals tables, and slightly modifies the constraints for those tables as well. It also has some none-behavior refactors for the db-tests files. Also contains a small refactor in MerlinDatabaseTests.java (see 4).

fixes a small unrelated typo
Implements the triggers, adds non-negative-priority constraint, sets (spec/template_id, priority) constraint to deferred.
Refactors database management out of MerlinDatabaseTests.java into a separate file so SchedulerDatabaseTests.java can use it.
Small quality-of-life refactor, combines all the table-clearing functions in MerlinDatabaseTests.java into a single clearTable(String tableName) function.
Implements the database tests for commit 2.

Verification
The tests for these triggers are the content of the last commit of the PR.
Documentation

Future work

Can you add your test script to the db-tests repo so they run in CI?

Can you add your test script to the db-tests repo so they run in CI?

I've marked the PR ready for review, and that is the content of the last commit.

Looks great to me, nice work 👍


当keep-alive和transition mode="out-in" 在一起时的BUG

Vue.js / vue-router versions
Vue.js 2.2.2
vue-router 2.3.0
Reproduction Link
JSFiddle https://jsfiddle.net/sqchenxiyuan/g3snybbv/2/
Steps to reproduce
step1: click to /b you will see this is B
step2: click to /c you will see this is C
step3: click to /  you will see this is B not  this is A
What is Expected?
at step3 i need this is A not this is B
What is actually happening?
at step3 i need this is A
if not use mode="out-in" this will run success

It looks like Vue is reusing the node but not replacing the content as it should. In your case you should key the router-view, otherwise, you won't get a transition between routes / and /b
https://jsfiddle.net/posva/jm2874L9/
IMO, when using a keep-alive combined with transitions, the router-view should always be keyed

@posva I spend few hours trying to fix this. Thanks a lot! Don't you think this should be documented?

this works indeed

@posva  thank you ,,, but this way will build 2 layout
https://jsfiddle.net/u05ubyr5/
layout at / and /b have different data， build 2 layout item

I try to find origin of this issues, this is what i find:
when the keep-alive change the component
if have cache will just render this vnode
if (this.cache[key]) {
        vnode.componentInstance = this.cache[key].componentInstance;
      } else {

and if mode is out-in while not trigger view update, so the child router-view will not try to update
if there add a $forceUpdate like this:
if (this.cache[key]) {
        vnode.componentInstance = this.cache[key].componentInstance;
        vnode.componentInstance.$forceUpdate();
      } else {

it will work ~~~~~
but I know that this will lead to waste of resources, so can resolve by add
activated(){
this.$forceUpdate();
}

https://jsfiddle.net/g3snybbv/5/

@sqchenxiyuan You save my time!


Chrome extension text changing constantly

Hi, the extension works great, but the text od the subtitles is changing itself so frequently so it is hard to read it. For example, it will re-do the same translation multiple times in a few seconds. Is there a way to modify the extension code so that it just gives a final result? Even if it is not a correct translation it would still be better than like it is now. Thank you!

One quick way I've hacked a solution to this is to change the lines parameter to some static number. It wont fix the line deletion and retranscription, but it will keep the transcribed lines on screen for much longer.
content.js:205
    text_segments = get_lines(elem, 50);


1.4.24

1.4.24

Coverage remained the same at 97.482% when pulling 591bd6b21b8caaa31fafed62efe9dbe865668022 on development into f8c88736dd5012721ae24442144244f3ae91127e on master.


Progress Bar Logic

Now that the home screen design has been completed and the progress bar is being displayed, we want to implement the logic for the progress bar.
For a Monday-Sunday week, each time they complete the exercise task for the day, it should add another segment of progress in the progress bar. This progress should be cleared at the beginning of each new week (on Monday). At 1 of 5 days, the progress bar should be “empty” and say “Let’s Get Started!” underneath. At 2-4 days, the progress should have x - 1 segments filled in and it should say “Keep Going!” underneath. At 5 days, the progress bar should be completely full and say “Well Done!” underneath.


Lexer implementation

Support tokenizing all tokens as listed in the standard from a read line.
https://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_10
Out of scope:
here doc reading and tokenizing

Backticks should be iterated over until a non-escaped backtick is encountered. Even if there are nested command substitutions, backticks must be escaped in nested sequences as well as defined by the standard.
echo `echo   $( echo \`echo 1234 \` ) `

An unquoted backslash followed by a newline should be removed from the input and not added to the history.
\ <newline>

[ ] Newline handling inside of a () parenthesis operator state and maybe also the braces state {}, e.g. (\n) {\n}. The standard doesn't mention these, but bash handles them so we might want to support that.
[ ] Make a graph for all the state transitions

I feel like these grammar rules cover this behavior?
subshell         : '(' compound_list ')'
                 ;
compound_list    :              term
                 | newline_list term
                 |              term separator
                 | newline_list term separator

Hmm I'm not sure, it seems like Bash at least has the lexer logic to look for a closing brace, for example $( ( .. ) would expand to a single word of the form $( ( ... ) and result in a syntax error in the expander instead of the lexer requesting additional input


PH does not display heap segments

The memory tab does not show that some private regions are used by the heap. (in the "Use" column).
The "Sysinternals VMMap" application shows that these memory regions are being used by the heaps.
The simplest example for diagnostics - memory region of the "notepad.exe" buffer. The location of this buffer should be on the heap, but if you find the entered string in memory, it will be in an unnamed private memory region. (VMMap shows that this region is being used by the heap).
In addition, PH does not display the "Portable Executable" sections and TEB like the VMMap does.
OS: Win11.

The memory tab does not show that some private regions are used by the heap.

The memory tab shows the underlying Windows VAD layout. Heap blocks are all located within 1 VAD allocation which grows or shrinks. You would need to use the Right click > Process > Miscellaneous > Heaps menu to see heap information (It's somewhat limited but more could be added if needed).

PH does not display the "Portable Executable" sections and TEB like the VMMap does.

VMMap creates fake pseudo entries for the TEBs and image sections that don't actually exist... We thought it was better to show the actual real layout, so developers can more easily check their code against PH and also review what allocations are sharing the same VAD and that they have appropriate memory protection?

The memory tab shows the underlying Windows VAD layout. Heap blocks are all located within 1 VAD allocation which grows or shrinks. You would need to use the Right click > Process > Miscellaneous > Heaps menu to see heap information (It's somewhat limited but more could be added if needed).

The main issue is that VMMap displays that the my string from "notepad.exe" is located on the heap (and this is logical).
But PH displays that this region is unnamed. This is fine?

The memory tab shows the underlying Windows VAD layout.

I used windbg !address command. (https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/-address)
The output of the command shows that my string entered in "notepad.exe" is located on the heap, as is shown by VMMap. PH does not display this.
windbg output:
1ee`47c2d000 _ Heap       [ID: 0; Handle: 000001ee47a60000; Type: SegmentHeap Segment]
VMMap:
000001EE47C2D000 _ Heap ID: 0 (Default) [COMPATABILITY]
PH:
0x1ee47c2d000 _ ...

my string entered in "notepad.exe" is located on the heap, as is shown by VMMap. PH does not display this.

VMMap is showing regions which don't actually exist in the VAD:

PH detects segments by checking for the heap signature at the beginning of the region which doesn't exist for these allocations.

PH displays that this region is unnamed.

This is the same problem I mentioned with VMMap creating fake pseudo entries. If we split these regions like it does then PH won't show the actual memory layout and any code you write to loop the memory won't match what you see with PH.
Ideally these regions would still be named so you know X, Y and Z are all sharing the same region but I'm not sure how VMMap determined all these regions are part of the heap without the heap signature at this moment.

WinDbg's !address command also seems to recognize segment heap blocks somehow:
More info:              heap owning the address: !heap 0x13219920000
More info:              segment heap segment

It does it also for reserved memory blocks, so it most likely doesn't do any signature match.
I assume it walks all heaps and enumerates their internal blocks.
But I have no technical info about how to do that :(

I assume it walks all heaps and enumerates their internal blocks. But I have no technical info about how to do that :(

You can walk the blocks using CreateToolhelp32Snapshot but last I checked it doesn't enumerate segment heaps.

Ideally these regions would still be named so you know X, Y and Z are all sharing the same region but I'm not sure how VMMap determined all these regions are part of the heap without the heap signature at this moment.

This is a confusing topic.
But in this question I would take WinDbg as a main reference. After all, VMMap is some kind of magic.

@ge0rdi
Your PR has to be reverted, can you please send me an email so I can give you the details?
My email is<EMAIL_ADDRESS>

@dmex
Email sent.

@dmex
Wow, looks pretty cool.
Though I have noticed one issue with it.
RtlCreateProcessReflection creates cloned process from within target process.
And some processes have Child process creation disabled mitigation enabled (like some Edge processes) because they are not supposed to create any children.
And so RtlCreateProcessReflection fails for them :(
Maybe we can try the clone way first and then just fallback to original code if cloning fails?

More info on the failure:
There is RtlpProcessReflectionStartup thread created in target process. It calls RtlCloneUserProcess which fails with:
Error code: (NTSTATUS) 0xc000049d<PHONE_NUMBER>) - The process creation has been blocked.

This should be fixed in the latest nightly @ge0rdi

@dmex
I seems to be working correctly now 👍
Thank you.


Potential summer intern projects?

Try wrapping our spatial component as an R htmlwidget: #153
Documentation process: Find tools for react documentation (#101), or generate from proptypes (#144) + json schema (#72); push to hosting service?

...?

I created a good first bug tag -- Generally, these have a more bounded scope, so they aren't "projects" per se, but they could be a good place to begin.

This will evolve, but we've articulated a project for each intern.


Tests

This gives Neon three things.

Acceptance tests in Javascript
Compile tests
A place for future Rust unit tests  (by adding cd tests/native && env NEON_NODE_ABI=node -e 'console.log(process.versions.modules)' cargo test to bin/test and then adding Rust tests inside the native crate)

From root run bin/test to run the suite.

This is so great! If you wouldn't mind fixing the couple minor nits then I'll merge right away.

Fixed.  I removed index.node with a commit but I can squash and force if you prefer that.

I figured out why the Travis tests are failing: they upgraded to Node.js v6, which requires an upgrade of nan and node-gyp. Can you change the crates/neon-sys/package.json to use "nan": "^2.3.2" and "node-gyp": "^3.3.1"?
Also, we should start specifying the exact versions of Node.js we support in .travis.yml. I think for now we should support 4.x and later. It's up to you if you want to add that in this PR or we can add it afterwards.

Pushed up the neon-sys dep bumps.  I can mess with travis config later on today or tonight if you don't get to it.


Truffle typings needed with unupdated web3 packages

Hi!
I read in the README that to use Truffle target is needed to have the truffle-typings package. The problem's that truffle-typings uses web3 1.2.6 packages. Is there a possibility to update those web3 packages to 1.3.0?
Thank you in advance

Which package versions are you using?
If you check the truffle-typings repo, it says the package is deprecated as TypeChain v2 automatically generates the required typings.
@krzkaczor the README for the truffle target needs to be updated -- remove the typings package reference, and update example links (I'd do it immediately via github UI, but it says I can't if I'm not on a branch, so I can't right now 😅 )

Thanks for the fast response!
I'm using:
typechain --target trufflehotfix './build/contracts/**/*.json'
    "typechain": "1.0.5",
    "typechain-target-trufflehotfix": "0.0.4-alpha",

Which I know those get old. In the other hand, I read the typings package reference on the READMA and that's why I got confused. In addition, I tried to use Truffle-v5 and there were a lot of incompatibility errors. I'll try again and comment here what happened.

You don't need truffle-typings anymore as TypeChain generates it for you. Can you tell me where did you find this info?
When in doubt check out examples: https://github.com/ethereum-ts/TypeChain/tree/master/examples

I found it on the README in Targets section
It says:
Truffle v4 / v5
Truffle target is great when you use truffle contracts already. Check out truffle-typechain-example for more details. It require installing typings for truffle library itself.

Now you can simply use your contracts as you did before and get full type safety, yay!

I'll try to use truffle-v5 target

Thanks! This seems outdated. I will fix it today.

OK, just to know, this kind of problem:
node_modules/@truffle/contract-schema/spec/index.d.ts:72:3 - error TS2411: Property 'contractName' of type 'string | undefined' is not assignable to string index type 'string | number | boolean | any[] | { [k: string]: any; }'.

72   contractName?: string;

is it because I'm importing more than one package of Truffle?

yeah... i think so... Compare your deps with examples - I am sure that they work.

@julianlen best would be to update TypeChain and typechain-target-truffle to the latest version (and a corresponding version of truffle). If you encounter an error in the typings after that, feel free to open a new issue.


Use NotebookEditorWidget from run context to put up kernel picker

This PR fixes https://github.com/microsoft/vscode/issues/127727

We would also need to tweak the precondition, right?

@rebornix Nope, this change was sufficient:

@joyceerhl thanks, it works as charm.


Update template create page weight

Create page should be below Overview and above manage
http://screencast.com/t/nqs22th8

Agree.


allow to set the http method for webhook output

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area config

/area outputs

/area tests

What this PR does / why we need it:
Allow to set different HTTP methods for Webhook output
Which issue(s) this PR fixes:
#398

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Update sbt-typelevel-ci, ... to 0.4.21

About this PR
📦 Updates

org.typelevel:sbt-typelevel-ci
org.typelevel:sbt-typelevel-github
org.typelevel:sbt-typelevel-mergify
org.typelevel:sbt-typelevel-settings
org.typelevel:sbt-typelevel-versioning

from 0.4.18 to 0.4.21
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel" }
}]

labels: sbt-plugin-update, early-semver-minor, semver-spec-patch, version-scheme:early-semver, commit-count:n:2

Superseded by #25.


Implicit staging #169

Adds implicit staging out for executors with shared file systems. Updates data.rst to reflect the latest changes:

added 'ftp', 'http', https' schemes
hidden explicit staging in/out (although still can be used)
added implicit staging in/out

I do not like the long condition at https://github.com/Parsl/parsl/blob/6363ac7e0be88a3a5676ab167247e3f36e9733ee/parsl/dataflow/dflow.py#L198, but I cannot find a good way to get rid of this.

@lukaszlacinski I think these changes look good. Let me know how soon you can make these changes, I can also lend a hand to get this merged quickly :)


Hide section for survey results

We've used a couple of different survey tools - this was requested in an earlier iteration of survey tools.  We're not recording these here now so I'd like to hide this from the view until we decide what to do.

@maneesha hide in the form or in the event details or both?

Both

Reopening...
this should also be hidden on the Edit Event view.

@maneesha
The survey section is hidden on the event_edit view. Can you post a screenshot?

@maneesha Ping.

This is from an older release... all looks good now.


Packaged for NixOS

Just a note, packaged for NixOS in https://github.com/NixOS/nixpkgs/pull/262822 .

Nice, thanks!


check_configuration.cmake: enable correct language CXX

I got this error in a CI build:
CMake Error at cmake/common/check_configuration.cmake:120 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  $<COMPILE_LANGUAGE:...> Unknown language.

The same build works locally though.
Other projects are affected by this as well.

Build status:

Linux
Windows

Which toolchain are you using?

GCC on linux

This was changed in #67 to fix #57.
Micro-CDR is not a C++ project -- the tests use it though, but the sub-CMakeLists.txt configures it.

I only saw it in a CI build, and the same build works locally. I'm not sure where the difference comes from. The change fixes the CI build though, and given the instructions further down $<$<COMPILE_LANGUAGE:CXX>, it's clearly incorrect if C++ isn't enabled.
The alternative (and IMO better) way is to remove $<COMPILE_LANGUAGE:CXX>. It shouldn't be required, as it's C code.

given the instructions further down $<$<COMPILE_LANGUAGE:CXX>, it's clearly incorrect if C++ isn't enabled.

$<COMPILE_LANGUAGE:CXX> is a generator expression, specifically a conditional which checks whether CXX has been enabled previously (see the docs).
What makes you suggest it's incorrect?

It checks for the language used for a given compilation unit, not whether a language is enabled.
It does not mention the case where a language is specified by the expression, but not enabled by the project (possibly because it seems like a logical expectation), so the behavior might depend on the cmake version.

I can reproduce with cmake version 3.10.2, with this case:
project(test LANGUAGES C)

add_executable(test test.c)
target_compile_options(test PRIVATE -Wall
	-Wextra
	-Wshadow
	$<$<COMPILE_LANGUAGE:CXX>:-Wnon-virtual-dtor>
	)

CMake Error at CMakeLists.txt:4 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  $<COMPILE_LANGUAGE:...> Unknown language.

cmake version 3.22.2 does not produce an error.

@pablogs9 do you have any reason not to remove COMPILE_LANGUAGE:CXX?

Build status:

Linux
Windows

LGTM


Intuitive Request Page

As
pupil
I want
a more intuitive request page
In order to
create requests easily
Estimate:
Acceptance Criteria:

[ ] all info about the requested workshop (Thema des Workshops, Zeitrahmen, Teilnehmeranzahl, Kenntnisstand, Anmerkungen) is supposed to move to the pub
[ ] all info about the contact person should be displayed at the bottom
[ ] between those filed there should be a small heading saying: "Persönliche Daten"
[ ] after I sent the request I want to be returned to the home page with the "Anfrage wurde erfolgreich abgesendet" (STILL ENGLISH RN)

A pupil shouldn't request workshops

@hendraet "is supposed to move to the pub"
*top? Or what is 'pup' supposed to mean? :)

@bjrne it should say "top". Helene mistakenly wrote pub and found it funny to leave it like this. (Changed it.)
@Baschdl I could change it to user but for consistency I wrote "pupil" because that's the role with the lowest rights. (We won't be able to keep pupils from requesting workshops, because there is currently no way to distinguish between pupils and teachers.)

@hendraet As far as I know a teacher shouldn't have to create a account to request a workshop. Or did we change this?

@Baschdl Yeah sorry for being imprecise again. It's correct that you don't have to have an account for creating a request but that also means that you can't distinguish between teachers and other people, e.g. pupils


control whether completions or snippets go first

Add a (boolean) setting snippets_first that controls whether completions or snippets get returned first by the LSP.
This change allows for completions to look like

which is nice because the default completion is no longer context-dependent (that is, it does not depend on the file I am editing).

Thanks!


envoy: Add response headers access logging

Use cilium-envoy image that adds response headers to response access
log messages.
Hubble logs for HTTP responses now include HTTP response headers.

test-me-please

gke-stable hit by a known unrelated flake: #16004, no other errors

k8ss-1.16-kernel-netnext hit by known flake #12511, no other failures

k8s-1.21-kernel-4.9 hit by known flake #15097, no other failures


Add multithreaded download

the download is usually slow as it downloads multiple files. A multithreaded download (download multiple files simultaneously) might help? Please add a option for the number of download threads too if this was added.

This might be quite tricky as android only allow limited pool of task based on the cpu count (https://stackoverflow.com/a/40823734)
Also, this might cause a problem with concurrent update to DB, maybe paralel download on the novel level, but not down to chapter level.

I see. Thanks for reviewing it anyways!


Parameters to alter

Hello,
I've tried a few targets now and have failed to obtain binders with the default parameters. The PDL1 example works just fine, so it's not the installation as far as I can tell. What parameters would you recommend I play with?
Thanks!

How many trajectories did you generate so far? Easy targets require about 200-300 trajectories, while hard targets might require more like 2000-3000/

It's not clear to me how many trajectories it generates or how to specify this. My trajectory_stats.csv has between 18-80 rows.

each row is one trajectory. You need to just keep it running longer probably

The script seems to have finished in these cases. Is the workflow to keep re-running or is there a way to specify for it to run longer?

Just keep running or run parallel jobs into the same output folder. You can also reduce the acceptance_rate setting so it doesn't stop, or just set it to false

Ok I'll try that, thanks!


Namsonx/task/stabi branch

Hi Son,
please consider my comments in corresponding ticket:
#153 (comment) #153 (comment) #153 (comment) #153 (comment)

Hi Son,
please consider the four above linked issues as prio1 bugs.
Please provide as soon as possible a pull-request for this.
Thank you,
Thomas

Hi Son,
please consider my comments in corresponding ticket:
#153 (comment) #153 (comment) #153 (comment) #153 (comment)

Hi Son,
please consider the four above linked issues as prio1 bugs. Please provide as soon as possible a pull-request for this.
Thank you, Thomas

Hello Thomas, Hello Holger,
Thank you for your findings!
I resolved all 4 issues based on your comment in the latest commit 34a35aa697fc2 in this pull-request.
Thank you,
Son

Hi Son,
restest mostly successful.
But one curious observation left: JPP_1057 executed separately, causes:
'Could not set variable 'testdict[C][C]' with value '4'! Reason: name 'C' is not defined'
That is OK.
But executed together with other test cases, the error message changes to:
'Could not set variable 'testdict[C][C]' with value '4'! Reason: 2'
Seems that there are still interdependencies.

Hi Son,
restest mostly successful.
But one curious observation left: JPP_1057 executed separately, causes:
'Could not set variable 'testdict[C][C]' with value '4'! Reason: name 'C' is not defined'
That is OK.
But executed together with other test cases, the error message changes to:
'Could not set variable 'testdict[C][C]' with value '4'! Reason: 2'
Seems that there are still interdependencies.

Hello Holger,
I will check the test case ID JPP_1057 and analyze the root cause.
Thank you,
Son

Hi Son,
restest mostly successful.
But one curious observation left: JPP_1057 executed separately, causes:
'Could not set variable 'testdict[C][C]' with value '4'! Reason: name 'C' is not defined'
That is OK.
But executed together with other test cases, the error message changes to:
'Could not set variable 'testdict[C][C]' with value '4'! Reason: 2'
Seems that there are still interdependencies.

Hello Holger,
I have just pushed new commit a95c86f271780 to fix the issue you mentioned in test case ID JPP_1057
Thank you,
Son


docs(headless): Update usage example for FieldSuggestions and CategoryFieldSuggestions

DOC-13317
Updated the //usage examples in

category-suggestions.fn.tsx
field-suggestions.fn.tsx

At first, it was done on the docs repo in this PR: update usage example, but was informed that the build scripts in this instance, take the information from the actual pages in the ui-kit repo. It would've been overridden in the next headless documentation update.
It was advised to update the example in the ui-kit repo to keep the updated examples in future documentation versions.

@fbeaudoincoveo thanks for the review 👍
I don't have the authorization to merge this PR.
Do I need another reviewer to approve or someone from the team has to merge it instead of me?


Create docker image

Create the final docker image for the service.

Done and pushed to dockerhub:
https://hub.docker.com/r/olevezinho/curriculum-vitae

Closing this as done


Fixed bug regarding reset value

I think there's a bug in the function "add_latches_from_implementation", as afterwards the reset value might be different from the original, violating AIGER format specifications. There's more info in the comments in the function. Someone should look over this to make sure it works fine (formally). Upon request I can also give two files where the bug might occur.
I also updated the aiger toolset, added a gitignore and my autoformatter did some stuff, but that shouldn't be of any concern I think.

I think this bug has to do with changes to the AIGER format. It should probably be investigated whether there are other changes that need to be made.


Using Mockingjay in app target (no XCTest)

I want to use Mockingjay in my app to stub real APIs while they are still in development, so I tried what @kylef suggested in #28, but it is not working because you also need to swizzle the NSURLSessionConfiguration (as the implementation in Mockingjay/XCTest does).
The final replacement stub method should be:
func stub(matcher:Matcher, builder:Builder) -> Stub {
    NSURLSessionConfiguration.mockingjaySwizzleDefaultSessionConfiguration()
    return MockingjayProtocol.addStub(matcher, builder: builder)
}

Since using Mockingjay without XCTest could be a useful scenario, maybe it is worth having a note in the readme, or even better supporting this natively.
Another issue is that using the full Mockingjay pod in a test target while using Mockingjay/Core pod in the app creates conflicts on compilation, since if you include both pods they will be compiled as a single framework, I guess (maybe Cocoapods error?).
In my opinion, the stub method should be moved to another global place (like Mockingjay.stub), so that it would be available regardless of XCTest, while the XCTest stuff should be moved to a separate framework or even removed entirely, since it is so simple (and much more clear) to just add a removeAllStubs on tearDown method in a test case, like OHHTTPStubs does.

+1
Found the README to be fairly confusing / misleading around this. While it says it has full XCTest integration, it doesn't say that XCTest is required. Its quite a common use case to stub backend API's while in development, or debugging. It would be useful to have both options, and it needs to be spelled out clearer in the README.

+1 on using stubs for development outside of tests targets

As of version 1.2.1, Mockingjay will swizzle NSURLSessionConfiguration on load so doing this manually is unnecessary.
As for running Mockingjay without XCTest, that is possible and XCTest is not required. If you integrate Mockingjay with CocoaPods by depending on Mockingjay/Core, XCTest will not be required. You can use the following APIs:

MockingjayProtocol.addStub(matcher, builder)
MockingjayProtocol.removeStub(stub)
MockingjayProtocol.removeAllStubs()

Sorry to drop in late on a closed issue, but is there anything special you need to do with your Podfile to make this work? I have my app's pod target doing pod 'Mockingjay/Core', and my tests target doing pod 'Mockingjay', and now running the tests crashes with dyld: Symbol not found on an XCTest.stub().
Have only been fighting this for a couple hours, so maybe posting here is premature.

@invalidname Could you share a bit more of your Podfile please.

Thanks @kylef. Hiding my company's stuff as myproject, it's something like:
def myproject_pods
    pod 'Fabric', '~> 1.6.11'
    pod 'Crashlytics', '~> 3.8.3'
   # etc
end

target 'myproject' do
    shared_pods
    myproject_pods

    pod 'Mockingjay/Core'
end

target 'myprojectTests' do
   inherit! :search_paths

    shared_pods
    myproject_pods
    shared_testPods

    pod 'Quick', ' ~> 0.9.2'
    pod 'Mockingjay'
    pod 'RxBlocking', '~> 2.6'
end

@invalidname I think you will want to try something more along the lines of:
target 'MyProject' do
  pod 'Mockingjay/Core'
  # all pods that are not test go here

  target 'MyProjectTest' do
      inherit! :search_paths
      pod 'Mockingjay/XCTest'
      pod 'Quick', ' ~> 0.9.2'
      # .. all test pods go here
  end
end

@kylef thanks, but still crashing.

I also wanted to use Mockingjay in my main app target and it took some head scratching and searching to find this page. Probably worth adding this information to the README.


Instructor does not support multiple tool calls

[X] This is actually a bug report.
[ ] I am not getting good LLM Results
[ ] I have tried asking for help in the community on discord or discussions and have not received a response.
[ ] I have tried searching the documentation and have not found an answer.

What Model are you using?

[ ] gpt-3.5-turbo
[ ] gpt-4-turbo
[ ] gpt-4
[X] Other (please specify): Qwen2-72B-Instruct with litellm

Describe the bug
When having an unrelated response the structured output fails with:

AssertionError: Instructor does not support multiple tool calls, use List[Model] instead.

To Reproduce
https://github.com/BerriAI/litellm/issues/4699
Expected behavior
Return an empty response and a warning.
Screenshots
If applicable, add screenshots to help explain your problem.

Getting the same error with together ai async client when using the new llama 3.1 7B instruct.

Any updates on this?

I can see that the deepinfra issue from here and the llama 3.1B issue from here are syntax related issues because both providers are deviating from openAI compatible function calling.
Deepinfra only supports "tool_choice" = 'auto' and Together.ai has its own unique requirement for Llama 3.1 function calling.

I can see that the deepinfra issue from here and the llama 3.1B issue from here are syntax related issues because both providers are deviating from openAI compatible function calling.
Deepinfra only supports "tool_choice" = 'auto' and Together.ai has its own unique requirement for Llama 3.1 function calling.

So what do you think can be done about it?
There's no workaround other than updating the lib?

I think function calling and JSON mode are 2 different things in together ai right?
https://docs.together.ai/docs/json-mode
How can I use json mode instead of tool mode?

Yeah so using JSON_SCHEMA mode works just fine.

I'm not using together.ai, why do you bring it up?


[release/v1.36] Refactor handling of kubeconfig for kubevirt

What this PR does / why we need it:
Manual cherry-pick for https://github.com/kubermatic/machine-controller/pull/1301
Which issue(s) this PR fixes (optional, in fixes #<issue number> format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Optional Release Note:

Improve handling of Kubeconfig for KubeVirt

/retest

/test pull-machine-controller-e2e-kubevirt

/test pull-machine-controller-e2e-kubevirt

/retest

/test  pull-machine-controller-e2e-kubevirt-dns-config


Is there a way to draw the Nodes within Drawflow canvas based on user preferred size and position?

I am using the Drawflow within my Vuejs/Nuxtjs application and creating Nodes dynamically upon clicking on the Add Node button. During the addition of the Node within addNode method, I am passing the posx and posy due to which Node is always added to the same place in Drawflow Canvas and I have to drag it to the different place based on my wish.
Is there any way for me to add it to the place I would like directly rather than adding it to the same posx and posy? Also, set the size (height and width) of the Node dynamically? Something like the Drag-and-drop with Draw approach after clicking on the Add Node button?
I have added my code sample in CodeSandbox.
I am really looking forward to some suggestions or work-around. I looking for some suggestions that would look something like this:

To add a node in the position look at you:
Vue3 Example
Repo: https://github.com/jerosoler/drawflow-vue3-example
Demo: https://jerosoler.github.io/drawflow-vue3-example/
Or with vanilla javascript:
Demo: https://jerosoler.github.io/Drawflow/
Repo: https://github.com/jerosoler/Drawflow/blob/master/docs/index.html
You have to use the drag methods (ondragstart, ondragover).
The issue of resizing a node is already more complicated. You will have to use some external library.

@jerosoler Thanks a lot for the links and example. I have been trying to achieve the same using the example mentioned here. However, I am running into a few errors and unable to make it work.
I have posted my code in CodeSandBox for your reference.
I am getting the error within the drag(event) function and the error are due to the following line:

this.mobile_item_selec = event.target.closest('.drag-drawflow').getAttribute('data-node')

event.target has the li element and I am trying to read the closest on it and its throwing the error:
client.js:215 TypeError: Cannot read properties of null (reading 'getAttribute')
    at VueComponent.drag (index.js?!./node_modules/vue-loader/lib/index.js?!./pages/Test.vue?vue&type=script&lang=js&:102)
    at dragstart (templateLoader.js?!./node_modules/vue-loader/lib/index.js?!./pages/Test.vue?vue&type=template&id=cde3d4aa&scoped=true&:32)
    at invokeWithErrorHandling (vue.runtime.esm.js:1862)
    at HTMLLIElement.invoker (vue.runtime.esm.js:2187)
    at HTMLLIElement.original._wrapper (vue.runtime.esm.js:6951)

Can you please suggest how to achieve the drag-and-drop function to draw the nodes whenever I want?

@jerosoler Thanks a lot for your response and example.
I am trying to follow the mentioned code and implement it similar within my application.
I have a few doubts with regards to this code:

I am not understanding what is this significance of the parameter mobile_last_move and where is the value populated to it. Because if I remove the if block and keep only else then it's working within your sample code.

I am trying to follow the same logic and it's not working for me. I have added the code in CodeSandbox

Can you please help me out with this issue?

Fix! Is for support drag with mobile.
View changes: https://github.com/jerosoler/drawflow-vue3-example/commit/dbd08ca8156a4aae7a8c5d4f9fe5f29a0f5b0a58

@jerosoler Thanks a lot for the response and correction. Since I am developing only for the desktop I have removed that part and made it work for the desktop.
I am trying to develop an application similar to what you have developed here. I observe that you have used element-plus which works only with the Vue 3 version. Since I am using the Nuxtjs which is based on the Vue 2 version I am unable to use it. So the look and feel of my application are not as cool as yours.
Can you please let me know what alternative I can use to make my application look cool like yours? I tried the CSS styling but for some reason I am unable to make it look as similar as yours. I have posted my code on CodeSandbox.
@jerosoler If you get a chance can you please have a look at my code and suggest me something so I can develop an application somewhat similar to yours.

Element ui for vue2 https://element.eleme.io/#/en-US

@jerosoler Thanks a lot for providing the Vue2 Element-ui. I included it within my code and modified your node1.vue and nodeHeader.vue so I can adapt them within my Vuejs/Nuxtjs application. But still, for some reason, it does not appear the same.
As of now, I am trying to include only 1 node node1, and trying to make sure it would look as in your sample. I have added the complete code sample similar to your code in Codesandbox.
Can you please let me know what should I do within my Nuxtjs to ensure my front-end looks similar to yours?
Your code: https://github.com/jerosoler/drawflow-vue3-example/blob/master/src/components/drawflow.vue
Your frontend: https://jerosoler.github.io/drawflow-vue3-example/
My code and frontend: https://codesandbox.io/s/blissful-wozniak-6voii?file=/pages/index.vue

The style css is only in files:
https://github.com/jerosoler/drawflow-vue3-example/blob/master/src/assets/style.css
https://github.com/jerosoler/drawflow-vue3-example/blob/master/src/App.vue
https://github.com/jerosoler/drawflow-vue3-example/blob/master/src/components/drawflow.vue

Try change this lines:
@import "~/assets/css/drawflow.css";
@import "drawflow/dist/drawflow.min.css";

to
@import "drawflow/dist/drawflow.min.css";
@import "~/assets/css/drawflow.css";

And add css of the library theme: https://element.eleme.io/#/es/component/quickstart
import 'element-ui/lib/theme-chalk/index.css';

I just saw that the corresponding css was not being applied.


Clarify the usage of ClientOption.ServiceVersion

I tried to generate the SDK by using the following swagger:  https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/data-plane/TranslatorText/stable/v1.1/TranslatorBatch.json
Here is the command I use:
Invoke-DataPlaneGenerateSDKPackage.ps1 -service cognitiveservices -namespace Azure.AI.DocumentTranslation -sdkPath c:/work/azure-sdk-for-net -inputfiles https://github.com/Azure/azure-rest-api-specs/blob/1f1d5b0b9ce6cc94605b2fd619dce374fb6e033a/specification/cognitiveservices/data-plane/TranslatorText/stable/v1.1/TranslatorBatch.json -securityScope https://cognitiveservices.azure.com/.default
In   DocumentTranslationClientOptions.cs
public DocumentTranslationClientOptions(ServiceVersion version = LatestVersion)         {             Version = version switch             {                 ServiceVersion.Vv1_1 => "v1.1",                 _ => throw new NotSupportedException()             };         }

Though this could be a problem in Swagger, can we add a check for the supported version format to avoid generating the name like ServiceVersion.Vv1_1
The version is already part of the URL  uri.AppendRaw("/translator/text/batch/v1.1", false);,  I didn't see this ServiceVersion used in the dotnet SDK, other SDKs like python & JS don't have this 'Version' property,  is there any specific usage of it in dotnet?

@tg-msft, are there Azure.SDK libraries that use the ServiceVersion enum currently?

@lirenhe, is this sufficient clarification to close this issue?  We should create separate issues for specific concerns or feature asks that this explanation raises.

Thanks @annelo-msft and @tg-msft for the reply.
I have 2 questions:

For the version name like 'v1.1' in Swagger, shall we generate the code like 'ServiceVersion.Vv1_1'  or just use 'ServiceVersion.V1_1'
For this case of documentTranslation, we did not pass that value to the service.  The version is hard coded in the uri path.
uri.AppendRaw("/translator/text/batch/v1.1", false);
So even we use a different value,  service would still get v1.1.  So my question would be 'shall we expose that value that is not referenced/used into the public constructor'?

As those are related to API design, I will leave it to you to decide whether we need take any action.
For this one, feel free to close it.

Any service version that is not date-based violates Azure API Guidelines and is flagged by linter rules.

@annelo-msft, thanks for your explanation. DocumentTranslation is just my experiment to check the generated code and do some test. I don't think there is a plan to port DocumentTranslation to DPG.
@mikekistler, we have this rule https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/openapi-authoring-automated-guidelines.md#r3012-apiversionpattern. But it does not seem to be applied to dataplane as I can see a lot of violation there.

The data plane linter rule for api-versioning is implemented in our Spectral ruleset, which we are in the process of integrating into the Azure linter.
https://github.com/Azure/azure-api-style-guide/blob/main/docs/azure-ruleset.md#az-version-policy

Close it as there is no furthur action in DPG side.


Code improvements

Please have a look at the individual commit messages for the details.

This change is

Ignoring AppVeyor which timed out, but Travis succeeded.


Cart-Item card buttons alignment mismatch

Description:
In the Cart section of the page we can see the items added to our cart, where the buttons like Increment(+), Decrement(-) and Delete(X) are not in the same alignment.

The Delete(X) button is also touching the bottom-right ends of the card when we hover on it which affects UI/UX.
It is because of the reason Delete(X) button is given CSS properties of absolute bottom-0 right-0 whereas Increment(+) and Decrement(-) are inside another element.
Proposed Changes:

All 3 buttons can be nested inside the same element.
Flexbox can be used to distinguish (Increment, Decrement) and Delete buttons in the same alignment.

Make sense would you like to address the issue ?

Yes @Anandsg
Can you please assign me to this issue and add Hacktoberfest labels.
Thanks in advance!


Memory leak in ParquetDataset

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
DeepRec version or commit id: 1.15.5+deeprec2208
Python version: python3.6
Bazel version (if compiling from source): bazel 0.26.1
GCC/Compiler version (if compiling from source): 5.4.0
CUDA/cuDNN version: none

Describe the current behavior
Memory leak in ParquetDataset has occured, after run python code, the memory has increase to 3Gb
Describe the expected behavior
Memory stable in ParquetDataset
Code to reproduce the issue
import os

import tensorflow as tf
from tensorflow.python.data.experimental.ops.dataframe import DataFrame
from tensorflow.python.data.experimental.ops.parquet_dataset_ops import ParquetDataset
from tensorflow.python.data.ops import dataset_ops

fields = get_parquet_fields_type(conf)

def make_initializable_iterator(ds):
    if hasattr(dataset_ops, "make_initializable_iterator"):
        return dataset_ops.make_initializable_iterator(ds)
    return ds.make_initializable_iterator()

filename = './output.parquet'

def build_input_fn():
    def parse_parquet(record):
      label = record.pop("clk")
      return record, label
    return parse_parquet

def build_dataset():
    dataset = ParquetDataset(
        filename,
        batch_size=256,
        fields=fields,
        drop_remainder=True,
        )
    dataset = dataset.map(build_input_fn())
    dataset = dataset.prefetch(2)
    return dataset

for i in range(1000):
    ds = build_dataset()
    iterator = make_initializable_iterator(ds)
    with tf.Session() as sess:
      sess.run(iterator.initializer)

Provide a reproducible test case that is the bare minimum necessary to generate the problem.
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Why create 1000 Datasets? This will create 1000 Dataset objects in memory.

oh sorry, I make a misstake for the iterator.  when the iterator is 180, only cost 0.5M. but whenthe iterator increase to 1000, it will cost 3Gb,  why and any adivce to release the dataset?
in our scenario, data source will store in hadoop directory in each hour or each day, we will train 3 month or online learing every 15 min。
day train, for example:
├── data
├── 20240301              # training day1
...
├── 20240530              # training day90
for day in (day1, day90):
for steps in [eval, train]:
dataset = build_dataset()
eval or train

it does create only one 'ParquetDataset' in one day, we will eval_train 90 days dataset, so it will create 180 'ParquetDataset'


A commented line gets checked and errors are thrown

I ran into following issue:
Images were not able to be rendered with the width set and an error was thrown: Prawn::Errors::CannotFit
After fiddling around I tried to comment all lines containing image:..., but the error was still thrown - this is strange as comments should not get checked.
I had to go in that document, set all width to a very low value and raised image by image (many) the width value, which ended up that the width of 60% of images in a table with 2 columns caused the error.
^| image:my_image1.png[text, width=60%,pdfwidth=60%]
^| image:my_image2.pngtext, width=60%,pdfwidth=60%]

There are now two issues:

why do lines get processed if they are set to comment with // image: ....
Note that running a html build does not render commented lines (checked)
why is there no error message where the incident occurs (the image text)

Traceback (most recent call last):
	79: from /usr/local/bin/asciidoctor-pdf:23:in `<main>'
	78: from /usr/local/bin/asciidoctor-pdf:23:in `load'
	77: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/bin/asciidoctor-pdf:27:in `<top (required)>'
	76: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/cli/invoker.rb:110:in `invoke!'
	75: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/convert.rb:117:in `convert'
	74: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/document.rb:936:in `convert'
	73: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:135:in `convert'
	72: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:208:in `convert_document'
	71: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:594:in `indent_section'
	70: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:261:in `block in convert_document'
	69: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:152:in `traverse'
	68: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/document.rb:1005:in `content'
	67: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:84:in `content'
	66: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:84:in `map'
	65: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:84:in `block in content'
	64: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:75:in `convert'
	63: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:135:in `convert'
	62: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:584:in `convert_section'
	61: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:152:in `traverse'
	60: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:84:in `content'
	59: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:84:in `map'
	58: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:84:in `block in content'
	57: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:75:in `convert'
	56: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:135:in `convert'
	55: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:584:in `convert_section'
	54: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:152:in `traverse'
	53: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:84:in `content'
	52: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:84:in `map'
	51: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:84:in `block in content'
	50: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:75:in `convert'
	49: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:135:in `convert'
	48: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:584:in `convert_section'
	47: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:152:in `traverse'
	46: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:84:in `content'
	45: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:84:in `map'
	44: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:84:in `block in content'
	43: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.12/lib/asciidoctor/abstract_block.rb:75:in `convert'
	42: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:135:in `convert'
	41: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/converter.rb:2163:in `convert_table'
	40: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:111:in `table'
	39: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:111:in `new'
	38: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:148:in `initialize'
	37: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:656:in `set_row_heights'
	36: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:369:in `row_heights'
	35: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:369:in `each'
	34: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:373:in `block in row_heights'
	33: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table/cell.rb:317:in `height'
	32: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table/cell.rb:309:in `height_ignoring_span'
	31: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table/cell.rb:336:in `content_height'
	30: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table/cell/text.rb:58:in `natural_content_height'
	29: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table/cell/text.rb:92:in `with_font'
	28: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/font.rb:214:in `save_font'
	27: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table/cell/text.rb:99:in `block in with_font'
	26: from /var/lib/gems/2.5.0/gems/prawn-table-0.2.2/lib/prawn/table/cell/text.rb:60:in `block in natural_content_height'
	25: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/box.rb:214:in `render'
	24: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/font.rb:214:in `save_font'
	23: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/box.rb:215:in `block in render'
	22: from /var/lib/gems/2.5.0/gems/pdf-core-0.9.0/lib/pdf/core/text.rb:227:in `character_spacing'
	21: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/box.rb:216:in `block (2 levels) in render'
	20: from /var/lib/gems/2.5.0/gems/prawn-templates-0.1.2/lib/prawn/text.rb:19:in `text_rendering_mode'
	19: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/box.rb:221:in `block (3 levels) in render'
	18: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/ext/prawn/extensions.rb:265:in `font_size'
	17: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/font.rb:100:in `font_size'
	16: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/box.rb:229:in `block (4 levels) in render'
	15: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/formatted_text/inline_image_arranger.rb:12:in `wrap'
	14: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/wrap.rb:55:in `wrap'
	13: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/line_wrap.rb:49:in `wrap_line'
	12: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/line_wrap.rb:79:in `apply_font_settings_and_add_fragment_to_line'
	11: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/arranger.rb:183:in `apply_font_settings'
	10: from /var/lib/gems/2.5.0/gems/pdf-core-0.9.0/lib/pdf/core/text.rb:231:in `character_spacing'
	 9: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/arranger.rb:193:in `block in apply_font_settings'
	 8: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/arranger.rb:274:in `apply_font_size'
	 7: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.6.0/lib/asciidoctor/pdf/ext/prawn/extensions.rb:265:in `font_size'
	 6: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/font.rb:100:in `font_size'
	 5: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/line_wrap.rb:80:in `block in apply_font_settings_and_add_fragment_to_line'
	 4: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/line_wrap.rb:96:in `add_fragment_to_line'
	 3: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/line_wrap.rb:96:in `each'
	 2: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/line_wrap.rb:117:in `block in add_fragment_to_line'
	 1: from /var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/line_wrap.rb:231:in `fragment_finished'
/var/lib/gems/2.5.0/gems/prawn-2.4.0/lib/prawn/text/formatted/line_wrap.rb:248:in `update_output_based_on_last_fragment': Prawn::Errors::CannotFit (Prawn::Errors::CannotFit)

The problem you are encountering regarding the image not fitting is documented at the top of the README as a limitation of Asciidoctor PDF:

An inline image in a table cell will not force the column wider if the width of the image exceeds the width of the column; either reduce the image width using pdfwidth, increase the width of the column using cols, or convert the cell to an AsciiDoc table cell (see asciidoctor/asciidoctor-pdf/issues/830).

When putting an image in a table cell, you should almost always use an AsciiDoc table cell and, even better, make it a block image. If you don't use an AsciiDoc table cell, the image has to fit within the width you have allocated for the column. If it doesn't, you get the error you see.

as comments should not get checked.

I assure you that comments do not get checked. Something must be incorrect about the syntax you are using for your line comment. I can't tell what you are entering based on the example you have provided.

why is there no error message where the incident occurs (the image text)

When Asciidoctor PDF crashes, this is just how it works. It's too late in a converter to provide line information from the source document. And the "cannot fit" errors happen deep inside of prawn-table where we cannot anticipate and catch them. That's not going to change.

With the help of your comment regarding images in tables and ad-pdf, I fixed them all and the pdf build is working now correctly, images are shown as expected. Even after years of using Antora/ad-pdf I am still learning 😄
Regarding the comment line issue, I have to recheck

Images were not able to be rendered with the width set and an error was thrown: Prawn::Errors::CannotFit

Asciidoctor PDF 2 will now log this at the error level and, if the sourcemap is enabled, report the file and line number of the table. See #2009.


[Feature]: Update dependabot.yml for Json file

Details
The repo only contain dependabot.yml for npm. Since it also contains Json files, it also needs to be updated.
Screenshots

Type of Contribution

[ ] Update to an existing Animated Button
[ ] Adding a new Button
[ ] Resolving a bug
[ ] Proposal to the Repository
[X] Changes related to documentation or README.md
[X] Other Changes

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue
[ ] I am a GSSoC'23 contributor

What would that do ?

Updates the configurations for different package ecosystems, here JSON

🎉 The GSSOC'23 program has reached its conclusion, prompting us to officially close all pull requests (PRs) and issues. We extend a heartfelt thank you for your amazing contributions! 🙌 Keep the coding spirit alive with the same enthusiasm, and may luck 🍀 favor you in all your future coding adventures!


Domain activation is Failed - [BRIEF DESCRIPTION]

App Id: d2pjmkqzpaoen9
Region: eu-west-2
Step: Domain activation
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.
Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

Looks like the app associated with d2pjmkqzpaoen9 has since been deleted.
If you are still experiencing issues you can try following these steps:

Is this domain connected to a different Amplify App that you own? If so, make sure you are not trying to reuse one of the hostnames.
If you are using www.domain.com on the other app, you cannot use www.domain.com on this app
You can use other hostnames, like blog.domain.com
If you had this domain successfully connected to Amplify and then recently (within the last hour) deleted it, please wait and try again.
Check the Cloudfront console to see if you have this domain deployed to any distributions
If you are positive no CloudFront distribution exists (including in other accounts) using this domain, and only if it would not be disruptive to any currently running services, try deleting and recreating the hosted zone


Target Profiles

Rules for Aurelia templates are slightly different to generic html templates. Should be able to change rule behavor based on profile; or have different rules for different targets.

Should be solved by having this project build on-top of https://github.com/MeirionHughes/template-lint and by #2


Best 2020 Sample Lit Parallax Ingest

PR for the ingest for sources with lit parallax from Best 2020 but without Gaia parallax

This is the datasheet: https://docs.google.com/spreadsheets/d/19OQ-W5GrqlwVv3F_6XExgoRY2PjdL-F9OOtOG5mOaZo/edit?usp=sharing

This work should now be done using the new UCS.  The useful reference mapping script was pasted into the relevant issue. https://github.com/SIMPLE-AstroDB/SIMPLE-db/issues/452


Changing an attribute of a sequence is not persisted

Create two sequences
Change the attribute name of the first sequence and save it.
Open the second sequence
Open the first sequence. The attribute renaming is lost on the first sequence

In this case, the two sequences were involved in a union, which I had deleted. I believe the Union propagated some attributes to the input sequences, which might cause this ssue.

closing the panel and reopening shows the correct value, however, when you switch between the same node type the old values don't get flushed/reset


Extending EventEmitter in the coffeescript class

I'm trying to extend my coffeescript class with EventEmitter, but only accessible property is _events.
No other methods are available after extending this object.
Here is my code which is working:
`EventEmitter = require('eventemitter3')
module.exports = (ngModule) ->
item = null
Store = new EventEmitter()
_.extend Store,
  getItem: -> item

return Store`

And this is what I'm trying to accomplish:
`class Store extends EventEmitter
  @item = null

  getItem: =>
    @item

return new Store()`

It doesn't have properties like emit, on, off etc., Just _events.

This works fine:
EE = require 'eventemitter3'

class MyEmitter extends EE
  constructor: (name) -> @name = name
  getName: -> @name

ee = new MyEmitter 'foo'

ee.on 'event', (data) -> console.log data
ee.emit 'event', 'hello'

Closing as this is in no way a limitation or a bug in EE3.


Compat compile options macro

This switches from using an implicit val that required awkward
suppression (as illustrated in CompileOptionsSpec) to allowing
overriding in the same way as done in "import chisel3._" via the
creation of an implicit val in lexical scope.
The motivation is attempting to partially migrate Diplomatic stuff in rocket-chip to import chisel3._. I currently have to do the following:
import Chisel.{defaultCompileOptions => _, _}
import freechips.rocketchip.util.CompileOptions.NotStrictInferReset

It would be nice if we could just write
import Chisel._
import freechips.rocketchip.util.CompileOptions.NotStrictInferReset

This is probably backportable to 3.2.x, although if so we should (probably) exclude the deprecation of Chisel.defaultCompileOptions.

Related issue:

Type of change: other enhancement

Impact: API modification

Development Phase: implementation
Release Notes

Replace Chisel.defaultCompileOptions with a low-priority macro
Deprecate Chisel.defaultCompileOptions

Unfortunately, this seems to cause rocket-chip regression tests to fail:
[info] running freechips.rocketchip.unittest.Generator emulator/generated-src freechips.rocketchip.unittest TestHarness freechips.rocketchip.unittest TLSimpleUnitTestConfig
[info] [0.003] Elaborating design...
[error] (run-main-0) java.lang.reflect.InvocationTargetException
[error] java.lang.reflect.InvocationTargetException
[error] 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[error] 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
[error] 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
[error] 	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
[error] 	at freechips.rocketchip.util.HasGeneratorUtilities.$anonfun$elaborate$1(GeneratorUtils.scala:55)
[error] 	at chisel3.Module$.do_apply(Module.scala:52)
[error] 	at chisel3.Driver$.$anonfun$elaborate$1(Driver.scala:93)
[error] 	at chisel3.internal.Builder$.$anonfun$build$2(Builder.scala:406)
[error] 	at scala.util.DynamicVariable.withValue(DynamicVariable.scala:62)
[error] 	at chisel3.internal.Builder$.$anonfun$build$1(Builder.scala:404)
[error] 	at scala.util.DynamicVariable.withValue(DynamicVariable.scala:62)
[error] 	at chisel3.internal.Builder$.build(Builder.scala:404)
[error] 	at chisel3.Driver$.elaborate(Driver.scala:93)
[error] 	at freechips.rocketchip.util.HasGeneratorUtilities.elaborate(GeneratorUtils.scala:60)
[error] Caused by: chisel3.package$ExpectedChiselTypeException: 'TLBundleA(Wire in TLRationalCrossingSource)' must be a Chisel type, not hardware
[error] 	at chisel3.internal.requireIsChiselType$.apply(Binding.scala:30)
[error] 	at chisel3.SpecifiedDirection$.specifiedDirection(Data.scala:49)
[error] 	at chisel3.Output$.apply(Data.scala:241)
[error] 	at Chisel.package$AddDirectionToData.asOutput(compatibility.scala:38)
[error] 	at freechips.rocketchip.util.RationalIO.<init>(RationalCrossing.scala:52)
[error] 	at freechips.rocketchip.util.RationalIO$.apply(RationalCrossing.scala:64)
[error] 	at freechips.rocketchip.util.RationalCrossingSource$$anon$1.<init>(RationalCrossing.scala:71)
[error] 	at freechips.rocketchip.util.RationalCrossingSource.<init>(RationalCrossing.scala:69)
[error] 	at freechips.rocketchip.util.ToRational$.$anonfun$apply$1(RationalCrossing.scala:157)
[error] 	at chisel3.Module$.do_apply(Module.scala:52)
[error] 	at freechips.rocketchip.util.ToRational$.apply(RationalCrossing.scala:157)
[error] 	at freechips.rocketchip.tilelink.TLRationalCrossingSource$$anon$1.$anonfun$new$1(RationalCrossing.scala:26)
[error] 	at freechips.rocketchip.tilelink.TLRationalCrossingSource$$anon$1.$anonfun$new$1$adapted(RationalCrossing.scala:22)
[error] 	at scala.collection.immutable.List.foreach(List.scala:392)
[error] Nonzero exit code: 1
[error] (Compile / runMain) Nonzero exit code: 1
[error] Total time: 14 s, completed Dec 4, 2019 3:31:50 PM
make[1]: *** [emulator/generated-src/freechips.rocketchip.unittest.TLSimpleUnitTestConfig.fir] Error 1
make: *** [stamps/TLSimpleUnitTestConfig/emulator-ndebug.stamp] Error 2

uh oh. I'll debug

@ucbjrl this did not make it into 3.2.1 right?

Correct. It's been back-ported to 3.2.x so it would go out in 3.2.2.

It looks like the ExplicitCompileOptions (all false) are correct in the target passed to AddDirMethodToData(), but they're replaced by all true in Output.apply().

Alright so the issue then is that by removing the implicit val, package Chisel is pulling it from import chisel3._ at the very top of the file.

It's worse than that, some parts are using the implicit from the macro, others are pulling from import chisel3._:
This pulls from import chisel3._ thus the error
  implicit class AddDirectionToData[T<:Data](target: T) {
    def asInput: T = Input(target)
    def asOutput: T = Output(target)
    def flip(): T = Flipped(target)
  }

This gets the macro in object Chisel
  object Wire extends WireFactory {
    import chisel3.CompileOptions

    def apply[T <: Data](dummy: Int = 0, init: T)(implicit compileOptions: CompileOptions): T = {
      println(s"compileOptions = $compileOptions")
      chisel3.WireDefault(init)
    }

    def apply[T <: Data](t: T, init: T)(implicit compileOptions: CompileOptions): T =
      chisel3.WireDefault(t, init)
  }

I think this is fixable, but I don't have the time to do it thoroughly at the moment so I'm going to revert.


Bug: UI doesn't correctly show onEnd-type infinite piece continuing after having being interrupted by a timed piece on the same source layer

Scenario
On a source layer "Graphic", play a piece "A" of type onSegmentEnd.  Some seconds into the first part of the segment, adib a piece "B" with duration X seconds.
What happens

Playout/timeline: Plays A until the beginning of B, then plays B until the end of B, then goes back to A again.
Timeline View: Shows A correctly spanning the entire segment from the start. As B gets inserted, A gets capped, and only the length of B shows with "nothing" trailing B for the remainder of the current part. In the following parts of the Segment, A is still present.

What should happen
The Timeline View should aim to be WYSIWYG and show what the output (correctly) does. Meaning, when B gets inserted, you should see A continue trailing it for the remainder of the current part. Perhaps even with a new/repeated label for A.
Notes
Have not tried how this behaves or looks with a timed non-adlib piece doing B's job here.

Additional testing suggests that the "wrong" appearance is the same when inserting timed graphics, and that the missing continuation of A shows already before playing the part, and stays the same through playback of A, B and after B.


KaSa interface fixes

This PR introduces some small changes to the Kappa interface in PySB to make static analysis (generating contact maps and influence maps) compatible with the 4th generation Kappa tools. First, the executable for static analysis changes from KaSim to KaSa, and second, the output folders for contact map and influence map have to be specified separately.

Something is wrong on Travis, I'll need to sort that out before this can proceed.

Yes, this commit needs to be merged first: https://github.com/pysb/pysb/pull/254/commits/a85b119f9fec1c2bdebdd1b563f19507514a5bc4

Okay so Travis explicitly checks out an old commit of KaSim which I'll need to change before proceeding.

This latest commit should fix the issues with the new installation requirements. There is one KaSim command line option remaining to be updated before tests will pass.

Closing because this PR is superseded by the more general #265 .


Plugin should require Chartist in UMD

If you load the chartist plugin in a module based environment it fails with the reference error "Chartist is not defined".

https://github.com/gionkunz/chartist-plugin-accessibility/issues/1

https://github.com/gionkunz/chartist-plugin-accessibility/issues/1

Would appreciate a PR :)


{Core} Error message improvement

Description

This PR works to improve the error messages of CLI, which includes the output messages shown to users, messages for Telemetry records, and new error categories. These changes are interdependent to some extent, so it's not very easy to split it into smaller PRs. Beg your patience and understanding for it may be a little large to review. The main changes are:
1. Introduce AzCLIError to replace CLIError
Backgrounds
Currently, CLIError is widely used in both CLI core and command groups. Working as a wrapper of the service-defined error types, CLIError accepts only an error message, which brings a side-effect that we can not distinguish the different error types and categorize them.
For example, CLIError can be caused by resource not found which is an userfault, and it can also be caused by service failure which is a service error. So when we want to differentiate UserFault from Service-Side-Error to do some analysis using telemetry, CLIError will block us. Explore here to see more CLIError messages.
This PR Bings
This PR introduces the new AzCLIError, while it will not change the original workflow of CLIError. You can use the AzCLIError to replace your CLIError anywhere in your codes. And by using AzCLIError, you need to specify

[Required] An error type, defined below in section 2
[Required] An error message
[Optional] A recommendation to fix the error

Another benefit AzCLIError brings is that we can provide the same error message for both CLI users and Telemetry records. Previously, there are many cases that we print error messages for users, while the error message details are not recorded in Telemetry, and even the entire record is missing. Here is an example.
2. Define new error types for better error categorizing
As mentioned in section 1, these new error types can help us differentiate UserFault, Client-Side-Error and Service-Side-Error. The new defined error types are:
# userfaults
  CommandNotFoundError
  ArgumentParseError
  ValidationError
  ManualInterrupt

# service side error
  ServiceError

# client side error
  ClientError

# unexpected error
  UnexpectedError

3. Improve Telemetry

One record for one command.

This PR sets the exception info into the UserTask type record, which means the UserTask record will have all the needed info for a command execution, no matter the comand fails or not. The PR now doesn't change the original workflow of Fault type record, which will be removed from Telemetry records after we confirm the UserTask record work properly.

Fix the record missing issue.

When a command fails with a 404 error, there is no Telemetry record for the command. This PR fixes the issue.
4. New error messages

New error messages format

As we discussed in previous meeting, the new error messages are applied in this PR. These message changes are mainly for userfaults, like CommandNotFountError and ArgumentParseError. The pattern is
ErrorType: ErrorMSG
Try this: ...recommend a command...
Still stuck? ...reference...

Recommend a command when user's command fails

This PR provides the logic to recommend a command for users combining both examples from help files and aladdin recommendations.  It makes sure the recommended command has the same command name with user's input. If there are multiple recommendations, we compare them and find the most similar one with the user's original inputs.
Testing Guide

History Notes

Core

/azp run

May I ask whether the customer's adoption of the commands recommended by ai-did-you-mean-this will be collected?
I personally think that if there is a feedback mechanism to analyze user adoption, it can help us better optimize the recommendation effect.

By the way, we've recently been working on az next project, which also includes the scenario of error handling
PR Link: click
I think we can integrate these similar features in the future, I will discuss with you after I have perfected my project~ 😊

May I ask whether the customer's adoption of the commands recommended by ai-did-you-mean-this will be collected?
I personally think that if there is a feedback mechanism to analyze user adoption, it can help us better optimize the recommendation effect.

Not yet now. Maybe we can discuss with Aladdin team to see if that can help them improve the service and consider then add it in next release if necessary.

All the changes on test files are removed. All the changes on Azure Pipeline are removed.
Now the method is: disabling aladdin requests in all the testing environments, which is decied by CLI core whether current instance is DummyCLI.

#15314


updating docs etc

Hi @irosenboom
thanks for the new pics.
Can you please upload them to this repo, not the Wochenende repo, and use the dev branch so they don't get overwritten ?
link:
https://github.com/MHH-RCUG/nf_wochenende/tree/dev
Thanks.
Colin

Hi @colindaven
yes sure, I will add them here as well. Should I also add output for growth rate and raspir?


Dockerhub - You have reached your pull tate limit

Hello,
Dockerhub 20.11.2020 has announced anonymous pulling rate limit.
https://www.docker.com/increase-rate-limits
For building our images we are using docker hub images. We would like to have a possibility to add Docker Hub credentials into ECR pipeline step to not see this error anymore.

Wrong place for this issue. Please ignore it.


PurgeCSS not stripping styles that get imported (vuejs)

Hey there,
I'm using this plugin with Tailwind + VueJS. In regards to both of those, it works flawlessly with the custom extractor.
However, I recently decided to start using Animate.css in my project, so I imported it in my main.js like so;
import {} from 'animate.css';
(Installed using NPM)
I'm only using 2-3 of the animations in the entire library, so I wanted to lean it down a bit so there wouldn't be pointless code in my app. However, it would appear purgecss isn't "detecting" it for some reason.
Here you can see below how I use these animation classes inside my VueJS templates;
      <transition
        enter-active-class="animated fadeIn custom-fast"
        leave-active-class="animated fadeOut custom-fast"
        mode="out-in">
        <router-view></router-view>
      </transition>

and here is relevant parts of my vue.config.js file;
class TailwindExtractor {
  static extract(content) {
    return content.match(/[A-Za-z0-9-_:\/]+/g) || [];
  }
};

  configureWebpack: {
    plugins: [
      new PurgecssPlugin({
        paths: glob.sync([
          path.join(__dirname, './public/index.html'),
          path.join(__dirname, './src/**/*.vue'),
          path.join(__dirname, './src/**/*.js'),
        ]),
        extractors: [
          {
            extractor: TailwindExtractor,
            extensions: ['html', 'js', 'vue'],
          },
        ],
      }),
    ],
  },

Any idea why this might be happening?
Let me know if more information is needed!

@marbuser @MaickellVilela I am the same, is there any solution?


Prepare 4.7 branch

Disable LUKS
Use latest preview

Argh, there is no CI on branch 4.7! Maybe we should add it for all our branches?

Let's stick on master for now. I will reopen with what can be accepted.

Let's stick on master for now. I will reopen with what can be accepted.


chore: auto assign gh issue templates to project

TASK: #2210
Description, Motivation and Context
Issues created from issue templates are now attached to Spark project (backlog) with the Needs Triage label.
Note: I tried to make it assigned to the Web team automatically, but this is not possible for now: https://github.com/orgs/community/discussions/86679
=> It means every issue we receive must be manually assigned to Web to appear on the Web board. Let's hope GH improves this.
Types of changes

[x] 🛠 Tool

It means every issue we receive must be manually assigned to Web to appear on the Web board
Knowing this limitation, and as we early discussed this topic during workshop, I suggest we keep this as a draft and discuss on the strategy we would adopt for the web team, to be sync and able to communicate with the rest (Elisa + Thomas) :+1:

❤


Further make more clear how enderchest six-rows works

Previous PR said:

Someone on discord got confused with that and I remember I was too when I tried this options for the first time, so this addition should clear things up a bit.

Yet again someone on discord got confused on the Discord, causing a massive loss of productivity in the support Discord and confusion among the meaning of the word "denote". Some people's vocabulary "in their world" may be different, and this commit accounts for that by clarifying these 2 lines in configuration.md.

To repeat what I said in the discord server; The current phrasing of the explanation is fine as is. The "massive loss of productivity . . . and confusion among the meaning of the word 'denote'" is an over exaggeration :P I've replaced "denote" with something else https://github.com/pl3xgaming/PurpurDocs/commit/8b3c49ae10685f2861eec0b5725dfb8e9f932462 so hopefully it's a bit more clear than it was before.


kurator install should be idempotent

I have met after install some component with kurator failed the first time, it always fails afterwards.
One cause I have found is that some resources can be created at the first time, but the second time it still create same resources.  That can happen on helm client now.
Not sure if there are other places that is not idempotent, need to investigate.

Yes, such as installing istio, the first installation has initialized resources such as CRDs. If it fails, you need to delete these resources before re-installation

Another point I found is some intermediate output(secret , leader election configmap/endpoint, etc) can be generated, we need to clean them up too.

[ ] istio https://github.com/kurator-dev/kurator/pull/84
[ ] thanos
[ ] argocd
[ ] karmada
[ ] kubeedge
[ ] submariner
[ ] volcano
[ ] pixie
[ ] prometheus

cc @Xieql

[x]  istio istio: make install idempotent #84
[ ]  thanos
[ ]  argocd
[ ]  karmada
[ ]  kubeedge
[ ]  submariner
[x]  volcano #90
[ ]  pixie
[x]  prometheus #90


Add Arena as Mouseplatform option

arena needs:

[ ] size3D
[ ] material
[ ] color
[ ] shape (enum of rectangle/ellipse/other)

objects in arena include: ladders, wheels, cubes. These will need to be devices. I wonder if we can have a generic "object" class (better name?) for cubes/ladders/etc
(this is part of Motor Observatory needs)

[ ] Need to resolve how shape and size work together. Size3D is fine for rectangle shape, but not for ellipse or other. How likely are other shapes?
[ ] How do we want to document objects in the arena? Need a description of the object as well as its position in the arena.

Also need to add "Cup" as a platform - for Kaspar's experiments. Ask him what details are needed.


Why this "Flag option isn't available in Thorium"?

Please make sure that the theme you are currently using is officially provided by Google, also are you using the CR23 style?

I'm using GTK Theme, but i was also using it on Ungoogledchromium and it worked fine.
This option is just not showing up on the config...

Oh, I partially misunderstood the meaning of your issue.
Thorium currently does not have this experimental flag.
@RyanOrigens

@gz83
Is it going to be added? the dark mode is burning my eyes.

We will explain it in the release log when it is added.
@RyanOrigens

yeah around here we really love dark mode enabled when it works. not understood why it doesnt actually provide dark mode like chrome does, its like as if its still not enabled even though it says enabled, relaunch, and all that.


Cannot Debug Air Application

I've taken a look at both #237 and #295, and neither of them helped me resolve the issue.
Here are my configs.
Any idea what could be preventing debugging?
{
    "application": "application.xml",
    "config": "air",
    "type": "app",
    "compilerOptions": {
        "output": "bin_air/R3Air.swf",
        "library-path": [
            "lib/",
            "src/assets/"
        ],
        "define": [
            {
                "name": "CONFIG::not_air",
                "value": false
            },
            {
                "name": "CONFIG::air",
                "value": true
            },
            {
                "name": "CONFIG::debug",
                "value": false
            },
            {
                "name": "CONFIG::release",
                "value": true
            }
        ],
        "default-size": {
            "width": 780,
            "height": 480
        },
        "default-frame-rate": 120,
        "default-background-color": "#000000",
        "swf-version": 32,
        "target-player": "32.0"
    },
    "files": [
        "src/Main.as"
    ],
    "airOptions": {
        "windows": {
            "output": "bin/r3.air",
            "signingOptions": {
                "storetype": "pkcs12",
                "keystore": "bat/R3Air.p12"
            }
        },
        "mac": {
            "output": "bin/r3.air",
            "signingOptions": {
                "storetype": "pkcs12",
                "keystore": "bat/R3Air.p12"
            }
        },
        "files": [
            {
                "file": "bin_air/data",
                "path": "data"
            },
            {
                "file": "bin_air/icons",
                "path": "icons"
            },
            {
                "file": "bin_air/changelog.txt",
                "path": "changelog.txt"
            }
        ]
    }
}

<?xml version="1.0" encoding="utf-8"?>
<application xmlns="http://ns.adobe.com/air/application/32.0">
  <id>R3Air</id>
  <versionNumber>3.32.0</versionNumber>
  <filename>R3Air</filename>
  <name>R^3</name>
  <architecture>64</architecture>
  <description>FlashFlashRevolution R^3 Engine Standalone</description>
  <supportedProfiles>extendedDesktop desktop</supportedProfiles>
  <gpuPreference>discrete</gpuPreference>
  <initialWindow>
    <title>FFR R^3 - Air Edition</title>
    <content>R3Air.swf</content>
    <systemChrome>standard</systemChrome>
    <transparent>false</transparent>
    <visible>true</visible>
    <minimizable>true</minimizable>
    <maximizable>true</maximizable>
    <resizable>true</resizable>
    <renderMode>direct</renderMode>
  </initialWindow>
  <!--
	More options:
	http://livedocs.adobe.com/flex/3/html/File_formats_1.html#1043413
	-->
  <icon>
    <image36x36>icons/ffr_36.png</image36x36>
    <image48x48>icons/ffr_48.png</image48x48>
    <image72x72>icons/ffr_72.png</image72x72>
    <image96x96>icons/ffr_96.png</image96x96>
    <image144x144>icons/ffr_144.png</image144x144>
    <image180x180>icons/ffr_180.png</image180x180>
    <image192x192>icons/ffr_192.png</image192x192>
    <image512x512>icons/ffr_512.png</image512x512>
  </icon>
</application>

{
	// Use IntelliSense to learn about possible SWF debug attributes.
	// Hover to view descriptions of existing attributes.
	// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
	"version": "0.2.0",
	"configurations": [
		{
			"type": "swf",
			"request": "launch",
            "name": "Launch FFR",
            "preLaunchTask": "ActionScript: compile release - asconfig.json"
		},
		{
			"type": "swf",
			"request": "attach",
			"name": "Attach SWF"
		}
	]
}

"preLaunchTask": "ActionScript: compile release - asconfig.json"

You need a debug build instead of a release build.

Makes no difference. Sorry I was tired last night and didn't include all of the information.
VerifyError: Error #1014: Class flash.events::VsyncStateChangeAvailabilityEvent could not be found.
I also want to be able to debug both debug and release builds, which is possible in FlashDevelop.
@joshtynjala
I am using AIR <IP_ADDRESS>.
So it feels like the debugger is not launching with the debugger for the asc2 compiler, as mentioned in the issues above. The code compiles, so the build is using the compiler.

This is the result I get after the error popup, in release mode. In debug mode, no window opens after the failure.

"swf-version": 32

The swf-version for AIR 32 is 43.
Source: https://www.adobe.com/devnet/articles/flashplayer-air-feature-list.html
Fixing this should make the VerifyError go away.

I also want to be able to debug both debug and release builds, which is possible in FlashDevelop.

I believe that FlashDevelop can show trace() output in the console with release builds, and that's something that I hope to add in VSCode too. However, release builds cannot connect to the full debugger with support for breakpoints, inspecting variables, and things like that.


warning: 'bad_variant_access'

With clang++ -Weverything I see:
deps/mapbox/variant/variant.hpp:58:7: warning: 'bad_variant_access' has no out-of-line virtual method definitions; its vtable will be emitted in every translation unit [-Wweak-vtables]
class bad_variant_access : public std::runtime_error
      ^

/cc @artemp - worth fixing?

I think this is not fixable if I understand the error correctly. We want to derive our exception class from std::runtime_error which is a virtual class. But this being a header-only library there is no way to define the methods of our class anywhere but in the header. There is no .cpp file to define them in.

Yes, as long as we want to derive from std::runtime_error or 'std::exception` we'll face this issue.
Having a look at implementation - with our current usage there's no benefit or requirement to derive from std::runtime_error' and it'll be better to derive from std::exception` (same as boost::variant)
class bad_variant_access : public std::exception
{
public:
    virtual const char* what() const noexcept
    {
        return "mapbox::util::bad_variant_access: FAIL";
    }
}; // class bad_variant_access

At least the above is slightly more efficient ^

See #48. I specifically used std::runtime_error to be backwards compatible with current user code that might check for it, but I believe this should be std::logic_error.
As for your proposed change: I don't think making exceptions more efficient is really important, but otherwise that change looks okay to me if we are sure we always want a fixed string as the message here.

Okay thanks for the details and discussion. Going to close as I agree there is nothing needing fixed.

I m also facing same issue.
anyone have solution or workaround?


Introduce new Promise API methods

The new API methods make it possible to get a Promise object's
result and it's state.

Documentation will be added a bit later. First I would like to get a feedback on the API.

I support this idea! +1

The new functions look reasonable, I support this as well.

I've rebased and updated the PR with docs.


SN1987A photometry mismatch between sources

@jparrent I'd like to figure out exactly why the SUSPECT and the data pulled from Sternberg seem to disagree in regards to the photometry, which is most prominently visible in the I-band (almost a half mag difference between the two sources), but is also apparent in the other bands as well. As far as I can tell, both Sternberg and SUSPECT pulled this data from the same batch of papers from Whitelock and Catchpole. Any idea why the two are different?

@guillochon OK so I think I've figured out what's going on, at least for the I-band. There are 4 datasets being pulled for the I-band. Three of them are Catchpole et al. (1987, 1988, 1989), the last two of which are coming from Sternberg, whereas the first Catchpole points (1987) are coming from SuSpect. And all three of these datasets are the topmost I-band light curve in the plot. It's the fourth set of points, the ones that are noticeably off, that are coming from SuSpect, and those points are actually from Suntzeff et al. (1988), but it's being marked as Catchpole et al. (1987) in the plot/source number (1,2). I have also confirmed that the values for the fourth set are the same as they are in Suntzeff et al.
Turns out Suntzeff et al. point out these 0.3 magnitude differences, although I'm not sure I follow why exactly: ``There are large systematic differences of up to 0.3 mag between the CTIO photometry and other published photometry due to the presence of strong emission lines during this exponential-decline phase.''
At any rate, the reference for the "off points" should be updated to Suntzeff et al., linked above. I'm guessing the UBVRI from Suntzeff (SuSpect) just got lumped together with the Catchpole reference at some point.

@jparrent Thanks for looking into this, I see now that there's a bug in the code pulling from SUSPECT, it is using the first source found for a given even as the source for all data for that event name, hence the Catchpole reference was being used instead of Suntzeff. I think I've fixed this, will go live with the next update.
It's also interesting that there's a real difference between the two sets of photometry. At least we now know the stated reason.

This issue is now fixed, the sources are now properly shown as being different for 1987A (and a number of other events for which SUSPECT was being scraped for).


Added portuguese translations

Add pt.json, pt-br.json files and a variant pt_BR.json because some people uses these variants.

Looks good, thanks


NGSI-LD: test and host context data

Since NGSI-LD brokers will need to access context data via URL. We should provide a simple service to test and host the context data.

duplicated with #339


Good strategy for a frontend

I was wondering what the initial architecture for the frontend/ui could be like?
Should you create a native hi for each major os, or write once run everywhere like electron (you said you didn't want that)?
I could have a look into a simple macOS gui in the next few days, so there could be something clickable

I think there are a few things we need to take into account:

we (will) have a gosub-engine that does the most work
we have user-agents that will display the data and act with user input

I haven't looked into how engines like webkit and gecko and even chromium do this, and how they communicate with the user agents. My initial idea was to see if we can create a (relatively simple) text user agent, as this sounds the least work, but a graphical user-interface is ultimately what it should become.
I sounds like a browser should be native, to give the most flexibility and performance, but I think we should define first what would be part of the engine, and what would be part of the user agent, and how we would communicate between them.

I think a strategy is a plan of actions designed to achieve a long term or overall aim

I'd pitch for investigating these topics before getting too far into this question:

[ ] How does Chromium interact with the app layer?
[ ] How does Firefox interact with the app layer?
[ ] How does Servo interact with the app layer?

It seems like an easy thing to paint yourself into a corner with if one's assumptions are wrong.

Agreed with @emwalker. A lot more research is needed on many different topics, but I wouldn't be afraid to experiment with different components at this moment. Writing small proof of concepts gives us just like doing research some insights in the problems we will face later on.
I don't expect a complete rewrite of the codebase in say a year, but I do think that with knowledge gathered during the year, we should rewrite some parts in order to give it a more stable foundation.
I don't want to create a million pages, but it might be nice if we have a place where we can bundle research (links, notes etc) together. I'm not sure that github is the correct place for this though.


Remember credentials for basic HTTP authentication

Description
https://github.com/jiahaog/nativefier/issues/100, https://github.com/jiahaog/nativefier/issues/155, https://github.com/jiahaog/nativefier/issues/261
Carrying the conversation forward about password saving, I have a web app that requires login every time it is launched and there is no option to "keep me logged in". This site is using a native login prompt, which in the app created by Nativefier looks like this:

Here we go. Maybe electron-cookies is the answer! https://www.npmjs.com/package/electron-cookies

anyone found a solution to this problem yet???

You can write credentials in the url<EMAIL_ADDRESS>(because that looks like tfs).

I suppose that would work for one person, however, not if you wanted to distribute it. As it stands, I gave up and moved on to something else as what I was trying to do was not important at all.

Any solution?

@davibe that doesn't work.

Hi! I'm not sure if 4c581f9 addresses this issue --- I tried the CLI based approach but the website I use seems to only work with chrome password managers (they appear to have no cookies). Please let me know if I'm missing something. Thanks so much!!