Implement a "Monitor" mode for RaSCSI

It would be extremely useful to implement a "monitor" mode for RaSCSI, where it would only be a listener on the SCSI bus. This would be extremely useful for debugging issues.
The Monitor should be configurable so that it can filter out for certain SCSI IDs (for example, all traffic going to/from SCSI ID 5). The data should then be logged to a file so that it can be reviewed later.

Note that this will probably include a hardware modification. It might be possible with the "FULLSPEC" version of the board, but that needs to be confirmed.

This has been started a bit on : https://github.com/akuker/RASCSI/blob/scsimon/src/raspberrypi/scsishark.cpp

Code has been implemented and merged to master. Documentation still needs to be cleaned up.

Documentation is here: https://github.com/akuker/RASCSI/wiki/SCSI-Bus-Capture
This issue can be closed.


Update index.html

Remove duplicate support for "Forge"

Closing PR with regrets and apologies:

PR already exists
Bad title


GFM Syntax highlighting broken

The following markdown code breaks highlighting
```yaml
notifications:
slack:
template:
  - "Build <%{build_url}|#%{build_number}> (<%{compare_url}|%{commit}>) of %{repository}@%    {branch} by %{author} %{result} in %{duration}"
```

Steps to Reproduce
Reproduces how often: 100%
Versions
You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.
Atom    : 1.11.2
Electron: 0.37.8
Chrome  : 49.0.2623.75
Node    : 5.10.0
On Linux Antergos

Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

This will be fixed in upcoming versions of Atom, most likely 1.16.0 or 1.17.0.


Code optimization: Group the properties of load balancing as a "LoadBalancing" class

https://github.com/turms-im/turms/commit/6dae9a4264e116d12ad6a0288e6ea6a6d4ae6f3f


Mutation is causing a THROWN error to propagate.. but not even sure WHY its throwing this error..

Describe the bug
I am getting an (unexpected) Thrown Error in a Query Mutation call ... however, what appears to be the same mutation works in GraphiQL..
The relevant error stack is as follows:
E/flutter (15507): [ERROR:flutter/shell/common/shell.cc(181)] Dart Error: Unhandled exception:
E/flutter (15507): NoSuchMethodError: Class 'JsonUnsupportedObjectError' has no instance getter 'message'.
E/flutter (15507): Receiver: Instance of 'JsonUnsupportedObjectError'
E/flutter (15507): Tried calling: message
E/flutter (15507): #0      Object.noSuchMethod (dart:core/runtime/libobject_patch.dart:50:5)
E/flutter (15507): #1      QueryManager.fetchQuery (package:graphql_flutter/src/core/query_manager.dart:142:24)
E/flutter (15507):
E/flutter (15507): #2      QueryManager.mutate (package:graphql_flutter/src/core/query_manager.dart:59:12)
E/flutter (15507): #3      GraphQLClient.mutate (package:graphql_flutter/src/graphql_client.dart:50:25)
E/flutter (15507): #4      _EventMessageEditScreenState._addEventMessage (file:///Users/sjm/work/mm/mms4/mobile/lib/screens/events/eventMessageEditScreen.dart:224:50)
E/flutter (15507):
E/flutter (15507): #5      _EventMessageEditScreenState._submitForm (file:///Users/sjm/work/mm/mms4/mobile/lib/screens/events/eventMessageEditScreen.dart:276:26)
E/flutter (15507):
To Reproduce
The GraphQL mutation is:
String createEventMessage = """
  mutation createEventMessage(\$customerId: Int!, \$eventId: Int!, \$memberId: Int!,
  \$nameFirst: String!, \$nameMiddle: String!, \$nameLast: String!,
  \$subject: String!, \$content: String!, \$messageClass: Int!) {
  createMessage(
    input: {
      message: {
        customerId: \$customerId,
        eventId: \$eventId,
        memberId: \$memberId,
        messageSubject: \$subject,
        content: \$content,
        nameFirst: \$nameFirst,
        nameMiddle: \$nameMiddle,
        nameLast: \$nameLast,
        messageClass: \$messageClass,
        miimeType: "text/plain",
        isSticky: 0
	    }
    }
    ) {
      message {
        messageId
        createdTime
      }
    }
	}

"""
    .replaceAll('\n', ' ');

With the call being:
    QueryResult result = await globals.gqlClient.mutate(
      MutationOptions(
        document: createEventMessage,
        variables: {
          'customerId': globals.user.customerId,
          'eventId': widget.eventId,
          'memberId': globals.user.memberId,
          'messageClass': MessageClass.MESSAGE_CLASS_USER,
          'messageSubject': subject,
          'content': content,
          'nameFirst': globals.user.nameFirst,
          'nameMiddle': globals.user.nameMiddle,
          'nameLast': globals.user.nameLast,
        },
        fetchPolicy: FetchPolicy.networkOnly,
        context: <String, dynamic>{
          'headers': <String, String>{
            'Authorization': 'Bearer ${globals.user.token}',
            'X-MM-Organization': '${globals.user.customerId}',
          }
        },
      ),
    );

Expected behavior
Well I am hoping the actual mutation works -- but at a minimum I would have expected it to catch the error and then return that in the result.errors aspect ..
However, I am not sure why the error is thrown in the first place?  Here is the working GraphiQL screen shot

Desktop (please complete the following information):
Mac OS 10.14
Smartphone (please complete the following information):
Android Emulator SDK 27

It appears the error is being thrown here - which is hiding some underlying error ..
Error Line
Thanks to my co-worker Scott for tracking this down... one step closer..

@sjmcdowall I'm running into issues around having this library swallow errors as well. I think the problem is that the catch statement swallows all errors instead of catching just the specific errors that need to be transformed into graphql errors.
As far as I can tell, Dart has the ability to catch errors explicitly https://stackoverflow.com/a/20803316/67655
If an exception does not fall under a graphql specific error, it probably should not to be caught.

Getting the same error can you please elaborate how can i get rid of this error @sjmcdowall
But the thing is i am not using mutation, i am using Query because  i want to fetch the data from graphql.
In that query when i am passing the variable default value like any integer value it is working fine but when i am trying to get that variable value from SharedPreferences and trying passing it to query it is giving me this error.
Can you please help.
Thanks in advance

Your problem -- I think -- is that getUserId is an async function (and rightly so) -- but you are NOT calling it async in superInit (because you can not) ..
You need to wait until the userId is actually set .. and that "var prefs" is ugly too :)
You need to handle in your build() the condition where userId is null (and return an "In progress" sort of thing) and only redner the Query() widget if userId is set ..
and then (maybe in your getUserid -- do something like
if (mounted) {
setState() {};
}
to cause a new build() .. now with userId set .. (i'd set it right there in the program) ..
You also do not want your Link and Valuenotifiier stuff like that in ANY build() routine .. that can get 100's / second (assume it can) .. and those should only be done ONCE in the app launch ..
And don't use "var" for anything -- remove that from your Javascript mind..
Grab the google analyze_options.yaml  anduse VS Code .. and make sure to clean up all the errors it finds and keep it clean ..
The last items are just freebie tips :)
But basically you have a fundamental flaw in your knowledge of Flutter flow .. like we all do when we start :)

If I understand correctly, the main issue is error swallowing which will be solved by #193.
@sjmcdowall were you ever able to figure out the underlying cause

closing this as the error swallowing should be solved by #193, and the other issue will need more details


Update docker yaml

Codecov Report

Merging #12 (7aadfcb) into main (887d55a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #12   +/-   ##
=======================================
  Coverage   96.64%   96.64%
=======================================
  Files          50       50
  Lines         835      835
  Branches      124      124
=======================================
  Hits          807      807
  Misses         21       21
  Partials        7        7

Help us with your feedback. Take ten seconds to tell us how you rate us.


Cloud redis

Changes
connecting to a cloud based redis instance instead of a local one.

add instructions for connecting to cloud based redis instance
add functionality for connecting to cloud based redis instance

/kind enhancement
/kind documentation

Fixes #52

See issue for username with golang redis library: https://github.com/go-redis/redis/issues/1343

See issue for username with golang redis library: https://github.com/go-redis/redis/issues/1343

/lgtm
/hold since coverage fails for main.go
If you can add some tests then cool, otherwise got to adjust your coverage goals OR move code to some utility and test there.

@maximilien I'll also add some instructions in the README for this.

/lgtm
/hold since coverage fails for main.go
If you can add some tests then cool, otherwise got to adjust your coverage goals OR move code to some utility and test there.

@maximilien I'll also add some instructions in the README for this.

@beemarie time to rebase and let's get this in soon. Thx

@beemarie time to rebase and let's get this in soon. Thx

yep - just started looking at this since the other one was just merged. I need to remind myself why i marked this WIP first.

/test pull-knative-sandbox-async-component-go-coverage

@maximilien looking at the latest go coverage failure, it actually looks like it's something wrong with the job itself. Will need to see if we can debug:
2021/05/21 01:38:22 Running workflow: presubmit
Warning: token len = 41, which is different from 40
2021/05/21 01:38:22 starting PreSubmit.RunPresubmit(...)

2021/05/21 01:38:22 GetConcernedFiles(...) started
2021/05/21 01:38:22 error running c.PullRequests.ListFiles(Ctx, repoOwner=knative-sandbox, RepoName=async-component, pullNum=64, listOptions): Get "https://api.github.com/repos/knative-sandbox/async-component/pulls/64/files?page=1": net/http: invalid header field value "Bearer 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\n" for key Authorization
+ EXIT_VALUE=1
+ set +o xtrace

@maximilien One other comment, would like to see what @aavarghese & @lionelvillard think about this one before merging this: https://github.com/knative-sandbox/eventing-redis/issues/152

/test pull-knative-sandbox-async-component-go-coverage

@maximilien looking at the latest go coverage failure, it actually looks like it's something wrong with the job itself. Will need to see if we can debug:
2021/05/21 01:38:22 Running workflow: presubmit
Warning: token len = 41, which is different from 40
2021/05/21 01:38:22 starting PreSubmit.RunPresubmit(...)

