switch to curl for fetching binaries, rework fetching binaries

rename containerd setup script to better reflect what it does
consistently switch to curl for containerd and shellcheck installs (which we have more widely in our CI images and scripts)
fold installing shellcheck into main shellcheck script and drop dockerized version in favor of host binaries aligning with other scripts

resolves https://github.com/kubernetes/registry.k8s.io/pull/226#issuecomment-1512271462 (we don't have wget in the infra-tools image, we do however have curl)

oh hmm, well have to update the CI job, I guess the easiest thing to do here is leave a stub script until this merges, then drop calling the script and clean it up

OK, that'll do for now https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/registry.k8s.io/230/pull-registry-shellcheck/1648130127550222336 ✅

For some reason the postsubmit didn't trigger despite being configured for all merges ...

Working on subsequent merges https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-registry-push-images/1648298079301931008


alpha.9 is not properly set up in npm

Bug, feature request, or proposal:
When I put "@angular2-material": "^2.0.0-alpha.9", in my project's package.json and do an npm outdated depth=0,  I get a lengthy npm error report. This happens whether or not the old alpha.8-2 entries are in package.json i.e., in both cases.  The error report is:
$ npm outdated --depth=0
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\                                                                                node_modules\npm\bin\npm-cli.js" "outdated" "--depth=0"
npm ERR! node v5.0.0
npm ERR! npm  v3.3.6
npm ERR! code EMISSINGARG
npm ERR! typeerror Error: Missing required argument #2
npm ERR! typeerror     at exports.findRequirement (C:\Program Files\nodejs\node_                                                                                modules\npm\lib\install\deps.js:475:3)
npm ERR! typeerror     at C:\Program Files\nodejs\node_modules\npm\lib\install\d                                                                                eps.js:90:19
npm ERR! typeerror     at zalgoSafe (C:\Program Files\nodejs\node_modules\npm\no                                                                                de_modules\dezalgo\dezalgo.js:20:10)
npm ERR! typeerror     at finalize (C:\Program Files\nodejs\node_modules\npm\nod                                                                                e_modules\realize-package-specifier\index.js:37:5)
npm ERR! typeerror     at C:\Program Files\nodejs\node_modules\npm\node_modules\                                                                                realize-package-specifier\index.js:22:20
npm ERR! typeerror     at FSReqWrap.oncomplete (fs.js:82:15)
npm ERR! typeerror This is an error with npm itself. Please report this error at                                                                                :
npm ERR! typeerror     http://github.com/npm/npm/issues
What is the expected behavior?
I should get a standard outdated report showing alpha.9 as MISSING and alpha.9 as Latest available.
What is the current behavior?
I get the above error statement, not the standard npm outdated report.

use @angular/material instead.

I tried @angular/material, and get the same error - (see below). I also
have to say this new name is a mistake by the MD team because it creates
confusion about which Angular it matches.  Here is the continuing error
report.
$ npm outdated --depth=0
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program
Files\nodejs\node_modules\npm\bin\npm-cli.js" "outdated" "--depth=0"
npm ERR! node v5.0.0
npm ERR! npm  v3.3.6
npm ERR! code EMISSINGARG
npm ERR! typeerror Error: Missing required argument #2
npm ERR! typeerror     at exports.findRequirement (C:\Program
Files\nodejs\node_modules\npm\lib\install\deps.js:475:3)
npm ERR! typeerror     at C:\Program
Files\nodejs\node_modules\npm\lib\install\deps.js:90:19
npm ERR! typeerror     at zalgoSafe (C:\Program
Files\nodejs\node_modules\npm\node_modules\dezalgo\dezalgo.js:20:10)
npm ERR! typeerror     at finalize (C:\Program
Files\nodejs\node_modules\npm\node_modules\realize-package-specifier\index.js:37:5)
npm ERR! typeerror     at C:\Program
Files\nodejs\node_modules\npm\node_modules\realize-package-specifier\index.js:22:20
npm ERR! typeerror     at FSReqWrap.oncomplete (fs.js:82:15)
npm ERR! typeerror This is an error with npm itself. Please report this
error at:
npm ERR! typeerror     http://github.com/npm/npm/issues
On Thu, Oct 6, 2016 at 2:43 AM, Pascal Temel<EMAIL_ADDRESS>wrote:

use @angular/material instead.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/material2/issues/1435#issuecomment-251879934,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADDSb58nIzi13ARRCWzJVX8tx0votrUbks5qxJh3gaJpZM4KPMjz
.

--
Mike Laird
12 Arbor Creek Drive, Pittsford, New York 14534
<EMAIL_ADDRESS>". . . remembering on both sides that civility is not a sign of weakness,
and sincerity is always subject to proof. Let us never negotiate out of
fear, but let us never fear to negotiate."  - John F. Kennedy

There is no alpha.9 version for the old angular2-material packages. All new updates are on @angular/material. Latest version is 2.0.0-alpha.9-3.
https://www.npmjs.com/package/@angular/material
I'd suggest wiping out your node_module and reinstalling, possibly with a node version other than 5.*, which isn't supported any longer. As far as I can tell, this isn't a problem with material and is more likely an environment issue.

@Jeremy Elbourn,  Thanks. You guessed well.  I had Node 5.0, and when I
re-installed to Node 4.6, everything worked.
If you are part of the Angular2 Material team, note that neither the npm
page nor the Getting Started page say anything about Node 5.0 not being
supported.  FWIW, I find it odd to install angular/material  and get a
folder named @angular-material.  But/overall, @thanks-I'm OK.
;-)
On Fri, Oct 7, 2016 at 3:32 PM, Jeremy Elbourn<EMAIL_ADDRESS>wrote:

There is no alpha.9 version for the old angular2-material packages. All
new updates are on @angular/material. Latest version is 2.0.0-alpha.9-3.
https://www.npmjs.com/package/@angular/material
I'd suggest wiping out your node_module and reinstalling, possibly with a
node version other than 5.*, which isn't supported any longer. As far as I
can tell, this isn't a problem with material and is more likely an
environment issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/material2/issues/1435#issuecomment-252341426,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADDSb4Qb948bEGqdsPjIKiSn-uPBlwxLks5qxp5jgaJpZM4KPMjz
.

--
Mike Laird
12 Arbor Creek Drive, Pittsford, New York 14534
<EMAIL_ADDRESS>". . . remembering on both sides that civility is not a sign of weakness,
and sincerity is always subject to proof. Let us never negotiate out of
fear, but let us never fear to negotiate."  - John F. Kennedy


Mobile Safari landscape zoom level

When rotating from portrait to landscape (iPhone4 w/ iOS5), the default zoom level is a little janky and forces the user to manually zoom out so the page is coherent.

I know that forcing a max-scale solves the problem but not sure if you guys are philosophically against restricting the user from zooming the page. It's always been my style because if you've designed the page right the user shouldn't need to zoom in on anything.
Use:
meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0"
instead of:
meta name="viewport" content="width=device-width, initial-scale=1.0"

Fixing maximum-scale to 1.0 is not good for accessibility reasons.
Actually this was a iOS bug: the viewport meta element properties seem to be ignored when Accessibility Zoom has been turned on in iOS
http://openradar.appspot.com/9025220

Thanks for the link! So is there not actually a better fix than fixing max-scale? Or am I missing something?

This is the easiest way to handle the scaling issue. For now, we'll leave it. Please open another issue if there is a better (and equally light) solution.


fix: 虚拟渲染修复

Description
修复虚拟渲染现在不生效的问题，并解决虚拟渲染过程中节点不显示 对应边不显示的内容

Motivation and Context

Types of changes

[✅] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Enhancement (changes that improvement of current feature or performance)
[ ] Refactoring (changes that neither fixes a bug nor adds a feature)
[ ] Test Case (changes that add missing tests or correct existing tests)
[ ] Code style optimization (changes that do not affect the meaning of the code)
[ ] Docs (changes that only update documentation)
[ ] Chore (changes that don't modify src or test files)

Self Check before Merge

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

@struggleRoue 这个分支解决了这个问题吗？如果解决了什么时候准备合入master？为什么这个问题closed了？


Scene. Add Behaviors to the scene class

I had some idea how to use Behaviors with the Scene, but to my regret I did not find such an opportunity.
So, check this PR, please :)
P.S. I made it most similar to how it implemented in the Mesh class.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Or, maybe I should to make an empty node and attach the Behavior to them? What is the best practice?

Snapshot stored with reference name:
refs/pull/13674/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13674/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13674/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13674/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13674/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13674/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13674/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13674/merge#BCU1XR#0

I wanted to have a standalone class like GameMode or any other controller that specific for current scene. The Behavior interface allow me to pack my custom behavior and share it between projects or scenes inside a project. And also I can pack the init and detach behavior into the class.
Without Behavior on the scene I can do same things, but it requires me to copy-paste code relative to attach and detach functions and make some relations between a class instance to some scene.
And also look the docs here https://doc.babylonjs.com/features/featuresDeepDive/behaviors

Babylon.js v3.1 introduced a new component based tools: the behaviors. A behavior is a simple class that can be attached to a target where it will provide a specific set of features. Features will be triggered by defined events.

