Module
Core
Testcontainers version
1.17.3
Using the latest Testcontainers version?

Fails to start with exception  with exception NoClassDefFoundError (Could not initialize class com.github.dockerjava.transport.DomainSocket)
Newest version used.
Java 11.0.15-zulu arm.
Relevant log output
2022-07-13 09:45:52,656 [Test worker] DEBUG o.t.j.ContainerDatabaseDriver - Container not found in cache, creating new instance
    2022-07-13 09:45:52,689 [Test worker] DEBUG o.t.u.TestcontainersConfiguration - Testcontainers configuration overrides will be loaded from file:/Users/jglapa/.testcontainers.properties
    2022-07-13 09:45:52,695 [Test worker] INFO o.t.u.ImageNameSubstitutor - Image name substitution will be performed by: DefaultImageNameSubstitutor (composite of 'ConfigurationFileImageNameSubstitutor' and 'PrefixingImageNameSubstitutor')
    2022-07-13 09:45:52,740 [Test worker] INFO o.t.d.DockerClientProviderStrategy - Loaded org.testcontainers.dockerclient.UnixSocketClientProviderStrategy from ~/.testcontainers.properties, will try it first
    2022-07-13 09:45:52,741 [Test worker] DEBUG o.t.d.DockerClientProviderStrategy - Trying out strategy: UnixSocketClientProviderStrategy
    2022-07-13 09:45:53,242 [Test worker] INFO o.a.c.c.C.[.[.[/] - Initializing Spring embedded WebApplicationContext
    2022-07-13 09:45:53,504 [Test worker] INFO o.t.d.DockerClientProviderStrategy - Loaded org.testcontainers.dockerclient.UnixSocketClientProviderStrategy from ~/.testcontainers.properties, will try it first
    2022-07-13 09:45:53,505 [Test worker] DEBUG o.t.d.DockerClientProviderStrategy - Trying out strategy: UnixSocketClientProviderStrategy
    2022-07-13 09:45:53,506 [Test worker] DEBUG o.t.d.DockerClientProviderStrategy - UnixSocketClientProviderStrategy: failed with exception NoClassDefFoundError (Could not initialize class com.github.dockerjava.transport.DomainSocket)
    2022-07-13 09:45:53,508 [Test worker] INFO o.t.d.DockerMachineClientProviderStrategy - docker-machine executable was not found on PATH ([..redacted...])
    2022-07-13 09:45:53,508 [Test worker] ERROR o.t.d.DockerClientProviderStrategy - Could not find a valid Docker environment. Please check configuration. Attempted configurations were:
    2022-07-13 09:45:53,508 [Test worker] ERROR o.t.d.DockerClientProviderStrategy -     UnixSocketClientProviderStrategy: failed with exception NoClassDefFoundError (Could not initialize class com.github.dockerjava.transport.DomainSocket)
    2022-07-13 09:45:53,508 [Test worker] ERROR o.t.d.DockerClientProviderStrategy - As no valid configuration was found, execution cannot continue

Additional Information

2960 +--- org.testcontainers:postgresql:1.17.3
2961 |    --- org.testcontainers:jdbc:1.17.3
2962 |         --- org.testcontainers:database-commons:1.17.3
2963 |              --- org.testcontainers:testcontainers:1.17.3
2964 |                   +--- junit:junit:4.13.2 ()
2965 |                   +--- org.slf4j:slf4j-api:1.7.36
2966 |                   +--- org.apache.commons:commons-compress:1.21
2967 |                   +--- org.rnorth.duct-tape:duct-tape:1.0.8
2968 |                   |    --- org.jetbrains:annotations:17.0.0
2969 |                   +--- com.github.docker-java:docker-java-api:3.2.13
2970 |                   |    +--- com.fasterxml.jackson.core:jackson-annotations:2.10.3 -> 2.13.3 ()
2971 |                   |    --- org.slf4j:slf4j-api:1.7.30 -> 1.7.36
2972 |                   --- com.github.docker-java:docker-java-transport-zerodep:3.2.13
2973 |                        +--- com.github.docker-java:docker-java-transport:3.2.13
2974 |                        +--- org.slf4j:slf4j-api:1.7.25 -> 1.7.36
2975 |                        --- net.java.dev.jna:jna:5.8.0

seems like problem goes away when switching to java11 amd64 e.g. (11.0.2-openjdk)

Are you sure that the actual runtime classpath contains an up-to-date version of JNA?

any suggestion how could I verify that at runtime? Gradle dependency check claims its 5.8.0

Hi everyone, any update here?
Thanks!

Still experiencing this mac m1 using testcontainers-java:1.17.3 and jna:5.5.0, Tried upgrade to jna:5.12.1 and seem to work.
...
  <dependency>
    <groupId>org.testcontainers</groupId>
    <artifactId>testcontainers</artifactId>
    <scope>test</scope>
    <exclusions>
      <exclusion>
	  <groupId>net.java.dev.jna</groupId>
	  <artifactId>jna</artifactId>
      </exclusion>
    </exclusions>
  </dependency>
  <dependency>
    <groupId>net.java.dev.jna</groupId>
    <artifactId>jna</artifactId>
    <version>5.12.1</version>
    <scope>test</scope>
  </dependency>
...

@jglapa run ./gradlew dependencies or that's what you mean by Gradle dependency check claims its 5.8.0

Closing due to there is no answer. @jglapa feel free to reopen this issue.

sorry, the notification got lost somehow, we worked around the issue by forcing JNA to later version with:
...
    implementation 'net.java.dev.jna:jna'
    constraints {
        implementation('net.java.dev.jna:jna:5.12.1') {
            because '5.8 and 5.11 cause errors on Apple - M1'
        }
    }
...


Add collaborators to this repo

Comment below to be added as a collaborator
We will all be using this repository today. Even though it's public right now, you will not be able to make changes until you're given the correct permissions. We've automated this process via the GitHub API. Once you comment, we will add you as a collaborator.
You'll start to receive a lot of emails. (❗) You can slow these down immediately by clicking the Unwatch button at the top of the page and selecting either the Participating and @mentions or Ignore option.

This is a massive issue, I'm really concerned about it.

Hello!!

Add a comment

Thank you.

Hi

Hello!  Thanks for the course.

Demanding to make me a collaborator

Piling up another comment

In this!

comment

Demanding to make me a collaborator

so needy

I am here!!! sorry

hello!

Hi

Hi there!


Attached is a log of the errors.  Please ensure that you run Vim 7/8 (and not regular Vi)


Uncaught TypeError: Cannot read property 'postMessage' of undefined     at test.php:8

Hi,
I'm getting error as "Uncaught TypeError: Cannot read property 'postMessage' of undefined"
when calling from url where the response is inside php as,

in RN:
return ( <View style = {{flex: 1}} >
<WebView source = {{uri: url/test.php}}
startInLoadingState={true}
onLoadStart={() => {console.log("LOAD START");}}
onLoadEnd={() => {console.log("LOAD END ");}}
onMessage = {
event => {
const { getData } = event.nativeEvent.data
console.log('handle message : ', getData)
alert(getData);
}
}
/>
   );
Response:
handle message :  undefined
Error:
Uncaught TypeError: Cannot read property 'postMessage' of undefined
at test.php:8
Environment:

react-native-cli: 2.0.1
react-native: 0.59.8
react-native-webview version: 5.10.0
react-native-gesture-handler: 1.2.2

Same issue here

Hi, i got into trouble with the same issue, finally i resolve this issue.
It's totally the window scope problem, plz make ensure you window is the window, so do not test this sdk in iframe(such as jsbin.com).

Hi, i got into trouble with the same issue, finally i resolve this issue.
It's totally the window scope problem, plz make ensure you window is the window, so do not test this sdk in iframe(such as jsbin.com).

Means? can you show it some example!

const html = `

<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width">
  <title>JS Bin</title>
</head>
<body>
  <button id="btn">Test +1</button>

  <script>
    document.getElementById('btn').onclick = () => {
      window.ReactNativeWebView.postMessage('msg from the webview');
    }
  </script>
</body>
</html>
`

const App = () => {
  return (
    <SafeAreaView style={{ flex: 1 }}>
      <WebView
        style={{ height: 300, width: '100%' }}
        source={{ html: html }}
        onMessage={event => {
          console.log(event.nativeEvent.data)
        }}
      />
    </SafeAreaView>
  )
}

I just test the sample code by using source html props.
My env is 0.60.3,and the latest webview version.


Pass correlation ID in auth adapter

Not to self: This should be adapted. Instead of putting the correlation ID into the response manually, rely on the middleware that will be soon provided in the service-commons lib.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

4 of 5 (80.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 89.333%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/auth_service/main.py
2
3
66.67%

Totals

Change from base Build<PHONE_NUMBER>8:
0.02%

Covered Lines:
1968

Relevant Lines:
2203

💛  - Coveralls

Closed in favor of #109 which makes use of the feature being provided by the service commons now.


impl.hpp - add an explicit flags cast in receiveMessage()

Some compilers like gcc 5.3 don't manage to determine the correct overload, so we need this explicit cast.
| In file included from build/release/.moc/../../../../../trunk/UI/BizMQ/nzmqt/nzmqt.hpp:553:0,
|                  from build/release/.moc/moc_nzmqt.cpp:9:
| ../../trunk/UI/BizMQ/nzmqt/impl.hpp: In member function 'bool nzmqt::ZMQSocket::receiveMessage(nzmqt::ZMQMessage*, nzmqt::ZMQSocket::ReceiveFlags)':
| ../../trunk/UI/BizMQ/nzmqt/impl.hpp:207:29: error: call of overloaded 'recv(nzmqt::ZMQMessage*&, nzmqt::ZMQSocket::ReceiveFlags&)' is ambiguous
|      return recv(msg_, flags_);
|                              ^
| In file included from build/release/.moc/../../../../../trunk/UI/BizMQ/nzmqt/nzmqt.hpp:32:0,
|                  from build/release/.moc/moc_nzmqt.cpp:9:
| ../../trunk/daemons/libs/zmq.hpp:633:23: note: candidate: size_t zmq::socket_t::recv(void*, size_t, int)
|          inline size_t recv (void buf_, size_t len_, int flags_ = 0)
|                        ^
| ../../trunk/daemons/libs/zmq.hpp:643:21: note: candidate: bool zmq::socket_t::recv(zmq::message_t, int)
|          inline bool recv (message_t *msg_, int flags_ = 0)
|                      ^
| Makefile:487: recipe for target 'build/release/.obj/moc_nzmqt.o' failed

@mwallnoefer Thanks for reporting the issue and fix.
The source of the problem is that the default enum type of C++ is unsigned whereas the ZMQ flags are signed. Therefore, I think it might be a better solution to specify the enum type as int.
Can you please check if enum ReceiveFlags: int works for gcc 5.3.

The interesting is that with Qt 5.6 this worked WITHOUT cast. But now with Qt 5.9 things changed so I guess that the implementation of QEnum differs between the two releases. The compiler (gcc 5.3) remained the same.
Regarding the enum typing: when we put it on the ReceiveFlags I would add it also elsewhere to SendFlags etc.

Okay, that's interesting. Q_ENUMS should just register the enum into the Qt meta object system. Clang also gives a warning.
Yes, good idea. It makes sense to specify the types of all enums in nzmqt which represent flags.

fine so?

Yes, looks good.


Fixes overflow issue for 32-bit compilation

I tried switching to Int64 throughout the codebase but it quickly became a rabbit hole. A hundred billion dollars (the previous high value of the range) is a... pretty unlikely bid amount, so I used Int.max instead (which will work on either architecture). This introduces a problem if a bid exceeds $21 474 836.47 on an older device, but I don't think that's likely in the short term. @alloy it may be worth considering opening an issue to make sure this gets addressed eventually.
Fixes #1405.

This introduces a problem if a bid exceeds $21 474 836.47 on an older device, but I don't think that's likely in the short term. @alloy it may be worth considering opening an issue to make sure this gets addressed eventually.

Note that I’m fine with whatever technical solution for the build failure.
My issues with Int64 vs Int32 are purely that it’s an auction team decision, from my pov. i.e. what is the max you want to support ?, what does Gravity support ?, what do other clients support ?, etc
So if you say this is fine for now, then I’ll merge on green 👍

@acjay We could use your input here – do we expect bid amount (expressed in cents) to exceed the value stored in a 32-bit signed integer?

Closing in favour of #1421, a more technically sound solution.

That's a good point. Let's model prices as Long. In a dollars & cents auction, using 32-bit signed integers means the biggest price we can represent is ~$20M. Even though it may be a long time before we hit that point, it would be smart to not back ourselves into a corner, when the cost of going 64-bit and ensuring we never have a problem is negligible.

@acjay Thanks


Make deepcopy functionality available to copy.deepcopy

I am deep-copying models using gpflow.utilities.deepcopy. I'm also deep-copying other objects using copy.deepcopy. For simplicity, I'd like to be able to do both with copy.deepcopy. This may be possible by migrating the functionality in gpflow.utilities.deepcopy to a __deepcopy__ implementation on gpflow.base.Module. I reckon the change can be backwards compatible by then aliasing gpflow.utilities.deepcopy to copy.deepcopy
Are you willing to open a pull request?
Yes, but I don't know when as I'm pretty busy

This will be handled by tensorflow-probability's 0.12 release, which enables native deepcopy of bijectors. (See https://github.com/tensorflow/probability/pull/947#issuecomment-702403437). I just successfully tested it on tf[p]-nightly.


reactpy.run and configure(...) refactoring

Issues
Right now reactpy.run can fail in fairly unpredictable ways which give little in terms of stack traces.
Summary
This refactors the reactpy.run call stack in order allow failures that are user-readable.

Change reactpy.backends.utils.find_all_implementations() to first try to import <backend_name> before importing reactpy.backend.<backend_name>

Allows for missing sub-dependencies to not cause reactpy.run to silently fail

Import uvicorn directly within serve_with_uvicorn in order to defer import.

Allows for ModuleNotFound: Could not import uvicorn exception to tell the user what went wrong

Added CommonOptions.serve_index_route: bool

Allows us to not clutter the route patterns when it's not needed
There are real circumstances where a user might want the index route to 404

Fix bug where in-use ports are being assigned on Windows.

Removes allow_reuse_waiting_ports parameter on find_available_port()

Rename BackendImplementation to BackendProtocol
Change load order of SUPPORTED_PACKAGES so that FastAPI has a chance to run before starlette
Rename SUPPORTED_PACKAGES to SUPPORTED_BACKENDS
Refactor reactpy.backend.* code to be more human readable
Use f-strings where possible
Merge if statements where possible
Use contextlib.supress where possible
Remove defunct requirements.txt file

Checklist

[ ] Tests have been included for all bug fixes or added functionality.
[x] The changelog.rst has been updated with any significant changes.

@rmorshea npm install -g<EMAIL_ADDRESS>seems to have broken in the github workflow in the last 24 hours. Not sure why, but I tried bumping actions/setup-node version. Did not fix it.

I was planning on doing a 1.0.1 release tomorrow. Should this wait for the next release?

Yes, technically this release has an API change (BackendImplementation to BackendProtocol), so we shouldn't put this in a hotfix release.

I discovered that the reason why Flask doesn't work with uvicorn is that WsgiToAsgi does not allow non-HTTP scopes. I attempted to rewrite WsgiToAsgi but it broke a ton of other stuff.
Ref: https://github.com/miguelgrinberg/flask-sock/issues/58

@rmorshea This seems to be mergeable, but needs approval.


Detach NamespaceStore from KubeWatchApi, proper store.loadAll()

Detached NamespaceStore from KubeWatchApi
Loading all namespaces by default with KubeObjectStore.loadAll()
Added KubeObjectStore.loadSelectedNamespaces()

@Nokel81 please re-review again

@Nokel81 please re-review again

@ixrock Please rebase (and maybe even squash) this against master. It has several conflicting versions (compared to master at least) which makes it hard to review. Thanks.

rebased to https://github.com/lensapp/lens/pull/2063


Update steampipe-plugin-sdk to v1.3.1

This SDK was updated to v1.4.1 in https://github.com/turbot/steampipe-plugin-steampipe/pull/13


python310Packages.pylutron-caseta: 0.13.1 -> 0.14.0

Description of changes
https://github.com/gurumitts/pylutron-caseta/blob/dev/CHANGELOG.md#0140---2022-06-18

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

3 packages built:

home-assistant-component-tests.lutron_caseta
python310Packages.pylutron-caseta
python39Packages.pylutron-caseta


Ctr-r shuld use the current command as query as default Ctr-r do in bash

It's my implementation  on fish
  function __fzf_ctrl_r
    set -l query (commandline|string trim)
    if test -z $query
      set query ''
    else
      set query "-q $query"
    end

    history | eval (__fzfcmd) +s +m --tiebreak=index --toggle-sort=ctrl-r  $query | read -l out
    and commandline $out
    commandline -f repaint
  end

So you're suggesting we make the behavior across all three shells, right? Unfortunately I haven't been able to find a way to achieve that in bash.

I applied your patch like follow
diff --git a/shell/key-bindings.fish b/shell/key-bindings.fish
index 3d3c2a7..36cbf17 100644
--- a/shell/key-bindings.fish
+++ b/shell/key-bindings.fish
@@ -26,7 +26,14 @@ function fzf_key_bindings
   end

   function __fzf_ctrl_r
-    history | eval (__fzfcmd) +s +m --tiebreak=index --toggle-sort=ctrl-r > $TMPDIR/fzf.result
+    set -l query (commandline|string trim)
+    if test -z $query
+      set query ''
+    else
+      set query "-q $query"
+    end
+
+    history | eval (__fzfcmd) +s +m --tiebreak=index --toggle-sort=ctrl-r $query > $TMPDIR/fzf.result
     and commandline (cat $TMPDIR/fzf.result)
     commandline -f repaint
     rm -f $TMPDIR/fzf.result

But I'm getting
fish: Unknown command 'string'
~/.config/fish/functions/fish_user_key_bindings.fish (line 1): commandline|string trim

Maybe I did something wrong, I don't know fish too well.

If you are using a fish <= fish2.2.0 (not an development version like me) you have not the string builtin yet (sorry) so you can replace it:
set -l query (commandline|string trim)

with:
set -l query (commandline|xargs) #xargs alone do the trimming work

I noticed the patch doesn't work with non-trivial string on the command prompt.
e.g. seq 10 | wc -l<CTRL-R> or echo $PATH<CTRL-R>

It looks as  you are using too much evals, I'll rewrite the fish scripts removing some of them (maybe all) and do a pull request.


Support for FY_2x?

Is your feature request related to a problem? Please describe.
Sanchez doesn't support add false colour to FY_2x.
Describe the solution you'd like
Add support for FY_2x, including add country borders to its false colour image.
Describe alternatives you've considered
Currently it's possible to add false color to FY_2x through GeoSatSignal and CLUT, but this software only supports Windows platform. (https://github.com/eswnl/FY-2x_CLUT)
Additional context
None.

Sure thing. Do you have a sample image for me to use?
In the meantime, you should be able to add support by adding a section to the Satellites.json file - see here for details.

Of course here is one from FY_2G
https://3pfy6f-my.sharepoint.com/:i:/g/personal/bclswl0827_3pfy6f_onmicrosoft_com/EcwWTl_AQiFBu-mDAwxsdzIBwN6Bo2OpH_hfodLB6Z7NYA

Thanks! Sanchez uses regular expressions against filenames to determine which satellite configuration to use for each image. Is FY-2x a standard prefix? Or is it FY-2[A-Z]? (e.g., FY-2C, FY-2G, etc.)

Yes, FY_2x is standard prefix

Quick json file addition allows it to work, though your imagery has extra black space surrounding the earth and will have to have cropping adjusted to the json as well to properly line up everything.  the crop settings below are just copied from another geo satellite. You can clearly see where the continents don't line up.
{
   "DisplayName": "FY-2H",
   "FilenamePrefix": "FY-2x_1_",
   "FilenameParser": "Goesproc",
   "Invert": false,
   "Longitude": 79.5,
   "Brightness": 1.2,
   "Crop": [
     0.003166,
     0.089925,
     0.001166,
     0.001010
   ]

What software are you decoding with? I noticed some use the prefix  FY_2x while the file you sent has FY-2x_

SatDump :)

We can use a regex to support both prefixes. Are the filename date formats and the image alignment the same for all?
If so, all we require is more accurate crop values, as @creinemann noted above. Either you or I can work on this. You can either measure pixels or just divide and conquer.
I can then add the final config to git and create a new release.

Yes, they're same for all.

unfortunately there will be a problem for exact FY-2H crop values, as every capture has drift. Sat orbit is unstable which results in xy offset on every image

unfortunately there will be a problem for exact FY-2H crop values, as every capture has drift. Sat orbit is unstable which results in xy offset on every image

I guess there's no EXIF metadata to indicate the offset, he says optimistically...
Before I hard-coded crop values, I had code which tried to guess the crop. This approach works okay for IR images. Perhaps I should resurrect it and use it for FY-2H. May be better than nothing?


New version: Mozilla.Thunderbird.Beta version 119.0b2

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: Open in CodeFlow

Close with reason: Beta versions higher than the stable ones should not be added for now as it's causing matching errors for users on stable versions;


add tf yolo v1

 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.:x: Wayfear sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@Wayfear HI, the yolo project has passed the test and I merged it to master branch. I wonder if you are the student from student club. If yes, please send me your information and I will add to contributors list. Thanks.


Implement CoreUI info tile about onyx

Why?
Follow up for #1549. We want to announce to our CoreUI users that onyx is now beta version and the onyx based v3 Vue Blueprint has been released.
Acceptance criteria

[x] the CoreUI showcase shows a global info tile below the top bar that informs the user about the onyx beta + v3 Vue Blueprint (maybe with link to the teams announcement or page with further information / FAQ)
[x] the global info tile can be dismissed which is saved in the localStorage so it does not show up again when reloading the page (optionally the message is moved to the notification center of the top bar)
[ ] an announcement in the CoreUI teams channel is made

we can use that chance to mention the new inner-source accessibility of the core-ui repo :)

[x] the hybrid mode is mentioned: https://vue-blueprint.schwarz/migrations/v3.html#coreui-hybrid-mode

Definition of Done

[ ] follow-up tickets were created if necessary
[ ] updated version + documentation is deployed

Approval

Home Page of Showcase, see:

Global Info tile
onyx link in top-bar context area
faq entry
Martin as product owner

Info Page explaining onyx + CoreUI + Vue Blueprint strategy
[ ] approved by designer @jannick-ux
[ ] approved by dev

Announcement text:
Vue Blueprint, onyx and what it has to do with CoreUI
onyx - the new Schwarz design system and
component library, is the successor of CoreUI.
onyx is based on Vue.js (see
Principles@Schwarz) and built from the ground up with focus on modern implementation patterns, design, developer experience,
accessibility as well as improvements based on learnings from CoreUI over the past few years.
Read more on the future of CoreUI in regards to onyx here!

Pull Request 621614: docs: inform about CoreUI's future, onyx and the Vue Blueprint


Django 5.0 support

When will it support Django 5.0?

You should be able to install it with Django 5. Or is there anything else that doesn’t work?

Nothing wrong. Django 5.0 support wasn't explicitly stated.


Update .asf.yaml to protect release branches

Motivation
Many of our current Pulsar branches are not protected. They are vulnerable to accidental force pushes. We should not allow for any modification of history on our release branches.
Further, it is important to update this check because we currently have several status checks that are not required. If a committer were not paying close attention, they could accidentally merge a PR that is not passing all tests. Here is an example: https://github.com/apache/pulsar/pull/14158#issuecomment-1035637925.
I followed the instructions here https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-BranchProtection when drafting this PR.
Modifications

Update the .asf.yaml file.
** There are instructions here: https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-BranchProtection

Verifying this change
I opened this ASF Infra Jira ticket https://issues.apache.org/jira/browse/INFRA-22833 to discuss the current protections for our branches.
Checking with ASF infra is important because otherwise we could overwrite current protections:

NB (1): Enabling any of the above checks overrides what you may have set previously, so you'll need to add all the existing checks to your .asf.yaml to reproduce any that Infra set manually for you.

Does this pull request potentially affect one of the following parts:
This PR only affects the GitHub repo management.
Documentation
We don't need documentation for this feature. The git history should be sufficient.

btw. it's possible to find out currently protected branches with this GitHub API call
❯ curl -s https://api.github.com/repos/apache/pulsar/branches |jq -r '.[] | select(.protected) | .name'
asf-site
branch-1.15
branch-1.16
branch-1.17
branch-1.18
master

Getting current required status checks:
❯ curl -s -H 'Accept: application/vnd.github.v3+json' https://api.github.com/repos/apache/pulsar/branches/master | jq .protection
{
  "enabled": true,
  "required_status_checks": {
    "enforcement_level": "non_admins",
    "contexts": [
      "License check",
      "backwards-compatibility",
      "cli",
      "cpp-tests",
      "function-state",
      "messaging",
      "process",
      "schema",
      "sql",
      "standalone",
      "thread",
      "tiered-filesystem",
      "tiered-jcloud",
      "unit-tests"
    ],
    "checks": [
      {
        "context": "License check",
        "app_id": null
      },
      {
        "context": "backwards-compatibility",
        "app_id": null
      },
      {
        "context": "cli",
        "app_id": null
      },
      {
        "context": "cpp-tests",
        "app_id": null
      },
      {
        "context": "function-state",
        "app_id": null
      },
      {
        "context": "messaging",
        "app_id": null
      },
      {
        "context": "process",
        "app_id": null
      },
      {
        "context": "schema",
        "app_id": null
      },
      {
        "context": "sql",
        "app_id": null
      },
      {
        "context": "standalone",
        "app_id": null
      },
      {
        "context": "thread",
        "app_id": null
      },
      {
        "context": "tiered-filesystem",
        "app_id": null
      },
      {
        "context": "tiered-jcloud",
        "app_id": null
      },
      {
        "context": "unit-tests",
        "app_id": null
      }
    ]
  }
}

Listing job names:
for f in .github/workflows/*.yaml; do FILE=$f yq eval -o j '.jobs | to_entries | {"file": env(FILE),"id":.[].key, "name":.[].value.name}' $f; done

The name of the job is the id if the name is empty or unspecified. for example
{
  "file": ".github/workflows/ci-license.yaml",
  "id": "license-check",
  "name": "License check"
}

and in comparison
{
  "file": ".github/workflows/ci-owasp-dep-check.yaml",
  "id": "owasp-dep-check",
  "name": null
}

Some workflows have duplicate names. I guess that's fine, but the only issue it causes it that you cannot distinguish a specific workflow.

@lhotari - this could be a feature in the sense that all duplicate names get the same treatment. For example, if all "unit tests" are named the same, they'll all be required. In the GitHub UI, they are visibly different because the top level name field is associated with the check. I left the duplicates in place for now. Please take a look and let me know what you think. Thanks.

@dave2wave - as far as I can tell, it's not possible to set protections using the REST API. It's only possible with the GraphQL API. @lhotari found the GitBox code https://github.com/apache/infrastructure-puppet/blob/deployment/modules/gitbox/files/asfgit/asfyaml.py#L278-L302, and it looks to me like it currently uses the REST API.
Source: https://github.community/t/rest-api-v3-wildcard-branch-protection/13593/13

@michaeljmarshall The API used by .asf.yaml very likely predates the GraphQL. Changing the API would be a larger project and impacts every project that uses .asf.yaml which is a large proportion of ASF projects. If anyone is interested in helping ASF Infra I can connect you. (Note that one given is that everything with Infra must be Python and for templates EZT is preferred.)

@dave2wave - sorry, I forgot a word in my last message. I meant to say it's not possible to set wildcard permissions via the REST API. This will work as is. We will just have to update the release process to include adding branch protections to new branches.

Sure. If a volunteer wished to implement wildcard branch protection update then you would start by rewriting https://github.com/apache/infrastructure-puppet/blob/deployment/modules/gitbox/files/asfgit/asfyaml.py#L257-L391

@lhotari - can you take another look? Thanks.


Update tutorials.md to add links to EEG importing tutorials

Thanks Remi

On Mar 7, 2022, at 11:56 PM, Remi Gau @.***> wrote:
@Remi-Gau approved this pull request.
Thanks for those @arnodelorme
I am "refactoring" some of the talks and tutorial pages in #263, so I might move those additions but they are here to stay.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.


Timespan

Email TG about timespans CEC

Adam's explanation 2022-01-18 @mcm104 @AdamSchiff :  Do I understand timespan?  Hmmm, sort of!  In MARC, I think we are recording timespan sometimes as a relationship and sometimes as an attribute.  Timespan can go in many different fields: 033, 045, 046, 388, 3XX $s and $t, as well as 5XX (note in bib; related entity in authority), and 6XX (subject) in bib.
date of expression (https://access.rdatoolkit.org/Content/ContentById/a4d33934-9633-4fa2-80d6-28e7acf81078), "A timespan that is the earliest associated with an expression, is a subelement of related timespan of expression (https://access.rdatoolkit.org/Content/ContentById/d119eeb3-2187-4ce9-8bdf-fe97cade8c6a), "A timespan that is associated with an expression."  Note the difference from the definitions.  In practice, I doubt we will use the broader element much if ever.  I'm having trouble even thinking of a case where we'd know a date for an expression that isn't the date of expression.  Maybe: an expression with date of expression 1965 has the related timespan of expression 1960s, or 20th century.  Why would we bother to record that though?
I think how to choose which property to use depends on what data is recorded.  In an authority record for an expression, 046 $k will map to date of expression.  So would 1XX $f.
In a bib record, which combines all or some of WEMI, 046 $k can't reliably be mapped unless an indicator value for type of entity is included.  In absence of an indicator, the general assumption is that the date in $k is date of work.  1XX and 240 $f in a bib would always map to date of expression. 388 was only defined for work creation date controlled vocabulary.
date of capture is a subelement of date of expression, so 033 second indicator 0 will map to it. Second indicator 1 (date of broadcast) and 2 (finding) don't exactly match expression. Unless, perhaps, date of broadcast is the same as the date of expression (e.g. a live broadcast).
The RDA Toolkit has a whole section on Entity Boundaries: https://access.rdatoolkit.org/Guidance/GuidanceById?id=5eeaa822-e21c-4576-b728-0e7d0035d5ca
The toolkit is not working very well at the moment however.  I keep getting a system error when I try to view that guidance chapter.  But the entity boundaries are provided to give help in determining when something has changed from one entity to another (such as where the boundary is between works versus one work with two expressions; or when two people with the same name are different entities; there will be boundaries for timespans as well (any time/date between 1901 and 2000 is in the 20th century; if the date is 23:59 hours of 1900, that is across the boundary and in the 19th century).
I don't know if any of this helps.  Dates are complex and the new timespan elements are new.  The LC/PCC Metadata Guidance Documents on timespan ought to help once they are issued

look at range of property. timespan = timespan. undefined range = need to decide in AP if datatype or object property. most of time, datatype property with literal value. don't generally create timespans unless needed? refer to toolkit in addition to marc and rda registry. meeting 2022-01-19.


unable to view dashboards

Hi guys,
after cloning git repo and start stack with follow command....
ADMIN_USER=admin ADMIN_PASSWORD=admin docker-compose up -d

I am unable to view the graphana dashboards. From the grafana logs I see the following error
Thanks
lvl=eror msg="Failed to read plugin provisioning files from directory" logger=provisioning.plugins path=/etc/grafana/provisioning/plugins error="open /etc/grafana/provisioning/plugins: no such file or directory"
lvl=eror msg="Can't read alert notification provisioning files from directory" logger=provisioning.notifiers path=/etc/grafana/provisioning/notifiers error="open /etc/grafana/provisioning/notifiers: no such file or directory

This is an expected error and does not prevent you from being able to view the dashboard.
Here's a snippet of a new stack being run up, including the line that you provided above.
t=2020-10-21T02:48:29+0000 lvl=info msg="Created default admin" logger=sqlstore user=admin
t=2020-10-21T02:48:29+0000 lvl=info msg="Starting plugin search" logger=plugins
t=2020-10-21T02:48:31+0000 lvl=info msg="Registering plugin" logger=plugins name="Direct Input"
t=2020-10-21T02:48:31+0000 lvl=info msg="inserting datasource from configuration " logger=provisioning.datasources name=Prometheus uid=
t=2020-10-21T02:48:31+0000 lvl=eror msg="Failed to read plugin provisioning files from directory" logger=provisioning.plugins path=/etc/grafana/provisioning/plugins error="open /etc/grafana/provisioning/plugins: no such file or directory"
t=2020-10-21T02:48:31+0000 lvl=eror msg="Can't read alert notification provisioning files from directory" logger=provisioning.notifiers path=/etc/grafana/provisioning/notifiers error="open /etc/grafana/provisioning/notifiers: no such file or directory"
t=2020-10-21T02:48:31+0000 lvl=info msg="HTTP Server Listen" logger=http.server address=[::]:3000 protocol=http subUrl= socket=

This instance comes up fine with all the dashboards auto-provisioned. Can you please detail the exact issue you're having and provide full log outputs if the issue is still recurring?

Thanks to the answer I solved ....
There was no issue. I didn't see the Dashboards in the "Recently Used" and "Starred" sections the first time I started the container. From the "Manage Dashboard" section and I see everything correctly.
Thanks again. Issue closed immediately


fix(npm): Prevent unnecessary hash pinning in lock file constraint

Why is this needed?
To make sure that Dependabot does not pin to a specific git hash when the package.json has not pinned to one.
What does this do?
It updates the npm helper to check for a pinned hash in git based version constraints.
Fixes https://github.com/dependabot/dependabot-core/issues/3813
Screenshots
Before:
[dependabot-core-dev] ~/dependabot-core $ ./bin/dry-run.rb npm_and_yarn xlgmokha/hypixel-translators-bot --dep discord.js --branch core-3813
Resolving dependencies...
warning: parser/current is loading parser/ruby26, which recognizes
warning: 2.6.7-compliant syntax, but you are running 2.6.6.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
=> fetching dependency files
=> dumping fetched dependency files: ./dry-run/xlgmokha/hypixel-translators-bot/core-3813/
=> parsing dependency files
=> updating 1 dependencies: discord.js

=== discord.js (ab82cafcde0ee259a32ef14303c1b4a64dea8fae)
 => checking for updates 1/1
 => latest available version is 7b85a7259f563ab14ae6c0a665a3dd43c486fde4
 => latest allowed version is 7b85a7259f563ab14ae6c0a665a3dd43c486fde4
 => requirements to unlock: own
 => requirements update strategy: bump_versions
 => updating discord.js from ab82cafcde0ee259a32ef14303c1b4a64dea8fae to 7b85a7259f563ab14ae6c0a665a3dd43c486fde4

    ± package-lock.json
    ~~~
    37a38,42
    >     "@sapphire/async-queue": {
    >       "version": "1.1.2",
    >       "resolved"<EMAIL_ADDRESS>    >       "integrity": "sha512-NkR7AzC9uyb++tMIZgG4X0ci8JM1rnvNmKbLwY42RgotRV8JGUntZ7ZpR7MN7p5zPlVdKo/YmOqcCCsBJ6LNuw=="
    >     },
    88d92
    <       "dev": true,
    308,309c312
    <       "integrity": "sha512-hNC38R9ZF4uaujaZQtQfm5CdQO58uhdkoHQAVvMfIL0LgOSZeW575W8H6upngQOuoxWd8tiRII3LLJm9zuQKYg==",
    <       "dev": true
    ---
    >       "integrity": "sha512-hNC38R9ZF4uaujaZQtQfm5CdQO58uhdkoHQAVvMfIL0LgOSZeW575W8H6upngQOuoxWd8tiRII3LLJm9zuQKYg=="
    312,313c315,316
    <       "version": "github:discordjs/discord.js#ab82cafcde0ee259a32ef14303c1b4a64dea8fae",
    <       "from": "github:discordjs/discord.js",
    ---
    >       "version": "github:discordjs/discord.js#7b85a7259f563ab14ae6c0a665a3dd43c486fde4",
    >       "from": "github:discordjs/discord.js#7b85a7259f563ab14ae6c0a665a3dd43c486fde4",
    316a320,321
    >         "@sapphire/async-queue": "^1.1.2",
    >         "@types/ws": "^7.4.4",
    317a323
    >         "discord-api-types": "^0.18.1",
    319c325
    <         "prism-media": "^1.2.2",
    ---
    >         "prism-media": "^1.2.9",
    321c327,334
    <         "ws": "^7.3.1"
    ---
    >         "ws": "^7.4.6"
    >       },
    >       "dependencies": {
    >         "ws": {
    >           "version": "7.4.6",
    >           "resolved": "https://registry.npmjs.org/ws/-/ws-7.4.6.tgz",
    >           "integrity": "sha512-YmhHDO4MzaDLB+M9ym/mDA5z0naX8j7SIlT8f8z+I0VtzsRbekxEutHSme7NPS2qE8StCYQNUnfWdXta/Yu85A=="
    >         }
    ~~~

After:
$ ./bin/dry-run.rb npm_and_yarn xlgmokha/hypixel-translators-bot --dep 'discord.js' --branch core-3813
warning: parser/current is loading parser/ruby26, which recognizes
warning: 2.6.7-compliant syntax, but you are running 2.6.6.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
=> fetching dependency files
=> dumping fetched dependency files: ./dry-run/xlgmokha/hypixel-translators-bot/core-3813/
=> parsing dependency files
=> updating 1 dependencies: discord.js

=== discord.js (ab82cafcde0ee259a32ef14303c1b4a64dea8fae)
 => checking for updates 1/1
 => latest available version is 51551f544b80d7d27ab0b315da01dfc560b2c115
 => latest allowed version is 51551f544b80d7d27ab0b315da01dfc560b2c115
 => requirements to unlock: own
 => requirements update strategy: bump_versions
 => updating discord.js from ab82cafcde0ee259a32ef14303c1b4a64dea8fae to 51551f544b80d7d27ab0b315da01dfc560b2c115

    ± package-lock.json
    ~~~
    37a38,42
    >     "@sapphire/async-queue": {
    >       "version": "1.1.2",
    >       "resolved"<EMAIL_ADDRESS>    >       "integrity": "sha512-NkR7AzC9uyb++tMIZgG4X0ci8JM1rnvNmKbLwY42RgotRV8JGUntZ7ZpR7MN7p5zPlVdKo/YmOqcCCsBJ6LNuw=="
    >     },
    88d92
    <       "dev": true,
    308,309c312
    <       "integrity": "sha512-hNC38R9ZF4uaujaZQtQfm5CdQO58uhdkoHQAVvMfIL0LgOSZeW575W8H6upngQOuoxWd8tiRII3LLJm9zuQKYg==",
    <       "dev": true
    ---
    >       "integrity": "sha512-hNC38R9ZF4uaujaZQtQfm5CdQO58uhdkoHQAVvMfIL0LgOSZeW575W8H6upngQOuoxWd8tiRII3LLJm9zuQKYg=="
    312c315
    <       "version": "github:discordjs/discord.js#ab82cafcde0ee259a32ef14303c1b4a64dea8fae",
    ---
    >       "version": "github:discordjs/discord.js#fdad14099779e61cb84dcd1cb2497e0e853a6144",
    316a320,321
    >         "@sapphire/async-queue": "^1.1.2",
    >         "@types/ws": "^7.4.4",
    317a323
    >         "discord-api-types": "^0.18.1",
    319c325
    <         "prism-media": "^1.2.2",
    ---
    >         "prism-media": "^1.2.9",
    321c327,334
    <         "ws": "^7.3.1"
    ---
    >         "ws": "^7.4.6"
    >       },
    >       "dependencies": {
    >         "ws": {
    >           "version": "7.4.6",
    >           "resolved": "https://registry.npmjs.org/ws/-/ws-7.4.6.tgz",
    >           "integrity": "sha512-YmhHDO4MzaDLB+M9ym/mDA5z0naX8j7SIlT8f8z+I0VtzsRbekxEutHSme7NPS2qE8StCYQNUnfWdXta/Yu85A=="
    >         }
    ~~~

Type of change

[X] Bug fix (non-breaking change which fixes an issue)

Thanks for this! I see that you committed our package and package-lock files, is this intentional?

Thanks for this! I see that you committed our package and package-lock files, is this intentional?

No, this is temporary until I could wrap my head around the problem. I'll tidy up the fixture file before submitting for review.

@feelepxyz would you mind double checking the latest commit to this PR?


Support for submission requirement for WACI

This is the advanced use case , Submission Requirement for waci is required.
Use case scenario: Issue Driving license
Requirement: Provide address proof
Acceptable IDs:  Provide any two piece of IDs in order to validate the address, Permanent Resident Card, T4slip , Health Card.
Advanced use case put in backlog.

Add presentation_def parallel to output_descriptors in config - https://identity.foundation/credential-manifest/#credential-manifest---all-features-exercised


Bug: Transform user secret to hex, if not already hex formatted

Versions

OS:
Browser:

Reproduction

Additional Details

Steps to reproduce
What is Expected?
What is actually happening?

e75c090cd06de6bd4bd785dde868cd2e3bd01851


Merge ops-2.2 into master.

Merge the ops-2.2 branch into master and phase-out the ops-2.2 branch.
Fixed the missing URI pattern that was preventing load of Uniprot-->Ensembl Linkset during
openphacts v2.2 refresh.
Reverted mysql port back to standard mysql default of 3306.

In taverna-bridgedb/pom.xml there is this line:


Validate http headers names

As per Ahson request, we are adding validation for headers names.
For Http Requests, validation is done as soon as customer try to append one header to some http request. We return AZ_ERROR_ARG as the input args are not valid to append a header.
For Http Response, I propose in this PR to add a policy before transport policy that will handle validation after response comes back from transport policy. This way, if customer wants to remove this, they can remove this policy from the pipeline and trust that Service will never return a bad header back (this would provide some speed because validating response headers needs to parse the response and loop through all headers in the response)

For request headers, I think we can check them with a precondition; what would a customer do with AZ_ERROR_ARG?
For response headers, the policy idea is an interesting one; I never thought of that myself. The downside to this is that you're ultimately scanning over the data twice: once in the policy & once again as we return headers to the customer. We always have to scan the response to return headers to the customer. So, while scanning, it might just be faster to check the characters against valid characters. We could make this an http_response option set when initializing it IF the perf hit is too great.

For request headers, I think we can check them with a precondition; what would a customer do with AZ_ERROR_ARG?

The only problem whit this is if customer won't set header statically and will get the values for header name and value from I/O. Anyway, I have changed it to PRECONDITION and eventually we will see if this becomes a problem in the future.  Worst case will be customer adding a header that Service will validate and return INVALID HTTP Request back.

For response headers, the policy idea is an interesting one; I never thought of that myself. The downside to this is that you're ultimately scanning over the data twice: once in the policy & once again as we return headers to the customer. We always have to scan the response to return headers to the customer. So, while scanning, it might just be faster to check the characters against valid characters. We could make this an http_response option set when initializing it IF the perf hit is too great.

The problem of waiting to validate header until we are parsing the response for the user is that we won't fail the request. We will return AZ_OK and fill the az_http_response with the invalid data.
Then during parsing, we will return the error.
My understanding is that we want to fail the request on this case. We would be still returning all the response to customer, but he will know that it's not valid in advance.
If a Service like KeyVault or Storage would review this SDK client and decide they won't never return an invalid header, they can update the SDK client and remove the policy.
By adding an option for az_http_response, it would be final customer decision if they want to have this validation or not.

No service will ever intentionally return invalid headers. So, the chance of discovering an invalid header is really zero. This checking is just for paranoia and so we don’t want to introduce infrastructure (like a policy) or significant CPU wastage (like scanning twice) to address something that should never happen.
It’s OK to just fail returning a header pair because this will never actually happen. Today, I would just check when returning a header and NOT offer a way for a customer to turn this off as it is an extra know that we have to document, test, support, explain, etc. IF we hear that perf is bad, then we can offer a switch to turn it off in a non-breaking way.

Jeffrey Richter (watch Architecting Distributed Cloud Appshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fazure.microsoft.com%2Ftraining%2Fdistributed-cloud-apps%2F&data=02|01|jeffreyr%40microsoft.com|c2139bebacc8433bd13308d76a014af0|72f988bf86f141af91ab2d7cd011db47|1|0|637094426089210301&sdata=GjJbhammA5C%2F1Pve%2FXjbMq8wjjpGr2W1KSrYaCmzq7E%3D&reserved=0)

From: Victor Vazquez<EMAIL_ADDRESS>Sent: Tuesday, May 5, 2020 2:48 PM
To: Azure/azure-sdk-for-c<EMAIL_ADDRESS>Cc: Jeffrey Richter<EMAIL_ADDRESS>Review requested<EMAIL_ADDRESS>Subject: Re: [Azure/azure-sdk-for-c] Validate http headers names (#684)
For request headers, I think we can check them with a precondition; what would a customer do with AZ_ERROR_ARG?
The only problem whit this is if customer won't set header statically and will get the values for header name and value from I/O. Anyway, I have changed it to PRECONDITION and eventually we will see if this becomes a problem in the future. Worst case will be customer adding a header that Service will validate and return INVALID HTTP Request back.
For response headers, the policy idea is an interesting one; I never thought of that myself. The downside to this is that you're ultimately scanning over the data twice: once in the policy & once again as we return headers to the customer. We always have to scan the response to return headers to the customer. So, while scanning, it might just be faster to check the characters against valid characters. We could make this an http_response option set when initializing it IF the perf hit is too great.
The problem of waiting to validate header until we are parsing the response for the user is that we won't fail the request. We will return AZ_OK and fill the az_http_response with the invalid data.
Then during parsing, we will return the error.
My understanding is that we want to fail the request on this case. We would be still returning all the response to customer, but he will know that it's not valid in advance.
If a Service like KeyVault or Storage would review this SDK client and decide they won't never return an invalid header, they can update the SDK client and remove the policy.
By adding an option for az_http_response, it would be final customer decision if they want to have this validation or not.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-sdk-for-c/pull/684#issuecomment-624324405, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AARLJP7626NR6QF4D7E2XM3RQCCQPANCNFSM4MZZKBOQ.


Handle active bindings

When displaying info about variables, we could indicate if a variable is an active binding. This can be tested by base::bindingIsActive. From R 4.0.0, there is a function activeBindingFunction which could be used to display the binding function as well. Probably this could be back-ported to <R.4.0.0 if required.

Sounds good, I will look into that


fetch abstract up till well known <!-- more --> tag

👋
It is quite common for the markdown-based blog engines/themes to leverage the well known <!-- more --> tag to auto-generate the abstracts when the post is rendered.
It makes sense to expose an option for RSS plugin to fetch the post abstract up till that tag instead of a hard cut on the char limit.

Good idea.
I've no more time for this project these times. Feel free to push a PR or please wait until next avaibility.

↑ Implemented in #173 2 weeks ago. :tada:
So let's close this issue?

Right, I though the merging the PR would close here.


no-switch-case-fall-through does not handle braces correctly

Bug Report

TSLint version: 4.3.1
TypeScript version: 2.2.1
Running TSLint via:  cli

TypeScript code being linted
  public testfunc(): string {
    let test = 'bla';
    switch (test) {
      case 'bla': {
        return 'Hallo in case';
      }
      case 'blub':
        return 'Hello blub';
    }

    return 'Hallo outside';
  }

with tslint.json configuration:
    "no-switch-case-fall-through": true,

Actual behavior
I got an error that there is a break statement expected before the case
src/app/shared/demo.ts[25, 7]: expected a 'break' before 'case'
It works without the braces around case 'bla'
Expected behavior
Working with braces.

This is fixed by #2218 and released with tslint v4.5.0


Touch screen calibration

Hi all! First of all thank you for a great software for Raspberry!
I need to create public kiosk using Elo touch screen. So I downloaded their driver and followed the guide to set it up. Finally it worked but touch function of the screen seems to be mirrored diagonally. If I want to use their calibration app, it needs X Windows. I tried to make it work using command:
sudo apt-get install xorg-dev
I installed libXm.so.4 library too but still no success.
I used older version 2.1.0 (newer ones somehow did not work for me) with Raspberry Pi version 1B.
Is there something I am missing? Can anyone please provide a simple step by step guide to set what is needed?

I don't know about the elo driver but probably there is something similer like this
Where with invert option on or off you can swap direction
sudo nano 99-calibration.conf
Section "InputClass"
Identifier      "calibration"
MatchProduct    "ADS7846 Touchscreen"
Option  "Calibration"   "208 3905 288 3910"
Option  "SwapAxes"      "0"
Option "EmulateThirdButton" "1"
Option "EmulateThirdButtonTimeout" "1000"
Option "EmulateThirdButtonMoveThreshold" "300"
Option "InvertY" "0"
Option "SwapXY" "0"
Option "InvertX" "1"
EndSection

Thank you for the advice. I have tried to look for somethink similar in my driver directory but I cannot see optins like these. I will probably try to invert screen globaly in system settings. If I find working solution, I will post it here.

look if you have this directory
/etc/X11/xorg.conf.d

I could not find directory like that.
I used sudo nano /boot/config.txt and wrote display_hdmi_rotate=2 to invert screen and it works just fine for me.
Now I am trying to hide cursor completely. Is there any config where I could do this?

unclutter will prevent that
sudo apt-get install -y unclutter

I have tried this. It seems like unclutter is already included in this version. Pointer disappers after few seconds of inactivity. I would prefer to hide it forever.


Issue with UAA Service Instance

while deploying the app, we got an error saying could not find service instance for UAA.
"Error creating application null (Error parsing xs-security.json data: Error reading service instance ID for service instance 'btp-procurement-data-extractor-jobscheduler' from cloud controller: 'Cannot find service instance for space id 'ae9e0c39-9f5d-4f08-a816-315eac850cd0' and service 'btp-procurement-data-extractor-jobscheduler'.')",
We created UAA service instance manually and tried to redeploy, got below error:
Couldn't update service instance 'btp-procurement-data-extractor-uaa'.
Instance ID: 341d1943-d889-4cc4-b0e6-ea6df8331503
Updating service "btp-procurement-data-extractor-uaa" failed: Could not find xsapp entry for btp-procurement-data-extractor!t333227

Hello @jainmrce , you'll need to delete the UAA service instance and re-create it. This should solve the problem as the Job Scheduler instance need to be created prior to UAA service instance


🌕 Deprecating Moon(River/Beam) for now

comment 🌕-chains in libs/static/src/chains.ts
comment 🌕-chains in libs/static/src/endpoints.ts
comment 🌕-chains in libs/static/src/indexers.ts
comment 🌕-chains in libs/static/src/names.ts
comment 🌕-chains in libs/static/src/services.ts
comment 🌕-chains in libs/static/src/types.ts
:wastebasket: remove moonchains
:wastebasket: moonchains from create collectons
:wastebasket: moonchains from landing page
:wrench: :wastebasket: moonchains config
:wrench: :wastebasket: moonchains config

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[ ] Feature
[x] Refactoring

Context
https://github.com/kodadot/nft-gallery/discussions/4754#discussioncomment-7111297
Copilot Summary

🤖 Generated by Copilot at 6f87925
The pull request removes or disables support for the 'movr' and 'glmr' chains, which are experimental networks based on Polkadot, from various parts of the codebase. This may be done to simplify the code, avoid potential issues, or focus on other chains. The pull request also makes some minor adjustments to the UI components related to these chains, such as the landing page carousel and the collection creation menu.

🤖 Generated by Copilot at 6f87925

The code has removed movr and glmr
These chains were experimental and dimmer
They caused some trouble
With prefixes and stubble
So the codebase is now cleaner and slimmer

wasn't it part of a hackathon? aren't there any obligations? or maybe we can try to found indexer?

wasn't it part of a hackathon?
Yes it was

aren't there any obligations?

No they aren't

or maybe we can try to found indexer?

It's a work-in-progress

(or use external squid)

As I mentioned in the discussion above there is a WIP for the new click indexer but cannot make it until 1st OCT

balances not loading on this one


Fix for angular velocity (Y) resetting

I mentioned this on twitter but figured I should make a PR for it too.
This fixes the condition where contact velocity reaches 0, but still has angular Y momentum.
Before: ωᵧ = 0
After: △ωᵧ = sgn(ωᵧ) * -0.3
This would heavily effect shots that make use of English/Side against rails.

Ya fair enough, it was only this little error i made previously thats i feel its important to get physics consistent, other than that not really any major changes from when you forked it out.
also, after reading through the code you've upgraded it to, i would like to redact my previous opinions on coding styles haha. it for sure is more approachable to work on this branch


feat(deps): update some dependencies

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


Re-implement hidden tabs from tabbar behavior

Version
Tell us which versions you are using (react native 0.26 is required for v3):

react-native-router-flux v3.26.2
react-native v0.26.2

In the previous versions not supplying  icon={TabIcon} to a Scene inside a tabs={true} component allowed to hide the tab from the tabbar, but still be allowed to navigate to it using Actions.
After upgrading from "react-native-router-flux": "^3.2.7", to latest, this behavior is gone.
Steps to reproduce
    <Scene key="tabbar" hideNavBar={true}  tabBarStyle={tabBarStyle.bar}  tabs={true} default="me">
        <Scene key="1" icon={TabIcon} title="1">
          <Scene key="1_1" component={1_1}  title="Browse"/>
        </Scene>
        <Scene key="2" icon={TabIcon} title="2">
          <Scene key="2_1" component={2_1} />
          <Scene key="2_2" component={2_2} />
       </Scene>
        <Scene key="magicHiddenTab" /* icon={TabIcon} */  hideTabBar={true} >
        </Scene>
        <Scene key="3" component={3} icon={TabIcon}  />
        <Scene key="4" component={4} icon={TabIcon}  />
      </Scene>

agree, @joenoon could you fix that?

the old behaviour sounds like a bug to me. But I can see the usefulness of it. Can we make it by explicit setting a new prop like hideTab={true} ?

agree it seems like more of a bug than a feature - but maybe there is a valid use case there that I just dont use.  I have a branch in progress that brings back the old tab implementation exactly as it was, and fixes the part I couldnt get working before for the scene rendering.  so hopefully all of these problems since the new tab implementation will go away soon.

One use case is where you want a small amount of tabs (main functionality/views of the app) to be shown on most of the scenes.

Hi @Elyx0 Can you elaborate why you need this? Looks like that your magicHiddenTab can easily be placed as a sibling to tabbar and by default it will be hidden if you use switch. Or for a more sophisticated design you'll be able to hide it using redux.
I agree with @ms88privat this old behaviour is more like a bug that could lead to incongruent scenarios where it will be hard to define what shows or not a tab.

@Cordazar what you're describing can't be achieved with nested scenes?

@rturk I can't see how.
10 Views numbered 1-10.
View 1 and 2 should be in the tab bar for Views 1-8 but not on View 9-10.
How would you nest that?

I'm wondering how this plays with the inclusion of a Drawer. In the documentation for a Drawer, it is suggested that within the "drawer" Scene you include a scene with tabs={true}, presumably so that children scenes will automatically set type='jump'.
However, doing so leads to something like the referenced issue:

Error: Warning: React.createElement: type should not be null, undefined, boolean, or number. It should be a string (for DOM elements) or a ReactClass (for composite components). Check the render method of TabNavigator.

Is the tabs={true} therefore erroneous in the documentation OR is this example a reason that the above is a feature rather than a bug?

I am having trouble with the tab bar as well, maybe it's related to this. I want to display the tab bar for scenes that I have declared outside of the tab bar scene but have navigated to from a scene within a tabbar. Is that possible?

@rgovindji that sounds to me like you want this:
You click a tab, click a user's name which should open their profile.  That could happen from any tab at any depth.  The expected behavior would be to "push" the profile screen into the current navigation flow (current nav/tab).  And then when browsing that profile, you might see a "friends" section and find someone else to click... their profile would then be pushed as well.  You would get back to the root of the tab my going Back, Back on the nav bar.
If that sounds like the flow you want, thats exactly what the "clone" feature allows.  You can check the Example app where its used in the tabbar demo:  EchoView, push new scene, all of the inherit/explicit options for hideNavBar/hideTabBar etc.

@joenoon thanks a lot that is exactly what I was looking for 👍


update v3relay article from stub to article

squashed version, "builds" on-top of PR #1001.

@paulkania the current build errors are:
_topics/en/version-3-transaction-relay.md:60: MD009 Trailing spaces

_topics/en/version-3-transaction-relay.md:61: MD009 Trailing spaces

_topics/en/version-3-transaction-relay.md:62: MD009 Trailing spaces

_topics/en/version-3-transaction-relay.md:63: MD009 Trailing spaces

_topics/en/version-3-transaction-relay.md:69: MD009 Trailing spaces

This means, on the lines indicated (60, 61, 62, 63, and 69), there's an unnecessary space at the end of the line.  We have a test for that because, in some flavors of Markdown, extra spaces at the end of a line are translated into an HTML <br> tag.

I hate how unnecessarily complex I've made this PR...my apologies.
I tangled myself up in rebasing and merging conflicts, and decided to try to nuke my local repo and start fresh.
The issue now is that I'm unable to push a new PR or update this one : requested url error 403.
I promise to re-visit the git-documentation asap.

@paulkania: If you tell us what specific problems you are running into, we can probably walk you through. Alternatively, one of us can squash your PR for you, and you can continue from there.

@Xekyo I blundered with my branching and merging. I re-opened this PR as #1009


Allow Feature files like .bed and .vcf be used as inputs to -L

Gatk3 allowed inputs like -L some_intervals.vcf.  This functionality should be integrated into the IntervalArgumentCollection so that it is available to all tools.

This is needed for a tool that @samuelklee is working on.

I can take this one


Release of version <IP_ADDRESS> of xBitlocker

Releasing version <IP_ADDRESS>

This change is

Codecov Report

Merging #45 into master will increase coverage by 73.91%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #45       +/-   ##
=========================================
+ Coverage   26.08%   100%   +73.91%
=========================================
  Files           3      3
  Lines          92     96        +4
=========================================
+ Hits           24     96       +72
+ Misses         68      0       -68

Impacted Files
Coverage Δ

...Resources/MSFT_xBLBitlocker/MSFT_xBLBitlocker.psm1
100% <100%> (+92.3%)
:arrow_up:

DSCResources/MSFT_xBLTpm/MSFT_xBLTpm.psm1
100% <100%> (+96.29%)
:arrow_up:

...s/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1
100% <100%> (+57.69%)
:arrow_up:

Continue to review full report at Codecov.

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


Mini project 01

Mini Project 01 with Ben Tarr (Were given 36 hour extension)

Rubric For Mini Project 1: Device Driver
Submission
Canvas
1: The link submitted on Canvas is for the pull request containing the
assignment submission.
0: The link submitted on Canvas is not for the pull request containing the
assignment submission.
Git Branch
1: The branch includes only changes for this assignment.
0: The branch includes commits or changes outside this assignment.
Git Commit Message
1: All commit messages for the branch are reasonably clear.
0: One or more commit messages for the branch are reasonably clear.
GitHub Pull Request
1: The pull request is made to the main branch of the student's fork of the
course repository.
0: The pull request is made to a branch other than main or to a repo that is
not the student's fork of the course repository.
Comments
(-1) Some of these commit messages are.......
Points
Submission Score: 3/4
Onboarding Project
For each of the five requires subcomponents of the onboarding project (serial interface, parallel processing, controller management, game state management, and the user-interface):
4: The game component is fully implemented, leading to no noticeable user-facing bugs that hinder game flow.
2: Minor errors exist in the implementation, that are apparent during certain edge cases of the game workflow.
0: This specific subcomponent was not implemented, or major bugs exist in the implementation that hinder game play.
Comments
(-1) There's a minor error in your state machine when transitioning between rounds - the LEDs don't seem to get reset back to just "ready" and stay constantly on
(-2) There's a minor error in how you analyze the controller state through the bit mask of the buttons (see comment).
Points
Onboarding Project Score: 17/20
First Sprint
For each story point that was taken on (automatic 0 points for story points not implemeneted under 10):
4: The additional feature is fully implemented, leading to no noticeable user-facing bugs that hinder game flow.
2: Minor errors exist in the implementation, that are apparent during certain edge cases of the game workflow.
0: This specific feature was not implemented, or major bugs exist in the implementation that hinder game play.
NOTE: The score out of 4 is for 1 story point. For the tasks worth more than 1 story point, the rubric value will be scaled by the amount of story points.
Comments
Extra Buttons
Nice work on this! Really like the verbose structs you created to explicitly store the button states (won't take off more points for the same bit mask error as the onboarding project)
Arbitrary Number of Controllers
Left a few nit picky comments about data structures, but overall this was really clean and solid!
New Plots
(-5) Overall, I like the logging infrastructure and the idea to display the player's score over time! However, I do think there's some logical issues in how you're storing the data (see comments), especially around the timing of sampling.
Points
Onboarding Project Score: 35/40
Guide
In order for users (the teaching team) to know what features your software stack supports, please list out all of the store points you attempted in guide.md.
Comments
No file provided
Points
Guide Score: 0/1
Code Quality
Design
File/Module organization
2: The program is appropriately split into reasonable files/modules
1: The program is somewhat organized, but there's room for improvement (splits aren't idiomatic, or some modules are still too large, etc.)
0: The program is not split at all
Scalability
5: The code is architected with scalability in mind. If more features needed to be added, they could easily be integrated.
3: The code was architected with some scalaibility in mind. However, significant refactoring would be needed in order to expand the feature set of this tool. (Possible symptoms include not modularizing enough/not effectively using traits + generics).
0: The code is not scalable. The entire package would need to be refactored in order to expand its features.
General Cleanliness
4: The code is effectively documented, especially for sources of user-facing errors. Additionally, function signatures are clear and the code is overall very readable.
2: Attempts at verbose documentation were made, but certain sources of error are unclear OR poor function signatures are used and readers would have slight difficulties while scanning the code.
0: Documentation is severely lacking in several palces and the code is not written in a readable way.
Lint/Format
RustFmt
2: RustFmt produces no warnings when run on the changed files
1: RustFmt produces a few minor warnings when run on the changed files
0: RustFmt produces many warnings when run on the changed files
Clippy
2: Clippy produces no warnings when run on the changed files
1: Clippy produces a few minor warnings when run on the changed files
0: Clippy produces many warnings when run on the changed files
Comments
Overall, I commend you for the amount of attention to detail you had when planning your architecture. I know y'all had some issues with the weeds of the actual implementation, but I really like the separation of logic and verbose logging y'all had.
(-1) clippy :(
Points
Code Quality Score: 14/15
Summary
Add up the point totals here
Total Score: 69/80


Incorrect line splitting

What were you trying to do?
Passing text to layoutMultilineText is splitting the lines for both \n and \r which is inserting a blank line where there is none.
lineSplit
pdf-lib/string.ts:45
How did you attempt to do it?
Pass text in windows to it that has a carriage return and line feed ( i.e.  \r\n ) should not return a blank line, it should only end the current line.
What actually happened?
It returned a blank line. i.e.:
Input:
Line 1\r\n
Line 2\r\n
Output
Line1: Line 1
Line2:
Line3: Line 2
Line4:
What did you expect to happen?
Input:
Line 1\r\n
Line 2\r\n
Output:
Line1: Line 1
Line2: Line 2
How can we reproduce the issue?
let descDetail =
`Line 1
Line 2`;

let descLines = PDFLib.layoutMultilineText(descDetail,{alignment: "left", font: font["timesRomanFont"], fontSize: 10, lineHeight: 10*1.2, bounds: {width:280,height: 10000}});

Output descLines = {lines: [{text: "Line1, ...},{text: "",...},{text: "Line2",...},{text: "",...}], ... }
Version
1.17.1
What environment are you running pdf-lib in?
Browser
Checklist

[X] My report includes a Short, Self Contained, Correct (Compilable) Example.
[X] I have attached all PDFs, images, and other files needed to run my SSCCE.

Additional Notes
The cleanText function ( pdf-lib/strings.ts:40 ) should strip out the carriage returns \r

hmm its quite common as linefeed in nix and mac are different single characters and widows uses both as one ! Always been that way since Ye olde DinOosaurS


[BUG] Maestro is completely blocked

Describe the bug
The Maestro test can't see anything to click on.
To Reproduce
Steps to reproduce the behavior:
When I add in:
<TabNavigation />
            <Toaster />

If I remove <Toaster /> my tests pass with the overlay gone.
Expected behavior
For Maestro to be able to click on buttons.
Environment info

Library
Version

sonner-native
0.15.0

react-native
0.75.4

react-native-reanimated
3.15.4

react-native-gesture-handler
2.20.0

If you use the element inspector, you're able to click through it while the toast is visible, right?
Since that's the case for me at least, I don't think there's much to be done here. I'd suggest conditionally render the Toaster if the Maestro test is running. While I didn't find a React Native implementation of detecting that Maestro is running, you could always create a native module that surfaces that: https://maestro.mobile.dev/advanced/detect-maestro-in-your-app


multi-token EmbeddingConstruction

📚 Documentation
I am confused with the EmbeddingConstruction documentation.
    embedding_style:
      single_token_item: false
      emb_strategy: "w2v_bilstm"

If I understand correctly if there are multiple tokens in the node attribute i.e.: graph_data.node_attributes[index]["token"] = "I am multiple tokens", in that case I should set single_token_item as false. Is this understanding correct?
Secondly, why I can't set seq_info_encode_strategy as true for the multi-token items?

@vinven7 do you know?

@AlanSwift @hugochan can anyone please help me with this query?

📚 Documentation
I am confused with the EmbeddingConstruction documentation.
    embedding_style:
      single_token_item: false
      emb_strategy: "w2v_bilstm"

If I understand correctly if there are multiple tokens in the node attribute i.e.: graph_data.node_attributes[index]["token"] = "I am multiple tokens", in that case I should set single_token_item as false. Is this understanding correct?
Secondly, why I can't set seq_info_encode_strategy as true for the multi-token items?

@nashid Thank you for your attention to the library!

yes, you are correct about the first statement.
seq_info_encode_strategy specifies strategies of encoding sequential information in raw text (i.e., each token in raw text as a graph node). If a graph node contains multiple tokens, we think in general it doesn't make sense to encode the raw sequential text to help initialize node embeddings. Can you give concrete cases where you think it makes sense to turn on seq_info_encode_strategy for multi-token node?

@hugochan I am applying the Graph2Seq model to the source code.

A single line of source code in a single node.
Different lines are then connected  with next-line edge.

I am wondering why not leave it to the user of the library? The users of the library can set seq_info_encode_strategy according to their use case?

@hugochan I am applying the Graph2Seq model to the source code (JAVA).

A single line of source code in a single node.
Different lines are then connected  with next-line edge.

I am wondering why not leave it to the user of the library? The users of the library can set seq_info_encode_strategy according to their use case?

@nashid That's a good question! We want to keep a good balance between providing enough flexibility to users and providing off-the-shelf solutions which are proven to be effective in existing literature. For multi-token node, we think it's a common practice to run a sequence encoder on each node to initialize the node embeddings in many scenarios (e.g., IE graph, knowledge graph). Users are encouraged to build their customized embedding initialization strategy if the built-in options cannot suit their needs.

@hugochan if I use pre-trained embedding (let’s say word2vec or gloVe), I presume I can just feed the pre-trained embedding.
For multi-token node, would that work? Can you please point me to an example, if you have one?

@hugochan if I use pre-trained embedding (let’s say word2vec or gloVe), I presume I can just feed the pre-trained embedding.
For multi-token node, would that work? Can you please point me to an example, if you have one?

@nashid yes, you can refer to this text summarization example which constructed an IE graph (containing multi-token nodes).


childprocess compatibility with selenium driver

Would it be possible to update the gemspec to set childprocess (~> 0.3)?
Trying to update to your latest, results in this error from bundler.
Bundler could not find compatible versions for gem "childprocess":
In Gemfile:
guard-jasmine (~> 0.9.5) ruby depends on
childprocess (~> 0.2.8) ruby
selenium-webdriver (= 2.17.0) ruby depends on
  childprocess (0.3.0)

Thanks,
Michael

I've removed a strict dependency on a specific gem version.


Redo consume Roslyn from new location

Reverts Microsoft/msbuild#1391

@omartawfik this will bring back the changes for our rc3 branch.

@dotnet-bot test Windows_NT Build for Desktop please

This went in to Roslyn with https://github.com/dotnet/roslyn/pull/15222, so it should go in here as well.


.Net wrapper issue

I am unable to start the .Net wrapper due to the following issue:

Did I miss any configurations?

I suggest you install the ZXingCpp nuget package, which comes with the native DLL included:
dotnet add package ZXingCpp


Segfault when running test_dpjit_reduction.py on Intel ARC A770 GPU device

I encountered a segfault when running the dpjit reduction test case on ARC with numba-dpex 0.23.0rc1. The same tests fail with 0.21.1, but do not segfault.
$ ONEAPI_DEVICE_SELECTOR=*:gpu NUMBA_CAPTURED_ERRORS=new_style pytest numba_dpex/
tests/dpjit_tests/test_dpjit_reduction.py
================================================================== test session starts ===================================================================
platform linux -- Python 3.10.14, pytest-8.1.1, pluggy-1.4.0
rootdir: /localdisk/work/diptorup/devel/numba-dpex
configfile: pyproject.toml
plugins: cov-5.0.0
collected 9 items

numba_dpex/tests/dpjit_tests/test_dpjit_reduction.py Fatal Python error: Segmentation fault

Current thread 0x00007fbcddd12b80 (most recent call first):
  File "/localdisk/work/diptorup/devel/numba-dpex/numba_dpex/core/parfors/kernel_builder.py", line 105 in _compile_kernel_parfor
  File "/localdisk/work/diptorup/devel/numba-dpex/numba_dpex/core/parfors/reduction_kernel_builder.py", line 174 in create_reduction_main_kernel_for_parfor
  File "/localdisk/work/diptorup/devel/numba-dpex/numba_dpex/core/parfors/parfor_lowerer.py", line 262 in _reduction_codegen
  File "/localdisk/work/diptorup/devel/numba-dpex/numba_dpex/core/parfors/parfor_lowerer.py", line 385 in _lower_parfor_as_kernel
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/parfors/parfor_lowering.py", line 69 in _lower_parfor_parallel
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/parfors/parfor_lowering.py", line 51 in lower_inst
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/lowering.py", line 270 in lower_block
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/lowering.py", line 256 in lower_function_body
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/lowering.py", line 226 in lower_normal_function
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/lowering.py", line 187 in lower
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/typed_passes.py", line 468 in run_pass
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/compiler_machinery.py", line 273 in check
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/compiler_machinery.py", line 311 in _runPass
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/compiler_lock.py", line 35 in _acquire_compile_lock
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/compiler_machinery.py", line 356 in run
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/compiler.py", line 479 in _compile_core
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/compiler.py", line 513 in _compile_bytecode
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/compiler.py", line 445 in compile_extra
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/compiler.py", line 751 in compile_extra
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/dispatcher.py", line 152 in _compile_core
  File "/localdisk/work/diptorup/devel/numba-dpex/numba_dpex/core/dpjit_dispatcher.py", line 34 in _compile_cached
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/dispatcher.py", line 125 in compile
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/dispatcher.py", line 957 in compile
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/numba/core/dispatcher.py", line 420 in _compile_for_args
  File "/localdisk/work/diptorup/devel/numba-dpex/numba_dpex/tests/dpjit_tests/test_dpjit_reduction.py", line 75 in test_dpjit_array_arg_types_add1
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/python.py", line 195 in pytest_pyfunc_call
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_callers.py", line 102 in _multicall
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_manager.py", line 119 in _hookexec
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_hooks.py", line 501 in __call__
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/python.py", line 1772 in runtest
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/runner.py", line 172 in pytest_runtest_call
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_callers.py", line 102 in _multicall
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_manager.py", line 119 in _hookexec
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_hooks.py", line 501 in __call__
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/runner.py", line 240 in <lambda>
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/runner.py", line 340 in from_call
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/runner.py", line 239 in call_and_report
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/runner.py", line 134 in runtestprotocol
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/runner.py", line 115 in pytest_runtest_protocol
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_callers.py", line 102 in _multicall
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_manager.py", line 119 in _hookexec
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_hooks.py", line 501 in __call__
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/main.py", line 364 in pytest_runtestloop
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_callers.py", line 102 in _multicall
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_manager.py", line 119 in _hookexec
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_hooks.py", line 501 in __call__
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/main.py", line 339 in _main
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/main.py", line 285 in wrap_session
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/main.py", line 332 in pytest_cmdline_main
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_callers.py", line 102 in _multicall
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_manager.py", line 119 in _hookexec
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/pluggy/_hooks.py", line 501 in __call__
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/config/__init__.py", line 174 in main
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/lib/python3.10/site-packages/_pytest/config/__init__.py", line 197 in console_main
  File "/localdisk/work/diptorup/miniconda3/envs/dpex-devel/bin/pytest", line 10 in <module>

Extension modules: dpctl._sycl_context, dpctl._sycl_platform, dpctl._sycl_device, dpctl._sycl_device_factory, dpctl._sycl_event, dpctl.program._program, dpctl._sycl_queue_manager, mkl._mklinit, mkl._py_mkl_service, numpy.core._multiarray_umath, numpy.core._multiarray_tests, numpy.linalg._umath_linalg, numpy.fft._pocketfft_internal, mkl_fft._pydfti, numpy.random._common, numpy.random.bit_generator, numpy.random._bounded_integers, numpy.random._mt19937, numpy.random.mtrand, numpy.random._philox, numpy.random._pcg64, numpy.random._sfc64, numpy.random._generator, _patch, mkl_umath._patch, dpctl.memory._memory, dpctl._sycl_queue, numba.core.typeconv._typeconv, numba._helperlib, numba._dynfunc, numba._dispatcher, numba.core.runtime._nrt_python, numba.np.ufunc._internal, numba.experimental.jitclass._box, dpctl.utils._compute_follows_data, dpctl.tensor._dlpack, dpctl.tensor._flags, dpctl.tensor._usmarray, dpnp.dpnp_utils.dpnp_algo_utils, dpnp.dpnp_algo.dpnp_algo, dpnp.fft.dpnp_algo_fft, dpnp.linalg.dpnp_algo_linalg, dpnp.random.dpnp_algo_random (total: 43)
Segmentation fault (core dumped)

The segfault is resulting from a scenario where the test case uses a double precision floating point value that is not supported on ARC. To work around the issue the failing GDB test case should be updated to not use floating point numbers so that it works on all devices as expected.


Unable to access Terraform Cloud due to "invalid certificate: UnknownIssuer"

Hey Christian!
I was trying out your tfct cli and I'm running into some TLS errors due to Zscaler intercepting all of the traffic and breaking TLS. I'm not familiar with rust, but I was able to workaround this same problem using python and installing pip-system-certs.
From what I have found online, this could be fixed with using rustls-native-certs instead of webpki-roots because it will read my local certificate store instead of Mozilla's. I did try creating an environment variable RUSTUP_USE_CURL=1 but that didn't change the error below.
[2024-04-17T15:17:07Z INFO  tfct::cli::command::workspace::list] Retrieving Workspaces.
[2024-04-17T15:17:07Z INFO  tfc_toolset::workspace] Retrieving the initial list of workspaces.
[2024-04-17T15:17:07Z WARN  rustls::session] Sending fatal alert BadCertificate
[2024-04-17T15:17:07Z WARN  rustls::session] Sending fatal alert BadCertificate
Error:   x An error occured while creating a new object: invalid certificate: UnknownIssuer

Nice, good to know. I'm cool with making that change, I should be able to tweak and test that soon!

@RyanMarkoff-eaton I have the new version publishing new using native tls, should resolve this I believe but lmk if that turns out not to be the case.

@RyanMarkoff-eaton I have the new version publishing new using native tls, should resolve this I believe but lmk if that turns out not to be the case.

Awesome! I'll give it try

@RyanMarkoff-eaton I have the new version publishing new using native tls, should resolve this I believe but lmk if that turns out not to be the case.

That fixed it, thank you!!


problem with powershell installer

This was experienced in deno_std CI
##[section]Starting: PowerShell
==============================================================================
Task         : PowerShell
Description  : Run a PowerShell script on Linux, macOS, or Windows
Version      : 2.151.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
==============================================================================
Generating script.
========================== Starting Command Output ===========================
##[command]"C:\windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\a\_temp\f19fe38a-bd1a-4e5d-a15f-a4eeb59e2c28.ps1'"
iwr : The magic number in GZip header is not correct. Make sure you are passing in a GZip stream.
At D:\a\_temp\f19fe38a-bd1a-4e5d-a15f-a4eeb59e2c28.ps1:2 char:1
+ iwr https://deno.land/x/install/install.ps1 -out install.ps1; .\insta ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Invoke-WebRequest], InvalidDataException
    + FullyQualifiedErrorId : System.IO.InvalidDataException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

##[error]PowerShell exited with code '1'.
##[section]Finishing: PowerShell

This might be related to registry changes I've been making. In particular it seems that Content-Encoding: gzip header is being forwarded from github, but the body is plaintext for Content-Encoding: gzip


Add support for catalyst

C++ implementation: https://github.com/apple/swift/pull/29017
Also fixes test/Driver/print_target_info.swift

@swift-ci please test

Ah, there are conflicts due to other things that have gone in. This LGTM when those are resolved.

@DougGregor Okay, resolved. Looks like CI needs to be kicked off again.

@swift-ci smoke test

@swift-ci test

@swift-ci please test


Update hakyll-template.hsfiles

Create .ghci, changed hakyll version build depend to 4.7.*, removed setup.hs

I'd recommend just merging this yourself, and pushing future changes directly. No need to stand on formality :)

Will do. Thank you.


NTR: coenzyme A binding

Hello,
Is it possible to have a term 'Coenzyme A binding'?  There is  GO:1905502
'acetyl-CoA binding' but it's not suitable for the case I am checking.
Thanks,
Penelope
Originally posted by @pgarmiri in https://github.com/geneontology/go-annotation/issues/2927#issuecomment-611385597

Add CoA synonym


Update README.md

@buketgul23 this content is still relevant and useful. What necessitates removing it?

Closing due to inactivity