2021/05/21 01:38:22 GetConcernedFiles(...) started
2021/05/21 01:38:22 error running c.PullRequests.ListFiles(Ctx, repoOwner=knative-sandbox, RepoName=async-component, pullNum=64, listOptions): Get "https://api.github.com/repos/knative-sandbox/async-component/pulls/64/files?page=1": net/http: invalid header field value "Bearer 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\n" for key Authorization
+ EXIT_VALUE=1
+ set +o xtrace

Seems to perhaps be a flake since test passed when I ran it today

/ok-to-test
/approve
/lgtm
/unhold


Send Link" Button isn't seems to be consistent with other buttons

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app
Go to any workspace
Connect bank account,
Add all bank, company and personal information
Select any country for "Issuing Country" & Go to next step
Click on "Get secure link"
Click on "Get link via SMS"
Notice "Send Link" has very less width, taking 2 lines

Expected Result:
Send Link button should be consistent with other buttons in the app (more width)
Actual Result:
Send Link is short & sticking to the phone input
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] MacOS / Chrome / Safari

Version Number: 1.2.67-3
Reproducible in staging?: y
Reproducible in production?: could not check
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/217399328-0094bb78-2b93-41da-96ac-330bd048a3ae.mp4

Expensify/Expensify Issue URL:
Issue reported by: @daraksha-dk
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1675767582642189
View all open jobs on GitHub

Triggered auto assignment to @shawnborton (Design), see these Stack Overflow questions for more details.

I reproduced this in Safari:

I've looped in @Expensify/design to advise on the ideal layout for this button.

This is coming from Onfido, so I'm not sure exactly what we can and can't adjust here. @MariaHCD or @nkuoch any ideas how we might solve this one?

The UI customizations available are listed here: https://github.com/onfido/onfido-sdk-ui/blob/10.4.0/UI_CUSTOMIZATION.md
Taking a look to see if we can adjust any styles for that input field and button

I don't see any options to customize that field and button, unfortunately. It looks like the form itself isn't responsive. I think an option would be to create an issue in the onfido sdk repo to either make that form responsive or allow the option to customize that button (perhaps the former fix would be better)

Okay great, thanks for digging into that Maria! I agree, let's just make an issue in the repo and see what happens from there?

Who is usually in charge of creating issues in other repos? I'd have no idea what information needs to be passed along and in what format, but with some help I'd be happy to do it.

Ookay, I see that it has already been reported to Onfido:

https://github.com/onfido/onfido-sdk-ui/issues/2145
https://github.com/onfido/onfido-sdk-ui/issues/2144

It looks like we have two other issues on our repo that are likely dupes of this one:

https://github.com/Expensify/App/issues/14766
https://github.com/Expensify/App/issues/14879

I think we can close this issue. Let me know what you think, @shawnborton @kadiealexander

Works for me!

Sounds good!


Modifying dopamine to accept continuous action spaces

Could you possibly comment on the difficult of getting dopamine to work with continuous action spaces? Is this something that could be done with a bit of effort, or are the agents completely incompatible with this type of action space? I wanted to have a go getting dopamine to work with the OpenAI Gym BipedalWalker environment. I managed to get all of the initialization and setup working, then realized an assumption of discreet action spaces was hard-coded into dopamine.

It probably isn't easy, the agents are incompatible with these action spaces. This was probably the toughest choice for the first version – to support continuous actions or not. It would have significantly increased code complexity, so we decided to wait until we had a better sense of where to take Dopamine next.

Ok, thanks for this, I appreciate you taking the time to answer my question.


Element type is invalid

I am unable to use the component. When i am importing ToastController and using it, i am getting the below error
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

Instead of  use . Also at that same file add import 'react-toastify/dist/ReactToastify.css'; Wasted a few hours trying to figure it out. Thank you README.md -.-


Real-DRCT-GAN_Finetuned from MSE only in onnx. Author removed pth. Anyone have pytorch weight backup?

Does anyone by any chance have a backed-up PyTorch model "Real-DRCT-GAN_Finetuned from MSE" :

https://drive.google.com/file/d/1DnEb1G58xumuMmXoqiLG2lbYZOVbz_Kp/view?usp=drive_link
The author @ming053l  deleted the file from Google Drive.
Here are my backed up onnx in onnx 16.
https://mega.nz/file/0gJwyIBA#fTdbXWb6zbWrQApg2VgNRbY_fh3wdy5f-mP4Oz1jVbU
You could run it with this script:
https://pastebin.com/DUAKpuF1
Or within chainner.
Anyway, pytorch weight would be nice to have.

Hi, sorry for inconvinece.
The checkpoint of  "Real-DRCT-GAN_Finetuned from MSE" somehow losses in my Googledrive. So the link on github was going to be invalid.
I will retrain a new one and update the link on repository as soon as possible, thanks!

And one more question, please. When we can expect DRCT v2 to be released?  Thank you very much!

Hi @ming053l . Are there any hints about a re-upload of the Real-DRCT-GAN_Finetuned from MSE model? If you can send it to me, please do :) Also, what's the status of DRCT v2, how's the progress, and when can we expect it to be released on GitHub? Thank you very much.

Hi, @ming053l  Please answer :)
Thanks

您好，抱歉回覆晚了，我沒有註意到該電子郵件。
Real-DRCT-GAN已經準備好了，稍後再更新。
Real-DRCT-GAN 現在正在訓練中。
由於伺服器問題，我們的訓練過程中斷了一個星期。現在已修復並運行良好
我認為 FractalDRCT (v2) 將於 2025 年 1 月發布。
Best Regards
[image: 圖片.png]
zelenooki87 @.***> 於 2024年12月3日 週二 上午3:35寫道：

Hi, @ming053l https://github.com/ming053l Please answer :)
Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/ming053l/DRCT/issues/28#issuecomment-2512583582, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A4P3JL2GOMVDPAATB477ECD2DSZA3AVCNFSM6AAAAABRCWAQT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJSGU4DGNJYGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

hi, Real-DRCT-GAN have already updated in google drive, if there are any questions, please let me know! thanks
And Real-DRCT-GAN is still training, almost 1~2 days


Fix: Make HelmChartTemplate a pointer in .spec.chart

If implemented, this will omit empty .spec.chart in rendered yamls.
Required for: https://github.com/fluxcd/flux2/pull/4766

@souleb @stefanprodan was the breaking change to the v2beta2 types here intended? didn't see any mention of that being the case here or in the changelog

@seaneagan if you need v2beta2 stay on api v0.x. In v1.0.0 we have deprecated v2beta2, no one should use it with this version.


Optimizations are causing crashes

Compiling some of our end-to-end test cases with -O seems to cause issues:

Adding readonly on let parameters causes AddressOf.hylo to crash at runtime.
MemoryLayout.hylo makes the compiler crash with LLVM complaining that @llvm.coro.begin occurs more than once

These problems are blocking #864

Have bugs been reported to LLVM?

I think we need more investigation to be sure we're not misusing LLVM before we can do that.


⚠ Visit Santa Rosa - Search has degraded performance

