E2E tests are using the wrong image tags

Describe the bug
The github action e2e is using the wrong images, we expected the e2e tag images will be used, but it always uses the latest images.
╰─$ IMAGE_TAG=e2e make test-e2e
Using existing helm from "_output/tools/bin/helm"
_output/tools/bin/helm install cluster-manager deploy/cluster-manager/chart/cluster-manager --namespace=open-cluster-management --create-namespace --set images.registry=quay.io/open-cluster-management,image.tag=e2e
NAME: cluster-manager
LAST DEPLOYED: Mon Dec  9 21:32:22 2024
NAMESPACE: open-cluster-management
STATUS: deployed
REVISION: 1
TEST SUITE: None
kubectl config view --minify --flatten > ./.hub-kubeconfig
kubectl config set clusters.kind-kind.server https://<IP_ADDRESS> --kubeconfig ./.hub-kubeconfig
Property "clusters.kind-kind.server" set.
_output/tools/bin/helm install klusterlet deploy/klusterlet/chart/klusterlet --namespace=open-cluster-management --set klusterlet.create=false,images.registry=quay.io/open-cluster-management,image.tag=e2e --set-file bootstrapHubKubeConfig=./.hub-kubeconfig
NAME: klusterlet
LAST DEPLOYED: Mon Dec  9 21:32:24 2024
NAMESPACE: open-cluster-management
STATUS: deployed
REVISION: 1
TEST SUITE: None
go test -c ./test/e2e
./e2e.test -test.v -ginkgo.v -nil-executor-validating=true -registration-image=quay.io/open-cluster-management/registration:e2e -work-image=quay.io/open-cluster-management/work:e2e -singleton-image=quay.io/open-cluster-management/registration-operator:e2e -klusterlet-deploy-mode=Default
=== RUN   TestE2E
Running Suite: ocm E2E Suite - /Users/jiazhu/go/src/open-cluster-management.io/ocm
==================================================================================
Random Seed:<PHONE_NUMBER>

Will run 67 of 67 specs
------------------------------
[BeforeSuite]
/Users/jiazhu/go/src/open-cluster-management.io/ocm/test/e2e/e2e_suite_test.go:85
  STEP: Setup hub @ 12/09/24 21:32:45.333
  STEP: Setup spokeTestHelper @ 12/09/24 21:32:45.335
  STEP: Setup default bootstrap-hub-kubeconfig @ 12/09/24 21:32:45.336
  STEP: Check Hub Ready @ 12/09/24 21:32:45.341
  [FAILED] in [BeforeSuite] - /Users/jiazhu/go/src/open-cluster-management.io/ocm/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 @ 12/09/24 21:34:15.345
[BeforeSuite] [FAILED] [90.011 seconds]
[BeforeSuite]
/Users/jiazhu/go/src/open-cluster-management.io/ocm/test/e2e/e2e_suite_test.go:85

  [FAILED] Timed out after 90.001s.
  Expected success, but got an error:
      <*fmt.wrapError | 0x14000874780>:
      failed to check cluster manager status: HubPlacement is degraded
      {
          msg: "failed to check cluster manager status: HubPlacement is degraded",
          err: <*errors.errorString | 0x1400071d100>{
              s: "HubPlacement is degraded",
          },
      }
  In [BeforeSuite] at: /Users/jiazhu/go/src/open-cluster-management.io/ocm/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 @ 12/09/24 21:34:15.345
------------------------------
[AfterSuite]
/Users/jiazhu/go/src/open-cluster-management.io/ocm/test/e2e/e2e_suite_test.go:185
  STEP: clean klusterlet e2e-universal-klusterlet resources after the test case @ 12/09/24 21:34:15.346
[AfterSuite] PASSED [0.002 seconds]
------------------------------

Summarizing 1 Failure:
  [FAIL] [BeforeSuite]
  /Users/jiazhu/go/src/open-cluster-management.io/ocm/vendor/github.com/onsi/gomega/internal/async_assertion.go:145

Ran 0 of 67 Specs in 90.013 seconds
FAIL! -- A BeforeSuite node failed so all tests were skipped.

Environment ie: OCM version, Kubernetes version and provider:
ocm version: 02a202aa6a087b6880fe563c03f079afa7ac1722
Additional context
Add any other context about the problem here.

@dosubot when running the e2e test, we use the IMAGE_TAG=e2e make test-e2e command, the Makefile is https://github.com/open-cluster-management-io/ocm/blob/main/test/e2e-test.mk, is there any bug in the Makefile?

@dosubot deploy-hub-helm and deploy-spoke-operator-helm use image.tag=$(IMAGE_TAG) to set the image tag for deployments. But you have already said The tag is determined by checking if a value is provided in .Values.images.tag, so is there any bug?

@dosubot I think the image.tag=$(IMAGE_TAG) should be images.tag=$(IMAGE_TAG), since the Helm chart is using .Values.images.tag, WDYT?


Create devcontainer.json

added copilot extension
Summary

Changes

Closes:
Task list

[ ] For workflow changes, I have verified the Actions workflows function as expected.
[ ] For content changes, I have reviewed the style guide.

added for commit


Branch domain support

Feature request
Now that we can branch deploy through the cli #275 , how can we add a domain on the generated https://<branch>--<app name>.netlify.app/ ?

Apparently, it's not possible to do so: Setting Branch Subdomain for Manual Branch Deploys

My workaround for this right now is something like this:
  "scripts": {
    "deploy": "cross-env BRANCH=$(git symbolic-ref --short HEAD) USER=\"$(git config user.name)\" yarn deploy:branch",
    "deploy:branch": "cross-env-shell yarn build:quick && netlify deploy --dir dist --open --alias $BRANCH --message \"A new local branch deploy from branch $BRANCH by $USER.\"",
  },

So I just run yarn deploy in the command line to kick off a Netlify build that uses the current branch name as the alias.  It works ok, the problem that I'm noticing are the unpredictable URL's.
Some examples:

Alias
Result

feature-5345-cm-icon-picker
Not found

iconpicker
Not found

icon-picker
Successful

I have no idea why the first two don't work, but the last one with a dash in it worked just fine.  I haven't been able to figure out the pattern for what makes a successful URL.  I'm currently in contact with support, so I'll report back any findings. If anyone else has any ideas, please let me know!

I would also like to point my domain to the aliased branch deploy

adding a +1 for this as it would be a major help to our current workflow!

adding a +1 for this as it would be a major help to our current workflow!

We are also looking for support in this regard! We are using cli deploys because (1) we can check logs faster, (2) we can add additional checks in pipelines (e.g. Sonar scanning) and (3) we are migrating to Trunk Based Development, so we are using the main branch for development and we create separate release branches, all of the logic being handled inside GitHub Actions. Having custom domains in branch deploys (even just setting up some hardcoded ones manually is fine) would help a log.

Do we have any update on this request? Maybe if there has been any progress on the backend side at least? Not sure who to ping, @erezrokah @khendrikse

this would be great, we could also use this

+1 for this. My team moved to Netlify DNS for this feature but unexpected when it only apply to netlify.app domain (build then deploy with alias)

I think it is the most common feature request.


fixfix bug that query infomation_schema.rowsets fe send fragment to one of muilti be.

Fixed the bug of incomplete query results when querying information_schema.rowsets in the case of multiple BEs.
The reason is that the schema scanner sends the scan fragment to one of multiple bes, and be queries the information of fe through rpc. Since the rowsets information requires information about all BEs, the scan fragment needs to be sent to all BEs.
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


fix: Do not escape backticks & shell vars

But use single quotes for tag message in release_pr workflow.
Fixes: #63

Coverage remained the same at 97.15% when pulling f1b0b0db93c0f8e9669283b6daac29c14607bfdf on fix/63 into 543d8cfc9b0692b9f05e334c3c2a47add82c2c16 on master.


Using Wagmi to build walletConnect mobile phone scan code will crash back, what is the problem?

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
1.0.2
Current Behavior
Using Wagmi to build walletConnect mobile phone scan code will crash back, what is the problem?
Expected Behavior
No response
Steps To Reproduce
No response
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response

What do you mean by "crash back"? Can you please provide a minimal reproducible example via https://new.wagmi.sh, so we can help you?

“崩溃”是什么意思？您能否通过https://new.wagmi.sh提供一个最小的可重现示例，以便我们为您提供帮助？

It is the provided walletconnect example and I built it myself, the mobile wallet scan code will directly exit the wallet, and the desktop does not show that the login is successful.
This is the case both with the official example and with my own build, how to fix it, please?
Here's an example of walletconnect I built:

Can you upload your code please?

---------------------wagmiConfig.js:
import {
createConfig,
configureChains,
} from '@wagmi/core'
import { mainnet, optimism, polygon, arbitrumGoerli } from '@wagmi/core/chains'
import { publicProvider } from '@wagmi/core/providers/public'
import { alchemyProvider } from '@wagmi/core/providers/alchemy'
import { MetaMaskConnector } from '@wagmi/core/connectors/metaMask'
import { CoinbaseWalletConnector } from '@wagmi/core/connectors/coinbaseWallet'
import { WalletConnectConnector } from '@wagmi/core/connectors/walletConnect'
import { InjectedConnector } from '@wagmi/core'
const projectId = "624944ddf69f52071b35b4c4aa7f602f";
const alchemyId = 'oKMNBGBp_hvmPNKm1uNcDbqb32FxOGYP';
const { chains, publicClient, webSocketPublicClient } = configureChains(
[mainnet, optimism, polygon, arbitrumGoerli],
[alchemyProvider({ apiKey: alchemyId })],
)
export const wagmiConfig = createConfig({
autoConnect: true,
connectors: [
new MetaMaskConnector({ chains }),
new CoinbaseWalletConnector({
chains,
options: {
appName: 'owlto',
jsonRpcUrl:
'https://eth-mainnet.alchemyapi.io/v2/oKMNBGBp_hvmPNKm1uNcDbqb32FxOGYP',
},
}),
new WalletConnectConnector({
chains,
options: {
projectId: projectId,
showQrModal: true,
metadata: {
name: 'Owtlo',
description: 'Owlto Finance',
url: 'https://wagmi.sh',
icons: ['https://wagmi.sh/icon.png'],
},
},
}),
new InjectedConnector({
chains,
options: {
name: 'Injected',
shimDisconnect: true,
},
explorerRecommendedWalletIds: 'NONE'
}),
],
publicClient,
webSocketPublicClient,
})
-----Wagmi.vue

User ID：{{ userId }}

User Balance{{ balance }}

<button
  v-for="item in vagmiConfig.connectors"
  @click="test(item)"
  style="margin: 0 20px"
>
  {{ item.id }}
</button>

  <button @click="getBalance">getBalance</button>
  <button @click="sengValue">send</button>
  <button @click="changeNetWork">switchNetwork</button>

  <button @click="dis">disconnect</button>