Here talked about a target, not a Node or a Mesh, so I thought here talking about any BabylonJS's entity. So, it is strange for me, why I can't attach my behavior class to the scene :)

But there are no scene behaviors implemented...
I understand the question - why can't we add behavior to a scene, but - what behavior would you add to a scene? Do you want to use the behaviors to a form of a plugin-system?

Hello! Thank you for bringing this up. After careful consideration and internal discussion, we have come to the conclusion that it would be best not to implement any changes to Behavior at this time. This is because we want to ensure that any changes we make are fully compatible with the GLTF behaviors extension (https://docs.google.com/document/d/1MT7gL-IEn_PUw-4XGBazMxsyqsxqgAVGYcNeC4Cj_9Q/edit#) when it is finalized. We appreciate your understanding and patience as we work to ensure the best possible outcome for everyone involved.


Send an 'Accept' header in the image request

Some urls, e.g. this one - http://www.congreso.gob.gt/manager/images/69DBC2D6-2EE6-3EA7-411F-07C91997560D.jpg, don't respond correctly if there's no Accept header in the request.
https://everypolitician-image-proxy.herokuapp.com/http%3A%2F%2Fwww.congreso.gob.gt%2Fmanager%2Fimages%2F69DBC2D6-2EE6-3EA7-411F-07C91997560D.jpg/140/140.jpg
This change adds an Accept: image/* header to each request for external images.
I'm not 100% sure that this is the correct and/or best thing to be doing, but it certainly fixes it for the specific case of images on www.congreso.gob.gt.

Thanks! Changed to */* though.


[Microsoft.Advisor] Add isAlertable property to metadata entity properties. (API is not live yet)

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Can one of the admins verify this patch?

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/6390
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/6390/commits/2fc54b3527940d7ffbe20a0b7bcc8b4e3a59e38d

Automation for azure-sdk-for-ruby

To make the spelling happy, you'd need to add "Alertable" to the words array in https://github.com/Azure/azure-rest-api-specs/blob/master/cSpell.json#L5

Automation for azure-sdk-for-java

To make the spelling happy, you'd need to add "Alertable" to the words array in https://github.com/Azure/azure-rest-api-specs/blob/master/cSpell.json#L5

Added "Alertable" in spell.json.
node SDK failure is known thing. It is due to some infra issue.


It should be possible to specify a background image/colour etc... for cards

A card (or perhaps a default setting at the app level) should be able to specify a default background consisting of:

Solid colours
Gradients
Images (with size, position, repeat and opacity control)

In the first instance, I imagine this being attached to the page's <body> tag.

Inspiration from here: https://revealjs.com/backgrounds/


[Bug]: mySQL store boolean inputs false and true as 0 and 1 when table column type is varchar

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
mySQL insert or update query saves boolean values false and true as 0 and 1 even when column type is varchar

Steps To Reproduce

Create a CRUD using mySQL table that has a varchar column
During update and insert use false and true to update the value and observe that DB stores it as 1/0 instead

Environment
Production
Version
Cloud

@ramsaptami the issue is not clear. First of all MongoDB automatically identify the data type when we create collection and insert documents in it, thus we don't create any table with data type in MongoDB. Secondly video available in the Current Behavior section is all about MySQL. Can you please clarify?

@ramsaptami @sumitsum By default MySQL does not contain built-in Boolean or Bool data type. MySQL TINYINT datatype instead, and converts every Boolean input (true/false) into 0 or 1 which are integer value. Example given below :

If any column is VARCHAR or TEXT type and We want to store Boolean data in it then MySQL should store those values as String of 0 or 1. Example given below :

If We have to store true or false into VARCHAR We have to provide input as string ('true' or 'false').  Can we consider this as an issue?

This issue is occurring because when using prepared statement with mustache binding, the data type of true is getting evaluated as boolean and MySQL plugin has handled the boolean type that way:
else if (DataType.BOOLEAN.equals(valueType)) {
                connectionStatement.bind((index - 1), Boolean.parseBoolean(value) == TRUE ? 1 : 0);
            }

Ideally this issue should be resolved within the framework decided by the datatype project cc: @nidhi-nair @rohan-arthur @ajinkyakulkarni . Hence, un-assigning Somnath.

This is not an issue. This is the behavior of MySQL. There is no boolean data type in MySQL. MySQL interprets true as 1 and false as 0.  Even if you create a table with one column having a boolean data type MySQL won't restrict you to do so. It will allow you to create the table and you will notice that the type of your requested boolean column is of type TINYINT.

cc: @sribalajig @riteshkew

@subrata71 IMO, the issue here is that the user is trying to store string true or false but it is getting stored as 0 or 1 (even if true / false is wrapped within quotes ?) - can you please investigate from this PoV ?

Thanks, Sumit. If I understand the requirement correctly then I would say that it's already resolved.
{{true}} vs {{"true"}}
The former is treated as a boolean and the latter is treated as a string now. This is already in release and waiting to be shipped into production through the next release.
@sumitsum

@subrata71 apologies, the video use case looks slightly different - can you please check if this works or if we can make it work - the user has {{my_binding}} where the binding itself receives the value as a string true . The intent of the user is to save the string true as a string since the column type is varchar.

@sumitsum This should work as you said.
If the value of my_binding is evaluated to string "true" then "true" will be stored in that column.

@ramsaptami can you please verify if this has been fixed in release ?

Still getting saved as 0/1 when the value is false/true @sumitsum

@ramsaptami asking just for confirmation - were you able to verify the use case exactly as shown in the description video ?

Yep, created a CRUD of the same table and inserted true/false values expecting them to save as true/false - which it did thankfully! :)
@subrata71 @sumitsum


Which version of clip-vit-large-patch14 is used?

Does Bakllava checkpoints uses openai/clip-vit-large-patch14 or openai/clip-vit-large-patch14-336 as the vision tower?
In finetune_lora.sh, it uses --vision_tower openai/clip-vit-large-patch14.
In finetune.sh, it uses --vision_tower openai/clip-vit-large-patch14-336.

@pharaouk , do you have any updates here?

--vision_tower openai/clip-vit-large-patch14-336


Nodeport - connect to DB?

How does one connect to the database via tools like DBVisualizer from outside of the cluster? I have deployed Db2 on OCP 3.11. I tried connecting using IP:NodePort, IP:50000. Created route, tried hostname:50000. None of the combination work. Anyone able to connect to the DB from outside of the cluster? How?

You need to use the NodePort associated with the service as well -- IE. you cannot use port 50000 from outside ..  When connecting via NodePort IP, you can simply direct to the hostname/IP of the master node and it'll get routed accordingly.
Example from my OpenShift cluster,
[root@harihari-master-1 ~]# oc get svc | grep -i engn
db2wh-1582088279-db2u-engn-svc   NodePort    <IP_ADDRESS>     <none>        50000:31881/TCP,50001:31977/TCP                                                   1d

[root@harihari-master-1 ~]# oc describe svc db2wh-1582088279-db2u-engn-svc | grep -i nodeport
Type:                     NodePort
NodePort:                 legacy-server  31881/TCP
NodePort:                 ssl-server  31977/TCP

Thanks @adesilva74, could you please submit a PR against our DOC on how to
@aroute Please reopen if you feel we did not provide enough guidance.
@rayyaoibm Could you please submit a PR for our README that further details this?


[Bug] Kernel wireguard outbound not work when enabled TUN

Verify steps

[X] I have read the documentation and understand the meaning of all the configuration items I have written, rather than just piling up seemingly useful options or default values.
[X] I have carefully reviewed the documentation and have not resolved the issue.
[X] I have searched the Issue Tracker for the issue I want to raise and did not find it.
[ ] I am a non-Chinese user.
[X] I have tested with the latest Alpha branch version, and the issue still persists.
[X] I have provided the server and client configuration files and processes that can reproduce the issue locally, rather than a sanitized complex client configuration file.
[X] I provided the simplest configuration that can be used to reproduce the errors in my report, rather than relying on remote servers or piling on a lot of unnecessary configurations for reproduction.
[X] I have provided complete logs, rather than just the parts I think are useful out of confidence in my own intelligence.
[X] I have directly reproduced the error using the Mihomo command-line program, rather than using other tools or scripts.

Operating System
Linux
System Version
Linux 5.15.163-1.el7.x86_64
Mihomo Version
Mihomo Meta v1.19.0 linux amd64 with go1.20.14 Mon Dec  9 09:51:29 UTC 2024
Use tags: with_gvisor
Configuration File
mixed-port: 7890
allow-lan: true
bind-address: '*'
mode: rule
log-level: info

dns:
  enable: true
  ipv6: false
  listen: <IP_ADDRESS>:53
  default-nameserver:
    - <IP_ADDRESS>
    - <IP_ADDRESS>
  enhanced-mode: redir-host
  nameserver:
    - https://<IP_ADDRESS>/dns-query
    - tls://<IP_ADDRESS>:853
    - https://<IP_ADDRESS>/dns-query
  fallback:
    - tcp://<IP_ADDRESS>:443
    - tls://dns.google

sniffer:
  enable: true
  force-dns-mapping: true
  parse-pure-ip: true
  sniff:
    HTTP:
      ports: [80, 8080-8880]
    TLS:
      ports: [443, 8443]
    QUIC:
      ports: [443, 8443]

