Studio: Failed to resolve import "replicad.d.ts?raw"

Hi,
I tried to build the studio following the instructions . but have this Error. I ran npm i in the root too.
[plugin:vite:import-analysis] Failed to resolve import "../../node_modules/replicad/dist/replicad.d.ts?raw" from "src/workbench/EditorPane.jsx". Does the file exist?
C:/Dev/Sources/replicad/packages/studio/src/workbench/EditorPane.jsx:6:26
20 |  import { observer } from "mobx-react";
21 |  import Editor from "@monaco-editor/react";
22 |  import replicadTypes from "../../node_modules/replicad/dist/replicad.d.ts?raw";
   |                             ^
23 |  import Splitter, { GutterTheme, SplitDirection } from "@devbookhq/splitter";
24 |  import "./loadMonaco";
    at TransformPluginContext._formatError (file:///C:/Dev/Sources/replicad/packages/studio/node_modules/vite/dist/node/chunks/dep-CDnG8rE7.js:49193:41)
    at TransformPluginContext.error (file:///C:/Dev/Sources/replicad/packages/studio/node_modules/vite/dist/node/chunks/dep-CDnG8rE7.js:49188:16)
    at normalizeUrl (file:///C:/Dev/Sources/replicad/packages/studio/node_modules/vite/dist/node/chunks/dep-CDnG8rE7.js:63984:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///C:/Dev/Sources/replicad/packages/studio/node_modules/vite/dist/node/chunks/dep-CDnG8rE7.js:64116:39
    at async Promise.all (index 7)
    at async TransformPluginContext.transform (file:///C:/Dev/Sources/replicad/packages/studio/node_modules/vite/dist/node/chunks/dep-CDnG8rE7.js:64043:7)
    at async PluginContainer.transform (file:///C:/Dev/Sources/replicad/packages/studio/node_modules/vite/dist/node/chunks/dep-CDnG8rE7.js:49034:18)
    at async loadAndTransform (file:///C:/Dev/Sources/replicad/packages/studio/node_modules/vite/dist/node/chunks/dep-CDnG8rE7.js:51867:27
Click outside, press Esc key, or fix the code to dismiss.
You can also disable this overlay by setting server.hmr.overlay to false in vite.config.js.

I tried again and it works for me. I guess this is a Windows + vite issue, but I do not have a windows machine to debug it myself.

I solved it by changing this path:
'"../../node_modules/replicad/dist/replicad.d.ts?raw"'
I will create a PR when back at my PC ...


fixing React Example of Marupay Package fixed #18

fixing React Example of Marupay Package fixed #18

Hey @abdiaziiz-Arrale thanks for first contribution.
Regarding to this pull, I liked the way you did it. But I do have some suggestions:

Adding a new way that user could choose which payment he needs either edahab and waafi
Also I see only the purchase one, are you planning to add the credit one also. It dont have to be separate just add a new button that could initiate the credit method.
Are you planning an example that it could directly call the sdk without the need of any api.
And lastly, somehow the button un-clickable :)

Thanks again


Doubleclick to insert text should deselect parent element

Not a huge problem, but doesn't look right, and has weird behavior in some edge cases.
test plans
Scenario A:

Select empty-fill rectangle.
Doubleclick inside it to create text.
Should deselect rectangle.

Scenario B:

Doubleclick inside background-filled rectangle to create text.
It selects the rectangle, and keep it selected during editing the text. It should deselect the rectangle, instead.

Hey @dwelle! I'd love to take a look at this!

Fix is up. Looking forward to folks' input since I'm still not totally sure what's the expected behavior is.


[WIP] / [DRAFT] / [ETC] implement uri method

resolves #278
mostly here so that I have a nice overview of my changes.

Gonna close this one for now, I think it's too complicated with how we need to pass in variables. Thanks for looking into it!


update openshift and microshift bundles to 4.13.9

bump OpenShift and MicroShift bundles to 4.13.9
cut v2.26.0

/test e2e-crc

/retest

integration-crc failure is known (http proxy config leaking to unrelated test scenarios), e2e-crc failed on certificate rotation test
 --- Failed steps:
  Scenario: Start CRC "in the future" and clean up # features/cert_rotation.feature:9
    When checking that CRC is running # features/cert_rotation.feature:14
      Error: not found: running. Timeout
33 scenarios (32 passed, 1 failed)
270 steps (266 passed, 1 failed, 3 skipped)
1h32m38.63376152s


OCI manifest found, but accept header does not support OCI manifests

Description
Content translated using ChatGPT, please forgive any errors.
I encountered an error while downloading Docker images. It says OCI manifest found, but accept header does not support OCI manifests, which is a strange problem. I tested with two images. The nginx:1.18.0-alpine image can be downloaded successfully, but the nginx:stable-alpine3.19-perl image fails to download. I'm not sure what the reason is behind this. Could you please help me figure it out?
Reproduce
I've outlined a process for downloading Docker images:

Request the token for downloading from https://auth.docker.io/token?service=registry.docker.io&scope=repository:library/nginx:pull.
Fetch the image manifest from https://registry-1.docker.io/v2/library/nginx/manifests/stable-alpine3.19-perl.
Fetch the layer list from https://registry-1.docker.io/v2/library/nginx/manifests/sha256:xxx.

The issue arises in step 3. While nginx:1.18.0-alpine can be successfully fetched, nginx:stable-alpine3.19-perl returns an error message: OCI manifest found, but accept header does not support OCI manifests.
Expected behavior
I'm looking to resolve the issue where nginx:stable-alpine3.19-perl can successfully retrieve layer information.
registry version
nginx:stable-alpine3.19-perl
Additional Info
No response

This is the wrong repo to ask questions about Docker Hub. Docker Hub is a commercial offering hosting Docker Official Images such as the nginx image you are trying to download. Please open an issue in https://github.com/docker/hub-feedback
Closing


Confluence Page attachments are deleted while orphanRemovalStrategy=KEEP_ORPHANS

Thanks for this great project.
Here is a scenario causing issue:

Create adoc page with some attachments (e.g. image: or plantuml:)
Publish page to Confluence
Remove the attachment from adoc
Re-publish
In Confluence, browse to page attachments to see that the attachment was deleted even if KEEP_ORPHANS is set

.Example logs:
Updated page 'MyProject - Tests' (id 133606310, version 25 -> 26)
Deleted attachment 'MyProject-some-image.png' (page id 133606310)
NOTE:
A Confluence instance may be setup with preventing delete.
If so, the re-publish step will fail with error and prevents full doc publication.
Any of below ideas would help bypass this use-case:

When KEEP_ORPHANS, simply skip attachment deletes like done for pages
If need to make a difference between Pages and Attachments, introduce option such as KEEP_ORPHANS_ATTACHMENTS
If such delete attachment operations fails, perhaps this is not important, and publish should continue next, with WARNING log

Hi @cstettler
Exactly, an option "no delete allowed" is the perfect understandable name for the intent when user is not allowed any deletes on the Confluence space (pages or attachments)

Hi @cstettler
Is this possible to follow-up on this issue?


Mockery doesn't seem to be doing anything

views.js
controllers = require '../../modules/fixture/controllers.js'
exports.custom = (db) ->
  (req, res) ->
    controllers.custom req.body
      , (result) ->
        res.json result : result
      , (error) ->
        res.json 400, error : error

test.js
mockery = require "mockery"

exports.tests = (app, db, config) ->
  describe '#routes', ->
    describe '/fixture/custom', ->
      it 'should return status 400 if no request body was provided', (done) ->
        request app
          .post '/fixture/custom'
          .send
            body :
              players : []
          .expect 400, done

  describe '#views', ->
    describe '#custom', ->
      controller =
        custom : (body, success_callback, error_callback) ->
          console.log "###MOCK CONTROLLER BODY: #{req}"
          if body
            success_callback 'result'
          else
            error_callback 'error'
      mockery.enable()
      mockery.registerAllowable '../../modules/fixture/controllers.js', true
      mockery.registerMock '../../modules/fixture/controllers.js', controller

      it 'should return json keyed by result on success callback', (done) ->
        req =
          body : true
        res.json = (response) ->
          response.result.should.eql 'result'
          done()
        custom req, res

I get the error TypeError: Cannot read property 'should' of undefined which I have confirmed is due to my mock not getting registered as I'd like.
I'm thinking the problem is that require(../../modules/fixture/controllers.js) is happening before test.tests(app, db, config) is called, and so the require cache is already created.
Shouldn't mockery.registerAllowable('../../modules/fixture/controllers.js', true) allow me to override already required modules? I require quite a lot of switching between real and mock modules throughout many tests, so I'd prefer to be able to register mocks "just in time" rather than all at the beginning, for instance before instantiating my express app. Is this possible?

@carn1x Did you ever figure out whether or not "just in time mocking" is possible?

Sorry @BillBrower, I did crack this, and I'm pretty sure I did it with mockery, but unfortunately I've long since stopped using Node and no longer have access to the source code of the related project so apologies I can't give any useful advise now :(


Use systemd as cgroup driver

How to categorize this issue?

/area open-source
/kind enhancement
What would you like to be added:
With https://github.com/gardener/gardener/pull/5255 we have switched the cgroup driver from cgroupfs to systemd for shoots >= 1.23. However, this change was reverted with https://github.com/gardener/gardener/pull/5324.
Let's look into that the consequences of this change are, how the container runtime needs to be configured and how to properly roll this out.
Why is this needed:
Following upstream recommendations.
Work Items

[ ] Switch default kubelet configuration to systemd for all k8s versions >= 1.24 as was done in https://github.com/gardener/gardener/pull/5255/files#diff-fc4776dd3fd3277fcbaac11c0bcfe15e6bd797038eb1cc601444de5ca4c3bc68 but later reverted

We don't care about docker configuration as that's not a possible configuration in Gardener for k8s >= 1.23

[ ] Introduce a property/helper function to figure out what the cgroupfs driver configuration is
[ ] Switch g/g containerd configuration to respect the selected cgroupfs driver

Adapt containerd bootstrapping in OS extensions to use systemd as cgroupfs driver

Pass in an additional parameter similar to isContainerDEnabled that indicates which cgroupfs driver is used.

[ ] Gardenlinux
[ ] Flatcar
[ ] Ubuntu
[ ] SUSE Chost

Open Questions

How do we prevent running with systemd as cgroupfs driver when the OS extensions have not been updated to respect this in their bootstrapping logic?
Should we have a killswitch e.g. in cloud-config/kubelet reconfiguration that throws and error when there's a mismatch between kubelet config and containerruntime?

Thinking again on this topic, Gardener can configure both kubelet and containerd (similarly to how it control the pause image) to use the wanted cgroup driver, so from this point of view the OS extensions should not do anything.  What do you think?

Thinking again on this topic, Gardener can configure both kubelet and containerd (similarly to how it control the pause image) to use the wanted cgroup driver, so from this point of view the OS extensions should not do anything. What do you think?

I can see how gardener modifies the containerd configuration file to inject the pause image and was thinking about something similar for the cgroup driver setting as well. This would, however, mean that we bootstrap a node first with the containerd configuration file from the OS extensions (flatcar example here, and later on change the cgroup driver, when the cloud-config is applied. My understanding was that changing the cgroup driver for a running node was something we would want to avoid? Or do you think in this scenario this would be okay?

@vpnachev do you have some thoughts on the above discussion? It may be that we have some time to pick this up in the near future.

/remove-lifecycle stale
cc @MrBatschner

I understand that this is only a prerequisite for enabling cgroupsv2, but please be aware that additional things need to be done before switching the cgroup:

[ ] ensure that we're using at least containerd 1.5.12 or 1.6.3 to get the fix for incorrectly detected OOMKill events, or otherwise VPA cannot act on OOMKill events.

And a few interesting things from https://blog.kintone.io/entry/2022/03/08/170206
For example (taken from the above link) regarding uber-go/automaxprocs:

If you're using a version until v1.4.0, you need to patch it with a cgroup v2 PR or set GOMAXPROCS manually for a while.

And regarding the JDK version

We need to use JDK 15 or later to run Java applications properly in the cgroup v2 environment. Let me describe it briefly.
JDK has built-in support for the container environment from version 8u131. JDK 10 introduced the +UseContainerSupport option and enabled it by default. With this option, JDK inspects the cgroup filesystem and reads the CPU and memory quotas for its use. The CPU quota information is available on Runtime.availableProcessors() (see Docker blog for details). The memory quota affects its heap memory usage. This mechanism should be adjusted for cgroup v2, and the fix became available with JDK 15.

/remove-lifecycle stale
/lifecycle frozen

/assign @danielfoehrKn

ping @danielfoehrKn @MrBatschner

@danielfoehrKn @MrBatschner Could you check the PR description and tell whether this is still up-to-date/the plan you are pursuing?

Sorry for the delay in answering. The PR linked above is meant to configure containerd and kubelet on Garden Linux to use systemd as cgroup driver if cgroup v2/unified hierarchy is detected (as Garden Linux 934 came with cgroup v2 support). However, this is just for Garden Linux. The CoreOS/FlatCar extension contains similar code and eventually, the Ubuntu and cHost extensions would require such code too - especially since the systemd announced to drop cgroup v1 support in a future release. Instead of having quite similar code to deal with the cgroup versions in each operating system extension separately, we should explore if this can be moved into the OS config part of Gardener itself - and that is the direction @danielfoehrKn and myself were looking into so far. Thus, this issue in my opinion is still relevant.

With https://github.com/gardener/gardener/pull/10472, starting K8s 1.31 the cgroup driver of kubelet and containerd is being defaulted to systemd.


Changed a reference to deprecated BASE_URL to the new WAGTAILADMIN_BASE_URL

The docs didn't match the code, so an user trying to set BASE_URL as shown will do nothing.

@xbello - thanks for this! We really appreciate it.
We do not add changelog entries for small docs fixes but will add you to the contributors list as Xabier Bello - let me know if you want a different name shown.


Partial parsing of configuration

I've noticed that the port number is parsed using Confex but not the host name value. Is this intentional?

Stacktrace:
** (Mix) Could not start application maru: Maru.start(:normal, []) returned an error: an exception was raised:
    ** (FunctionClauseError) no function clause matching in String.to_charlist/1
        (elixir) lib/string.ex:1834: String.to_charlist({:system, :bitstring, "API_HOST", "<IP_ADDRESS>"})
        (maru) lib/maru/supervisor.ex:48: Maru.Supervisor.to_ip/1
        (maru) lib/maru/supervisor.ex:38: Maru.Supervisor.endpoint_spec/3
        (maru) lib/maru/supervisor.ex:18: anonymous fn/4 in Maru.Supervisor.init/1
        (elixir) lib/enum.ex:1811: Enum."-reduce/3-lists^foldl/2-0-"/3
        (maru) lib/maru/supervisor.ex:16: anonymous fn/2 in Maru.Supervisor.init/1
        (elixir) lib/enum.ex:1811: Enum."-reduce/3-lists^foldl/2-0-"/3
        (maru) lib/maru/supervisor.ex:15: Maru.Supervisor.init/1

Hi @jalcine
confex is a soft depend of maru, that means if it is added in your deps list, maru will use it, if you haven't added it, maru will treat all the config values as tring.
so I guess adding confex to your deps list in the mix.exs file will resolve your problem 🙂

Understood.
Something like this has to be in the README. I can open a pull request for that.

It will be great if you can do the help!

Just noticed that this didn't answer the question, though. Two things have to be done:

[ ] Adding information to the README about the optional dependency on confex,
[ ] Having all of the configuration for Maru resolvable by Confex resolvable vs only one option.


⚠ Telly has degraded performance

In 13ee39d, Telly ($TLY) experienced degraded performance:

HTTP code: 200
Response time: 3233 ms

Resolved: Telly performance has improved in 0e3b72f.


Reworked footer styling

Un-fixed footer from the bottom of the page. Now the footer will just be appended to the bottom (so pages with scrolling enabled should work properly).

Everything looks good. We should probably look at maybe adding a spacer or something that, if content does not fill up the entire screen, will separate the footer and content. We might be able to do this in CSS but it's not that big of a deal right now.


Update dependency version of GCDAsyncSocket pod

https://github.com/robbiehanson/CocoaAsyncSocket/blob/7.5.0/Source/GCD/GCDAsyncSocket.h#L1048
CococAsyncSocket v7.5.0 still use the following declaration.
@protocol GCDAsyncSocketDelegate
But in the the un-released version v7.5.1 the statement has been correctly.
@protocol GCDAsyncSocketDelegate<Object>
podspec:  dependency of  CocoaAsyncSocket should be updated after/if CocoaAsyncSocket is released

I really should get around to that
On Sun, Oct 23, 2016 at 11:35 PM, raxcat<EMAIL_ADDRESS>wrote:

https://github.com/robbiehanson/CocoaAsyncSocket/blob/7.5.0/Source/GCD/
GCDAsyncSocket.h#L1048
CococAsyncSocket v7.5.0 still use the following declaration.
@protocol GCDAsyncSocketDelegate
But in the the un-released version v7.5.1 the statement has been correctly.
@protocol GCDAsyncSocketDelegate
podspec: dependency of CocoaAsyncSocket should be updated after/if
CocoaAsyncSocket is released
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/chrisballinger/ProxyKit/issues/15, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfqH-twfahM0LDInELHv3YIWHnCcpJiks5q3FGwgaJpZM4KecK3
.

Thank you :)

Done


Build shared lib directly, remove OSX hack.

Should allow building on all architectures supported by Node.js and Rust.
Builds fine on Linux, although the .node file refers to ../target/release/libfoo.so directly so the require('neon').load() only works in the build directory of the package.
Not sure how it worked at all on OSX before, I'd love to see the result of ldd build/Release/*.node (or the OSX equivalent thereof).

Interesting, I got this from the compiled hello.node lib:
> require('./build/Release/hello')
{ '\u0000\u0000\u0000\u0000\u0000': [Function] }
> for (var k in a) { a[k]()}
'hello node'

@diorahman Yes, that's fixed by dherman/neon#22.

@eddyb thanks!

Turns out shared libs are not worth creating because .node is already a shared lib and it's easier to link everything into it statically.

FYI when I follow the example on FreeBSD 11 CURRENT December node 4.2.3 i get
node -e 'require("./")'
/xxx/hello/lib/index.js:3
console.log(neon.hello());

TypeError: neon.hello is not a function
    at Object.<anonymous> (/xxx/hello/lib/index.js:3:18)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at [eval]:1:1
    at Object.exports.runInThisContext (vm.js:54:17)
    at Object.<anonymous> ([eval]-wrapper:6:22)

But when I follow the steps by @diorahman in https://github.com/dherman/neon-cli/pull/6#issuecomment-167090983 I get the same positive outcome with no error :)
BTW Loving this cool stuff <3

@No9 It seems that @dherman did not update the crates.io version of neon - so you're not getting the fix at dherman/neon#22.
If you replace the crates.io version dependency on neon with a github one (https://github.com/dherman/neon should work), and run cargo update followed by npm install, you should get a fully functional .node addon.

Thanks @eddyb for your help
After trying that update I seem to have walked into an unrelated issue
/xxx/neon-cli/lib/create.js:64
    { type: 'input', name: 'author',      message: "author",           default: guess.author   },
TypeError: Cannot read property 'author' of undefined
    at wizard (/usr/home/anton/builds/neon-cli/lib/create.js:64:86)
    at Object.<anonymous> (/usr/home/anton/builds/neon-cli/bin/cli.js:64:3)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Function.Module.runMain (module.js:467:10)
    at startup (node.js:136:18)
    at node.js:963:3

FWIW I am running neon-cli linked not installed I'll try and come back to it at some stage and work out why

Yeah, updating the deps, on the e.g. hello's Cargo.toml and the ../neon is dherman/neon seems working:
[dependencies]
neon = { version = "0.1", path = "../neon" }

@diorahman git = "https://github.com/dherman/neon" in Cargo.toml is what I meant (where you currently have path = "../neon".

OK.
Got this one:
/home/diorahman/Experiments/misc/rs/neon/src/hello/build/Release/hello.node
module.js:460
  return process.dlopen(module, path._makeLong(filename));
                 ^

Error: ../target/release/libhello.so: cannot open shared object file: No such file or directory
    at Error (native)
    at Object.Module._extensions..node (module.js:460:18)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.load (/home/diorahman/Experiments/misc/rs/neon/src/hello/node_modules/neon-bridge/lib/index.js:19:10)
    at Object.<anonymous> (/home/diorahman/Experiments/misc/rs/neon/src/hello/lib/index.js:1:97)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)

Do you have any ideas?
Previously I copy the target directory to ... The application is working it seems there is a problem regarding to the process cwd.

@diorahman You're not using the latest version of this PR, maybe? I've switched from linking a dylib into the .node to linking a staticlib, which seems to work much better for me.

@eddyb thanks! Now everything works as expected!

This is great. I'll follow up immediately with the one fix needed to make it work in OS X again.


Bug: Badges and Circular progress value not visible in about section

Expected Behavior
Badges and Circular progress value should visible in the about section as it is in the example/demo site
https://hugo-toha.github.io/#about
Current Behavior
Badges and Circular progress value not visible in about section
Screenshots

I can see them. What browser are you using?

In the local setup that was downloaded from the source branch, it is not visible for all browsers.  As it is showing on the site below:
https://hugo-toha.github.io/#about
The screenshot is of the local setup.


Correct FreeBSD Python package name

Pull Request (PR) description
When trying to install Puppetboard I ran into this module trying to install virtualenv (doesn't exist as a package, only a port) and py3.9-pip (correct name is py39-pip).
Replace out the . in the version name. I did not test this extensively, just enough to get it to compile and install the right package for puppetboard. The origination of of the module doesn't seem to allow an easy way to get a default version based on OS and pass it down to python, pip, etc.
Feedback welcome.

Regarding the version, I never hit that issue.  It happen I use this in my python profile:
class profile::python {
  class { 'python':
    version => '39',
    dev     => 'present',
  }
}

The data type for the version parameter accept a large number of formats, maybe too much.
The other change seems unrelated and break CI.  Maybe worth a different PR?


Filter components not drawn

I'm using Vaadin 7.6.4, FilterTable 0.9.15.v7. I recently changed the datasource backing my table from a BeanItemContainer to an IndexedContainer because the BeanItemContainer performance was very slow. Using an IndexedContainer gave me great responsiveness however, now when I call setFilterBarVisible, the filter row is inserted but there are not components in the cells to accept data entry.
Each of the filter cells contains only the place holder div.

Am I doing something wrong?

I found my problem. The BeanItemContainer I used before knows all of the column types at construction time. With my IndexedContainer, I wasn't adding the item property defintions until after the FilterTable was already constructed. I changed my container to make sure all the item properties were defined prior to passing it on the FilterTable constructor and that fixed the problem


Emulate locale settings for specified app.

📝 Provide a description of the new feature
Backdrop
The most of OS except Windows has already used UTF-8 as preferred default encoding in several years.
But Windows still use locale encoding in the bulk of countries and regions. UTF-8 code page of Windows is still in beta.
Therefore, there are still so many applications that use locale encoding. It bothers the multilingual users.
For example, I'm a Chinese mainland user, my default code page is 936 (GB2312). But I use some Taiwanese software that use code page 950 (Big5). And sometimes I play the Japanese game that use code page 932 (Shift-JIS).
Solution
In Windows itself, change the locale setting is not convenient, it need to restart computer.
Fortunately, there is an open source utility to solve the problem. It's Locale-Emulator.
As mentioned in the backdrop, this is a general problem in Windows. So I think it will be awesome if solved by PowerToys.
Design
Locale-Emulator made a good job, but I think it will be greater if we can storage and manage the locale emulating settings centralized in one place. Just like what the Keyboard Manager do.
Set the code page, region and time zone. Then set the path of executable or just executable name.
Once we start the application, PowerToys will hook it and emulate the locale.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Great scenarios and really does help me understand the issue.


how to generate id field into gql mutation input

Currently, in entgql mutation input, the primary key field  is ignored. what can I add the id field and set it nullable?
i expect id value can be passed on mutation. or auto generate by default function.
....
func (User) Fields() []ent.Field {
   return []ent.Field{
   	field.String("name").
   		Default("Anonymous"),
   }
}
...

expect
type CreateUserInput {
  id: ID
  name: String!
}
input UpdateUserInput {
  id: ID!
  name: String!
}
type Mutation{
  createUser(input: CreateUserInput!)
 updateUser(input: UpdateUserInput!)
}

on doc Mutation Inputs
The idea is to insert the data into the associated table and then update it. If I can determine the ID beforehand, then I can just use the Insert methoda and reduce sql execution

Hey @tsingsun 👋
You can extend the generated mutation input types with your fields as follows:
extend input CreateTodoInput {
  id: ID
}

See this example: https://github.com/ent/contrib/blob/master/entgql/internal/todo/todo.graphql#L36-L38

thx ,it is a way. but i must resolve id myself because go struct "CreateTodoInput" has not id field.
SoI try to override gql_mutation_input.tmpl,generate code like:
type CreateUserInput struct {
   ID: *int
   Name: string
}

Will you consider adding an option to add the id field to the mutation input struct and ent.graphql?

Hi @tsingsun ! How did you manage to add the ID field to CreateInput?
I'm struggling to set primary key from input. Cannot figure out the right approach.


Can stick fields in columns

Totally unnecessary
Following #243

Haha, was this on our feature list?

I thought it would be fun :p


clipping of adversarial examples missing in PGD attack

Describe the bug
For the projected gradient descent attack, we need to perform two projections.

ensure that the perturbation do not exceed the maximum allowed perturbation
ensure that the resulting adversarial example is in the valid image range.

In the current implementation, the second projection is missing. I was getting very different results for the robustness accuracy to a PGD attack when using ART or the code from the TRADES paper. The resulting adversarial examples do not conform to the clip values set in the PyTorch classifier
Upon looking at the code, I found that the projection step to a valid image is missing.
In the original code from madry's lab, this projection can be seen here: https://github.com/MadryLab/cifar10_challenge/blob/master/pgd_attack.py#L59
In the code from the TRADES paper, the corresponding projection for an image normalized between 0 and 1 can be seen here: https://github.com/yaodongyu/TRADES/blob/master/pgd_attack_cifar10.py#L78
In the following ART's code, https://github.com/IBM/adversarial-robustness-toolbox/blob/master/art/attacks/fast_gradient.py#L273
I believe the following addition should be made.
if project:
    perturbation = projection(x_adv[batch_index_1:batch_index_2] -x_init[batch_index_1:batch_index_2], eps, self.norm)
    x_adv[batch_index_1:batch_index_2] = x_init[batch_index_1:batch_index_2] + perturbation
    # addition
    if hasattr(self.classifier, 'clip_values') and self.classifier.clip_values is not None:
        clip_min, clip_max = self.classifier.clip_values
        x_adv[batch_index_1:batch_index_2] = np.clip(x_adv[batch_index_1:batch_index_2], clip_min, clip_max)

Note:
I am using art 0.10

Hi @fahad92virgo Thank you for describing your observation. We will look at it as soon as possible. Would it be possible for you to share a short code section of how you are using PGD so that we can reproduce it?

Hi @fahad92virgo I have compared PGD of ART and TRADES on the same datasets using pgd_attack_cifar10.py and pgd_attack_mnist.py of TRADES and I have obtained numerically identical results in terms of error and adversarial pixel values for MNIST and CIFAR10 using the default eps and step_size values of TRADES. In my tests all adversarial samples had all pixel values within the clip_values and I did not observe any pixel values outside of this valid image range.
As far as I can see it should not be necessary to add an additional clipping to line 277 because we are clipping the values to the image range with _apply_perturbation in line 271. Between lines 271 and 277 we are applying only the projection to eps.
To get exactly comparable results with PGD of ART and TRADES I have also tested turning off the random initialisation in both. It looks like that for TRADES the argument --random=False does not turn off random initialisation, I think because of missing conversion to type bool, therefore I have manually commented the lines 63-65 in the TRADES codes for MNIST and CIFAR10.
I would be very interested to see your code and to learn how you have created the described behaviour to make sure that we find all potential bugs. Until then I will close this issue.


use busy stack instead of binary busy state

LGTM with two questions that may be suggestions for changes depending on the answer :)

We needed the fix for downstream apps, so I committed. @Cypher1: is not intended to gloss over your questions. Let's follow up.

We needed the fix for downstream apps, so I committed. @Cypher1: is not intended to gloss over your questions. Let's follow up.

100%, I LGTM'd it.


Run azure/webapps-container-deploy@v1 took 15 minutes with many 500s and failed attempts

Reading the log, it's not actually clear to me that it succeeded even though it shows green.
Here's the log:

[PATCH]https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.Web/sites/mywebapp_redacted/config/web?api-version=2016-08-01
Updated App Service Configuration settings.
Restarting app service: mywebapp_redacted
[POST]https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.Web/sites/mywebapp_redacted/restart?api-version=2016-08-01
Restarted app service: mywebapp_redacted
[POST]https://management.azure.com/subscriptions//resourceGroups/***/providers/Microsoft.Web/sites/mywebapp_redacted/config/appsettings/list?api-version=2016-08-01
[PUT]***mywebapp_redacted.scm.azurewebsites.net/api/deployments/2b5011fd3706e5e9c7d2fa574671e8d0fe8f74431582307999581
[PUT]***mywebapp_redacted.scm.azurewebsites.net/api/deployments/2b5011fd3706e5e9c7d2fa574671e8d0fe8f74431582307999581
[PUT]***mywebapp_redacted.scm.azurewebsites.net/api/deployments/2b5011fd3706e5e9c7d2fa574671e8d0fe8f74431582307999581
Could not parse response: ***
Response: undefined
Encountered a retriable status code: 503. Message: 'Service Temporarily Unavailable'.
[PUT]***mywebapp_redacted.scm.azurewebsites.net/api/deployments/2b5011fd3706e5e9c7d2fa574671e8d0fe8f74431582307999581
Could not parse response: ***
Response: undefined
Encountered a retriable status code: 503. Message: 'Service Temporarily Unavailable'.
[PUT]***mywebapp_redacted.scm.azurewebsites.net/api/deployments/2b5011fd3706e5e9c7d2fa574671e8d0fe8f74431582307999581
Could not parse response: ***
Response: undefined
Encountered a retriable status code: 502. Message: 'Bad Gateway'.
[PUT]mywebapp_redacted.scm.azurewebsites.net/api/deployments/2b5011fd3706e5e9c7d2fa574671e8d0fe8f74431582307999581
Successfully updated deployment History at https://mywebapp_redacted.scm.azurewebsites.net/api/deployments/2b5011fd3706e5e9c7d2fa574671e8d0fe8f74431582307999581
[POST]https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.Web/sites/mywebapp_redacted/publishxml?api-version=2016-08-01
Could not parse response: ***
Response: undefined
App Service Application URL: https://mywebapp_redacted.azurewebsites.net

Thanks for reporting the issue @darzu . Could you please use azure/webapps-deploy@v2 action in your workflow in place of azure/webapps-container-deploy and confirm if you are still seeing this issue?

Closing due to no response from the customer. Please comment to re-open.


Consider using kong prometheus plugin

After moving to kong 0.14 we can use Kong prometheus plugin:
https://docs.konghq.com/hub/kong-inc/prometheus/
https://grafana.com/dashboards/7424

I investigated the work of this plugin and a general decision was made by the ops team. Currently, we use the too old version of kong, after update kong we will be able to deploy this plugin.


What are the differences between rxjs and @reactivex/rxjs

It appears that there are 2 packages on npm. What are the differences between them?

Scoped pkg was to include all module output, but now 'rxjs' does and we plan to deprecate scoped one eventually.


Terragrunt destroy takes very long becuase of git show-toplevel

Hello,
I have a monorepo with several terragrunt deployments. When I want to destroy a specific terragrunt resource via terragrunt destroy, terragrunt takes a very long time to resolve for affected dependencies to destroy because it crawls for affected dependencies via git rev-parse --show-toplevel. This makes a simple resource destruction take ~10mins which is a really long time.
Is there a smarter way to do this? Maybe by specifying a boundary of which to crawl for dependencies?

We also affected by terragrunt destroy takes long time issue, terragrunt apply is not affected and is near instant.
terragrunt version 0.51.6
When running terragrunt destroy --terragrunt-log-level debug we can see that
terragrunt goes through every child directory in the repo and evaluates locals, which takes time.
We are not using dependencies much, and as a workardound, we've done the following:
mkdir $REPO_ROOT/0-terragrunt-destroy-workaround
tee $REPO_ROOT/0-terragrunt-destroy-workaround/terragrunt.hcl <<EOF >/dev/null
locals {
  raise = get_env("DOES_NOT_EXIST")
}
EOF

The workaround causes terragrunt to fail early the "evaluate all locals" stage, but
doesn't seem to affect destroy/apply commands and it's working fine from what we can tell.
Why terragrunt tries to evaluate all locals in every child directory when doing destroy even when no dependencies are used?

Anyone know which version introduced this bug?
We've just moved to terraform 1.6.2 and terragrunt 0.52.5 and terragrunt destroy actions now take 30mins or more.
We use a mono-repo for a 'controlplane layer' and having a destroy action evaluate everything takes an age.
Plan and Apply don't have this behaviour, so it seems strange that Destroy does.

Hitting the same issue, was updating our binaries and noticed that it was taking an excruciatingg amount of time. Even on the latest version so this is not fixed yet.. so will lock our version to 0.51.8 as well, which is working fine.
@denis256 this seems like a bit of a bug, any way to raise priority on this ?

Same issue here, destroying takes about 15 minutes before it even starts showing something. v0.52.5, not the most recent but I understand it isn't solved in the latest version anyways.

This issue is still present. It seems this functionality is running git rev-parse even if there are no .git directories which makes for ugly output and there's no way to suppress it even though it doesn't functionally affect terraform:
fatal: not a git repository (or any of the parent directories): .git

exit status 128

Hello everyone,
this should be better now since #3534 and release v0.68.8
try running:
terragrunt destroy --terragrunt-no-destroy-dependencies-check

@dustyhorizon ,
Would you be able to confirm this? If so, we can close out this issue.

Works for me. Thanks guys!

Thanks for confirmation, @gercograndia .
Closing this issue out. Please feel free to open another if you have any other issues, @dustyhorizon !


Question: Private registry instructions

I was just wondering why the instructions for how to use testcontainers with a private registry where removed in https://github.com/testcontainers/testcontainers-python/pull/579 .
Does that guide does not apply anymore? Thanks

Probably a bad rebase, thanks for catching
On Tue, Jul 2, 2024, 4:15 AM Domenico @.***> wrote:

I was just wondering why the instructions for how to use testcontainers
with a private registry where removed in #579
https://github.com/testcontainers/testcontainers-python/pull/579 .
Does that guide does not apply anymore? Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/testcontainers/testcontainers-python/issues/632, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACECGJHDNSSNAWJFMIDIC7TZKJOTRAVCNFSM6AAAAABKHAPIBWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4DKNJWGY4DAMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


chore(cli): templates/base/App.tsx.ejs: remove superfluous EJS brackets

My best guess is that EJS was silently omitting these in output. Remove them to avoid confusion.

I did at least 1 build with this change that worked and am continuing some now, but some other parts of my local dev environment are borked (notably, prettier), so external verification would be appreciated!


Start rustformat config

Dearest Reviewer,
rustfmt seems to be the winning formatter. Cargo holds to a 80 character line max. It  would be good if the formatter would just work for the project. Discussed a bit in #2467 I checked and about 330 lines are currently over 80 characters. Keeping the style check at a limit of 100 would prevent a bulk reformatting and allow it to happen over time.
Thanks
Becker

r? @huonw
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks! I'd prefer to hold off on this for now until we actually rustfmt the whole repo though, perhaps. Just adding this for now probably won't gain much benefit :(

Howdy.
Is there a plan to do a bulk reformat? This config would with help to keep the formatting the same between different systems. I guess who ever does the bulk formatting can create this file as well. I will close it.
Thanks
Becker

Currently, no I haven't looked into doing a bulk reformat just yet. I'd want to add a "rustfmt check" as part of the CI afterwards as well (to ensure that we're always checking in with the rustfmt format), and I just haven't gotten around to doing that yet.
There's also a few things I'd like to see done in rustfmt as well...


Create new method to return executions by job name

@RequestMapping(value = "/jobs/executions/{jobName}", method = RequestMethod.GET)
public Set<Long> findLastExecutions(@PathVariable String jobName) throws NoSuchJobExecutionException {
	List<JobInstance> jobInstances = jobExplorer.getJobInstances(jobName, 0, 10);

	Set<JobExecution> jobExecutions = new HashSet<JobExecution>();
	for(JobInstance jobInstance : jobInstances){
		jobExecutions.addAll(jobExplorer.getJobExecutions(jobInstance));
	}

	if (jobExecutions.isEmpty()) {
		throw new NoSuchJobExecutionException("There is not any JobExecution for the job '" + jobName + "'.");
	}

	return runningExecutionTracker.getAllRunningExecutionIds();
}

Please create a merge request


Support column alias: SELECT * FROM Table AS T (C1, C2..)

Currenlty, We are not using TableAlias.columns at all.
We can implement it to use like below.
postgres> SELECT * FROM (VALUES (1, 'one'), (2, 'two'), (3, 'three')) AS t (num, letter);
 num | letter
-----+--------
   1 | one
   2 | two
   3 | three

postgres> CREATE TABLE Items (id int, name text);
postgres> INSERT INTO Items VALUES(1, 'glue'),(2, 'sql');
postgres> SELECT * FROM Items AS A (col_alias1, col_alias2);
 col_alias1 | col_alias2
------------+------------
          1 | glue
          2 | sql

Was this closed in pair with #1065? Or is this still active?

@LeoDog896 This issue has been resolved as you mentioned.

Odd that it's still open, probably just a closing mistake. Thanks for the clarification@


NetworkReachabilityManager connectionRequired flag

I'm using the latest version of NetworkReachabilityManager in a my project and I have a problem when SCNetworkReachabilityFlags contain both .isWWAN and .connectionRequired. I noticed that other libraries check if the flags contain .connectionRequired and if it's true they throw a not reachable network. Therefore, I'm wondering why NetworkReachabilityManager doesn't do it. Is it a bug or a wanted behaviour?
You debug this scenario when you have a device with a sim but the user didn't select the carrier yet.

Thanks for the report! We'll take a look!

@jshier I could have a possible fix for that. Should I create a PR or are you working on it?

A PR would be great!

https://github.com/Alamofire/Alamofire/pull/2060 Ready for review 👍

I tested the change to reachability computation on a device running 10.3.1 today and all seemed to work well.  Is there a timeframe to when this will be added or is this still under review?
Here is a link to the Gist I created to test this branch: https://gist.github.com/agnosticdev/b2c7af87fc90adb1fe87e0e203634d51

Closing this issue out in favor of #2060. Please direct all further comments to #2060. 🍻


Cannot read property 'state' of undefined

ERROR TypeError: Cannot read property 'state' of undefined
    at /usr/local/lib/node_modules/upload-gphotos/lib/index.js:603:31
    at Generator.next (<anonymous>)
    at onFulfilled (/usr/local/lib/node_modules/upload-gphotos/node_modules/co/index.js:65:19)
    at tryCatcher (/usr/local/lib/node_modules/upload-gphotos/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/upload-gphotos/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/usr/local/lib/node_modules/upload-gphotos/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/usr/local/lib/node_modules/upload-gphotos/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/usr/local/lib/node_modules/upload-gphotos/node_modules/bluebird/js/release/promise.js:693:18)
    at Async._drainQueue (/usr/local/lib/node_modules/upload-gphotos/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/usr/local/lib/node_modules/upload-gphotos/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues (/usr/local/lib/node_modules/upload-gphotos/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)
Aborted

Hi,
With this error, Can I know the photo with the error?

This caused here.
Note:
I'll try to fix Upload Error on #233.
I think almost Upload Errors are Google Photo's Error.
If you failed to upload, please try again.
When same error caused continuously, please you report via issues.

I found the problem for this error,
I try many time to upload a 12500px by 9000px photo
I found it's fail too on google photo site.
I read this ;
https://support.google.com/photos/answer/6174018?hl=en&vid=0-1025738173526-1502398038850
and it's says photos can't exceed 75MB or 100 megapixels
My photo is 12500x9000 so 112,5 megapixels
Is it possible for you to add a test for this ?
Thanks

I'll research and add test for upload limit.
This issue moved to https://github.com/3846masa/upload-gphotos/issues/246


Valid concurrent merge returns Invalid comparison operation

Environment
Delta-rs version: 0.17.2 (also tried against latest main, including https://github.com/delta-io/delta-rs/pull/2396)
Binding: python

Bug
What happened:
I was testing performing concurrent merges to different partitions. When partitioned by a string, concurrent merges to different partitions worked as expected, with both writes going through and no error raised. However, when partitioned by a date32, it raised the following exception:
CommitFailedError: Failed to commit transaction: Error evaluating predicate: Failed to convert into Arrow schema: Invalid argument error: Invalid comparison operation: Date32 <= Int64

When I change it to a sequential write, it does not raise this exception, so it is probably a bug somewhere in the logic that determines if concurrent writes conflict.
What you expected to happen:
Concurrent writes to different partitions should work even if partitioned on a non-string column.
How to reproduce it:
import datetime
from deltalake import DeltaTable, write_deltalake
import pandas as pd
import pyarrow as pa

path = "test-concurrent-merge"

df = pd.DataFrame.from_dict(
    {
        "p": [datetime.date(2020, 1, 1)],
        "k": [1],
        "v": [1],
    }
)

schema = pa.schema(
    [
        ("p", pa.date32()),
        ("k", pa.int32()),
        ("v", pa.int32()),
    ]
)
table = pa.Table.from_pandas(df, schema)

write_deltalake(
    path,
    table,
    partition_by="p",
)

def write_table(table: DeltaTable, data):
    table.merge(
        data,
        predicate="s.p = t.p and s.k = t.k",
        source_alias="s",
        target_alias="t",
    ).when_matched_update_all().when_not_matched_insert_all().execute()

# by getting both delta tables first, it simulates concurrent actions
table_1 = DeltaTable(path)
table_2 = DeltaTable(path)

# these data touch different partitions
data_1 = pd.DataFrame.from_dict(
    {
        "p": [datetime.date(2020, 1, 1)],
        "k": [3],
        "v": [-3],
    }
)

data_2 = pd.DataFrame.from_dict(
    {
        "p": [datetime.date(2021, 1, 1)],
        "k": [4],
        "v": [-4],
    }
)

write_table(table_1, pa.table(data_1, schema=schema))
write_table(table_2, pa.table(data_2, schema=schema))

More details:
I also tested with partitioning on ints, and I got the same exception with int32, but it worked with int64.

@echai58 can you try this PR please: https://github.com/delta-io/delta-rs/pull/2463

@ion-elgreco Running against that branch works for the date partition!
Under More details I also mentioned that it didn't work for int32 partitions either, is there another simple fix for that?

@ion-elgreco Running against that branch works for the date partition!
Under More details I also mentioned that it didn't work for int32 partitions either, is there another simple fix for that?

What's the error for int32?

@ion-elgreco Running against that branch works for the date partition!
Under More details I also mentioned that it didn't work for int32 partitions either, is there another simple fix for that?

What's the error for int32?

same thing:
CommitFailedError: Failed to commit transaction: Error evaluating predicate: Failed to convert into Arrow schema: Invalid argument error: Invalid comparison operation: Int32 <= Int64

@echai58 I'll look into it later this week. We likely rather want to compare logical types and not physical

Hi @ion-elgreco , have you had a chance to look at this?

@echai58 unfortunately not, currently swamped with other stuff for the time being

I believe the issue is this line: https://github.com/delta-io/delta-rs/blob/66441d10ec54a8afb31f6b46489f15ef3369d8bd/crates/core/src/delta_datafusion/expr.rs#L363
Because there's no quotation marks (vs "'{}'"), the sql expression ends up being e.g. 2024-09-23, which is parsed as an integer subtraction expression, and evaluates to 1991, which is an integer, thus producing the Invalid comparison operation: Date32 <= Int64 error.


:bug: Inject kcp-start-informers logger into correct hook context

Summary
I've observed log lines like the one below for quite a while:
{"ts":1715849616335.2378,"caller":"replication/replication_reconcile.go:200","msg":"Updating object in global cache","component":"kcp","postStartHook":"kcp-start-informers","postStartHook":"kcp-start-controllers","reconciler":"kcp-replication-controller","key":"v1.clusterroles.rbac.authorization.k8s.io::root|system:kcp:universal-workspacetype-use","reconcilerKey":"root|system:kcp:universal-workspacetype-use","kind":"ClusterRole","namespace":"","name":"system:kcp:universal-workspacetype-use","v":2}

Note the double entry "postStartHook":"kcp-start-informers","postStartHook":"kcp-start-controllers".
Turns out that in the kcp-start-informers post start hook the logger gets injected into ctx. That's however not the context of the hook, it's the main context used by the whole (s *Server) Run method! This PR creates a new hookCtx that is explicitly instantiated within the hook and is subsequently passed to all informers and the server bootstrap code.
Note this is relatively low priority and I don't want it to block #3132.
Related issue(s)
Fixes #
Release Notes

NONE

/cc @mjudeikis @xrstf

/kind bug


aws-workspaces: Couldn't find a valid ICU package installed on the system.

Describe the bug
$ workspacesclient
Process terminated. Couldn't find a valid ICU package installed on the system. Set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support.
   at System.Environment.FailFast(System.String)
   at System.Globalization.GlobalizationMode.GetGlobalizationInvariantMode()
   at System.Globalization.GlobalizationMode..cctor()
   at System.TimeZoneInfo.GetDisplayName(TimeZoneDisplayNameType, System.String ByRef)
   at System.TimeZoneInfo..ctor(Byte[], System.String, Boolean)
   at System.TimeZoneInfo.GetTimeZoneFromTzData(Byte[], System.String)
   at System.TimeZoneInfo.GetLocalTimeZoneFromTzFile()
   at System.TimeZoneInfo+CachedData.CreateLocal()
   at System.CurrentSystemTimeZone..ctor()
   at System.TimeZone.get_CurrentTimeZone()
   at GLib.Marshaller..cctor()
   at GLib.Marshaller.StringToPtrGStrdup(System.String)
   at GLib.Global.set_ProgramName(System.String)
   at Gtk.Application.SetPrgname()
   at Gtk.Application.Init()
   at WorkSpacesClient.Gtk.Program.Initialize()
   at WorkSpacesClient.Gtk.Program.Main(System.String[])

Steps To Reproduce
Steps to reproduce the behavior:
run workspacesclient
Expected behavior
I expected workspacesclient to start
Screenshots
N/A
Additional context
N/A
Notify maintainers
@mausch
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.43, NixOS, 22.11 (Raccoon)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.8.1`
 - channels(root): `"nixos-21.11, nixos-unstable"`
 - channels(******): `"nixos-21.11.337605.43538dfb5d6"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Workaround:
NIXPKGS_ALLOW_UNFREE=1 nix-shell -I nixpkgs=https://github.com/NixOS/nixpkgs/archive/21.11.tar.gz -p aws-workspaces --run workspacesclient

@mausch that workaround is working for me.
Any idea when your pull request might get merged? I'm not familiar with the process/workflow.

@boozedog  I don't have commit access, can't say really.
Sometimes it takes just days, sometimes it takes months.

I am bumping aws-workspaces at pr #180854 with the fix from @mausch applied.


[Usage]: how can i get all logits of token?

Your current environment
The output of `python collect_env.py`

How would you like to use vllm
I want to do a discriminant task and directly use the logits score of the last layer, such as comparing the logits score of the two tokens yes or no, but I designed Qwen to only output one character through prompt design. How can I get the logits score of the above two characters.
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

我修改了下model_executor/layers/sampler.py，在Sample the next tokens之后，重置logprobs = logits。不够优雅，但是推理结果可以返回logits了。可以参考，不知道会不会对生成结果有影响。 #10688

能否会整个向量的logits吗？而不是logits里面的最大值。你这种修改返回的还是logits里面的最大值吧

我修改了下model_executor/layers/sampler.py，在Sample the next tokens之后，重置logprobs = logits。不够优雅，但是推理结果可以返回logits了。可以参考，不知道会不会对生成结果有影响。 #10688

你好有验证对结果影响吗


Permanent y-scrollbar

[x] I am on the latest Cerebro.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: Ubuntu 16.04
Cerebro.app version: v0.3.0

Issue
Permanent scroll bar on y. Problem is overflow-y: scroll on html element.
See atached pics.

Same issue on Linux Mint 18.2

Well i found the origin of this problem. is from the minireset.css which is being included somewhere and render inline styles which take precedence over the css files like global.css.
The only workaround for now I found is too add an inline style to the end of index.html file like:
 <style>
      html {
        overflow-y: hidden;
      }
    </style>

@brpaz can you find where it was included? I suppose some plugin added it. Would be better to ask plugin maintainer to remove it instead of hardcoding this style rule

It was plugin related bug.


MNT: Replace master with main, project with astropy-project

This PR attempts to replace all mention of master to main in this repository. This should be reviewed and merged right after the maintainer has renamed the default branch.
This is an automated update made by the batchpr tool :robot: - feel free to close if it doesn't look good! You can report issues to @pllim.
This is part of #179

Oops! Didn't follow-up on this because waiting on astropy-procedures, but doing it now!


Zoom Disable forces into firstperson

fuckin ell

i agree FedUser23

i agree FedUser23

i agree FedUser23

i agree FedUser23

i agree FedUser23


Camel DataSonnet Extension  - resolves Issue #2078 (needs Scala >= 2.13)

@aldettinger I created this PR and I'm going to close the old one.

Hmm, not sure what this error means:
Caused by: java.lang.RuntimeException: Too little or too much org.apache.camel:* entries in camel-quarkus-bom:
[2920](https://github.com/apache/camel-quarkus/runs/6214331067?check_suite_focus=true#step:8:2920)

[2921](https://github.com/apache/camel-quarkus/runs/6214331067?check_suite_focus=true#step:8:2921)
    Extra content at line 89:
[2922](https://github.com/apache/camel-quarkus/runs/6214331067?check_suite_focus=true#step:8:2922)
  ["org.apache.camel:camel-datasonnet"]
[2923](https://github.com/apache/camel-quarkus/runs/6214331067?check_suite_focus=true#step:8:2923)

[2924](https://github.com/apache/camel-quarkus/runs/6214331067?check_suite_focus=true#step:8:2924)

[2925](https://github.com/apache/camel-quarkus/runs/6214331067?check_suite_focus=true#step:8:2925)
Consider adding, removing or excluding them in the BOM

Are there any dependencies I need to exclude?

Hmm, not sure what this error means:
Caused by: java.lang.RuntimeException: Too little or too much org.apache.camel:* entries in camel-quarkus-bom:
[2920](https://github.com/apache/camel-quarkus/runs/6214331067?check_suite_focus=true#step:8:2920)

[2921](https://github.com/apache/camel-quarkus/runs/6214331067?check_suite_focus=true#step:8:2921)
    Extra content at line 89:
[2922](https://github.com/apache/camel-quarkus/runs/6214331067?check_suite_focus=true#step:8:2922)
  ["org.apache.camel:camel-datasonnet"]
[2923](https://github.com/apache/camel-quarkus/runs/6214331067?check_suite_focus=true#step:8:2923)

[2924](https://github.com/apache/camel-quarkus/runs/6214331067?check_suite_focus=true#step:8:2924)

[2925](https://github.com/apache/camel-quarkus/runs/6214331067?check_suite_focus=true#step:8:2925)
Consider adding, removing or excluding them in the BOM

Are there any dependencies I need to exclude?

Looks like you figured out in between?
Once again please, if you could rebase on top of target branch rather than merging it. The resulting history is much easier to read like that. Also, if you could please squash your commits for the same reason.

Really sorry about it, I tried to squash and rebase, but ran into al kinds of conflicts and errors and ended up making a mess again. Would it be possible to squash and merge the PR instead?

Really sorry about it, I tried to squash and rebase, but ran into al kinds of conflicts and errors and ended up making a mess again.
Would it be possible to squash and merge the PR instead?

I doubt it is even possible as long as there are conflicts. Basically it is you who should know best how to solve them. BTW, having less commits in the topic branch may make rebasing a bit easier.
I guess after #3767 is merged, this PR can again target the main branch.


[Feature][Connector-V2-Hive] Add parquet file format support to Hive Sink

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
I found we already supported Parquet File Sink now, For Hive Sink we only need add some code in HiveSinkConfig and get the target schema from hivemetastore. Then deal with the mapping relationship between the field type in SeaTunnelRowType  and the field type in hive table, and modify the field type in SeaTunnelRowType  to the type in hive table.
After completing the above modifications, we have completed the support of hive sink connector for parquet table.
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I am willing to do it.


aider error Unexpected value for AIDER_DEEPSEEK

Issue
aider only working with DEEPSEEK model
I tried to use gemini or sonnet and I got the error for both
aider --model gemini/gemini-1.5-pro-latest
aider --opus
aider --model ollama/llama3:8b
aider: error: Unexpected value for AIDER_DEEPSEEK: 'sk-95...the rest of deepseek API KEY'. Expecting 'true', 'false', 'yes', 'no', 'on', 'off', '1' or '0'
I followed the instructions of the documentation and exported in the bash shell each key api above
https://aider.chat/docs/llms/
Version and model info
No response

Thanks for trying aider and filing this issue.
The AIDER_DEEPSEEK varible is an alias for --deepseek which means "use the deepseek model".
https://aider.chat/docs/config/options.html#--deepseek
Looks like you put your API key in it. That belongs in DEEPSEEK_API_KEY. This doc may be helpful:
https://aider.chat/docs/llms/deepseek.html

I'm closing this issue for now.
If any new related concerns arise, please feel free to comment, and I'll reopen the issue.


Allow Aurora as an alternative to DynamoDB

Some customers will want to stick to traditional relational databases. Having Aurora as an option would allow that.

100% agree. Adding this to to the roadmap.

Closed in PR #191


Use Actions Tagger to provide an up-to-date major tag and keep it up-to-date automatically

Is your feature request related to a problem? Please describe.
People might want to use our Action using a major tag that is automatically updated to include security patches, and similar (e.g: v1 instead of v1.1.0). Using https://github.com/marketplace/actions/actions-tagger would help us to do so automatically, while providing a tag specific for each release.
This way, people can either lock into a release (e.g: v1.1.1) that we won't update (by convention, even though it's technically possible), or use a major version (e.g: v1) which will automatically be updated when a new minor/patch tag is released.
Describe the solution you'd like
Use https://github.com/marketplace/actions/actions-tagger to provide a major tag that's keeping our tags up to date.
Additional context
https://github.com/marketplace/actions/actions-tagger
https://michaelheap.com/semantic-versioning-for-github-actions/

Implemented by @Demmonius


Rework crashes on window resize

Not sure where the issue is, but the code currently crashes for me on swapchain recreate.  It was not doing this with the previous versions of the code.  The following crash occurs using the exact code in the tutorial as of right now.
thread 'main' panicked at 'called Result::unwrap()on anErr value: AccessError { error: SwapchainImageAcquireOnly, command_name: "vkCmdBeginRenderPass", command_param: "attachment 0", command_offset: 0 }', libcore\result.rs:945:5 stack backtrace:    0: std::sys::windows::backtrace::unwind_backtrace              at C:\projects\rust\src\libstd\sys\windows\backtrace\mod.rs:65    1: std::sys_common::backtrace::_print              at C:\projects\rust\src\libstd\sys_common\backtrace.rs:71    2: std::sys_common::backtrace::print              at C:\projects\rust\src\libstd\sys_common\backtrace.rs:59    3: std::panicking::default_hook::{{closure}}              at C:\projects\rust\src\libstd\panicking.rs:211    4: std::panicking::default_hook              at C:\projects\rust\src\libstd\panicking.rs:227    5: std::panicking::rust_panic_with_hook              at C:\projects\rust\src\libstd\panicking.rs:511    6: std::panicking::continue_panic_fmt              at C:\projects\rust\src\libstd\panicking.rs:426    7: std::panicking::rust_begin_panic              at C:\projects\rust\src\libstd\panicking.rs:337    8: core::panicking::panic_fmt              at C:\projects\rust\src\libcore\panicking.rs:92    9: core::result::unwrap_failed<vulkano::command_buffer::traits::CommandBufferExecError>              at C:\projects\rust\src\libcore\macros.rs:26   10: core::result::Result<vulkano::command_buffer::traits::CommandBufferExecFuture<vulkano::sync::future::join::JoinFuture<alloc::boxed::Box<GpuFuture>, vulkano::swapchain::swapchain::SwapchainAcquireFuture<winit::Window>>, alloc::arc::Arc<vulkano::command_buffer::auto::AutoCommandBuffer<vulkano::command_buffer::pool::standard::StandardCommandPoolAlloc>>>, vulkano::command_buffer::traits::CommandBufferExecError>::unwrap<vulkano::command_buffer::traits::CommandBufferExecFuture<vulkano::sync::future::join::JoinFuture<alloc::boxed::Box<GpuFuture>, vulkano::swapchain::swapchain::SwapchainAcquireFuture<winit::Window>>, alloc::arc::Arc<vulkano::command_buffer::auto::AutoCommandBuffer<vulkano::command_buffer::pool::standard::StandardCommandPoolAlloc>>>,vulkano::command_buffer::traits::CommandBufferExecError>              at C:\projects\rust\src\libcore\result.rs:782   11: triangletest::HelloTriangleApplication::draw_frame              at .\src\main.rs:607   12: triangletest::HelloTriangleApplication::main_loop              at .\src\main.rs:573   13: triangletest::main              at .\src\main.rs:649   14: std::rt::lang_start::{{closure}}<()>              at C:\projects\rust\src\libstd\rt.rs:74   15: std::rt::lang_start_internal::{{closure}}              at C:\projects\rust\src\libstd\rt.rs:59   16: std::panicking::try::do_call<closure,i32>              at C:\projects\rust\src\libstd\panicking.rs:310   17: panic_unwind::__rust_maybe_catch_panic              at C:\projects\rust\src\libpanic_unwind\lib.rs:105   18: std::panicking::try              at C:\projects\rust\src\libstd\panicking.rs:289   19: std::panic::catch_unwind              at C:\projects\rust\src\libstd\panic.rs:392   20: std::rt::lang_start_internal              at C:\projects\rust\src\libstd\rt.rs:58   21: std::rt::lang_start<()>              at C:\projects\rust\src\libstd\rt.rs:74   22: main   23: invoke_main              at f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:64   24: __scrt_common_main_seh              at f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:259   25: BaseThreadInitThunk   26: RtlUserThreadStart

Interesting, will try to look into it later today. Haven't tested on Windows yet, actually.

This may be card-specific.  I reran the same built binary on my laptop and it works just fine.   Laptop has Intel GPU, my other computer is nvidia.

Ok, I can reproduce it on macOS/Intel and confirm it worked before the rework - but I don't know what's different yet. And the error seems weird - the comment for it says Trying to use a swapchain image without depending on a corresponding acquire image future., but it's joined just before:
https://github.com/bwasty/vulkan-tutorial-rs/blob/e58aac89377822d480ae0b2a931df7e0366545f7/src/main.rs#L607-L610

Found the problem - see linked commit above.

Very nice find, I completely missed that.
On an unrelated side note found while tinkering with this issue - I may be entirely wrong, but I don't think you need the unsafe device wait line in the swapchain recreation.  Vulkano appears to do all the sync needed with the previous frame cleanup and the passing of the old swapchain during recreation.  I am unfortunately too new in both Rust and Vulkan to know for sure, but it works in my limited testing just fine without any validation errors or crash, and the documentation indicates that you shouldn't generally need to directly call that function.

I went through the Vulkano code and I'm not entirely sure it's safe to omit it, but I removed it now because the docs say that and none of the examples use it either.


[Feature] Evaluate implementation of WakeOnLan

Currently the synology adapter supports commands shutdown and reboot.
A possibility to starte the synology using wake on land would be a good enhancement.

or a general WOL adapter makes sense too? ;-) Right now users do this via javascript adapter I think

The net-tools adapter should support wakeOnLan, but I did not test it.
I suggested this extension here as it might be a very small extension and would logically match the functionality to shutdown / reboot.
A new adapter is not needed in my oppinion as net-tools shoudl support ist and if not extending ping Adapter would be preferable to avoid running to many adapters solely for a small purpose.
But I'm open to any discussion.

A agree. I use net-tools adapter exactly for this purpose and works perfectly with my Synology.

done with PR #231


Add Swaps decoding debug logs

Changes

Adds more transient logging to debug Swap orders decoding issues.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 3 (33.33%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.001%) to 48.461%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/routes/transactions/transactions-view.service.ts
1
3
33.33%

Totals

Change from base Build<PHONE_NUMBER>:
0.001%

Covered Lines:
4214

Relevant Lines:
7011

💛  - Coveralls


Will it support Chinese?

Will it support Chinese training and synthisis?

@jinfagang I have no plan to support Chinese. I think a code is general enough to apply for all languages. FOr melgan, it can be apply for all languages and multi speakers datasets. FOr tacotron and Fastspeech you should write ur own preprocessing.


AArch64 semantics built with amd64 target triple

The BCCompiler CMake build system does not (yet :) ) support setting a target triple for emitting bitcode. Therefore, everything is built as native arch triples (very likely amd64). For AArch64 semantics, we obviously want to emit bitcode with the AArch64 triple of correct endianness.
It should be a matter of modifying the build system to support a ${BC_COMPILER_TRIPLE} flag and setting it in each semantics generation CMakeList.txt

I thought that I got closer to getting this right. I have added in a new ARCH <target_arch> thing into the add_runtime. I don't think it's actually sending the right params through though.

I am thinking of going back on this. Specifically, I envision use cases where the bitcode needs to be compilable for the host arch, but bot necessarily the target arch.

Closing this. Compiling semantics to a specific arch happens to be a bit trickier than intended. Specifically, -target needs to be manually specified, and then include search paths go all wonky. Also, there doesn't happen to be a gcc-multilib package on Scaleway's aarch64 ubuntu 16.04 vms, so that doesn't help things in that department. Finally, I've observed that really we probably want to be compiling all bitcode using the x86_64-unknown-unknown triple. The following illustrates some annoying ABI things:
struct P {
   int *y;
};

int foo(struct P x) {
   return *(x.y);
}

for amd64, this compiles down into:
define i32 @foo(P)(i32* nocapture readonly) local_unnamed_addr #0 {
%2 = load i32, i32* %0, align 4, !tbaa !2
ret i32 %2
}

for aarch64, this compiles down into:
define i32 @foo(i64) local_unnamed_addr #0 {
 %2 = inttoptr i64 %0 to i32*
 %3 = load i32, i32* %2, align 4, !tbaa !1
 ret i32 %3
}


Headless cypress tests fail on create contentType step

now tests are working as expected, I don't know what was the problem. now it is fixed.


Dispatching Shorthand in Routes Issue

Laravel Version: 8.40.0
PHP Version: 7.4.3
Database Driver & Version: mysql

Description: It seems you cannot enter shorthand functions to callback to dispatch function.
The function inside the dispatch then goes into a forever loop. It then has to be hard reset to actually be stopped.
Steps To Reproduce:
Route::get('test', fn () => dispatch(fn () => App\Model::find(1)));

dispatch returns an object which can't be returned from a route.

Could you explain a bit more because it seems to be working in long hand function
Route::get('test', function () {
    dispatch(function () {
        App\Model::find(1);
     });
});

shorthand function automatically return the result, while longhand you will need to explicitly write return dispatch()


no drop at test, upsample output to arbitrary size

Modified the model graph so that it only has dropout probability 0.5 at training time, but 0.0 at test time.
Added 2 command-line arguments "upsample_w" and "upsample_h" to upsample model output to arbitrary size

Actually the dropout is necessary for both training and testing as a kind of input noise to the network. They mentioned this in the original paper.


Support AWS VPC ACLs

Description
Add support for AWS VPC ACLs
Example
ACLs are an important piece of security in AWS. Would be nice to see support for this type of resource in driftctl

Any progress on this issue?

We'll re-prioritize this one based on your request!

Assigned @sjourdan for testing, this one need to be deeply tortured.


Support for Azure DevTest Lab

I would like to add the arm templates to azure Dev/Test Lab to have a better control over thins like start/stop and to have all these vms in one place (we use dev/test to organize all other vms in azure that fall in that category).
Unfortunatly the structure of this repo does not allow this right now.
According to the docs: https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/lab-services/devtest-lab-create-environment-from-arm.md the template files must be seperated in folders and must be named azuredeploy.json like in the default repo https://github.com/Azure/azure-devtestlab/tree/master/Environments
@freddydk  are you willing to support this scenario?

I will have a look at that and get back

I played around with this today and have created one template, which works.
If you setup a private repo for templates like this:

Then you should be able to deploy.
You can also create your own github repo and grab the files from the Environments/getbc folder, and change parameters, default them etc. and then spin up your machines with that.

Perfect thanks a lot i will give it a try!


copy interface pointers (arbitrarily deep)

Fixes #16
This properly converts a reflected value to *interface{} (with any
number of * nesting) so that it is settable.
When a field is interface{} (no pointer), any value is settable to it.
But when a field is *interface{} (one or more pointers), then pointer
values are not assignable to it, it must exactly match *interface{}.
The code added in this PR checks for this scenario and converts.

Tests pass, would still love eyeballs @jbardin if you get a chance.

Thanks, this LGTM! Guess I missed a nested pointer-interface combination when laying this out.


A couple missing packages needed for Resolve 18.1

A quick note that for the just-released Resolve 18.1, the following packages are apparently now dependencies and required to be added to the Dockerfile installed packages:
apr apr-util libXinerama libxkbcommon libxkbcommon-x11 libXrandr xcb-util-image xcb-util-keysyms xcb-util-renderutil xcb-util-wm
I added these manually and it seems to be working okay.  These specific packages were reported as required by the 18.1 installer:
Error: Missing or outdated system packages detected.

Please install the following missing packages:
    apr apr-util libXinerama libxkbcommon libxkbcommon-x11
    libXrandr xcb-util-image xcb-util-keysyms
    xcb-util-renderutil xcb-util-wm

So I added them, and the built completed without issue. I did not test to see whether they were ALL actually needed, I just blindly added them.
When running for the first time, I got a weird frozen splash screen, and had to go into the container where I saw these two processes:
QtWebEngineProc
DaVinci_Resolve

When I killed those two, suddenly DR started running, and I got this:

The libraries needed to be updated:

I decided to do a backup of the database first, just in case.  You can do this by clicking on the "i" with the circle around it next to the database name.

To fix the black hanging screen, you need to ensure that you have openssl 1.0 libraries installed.

What's odd is it was installed and subsequent runs have no issue.  Might have been something weird on my side....

The black screen hang is caused by the on-boarding app not being able to find openssl 1.0 libraries. The on-boarding app only runs the first time after an installation. If you kill the QtWebEngine process or restart the container, the next time the container runs, the on-boarding app will not execute and everything will be fine.
tl;dr - The run-time environment needs to have openssl 1.0 libraries installed to prevent a black screen hang when Resolve runs the first time after installation.

Yes, you are so right!  Thanks!  Running
 /opt/resolve/Onboarding $ ./DaVinci_Resolve_Welcome

does indeed seem to run into ssl errors:
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push

etc
The issue tho is that older versions of 1.0.2 up to 1.0.2w have at least one CVE and "All older versions (including 1.1.0, 1.0.2, 1.0.0 and 0.9.8) are now out of support and should not be used."
Wonder what the best course of action is.  Could bring in an old/outdated 1.0.2 but if there's a better way to not rely on EOL libraries (especially ones related to security) that would be preferred.  Any thoughts?

It's only the on-boarding app that uses the openssl 1.0 libraries and, to the best of my knowledge, the on-boarding app does not actually make any connections to the network. The openssl 1.0 requirement needs to be satisfied only to start QtWebEngine, even if the SSL features are not being used for anything.
The main Resolve binary uses a newer version of openssl and therefore does not exhibit the same hanging issue and, just as importantly, is not affected by the CVEs of concern.
From a security point of view, it should be safe to go ahead and install the openssl 1.0 compatibility libraries as their usage is very limited.

The "official"/old Centos 7 packages appear to be incompatible with a zillion dependencies.   I don't know the centos world very well-- is pkgs.org a legit source to get rpms-- the centos-9 stream derivative distros don't seem to have the package:

Well FWIW the almalinux version from 8 works in 9, at last enough to get to that main screen, though it then dies like this:
$ ./DaVinci_Resolve_Welcome
Failed to connect to Resolve server.

But I don't care too much.  At least it gives me the onboard feature screen, though it's teensy-tiny on my screen.

K for now, commit f546536 takes care of the dependencies which the Resolve installer asked for.  Not sure which compat-openssl10 to use with certainty in alma/rocky/stream 9... but thoughts are appreciated!
(also checked in some env variables to support Resolve scripting...)

Since this should be addressed in PR #34, I'm going to close this.  So to get compat-openssl10 for the onboarding app, if you want to use it, just be sure to use the Rocky Linux 8.6 (default) image as your base.  This is what's officially supported by BMD.
Feel free to comment on the PR thread if there are any issues.


Try to add support for device's default TTS and decouple the languages supported by TTS engine and Whisper

Add support for Huawei's TTS and decouple the languages supported by TTS engine and Whisper
Hello,
Thank you for maintaining this project. The project has been very useful for me. I installed the latest version to a Huawei device with HarmonyOS 4.2.0 but it could not detect Huawei's TTS engine as what happened on Samsung previously. Besides, I noticed that the list of languages only included the languages supported by both TTS and Whisper when it detected the TTS engine. However, users including me may expect to use only the Whisper's translation even the Google, Samsung or Huawei's TTS are not available because the supported languages in TTS sometimes are limited.
To address these issues, I have made the following modifications:

Modified TTS.java to load device's default TTS engine and check if the voices can be used;
Decoupled the lists from Whisper and TTS by modifying several lines to save the TTS's language list in TTS.java, some lines in Global.java to get the "compatibleLanguages" supported by whisper;
Modified if conditions in ConversationService.java and WalkieTalkieService.java to avoid speaking from incompatible TTS engines such as trying to speaking Japanese using Chinese TTS...
Modified getDisplayName() in CustomLocale.java to display if the language is available in TTS.

The modifications were tested on a Huawei device with HarmonyOS 4.2.0 (com.huawei.hiai) and and a Samsung device with Android 14 (com.samsung.SMT). The built app looks good for me on both devices. However I did not have a chance to test on other platforms. The .apk prerelease of this version is avaliable and can also be built from the branch.
The updated language list displayed on Samsung with Samsung's TTS is as follows.

Hi again JingziC,
In these days I will review the pull request (don't make any changes in the meantime, If you have other ideas, leave a comment).
I'll tell you in advance that I won't be very fast in the review because I don't have much free time and I'm not used to receiving and reviewing pull requests, so I still need more practice to become faster.
Thank you again!

Hi niedev, thanks for the prompt reply.
I understand and will not change this request and corresponding branch. Please take you time.


Added php8 for ci

https://github.com/openzipkin/zipkin-php/issues/202

https://github.com/jcchavezs/zipkin-php-opentracing/pull/52


Coffin fails with Django >=1.8, Breaks CI Build

Coffin fails with Django >=1.8
Breaks CI Build.
Please see: https://travis-ci.org/amitu/importd/jobs/50173170
Please see: https://travis-ci.org/amitu/importd/jobs/50173170#L267

I complains:
 File "/home/travis/build/amitu/importd/.tox/py27-django18/lib/python2.7/site-packages/coffin/template/__init__.py", line 1, in <module>
    from django.template import (add_to_builtins
ImportError: cannot import name add_to_builtins

:disappointed:

Damn. It also breaks my djangothis project which relies on add_to_builtins.
add_to_builtins is no django.template.base now. We have to wait for coffin to change their import path, probably an ImportError fallback.

Files bug with django-jinja and created pull request for coffin.
Will have to wait for those guys. I tried monkey patching things, but it did not fix all the issues.

Nopes. It is our fault. Starting 1.8 django has deprecated a bunch of settings, TEMPLATE_*, and replaced them all with TEMPLATES dict.
Currently we are detecting if django_jinja/coffin is installed, in which case we auto configure TEMPALTE_* settings.
We either remove support for them, or make them use the new way.
Problem is that now since there is only one big dict, its not safe for us to overwrite/change it. It contains template locations, loaders, context processors etc. And one or another will be modified by most developers, meaning some dict will always be there.
I am biased towards removing coffin/django_jinja support, and letting developers configure them. As we are not doing much value add, and developers have to do rather little to support it.
What do you say?

Can be Coffin removed without losing Jinja ?
If removing is the safest way, we may...

Yep. Since django_jinja has better integration with django, I think we should prefer that one, and not have two different implementation for jinja.
How to remove it, let me see.

We should keep it clean, simple, readable...,
if it have too many lines of weird hacks to make 1 feature works on the risk of the whole thing not working,
its not worth it, some stuff are more friendly to integrate than others, we should point that way.

I have the same error when i try migrate my apps with --fake-initial

We will be removing coffin as part of #72, so closing this.


Allow multiple drupal

@Islandora/8-x-committers this should have no effect on current builds but will enable multiple Drupal version testing ala https://github.com/Islandora/islandora/pull/821

@Islandora/8-x-committers this should have no effect on current builds but will enable multiple Drupal version testing ala https://github.com/Islandora/islandora/pull/821

No, https://github.com/Islandora/islandora/pull/821 passed because islandora_ci can only run 8.9.11. It just ran it 6 times instead of 3.

No, https://github.com/Islandora/islandora/pull/821 passed because islandora_ci can only run 8.9.11. It just ran it 6 times instead of 3.

Before I opened the draft pr 8 did run a test. I can show you how to run your own tomorrow if you'd like.

Before I opened the draft pr 8 did run a test. I can show you how to run your own tomorrow if you'd like.

Ah ok, talk to you tomorrow then 👍

Ah ok, talk to you tomorrow then 👍

With @whikloj 's help, i was able to test the islandora_ci change on the islandora module here: https://travis-ci.com/github/asulibraries/islandora/builds/212494945
which created 12 builds
php 7.3 / drupal 8 / kernel
php 7.3 / drupal 8 / functional
php 7.3 / drupal 8 / functional-javascript
php 7.3 / drupal 9 / kernel
php 7.3 / drupal 9 / functional
php 7.3 / drupal 9 / functional-javascript
php 7.4 / drupal 8 / kernel
php 7.4 / drupal 8 / functional
php 7.4 / drupal 8 / functional-javascript
php 7.4 / drupal 9 / kernel
php 7.4 / drupal 9 / functional
php 7.4 / drupal 9 / functional-javascript
verified that the correct PHP version and drupal version was installed so i think this is good to go

With @whikloj 's help, i was able to test the islandora_ci change on the islandora module here: https://travis-ci.com/github/asulibraries/islandora/builds/212494945
which created 12 builds
php 7.3 / drupal 8 / kernel
php 7.3 / drupal 8 / functional
php 7.3 / drupal 8 / functional-javascript
php 7.3 / drupal 9 / kernel
php 7.3 / drupal 9 / functional
php 7.3 / drupal 9 / functional-javascript
php 7.4 / drupal 8 / kernel
php 7.4 / drupal 8 / functional
php 7.4 / drupal 8 / functional-javascript
php 7.4 / drupal 9 / kernel
php 7.4 / drupal 9 / functional
php 7.4 / drupal 9 / functional-javascript
verified that the correct PHP version and drupal version was installed so i think this is good to go


review/update documentation

refresh documentation

curate: verify organization of all public API
verify abstracts on all methods
publish to GH pages

#58 is partial work

resolved with #78


BUG!! Not giving Audio Output on Physical Device after Generating Release Apk

This is not giving audio output on Real physical device but works fine in Emulator.
Main File
....
TrackPlayer.setupPlayer().then(async () => {

          // Adds a track to the queue
          await TrackPlayer.add({
              id: '11',

              // url: 'http://example.com/avaritia.mp3', // Load media from the network
              url: require('./../../AppAssets/songstest/AR.mp3'), // Load media from the app bundle

              title: 'Humpi',
              artist: 'AR',
              album: 'Carnival of Carvings',
              genre: 'Melody',
              date: '2018-01-20T07:00:00+00:00', // RFC 3339

              artwork: require('./../../AppAssets/images/xyz.jpg'), // Load artwork from the app bundle
          });

....
onPressPlay = () => {
TrackPlayer.play();
}

....
index.js
AppRegistry.registerComponent('MyProject', () => AppNavigator);
AppRegistry.registerHeadlessTask('TrackPlayer', () => require('./player-handler.js'));

For your information, Its happening with Release Apk.

Does URLs work?

Yes, URL works Seamlessly . The problem with bundle files and that too after making release apk.
Not giving audio in both emulator and physical device

Can you log the result of the require? Something like console.log(require('./../../AppAssets/songstest/AR.mp3'));

And even better:
import resolveAssetSource from 'react-native/Libraries/Image/resolveAssetSource';

console.log(resolveAssetSource(require('./../../AppAssets/songstest/AR.mp3')));

@Guichaguri It is not working and giving expected output.

What is it outputting?

@Guichaguri I'm trying to replicate your demo project .I will update you the progress with relevant to this

Data ={"key":"a","id":"11","url":3,"mail":"dv1@gmail.com","title":"My Album Title","artist":"AR","album":"Person album","genre":"Melody","date":"2018-01-20T07:00:00+00:00","artwork":4},index = 0
C:\MyProject\src\AppScreens\MyPlaySection\TrackPlayDummy.js:141 This File Refers To ::{"__packager_asset":true,"uri":"http://<IP_ADDRESS>:8081/assets/src/AppAssets/songstest/ar.mp3?platform=android&hash=c115f2e73bc5417ff393fda331347d63","scale":1}

It will be fine if you could give sample code without redux implementation.

And what does it outputs in a release apk?

I have added project in a public repository for you.
I feel you can catch with a glimpse over it.
<EMAIL_ADDRESS>

Debug : Mode

Release Mode

Insights please

It would be helpful if you cud give a push to the solution

same issue here, with android but with an streaming url, app works fine on debug mode, but on release after init the TrackSetup, it stop working

I'll check it out when I have time

We are waiting for it!..

after my testing the issue appear on release apk even it is returning the same resources id and that's strange,
I tried to use different source files such as import or require or even i put the files in raw folder and i call using uri such as
{uri:'file:///android_asset/test.mp3'}
and all didn't work on release version

@Guichaguri How the uri gets changed !? made the apk with Same code !

@deva11 he is closing my issue post as it is same of current one, i said that track url is different and i mean that on release the files location is changed but the track player is returning same resource ID.

Okay okay! Fine @MohammadElKhatib .

Looks like the issue happens because react-native changed the way resources are packaged. In the past everything was drawable. But now resources are packaged as raw.
ResourceDrawableIdHelper helper = ResourceDrawableIdHelper.getInstance();
int id = helper.getResourceDrawableId(context, uri);

This code does not work in release.

Is this still an issue?

@dcvz were there any commits changing the behaviour? Non-image resources are packaged as raw. Although if you want to bundle a lot of audio in APK itself, you might have more issues with the fact that APK can only be 100 mb large, and you need to use expansion files and generate paths for content provider for example.

is this still an issue?

Yes. Because resources are packaged not as drawables in newest RN. https://github.com/react-native-kit/react-native-track-player/blob/e217c74b11772dc32d0d08236ec3feaeb606748a/android/src/main/java/com/guichaguri/trackplayer/service/Utils.java#L65 this code is wrong. It should try to search resource in raw first.

Hi, when problem will be solved? There is a way to work around the problem? It is works in dev version of package? Because on 1.0.0 I have this problem (With React Native 0.57.5)

Sorry for taking too long to look into this.
In release mode, RN used to copy all resources to the drawable directory, and this module used to look up the files there.
It became a problem when RN started to copy non-image files into the raw directory.

same issue here, with android but with an streaming url, app works fine on debug mode, but on release after init the TrackSetup, app crashes

Wondering ..Were to able to fix it?

Hi,
I have the same problem on Android with a release apk loading a url live stream, is there a way to fix it ?
Thanks.

Problem solve, due to http instead of https in the streaming url