This is my code, and I am using Vue3

This is my configuration file:
`import {
createConfig,
configureChains,
} from '@wagmi/core'
import { mainnet, optimism, polygon, arbitrumGoerli } from '@wagmi/core/chains'
import { publicProvider } from '@wagmi/core/providers/public'
import { alchemyProvider } from '@wagmi/core/providers/alchemy'
import { MetaMaskConnector } from '@wagmi/core/connectors/metaMask'
import { CoinbaseWalletConnector } from '@wagmi/core/connectors/coinbaseWallet'
import { WalletConnectConnector } from '@wagmi/core/connectors/walletConnect'
import { InjectedConnector } from '@wagmi/core'
const projectId = "624944ddf69f52071b35b4c4aa7f602f";
const alchemyId = 'oKMNBGBp_hvmPNKm1uNcDbqb32FxOGYP';
const { chains, publicClient, webSocketPublicClient } = configureChains(
[mainnet, optimism, polygon, arbitrumGoerli],
[alchemyProvider({ apiKey: alchemyId })],
)
export const wagmiConfig = createConfig({
autoConnect: true,
connectors: [
new MetaMaskConnector({ chains }),
new CoinbaseWalletConnector({
chains,
options: {
appName: 'owlto',
jsonRpcUrl:
'https://eth-mainnet.alchemyapi.io/v2/oKMNBGBp_hvmPNKm1uNcDbqb32FxOGYP',
},
}),
new WalletConnectConnector({
chains,
options: {
projectId: projectId,
showQrModal: true,
metadata: {
name: 'Owtlo',
description: 'Owlto Finance',
url: 'https://wagmi.sh',
icons: ['https://wagmi.sh/icon.png'],
},
},
}),
new InjectedConnector({
chains,
options: {
name: 'Injected',
shimDisconnect: true,
},
explorerRecommendedWalletIds: 'NONE'
}),
],
publicClient,
webSocketPublicClient,
})
The framework I am using is Vue3，Using the page：

User ID：{{ userId }}

User Balance{{ balance }}

<button
  v-for="item in wagmiConfig.connectors"
  @click="test(item)"
  style="margin: 0 20px"
>
  {{ item.id }}
</button>

  <button @click="getBalance">getBalance</button>
  <button @click="sengValue">send</button>
  <button @click="changeNetWork">switchNetwork</button>

  <button @click="dis">disconnect</button>

`

Please make a minimal reproducible example that is runnable (StackBlitz works great for this). Once that is ready, we can look into this issue more.


To Reproduce
Steps to reproduce the behavior:

Create a QnA KB with multiturn utterances.
Publish KB
run the command 'dispatch create' with the KB related
check the *.json file over utterances and will see that only parent QnA utterances were considered.

Expected behavior
Consider the child utterances.
Additional context
On the test over QnaMaker.ai is available interactions starting with a child utterance.
[bug]

@trojengui can you take a look at this

@RenanCarso, a couple questions for you:

Are you training and publishing your KB?
Are you running dispatch add before dispatch create?
Are you looking at the right .json file?

When I test this (with regards to QnA), I use the following commands and parameters. I then end up with a _Q_distribution.json file (based on my QnA kb of the same name) and an nlp-dispatch.json file. The "distribution" file contains the prompt(s) - the "displayText" represents the actual prompt; "questions" represents what the prompt is referencing; and, the "answer" is the returned value when the prompt is selected.
> dispatch add -t qna -i 6932XXXX-XXXX-XXXX-XXXX-XXXXXXXXb55a -n distribution -k 5b94XXXXXXXXXXXXXXXXXXXXXXXX4abf

> dispatch create

Test - QnAmaker.ai:

_Q_distribution.json:

Closing due to a lack of activity. Please feel free to reopen if the issue persists. Review the above responses and post any new information.

@stevkan, I'm really sorry for late response. Now I'll have proper time for caring this subject.
I've double checked all steps you suggested and no child multiturn utterances.
Actually, I tried the @tsuwandy suggestion and didn't worked as well.
If I check the data_Q_*.json, it is exactly as you related, with all the multiturn utterances, parent and child.
But if I check json file on the root folder, which is outside the data folder, you will see no child multiturn utterance. This json file reflects exactly the Luis KB created with dispatch process.
Commands that I'm running in order:

dispatch init -n DispatchKBPT --luisAuthoringKey "8892XXXXXXXXXXXXXXXXX836c" --luisAuthoringRegion westus
dispatch add -t luis -i 9a16XXXXXXXXXXXXXXXXXXXXX9ae3 -n "LuisKBase" -v 0.2 -k 8892XXXXXXXXXXXXXXXXX836c
dispatch add -t qna -i 532bXXXXXXXXXXXXXXXXXXXXX8919 -n QnaPersonalityPT -k 0cf7XXXXXXXXXXXXXXXXXXXX67cd
dispatch add -t qna -i 4ddbXXXXXXXXXXXXXXXXXXXXXXXXXXXX66e0 -n QnaPT -k 0cf7XXXXXXXXXXXXXXXXXXXX67cd --includePrompts true

Worth mention points:

there is also 1 Luis KB on this dispatch

my bot is in pt-BR

@stevkan could you please reopen this issue?

@RenanCarso, would you mind sharing your .dispatch file to<EMAIL_ADDRESS>so I could investigate?  Thanks!

Just sent it.

Thanks Renan, taking a look.

@RenanCarso, try starting a clean dispatch (in a different folder), and run these commands again:
dispatch init -n DispatchKBPT --luisAuthoringKey "8892XXXXXXXXXXXXXXXXX836c" --luisAuthoringRegion westus
dispatch add -t qna -i 4ddbXXXXXXXXXXXXXXXXXXXXXXXXXXXX66e0 -n QnaPT -k 0cf7XXXXXXXXXXXXXXXXXXXX67cd --includePrompts true
Check the updated .dispatch file.  Make sure the services element looks like the following (note the "includePrompts": true property for the QnaPT kb):
"services": [
{
"includePrompts": true,
"kbId": "4ddb36b3-e93d-4f16-b7c1-53ecb38566e0",
"subscriptionKey": "0cf7c2f1e345472cb4062cc3f2be67cd",
"type": "qna",
"name": "QnaPT",
"id": "1"
}
],
Add the other sources (might worth checking the .dispatch file just to make sure the QnaPT still has the "includePrompts" property).  Run the "dispatch create" command and check the resulting json or check the dispatch app on LUIS portal and see if the prompts are part of the utterances for the kb intent.

I am having a very similar issue. When I use "includePrompts", it includes ones with context-only enabled. We have many prompts that are simply "Yes" or "No" and dispatch can't detect the intent for those.
Is there an option to ignore prompts with the context-only flag?

@danielt113, we were not aware of context-only flag, thanks for bringing this up.  It makes complete sense to update Dispatch to ignore these prompts.  Will update this thread once I take a look and update the cli.

@danielt113, latest dispatch is published.  It’ll now ignore prompts with isContextOnly for QnA kb added with “—includePrompts true”

closing th


OpenGL renderer and backend-agnostic graphics subcrate

This PR implements an OpenGL renderer on top of glow, introduces a glutin shell, and abstracts a bunch of backend-agnostic rendering logic in a new graphics subcrate.
iced_glow
iced_glow is an OpenGL renderer powered by glow (GL on Whatever). This renderer is meant to be an alternative (not a replacement!) to iced_wgpu while wgpu and its ecosystem mature.
As iced_glow uses OpenGL, it should offer us better compatibility, stability, and maintainability for the time being. Furthermore, users that currently have OpenGL-based applications should be able to integrate them directly with iced.
On a related note, my work on this renderer also prompted me to write and open-source glow_glyph, a direct port of wgpu_glyph for glow.
Please, feel free to give the renderer a try by switching to the feature/glow-renderer branch and running any of the examples! Keep in mind that Image and Svg widgets are not supported yet.
iced_glutin
iced_glutin is a shell on top of glutin. It can be used to easily initialize OpenGL-based renderers, as it will create and properly configure an OpenGL context for them.
Given that glutin is built on top of winit itself, iced_winit and iced_glutin both share a good amount of logic. However, while iced_winit provides a raw-window-handle to initialize the chosen renderer, iced_glutin provides an OpenGL loader function instead.
The work on this crate also introduced a couple of new concepts in iced_native that should ease the integration of iced in existing projects (#313). Specifically, a Program trait has been added which can be used together with some program::State to feed events to a user interface and obtain its drawing primitives. The integration example has been updated accordingly to showcase how to use them!
iced_graphics
The first draft of iced_glow was implemented by copy-pasting a lot of code from iced_wgpu. As most of this code was backend-agnostic and shared between renderers, it was abstracted away and moved to an intermediate crate: iced_graphics.
iced_graphics contains a bunch of backend-agnostic types that can be leveraged to build a renderer. The most important concepts it contains are:

The current Primitive type from iced_wgpu.
A Layer type that flattens a Primitive tree for rendering.
A default renderer that can be customized with a generic backend. It implements the Renderer trait for all the built-in widgets.
Other useful types like Transformation, Viewport, a font loader on top of font-kit, etc.

And I think that's about it! I am aware there is a lot to unpack here. Once I finish writing the documentation for all the changes, I will share a link.
As always, any feedback appreciated and feel free to ask any questions!

Fixes #357
Fixes #350
Fixes #349
Fixes #342
Fixes #284
Fixes #257
Fixes #212
Fixes #194
Fixes #182
Fixes #148
Fixes #98
Fixes #96
Fixes #72
Fixes #70

The new documentation is available at https://iced-docs.now.sh/iced/index.html

I think this is ready to be merged!
The OpenGL renderer still does not support the Image and Svg widgets, but I believe we can tackle that in another PR. There are many foundational changes in this one and it's important we merge it so we can build on top of them.
Given that the OpenGL renderer isn't feature-complete yet, I have kept iced_wgpu as the default one. The iced_glow renderer can be toggled using the new glow feature flag.

Currently there is no way to create a glow renderer backend (as it is a pub(crate) export), is this intentional until things are more complete?

@draivin Not intentional. I forgot about exposing it 😅

@draivin I have exported it in https://github.com/hecrj/iced/commit/6cb90570a3af18b1a1ad455dc1ce5858f8446aa6.

Does this PR indicate that iced will slowly move away from using wgpu (and eventually not at all)?

@m4b
No, as the description says:

This renderer is meant to be an alternative (not a replacement!) to iced_wgpu while wgpu and its ecosystem mature.

Gosh, sorry I missed that, thanks for clarification :)

Are there any estimates on how hard it is to implement image support for OpenGL renderer? It's the only thing that prevents me from using iced on Raspberry Pi (see #428). With just a couple of shader hacks, everything else works fine.

