feat(plugin-ledger-connector-burrow): add connector

Is your feature request related to a problem? Please describe.
We need a connector to transact on Hyperledger Burrow.
Describe the solution you'd like
Following the pattern of the other connector plugins we have out there.
cc: @takeutak @sfuji822 @hartm @jonathan-m-hamilton @AzaharaC @jordigiam @kikoncuo @jagpreetsinghsasan @arnab-roy

I would like to take this issue. But can I start working this maybe a week later? Kind of busy finishing my school final projects.

@jscode017 Sure thing! It's been open for quite some time so it can definitely wait another week. :-)
I'll assign it to your name so that we know you are working on it!

@petermetz I would probably start to work on this about Monday, after finish all my final projects at school. Would you recommend building cactus-plugin-ledger-connector-burrow first for a more test-driven fashion, or just write plugin-ledger-connector-burrow?

@jscode017 That's cool, no rush at all!
My personal take on TDD specific to this situation:
It depends on how familiar are you with the APIs of Burrow specifically. If you are fairly experienced with it and therefore know in advance what the tests should look like, then yeah, I think TDD is great. On the other hand if you are new to Burrow or not super familiar with it yet, then trying to define the tests up front will be difficult IMO because then the task of writing the connector will also be part research.
Strict TDD in my opinion works best when you are building something that you had built before like a run of the mill business application that is largely doing the same thing over and over again with a little twist. In scenarios like that it's fairly easy to know how a test will look like, but developing a new feature for a framework that is more on the research side in my opinion.
TLDR: I'd copy paste an existing connector's packages (both the test and the actual package) and then rename them accordingly and slowly work it over to have it operate on Burrow not the OG ledger. (this is what I usually do when writing new connectors)

Thanks for the advice, copy-paste an existing connector's packages sounds like a great approach

@jscode017 De-assigning it for now, please let me know if you'd like to pick this back up again!


Saving state_dict of optimizer

Guys, I notice the optimizer code e.g. for Noam, has load_state_dict and save_state_dict, but these appear not to be used and its step gets set to zero if you try to train from an intermediate epoch.  This means that with the attention models you cannot restart training and get the same results.
Not sure what the right fix for this is.

We'll need to add it as an argument to save/load checkpoint functions and store the state dict in checkpoints. IIRC the learning rate schedulers in pytorch have the same mechanism. I can do it but not sure when; if somebody's quicker then feel free to have a go.

Fixed in https://github.com/k2-fsa/snowfall/pull/111, like @pzelasko said, save optimizer and lr_scheduler every epoch and load them if training from an intermediate epoch.


Remove deprecated internal method

The only history I can find on this is https://github.com/Microsoft/TypeScript/commit/af5148d4f35533df55e61f87f0c0419b97a64a48 -- since this method is internal there should be no problem removing it?

@andy-ms can you add a note about it in the API breaking changes section.

Don't think it's an API breaking change since this was never in the public API?

I remember monaco used to take a dependency on it. but they do not any longer. even though it is not part of the public API ppl still use it. we just need to add a note to use getProgram().getSourceFile() instead.

Updated API breaking changes.


⚠ Bofrost.es has degraded performance

In 68fb3f2, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1648 ms

Resolved: Bofrost.es performance has improved in 0ab20f6 after 6 minutes.


etc/images.yml: add official Tumbleweed image

I hope I picked the right on from http://download.opensuse.org/tumbleweed/appliances/

Replaced by betacloud/openstack-image-manager#68


Create a regex that could handle 'emphasized' bad words

Well, like the title suggests we need a regex that could handle longer words.
Sorry, di magaling mag explain.
Example:
pooooooootang ina
amboboooooooooo
tttttttttanginamo!!!

I think this is applicable in the filter package, e.g. bad-words.
This package only provides a list of Filipino bad words to consume in a form of an array, object, and regexp.


Clear on a pool with no namespace should clear all namespaces

If you setup a cache instance with no namespace it should clear all namespaces, not clear the entire cache.
The use case for this is that all of our customers have their own namespace, however if a migration requires the clearing of their cache we want to be able to simply clear the cache. Unfortunately, we also use Redis for the PHP session storage, and it appears that this is cleared also.

Any update @tedivm


CI Docker image

Add CI docker image
Fix dockerfile
Add build_docker script

Codecov Report

Merging #846 (c5f7824) into main (6ff68cc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #846   +/-   ##
=======================================
  Coverage   81.27%   81.27%
=======================================
  Files         348      348
  Lines       31200    31200
=======================================
  Hits        25358    25358
  Misses       5842     5842

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 6ff68cc...c5f7824. Read the comment docs.


Feature/simple ui mods

Minor changes

[] Check that you pass the basic compilation and unit tests by running grunt

Coverage remained the same at 8.942% when pulling f5d74a2487ace4d9225b3f1d65aef4b034c3f264 on feature/simple_ui_mods into dfb64c4a4bc4814189ccc2681e5a3307c98f31ff on develop.


How could I use Log in Splat

I read the Logging part of Readme.md, but I still don't know how to use it. Could you be more specific? Or give me a sample?

May be its too late ^_^ ~~
1. Define a custom logger
        public class Logger : ILogger
        {
            public LogLevel Level { get; set; } = LogLevel.Debug;

            public void Write([Localizable(false)] string message, LogLevel logLevel)
            {
                Console.WriteLine(message);
                this.WriteCallCount = this.WriteCallCount + 1;
            }

            public int WriteCallCount { get; private set; }
        }

2. Register the logger
            var logger = new Logger();
            Locator.CurrentMutable.RegisterConstant(logger, typeof(ILogger));
            Assert.AreSame(logger, Locator.Current.GetService<ILogger>());

            LogHost.Default.Debug("SomeText");
            Assert.AreEqual(1, logger.WriteCallCount);

Any existing cross-platform log to file implementations?


feat: alerts continue and complete

Hello! I tried updating this branch with no success. It was meant for one file only. Thank you!
This PR is ready for review.

I think on your fork we remove the .github/workflows/add-to-keyman-project.yml
That's only supposed to run on the main keyman.com repo

Let's get @Meng-Heng setup to commit to the keymanapp repo rather than the fork. @darcywong00 can you help him with that?


React component inside Vue Project not reactive

My React Componen inside Vue not reactive on any change.
In code below, if I click the button, then title inside react component is not updated.
<template>
    <ReactPanel :title="title" />
   <button @click="onClick">Change Title</button>
</template>
<script setup>
import {ref} from "vue"
import { applyReactInVue } from "veaury";
import { Panel } from "my-react-panel-comp";
const title = ref("MyTitle")
const onClick = () => {
   title.value = "Title Change"
}

const ReactPanel = applyReactInVue(Panel);

</script>

@meshwara
The use case you provided works smoothly in my project.
Please describe how your project is built, is it based on webpack or vite?
My case
<template>
  <ReactPanel :title="title" />
  <button @click="onClick">Change Title</button>
</template>
<script setup>
import {ref} from "vue"
import { applyReactInVue } from "veaury";
import { createElement } from 'react'
// A simple React component
function Panel({title}) {
  return createElement('div', {}, title)
}
const title = ref("MyTitle")
const onClick = () => {
  title.value = "Title Change"
}

const ReactPanel = applyReactInVue(Panel);

</script>

@meshwara
I don't think this is needed, vue3 uses proxy, so there is no need to reset the value of the array, the following use case can still run smoothly.
<template>
  <ReactPanel :title="title" />
  <button @click="onClick">Change Title</button>
</template>
<script setup>
import {ref} from "vue"
import { applyReactInVue } from "veaury";
import { createElement } from 'react'
function Panel({title}) {
  return createElement('div', {}, title[0].val)
}
const title = ref([{val: "MyTitle"}])
const onClick = () => {
  title.value[0].val = 'Change Title'
}

const ReactPanel = applyReactInVue(Panel);

</script>

Ok. Thank you !!!


Modify ModelClassDiagram and Diagram Colours

Describe your changes
Remove tags from ModelClassDiagram
Add Department, Role and ContractEndDate to ModelClassDiagram
Modify the Diagram colours a bit (for extra lines of code)
Issue ticket number and link
Builds on #138
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] If it is a core feature, I have added thorough tests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:


CoinbaseWalletAdapter is not a constructor

Describe the bug
There is a runtime error which says:
CoinbaseWalletAdapter is not a constructor
To Reproduce
Steps to reproduce the behavior:

Set up the app by following this instruction
See error

Expected behavior
No error is shown and you can use all adapters
Screenshots

Desktop (please complete the following information):

OS: MacOS (11.5.2)
Browser: Chrome
Version: 103.0.5060.53

You need to import the class from the wallets package, are you doing that?

@jordansexton Thank you for replying. Yes I imported it:
import {
    CoinbaseWalletAdapter,
    GlowWalletAdapter,
    PhantomWalletAdapter,
    SlopeWalletAdapter,
    SolflareWalletAdapter,
    SolletExtensionWalletAdapter,
    SolletWalletAdapter,
    TorusWalletAdapter,
} from '@solana/wallet-adapter-wallets';

@jordansexton UPDATE 😄
I was able to use CoinbaseWalletAdapter from @solana/wallet-adapter-coinbase instead of @solana/wallet-adapter-wallets
import {
  // CoinbaseWalletAdapter,
  GlowWalletAdapter,
  PhantomWalletAdapter,
  SlopeWalletAdapter,
  SolflareWalletAdapter,
  SolletExtensionWalletAdapter,
  SolletWalletAdapter,
  TorusWalletAdapter,
} from '@solana/wallet-adapter-wallets';
import { CoinbaseWalletAdapter } from '@solana/wallet-adapter-coinbase';

Hmm, if you're using the latest version of the wallets package, this is imported:
https://github.com/solana-labs/wallet-adapter/blob/a634f5f6ac32e55ddca403b20b85f5bb895b0606/packages/wallets/wallets/package.json#L37
And exported:
https://github.com/solana-labs/wallet-adapter/blob/a634f5f6ac32e55ddca403b20b85f5bb895b0606/packages/wallets/wallets/src/index.ts#L7
Can you make sure you're running the latest version of the wallets package?


Format string: ENV_CVAT_REDIS_HOST cannot be expanded

Trying to build and run CVAT docker with my code changes. Build succeeded, but while starting cvat_server, it is throwing this error

