DRYed the retry tests a bit via shared examples

@ibalosh I thought that the specs needed a bit more love so I decided to clean them up a bit and here's a PR to your branch.
Let me know if you see anything that's not a convention in this project or smells bad.
Here's a few things I've changed:

I've extracted the new retry tests into shared examples. They were duplicated in many places and some of them were already out of sync with the rest.
The above required rescoping subjects per describe blocks. It's not yet fully consistent across the whole file but I'd like one day to get there. I mean, when you say describe "#deliver", then the subject in this block should be a call to that method.
I  tried to make sure the tests that start with it keyword read as English (e.g. it "sets max_retries" do vs it "max_retries" do
I used specify when a textual description of a test is redundant

Hey @tomazy
gotcha, looks good to me, shared_examples was a good choice. I think it's good to go. Couple of notes just by going through the rspec file (which at some point would be probably better to split in multiple for easier reading):
One thing which I do find bit too much are line 6 to 11 on rspec file.
Setting this dynamically options for client removes I think from readability of the tests, especially since they are so long and it's bit harder to grasp when the subject is having which setup.
Also I am fan of using let variables within context and not defining them on top level if not needed. I am thinking mainly of max_retries here at top. If max_retries option is the one tested, then it makes sense to set it up within context where it's used, which I guess could be in share_example "retryable" or something that covers retries solely. It makes things easier to follow.

Thanks for the feedback @ibalosh! Good point about the readability and scopes of lets. I tried to address these issues in this commit: 1a5d5e5. See if it's any better.

love it @tomazy , much easier to follow, thanks!
(At some point in near future let's catchup on refactor of whole rspec test suite, adding rubocop with 1.8.7 support as start, to make things easier. Current rspec follows very old rulings, from beginnings of the postmark gem)


feat: added formatting service

Closes #20

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ADB functionality.

You can actually operate adb on WSL.
Well, on some level.
By default, WSL will install adb of version 1.10.31.
If you pick the very same version on Windows and start adb server (adb start-server) on Windows, you can actually see and access android devices on WSL.
I assume adb server's inter-process communication is based on network model (on port 5037 as you often see).
So even the server is running on windows, it does not break the client running on WSL as long as they recognize each other with same version number.
Have fun hacking WSL :D

So for example, if you adb list it lists connected devices from bash? I would be very surprised if this is the case.

Hi @ethanhs,
Please kindly have a look :)

Wow, great! I am glad you found this. :) I will add this to the list and add something in the notes. Thank you!

Fixed in https://github.com/ethanhs/WSL-Programs/commit/810914cb9f232b0aedd4766fc388aae7477b8013

Awesome, this would enable me to develop React-Native on device. Will check it out

I don't believe this works on WSL2? I've got the same ADB version running on both windows and Ubuntu, ensuring I start the windows adb server first (via CMD) and the device list is always empty in the WSL.

For me it's very simple: Run the production build via WSL and use ADB through Git Bash on CMD (and everything else) works there as well.
I only have to remove the build folder and switch my ./android/local.properties to use the other location for the Android sdk.
# Windows
# sdk.dir=/C\:\\Users\\name\\AppData\\Local\\Android\\Sdk
# WSL
sdk.dir=/usr/lib/android-sdk/


Implement private IGDB endpoints

IGDB has a set of private endpoints meant for pro tier users. Three of these endpoints are listed under the regular list of endpoints so they are already implemented, but there still remains a dozen unimplemented endpoints.

In addition to private endpoints, a Pro tier account also has a higher per-page limit and offset limit. These should be configurable client variables.

Instead of client variables, I've instead opted to document the limits and let the user handle their own limits


fix: accept simple quotes in permalinks as even Windows accepts it

What has changed?
Make sure it's possible to have a permalink with simple quotes ('). Even Windows is fine with it :grin:
Long story short: I'm upgrading @metasmith/permalinks to 3.0.0 and with a bit of configuration everything works fine except a permalink with a ' (https://damien.pobel.fr/tag/lecteur-d'%C3%A9cran/) that previously worked fine.
Level of change

Bug fix
Added functionality

unsure if it's a bug or a feature to be honest but given the comment in the source about Windows not accepting a quote, I tend to think it's a bug fix. (note: the comment suggests it's possible to override the regexp, but I haven't found a way to do it)

For Added functionality and API changes make sure the documentation has been updated accordingly.

I remember I documented this in a commit body: https://github.com/metalsmith/permalinks/commit/b30d8752fb26d62514aa82655446dd7c91b2d56e. In your case specifying { slug: { remove: /regex-without-simple-quote/ }} as options would solve the issue (you could use the one defined as defaultSlugifyRemoveChars). Can you confirm?
My reasoning is that a FR user with a file at /tag/lecteur-d'écran probably wants it to end up at /tag/lecteur-d-écran, but I think this is not what happens with 3.0.0, so I need to go back and test. Any change to the single quote would also need to be a change for the double quote to be consistent. IMO single & double quotes should continue to be stripped/replaced by default, but it should be possible (and easy) to allow them anyway.

Sorry for the late reply @webketje I've been quite busy these days. I see you merged that and that's cool. I guess you figured it already but { slug: { remove: /regex-without-simple-quote/ }} was not working, I've not dug that much into the code, but I think the check was done anyway.
Also, given I want to keep a lots of characters that are removed by default, I need to pass a custom slug function and AFAICT it's not possible to pass both the remove RegExp and a custom slug function.
Anyway, I've just tested with the last commit and it's working fine me now. Is a 3.0.1 planned soon ?

https://github.com/metalsmith/permalinks/releases/tag/v3.0.1


The global notification subscribers are not being saved. It is not available if refresh the page

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 27c845a7-d230-c0b0-e68c-174246f866bc
Version Independent ID: a773099c-3af5-dc66-b303-335ccf9875dc
Content: Manage notifications for a team or group - Azure DevOps
Content Source: docs/notifications/manage-team-group-notifications.md
Product: devops
Technology: devops-collab
GitHub Login: @chcomley
Microsoft Alias: chcomley

@Chandrashekarachar Thank you for the feedback.
We will provide an update to the documentation.
In the meantime, please refer instead to Admin settings > Notifications:


Failed to resolve entry for package "@alchemy/aa-signers" on React + Vite

[REQUIRED] Environment

Browser version: Chrome 120
AA SDK version: 1.2.1
Package: aa-signers

[REQUIRED] Describe the problem
Hello everyone, I'm following the integration instructions for web3auth.
Trying to import @alchemy/aa-signers/web3auth does not work as it can't find the directory
Failed to resolve import "@alchemy/aa-signers/web3auth" from "src/App.tsx". Does the file exist?
When I import Web3AuthSigner from @alchemy/aa-signers I get the following error:
[vite] Internal server error: Failed to resolve entry for package "@alchemy/aa-signers". The package may have incorrect main/module/exports specified in its package.json: Missing "." specifier in "@alchemy/aa-signers" package Plugin: vite:import-analysis
I tried using the package on the main project (has some custom configs) and also on a clean vite project, the error is the same for both.

Same happens when I am trying to import signer as per tutorial here
import { FireblocksSigner } from '@alchemy/aa-signers/fireblocks';

results in error
src/core/providers/fireblocks/fireblocks-aa.signer.ts:1:34 - error TS2307: Cannot find module '@alchemy/aa-signers/fireblocks' or its corresponding type declarations.

this seems fixed, are you still seeing this?
you might need to use type: module in your package.json

Hi, yes this has been fixed with the updates.


Allow library podspec to declare Swift Package Manager dependencies

Summary:
React-Native uses Cocapods for native dependency management on iOS. While CocoaPods is flexible and popular, Apple's Swift Package Manager is the new standard. Currently consuming packages available only via Swift Package Manager is not possible. This change implements a single extension so .podspec files can declare Swift Package Manager dependencies via
ReactNativePodsUtils.spm_dependency(s,
     url: 'https://github.com/apple/swift-atomics.git',
     requirement: {kind: 'upToNextMajorVersion', minimumVersion: '1.1.0'},
     products: ['Atomics']
   )

Changelog:
[IOS] [ADDED] - libraries can now declare Swift Package Manager dependencies in their .podspec with ReactNativePodsUtils.spm_dependency
Test Plan:
https://github.com/mfazekas/rn-spm-rfc-poc/
Is a simple demo for the feature:

Podspec declare dependency with:
if const_defined?(:ReactNativePodsUtils) && ReactNativePodsUtils.respond_to?(:spm_dependency)
  ReactNativePodsUtils.spm_dependency(s,
    url: 'https://github.com/apple/swift-atomics.git',
    requirement: {kind: 'upToNextMajorVersion', minimumVersion: '1.1.0'},
    products: ['Atomics']
  )
else
  raise "Please upgrade React Native to >=0.75.0 to use SPM dependencies."
end

import Atomics and ManagedAtomic is used in the code

3.) spm_dependency causes the dependency to be added via post_install hook in the workspace

4.) spm_dependecy causes the library to be linked with Atomics library

Limitations:
1.) only works USE_FRAMEWORKS=dynamic pod install otherwise the linker fails with known Xcode issue - duplicate link issue
2.) .xcworkspace needs to be reopened after pod install - this could be worked around by not removing/readding spm dependencies
See also:
https://github.com/react-native-community/discussions-and-proposals/issues/587#issuecomment-2117025448
https://github.com/react-native-community/discussions-and-proposals/pull/787