@0x7CFE It shouldn't be hard to get a similar implementation to the iced_wgpu one.
However, we should try to abstract and move the atlas logic to iced_graphics instead of duplicating code. Additionally, it would be great to set the foundations for asynchronous loading of images at the same time.

@hecrj is there a tracking issue for Image and Svg support for the glow feature?
Also, could it be that the current master fails to compile with the glow feature? I'm getting lots of errors.

@hecrj is there a tracking issue for Image and Svg support for the glow feature?
Also, could it be that the current master fails to compile with the glow feature? I'm getting lots of errors.

Seconded. I would create an issue myself, but i feel like the OP of a tracking issue should contain all meaningful information, and it would be much better if you had control over that OP.


MINOR CHANGE - Add a check for CLI execution

Because php5-cli does not have HTTP_HOST set, this causes PHP error of type warning

:+1:


JSON standardization

This applies to both specified and specify, I'm putting it here. This change entails standardizing and cleaning up the Specify json.
TODO

[ ] Write a broad summary of the json, breaking it down into various parts and clarifying keys when needed. Units should be specified(mega, mebi and so on).
[x] On the specified side, convert WorkingSet to me(ga|bi)bytes and label in the viewer. Drives are also measured in bytes then converted specified side, so I feel this is fine.
[ ] Ensure all references to datetime and elapsed time are in Unix time, or decide on a standard to abide by (eg: 8601). This affects InstalledApps, startuptasks, possibly bios release date, DHCP info, and uptime
[ ] Remove redundant data from the JSON, or add a clarifying reason in the json doc explaining why it's needed (see ScheduledTasks Path and Name) for one instance

More can be added, this should be enough to start.

ISO 8601/DateTime object please


Add "IsActive" to connection type

Copied from: https://github.com/jamesmontemagno/Xamarin.Plugins/issues/255
Feature Request:
ConnectionTypes returns a list of active connections, but it would be nice to know which connection is being used for network calls... I'm not sure about other platforms, but for Windows you can get the connection that's being used by calling NetworkInformation.GetInternetConnectionProfile();
Can you either order the ConnectionTypes so that the first item is the connection being used or maybe add a new property... I guess this request could get tricky if Android and iOS don't support finding the connection being used.

There is the Reacability NuGet

+1 on this - the purpose of the ConnectionTypes property is slightly ambiguous - is it a list of all connections on the device? Or all active connections?
We want to know whether the network request will be sent over, say, 4G, wifi, or something else. Is it reliable to use the first item in the list?

I found that sometimes IsConnected is not sufficient because I want to be able to tell when the Wifi is turned on but not connected when not Wifi is in range. Without a "IsConnectedToWifi" method I can't tell if the device is connecting using the cellular network or the Wifi as both are turned on but only teh cellular is connected. To make things even worse, the IsReachable returns true if the Wifi is turned on but not connected as it automatically uses the cellular network instead... So unless the Wifi is manually turned off we can't tell if it is connected ?

When can we have a IsConneectedToWifi and IsConnectedToCellular methods please ? Or IsConnected(connectionType) with a parameter... ?

Or a IsReacchable method that has a useConnectionType parameter too so we know exactly if a site is reachable through Wifi or Cellular ?
Thanks!!!


add driver's config.map with default values to the assets created

/assign @coreydaley

/hold
while I manually try out my new no refresh resource e2e test

clusterbot version of this PR confirmed my fear / suspicion with library-go static resource controller
by static, it really means static, as it we cannot change the contents of the config map ... it switches back to the default
/close


scron desisim daily update OOM failures on perlmutter

Scrontab that runs the daily test fails at the desisim step with OOM, causing the entire job to crash before completing subsequent updates. Likely reason is that memory is limited to 4 GB on login nodes on which scrontab jobs run. The cpu limit (and probably corresponding memory limit) is set by the "cron" qos. Thanks @dmargala for helping investigate this.
Some possible solutions:

don't do desisim unit tests on perlmutter
modify desisim unit tests to use < 4 GB
increase the scrontab memory limit, if possible

I have implemented (1) above already at
/global/common/software/desi/users/desi/perlmutter/code/desitest/main/py/desitest/nersc.py

i.e.:
-            #- desisim-testdata & redrock-templates: data only, no tests
-            if repo in ['desisim-testdata', 'redrock-templates']:
+            if repo in ['desisim-testdata', 'desisim', 'redrock-templates']:
+            #- desisim-testdata, desisim & redrock-templates: data only, no tests

@sbailey please have a look and confirm that this solution makes sense for daily updates going forward (it would have the added benefit of speeding up the updates). If so, I can merge this change into main.

Another possible solution would be to submit a request for the "workflow" scrontab queue:
https://docs.nersc.gov/jobs/workflow/workflow-queue/

Jobs in the workflow queue may request a walltime of up to 90 days and up to one quarter of the resources (CPU and/or memory) of a Perlmutter login node.

That would get you up to 128 Gb of memory.

@marcelo-alvarez let's find a way to run these tests on Perlmutter instead of turning them off.  For the short term, let's try the workflow queue with 8 GB, and then file a ticket with desisim to track down what test(s) need so much memory and update them to use less memory.

The desisim unit tests are still producing OOM crashes in scrontab jobs, even with the workflow qos specified. Details below.
I obtained access for the workflow scrontab qos on perlmutter and preliminary results and scheduled the following scrontab to run as a test:
#
#- Scron job to run daily integration tests on perlmutter
#
#SCRON -A desi
#SCRON -q workflow
#SCRON -t 00:60:00
#SCRON -o ___/output-%j.out
#SCRON --open-mode=append
#SCRON --mail-type=ALL
#SCRON --mail-user=___
#SCRON --cpus-per-task=4
25 21 * * * /bin/bash -lc "source /global/common/software/desi/users/desi/perlmutter/code/desitest/main/etc/cron_dailyupdate.sh"

I believe the combination of setting -q workflow and --cpus-per-task=4 should have ensured there were 8 GB of memory available. However, it still crashes at the desisim unit test step with OOM errors, as indicated in an email message from<EMAIL_ADDRESS>Running
source /global/common/software/desi/users/desi/perlmutter/code/desitest/main/etc/cron_dailyupdate.sh

on a perlmutter login node as the desi user succeeds, and profiling individual unit test commands for each update with Arm (i.e. with modified commands
'perf-report -o $SCRATCH/dailyupdatetest/{}.txt python setup.py test'.format(repo)

in desitest.nersc.update for repo in desiutil, specter, etc.) indicates desisim uses only ~3 GB of memory (see the 'profiling summary' text copied below), which is less than the 8 GB that should have been available for the scrontab job with -q workflow and --cpus-per-task=4 set.
From these two tests above (same script from either a scrontab with -q workflow and --cpus-per-task=4 set or instead source d from a login node), it's not clear that it's just a memory limit issue. It is possible it is something specific to desisim unit tests on a scrontab job that would happen even if there was no memory limit at all. I have also found that OOM errors occur even when the scrontab runs only cd .../desisim/main; python setup.py test.

profiling summary:
desiutil:     646   MiB
specter:      1.09  GiB
gpu_specter:  2.43  GiB
desimodel:    890   MiB
desitarget:   1.23  GiB
desispec:     1005  MiB
specsim:      131   MiB
desisim:      2.86  GiB
desisurvey:   790   MiB
surveysim:    565   MiB
redrock:      448   MiB

After an overhaul of how desitest is run nightly at Perlmutter, desisim tests are now running on Perlmutter with no memory failures, so this issue has been resolved.


Always VIP Pool will not maintain anymore, it should be removed

Close with : https://github.com/Charlie85270/conflux-pos-pools/commit/450aed00c0d8cc14264b8beb6743fe52df38019e


bug: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: org.eclipse.lsp...

IDE Information
GoLand 2024.2.3
Build #GO-242.23339.24, built on September 26, 2024
Licensed to Michael Henderson
Subscription is active until January 31, 2025.
Runtime version: 21.0.4+13-b509.17 aarch64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.lwawt.macosx.LWCToolkit
macOS 14.6.1
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 16000M
Cores: 10
Metal Rendering is ON
Registry:
ide.completion.variant.limit=500
suggest.all.run.configurations.from.context=true
ide.experimental.ui=true
i18n.locale=
terminal.new.ui=true
Non-Bundled Plugins:
org.asciidoctor.intellij.asciidoc (0.43.1)
com.sourcegraph.jetbrains (7.0.6)
com.intellij.tailwindcss (242.20224.204)
Bug Description
Moved a file to a new folder in the IDE
Additional context
Stacktrace:
java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: codeActions/provide: document not found for file:///Users/wraith/JetBrains/tribenet/ottoweb/components/app/pages/settings/settings.gohtml

Error: codeActions/provide: document not found for file:///Users/wraith/JetBrains/tribenet/ottoweb/components/app/pages/settings/settings.gohtml
    at /Users/wraith/Library/Application Support/JetBrains/GoLand2024.2/plugins/Sourcegraph/agent/index.js:128784:19
    at /Users/wraith/Library/Application Support/JetBrains/GoLand2024.2/plugins/Sourcegraph/agent/index.js:129744:18
    at async /Users/wraith/Library/Application Support/JetBrains/GoLand2024.2/plugins/Sourcegraph/agent/index.js:128268:44
	at com.intellij.util.ExceptionUtil.rethrow(ExceptionUtil.java:136)
	at com.intellij.openapi.progress.util.ProgressIndicatorUtils.awaitWithCheckCanceled(ProgressIndicatorUtils.java:399)
	at com.sourcegraph.cody.inspections.CodyFixHighlightPass.doCollectInformation(CodyFixHighlightPass.kt:104)
	at com.intellij.codeHighlighting.TextEditorHighlightingPass.collectInformation(TextEditorHighlightingPass.java:67)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.lambda$doRun$2(PassExecutorService.java:431)
	at com.intellij.platform.diagnostic.telemetry.helpers.TraceKt.runWithSpanIgnoreThrows(trace.kt:118)
	at com.intellij.platform.diagnostic.telemetry.helpers.TraceUtil.runWithSpanThrows(TraceUtil.java:36)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.lambda$doRun$3(PassExecutorService.java:426)
	at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.tryRunReadAction(AnyThreadWriteThreadingSupport.kt:291)
	at com.intellij.openapi.application.impl.ApplicationImpl.tryRunReadAction(ApplicationImpl.java:965)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.lambda$doRun$4(PassExecutorService.java:417)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$13(CoreProgressManager.java:660)
	at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:735)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:691)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:659)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:79)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.doRun(PassExecutorService.java:416)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.lambda$run$0(PassExecutorService.java:392)
	at com.intellij.openapi.fileTypes.impl.FileTypeManagerImpl.cacheFileTypesInside(FileTypeManagerImpl.java:802)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.lambda$run$1(PassExecutorService.java:392)
	at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.executeByImpatientReader(AnyThreadWriteThreadingSupport.kt:486)
	at com.intellij.openapi.application.impl.ApplicationImpl.executeByImpatientReader(ApplicationImpl.java:178)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.run(PassExecutorService.java:390)
	at com.intellij.concurrency.JobLauncherImpl$VoidForkJoinTask$1.exec(JobLauncherImpl.java:259)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:507)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1491)
	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:2073)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:2035)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:187)
