APK download?

Would you consider making the APK of your app available to those outside of Google's walled garden (without PlayStore access) – e.g. by tagging releases and attaching the APK there? Thanks in advance!

No problem, I'll do it.

Thanks a lot! Your app will then become available here with the next sync around 7 pm UTC today (updates will be checked for and retrieved within 24h of your making a new release and attaching the APK to it – users then will be notified via their F-Droid clients). Be welcome to pick a badge to accompany Google's in your Readme and link there :smiley:


unable to compile with org 0000h

I'm working in my z80 kernel and I can compile and run my software when org is > 0.
I got an error when org is 0. I think it should be linked to curAddr in file assembler.ts that it returns error when curAddr = 0
I suppose it should be linked to line 191.
if (curSymbol && curAddr) {

Yeah good catch. I think that if() needs to check that curAddr isn't NaN instead. I'll try to fix this in the couple of days.

Ok, this should be fixed in version 1.8.2 (currently verifying but should show up in a couple of minutes).
Thanks for the bug report!

Thanks! it is fixed


Vickel: Watch eldmandate.biz

Vickel requests the watch of the watch_keyword eldmandate\.biz. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

eldmandate\.biz has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Nick in Charcoal HQ


Updated Scheduling Docs to Include Kubernetes Constraints

Proposed changes
Fixes: https://github.com/docker/docker.github.io/issues/8321
Adding details on how to enable Kubernetes workloads to run on all node types.
Unreleased project version (optional)

Related issues (optional)

@axeal As it was your notes I "borrowed", do you mind taking a look? Thanks :)

Deploy preview for docsdocker ready!
Built with commit c62eb36fa392669d7646ab9ecf6441b31704c161
https://deploy-preview-8332--docsdocker.netlify.com

Good to go


[19.09] signal-desktop: 1.27.2 -> 1.27.3 (backport)

(cherry picked from commit 6f3b44baa4f446cd920a14eb7a2f1f3a54d45851)
Reason: Avoid an expired (unusable) release in the stable release
(Signal-Desktop releases expire after 90 days).

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Notify maintainers
cc @

@GrahamcOfBorg test signal-desktop


Tree shake suggestions?

Hello everyone, I am currently investigating the possibility of tree shaking. In that regard, I would like to see what you think of it, is it worth it, or if you have any better suggestions?
As you see, currently the picker exports a single component. Child components are imported depending on the mode you select, e.g. month-picker, year-picker, and so on. Even tho, the logic for each mode is scoped per mode, the menu components imports all components, and depending on the mode, it displays the needed one, meaning, that all of these components are going to be included in the single output.
I have created a blank vite app and tried different approaches.
Here is the build output based on the current state where the build app is ~250kB

The solution I came up with (the only one actually that worked) is to remove imports from the menu component and move it to the prop. Basically, you will pass a component that you want to use instead of a mode. Something like this:
From:  :month-picker=true to :mode="MonthPicker"
Using that approach, we can see that the same app size changes based on the mode used (some modes require less logic):
DatePicker

MonthPicker

TimePicker

YearPicker

The proposed change would look something like this
<template>
    <VueDatePicker :mode="DatePicker">
<template>

<script setup>
  import { VueDatePicker, DatePicker } from "@vuepic/vue-datepicker"
</script>

Would love to hear your thoughts.

Linking #479 as it was previously raised.

Close due to low interest, can be reopened in the feature.

I currently use 1 time the picker in my project, and it takes up to 12% of it in my bundle:

And date-fn is 50% of it, I would vote for explicit import if possible


use the plugin with javascript

How can I implement your plugin using only javascript and XML?

Is that what you need? https://github.com/Akylas/nativescript-canvas#xml
Exactly the same as any other plugin.


Vite Error: Unrestricted file system access ...

Hey there, thanks for creating this plugin. Exactly what I needed.
There is just an error on every dev-server startup that notifies me that this package will break in future vite versions because of file system access. The error message:
Unrestricted file system access to "/notes/function render(_ctx, _cache) {  return (_openBlock(), _createElementBlock("svg", _hoisted_1, _hoisted_3))}"
For security concerns, accessing files outside of serving allow list will be restricted by default in the future version of Vite. Refer to https://vitejs.dev/config/#server-fs-allow for more details.

Now everything works. But I guess this is not something to ignore.

Have to add something, it's only when I do
<img<EMAIL_ADDRESS>
directly, without import in JS.

Hi, thanks for reporting. I can't reproduce the message. Could you maybe share your project (or a test project), so I can investigate.

@jpkleemans  Thanks for your answer. If I use the plugin as the docs tell me to, everything works fine. It's just that direct <img<EMAIL_ADDRESS>does not work. Will close this :)


Get-SdnServiceFabricClusterManifest fails when calling back to itself

Describe the bug
Get-SdnServiceFabricClusterManifest fails when calling back to itself
To Reproduce
Steps to reproduce the behavior:

Connect to Network Controller and run Get-SdnServiceFabricClusterManifest which will fail

Expected behavior
Cluster Manifest should be returned back successfully.
Screenshots

Is this happening on a Cluster with X509 auth or Kerberos?

It's happening with how the invoke command is working and just a logic issue, not anything to do with actual authentication. Fix itself is easy and I will have a fix submitted early next week.

@luyaof not sure best method to proceed on this. Ultimately the issue happens when you do the following:

Connect to NC via PSRemoting from another node
Run the Get-SdnServiceFabricClusterManifest command, or any other SF cmdlet without specifying a NetworkController, or specify the NetworkController you are connected into
Error is received, because we cannot pass our current session credentials into a new one, not without specifying -Credential

To get around this problem, need to evaluate the following:

Update Invoke-SdnServiceFabricCommand to do either Invoke-Command or Invoke-Command -ComputerName / -Sesssion based on if NetworkController is local. This introduces other challenges, because SF requires us to use Connect-ServiceFabricCluster within the current runspace. All higher level commands passing through then would either need to add Connect-ServiceFabricCluster  before the command being executed, or get crafty on the -Arguments.
Add more defensive blocks by detecting if we connecting into the remote runspace and block operation entirely.

Open to ideas on this one.


Use python-oracledb instead of cx-oracle

Affected module
Does it impact the UI, backend or Ingestion Framework?
Ingestion Container Image
Describe the bug
Currently, Ingestion Container does not support Oracle Connector due to missing instant client libraries.
A potential fix to try out is swap usage of cx-oracle python library with python-oracledb.

https://oracle.github.io/python-oracledb/


collapse linkmenu on selecting link

Description
Link menu will be collapsed on selecting a link when the user configures the collapseOnClick property on link menu.
Overview of Changes
action drop component has an event listener on the child component links.
Type of Change

[ ] New feature

You did it @sandeepmantha!
Thank you for signing the Anthem Opensource Software CLA.


add health check endpoint (/)

We currently check the hypernova process by pid, but sometimes hypernova does not work even if the process lives.
This PR mount / as a health check endpoint to check the server is working or not.
What do you think of it?

the hypernova function returns the express app object, so you could just add additional endpoints there
fwiw this is what I also do. this does tie us to an implementation detail of hypernova though, so I'm +1 for a built in healthcheck option if it's useful to more people?

I think this should be at the discretion of the user. You can currently do this by:
hypernova(hypernovaOptions, (app) => {
  app.get('/health', (req, res) => res.send(Date.now()))
})

Thanks, everyone. I agree with @goatslacker, "different folks will have different requirements".
I hope README.md shows how to add health check endpoints, which seems the best way on it.


Use StandardJS.

I think StandardJS is best standard for NodeJS, so if you agree I will can change this code to SJS.

I 100% agree with StandardJS, but you certainly don't have to go through the trouble.
I wrote this package quite a while ago, and it needs a once over. There's a development branch in the works, (it's been Idle for a while, but as coincidence would have it I need to update this package for work)
The rewrite will be SJS compliant!


Upgrade to foundation-sites 6.3.1

This is to update the gem to the latest released version. foundation-sites 6.3.1

This fix actually does pass tests however Travis is failing due to https://github.com/zurb/foundation-rails/issues/220

Hey @kball, Was wondering if it is possible to get this in soon.

We would like to get this version too.  There are some bugs on mobile devices that 6.3.1 will fix for us.

Sorry for the delay on this - merged and published!


Updated Helm version and change priority value for jobs

Issue #, if available: #4
Description of changes:
Updated the helm version to incorporate latest change of the Galaxy Helm Chart, exposing the value for the priority class: https://github.com/galaxyproject/galaxy-helm/commit/adfda49ac7a7ca6c9598dd73a39c9feb99cef76b
Setting this value to 1000 by default. Kubernetes currently does not support the updating of the priority value for an existing priority class. Thus it is not configurable via cdk.json.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Review done by gbabis.


Suboptimal Handling of Road Access

I don't know how much you can do about it, but I noticed some weird behavior when bike-routing from or to areas with private but bike-accessible paths and roads (e.g. at Hans-Dickmann-Kolleg, Karlsruhe).

I'd suggest to use more details from the osm tags and maybe allow otherwise forbidden roads if a waypoint is placed on them, potentially with a warning.

Hi @McLP2,
these are issues with handeling access of our openrouteservice backend and can't be fixed in the client.
access=no or access=private currently can't be used.
Best look at the existing ones before you open an other one there, but feel free to add info if you think it's missing


useFlagsStatus always returns false for flagsReady

Describe the bug
Hello! We recently upgraded from 3.4.0 to 3.5.0, and noticed that for some reason our feature toggles aren't working when running locally. We have a wrapper hook with the following line:
const { flagsReady, flagsError } = useFlagsStatus()

Previously flagsReady would come back as true if everything is fine, but now it only seems to be false. It's not obvious to me why though, as the 3.5.0 release only appears to contain dependency upgrades. But if I downgrade to 3.4.0 and don't change anything else, it works fine as usual. I also tried the v3.5.0-beta.0 release and found the same issue.
Strangely, it does seem to work fine in our staging deployment. But we've tried on two different machines and found the same thing.
Subscription type
Open source
Hosting type
Self-hosted

Hi @matt2112 👋
Thanks for sharing the bug. It is odd that is works on staging, and not otherwise. Since you were able to make it work on two different machines, can you share the steps to reproduce this?

Hi @pransh15 👋  Steps are just:

Insert const { flagsReady } = useFlagsStatus() anywhere and log flagsReady, always false.
Stop dev server.
Run yarn add<EMAIL_ADDRESS>Change nothing else and restart dev server.
Log flagsReady, always true.
Stop dev server.
Run yarn add<EMAIL_ADDRESS>Change nothing else and restart dev server.
Log flagsReady, back to always being false.

To clarify, I mean we've replicated the bug on two different machines. If it's relevant, this is with React 18.2.0 and Next 12.3.3.

I can confirm this behavior as well. here is a simple reproduction
export function TestFlags() {
  const { flagsReady, flagsError } = useFlagsStatus();

  if (!flagsReady) return
loading
;

  return
done
;
}