Error: Format string '%(ENV_HOME)s/wait-for-it.sh %(ENV_CVAT_REDIS_HOST)s:6379 -t 0 -- bash -ic \\n"exec python3 %(ENV_HOME)s/manage.py rqworker -v 3 default"' for 'program:rqworker_default.command' contains names ('ENV_CVAT_REDIS_HOST') which cannot be expanded. Available names: ENV_DJANGO_CONFIGURATION, ENV_HOME, ENV_HOSTNAME, ENV_LANG, ENV_LC_ALL, ENV_NUMPROCS, ENV_PATH, ENV_TERM, ENV_TZ, ENV_USER, ENV_http_proxy, ENV_https_proxy, ENV_no_proxy, ENV_socks_proxy, group_name, here, host_node_name, process_num, program_name in section 'program:rqworker_default' (file: 'supervisord/all.conf')
Steps to Reproduce (for bugs)

Build CVAT Docker - docker compose -f docker-compose.yml -f docker-compose.dev.yml build  ===> successful
docker run cvat/server:v2.2.0  ===> error
docker run cvat/ui:v2.2.0 ===> successful, but tool page not  loading as backend not avaiable

I'm also not sure, whether these are the proper commands to run the cvat docker after building it.
Your Environment

Docker version docker version (e.g. Docker 17.0.05): Docker version 24.0.5, build ced0996
Operating System and version (e.g. Linux, Windows, MacOS): Ubuntu 22

Why you dont use docker compose to run ?

Why you dont use docker compose to run ?

Tried docker-compose after build, I got the below error
Starting cvat_db             ... failed
Starting cvat_redis          ... failed
Starting traefik             ... failed
Starting cvat_opa            ... failed
Starting cvat_worker_low     ... failed
Starting cvat_worker_default ... failed
Starting cvat_utils          ... failed
Starting cvat_server         ... failed
Starting cvat_ui             ... failed
ERROR: No containers to start
ERROR: 1
In VSCode, under Docker Images, I fond only two docker images docker.io/cvat/server & docker.io/cvat/ui.
But how to build other images like redis, postgressql

Why you dont use docker compose to run ?

Tried docker-compose after build, I got the below error
Starting cvat_db             ... failed
Starting cvat_redis          ... failed
Starting traefik             ... failed
Starting cvat_opa            ... failed
Starting cvat_worker_low     ... failed
Starting cvat_worker_default ... failed
Starting cvat_utils          ... failed
Starting cvat_server         ... failed
Starting cvat_ui             ... failed
ERROR: No containers to start
ERROR: 1
In VSCode, under Docker Images, I fond only two docker images docker.io/cvat/server & docker.io/cvat/ui.
But how to build other images like redis, postgressql

Please follow the installation guide

ok. Thanks.
with "docker compose start" ==> i'm able to get the login page, but with errors as below

Could not check authorization on the server
Error: Request failed with status code 502. "Bad Gateway".
Could not get user agreements from the server
Error: Request failed with status code 502. "Bad Gateway".

Can you please suggest what I need to change to resolve these errors.

Please provide exact steps to reproduce the issue

Following are the steps I followed.

docker compose -f docker-compose.yml -f docker-compose.dev.yml build
docker compose up

When I open :8080 url in browser, I got these errors
1)Could not check authorization on the server
Error: Request failed with status code 502. "Bad Gateway".
2)Could not get user agreements from the server
Error: Request failed with status code 502. "Bad Gateway".
Previously, I was using CVAT in a development environment, which I configured it using this https://opencv.github.io/cvat/docs/contributing/development-environment/   page.
During development, I had 8000 port for cvat_server and 3000 port for cvat_ui

Now the browser is showing as
"Could not check authorization on the server
Open the Browser Console to get details"
In the console log of browser,
Error: Request failed with status code 500. "\n\n500 Internal Server Error\n\nInternal Server Error\nThe server encountered an internal error or\nmisconfiguration and was unable to complete\nyour request.\nPlease contact the server administrator at \n [no address given] to inform them of the time this error occurred,\n and the actions you performed just before this error.\nMore information about this error may be available\nin the server error log.\n\n".

What exact version of CVAT are you using gil log -1?
Also please attach logs from cvat_server container

Got error in urls.py in my application, "Settings: Unable to find "ROOT_URL_CONF", as I have settings.py file also. Tried to remove that settings.py file and changed the dependencies on seetings.py.
It worked.

But I got EventSource call blocking by Django, which is hosted in docker. Need any suggestions from this


🐛 [cloud firestore web] some time(40%) query by timestamp return empty, but on mobile it is working well

Bug report
Describe the bug
Query query = org
       .collection("myCol")
       .doc("docId")
       .collection('subCol')
       .where("readTimes", arrayContains: timestamp);

"timestamp" after arrayContains is from doc fetched by other query, and then put it here as a condition.
On android and ios it is working as expected, but on web, it cannot fetch any doc.
Tested on it many times, about 40% it is doesn't work, and if a doc cannot be fetched, it is same result among different tests.
And also printed timestamp and compare between web and android, exactly same value.....  so weird.
Flutter dependencies
My pubspec.yaml
firebase_core: ^1.20.1
cloud_firestore: ^3.4.4
Also tried core 1.21.1 and cloud_firestore 3.4.6, doesn't work.

@LiangHuangBC
Thanks for the report. Can you provide flutter doctor -v, expected vs actual result you are getting in prooperly formatted text along with a minimal code sample ?

[✓] Flutter (Channel stable, 3.3.0, on macOS 12.5.1 21G83 darwin-x64, locale en-CA)
• Flutter version 3.3.0 on channel stable at /Users/lianghuang/dev/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision ffccd96b62 (8 days ago), 2022-08-29 17:28:57 -0700
• Engine revision 5e9e0e0aa8
• Dart version 2.18.0
• DevTools version 2.15.0
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/lianghuang/Library/Android/sdk
• Platform android-33, build-tools 30.0.3
• ANDROID_HOME = /Users/lianghuang/Library/Android/sdk
• ANDROID_SDK_ROOT = /Users/lianghuang/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 13F100
• CocoaPods version 1.11.3
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2021.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
[✓] IntelliJ IDEA Community Edition (version 2020.2.3)
• IntelliJ at /Applications/IntelliJ IDEA CE.app
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
[✓] VS Code (version 1.71.0)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.23.0
[✓] Connected device (2 available)
• macOS (desktop) • macos  • darwin-x64     • macOS 12.5.1 21G83 darwin-x64
• Chrome (web)    • chrome • web-javascript • Google Chrome 104.0.5112.101
[✓] HTTP Host Availability
• All required HTTP hosts are available
• No issues found!

BTW, on my web app, there is no local cache.  No index.html changed either, all injected.

Thanks for the update. I am unable to replicate this behavior using plugin's example and running on web.

"timestamp" after arrayContains is from doc fetched by other query, and then put it here as a condition.

Is it possible to directly pass the timestamp rather than using the result of other query and see if you still get same behavior or not ?
Also, since you said it is not consistent and happens only sometimes, it probably may not be an issue from client side.

Thanks for your reply.
timestamp is generate by FieldValue, it is hard to get its value without query.
On Android,  query by timestamp is always working well, seams like JavaScript package did something wrong....

Thanks for the feedback. I am unable to replicate this behavior using the plugin example running on web, so I am keeping this issue open and labeling for further insights from the team.

We updated how Timestamp are being handled on Web for Firestore, please update to the latest cloud_firestore version. Feel free to reopen if it's still happening.


Require hhvm 4.128 and support autoloading with ext_watchman

The hsl is always built-in.
ext_watchman and HH\Facts are always available.
varray eq vec and darray eq dict is always true.
All legacy arrays have been replaced with Hack arrays.

Looks good. Thank you!


⚠ Bofrost.be has degraded performance

In 8b0b807, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 893 ms

Resolved: Bofrost.be performance has improved in 5f18198 after 6 minutes.


[4.x] Switches default JPA CDI portable extension to PersistenceExtension from JpaExtension