tun:
  enable: true
  stack: mixed
  auto-route: true
  auto-redirect: true
  auto-detect-interface: true
  dns-hijack:
    - udp://any:53
  device: utun0
  strict-route: false
  udp-timeout: 300
  endpoint-independent-nat: false
  route-exclude-address:
  - <IP_ADDRESS>/8
  - <IP_ADDRESS>/10
  - <IP_ADDRESS>/12
  - <IP_ADDRESS>/16
  - fc00::/7
  include-uid:
  - 1020

proxies:
  - {name: socks, server: <IP_ADDRESS>, port: 23456, type: socks5, udp: true}

proxy-groups:
  - name: PROXY
    type: select
    proxies:
      - socks
  - name: Others
    type: select
    proxies:
      - PROXY
      - DIRECT

rules:
  - GEOIP,LAN,DIRECT
  - GEOIP,CN,DIRECT
  - MATCH,Others

Description
The system has already setup up a kernel level wireguard NIC.
> wg
interface: wg0
  public key: HIDDEN
  private key: (hidden)
  listening port: 51820

peer: HIDDEN
  endpoint: HIDDEN
  allowed ips: <IP_ADDRESS>/32

peer: HIDDEN
  endpoint: HIDDEN
  allowed ips: <IP_ADDRESS>/32, <IP_ADDRESS>/24, <IP_ADDRESS>/10

> ip route
default via <IP_ADDRESS> dev bond0 proto static metric 300
<IP_ADDRESS>/24 dev bond0 proto kernel scope link src <IP_ADDRESS> metric 300
<IP_ADDRESS>/10 dev wg0 scope link
<IP_ADDRESS>/16 dev docker0 proto kernel scope link src <IP_ADDRESS>
OMIT SOME DOCKER BRIDGE
<IP_ADDRESS>/24 dev wg0 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev wg0 scope link
<IP_ADDRESS>/30 dev utun0 proto kernel scope link src <IP_ADDRESS>

I want to use the proxy (socks5) that already been setup on host <IP_ADDRESS>:23456. So without Meta, I can successfully
curl -x socks5://<IP_ADDRESS>:23456 https://www.google.com
Now, the problem is, the Linux server is a shared resource with others, I'd like to create a TUN device only for myself (tun.include-uid).
So I tried to use tun module on Meta with the above configuration. If I do not enable the tun module, the proxy through externel wireguard socks5 works fine (I can verify it by test the latency on metacubexd dashboard). But when I enable the tun, the socks proxy does not work. I have already excluded the wireguard routes by specifying tun.route-exclude-address
Reproduction Steps
See above
Logs
level=warning msg="[TCP] dial Others (match Match/) <IP_ADDRESS>:58498 --> <IP_ADDRESS>:853 error: <IP_ADDRESS>:23456 connect error: connect failed: dial tcp <IP_ADDRESS>:23456: i/o timeout"
level=warning msg="[TCP] dial PROXY (match RuleSet/proxy) <IP_ADDRESS>:53110 --> dns.cloudflare.com:443 error: <IP_ADDRESS>:23456 connect error: connect failed: dial tcp <IP_ADDRESS>:23456: i/o timeout"

https://wiki.metacubex.one/en/config/proxies/#interface-name
It seems you haven't fully reviewed the document


feat(engine): ensure cache volumes are namespaced

fixes #7211
This PR namespaces the cache volumes so that across the modules they have different keys.

one additional issue I am running into is how to hide this internal api cache. We don't want this internal api to be exposed to SDK's.
I was looking for patterns in code around this, and noticed some api's with name like __internal<SOMETHING>, is that an ok pattern to use?

I think this PR is ready for final review/merge

We should probably review + merge https://github.com/dagger/dagger/pull/8971 first? cc @vito is that one ready to go?

@jedevc I flew too close to the sun with the last few commits and haven't had time to hunt down what went wrong, so I just pushed HEAD~2:HEAD and hopefully it'll pass now. I'm good with reviewing + merging it first assuming it passes.

I know it's annoying, but I'm going to remove this from the milestone - it's frustrating if it won't make it in, but I know there's still issues outstanding that we should take the time to properly understand and fix (cc @rajatjindal do you have an update on those, I remember we discussed them sync last week).
With this as the last feature remaining in the milestone, I don't think we should hold the entire release for this to be ready.

I know it's annoying, but I'm going to remove this from the milestone - it's frustrating if it won't make it in, but I know there's still issues outstanding that we should take the time to properly understand and fix (cc @rajatjindal do you have an update on those, I remember we discussed them sync last week).
With this as the last feature remaining in the milestone, I don't think we should hold the entire release for this to be ready.

Hi @jedevc
Yeah, I understand. I am still working through the other issue (update-cmd, in retrospect I should have prioritized this issue as the other one was moved out of the milestone earlier). I will get back to this issue tomorrow, but I guess that would be too late for the release.


Error: Notifee native module not found.

Hi after installation in my main screen i can import notifee but when use like notifee.displayNotification(JSON.parse(message.data.notifee)) it crashing with the error : Error: Notifee native module not found.
Installed with yarn all steps done correctly made clean build it works after install until I call notifee.

"@notifee/react-native": "^5.5.0",
"@react-native-async-storage/async-storage": "^1.17.7",
"@react-native-community/blur": "^4.1.0",
"@react-native-community/netinfo": "^8.3.1",
"@react-native-firebase/app": "^15.2.0",
"@react-native-firebase/auth": "^15.2.0",
"@react-native-firebase/database": "^15.2.0",
"@react-native-firebase/firestore": "^15.2.0",
"@react-native-firebase/messaging": "^15.2.0",
"@react-native-firebase/storage": "^15.2.0",
"@react-native-masked-view/masked-view": "^0.2.7",
"@react-navigation/bottom-tabs": "^6.3.1",
"@react-navigation/native": "^6.0.10",
"@react-navigation/native-stack": "^6.6.2",
"@types/react-combine-reducers": "^1.0.0",
"@types/react-native-snap-carousel": "^3.8.5",
"axios": "^0.27.2",
"chroma-js": "^2.4.2",
"expo": "^45.0.0",
"expo-image-manipulator": "~10.3.1",
"expo-image-picker": "~13.1.1",
"expo-linear-gradient": "^11.3.0",
"expo-localization": "~13.0.0",
"expo-updates": "~0.13.2",
"i18next": "^21.8.5",
"libphonenumber-js": "^1.10.6",
"moment": "^2.29.3",
"moment-timezone": "^0.5.34",
"react": "17.0.2",
"react-combine-reducers": "^1.1.1",
"react-countdown": "^2.3.2",
"react-i18next": "^11.16.9",
"react-native": "0.68.2",

If this happens:

Error: Notifee native module not found.

Then this statement is an assumption as opposed to a fact, and it is incorrect for some unknown reason:

Installed with yarn all steps done correctly made clean build it works after install until I call notifee.

You have not done all the steps correctly and installed notifee and built notifee correctly, because the native module is missing

If this happens:

Error: Notifee native module not found.

Then this statement is an assumption as opposed to a fact, and it is incorrect for some unknown reason:

Installed with yarn all steps done correctly made clean build it works after install until I call notifee.

You have not done all the steps correctly and installed notifee and built notifee correctly, because the native module is missing

Hi, mikehardy I followd documentation full wiped node pods cache restarted pc and re-installed
but still same. I have bare-react-native project with expo installed.
Using Yarn
yarn add @notifee/react-native
For iOS
cd ios/ && pod install --repo-update
npx react-native run-ios
When U import notifee no problem but when i created component with it, still throws error.
Expo SDK 45 maybe inceremental issue or pod error
My Component :
import notifee from '@notifee/react-native';

export async function onDisplayNotification(remoteMessage: any) {
  const channelId = await notifee.createChannel({
    id: 'default',
    name: 'Default Channel',
  });

  // Required for iOS
  // See https://notifee.app/react-native/docs/ios/permissions
  await notifee.requestPermission();

  // Sometime later...
  await notifee.displayNotification({
    id: '123',
    title: remoteMessage.notification.title,
    body: remoteMessage.notification.body,
    android: {
      channelId,
    },
  });
}

My POD File
$RNFirebaseAsStaticFramework = true
require File.join(File.dirname(`node --print "require.resolve('expo/package.json')"`), "scripts/autolinking")
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

platform :ios, '13.0'
install! 'cocoapods', :deterministic_uuids => false