Caused by: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: codeActions/provide: document not found for file:///Users/wraith/JetBrains/tribenet/ottoweb/components/app/pages/settings/settings.gohtml

Error: codeActions/provide: document not found for file:///Users/wraith/JetBrains/tribenet/ottoweb/components/app/pages/settings/settings.gohtml
    at /Users/wraith/Library/Application Support/JetBrains/GoLand2024.2/plugins/Sourcegraph/agent/index.js:128784:19
    at /Users/wraith/Library/Application Support/JetBrains/GoLand2024.2/plugins/Sourcegraph/agent/index.js:129744:18
    at async /Users/wraith/Library/Application Support/JetBrains/GoLand2024.2/plugins/Sourcegraph/agent/index.js:128268:44
	at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2096)
	at com.intellij.openapi.progress.util.ProgressIndicatorUtils.awaitWithCheckCanceled(ProgressIndicatorUtils.java:370)
	... 27 more
Caused by: java.util.concurrent.ExecutionException: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: codeActions/provide: document not found for file:///Users/wraith/JetBrains/tribenet/ottoweb/components/app/pages/settings/settings.gohtml

Error: codeActions/provide: document not found for file:///Users/wraith/JetBrains/tribenet/ottoweb/components/app/pages/settings/settings.gohtml
    at /Users/wraith/Library/Application Support/JetBrains/GoLand2024.2/plugins/Sourcegraph/agent/index.js:128784:19
    at /Users/wraith/Library/Application Support/JetBrains/GoLand2024.2/plugins/Sourcegraph/agent/index.js:129744:18
    at async /Users/wraith/Library/Application Support/JetBrains/GoLand2024.2/plugins/Sourcegraph/agent/index.js:128268:44
	at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073)
	at com.sourcegraph.cody.inspections.CodyFixHighlightPass.doCollect...

Hi there 👋 sorry for the inconvenience 🙇 we know about that problem and we fixed it already!
The original issue: https://github.com/sourcegraph/jetbrains/issues/2512
The fix: https://github.com/sourcegraph/jetbrains/pull/2539
The fix will be included in the next release. The next release should be available next week.
I kindly ask you for some more patience 🙏


Using [NotNull] and 'nameof' operator

Hi @hishamco, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

:shipit:
@Tratcher can you merge?

Merged.


Copy content dir to user writable dir

In order to avoid permission problems when importing, the content and log should not be written to the program dir, but a dir, where the user has write permissions.
On Windows that would be:
%appdata%\Valkyrie
Reading them as Resources or copying them over should be fine though.

Yep, this is in the long term plan.


Update DEE31A and 31B

Addresses #7641

Updated names and synonyms to represent new medical understanding of DEE31 as DEE31A
Updated definitions for 31A and 31B from OMIM. Included my ORCID and OMIM as annotations
Included broad and exact synonyms, along with ORCID and OMIM annotations for these

@yshwetar please assign this back to me when you have made the edits, thanks!

thanks for addressing all of the comments @yshwetar.
I added the term tracker item to these two terms. This can be merged after QC passes


Which year is implied when given just a month and day? Next and last?

There may have already been a discussion about this but I was a bit curious about how the year should be determined when given only a month and a day. This may be an interesting discussion topic for all users even if you're not familiar with the code.
For instance, let's say that today, June 12, 2015 I make a reference to June 10. I'm probably talking about two days ago but parsedatetime assumes I'm looking ahead to 2016.
Current behavior
Given the source date June 12, 2015, parsedatetime will produce the following dates when parsing the text shown in gray:

June 11: June 11, 2016
June 12: June 12, 2015
June 13: June 13, 2015
next June 11: June 11, 2017
next June 12: June 12, 2016
next June 13: June 13, 2016
last June 11: June 11, 2015
last June 12: June 12, 2014
last June 13: June 13, 2014

The logic considers the 365±1 day period beginning today to be my frame of reference. It's not wrong since the behavior can be documented and understood easily, but it may not be expected.
What is expected?
Given the source date June 12, 2015, I think that the following would be expected:

June 11: June 11, 2015
June 12: June 12, 2015
June 13: June 13, 2015
next June 11: June 11, 2016
next June 12: June 12, 2016
next June 13: June 13, 2016
last June 11: June 11, 2014
last June 12: June 12, 2014
last June 13: June 13, 2014

This logic considers the current Jan 1–Dec 31 period to be my frame of reference. "Next" means the date is in the upcoming year, "last" means the date is in the preceding year, and the omission of both suggests that the date is in the current year.
End of the year
The example above is oversimplified as it considers only today, tomorrow, and yesterday. I don't think it's necessarily as simple as requiring "next" to refer to dates in the following year. If today is December 28 and I want to refer to January 4, I would probably not say next January 4; it's just a couple days away.
Any good ideas for how to handle that? For example, if the date is within ±90 days of today then use it regardless of the year, otherwise assume the date is in the current year. I am afraid that crossing over the new year like that would be more error prone and difficult to understand. There is a fine line here between striving for the most likely natural language interpretation and employing logic that is stable and easy to understand.
Other considerations

If we agree that the current implementation is unexpected, how much work would it be to change the frame of reference like this?
Which other phrases would this change affect? For example:

June: June, 2015 rather than June, 2016
next May: May, 2016 rather than May, 2017

Would this badly affect backwards compatibility for your particular use case? This would probably require a major version update.

That behaviour is done for reason - the first use case for parsedatetime was to allow phrases in the Chandler project's calendar input. The vast majority of dates entered for that use case are future.
But you also need to know that this is already considered by the code - there is a set of flags that alter how next/last work with missing values - see https://github.com/bear/parsedatetime/blob/master/parsedatetime/init.py#L2140 for the one that covers a year value.
YearParseStyle, DOWParseStyle and CurrentDOWParseStyle
An example of usage can be found https://github.com/bear/parsedatetime/blob/master/parsedatetime/tests/TestFrenchLocale.py#L71

Oh, that's excellent! I had not taken a close enough look at Constants to discover the existing ability to configure this exactly how I described above.
So to wrap this up for anyone desiring to tweak this behavior, here is an example setup for parsing past and future dates relative to the current calendar year:
import parsedatetime as pdt
con = pdt.Constants()

# When a year is not specified, assume the current year regardless
# of whether the date is before or after today
con.YearParseStyle = 0

# When given a day of week that is earlier than today
# (e.g. *Monday* when today is Tuesday), assume that day
# refers to the current week rather than the following week.
con.DOWParseStyle = 0

# When given a day of week matching today, parse as today's
# date rather than one week later.
con.CurrentDOWParseStyle = 0

cal = pdt.Calendar(con)

cal.parse(...)

The source code has more complete documentation for those options; each supports 1 (the default), 0, and -1. In general, use cases where future dates are entered will prefer the default option while other cases may prefer 0. There are probably some specialized use cases for -1 but that one is probably less common.


Added configurable thread counts and post sizing

As requested per @Skunnyk (dbpedia-spotlight#3) , I've moved this change set here for PR.
It adds three runtime parameters:

threads.max to regulate how many threads the server can utilize (default: 5)
threads.core to define how many threads the server starts with (default: 5)
post.size.max to define the maximum POST-request payload size (default: 2097152 aka 2MB)

They can be tacked on at execution like so:
java -Xmx14G -Dthreads.max=10 -Dthreads.core=10 -Dpost.size.max=10485760 -jar ...

Hi @kfitzgerald ,
Thanks for this contribution. Merged!


Moderation 2: people report bad posts and a mechanism for moderators to receive reports

As part of #489
Requirements

Have a contract method to report bad post, can be called by any user
Have a frontend icon on each post to call the report bad post method, visible and can be used by any user
Notify all moderators when the report bad post is called, with the info: who reported which post

A possible technical approach
There should be a new type of action added in smart contract, we can it report_post. Technically it's similar to the implementation of like_post, and store post flagged by certain user at certain timestamp on smart contract. And instead of notification to the author, it notifies moderators, which is update all moderators SocialDB entry of notification. And also update notification type to display notification of "Post Reported" type properly on gateway

Close as we going to apply SocialDB + indexer based approach


tridentctl: better kubectl output parsing

Trident: 21.10.0
$ /tmp/trident-installer/./tridentctl -n sys-trident version
Error: invalid character 'I' looking for beginning of value

Probably want to parse stderr separately:
$ kubectl --context exp-1-merit -n sys-trident get pod
I1104 09:12:07.428631  234537 request.go:665] Waited for 1.084555807s due to client-side throttling, not priority and fairness, request: GET:https://lb.master.exp-1.merit.uw.systems/apis/cert-manager.io/v1beta1?timeout=32s
NAME                           READY   STATUS    RESTARTS   AGE
trident-csi-2ccp7              2/2     Running   0          26d
trident-csi-556b9cb7cb-9d8hc   6/6     Running   0          8d
trident-csi-5xqts              2/2     Running   0          13d

$ kubectl --context exp-1-merit -n sys-trident get pod 2>/dev/null
NAME                           READY   STATUS    RESTARTS   AGE
trident-csi-2ccp7              2/2     Running   0          26d
trident-csi-556b9cb7cb-9d8hc   6/6     Running   0          8d
trident-csi-5xqts              2/2     Running   0          13d

It's probably easier to recognize such I/W/E#### messages in the parser and drop them, then it is to change the I/O channel reading, or in java terms: if(!line.matches("^[IWE]\d+") { parse; }

This issue is fixed in commit bc247fb and will be included in the Trident 22.07 release.


Help: CustomThrottle not use. Why?

Look

New file

<?php

namespace App\Http\Middleware;

use Illuminate\Container\Container;

use Dingo\Api\Http\RateLimit\Throttle\Throttle;

class CustomThrottle extends Throttle

{

    protected $enabled;

    public function __construct(array $options = ['limit' => 13, 'expires' => 60], $enabled = true)

    {

        $this->enabled = $enabled;

        parent::__construct($options);

    }

    public function match(Container $app)

    {
        return $this->enabled;

    }

}