Thanks for the amazing PR. 👏 I left some comments in the code to simplify it a little bit and to make it easier to use.
I also have a couple of questions:

1.) only works USE_FRAMEWORKS=dynamic pod install

Does it works with static frameworks?

It's a bit complicated. I've tested with Almofire Swift Package Manager package that has a dynamic and static product.

Almofire - static
AlmofireDynamic

USE_FRAMEWORKS=dynamic pod install
works
works

USE_FRAMEWORKS=static pod install
duplicate symbols
undefined symbol*

pod install
duplicate symbols
undefined symbol*

Now undefined symbols can be fixed by adding AlmofireDynamic to the user project. But modifying the user project is less than ideal as unlike Pods project which get regenerated with each pod install, the user project is not regenerated.

2.) .xcworkspace needs to be reopened after pod install - this could be worked around by not removing/readding spm dependencies

Do you think there is a way to detect whether dependencies changed so that we can emit a red message to prompt the user to close and reopen the .xcworkspace project? Alternatively, we can kill Xcode, but if a person has multiple project open, that could be annoying.

According to testing in Xcode 15.4, if there is a single swift package manager dependency, the regenerating the project might loose the dependency in the UI. (Not 100% reproducible)
https://github.com/facebook/react-native/assets/52435/e4f742e4-1248-429f-8588-4235a827b6d3
We can write an osascript that reloads the project if it's open, but it's a bit tacky
#!/usr/bin/osascript -l JavaScript

function main() {
  const app = Application("Xcode")
  const active = app.activeWorkspaceDocument();

  console.log("Active", app.activeWorkspaceDocument().file());

  const worspacePath = "/Users/boga/Work/OSS/react-native-sim/rn-spm-rfc-poc/example/ios/RnSpmRfcPocExample.xcworkspace"

  if (app.activeWorkspaceDocument().file() == filePath) {
	  app.activeWorkspaceDocument().close();
	  app.open(filePath);
  }
}

main()

Sorry for the late reply. I'm still catching up after the conferences of the past weeks.
One thing we can add is a big warning message that runs only if SPM dependencies are found.
The message can

ask the user to close and reopen the XCWorkspace
ask the user to run with dynamic frameworks (if it has not done that)

What do you think?

One thing we can add is a big warning message that runs only if SPM dependencies are found. The message can

ask the user to close and reopen the XCWorkspace

I've tested this with new Xcode 16.0 beta and close/reopen issue is solved there. So likely some warning that
If you're using Xcode 15 or earlier you might need to reload the Xcode workspace

ask the user to run with dynamic frameworks (if it has not done that)

The SPM might be a simple Swift Macro and in that case it works with all linking. If it's a static library then static linking causes link errors with duplicate symbols. If it's a dyanamic library, then static linking only works if the app also links with the dynamic library, otherwise they'll see undefined symbols.
So not sure what's the good message here.
You're using swift packages with static linking, this might cause linker errors.
Maybe we also add a url to this issue, or a new one created just for explaining the potential issues with SPM regarding linking?

What do you think?

Yes given that the reload issue seems to get's solved by new Xcode version, it don't think it's worth to mess with osascript workaround, so message is good there.  The linking part is a bit complicated, not sure what's a good message there.


Running from rc.local

When I run the bridge from the console it works and save the config file relative to the java package  for example if my java package is in /home/pi/link/habridge then the conf file is in /home/pi/habridge/data/habridge.conf
When i run from rc.local, no matter what i do, it wants to save the the file to a data dir in the root of the file system.
I have tried many variations of this, what am i doing wrong?
sudo -u pi /usr/bin/java -jar -Dserver.port=9090 /home/pi/link/habridge/ha-bridge-2.0.5.jar -d /home/pi/link/habridge/ > /dev/null 2>&1 &

Try to start with option: -Dconfig.file=/etc/habridge/habridge.config

Here is the way I have mine start.
Command I run from rc.local:      su -l -c "/home/pi/startup.sh" pi &
#!/bin/bash
This is /home/pi/startup.sh
/home/pi/starteb.sh
/home/pi/startscript2.sh
/home/pi/startscript3.sh
#!/bin/bash
This is /home/pi/starteb.sh
cd /home/pi/habridge
nohup java -jar -Dserver.port=9090 ha-bridge-2.0.5.jar > /home/pi/habridge.log 2>&1 &
It seems to set up the base directory in whatever directory you are in when you run the script.  I think rc.local runs as root, so even though you use sudo -u pi, I think it is still executing the command in the root directory

@paulv888  thanks, i tried that first and that resulted in a 500 error as it couldn't create file / said file was missing
@dmoos777  thanks i like that, looks elegant, after i posted i found this also works (calling a bash shell, though i have no idea why this needs it and the other apps in rc.local don't - but then i am a windows guy and pi dragged me kicking and screaming to linux :-) )
sudo - u pi sh "cd /home/pi/link/habridge ; java -jar Dserver.port:9090 ha-bridge-2.0.5jar" 2>&1 &
i guess it is time for me upgrade to jessie and figure out sysctrl  :-)

try this and no need to run as sudo on the pi
$ nano starthadridge.sh

Then cut and past this, modify any locations that are not correct
cd /home/pi/link/habridge
rm log.txt
nohup java -jar -Dserver.port=9090 ha-bridge-2.0.5.jar > log.txt &
chmod 777 log.txt

Then execute on the command line:
$ chmod u+x starthabridge.sh

Then execute the script:
$ ./starthadridge.sh

@bwssytems thanks i can try that too.  To be clear the line below worked for me and is simpler for me to maintain so you can close issue. though i can't be the only linux noob so documenting your way  might be a good idea?
sudo -u pi sh "cd /home/pi/link/habridge ; java -jar Dserver.port:9090 ha-bridge-2.0.5jar" 2>&1 &

I'll add it to the readme as that will help.


When you tap on the image on "how it works" section (using Coinbase Wallet) you can't see it in fullscreen

Pre conditions:
-Using Coinbase
Steps to reproduce:
1- Enter https://dx.staging.gnosisdev.com/
2- Select 'How it works'
3- Tap on the image of what is Slow.trade
4- Observe
Expected result:
The user see the full screen of the image
Actual result:
The user can see the file code of the image
Environment:
Android 7.0

https://drive.google.com/open?id=1dni6qTNFsyo4wW_50zFDLtN7sBw9fxwq
@andre-meyer

fixed in #418


The CPU/MEM info can not display the detail in the VM detail info page.

Version: 0.9
Issue: The CPU/MEM detail can not show in VM detailed page, no matter the VM is running or not.

This should be an UI bug.

fixed in 1.0


Add Force Re-Evaluation option

On the Evaluate screen, add an option to force re-evaluation of MP, QA, and EM data.
There is a check that requires the evaluation of MP's at least once a calendar year. There will also be times when there are plant/unit changes in CBS that are logged to INVENTORY_STATUS_LOG and subsequently require MP's to be re-evaluated.
Users may not know the MP needs evaluation flag is set but QA/EM evaluations will indicate that the MP needs evaluation.
It would be useful for users to just be able to re-evaluate all affected data using this flag at once.
Have also come across instances in 2.0 testing where QA and EM evaluations indicate the MP needs to be evaluated even though the MP status is Passed, Updated on Host, and the Monitoring Plan cannot be selected for evaluation. The user either needs to make a temporary change to the MP or export/re-import the MP to trigger the evaluation.

Users should have the option to force a re-evaluation of their data.
This will require a new button, and the check engine will be called for the data indicated.

ECMPS 1.0 Evaluation Screen for reference

Verified on dev using ORIS 50368, CT1

Force Re-Evaluation checkbox is added to the Evaluation screen
MP, QA Test Data, QA Cert Events, TEEs, and EM records can be force-reevaluated
Evaluation Report emails are sent on force-reevaluations

I did notice one issue with force-reevaluations on TEE and EM records. When the user selects a Facility, Location, Reporting Period, clicks Apply Filter, and then checks off the Force-Reevaluation box, previously evaluated TEE and EM records cannot be selected. The user will have to click Apply Filter again before selecting them.
The checkboxes for these records are greyed out after select 50368, CT1, clicking Apply Filter, and then clicking the Force-Reevaluation checbox.

After clicking Apply Filter again.

Issue noted above has been resolved on dev.

I verified this option is working.


Removing attribute type in YAML, in order to make it cleaner and more flexible

interesting, you're proposing to remove type attribute to use a YAML notation where one line of response could have a new structure of levels for multiple responses.
Is that right?

Yes. The main idea is that you have a list of answers and the bot will choose one of them randomly. Each answer can be a single message or a list of messages (previously called 'block' messages). Each message (string) may have multiple lines by using de default YAML syntax (with | and >, as described in YAML Multiline Strings).

@Duerno we have some problems with your commits, just merged another one that changes some structure conventions.
Can you take a look?

@diegodorgam I've rebased my commit with origin/master and updated the structure conventions.


Wallet: Bad input selection with >50 coin objects results in InsufficientCoinBalance in command 0

Bug description
Sending or staking with the coins split over many objects results in this error InsufficientCoinBalance in command 0.
Instead of having many inputs, the wallet just tries to split the required amount from a coin object and then fails if it has insufficient funds.
Example tx to send https://explorer.rebased.iota.org/txblock/7iP64PHnpG55YgCSdUZcHN2oedFAugS4ydgo9SG9S88V?deviceId=a68ffc39-4a1e-4362-ad35-9f2c50b9e1e6&network=testnet (I had enough funds, split over 500 objects).
Example tx to stake https://explorer.rebased.iota.org/txblock/59mWXHFh2jvWXLouWAW6z2fTQodys3jcHMjiKtmVLnCK?deviceId=a68ffc39-4a1e-4362-ad35-9f2c50b9e1e6&network=testnet
Steps To reproduce the bug