target 'TestApp' do
  use_expo_modules!
  use_frameworks!

  pod 'RNPurchases', :path => '../node_modules/react-native-purchases'

  post_integrate do |installer|
    begin
      expo_patch_react_imports!(installer)
    rescue => e
      Pod::UI.warn e
    end
    begin
      expo_patch_react_imports!(installer)
    rescue => e
      Pod::UI.warn e
    end
  end
  config = use_native_modules!

  # Flags change depending on the env values.
  flags = get_default_flags()

  use_react_native!(
    :path => config[:reactNativePath],
    # to enable hermes on iOS, change `false` to `true` and then install pods
    :hermes_enabled => flags[:hermes_enabled],
    :fabric_enabled => flags[:fabric_enabled],
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

  # Enables Flipper.
  #
  # Note that if you have use_frameworks! enabled, Flipper will not work and
  # you should disable the next line.
  #use_flipper!()

  post_install do |installer|
    react_native_post_install(installer)
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end
end

Error: Notifee native module not found.
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.

In simulation I menage to enter home screen with notifee. But with xCode it still gives same error at the moment. In terminal it was google map import issue therefore I removed it. But in real device same error

with npx react-native run-ios --device 'Device Name' it worked on real device but xcode builds not okay with I don't get it

its not solve yet!

@Garrysahota , I am facing the same issue, it seems that autolink is not working well, it does not include the necessary pod in the podfile for ios.
To solve it, I had to manually link it by running the following command:
npx react-native link @notifee/react-native
Jus to take it into account, my project has different xcode targets, im not sure if this can cause autolink not to work as expected

I am getting the, even tried the starter react project.
npx create-expo-app reactBasic
npm install --save @notifee/react-native and or the yarn version
added import to app.js and get the same error

@rubberduckyint expo --> https://notifee.app/react-native/docs/installation#expo-support
I did not see you mention the plugin

FOrget everthing and use "npx react-native link @notifee/react-native". It will work .

@vikasattri no one should ever use the link command anymore, and in fact it does not exist in the react-native CLI in current versions as far as I know. The need to use it is the sign of a damaged / broken react-native integration and should be investigated as such until you find and fix the reason it seems link is needed

i do all steps on notifee's documentation, but don't have sucess. i tryied "npx react-native link @notifee/react-native". Not sucess. say "link unknown comand".

@CaioCesarFranklin

no one should ever use the link command anymore, and in fact it does not exist in the react-native CLI in current versions as far as I know

So your results are as expected for the "link" attempt.
no on should use link, the apparent need to do so is a sign your react-native application has a problem and should be investigated as such
This issue is closed and I'm going to close it. New people with new problems should open new issues, but they should definitely make sure they can create a fresh test app (npx react-native init NotifeeTestIntegration) and add the module to it following the instructions and get it working before asking for support. The module definitely works and there is not enough time in the world to help every react-native user with integration problems unfortunately


Remove container from Tailwind config

It seems like they are removing the container config:
https://github.com/shadcn-ui/ui/discussions/2066

This isn't created by a maintainer and is one of hundreds of PRs. If and once it is merged in, then we will consider it!


Improved Dockerfile and added Docker-Compose

Hi,
I optimised your Dockerfile and reduced the Image size from around 1.20GB to around 195MB. This also reduced build times and container startup a lot. Also added a simple docker-compose.yaml for starters.
Looking forward to here from you. thost96

Hi thost96,
I am grateful for your contribution to our project, I hope we can work together further.
If you need help in the project, or have any suggestions for the development of my projects, you can write to me. <3


[HotFix] [SVCS-697] Delay URL Build/Sign for GoogleCloud

Ticket
https://openscience.atlassian.net/browse/SVCS-697
Purpose
Delay URL Build/Sign for GoogleCloud.
For more information, refer to the JIRA ticket and Sentry errors.
Changes
Use functool.partial() to delay building and signing URL until the request is actually made.
Side effects
No
QA Notes
Dev QA only. Monitor the Sentry for errors.
Deployment Notes
No

Coverage increased (+0.001%) to 89.957% when pulling d552440da5e359e8de9fc23f53a3277efddfbea1 on cslzchen:hotfix/gc-delay-url-signing into 11b6f549d4939c7520a3d33217e689669fd19252 on CenterForOpenScience:master.

No test update and the coverage increase is due to 1 more line in covered code.


Saving hasMany item gives error

Discussed in https://github.com/duncanmcclean/runway/discussions/266

Originally posted by Glenf May  9, 2023
Hello again,
When I try to save hasMany related child item, it gives me following error:
Call to undefined method /App/Models/ChildModelName::parent_item_id()
Saving in it self works correctly. I tried to follow this up and things point to here: https://github.com/duncanmcclean/runway/blob/27d1850a5b0a3baeeee55606bcc2b4cb389959ea/src/Http/Controllers/ResourceController.php#L298
I'll build you an example project here: https://github.com/Glenf/runway-hasMany-issue
Steps to reproduce (with example project):

Open Statamic CP
Click 'Parents' in the sidebar
Select a parent
Select a child under the parent
Click 'Save' on child

This should now be fixed in the latest release(s).
Runway will try to guess the relationship name (the name of the method in your model) but because the field handle & the relationship name are so different (standard_parent_id and parent), it's unable to do that correctly.
Instead, you can specify the relationship name you wish to be used in the field's config using the new relationship_name setting:
[
    "handle" => "standard_parent_id",
    "field" => [
        "max_items" => 1,
        "mode" => "typeahead",
        "create" => false,
        "display" => "Parent Item",
        "type" => "belongs_to",
        "icon" => "belongs_to",
        "listable" => "hidden",
        "instructions_position" => "above",
        "visibility" => "visible",
        "resource" => "parent",
        'relationship_name' => 'parent',
    ]
],


Fix: handle requests without session attributes

Proposed changes
When an error is returned from Alexa, an exception is thrown because the getSessionAttributes method isn't a member of ErrorRequest. This PR adds a check for the existence of getSessionAttributes.
Types of changes

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

Checklist

[ ] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Thanks again :)


Namespace not found issues

I tried opening one of my projects but I end up with a lot of namespace not found errors.

Xamarin Studio and Visual Studio have no complaints.  Am I missing something obvious?
Thanks!

That's interesting. Looks like a problem with FSAC? /cc: @rneatherway

Is it possible to paste the output of the project command to FSAC? And also the fsproj file would be useful.

I'll come up with a sample project and get back to you.

I created the project like I did with my other projects.  I used ProjectScaffold template, added dependencies with paket on command line, and edited some code with Xamarin Studio, then opened with Atom.
https://github.com/TheAngryByrd/IonideBugSample

What OS are you running. If Windows, which versions of VS are installed. If not, which versions of Mono and F#?

Yeah, forgot to mention, OSX.

I do have the 32 bit version of Mono because Xamarin Studio packages that.

I see, could you also please verify your version of fsautocomplete?

FsAutoComplete 0.24.1

I think I'm experiencing the same issue, using the fsharp yeoman generator to create a Websharper.UI.Next project.  When I open Client.fs I get namespace not found errors for WebSharper (Paket dependency - added and installed by the yo generator).

I'm also using 32-bit Mono 4.03 on OSX.

I can reproduce it on Windows - it's working in VS, while Ionide (both Atom and VS Code) shows me same errors. What makes me believe it's some problem with FSAC.

WebSharper has caused some problems in the past because it uses a custom MSBuild task. This might be fixed by upgrading FSAC to FCS 2.0.0, where I reworked the project cracking. I have a branch nearly finished for that and will do a new release soon.

I'll definitely be ready for testing it.

I have released a new version of FSAC now, but it probably isn't included in ionide yet. You could get some debug output by downloading the release, unzipping it and running something like:
FSharp.Compiler.Service.ProjectCrackerTool.exe --text <path to>/MyProject.fsproj true

Actually, I've already updated to FSAC 0.27.0

Cool! In that case to get debug output the project command needs to be told to be verbose, have you added support for that?

No, not yet. I've only updated FSAC haven't added new functionalities yet.

Ok no worries. @TheAngryByrd @tonyj-dootrix  if you have a chance to do the manual test I suggested above that would be great.

debug.txt
This help?

Ok I'll give it a shot.

@tonyj-dootrix there don't seem to be any errors and the WebSharper DLLs are found, so I think it will be working with the latest version.

Have updated ionide-fsharp to 1.5.0 but I'm still getting the same errors in Atom.  Is there something else I should be updating?

@TheAngryByrd I tried your example project and it works fine for me on Linux Mono 4.2.
@tonyj-dootrix can you make your project available for me to double-check please?

wsdemo.zip
This is a completely 'clean' project, simply generated using the f-sharp yeoman generator.  I chose the 'Create standalone project' option and then chose 'WebSharper.UI.Next SPA'.  Let  me know if there's anything else you need.

Here are the dependencies I find locally:
    "-r:packages/WebSharper/lib/net40/IntelliFactory.Xml.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.Collections.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.Control.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.Core.JavaScript.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.Core.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.Html.Client.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.Html.Server.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.InterfaceGenerator.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.JQuery.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.JavaScript.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.Main.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.Sitelets.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.Testing.dll";
    "-r:packages/WebSharper/lib/net40/WebSharper.Web.dll";
    "-r:packages/WebSharper.UI.Next/lib/net40/WebSharper.UI.Next.Templating.dll";
    "-r:packages/WebSharper.UI.Next/lib/net40/WebSharper.UI.Next.dll";
    "-r:/usr/lib/mono/4.5/mscorlib.dll";
    "-r:/usr/lib/mono/gac/FSharp.Core/<IP_ADDRESS>__b03f5f7f11d50a3a/FSharp.Core.dll";
    "-r:/usr/lib/mono/4.5/System.dll";
    "-r:/usr/lib/mono/4.5/System.Numerics.dll";
    "-r:/usr/lib/mono/4.5/System.Web.dll"; "-r:/usr/lib/mono/4.5/System.Xml.dll";
    "-r:/usr/lib/mono/4.5/System.Xml.Linq.dll";
    "-r:/usr/lib/mono/4.5/System.Core.dll";