Config

    /*
    |--------------------------------------------------------------------------
    | Throttling / Rate Limiting
    |--------------------------------------------------------------------------
    |
    | Consumers of your API can be limited to the amount of requests they can
    | make. You can create your own throttles or simply change the default
    | throttles.
    |
    */
    'throttling' => [

        'default' => new App\Http\Middleware\CustomThrottle(['limit' => 200, 'expires' => 10])
    ],

My router

$api = app('Dingo\Api\Routing\Router');

$api->version('v1', function ($api) {

    $api->get('hello', 'App\Http\Controllers\Api\HomeController@index');

    $api->post('register', 'App\Http\Controllers\Auth\ApiAuthController@register');

    $api->post('login', 'App\Http\Controllers\Auth\ApiAuthController@authenticate');

    $api->post('logout', 'App\Http\Controllers\Auth\ApiAuthController@logout');

    /*
     * Protected API route with JWT (must be logged in) throttle:60,1
     */
    $api->group(['middleware' => 'api.throttle', 'limit' => 120, 'expires' => 5], function ($api) {

        $api->get('authenticated', 'App\Http\Controllers\Api\UsersController@authenticated');

        $api->get('token', 'App\Http\Controllers\Api\UsersController@refreshToken');

    });

});

Not use CustomThrottle. Why?

Dingo will look for throttles in the following order...

A throttle instance defined on the route itself.
Route specific throttling, i.e., the limit and expires options being set on the route.
Matching any of the registered throttles.

So, in your case, you have route specific throttlting defined on the group which is set on each of the routes, so it's never using the custom throttle you defined.
If you wish to override the route specific stuff on a per-route basis you can...
$api->get('token', ['throttle' => 'App\Http\Middleware\CustomThrottle', 'uses' => 'App\Http\Controllers\Api\UsersController@refreshToken']);


Typescript issue

Can't get this working with typescript, it says:
node_modules/react-native-tab-view/lib/typescript/src/SceneMap.d.ts:4:8 - error TS2339: Property 'route' does not exist on type '{}'.

4 }): ({ route, jumpTo, position }: T) => JSX.Element;
         ~~~~~

node_modules/react-native-tab-view/lib/typescript/src/SceneMap.d.ts:4:15 - error TS2339: Property 'jumpTo' does not exist on type '{}'.

4 }): ({ route, jumpTo, position }: T) => JSX.Element;
                ~~~~~~

node_modules/react-native-tab-view/lib/typescript/src/SceneMap.d.ts:4:23 - error TS2339: Property 'position' does not exist on type '{}'.

4 }): ({ route, jumpTo, position }: T) => JSX.Element;
                        ~~~~~~~~

Got it too. The problem is here: https://github.com/react-native-community/react-native-tab-view/blob/master/src/SceneMap.tsx#L12 { route, jumpTo, position } should be present in parent of T

repro:
git clone git@github.com:react-native-community/react-native-tab-view.git
npm ci
npm run typescript

Found 7 errors.

@punksta that's not how you setup this repo. anyway the op's issue seems to be with updated typescript.

I can confirm I've got the same issue<EMAIL_ADDRESS>typescript@3.9.7).
After bumping react-native-tab-view to 2.15.0, the errors were solved.


v0.2 release notes

Whenever we cut a new release we need to write a list of the new features. I also forget what all the new features are by that time. We should keep a running list of new features in this "issue". Whenever you fix a bug or add a feature, just mention it here and when we cut the release we'll include what your write in the release notes. I'll start with a couple of points.

Generalized the InteractionTensor class to handle arbitrary marginals. Now called PolynomialTensor.
Added a data structure for manipulating Majoranas called QuadraticHamiltonian

Ryan, I edited your comment because QuadraticHamiltonian uses Majoranas only internally, in contrast with my original plans that I discussed with you.

Fixed a bug in jordan_wigner_sparse where Pauli-Z strings of the Jordan-Wigner Transform were placed on higher indices rather than lower.
Added code to obtain arbitrary eigenstates of quadratic Hamiltonians (a.k.a. fermionic Gaussian states) and circuits to prepare them.


Fix some install package errors.

Coverage decreased (-0.02%) to 62.961% when pulling 4705083ee13b3827175502ac7b68c67bd3bc2e9f on reyoung:release/v0.9.0 into 82fafb7ce9991c164b58c1373dad7102a61b1ab4 on baidu:release/v0.9.0.


Add dockerfile for CI runner

Builds two different images: morpheus-ci-driver and morpheus-ci-test.
The driver image is 15.9GB and the test image is 14.2GB.
In this setup only the wheel is transferred from the build to the test and documentation stages(#112).
Base image contains:

Pre-populated conda env
libnuma1

Driver image contains:

libnvidia-compute-495
ibcublas-dev-11-5
libcufft-dev-11-5
libcurand-dev-11-5
libcusolver-dev-11-5

Test image contains

pytest-kafka
Kafka
openjdk-11 (needed for kafka)
nodejs
npm
camouflage

fixed #112
fixes #400

@gpucibot merge


Using Anthropic's Claude 3 rather than OpenAI's GPT models

How can I use Anthropic's Claude 3 rather than OpenAI's GPT models? I think, giving this is an open source project, you must have this flexibility of modifying ai calls. So please lemme know how can we do that. Which file I have to change to accommodate the Anthropic.

from langchain_anthropic import ChatAnthropic
u need to define the llm :
anthropic_llm = ChatAnthropic(model=modelnameifllmuwannause)
then u need to add llm Parameter to each agent what is equal anthropic_llm
KK Water @.***> schrieb am Di., 11. Juni 2024, 04:35:

How can I use Anthropic's Claude 3 rather than OpenAI's GPT models? I
think, giving this is an open source project, you must have this
flexibility of modifying ai calls. So please lemme know how can we do that.
Which file I have to change to accommodate the Anthropic.
—
Reply to this email directly, view it on GitHub
https://github.com/joaomdmoura/crewAI/issues/752, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANTFTIHAA6RNXENZZCU336LZGZO5RAVCNFSM6AAAAABJDM3T4WVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM2DKMRTHE3TKNY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

thanks a lot


Doesn't support "baseUrl" in tsconfig.json when tsconfig.json is in a different folder

Codesandbox: https://codesandbox.io/p/sandbox/dazzling-smoke-njhyww
I'm using "baseUrl": "src" so that I can resolve absolute imports in TS relative to baseUrl.
import from 'bar/bar' should resolve to ./src/bar/bar
Skott doesn't resolve the import to bar.ts:

Even though it's imported from foo.ts and Typescript works correctly with this setup.

Inveestigated some more:
It works correctly when tsconfig.json is in the same folder as my working dir when running Skott.
But it doesn't work when tsconfig is in a different folder.
baseUrl should be resolved relative to tsconfig.json

With this config:

With a subfolder:

Hey @grumd, nice catch, thanks for opening that issue with that complete repro.
I just checked and I believe your analysis is on point, paths only relying on "baseUrl" won't be resolved correctly when the tsconfig is not located in the working directory where the analysis was started from.
I'm currently on vacations so pushing an immediate fix (as I love to do) will be hard for me, but I started a little bit to think about it and implement a fix for it, it will most likely take into account the location of the provided tsconfig file to resolve these absolute module imports to reproduce the same behaviour as if the analysis was started from the current working directory.
Please also note that it's a specific case where only "baseUrl" is provided without plain path aliases (via "paths" property).
I'll keep you updated here in that issue. If you ever encounter other  issues feel free to share them as well :)

This was auto-closed, @grumd I'll let please you confirm that this works in 0.28.2 before closing the issue

Just in case retested it and seems to work correctly now! Thanks!

Thanks for confirming that @grumd but also for raising the issue!


Stable Release 2.1

How do we feel about current Dev being released as stable, in the near future?
Anyone have bugs but havent reported it ?

I've been heavily testing it myself for the past week or so and haven't found any major issues, but i should know within the next few days once i'm able to release a beta, how things are going.
Any possibility of adding a function similar to Homie_setFirmware for the interval, say, Homie_setStatsInterval to allows configuring initial interval in the setup function?
I did see you added the ability in the config file, just wasn't sure if Homie would read incremental config.json from spiff or not ... as I do still want to use the Web UI setup (interval not necessary to set in web UI)

Who wants to help write up some release notes?

The documentation is in a very good state so there is no need for long release notes.
So I would just write that the beta has been proven as stable and there is more exciting stuff to come with releases 2.1 and 3.0.
The most important new features have already been summarized in the release notes for beta.1, so they can be used as base for the release notes.
What do you think about some small "press release", so Homie-ESP8266 may get some advertisement? Such a release could be send to some maker magezine / technical news portals!?

Hi @timpur!
Great to see that you are going to release Homie-ESP8266 2.0 as a stable version!
One question though, is this (https://github.com/marvinroger/homie-esp8266/issues/485) problem fixed in the 2.0 branch? I know that you have fixed it in your 2.1 branch, but is there any option to backport it to the 2.0 branch?
For new and inexperienced users using the web ui to configure the device is a much more pleasant experiencience and we should offer it as an option. Every documentation page talks about this method and was the prefered one, so please, keep it in the 2.0 stable version :pray:
Thanks you so much for your work!

I think you have a good point there actually, I think I will merge the bug fixes (that make sense) back to 2.0

I shall do these things over the week and, we should be ready this weekend.

Awesome! Thanks for taking my comment into account :+1:
I will help debugging before the final release, keep up with the good job!

merged some issues #501 back to 2.0 from 2.1
@bodiroga can you check the CORS issue #446
@Gulaschcowboy can you test #477
Thanks guys.

Hi @timpur!
I have deleted the previously installed homie-esp-2.1 library, downloaded the "develop" branch as a .zip file, imported it to my Arduino IDE, reflashed the NodeMCU and... it works! The configuration page make its job, so I can confirm that the CORS issue is resolved :+1:
Thank you so much for the effort!

Thank you for testing :)

Good morning again @timpur!
This is not very important, but I'm not sure if you could clean the different warning messages that appear in the compilation stage before the final version. It is just an aesthetic thing, nothing serious :wink:
Here you have what I get when compiling a Homie sketch:

/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie.cpp: In constructor 'HomieInternals::HomieClass::HomieClass()':
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie.cpp:13:30: warning: 'BUILTIN_LED' is deprecated (declared at /home/aitor/.arduino15/packages/esp8266/hardware/esp8266/2.4.1/variants/nodemcu/../generic/common.h:78) [-Wdeprecated-declarations]
Interface::get().led.pin = BUILTIN_LED;
^
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Logger.cpp: In member function 'virtual size_t HomieInternals::Logger::write(uint8_t)':
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Logger.cpp:20:1: warning: no return statement in function returning non-void [-Wreturn-type]
}
^
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Logger.cpp: In member function 'virtual size_t HomieInternals::Logger::write(const uint8_t*, size_t)':
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Logger.cpp:24:1: warning: no return statement in function returning non-void [-Wreturn-type]
}
^
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Timer.cpp: In member function 'uint32_t HomieInternals::Timer::getInterval()':
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Timer.cpp:20:12: warning: statement has no effect [-Wunused-value]
_interval;
^
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Timer.cpp:21:1: warning: no return statement in function returning non-void [-Wreturn-type]
}
^
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Boot/BootConfig.cpp: In member function 'void HomieInternals::BootConfig::_proxyHttpRequest(AsyncWebServerRequest*)':
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Boot/BootConfig.cpp:285:40: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < request->headers(); i++) {
^
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Boot/BootConfig.cpp: In member function 'void HomieInternals::BootConfig::_onDeviceInfoRequest(AsyncWebServerRequest*)':
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Boot/BootConfig.cpp:339:32: warning: comparison with string literal results in unspecified behaviour [-Waddress]
if (iSetting->getType() != "unknown") {
^
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Boot/BootConfig.cpp: In static member function 'static void HomieInternals::BootConfig::__parsePost(AsyncWebServerRequest*, uint8_t*, size_t, size_t, size_t)':
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Boot/BootConfig.cpp:425:41: warning: pointer of type 'void ' used in arithmetic [-Wpointer-arith]
void buff = request->_tempObject + index;
^
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Boot/BootConfig.cpp:428:43: warning: pointer of type 'void ' used in arithmetic [-Wpointer-arith]
void buff = request->_tempObject + total;
^
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Boot/BootConfig.cpp: At global scope:
/home/aitor/Arduino/libraries/homie-esp8266-develop/src/Homie/Boot/BootConfig.cpp:433:21: warning: 'const String ConfigJSONError(String)' defined but not used [-Wunused-function]
static const String ConfigJSONError(const String error) {

Low priority feature request, take your time! Thank you!

@bodiroga  can you test my dev branch for warnings ?

Perfect @timpur, no more warning messages! You are really fast!

Again thanks for testing.

@bodiroga could we close this issue?


Formatting date in input field

Question:  I'd like to use the datetimepicker with an associated input field.  This all works fine, except the date that displays in the input field is the full date, time, timezone, etc, format.  (I'm assuming this is just because ngModel is a js date object?)  Since you can't use a filter on an input field (short of writing a special directive to do it), is there a way to format the date display within the datetimepicker directive so that I can control how it looks on an input field?   thanks!

This is closed but you said you were looking for feedback - and angular-date-time-input seems to be working beautifully for me so far!  Thank you!


TypeScript worker fails to compile with Angular 5.2.0

Loading a .js worker loads and works well in my TypeScript Angular project.
import Worker = require('worker-loader!./worker.js');
But I can't get the example .ts file working:
webpack: Failed to compile.
Unfortunately there's no more info with the error. Any ideas where I've gone wrong?

I'm facing the same issue - any news @TerryHibbert ?

From the issue template:

IMPORTANT! You should use Stack Overflow for support related questions.

Give that or the webpack gitter a shot folks: https://gitter.im/webpack/webpack

having the same issue with angular 7.xx


RecursionError when using discover() on SQL tables with circular references

Reposting from: https://github.com/blaze/datashape/issues/226

Continuing the conversation...
Yes follow_fkey=False would be a valid solution for this case. Although, the user would need to know that there is a circular reference among the tables in order to set the flag beforehand, right? what would happen in a non-trivial production database with dozens of tables where the cycle might not be so clear? It would be hard for the user to know which tables are affected. They will also lose all the fkey information for other tables by setting follow_fkey=False.
Anyway, sorry I can't provide a solution myself. follow_fkey=False seems like a reasonable approach.
Thanks


Convert line_number to int, fixes #105

Hmm, it also looks like the line numbers obtained from the Javascript Console are 1-based, so maybe the + 1 should be removed, but I don't know if there are other uses of the open_script_and_focus_line_callback function that pass 0-based line numbers...


Update CHANGELOG

Description

Added a date for v2 release
Tried to do some MakeAChangelog like style for the entries

Motivation and Context

Cleaning up the Changelog
How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Trivial change (affects only documentation or cleanup)

Checklist:

[ ] I have tested this change with a run of GEOSgcm (if non-trivial)
[X] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[X] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

A query for @tclune and @bena-nasa. The Keep a Changelog style does have a "Deprecated" section. Should we add anything as now "Deprecated" with MAPL 2.0?


New build errors?

Hello,
I have had Squido up and running for a few months now. Recently I'm seeing the build action fail due to new errors. I can't quite tell where the error exists, Squido or Azure DevOps. I haven't changed anything except adding new markdown blog posts.
If you see something that would tell where the issue is occurring, please let me know.
Stack:

Source: Azure DevOps Repo
Build: Github Action
Hosting: Azure Static Web App

Error when building:
...

Using Npm version:
6.14.15

Running 'npm install --unsafe-perm'...

npm WARN deprecated<EMAIL_ADDRESS>flatten is deprecated in favor of utility frameworks such as lodash.

><EMAIL_ADDRESS>postinstall /working_dir/node_modules/esbuild
> node install.js

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.
added 418 packages from 343 contributors and audited 419 packages in 30.168s

45 packages are looking for funding
  run `npm fund` for details

found 1 moderate severity vulnerability
  run `npm audit fix` to fix them, or `npm audit` for details

Running 'npm run build'...

><EMAIL_ADDRESS>build /working_dir
> squido build -c

Cleaned: /working_dir/build
[Building environment: development]
(node:275) UnhandledPromiseRejectionWarning: Error: Input data should be a String
    at MarkdownIt.parse (/working_dir/node_modules/markdown-it/lib/index.js:519:11)
    at MarkdownIt.render (/working_dir/node_modules/markdown-it/lib/index.js:544:36)
    at getMeta (/working_dir/node_modules/squido/lib/common.js:42:26)
    at compilePosts (/working_dir/node_modules/squido/lib/source.js:20:28)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async runBuild (/working_dir/node_modules/squido/cli.js:185:5)
    at async Command.<anonymous> (/working_dir/node_modules/squido/cli.js:51:9)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:275) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:275) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Preparing output...