Split funds into many >50 objects
Send a transaction that requires the coins of >50 objects

Expected behaviour
If there are many objects, the wallet should check how many of them are required to fulfill the needed amount and provide merge them for the gas payment. Why does it only merge 50 currently? 256 is the max_gas_payment_objects, so at least this would be an easy improvement already.
If it's still not enough, it could provide more inputs separated from the gas coin and use the amount from there. Alternatively if that's too complex logic for the wallet, it could at least display an error message that the funds are split over too many objects and that they should be consolidated.
Actual behaviour
Wallet merges only 50 coin objects for the gas coin and then tries to split the required amount from this gas coin, without checking if it has enough balance
Errors
InsufficientCoinBalance in command 0

Hello @Thoralf-M
This will be review by the support team. Visit the live support page to initiate a chat with an agent for further assistance via live agent.
Regards


Tests failing on master because password hashing is broken

python manage.py test fails on master (I think because password hashing is broken).

#82


When there is a compilation error...

Would it be possible to stop attempting to compile (until a file save takes place, which would retrigger the watch/compile process)?

I don't think it's possible as kre doesn't give you that option I assume, maybe DTH has that capability but I am not sure.


Maximize seems to be broken

function M.maximise()
    local width, height = vim.o.columns, vim.o.lines

    local win = vim.api.nvim_get_current_win()
    local view = vim.fn.winsaveview()
    vim.api.nvim_win_set_width(win, width)
    vim.api.nvim_win_set_height(win, height)
    vim.api.nvim_win_call(function()
        vim.fn.winrestview(view)
    end)
end

This method since the last updated it is broken.
Locally I fixed it by passing the win variable like this
vim.api.nvim_win_call(win, function()
        vim.fn.winrestview(view)
 end)

@willothy FYI ;-)

Oops, that must have happened while resolving a conflict during rebase while I was cleaning up the commits in that PR. I'll send in a PR fixing this tonight!

There seems to be a few things not working quite right since the last refactoring. Is there tests to check nothing breaks?


error occur: shape error

Hi, thank you for making easy notebook for WGAN. I am trying to use your WGAN.
However, I got this error message
RuntimeError: Mismatch in shape: grad_output[0] has a shape of torch.Size([1]) and output[0] has a shape of torch.Size([32, 1, 1, 1]).
I just cloned your code, and run.
Do you know how can I fix this error?

add
one = one.repeat(32,1,1,1)
mone = mone.repeat(32,1,1,1)
and set drop_last=True in dataloader should fix this error.


[TASK-30] Show user name and image with sidebar specs.

Task Card - https://github.com/rafayet-monon/surveyor/projects/1#card-51278200
What happened
See user name and profile photo
Insight
No user name provided in the API. Using type for now. User photo for dev is not available

[x] Show user image and email
[x] Write sidebar unit tests
[x] Write sidebar UI tests

Proof Of Work

CI should pass successfully.

Fails

:no_entry_sign:

🃏 FAIL in details.test.js

renders the user image of sidebar

Expected the element to have attribute: src="user-placeholder.jpg", received: null

Full message

Error: expect(element).toHaveAttribute("src", "user-placeholder.jpg") // element.getAttribute("src") === "user-placeholder.jpg"
Expected the element to have attribute:
src="user-placeholder.jpg"
Received:
null
at Object. (/home/runner/work/surveyor/surveyor/src/tests/screens/Home/details.test.js:45:18)
at Object.asyncJestTest (/home/runner/work/surveyor/surveyor/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:102:37)
at /home/runner/work/surveyor/surveyor/node_modules/jest-jasmine2/build/queueRunner.js:43:12
at new Promise ()
at mapper (/home/runner/work/surveyor/surveyor/node_modules/jest-jasmine2/build/queueRunner.js:26:19)
at /home/runner/work/surveyor/surveyor/node_modules/jest-jasmine2/build/queueRunner.js:73:41

:no_entry_sign:

🃏 FAIL in index.test.js

shows user avatar

Expected the element to have attribute<EMAIL_ADDRESS>received: src="user-placeholder.jpg"

Full message