And it works fine in the latest version of Emacs, so I think it is an issue with the Suave frontend. I'm not sure why there would be a problem though.

Sorry, I don't understand how Suave is involved?

Ionide uses a Suave interface to FsAutoComplete rather than a pipe like Emacs and Vim. @Krzysztof-Cieslak will know how to debug that properly.

@rneatherway
I can reproduce (at least on some of my projects) it on my PC. After update to newest FSAC (so with new resolver).
For example:
https://github.com/deepcovelabs/ServiceFabricSuave/blob/master/src/CalculatorService/CalculatorService.fsproj
gives:
{"Kind":"project","Data":{"Project":"d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\CalculatorService.fsproj","Files":["d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\AssemblyInfo.fs","d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\ServicesCommon.fs","d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\Services.fs","d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\Program.fs"],"Output":"CalculatorService.exe","References":["C:\\Program Files (x86)\\Reference Assemblies\\Microsoft\\FSharp\\.NETFramework\\v4.0\\<IP_ADDRESS>\\FSharp.Core.dll"]}}

which obviously has some more references than just FSharp.Core ;)

Please could you run it again in "verbose" mode? Just add an extra 'verbose' to the end of the 'project' command, or run it manually as per https://github.com/fsharp/emacs-fsharp-mode#project-file-issues

Output running verbose option:
project "d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\CalculatorService.fsproj" verbose
{"Kind":"project","Data":{"Project":"d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\CalculatorService.fsproj","Files":["d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\AssemblyInfo.fs","d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\ServicesCommon.fs","d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\Services.fs","d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\Program.fs"],"Output":"CalculatorService.exe","References":["C:\\Program Files (x86)\\Reference Assemblies\\Microsoft\\FSharp\\.NETFramework\\v4.0\\<IP_ADDRESS>\\FSharp.Core.dll"],"Logs":{"d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\CalculatorService.fsproj":"Build started.\r\nProject \"CalculatorService.fsproj\" (Build target(s)):\r\nBuilding with tools version \"12.0\".\r\nProject file contains ToolsVersion=\"14.0\". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild, or the build may have been forced to a particular ToolsVersion for policy reasons. Treating the project as if it had ToolsVersion=\"12.0\". For more information, please see http://go.microsoft.com/fwlink/?LinkId=293424.\r\nTarget \"_CheckForInvalidConfigurationAndPlatform\" in file \"C:\\Program Files (x86)\\MSBuild\\12.0\\bin\\Microsoft.Common.CurrentVersion.targets\" from project \"d:\\Programowanie\\!DCL\\HelloWorld\\src\\CalculatorService\\CalculatorService.fsproj\" (entry point):\r\nUsing \"Error\" task from assembly \"Microsoft.Build.Tasks.v12.0, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a\".\r\nTask \"Error\"\r\nThe OutputPath property is not set for project 'CalculatorService.fsproj'.  Please check to make sure that you have specified a valid combination of Configuration and Platform for this project.  Configuration='Debug'  Platform='AnyCPU'.
  This error may also appear if some other project is trying to follow a project-to-project reference to this project, this project has been unloaded or is not included in the solution, and the referencing project does not build using the same or an equivalent Configuration or Platform.\r\nDone executing task \"Error\" -- FAILED.\r\nDone building target \"_CheckForInvalidConfigurationAndPlatform\" in project \"CalculatorService.fsproj\" -- FAILED.\r\nDone building project \"CalculatorService.fsproj\" -- FAILED.\r\nBuild FAILED.\r\n"}}}

What platform? If windows, which versions of VS and MSBuild are installed? Is the OutputPath property specified in the project file?

Windows 10, VS 2015, MSBuild 14 and 12. Output path is set here and here

Please also consider that it's output from command line version of FSAC so it's not Suave version problem

(Also even if something would be wrong with output path i think it should not result in wrong references resolving)

I took another look and in fact the error message is quite good here:

The OutputPath property is not set for project 'CalculatorService.fsproj'.  Please check to make sure that you have specified a valid combination of Configuration and Platform for this project.  Configuration='Debug'  Platform='AnyCPU'.

The two places where you specify the OutputPath are both guarded by platform x64, so under the defaults set by the upper section, which sets platform to AnyCPU they will not be used. Probably when you open this in Visual Studio the solution context sets the platform to x64. If I set that property then FCS gets better options (see bottom of this comment).

(Also even if something would be wrong with output path i think it should not result in wrong references resolving)

The project cracking functionality works by invoking MSBuild, so it's really up to whatever MSBuild does. It's now a standalone application: https://github.com/fsharp/FSharp.Compiler.Service/blob/master/src/fsharp/FSharp.Compiler.Service.ProjectCrackerTool/Program.fs
If we want to make the errors easier to present, that's another question. However, in the past the build has often failed (would check here) while still providing useful references, so I'm not 100% sure what to do. Perhaps if no references are returned? Always using verbose mode is also likely to slow things down, but then we don't often crack projects so maybe that's OK.
~/dev/ServiceFabricSuave (master|✔)
$ mono ../FsAutoComplete/packages/FSharp.Compiler.Service.ProjectCracker/lib/net45/FSharp.Compiler.Service.ProjectCrackerTool.exe src/CalculatorService/CalculatorService.fsproj false Platform x64 | jq .
{
  "LogOutput@": "",
  "Options@": [
    "--simpleresolution",
    "--noframework",
    "--out:/Users/robnea/dev/ServiceFabricSuave/src/CalculatorService/bin/Debug/CalculatorService.exe",
    "--doc:/Users/robnea/dev/ServiceFabricSuave/src/CalculatorService/bin/Debug/SuaveHost.XML",
    "--fullpaths",
    "--flaterrors",
    "--target:exe",
    "--define:DEBUG",
    "--define:TRACE",
    "--debug+",
    "--optimize-",
    "--tailcalls-",
    "--debug:full",
    "--platform:x64",
    "-r:/usr/local/Cellar/mono/<IP_ADDRESS>_1/lib/mono/4.5/System.Runtime.Serialization.dll",
    "-r:/usr/local/Cellar/mono/<IP_ADDRESS>_1/lib/mono/4.5/System.ServiceModel.dll",
    "-r:/usr/local/Cellar/mono/<IP_ADDRESS>_1/lib/mono/4.5/mscorlib.dll",
    "-r:/usr/local/Cellar/mono/<IP_ADDRESS>_1/lib/mono/4.5/FSharp.Core.dll",
    "-r:/usr/local/Cellar/mono/<IP_ADDRESS>_1/lib/mono/4.5/System.dll",
    "-r:/usr/local/Cellar/mono/<IP_ADDRESS>_1/lib/mono/4.5/System.Numerics.dll",
    "-r:/usr/local/Cellar/mono/<IP_ADDRESS>_1/lib/mono/4.5/System.Core.dll",
    "/Users/robnea/dev/ServiceFabricSuave/src/CalculatorService/AssemblyInfo.fs",
    "/Users/robnea/dev/ServiceFabricSuave/src/CalculatorService/ServicesCommon.fs",
    "/Users/robnea/dev/ServiceFabricSuave/src/CalculatorService/Services.fs",
    "/Users/robnea/dev/ServiceFabricSuave/src/CalculatorService/Program.fs"
  ],
  "ProjectFile@": "src/CalculatorService/CalculatorService.fsproj",
  "ReferencedProjectOptions@": []
}

Happening to me in both Atom and VS Code too (Windows 10 Enterprise 10.0.11099, Visual Studio 2015 Enterpise 2015 Version 14.0.24720.00 Update 1) in console project. Is there any way I can help with this?

Hi @davidpodhola, thanks a lot for offering to help. Can you please find the file ProjectCrackerTool.exe on your computer (will be wherever you install your Atom packages), and run the following from a command prompt:
FSharp.Compiler.Service.ProjectCrackerTool.exe --text /console.fsproj true
@Krzysztof-Cieslak it would be great if there was a way to toggle this verbose logging in Atom/VSCode.