Copying files to destination directory '/ss-oryx/app'...
Done in 1 sec(s).

Removing existing manifest file
Creating a manifest file...
Manifest file created.

Done in 35 sec(s).
...

Interesting note...

I receive the above error when adding a new blogpost.md.
I receive the below message when removing the blogpost.md

...

Using Node version:
v14.18.3

Using Npm version:
6.14.15

Running 'npm install --unsafe-perm'...

npm WARN deprecated<EMAIL_ADDRESS>flatten is deprecated in favor of utility frameworks such as lodash.

><EMAIL_ADDRESS>postinstall /working_dir/node_modules/esbuild
> node install.js

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.

added 418 packages from 343 contributors and audited 419 packages in 31.192s

45 packages are looking for funding
  run `npm fund` for details

found 1 moderate severity vulnerability
  run `npm audit fix` to fix them, or `npm audit` for details

Running 'npm run build'...

><EMAIL_ADDRESS>build /working_dir
> squido build -c

Cleaned: /working_dir/build
[Building environment: development]
Built: /working_dir/build/powertrip-1/index.html
Built: /working_dir/build/about/index.html
...
Copied: /working_dir/build/404.ejs
Copied: /working_dir/build/index.ejs
Copied: /working_dir/build/package.json
Copied: /working_dir/build/page.ejs
Copied: /working_dir/build/post.ejs
Copied: /working_dir/build/robots.txt
Copied: /working_dir/build/tag.ejs
...
Minified: /working_dir/build/content/javascripts/site.min.js
Minified: /working_dir/build/content/stylesheets/style.min.css
Built: /working_dir/build/sitemap.xml
Built: /working_dir/build/rss
Built: /working_dir/build/atom
Built: /working_dir/build/json
[Build complete]
Preparing output...

Copying files to destination directory '/ss-oryx/app'...
Done in 2 sec(s).

Removing existing manifest file
Creating a manifest file...
Manifest file created.

Done in 38 sec(s).

---End of Oryx build logs---
...

It's definitely failing to parse the Markdown content. Would you be able to post the contents of the .md file?

It happens with any markdown, even a test.
And just realized what happened...I created the blogpost.md file without the YAML frontmatter! It was just plain markdown.
Eh! Sorry for the false alarm!

Thanks for the update. I might write some code to catch that and print a nice/helpful error.


Considering searchability

From the current interface it is not clear yet how individual reports will be searched for once there will be 1000s - may need some consideration depending on the interface.

done


Deploy AppRTC wihtout App Engine

Hi, is possible for AppRTC deployed without app engine? I wan't to make my on server to serve client apprtc.

any update @suparsana21


Using AddValidationKeys

Hi,
Along with AddSigningCredential if I use AddValidationKeys to add additional validation keys to validate access token then, will it clear the security key added by AddSigningCredential as calling AddValidationKeys method creates new singleton instance of DefaultValidationKeysStore with validation keys.
Thanks.

No it won't. Did you run into a problem here?

Actually, I haven't used it yet but I got this query while looking at IdentityServer code on how singleton of DefaultValidationKeysStore works.

The DI system allows to register multiple instances of the same type.
https://github.com/IdentityServer/IdentityServer4/blob/dev/src/IdentityServer4/Services/DefaultKeyMaterialService.cs

Thanks for the clarification. Can I use AddValidationKeys method to add KeyId, which I have got from wellknown endpoint of other IdentityServer using DiscoveryClient.

you can add a key - yes.

ok. So I can create instance of RsaSecurityKey and assign KeyId and pass this security key to AddValidationKeys method.

yes - that works.

Hi,
If order to call "AddValidationKeys" method to add keyId issued by other Identity sever, If I create DiscoveryClient object by passing authority value as url of other identity server e.g. "https://Identitysvr2:44333/IdentityServer4"
and call GetAsync() method to get JsonWebKey I get following error. Any idea regarding below error.
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at System.Net.Http.WinHttpHandler.d__105.MoveNext()
Thanks.


It don't fit to the Page Container width

If I have Left Or Right Navigation Sidebar, then it's not subtracting the Sidebar width, resulting in showing the toaster starting from behind the sidebar.

This seems to be a simple z-index issue. Can you please provide a small plunker that demonstrates this issue?


AVIF image support has been disabled

Describe the bug
Not able to use AVIF format.
Getting an error like:
imagecreatefromavif(): AVIF image support has been disabled at /var/www/platoshop-v2/vendor/intervention/image/src/Drivers/Gd/Decoders/FilePathImageDecoder.php:48)
Code Example
 $manager = new ImageManager(new Driver());
 $img = $manager->read($file);

Expected behavior
It should read my avif file.
Environment (please complete the following information):

PHP Version: 8.2.15
OS: Ubuntu 20.04
Intervention Image Version: 3.3.2
GD or Imagick: GD