In a9c6f06, Visit Santa Rosa - Search (https://www.visitsantarosa.com/results?search=) experienced degraded performance:

HTTP code: 200
Response time: 934 ms

Resolved: Visit Santa Rosa - Search performance has improved in cd58c08.


Updating readme to test pull requests on GitHub

This is just a test merge to see if my instructions are correct.

Normally I would wait for a code review but since this is a test, I will be merging the pull request.


chore: golang-demo1 to 0.0.2

chore: Promote golang-demo1 to version 0.0.2

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
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

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


dependency bcrypt returns 404 when downloading

Error:
node-pre-gyp ERR! Tried to download(404): https://github.com/kelektiv/node.bcrypt.js/releases/download/v1.0.3/bcrypt_lib-v1.0.3-node-v64-win32-x64.tar.gz
Temporary Solution: I have upgrade to 3.0.0
"dependencies": {
    "bcrypt": "^3.0.0",
    "body-parser": "^1.18.2",
    "express": "^4.16.3",
    "knex": "^0.14.4",
    "pg": "^7.4.1"
  }

Sorry for the delayed response. Seems like there was an issue with npm v5 involving node-pre-gyp which affected this (https://github.com/npm/npm/issues/16728 & https://github.com/kelektiv/node.bcrypt.js/issues/509) but subsequent versions of npm (e.g., >= 5.3) seems to have fixed this.
That said, it's probably a good idea to upgrade :D I'll work on this a bit more in the near future and do so.
Thanks for the headsup!


De-emphasize deprecated scheduling policies for v1.23 and later

Scheduling priorities are deprecated, so:

move the page later in the parent topic
hint that it's not a priority in the sitemap for the live docs

Follow -up to https://github.com/kubernetes/website/pull/30404
/milestone 1.23
/kind cleanup

/assign

/approve


Document cms 3.2 as the last version to support Django 1.7.

As discussed on https://groups.google.com/d/topic/django-cms-developers/WewxCMVtzSI/discussion

Coverage remained the same at 89.335% when pulling 1b67f0916e599420671d28b89f77d90d53e821aa on timgraham:django17-lastversion into 4cb7d715f525290afb736d3c6a61820e24fded09 on divio:develop.

Coverage remained the same at 89.335% when pulling 1b67f0916e599420671d28b89f77d90d53e821aa on timgraham:django17-lastversion into 4cb7d715f525290afb736d3c6a61820e24fded09 on divio:develop.


Update WalkingLeg and JourneyDetailCard

Single Leg Journey
MultiLeg Journey

Large Font Size

#223
#222
#221  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ksharma-xyz and the rest of your teammates on  Graphite


Audios for the dev and test sets

Now it's needed to download all audio files for the "large" dataset in order to have audios for the dev and test sets, which is 3 TB and it's too much if I only want to experiment with the "small" or "medium" training sets. Would it be possible to upload the audios for the dev and test sets separately?

Sure, it is a good idea.

Any update on this? Don't see a way to access the eval audios separately.


Length of Last Word

Problem Link
Mention the problem on which you want to work on
https://leetcode.com/problems/length-of-last-word/
Coding platform
Mention the coding platform from where you have picked the problem
LeetCode
Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python

Additional context (OPTIONAL)
Add any other context or screenshots about the feature request here.

I would love to work on this in java. Kindly assign me as a part of Cross-Woc.

Please assign me this problem in C++

@Nivedita967 Can I work on this issue in Python and C

Sure @kiruba-r11 Go for it :)


Add vim-style j, k bindings for moving up and down cells

Awesome project!
This PR adds "j" and "k" as navigation alternatives to the arrow keys, bringing nbterm slightly closer to the standard keybindings for Jupyter notebooks.

Thanks @larsyencken !


Convert _notification methods to switch - Chunk C

Converts ::_notification methods to use switch statements instead of if. Chunk C of #58155.
I think I didn't miss anything!

Note: To update the PR with relevant changes, please use git commit --amend to keep a single commit (see PR workflow for details).

Note: To update the PR with relevant changes, please use git commit --amend to keep a single commit (see PR workflow for details).

Just noticed your reply, I'll squash my new commit.

Thanks! And congrats for your first merged Godot contribution :tada:

Thanks! I want to make more contributions in the (hopefully) near future!


keepassxc: fix NIX_CFLAGS_COMPILE

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 217905 run on aarch64-linux 1

This seems to me like a bug in how env is parsed. @Artturin do you have an idea? Or am I missing something here?

fixed in https://github.com/NixOS/nixpkgs/pull/217961


fix issue of reading params

It is my attempt to fix the issue #124, which was possibly introduced by PR #123. @zikun-li, can you please check?
In an unrelated change, I also edited a line in substitution.cpp that was tripping earlier.

This may be a quick way to fix it but we need to make sure that not assigning the parameter values won't break other things.
Why do we have the context object not containing the input parameter values? How did you load the QASM file (like, using the function from Graph or from CircuitSeq)?

Great questions, I couldn't figure out how the loading works. But, I saw this line in the prior code,  which also assigns to the map, only if the context object contains the input parameter values. Only the recent PR always assigns, which maybe a good thing, but I couldn't figure it out.

Great questions, I couldn't figure out how the loading works. But, I saw this line in the prior code,  which also assigns to the map, only if the context object contains the input parameter values. Only the recent PR always assigns, which maybe a good thing, but I couldn't figure it out.

Great questions, I couldn't figure out how the loading works. But, I saw this line in the prior code,  which also assigns to the map, only if the context object contains the input parameter values. Only the recent PR always assigns, which maybe a good thing, but I couldn't figure it out.

Great questions, I couldn't figure out how the loading works. But, I saw this line in the prior code,  which also assigns to the map, only if the context object contains the input parameter values. Only the recent PR always assigns, which maybe a good thing, but I couldn't figure it out.

The node->index is a index into context->input_parameters (i.e. you can find the value of the parameter represented by node by context->input_parameters[node->index]. Is this correct? @xumingkuan

The node->index is a index into context->input_parameters (i.e. you can find the value of the parameter represented by node by context->input_parameters[node->index]. Is this correct? @xumingkuan

Note that node->type == CircuitWire::input_param, so node->index is essentially the input parameter index. If the circuit is loaded using the function in CircuitSeq with the same Context object, the Context will store the input parameter value there.

I don't think the problem comes from the qasm_parser. I think the bug is in CircuitSeq::read_json, which does not push parameters to context->input_parameters. When a circuit_seq generated by CircuitSeq::read_json is converted to a graph, the bug above comes, because the context has not been updated.

I see. The problem is that CircuitSeq can have parameters that are symbolic (i.e. without a constant value), but in the Graph::Graph(Context *ctx, const CircuitSeq *seq) API, we assumes that all parameters have a constant value. This should be fixed indeed.
But why you are constructing a Graph from a CircuitSeq generated by CircuitSeq::read_json?

@zikun-li, it happens every time we load equivalence classes. We read the file, parse equivalence classes as circuit sequences (using read json), and then generate graph transformations by converting the sequences to graphs.

Could we parse symbolic parameters as internal_params? would that work

Oh right, so Graph must be able to support symbolic parameters.
For CircuitSeq, I assumed the Context to have either all parameters symbolic or all parameters concrete. I don't know what assumptions are made about symbolic parameters in Graph.

Actually in Graph we allow both symbolic and constant parameters. The only difference between then is that symbolic parameters don't have entries in Graph::constant_param_values, and we don't have support to convert Graph  with symbolic parameters to qasm.

I see. Maybe let's merge this PR for now and I'll make a better API to show if a parameter in CircuitSeq is symbolic.


VTALRM on OSX 10.9.5

I got this while running default vim on Mavericks (OSX 10.9.5).
work/config.vim :) /usr/bin/vim                                                                                g:m[4/694]
vim-pandoc: 'bibliographies' and 'command' modules require vim >= 7.4 and have been disabled.
Press ENTER or type command to continueVim: Caught deadly signal VTALRM

Vim: Finished.

[1]    67444 virtual time alarm  /usr/bin/vim

Vim version:
work/config.vim :) /usr/bin/vim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Dec 19 2013 15:19:49)
Compiled by<EMAIL_ADDRESS>Normal version without GUI.   The vim you're using does not meet the requirements for vim-pandoc apparently.

This error was transient. For example, just now:
$ /usr/bin/vim +PlugInstall +qall
vim-pandoc: 'bibliographies' and 'command' modules require vim >= 7.4 and have been disabled.
Press ENTER or type command to continue
$

The

Try opening vim without any plugin and then do :py print 1 does it segfault? Try with ruby also :ruby puts 1.

Well, the SEGVs are a slightly different issue because they are happening with consistency, and on a different install of Vim. I ran your tests (on that Vim), and :ruby was causing segfaults. I tracked it down to this issue, which I resolved with by running brew uninstall vim; rvm system; brew install vim, per this comment.
That said, I'm unable to reproduce the VTALRM crash on my end (which was with the Apple-provided, system-installed /usr/bin/vim).

I agree with @vheon that the first case you mentioned has nothing to do with vim-plug though I can't be sure if it's caused by vim-pandoc. I would examine plugins that depend on foreign language interfaces. vim-plug is one of them but only so when you run :PlugInstall or :PlugUpdate.
When you run :PlugInstall, vim-plug will use Ruby interface of Vim, and that of OS X default vim has been known to be unstable to some degree and there's not much we can do about it. But the segfault you ran into with homebrew-vim is caused by the broken installation as you have noticed and it's obviously unrelated to the VTALRM in the first case.


can't create logfiles in WIN10

failed to rotate: failed to create new symlink: symlink \LogData\test_error.log.2020052917.3 /LogData/test_error.log.2020052917.3_symlink: A required privilege is not held by the client.

I don't code on windows, so I can't be 100% sure, but I'm pretty certain that

A required privilege is not held by the client.

in the error message means exactly that: you don't have the proper permissions, and that it has nothing to do with this library.

👋 I'm also coming up against this issue, and rather than open a new issue I thought I'd add to this one to give some more context. Love the library, thanks for all your hard work!
On Windows, creating a symlink from a non-elevated process is not allowed, unless

A special developer mode flag has been set at the OS level AND a flag SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE is added to the symlink creation call if using the windows API, OR
the process is run as administrator

You're absolutely right - this isn't the fault of the library. The Golang developers explicitly support this flag when creating symlinks. However, the developer mode flag is rightly off by default and I imagine that most end users would be averse to turning it on or giving an application administrator rights for security reasons.
I won't pretend to have any suggestions beyond adding an option to use this without symlinks. Being primarily a windows user I've never consciously used them before, so this was a good learning opportunity :)

Ah, symlinks. Okay. That changes things a bit. In that case (IIRC) all you should need to do is to NOT use the rotatelogs.WithLinkName option. You then lose the convenient symlink that always points to the latest file, but the rest should work as expected.

In hindsight I didn't even register that the OP had the word symlink in the post. Apologies.


Allow for larger excursions of min, max content boost

Current implementation clips min/max content boost to a smaller range. Allow for larger excursions for better hdr intent representation.
Also, fixed round factor before encoding gainmap coefficient
Test: ./ultrahdr_unit_test

We may not be able to merge this since this may introduce other concerns (e.g. performance drag, introducing error if the input is compressed due to compression artifacts). Besides, existing components e.g. Skia is using the old logic, and moving to this logic may lead to changes outside this library. We can hold this for now.

@ram-mohan @harishdm we will take this change, and some modifications need to be done.
We can introduce an encode mode parameter, "SPEED" mode and "QUALITY" mode, the former to be default. Under "QUALITY" mode we do this. This can happen in API-1, 2, 3 (no API-0 because our internal tone mapping already considered this)
I suggest in this change we start we a macro definition of the encode mode parameter, and making it configurable through the command line app in a follow-up change.
Thank you for your help!

Besides, we may also try out https://github.com/google/libultrahdr/pull/236, which has similar effects for API-1 in my local tests but it's much easier.

@ram-mohan @harishdm we will take this change, and some modifications need to be done.
We can introduce an encode mode parameter, "SPEED" mode and "QUALITY" mode, the former to be default. Under "QUALITY" mode we do this. This can happen in API-1, 2, 3 (no API-0 because our internal tone mapping already considered this)
I suggest in this change we start with a macro definition of the encode mode parameter, and making it configurable through the command line app in a follow-up change.
Thank you for your help!

Dichen, I have made the necessary changes and pushed a patchset.

Besides, we may also try out #236, which has similar effects for API-1 in my local tests but it's much easier.

This should improve quality but solution is not universal. Even though the lower limit is extended from 0 to -6.64, to some extent it is clamped and the upper limit is still clamped. Range of content boost is indicative of dynamic range of recovery of hdr intent from sdr intent. Clamping to a predefined value can work in most cases, but there can be scenarios where this can cause limitations.

Thank you for the latest change. My point is if #236 can give us similar quality improvement as this one, we can consider taking #236. Or we may take both.


firebase_remote_config latest version is not published to pub.dev