This PR "turns on" the "new" JPA machinery that has been lying somewhat dormant in Helidon since 3.x.  The "old" machinery remains, since the new machinery is a very different approach, and there may be production cases where the old machinery needs to be switched back on in case old behavior was being relied upon.
This PR also adds deprecation notices to various classes (most of which are internal anyway but it's good practice).
This PR also ensures that any usage of the CDISEJtaPlatform in combination with the ("new machinery") PersistenceException will cause the appropriate Hibernate-specific connection handling policy to be in effect, even if it isn't present in a persistence.xml.
This PR also fixes a setting-the-autoCommit-property-on-a-Connection bug that may be responsible for blocking #7448. We'll see.
Documentation impact: none.

@tjquinno added you as reviewer since you were kind enough to review the "new machinery" back in the day. Obviously check the Github actions etc. and if they're borked don't bother wasting your time; I'll fix whatever breaks first. Any early eyes-on from you would be great.

Related to #4928, and may (finally) fix it.


"varimax" and "quartimax" seem to produce the same outcomes.

Hey Tomas,
I've noticed that happening a lot as well. I've noticed that it happens regardless of whether you use a pure-python or tensorflow rotation method. Those two each use different approaches to optimizing the varimax/quartiamx criteria, so I doubt that this is due to algorithm bug.
I think that the issue is that for many datasets the two criteria will result in components that are really similar. I don't have a strong intuition for when that would happen, but it definitely seems that way for small toy datasets.
If you have an example where this is happening and you know that it's wrong, I'd love to see it so I can find where the code is going awry


Header image of diff. size between pages

Environment

Minimal Mistakes version: Think latest as is configured as remote theme
Ruby gem or remote theme version: Remote theme method
Jekyll version: Think latest as is configured as remote theme
Git repository URL: https://github.ceso/ceso.github.io
GitHub Pages hosted (if yes provide URL to site): yes, https://ceso.github.io/
Operating system: Linux Manjaro

Expected behavior
The default header of the site, configured in:
defaults:
  # _posts
--- CUTED ----
  # _pages
  - scope:
      path: "_pages"
      type: pages
    values:
      layout: single
      author_profile: true
      header:
        overlay_image: "/assets/images/site/banner-site.jpg"
--- CUTED ---

Appears in different size between the home page/404 vs /posts /tags /categories /about.html (in the last ones is a bit smaller).
None of those pages had over-writen the default header (yes the posts itself)
Steps to reproduce the behavior
Example going to my blog:
https://ceso.github.io/
and jumping into https://ceso.github.io/about.html
they were took with google chrome, but is the same with any browser.
Other
Here I leave 4 screenshots, comparing between the home page, a not found page, about, and posts:

they were took with chrome, but is the same behaviour with other browsers.
Is possible to notice the size on them changes.

The image is technically a background image and depending on how much text content you have determines the height of the container. The less text, the lower the height and it appears the image is being cut off.
If you want to force the height of the container to be consistent you can do that with CSS. Search through the closed issues as this has come up before and I know there are more detailed answers available.

https://github.com/mmistakes/minimal-mistakes/issues/542


[FEATURE REQUEST] support Workflow.spec.affinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution

Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST
What happened:
# example.yaml
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: example-
spec:

  affinity:
    nodeAffinity:
      preferredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
          - matchExpressions:
              - key: role
                operator: In
                values:
                  - "worker"

  entrypoint: whalesay
  templates:
  - name: whalesay
    container:
      image: docker/whalesay:latest
      command: [cowsay]
      args: ["hello world"]

argo submit example.yaml

2019/08/16 21:56:36 Failed to parse workflow: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal object into Go struct field NodeAffinity.preferredDuringSchedulingIgnoredDuringExecution of type []v1.PreferredSchedulingTer

What you expected to happen:
submit succeed and scheduled on node which has label "role: worker".
Environment:

Argo version:

$ argo version
argo: v2.3.0
  BuildDate: 2019-05-20T22:11:23Z
  GitCommit: 88fcc70dcf6e60697e6716edc7464a403c49b27e
  GitTreeState: clean
  GitTag: v2.3.0
  GoVersion: go1.11.5
  Compiler: gc
  Platform: darwin/amd64

Kubernetes version :

$ kubectl version -o yaml
clientVersion:
  buildDate: "2019-08-05T16:54:35Z"
  compiler: gc
  gitCommit: f6278300bebbb750328ac16ee6dd3aa7d3549568
  gitTreeState: clean
  gitVersion: v1.15.2
  goVersion: go1.12.7
  major: "1"
  minor: "15"
  platform: darwin/amd64
serverVersion:
  buildDate: "2019-08-05T09:15:22Z"
  compiler: gc
  gitCommit: f6278300bebbb750328ac16ee6dd3aa7d3549568
  gitTreeState: clean
  gitVersion: v1.15.2
  goVersion: go1.12.5
  major: "1"
  minor: "15"
  platform: linux/amd64

You can do something similar with requiredDuringSchedulingIgnoredDuringExecution,
but I want to use preferredDuringSchedulingIgnoredDuringExecution.

I realized my definition was wrong. sorry my noisy issue.


Collaboration between Amelie (vipnvap), Chirel (54R7EURTIF), Wassim (wassimderbel-hub) and Vincent (tovincent) : (FUN) (readme is in the pull request and main.tex is in the comment)"Gameplay Update: Wildcard Round Addition and Clarified Prompt Definitions in 'What Could Go Wrong'"

This pull request introduces comprehensive enhancements to the "What Could Go Wrong" game's instructions, including the innovative Wildcard Round that brings a strategic layer to the gameplay. The modifications present in this pull request are as follows:
Clarification of Rules for Understanding Prompts: A new rule has been added where if a player is unclear about the meaning of a term on a prompt card, there is a structured approach to ensure everyone has a shared understanding before proceeding. This process involves group discussion and, if necessary, a decision by the Card Czar to establish a consensus on the term's meaning.
Wildcard Round Integration: The most notable update in this pull request is the formal introduction of the Wildcard Round. This feature is triggered at a pre-defined moment in the gameplay cycle, such as after every third round, and it allows players to play two white cards instead of one. The specifics of the Wildcard Round are:
Activation: Clear guidance is provided on when the Wildcard Round becomes active, injecting an element of surprise and anticipation into the game.
Dual Play: Players can strategically choose two white cards to play together, adding depth as they consider how the cards interact with each other and the prompt.
Double Points Opportunity: The stakes are higher in this round, as a player can earn double points if the Card Czar selects their combination of white cards, promoting more thoughtful play and card synergy.
Scoring Adaptations for Wildcard Round: Adjustments to the scoring system to accommodate the Wildcard Round, providing potential for a player to earn double points for a well-chosen card pair, enhancing the competitive aspect of the game.

We have also edited the main.tex to include both edits.

I'm enthusiastic about the Wildcard Round addition, seeing great potential for strategic depth. I recommend randomizing its occurrence to keep the game unpredictable and engaging. Additionally, providing clear examples for Dual Play could help players grasp this new concept more easily. I’m also interested in contributing to playtesting to ensure this feature enhances the game as intended.

the updates main.tex is : % adopted from "Riddles in the Dark" template on Overleaf
% incorporated ideas from "Mailmerged Conference Name Cards" template
\documentclass[grid,avery5371]{flashcards}
% include font icons
\usepackage{fontawesome}
% format url
\usepackage{hyperref}
% specify the variant (AV, AI, LLM, etc) among available card decks.
\newcommand{\deck}{flow}
% read card info from external file
\usepackage{datatool}
%% The "database" is a comma-separated values (CSV) file.
%% The first line should contain the column headers, without space characters, e.g.
%% Name,JobTitle,Department
%%
%% If a field value contains a comma, then the field value needs to be surrounded with double quotes, e.g.
%% John Smith,Lecturer,"School of Science, Mathematics and Engineering"
%%
%% Spreadsheet applications can usually export such a .csv file.
%%
%% If field values are expected to contain LaTeX special characters like $, &, then use \DTLloadrawdb{data}.csv instead.
\DTLloaddb{prompt}{prompts-\deck.csv}
\DTLloaddb{response}{responses-\deck.csv}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{ebgaramond}
\usepackage{tikz}
\usepackage{multicol}
\geometry{headheight=12pt,footskip=4pt}
\usepackage{fancyhdr}
\pagestyle{fancy}
\fancyhf{}
\renewcommand{\headrulewidth}{0pt}
\chead{\small What could go wrong? ({\sc \deck} deck) }
\title{What could go wrong?}
% compiled by:
\author{Matthijs den Besten}
% based on work by Nik Martelaro
% see resitory at https://github.com/mdbesten/what-could-go-wrong-llm
\cardbackstyle[\Huge]{plain}
\cardfrontstyle[\large]{headings}
\begin{document}
\cardfrontfoot{What could go wrong?\qquad\faicon{creative-commons}}
\begin{flashcard}[\faicon{gamepad}\quad Gameplay Instructions]{
%\begin{turn}{180}
%\Rotatebox[origin=c]{90}{%
{\bf\small During the game}
\begin{multicols}{2}
\begin{enumerate}\tiny \setlength{\itemsep}{.5ex}
\item Take notes on ideas that you have not thought about before
\item Some of the cards are causes, others are effects. Don’t worry about what the game designers intended with each card, go where the discussion is best.
\item Some of the cards may be upsetting. (Such as, a person is abused.)
\item It’s fine to take time to have discussion.
\item Try not to get sidetracked, though!
\end{enumerate}
\end{multicols}
%}
%\end{turn}{180}
}
{\bf\small What could go wrong?---Gameplay Instructions}
\begin{multicols}{2}
\begin{enumerate}\tiny \setlength\itemsep{.1ex}
\item All players draw 5 event cards from their stack.
\item Use the spinner to select the Card Czar.
\item The Card Czar reads a black prompt card to the group. If unsure about the prompt word, players clarify collectively or defer to the Card Czar's decision.
\item Players think strategically about a card and submit it face down, or a combo in the case of the Wildcard Round, for the best match with the prompt.
\item \textbf{Wildcard Round: Introduced at a set game point, like after every third round. Players can use two white cards for a chance at double points if both cards of one player are chosen by the Card Czar.}
\item The Card Czar reveals and chooses the most fitting or humorous cards. Chosen cards earn points: +1 normally, \textbf{+2 during the Wildcard Round if both cards of one player are chosen}.
\item Discuss the chosen cards and award +1 point for compelling contributions.
\item After discussing, the next player becomes the Card Czar. Each player then draws new cards, so that they again have 5 cards in their hand.
\end{enumerate}
\end{multicols}
\end{flashcard}
% Adopted from http://www.unm.edu/~unmvclib/gamification/assessment/gameevaluationcriteria.pdf
\begin{flashcard}[\faicon{meh-o}\quad Game Evaluation Criteria]{
\begin{itemize}\tiny \setlength{\itemsep}{.1ex}
\item Category Biases
\item Scale 1 to 7
\begin{multicols}{3}
\begin{itemize}
\item Clarity
\item Flow
\item Balance
\item Length
\item Integrity
\item Fun
\end{itemize}
\end{multicols}
\begin{multicols}{2}
\item Strongest Point
\item Weakest Point
\item One Change
\item Comparable Games
\end{multicols}
\end{itemize}
}
{\bf\small What could go wrong?---Game Evaluation}
\small
\begin{tabular}{l|c|c|c|c|}
& 1 & 3 & 5 & 7\
\hline
{\em Clarity} & Opaque & Muddy & Transparent & Water-clear \
{\em Flow} & Cumbrous & Fraught & Smooth & Natural \
{\em Balance} & Broken & Fluky & Sensible & Fair\
{\em Length} & Wrong & Unfit & Apt & Perfect \
{\em Integrity} & Eristic & Erratic & Coherent & Sound \
{\em Fun} & Offputting & Boring & Engaging & Exciting \
\hline
\end{tabular}
\end{flashcard}
\begin{flashcard}[\faicon{star}\quad Wildcard Round]{
\begin{center}
\begin{tikzpicture}[scale=1]
% Title with customized font
\node[align=center, font=\bfseries\Large] at (4cm, 4.5cm) {Wildcard};
% Additional customization
% You can add more elements here to customize the first side further

\end{tikzpicture}
\end{center}
}
{\bf\small Wildcard Round}
\begin{center}
\begin{tikzpicture}[scale=1]
% Card background
% Quote
\node[align=center, font=\itshape, text width=6cm] at (4cm, 2.5cm) {Go wild for a while}; % Adjusted position and width

% Instruction Text
\node[text width=7cm, align=center, font=\footnotesize] at (4cm,1cm) {Play two cards this round for a chance to double your points!}; % Adjusted position and width

\end{tikzpicture}
\end{center}
\end{flashcard}
\DTLforeach{prompt}{%
%% Map each column header in your .csv file to a command
\Description=PROMPT,%
\Category=LABEL,%
\Id=NUMBERS%
}{%%%  Start designing your output text!
\begin{flashcard}[\deck:\quad\Id\quad\DTLifnull{\Category}{}{\Category}]{%
%\begin{verse}[\versewidth]
\Description
%\end{verse}
}
\faicon{tasks}\quad{\sc \deck}\
\end{flashcard}
}
\DTLforeach{response}{%
%% Map each column header in your .csv file to a command
\Description=RESPONSE,%
\Category=LABEL,%
\Id=NUMBERS%
}{%%%  Start designing your output text!
\begin{flashcard}[\deck:\quad\Id\quad\DTLifnull{\Category}{}{\Category}]{%
\Description
}
\faicon{reply}\quad{\sc \deck}\
\end{flashcard}
}
\end{document}

The Wildcard Round is an excellent addition, introducing an element of unpredictability that can energize the game. I recommend including a few scenarios or examples to guide players on how best to leverage this opportunity, especially for those less familiar with strategy-based card games.
It might be helpful to adjust the scoring system to integrate the Wildcard Round smoothly. Ensure that the scoring rules are easy to follow and do not disrupt the flow of the game. It could be beneficial to include a brief section on score-keeping best practices with the new system.
The documentation is clear, but adding a FAQ section could preemptively address any questions or uncertainties that may arise from these new rules, and I believe you should put the code to main.tex file in the final edition rather than write in the comment.


Result file missing

I have finished the task 'python3 run_exper.py gnn_lisa 0 0 13', but I cannot find the result file or folder. Would you please tell me how to solve this problem? Thank you.

Hi, can you create a folder "result" in lisa/cgra_me?

I have updated the repo and this bug has been fixed. Please use the latest code.


Vendor as needed

vendor/modules.txt is updated whenever "go mod vendor" is run, so we
can use that to track vendor freshness compared to go.mod. This avoids
problems with an already-present but out-dated vendor directory when
we add or update dependencies.
Signed-off-by: Stephen Kitt<EMAIL_ADDRESS>

Needs a manual rebase.


Redis memory strategy crashes app when trying to save access token

https://github.com/Shopify/shopify-node-app/blob/master/shopify-express/shopStore/RedisStrategy.js#L15
I got it working by changing done(null, clientToken); to done(null, shopData);

Should be closed as per https://github.com/Shopify/shopify-express/pull/11 ?


BUG: Fix GIL handling in _sosfilt

Reference issue
Follow up to https://github.com/scipy/scipy/pull/13087#discussion_r525265920
What does this implement/fix?
The nogil annotation doesn't actually release the gil, you do still need the with nogil. Also, cpdef doesn't do anything if the function isn't actually called from a C or cythonized function.

Yes the idea was to call this function from some other cythonized function if we decide to implement it later on. And cpdef makes it call the underlying cdef with nogil enabled so I'm not sure if what you wrote is correct.

In fact if I leave the with gil in the object path complains that you can't use a gil function inside a nogil. So either docs are wrong or there is a cython bug about it

Yes the idea was to call this function from some other cythonized function if we decide to implement it later on.

I would lean toward YAGNI here. If it is needed in a cython context, then the appropriate changes are small and could easily be included in that PR. Until such a time, there's no need to make cython generate two interfaces to this function.

cpdef makes it call the underlying cdef with nogil enabled so I'm not sure if what you wrote is correct.

That's incorrect, you can look at the output of cython -3 -a _sosfilt.pyx and see that there is no gil handling in a cpdef ... nogil function.

In fact if I leave the with gil in the object path complains that you can't use a gil function inside a nogil. So either docs are wrong or there is a cython bug about it

When you declare a function as nogil it must be valid to call without the GIL, but is not required to not hold the GIL. So, the error message is correct.

If it is needed in a cython context, then the appropriate changes are small and could easily be included in that PR. Until such a time, there's no need to make cython generate two interfaces to this function.

I would argue the opposite since it is small it doesn't make any difference, but anyways I don't mind.

When you declare a function as nogil it must be valid to call without the GIL, but is not required to not hold the GIL. So, the error message is correct.

I quite disagree with this because that's just "keep the door open but don't let in" behavior and it is unfortunate. What's the point of declaring it if you can't declare it nogil anyways without placing thousands of with nogil statements? Doesn't make any sense to me

What's the point of declaring it if you can't declare it nogil anyways without placing thousands of with nogil statements?

You can't call any functions from a nogil context, unless that function is declared as nogil. This way you ensure at compile time that no functions which require the GIL are ever called without it.

Declaring a function with gil (i.e. as acquiring the GIL on entry) also implicitly makes its signature nogil.
What does this even mean?

A function that acquires the GIL on entry is obviously safe to call without holding the GIL before calling it. I can see how gil and nogil annotations doing completely different things is confusing though.

OK please let me understand. So how are we supposed to release GIL from a Python call to a nogil function? By always nesting it in a def function that has with nogil in the body?

I believe it's safe to have with nogil when the GIL isn't held, so you could just do:
cpdef void foo() nogil:
    with nogil:
        pass

So that brings us to the change you have on this pr right? Because then it becomes
def foo():
    with nogil:
        pass

Cython is very confusing me lately.

The motivation for this btw is that re-aquiring the GIL can be an expensive operation. So it often makes sense to call nogil function without releasing the GIL first.

I think I am not knowledgeable enough to appreciate these subtleties or the syntax is confusing. But anyways that's a different story. Let's get this in first. Thanks all.


feat(materials): New JACOCO_XML material type and support for policies

This PR fixes does:

Fixes Junit XML autodiscovery,
Adds support for Jacoco coverage reports (XML)
Adds support for policies for both JACOCO and JUnit XML

Regarding policy support, it's now possible to create a policy for any of those datatypes. The contents will be injected to the policy engine as always (as well as chainloop_annotations). This is an example of a Rego input for Jacoco:
{
  "chainloop_metadata" : {
    "name" : "sample.xml",
    "digest" : {
      "sha256" : "0a13680c120ff5d4d8bec97dee72e8a35e640ad265a72aca9d80222ddc1fb810"
    },
    "content" : "...",
    "annotations" : {
      "chainloop.material.cas.inline" : true,
      "chainloop.material.name" : "material-1733445732517408000",
      "chainloop.material.type" : "JACOCO_XML"
    }
  },
  "counters" : [ {
    "covered" : 10,
    "missed" : 30,
    "type" : "INSTRUCTION"
  }, {
    "covered" : 1,
    "missed" : 3,
    "type" : "BRANCH"
  }, {
    "covered" : 3,
    "missed" : 10,
    "type" : "LINE"
  }, {
    "covered" : 1,
    "missed" : 6,
    "type" : "COMPLEXITY"
  }, {
    "covered" : 1,
    "missed" : 4,
    "type" : "METHOD"
  }, {
    "covered" : 1,
    "missed" : 0,
    "type" : "CLASS"
  } ]
}

Note that for this specific case, only the coverage summary is injected into the policy.
Example policy (not useful at all):
apiVersion: workflowcontract.chainloop.dev/v1
kind: Policy
metadata:
  name: jacoco-policy-test
spec:
  policies:
    -  kind: JACOCO_XML
       embedded: |
         package main
         import rego.v1
         result := {"violations":[], "skipped": true, "skip_reason":"hello jacoco"}

Example att add command with autodiscovery:

> cldev att add --value test/sample.xml
WRN API contacted in insecure mode
INF evaluating policy jacoco-policy-test against material-1733445914394619000
WRN policy evaluation skipped (jacoco-policy-test) for material-1733445914394619000. Reasons: [hello jacoco]
INF material kind detected kind=JACOCO_XML
INF material added to attestation

Fixes #1623

Awesome, but what's the magic that makes the xml work in policies?

No magic at all, we just unmarshall from XML to Go and marshall again to JSON. For now we do it with Junit and Jacoco.


Remove IO Scheduler suggestions from ProducerSink

See #36
I also fixed few errors in README and upgraded dependencies

@Avasil Looks good!


Client Error on first EGP render

Describe the bug
Upon entering on map, when egp is rendered for the first time console throws a client error
Bug ocurs only on fresh start of Gmod, if server is restarted or changed level there will be no error
[Wiremod] render.PopFilterMin underflow!
  1. unknown - lua/entities/gmod_wire_egp/cl_init.lua:45
   2. xpcall - [C]:-1
    3. RenderToGPU - lua/wire/gpulib.lua:300
     4. _EGP_Update - lua/entities/gmod_wire_egp/cl_init.lua:25
      5. unknown - lua/entities/gmod_wire_egp/cl_init.lua:68

[Wiremod] render.PopFilterMag underflow!
  1. unknown - lua/entities/gmod_wire_egp/cl_init.lua:46
   2. xpcall - [C]:-1
    3. RenderToGPU - lua/wire/gpulib.lua:300
     4. _EGP_Update - lua/entities/gmod_wire_egp/cl_init.lua:25
      5. unknown - lua/entities/gmod_wire_egp/cl_init.lua:68

To Reproduce
Steps to reproduce the behavior:

Start Gmod
Load into any map
Place EGP Screen
Connect E2 to EGP
Refresh chip, to create objects
See error

Video
https://user-images.githubusercontent.com/58744956/177534666-843fc83a-396c-4f28-b537-6ec2c174d534.mp4
E2 Chip
speedometer.txt

The texture_filtering var is being changed but isn't pushing a filter so that's why.


Unstable connection after Upgrade to 2.5.70

I have connected OpenHab to deconz via hue and deconz binding.
After upgrading docker container to actual version, both binding loses connection to deconz container nearly every minute. After doing some investigation it seems to me like deconz is doing constantly reboots inside the container. I have following logs
15:23:49:363 reconnect network done 15:23:49:364 invalid current channel 0 (TODO) 15:23:49:824 saved node state in 13 ms 15:23:49:859 sync() in 34 ms 15:23:49:867 REST API plugin shutting down 15:23:50:278 sync() in 0 ms 15:23:51:006 HTTP Server listen on address <IP_ADDRESS>, port: 80, root: /usr/share/deCONZ/webapp/ 15:23:51:139 CTRL. 3.16.215:23:51:223 dev /dev/ttyAMA0 15:23:51:224 ZCLDB init file /root/.local/share/dresden-elektronik/deCONZ/zcldb.txt 15:23:51:373 parent process /bin/sh 15:23:51:373 gw run mode: docker 15:23:51:376 GW sd-card image version file does not exist: /root/.local/share/dresden-elektronik/deCONZ/gw-version 15:23:51:376 sd-card cid:<PHONE_NUMBER>33324780ffffffff00ec31 15:23:51:393 DB sqlite version 3.16.2 15:23:51:432 DB PRAGMA page_count: 52 15:23:51:435 DB PRAGMA page_size: 4096 15:23:51:450 DB PRAGMA freelist_count: 7 15:23:51:452 DB file size 212992 bytes, free pages 7 15:23:51:473 DB PRAGMA user_version: 6 15:23:51:476 DB cleanup 15:23:51:625 DB create temporary views 15:23:52:091 don't close database yet, keep open for 900 seconds 15:23:52:092 started websocket server at port 443 15:23:52:097 found node plugin: libde_rest_plugin.so - REST API Plugin 15:23:52:099 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin 15:23:52:113 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin 15:23:52:140 dev /dev/ttyAMA0 15:23:52:576 New websocket <IP_ADDRESS>:54392 (state: 3) 15:23:52:655 device state timeout ignored in state 2 15:23:53:607 device state timeout ignored in state 2 15:23:54:558 device state timeout ignored in state 2 15:23:55:515 device state timeout ignored in state 2 15:23:56:515 device state timeout ignored in state 2 15:23:57:411 dev /dev/ttyAMA0 15:23:57:514 device state timeout (handled) 15:23:58:014 wait reconnect 15 seconds 15:23:58:014 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state 15:23:58:014 device state timeout ignored in state 1 15:23:58:118 Announced to internet 15:23:58:118 discovery server date: Wed, 06 Nov 2019 13:23:58 GMT 15:23:58:118     local time seems to be ok 15:23:58:118 discovery found version 2.04.35 for update channel stable

Okay I did some further analyses now. My ConBee II was not connected probably to the deconz inside the docker container. After doing another investigation I found an obvious configuration error inside my docker-compose file. I only added
devices:             - /dev/ttyACM0
But I didn't add the corresponding enviroment variable
 environment:             - DECONZ_DEVICE=/dev/ttyACM0
after adding this line it seems to work fine again. Now the question for me is, why has this worked before in previous version and what has changed it doesn't anymore?


Routing with vue router

Describe the bug
Hi i dont know if anyone posted this issue before, but not as far as i can see..
Routing works fine when in development (npm run dev) but when building and hosted in vercel, only home route is accessible.. other routes goes to 404. anyone had this issue? this is the first time i try vite, strangely i tried to recreate this issue on nuxt but routing works fine even after building to static.
i opened my git to public access as this is just a work in progress for hobby related that you can access here..
https://github.com/billysean/arquatics
Reproduction
https://github.com/billysean/arquatics
System Info
can't find WIMC.exe in any system32 directory
so i'll try to provide any information i can

System
------------
OS : Win 11
Node : v.14.18.1
npm : 8.1.1
CPU : AMD Radeon 4500H

Browsers
-----------
Google Chrome latest
Brave latest
Mozilla Firefox latest

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

i have check your project's code, u are using the route navigation in the wrong way.
For example, in this file:   src\components\Header.vue ,replace 'a' with 'router-link' will solve the problem.

u can get more info from vue-router-next docs https://next.router.vuejs.org/guide/
and https://stackoverflow.com/questions/45387857/router-link-and-href-not-working-in-vue-js

To add to what @toSayNothing said (which appears to be the issue), you may find that routing still doesn't work i.e. 404s once your site is deployed to Vercel. If this is the case, you may need to configure a SPA fallback. Here's an example from one of my projects hosted on Vercel.

As noted by @MatthewZito, this seems to be an spa fallback misconfiguration. With that it should work again for all paths.


[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog
:cl:

add: added a funny haha midround syndie borg shuttle :godo:

Summary by CodeRabbit

New Features

Introduced a new shuttle event configuration for the "Syndicate Striker," enhancing gameplay with new entities and interactions.
Added a new entity, "UnknownShuttleStriker," which includes specific event and loading rules.
Included a preloaded grid for the "SyndieStriker," expanding shuttle event options.

Bug Fixes

Updated weight property for the "UnknownShuttleFrontierProspector" to improve game balance.

At least one assault both should be guaranteed, two saboteurs would suck!


fix(tailwind): use default init_options if none are provided

What is this PR for?
The tailwind extra currently doesn't work with elixir ex/heex files. Using the default init_options fixes this issue.
Checklist

[x] I've read the CONTRIBUTING guidelines.

Why is this needed?
Default options are always merged by lspconfig.
Can you first figure out why this is not working?

I was having issues getting tailwind suggestions to work and couldn't figure out what was different. When I printed out the final opts object from the tailwind extra I noticed init_options wasn't included even though it's in the default config for tailwind. Adding this back resulted in suggestions working as expected.

The final opts object from LazyVim.opts("plugin_name") only outputs the opts that are defined in the plugin spec as parsed by lazy.nvim as far as I know. So, it won't show the default settings for the nvim-lspconfig servers. There's another command you can do that, but I can't remember right now.

I see that you're extending the init_options in your configuration here which adds these entries to the default tailwind config. I enabled the tailwind Extra and opened a .html file and doing =LazyVim.opts("nvim-lspconfig").servers.tailwindcss indeed doesn't show the default options from nvim-lspconfig, but I believe that's because of what I said in my previous post. However, doing =vim.lsp.get_client_by_id(1).config.init_options correctly shows that the default nvim-lspconfig init_options have been extended by what you have in your configuration (change 1 with the client_id shown for Tailwind in :LspInfo). So, maybe there's something else going on?

I see that you're extending the init_options in your configuration here which adds these entries to the default tailwind config.
I enabled the tailwind Extra and opened a .html file and doing =LazyVim.opts("nvim-lspconfig").servers.tailwindcss indeed doesn't show the default options from nvim-lspconfig, but I believe that's because of what I said in my previous post.
However, doing =vim.lsp.get_client_by_id(1).config.init_options correctly shows that the default nvim-lspconfig init_options have been extended by what you have in your configuration (change 1 with the client_id shown for Tailwind in :LspInfo).
So, maybe there's something else going on
PS: I don't do web development, so I couldn't test the Tailwind auto-completion, I'm just detailing what I've observed from a user configuration point of view.

I added it to my config and then decided it could be helpful if I upstreamed the change so no one else would encounter this issue. As for not getting any suggestions, if you don't have a tailwind.config.js file in your project root you won't get any from tailwind.

But that doesn't mean you should add the init_options like this. If you want to upstream the changes, then if you simply added
init_options = {
  userLanguages = {
    elixir = "html-eex",
	eelixir = "html-eex",
	heex = "html-eex",
  },
},

I believe should do the trick. These should get merged with the default init_options from Tailwind.

I didn't want to hardcode the values as they're already provided by the tailwind lspconfig. This way if that config is updated the changes would be included here. Of course if the intention of the tailwind extra is to only provide supported filetypes and leave the rest of the config up to the user I'm more than happy to keep this in my config and close this PR.

But whatever the user adds in his Tailwind nvim-lspconfig spec, it will be merged with the default Tailwind config. So, I don't get why we're extending opts.init_options with tw.default_config.init_options. They already get merged as far as I can tell. Or am I missing something?

That's the issue I noticed. For some reason all of the default tailwind settings seem to be merged, except for init_options.

What does =vim.lsp.get_client_by_id(1).config.init_options show? Change 1 to the client id for Tailwind that is shown in LspInfo.

Oddly enough, both with and without, that command shows init_options under config. Unless I add the settings to my config as well though tailwind lsp doesn't show suggestions. I don't think I completely understand what's happening here, so this PR may have been premature. I'll wait for feedback from folke, but I'm thinking I should just keep these settings in my config.

Yes the command shows init_options in both cases as it should. Without your customization it shows the default options from nvim-lspconfig. With your customizations it should show the init_options with both the default options and your custom ones.
Maybe you don't get auto-completions because you use a different filetype than the ones defined in default Tailwind nvim-lspconfig config and you need to add these to your personal configuration to have auto-completions. What exactly does the userLanguages field do? It seems to be mapping some kind of Tailwind specific filetypes to filetype extensions?

closing, since there's probably something else going on here.
The reason we merge filetypes, is because that's a list and as such won't be merged automatically.


[Suggestion] Regarding issues in Chinese

I know this is probably not the place for this but i don't know where else to reach you,
i'd like to suggest that you try to tell Chinese users to try and report issues in English if and whenever they can, because a lot of people in my current company and others i know of are shutting down Vue proposals on account of not being able to understand bug tickets made for VueJS and the fact many popular libraries are primarily and/or exclusively in Chinese.
It's important for VueJS to have a healthy Chinese community but i feel that the community's disregard for non-Chinese users is ultimately damaging VueJS and frustrating the efforts of Vue evangelists in the west. Couple the non-english documentation and issues with React's facebook backing and it's very hard to convince anyone in management that Vue is the way to go, i feel that i'm not alone and would also like to hear what others have to say about it.

It's important for VueJS to have a healthy Chinese community but i feel that the community's disregard for non-Chinese users is ultimately damaging VueJS and frustrating the efforts of Vue evangelists in the west.

It's important for VueJS to have a healthy English-speaking community but i feel that the community's disregard for non-english users is ultimately damaging VueJS and frustrating the efforts of Vue evangelists in China.
Wouldn't that sound a bit condescending towards your part
On a more serious note, the success of Vue is to no small part due to the Adoption in the chinese market - and that happened because Vue's creatr is chinese and provided great documentation and support in chinese.
While I can empathise with your request it sound a bit like the western market is somehow superior or more important, which we won't side with.
If your company sees it as a problem that a big part of the community is chinese instead of seeing the value in the global adoption, that's their problem. Yes, some of the biggest libs are from china, yet have good english docs. Others of the greatest libs (like Vuetify) are from the west.
Why someone would see that as a negative is beyond me.

@yyx990803 and @LinusBorg I think you guys got it the wrong way, i'm not saying tell the Chinese devs they can't speak Chinese, but rather try to ask them to use English if and when they can as that makes the issues understandable for everyone and invites collaboration from everyone, not just Chinese speakers.
Ultimately i'd like to bring the communities closer together and possibly even have both communities collaborate on stuff, so i'm in no way saying the west is better, i have great respect for Chinese tech and the amazing stuff they manage to do with apps like Wechat.
But fact of the matter is it's more likely for a Chinese web developer to be able to understand english than it is for any western developer to understand Chinese, that's not saying the west is better, just that English is more inclusive amongst developers and should be used whenever possible so that communities don't splinter into different groups based on their first languages, you know?
Maybe there's just one issue currently but there's usually more than one, but all in all, i just wanted to voice a potential issue in trying to promote Vue adoption in companies and start a discussion, if no other people have such problems then it's disregardable and i'll try to bring up the issue to my colleagues again.
Thanks for your attention and sorry to have bothered you guys with a non-issue discussion.

but rather try to ask them to use English if and when they can as that makes the issues understandable for everyone and invites collaboration from everyone, not just Chinese speakers.

What if there are more Chinese speakers in the community? Would you convince us to encourage everyone to file issues in Chinese so “that makes the issues understandable for everyone and invites collaboration from everyone, not just English speakers”?
Ironically we Chinese developers are actually doing a lot in Chinese community to encourage people to use English on GitHub and provide English documentation for their OSS. But unfortunately not everyone can fully express themselves in English while some issue need very detailed elaboration. If they use Chinese instead at least Chinese speakers can understand better and provide some help. The only issue with Chinese content under discussion right now is a good example of this (I suppose it’s the same one Evan mentioned earlier). Given that 95%+ of the discussions are already in English (many of them are provided by Chinese speakers), I just want to ask those who are still trying to eliminate all Chinese usage in the community, to show a little empathy. Maybe it’s not you, but I think you should try to explain this to those who cannot bear to see any Chinese character on the screen instead.

but rather try to ask them to use English if and when they can as that makes the issues understandable for everyone and invites collaboration from everyone, not just Chinese speakers.

Again: not everyone speaks english, so English issues are not "understandable for everyone" - they are understandable for most people from your hemisphere

@Justineo Will do, and thanks for the efforts in trying to encourage it which i'm also sure to mention.
@LinusBorg I feel that one of the good things about development and the web in particular is that first languages are not as much of a barrier as they are in real life, the web is very international and a big part of it is the fact that english is a common language.
I understand that not all of them speak English but especially for new Chinese developers starting out i feel it's important for them to be encouraged to learn it and use it when they can, it brings them into the larger community and tears down walls built around first languages, as well as it opens new doors for them to work outside China, give conferences and learn from non-chinese tutorials.
My first language is not english either, but i don't feel offended in any way by speaking it online and/or being expected to, instead i feel like it's a great thing to bring us all together and break down silly language boundaries that would've splintered us otherwise. All in all what i'd suggest is as @Justineo said simply encouraging them, especially the new devs to use English if they're bilingual.
But at the same time i understand China is different from Russia, India, Romania, etc... especially when it comes to the internet and so Chinese users are more used to having their own internal communities rather than being part of a global internet experience, but that's another issue altogether unfortunately out of our hands.
All in all i feel confident enough that this is a non-issue and that the Chinese community is already working hard to mitigate it.

Also FYI - in the new issue creator we already explicitly encourage Chinese users to use English. This is literally the first thing they see. If they still opt to use Chinese, it's most likely because their English skills doesn't allow them to clearly explain the problem they are trying to describe, and in those cases forcing them to use English just makes the problem harder to understand for everyone involved.
Final comments before I unsubscribe:

There is absolutely no "disregard for non-Chinese users" given the actual percentage of Chinese issues is quite low. I'm not sure where you get that impression from, but that impression is simply wrong. All our communication channels (release notes, Twitter, blog posts, documentation, issues, conferences) are using English as the first (and in most cases the only) language.

If your colleagues or manager cites the presence of Chinese issues as a reason for not adopting Vue, they are probably pulling misleading arguments like "Vue is focused on China only and lacks a western community". Ask them to prove it. Ask them to check how many open issues are actually in Chinese. Ask them to search on Twitter, Medium and StackOverflow to see how many Vue articles and discussions in English are out there. Ask them to search about Vue conferences and meetups going on around the globe. Ask them to read our documentation. Then ask them again do they really think this is going to be a problem.


Modify IterKeyZipper to accept any number (2+) of IterDataPipe

🚀 The feature
Currently, IterKeyZipper can only zip two DataPipes together.
https://github.com/pytorch/data/blob/198cffe7e65a633509ca36ad744f7c3059ad1190/torchdata/datapipes/iter/util/combining.py#L13
The proposal is to modify its API to allow users to pass in any number (two or more) IterDataPipe, rather than just strictly two. We will have to think carefully about how the key_fn and ref_key_fn will change.
Motivation, pitch
There are situations where users may want to zip multiple DataPipes together.
Alternatives
Users will have to write their own custom DataPipes.
Additional context
There are similar DataPipes and we should keep in mind that their APIs should be as consistent as possible.

Another alternative is to "stack" multiple IterKeyZipper's. This is what torchvision is currently doing and it is ugly:

SBD
VOC

Given that we already have use cases for this, I could look into it.


[Feature Request] multiprocessing shared memory

I want parallel processing using multiprocessing.
In this case, each process use huge memory.
How can I reduce memory usage?

Which model are you using? How much memory does it occupy? This may be difficult to achieve, as models tend to consume a lot of memory.


Don't log errors when claim

I think we should still log errors, but only if they are not present in the list of known messages received from the contract.

I"m completely agree with Milen. In the Base app we were doing it like this: https://github.com/aeternity/aepp-base/blob/de884d8bb97053319793cf862b06eea6739ed981/src/pages/mobile/NameNew.vue#L89-L91


WFS tutorial needs update regarding WFS address for GDAL based utilities

It seems that current GDAL needs a WFS: prefix before the plain https:// URL (source). Contrary to the GDAL documentation, at least for the BWK WFS (the only case I tested), it appears that '&' should not be changed in our URLs, so the WFS: prefix is the only thing to add. (See also a function getfeature_sf(), updated accordingly, in https://github.com/r-spatial/sf/issues/1573#issuecomment-866887585.) This affects at least the usecase with sf::read_sf(url), which calls GDAL. I've not tested whether that changes something for the httr::GET() approach, but I don't expect so.
While I believe the request object below is used only for pasting in the browser:
https://github.com/inbo/tutorials/blob/e16db19ae936631395e842000886def2c71df5c2/content/tutorials/spatial_wfs_services/index.Rmd#L90-L96
... in the following chunks the request object is used with read_sf() and still lacks the WFS: prefix:
https://github.com/inbo/tutorials/blob/e16db19ae936631395e842000886def2c71df5c2/content/tutorials/spatial_wfs_services/index.Rmd#L240-L247
https://github.com/inbo/tutorials/blob/e16db19ae936631395e842000886def2c71df5c2/content/tutorials/spatial_wfs_services/index.Rmd#L272-L283
https://github.com/inbo/tutorials/blob/e16db19ae936631395e842000886def2c71df5c2/content/tutorials/spatial_wfs_services/index.Rmd#L319-L328
https://github.com/inbo/tutorials/blob/e16db19ae936631395e842000886def2c71df5c2/content/tutorials/spatial_wfs_services/index.Rmd#L377-L383
https://github.com/inbo/tutorials/blob/e16db19ae936631395e842000886def2c71df5c2/content/tutorials/spatial_wfs_services/index.Rmd#L573-L583
https://github.com/inbo/tutorials/blob/e16db19ae936631395e842000886def2c71df5c2/content/tutorials/spatial_wfs_services/index.Rmd#L611-L625
Beside the above, there are at least three other chunks where request is used for GET - there it must probably stay as-is. So something will need to be said about this difference.
@hansvancalster can you check this further and update the tutorial? Maybe https://github.com/inbo/inborutils/blob/master/R/extract_soil_map_data.R is affected as well, but I don't think so.

I ran the code in the tutorial and everything worked. When I load sf it is linking to GEOS 3.9.0, GDAL 3.2.1, PROJ 7.2.1.
The GDAL documentation also states:

The minimal syntax to open a WFS datasource is : WFS:http://path/to/WFS/service or http://path/to/WFS/service?SERVICE=WFS

So it seems the WFS: prefix is not required. Did you experience trouble without the prefix?

You're right @hansvancalster, 'today' it runs here as well, without problems :thinking:. Running same versions of the backend libraries. Strangely I thought I had this problem yesterday, but now can't reproduce it anymore - bummer.
We had found that execGRASS("v.in.ogr") needs the WFS: prefix to work - after that I tried read_sf() and it seemed as if it didn't work without WFS: either. Most probably that wasn't the cause for error then (perhaps some other URL mistake) - sorry to trouble! Will close this.


Add config to support asdf version manager

This update allows for node versions that are managed by asdf. The solution was found here: https://github.com/gohugoio/hugo/issues/9811.
If you don't use asdf, that's fine; please just ensure you can correctly build the site.

I think 1 approval is enough for this one!


[AUDIT][SPARK-46037][SQL] Correctness fix for Shuffled Hash Join build left without codegen

Describe the bug
This PR fixe a join correctness bug for Shuffled Hash Join build left. We should check our implementation in GpuHashJoin
https://github.com/apache/spark/commit/af5e0a267e5

The plugin doesn't execute with codegen off so this doesn't impact us.


Office Hours: Suggestions and Improvements

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2875
Originally created by @afolson on 2021-08-04 14:53:42

We want to make sure that the community is getting what they need from Office Hours sessions and would like to hear from you.

What's going well with Office Hours?
What's one thing we could improve or do differently?
Is there anything you'd like to see in these sessions?

View 8 previous comments from the original issue on GitLab


write_image (via kaleido) visually distorts large square heatmaps through aliasing artifacts

I have a relatively large matrix that I want to plot usinggraph_objects.Heatmap. The matrix has some structure that should become immediately apparent to the viewer (i.e. it has a constant diagonal and is symmetric). However due to visual artifacts, it looks like these properties are violated in the image produced by write_image (with the kaleido backend, haven't tested orca).
It was difficult to write a simple example script to reproduce these distortions, as variations in both the matrix and output image size can affect the issue significantly (both in intensity and quality). In any case it looks to be an aliasing artifact related to the selection of heatmap cell data that results in a non-bijective map between the heatmap cells and regions within the (vector) output image.
In the script below, one output format is PDF to rule out image compression as a culprit (as there the heatmap appears to be stored as a vector image as its cells remain sharp when zoomed in). However, the issue can be reproduced also when the output format is PNG. I assume that in the vector-output case, the heatmap data is (badly) rescaled like a bitmap image whose pixels are then re-interpreted as an array of square cells, even though those cells then do not match the heatmap/data cells any more.
#!/usr/bin/env python3

import numpy as np
import plotly.graph_objects as go
import plotly.io as pio

resultions = [
    # Gives very unequal cell sizes, making the result look like a mosaic:
    (200, 400, 400),
    # Looks almost correct, but some diagonal elements show bad values:
    (400, 400, 400),
]

for n, width, height in resultions:
    # Produce a random matrix with key properties (symmetric, constant
    # diagonal) matching my actual data.
    np.random.seed(1)
    A = np.random.random(size=(n, n))
    A += A.T
    np.fill_diagonal(A, -1)

    # Plot the matrix as a square heatmap.
    fig = go.Figure()
    fig.add_trace(go.Heatmap(z=A))
    fig.update_layout(
        autosize=False,
        width=width,
        height=height,
        margin=dict(b=0, l=0, r=0, t=0),
        yaxis1=dict(scaleanchor="x1", constrain="domain"),
        yaxis2=dict(scaleanchor="x2", constrain="domain"),
    )
    for ext in ("pdf", "png"):
        pio.write_image(fig, f"n={n}_{width}x{height}.{ext}")

The outcomes are:
PDF:
n=200_400x400.pdf
n=400_400x400.pdf
PNG (note in the first image that only the heatmap, not the text looks blurred):

For n = 200 and a layout size of 400x400, many adjacent rows and columns appear to use the same heatmap data. As a result the diagonal looks to be composed of alternating small and large blue cells. On closer inspection you can see that there are two locations where a double row and a double column meet off-diagonal, so that the result looks asymmetric.
For n = 400 and a layout size of 400x400, the result looks mostly correct but some main diagonal cells are not blue, i.e. they have not been sampled from the data's main diagonal.

Given that my understanding of the problem is correct, I would suggest:

For bitmap output, use a better interpolation method to scale the heatmap image to its output size.
For vector output, if possible, do not go the middle route of rescaling a bitmap image. Instead rescale the vector data.

Thanks for your interest in Kaleido. We are currently working on an overhaul that might address your issue - we hope to have news in a few weeks and will post an update then. Thanks - @gvwilson


 incorrectly converts negative ISO timezones

Short description of the problem:
When <ion-datetime> [(ngModel)] is bound to an ISO string with a negative timezone (ex: 2016-01-01T12:00:00.000-05:00), all updates after a date has been selected get converted with a double minus sign (turns into 2016-01-01T12:00:00.000--5:00) which is incorrect for the spec. Passing it into the constructor of a Date object is an invalid date.
What behavior are you expecting?
Negative timezones should be formatted as -XX:XX instead of --X:XX.
Steps to reproduce:

Create an <ion-datetime> with a negative timezone value.
Open the picker and change it to a new value.
Examine the bound model value to see the change.

Which Ionic Version? 1.x or 2.x
2.0.0-beta.10
Plunker that shows an example of your issue
http://plnkr.co/edit/M6BXQuhHEcV5GtAcRv8M?p=preview
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 6.2.0
Gulp version:  CLI version 3.9.1
Gulp local:   Local version 3.8.11
Ionic CLI Version: 2.0.0-beta.32
Ionic App Lib Version: 2.0.0-beta.18
ios-deploy version: 1.8.6
ios-sim version: Not installed
OS: Mac OS X El Capitan
Node Version: v5.11.0
Xcode version: Xcode 7.3.1 Build version 7D1014

PR merged, closing!


New cases not getting displayed and also new unassigned category cases not shown

Possible duplicate of #2084

This happened because of MoHFW decreasing the count of 'State Unassigned'. Should be okay now


Falloff Map Makes 9 chunks

I have been having an Issue regarding the falloff Map settings creating 9 terrain chunks after finishing the 21st episode and adding the fix for the falloff map. I really would appreciate any help
edit:
Turns out it doesnt just create 9 other chunks but instead creates an endless map of multiple falloff maps

Sorry I’m late - Did you ever find a way to get around this? I’d like to have the falloff map generate over all of the chunks together, not each individual chunk.

I want to have 10 x 10 terrain chunks before it falls off. Anyone think it's possible?

Sorry I’m late - Did you ever find a way to get around this? I’d like to have the falloff map generate over all of the chunks together, not each individual chunk.

Hi did you find the solution?

yah did you find the sollution


Remove application banner and redirect

[x] /apply redirect
[x] Application banner
[x] Remove scheduler banner too

PR: #627


add ptx formatter + syntax highlighter

Also doing formatting as it's easier to compare ptx to cuda backend code.
orange - instruction or immediate value
purple - state space
blue - operand or identifier
green - type
white - modifier (be it infix or prefix)

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/runtime/ops_cuda.py              19               2
------------------------------------------------------------
lines added in the tinygrad folder: 17

It's not obvious to me reading this that the text will always be the same (just colored differently)

oh, so we don't want to format it (fix indentation on args and instructions, add newlines for params) ?

I'd merge the colorizer.

I'd merge the colorizer (if it's clear from code it's just a colorizer), I think the formatting is fine from what I've seen. The risk is that it misprints the ptx and that bug wastes hours of someone's time.

Done. Explained in the comment in code:
all expressions match <valid_before><expr><valid_after> and replace it with <valid_before>color(<expr>)<valid_after>
The only caveat is that we don't color conditional instructions, but doing that would add additional complexity to the tokenizer which I don't think is worth it.

Thanks!


chore: 絵文字Seqの調整

Type of Change:

新規追加
改善

Details of implementation (実施内容)

腹切り の り の部分の更新
絵文字が削除された雪留年のSeqを削除
以下のSeqを追加
　 - 留年
　 - 最悪
　 - 黙れ
　 - 腹切れよ

Codecov Report

Merging #419 (a1b4f21) into main (f38fa84) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #419   +/-   ##
=======================================
  Coverage   71.12%   71.12%
=======================================
  Files          57       57
  Lines        3851     3851
  Branches      360      360
=======================================
  Hits         2739     2739
  Misses        752      752
  Partials      360      360

Flag
Coverage Δ

unittests
71.12% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


PoC for centralized throttling control

PoC for using a centralized middleware to control
1k-per-minute get requests to graph api.

Does this PR need a docs update or release note?

[x] :no_entry: No

Type of change

[x] :robot: Supportability/Tests

Test Plan

[x] :muscle: Manual

Success on a small backup
Connecting to repository:      4s done
Connecting to M365:         done
Connecting to M365:         done
Discovering items to backup:     21s done
∙ contacts -<EMAIL_ADDRESS>     1s done
∙ email -<EMAIL_ADDRESS>     9s done
∙ events -<EMAIL_ADDRESS>     8s done
Backing up data:     15s done
  Started At            ID                                    Status     Resource Owner
  2023-03-21T01:11:10Z  ce01d963-4936-46f1-931a-9d1306d7e809  Completed<EMAIL_ADDRESS>
Large backup test is running overnight.

With change to rate library:
Confirmation of a small backup success
Connecting to repository:      3s done
Backing Up ∙<EMAIL_ADDRESS>Connecting to M365:         done
Discovering items to backup:     22s done
∙ contacts:      1s done
∙ email:      9s done
∙ events:      9s done
Backing up data:     18s done
  Started At            ID                                    Status     Resource Owner
  2023-03-21T22:08:53Z  319eaf79-0406-4310-9e0a-c8407409adb2  Completed<EMAIL_ADDRESS>
Confirmation of (ongoing) large backup success
Connecting to repository:      3s done
Backing Up ∙<EMAIL_ADDRESS>Connecting to M365:         done
Discovering items to backup:   2m24s done
∙ contacts:      1s done
∙ email:   2m16s done
∙ events:      4s done
Backing up data:  11m39s ∙∙∙
email ∙∙∙∙∙∙∙●∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙  1714 - Test2
email ∙∙∙∙∙∙∙●∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙  1685 - Test1
email ∙∙∙∙∙∙∙∙∙∙∙∙∙∙●∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙  1049 - Test10
email ∙∙∙∙∙∙∙∙∙∙∙∙∙∙●∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙  1051 - Test9

any new updates on the large backup test with this?


Add logo to docusaurus website

Docusaurus has a users page where we showcase projects using Docusaurus. This has the benefits of giving projects recognition and also lets the community and new users reference the creative ways of using Docusaurus.
I would like to add your project if you don't mind.
Kindly let me know your decision asap. Thanks

Please go ahead 👍

In our logo repository we have two png logos and the svg versions.
You can use the one which fits best :)

@dbanck  I converted the one used in the README.md to svg and used for that.
You can look at it and let me know what you think. I will change it if you want me to. https://github.com/facebook/Docusaurus/pull/1176


Image size in xml files

Image width and height match in xml files do not meet the real image size.

Hi giakou4,
please excuse my late reply.
I searched for the .xml files with wrong image width and height information and corrected them.
Thank you!


The Headers API is missing methods

Looks like get is the only method mocked:
https://github.com/pinterest/service-workers/blob/master/packages/service-worker-mock/models/Headers.js
I may be able to submit a PR in a few days, but if someone else can get to it sooner, that'd be much appreciated :)

Yes, this mock definitely needs some love!

This should be fixed now!


Make --update-dir optional when using --dry-run for "update prepare"

At this moment, --update-dir is mandatory even when I'm using dry-run.
update prepare --dry-run --dir=... should be enough for getting a list of available updates.

Actually thinking about it, maybe the best way would be to remove --dry-run and replace it with update list or update check subcommand WDYT?

update list makes sense to me too.

If you slipt it up, then there will be a time gap between the update list and update prepare, so your list could end up preparing different updates

well, we always get such a possibility, I don't know if the tool is doing something behind scenes to prevent preparing a different server that has been updated with a different set of updates.
If you slipt them up, you will also remove the user configuration accepting the list of updates?

well, we always get such a possibility, I don't know if the tool is doing something behind scenes to prevent preparing a different server that has been updated with a different set of updates.

no there's no check at the moment. We could add it though if it's necessary

If you split them up, you will also remove the confirmation to accept the list of updates?

no, the confirmation will still be there as well as the --yes override


fix daylight saving issue for non utc dates

In some cases the date written and read from database are not the same. This only happens if the connection is established with options.useUTC = false. My node and sql server run both in the CET/CEST timezone.
Example:
Input date "2015-06-18T22:00:00Z" -> 2015-06-19 00:00:00 CEST
Output date "2015-06-17T22:00:00Z" -> 2015-06-18 00:00:00 CEST
This was caused because the EPOCH_DATE used to calculate the days since 1900-01-01 did not consider the daylight savings difference. The calculated difference was 42171.958333333336, which was floored down to 42171. When taking the DST into account the difference would be 42172 days.
fixed datatypes:
datetime
datetime2
smalldatetime
date

Hey @lchngr, many thanks for your contribution.
Would you be so kind to provide a unit and/or integration test that shows that this fix is working correctly and to ensure we don't reintroduce this in the future?

Hi @arthurschreiber
I think I'll be able to provide some unit tests, but for the integration tests I think I'll need some guidance, how to do it correctly. This environment is pretty new for me.

I just spent a while tracking down the source of this bug and was just about to make a pull request until I saw this sat at the top :)
When can we expect a version bump with this fix? I'm using the node-mssql library in my project which is dependent on this.


support local src mounting with subpaths

Current behaviour
> wskdebug myaction path/to/myaction/myaction.js
=> will mount path/to/myaction/ to /code in the docker container
see https://github.com/adobe/wskdebug/blob/master/src/kinds/nodejs/nodejs.js#L38
Nice to have
would be great to have something like
> wskdebug myaction path/to/myaction/myaction.js --local-root path/
Why
this would enable things like require('../whatever.js') or having node_modules in a parent directories

To avoid adding more cli args, what about using the current working directory as source mount?
I think one usually starts wskdebug it in the root of the „project“, the sourcePath is then always relative to it and VS Code / IDE debug launcher configurations will also usually be run in the root of the project.
AFAIK there is nothing else at this point depending on the current working directory.

Ok so you mean sourceDir becomes cwd instead of parent folder?
I am ok with that but I think it is a breaking change

Not sure if it‘s a breaking change. If the source argument is a relative path, the only change is that we mount at a higher level of the folder hierarchy and include „more“, which is what we want. It will still load the same source file.
Some examples for the mounting:

wskdebug myaction action.js

dir: .
file: ./action.js
identical

wskdebug myaction src/folder/action.js

before

dir: src/folder
file: action.js

after

dir: .
file: src/folder/action.js

I think for the file watching it should also be ok. Need to try.

@alexkli the breaking change I experienced was with the vscode launch.json config and localRoot/remoteRoot fields, where vscode maps a remote file in $remoteRoot/path/to/file to a local file in $localRoot/path/to/file
let's say we have:
cwd -> actions -> myaction -> index.js
if localDir is mounting at parent path then localRootmust be set to to cwd/actions/myactions
if localDir is mounting at cwd then localRoot must be set to cwd
so an existing vscode config with nested subfolders will break with this change

AFAICS that would also be the case with your PR, as we change the mount location after all.
wskdebug itself still works, it just affects the vscode configs and only if you have a nested path. Which probably didn’t work well... so this change would be welcome, I think. We can log a note about this change if wskdebug is called with a relative path.
In my personal experience (which might be skewed), 90% the action source file is in the root and there is no relative path.

BTW we also have to think what to do with —build-path, it needs the same fix. Here it might need to have a separate argument, as it must be a different folder than the project = current working directory.

AFAICS that would also be the case with your PR, as we change the mount location after all.
wskdebug itself still works, it just affects the vscode configs and only if you have a nested path. Which probably didn’t work well... so this change would be welcome, I think. We can log a note about this change if wskdebug is called with a relative path.
In my personal experience (which might be skewed), 90% the action source file is in the root and there is no relative path.

Well with my PR the default behaviour of parent mounting would be preserved and only if the source-root option is provided we would do the cwd mounting.
Anyways I agree with you that cwd mounting is welcome, and I am happy to do the change

BTW we also have to think what to do with —build-path, it needs the same fix, in case the built source structure is nested. Here it might need to have a separate argument, as it must be a different folder than the project = current working directory.

ok good point! will push some changes together with cwd changes

@alexkli wdyt about:
--build-path only => mount cwd
--build-path and --build-path-root => mount build path root

For only —build-path, I don‘t think we can ever mount cwd. It would mess up things. The build path means you compiled, transpiled etc. the entire source code into a new directory, which needs to be „isolated“ from the normal sources, i.e. it would almost always be a subdirectory.
And usually the built structure would be pretty flat, so in most cases that would work and you would only need the one —build-path argument.
I would keep —build-path as is (use parent dir). But if —build-path-root is given, use that for mounting, as you write.

yup makes sense thanks for the details!


tour: clarify when to use pointer receivers

There appears to be a confusion (at least to me) on what the appropriate receiver type ought to be by default.
Looking at; https://tour.golang.org/methods/8
That tutorial encourages new go users that:
There are two reasons to use a pointer receiver.
The first is so that the method can modify the value that its receiver points to.
The second is to avoid copying the value on each method call.
this seems to imply that you should default to using pointer receivers in only those two cases.
whereas looking at; https://github.com/golang/go/wiki/CodeReviewComments#receiver-type and a few other credible go sources eg; https://twitter.com/rob_pike/status/788743046280077313
we see that actually, pointer receivers should be the default while value receivers are the exception.
So to summarize; the tour.golang notes makes it appear as if pointer receivers are the exception(that was my impression when I went through those notes as a new go user some months back) whereas in actual sense they are (or ought to be) the default.

Where does the tour code live? This doesn't appear to be part of the main go codebase.

The tour is in golang.org/x/tour.

Aha, thanks @ianlancetaylor - CL on the way.

https://go-review.googlesource.com/31728

This is my first contribution to any of the Go projects. Who is assignment of the issue up to? Do people generally just self-assign once they have a patch ready? If anyone here knows how that workflow goes, please let me know.

We don't use the "assignees" of these issues very seriously.  It's sufficient to leave a comment saying that you have sent a CL, as you did.  Thanks.

all of you, thank you.

Can anyone recommend another reviewer here? I got a +1 but seems like we need at least one more?

I've pinged @campoy on the Gerrit CL.


German translation

Working on german translation. Will upload the file here then (im pretty new on github)

https://github.com/vergecurrency/VERGE/pull/311

pull number: https://github.com/vergecurrency/VERGE/pull/311
closing issue -- should be merged soon ..  Thank you for the assistance everyone !


Alps 1696 - Accelerometer

Add a plugin to display the acceleration and g-force with an accelerometer, given GPMF telemetry from a GoPro. Can be tested in the sample Metadata (in the branch metadata of the samples repo).

 All committers have signed the CLA.


update feature: SubtractUpcomingFromAvailable

I reworked this feature to track upcoming transactions into future months. Also includes lots of various fixes/improvements. This is all on top of my other PR. https://github.com/toolkit-for-ynab/toolkit-for-ynab/pull/2446

Additionally, if one credit card payment category is selected, the inspector message gets changes directly instead of adding entries to the budget breakdown.

I'm currently in the process of adding destroy() methods to both SubtractUpcomingFromAvailable and ShowAvailableAfterSavings.

@joshmadewell I finished adding the destroy methods and implemented the requested changes from the previous PR.


fix(kvs/sink_gstreamer_sample): Use videotestsrc and add additional debug logging

Issue #, if available
When running the sample on a mac in live_source mode (./kvs_gstreamer_sample demo-stream), we would get "Elements could not be linked." error. We tested this on both m1 mac, and intel mac, each using GStreamer Core Library version 1.22.5 and encountered this error both times.
What was changed, and how was it changed?

In live_source mode, use videotestsrc instead of autovideosrc
Add additional debug logs
The same was also applied to kvssink_gstreamer_sample, as these samples are very similar.

Fix typo in kvssink_gstreamer_sample: gracefully.

Why was it changed?

We determined that data->h264_stream_supported is true, therefore, this pipeline was getting created.
autovideosrc has ANY pads, so, when data.h264_stream_supported being determined, the intersection will always return true. autovideosrc's pads do not accurately reflect the available elements on the device, as that is determined during the application runtime. Both this if statement and this if statement return true with autovideosrc.
Neither autovideosrc, videotestsrc or avfvideosrc output video/x-h264, therefore it cannot be directly linked to h264parse.

You can confirm this by using the following: gst-launch-1.0 <src element> ! capsfilter name=filter caps="video/x-h264" ! fakesink and seeing "WARNING: erroneous pipeline: could not link <src element> to filter". The application should be choosing to construct the top pipeline with the encoder element, rather than the bottom pipeline.

By switching autovideosrc to videotestsrc, the correct caps are advertised, and the sample application (using gst_caps_can_intersect) is able to choose the correct pipeline to construct.

Testing

Ran both samples in live source mode: ./kvs_gstreamer_sample demo-stream and ./kvssink_gstreamer_sample demo-stream and verified playback in the AWS management console.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report
Patch coverage has no change and project coverage change: -0.10% :warning:

Comparison is base (4c4afff) 16.56% compared to head (08f8182) 16.47%.

:exclamation: Current head 08f8182 differs from pull request most recent head a065396. Consider uploading reports for the commit a065396 to get more accurate results

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1047      +/-   ##
===========================================
- Coverage    16.56%   16.47%   -0.10%
===========================================
  Files           51       51
  Lines         6778     6793      +15
===========================================
- Hits          1123     1119       -4
- Misses        5655     5674      +19

Files Changed
Coverage Δ

samples/kvs_gstreamer_sample.cpp
0.00% <0.00%> (ø)

samples/kvssink_gstreamer_sample.cpp
0.00% <0.00%> (ø)

... and 2 files with indirect coverage changes

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

Can we please correct all of those as well so we do not have silent failures.

Added.


Fix borrowed Cow<'_, [u8]> deserializing as str.

This changes the deserialize implementation for a borrowed Cow<[u8]> to specifically request a byte slice, rather than a borrowed string.
The old behavior breaks any program which relies on data being deserialized the same way as it was serialized and uses Cow<[u8]>. In serde_json, it just wouldn't deserialize. In bincode, it deserialized normally unless the bytes were invalid UTF8.
See https://github.com/TyOverby/bincode/issues/231 for error description, and test program.
I'm not sure where a test for this behavior would fit in, since it's a "what hint to provide the deserializer" failure, but if needed I can try and make one.
Thanks!

I published this fix in serde 1.0.30.

Thanks! Glad to have this working.


Support for @derivedFrom field on an interface

Do you want to request a feature or report a bug?
Feature
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
The following schema throws an error:
interface Owner {
  id: ID!
}

type Pool implements Owner @entity {
  id: ID! # Contract address
  loanPositions: [LoanPosition!] @derivedFrom(field: "owner")
}

type User implements Owner @entity {
  id: ID! # ethereum address
  loans: [Loan!] @derivedFrom(field: "borrower") # Loans, created by the user
  loanPositions: [LoanPosition!] @derivedFrom(field: "owner")
}

type LoanPosition @entity {
  id: ID!
  owner: Owner!
  loan: Loan!
}

Error:
✖ Failed to deploy to Graph node http://localhost:8020/: subgraph validation error: [SchemaValidationError([InvalidDerivedFrom("Pool", "loanPositions", "field owneron typeLoanPosition must have one of the following types: Pool, Pool!, [Pool!], [Pool!]!")])]

@lutter is this a bug or expected behaviour? The challenge seems to be that Pool expects the LoanPosition derivedFrom field to be its own type (Pool), when it is Owner?

Is there a status update on this bug/feature? This is fairly integral to how I would like to implement my subgraph relationships

Any progress on this?


Add .config/cargo/config.toml to probe list

Describe the problem you are trying to solve

Many programs, like git, also look for config file in their own directory in $XDG_CONFIG_HOME and If $XDG_CONFIG_HOME is not set or empty it looks in  $HOME/.config. It would be nice if cargo also do this.
Describe the solution you'd like

Cargo to look for config.toml in $XDG_CONFIG_HOME/cargo and $HOME/.config

Thanks for the suggestion!  I believe this is a duplicate of #1734 (or at least a subset of), so I'm going to close in favor of that.

Being a subset it is much easier to implement. And if this is available, CARGO_HOME can be happily assigned to ~/.local/share/cargo
This will for most part match with Go, which stores it's config (env) file at ~/.config/go/env and has GOPATH variable for most other things (which I set it to ~/.local/share/go).