Error: expect(element).toHaveAttribute("src"<EMAIL_ADDRESS>// element.getAttribute("src") ===<EMAIL_ADDRESS>Expected the element to have attribute:
<EMAIL_ADDRESS>Received:
src="user-placeholder.jpg"
at Object. (/home/runner/work/surveyor/surveyor/src/tests/components/Sidebar/index.test.js:27:23)

shows user name and avatar in the menu

Expected the element to have attribute<EMAIL_ADDRESS>received: src="user-placeholder.jpg"

Full message

Error: expect(element).toHaveAttribute("src"<EMAIL_ADDRESS>// element.getAttribute("src") ===<EMAIL_ADDRESS>Expected the element to have attribute:
<EMAIL_ADDRESS>Received:
src="user-placeholder.jpg"
at Object. (/home/runner/work/surveyor/surveyor/src/tests/components/Sidebar/index.test.js:42:22)

  Generated by :no_entry_sign: dangerJS against d486c2b6de7536acb4504c1ec821d752f8309699

Fails

:no_entry_sign:

🃏 FAIL in details.test.js

renders the user image of sidebar

Expected the element to have attribute: src="user-placeholder.jpg", received: null

Full message

Error: expect(element).toHaveAttribute("src", "user-placeholder.jpg") // element.getAttribute("src") === "user-placeholder.jpg"
Expected the element to have attribute:
src="user-placeholder.jpg"
Received:
null
at Object. (/home/runner/work/surveyor/surveyor/src/tests/screens/Home/details.test.js:45:18)
at Object.asyncJestTest (/home/runner/work/surveyor/surveyor/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:102:37)
at /home/runner/work/surveyor/surveyor/node_modules/jest-jasmine2/build/queueRunner.js:43:12
at new Promise ()
at mapper (/home/runner/work/surveyor/surveyor/node_modules/jest-jasmine2/build/queueRunner.js:26:19)
at /home/runner/work/surveyor/surveyor/node_modules/jest-jasmine2/build/queueRunner.js:73:41

:no_entry_sign:

🃏 FAIL in index.test.js

shows user avatar

Expected the element to have attribute<EMAIL_ADDRESS>received: src="user-placeholder.jpg"

Full message

Error: expect(element).toHaveAttribute("src"<EMAIL_ADDRESS>// element.getAttribute("src") ===<EMAIL_ADDRESS>Expected the element to have attribute:
<EMAIL_ADDRESS>Received:
src="user-placeholder.jpg"
at Object. (/home/runner/work/surveyor/surveyor/src/tests/components/Sidebar/index.test.js:27:23)

shows user name and avatar in the menu

Expected the element to have attribute<EMAIL_ADDRESS>received: src="user-placeholder.jpg"

Full message

Error: expect(element).toHaveAttribute("src"<EMAIL_ADDRESS>// element.getAttribute("src") ===<EMAIL_ADDRESS>Expected the element to have attribute:
<EMAIL_ADDRESS>Received:
src="user-placeholder.jpg"
at Object. (/home/runner/work/surveyor/surveyor/src/tests/components/Sidebar/index.test.js:42:22)

  Generated by :no_entry_sign: dangerJS against d486c2b6de7536acb4504c1ec821d752f8309699

image

@carryall I opened an issue in the backend Repo. I'm planning to fix it next week hopefully.

image

@carryall I opened an issue in the backend Repo. I'm planning to fix it next week hopefully.


Make siege waves use a higher troop percentage

Basically the title. I.e. make the bots send their attack troops in at most two waves instead of a thousand. Without that, the higher troop limit is not always worth it.

As discussed elsewhere on here today, it seems to be to do with wall length of the castle their are attacking how many troops the AI sends at once to attack a wall. Saladin and Frederick have very little free areas of wall to attack and so the AI struggles to attack these two, as they only send small groups of troops at once to attack the walls.

And that's true. Had a long discussion and a lot of AIV design iteration with Udwin about that back in the days, which resulted in my Wolfs no longer having an outer moat. Fixing this without AIV-changes would be very difficult, as it would require possibly complicated code changes:

Dispatch more troops to simultaneously attack the same wall segments.
Or dispatch remaining troops to destroy the surrounding economy in the mean time.
Or do both.

Or dispatch remaining troops to destroy the surrounding economy in the mean time.

I think Richard kind of does this anyway, sometime some of his siege force go off and destroy quarries outside the castle. Haven't seen many other AIs do it though with any of their siege force.

I have found the part with the wall attacking, so I will try to make the AI send less waves in the next patch version. I guess multiple units need to attack the same wall part therefore.

A point about a specific AI's tactics:
As I said in the duplicate thread that was closed, Emir sometimes sends his siege force and a large Arabian swordsmen raiding party simultaneously (which can be a big amount of Arabian swordsmen together), and it would be good if during sieges, Emir's Arabian swordsmen raids could join up with the siege force and attack walls alongside them. Between sieges it is very effective for Emir's Arabian swordsmen raids to destroy enemy quarries/mines/farms but during a siege they would be better joining up with the siege force I think.
It would also be good if Emir's Arabian swordsmen raiding parties could switch from raiding to going straight for the enemy lord if an enemy AI was weak enough to be panicking about the presence of the raiding party close to their castle. If Rat is panicking for example about a big raid of Emir's Arabian swordsmen (as he often does), it would make sense for those Arabian swordsmen to chop down the walls and go straight for the lord.


TypeError: Unable to require file: test/steps.d.ts

What are you trying to achieve?
Running a Codeconcept test suite with TypeScript and Playwright (npx codeceptjs run -f start). The error occurs even when I don't have any other file than steps.d.ts in my test directory.
What do you get instead?

Provide console output if related. Use --verbose mode for more details.

# npx codeceptjs run -f start
TypeError: Unable to require file: test/steps.d.ts
This is usually the result of a faulty configuration or import. Make sure there is a `.js`, `.json` or other executable extension with loader attached before `ts-node` available.
    at getOutput (/myworkspace/myproject/node_modules/ts-node/src/index.ts:817:17)
    at Object.compile (/myworkspace/myproject/node_modules/ts-node/src/index.ts:1111:30)
    at Module.m._compile (/myworkspace/myproject/node_modules/ts-node/src/index.ts:1224:30)
    at Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Object.require.extensions.<computed> [as .ts] (/myworkspace/myproject/node_modules/ts-node/src/index.ts:1228:12)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at /myworkspace/myproject/node_modules/mocha/lib/mocha.js:390:36

Unable to require file: test/steps.d.ts
This is usually the result of a faulty configuration or import. Make sure there is a `.js`, `.json` or other executable extension with loader attached before `ts-node` available.

TypeError:
    at getOutput (/myworkspace/myproject/node_modules/ts-node/src/index.ts:817:17)
    at Object.compile (/myworkspace/myproject/node_modules/ts-node/src/index.ts:1111:30)
    at Module.m._compile (/myworkspace/myproject/node_modules/ts-node/src/index.ts:1224:30)
    at Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Object.require.extensions.<computed> [as .ts] (/myworkspace/myproject/node_modules/ts-node/src/index.ts:1228:12)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at /myworkspace/myproject/node_modules/mocha/lib/mocha.js:390:36

Provide test source code if related

Generated steps.d.ts in the test directory:
/// <reference types='codeceptjs' />

declare namespace CodeceptJS {
  interface SupportObject {
    I: I
    current: any
  }
  interface Methods extends Playwright {}
  interface I extends WithTranslation<Methods> {}
  namespace Translation {
    interface Actions {}
  }
}

Details

CodeceptJS version: 3.0.7
NodeJS Version: v12.22.2
Operating System: Ubuntu
Playwright version: 1.12.3
Typescript version: 4.3.5
Configuration file:

require('ts-node/register')

exports.config = {
  tests: './test/*.ts',
  output: './test/output',
  helpers: {
    Playwright: {
      url: 'http://localhost:3000',
      show: true,
      browser: 'firefox',
    },
  },
  bootstrap: null,
  mocha: {},
  name: 'myproject',
  plugins: {
    pauseOnFail: {},
    retryFailedStep: {
      enabled: true,
    },
    tryTo: {
      enabled: true,
    },
    screenshotOnFail: {
      enabled: true,
    },
  },
}

I googled this error and it seems to happen when multiple files have the same same, however in my case I don't have any other file than steps.d.ts in my test directory.

Sorry, cant help with this one.


[Testing] use test reflector instead of reflector.lbry.io

Use a temporary test reflector (with head blob announce enabled) for clients to upload things to.

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

          1 Message

:book:
See http://keepachangelog.com/en/0.3.0/ for details on good changelog guidelines

  Generated by :no_entry_sign: Danger

@kaykurokawa why is this in "needs review"?


chore: bdd-spring-1576838904 to 0.0.1

chore: Promote bdd-spring-1576838904 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


🐛 Bug Report: createGitlabProjectVariableAction gets 401 Unauthorized

📜 Description
when using action gitlab:projectVariable:create out of the box i get 401 Unauthorized.
👍 Expected behavior
New Gitlab Variable should have beed created in my project
👎 Actual Behavior with Screenshots
i got 401 Unauthorized from gitlab

👟 Reproduction steps
  steps:
    - id: gitlab_var_create
      name: gitlab:projectVariable:create
      action: gitlab:projectVariable:create
      input:
        repoUrl: ${{ parameters.repoUrl }}
        token: ${{ secrets.USER_OAUTH_TOKEN }}
        projectId: ${{ parameters.peojectId }}
        key: ${{ parameters.key_name }}
        value: ${{ parameters.key_value }}
        variableType: "env_var"
        environmentScope: "*"

📃 Provide the context for the Bug.
when debugging the issue i saw that the header that was forwarded to gitlab is "PRIVATE-TOKEN" instead of "Authorization: Bearer"
was solved by changing the "token: token" to "oauthToken: token" in: https://github.com/backstage/backstage/blob/3dcc9d4e0b2d0def7db28845f11700ab6dc887da/plugins/scaffolder-backend-module-gitlab/src/actions/gitlabProjectVariableCreate.ts#L88
🖥 Your Environment
yarn run v1.22.19
OS:   Darwin 23.5.0 - darwin/arm64
node: v20.12.2
yarn: 1.22.19
cli:  0.26.10 (installed)
backstage:  1.28.3
Dependencies:
@backstage/app-defaults                                          1.5.7
@backstage/backend-app-api                                       0.7.9
@backstage/backend-common                                        0.23.2
@backstage/backend-defaults                                      0.3.3
@backstage/backend-dev-utils                                     0.1.4
@backstage/backend-openapi-utils                                 0.1.14
@backstage/backend-plugin-api                                    0.6.21
@backstage/backend-tasks                                         0.5.26
@backstage/catalog-client                                        1.6.5
@backstage/catalog-model                                         1.5.0
@backstage/cli-common                                            0.1.14
@backstage/cli-node                                              0.2.6
@backstage/cli                                                   0.26.10
@backstage/config-loader                                         1.8.1
@backstage/config                                                1.2.0
@backstage/core-app-api                                          1.13.0
@backstage/core-compat-api                                       0.2.6
@backstage/core-components                                       0.14.8
@backstage/core-plugin-api                                       1.9.3
@backstage/e2e-test-utils                                        0.1.1
@backstage/errors                                                1.2.4
@backstage/eslint-plugin                                         0.1.8
@backstage/frontend-plugin-api                                   0.6.6
@backstage/integration-aws-node                                  0.1.12
@backstage/integration-react                                     1.1.28
@backstage/integration                                           1.12.0
@backstage/plugin-api-docs                                       0.11.6
@backstage/plugin-app-backend                                    0.3.70
@backstage/plugin-app-node                                       0.1.21
@backstage/plugin-auth-backend-module-atlassian-provider         0.2.2
@backstage/plugin-auth-backend-module-aws-alb-provider           0.1.13
@backstage/plugin-auth-backend-module-azure-easyauth-provider    0.1.4
@backstage/plugin-auth-backend-module-bitbucket-provider         0.1.4
@backstage/plugin-auth-backend-module-cloudflare-access-provider 0.1.4
@backstage/plugin-auth-backend-module-gcp-iap-provider           0.2.16
@backstage/plugin-auth-backend-module-github-provider            0.1.18
@backstage/plugin-auth-backend-module-gitlab-provider            0.1.18
@backstage/plugin-auth-backend-module-google-provider            0.1.18
@backstage/plugin-auth-backend-module-guest-provider             0.1.7
@backstage/plugin-auth-backend-module-microsoft-provider         0.1.16
@backstage/plugin-auth-backend-module-oauth2-provider            0.2.2
@backstage/plugin-auth-backend-module-oauth2-proxy-provider      0.1.14
@backstage/plugin-auth-backend-module-oidc-provider              0.2.2
@backstage/plugin-auth-backend-module-okta-provider              0.0.14
@backstage/plugin-auth-backend-module-onelogin-provider          0.1.2
@backstage/plugin-auth-backend                                   0.22.8
@backstage/plugin-auth-node                                      0.4.16
@backstage/plugin-auth-react                                     0.1.3
@backstage/plugin-catalog-backend-module-gitlab-org              0.0.4
@backstage/plugin-catalog-backend-module-gitlab                  0.3.20
@backstage/plugin-catalog-backend-module-scaffolder-entity-model 0.1.19
@backstage/plugin-catalog-backend                                1.23.2
@backstage/plugin-catalog-common                                 1.0.24
@backstage/plugin-catalog-graph                                  0.4.6
@backstage/plugin-catalog-import                                 0.12.0
@backstage/plugin-catalog-node                                   1.12.3
@backstage/plugin-catalog-react                                  1.12.1
@backstage/plugin-catalog                                        1.21.0
@backstage/plugin-devtools-backend                               0.3.7
@backstage/plugin-devtools-common                                0.1.10
@backstage/plugin-devtools                                       0.1.15
@backstage/plugin-events-node                                    0.3.7
@backstage/plugin-kubernetes-backend                             0.18.2
@backstage/plugin-kubernetes-common                              0.8.0
@backstage/plugin-kubernetes-node                                0.1.15
@backstage/plugin-kubernetes-react                               0.4.0
@backstage/plugin-kubernetes                                     0.11.11
@backstage/plugin-org                                            0.6.26
@backstage/plugin-permission-backend-module-allow-all-policy     0.1.18
@backstage/plugin-permission-backend                             0.5.45
@backstage/plugin-permission-common                              0.7.14
@backstage/plugin-permission-node                                0.7.32
@backstage/plugin-permission-react                               0.4.23
@backstage/plugin-proxy-backend                                  0.5.2
@backstage/plugin-scaffolder-backend-module-azure                0.1.13
@backstage/plugin-scaffolder-backend-module-bitbucket-cloud      0.1.11
@backstage/plugin-scaffolder-backend-module-bitbucket-server     0.1.11
@backstage/plugin-scaffolder-backend-module-bitbucket            0.2.11
@backstage/plugin-scaffolder-backend-module-gerrit               0.1.13
@backstage/plugin-scaffolder-backend-module-gitea                0.1.11
@backstage/plugin-scaffolder-backend-module-github               0.3.2
@backstage/plugin-scaffolder-backend-module-gitlab               0.4.3
@backstage/plugin-scaffolder-backend                             1.22.11
@backstage/plugin-scaffolder-common                              1.5.3
@backstage/plugin-scaffolder-node                                0.4.7
@backstage/plugin-scaffolder-react                               1.9.0
@backstage/plugin-scaffolder                                     1.22.0
@backstage/plugin-search-backend-module-catalog                  0.1.27
@backstage/plugin-search-backend-module-techdocs                 0.1.26
@backstage/plugin-search-backend-node                            1.2.26
@backstage/plugin-search-backend                                 1.5.13
@backstage/plugin-search-common                                  1.2.12
@backstage/plugin-search-react                                   1.7.12
@backstage/plugin-search                                         1.4.12
@backstage/plugin-signals-react                                  0.0.4
@backstage/plugin-techdocs-backend                               1.10.8
@backstage/plugin-techdocs-module-addons-contrib                 1.1.11
@backstage/plugin-techdocs-node                                  1.12.7
@backstage/plugin-techdocs-react                                 1.2.5
@backstage/plugin-techdocs                                       1.10.6
@backstage/plugin-user-settings-common                           0.0.1
@backstage/plugin-user-settings                                  0.8.8
@backstage/release-manifests                                     0.0.11
@backstage/test-utils                                            1.5.7
@backstage/theme                                                 0.5.6
@backstage/types                                                 1.1.1
@backstage/version-bridge                                        1.0.8
✨  Done in 2.92s.
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

Hi @chkp-benzy, thanks for opening an issue.
Just to confirm, was it working before or is this the first time you are trying to use this module?
I'm asking because it appears this action was created to only work with personal tokens and a private-token header is expected to be set for this type of token:
https://github.com/jdalrymple/gitbeaker/blob/1d1e2e354cd55d4776bc73d70b16091cea1d679d/packages/requester-utils/src/BaseResource.ts#L122-L132
My recommendation would be to add a module configuration so that you can specify the AuthToken alternatively as well.  What do you think @backstage/scaffolder-maintainers ?

Hi @camilaibs ,
I believe the problem is in the way the action instantiates the GitLab Client. Here the client is directly instantiated . If we use this wrapper,  the type of token gets sorted out (id token or personal token) ...

Thanks @elaine-mattos sounds like a great idea, thanks for the quick response 🙌🏻

Hi @camilaibs ,
I have submitted a PR, could you please take a look?  😊
I have also realized there are other GitLab actions in the same situation and that some of them are using the @gitbeaker/node
library that has already been deprecated. I would also take a look at these other actions if I can find some time 😅.

Hi @camilaibs, thanks everyone for the quick response :)
Its the first time i'm trying to use this module,
and for my use-case the AuthToken is needed.

Closing this as fixed in @elaine-mattos' PR! :tada:


[SPARK-17303] Added spark-warehouse to dev/.rat-excludes

What changes were proposed in this pull request?
Excludes the spark-warehouse directory from the Apache RAT checks that src/run-tests performs. spark-warehouse is created by some of the Spark SQL tests, as well as by bin/spark-sql.
How was this patch tested?
Ran src/run-tests twice. The second time, the script failed because the first iteration
Made the change in this PR.
Ran src/run-tests a third time; RAT checks succeeded.

Can one of the admins verify this patch?

Jenkins, this is ok to test.

Test build #64608 has started for PR 14870 at commit 850261f.

Test build #64608 has finished for PR 14870 at commit 850261f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64608/
Test PASSed.

Merged to master. Thanks!


testing on-demand-isr

Hey sorry for the inconvenience, testing things on your issue :)
test the speed of revalidating on demand ISR, and if it have the issue of out of sync with pagination on page

Hey sorry for the inconvenience again, testing things on your issue :)
test the speed of revalidating on demand ISR, and if it have the issue of out of sync with pagination on page
2


Add about tab to sidebarVC, with info on team, CUAppDev, and links

https://github.com/cuappdev/tempo/issues/54

Let's add "About" as the navigation bar title and make the tempo logo a little bigger.

Ok I'll comment when I make all the changes

Alright, made the changes. The links should have been clickable before the changes, and I added "Leads" to the team because I wasn't sure where to put people.

Looks good!

Joe is on backend

^ oh right, good catch

Ok I'll fix it and then merge it in!


Postgresql active schema should modify search_path

When opening a sql editor in order to get content assist I need to activate one of the schemas in the database. But when I try to run a query created using content assist, it will fail because my search_path by default points to public only.
This may cause the odd situation that my content assist uses one schema and my queries run on a different one.
I believe that the active schema and the search_path of the sql editor should be connected.
when activating a schema please change the search_path to active_schema,public.
Or at least when opening a new sql editor, by default set its search_path to active_schema,public.

That's odd.
DBeaver updates search_path whenever you switch active schema (using navigator context menu).
What version do you use?

I'm using dbeaver 3.6.7 and postgresql 9.5.
I'll give you an example on how to reproduce my exact problem.

connect to a pg database
open new editor, this should by default have search_path=public, since no schema is selected as active.
run the following sql:

create schema mytest;
create table mytest.mytable (
    id int
);

close the editor
refresh the database (so that the new schema can be seen)
set the mytest schema as active
open a new editor
perform the following queries:

as you can see the search_path is set to public only although I've created a new sql editor when a schema was set to active.

Yep, this happens when you reopen SQL editor (DBeaver opens a separate connection and doesn't set search path for it).
Thanks for report.


inconsistency in sharing URLs

TLDR: sharing URLs from safari works, but it doesn't from the website itself (i guess that uses navigator.share(...))
app.config.js
[
	"expo-share-extension",
	{
		height: 700,
		activationRules: [
			{ type: "url" },
			{ type: "text" },
			{ type: "image" },
			{ type: "video" },
		],
		backgroundColor: {
			red: 255,
			green: 255,
			blue: 255,
			alpha: 0,
		},
		preprocessingFile: "./ShareExtension/preprocess.js",
		excludedPackages: [
			"expo-font",
			"expo-updates",
			"expo-dev-client",
			"expo-splash-screen",
		],
	},
]

https://github.com/MaxAst/expo-share-extension/assets/60462284/52ce623a-6196-4691-acbb-6ef91cad5591

figured the preprocessing.js file and it's activation rule clashes with activationRules: [{ type: "url" }]. dropped the file and everything works now.

glad you resolved it! I actually mention this in the README, but should probably throw an error during prebuild (or filter out the url activation rule if a preprocessing file exists


Cloud Variable IndexError: list index out of range

Traceback (most recent call last):
File "main.py", line 26, in
variable_value = variables.get_cloud_variable_value(variable_name='Name')[0]  # Get the variable value
IndexError: list index out of range

Maybe that variable has no value... Try setting the cloud variable...

Can you share the code so that I can figure out the problem?

Usually when I've ran into this problem there just isn't any data for the cloud variable. Like he said, either try recreating the cloud variable or setting data to it (probably in Scratch).

Usually when I've ran into this problem there just isn't any data for the cloud variable. Like he said, either try recreating the cloud variable or setting data to it (probably in Scratch).

Yes

Closing this issue...


Restore Browser Compatibility

Versions >v0.4.0 are not browser compatible.
Trust assumptions are non-fungible for contracts on permissionless chains, and self-relaying is the most obvious solution.
See:

https://github.com/DA0-DA0/dao-dao-ui/issues/885
https://github.com/game-of-nfts/gon-evidence/issues/479

Hey @mccallofthewild, it's a lot of text in the linked issues.
What exactly is not working in browsers that is working in node.js? What do you do? What errors do you have?

If there is anything wrong with browser support, please create a specific issue with details of the problem. In general, it is expected that ts-relayer works in browsers. Closing for now.


Fix leak if duplicated static metadata

Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=2740

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Windows: #11383
All other failure are testing infra problems


SegFault when drawing text

MacOS 14.0 (ARM64)
Julia 1.9.3
I've tried multiple examples, and all crash with a seg fault (11) when calling either, TTF_RenderUTF8_Blended(), TTF_RenderText_Solid(), and TTF_RenderUNICODE_Solid().
Sample Code:
using SimpleDirectMediaLayer
using SimpleDirectMediaLayer.LibSDL2
using SDL2_ttf_jll

function flip(renderer::Ptr{SDL_Renderer})
	SDL_RenderPresent(renderer)
	SDL_PumpEvents()
	SDL_SetRenderDrawColor(renderer, 0, 0, 0, 255)
	SDL_RenderClear(renderer)
end

SDL_GL_SetAttribute(SDL_GL_MULTISAMPLEBUFFERS, 16)			# the number of multisample anti-aliasing buffers.
SDL_GL_SetAttribute(SDL_GL_MULTISAMPLESAMPLES, 16)			# the number of samples used around the current pixel used for multisample anti-aliasing

@assert SDL_Init(SDL_INIT_EVERYTHING) == 0 "error initializing SDL: $(unsafe_string(SDL_GetError()))"
@assert TTF_Init() == 0 "error initializing TTF_Init: $(unsafe_string(SDL_GetError()))"

winPtr = SDL_CreateWindow("Game", SDL_WINDOWPOS_CENTERED, SDL_WINDOWPOS_CENTERED, 1000, 1000, SDL_WINDOW_SHOWN)

renderer = SDL_CreateRenderer(winPtr, -1, SDL_RENDERER_ACCELERATED | SDL_RENDERER_PRESENTVSYNC)

mRect = SDL_Rect(250, 150, 200, 200)
SDL_RenderFillRect( renderer, Ref{SDL_Rect}(mRect))		# that addition mess lets me send the rect as a pointer to the rect
flip(renderer)
SDL_Delay(1000)

Sans = TTF_OpenFont("Sans.ttf", 24);
White = SDL_Color(255, 255, 255, 255)
sf = TTF_RenderUTF8_Blended(Sans, "hello world", White)
flip(renderer)

It crashes right at TTF_RenderUTF8_Blended. Crash sample:
[47951] signal (11.2): Segmentation fault: 11
in expression starting at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/debugger/run_debugger.jl:10
TTF_SizeUTF8_Internal at /Users/BobsAccount/.julia/artifacts/f4b1701fba3f3038f437274c8d136772963cd9ec/lib/libSDL2_ttf-2.0.0.dylib (unknown line)
TTF_RenderUTF8_Blended at /Users/BobsAccount/.julia/artifacts/f4b1701fba3f3038f437274c8d136772963cd9ec/lib/libSDL2_ttf-2.0.0.dylib (unknown line)
##compiled_ccall#304 at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/optimize.jl:346
unknown function (ip: 0x28e754067)
ijl_apply_generic at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
jl_f__call_in_world at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
ijl_apply_generic at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
do_apply at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
#invoke_in_world#3 at ./essentials.jl:853
ijl_apply_generic at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
do_apply at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
invoke_in_world at ./essentials.jl:850
ijl_apply_generic at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
do_apply at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
bypass_builtins at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/interpret.jl:195
#evaluate_call_recurse!#65 at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/interpret.jl:222
evaluate_call_recurse! at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/interpret.jl:220 [inlined]
eval_rhs at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/interpret.jl:393
step_expr! at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/interpret.jl:557
step_expr! at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/interpret.jl:607
finish! at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/commands.jl:14
finish_and_return! at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/commands.jl:30
#evaluate_call_recurse!#65 at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/interpret.jl:260
evaluate_call_recurse! at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/interpret.jl:220 [inlined]
eval_rhs at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/interpret.jl:393
step_expr! at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/interpret.jl:552
step_expr! at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/interpret.jl:607 [inlined]
next_until! at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/commands.jl:92
_next_line! at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/commands.jl:181 [inlined]
next_line! at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/commands.jl:176
#debug_command#86 at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/commands.jl:467
debug_command at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/JuliaInterpreter/src/commands.jl:448
jfptr_debug_command_1033 at /Users/BobsAccount/.julia/compiled/v1.9/VSCodeDebugger/xYOi8_cFusM.dylib (unknown line)
ijl_apply_generic at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
jl_f__call_latest at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
#invokelatest#2 at ./essentials.jl:819 [inlined]
invokelatest at ./essentials.jl:816 [inlined]
our_debug_command at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/DebugAdapter/src/debugger_core.jl:67
startdebug at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/DebugAdapter/src/packagedef.jl:108
startdebugger at /Users/BobsAccount/.vscode/extensions/julialang.language-julia-1.61.2/scripts/packages/VSCodeDebugger/src/VSCodeDebugger.jl:43
unknown function (ip: 0x11309445f)
ijl_apply_generic at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
do_call at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
eval_body at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
jl_interpret_toplevel_thunk at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
jl_toplevel_eval_flex at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
jl_toplevel_eval_flex at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
ijl_toplevel_eval_in at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
eval at ./boot.jl:370 [inlined]
include_string at ./loading.jl:1903
ijl_apply_generic at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
_include at ./loading.jl:1963
include at ./Base.jl:457
jfptr_include_29526 at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/sys.dylib (unknown line)
ijl_apply_generic at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
exec_options at ./client.jl:307
_start at ./client.jl:522
jfptr__start_51456 at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/sys.dylib (unknown line)
ijl_apply_generic at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
true_main at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
jl_repl_entrypoint at /Applications/Julia-1.9.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.9.dylib (unknown line)
Allocations: 9495066 (Pool: 9487246; Big: 7820); GC: 13

Strangely, I can get GameZero to work and draw text, and I've audited their function calls, and they look identical to mine, yet it does not crash.

Mea culpa: I never noticed that the pointer to the font was null.  It turns out that the file path in VScode was pointing to the wrong folder, and so the font was never loaded.


Update autothread and stars

This PR adds typehinting in autothread.py and updates stars.py for code consistency across other cogs as well as adds typehinting.

You should be removing type annotations where they are unnecessary, not adding more

For prs like this, I'd recommend actually turning on your type checker so it tells you stuff like that cog annotation isn't meant to pass to the cog init

First time doing this huh, everything should be resolved now.
Appreciate the input (and if more)!


fix: tsconfig paths are not expanded correctly for tsconfigs and libs not placed at workspace root (#499)

Fix #499
Test plan

Covered by existing test cases
New test cases added

General
This fix ensures, that if an expanded import path like specified in the corresponding tsconfig.json (of a file which for example lays in the following space /projects/p1) is not absolute e.g. @org/liba/* -> ./*: @org/liba/test will be expanded to projects/p1/test. Otherwise gazelle has issues resolving the correct imports.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @joelMuehlena,
Thanks for your help with relative imports in Clover. They're working great with baseUrl and paths, but I'm running into an issue where they don't work with just baseUrl alone. Here's a codesandbox with the issue (basic ts setup without bazel): https://codesandbox.io/s/practical-architecture-wlft6z?file=/src/App.tsx:0-31
Could you please add support for baseUrl-alone as well? That would be a huge help!
Thanks again

Hi @xc2,
I looked into your codesandbox & request and made some changes. Maybe you can have a look if those changes are reflecting your request.

@jbedard this should be everything. Maybe you can have a look at it, when you have the time?

A bunch of minor comments but overall looks great! Could merge as-is but if you have time to address or reply to the comments that would be great 👍

Yep no problem, I'll take a look on the review this week when I have some time.

Hi @xc2, I looked into your codesandbox & request and made some changes. Maybe you can have a look if those changes are reflecting your request.

Thank you, it works as expected!

Thanks, we brought the PR into our monorepo and exporting again in https://github.com/aspect-build/aspect-cli/pull/502


Implement basic sentiment analyzer

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #1

PR #2

PR #3

PR #4   👈

This stack of pull requests is managed by Graphite.

Merge activity

Jan 27, 7:47 AM: @raulfrk started a stack merge that includes this pull request via Graphite.


Fix a test hole for ref_backend, i.e. finufft

Currnetly in:
https://github.com/mind-inria/mri-nufft/blob/71f1cf0c781210b35907e8686a9b4b8dfc522b98/tests/conftest.py#L84-L87
This was added originally to ensure we dont blow up the number of tests, however, we seem to be missing some basic tests with finufft like test_batch and test_autodiff which was seen in #139 .
In #139, only closing this, the issue turned to be more complicated, with a lot of failures (some handeled in #139) and also a lot of extra tests running (for example finufft tests in cufinufft.
To fix this, we might need to rediscuss our strategy on how to tackle it.

We need to also fix https://github.com/mind-inria/mri-nufft/pull/139#discussion_r1656766312 also here.


Update exposures.md - missing version in example

Example exposure YAML file is the missing version. The existing sample on this page results in an error. Adding the version: 2 line fixes it.
Description & motivation

To-do before merge

Prerelease docs
If this change is related to functionality in a prerelease version of dbt (delete if not applicable):

[ ] I've added versioning components, as described in "Versioning Docs"
[ ] I've added a note to the prerelease version's Migration Guide

Checklist
If you added new pages (delete if not applicable):

[ ] The page has been added to website/sidebars.js
[ ] The new page has a unique filename

If you removed existing pages (delete if not applicable):

[ ] The page has been removed from website/sidebars.js
[ ] An entry has been added to _redirects

Thank you for contributing to the dbt product docs! This issue has been fixed in a different PR, but if you see anything else in the Exposures docs, then you can open a new PR. 🙇🏻♀


Update to logicalcluster v2

Hi @ncdc , this involves updating go.mod ?
github.com/kcp-dev/logicalcluster v2.0.0-alpha.0
I wasn't sure if I should use an alpha version here.

Hi @pradeepnnv, yes, that's what is needed for now. We'll have a newer v2.x tag of logicalcluster in the future, but for the time being, that's the one to use.

Hi @ncdc ,
I updated the go.mod as below.
diff --git a/go.mod b/go.mod
index 3823a930..6dc27c10 100644
--- a/go.mod
+++ b/go.mod
@@ -8,7 +8,7 @@ require (
        github.com/go-logr/logr v1.2.0
        github.com/go-logr/zapr v1.2.0
        github.com/kcp-dev/apimachinery v0.0.0-20220708220956-c302aeddfde7
-       github.com/kcp-dev/logicalcluster v1.1.1-0.20220705215104-8e46328c24a5
+       github.com/kcp-dev/logicalcluster/v2 v2.0.0-alpha.0
        github.com/onsi/ginkgo v1.16.5
        github.com/onsi/gomega v1.17.0
        github.com/prometheus/client_golang v1.11.0

But, most of the tests are failing when I run make test.
Please let me know if I'm doing anything wrong.

There's some work that needs to be done to get the tests functional in our fork. Feel free to open a PR and not worry about the tests for now (while we get them working again).

Fixed in #21
/close


Which notebook image to use xgboost-high-level-apis example?

Is there an existing notebook image suitable for running the example:
https://github.com/kubeflow/fairing/blob/master/examples/prediction/xgboost-high-level-apis.ipynb
I tried using
gcr.io/kubeflow-images-public/tensorflow-1.13.1-notebook-cpu:v0.5.0
But it looks like its missing some dependencies.
import argparse
import logging
import joblib
import sys
import pandas as pd
from sklearn.metrics import mean_absolute_error
from sklearn.model_selection import train_test_split
from sklearn.impute import SimpleImputer
from xgboost import XGBRegressor

I was able to work around this just by installing the modules.
!pip install joblib
!pip install pandas
!pip install scikit-learn

/cc @karthikv2k @r2d4

you have to install the requirements in https://github.com/kubeflow/fairing/blob/master/examples/prediction/requirements.txt . We didn't create a separate image for this example. We will add "!pip install -r requirements.txt" as the first cell in the notebook to let the users know they have to install the deps.


ballerina: 2201.2.2 -> 2201.3.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/ballerina/versions.
meta.description for ballerina is: "An open-source programming language for the cloud"
meta.homepage for ballerina is: ""
meta.changelog for ballerina is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2201.2.3 with grep in /nix/store/hkpxr8vlwafcyi61zlp7spbhdkjcn7px-ballerina-2201.2.3
found 2201.2.3 in filename of file in /nix/store/hkpxr8vlwafcyi61zlp7spbhdkjcn7px-ballerina-2201.2.3

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ballerina

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hkpxr8vlwafcyi61zlp7spbhdkjcn7px-ballerina-2201.2.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ballerina https://github.com/r-ryantm/nixpkgs/archive/af883bfdff286a8e9377e07f6c9d1bb034b107d8.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hkpxr8vlwafcyi61zlp7spbhdkjcn7px-ballerina-2201.2.3
ls -la /nix/store/hkpxr8vlwafcyi61zlp7spbhdkjcn7px-ballerina-2201.2.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ballerina

Maintainer pings
cc @eigengrau for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/ballerina/versions.
meta.description for ballerina is: "An open-source programming language for the cloud"
meta.homepage for ballerina is: ""
meta.changelog for ballerina is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2201.3.0 with grep in /nix/store/bk9dkrhp4wcfdw2fymr5w2f0s0a10z2v-ballerina-2201.3.0
found 2201.3.0 in filename of file in /nix/store/bk9dkrhp4wcfdw2fymr5w2f0s0a10z2v-ballerina-2201.3.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ballerina

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bk9dkrhp4wcfdw2fymr5w2f0s0a10z2v-ballerina-2201.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ballerina https://github.com/r-ryantm/nixpkgs/archive/6833d68b2992447353455c39b2d5654c6887c48d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bk9dkrhp4wcfdw2fymr5w2f0s0a10z2v-ballerina-2201.3.0
ls -la /nix/store/bk9dkrhp4wcfdw2fymr5w2f0s0a10z2v-ballerina-2201.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ballerina

Maintainer pings
cc @eigengrau for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/ballerina/versions.
meta.description for ballerina is: An open-source programming language for the cloud
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2201.3.1 with grep in /nix/store/3vvvzblhbrfb9idh786lg4yhfwkwc93x-ballerina-2201.3.1
found 2201.3.1 in filename of file in /nix/store/3vvvzblhbrfb9idh786lg4yhfwkwc93x-ballerina-2201.3.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ballerina

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3vvvzblhbrfb9idh786lg4yhfwkwc93x-ballerina-2201.3.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ballerina https://github.com/r-ryantm/nixpkgs/archive/bb8f3e8c39b71be7c4d80747900d860f58a7fbb3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3vvvzblhbrfb9idh786lg4yhfwkwc93x-ballerina-2201.3.1
ls -la /nix/store/3vvvzblhbrfb9idh786lg4yhfwkwc93x-ballerina-2201.3.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ballerina

Maintainer pings
cc @eigengrau for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/ballerina/versions.
meta.description for ballerina is: An open-source programming language for the cloud
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2201.3.2 with grep in /nix/store/qqn6fjcynvpibi15k7c9dwgxprshzd4h-ballerina-2201.3.2
found 2201.3.2 in filename of file in /nix/store/qqn6fjcynvpibi15k7c9dwgxprshzd4h-ballerina-2201.3.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ballerina

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qqn6fjcynvpibi15k7c9dwgxprshzd4h-ballerina-2201.3.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ballerina https://github.com/r-ryantm/nixpkgs/archive/ec0c425a4a9ceb0dab8fa857d31277a536a9b218.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qqn6fjcynvpibi15k7c9dwgxprshzd4h-ballerina-2201.3.2
ls -la /nix/store/qqn6fjcynvpibi15k7c9dwgxprshzd4h-ballerina-2201.3.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ballerina

Maintainer pings
cc @eigengrau for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/ballerina/versions.
meta.description for ballerina is: An open-source programming language for the cloud
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2201.4.0 with grep in /nix/store/hwh74dd2zgsaplqgcr5ivy4fpyw2mcw4-ballerina-2201.4.0
found 2201.4.0 in filename of file in /nix/store/hwh74dd2zgsaplqgcr5ivy4fpyw2mcw4-ballerina-2201.4.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ballerina

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hwh74dd2zgsaplqgcr5ivy4fpyw2mcw4-ballerina-2201.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ballerina https://github.com/r-ryantm/nixpkgs/archive/98ee15d1920db3fd3f17e230d3339cee719f9476.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hwh74dd2zgsaplqgcr5ivy4fpyw2mcw4-ballerina-2201.4.0
ls -la /nix/store/hwh74dd2zgsaplqgcr5ivy4fpyw2mcw4-ballerina-2201.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ballerina

Maintainer pings
cc @eigengrau for testing.


[FEATURE] Roll Willpower 'shortcut' button

The green buttons row below chat. Roll Willpower button rolls Willpower dice, as expected, but marks Willpower expenditure as well.
Is that an intended behaviour?

Closing this issue because it's being handled by #215


Testing the functionality of user module after integration into caravel

Hi,
How to  write  testbenches to test the functionality  of  user modules after integrating into caravel? is there any documentation available?

You can look at the user project example testbenches, the documentation can be found here.


How to make a static build

I want to run vtm on a server with a old version of libc.so only (GLIBC==2.31).
The binary release 0.9.9h does not work since it requires GLIBC>=2.34
./vtm: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by ./vtm)
./vtm: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./vtm)
./vtm: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by ./vtm)

I do not have root access to that server, so I'm not able to update libc.so there.
Instead, I tried to build a static version of vtm in my local WSL environment.
First I uncommented the line in vtm/src/CMakeLists.txt
        set (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -static-libstdc++ -static-libgcc -pthread -s")

then I ran
cmake ./src
cmake --build .

However, the built executable still requires libc.so:
ldd ./vtm
        linux-vdso.so.1 (0x00007ffff454c000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f91951c0000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f9194f90000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f9195c95000)

and still fails to launch on that server.
I tried both master and dev/sdn branch, and neither of them worked.
Is it possible to build a static vtm executable without libc.so.6 requirement?

Looks like the -static parameter is missing. I updated CMakeLists.txt/CMakeSettings.json.

It works now.
Thank you!


about search

Document description: put "search: true" in the front-matter. However, I don't understand which file "search: true" .

I've solved it. "index.md" in the "search" directory.


Add FAQ on logging SQL queries

Fixes #1066

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/816cedb52cf3b16b8d0ed21782dbad846408ef8e/


Insert Section wrapping a Resource and Children

I just spent some hours trying to create a section to group a resource (just for organization)
But, i couldnt find any option inside ResourceOptions
If i use "type: mixed", an section is created but data cant be saved
The section is also created if i create a array of billings, but i want only one
There is a way to turn this model (Mongoose)

From this UI

Into this?

Thanks

Using a Mongoose schema for shipping in the model is enough to get this to work:
  shipping: new mongoose.Schema({
    state: { type: String, required: true },
    city: { type: String, required: true },
    checkbox: Boolean
  })

Let me know if this works fo you so I can close the issue.


Add option to use yarn instead of npm for ArtifactoryNpm tasks

Is your feature request related to a problem? Please describe.
At the moment we are using yarn for a node based repo, however this means when using a the azure devops extension, and using the<EMAIL_ADDRESS>task, it will use npm. This creates an issue where we do not have a package-lock.json, but do have a yarn.lock file.
Describe the solution you'd like to see
A clear and concise description of the new feature.
Option to use yarn instead of npm for all the artifactorynpm tasks
Describe alternatives you've considered
Can do a manual npm login to Artifactory and yarn install, but then thats not using this devops extension

👍 For this. We use Artifactory + Azure DevOps + Yarn as well. I would like to use the extension to collect all of the build meta data if possible, but we can't do that and use yarn at the moment.

I, too, have a Node+React app using yarn. This would be a very welcome addition.


Revisit org switcher dropdown for admins

Problem statement
The current dropdown didn't go through design/prototyping. It is not a public-facing feature and we frequently demo from our own machines, which could be confusing for folks seeing that feature. As we continue to develop user/settings-type features, that dropdown will start colliding more with UI elements.
What you need to know
[Links to documents, workflows, or list of key people and contact info]

...

Acceptance criteria

[ ] Dropdown should either be concealable or otherwise not interfering with the top nav UI

To do

[ ] Mockup alternate ideas
[ ] Test with team
[ ] Code!

Internal feature to switch between orgs for testing; need to meet with Dev to figure out alternate implementation


⚠ Bofrost.de has degraded performance

In 6cd278f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1376 ms

Resolved: Bofrost.de performance has improved in 6fe733f after 9 minutes.


gh-r option doesn't appear to work behind a proxy.

Problem Summary

gh-r downloads don't seem to work, yet prints "Installed!".
There's no error output or verbose flags to figure out why.

    zplug "BurntSushi/ripgrep", \
        from:gh-r, \
        as:command

    # The example.
    zplug "junegunn/fzf-bin", \
        from:gh-r, \
        as:command

zplug install

results in
Installing...        junegunn/fzf-bin
Installing...        BurntSushi/ripgrep
[zplug] junegunn/fzf-bin: there are no available releases
[zplug] BurntSushi/ripgrep: there are no available releases
Installed!           junegunn/fzf-bin   (4.89s)
Installed!           BurntSushi/ripgrep (4.97s)
 ==> Installation failed for following packages:
- junegunn/fzf-bin
- BurntSushi/ripgrep
[zplug] |install| total wall-time 5.180555 sec.

And the files are not installed.
I assume proxy configuration is the problem, but my only evidence is that git required the proxy settings to work.
System Information

uname -a

Linux Debian x86_64 GNU/Linux [work details redacted]
```

zsh version

zsh 5.0.7 (x86_64-pc-linux-gnu)
```

zplug version/commit

2.3.2
```
Minimal zshrc
Create a minimal reproducing set of configurations for this issue. Please
remove all unnecessary parts!
source ~/.zplug/init.zsh

    zplug "BurntSushi/ripgrep", \
        from:gh-r, \
        as:command

    # The example.
    zplug "junegunn/fzf-bin", \
        from:gh-r, \
        as:command

zplug install

zplug load --verbose

Steps to Reproduce
Run zsh w/ the above .zshrc

Show me your proxy setting (if you can do)

# server details hidden
INTERNAL_PROXY_SERVER=http://[proxy-server]:[port]

export http_proxy=$INTERNAL_PROXY_SERVER
export https_proxy=$INTERNAL_PROXY_SERVER
export ftp_proxy=$INTERNAL_PROXY_SERVER
export all_proxy=$INTERNAL_PROXY_SERVER
export no_proxy="localhost,<IP_ADDRESS>"

This problem should have been resolved. Check latest master branch out please.
Related issues:

#296
#295


Unable to install v0.10.4

Latest version on Packagist is 0.10.3.

Released v0.10.5, made a mistake in the previous version that made it not possible to publish to packagist.
Thanks for reporting!


Add statusLink parameter to add hyperlink to status tag.

modifying to merge statuses rather than overriding, allowing consumers to override only one status while keeping others.
Add statusLink param to turn status label into a link. For example, a consumer could link to the component that replaces a deprecated one.

Anything I can do to help facilitate this going in?

Hey! Sorry for the slow review, we are up against some heavy deadlines.
Could you split out the prettier bits from the functionality? Or get prettier to read from the airbnb-typescript rules, not really a fan of these default double quote styles.
The quote updates are making it hard to quickly read through the functionality to check it makes sense as there's so many style changes.

I've added:

eslint with airbnb typescript guidelines
statusLink prop
extending default statuses

to v3.0.0
Think that covers everything so I'm going to close this one down. Thank you for your efforts though!


Added four files related to car avoidance game project (issue-368)

Related Issue

I have created a Car Avoidance Game using javaScript.

Closes: #368
Describe the changes you've made
I have added four files (Html, CSS, javascript, and an image).
The game has features like :

Score Board
Movement of cars is controlled by arrow keys
Has replay option
UI is made using Canva

Checklist:

[ Done ] My code follows the style guidelines of this project.
[ Done ] I have performed a self-review of my own code.
[ Done ] I have commented my code, particularly in hard-to-understand areas.
[ Done ] I have made corresponding changes to the documentation.
[ Done ] New and existing unit tests pass locally with my changes.

Screenshots

@ridsuteri Hey! I have changed the files. Now it has no conflicts. Have a look.

@ridsuteri Hey! I have changed the files. Now it has no conflicts. Have a look.

please add this project to script.js file as well

@ridsuteri Hey! I have added the project to script.js file as well.....It was having some conflict , so I resolved the way I knew to resolve this.

Some of the existing projects have been removed while solving the conflict. What you need to do is to accept both changes
Please fix that. What you could do whatever project you removed add them and push
if conflict occur I'll resolve no worries.

@991rajat I have added those projects which I removed earlier....Can you please resolve the conflict?

Congratulations on merging of first PR. :tada:
Keep Contributing. :smile:

@991rajat Thank you!!😊


Enable an "EdgeFlow" service

EdgeFlow is the name that we give to a feature that will be essential for accountability on EdgeNet. It will provides NetFlow-style packet header capture at each EdgeNet worker node, thereby allowing people to determine who was responsible for any packet that entered or left EdgeNet. The concept is based the PlanetFlow service that ran on PlanetLab.
EdgeFlow will register the "five-tuple" of each packet that leaves or enters each EdgeNet worker node: source IP address, source port number, destination IP address, destination port number, and transport-layer protocol. It will associate the five-tuple with the pod that is the ultimate source or destination for the packet, thereby allowing an association with the owner of the pod.
This "flow data", in the IPFIX (or NetFlow or sFlow) format, will be gathered on the worker node. Ultimately, it will need to be made available to concerned third parties that have witnessed unusual traffic. This can be done in two ways: via a website run on TCP port 80 of the worker node, or via a website run centrally by the EdgeNet administrators.
Based upon our experience running PlanetFlow on PlanetLab Europe, some combination of the two ways of presenting the EdgeFlow data is probably needed. Network administrators who witness unusual traffic will naturally look to the IP address at the source of that traffic, so a website on a worker node provides a first line response. But queries might also come to the EdgeNet administrators themselves, for whom a centralized database allows answers to be found, even when the worker node in question is no longer accessible (provided that it previously had time to offload its data).

This talk by Rastislav Szabo of PANTHEON.tech appears to be highly pertinent.
Szabo points out that in a Kubernetes deployment, the entity that plays a similar role to a router or a switch is a CNI plugin. It routes or switches the nodes between the pods on a given node, as well as between nodes. This is where the flow data can be captured.
For collection and analysis of the flow data, he suggests an ELK stack: Elasticsearch, Logstash, and Kibana. Logstash, the part that does the collection, supports IPFIX, NetFlow, and sFlow.

@bsenel which CNI do we currently use for EdgeNet?

We use Weave Net as CNI plugin.

OK, I see that Weave does not currently permit the collection of IPFIX/NetFlow/sFlow statistics:
https://github.com/weaveworks/weave/issues/3596
We should think about whether we can adopt Contiv-VPP in place of Weave.

@cscognamiglio @rickmcgeer @JustinCappos @eqfarhad @habdullah
Kindly take a look, we'll discuss tomorrow.

Following discussion with people at Cisco who have developed an FD.io VPP data plane for the Calico networking technology, we will try using the Calico CNI in place of the Weave CNI. If it works, we can envisage building on this for our EdgeFlow solution.
Notably, the folks at Cisco have already developed an IPFIX exporter for the Calico VPP data plane. Our contacts at Cisco suggest two ways in which we could build upon this:

Simultaneously collect the IPFIX flow data and the Kubernetes logs that describe the IP address of each container and associate the two.
Extend the IPFIX exporter to attach metadata concerning which container is at the origin of each packet.

We should look into the current status of IPv6 in Kubernetes and plan accordingly.

I've googled the issue so there seem to be a few steps to go from Weave to Calico. And these might cause some downtime due to the cluster configuration.
First of all, all Kubernetes objects related to Weave need to be deleted, which is so easy. Next, we need to clear all files related to Weave configuration and binaries and remove the Weave interface from the nodes. At this point, the EdgeNet cluster is ready to install Calico.
I will share the results when I make this transition in the sandbox.

I am happy to announce that Calico has officially replaced Weave in production. 🥳


Graceful shutdown

It might make sense to add shutdown hook in plugin registration method:
        override fun install(
            pipeline: Application,
            configure: RabbitMQConfiguration.() -> Unit
        ): RabbitMQ {
            pipeline.environment.monitor.subscribe(ApplicationStopped){
                // Gracefully stop RabbitMQ here
            }

I'll give it a try 👀

@JUtupe Actually, better approach would be to implement Closeable interface for the RabbitMQ plugin class. Then ktor will automatically call the disposal logic on shutdown.

I've been scratching my head over any test case that would help me with implementation, but I don't really know how to check if shutdown was "graceful". Can you provide an example test case @kibertoad? That would help me a lot!

@JUtupe You can try calling  this.application.dispose() in test and then try firing an event; it should fail because connection should be already destroyed.