ReactDOM.createRoot(document.getElementById('root') as HTMLElement).render(
  <React.StrictMode>
      <FlagProvider config={config}>
        <TestFlags />
      </FlagProvider>
  </React.StrictMode>,
);

Thanks for sharing, @matt2112 and @clouddra 👍
Let me try and reproduce in some time and get back to you! 😄

Thanks for fixing this @Tymek, much appreciated! Can confirm it now works as expected 🎉


fix: bump to fastify 5 and resolve vulnerabilities

Nothing that was used other than customLogger https://fastify.dev/docs/latest/Guides/Migration-Guide-V5/


command not found

Hello, I'm trying to run porcupine_demo_mic --keywords picovoice after installation with pip3 install pvporcupine, the installation seems to run fine with no errors, I get a successfully installed pvporcupine-1.8.7 on a raspberry pi.
Expected behaviour
Actual behaviour
bash porcupine_demo_mic: command not found
Steps to reproduce the behaviour
Include enough details so that the issue can be reproduced independently.

pip3 list shows pvporcupine as an installed package.

you installed the engine package and not the demo. Please follow this:
https://github.com/Picovoice/porcupine/tree/master/demo/python#installation

ah yes, I see, thanks++ got it

I have run this command pip3 install pvporcupinedemo but porcupine_demo_mic --keywords porcupine this giving error porcupine_demo_mic --keywords porcupine please explain @kenarsa


changed to / cc/ bcc selectors to 'input[name=bcc]' instead of textarea

The current selectors catch the textarea where the user types new email addresses. The existing and fully typed email addresses belong to the input element with the same name.

I'm not sure this change is safe to be honest.
input seems to target the underlying data-layer of the dialog (which at some points may be correct), while textarea seems to target the area visible to the user.
Please note these selectors are used for both retrieving and setting data, so while this may work to obtain info from an compose-instance, it may not produce the expected UI-results when using it for setting values.
See the following code where these selectors are used:
https://github.com/KartikTalwar/gmail.js/blob/b610092b96122f2efaad65884cd08fe9117b68d2/src/gmail.js#L3790-L3827

Consider the following use-case. I've crafted this email:

Using the input selector will obtain the right address, but it won't replace the existing email when setting:

After this, the email still looks the same:


File transfer

Implement a file transfer mechanism to allow one (or both) peer(s) to transfer a file to the other once successfully hole punched to each other

[ ] One peer can transfer a file to the other
[ ] (Optional) Both Peers can transfer files to the other
[ ] (Optional) Works in both TCP and UDP

completed in commit eb75ddeca9edc80abf0ef53a7633b3d2c463646b


[Display News, List View] Incorrect display of Title with 4 rows

Environment: Windows 10 Pro, Mozilla Firefox 82.0.3 (64-біт)
Microsoft Windows 10 Home, Version 10.0.19041
Google Chrome Version 86.0.4240.198 (Official Build) (64-bit)
Reproducible: always
Build found: 20.11.2020
Preconditions

https://ita-social-projects.github.io/GreenCityClient/ is opened.
News items are created in the DB and are displayed as first news item in the list view. Use queries:
INSERT INTO eco_news
(ID, title, text, author_id, creation_date)
VALUES (708, 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim ven',
'Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure d',
857, '<current date and time in format e.g. "2020-05-17 10:00:00.000000">');

INSERT INTO eco_news_tags
(eco_news_id, tags_id)
VALUES (708, 1), (708, 3);
Steps to reproduce

Go to GreenCity https://ita-social-projects.github.io/GreenCityClient/#/welcome
Click on 'Eco news' link in the header.
Set browser window width to 1024px.
Click on the View as a List option on the right side of the page.
Pay attention to created news Title and Description display.

Actual result

Title is displayed and consists of 4 rows and has 104px in height In Mozilla, Title is displayed and consists of 4 rows and has 102px in height in Chrome, No description is shown.
Title content is placed out of the frame.

Expected result

Title is displayed and consists of 4 rows and has 128px in height. No description is shown.
Title content is placed inside of the frame.

Postconditions
Created news are deleted from DB using queries:
DELETE FROM eco_news_tags
WHERE eco_news_id = 708;
DELETE FROM eco_news
WHERE id = 708;
User story and test case links
User story #460
Test case

hiiiii
can you check this again? please )

Hi, the title now is placed within the frame, but problem with the size still exists. In addition the row with author and date now overlaid with 'Title' field.

The test data given above is designed to test 4 row title. Now the results show 2 row title.

how can i put a 4 line header there?
see design for 1024px

Hello! I am not sure what do you mean by this image and "4 line header". We have user story #460 with the guidelines that are shown on mock-up for different title heights (including 4 row title). If 4 row  title is not possible to implement we should discuss this at the meeting.

Hello! I am not sure what do you mean by this image and "4 line header". We have user story #460 with the guidelines that are shown on mock-up for different title heights (including 4 row title). If 4 row  title is not possible to implement we should discuss this at the meeting.

I might have used a confusing image for you, because there is some data highlighted with DevTool. The point was that the title has 2 rows, althought with such test data 4 rows should have been shown.

I might have used a confusing image for you, because there is some data highlighted with DevTool. The point was that the title has 2 rows, althought with such test data 4 rows should have been shown.

defect is  fixed partly
Not fixed is the next disparity:

size of tittle is 61252 (Chrome), 61278 (Mozila) (See attachments) - expected result is 613*53

Title is displayed and consists of 4 rows and has 104px in height In Mozilla, and "eco news date text"  is placed out of the frame. (see attachment)

defect is  fixed partly
Not fixed is the next disparity:

size of tittle is 61252 (Chrome), 61278 (Mozila) (See attachments) - expected result is 613*53

Title is displayed and consists of 4 rows and has 104px in height In Mozilla, and "eco news date text"  is placed out of the frame. (see attachment)

Actual result:
Title is displayed and consists of 4 rows and is 104px in height.

Expected result:
Expected result:
Title is displayed and consists of 4 rows and is 128px in height.

User story #460


Federation: Generalized Cluster Selection and Weighting

Description
Many of the existing (v1.4) federated API objects are by default scheduled across all underlying clusters (e.g. federated services, namespaces, secrets, ingress...).  Federated replicasets support a set of alpha annotations by which the user can influence replica placement.  This alpha concept is extended to a fully supported API for scheduling entities across multiple clusters and cloud providers.
Progress Tracker

[ ] Before Alpha

[ ] Write and maintain draft quality doc

[ ] During development keep a doc up-to-date about the desired experience of the feature and how someone can try the feature in its current state. Think of it as the README of your new feature and a skeleton for the docs to be written before the Kubernetes release. Paste link to Google Doc: DOC-LINK

[ ] Design Approval

[ ] Design Proposal.  This goes under docs/proposals.  Doing a proposal as a PR allows line-by-line commenting from community, and creates the basis for later design documentation.  Paste link to merged design proposal here: PROPOSAL-NUMBER
[ ] Initial API review (if API).  Maybe same PR as design doc. PR-NUMBER

Any code that changes an API (/pkg/apis/...)
cc @kubernetes/api

[ ] Identify shepherd (your SIG lead and/or<EMAIL_ADDRESS>will be able to help you). My Shepherd is<EMAIL_ADDRESS>(and/or GH Handle)

A shepherd is an individual who will help acquaint you with the process of getting your feature into the repo, identify reviewers and provide feedback on the feature. They are not (necessarily) the code reviewer of the feature, or tech lead for the area.
The shepherd is not responsible for showing up to Kubernetes-PM meetings and/or communicating if the feature is on-track to make the release goals. That is still your responsibility.

[ ] Identify secondary/backup contact point. My Secondary Contact Point is<EMAIL_ADDRESS>(and/or GH Handle)

[ ] Write (code + tests + docs) then get them merged.  ALL-PR-NUMBERS

[ ] Code needs to be disabled by default.   Verified by code OWNERS
[ ] Minimal testing
[ ] Minimal docs

cc @kubernetes/docs on docs PR
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
New apis: Glossary Section Item in the docs repo: kubernetes/kubernetes.github.io

[ ] Update release notes

[ ] Before Beta

[ ] Testing is sufficient for beta
[ ] User docs with tutorials
- Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
- cc @kubernetes/docs on docs PR
- cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
[ ] Thorough API review

cc @kubernetes/api

[ ] Before Stable

[ ] docs/proposals/foo.md moved to docs/design/foo.md
- cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
[ ] Soak, load testing
[ ] detailed user docs and examples

cc @kubernetes/docs
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

FEATURE_STATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers.
FEATURE_STATUS: IN_DEVELOPMENT
More advice:
Design

Once you get LGTM from a @kubernetes/feature-reviewers member, you can check this checkbox, and the reviewer will apply the "design-complete" label.

Coding

Use as many PRs as you need.  Write tests in the same or different PRs, as is convenient for you.
As each PR is merged, add a comment to this issue referencing the PRs.  Code goes in the http://github.com/kubernetes/kubernetes repository,
and sometimes http://github.com/kubernetes/contrib, or other repos.
When you are done with the code, apply the "code-complete" label.
When the feature has user docs, please add a comment mentioning @kubernetes/feature-reviewers and they will
check that the code matches the proposed feature and design, and that everything is done, and that there is adequate
testing.  They won't do detailed code review: that already happened when your PRs were reviewed.
When that is done, you can check this box and the reviewer will apply the "code-complete" label.

Docs

[ ] Write user docs and get them merged in.
User docs go into http://github.com/kubernetes/kubernetes.github.io.
When the feature has user docs, please add a comment mentioning @kubernetes/docs.
When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.

@quinton-hoole @kubernetes/sig-cluster-federation can you clarify the actual status of the feature?
Also could you provide with the design document?

@marun Has the beginnings of a design proposal for this.  Reassigning to him.  I believe that there is a plan to get this to alpha in v1.7.  Labelling accordingly.

ref/ https://github.com/kubernetes/kubernetes/issues/39982

@marun I've updated the feature description to fit the new template. Please, fill the empty fields in the new template (their actual state was unclear).

@madhusudancs @nikhiljindal please, update the feature description to the actual state. cc @kubernetes/sig-federation-feature-requests


Source generator errors are hidden

Describe the bug
Errors are hidden from the user when the source generator fails to produce code
Additional context
Show errors and warnings in Visual Studio

This relates to #534


Sim rejects undock after successful dock at end of explore

I performed repeated coverage server explore goals until the bot ended up docked.
Next I sent the coverage server an undock goal, which it forwarded on to the sim.  The sim motion_control rejected the undock goal:
...
[motion_control-13] [INFO] [1635806767.200327952] [motion_control]: Received new dock servo goal
[motion_control-13] [INFO] [1635806825.107624130] [motion_control]: Dock Servo Goal Succeeded

Sent undock goal through coverage server:
[motion_control-13] [INFO] [1635809785.227185078] [motion_control]: Received new undock goal
[motion_control-13] [WARN] [1635809785.227501148] [motion_control]: Robot already undocked, reject