Thanks @rneatherway, this is the result
C:\Users\david.podhola\.atom\packages\ionide-fsharp\bin>FSharp.Compiler.Service.ProjectCrackerTool.exe --text C:\Users\david.podhola\S\sagacious-octo-kumquat\console\console.fsproj true
{ProjectFile =
  "C:\Users\david.podhola\S\sagacious-octo-kumquat\console\console.fsproj";
 Options =
  [|"--simpleresolution"; "--noframework";
    "--doc:C:\Users\david.podhola\S\sagacious-octo-kumquat\console\bin\Debug\console.XML";
    "--fullpaths"; "--flaterrors"; "--target:exe"; "--define:DEBUG";
    "--define:TRACE"; "--debug+"; "--optimize-"; "--tailcalls-"; "--debug:full";
    "--platform:anycpu";
    "C:\Users\david.podhola\S\sagacious-octo-kumquat\console\console.fs"|];
 ReferencedProjectOptions = [||];
 LogOutput =
  "Build started.
Project "console.fsproj" (Build target(s)):
Building with tools version "14.0".
Project file contains ToolsVersion="12.0". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild, or the build may have been forced to a particular ToolsVersion for policy reasons. Treating the project as if it had ToolsVersion="14.0". For more information, please see http://go.microsoft.com/fwlink/?LinkId=293424.
The target "Build" does not exist in the project.
Done building project "console.fsproj" -- FAILED.
Build FAILED.
";}

Might be related to this section in my fsproj
  <Choose>
    <When Condition="'$(VisualStudioVersion)' == '11.0'">
      <PropertyGroup Condition="Exists('$(MSBuildExtensionsPath32)\..\Microsoft SDKs\F#\3.0\Framework\v4.0\Microsoft.FSharp.Targets')">
        <FSharpTargetsPath>$(MSBuildExtensionsPath32)\..\Microsoft SDKs\F#\3.0\Framework\v4.0\Microsoft.FSharp.Targets</FSharpTargetsPath>
      </PropertyGroup>
    </When>
    <Otherwise>
      <PropertyGroup Condition="Exists('$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\FSharp\Microsoft.FSharp.Targets')">
        <FSharpTargetsPath>$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\FSharp\Microsoft.FSharp.Targets</FSharpTargetsPath>
      </PropertyGroup>
    </Otherwise>
  </Choose>
  <Import Project="$(FSharpTargetsPath)" Condition="Exists('$(FSharpTargetsPath)')" />

because if I simplify it to just
  <Import Project="C:\Program Files (x86)\Microsoft SDKs\F#\4.0\Framework\v4.0\Microsoft.FSharp.targets" />

I get the attachment which I assume is better. Not sure how the previous fsproj was working anyway.
result.txt
Anyway the result in Atom is still the same (the namespace or module 'PostSharp' is not defined)

OK, I think that the first problem you experienced is probably because the project cracker assumes Visual Studio 12 in one part (https://github.com/fsharp/FSharp.Compiler.Service/blob/master/src/fsharp/FSharp.Compiler.Service.ProjectCrackerTool/Program.fs#L131).
Can you tell me the contents of this folder:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio

and which versions of VS you have installed please? If you can clone FCS, change that line to 14.0 and give it another guy against the original project file that would be even better.
In the second version the listed references include PostSharp, so I can't see why there would be a problem with missing reference at that stage.

To answer the question: just two folders there, v12.0 and v14.0. I have Visual Studio 2015 Enterpise 2015 Version 14.0.24720.00 Update 1 installed only, the subfolder v12.0 containts the folder TypeScript only.

Here's a very dirty hack i have used to overcome namespaces issue.
Works in Windows with Atom and VsCode. Im not using Visual Studio in any way (although, i have it installed), so there is no *.fsproj, just VsCode (or Atom) + Paket + Fake.

Use *.fsx files instead of *.fs (rename all your *.fs to *.fsx) to get access to fsi directives (#load, #r), otherwise it will complain that you can't use directives.
In each file you can use #load directive to reference file you need types from.
Also, you can wrap it with #if INTERACTIVE ... #endif
Notice, everything works fine now

Also notice, im using this environment setup in a new project, so i have no legacy code and it's not a problem for me to just drop in *.fsx files instead of *.fs
Please, let me know if it is really a wrong way of doing things :smile:

@avy-the-one thanks, I will try, my problem sith fsx files is I am not used to use them. I mostly create the projects with fsproj files.

Please don't go down that road! You will have to manually maintain the references in each file. I have an update at the referenced PR, which should address this problem. Once it is merged into FCS then we can do new releases of FSAC and Ionide.

@Krzysztof-Cieslak I've released a new version of FsAutoComplete with latest FCS that should fix at least some of these issues. Can you update ionide to include it?

New FSAC released in 1.6.1

working for me, thanks a lot!

Great!

Hi, I am facing similar kind of issue. When I am having multiple projects.
I am having solution having C# and F# projects in src/ folder. If I open top level folder F# project can't resolve the namespace. But if I go to F# project folder and open the project it works fine. This issue is only reproducible for Windows machine only. In OSX everything works fine.
Should I open this issue or file another one?
cc/ @Krzysztof-Cieslak


Update Sys Report for changes to INBOX

Updated SR with up-to-date info about the usage and capacity of dbic-mrinbox storage


Improve the code coverage of the gtcp module

Codecov Report

Merging #1836 (f8ce6bd) into master (a73769e) will decrease coverage by 73.53%.
 Consider uploading reports for the commit dbc8e91 to get more accurate results

@@            Coverage Diff             @@
##           master   #1836       +/-   ##
==========================================
- Coverage   73.53%       0   -73.54%
==========================================
  Files         495       0      -495
  Lines       44310       0    -44310
==========================================
- Hits        32582       0    -32582
+ Misses       9772       0     -9772
+ Partials     1956       0     -1956

Flag
Coverage Δ

go-1.15
?

go-1.16
?

go-1.17
?

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

Impacted Files
Coverage Δ

os/gcmd/gcmd_command.go

os/gcmd/gcmd_command_object.go

os/gcmd/gcmd_command_run.go

os/gcmd/gcmd_parser.go

protocol/goai/goai.go

protocol/goai/goai_parameter_ref.go

protocol/goai/goai_shema.go

protocol/goai/goai_xextensions.go

os/gcron/gcron_cron.go

net/gsel/gsel_selector_random.go

... and 485 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 3a014dc...dbc8e91. Read the comment docs.


Mx server in configuration file

Hi there, in dns configuration, it is not clear if we have to use mail.yourdomain.com (as wiki says) or mx.mail.yourdomain.com (as postal.yml says) as our mx server...
What is the right mx address? I think is mx.mail.yourdomain.com, but I'm not sure...

You can use any MX domain that you want as long as the record has A records pointing to your server.


load_checkpoint backward compatibility

In https://github.com/microsoft/DeepSpeed/pull/1484 a checkpoint key was changed, and it generated a backward compatibility issue when loading old checkpoints. This PR fixes the issue and also helps to match the old value with new key.

Good catch @conglongli! Maybe we need to create a static checkpoint that is saved in our unit tests that we attempt to load as a unit test. This would help catch backwards compatibility issues going forward.


Makefile improvements

A few fixes to improve working with makefile. Precompiled header support being the big one.

This doesn't work in a sample I've created, here's the error I get:
 ==== Building static_lib1 (debug) ====
pch.h
cp ../../../static_lib1/src/pch.h ../../obj/linux_Debug/static_lib1
g++ -MMD -MP -D_DEBUG -I../../../static_lib1 -g -Wall -fPIC  -fno-exceptions -fno-rtti  -xc++-header -o "../../obj/linux_Debug/static_lib1/src/pch.h.gch" -c "../../../static_lib1/src/pch.h"
In file included from <command-line>:
/usr/include/stdc-predef.h:1: fatal error: cannot create precompiled header ../../obj/linux_Debug/static_lib1/src/pch.h.gch: No such file or directory

I'll push the sample soon

Fixed, I wasn't accounting for pch files being in subfolders the way main source files. It now strips the subfolders the same way.

Merged, thanks for the fix!


Node 3d input clears Scalar and Boolean inputs (attach/detach/load)

Attaching and detaching a Node 3d input will clear Scalar and Boolean inputs on the same node to their default.
This clearing also happens on graph load, so it feels like state isn't saving, but if the Node 3d input isn't attached the Scalar and Boolean inputs will load their saved state.
Checked on Godot 3.2-stable with a new project and clean install of concept_graph 0.3-alpha.
Some example nodes and the inputs that get cleared:

Exclude from noise - Threshold, Invert, Local space
Set material - Override children
Rotate random - Seed, Local Space
Offset - Negative, Local space
Spawn random duplicates - Seed

Parent to node also bugs out when attaching/detaching inputs.
I'm guessing this has something to do with the new dynamic slot system?

Yes this is probably because of the dynamic slot system. I didn't test this enough it seems. I'll make a patch tonight

Should have been fixed in c79993de9861813e106e51dbd09e87248272b22f


No continuous input from apple pencil

Describe the bug
After a hard reset of the tablet and launching the apple pen, the functions of writing as well as drawing do not work. The only thing that the stylus can make are dots. Eraser function works flawlessly with the stylus. It is possible to draw with your finger, but it requires switching to keyboard mode. Touching the stylus against the tablet again blocks the drawing.
I checked basic solutions like reinstalling, restarting obsidian, re-pairing via bluetooth of the stylus did not result in a fix
Video or screenshots
https://github.com/user-attachments/assets/8e502101-3c23-450c-b8cc-c8fd4e206f84
To Reproduce
If you're video or screenshots need more context, describe the steps reproduce the behavior:

Hard reset tablet
Open obsidian
Open new drawing widget
Try to draw

Expected behavior
If used to draw a lines.
Desktop (please complete the following information):

Device & OS: iOS 18.0.1
Plugin version: 0.2.6
Obsidian version: 1.6.7

Additional context

Oh! I'm sorry to hear you're experiencing that.
Can I clarify what a hard reset involves for you? Was it just holding the power button combo and then swiping to confirm?
Or did you wipe the tablet, reinstall?
What was the reason for the hard reset? Did iPadOS update by any chance?
Is it possible that the plug-in update?
Perhaps you could try using the BRAT plug-in and reverting to a specific version of Ink incase that was the cause.
Lastly, does the pen work the same as it used to in other apps like procreate or notes, or in the excalidraw plugin?

Oh, and one more thing.
I'm pretty sure I've experienced a similar effect before.
I found, in the end, that the tip of the Apple Pencil had become slightly unscrewed. Please try tightening it and hopefully that helps!

As for the update, it was simply that the tablet was discharged. After the reset, this error occurred. I did not install while using the app.
And I was able to fix it. I just forgot that you can do a hard reset again (through settings) and after that it worked. Fortunately, nothing serious happened to the stylus or the system. But I can only theorize that when using apps and the device discharges, such situations can occur again.
Thank you so much for the answer with solutions.

PS: sorry, I mixed up your repos, it should be in Obsidian_ink, but I hope you don't mind it

Ha ha. I noticed that.
All good mate 👍


Fixed retry of cluster discovery on initialization

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

Codecov Report
Base: 62.51% // Head: 62.48% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (73a94ce) compared to base (83def33).
Patch coverage: 62.96% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #536      +/-   ##
==========================================
- Coverage   62.51%   62.48%   -0.03%
==========================================
  Files         219      219
  Lines       21044    21058      +14
==========================================
+ Hits        13155    13159       +4
- Misses       7239     7258      +19
+ Partials      650      641       -9

Flag
Coverage Δ

1.16.x
60.61% <62.96%> (-1.55%)
:arrow_down:

1.18.x
60.60% <62.96%> (-1.82%)
:arrow_down:

1.19.x
62.54% <62.96%> (+0.15%)
:arrow_up:

connection
9.53% <59.25%> (+0.06%)
:arrow_up:

database_sql
17.25% <59.25%> (+0.31%)
:arrow_up:

discovery
7.29% <0.00%> (-0.01%)
:arrow_down:

e2e
52.91% <59.25%> (-0.02%)
:arrow_down:

integration
17.25% <59.25%> (+0.31%)
:arrow_up:

macOS-latest
47.64% <44.44%> (-0.02%)
:arrow_down:

ratelimiter
9.49% <0.00%> (-0.01%)
:arrow_down:

scripting
10.04% <0.00%> (-0.01%)
:arrow_down:

table
32.63% <59.25%> (+0.02%)
:arrow_up:

topic
28.93% <59.25%> (-0.08%)
:arrow_down:

ubuntu-latest
62.47% <62.96%> (+0.01%)
:arrow_up:

unit
47.77% <44.44%> (-0.02%)
:arrow_down:

windows-latest
47.73% <44.44%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

internal/balancer/balancer.go
87.05% <62.96%> (-0.57%)
:arrow_down:

retry/errors.go
0.00% <0.00%> (-100.00%)
:arrow_down:

internal/xsql/badconn/badconn.go
0.00% <0.00%> (-100.00%)
:arrow_down:

internal/xsql/unwrap.go
0.00% <0.00%> (-56.25%)
:arrow_down:

sql_unwrap.go
0.00% <0.00%> (-55.56%)
:arrow_down:

retry/sql.go
62.96% <0.00%> (-3.71%)
:arrow_down:

retry/retry.go
86.13% <0.00%> (-1.99%)
:arrow_down:

internal/repeater/repeater.go
90.99% <0.00%> (-1.81%)
:arrow_down:

internal/topic/topicreaderinternal/committer.go
87.91% <0.00%> (-0.68%)
:arrow_down:

internal/table/session.go
77.51% <0.00%> (-0.24%)
:arrow_down:

... and 8 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Look at adding Dissect tool

Review Dissect tool and add to SIFT:
https://github.com/fox-it/dissect
Company page on Dissect: https://www.fox-it.com/nl-en/dissect/
The team also presented at CyberThreat 2023 and would like to submit to DFIR Summit 2023 (US and EU)

Thanks for the issue. Will review.


Containerd change

To test:

single-machine installation/upgrade
custom repository mapping where k8s master is on the same host as repo
k8s ha install/upgrade
k8s backup
k8s certs renewal
keep an eye on filebeat logs gathering from containers

i know it's not scope of this task but can we try to use imperative style which is shorter and fits more to manuals. I mean eg. instead: "To check status of Grafana you can use the command", use "To check status of Grafana use the command"

I like this, will change that after more reviews.

containerd service is disabled by default and it does not start after system reboot:
[ec2-user@ci-devprawsrhelcalico-kubernetes-master-vm-0 ~]$ systemctl is-enabled containerd.service
disabled

[ec2-user@ci-devprawsrhelcalico-kubernetes-master-vm-0 ~]$ systemctl status containerd.service
● containerd.service - containerd container runtime
   Loaded: loaded (/usr/lib/systemd/system/containerd.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
     Docs: https://containerd.io

I would also add tests for kubernetes master and node:
describe 'Check if containerd service is enabled/running' do
  describe service('containerd') do
    it { should be_enabled }
    it { should be_running }
  end
end

/azp run

/azp run

:x: HA upgrade fails:
2022-02-15T16:55:56.2176599Z[38;21m16:55:56 INFO cli.src.ansible.AnsibleCommand - TASK [upgrade : k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0] ***
2022-02-15T16:55:56.9095619Z[31;21m16:55:56 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (20 retries left).
2022-02-15T16:56:27.6105342Z[31;21m16:56:27 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (19 retries left).
2022-02-15T16:56:58.3295568Z[31;21m16:56:58 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (18 retries left).
2022-02-15T16:57:29.0190866Z[31;21m16:57:29 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (17 retries left).
2022-02-15T16:57:59.7226247Z[31;21m16:57:59 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (16 retries left).
2022-02-15T16:58:30.4145436Z[31;21m16:58:30 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (15 retries left).
2022-02-15T16:59:01.1184037Z[31;21m16:59:01 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (14 retries left).
2022-02-15T16:59:31.8290035Z[31;21m16:59:31 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (13 retries left).
2022-02-15T17:00:02.5730129Z[31;21m17:00:02 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (12 retries left).
2022-02-15T17:00:33.3052430Z[31;21m17:00:33 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (11 retries left).
2022-02-15T17:01:04.0086743Z[31;21m17:01:04 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (10 retries left).
2022-02-15T17:01:34.7118245Z[31;21m17:01:34 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (9 retries left).
2022-02-15T17:02:05.4081510Z[31;21m17:02:05 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (8 retries left).
2022-02-15T17:02:36.1348692Z[31;21m17:02:36 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (7 retries left).
2022-02-15T17:03:06.8328911Z[31;21m17:03:06 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (6 retries left).
2022-02-15T17:03:37.5133882Z[31;21m17:03:37 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (5 retries left).
2022-02-15T17:04:08.2124231Z[31;21m17:04:08 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (4 retries left).
2022-02-15T17:04:38.9116667Z[31;21m17:04:38 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (3 retries left).
2022-02-15T17:05:09.6283168Z[31;21m17:05:09 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (2 retries left).
2022-02-15T17:05:40.3292718Z[31;21m17:05:40 ERROR cli.src.ansible.AnsibleCommand - FAILED - RETRYING: [ci-10todevazubcanal-kubernetes-master-vm-0]: k8s/masterN | Upgrade master ci-10todevazubcanal-kubernetes-master-vm-0 (1 retries left).
2022-02-15T17:06:11.0555087Z[31;21m17:06:11 ERROR cli.src.ansible.AnsibleCommand - fatal: [ci-10todevazubcanal-kubernetes-master-vm-0]: FAILED! => {"attempts": 20, "changed": false, "cmd": ["kubeadm", "upgrade", "node"], "delta": "0:00:00.134915", "end": "2022-02-15 17:06:10.987267", "msg": "non-zero return code", "rc": 1, "start": "2022-02-15 17:06:10.852352", "stderr": "W0215 17:06:10.978771   35797 kubelet.go:200] cannot automatically set CgroupDriver when starting the Kubelet: cannot execute 'docker info -f {{.CgroupDriver}}': executable file not found in $PATH
error execution phase preflight: docker is required for container runtime: exec: \"docker\": executable file not found in $PATH
To see the stack trace of this error execute with --v=5 or higher", "stderr_lines": ["W0215 17:06:10.978771   35797 kubelet.go:200] cannot automatically set CgroupDriver when starting the Kubelet: cannot execute 'docker info -f {{.CgroupDriver}}': executable file not found in $PATH", "error execution phase preflight: docker is required for container runtime: exec: \"docker\": executable file not found in $PATH", "To see the stack trace of this error execute with --v=5 or higher"], "stdout": "[upgrade] Reading configuration from the cluster...
[upgrade] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'", "stdout_lines": ["[upgrade] Reading configuration from the cluster...", "[upgrade] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'", "[preflight] Running pre-flight checks", "[preflight] Pulling images required for setting up a Kubernetes cluster", "[preflight] This might take a minute or two, depending on the speed of your internet connection", "[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'"]}

So the kubelet knows about the new configuration but there was annotation missing on masterN nodes.


Reverse chronological feed view

Is there a way to flip the feed into a reverse-chronological order (in the Elfeed-Search mode)? I can't find anything for this in §'Filter syntax' in the README.
If we could order entries reverse-chronologically in Elfeed-Search, pressing 'n' inside Elfeed-Show buffers could move to the next entry chronologically. Parsing feed entries chronologically can be useful, especially in social media feeds—Twitter, Mastodon, Instagram, et al.

butter-radish @.***> writes:

Is there a way to flip the feed into a reverse-chronological
order (in the Elfeed-Search
mode)? I can't find anything for this in §'Filter syntax' in the
README.
If we could order entries reverse-chronologically in
Elfeed-Search, pressing 'n' inside
Elfeed-Show buffers could move to the next entry
chronologically. Parsing feed entries
chronologically can be useful, especially in social media
feeds—Twitter, Mastodon, Instagram,
et al.

Take a look at elfeed-search-sort-function?
--
Michael @.***>

I had your same problem and this works (copy into the init file):
(defun my/elfeed-search-sort--feed-url (a b)
(>=
(elfeed-entry-date a)
(elfeed-entry-date b)))
then customise elfeed-search-sort-function to be: my/elfeed-search-sort--feed-url
Close this issue?

Sorry, I’d mixed it up while writing the issue, I wanted the reverse of what Elfeed does by default—I suppose now that would be a chronological feed view.
Switching the function in your code gets me that, thank you @user86940! And you too @sp1ff, even though I didn’t understand what you meant back then.
(defun my/elfeed-search-sort--feed-url (a b)
  (<=
   (elfeed-entry-date a)
   (elfeed-entry-date b)))

But I don’t want to have it chronological all the time, the default reverse-chronological sorting works for most things; it’s only for a few things that I want the opposite. So I’d like to be able to easily toggle it, like with a ‘elfeed-search-live-filter’ (‘s’) search. “@1-week” reverse-chronologically sorts all the entries from the past week, maybe some other operator instead of ‘@’ prefixing the duration could list all the entries from that period chronologically.


NMEAReader Checksum Validation Error

NMEAReader Checksum Validation Error
Sorry for not foloowing the exact template. Feel free to close without resolution if you find it necessary.
Describe the bug
The bug consists on the validation of the checksums when instantiating the NMEAReader class as follows: NMEAReader(stream)
Is probable that my GPS Server is different here but it results on the checksums failing because of the case of the letters.

The bug is in https://github.com/semuconsulting/pynmeagps/blob/2b9538d82ea2eb50ea18aeb3a3291677b261fec3/src/pynmeagps/nmeareader.py#L247
It's comparing strings instead of hex, so naturally "c9" != "C9"
The comparison should be done either both in lowercase or uppercase, or in a case insensitive format as decimal or hex.

Hi @0wulf,
What was your raw NMEA data source? If possible, could you send me an example of your raw data (you can redact any lat/lon if you prefer).
I’ve never come across a legitimate lower case NMEA checksum,  though a fix is easy enough.
Thanks

Hello @semuadmin
I'm currently using my iPhone's GPS. Through an app called NMEA Gps. The app sets up a server, which I'm connecting via iPhone's hotspot from a Raspberry Pi. IDK if it is the GPS module from the phone or the server app.
Either way, here I connected to the server, and show the first and last columns (msgID and checksum i think)

Thanks to you for being an active maintainer of an open source project!!

@0wulf
It is an almost universally accepted convention that the checksum digits are transmitted as upper case. The simplest and quickest resolution may be for you to apply something like a ,$NF[:-2]+$NF[-2:].upper() transformation to your own datastream.
But as the change is trivial, I'm happy to support this particular use case. Ideally I'd like an original, complete raw datastream to test against, but failing that can I ask you to install and test the following branch and let me know if this resolves the problem:
 pip install<EMAIL_ADDRESS>

Where can I send you the datastream?

There's an email link under "Author & License Information" at the foot of the README. Thanks.


Sharing a dynamic link on ios email app cuts some of the parameters and link opens the app but not the page that is needed

Steps to reproduce
1.share via email on ios
2.check the url in the body of email. it will be shorter than the one shared
3.
Expected behaviour
the url should not change
Actual behaviour
shared url is shorter
Environment

React Native version: 0.59
React Native platform + platform version: iOS 12.0

react-native-share
Version: 1.2.1
Link to repo (highly encouraged)
https://github.com/

what happens if you console.log it before using share?

I tested it that way. Because that link is shared on other apps too and it works well. only email on ios is having problems. the link is a dynamic link. so it has several params to open needed page later when app starts

I facing same issue

I found one solution to this problem. Just use link shortener. for example this one https://bitly.com

Great
can we close?

Great
can we close?

sure


Suggestion to include video screen recording.

Using maim / slop http://tuxdiary.com/2014/10/17/maim-slop/
Have a flag to record video of a window or select rectangle and automatically upload to pomf.
example code:
eval $(slop); ffmpeg -f x11grab -s "$W"x"$H" -i :0.0+$X,$Y -f alsa -i pulse ~/.recording/slop_$(date "+%Y-%m-%d_%H:%M:%V").webm

Not sure if I misunderstood something, but slop is for selection and maim is for image capturing, so if you plan to implement screen recording using FFMPEG, that wouldn't be using maim at all.

yeah MAIM wouldn't be used but ffmpeg x11grab could be used. I made an example bash script that uploads to teknik:  http://sprunge.us/XTah
worked great first few times but now it is recording at only a couple FPS now @_@

I'd imagine it'd be easy enough to easy enough to add screen recording to poomf. I don't want to try it myself if someone else can, because it'd be too much of a mess to be accepted.

Usually the best way to record your screen is to record it to a normal video format (I use mkv) and then convert it to webm afterwards. It takes a while to do this conversion, that's why you're probably only getting a few FPS, it's trying to encode it on the fly. This is just my personal experience, I'm probably using the wrong terminology. I've had bad experiences just trying to record to webm, though.
Not sure if I could write a one-size-fits-all way to do this in the script though. People have different resolutions and will want to record at different bitrates, etc, and I don't know if there's a way I could implement this easily and without a lot of autodetection(?) stuff that I don't know anything about.
I'm open to the idea, though, I'd like to use this feature myself.


[Part 3] Data science

Description
https://github.com/zzsza/Datascience-Interview-Questions

제 글이네요 ;ㅁ;
블로그 글은 https://zzsza.github.io/data/2018/02/17/datascience-interivew-questions/ 입니다!


Multiple errors and loss of a lot of items on startup since build <IP_ADDRESS>4

Got multiples errors on startup after build release <IP_ADDRESS>4. I've found that all of the shrink animal are corrupt. When you dclick on the shrink, it become as a c_man and died. Impossible to have newer build on live server, too much error and loss for players.
I have these errors still again but with previous build no.
Problem seems to be with shrink mount and a lot of other items

10:04:ERROR:GC: Deleted UID=046a11, Defname='c_drazos', Name='Drazos'. Invalid code=0x1204 (Ridden NPC without a valid mount item).
10:04:ERROR:Mount (UID=046a11, id=061dc 'Drazos'): Can't auto-fix invalid mount item (ACTARG1=04016569e)'
10:04:ERROR: Reason: Mount item in owner's LAYER_HORSE has a MORE2 which doesn't match this mount UID (owner's riding another mount?).
10:04:ERROR:GC: Deleted UID=04006347c, Defname='i_tambourine', Name='Tambourine'. Invalid code=0x1104 (Ridden NPC without a valid mount item).

With build <IP_ADDRESS>1 everything working good.
Thanks

https://github.com/Sphereserver/Source-X/commit/0d3c068ddf479ea1d537fd2a963160139a8d5981


make small change to doc_string so we can test permissions

Hopefully we can use this PR to test write permissions for maintainers on this repo.
@Schefflera-Arboricola can you try pushing to this PR?

OK… this worked.  Do you want to try merging this PR? (Assuming these changes are ok)


Notifications are not displayed after an android reboot

Rules

1 - Describe the bug
I'm in the process of creating a reminder application. It works as expected (notifications are displayed) as long as the application is running.
If I restart my android smartphone, then the reminders already created are no longer displayed as notifications.
2 - Provide us as much information as possible
I'm working on a flutterFlow project
I asked the permissions via :
await AwesomeNotifications().requestPermissionToSendNotifications();

And I also disabled battery optimisation on the phone.
I've noticed that after a reboot, notifications are still seen as existing by awesome_notifications. However, they are no longer displayed when the time comes.
3 - How To Reproduce the Error
Build a flutterflow Project with awesome_notifications, launch a reminder and then reboot the phone.
4 - Expected behavior
After a reboot, scheduled reminders should appears
5 - Screenshots
No screenshots to provide
6 - Additional context
I tried on a onePus and Honor and asus smartPhones

I just see this thread : https://github.com/rafaelsetragni/awesome_notifications/issues/806
But adding this code in the manifest :
  <receiver android:name="me.carda.awesome_notifications.ScheduledNotificationReceiver" android:exported="true" />
    <receiver android:name="me.carda.awesome_notifications.ScheduledNotificationBootReceiver" android:exported="true">
      <intent-filter>
          <action android:name="android.intent.action.BOOT_COMPLETED"></action>
          <action android:name="android.intent.action.QUICKBOOT_POWERON" />
      </intent-filter>
  </receiver>

Didn't resolve anything.
In order for phone reboot to work, do I have to change the manifest other than add this permission :
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>