This seems to be due to the setup of the GD library on the server host and is not under the influence of Intervention Image.
Read how to setup Avif with GD properly.


replace AudioCache with assetToFile(assertPath, filePath) ?

I looked at AudioCache, and all it does is:

make an asset to a file
memoize

I think we can refactor AudioCache into:
assetToFile( assetPath, filePath)
// and
assetToTempFile (assetPath)

and have users use their own memoize function
(eg. https://docs.flutter.io/flutter/package-async_async/AsyncMemoizer-class.html )

@luanpotter what are you thoughts about this?

@devdoomari3, thanks for the suggestion! :)
But why would we require from the users to do their own memoization? I think AudioCache is a nicely closed package for playing audios from assets because while it might load then in the device, it takes care of not overusing that through its built-in memoization.
It seems to me that you are suggesting that the users of the AudioCache API would need to go to additional steps to use it properly, without any apparent gain (AFAICS). Would you care to elaborate a bit more on the idea and why would it be an improvement?

Closing as I think this is fine the way it is now.


How to migrate a database prior to 1.0

Sorry, I clicked on the database migration link in the release notes. Didn't understand how to migrate?

Hi @shuen2023, to migrate the database you can download the file called kure_v1_migration.tar.gz from the assets section of the v1.0.0 release, decompress it and execute the script that comes with it.
It will ask you for the master password and to confirm the operation, but that's all.
You can make a backup of your database by using the kure backup command before the migration if it gives you peace of mind.

[!Note]
Alternatively, if you don't trust the artifacts, you could clone the repository and execute the script locally by doing
git clone -b v1.0.0 --single-branch https://github.com/GGP1/kure
go get -u
go run migration/v1/main.go

Hi @shuen2023, to migrate the database you can download the file called kure_v1_migration.tar.gz from the assets section of the v1.0.0 release, decompress it and execute the script that comes with it.
It will ask you for the master password and to confirm the operation, but that's all.

This will encrypt all the names in the database using a XOR operation between the authentication key and each one of the names.

You can make a backup of your database by using the kure backup command before the migration if it gives you peace of mind.

[!Note]
Alternatively, if you don't trust the artifacts, you could clone the repository and execute the script locally by doing
git clone -b v1.0.0 --single-branch https://github.com/GGP1/kure
go get -u
go run migration/v1/main.go

Hi @shuen2023, to migrate the database you can download the file called kure_v1_migration.tar.gz from the assets section of the v1.0.0 release, decompress it and execute the script that comes with it.
It will ask you for the master password and to confirm the operation, but that's all.

This will encrypt all the names in the database using a XOR operation between the authentication key and each one of the names.

You can make a backup of your database by using the kure backup command before the migration if it gives you peace of mind.

[!Note]
Alternatively, if you don't trust the artifacts, you could clone the repository and execute the script locally by doing
git clone -b v1.0.0 --single-branch https://github.com/GGP1/kure
go get -u
go run migration/v1/main.go

<EMAIL_ADDRESS>它会要求您输入主密码并确认操作，但仅此而已。

这将使用身份验证密钥和每个名称之间的 XOR 运算来加密数据库中的所有名称。

kure backup如果这样能让您安心，您可以在迁移之前使用该命令备份您的数据库。
 I was able to migrate it. However, there is still a garbled name and I don't know how to deal with it

I originally thought that the migration database would be included in the new version of the command. So I directly go install -v github.com/GGP1/kure@latest and then I couldn't wait to use the new version of kure to open the original database. What happened next was that I could only leave a message for help.Thank you

Oh, I remember now. I created the entry right after installing the new version. So when I migrate the database later, the password entry created with the new version may have garbled names.


Update node-pty in vscode and remove any case on ptyProcess

Part of #113827
After https://github.com/microsoft/node-pty/issues/451 is done we need to update vscode's node-pty to the latest (let's do this part on master. As part of the same update we need to remove the bad casts here (in tyriar/flow_control):
https://github.com/microsoft/vscode/blob/c6c7ddd443771bd7bda7e1bf82b360e1a38218f3/src/vs/workbench/contrib/terminal/node/terminalProcess.ts#L175-L176
https://github.com/microsoft/vscode/blob/c6c7ddd443771bd7bda7e1bf82b360e1a38218f3/src/vs/workbench/contrib/terminal/node/terminalProcess.ts#L342-L343

Included in test https://github.com/microsoft/vscode/issues/114378

Included in test https://github.com/microsoft/vscode/issues/114378


Use CO-RE to remove dependency on host machine kernel headers?

Hey all, I've been able to get kubectl-prof working with the perf profiler and it works beautifully (thanks for the hard work here!). However, I'd really like to use the eBPF profiler, but on DigitalOcean, their host instances do not have the kheaders module available.
I've reached out to DO and it doesn't seem like the lack of kheaders is going to change anytime soon. I was looking at CO-RE (https://web.archive.org/web/20220522105208/https://www.seekret.io/blog/handling-the-challenge-of-deploying-ebpf-into-the-wild/) as a potential work around.
Is this something that I could help implement here?

"Thank you for the suggestion. I will study this functionality."

Let me know if there's a way I can help implement it!


Netflix Clone

Netflix clone
you have to make the clone of netflix page with proper responsiveness.
because this is a Hard issue you have to make it properly.

i want to contribute in this .This clone is made in react and it is completely responsive.

ok @Rick-03 You have assigned this issue happy coding


Only one user able to pair?

Hello @HomeACcessoryKid I was wondering if only one device can pair at a time, I didn't realize until I wanted to pair another iOS device

One user can pair, but after that can invite other users to the home. In case you use a home hub (iPad4+/iTV) then you can make others an administrator as well. So, it works, but pairing only happens once...


Using 'allowInput' requires the user to click outside of the input (twice) for focus to be lost

Using allowInput requires the user to click outside of the input (twice) for focus to be lost.
Ember Twiddle

@Mithrilhall I assume this is the same issue as the other one? Can we close it too as it's likely a flatpickr bug?

@rwwagner90 I don't think this is the same issue (I could be wrong). I tested this in a jsfiddle with vanilla flatpickr and it didn't have this issue. I'll recreate it and link to it in here.

Vanilla flatpickr doesn't appear to have this behavior.
JSFiddle Example

@Mithrilhall can you please try ember-flatpickr 1.3.0? This seems to have been an issue with older flatpickr.

Works like a charm. Thank you @rwwagner90.


cnspec: 10.7.0 -> 10.7.1

Diff: https://github.com/mondoohq/cnspec/compare/refs/tags/v10.7.0...v10.7.1
Changelog: https://github.com/mondoohq/cnspec/releases/tag/v10.7.1
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 295820 run on x86_64-linux 1

1 package built:

cnspec


Monitoring tools exclusion

Rule Logic:
A user must uncomment SecAction 900980 from crs-setup.conf to enable the exclusion. The SecAction has 2 variables that users must configure:

tx.trusted_ips: a comma-separated list of IPs or classes
tx.trusted_ua: a whitespace-separated list of User-Agent (partial match)

The exclusion occurs only for GET and HEAD methods, and it removes the following rules:

id: 911100 (allowed methods)
id: 913100,913110,913120,913101,913102 (scan detection)
id: 920280 (missing/empty host header)
id: 920350 (IP address in host header)
tag: attack-dos (DoS protection)
tag: attack-disclosure (all RESPONSE-*-DATA-LEAKAGES rules)

Just a quick note: as I see in v3.4/dev branch we use OWASP_CRS/3.3.0 for ver action, not OWASP_CRS/3.4.0.

@airween Nice spotted. We have all our ver actions still at 3.3.0 though. I think it would be a good idea if we change our release procedure, to increase the versions directly after a main branch. Then it's consistent, and it's also useful for debugging (e.g see if a machine is running release version or master branch). Would you agree? Then I'll open a separate PR for that.

I think it would be a good idea if we change our release procedure, to increase the versions directly after a main branch.

This is how we're doing now, or isn't it?

Then it's consistent, and it's also useful for debugging (e.g see if a machine is running release version or master branch).

I just thought the 3.3.0 would be better here to keep this consistent state.

Would you agree? Then I'll open a separate PR for that.

I agree - but open a PR for what? :)

This is how we're doing now, or isn't it?