Tried again:
[motion_control-13] [INFO] [1635809941.818917710] [motion_control]: Received new undock goal
[motion_control-13] [WARN] [1635809941.819046534] [motion_control]: Robot already undocked, reject

This is really a pain to repro because coverage goal does not see the dock very often, but I confirmed this issue is happening.
Method:

Repeated short max_duration explores till one finished with is_docked: true.
Send /undock goal to coverage server

move_short_explore.sh issues:
ros2 action send_goal /coverage create3_examples_msgs/action/Coverage "{explore_duration:{sec: 60, nanosec: 0}, max_duration:{sec: 120, nanosec: 0}}"

This is the move_short that docked:
$ ./move_short_explore.sh
1635860055.630689 [0]       ros2: using network interface wlan0 (udp/<IP_ADDRESS>) selected arbitrarily from: wlan0, wlan1
Waiting for an action server to become available...
Sending goal:
     explore_duration:
  sec: 60
  nanosec: 0
max_duration:
  sec: 120
  nanosec: 0

Goal accepted with ID: 1daf22925e72413c9f925bf871662b35

Result:
    success: true
is_docked: true
duration:
  sec: 159
  nanosec: 333841204

Goal finished with status: SUCCEEDED

Coverage Server logged:
[INFO] [1635860056.037624343] [create3_coverage]: Accepting goal request
...
[INFO] [1635860135.540674044] [create3_coverage]: Rotation completed: from -0.666271 to 2.469646
[INFO] [1635860135.574859781] [create3_coverage]: Sending docking goal!
[INFO] [1635860215.308334524] [create3_coverage]: Docking succeeded!
[INFO] [1635860215.373907229] [create3_coverage]: Coverage action terminated

Sim logged:
[motion_control-13] [INFO] [1635860135.578554033] [motion_control]: Received new dock servo goal
[motion_control-13] [INFO] [1635860215.297843477] [motion_control]: Dock Servo Goal Succeeded

undock_it.sh sends:
ros2 action send_goal /undock irobot_create_msgs/action/Undock "{ }"

Sending /undock goals will fail, even though the last docking reported success:
$ ./undock_it.sh
1635860240.354535 [0]       ros2: using network interface wlan0 (udp/<IP_ADDRESS>) selected arbitrarily from: wlan0, wlan1
Waiting for an action server to become available...
Sending goal:
     {}

Goal was rejected.
ubuntu@CREATE3RPI:~/create3ros/create3_examples_ws$ ./undock_it.sh
1635860285.128759 [0]       ros2: using network interface wlan0 (udp/<IP_ADDRESS>) selected arbitrarily from: wlan0, wlan1
Waiting for an action server to become available...
Sending goal:
     {}

Goal was rejected.

Sim reports:
[motion_control-13] [INFO] [1635860240.803464673] [motion_control]: Received new undock goal
[motion_control-13] [WARN] [1635860240.803599514] [motion_control]: Robot already undocked, reject
[motion_control-13] [INFO] [1635860285.576984825] [motion_control]: Received new undock goal
[motion_control-13] [WARN] [1635860285.577073084] [motion_control]: Robot already undocked, reject

Note: Sending an explore goal will undock and execute properly.  Performing the dance example will also undock and execute properly so the impact of this issue could be considered low.

Next time you get into this state, can you try
ros2 topic echo /dock
To see if the robot is reporting is_docked = true

Indeed successful docking never publishes is_docked: true.
Waiting for an action server to become available...
Sending goal:
     {}

Goal accepted with ID: f1795501316a4c5db88823d3d7b7ecff

Result:
    is_docked: true

Goal finished with status: SUCCEEDED

but echo of the /dock topic does not show is_docked: true -
header:
  stamp:
    sec: 18863
    nanosec: 907000000
  frame_id: base_link
dock_visible: true
is_docked: false
---

I think that we should keep this issue open, even if it's not reliably reproducible it appears to be a valid problem.
The problem may be that:

the is_docked simulated topic is unreliable
the simulated dock action terminates too early, assuming that it's already on the dock while it is not true


Have problem reproducing experiment

Description
I ran the same command twice, but the result is different.
Here is my command:
MUJOCO_GL="osmesa" LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/nvidia-opengl/:$LD_LIBRARY_PATH PYTHONPATH=. python3 -u main.py setup=hipbmdp env=dmcontrol-walker-skill-distribution-v0 agent=distral setup.seed=2 agent.distral_alpha=0.0 agent.distral_beta=1.0
How to reproduce
Run the command below twice and see the result.
MUJOCO_GL="osmesa" LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/nvidia-opengl/:$LD_LIBRARY_PATH PYTHONPATH=. python3 -u main.py setup=hipbmdp env=dmcontrol-walker-skill-distribution-v0 agent=distral setup.seed=2 agent.distral_alpha=0.0 agent.distral_beta=1.0
Any other information
The code setting seed is in set_seed function in mtrl/utils/utils.py.
I think it is quite correct, but I still got different results with the same setting.
Could anyone please tell me how to fix it?

I solved the problem by setting seed in mtenv.


Move the argv handling out of async context

The async context is expensive, like spawning worker threads, scheduling the task etc. So move the argv handling into the main thread.
Also, the CLI can be used to add more configuration into config::Config, which the proxy may need for run.

Hi @haiyuewa. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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

/ok-to-test


The orchestration of Sharding-jdbc-spring-namespace

Fixes  #1201 .
Changes proposed in this pull request:

Separate orchestration configuration from sharding configuration and master-slave configuration.
Adjust orchestration spring namespace module.
Add test cases.

Pull Request Test Coverage Report for Build 4955

67 of 94 (71.28%)  changed or added relevant lines in 12 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.3%) to 64.096%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-orchestration/sharding-jdbc-orchestration/src/main/java/io/shardingsphere/jdbc/orchestration/api/yaml/YamlOrchestrationShardingDataSourceFactory.java
3
4
75.0%

sharding-orchestration/sharding-jdbc-orchestration/src/main/java/io/shardingsphere/jdbc/orchestration/api/datasource/OrchestrationMasterSlaveDataSourceFactory.java
0
1
0.0%

sharding-orchestration/sharding-jdbc-orchestration/src/main/java/io/shardingsphere/jdbc/orchestration/api/yaml/YamlOrchestrationMasterSlaveDataSourceFactory.java
3
4
75.0%

sharding-orchestration/sharding-jdbc-orchestration/src/main/java/io/shardingsphere/jdbc/orchestration/internal/datasource/AbstractOrchestrationDataSource.java
5
12
41.67%

sharding-orchestration/sharding-orchestration-core/src/main/java/io/shardingsphere/jdbc/orchestration/config/OrchestrationType.java
0
7
0.0%

sharding-orchestration/sharding-jdbc-orchestration-spring/sharding-jdbc-orchestration-spring-namespace/src/main/java/io/shardingsphere/jdbc/orchestration/spring/namespace/parser/OrchestrationBeanDefinitionParser.java
39
49
79.59%

Files with Coverage Reduction
New Missed Lines
%

sharding-orchestration/sharding-orchestration-reg/src/main/java/io/shardingsphere/orchestration/reg/newzk/client/zookeeper/base/Holder.java
1
76.81%

sharding-orchestration/sharding-orchestration-core/src/main/java/io/shardingsphere/jdbc/orchestration/config/OrchestrationType.java
1
0.0%

Totals

Change from base Build 4949:
-0.3%

Covered Lines:
8055

Relevant Lines:
12567

💛  - Coveralls


couldn't upload this Codespaces project to GitHub repo

ADD ISSUE DESCRIPTION HERE
Version: 1.93.1
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.0 Safari/605.1.15
Embedder: codespaces

I couldn't upload this Codespaces project to GitHub repo

Thanks for taking the time to open an issue. General support for Codespaces is best handled by GitHub support.  If you find a bug or issue in anything related to VS Code while using codespaces, please feel free to use the built-in error-reporter to share (which will automatically include any relevant logs we may need!)
Please feel free to reopen with additional information that may help us understand your problem better!


adding ros_rtt to documentation index for distro

I did some work about real-time communication in ros. The package supports real-time communication within node at the moment. And it will support communication between nodes in the future. I'd like this repository to be indexed and documented on ros.org.

What's the difference in your work and this?
http://wiki.ros.org/rtt
Also, out naming guidelines suggest not putting ros_ as a prefix in a name since it is redundant, and instead you should put a more meaningful name that's tied to you or your organization until it becomes widely used.
Also the CI is failing because your repository doesn't seem to have a package.xml:
https://travis-ci.org/ros/rosdistro/builds/70866291#L3980
If you just want to document, then you don't need the source or release entries. If you want to release it, you should follow the bloom tutorials: http://wiki.ros.org/bloom


Add an optional key_source parameter to set up the package repository.

Our internal hosts have no access to the internet, hence no option to download GPG-KEY-elasticsearch. This tiny patch adds the option to specify the download location for the GPG file.

Hepp! @gitbensons  - do you have anything against signing the agreement?  This is important for me too.

@bahner you are free to steal the commit 🙂

The agreement is not required anymore: the module is now managed by voxpupuli.  The transition is in progress, once #39 is merged, the CI should stop checking this :wink:

Can you please rebase your changes on top of the main branch?
From your working directory:
git fetch origin       # Download the latest code we have here
git rebase origin/master # Move your commits on top of the main branch
git push -f            # Send the changes (-f is required because we re-wrote history)

@smortex I synced my repo with master and rebased my changes. Not sure if this actually did what you expected. Directly after pushing the changes, Github went down, so I take this as a sign :)

Yes. I use nexus[1], which goes out and fetches all files required. So it
will just download the GPG key from you and store it in it's repo cache. It
could also just use the base repo path to get this really.

bahner

[1] https://www.sonatype.com/products/repository-oss
søn. 28. nov. 2021 kl. 20:40 skrev Romain Tartière @.***

:

@.**** commented on this pull request.
New CI proves to be useful \o/
Q: if your nodes cannot download the PGP key, how do they manage to fetch
the actual packages? Are these changes really enough?
In manifests/repo.pp
https://github.com/voxpupuli/puppet-elastic-stack/pull/35#discussion_r757940434
:

@@ -18,6 +18,7 @@

String            $proxy         = 'absent',
Integer           $version       = 7,
Optional[String]  $base_repo_url = undef,

Optional[String]  $key_source    = 'https://artifacts.elastic.co/GPG-KEY-elasticsearch'

CI failure can be fixed by removing the Optional. While here, maybe we
can use a stricter type than String, e.g. String[1] (non-empty string) or
Stdlib::HTTPUrl (which would not allow
puppet:///modules/profile/esGPG-KEY-elasticsearch/ so maybe not so
good?). Also, missing coma at end of line 😉
⬇ Suggested change

Optional[String]  $key_source    = 'https://artifacts.elastic.co/GPG-KEY-elasticsearch'