https://pub.dev/packages/firebase_remote_config/versions/0.8.0-dev.0
it's published on Jan 14, 2021
could you please update to latest version?

Hi @devit365
The latest version will be pushed when it's ready.
Thank you


fix(UI): use .extend and update color style in P component

Issue:
What I did
How to test

Deploy preview for mcs-lite-ui ready!
Built with commit d5f4770ebac5cf50336a01e7bb4e225ec8ff4411
https://deploy-preview-608--mcs-lite-ui.netlify.com

Deploy preview for mcslite ready!
Built with commit d5f4770ebac5cf50336a01e7bb4e225ec8ff4411
https://deploy-preview-608--mcslite.netlify.com

Deploy preview for mcs-lite-introduction ready!
Built with commit d5f4770ebac5cf50336a01e7bb4e225ec8ff4411
https://deploy-preview-608--mcs-lite-introduction.netlify.com


fix weird error x2

fix #275

Oh, seems like self-hosted compiler solved this problem long ago.
But I think to show error, we still need to show self

I hate this!!!!

Now that we know our editorconfig file is somewhat accurate, we could delete the check in github actions (in a separate PR). I don't care much if a few C files have a few tab characters or some lines that contain unnecessary spaces.

LOL, I just get tired of it...

okay


Implement MSAA with WebGL 2