No, all our rules are still at 3.3.0. Right now in the [https://github.com/coreruleset/coreruleset/wiki/Release-Procedure](Release Procedure) we bump all versions before the next release. I think it would be better to bump them after a release. (And also check them before the next release).

No, all our ver actions are still at 3.3.0.

Ah, thanks for pointing that. I think we must discuss it at the next monthly chat.
Note, I checked the wiki page above, and found an another interesting part:
Update copyright in all the files if there is a new year
I think we should discuss about another context of copyrights.

Here is full UA for Zabbix version 5.0.4 using key web.page.get:
Zabbix 5.0.4
and for Web monitoring feature (don't know them doesn't match):
Zabbix

Zabbix 5.0.4

idk if I get it well, the partial match "Zabbix" didn't match "Zabbix 5.0.4"?
(maybe I missed something, but anyone knows what's wrong with the PR test?)

idk if I get it well, the partial match "Zabbix" didn't match "Zabbix 5.0.4"?

It will match, sorry i confused you. I just wanted to be precise so i pointed out that the same version of Zabbix will use different UA while using different methods of accessing HTTP resource.

It will match, sorry i confused you. I just wanted to be precise so i pointed out that the same version of Zabbix will use different UA while using different methods of accessing HTTP resource.

ahh I see! Indeed it's a good point, I'm wondering: what if a user wants to allow a specific UA and not match something in it? Should I edit the matching UA rule (901480) replacing pm with rx operator? I mean, by doing it a user could set the tx.trusted_ua with something like .*Nagios.*|Zabbix 5\.0\.4 ?

ahh I see! Indeed it's a good point, I'm wondering: what if a user wants to allow a specific UA and not match something in it? Should I edit the matching UA rule (901480) replacing pm with rx operator? I mean, by doing it a user could set the tx.trusted_ua with something like .*Nagios.*|Zabbix 5\.0\.4 ?

I would keep the pm because:

Request needs to match also allowed IPs so there's a very little chance of bypassing using UA.
Asking users to write regexpes as part of software configuration seems to be a little hardcore.

In case you want to allow using very specific UAs, then i suggest creating two methods of specifying UA: pm and also rx (using two different configuration rules).

OK. So this has been lingering too long with failing tests.
I'm sorry to announce that both, the ipMatch as well as the pm do not support macros. This means the variable expansion via the %{tx...} is not going to work.
We usually do within instead of pm. So that could work. However, I do not see a solution for ipMatch outside of working with ipMatchFromFile and that looks a bit ugly. Please be aware that the target file of ipMatchFromFile has to exist. Which brings us to the whole "foo.conf.example" problem for an optional feature (the rule is active from the beginning, so the file has to be existing from the beginning too, yet we have to make sure we are not overwriting it).
All in all, I do not see a clear way forward and will close this PR. Mainly because I want to clean up the queue. Feel free to re-submit @theMiddleBlue when you have a solution. Thank you for the nice idea, it would have been so sweet if this would work.


[Feature] Accessibility for blind students/people.

Fix to #27 and https://github.com/YJDoc2/8086-Emulator/issues/5

Changelog
Keyboard shortcuts

Shortcuts
Function

Ctrl+Shift+1
Compile

Ctrl+Shift+2
Execute next instruction

Ctrl+Shift+3
Run Code

Ctrl+Shift+4
Stop

Ctrl+Shift+5
Submit input

Ctrl+Shift+6
Focus on start address

Ctrl+Shift+7
Save address

Shift+E
Focus on editor

Shift+A
Accessibility Mode

Shift+I
Focus on input

Others

When accessibility mode is on the editor goes in Read-only mode
Miscellaneous fixes.

Updated the PR to resolve the conflicts.


A load balancer cannot be attached to multiple subnets in the same Availability Zone

Error: error creating application Load Balancer: InvalidConfigurationRequest: A load balancer cannot be attached to multiple subnets in the same Availability Zone
│       status code: 400, request id: 9831def4-be92-4315-a399-ddeb1b8f9dde
│
│   with module.vault.aws_lb.default,
│   on .terraform/modules/vault/main.tf line 270, in resource "aws_lb" "default":
│  270: resource "aws_lb" "default" {

Related code:
# Add a load balancer.
resource "aws_lb" "default" {
  load_balancer_type = "application"
  name               = var.name
  security_groups    = [aws_security_group.loadbalancer.id, aws_security_group.default.id]
  subnets            = local.aws_subnet_ids
  tags               = var.tags
}

The related local:
  # Set the `aws_subnet_ids` based on either the resource object or the data object, whichever is set.
  aws_subnet_ids = coalescelist(aws_subnet.default[*].id, try(tolist(data.aws_subnets.default[0].ids), []))

Related data object:
data "aws_subnets" "default" {
  count  = var.vpc_id == "" ? 0 : 1
  filter {
    name   = "vpc-id"
    values = [local.vpc_id]
  }
}

So; I guess the data object (aws_subnets) needs an extra filter.

Just released version 2.0.0, which addresses this issue.


build: move zip into separate step

:tada: This PR is included in version 1.2.0-test.1 :tada:
The release is available on:

v1.2.0-test.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

v1.2.0
GitHub release

Your semantic-release bot :package::rocket:


Add HeaderLayoutType accepted values in Set-PnPPage.md

Type

[x] Bug Fix
[ ] New Feature
[ ] Sample

Related Issues?
Fixes #2870
What is in this Pull Request ?
Correct Accepted values for the HeaderLayoutType parameter for the Set-PnPPage cmdlet documentation

Thank you so much @a1mery , merged it !


chore(main): release 1.1.3

:robot: I have created a release beep boop
1.1.3 (2024-04-03)
Bug Fixes

Update architecture diagram URL (f478aa0)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/nesty92/terraform-aws-gitlab-runner-autoscaler/releases/tag/1.1.3 :sunflower:


WIP: [GEN-8039] chore:completely remove PGBouncer from postgres image

closing as stale. please re-open as needed


Create -about flag when requesting information about an entity

It would be helpful to get information regarding an entity before using it/selecting what may the right entity for a certain job. This will be achieved during file-parsing and entity data collection; legoHDL will store any initial continuous line of comments found at the beginning of an entity's file as the "information" for that entity.
Ex:
-- Project: block_b
-- Entity: mux_2x1
-- Created: 10/19/2021
-- Description:
--     Selects first input on '0' otherwise selects second input.

entity mux_2x1 is
...

Something like:
legohdl port market_a.library_c.block_b:mux_2x1 -about
will print the commented lines as a block of text for users to read.
Project: block_b
Entity: mux_2x1
Created: 10/19/2021
Description:
    Selects first input on '0' otherwise selects second input.

This encourages well-documented code and doesn't require the user to write the same documentation in multiple places (like filling out a separate section for legohdl to see the information).

To be merged from major-refactor branch.

Merged major-refactor.


KAFKA-4921: AssignedPartition implements equals

Solves: KAFKA-4921
Bug type EQ_COMPARETO_USE_OBJECT_EQUALS (click for details)
In class org.apache.kafka.streams.processor.internals.StreamPartitionAssignor$AssignedPartition
In method org.apache.kafka.streams.processor.internals.StreamPartitionAssignor$AssignedPartition.compareTo(StreamPartitionAssignor$AssignedPartition)
At StreamPartitionAssignor.java:[line 75]

This change has been incorporated into trunk. Closing for now.


Get config from the environment

Check environment for configuration, using hardcoded values as defaults
Gitignore
Use python-dotenv to load config from file
Add requirements.txt

I really want to keep imports on separate lines, it's a lot easier to see what changes when anything does.
The same way, I really want to keep imports as minimal as possible. It's not a performance thing (I'm sure you are aware the entire module is imported either way), but it's about doing things explicitly.


Support Rust workspace Cargo.toml

Tried this under Railway, but when your Cargo.toml is a workspace one, it doesn't work. It however should be allowed. Building a workspace will build all members, and while that may be not ideal, starting a binary will still work with it since it'll get generated. A person can also provide a custom build command targeting only one package when that's undesired behavior,
cargo build --release -p package-name
Error: Generating start phase

Caused by:

0: Reading Cargo.toml
1: missing field `package` at line 1 column 1

will work on this
cc @Milo123459


No releases under https://github.com/PowerShell/PowerShellGet/releases

Not sure when this disappeared, but I can no longer find any published releases under:
https://github.com/PowerShell/PowerShellGet/releases

@musm thanks for opening this! We intend to start doing this once we ship stable (starting with version 1.0.0) and also include tags on the release.


Release v1.0.8

@VodkaBears Could we have a new release with the latest additions/features.
Thank you!

Yes, a bit later


Add support to a seeked event

Today Clappr does not support 'seeked' event, sometime we need listen this event to realize one action when seek is finished.
I talked with @towerz and we discuss about the new architecture of Clappr, so we decided to implement this event only for playback.

Coverage decreased (-0.2%) to 73.588% when pulling add75f1903281f6cad672dadaddb21d4279de0c2 on diegosperes:seeked-event into 2bf02ed17546c485d48eb4622969e2d53fcf7d5d on clappr:master.

Coverage increased (+0.0009%) to 73.759% when pulling bea04e50953cc48117d1762af36ae38cc9141159 on diegosperes:seeked-event into 2bf02ed17546c485d48eb4622969e2d53fcf7d5d on clappr:master.

@diegosperes thank you for working on this feature! why only adds to playback ?
Currently, when playback starts to seek, the container event is CONTAINER_SEEK.
The first issue, (imo) is that event is trigger by the container in seek() method : i think that container should listen to a playback PLAYBACK_SEEK event (or PLAYBACK_SEEKING) and bubble it up like other payback event. This is not a small modification, because you need adds the new event to all playbacks.
Then when playback has finished to seek, it should trigger a PLAYBACK_SEEKED event and container should listen to this event and then trigger a CONTAINER_SEEKED event. (it require to modify all playbacks to add also this new event).
PS: I am aware that this may be tricky as each playback event mechanisms differs and it may be only partially supported.

Hi @kslimani, thank for your consideration, so in new Clappr architecture, @towerz was talked that the container not would be a proxy anymore, you can see this in android implementation, It's the reason of first implementation. But It's better change this only when Clappr will be updated to the new architecture, so I implemented the CONTAINER_SEEKED too.
I think is better do this way  it may be only partially supported

Coverage increased (+0.3%) to 74.083% when pulling 11107d2da64568cabf51c50bae7b1a1e7b552e93 on diegosperes:seeked-event into 2bf02ed17546c485d48eb4622969e2d53fcf7d5d on clappr:master.

Allright, so with these changes, the seeked event is triggered by playback and bubble up by container and the seek(ing) event is still triggered only by container. (in seek method).
I will take a look at android implementation, thank you for pointing this.

Coverage increased (+0.3%) to 74.083% when pulling 63bf1fd6c91a185b81e3aa12abeb8cd83da6a514 on diegosperes:seeked-event into 2bf02ed17546c485d48eb4622969e2d53fcf7d5d on clappr:master.

Coverage increased (+0.3%) to 74.102% when pulling 518046c4e8ef3577067bb397d0382d27e87b2cd0 on diegosperes:seeked-event into 2bf02ed17546c485d48eb4622969e2d53fcf7d5d on clappr:master.

Coverage increased (+0.3%) to 74.102% when pulling 1049db3df9e1d9d63e071d81d87242d5451253d1 on diegosperes:seeked-event into 2bf02ed17546c485d48eb4622969e2d53fcf7d5d on clappr:master.

Coverage increased (+0.3%) to 74.083% when pulling 34e760935243288b45ee47e66aee61e446731906 on diegosperes:seeked-event into 2bf02ed17546c485d48eb4622969e2d53fcf7d5d on clappr:master.

Coverage increased (+0.4%) to 74.14% when pulling 11dea94831ca33627010bc54869a4abf3c1cb922 on diegosperes:seeked-event into 2bf02ed17546c485d48eb4622969e2d53fcf7d5d on clappr:master.

Coverage increased (+0.7%) to 74.501% when pulling 6678a24468fd3fda259a4de0ff2dc9cff9dddf28 on diegosperes:seeked-event into 2bf02ed17546c485d48eb4622969e2d53fcf7d5d on clappr:master.

Coverage increased (+0.5%) to 74.235% when pulling 061e48f615884ee7dd24818aeee0bc11a4b1e33f on diegosperes:seeked-event into 2bf02ed17546c485d48eb4622969e2d53fcf7d5d on clappr:master.

Coverage increased (+0.4%) to 74.121% when pulling 4c6ddcd729aec5b28468a8487bf4b7023d21cfdd on diegosperes:seeked-event into 2bf02ed17546c485d48eb4622969e2d53fcf7d5d on clappr:master.


fix: 🐛 update dependencies

:tada: This PR is included in version 1.1.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support IRSA for the service operator role assumption

Is your feature request related to a problem?
The old version of this operator did not natively support using IAM Roles for Service Accounts to assume the role necessary to provision resources.
Describe the solution you'd like
I think all that needs to happen is that the service operator server gets built with a compatible version of the aws-sdk-go, i.e. version 1.23.13 or later. Then, a method for adding the proper annotation to the ServiceAccount resource in the manifests needs to be provided.

Thanks and IRSA support is covered in #3.