Stdlib::HTTPUrl   $key_source    = 'https://artifacts.elastic.co/GPG-KEY-elasticsearch',

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/voxpupuli/puppet-elastic-stack/pull/35#pullrequestreview-817250196,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNLSL2TPDWGY25QED6A2XDUOKARDANCNFSM4YCFMXSQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Mvh,
Lars Bahner


Not Found on gateway.ethswarm.org

Summary
I've uploaded a file using curl -F<EMAIL_ADDRESS>http://localhost:1633/files command, result is
{"reference":"044b15100e2385101b1886a52d33d9a31cd06874cfdf1a9aafde2dc6f82d0471"}
But page https://gateway.ethswarm.org/files/044b15100e2385101b1886a52d33d9a31cd06874cfdf1a9aafde2dc6f82d0471 returns not found
Steps to reproduce
Upload a file and try to share it via gateway.ethswarm.org
Expected behavior
File is available on gateway.ethswarm.org
Actual behavior
Not found

Thank you for reporting this. The Swarm network is a multitude of nodes with various latencies and configurations that all need to collaborate with each other. We are currently witnessing a Swarm network size that was never seen before and because of that, we run into situations not previously encountered. Rest assured that we are working on fixing this.

Please let us know if this resolved in v0.6.0!


some tests failed on macOS

Hi, thanks for developing this awesome project.
Version :
4.0.0
Describe the bug :
I tried to use truvari on macOS, and when I ran the test, I got the following error.

error log
test_anno_grm ran in 2 sec with 34/0 lines to STDERR/OUT
 FAIL EXIT CODE (LINE 59)