CesiumJS has noticeable aliasing artifacts, especially with thin geometry (see https://github.com/CesiumGS/cesium/issues/8228). With multisampled render targets in WebGL 2, MSAA is a good step towards fixing them.
To implement MSAA in CesiumJS, we need to decide which render targets will need to get multisampled to avoid artifacts. One idea was to start with the color framebuffer in GlobeDepth.js. There are also questions about how this would interact with translucency passes, and whether there might need to be additional logic for compute commands to perform MSAA if needed.
I'm opening this issue to have a space to discuss the MSAA roadmap and implementation details for CesiumJS.

SMAA Screenshot dump
no AA, viewer.useBrowserRecommendedResolution = false

SMAA, viewer.useBrowserRecommendedResolution = false

no AA, viewer.useBrowserRecommendedResolution = true

SMAA, viewer.useBrowserRecommendedResolution = true

FXAA, viewer.useBrowserRecommendedResolution = true

no AA, viewer.useBrowserRecommendedResolution = true

SMAA, viewer.useBrowserRecommendedResolution = true

FXAA, viewer.useBrowserRecommendedResolution = true

@ebogo1 could you put together a sandcastle where you can switch between a few scenarios (including the two above) and a dropdown that lets you select the AA mode (FXAA, SMAA, None) and a checkbox for useBrowserRecommendedResolution? Even better if you could post an S3 link so anyone can try it out.
I've very interested to see how it looks in action. SMAA seems equal or better than FXAA.

SMAA findings
I put together a hacky branch with SMAA shaders from Three.js (see Three's SMAAPass.js and SMAAShader.js). First thoughts are that it's seems much more straightforward than trying to integrate MSAA (plus it works with WebGL 1) and looks comparable but better than FXAA. I've posted a few comparison screenshots - https://github.com/CesiumGS/cesium/issues/9900#issuecomment-962126274.

As a really high-level overview, SMAA consists of three passes:

Calculate edges in the rendered scene texture.
Calculate blending weights for these edges using two hardcoded texture files. In the smaa branch these are the png files in Source/Assets/Textures/SMAA/, which came from the data URLs that Three.js loads as uniforms (see these lines in Three's SMAAPass).
Use the blending weights to perform AA on the rendered scene texture.

In CesiumJS, this means two PostProcessStages for the edge pass and weights pass, a PostProcessStageComposite to combine them in that order, a PostProcessStage for the blend pass, and a final  PostProcessStageComposite to feed the blend weights and render texture into the blend pass. This all happens in PostProcessStageLibrary.createSMAAStage().
A couple related resources:

the smaa implementation from the authors of this paper
minimal three.js example to render a texture onto a full-screen quad: threejs-smaa.zip
Local Sandcastle to print a data URL containing the rendered scene texture (useful with the three.js example above)
Local Sandcastle with FXAA, SMAA, and useBrowserRecommendedResolution checkboxes with a few different scenes

MSAA findings
I made another branch for testing MSAA; to make it quicker to integrate, there are a couple hacky changes to use SceneFramebuffer instead of GlobeDepth. Only the color and depth textures are multisampled in this branch and if we move forward with MSAA, there is more planning to do for considerations of which other framebuffers to multisample, interpolation options (i.e. should idTexture use MSAA; should depth use the same interpolation as color...), usage with GlobeDepth, etc.

A brief list of changes in the MSAA branch:

SceneFramebuffer's framebuffer is split into two framebuffers. The first one has multisampled renderbuffer attachments and is bind-ed as gl.READ_FRAMEBUFFER during the gl.blitFramebuffer call. The second has the original texture attachments and is the gl.DRAW_FRAMEBUFFER during the gl.blitFramebuffer call. A similar double framebuffer + blit setup would need to be added for any framebuffer we want to apply MSAA to.
In most of Scene.render(), the first of SceneFramebuffer's framebuffers is active. The second, non-multisampled framebuffer is only used after the blit at the end of each frame.
RenderbufferFormat is made to support the DEPTH24_STENCIL8 format for use with WebGL 2 and the RGBA8 format for consistency with the target texture's format during the gl.blitFramebuffer call.

Here is a Sandcastle from the MSAA branch with the same scenarios as the SMAA Sandcastle and a dropdown to change the number of MSAA samples. This Sandcastle requires WebGL 2.

Based on the results from prototyping MSAA and SMAA, we decided to move forward with MSAA as an option for WebGL 2 contexts. The plan is split across a couple PRs, but details might change once I work through more of these changes -

Remove unused code from Scene.js and GlobeDepth.js - i.e. https://github.com/CesiumGS/cesium/issues/6763 still takes up a few lines and the Primitive Framebuffer in GlobeDepth is unused.
Create a new wrapper around Framebuffer to manage resources like Renderbuffers and Texture attachments. Refactor GlobeDepth, Sceneframebuffer, OIT, etc. to use this wrapper instead of creating and destroying Framebuffers and attachments directly. The idea is to make it easier to add a multisample = true option for classes using Framebuffers without having to add the same multisample behavior in different places.
Add a multisample option to the new Framebuffer wrapper and add MSAA. Two big challenges here are -

Managing the temp and copy depth framebuffers used by GlobeDepth. Depending on how blit interacts with transparent textures and stencil textures, there can definitely be a cleanest way to handle GlobeDepth MSAA.
Finalizing decisions on which framebuffers need to be multisampled when MSAA is enabled and which interpolation each should use if multisampled.

(Follow-up) Once MSAA is working, it's possible that it'll expose more code in Scene, View, and classes that own framebuffers that can be refactored. No estimate on this for now, but it's something I'm looking out for.


time type is undefined/inconsistent in store APIs

Although undocumented, store-json appears (through an internal use of Date.time()) to expect timestamp to be ms since Unix epoch. It will probably work with fractions of a ms in provided (double / Number) values.
store-timeseries uses seconds since Unix epoch and does not work with fractions of a second (uses int internally).

see my reply here https://github.com/me-box/databox/issues/181

store-json will be replaced by the new store. A discussion on the new API is ongoing hear https://github.com/me-box/databox/issues/184
closing this, in anticipation of the new store.


Improve readme

Some small improvements.
p.s.
Newbie question: I am learning about genType for the first time and saw usage of .re.js file extensions consistently. Is the extension used for generated js files for type annotations? I initially thought it might be a typo for .bs.js. files but I assume my initial assumption is wrong.

"gentypeconfig": {
    "language": "typescript" | "flow" | "untyped",
    "shims": {
      "ReasonReact": "ReactShim"
    }
  }

shims
e.g. Array with format: "ReasonModule=JavaScriptModule"

^ Is this still true? From the example it looks like a JSON/JS object.

@ryyppy @cristianoc Hi could you check my PR and comment? Thank you!

@wontheone1 I have completely missed this PR!

Thanks a lot for doing it.

@cristianoc Thank you too!


Add poru to the supported clients

Changes
I have added Poru to the supported clients list
Why
Because Poru now supports all of NodeLink's features and is still missing on this list.
Checkmarks

[x] The modified endpoints have been tested.
[x] Used the same indentation as the rest of the project.
[x] Still compatible with LavaLink clients.

Additional information
None.

Changes
I have added Poru to the supported clients list
Why
Because Poru now supports all of NodeLink's features and is still missing on this list.
Checkmarks

[x]  The modified endpoints have been tested.
[x]  Used the same indentation as the rest of the project.
[x]  Still compatible with LavaLink clients.

Additional information
None.

Will be merg

Huh? It was missing?? 🤔

Huh? It was missing?? 🤔

Missing what?

Poru in the list, isn't it in LavaLink client list?

This PR will be merged once https://github.com/parasop/poru/pull/107 is

@ThePedroo, The main PR on poru's repo was merged I'll merge this too.
@Joniii11 Merging this PR, Marks Poru fully compatible with Both Versions of NodeLink.
Thanks.


Refactor linalg routines into a separate module

Support unaligned vectors
Add Dot / Normalize / L2 / Cosine traits for f32 slice / Vec / PrimtiveArray. which can be extended to f16/f64 later.

Close it. will do small piece separately.


Flaky CI Test on Mac

The following test has been intermittently failing all 3 retries in the CI pipeline:
[chrome 118.0.5993.159 mac #0-5] Running: chrome (v118.0.5993.159) on mac
[chrome 118.0.5993.159 mac #0-5] Session ID: b4d99761df66b404c2f0163c1d381691
[chrome 118.0.5993.159 mac #0-5]
[chrome 118.0.5993.159 mac #0-5] » /test/specs/settings.e2e.ts
[chrome 118.0.5993.159 mac #0-5] settings @skipWeb
[chrome 118.0.5993.159 mac #0-5]    ✖ openSettings
[chrome 118.0.5993.159 mac #0-5]
[chrome 118.0.5993.159 mac #0-5] 1 failing (24.2s)
[chrome 118.0.5993.159 mac #0-5]
[chrome 118.0.5993.159 mac #0-5] 1) settings @skipWeb openSettings
[chrome 118.0.5993.159 mac #0-5] Timeout
[chrome 118.0.5993.159 mac #0-5] Error: Timeout
[chrome 118.0.5993.159 mac #0-5]     at listOnTimeout (node:internal/timers:569:17)
[chrome 118.0.5993.159 mac #0-5]     at processTimers (node:internal/timers:512:7)

For example, this affected #111 (first run).

It also affects stable. See the first run in #116.


⚠ DesiTorrents has degraded performance

In 2ad4c1e, DesiTorrents ($DST) experienced degraded performance:

HTTP code: 200
Response time: 2183 ms

Resolved: DesiTorrents performance has improved in 393d50a.


How to improve so we could get results closer to the "regular" VQGAN+CLIP?

Hi! I really love this idea and think that this concept solves the main bottleneck of current VQGAN+CLIP approach which is the optimisation for each prompt. I love how instantaneous this approach is to generating new images. However results with the different CC12M or blog captions model fall short in comparison to the most recent VQGAN+CLIP optimisation approaches
I am wondering where it could potentially be improved. I guess one thing could be trying to embed the MSE regularised and z+quantize most recent VQGAN+CLIP approaches. The other is that I am wondering whether a bigger training dataset would improve the quality. Would it make sense to train it on ImageNet captions or maybe even a bigger 100M+ caption dataset? (maybe C@H?)
As you can see, I can't actually contribute much (but I could help with a bigger dataset training effort) but I'm cheering for this project to not die!

Hi @apolinario, thanks for your interest ! indeed the quality does not match the optimization approaches yet,  the problem could come from the model architecture that is used and/or the loss function.
There is an issue by @afiaka87  #8  "Positional Stickiness" which mentions one of the problems that seem to be persistent (it seems to happen regardless of model size, data size), and we are still not certain about the reason it happens.
"I guess one thing could be trying to embed the MSE regularised and z+quantize most recent VQGAN+CLIP approaches."
Could you please give more details about this approach or a reference ? I could try it out.
"ImageNet captions" I wasn't aware there are captions for ImageNet, do you have a link or repo?
Thanks

Hi @mehdidc, thanks for getting back at this.
So this is a "MSE regularised and Z+quantize VQGAN-CLIP" notebook, there's a debate of whether or not this actually improves quality but it seems to be preferred and widely adopted by some of the digital artists and the EAI community
And yeah, actually "ImageNet captions" don't indeed exist, I just had the naive thought of trying to train it in similar captions of the dataset VQGAN itself was trained without putting more thought into. However, with the release of the first big dataset output from the crawl@home project, I think the LAION-400M or a subset of it could suit very well for training
And thanks for letting me know about the persisten #8 Positional Stickness issue. I noticed a similar behavior while using it. Will try to look into it and also bring some attention to it as well


Exam mode: Quiz pool generate student exams

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
[x] I followed the coding and design guidelines.
[x] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[ ] I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
[x] I documented the Java code using JavaDoc style.

Client

[ ] Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
[ ] I followed the coding and design guidelines.
[ ] Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
[ ] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
[ ] I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
[ ] I documented the TypeScript code using JSDoc style.
[ ] I added multiple screenshots/screencasts of my UI changes.
[ ] I translated all newly inserted strings into English and German.

Motivation and Context
Currently, if an instructor wants to have a high variance of quiz questions for an exam, the instructor needs to create a huge number of quiz exercises. Quiz Pool is created to improve the user experience for instructors to prepare such requirements by having groups of quiz questions that will be randomly selected for each student exam.
Description
Changes

Add student_exam_quiz_question table
Allocate quiz questions based on the group to the students

This is the data model of quiz questions and student exams:

Exam Mode Testing

Note: Detailed steps can be seen on the screencast in screenshot section below
Prerequisites:

1 Instructor

Log in to Artemis as an instructor
Create an exam (ensure the start date is in the future and number of exercises is 1)
Configure 1 exercise of any type
Navigate to the Quiz Pool configuration page (atm it is hidden), so you need to manually add /quiz-pool at the end of the exam detail URL (e.g. https://artemis-test1.artemis.in.tum.de/course-management/23/exams/483/quiz-pool)
Add quiz pool group
Create at least 1 quiz question
Map the quiz question to the group
Click save
Add student(s) to the exam
Generate student exams
Verify that the student exams are generated
Repeat the steps for another exam without Quiz Pool

Testserver States

[!NOTE]
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Performance Review

[ ] I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[ ] I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[ ] Code Review 1
[ ] Code Review 2

Exam Mode Test

[x] Test 1
[x] Test 2

Test Coverage

Class/File
Line Coverage
Confirmation (assert/expect)

StudentExam.java
98%
✅

QuizPool.java
97%
✅

StudentExamRepository.java
90%
✅

QuizPoolService.java
98%
✅

StudentExamService.java
94%
✅

ExamResource.java
95%
✅

Screenshots

https://github.com/ls1intum/Artemis/assets/10885503/ef24f921-7030-4158-9c08-126670827249

Tested on legacy ts11. While trying to delete the exam with the quiz pool I got the following:  I was able to delete the exam without the quiz pool

Thanks for noticing this. This will be solved by this PR: Exam mode: Exam with quiz pool deletion

Works as expected on ts3
Student exams are generated successfully


ja: Make docs/setup/_index.md follow v1.18 of the original text

This is a Feature Request

What would you like to be added
Update docs/setup/_index.md to follow v1.18 of the original (English) text.
Why is this needed
content/ja/docs/setup/_index.md is outdated.
Comments
/language ja
/good-first-issue
File to update
https://github.com/kubernetes/website/blob/dev-1.18-ja.1/content/ja/docs/setup/_index.md
Original
https://github.com/kubernetes/website/blob/fb6364d/content/en/docs/setup/_index.md
diff between translated and v1.18
https://gist.github.com/4f50be4640255bdde3be95dcda52787f
Note
Currently, we use dev-1.18-ja.1 branch. Please open a PR targeting the branch.
ref
https://kubernetes.io/ja/docs/contribute/localization/
If you have a question, feel free to ask us at slack.k8s.io #kubernetes-docs-ja channel

/assign

/close


Having a list field in flask-admin page

I'm making a admin dashboard for a MongoDB, I'm using pymongo. I want to have a list field, and do CRUD operations on it plus the Create,Update operation is limited to choices(using select2field). How can I do this?
I have posted the question on stackoverflow. https://stackoverflow.com/questions/44347462/list-field-in-flask-admin-crud-operations-from-flask-admin-on-a-specific-mongod I didnt go a response till now though.
It is defined with an example there.

from flask_admin import Admin, BaseView, expose
from flask_admin.contrib.mongoengine import ModelView
from flask_admin.form import Select2Field
from wtforms.fields import SelectField
from wtforms.validators import InputRequired
from flask_mongoengine.wtf import model_form

# Custom form with Select2Field for 'role'
class UserForm(model_form(User)):
    role = Select2Field('Role', validators=[InputRequired()], choices=[])

class UserView(ModelView):
    column_list = ('name', 'role')
    form = UserForm

    def on_model_change(self, form, model, is_created):
        model.role = form.role.data

    def create_form(self, obj=None):
        form = super(UserView, self).create_form(obj=obj)
        form.role.choices = [(choice, choice) for choice in ['Admin', 'Editor', 'Viewer']]
        return form

    def edit_form(self, obj=None):
        form = super(UserView, self).edit_form(obj=obj)
        form.role.choices = [(choice, choice) for choice in ['Admin', 'Editor', 'Viewer']]
        return form

admin = Admin(app, name='Flask Admin Example', template_mode='bootstrap3')
admin.add_view(UserView(User))


Improvements for Android platforms

Discussion started over on this thread .
Currently, The Unity connector builds fine for all platforms (except IL2CPP dependent ones)
However, There are some significant limitations for non-desktop platforms.

[ ] SQLite cache does not work out of the box, and it being the default local transport, causes problems.
[ ] No mechanism to load accounts.

It is, however, possible to manually receive through a hardcoded auth token, and manually specifying an alternative local transport (E.g. memory transport).
See https://github.com/specklesystems/speckle-unity/blob/main/Assets/Extra/ManualReceive.cs
Additionally, there are a number of ways we can improve the DX for Android/IOS builds.

[ ] Add Android/IOS to our release testing cycle.
[ ] Scope web based auth improvements.
[ ] Scope transport improvements.
[ ] Scope full SQLite support.

See discussion

https://speckle.community/t/unity-android-build/3104
https://speckle.community/t/receiving-speckle-streams-in-ios-apps/1910
#22

Closing this ticket as we are moving to Jira to reduce noise. You can access it there.


JSON formatter shows incorrect line number for steps in a Scenario Outline

Copied issue from cucumber-ruby: https://github.com/cucumber/cucumber-ruby/issues/1108
Configuration

Cucumber: 2.* (Confirmed issue on 2.4.0 & 2.0.0)
Gherkin: 4.1.1

Issue not present on Cucumber 1.3.20, that's why I assume it came with version 2.
Upon further inspection, it seems the introduction of Cucumber Core caused this issue
Summary
The line numbers given to a step in the json formatter is always the line number of the Example row. Because of this, it's not possible to distinguish the steps from each other, as the line number is their unique value.
Expected Behavior
In Cucumber 1.3.20 the correct JSON output is given, I've cut out the important pieces:
Feature: This is line 1

  Scenario Outline: This is line 3
    Given this step is line 4
    When when this step uses "<outline-item>" this should be line 5
    Then this is line 6
    Examples:
      | outline-item   |
      | example-line-9 |

cucumber --f json >> output.json

[
  {
    "keyword": "Feature",
    "name": "This is line 1",
    "line": 1,
    "elements": [
      {
        "keyword": "Scenario Outline",
        "name": "This is line 3",
        "line": 9,
        "steps": [
          {
            "keyword": "Given ",
            "name": "this step is line 4",
            "line": 4 # <---
          },
          {
            "keyword": "When ",
            "name": "when this step uses \"example-line-9\" this should be line 5",
            "line": 5 # <---
          },
          {
            "keyword": "Then ",
            "name": "this is line 6",
            "line": 6 # <---
          }
        ]
      }
    ]
  }
]

Note how the step line numbers are the same as the actual line number of the step.
Current Behavior
In cucumber 2.4.0 the following JSON output is given:
[
  {
    "uri": "features/outline_test.feature",
    "id": "this-is-line-1",
    "keyword": "Feature",
    "name": "This is line 1",
    "description": "",
    "line": 1,
    "elements": [
      {
        "id": "this-is-line-1;this-is-line-3;;2",
        "keyword": "Scenario Outline",
        "name": "This is line 3",
        "description": "",
        "line": 9, # <--- This is correct, it refers to the line number of the example
        "type": "scenario",
        "steps": [
          {
            "keyword": "Given ",
            "name": "this step is line 4",
            "line": 9 # <--- Should be line 4
          },
          {
            "keyword": "When ",
            "name": "when this step uses \"example-line-9\" this should be line 5",
            "line": 9 # <--- Should be line 5
          },
          {
            "keyword": "Then ",
            "name": "this is line 6",
            "line": 9 # <--- Should be line 6
          }
        ],
      }
    ]
  }
]

Context & Motivation
This issue has affected us at spriteCloud in the following way:

We run Cucumber and screenshots are saved on the server it ran on.
Then the screenshots are exported to the results database
Before exporting, the file is linked to the step where the screenshot was taken
This is going fine with regular Scenario's, but when it is an Outline we're not able to link the screenshot to the step and thus we can't visualize the given error.

Your Environment

Version used: Cucumber 2.4.0
Operating System and version: Windows 10, Ubuntu 16 and other linux systems.
Link to your project: http://calliope.pro

I've already found the issue and created a fix locally. I'll commit a pull request shortly.

I don't think this issue belongs here, since the JSON formatter is implemented in the Cucumber-Ruby project and its spec is also there - therefore issues and discussions about its behaviour should be kept there. Some issues might be fixed by a change here, but issues here in Cucumber-Ruby-Core should use the concepts defined here, rather than for instance formatters of Cucumber-Ruby.
Yes, the behaviour was changed in Cucmber-Ruby v2.0.0 (I do not know how conscious the change was), but both behaviours is equally right and equally wrong. The step executed is not the step of the scenario outline, but an instantiated/expanded step based on the step of the scenario outline - instantiated/expanded with the use of the data of the example row. The newer version of Gherkin get it really right by using multiple locations for compiled steps from scenario outlines (both the line of the scenario outline step and the example row are associated with the compiled step). Similarly in Cucumber-Ruvy >v2.0.0 both the scenario outline step and the instantiate/expanded step are included in error backtraces example:
  features/step_definitions/steps.rb:4:in `/^this step fails$/'
  features/outline.feature:9:in `Given this step fails'
  features/outline.feature:4:in `Given this step <status>'

As using one line is not really correct, regardless of which of the line of the scenario outline step or the
line of the example row is chosen, I undecided about what I think the behaviour should be.

Thanks for your input @brasmusson please feel free to move the ticket to Cucumber-ruby, I'm not familiar with your processes.
I understand that this is a difficult matter as in the depth that the issue is in and how it could break existing cucumber projects, however, I do not feel it's equally wrong or right. From my point of view, the data that we're working with is a crude form of a database, and thus it should apply to the standards of a database. The most important rule in databases is that in every Row of data should have a unique ID. In our case, the Line number + File creates this uniqueness. With Steps not having a Line number, it isn't unique and so it can't be used as data.
I understand if this change won't be added to Cucumber 2.x, but I hope you will consider implementing it in the upcoming Cucumber 3.

the Line number + File creates this uniqueness

3  Scenario Outline:
4    Given <x>
 ...
9    Examples
10  |      x        |
11  | one thing     |
12  | another thing |

Using <path/file.feature>:4 as id for both Given one thing and Given another thing is misleading at best, they are very different steps that could well be match to different step definitions. <path/file.feature>:4,11 for Given one thing and <path/file.feature>:4,12 for Given another thing on the other hand gives the complete picture.

I agree @brasmusson, if steps would get an id attribute like a feature and feature-elements, then the value should contain both the step and the example-row line number.
But in the case of the line attribute, I keep to my opinion that it should contain only the line number of the step location.
Anyway, what do you ought the chance of this being implemented?

Haven't had time to look into the discussed solution. But it's still on the to-do list. Feel free to assign to me.


Up arrow key does not work in bash.exe

Running 1.0.0, starting hyper, then starting bash.exe with no other changes or configurations, the up arrow key does not work out of the box. This is on Windows 10 version 1607.

Not only up but all arrow keys.
This issue is very common among console emulators on Windows.
See https://conemu.github.io/en/BashOnWindows.html#some-techinfo

@mqudsi this is an issue with Bash on Windows https://github.com/Microsoft/BashOnWindows/issues/111.
@CodeTheory

For the time being I'm using history plus !-1 (to run the last command) or !106 (to run e.g. the 106th command), but looking forward to a fix from the BOW team!

Ctrl+x doesn't work eather (could not exit nano).

@warpdesign you can use Ctrl+Shift+x to exit.

@stefanivic, @Tyriar from the VSCode team is also watching this issue. Maybe both teams can combine efforts?
@Maximus5 of ConEmu was able to develop a solution by translating "native keypresses into Xterm compatible keypresses" is it something relevant to Hyper and worth looking into?

@stereokai I'm actually in the process of updating https://github.com/Tyriar/pty.js to use<EMAIL_ADDRESS>which appears to have fixed this issue: https://github.com/rprichard/winpty/releases
Stay tuned: https://github.com/Tyriar/pty.js/issues/10

That rocks. I hope it ends up working!

Updating pty.js may resolve #1174 and #1180 as well, please keep us informed.

Yes I'm hoping it will fix some other random Windows issues such as these https://github.com/Microsoft/vscode/issues/14613, it's hard to know until it's done though.

Just wanted to see if you had any luck resolving the arrow issues?
Would love to start using Hyper for my WSL setup.

@jcolesio should be fixed when node-pty is upgraded to 0.6.0.

Until then you can use mintty/wsltty
shell: 'C:\\Users\\%USERNAME%\\AppData\\Local\\wsltty\\bin\\wslbridge.exe',
shellArgs: ['-t', '-C~', '/bin/zsh'],

Replace %USERNAME% with ours as hyper doesn't resolve env variables (yet). Omit the last argument if you use bash instead of zsh.

Where do I make the following modification?
Thanks
Sent from my iPhone
On Jan 22, 2017, at 4:31 AM, Michael Scherer <notifications<EMAIL_ADDRESS>wrote:
Until then you can use mintty/wslttyhttps://github.com/mintty/wsltty/releases
shell: 'C:\Users\%USERNAME%\AppData\Local\wsltty\bin\wslbridge.exe',
shellArgs: ['-t', '-C~', '/bin/zsh'],
Replace %USERNAME% with ours as hyper doesn't resolve env variables (yet). Omit the last argument if you use bash instead of zsh.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/zeit/hyper/issues/1127#issuecomment-274322582, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AERc7PS8KUT2250PxfKx2yBozmtuN3ogks5rUy_dgaJpZM4LK3Md.

@jcolesio the shell: ..., shellArgs: ... arguments are set inside hyper settings file.

Thanks guys, worked perfectly!

Do you guys have any issues with WSL in hyper that when deleting things from the command line it retains some old characters depending how much I am deleting from the command line?

Yeah, I also have it echoing back my commands before the output of each.

This seems fixed, using Windows Insider 15049 and Hyper 1.2.1. Also reported working on 15042: https://github.com/davatron5000/can-i-subsystem-it/pull/4#issuecomment-283368241

Indeed @nolanlawson, it's fixed – I forgot to close 😅 Thank you 🙌

Btw, huge props to @Tyriar :1st_place_medal:

:tada:

@nolanlawson @matheuss @Tyriar
That's weird. I've had it working since version 1,2,0, and I'm on Windows 10 14393.693 - I'm not an insider.

@stereokai it would have been fixed in a Hyper version, not Windows.

@Tyriar I wrote that because 4 days ago @nolanlawson specified his Windows version (recent build from Windows Insider Program), so I thought he meant there was a fix implemented in the Windows build he's on.

This seems fixed, using Windows Insider 15049 and Hyper 1.2.1. Also reported working on 15042:
davatron5000/can-i-subsystem-it#4 (comment)


[feature] User account merging

Ready for review.
Note that the additions to language.py should be reviewed and probably edited.

Fixture for generating users to test: https://gist.github.com/lyndsysimon/9a75f96ded03934f13d6#file-account_merge-py
:warning: WARNING: This script will remove all nodes  and users from your database.

Pass finished. :japan:

The account I am trying to merge with my main account was confirmed and has one project with one component and 0 addons associated with the account.
It would not merge.

@lyndsysimon @sloria .... The desired behavior is that my current account that I will be merging another account into is allowed to have addons.  The account that I am merging from is the one that should not have addons enabled.
So, my regular account with 10 projects and several addons will be able to accept account two which is confirmed and may have a project associated with it BUT NO ADDONS.


Inserting identical BaseDocument to VertexCollection returns (misleading) 404

My Environment

ArangoDB Version:        3.4.0 (Community edition)
Storage Engine:             MMFiles
Deployment Mode:       Single Server
Deployment Strategy:   ArangoDB/HomeBrew Service Starter
Configuration:               N/A
Infrastructure:               N/A
Operating System:        MacOS 10.14.1
Total RAM in your machine:       32 GB
Disks in use:        HDD
Used Package:          HomeBrew distribution
Client Library:  Java Driver (Synchronous) 5.0.4

Steps to reproduce
(See code to reproduce below.)

Create a graph
Add a vertex collection to the graph
Create a BaseDocument (with a self-provided key)
Insert BaseDocument
Attempt to insert the same BaseDocument again
The following exception is thrown: com.arangodb.ArangoDBException: Response: 404, Error: 1202 - document not found

Problem:
A 404 (Document Not Found) is slightly misleading if you're trying to insert a document which already exists.
Expected result:
Maybe 409 (Conflict) - A document with this ID already exists or something similar.
import com.arangodb.*;
import com.arangodb.entity.BaseDocument;
import com.arangodb.model.GraphCreateOptions;

import java.util.ArrayList;
import java.util.UUID;

// #########################################################
// Tested with arangodb-java-driver 5.0.4 and ArangoDB 3.4.0
// #########################################################
public class Main {

    public static void main(String[] args) {

        String DATABASE_NAME = "test_db1";
        String GRAPH_NAME = "test_graph";
        String VERTEX_COLLECTION_NAME = "test_vertices";

        try {
            ArangoDB connectionBuilder = new ArangoDB.Builder()
                    .build();

            ArangoDatabase db = connectionBuilder.db(DATABASE_NAME);
            ArangoGraph graph = db.graph(GRAPH_NAME);

            if (!graph.exists()) {
                db.createGraph(GRAPH_NAME, new ArrayList<>(), new GraphCreateOptions());
            }
            if (!graph.getVertexCollections().contains(VERTEX_COLLECTION_NAME)) {
                graph.addVertexCollection(VERTEX_COLLECTION_NAME);
            }
            ArangoVertexCollection vertexCollection = graph.vertexCollection(VERTEX_COLLECTION_NAME);

            // #########################################################
            // Create a new BaseDocument
            // #########################################################
            UUID uuid = UUID.randomUUID();
            BaseDocument bd = new BaseDocument();
            bd.setKey(uuid.toString());
            bd.addAttribute("name", "Paul");

            // #########################################################
            // Attempt to insert the same BaseDocument twice
            // Expected outcome:
            //   com.arangodb.ArangoDBException: Response: 404, Error: 1202 - document not found
            // #########################################################
            for (int i = 0; i < 2; i++) {
                System.out.println("Attempting to insert BaseDocument " + uuid);
                vertexCollection.insertVertex(bd);
                System.out.println("BaseDocument was inserted");
            }
        } catch (Exception ade) {
            ade.printStackTrace();
        }

    }
}

Hi,
We tested here and verified that the problem persists in version 3.4.2
Another thing we checked out was direct testing on the REST API, and same problem.
We noticed that the problem also occurs with Edge if there is a field with a unique index.

Error Message 1202 and Error Code 404 are the result of the rest call.

Inserting a vertex and inserting an edge violating a unique constraint is tested here:
https://github.com/arangodb/arangodb-java-driver/blob/583568a363ac9d40336997e0c97aa38ebb100563/src/test/java/com/arangodb/ArangoEdgeCollectionTest.java#L133
and
https://github.com/arangodb/arangodb-java-driver/blob/ae671ea616c8c447507d1d337a6c990f4be677ab/src/test/java/com/arangodb/ArangoVertexCollectionTest.java#L100
Tests are successful for ArangoDB versions 3.5+ and since ArangoDB 3.4 has reached EOL I am closing this issue.
Please feel free to open a new issue if you still encounter similar problems after upgrading the DB.


RSSI

oooo, an update from someone ! .. that's a first for me.
Have to bare with me when it comes to github, github I don't really know how to use.


cache.SetIfNotExist 返回错误

1. What version of Go and system type/arch are you using?
go version go1.13.4 darwin/amd64
2. What version of GoFrame are you using?
github.com/gogf/gf v1.10.0
3. Can this issue be reproduced with the latest release?
yes
4. What did you do?
	cache := gcache.New()
	cacheKey := "thisisakey"
	glog.Println(gf.VERSION)
	//v1.9.10

	glog.Println(cache.SetIfNotExist(cacheKey, "test", 1000))
	//2019-12-13 15:32:15.483 true
	time.Sleep(time.Second * 1)
	glog.Println(cache.SetIfNotExist(cacheKey, "test", 1000))
	//2019-12-13 15:32:16.488 false
	time.Sleep(time.Second * 2)
	glog.Println(cache.SetIfNotExist(cacheKey, "test", 1000))
	//2019-12-13 15:32:18.489 false

5. What did you expect to see?
if the cache key is expire,should return true when use SetIfNotExist
6. What did you see instead?
return false

go-demo 中使用的是1000数值型的，修改成1000*time.Microsecond就正常了


chore(ui): remove all todo comments and unwanted types

Describe your changes :

I worked on the cleaning up UI codes and remove TODOs

Type of change :

[x] Cleanup

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

@Sachin-chaurasiya @ShaileshParmar11 have address your comments please check once you have time


fix : remove invalid rating

Please do not merge this PR.

First pull from testing to your branch and then make changes to the ratings option.

The word cloud doesn’t seem to exist in the rendered html on my end

On local it is ok not to render. But I would suggest is close this PR without merging.
Open a new PR from a new branch out of testing branch. Make your changes in that branch.

I think the changes should be fine in this branch @rrrohit1


feat: existing scc instance support

Description

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

Created a PR to support existing scc instance in module

/run pipeline

Name in output will be null, when using existing instance, is that okay? If not we will need data block to fetch it
output "scc_name" {
  description = "SCC instance name"
  value       = var.existing_scc_instance_crn == null ? module.scc[0].name : null
}

@Soaib024 lets add the data lookup - no harm. Then we can update to get the values from there. Assume data lookup can be done on the CRN?

/run pipeline

/run pipeline

@Soaib024 lets add the data lookup - no harm. Then we can update to get the values from there. Assume data lookup can be done on the CRN?

@ocofaigh I have added data look up to fetch the existing instance from guid

/run pipeline

:tada: This issue has been resolved in version 1.14.0 :tada:
The release is available on:

GitHub release
v1.14.0

Your semantic-release bot :package::rocket:

@jor2 yea we should of put it there but just for ordering - it will still appear in the DA inputs, but not in any order. Do you want to create an issue to add it please?

@jor2 yea we should of put it there but just for ordering - it will still appear in the DA inputs, but not in any order. Do you want to create an issue to add it please?

https://github.ibm.com/GoldenEye/issues/issues/10237


Code cleanup

Regarding GIScience/orstools-qgis-plugin@8b243b8 - reformatting should be done after this by an automated tool, see #141.
In addition, the  .ui and …UI.py-files are auto-generated by qt designer and pyuic5, so reformatting them might actually make following changes less readable, since regenerating will overwrite the formatting.

Regarding 8b243b8 - reformatting should be done after this by an automated tool, see #141.
In addition, the .ui and …UI.py-files are auto-generated by qt designer and pyuic5, so reformatting them might actually make following changes less readable, since regenerating will overwrite the formatting.

removed the reformatting commit

Looks good to me :)


few dropdowns on the page

I have a few dropdowns on the page, and I want to have a few dropdowns openly, and that others dont close, how can I do this?

solution: http://f4.s.qip.ru/Ha2NUeB3.png


Lazy initialise the worker pool

Depends on https://github.com/home-assistant/home-assistant/pull/4108 to fix failing tests.
This will lazy initialise the worker pool. This should make startup slightly faster, including for our tests 💃

Python 3.4 tests are currently broken 😢

All fixed 🎉


Update IBM Cloud Container Service (IKS) k8s setup instructions

Copy IKS specific instructions from https://github.com/istio/istio.github.io/pull/1072 to general k8s setup page.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
Assign the PR to them by writing /assign  in a comment when ready.
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

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

fyi @linsun @gyliu513

Thank you @ayj /LGTM


_SysFatalErrorHandler not working properly for arc on quark_se_c1000_ss_devboard

The test tests/kernel/mem_protect/stackprot/ hangs after reporting "Stack Check Fail".
Arch: arc
Board: quark_se_c1000_ss_devboard
Zephyr tag:  v1.12.0-rc2 - commit d93ecda4c590d674e1cccdc65fb3501ae80a2055.
Actual Console Log:
***** Booting Zephyr OS v1.12.0-rc2 *****
Starts alternate_thread
alternate_thread: Input string is too long and stack overflowed!

***** Stack Check Fail! *****
Current thread ID = 0xa8000400

Expected Console Log:
***** Booting Zephyr OS v1.12.0-rc2 *****
Starts alternate_thread
alternate_thread: Input string is too long and stack overflowed!

***** Stack Check Fail! *****
Current thread ID = 0xa8007000
eax: 0x00000000, ebx: 0xa8007954, ecx: 0x00000000, edx: 0x0004dd6a
esi: 0x400330dc, edi: 0x4003038a, ebp: 0xa800794c, esp: 0xa8007944
eflags: 0x00000246 cs: 0x0008
eip: 0x40032eb3
Fatal fault in thread 0xa8007000! Aborting.
Running test suite stackprot
===================================================================
starting test - test_stackprot
test_stackprot: Stack ok
test_stackprot: Stack ok
test_stackprot: Stack ok
test_stackprot: Stack ok
test_stackprot: Stack ok
test_stackprot: Stack ok
PASS - test_stackprot
===================================================================
===================================================================
PROJECT EXECUTION SUCCESSFUL

Tried further debugging, the test hangs in _SysFatalErrorHandler function in the file "arch\arc\core\fatal.c".
Steps to reproduce:
**For running stackprot application on the ARC side of quark_c1000:**
cd zephyr.git/tests/kernel/mem_protect/stackprot/
rm -rf build && mkdir build && cd build
cmake -D BOARD=quark_se_c1000_ss_devboard ../
make BOARD=quark_se_c1000_ss_devboard flash

**Additionally, flash the boot stub to enable messages from the ARC processor:**
cd zephyr.git/tests/booting/stub
mkdir build && cd build
cmake -D BOARD=quark_se_c1000_devboard  ../
make BOARD=quark_se_c1000_devboard  flash

Check the console log.

@vonhust can you take a look?

Tried further debugging, the test hangs in _SysFatalErrorHandler function in the file
"arch\x86\core\fatal.c".

The fatal error handling for ARC changed, so there could indeed be a problem.
However, the comment is about hanging in x86 fatal.c
Can you confirm this is about ARC and not Quark? Could it be some interaction between the two processors?

We're supposed to get some kind of fault for the stack overflow but it's just hanging on ARC.
He gave expected output on x86 as an example.
I don't think we even turn on the MPU on the ARC processor on arduino 101 so I think we have a regression with how the stack guard registers are set, or possibly how exceptions are handled.

The fatal error handling for ARC changed, so there could indeed be a problem.
However, the comment is about hanging in x86 fatal.c
Can you confirm this is about ARC and not Quark? Could it be some interaction between the two processors?

Sorry, my mistake. I was trying to compare the arc/arm/x86 implementation in fatal.c and wrote "x86" by mistake. The test hangs in _SysFatalErrorHandler function in the file "arch\arc\core\fatal.c".

ARC commit 8da51ee and 3d9ba10 changed the behavior of the default sys_fatal_error_handler to hang the system instead of killing the task and continue. Behavior is not consistent over different architectures, there is an #ifdef that enables the hang for stack errors, but conditions for the #ifdef are different. Bit strange since the error that is triggered is in all cases the same.
My recommendation would be to stick with the conservative 'hang' behavior for all stack errors independent of the cause (sentinel, canary, hw bounds check, MPU, ...), and change tests to overrule the default handler.
@andrewboie @agross-linaro : any other opinions?

commit 5d58f0f allows the HW stack checking to be non-fatal in the ARC default sys_fatal_handler, so this test passes again (continue after killing the offending task).
Still, not sure this is the default behavior that we want...

Still, not sure this is the default behavior that we want...

@ruuddw can you open a new issue about default behaviour (enhancement) so we can address that for 1.13?

@ruuddw can you open a new issue about default behaviour (enhancement) so we can address that for 1.13?

#8265 opened.


Initial commit: Add structure for repo

Since we had an offline conversation around having this repo as a library, I'm simply going to close this merge request and create another one for ease of reviews/discussion.
Thanks for the feedback @metalmatze :)


Bug/fix events

This PR should fix a few issues regarding the event system and focus:

https://github.com/react-navigation/hooks/issues/34
https://github.com/react-navigation/hooks/issues/6
https://github.com/react-navigation/hooks/issues/37
https://github.com/react-navigation/hooks/issues/21
https://github.com/react-navigation/hooks/issues/3

@satya164 if you want to take a glance tell me, otherwise I'm going to merge and release anyway because I've tested this on my app and works fine and is actually usable, compared to former implementation which has a lot of problems.

LGTM

Thanks for the review 😊 will release tomorrow
Le jeu. 29 août 2019 à 21:09, Brent Vatne<EMAIL_ADDRESS>a
écrit :

@brentvatne approved this pull request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/react-navigation/hooks/pull/38?email_source=notifications&email_token=AAFW6PUJ2K3GYR4GKZ47GL3QHANHFA5CNFSM4IR7RRL2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCDE6BEI#pullrequestreview-281665681,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFW6PX6CRAN22GG6JEE3KDQHANHFANCNFSM4IR7RRLQ
.


[Enhancement] Ability to set what is auto-revealed for monster when first added to bestiary

Generally, I like to provide monster name, type/level, saves, and lore on the first successful RK check. Would be great if you could specify what should be auto-revealed the first time a monster is added to the bestiary, so we then don't have to go through and manually reveal a bunch of things.

Good idea. Just have to figure out where I want to put this module setting 😁 👍

I just released v0.9.5. It adds this as a feature 🤖 ✌


Backslash doesn't work in elm files

When I try to enter a backslash '' it doesn't appear. This only happens in .elm files. If I switch the filetype of an .elm file to 'just text' it works again. So I guess it has something to do with the plugin.
I am using VS Code Version 1.12.2 and V0.13.0 of the elm plugin.
My operating system is MacOs 10.12.4

I found a solution for this myself. Apparently there was a default keybinding that I simply erased.


Can't play the next song if  the song of playing have url as the next song

-Reality  : If now playing and the next song have same url. when now playing is finished then playlist is change but next song is pause

Can play the next song if the song of playing have url as the next song :heavy_check_mark:


'Message of the day' not appropriate on beta? — should be deleted there

The message of the day (the text that appears above the search form) on t3 has been synced to live (beta) where I do not believe it is appropriate. In which case it should be deleted or modified to be appropriate for beta.

Might be needed on Beta to highlight changes in progress (e.g. "links to images are not working  at the moment, otherwise site is working as expected") to stop people pointing out that something known to be a problem is not working, or just assuming that we don't care that there is a problem on the site

Apologies — I put that badly: what I'm saying is that that particular message should not be on beta. I agree that the ability to create a message should exist, so I am proposing that we delete the message but not the container which is the file 'Message'.
The issue is that every time a sync is performed, the 'Message' file on beta will be updated with the contents of that same file on t3. We need a strategy to correct the contents after each sync or a way of excluding the file 'Message' from the sync process.
What happens on CEN and REG?

OK, I can confirm that the message has gone from test3. @Vino-S could please move this version to beta so we can test it there? Thanks.

Done: closing


Completely white background until window is resized

This seems to be an issue both in the release template executable, as well when running a clean install with "npm run dev", or in a built project packaged using a clean install of this project. The background stays completely white, ignoring the "backgroundMaterial: 'mica' or 'acryllic' attributes set on window creation. I have tried my best to find a fix for this issue, to no avail. I have replicated this issue on another machine running Windows 11 as well. Setting "frame: false" fixes the issue, although for most purposes having "frame: true" is important. Also launching the app on a secondary screen seems to fix the issue, for some reason. Although this isn't either a suitable solution to the problem. Doing something like "window.resizeBy(790,680);" works too, but again, not ideal.

I had this issue before, i can workaround it by removing a property at src/renderer/App.tsx:
<FluentProvider theme={theme} style={{ height: "100vh", background: "transparent" }}> to <FluentProvider theme={theme} style={{ height: "100vh"}}> should fix the issue

I also experience this issue from time to time. Sometimes it happens, sometimes not. I think it's an issue of electron's implementation of the backgroundMaterial effect on Windows. Sometimes it fixes the issue after resizing the window. See this bug report on the electron repository: https://github.com/electron/electron/issues/41072
@hydexon The transparent background is needed to see the backgroundMaterial effect (mica or acrylic). If you don't need the backgroundMaterial in your application you can remove the background: transparent and remove the backgroundMaterial: "mica" from here:
https://github.com/oliverschwendener/electron-fluent-ui/blob/ef7c461300b5ea82b8be942b410a1f6ad32ea9ab/src/main/index.ts#L7-L16


Fixes #555 Structuring nested object causes DataException

Fixes #555

Hi @ogawa-takeshi thanks for the contribution but I think there is a misunderstanding.
A map chan have only values of the same type.
Something like this:
{
                |       key1: {
                |           subKey1: "value",
                |           subKey2: "value"
                |       },
                |       key2: {
                |           subKey1: "value",
                |           subKey2: true
                |       }
                |   } AS nested,

I'm closing this for lack of feedback. Feel free to re-open


make peerIDs static for all nodes (andrew)

Debugging why the peer ids are not getting picked up

Debugging why the peer ids are not getting picked up


Relaunch scenario without saved progress

As a user I want to be able to relaunch a scenario I have already started without keeping the scenario progress. This allows me to complete a scenario several times or restart a scenario I think I might have messed up.
Currently the scenario progress is saved in progress.yaml and does not get overridden, even if the infrastructure is torn down and scenario is restarted
Expected behaviour
simulator scenario launch <scenario name> always resets the progress for that scenario, so I can restart a task.
Actual behaviour
simulator scenario launch <scenario name> followed by start_task 1 informs me I am already on task 1 if I have started this task before.

It may be worth adding a simulator scenario reset command for this purpose. If someone has to tear down their infra they want to continue a scenario from where they were when they spin it back up.


Create a sticky TDI session to reuse for multiple writes to pipeline

A performance improvement suggested and tested by IDC team

For the record:

I successfully built the code for ES2K using Bazel and ran the unit test suite.
The CI pipeline successfully built the code for DPDK using Bazel and ran the unit test suite.

The fact that the unit test suite ran successfully is not a strong indication of correctness. We do not have a unit test for the Node class.


Date decoder throws error if instance uses fractional seconds

This is related to writefreely/writefreely-swiftui-multiplatform#200 where, if the WriteFreely instance returns dates with fractional seconds (e.g., 2022-09-28T11:55:39.886581893Z), the date-decoding strategy fails and an error is thrown.
A potential solution has been added in a note to this comment in the Vapor repo.

Without doing more digging yet, I'm not sure why sub-second datetimes are being stored for these WriteFreely instances. But as mentioned in this SO answer, the Go JSON library will always output times according to RFC3339, with sub-seconds if they're present.
So while we wait for a fix in WF (and for it to be widely deployed), I definitely think the library should be able to handle this behavior, since it still adheres to the standard (although the behavior is undesired).

I've put together a quick PR for WF, but as you say it will take a while for it to be fully deployed. https://github.com/writefreely/writefreely/pull/585


prepare validation datasets

[ ] I9 dry
[ ] I12
[ ] AshleyDene
[ ] LnP

[ ] SWC over time (mean + std)
[ ] Biomass in shoot
[ ] Biomass in stem
[ ] LAI
[ ] Root
[ ] Phenology

Better to prepare the dataset as Xiumei's
New objective - leave the report untouched or talk to people about this.
Prepare the dataset of AD AND I12 in a format that it can be joined.

The test node prevented simulation to finish because NSE values were too low.

Time zone issue? apsim can't join them

the date caused the joining failed.
Manually edit the date into dd/mm/yyyy format made it work

Maybe PAWC is more relevant?


don't scan the specified directory recursively

the effect can be observed when using arangoimp for a file in i.e. ~, it will then recurse through the whole home.

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/6656/

only unrelated testfailures.