-->     expected EX_OK, observed Unknown code: 1
    data = pd.concat(chunks, ignore_index=True)
  File "/nix/store/jhjlf5yy6ar5g7jl363pxzk6fqxwzj5s-python3.10-pandas-1.5.3/lib/python3.10/site-packages/pandas/util/_decorators.py", line 331, in wrapper
    return func(*args, **kwargs)
  File "/nix/store/jhjlf5yy6ar5g7jl363pxzk6fqxwzj5s-python3.10-pandas-1.5.3/lib/python3.10/site-packages/pandas/core/reshape/concat.py", line 368, in concat
    op = _Concatenator(
  File "/nix/store/jhjlf5yy6ar5g7jl363pxzk6fqxwzj5s-python3.10-pandas-1.5.3/lib/python3.10/site-packages/pandas/core/reshape/concat.py", line 422, in __init__
    objs = list(objs)
  File "/nix/store/v6f6y9mwmqj9v1jffiy4g96ili4pj5la-python3-3.10.11/lib/python3.10/multiprocessing/pool.py", line 873, in next
    raise value
AttributeError: 'types.SimpleNamespace' object has no attribute 'ref_filename'

test_anno_grm ran in 0 sec with 5/0 lines to STDERR/OUT
 FAIL EXIT CODE (LINE 48)
-->     expected EX_OK, observed Unknown code: 1
Traceback (most recent call last):
  File "<string>", line 4, in <module>
  File "/nix/store/kwv7hx63pw3djbd5ryk8365v25lh1ka6-python3.10-joblib-1.2.0/lib/python3.10/site-packages/joblib/numpy_pickle.py", line 650, in load
    with open(filename, 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: 'test_results/grm.jl'

test_anno_trf ran in 2 sec with 26/0 lines to STDERR/OUT
 FAIL EXIT CODE (LINE 72)
-->     expected EX_OK, observed Unknown code: 1
    main()
  File "/private/tmp/nix-build-truvari-4.0.0.drv-0/source/truvari/__main__.py", line 102, in main
    TOOLS[args.cmd](args.options)
  File "/private/tmp/nix-build-truvari-4.0.0.drv-0/source/truvari/anno.py", line 59, in anno_main
    ANNOS[args.cmd][1](args.options)
  File "/private/tmp/nix-build-truvari-4.0.0.drv-0/source/truvari/annotations/trf.py", line 658, in trf_main
    for i in chunks:
  File "/nix/store/v6f6y9mwmqj9v1jffiy4g96ili4pj5la-python3-3.10.11/lib/python3.10/multiprocessing/pool.py", line 873, in next
    raise value
AttributeError: 'types.SimpleNamespace' object has no attribute 'args'

test_anno_trf_reg ran in 2 sec with 26/0 lines to STDERR/OUT
 FAIL EXIT CODE (LINE 83)
-->     expected EX_OK, observed Unknown code: 1
    main()
  File "/private/tmp/nix-build-truvari-4.0.0.drv-0/source/truvari/__main__.py", line 102, in main
    TOOLS[args.cmd](args.options)
  File "/private/tmp/nix-build-truvari-4.0.0.drv-0/source/truvari/anno.py", line 59, in anno_main
    ANNOS[args.cmd][1](args.options)
  File "/private/tmp/nix-build-truvari-4.0.0.drv-0/source/truvari/annotations/trf.py", line 658, in trf_main
    for i in chunks:
  File "/nix/store/v6f6y9mwmqj9v1jffiy4g96ili4pj5la-python3-3.10.11/lib/python3.10/multiprocessing/pool.py", line 873, in next
    raise value
AttributeError: 'types.SimpleNamespace' object has no attribute 'args'

After a bit of research, I found out that it is caused by how the process is started in the multiprocessing module.
(ref: https://docs.python.org/3/library/multiprocessing.html#contexts-and-start-methods)
I changed it from the macOS default of spawn to the Linux default of fork, and the tests passed.
To Reproduce :
Run bash repo_utils/truvari_sshtests.sh on macOS.
Expected behavior :
All tests pass.
Example Data :
Additional context :
The full log is here.
https://hydra.nixos.org/build/219117259/log

Thank you for reporting this. I'm sure it wasn't easy to solve. I was able to recreate the issue and confirm that having multiprocessing.set_start_method('fork') before with multiprocessing.Pool.. calls can get tests to pass.
However, I don't think changing the set_start_method is a viable solution. The python docs state:

Changed in version 3.8: On macOS, the spawn start method is now the default. The fork start method should be considered unsafe as it can lead to crashes of the subprocess. See bpo-33725.

Possible solutions:

Make it clear that some truvari anno commands will fail on macOS
Make it clear that truvari is designed on/for unix and recommend docker (which is how I run truvari tests on my mac).
Change design pattern to not depending on 'fork' sharing semantics. Specifically it's the global namespace.

And as I'm digging deeper into bpo-33725 and the issues it references, I'm thinking changing the code might need to be the solution as this non-explicit sharing may become not possible in a future python version.. maybe.

Thanks for your response.

However, I don't think changing the set_start_method is a viable solution.

Yes, I don't think using set_start_method is a good way to fix it.
and thank you for starting the fix as quickly.
Let me know if I can help in any way.

Functional tests off of develop now pass on mac.  If you're still seeing a problem, please re-open this ticket.
These changes will be present in v4.1. However It'll be some time before that release is cut as there's at least two more features to add and a lot of user testing happening for a publication tied to the next version.


Adapting DS2 torch benchmark to new dataset

I've modified the dataset to follow the code from here. If there are any issues/feedback let me know!

Thanks!


[WIP] [feature] add info get k3s token and k3s secret

Hello,
Final contribution would be something like this (open to your advices):
k3d info k3s-token
and
k3d info k3s-secret
I realized afterwards the works done on master-v3 and master-v1 branch. But it don't seem finished yet so what is the most recent and suitable branch from which I have to start ?
At this moment I start from master branch, but I could rebase my work.
PS : PR add also some GCFLAGS to allow debug and gitgnore

Hi @RouxAntoine , thanks for your efforts :)
master-v3 is a complete rewrite of k3d which has a completely different structure and style than the currently existing versions. It will also have a wider featureset.
It's planned to freeze the current master in the near future.
I'll have a closer look on your PR later, when I have enough time to focus on it :+1:

Hi @RouxAntoine , would you be willing to re-do this on the new master branch (v3)?

Hello @iwilltry42 , if you think this is a pertinent feature yes i could. But what about this two token (k3s-token, k3s-secret) they are both equivalent and maintain or just one is sufficient ?

We're only using the K3S_TOKEN environment variable now. Additionally, we're storing the contents in the docker label k3d.cluster.secret" (which we may actually rename to k3d.cluster.token).
So probably, the PR is going to look a lot simpler afterwards :+1:

I will made this on this weekend. Thanks for information👌

I made new version of this pull request here : https://github.com/rancher/k3d/pull/257
I allowed myself some little refactoring. If you prefer i could extract it to another branch. Or totally remove them. Any reviews are welcome.


Outline not collapsed by default

create a new empty profile
open explorer
notice that files, timeline, and outline are all expanded and equal height

This isn't happen as the outline sets itself to collapsed: true

What was the state of these view before creating the profile? A profile does not include the workspace state. So if these views are expanded before, then they will remain expanded as the collapse state is stored in workspace.

Timeline is the bottom panel, outline in the hidden aux-side-view

What was the state of these view before creating the profile? A profile does not include the workspace state.

TBH I am surprised that matters because I expect "create new profile" to start fresh

It seems these views were expanded before and hence they are shown expanded.
Collapse state is workspace state because we do not want views to be collapsed or expanded in other windows when they are collapsed/expanded in one window. We cannot reset the workspace state when a new/empty profile is created because this might be unexpected in other areas like opened editors getting closed.
CC @bpasero Any insights?


Migrate from tslint to eslint and tsfmt to prettier.

Because tslint is deprecated, this commit migrates from tslint to eslint with typescript and prettier.  There is a new lint script that runs it, and prettier is set up to run on the generated code so it's in the format expected rather than relying on tsfmt.
As package-lock.json has not previously been generated here, it's now generated for the first time.
eslint and prettier have been run against relevant files.

It's not clear to me why the test-262 tests are failing on circleci and if that's affected by the particular node version that's being run or if something else that changed in this PR is causing the issue.

Hi @calvinf, thanks for the help!
IMHO there's too much going on in one PR like this, it's hard to understand and fix the breakage.

I'll make some smaller PRs.


Include glazed-cli on README

https://github.com/glazedio/glazed-cli
cc @niftylettuce

I will be deploying this tonight, already wrote it.


make snap confined and supporting sosreport only

The snap is currently built in classic mode so that it can be run on both a host or against a sosreport but this has led to problems e.g. when using the python3-cryptography lib. Rather than have an error prone snap that sort of works for host/sosreport it would be preferable to have work well for one at the expense of the other. Therefore going forward we will make the snap strictly confined in order to alleviate python lib issues and therefore only support using the snap with sosreports. If a user attempts to use the snap on a host (i.e. not against a sosreport) it will print a message suggesting they install the deb or pypi packages that have full support for host and sosreport.

to kick this off i tried simply changing classic -=> strict and it built fine but when i ran it got the following which I now remember was one of the problems we had before we went classic:
Traceback (most recent call last):
  File "/snap/hotsos/x1/bin/hotsos", line 5, in <module>
    from hotsos.cli import main
  File "/snap/hotsos/x1/lib/python3.8/site-packages/hotsos/cli.py", line 15, in <module>
    from hotsos.core.host_helpers import CLIHelper
  File "/snap/hotsos/x1/lib/python3.8/site-packages/hotsos/core/host_helpers/__init__.py", line 1, in <module>
    from .cli import CLIHelper  # noqa: F403,F401
  File "/snap/hotsos/x1/lib/python3.8/site-packages/hotsos/core/host_helpers/cli.py", line 12, in <module>
    from hotsos.core.host_helpers.common import HostHelpersBase
  File "/snap/hotsos/x1/lib/python3.8/site-packages/hotsos/core/host_helpers/common.py", line 4, in <module>
    from searchkit.utils import MPCache
  File "/snap/hotsos/x1/lib/python3.8/site-packages/searchkit/__init__.py", line 1, in <module>
    from .search import (   # noqa: F403,F401
  File "/snap/hotsos/x1/lib/python3.8/site-packages/searchkit/search.py", line 22, in <module>
    RS_LOCK = multiprocessing.Lock()
  File "/usr/lib/python3.8/multiprocessing/context.py", line 68, in Lock
    return Lock(ctx=self.get_context())
  File "/usr/lib/python3.8/multiprocessing/synchronize.py", line 162, in __init__
    SemLock.__init__(self, SEMAPHORE, 1, 1, ctx=ctx)
  File "/usr/lib/python3.8/multiprocessing/synchronize.py", line 57, in __init__
    sl = self._semlock = _multiprocessing.SemLock(
PermissionError: [Errno 13] Permission denied

i.e. as-is with core20 you can't use python3-multiprocessing. It might be worth testing with core22 to see if that has fixed these issues.


Refer swiftinterface hack in documentation

https://developer.apple.com/forums/thread/123253

Implemented --disable-library-evolution. It helps


How to apply ripple effect to Buttons?

Hey thanks for this library. I have a little issue. I downloaded the demo app from google play and took a look at your repository.
The only thing that is not working is the ripple effect on the buttons.
This is the xml for the buttons:
<com.rey.material.widget.Button
        android:id="@+id/add_text_btn"
        android:layout_width="200dp"
        android:layout_height="100dp"
        android:text="@string/add_deal_fragment_select_from_special_items"
<EMAIL_ADDRESS>        app:ripple="@style/FlatWaveColorButtonRippleStyle"
        app:delayClick="false"
        android:layout_marginBottom="8dp"/>

This is the styles xml:
<style name="FlatWaveColorButtonRippleStyle" parent="Material.Drawable.Ripple.Wave.Light">
    <item name="rd_rippleColor">#a0757171</item>
    <item name="rd_cornerRadius">4dp</item>
</style>

The problem is that the ripple effect does not show up. Could someone please help me here?

Release of 1.1.0 solved my issue. For any one that might come across the same issue, here is my current xml of the buttons. The style xml above stayed the same:
<com.rey.material.widget.Button
    android:id="@+id/add_text_btn"
    android:layout_width="200dp"
    android:layout_height="100dp"
    android:text="@string/add_deal_fragment_select_from_special_items"
<EMAIL_ADDRESS>    app:rd_style="@style/FlatWaveColorButtonRippleStyle"
    app:rd_delayClick="false"
    android:layout_marginBottom="8dp"/>


unknown operating system

While following the GettingStarted i encountered the following
[...]/Packages/BlueSSLService/Package.swift:36:12: warning: unknown operating system for build configuration 'os'
#elseif os(macOS) || os(iOS) || os(tvOS) || os(watchOS)
          ^

Xcode 8
Swift 3.0
macOS Sierra

Sorry, was just to dumb to see toolchain was still on xcode beta


replace clock from time

Many places in the library use
from time import clock
This has been deprecated since Python 3.3 and officially removed as of Python 3.8
Since Dolo requires 3.8, getting the library ready for 3.8 compatibility is important for maintaining joint environments.
The functions are recommended instead:
https://docs.python.org/3/library/time.html#time.process_time
https://docs.python.org/3/library/time.html#time.perf_counter

Maybe this is just in a couple example notebooks....
examples/Gentle-Intro/Gentle-Intro-To-HARK.py
examples/ConsIndShockModel/IndShockConsumerType.ipynb


Odometry random incrementation.

After running some basic tests I've encountered an issue when calling odometry for longer periods of time.
The test involved the robot endlessly running through the course while periodically outputting X and Y coordinates. It has been done in order to map out  key points/areas of the original track for other implementations:

The following values have been found with AND without clearing position after crossing the start/end line:

Conclusions:

Y values are somewhat consistent while X isn't at all
clearing position at the start/end line helps

main branch is updated, please verify.

After testing, I now get consistent results until around the 46 second simulation timestamp (or middle of 3rd lap)

tests were done one default track and different parameter sets, the first one giving the best results.
It looks like the PID Controller exponentially adds up the differences and somewhere at that timestamp, they start increasing very fast: when the robot is running on a straight segment, neither of the axes are constant, meaning that the input values of the PID are being heavily and drastically modified to fix the measured mistake.
This could also be why the first parameter set works the best, because it is slower and more precise.  The other sets blow up the calculations even more

There will be always a small error which sums up over time. Usually there are known fix waypoints, where this needs to be compensated again. This can not be handled by RU and must be handled on higher level like DCS.

Resetting orientation to Pi/2 and clearing the PID controller on Start/Endline recognition seems to fix the issue.


LSP Updates

I don't know what's going on here with the conflicts...I updated my branch to have no conflicts with main.  Probably this branch should just be deleted unless you are thinking of doing serious LSP work yourself. Branches that get out of sync with main are basically useless unless they have a lot of man power behind them.

I would like to work on this (eventually) and don't want to lose what you have done.  I just merged main into lsp-dev and resolved conflicts.  If you have additional changes since then, perhaps it would work to retry the pull request after merging the updated lsp-dev branch (or rebasing your new work)?

I will make a new PR against master. It can stay as a PR until you're ready for it.


[NOREF] Fixing package visibility

The only dependency outside the package was in the HttpStatusCodeException in a method called getResponseBody which doesn't return the body as you requested, or at least implied in the method name, but a RestClientResponse, which doesn't contain only the body but pretty much all the information you have already in the HttpStatusCodeException as well, so this leads to a redundant syntax: exception.getResponseBody(AnyDto.class).getBody(), creating a dependency with the impl package that doesn't need to be there. Also, the documentation was wrong.

@brunodequeiroz @eemmiirr do we still need this?

@marcust yes he did very nice hidding of it but i would keep it for a bigger release since it breaks backward compatibility


Multi-ancestry meta-analysis

Hi!
I've got a question that isn't so much related to a bug/issue with the software, but about the best way to implement the method in a cohort that will be included as part of a larger multi-ancestry meta-analysis.
In the methods of the paper it mentions that as an alternative to the joint model, separate GWAS can be run for each ancestry using the deconvolved tracts and "Results from the different ancestry runs could then be meta-analyzed to increase the power by incorporating summary statistics from both populations, although we recommend preferentially using the joint-analysis method described in this manuscript to avoid any potential bias from combining multiple ancestral portions of the genome of the same individuals."
So, I'm wondering what would be the best way to include a cohort with 3-way admixed individuals in both a) a multi-ancestry meta-analysis and b) ancestry specific meta-analyses. For b) it seems that the ancestry0 specific results from the joint model can be meta-analyzed with other cohorts of ancestry0 no problem (and so on for ancestries 1 and 2), but for a) I'm a bit lost if there's a way to include the cohort's ancestry0, 1, and 2 results (from the separate gwas, not the joint model) alongside each other in a larger meta-analysis? in the paper, results from the deconvolved segment meta-analysis are presented at some points, but the statement I mentioned above left me confused if this is not recommended.
Thanks in advance for any insight you can provide!
-Sarah

Sorry I missed this post.
The short answer is either meta-analysis strategy should be alright. For e.g. the PGC-PTSD group, we typically wanted to report ancestry-specific GWAS sumstats, hence the suggestion about meta-analyzing just the e.g. AFR sumstats with other homogeneous AFR cohorts. So yes, b is what we primarily described in the paper.
If you just want a multi-ancestry meta-analysis though, you could meta-analyze all the ancestry-specific terms together. We did benchmarking of this in the Tractor manuscript as well, and found it also reduced the size of the credible set for GWAS peaks prior to fine-mapping thanks to the incorporation of multiple disruptions of LD, and did not add inflation. The one weird thing about this is exactly what you mention - the inclusion of multiple components from the same individual thing. While we did not find this to cause problems in our preliminary tests, we cannot rule out that it could, so we noted that caveat.
Hope that helps!
Elizabeth


Close #LGVISIUM-101: Removed deprecated AWS Lambda script and removed the AWS Region from the environement variables

After working together with Oliver from Geowerkstatt, we were able to find a setup that makes it possible to integrate the data extraction API into the borehole application. This mainly involved figuring out which environment variables AWS needed to connect to the right S3 bucket in the correct region.
As it is also very unlikely that we will deploy the API using AWS Lambda in the near future I removed the code to avoid any sort of confusion.
The README was also edited to only document the possibility of passing the AWS credentials as environment variables to the container, as this is how the container is used in production.

@stijnvermeeren-swisstopo I added the information provided by Oliver from Geowerkstatt to the README.


Go back to no scene loaded, without destroying the viewer

I need, for a very specific case, to return back to the first state of the viewer, where no scene has been loade, because I am loading and unloading scenes dynamically. And I need to go back to an "empty state". I see that there is no viewer.unloadScene method, or something like that. Is there any straight forward way , without having to touch the base lib, to make the viewer unload the current scene, and just show the background with the "No scene Loaded" message?
Thanks!

This is not currently supported.
The following three lines should accomplish this, if used internally in pannellum.js:
controls.load.style.display = 'table';
loaded = undefined;
renderContainer.style.display = 'none';

Thanks! I missed your answer before.


Provide the user an option to specify absolute/relative paths for datasets

Describe the bug
This is a follow up to #3414.
As per the discussion, to avoid confusion about the dataset path being absolute or relative, it seems like a better approach to let the users specify how they'd like the dataset path to be saved in the session file.
Impact

[x] High - User productivity significantly degraded
[x] Medium - User productivity partially degraded
[ ] Low - User productivity trivially degraded

I observe that when I save a session file, there's no question asking me to use relative or absolute path. I'm not sure what's changed.


Fix github actions

We started to getting the following error during releases from Wendesday:
remote: You must verify your email address.
13
remote: See https://github.com/settings/emails.
14
fatal: unable to access 'https://github.com/GoodDollar/GoodDAPP/': The requested URL returned error: 403

It seems you'd need to verify techadmin email or email is used during actions runs.
I tried to set my email (which is verified) in git config --local user.email at line 43 of webtests.yml - it doesn't helped. So maybe email is set also somewhere else.
One of solutions i googled is suggesting to disable-enable actions on the repo. I was unable to do it as i don't have such permissions

[ ] understand which email is used during github actons
[ ] verify this email
[ ] try other solutions (e.g. disable-enable actions https://github.community/t/errored-please-verify-your-email-address-to-run-github-actions-workflows/17714)

as a temporary solution, to deploy prod and QA last time i did it manually by running commands listed in actions locally

the auth token was old format, refreshing it solved the issue


Add Tabby as AI coding assistant

This is an open-source AI coding assistant: https://tabby.tabbyml.com/

Looks cool! Please create a PR and we'll merge it.


add client method for /info endpoint

This unpacks additional server data which is added to the
server by a corresponding PR, and adds a direct call for
the /info endpoint as a convenience feature. This is intended
to be helpful for benchmarking-type functionality.

that seems like a really good idea.

Updated this to match changes in the server-side implementation.

Great! The PR works with the corresponding Pilosa PR: https://github.com/pilosa/pilosa/pull/1859

@seebs Since https://github.com/pilosa/pilosa/pull/1859 was merged, is it OK to merge this?

I'm not sure how we manage "releases"; I'd say either now, or after the next release of the server.

What we've typically said is the latest release of a client (or the pdk or
whatever) should work with the latest release of Pilosa. Master should
generally be compatible with master, though they may be incompatible for
short periods.
On Wed, Mar 27, 2019 at 11:53 AM seebs<EMAIL_ADDRESS>wrote:

I'm not sure how we manage "releases"; I'd say either now, or after the
next release of the server.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pilosa/go-pilosa/pull/216#issuecomment-477251209, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA4hcyqgaE2ytoHh6BD9GcF10RK8URTNks5va6H3gaJpZM4a32Jw
.

--
http://www.pilosa.com/
Matt Jaffee
Slothware Engineer
(302) 893-0193 <(302)%893-0193> |<EMAIL_ADDRESS>pilosa.com https://www.pilosa.com/ | @mattjaffee
https://twitter.com/mattjaffee | LinkedIn
https://www.linkedin.com/company/pilosa | Facebook
https://business.facebook.com/pilosaco | GitHub
https://github.com/pilosa/pilosa

The changes in this PR don't break any compatibility with current or past versions and the master. Let's merge it unless there is a compelling reason not to.

I should probably fix the test failures, at least. And the linter failures. I've asked CircleCI to rerun in case the updates to pilosa-master  fix any of it, but I think the lint is probably real.

Okay, tests seem to be passing, and I fixed the output from a test, dropped a bogus comment, and ran gofmt. The old linter claim about goimports needing to be run seems to be wrong now, or possibly goimports implied gofmt also. Rebased and repushed, if tests work I'll merge.


Constantly getting i2c errors when using touch (nothing else connected to i2c bus)

Im using the Lilygo T-Display-S3 CAP. Touch version and if I implement the touch functionality to my code I'm constantly getting the following i2c errors:
[383725][E][Wire.cpp:513] requestFrom(): i2cRead returned Error -1
[401620][E][Wire.cpp:513] requestFrom(): i2cRead returned Error -1
[403552][E][Wire.cpp:513] requestFrom(): i2cRead returned Error -1

The problem is also that as soon as the errors occur the whole process loop is slowed down. This is unacceptable.
Nothing else is connected to the i2c bus and this seems to be a problem with every unit since all 4 units that I bought have this problem.
I'm not doing anything special I'm just changing a variable with the touch function. Another problem is that sometimes even if I don't touch the display the variable is incremented...

#define TOUCH_MODULES_CST_SELF
#include <Arduino.h>
#include "TFT_eSPI.h"
#include "pin_config.h" //default TDisplay-S3 pin occupation
#include "TouchLib.h"

//TFT
TFT_eSPI tft = TFT_eSPI();
TFT_eSprite sprite = TFT_eSprite(&tft);
//                                     wire, 18, 17, 0x15, 21
TouchLib touch(Wire, PIN_IIC_SDA, PIN_IIC_SCL, CTS820_SLAVE_ADDRESS, PIN_TOUCH_RES);

int deb = 0; //debounce touch
uint8_t currentUIwindow = 0;
void switchTouch();

void setup() {
  Serial.begin(115200);
  // init TFT and Touch
  pinMode(PIN_POWER_ON, OUTPUT);
  digitalWrite(PIN_POWER_ON, HIGH);
  pinMode(PIN_TOUCH_RES, OUTPUT);
  digitalWrite(PIN_TOUCH_RES, LOW);
  delay(500);
  digitalWrite(PIN_TOUCH_RES, HIGH);
  tft.begin();
  tft.fillScreen(TFT_BLACK);
  tft.setRotation(1);
  touch.setRotation(1);
  sprite.createSprite(320,170);
  sprite.setTextColor(TFT_WHITE,TFT_BLACK);
  sprite.fillSprite(TFT_BLACK);
  sprite.setSwapBytes(true);
  Wire.begin(PIN_IIC_SDA, PIN_IIC_SCL);
}

void loop() {
  switchTouch();
  delay(10);
}

void switchTouch() {

   if (touch.read()) {
    if (deb==0){
      deb=1;
      TP_Point t = touch.getPoint(0);
      if (t.x >= 160) {
        if (currentUIwindow >= 4 || currentUIwindow < 0) {
          currentUIwindow = 0;
        }
        else {
          ++currentUIwindow;
        }
      }
      if (t.x < 160) {
        if (currentUIwindow <= 0) {
          currentUIwindow = 4;
        }
        else {
          --currentUIwindow;
        }
      }
    }
  }
  else {
    deb=0;
  }

}

I'v seen this as well
have a look at lvgl i2c_manager Arduino has no concept of multicore - so it's fly by night or you take care yourself pretty sure one task doing i2c is rescheduled before the i2c transaction is done and another task also does some i2c io

I dont understand why there are scheduling problems if nothing else is connected via i2c? Also I dont want to be forced to do RTOS or concurrency programming with all its pitfalls.

how exactly can you run touch on core 0 and loop on core 1 if you are saying this is single-threaded?
why not post a repo for inspection
that said: FreeRTOS-based Arduino usually has some background tasks like for Wifi event handling
you typically do not see them except if you dig deeper

With :
TaskHandle_t Task1;
xTaskCreatePinnedToCore(
      Task1code, /* Function to implement the task */
      "Task1", /* Name of the task */
      10000,  /* Stack size in words */
      NULL,  /* Task input parameter */
      0,  /* Priority of the task */
      &Task1,  /* Task handle. */
      0); /* Core where the task should run */

Void Task1code( void * parameter) {
  while(true) {
    if (touch.read()) {...
    (...)
  }

Are you sure you are using the CST820 touch?

Are you sure you are using the CST820 touch?

Yes the touch_test example only works if I use #define TOUCH_MODULES_CST_SELF
The touch functionality is also working as intended in my code but I'm constantly getting those i2c errors which also seems to block code execution irregularly for a short time. And also it seems that in irregular time intervals touch is beeing registered although nothing touched the display. Its really annoying and makes the use of the touch functionality unusable.

Oh! If using CST820, if the touch chip does not detect being pressed for a certain period of time, and ESP32 accesses the touch device, then CST820 will not return any data. This is mainly due to the access mechanism of CST820 touch, which is not a fault

By the way, the CST820 is not a standard I2C device This is very annoying to me

This is the complete code btw: https://github.com/shyney7/TDisplay-S3_PMX_Ground

You can add fully closed internal debugging printing in platformio.ini

build_flags =
    -DCORE_DEBUG_LEVEL=0

Disabling debug messages doesn't fix the problem it just hides it.
Also when the random touch registration occurs the values for the x and y coordinates are both 4095 which is completely out of range of the real display size. At least I can now ignore touch values higher than 320 for y and 170 for x in my program. But the annoying i2c errors is what bothers me since the loop itself is being blocked for a short time repeatedly due to these errors.

Whats also weird is that if I keep touching the display the touch functionality works completely fine.
But as soon as I dont use touch the i2c errors keep occuring.

Oh! If using CST820, if the touch chip does not detect being pressed for a certain period of time, and ESP32 accesses the touch device, then CST820 will not return any data. This is mainly due to the access mechanism of CST820 touch, which is not a fault

I think I have already explained.

Whats also weird is that if I keep touching the display the touch functionality works completely fine. But as soon as I dont use touch the i2c errors keep occuring.

well touch changes relative timing
it's likely a race condition
either use a mutex around I2C transactions, or try lvgl i2c_manager

Whats also weird is that if I keep touching the display the touch functionality works completely fine. But as soon as I dont use touch the i2c errors keep occuring.

well touch changes relative timing it's likely a race condition
either use a mutex around I2C transactions, or try lvgl i2c_manager

If nothing else except the touch IC is using the i2c bus why should there be a race condition?
Nevertheless I used a pthread mutex and locked it before calling the touch functionality and unlocked it after that, and I'm still getting the same i2c errors as shown above including touch registrations of 4095 and 3331.

This problem was fixed in the espressif esp-bsp touch driver repo 3 weeks ago with this pull request: https://github.com/espressif/esp-bsp/pull/181
This is the issue that was created: https://github.com/espressif/esp-bsp/issues/178
Is it possible for lilygo to update the touchlib with this information?

Try the CST816S library. It works. In case you don't need all the functionality of that library you can modify it and remove the gestures.


Question about interpolation in latent space

Hi, thanks for your great work!
I'm interested in concatenating two actions using your model. But I'm not sure what's means of "interpolation in latent space".
Could you give more details or some guidance?

Hello,

I'm interested in concatenating two actions using your model.

ACTOR is unfortunately limited to one action at a time.
If you want to concatenate multiple actions, you can try to put them together using interpolation methods, or with motion inbetweening/infilling methods (but with no guarantee of having something that works well).
You can also try to extend the method to deal with a sequence of actions, but I think it is not obvious how to do that, and train such a model.

But I'm not sure what's means of "interpolation in latent space".

In our latent space, a latent vector (given an action) can be decoded into an entire sequence. Given 2 latent vectors (v1 and v2) and an action A, if we decode the latent vectors into motions (m1 and m2), we will have 2 motions that represent the action (two different styles/ways of doing the action). So when we say "interpolation in the latent space", it means that if we take v = alpha*v1 + (1-alpha)*v2, this new latent vector can be decoded into a movement, which the "style" will be a mixture of m1 and m2.


I want to create a EKS cluster with AMI prepared by AWS and install additional packages on the node group instances

Hi,
I want to create an EKS cluster, which:

node group is using the AMI prepared by AWS
my SSH key pair is added to the node group EC2 instances
SSH access to the node group EC2 instances is unblocked
I can use the pre_userdata parameter to install additional packages to the node group EC2 instances

Unfortunately, I cannot achieve this, not sure if it is feasible at all. Maybe someone can point out what I am doing wrong?
provider "aws" {
  region = "us-west-1"
}

locals {
  name = "my_cluster"
  cluster_version = "1.23"
  region       = "us-west-1"

  vpc_id     = "<my_vpc>"
  subnet_ids = ["<subnet-1>", "<subnet-2>"]

  tags = {
    Environment    = "dev"
  }
}

data "aws_eks_cluster" "cluster" {
  name = module.eks_blueprints.eks_cluster_id
}

data "aws_eks_cluster_auth" "cluster" {
  name = module.eks_blueprints.eks_cluster_id
}

provider "kubernetes" {
  host                   = data.aws_eks_cluster.cluster.endpoint
  cluster_ca_certificate = base64decode(data.aws_eks_cluster.cluster.certificate_authority[0].data)
  token                  = data.aws_eks_cluster_auth.cluster.token
}

# Security group that allows SSH connection to the node group EC2 instances
resource "aws_security_group" "remote_access" {
  name_prefix = "${local.name}-remote-access"
  description = "Allow remote SSH access"
  vpc_id      = local.vpc_id

  ingress {
    description = "SSH access"
    from_port   = 22
    to_port     = 22
    protocol    = "tcp"
    cidr_blocks = ["<IP_ADDRESS>/8", "<IP_ADDRESS>/16"]
  }

  egress {
    from_port        = 0
    to_port          = 0
    protocol         = "-1"
    cidr_blocks      = ["<IP_ADDRESS>/0"]
    ipv6_cidr_blocks = ["::/0"]
  }

  tags = local.tags
}

#---------------------------------------------------------------
# EKS Blueprints
#---------------------------------------------------------------

module "eks_blueprints" {

  cluster_name    = local.name
  cluster_version = local.cluster_version

  source = "github.com/aws-ia/terraform-aws-eks-blueprints?ref=v4.0.2"

  # EKS CLUSTER
  vpc_id             = local.vpc_id
  private_subnet_ids = local.subnet_ids

  cluster_endpoint_public_access  = true
  cluster_endpoint_private_access = true

  cluster_enabled_log_types = ["audit", "api", "authenticator", "controllerManager", "scheduler"]

  # EKS MANAGED NODE GROUPS
  managed_node_groups = {
    mg_m5 = {
      vpc_security_group_ids = [aws_security_group.remote_access.id]
      create_launch_template = false
      launch_template_name   = ""

      node_group_name = "worker-eks-aws"
      desired_size = 2
      max_size     = 2
      min_size     = 2
      disk_size       = 100
      instance_types  = ["m5.large"]
      subnet_ids      = local.subnet_ids

      # Attempt to install additional packages on the node group hosts;
      pre_userdata = <<-EOT
      yum install -y osquery
      EOT

      ssh_security_group_id = aws_security_group.remote_access.id
      ec2_ssh_key = "<my_ssh_key_pair>"

      # Remote SSH access to the node group hosts
      remote_access = {
        ec2_ssh_key               = "<my_ssh_key_pair>"
        source_security_group_ids = [aws_security_group.remote_access.id]
      }
    }
  }
}

please see nearly identical answer provided here


Day353

Resolves #701.

Pull Request Test Coverage Report for Build 1290

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1288:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


Add OpenCL Wrapper Codes

Opencl Wrapper for GPU implementation

Hi @Rliop913 thanks for taking the initiative, before getting too deep into this:

we haven't decided what the approach is with accelerator support. currently leaning more towards webgpu than opencl given the trends of support for those APIs
if there's an SDK that needs to be vendored, would probably prefer to do it via submodules than to have a copy in the repo.

if you have any thoughts/comments feel free to post here, might be useful to discuss synchronously as well (may setup a discord in the near future).


[gpu] NFC: Move MMA schedule dueduction to Common/GPU/

This prepares it to be shared by the LLVMGPU path.

The first one is purely copy over. The second commit actually updates and rewires the code.


JSS doesn't work after update

I'm currently using version 3.0.1 and it works fine, but I decided to try out 4.x.x and after updating to 4.13 my app crashes with a following error:
Uncaught TypeError: Cannot call a class as a function
    at _classCallCheck (http://localhost:3000/packages/modules.js?hash=e724ac4eddc0c9046c881b2eb0cd2cdeeca5763b:72128:99)
    at Jss (http://localhost:3000/packages/modules.js?hash=e724ac4eddc0c9046c881b2eb0cd2cdeeca5763b:72179:7)
    at meteorInstall.imports.ui.components.uploadsProgress.jsx (http://localhost:3000/app/app.js?hash=915948cd4e35c9567e05f4eda51b5af17964626a:2495:42)
    at fileEvaluate (http://localhost:3000/packages/modules-runtime.js?hash=5d90b563997f267540e87eb08e19a293a1767772&hot=1:189:9)
    at require (http://localhost:3000/packages/modules-runtime.js?hash=5d90b563997f267540e87eb08e19a293a1767772&hot=1:118:16)
    at meteorInstall.imports.ui.layouts.appLayout.jsx (http://localhost:3000/app/app.js?hash=915948cd4e35c9567e05f4eda51b5af17964626a:8045:24)
    at fileEvaluate (http://localhost:3000/packages/modules-runtime.js?hash=5d90b563997f267540e87eb08e19a293a1767772&hot=1:189:9)
    at require (http://localhost:3000/packages/modules-runtime.js?hash=5d90b563997f267540e87eb08e19a293a1767772&hot=1:118:16)
    at meteorInstall.imports.startup.client.routes.jsx (http://localhost:3000/app/app.js?hash=915948cd4e35c9567e05f4eda51b5af17964626a:9999:18)
    at fileEvaluate (http://localhost:3000/packages/modules-runtime.js?hash=5d90b563997f267540e87eb08e19a293a1767772&hot=1:189:9)_classCallCheck @ modules.js?hash=e724ac4…:72128Jss(Component) @ modules.js?hash=e724ac4…:72179meteorInstall.imports.ui.components.uploadsProgress.jsx @ uploadsProgress.jsx:110fileEvaluate @ modules-runtime.js?hash=5d90b56…&hot=1:189require @ modules-runtime.js?hash=5d90b56…&hot=1:118meteorInstall.imports.ui.layouts.appLayout.jsx @ appLayout.jsx:12fileEvaluate @ modules-runtime.js?hash=5d90b56…&hot=1:189require @ modules-runtime.js?hash=5d90b56…&hot=1:118meteorInstall.imports.startup.client.routes.jsx @ routes.jsx:12fileEvaluate @ modules-runtime.js?hash=5d90b56…&hot=1:189require @ modules-runtime.js?hash=5d90b56…&hot=1:118meteorInstall.client.main.js @ main.js:8fileEvaluate @ modules-runtime.js?hash=5d90b56…&hot=1:189require @ modules-runtime.js?hash=5d90b56…&hot=1:118(anonymous function) @ main.js:29

here is my JSS instance:
import {create} from 'jss'
import reactJss from 'react-jss'
import vendorPrefixer from 'jss-vendor-prefixer'
import nested from 'jss-nested'
import extend from 'jss-extend'

export const jss = create();
jss.use(vendorPrefixer())
jss.use(nested())
jss.use(extend())

export const useSheet = reactJss(jss);

and a first react component from the error imports.ui.components.uploadsProgress.jsx:
const styles = {
...
}

@useSheet(styles, {named: false})
@observer
export default class UploadsProgress extends React.Component {
...
}

Is there any breaking changes in 4.x.x versions? Sorry, I didn't find it in change log.

Here is the changelog: https://github.com/cssinjs/react-jss/blob/master/changelog.md
Yes major version mostly means breaking changes. You don't need to have jss and its plugins as a separate dependency. Also you don't need to do a setup any more if you are ok with the default preset. Please reread the documentation.

Let me know if this helped.


FeignClient can not use Placeholder like ${}

Describe the bug
In FeignClientsRegistrar resolve, it use beanFactory.resolveEmbeddedValue to explain the value, but there is no EmbeddedValueResolver because PropertySourcesPlaceholderConfigurer is not init before FeignClientsRegistrar .Is it a bug or any solution to fix it.
Sample
@FeignClient(name = "${sid}", path = "test", contextId = "${sid}")

and sid: xxx in application.yml

I think the code for the main branch has already solved this problem. You can use this method to easily handle it
@Slf4j
public class MyApplicationContextInitializer implements ApplicationContextInitializer {
    @Override
    public void initialize(ConfigurableApplicationContext applicationContext) {
        ConfigurableListableBeanFactory beanFactory = applicationContext.getBeanFactory();
        if (!beanFactory.hasEmbeddedValueResolver()) {
            beanFactory.addEmbeddedValueResolver(strVal -> applicationContext.getEnvironment()
                    .resolvePlaceholders(strVal));
        }
    }
}

META-INF/spring.factories
org.springframework.context.ApplicationContextInitializer=\
  cn.haitaoss.config.MyApplicationContextInitializer

Describe the bug In FeignClientsRegistrar resolve, it use beanFactory.resolveEmbeddedValue to explain the value, but there is no EmbeddedValueResolver because PropertySourcesPlaceholderConfigurer is not init before FeignClientsRegistrar.Is it a bug or any solution to fix it.
Sample @FeignClient(name = "${sid}", path = "test", contextId = "${sid}")
and sid: xxx in application.yml

I think the code for the main branch has already solved this problem. You can use this method to easily handle it
@Slf4j
public class MyApplicationContextInitializer implements ApplicationContextInitializer {
    @Override
    public void initialize(ConfigurableApplicationContext applicationContext) {
        ConfigurableListableBeanFactory beanFactory = applicationContext.getBeanFactory();
        if (!beanFactory.hasEmbeddedValueResolver()) {
            beanFactory.addEmbeddedValueResolver(strVal -> applicationContext.getEnvironment()
                    .resolvePlaceholders(strVal));
        }
    }
}

META-INF/spring.factories
org.springframework.context.ApplicationContextInitializer=\
  cn.haitaoss.config.MyApplicationContextInitializer

Hello @qq583137502, this should work properly on the latest supported versions (4.0.4, 4.1.0). If you still face an issue on any of these versions, please provide a minimal, complete, verifiable example that reproduces the issue.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.


fix: remove upper limit for required terraform version

/run pipeline

:tada: This PR is included in version 1.1.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


File::move is not moving file

Describe the bug
File::move is not moving a file (but directories if accidentally possible)!
The line in File::move
		if (! @rename($this->getPath(), $destination))

has to be replaced by
		if (! @rename($this->getRealPath(), $destination))
``

because $this->getPath() is only referring to the directory in which the file can be found.

**CodeIgniter 4 version**
CodeIgniter4 Alpha 4

**Affected module(s)**
File

:open_mouth: When you upload a file, you can move the file normally.
But, new CodeIgniter\Files\File('/tmp/user-12.png') will fail.

I guess, this is fixed in #1809

@hwiesmann Can you confirm that this has been fixed?

@jim-parry Works for me!


WSL sees empty files/directories permissions for files/directories created under linux with ntfs-3g

After creating a bunch of files under linux with ntfs-3g, then rebooting to windows, WSL has trouble reading permissions of the newly created files. Instead of having the default permission from umask/dmask, they show up as a bunch of dashes, and directories cannot be 'ls'ed at all.
Steps to reproduce:

Have a dual booting system
(Not sure, it's possible my ntfs file system is corrupted, though chkdsk shows no error?)
Boot into linux (Arch linux) with ntfs-3g installed.
cd /j/
mkdir _test && touch _test/_test
reboot into Windows, open WSL,
cd /j/
ls -la

I end up with something that looks like this:

The _test entries have essentially no permissions.
Note that this doesn't happen on C drive, only on the other drives (d, j, k, l) I have.
If this is an issue with corrupted file system please let me know an easy way to fix it (backup software that preserve symlinks and extended attributes for instance) Given that I've found no report on the internet about this elsewhere I feel this bug could be an error on my part.
Update: happens with a freshly formatted disk as welll

Can you please provide clear steps to reproduce?
1. echo 'hello world'
2. sudo apt update
...

Hello,
Sure I've updated the first post with steps to reproduce.

Just checked that this also happens with a freshly formatted disk.
Happens in both WSL/WSL2.

Same problem here.
After this problem shows, I change permissions with chmod, and it works for a while. After a few hours working on my bash, at some point I start randomly losing access to files, with some of them showing permissions as all dashes ("----------") even though they were not created, accessed or modified, on WSL or on Windows, during this time.
Any ideas of how to fix this? This issue makes WSL unusable for me, as I have to keep doing chmod periodically to be able to access files. If I am running scripts, I never know when a script is going to fail because it cannot access the files it needs to.
Thanks.

Possibly duplicate of #4116


*ngIf affects button focus order

Bug, feature request, or proposal:
Bug
What is the expected behavior?
I would expect focus to go to the first button in the overlay menu.
What is the current behavior?
If I navigate to a simple overlay menu via keyboard and enter it, focus goes to the first button that doesn't contain an ngIf attribute, regardless of if the ngIf conditional is true.
What are the steps to reproduce?
https://stackblitz.com/edit/angular-zf82u8

Go to https://angular-zf82u8.stackblitz.io/
Tab to the button, then hit the space bar.
Note that focus goes to the second button instead of the first.

Upon initial investigation this is occuring because MatMenuItems add themselves to their menu via the addItem method during initialization.  Since it is in initialization order, items which are being stamped out by structural directives will be placed in the KeyListManager order after all of the non-structural directives.

https://github.com/angular/material2/pull/11720 sorts this out.

Closing as a duplicate of https://github.com/angular/material2/issues/11652.


(WIP) Full html rendering

Pull requests into cqm-parsers require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[ ] This pull request describes why these changes were made.
[ ] Internal ticket for this PR:
[ ] Internal ticket links to this PR
[ ] Code diff has been done and been reviewed
[ ] Tests are included and test edge cases
[ ] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Codecov Report

Merging #79 into master will decrease coverage by 84.97%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #79       +/-   ##
==========================================
- Coverage   89.14%   4.16%   -84.98%
==========================================
  Files          70      70
  Lines        1888    2400      +512
==========================================
- Hits         1683     100     -1583
- Misses        205    2300     +2095

Impacted Files
Coverage Δ

lib/html-export/qdm-patient/qdm_patient.rb
0.00% <0.00%> (-44.83%)
:arrow_down:

lib/qrda-export/catI-r5/qrda1_r5.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

lib/util/entity_helper.rb
0.00% <0.00%> (ø)

lib/ext/code.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

lib/ext/data_element.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

lib/qrda-import/entry_package.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

...rda-import/base-importers/demographics_importer.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

...-import/data-element-importers/symptom_importer.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

...mport/data-element-importers/diagnosis_importer.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

...rt/data-element-importers/device_order_importer.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 61 more

Continue to review full report at Codecov.

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


Update styled jsx

please check the yarn.lock file

woops need to fix my fork :)

Send this PR against master.

Will do tomorrow, there are two bugs in Stylis (a dependency of styled-jsx) which should be fixed in the meantime, I'll then have to release 1.0.1.
Also before we merge you may probably want to think about watch mode and hot reloading. If I am not mistaken modules outside of pages don't trigger a rebuild right?

Closing this #2095 @giuseppeg could you create an issue for watching the external files.


Blue Filtered Sunlight turns white at the edges

After a while of normal blue light, it will suddenly turn white again, as demonstrated here:

Additionally, it looks as though smooth lighting isn't... oriented correctly for all angles? While it's a smooth line on the right in that image, directly in front of me it's jagged.

I had the same issue when sideway filtering blue sunlight, maybe that one is similar. I'll look into it, thanks!
If you're curious, the problem is that I try to store 7 color channels in a single variable - that's sometimes a bit tight in these 32bits.

I could see that being somewhat troublesome. I suppose a big reason for that is performance and save size concerns?

Not really, the reason is that minecraft only ever accounted for 32bits of light. And unless I want to completely break compatibility, I am locked into this.

I see. It seems a bit excessive for how lighting works in the original game, but I don't really know the requirements of that.

1.7.10 version is out of date, the rework is written from scratch, so I close this bug.


Merging Code from angelescuo

I have try to merge the request but since your repository is not up to date with GhostBSD/ghostbsd-build it is impossible to merge please keep your ghostbsd-build update to date with GhostBSD/ghostbsd-build.
I will do the same thing that I have done last time but you will not have the credit on GitHub for that change.
To have any of your fork up to date please see https://help.github.com/articles/syncing-a-fork/
Your forks need to be in sync with the upstream repos.
Now you need to delete your ghostbsd-build fork and refork ghostbsd-build.


inreplace: support for audit arg in non-block form

Provides feature parity between the block and non-block forms of
inreplace by creating a four-argument version of the non-block form,
where the fourth argument is an optional Boolean value, defaulting to
true, which specifies whether a failed inreplace should cause an
InreplaceError error to be raised. The fourth argument is passed along
to StringInreplaceExtension#gsub!, which already supports an optional
audit_result argument.
This resolves the Catch-22 that single replacements aren't permissible
in the block form (in that they now cause brew audit to complain), but
the audit_result argument is not available in the non-block form.

CC @UniqMartin RE: https://github.com/Homebrew/homebrew-core/pull/2940#issuecomment-233355225

:+1: Haven't tested this personally, but I'd be very surprised if this breaks anything.

@UniqMartin Yup, tested it a bit:
iMac-TMP:local joe$ brew irb
==> Interactive Homebrew Shell
Example commands available with: brew irb --examples
irb(main):001:0> Utils::Inreplace.inreplace "dog.txt", "hello", "world"
=> nil
irb(main):002:0> File.read "dog.txt"
=> "world\nyellau\n"
irb(main):003:0> FileUtils.cp "dog.txt.orig", "dog.txt"
=> nil
irb(main):004:0> Utils::Inreplace.inreplace "dog.txt", "hello", "world", true
=> nil
irb(main):005:0> File.read "dog.txt"
=> "world\nyellau\n"
irb(main):006:0> FileUtils.cp "dog.txt.orig", "dog.txt"
=> nil
irb(main):007:0> Utils::Inreplace.inreplace "dog.txt", "yellow", "world"
Utils::InreplaceError: inreplace failed
dog.txt:
  expected replacement of "yellow" with "world"

	from /usr/local/Library/Homebrew/utils/inreplace.rb:36:in `inreplace'
	from (irb):7
	from /usr/local/Library/Homebrew/brew.rb:87:in `<main>'
irb(main):008:0> Utils::Inreplace.inreplace "dog.txt", "yellow", "world", true
Utils::InreplaceError: inreplace failed
dog.txt:
  expected replacement of "yellow" with "world"

	from /usr/local/Library/Homebrew/utils/inreplace.rb:36:in `inreplace'
	from (irb):8
	from /usr/local/Library/Homebrew/brew.rb:87:in `<main>'
irb(main):009:0> Utils::Inreplace.inreplace "dog.txt", "yellow", "world", false
=> nil
irb(main):010:0> File.read "dog.txt"
=> "hello\nyellau\n"
irb(main):011:0> Utils::Inreplace.inreplace "dog.txt", "yellau", "yellow", false
=> nil
irb(main):012:0> File.read "dog.txt"
=> "hello\nyellow\n"
irb(main):013:0> Utils::Inreplace.inreplace "dog.txt", "yellow", "world", true
=> nil
irb(main):014:0> Utils::Inreplace.inreplace "dog.txt", "yellow", "world"
Utils::InreplaceError: inreplace failed
dog.txt:
  expected replacement of "yellow" with "world"

	from /usr/local/Library/Homebrew/utils/inreplace.rb:36:in `inreplace'
	from (irb):14
	from /usr/local/Library/Homebrew/brew.rb:87:in `<main>'
irb(main):015:0> File.read "dog.txt"
=> "hello\nworld\n"
irb(main):016:0> Utils::Inreplace.inreplace "dog.txt", "yellow", "world", false
=> nil
irb(main):017:0> ^D


Skip XQJ SWIG bindings if no Zorba API JAR

XQJ JAR is dependent on zorba_api.jar, so XQJ Jar generation needs to be skipped if zorba_api.jar is not found.
Actually, this issue gets exposed because CMakeLists.txt for zorba_api.jar and XQJ jar check for Java in different ways: the former looks for java include path, while the latter searches for javac executable. On my system these checks give different results.

@fcavalieri It looks good to me. Do you approve it?

@wcandillon I am on it.

@fcavalieri any news on this?

Deprecated by #165


crystal won't run on my OS X install

I've updated to crystal 0.15, but I haven't really used it in a while. Now when I try to use it, I always get:
dyld: Library not loaded: /usr/local/opt/bdw-gc/lib/libgc.1.dylib
  Referenced from: /usr/local/bin/crystal
  Reason: image not found
Trace/BPT trap: 5

Seems like I was actually missing a dependency which I may have accidentally deleted.


Mouse clicks do not work

Hello everybody, i have a problem with scrcpy , i did it succesfully and i can see the mobile screen on my windows BUT my mouse in windows doesnt work on the mirror mobile screen , what is the probelm ?

Which device?
See https://github.com/Genymobile/scrcpy/issues/70#issuecomment-373286323.

Same here. I can see the mobile screen but mouse doesn't seem to do anything.
Xiaomi Mi 9.
Thank you!

thanks. my bro.i use xiaomi too.i didn't realize there is the second usb option.

Is that setting exclusive to the Xiaomi? Doesn't exist on my Moto G5 Plus.

I'm using Oppo and that option doesnt appear in the settings. It has only USB Debugging

I'm using Oppo and that option doesnt appear in the settings. It has only USB Debugging

Is there any error message in the console when you click?
This is what it said ( [server] WARN: Ignore touch event, it was generated for a different device size )

Then see #2031.


Statsmodel reference to import AMRA module is outdated in fmrisim

The package name has changed since statsmodels is now in its 0.13 version. Instead of
from statsmodels.tsa.arima_model import ARMA
the code should be changed to the newer library. Currently, the noise generation is not working.

This has been fixed (updated to new API) in https://github.com/brainiak/brainiak/pull/511. Waiting on some further issues to be fixed before merge but feel free to use it now.

Thank you! I changed the lines on my local copy.