[BUG] Relative imports '.' and '..' do not work

Bug Report Quick Checklist

[x] I am on the latest version of Snowpack & all plugins.
[x] I use package manager yarn/npm (Fill in: npm, yarn, pnpm, etc).
[x] I run Snowpack on OS mac (Fill in: Windows, Mac, Linux, etc).
[x] I run Snowpack on Node.js v12+

Describe the bug
Extracted from https://github.com/snowpackjs/snowpack/pull/2707#issuecomment-790926970, so it doesn't get lost.
I've found an issue with relative paths imports - import {BLAH} from '.' and import {BLAH} from '..' do not work as expected, however import {BLAH} from './' and import {BLAH} from '../'do work correctly.
It seems this was a problem in 3.0.x too, however 3.0.x compiled and served the file with incorrect content and the error occured at runtime. However in the 3.1.0-pre.11 the file with problematic code now returns a 500 error, with an unhelpful error message.
Reproduction is available here.
Given the input (found in this file)
import {value1} from '.';
import {value2} from '..';

import {value3} from './';
import {value4} from '../';

In 3.0.x it compiles to the incorrect output:
import {value1} from '.';
import {value2} from '..';

import {value3} from './index.js';
import {value4} from '../index.js';

In 3.1.0-pre.11 it errors during compile:
Error: Package(s) failed to build: Cannot find module '..' from '/Users/ben/src/github.com/BPScott/snowpack-test/bare-relative-import/package.json'

To Reproduce
Reproduction is available here.
Clone that repo, move into the bare-relative-import subfolder and run npm install and npm start
Expected behavior
I would expect the code:
import {value1} from '.';
import {value2} from '..';

import {value3} from './';
import {value4} from '../';

to compile to:
import {value1} from './index.js';
import {value2} from '../index.js';

import {value3} from './index.js';
import {value4} from '../index.js';

Thanks @BPScott, PR opened: https://github.com/snowpackjs/snowpack/pull/2877


next release date?

There's a patch in the current code - for opening new DMs to people - that I really need, but last release was a while ago so yeoman's pulling in an old version. Any idea when the next release is likely to be?
Thanks,

+1

:+1: Just got bitten by the bug mentioned, would be nice to have the version with the change on npm

+1

I'd love to see this released too.

I would really appreciate any information on this. Are we waiting for some other PRs to be merged? Any approximate date?

Looks like there's a new release but hasn't been published to npm yet!

Sorry for the oversight -- the latest version has been published.


Task 11

This Process indicates as per user input fruit message will be pop up.

{
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
}
]
}

{
"Main.xaml":  [
{
"Activity Log Message has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
}
],
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
}
]
}

@RajashekharPuligilla
Task -11
Code verified. Need to complete in flowchart concept


fix: Example provided in README.md

The example provided in README.md does not run, this PR fixes it.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

PS: also updated to the latest so that we may merge more easily.

Jenkins Linux amd64 Build #7258 [push] Example provided in READ... started at 12:25

Jenkins Linux ppc64le Build #6324 [push] Example provided in READ... started at 13:26

Jenkins Linux s390x Build #7274 [push] Example provided in READ... started at 13:25

Jenkins Linux amd64 Build #7258 [push] Example provided in READ... passed after 1 hr 6 min

Jenkins Linux s390x Build #7274 [push] Example provided in READ... aborted after 1 hr 48 min

Jenkins Linux ppc64le Build #6324 [push] Example provided in READ... aborted after 1 hr 48 min


ASTER docker container

Description of the bug
Change the container as it does not work
Command used and terminal output
No response
Relevant files
No response
System information
No response

updated.


profile handler step 2 -- enhance the command run to a service object

It enhanced the args combine functions
And it enhanced the resource creations to services
It resolved some issues of the not updated manifests file
The un-used functions of createMyTFxxx will be removed in next PR

/lgtm

/lgtm

/approve


[Feature] Support authenticating to registries with client certificates

Current Behavior
Only username/password-based authentication is supported.
Expected Behavior
Some registries may be configured to require mTLS client certificates to authenticate instead.  It would be nice to have this support.
Example Solution

Version
VCSTag:     v0.4.8
VCSRef:     847254c7ac7d6f027dcdfb196a9aa4c11eb61ed9
VCSCommit:  847254c7ac7d6f027dcdfb196a9aa4c11eb61ed9
VCSState:   clean
VCSDate:    2023-04-14T23:41:20Z
Platform:   linux/amd64
GoVer:      go1.20.3
GoCompiler: gc

Environment

Running as binary or container: binary
Host platform: Linux x86
Registry description: private

This is straight-forward to add. If this is for regctl, does a flag similar to regctl registry set --cacert (but for client cert/keys) work?

Great!  Yep for regctl, and I think flags like that would work fine.

This should now be supported in the main branch. Let me know if you encounter any issues. Thanks for the suggestion!

Looks like it's working perfectly.  Thanks for the quick fix!


add disk_cleanup action

Adding the jlumbroso/free-disk-space tool directly as an action as it is not from a verified creator. Most organisations like mine have a check to only use actions from verified creators.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 68.39%. Comparing base (f2d03ae) to head (c19d9a2).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

:exclamation:  There is a different number of reports uploaded between BASE (f2d03ae) and HEAD (c19d9a2). Click for more details.
HEAD has 7 uploads less than BASE

Flag
BASE (f2d03ae)
HEAD (c19d9a2)

8
1

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #348      +/-   ##
==========================================
- Coverage   77.95%   68.39%   -9.57%
==========================================
  Files          35       35
  Lines        2531     2531
==========================================
- Hits         1973     1731     -242
- Misses        558      800     +242

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

Makes sense. FWIW, the restrictions for verification do not seem to high. https://docs.github.com/en/apps/github-marketplace/github-marketplace-overview/applying-for-publisher-verification-for-your-organization

You're right it does look pretty straightforward, we can consider moving back to jlumbroso once he is a verified creator. I'll see if I can reach out to him


Freeze Molprobity version in the deployment script

Molprobity uses a rolling release model which makes it very hard to have a stable deployment-from-scratch script.
The culprit:

The recommended Molprobity installation way right now is with a bootstrap script.

The script pulls data from master branches of multiple repositories:

https://github.com/rlabduke/MolProbity/blob/2ce1fdb13eb4d874cd1053da9032924c3305269f/install_via_bootstrap.sh#L32-L39

The script also calls another bootstrap script:

https://github.com/rlabduke/MolProbity/blob/2ce1fdb13eb4d874cd1053da9032924c3305269f/install_via_bootstrap.sh#L44-L46
which internally pulls more git repositories
https://github.com/cctbx/cctbx_project/blob/7b32060a735f8f1d210fb34965f89e828150f29e/libtbx/auto_build/bootstrap.py#L1021-L1038
Thus it's not possible to freeze the Molprobity version except as a compiled singularity image.
Technically we can try reworking both installation scripts, but hopefully Molprobity team will adopt a different release scheme.

We decided to "freeze" the MolProbity version at the level of the singularity container.


[Discovery] Handle multiple lifecycle events on single event bus topic

This is a bit of a discovery ticket.
Acceptance Criteria:

[ ] ADR for handling of multiple lifecycle events (created, updated, deleted) on a single topic.

Notes:

Confluent recommends keeping multiple related event types on the same topic for ordering purposes:

See https://www.confluent.io/blog/put-several-event-types-kafka-topic/
And more recent article: https://www.confluent.io/blog/multiple-event-types-in-the-same-kafka-topic/

Questions:

Will we follow Confluent’s recommendation to use a single topic for multiple related events?

How will we get a partition key from our current event definition?
How will we handle the schema used for the topic to allow for the multiple event types?

Note: the second article (https://www.confluent.io/blog/multiple-event-types-in-the-same-kafka-topic/) offers two options with different pros/cons.
[Robert] I'm thinking the Union solution is probably more complicated than what we need. However, I'd like to understand how schema evolution works with the other solution.

Will this solution work for other event bus technologies other than Kafka?
What are good naming conventions for the event_type, event definition (signal), data class, etc. for the proposed solution?

Moved from original private ticket: https://2u-internal.atlassian.net/browse/ARCHBOM-2008

Move some of these notes into the doc ticket, and closing this.

Note: This was closed without completing, and will remain closed (for now). However, I just updated the how-to to refer to this closed ticket: https://openedx.atlassian.net/wiki/spaces/AC/pages/3508699151/How+to+start+using+the+Event+Bus#Event-design.
Other considerations for ordering will include Redis Streams capabilities, which don't have the same partiton ordering guarantees as Kafka.
Here are docs that I moved from the how-to back to this ticket here:

Confluent, a hosted solution for Kafka, recommends keeping multiple related event types on the same topic for ordering purposes. If going for the approach of multiple lifecycle events in one topic, you will want to consider the partition key carefully. See Publishing a signal for more.
See  https://www.confluent.io/blog/put-several-event-types-kafka-topic/
And more recent article: https://www.confluent.io/blog/multiple-event-types-in-the-same-kafka-topic/

I'm re-opening this ticket because I want to make progress on it, and it is difficult to find as a closed ticket. :)

Also, we would need to update docs on naming conventions for topics if someone plans to add multiple events, since the topic name would no longer match 1-to-1. This should possibly planned for even if only the first of multiple events are being published?

It may be that some lifecycle events all match the same schema(???), and in this case, they all might be able to be written to the same topic with no change (i.e. just allowing the single schema).

If you look at https://github.com/openedx/openedx-events/blob/143ffd745e1cf17c108156829fb26cd1255096c3/openedx_events/learning/signals.py#L86, you can see that the CERTIFICATE_CREATED, _CHANGED, and _REVOKED all have the same schema. COURSE_ENROLLMENT_CREATED and _CHANGED also take the same data structure.

@rgraber: You are welcome to test that sharing the same data structure is enough to make this work when that is the case. At the same time, I would like to understanding how this works for signals that don't share the same data structure. Note that the first events of this type will likely be these XBLOCK_ events, and one has different data.

Docs include two options: 1) changing the naming strategy to any event type, but one schema per event type or 2) using an Avro union of the specific event types.
@rgraber learned that option 2 is blocked on a potential Confluent bug, and can add more context.
Option 1 we learned we can do at the cluster level, but possibly not on a per-topic basis, because the per-topic settings may not be exposed by Confluent Cloud. See topic settings for Confluent Cloud.

TODO: Do a timeboxed test of setting this setting via terraform, or ticket this separately.
Based on the results of the test, either set by-topic or set for cluster, and potentially document the consequences.

Closing this. Updating documentation will be added as part of https://github.com/openedx/event-bus-kafka/issues/164


Resolve maas pip_lock_down and maas_common issues

The rpc_maas role needs to depend on the pip_lock_down role, otherwise
the openstack clients and other pip packages are not installed from the
repo server.
This will prevent us from having to run "pip-lockdown" against hosts
unnecessarily.
Additionally, in the next version of python-keystoneclient
apiclient.exceptions will be removed, as per:
https://review.openstack.org/#/c/258302/ - we can fix this in advance by
following the recommendation and use keystoneclient.exceptions. This
won't affect current releases but will future proof for upgrades to the
Newton cycle (and above).
Connects https://github.com/rcbops/rpc-openstack/issues/1404

recheck_all

failed to clone rsyslog_server - but manually that seems to work ok - so rechecking.

recheck_swift

testing this right now.

This change looks good to me, but two minor questions:

Should we make pip_lock_down a dependency in all rpcd roles?  This fixes maas but rpc_support may be susceptible to similar breakage if a deployer does not run pip_lockdown.yml during the upgrade process.
The linked bug mentions keystoneclient.apiclient.exceptions, we're using keystoneclient.openstack.common.apiclient.exceptions.  They're both deprecated so I think the change is right, I'm just wondering if we're linking to the wrong bug?

--Matt

Yepp @mattt416  see https://github.com/rcbops/rpc-openstack/pull/1409

@matt416 good catch on the PR - there were 2, I found the appropriate one.

Do you think horizon_extensions and rpc-support should benefit from this approach too?
It's probably better to lock them down too, right?

Well I just saw your comment on the other PR.
My analysis is the same, so we're good to go I guess.
The test-upgrade.sh still fails for me, but not linked to this PR.

Your content preview is now ready. :bow:

:eyes: Preview

Still waiting on gate, but this looks 👍 to me.

👎  We need to make sure that the pip_lock_down role is dependent on other roles too like rpc_support or the maas extensions

@BjoernT if you look at the PR it does address rpc_support, as well as horizon_extensions and rpc_maas. The kibana and elasticsearch roles are already dependent on it - all other roles don't actually install any pip packages and so don't need pip_lock_down.

@andymcc  OOps my bad we are 👍  here then

👍 looks good to me pending the gate

👍  pending checks

recheck_swift


Update the themes containers according to the design

should be completed before completion of #80
https://www.figma.com/proto/oK12zZACqvlACoqkZIrtxV/Gallery-Website?page-id=75%3A2347&node-id=2567-14290&node-type=frame&viewport=122%2C-5192%2C0.19&t=H9xeJRpv3K9H6lsa-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=2567%3A12705

Are you working on this issue?

I've self assigned, but please feel free to take this one if you want, dm me on discord if you want to work on this one.


Nethereum.JsonRpc.Client.RpcResponseException: 'data types must start with 0x'

I have downloaded your mobile app code, built it to point at my own instance of Infura's mainnet https://mainnet.infura.io/v3/<my infura project id>, but when I click the "history" button in the app, the app crashes and throws a Nethereum.JsonRpc.Client.RpcResponseException in the title above
Any ideas what might be causing this? :) thanks

Any updates on this?

I have the same problem and i don't know why. Any Help?

I have the same problem and i don't know why. Any Help?


Allow disabling service

We scrape the pod port directly. Plus scraping the service doesn't really work with daemonset since the service will point to only one of the daemonset pods, and when more than one node exists with GPUs, this ends up not scraping more than one node.

How would Helm like an empty template? For example, helm template needs --output-dir argument to ignore empty YAML files.

Helm does just fine, I did this and get correctly rendered deployment:
$ helm template dcgm-exporter deployment --set service.enable=false

This rendered my local changes without the Service.  This pattern of not deploying a template is already being used in this Helm chart:
https://github.com/NVIDIA/dcgm-exporter/blob/50ccb1a609153bed097ccfb849797a5ab8f7b23b/deployment/templates/service-monitor.yaml#L1
My local Helm deployment of this exporter sets that serviceMonitor to not be included and it works great.  Helm doesn't care if one file is empty, since it renders all the files together so one empty file is going to be like that file doesn't exist.

I moved the boolean for enable/disable service to same place (above comments) like the serviceMonitor file to make things consistent.

@treydock, Could you sign-off you commit, please?


Fix hit detection in a multi-cam scenario with billboarded meshes.

Related forum issue: https://forum.babylonjs.com/t/mutliple-cameras-affect-billboard-meshes/37496
Related PG: https://www.babylonjs-playground.com/#1WROZH%23266
Superseed https://github.com/BabylonJS/Babylon.js/pull/13471

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13479/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13479/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13479/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13479/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13479/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13479/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13479/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13479/merge#BCU1XR#0


enable CD for digicert-software-trust-code-sign-plugin

Testing done

### Submitter checklist
- [x] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!
- [x] Ensure that the pull request title represents the desired changelog entry
- [x] Please describe what you did
- [x] Link to relevant issues in GitHub or Jira
- [x] Link to relevant pull requests, esp. upstream and downstream changes
- [x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

You don't need to create new PRs constantly. I'd recommend working with branches instead of pushing to the default branch.


Bugfix to cast available at attribute to string

As requested i left out the cast for all attributes,
i wasn't sure if the input would be safe, therefore i added it.
If you say it's safe to only cast the available_at attribute.
This should be enough, including fixes for your unit tests.
Fixes issue #19

Thanks


Create Mock AMOS.Library

already underway,

an AMOS library needs creating that has blank graphics routines, a template framework and a mock library for running unit tests - and for a template to create new compatible libraries for the different architectures.
all procedure code needs replacing so that an AMOS program can be compiled with linked with this library so that graphical output is converted to text script and output to the console device for logging.
this template AMOS.Library can then be used for multiple purposes including unit and functional testing
as a template the code can be used to create a replacement for all the different native graphics architecures and the AMOS source code program remains compatible but executes on the new hardware.

Is this the best solution?  Could we possibly make the AMOS.library smarter, like having it load the correct code from a smaller library or hunk?  Or maybe split everything into smaller libraries like AMOSCore.library, AMOSGfx.library, AMOSNetwork.libary, etc.?
I'm just trying to think of alternatives to having multiple, monolithic AMOS libraries floating around.  I can see things getting messy quickly.

hmmm, no it's not the best solution, but it does have some interesting possibilities, and also in the creation of it some interesting learning - there are also other reasons for me doing this, it shouldn't take long and won't interfere - I mentioned not being able to add 'illegal' instructions into amos code from inside the compiler and this is an idea that covers that too, plus you'll be able to render graphics over a network and even record replay stuff but those ideas are for different project that this could spawn.

when using the template to create new amos.libraries only specific graphics routines would be marked for creation in the new platform, a demo of a screen open with output can then be created, i'll exeperiment with levels of functionality.

monolithic AMOS libraries

that is one way of looking at it, but the 'OS' in AMOS is there for a reason and the library iterfaces to the larger structure, files names can be renamed to protect the innocent, and I'm planning an extension installer that puts the name in the settings automatically, and copies the binary, the same can be done for libraries so folks know where they are at in the AMOS eco structure.

AMOSPro.Lib is loaded as extension 'A' and where the main language is, different thing to the AMOS.library - another on my list is a C library of the routines that is BLinked to a variation of AMOS.library full of XDEF's in the same way the +3d.s is created, so executing C functions from AMOS programs using the proven method they used to accomplish it.

have got a first version, it hasn't had anything removed - i've managed to log screen open and screen close https://github.com/AmosFactory/MockAmosLibrary/commit/baeabfa79004c850e79b584f94abb30dc3f4fd03

the interpreter loads fine with this, but the compiled program crashes when it loads it - the DosBase isn't in the same stack position when it's compiled, the +Header.s shows something, so I worked out grabbing the DosBase reference at this point makes it work...
; MOCK
; ~~~~

	lea		out_startup(pc),a1
	move.l	d5,DosBase(a5)
	bsr		outmsg

; ~~~~

it makes the compiled program version load up the library, but amsspro won't load as d5 is something different for it - nearly there...

I sorted out the above with a new +Header.s that initializes the dos.library before the amos.library as previously there was no reference to dos in the amos.library.
and, I've made some progress: https://github.com/AmosFactory/MockAmosLibrary/commit/a2ac2b367db1b2d911b715a98ed4479cb8ca224c +w.s is very readable now using includes...
during this exercise many good things came up, the original was very well organized (as I suggested) so I was able to disect the entire +w.s into individual "classes" - I'll finish the Bob/Sprite split and tag a release as a fully working library with the reformatted source.


Temporary error (try again later)

I run into this issue when building a docker image on Ubuntu Host.
The Same build on Windows 10 using docker-tools CLI (so technically inside a VirtualBox VM) has no issues and Docker images are built correctly.
I have reinstalled Docker on my Ubuntu completely to have a fresh version just in case.
Any suggestions what else I can do to troubleshoot this issue?
Build command output
Sending build context to Docker daemon  572.4kB
Step 1/15 : FROM alpine:edge
edge: Pulling from library/alpine
cc5efb633992: Pull complete
Digest: sha256:2b796ae57cb164a11ce4dcc9e62a9ad10b64b38c4cc9748e456b5c11a19dc0f3
Status: Downloaded newer image for alpine:edge
 ---> f96c4363411f
Step 2/15 : RUN apk add --update nodejs
 ---> Running in 12865b082f34
fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/edge/main: temporary error (try again later)
WARNING: Ignoring APKINDEX.066df28d.tar.gz: No such file or directory
fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/edge/community: temporary error (try again later)
WARNING: Ignoring APKINDEX.b53994b4.tar.gz: No such file or directory
ERROR: unsatisfiable constraints:
  nodejs (missing):
    required by: world[nodejs]
The command '/bin/sh -c apk add --update nodejs' returned a non-zero code: 1

My dockerfile
FROM alpine:edge
RUN apk add --update nodejs

#create an app directory
RUN mkdir -p /app
WORKDIR /app

# create some useful folders
RUN mkdir -p /data

# Copy apps build in another folder
COPY main.js /app
COPY package.json /app
COPY version.json /app
COPY dist /app/dist
COPY data /data
COPY app_modules /app/app_modules
COPY node_modules /app/node_modules

#expose the port
EXPOSE 5555

#start the app
#ENV NODE_ENV=development
#ENV debug=true

WORKDIR /app

# comment if need a console in the container
CMD [ "node", "main.js" ]

This keeps popping up in other threads and I wonder if there might be a change in the way Fastly is doing DNS. To debug this we really need to see the output of something like curl -v -s http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz > /dev/null to get headers and the HTTP response from within a container. My guess is a temporary issue with a Fastly POP or a change in POP IP address that hasn't yet properly timed out in Docker DNS proxy yet.

@andyshinn I'll see if I can provide you with the output. However, I believe the issue is in Docker Engine, and possibly in DNS caching. My Host Machine was on the corporate network 1, but when we switched it to corporate network 2, the issue was gone.
After speaking to networking people, they weren't able to tell how the difference between networks could have affected the Docker Build. It points to a combination of DNS and Docker Engine. However, we ruled out the DNS, because on both networks we were able to do curl from the host and download the .gz files.
I checked my docker config and its DNS is set to <IP_ADDRESS> and <IP_ADDRESS>. From both networks these IPs are reachable.

I think it is related to #279 which has more history. I think maybe when Fastly changes server IPs they may be redirecting with a 301, which causes apk to choke. But this is why I want to output to see where it is redirecting. I'm not sure if it comes from Fastly or a broken upstream server.

So I'm having dns issues, but my results are different. My stuff just hangs at getting packages.
https://www.whatsmydns.net/#A/mirrors.aliyun.com
This is the mirror mine tries to use.
curl -vvvv -s http://mirrors.aliyun.com/alpine/v3.5/main/x86_64/APKINDEX.tar.gz > /dev/null
*   Trying <IP_ADDRESS>...
* Connected to mirrors.aliyun.com (<IP_ADDRESS>) port 80 (#0)
> GET /alpine/v3.5/main/x86_64/APKINDEX.tar.gz HTTP/1.1
> Host: mirrors.aliyun.com
> User-Agent: curl/7.47.0
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection 0

It will just hang here indefinitely in docker (at least for an hour+) and the curl times out. This is from my laptop:
recipes: curl -vvvv -s http://mirrors.aliyun.com/alpine/v3.5/main/x86_64/APKINDEX.tar.gz > /dev/null
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to mirrors.aliyun.com (<IP_ADDRESS>) port 80 (#0)
> GET /alpine/v3.5/main/x86_64/APKINDEX.tar.gz HTTP/1.1
> Host: mirrors.aliyun.com
> User-Agent: curl/7.52.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: Tengine
< Content-Type: application/octet-stream
< Content-Length: 732690
< Connection: keep-alive
< Date: Wed, 27 Sep 2017 13:45:47 GMT
< Last-Modified: Thu, 21 Sep 2017 10:13:30 GMT
< ETag: "59c390ca-b2e12"
< Expires: Wed, 27 Sep 2017 13:50:47 GMT
< Cache-Control: max-age=300
< Accept-Ranges: bytes
< Via: cache14.l2nu29[36,304-0,H], cache32.l2nu29[38,0], cache2.cn547[0,200-0,H], cache6.cn547[1,0]
< Age: 18
< X-Cache: HIT TCP_MEM_HIT dirn:3:81977809 mlen:-1
< X-Swift-SaveTime: Wed, 27 Sep 2017 13:45:48 GMT
< X-Swift-CacheTime: 120
< Timing-Allow-Origin: *
< EagleId: db939d4615065199657165411e
<
{ [12630 bytes data]
* Curl_http_done: called premature == 0
* Connection #0 to host mirrors.aliyun.com left intact

@andyshinn this may be a different issue. But it's DNS related, and works one place but not the other. This is from my system, but if you need it from inside docker, I can provide it.

Other mirrors do work. I suppose I have to go dig and see if they hard coded a mirror or something. It's odd though that it breaks apk so hard. I suppose I would have thought it to be more resilient

I was seeing this error on my Drone build server, running on Kubernetes. By default it users "Docker-in-Docker" (dind) for builds. The error went away after I disabled dind on the Drone server.

@Zest-nikunj sure. My Drone server was deployed by a Helm chart to a Kubernetes cluster: https://github.com/kubernetes/charts/tree/master/incubator/drone
I just redeployed it, setting dind.enabled to false. I'd imagine if you're not using Helm or Kubernetes, you'd have to mount the host's docker socket on the drone agent's container: https://github.com/kubernetes/charts/blob/master/incubator/drone/templates/deployment-agent.yaml#L52

Thanks @matkam. We are not on Kubernetes and the settings seem correct but we continue to have the issue. We will investigate further. If needed, I shall come back to you. Thanks again.

same problem ... before i resolved with reboot. Now it is not working

Same problem, just kept on re-trying, and 3rd time it went thru. seems like there is a bad server which the load balancer hits.

same error here

same problem here . I tried many many times ... it is not a bad server ... it seams a bug

Hit the same problem (again) and tried many suggested (in #279) suggestions, involving changing apk settings in Dockerfile and such. but nothing helped. What did help finally was to restart Docker and then apk just pulled the APKINDEX like nobody's business.

I get this as well on my workstation using Docker for Windows. Using a mirror did not help.

I had this error with Gitlab, i just change docker build command to run with --network host option and it works!

sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf helped on Ubuntu 16 build agent to make CI jobs build alpine based docker images again as per https://github.com/gliderlabs/docker-alpine/issues/279#issuecomment-411982620

@EvgeniGordeev That solution worked for me too, running Windows 10 host + Ubuntu 18.04 with Vagrant and alpinelinux in a docker container in the Ubuntu.

@wlechowicz restart docker service solved my issue 👍

@andyshinn , RE: https://github.com/gliderlabs/docker-alpine/issues/334#issuecomment-330096922
It was a DNS error for me. By setting /etc/docker/daemon.json with,
{
  "dns": ["<IP_ADDRESS>"]
}

and then restarting docker with,
sudo service docker restart

I was able to build images again.

Since there are times when the bridge is disturbing, it is successful if you execute it as host.
docker build -t hoge:latest . --network=host

restarting docker service maybe help you

Same issue. Not using docker at all. Not using any external services at all either. DNS and package mirrors are on my local network. Building using the mkimg scripts. I've also tried setting the mirror ip/hostname in /etc/hosts.
I can reliably replicate the failure using a completely fresh install of (a slighly custom) Alpine. I'm not running in a virtualised/containerised environment - it's a phyiscal server. I can provide any further information requested.

Run docker build command to run with --network=host option and it works

any idea how to add this workaround using docker-compose ?  the --network flag is not available there

I just ran into this, everything had been working fine on:
Windows 10 host with Hyper-V
Ubuntu 18.04 Guest
Docker in the Ubuntu 18.04
Suddenly apk and go mod download started failing. The APK issue was the temporary error.  Did the fix suggested in this comment https://github.com/gliderlabs/docker-alpine/issues/334#issuecomment-450598069 and everything was working again. DNS Was working fine on the guest and the host, only when building the docker containers was I having issues.

same error

same error
Ubuntu in VMware
Docker in the Ubuntu 18.04
change virtual machine's network setting to NAT mode, and it works

same error
Ubuntu in VMware
Docker in the Ubuntu 18.04
change virtual machine's network setting to NAT mode, and it works

It is usually caused by the local network, try to reboot

any idea how to add this workaround using docker-compose ? the --network flag is not available there
same problem. It will be great if someone can advise. Restarting docker or reboot is no go for my case

Since there are times when the bridge is disturbing, it is successful if you execute it as host.
docker build -t hoge:latest . --network=host

Thank YOU!

any idea how to add this workaround using docker-compose ? the --network flag is not available there

Same problem. I'm using Manjaro and none of the solutions worked for me

I have encountered this problem before. The reason is that docker cannot access the external network. Maybe the internal network has designated a private DNS server, so it is necessary to configure daemon.json

I solved using this: https://github.com/docker/for-linux/issues/957#issuecomment-627166787
Using Manjaro, one of the first things I do is install firewalld, but it's configured with nftable by default.
I changed it to iptables and then it was fixed.

vim  /etc/firewalld/firewalld.conf
change FirewallBackend=nftables to FirewallBackend=iptables
restart the service of firewalld with sudo systemctl restart firewalld.service

If you're building an image via docker-compose you might try the following to use the host network at build time:
version: "3.7"

services:
  my_service:
    build:
      context: .
      network: host # this line is the trick

On WSL2 I've been building docker images successfully for months, but today suddenly I'm getting this error. Tried --network=host and it is still not working. Rebooted a few times too.
A wget of the url from inside WSL2 command line works.
Not sure how to fix it.

fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/community/x86_64/APKINDEX.tar.gz
ERROR: unable to select packages:
python (no such package):
Getting above error while running command from .gilab-ci.yml
FYI command: apk add --no-cache python py-pip bash gawk sed grep bc coreutils
required by: world[python]

I am still seeing this error. I have a docker image that I CANNOT BUILD because of this. If the problem is with the CDN, **USE ANOTHER CDN! ** Software users should not be forced to suffer from upstream issues just because upstream won't do anything about it.

@minecraftchest1 Just got the 'temporary error' problem myself:
fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/community/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.12/main/x86_64/APKINDEX.tar.gz: temporary error (try again later)
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.12/community/x86_64/APKINDEX.tar.gz: temporary error (try again later)
ERROR: unsatisfiable constraints:
  ...

I tried a few different solutions, including explicitly defining DNS servers in the docker-compose file and in /etc/docker/daemon.json, to no avail.
For me, adding network: host to my docker-compose file fixed the problem:
version: "3.9"
services:
  backend:
    build:
      context: .
      dockerfile: ...
      network: host    <--- this fixed it

I have tried --network host with my docker build command which still doesn't solve it for me. I don't use docker compose.

For Raspberry Pi:

The answer is this: https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.13.0#time64_requirements
(alpine 3.13 isn't compatible with raspberry pi os by default due to some outdated package)
For Raspberry Pi, you can upgrade libseccomp2 to a supported version from the Debian Repos eg.
wget http://ftp.de.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.1-1_armhf.deb
dpkg -i libseccomp2_2.5.1-1_armhf.deb

[source]

just for reference, https://dl-cdn.alpinelinux.org/ and https://alpine.global.ssl.fastly.net are still redirecting from https to http:
$ curl -I https://dl-cdn.alpinelinux.org/alpine/v3.13/main
HTTP/2 301
server: nginx
content-type: text/html
location: http://dl-cdn.alpinelinux.org/alpine/v3.13/main/

$ curl -I https://alpine.global.ssl.fastly.net/alpine/v3.13/main
HTTP/1.1 301 Moved Permanently
Connection: keep-alive
Content-Length: 162
Server: nginx
Content-Type: text/html
Location: http://alpine.global.ssl.fastly.net/alpine/v3.13/main/

@wlechowicz restart docker service solved my issue +1

thank you boss, you save my life

For Raspberry Pi:

The answer is this: https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.13.0#time64_requirements
(alpine 3.13 isn't compatible with raspberry pi os by default due to some outdated package)

[source]

For Raspberry Pi, you can upgrade libseccomp2 to a supported version from the Debian Repos eg.
wget http://ftp.de.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.1-1_armhf.deb
dpkg -i libseccomp2_2.5.1-1_armhf.deb

[source]

Same issue exists for apline 3.14 and this solution works

I had the same issue.
Changing the Alpin version solved mine.  alpin:3.6

Actual version is 2.5.3-2
For Raspberry Pi, you can upgrade libseccomp2 to a supported version from the Debian Repos eg.
wget http://ftp.de.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.3-2_armhf.deb
dpkg -i libseccomp2_2.5.3-2_armhf.deb

I used the host network mode to run alpine and the issue was solved:
docker run -it --network host alpine

this helped me https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.13.0#musl_1.2
there are several solutions
so I had to download default.json, change one line and pass --security-opt=seccomp=default.json to docker run

@andyshinn , RE: #334 (comment)
It was a DNS error for me. By setting /etc/docker/daemon.json with,
{
  "dns": ["<IP_ADDRESS>"]
}

and then restarting docker with,
sudo service docker restart

I was able to build images again.

-In Windows
C:\Users\Administrator\.docker\daemon.json

And add this line.
{
    ...
    "dns": ["<IP_ADDRESS>"]
}

My fix for drone was setting the repository as Trusted under the repo settings in drone and then adding this to the docker build steps:
steps:
  -
    name: docker
    image: plugins/docker
    network_mode: host   <----- this

Similar error happen to me when I try to build docker images from within my kubernetes cluster but my workflow is more complex

Locally I build a small docker image with awscli/docker/bash/git

FROM docker:latest
# Update & Upgrade OS
RUN apk update
RUN apk upgrade
# https://github.com/aws/aws-cli/issues/4971#issuecomment-1330633153
COPY --from=devopscorner/aws-cli:latest /usr/local/aws-cli/ /usr/local/aws-cli/
COPY --from=devopscorner/aws-cli:latest /usr/local/bin/ /usr/local/bin/
RUN apk add bash git

My jenkins (deployed itself on a kubernetes cluster) has some pipelines that spawn some pods that grab this image

node(POD_LABEL) {

  stage('Clone') {
    git url: 'https://github.com/example/example/', branch: '${build_branch_name}', credentialsId: 'github-app'

    container('aws-dockerizer') {
      stage('Build and deploy') {
        withAWS(credentials: 'aws-credentials', region: 'eu-central-1') {
          sh '''#!/usr/bin/env bash
            git config --global --add safe.directory ${WORKSPACE}
            scripts/build_and_push_docker_image_to_aws.sh
          '''
        }
      }
    }
  }

}

The script runs a docker build step that builds my application image with some dependencies, here is an extract of the Dockerfile being built

FROM ruby:3.1.2-alpine
RUN apk add --update --no-cache   binutils-gold   build-base   curl   file   g++   gcc   git   less   libc-dev   htop   libffi-dev   libgcrypt-dev   libstdc++   libxml2-dev   libxslt-dev   linux-headers   make   netcat-openbsd   nodejs   yarn   openssl   pkgconfig   postgresql-dev   ruby-full   tzdata

I run into the following errors from the jenkins-spawned pod
#6 4.372 fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/main/x86_64/APKINDEX.tar.gz
#6 9.404 fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/community/x86_64/APKINDEX.tar.gz
#6 9.404 WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.16/main: temporary error (try again later)
#6 14.41 WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.16/community: temporary error (try again later)

Since there are times when the bridge is disturbing, it is successful if you execute it as host. docker build -t hoge:latest . --network=host

After struggling for so long with what I though was a kubernetes specific docker-in-docker issue, I ended up adding the --network=host in my scripts commands and it fixed it. I should have tried that first instead of going nuts.

I have the same issue with "slow" internet connection. Is "slow" for Docker, maybe it have low parameter for "temporary error"

Still happening...

I also had this issue randomly building ingress-nginx images on Docker Desktop.
0.260 fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/main/x86_64/APKINDEX.tar.gz
5.295 WARNING: updating https://dl-cdn.alpinelinux.org/alpine/v3.18/main: temporary error (try again later)
5.295 fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/x86_64/APKINDEX.tar.gz
10.41 WARNING: updating https://dl-cdn.alpinelinux.org/alpine/v3.18/community: temporary error (try again later)

I added the "dns": ["<IP_ADDRESS>"] line to the Docker Desktop config and now it builds consistently.

Same issue trying to build python:3.11-alpine.
Solved by adding dns '<IP_ADDRESS>' in my existing list in /etc/docker/daemon.json :
{
        "dns": ["42.xx.xx.42", "<IP_ADDRESS>"]
}

as described in previous comment > https://github.com/gliderlabs/docker-alpine/issues/334#issuecomment-1135351701

Any recommendations to address it ?
So far, I have tried

Enabling UnsafeLegacyRenegotiation in /etc/ssl/openssl.cnf
Adding DNS to /etc/docker/daemon.json

Since there are times when the bridge is disturbing, it is successful if you execute it as host. docker build -t hoge:latest . --network=host

After struggling for so long with what I though was a kubernetes specific docker-in-docker issue, I ended up adding the --network=host in my scripts commands and it fixed it. I should have tried that first instead of going nuts.

where did u add the netwrok =true ? is that in the jenkins agent config command?

Figured it out what caused it for me. I had enabled IPV6 on my host and that caused the only DNS server in /etc/resolv.conf to also be IPV6. Disabling IPV6 again caused the build to run through. I could pretty much consistently trigger a failed/successful build by switching between an IPV6 DNS server and an IPV4 DNS server.
Some more info:
OS: Debian 12
OCI: Podman
Network changes relevant:
sudo nano /etc/network/interfaces
and then adding
iface eth0 inet6 dhcp
        dhcp6-pd yes

(Replace eth0 with whatever your actual network interface is)
Then just restart networking (sudo service networking restart)
As soon as you get the files once it won't reproduce until you clear all the build caches.

I had this error with Gitlab, i just change docker build command to run with --network host option and it works!我在 Gitlab 上遇到了这个错误，我只需将 docker build 命令更改为使用 --network host 选项运行即可，它可以工作！

works for me

I had this error with Gitlab, i just change docker build command to run with --network host option and it works!

works for me

In my case, I got this error when ca-certificates package is not installed and set /etc/apk/repositories to a HTTPS mirror, e.g.:
https://mirrors.aliyun.com/alpine/v3.18/main
https://mirrors.aliyun.com/alpine/v3.18/community

To work around, use HTTP mirror:
RUN sed -e 's/https:\/\/dl-cdn.alpinelinux.org/http:\/\/mirrors.aliyun.com/g' \
        -i /etc/apk/repositories \
    && apk add --no-cache tzdata

I used a borrowed retry function to get past this:
function retry {
  local retries=$1
  shift

  local count=0
  until "$@"; do
    exit=$?
    wait=$((2 ** $count))
    count=$(($count + 1))
    if [ $count -lt $retries ]; then
      echo "Retry $count/$retries exited $exit, retrying in $wait seconds..."
      sleep $wait
    else
      echo "Retry $count/$retries exited $exit, no more retries left."
      return $exit
    fi
  done
  return 0
}

retry 10 apk add --no-cache aws-cli jq

Another data point for those who stumble upon this thread: my issue was with Tailscale, needed to turn off stateful filtering with tailscale up --stateful-filtering=false
See https://tailscale.com/s/stateful-docker

For me it was the firewall blocking it. Turned it off temporarily with sudo systemctl stop firewalld and it built just fine.


Unable to run spatiaLite extension

How to load spatiaLite extension for spatial query ?

It works like this:

At first, you have to enable the function load_extension(..):

If you use DriverManager: Set up SQLiteConfig as described under Configure Connections and call config.enableLoadExtension(true)
If you use an connection pool like Hikari: Make sure you set the following property on the Properties object that you pass to the pool:
config.setProperty("dataSource.enable_load_extension", Boolean.toString(true));

Execute SELECT load_extension('mod_spatialite') (replace 'mod_spatiallite' with the actual name of the library. File extension can be omitted).

Further reading:
https://sqlite.org/loadext.html
http://www.gaia-gis.it/gaia-sins/splite-doxy-5.0.1/index.html

@meilleureVie can this be closed?


Added TermsSetQuery

Implement #299

Codecov Report

Merging #300 into master will increase coverage by 0.12%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #300      +/-   ##
============================================
+ Coverage     78.49%   78.61%   +0.12%
- Complexity      730      733       +3
============================================
  Files           122      123       +1
  Lines          1883     1894      +11
============================================
+ Hits           1478     1489      +11
  Misses          405      405

Impacted Files
Coverage Δ
Complexity Δ

src/Query/TermLevel/TermsSetQuery.php
100% <100%> (ø)
3 <3> (?)

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 2f4edab...56f6ee5. Read the comment docs.

@saimaz any remarks on this ☝
Tnx

Seems all good, let's merge it

cherry-picked in the https://github.com/ongr-io/ElasticsearchDSL/commit/59f9e4452f9762041e955d21725db7cce6510886


Optional query parameter for Horizon endpoints to include/exclude XDR-encoded fields

The XDR data size in response of /transactions and /ledgers endpoints may be quite substantial compared with the overall response size:

~30% for /ledgers (header_xdr field)
~80-96% for  /transactions (envelope_xdr, result_xdr, result_meta_xdr, fee_meta_xdr fields)

Additional query parameter (say, include_xdr or with_xdr) that controls whether the XDR-encoded fields are included in the Horizon response may bring significant bandwidth, CPU, and memory resources economy. It may be essential for the future Horizon scaling in high-load scenarios.
In most cases client applications don't use raw XDR, so excluding those fields by default makes sense.
Query format:
GET https://horizon.stellar.org/ledgers/?include_xdr=true
GET https://horizon.stellar.org/transactions/?include_xdr=true

Pros:

Faster serialization and reduced traffic from DB on the server side
Faster deserialization and lower memory footprint on the client side
Bandwidth economy

Cons:

Need to update all SDKs

Leaving this open but I think we should use something like GraphQL as it gives you better control of query and response.


Connect-Rubrik - add support for MFA

Is your feature request related to a problem? Please describe.
We recently turned on RSA for multi-factor Auth on our Rubrik server. There doesn't seem to be any support for that in the Connect-Rubrik command.
Describe the solution you'd like
Enable some way to handle MFA when using Connect-Rubrik.
Describe alternatives you've considered
Could possibly use a token, but unable to generate one right now.
Additional context
Getting an "Authentication is possible but has failed or not yet been provided" message after an Invoke-WebRequest call.

Just following up on this. Is there a workaround that can be used? Can anyone point to a working process/procedure?

Does any one have a workaround for this yet?

I ended up generating a token in the Rubrik site. I just saved that to a file and then use a Get-Content for the file and pass that in for the -Token param.
Why can you not generate a token on the site?  That might be the better problem to address.

Perfect. That worked for me. Thank you very much for your help!

The way around MFA for the powershell module is to use an API token. API tokens are more secure than using a basic authentication with MFA.
The approach we are moving to as a whole is to use Service Accounts. You can see how to use them here. https://rubrikinc.github.io/rubrik-api-documentation/api/auth/
When you use the Connect-Rubrik cmdlet it creates a Global Variable called $RubrikConnection. You will see it addressed as $Global:RubrikConnection. To use a Service Account with the module you can create the connection with the below code.
When you create the Service account in CDM, you can create a json file or some other file to store the contents.
If you have a vault or a more secure way to store this information, that would be better than a file.
$ServiceAccountPath = "C:\Scripts\CDM-DatabaseAutomation.json"
The below is used to talk to your CDM cluster and get the API session token based on your Service Account details in the file above.
$sessionURL = "https://$cluster/api/v1/service_account/session"
#region Connect to CDM
Read the contents of the json file in, or if you stored in a vault update the below code accordingly.
Talk to the CDM cluster and get the session token.
Create a $Global:RubrikConnection to use with Rubrik cmdlets
$ContentType = "application/json"
$ServiceAccount = Get-Content -Raw -Path $ServiceAccountPath | ConvertFrom-Json
$ConnectToRubrik = @{
Method = 'Post'
URI = "$($sessionURL)"
ContentType = $ContentType
Body = @{
serviceAccountId = "$($ServiceAccount.client_id)"
secret = "$($ServiceAccount.client_secret)"
} | ConvertTo-Json
}
$rubrikSession = Invoke-RestMethod @ConnectToRubrik
$rubrikSession
$Global:RubrikConnection = @{
api = 1
server = $cluster
token = $rubrikSession.token
header = @{
'Authorization' = "Bearer $($rubrikSession.token)"
}
}
#endregion

The way around MFA for the powershell module is to use an API token. API tokens are more secure than using a basic authentication with MFA. The approach we are moving to as a whole is to use Service Accounts. You can see how to use them here. https://rubrikinc.github.io/rubrik-api-documentation/api/auth/
When you use the Connect-Rubrik cmdlet it creates a Global Variable called $RubrikConnection. You will see it addressed as $Global:RubrikConnection. To use a Service Account with the module you can create the connection with the below code.
# When you create the Service account in CDM, you can create a json file or some other file to store the contents.
# If you have a vault or a more secure way to store this information, that would be better than a file.
$ServiceAccountPath = "C:\Scripts\CDM-DatabaseAutomation.json"

# The below is used to talk to your CDM cluster and get the API session token based on your Service Account details in the file above.
$sessionURL = "https://$cluster/api/v1/service_account/session"

#region Connect to CDM
# Read the contents of the json file in, or if you stored in a vault update the below code accordingly.
# Talk to the CDM cluster and get the session token.
# Create a $Global:RubrikConnection to use with Rubrik cmdlets
$ContentType = "application/json"
$ServiceAccount = Get-Content -Raw -Path $ServiceAccountPath | ConvertFrom-Json
$ConnectToRubrik = @{
	Method = 'Post'
	URI = "$($sessionURL)"
	ContentType = $ContentType
	Body = @{
		serviceAccountId = "$($ServiceAccount.client_id)"
		secret = "$($ServiceAccount.client_secret)"
	} | ConvertTo-Json
}
$rubrikSession = Invoke-RestMethod @ConnectToRubrik
$rubrikSession

$Global:RubrikConnection = @{
  api = 1
  server = $cluster
  token = $rubrikSession.token
  header = @{
    'Authorization' = "Bearer $($rubrikSession.token)"
  }
}
#endregion

That worked! awesome. Thank you!

In case of MFA:
If you manually generate a token from the GUI, you can use that token as long as it doesn't expire.
However, after some time (security!) the token expires. Via the GUI you can generate new tokens even before the previous token expires, but you cannot use API with a (nearly expiring) token to generate a new token.
So you can use automation through the API until your token expires, after that your automation is lost until you do things manually.


Meeting problem when apply the resumable_iterator.patch to CoorDL

I installed CUDA10.0 to my server. When I apply the resumable_iterator.patch to CoorDL, the terminal always shows:

echo 'Wrong CUDA_VERSION=10.1.163 provided. Only 9 and 10 are supported'
Wrong CUDA_VERSION=10.1.163 provided. Only 9 and 10 are supported

I also tried CUDA10.1, it also shows this.
Can you tell how to fix this?

BTW, the basic image building page seems missed.
https://github.com/msr-fiddle/ds_analyzer/README.md/


[BUG] 404 link in the documentation

Environment
Self-Hosted (Docker)
System
Debian 11
Version
2.1.1
Describe the problem
In "https://github.com/Lissy93/dashy/wiki/configuring#sectionicon-and-sectionitemicon" says: "See Icon Docs for all available supported icon types" but https://github.com/docs/icons.md returns 404.
Additional info
No response
Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

https://github.com/Lissy93/dashy/blob/master/docs/icons.md

https://github.com/Lissy93/dashy/blob/master/docs/icons.md

                                    **                          dashy/icons.md at master · Lissy93/dashy                      **                            🚀 A self-hostable personal dashboard built for you. Includes status-checking, widgets, themes, icon packs, a UI editor and tons more! - dashy/icons.md at master · Lissy93/dashy

Thank you! I had already found the right link, but I'm new to github and I didn't know how to help correcting the link for others, is there a better way? I don't want to bother people if I don't have to.
Thank you again.


ERROR in Cannot find module 'json5' && [webpack-isomorphic-tools] [error] asset not found

ERROR in Cannot find module 'json5'
@ ./common/components/Counter.js 63:23-59
[webpack-isomorphic-tools] [error] asset not found: ./common/assets/images/Plus.png
webpack-assets.json
{
  "javascript": {
    "main": "/static/bundle.js"
  },
  "styles": {},
  "assets": {}
}

webpack.config.js

var path = require('path')
var webpack = require('webpack')
var Webpack_isomorphic_tools_plugin = require('webpack-isomorphic-tools/plugin')

var webpack_isomorphic_tools_plugin =
    // webpack-isomorphic-tools settings reside in a separate .js file
    // (because they will be used in the web server code too).
    new Webpack_isomorphic_tools_plugin(require('./webpack-isomorphic-tools-configuration'))
    // also enter development mode since it's a development webpack configuration
    // (see below for explanation)
        .development();

module.exports = {
    devtool: 'inline-source-map',
    entry: [
        'webpack-hot-middleware/client',
        './client/index.js'
    ],
    output: {
        path: path.join(__dirname, 'dist'),
        filename: 'bundle.js',
        publicPath: '/static/'
    },
    plugins: [
        new webpack.optimize.OccurenceOrderPlugin(),
        new webpack.HotModuleReplacementPlugin(),
        new webpack.NoErrorsPlugin(),
        webpack_isomorphic_tools_plugin
    ],
    module: {
        loaders: [
            {
                test: /\.js$/,
                loader: 'babel',
                exclude: /node_modules/,
                include: __dirname,
                query: {
                    optional: ['runtime'],
                    stage: 2,
                    env: {
                        development: {
                            plugins: [
                                'react-transform'
                            ],
                            extra: {
                                'react-transform': {
                                    transforms: [
                                        {
                                            transform: 'react-transform-hmr',
                                            imports: ['react'],
                                            locals: ['module']
                                        }
                                    ]
                                }
                            }
                        }
                    }
                }
            },
            {
                test: webpack_isomorphic_tools_plugin.regular_expression('images'),
                loader: 'url-loader?limit=10240', // any image below or equal to 10K will be converted to inline base64 instead
            }
        ]
    }
}

Post your ./webpack-isomorphic-tools-configuration

webpack-isomorphic-tools-configuration.js
import Webpack_isomorphic_tools_plugin from 'webpack-isomorphic-tools/plugin'

export default
{
  assets:
  {
    images:
    {
      extensions: ['png', 'jpg', 'gif', 'ico', 'svg']
    }
  }
}

I try to add webpack-isomorphic-tools to the Redux example,but I got the problem above:
https://github.com/reactjs/redux/tree/master/examples/universal

The configuration seems ok.
You can try to add console.log('===========', require('./common/assets/images/Plus.png')) to ./client/index.js and report back the result.

Also you can try to add debug: true flag to webpack-isomorphic-tools-configuration.js and post the output here.

<EMAIL_ADDRESS>start /home/lewis/code/react-redux-tutorial/redux-examples/universal
node server/index.js

[webpack-isomorphic-tools] [debug] instantiated webpack-isomorphic-tools v2.2.48 with options {
"debug": true,
"assets": {
"images": {
"extensions": [
"png",
"jpg",
"gif",
"ico",
"svg"
]
}
},
"webpack_assets_file_path": "webpack-assets.json",
"webpack_stats_file_path": "webpack-stats.json"
}
[webpack-isomorphic-tools] [debug] entering production mode
[webpack-isomorphic-tools] [debug] registering require() hooks for assets
[webpack-isomorphic-tools] [debug]  registering a require() hook for *.png
[require-hook] [debug] Hooking into *.png files loading
[webpack-isomorphic-tools] [debug]  registering a require() hook for *.jpg
[require-hook] [debug] Hooking into *.jpg files loading
[webpack-isomorphic-tools] [debug]  registering a require() hook for *.gif
[require-hook] [debug] Hooking into *.gif files loading
[webpack-isomorphic-tools] [debug]  registering a require() hook for *.ico
[require-hook] [debug] Hooking into *.ico files loading
[webpack-isomorphic-tools] [debug]  registering a require() hook for *.svg
[require-hook] [debug] Hooking into *.svg files loading
[webpack-isomorphic-tools] [debug] (/home/lewis/code/react-redux-tutorial/redux-examples/universal/webpack-assets.json not found)
[webpack-isomorphic-tools] (waiting for the first Webpack build to finish)
[webpack-isomorphic-tools] [debug] (/home/lewis/code/react-redux-tutorial/redux-examples/universal/webpack-assets.json not found)
[webpack-isomorphic-tools] (waiting for the first Webpack build to finish)
[webpack-isomorphic-tools] [debug] (/home/lewis/code/react-redux-tutorial/redux-examples/universal/webpack-assets.json not found)
[webpack-isomorphic-tools] (waiting for the first Webpack build to finish)
loop and loop   not found

><EMAIL_ADDRESS>start /home/lewis/code/react-redux-tutorial/redux-examples/universal
> node server/index.js

[webpack-isomorphic-tools] [debug] instantiated webpack-isomorphic-tools v2.2.48 with options {
  "debug": true,
  "assets": {
    "images": {
      "extensions": [
        "png",
        "jpg",
        "gif",
        "ico",
        "svg"
      ]
    }
  },
  "webpack_assets_file_path": "webpack-assets.json",
  "webpack_stats_file_path": "webpack-stats.json"
}
[webpack-isomorphic-tools] [debug] entering production mode
[webpack-isomorphic-tools] [debug] registering require() hooks for assets
[webpack-isomorphic-tools] [debug]  registering a require() hook for *.png
[require-hook] [debug] Hooking into *.png files loading
[webpack-isomorphic-tools] [debug]  registering a require() hook for *.jpg
[require-hook] [debug] Hooking into *.jpg files loading
[webpack-isomorphic-tools] [debug]  registering a require() hook for *.gif
[require-hook] [debug] Hooking into *.gif files loading
[webpack-isomorphic-tools] [debug]  registering a require() hook for *.ico
[require-hook] [debug] Hooking into *.ico files loading
[webpack-isomorphic-tools] [debug]  registering a require() hook for *.svg
[require-hook] [debug] Hooking into *.svg files loading
[webpack-isomorphic-tools] [debug] (/home/lewis/code/react-redux-tutorial/redux-examples/universal/webpack-assets.json not found)
[webpack-isomorphic-tools] (waiting for the first Webpack build to finish)
[webpack-isomorphic-tools] [debug] (/home/lewis/code/react-redux-tutorial/redux-examples/universal/webpack-assets.json not found)
[webpack-isomorphic-tools] (waiting for the first Webpack build to finish)
[webpack-isomorphic-tools] [debug] (/home/lewis/code/react-redux-tutorial/redux-examples/universal/webpack-assets.json not found)
[webpack-isomorphic-tools] (waiting for the first Webpack build to finish)

and, what does it output when you render your component with the image?

if it loops indefinitely then read this section for troubleshooting
https://github.com/halt-hammerzeit/webpack-isomorphic-tools#infinite-waiting-for-the-first-webpack-build-to-finish

you aren't running your Webpack build either in parallel with your app or prior to running you app
you're using webpack-dev-middleware inside your main server code which you shouldn't

I think problem is this,   this tools should be used in a server , and webpack dev server should be another .

Ok, then you just need to run your webpack build and after that webpack-assets.json will be generated

If you like, you can write a simple demo base on redux  example，https://github.com/reactjs/redux/tree/master/examples/universal
maybe helpful to learn to use this tools

Well, these tools aren't bound to Redux or anything like that.
They aren't bound to React either.
Their only dependence is Webpack.

en ,  I should learn to use it  flexibly

FYI
I'm posting this in every issue and PR to notify whoever may be interested:
today I've released an alternative helper library called universal-webpack.
It takes a different approach than webpack-ismorphic-tools and instead of hacking Node.js require() calls it just compiles all code with target: 'node' webpack configuration option.
As a result, all Webpack plugins and features are supported.
If you think you might need that here's an example project:
https://github.com/halt-hammerzeit/webpack-react-redux-isomorphic-render-example


do not patch status if resource is not managed

Issue #, if available:
https://github.com/aws-controllers-k8s/community/issues/931
Description of changes:
Solution 1 in the issue linked above - return nil, nil instead of resource, nil after finalizer is removed
Testing:
make test
Manually using sagemaker controller
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Waiting for other ACK core team members to take a look as well.
I will merge this PR tomorrow morning, if it does not receive new comments.


FTP download for Internet download manager

Hi @arakasi72 , is there any method to change from ftps to ftp? So we can directly download using internet download manager ?

You can use ftp if you want, specify in the local client, and it should be ok.
If not in /etc/vsftpd.conf change the following variables from YES to NO:
force_local_data_ssl
force_local_logins_ssl

Thanks it working ! @arakasi72


Deploy Registry-API using Terraform in NGAP

💡 Description

Configure all deployable components of Registry API using Terraform. Also create Terrafrom workflow for Continuous Deployment using Github actions.
The scope of this task will include re-architecting how registry-api image gets deployed. Ideally with every push to main, we want to deploy a new docker image on ECR and have Terraform workflow use it to deploy / configure the ECS infrastructure.

Sagar reports: in progress, no blockers ATM

NGAP is not a deployment target anymore for PDS. We use MCP instead and deployment work with MCP as described in ticket https://github.com/NASA-PDS/registry-api/issues/509


Tool and workflow deletion

Feature Request
Desired behaviour
Users should have the ability to delete their own tools and workflows.
Alternatively, to switch the Build Mode
Note that we already have "deregister" for manually registered tools.
We ran into this when debugging tools that were registered as manual before build triggers were added to the underlying repos.
Environment (Browser or OS and Dockstore version)
1.1.5

After putting more thought into the idea of a delete button instead of a restub, and having the workflow disappear until the next refresh, I am starting to not like the idea.
A user might get annoyed if they delete a tool and then it comes back suddenly next time they refresh.
The main purpose we thought of was that a user wanted to completely reset a workflow, just in case they configured something wrong.
Perhaps updating the existing restub code to remove all extra data from the workflow, and just create a blank workflow with only the necessary defaults selected. Pretty much make it do the same thing as deleting the workflow and refreshing, but now the user won't see the tool randomly appear.
Also, we should more obviously indicate if a workflow is a stub or not on the my workflows page.

Not entirely related, but if we keep the stubbing feature, it might be useful to have a filter checkbox in the left panel somewhere that automatically hides all the stubbed workflows from the panel(s).   This is in the event that the user has a bunch of github organizations that are unneeded.

I think the problem is that there are two scenarios that someone would want to delete it.

The stub is totally irrelevant and they just want to delete it permanently.
The workflow was configured in a crummy way and it would be easier to delete it and restart.

I think unstub makes sense for both if we don't switch to a dockstore.yml. I think delete makes more sense for both when we do switch to a dockstore.yml.
Since the issue is essentially broken up into two parts, tools and workflows, maybe we can tackle this in two phases.

Add delete across the board for tools since the re-appearing problem doesn't occur there
Close/rename the tickets having to do with tool delete
Reschedule a closer look at workflow deletion at a time closer to the next release when we've decided on dockstore.yml

Just noting that I have added 1. Delete tools across the board


[Observation] Correct potential alignment of locks to ensure that os_unfair_lock is properly at an aligned address

The locking mechanism for Observation had a potential of misaligning the lock element; This was because it was only an element type of UInt8 - by changing it to a pointer it forces the alignment to be suitable for the maximum potential alignment of any stored lock.

@swift-ci please smoke test


Bug: recursive option in short format with other flags

https://github.com/jmattaa/laser/blob/8bd554916a7ede43c3686dc52f0563424e1d6ff0/src/utils.c#L52-L64
Running for example lsr -rS will cause the program to ignore the -S flag. But running -Sr works.
Expected functionality
lsr -rS and lsr -Sr should behave the same.

Its because s flag does not support arguments, but r does. line with getopt_long(argc, argv, "aFDSGr::l", long_args, NULL). I will try to fix it by falling to next argument case if r gets not a number.

By the way, flags must chain with delimiter like - or -- (-r -S but not -rS). Maybe its not bug at all

In future you can add numerical flags, and it will broke all complex parsing system for args like -r10S -rS 10

You want to support fast "flags" (smth like -rSfabc) , its better to add separate option for it , like
lsr --lflag rSa and parse it in  getopt check loop from optarg pointer


fix the grep error using compatible option

-P is not available on macos, but -E is.  It should also be available on linux.

:) Thanks!


How to create wake word engine with AVS sdk

Hi There
I'm creating a open of wake word engine can be used in AVS system in following like.
https://github.com/chesterkuo/kaggle-speech-challenge-1
The Benchmark results of inference speed for speech (wav file) about 60-75ms and verify on RP3 platform.
I'd like to share and integrate into AVS so people can train this engine with their own speech data.
How to quick create a wake word engine for AVS SDK ?
There already example for python/C++ interface in github also.

The model I had is based on CNN as network with mfcc input, and multiple label (pretrain model have "left", "right"...etc as spot word detection.
The frozen graph size about 5MB, and run time of inference is 60-75ms based on RP3.
People can train there own speech (word)by retraining to support your own data and apply as your spot word wake up engine.
For inference/test it , just use wav file as input and it will report prob result to see if it match spot words we had.

Hi @chesterkuo, have you tried to create an implementation of AbstractKeywordDetector as suggested above?

@celinval ,
Not yet, as i'm working on another project to support ASR running on device site (without using cloud) for simple task , so for simple tasks like wether, alarm can be handled in local device instead of going to Cloud.
Please go ahead to handle it if you needs, and drop me if you need help from my side on Tensorflow inference of spot word detection, i'm happy to help on this.
<EMAIL_ADDRESS>

Hi Chester!
Thank you for your interest and effort! As for the original matter - do you still have questions on it?

Maybe we can keep this open but use different label instead of closing it directly.
So people can still find this info if they need full source code implementation of wake up engine.

Hi Chester,
This sounds like an interesting project.  I'm going to go ahead and close the issue for now since you don't have any specific problems waiting on feedback, but it will remain on github and be searchable.  Please feel free to reopen if you run into any problems with integration and we'll be glad to help out.
Ken


NixOS fails to boot after upgrade and none of the 15 other versions work either

This is not what I expect to see after a successful upgrade (i.e. one that has an exit status of zero).

How can this situation be salvaged? None of the grub entries work. I do use ZFS, but that's it complexity wise. I would like to receive some assistance in getting this to work again.
If I could have run some VM automatically to verify the setup next time, I would have preferred to do that, instead of having to write this bug report again.
But with releases like this, I am not sure whether it is wise to call it an "upgrade". IMHO, this (16.03) should never have been released in the first place.
Should I use some kind of rescue CD?

It looks like it can't find the kernel where it expected it, so your boot config is wrong somehow. Try finding where it should get the kernel from by going into the grub command line and using tab completion on the disks.

There was a range of nixpkgs commits when Grub was broken. Try to edit the grub when you boot and prepend /nix/store to all the hash parts you see for a single entry to boot.
And when you boot, please write nixos-version here so we can see if you're really using the old commit or something is really broken.

Hm, maybe this is related somehow to ZFS indeed, but I'm not sure. Either way -- sounds not nice at all. You mentioned that you have updated -- if so I think you can at least revert by booting from 15.09 installation CD, mounting everything as you would do to install NixOS and then running nixos-install -- it would build 15.09 per your current configuration and re-install GRUB, hopefully fixing the problem.

@domenkozar Are you also saying that /nix/store/*linux-4.4.6 should exist?

Yes.

For completeness this is what Grub2 tries to do:

The repetition of // and @// seems suspicious indeed. Can we have an assertion somewhere that any configuration which has two subsequent / characters is not considered to be a valid configuration?

@aszlig another place :-)

@0xABAB can you provide what nixos-version you're using?

This is what I get now, after putting nix/store in the various places. "nix" is a rather unqualified location, which is also not something I like.

@domenkozar I upgraded to the 16.03 release. Various numbers can be found in the screenshots above. I cannot actually run NixOS now, as you know.

@domenkozar Any more ideas?

@0xABAB can you provide the configuration file? It's hard to guess without exacts steps to reproduce.

@domenkozar I was still only in hacking around mode with NixOS. So, it's all on the machine itself. I am now running the latest stable NixOS CD, but I need to figure out how to mount my ZFS pools. I don't get why it doesn't do that by default (i.e., detect and just mount them under /mnt/zfs/whatever).

@domenkozar zfs list as root returns no datasets available when booted from the 16.03 Stable CD. Does that mean that all my data is gone with the wind?

Hmm, it's not that bad.

@domenkozar Which configuration file do you want to have?

For future reference:
mount -t zfs -o zfsutil zpool/nixos /mymountpoint can be used as a hack to not have to set zfs mountpoint variables.

I also would prefer to not see any WARNINGs in processes involving a kernel:

@abbradar  My system is alive again, which was partially sped up by your contribution to this thread. Thanks.
I would say this issue can be closed once we know or have a good guess as to what caused this. I have the impression that @domenkozar and @aszlig have such a good guess, but I think it's clear that this stuff should never happen.

@0xABAB To help with determining what caused the issue: did you make changes to your /etc/nixos/ config to get it running again, or did you re-install from a 15.09 livecd as abbradar suggested? If the former, what did you change? If the latter, can you pastebin the contents of your /etc/nixos/ files?
Also, did you did the nixos-rebuild switch --upgrade the same day you posted about this issue?

Would be probably a good idea to have an installer test for ZFS, especially if ZFS was the issue here to also serve as a regression test.

@Shados I followed @abbradar's instructions with some command to make the zpool available, etc.
To answer your last question: yes.

I just hit this issue too, but I'm on NixOS 15.09. I didn't notice anything bad during "nixos-rebuild switch". Rebooted and none of the grub entries worked. All "linux" and "initrd" entries were missing "/nix/store/" prefix; instead they had just two slashes "//" (so the system couldn't find the file(s) and failed to boot). Editing the command line in grub worked, booted and ran "nixos-rebuild switch" again. Now grub entries are fixed. Scary.

@bjornfor did you mount /nix/store as writeable by any chance?

@domenkozar: Yes I did! Spot on! (Thank you!)
I had completely forgotten about that. I was working on a proprietary package and had temporarily writeable nix store as a way to investigate what files the package wanted to write to (it was segfaulting on startup). Not a good idea in retrospect. But on the other hand, WHY ON EARTH did nixos-rebuild break like that?

See https://github.com/NixOS/nixpkgs/issues/14999

@0xABAB is this also your case? If so, let's close this issue :)

@domenkozar I am not 100% sure, but that's likely. The sanity checks should still be added. I would be happy if those sanity checks are there in combination with the fix for #14999.
In fact, before rebooting there should be some checks that some kernel files actually exist and have a reasonable size (pick some useful lower bound according to your own insight). I know that on some operating systems in certain circumstances (for example with hardware RAID) there are lies about which files actually exist, even though in theory this issues should never occur.
So, from an engineering point of view, I would love to see some additional stat calls too. You could split this off as a separate feature request.

I'll close this in favor of #14999 for now as it appears to be a duplicate.


webtorrent data sync

Try out a static example, two pages:

Create torrent and search index from a data object and seed +  search
Leech that torrent and search data.

This will be a static search-index. But maybe we could manage to do incremental backup-style update of data. Not sure, but could be worth a test.
Also, just to show a search-index replicated with a webtorrent would be awesome.

Not sure how safe you can get trackers, but maybe you could implement authentication on tracker level? Also a webtorrent-desktop client is all that is needed to keep your search server alive.
Or if you want a bit more sturdy setup, do it with webtorrent-cli
The search engine will be using webtorrent in the browser creating and seeding data.


Fix to slider tick mark alignment (issue #48304)

Description
This change fixes the alignment of slider tick marks with the slider's thumb. The issue becomes apparent when large values are used for the height of the slider's track and the ticks marks' width. The tick marks will be shifted toward the center of the track and therefore not align properly with the thumb.
The change results in proper alignment of the tick marks' and the thumb's centers in all positions.

@googlebot I signed it!

Seems like my change breaks the slider tests in framework_tests_library_linux
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TestFailure object was thrown running a test:
  Expected: Object or closure painting: 'a circle with point Offset(25.0, 24.0), radius 1.0', 'a
circle with point Offset(212.5, 24.0), radius 1.0', 'a circle with point Offset(400.0, 24.0), radius
1.0', 'a circle with point Offset(587.5, 24.0), radius 1.0', 'a circle with point Offset(775.0,
24.0), radius 1.0', 'a circle with point Offset(24.0, 24.0), radius 10.0'
  Actual: _RenderSlider:<_RenderSlider#6b5de>
   Which: did not match the pattern.
          It called drawCircle with a center coordinate, Offset(24.0, 24.0), which was not exactly
the expected coordinate (Offset(25.0, 24.0)).
          The stack of the offending call was:
            #0      TestRecordingCanvas.noSuchMethod
(file:///tmp/flutter%20sdk/packages/flutter/test/rendering/recording_canvas.dart:89:70)
            #1      TestRecordingCanvas.drawCircle (dart:ui/painting.dart:3679:8)
            #2      RoundSliderTickMarkShape.paint
(package:flutter/src/material/slider_theme.dart:2052:22)
            #3      _RenderSlider.paint (package:flutter/src/material/slider.dart:1138:38)

The change of circle coordinates is intended by the patch, so if the patch is to be accepted, a change to the tests also needs to be done.
Thanks.

@clocksmith can you take a look at this one?
It looks like a reasonable fix to me, but I am not that familiar with this code. It does seem off that the thumb center is calculated based on the entire track width, but the tick marks are calculated based on the track width minus the tick width. Which means they won't line up properly.
To see an illustration of this issue (forgive the garish colors...):
import 'package:flutter/material.dart';

void main() => runApp(
  MaterialApp(
    theme: ThemeData.from(colorScheme: const ColorScheme.light()),
    home: Scaffold(
      appBar: AppBar(
        title: const Text('Sliders'),
      ),
      body: DiscreteSlider(),
    ),
  )
);

class DiscreteSlider extends StatefulWidget {
  @override
  _DiscreteSliderState createState() => _DiscreteSliderState();
}

class _DiscreteSliderState extends State<DiscreteSlider> {
  double _value = 0.0;

  @override
  Widget build(BuildContext context) {
    return Column(
      children: <Widget>[
        SliderTheme(
          data: SliderThemeData(
            tickMarkShape: RoundSliderTickMarkShape(tickMarkRadius: 10.0),
            trackHeight: 5.0,
            activeTickMarkColor: Colors.blue,
            inactiveTickMarkColor: Colors.blueGrey,
          ),
          child: Material(
            clipBehavior: Clip.antiAlias,
            child: Slider(
              value: _value,
              min: 0,
              max: 100,
              divisions: 5,
              onChanged: (double value) => setState(() => _value = value),
            ),
          ),
        ),
        Text('$_value'),
      ],
    );
  }
}

Hi, we are in the process of fixing this with the slider v2 update.
See https://groups.google.com/g/flutter-announce/c/69dmlKUL5Ew towards the bottom

Based on @clocksmith's comment above, I am going to close this PR as it will be super-ceded by the upcoming slider V2 update.


Gift Entry - Remove Gift From Elevate

Critical Changes
Changes

Gifts added to Batch Gift Entry that are processed through Elevate will no longer need to be added to their own individual Elevate batches
When a credit card gift has been added to Batch Gift Entry and is then either deleted from BGE or updated to no longer be a credit card gift, then the gift will be automatically removed from Elevate.

Issues Closed
Community Ideas Delivered
Features Intended for Future Release
Features for Elevate Customers
New Metadata
Lightning Web Components:

geElevateBatch

Deleted Metadata

@sokosaurus see my comment here about the bullets in the PR:  https://salesforce.quip.com/hjpOAUGvctSz#temp:C:AWccks6nb6h60002305ekem4ds46

@sokosaurus Reviewed the labels and added changes based on my final conversation with the UI text team. Once those suggestions are committed, the labels in this PR are good to go from my end. Thanks!

@sokosaurus Reviewed the labels and added changes based on my final conversation with the UI text team. Once those suggestions are committed, the labels in this PR are good to go from my end. Thanks!

Thanks for all the support here @melissabarber! I've pushed in your latest label updated but please let me know if anything looks off.

Thanks for all the support here @melissabarber! I've pushed in your latest label updated but please let me know if anything looks off.

Updated labels look good!


Problem with url(...) with multiple matched routes

Do you want to request a feature or report a bug?
bug
What is the current behavior?
Assume we have the following controller:
bash-5.0# cat app/controllers/test.rb
Test::App.controllers :test do

  get :foo, with: [:one, :two] do
    "world"
  end

  get :foo, with: :one do
    "hello"
  end

end

Test::App.url(:test, :foo, one: "one") shall match the second route with: :one, not the first with: [:one, :two]. However, the first one is actually taken and thus raises an error like below:
bash-5.0# bundle exec padrino c
=> Loading development console (Padrino v.0.14.4)
=> Loading Application Test::App
irb(main):001:0> Test::App.url(:test, :foo, one: "one")
Traceback (most recent call last):
       16: from /usr/local/bundle/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
       15: from /usr/local/bundle/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
       14: from /usr/local/bundle/gems/padrino-core-0.14.4/lib/padrino-core/cli/base.rb:43:in `console'
       13: from (irb):1
       12: from /usr/local/bundle/gems/padrino-core-0.14.4/lib/padrino-core/application/routing.rb:343:in `url'
       11: from /usr/local/bundle/gems/padrino-core-0.14.4/lib/padrino-core/application/routing.rb:432:in `make_path_with_params'
       10: from /usr/local/bundle/gems/padrino-core-0.14.4/lib/padrino-core/path_router.rb:70:in `path'
        9: from /usr/local/bundle/gems/padrino-core-0.14.4/lib/padrino-core/path_router/matcher.rb:44:in `expand'
        8: from /usr/local/bundle/gems/mustermann-1.1.0/lib/mustermann/ast/pattern.rb:108:in `expand'
        7: from /usr/local/bundle/gems/mustermann-1.1.0/lib/mustermann/expander.rb:152:in `expand'
        6: from /usr/local/bundle/gems/mustermann-1.1.0/lib/mustermann/expander.rb:182:in `with_rest'
        5: from /usr/local/bundle/gems/mustermann-1.1.0/lib/mustermann/expander.rb:150:in `expand'
        4: from /usr/local/bundle/gems/mustermann-1.1.0/lib/mustermann/ast/expander.rb:97:in `expand'
        3: from /usr/local/bundle/gems/mustermann-1.1.0/lib/mustermann/ast/expander.rb:97:in `fetch'
        2: from /usr/local/bundle/gems/mustermann-1.1.0/lib/mustermann/ast/expander.rb:97:in `block in expand'
        1: from /usr/local/bundle/gems/mustermann-1.1.0/lib/mustermann/ast/expander.rb:120:in `error_for'
Mustermann::ExpandError (cannot expand with keys [:one], possible expansions: [:one, :two])

The following patch seems to solve the problem, although I'm not sure it is a perfect solution.
bash-5.0# diff -u padrino-core-0.14.4/lib/padrino-core/path_router.rb.org padrino-core-0.14.4/lib/padrino-core/path_router.rb
--- padrino-core-0.14.4/lib/padrino-core/path_router.rb.org
+++ padrino-core-0.14.4/lib/padrino-core/path_router.rb
@@ -56,7 +56,7 @@
       #
       def path(name, *args)
         params = args.last.is_a?(Hash) ? args.pop : {}
-        candidates = @routes.select { |route| route.name == name }
+        candidates = @routes.select { |route| route.name == name && (route.matcher.names - params.keys.map(&:to_s)).length == 0 }
         fail InvalidRouteException if candidates.empty?
         route = candidates.sort_by! { |candidate|
           (params.keys.map(&:to_s) - candidate.matcher.names).length }.shift

What is the expected behavior?
irb(main):001:0> Test::App.url(:test, :foo, one: "one")
=> "/test/foo/one"

Which versions of Ruby, Padrino, Sinatra, Rack, OS are you using? Did this work in previous versions?
Ruby on Docker image ruby:2.6-alpine with Padrino 0.14.4

It seems that the problem is caused with ruby:2.6-alpine; the problem does not happen with ruby:2.6-slim


Add Research Scientist and Software Developer to people page

Probably add them to the top category of folks (professor + grad students)... but will have to change that header.
Currently, Mikey is not shown as a current lab member because his position is 'Research Scientist.'

Fixed!


Enable mass deletion of files

In the submission pipeline, if you want to select multiple files/folders and delete them at once, this is not possible and only on file/folder gets selected. We need to be able to select more.
screen-capture (3).webm

Closing in favor #211


Crash when accessing location twice

🐛 Bug Report
See BaseflowIT/flutter-geolocator#131
I think it's more related to this plugin then the geolocator plugin.
My stacktrace:
[ERROR:flutter/lib/ui/ui_dart_state.cc(148)] Unhandled Exception: PlatformException(ERROR_ALREADY_REQUESTING_PERMISSIONS, A request for permissions is already running, please wait for it to finish before doing another request (note that you can request multiple permissions at the same time)., null)
    #0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:564:7)
    #1      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:302:33)
    <asynchronous suspension>
    #2      PermissionHandler.requestPermissions (package:permission_handler/src/permission_handler.dart:66:30)
    <asynchronous suspension>
    #3      Geolocator._getLocationPermission (package:geolocator/geolocator.dart:184:16)
    <asynchronous suspension>
    #4      Geolocator.getPositionStream (package:geolocator/geolocator.dart:162:47)
    <asynchronous suspension>
    #5      new RestaurantWidgetState.<anonymous closure> (package:taurant_app/widgets.dart:208:22)
    #6      _rootRunUnary (dart:async/zone.dart:1132:38)
    #7      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
    #8      _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
    #9      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
    #10     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
    #11     Future._complete (dart:async/future_impl.dart:473:7)
    #12     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
    #13     _AsyncAwaitCompleter.complete (dart:async/runtime/libasync_patch.dart:28:18)
    #14     _completeOnAsyncReturn (dart:async/runtime/libasync_patch.dart:294:13)
    #15     Geolocator.isLocationServiceEnabled (package:geolocator/geolocator.dart)
    <asynchronous suspension>
    #16     new RestaurantWidgetState (package:taurant_app/widgets.dart:206:18)
    #17     RestaurantWidget.createState (package:taurant_app/widgets.dart:200:12)
    #18     new StatefulElement (package:flutter/src/widgets/framework.dart:3804:25)
    #19     StatefulWidget.createElement (package:flutter/src/widgets/framework.dart:805:38)
    #20     Element.inflateWidget (package:flutter/src/widgets/framework.dart:2954:40)
    #21     Element.updateChild (package:flutter/src/widgets/framework.dart:2759:12)
    #22     SingleChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:4876:14)
    #23     Element.inflateWidget (package:flutter/src/widgets/framework.dart:2956:14)
    #24     Element.updateChild (package:flutter/src/widgets/framework.dart:2759:12)
    #25     SingleChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:4876:14)
    #26     Element.inflateWidget (package:flutter/src/widgets/framework.dart:2956:14)
    #27     Element.updateChild (package:flutter/src/widgets/framework.dart:2759:12)
    #28     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3747:16)
    #29     Element.rebuild (package:flutter/src/widgets/framework.dart:3559:5)
    #30     ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:3716:5)
    #31     ComponentElement.mount (package:flutter/src/widgets/framework.dart:3711:5)
    #32     Element.inflateWidget (package:flutter/src/widgets/framework.dart:2956:14)
    #33     Element.updateChild (package:flutter/src/widgets/framework.dart:2759:12)
    #34     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3747:16)
    #35     Element.rebuild (package:flutter/src/widgets/framework.dart:3559:5)
    #36     ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:3716:5)
    #37     ComponentElement.mount (package:flutter/src/widgets/framework.dart:3711:5)
    #38     ParentDataElement.mount (package:flutter/src/widgets/framework.dart:4063:11)
    #39     Element.inflateWidget (package:flutter/src/widgets/framework.dart:2956:14)
    #40     Element.updateChild (package:flutter/src/widgets/framework.dart:2759:12)
    #41     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3747:16)
    #42     Element.rebuild (package:flutter/src/widgets/framework.dart:3559:5)
    #43     ComponentElement._firstBuild (package:flutter/src

@SimonIT this can happen when you request permissions multiple times without waiting for the initial result to return. We have seen this happen when developers use the Permission Handler or Geolocator plugin directly from their Widget build(BuildContext context) { ... } method (this method can be called multiple times in rapid succession by the Flutter framework to layout the widget).
The best way around this problem is to request permissions from a method that you are sure is executed only once (e.g. the void initState() { ... } method from a stateful widget). After that you can safely use the Geolocator plugin to get location updates from anywhere in your code.


train dataset

dear,
i want to know what the rgb image of the dataset of train

Yes, where is the RGB image of train.

@yqq924 Sorry for the late reply! I used the raw data from KITTI to train the network, which contains RGB images. I think you can find RGB images in the folder 2011_xx_xx_drive_xxxx_sync\velodyne_raw\image_02 and in 2011_xx_xx_drive_xxxx_sync\velodyne_raw\image_03， if you organize the folder structure as the suggestion in the README file in KITTI devkit.  @zbs881314 @yqq924


Add urchin to shell test frameworks

Uses shell idioms like files and folders for tests to files, which could also be files other than shell scripts, making it a generic testing framework. tlevine did a great presentation on it a while ago that I saw. Haven't used it for anything large scale, but useful for learning at the very least.

Just cloned this. Not sure why there are dupe links, but that's what it's telling me?

The CI failures are unrelated, so don't worry about it.


i think next_frame_task_cb function has some problems in release/v7

in release/v7 next_frame_task_cb function，
i think this code has some problems:
Because I tried a lot of GIFs, its loop_count is zero, but this code does not send LV_EVENT_LEAVE signal when loop_count=0, so that the upper application can stop it, but keeps looping
https://github.com/lvgl/lv_lib_gif/blob/27a74507ee73ae462daf8f4d4c2f65b366fc9cfd/lv_gif.c#L120-L132
I think this code can be modified like this：
https://github.com/lvgl/lv_lib_gif/pull/36/files

in release/v7 next_frame_task_cb function， i think this code has some problems:
Because I tried a lot of GIFs, its loop_count is zero, but this code does not send LV_EVENT_LEAVE signal when loop_count=0, so that the upper application can stop it, but keeps looping
https://github.com/lvgl/lv_lib_gif/blob/27a74507ee73ae462daf8f4d4c2f65b366fc9cfd/lv_gif.c#L120-L132
I think this code can be modified like this： https://github.com/lvgl/lv_lib_gif/pull/36/files

loop_count = 0 means that animation should repeated infinitely. I think the problem is in current version
https://github.com/lvgl/lv_lib_gif/blob/afdc2d69c7e80210256fd84837b839320fe2618a/lv_gif.c#L120-L143
In my example animated gif with loop_count = 0 shows only 1 cycle after that LV_SIGNAL_LEAVE sended wich cause lv_task_set_prio(ext->task, LV_TASK_PRIO_OFF); and animation freezes.

It was just updated in LVGL. Probably it can be applied here too.
See https://github.com/lvgl/lvgl/issues/3883


Crashes on complete-with-snippet when circular use

Hi everybody.
Racer's version: 2.0.3
The code:
pub use self::{crash as crash};

fn main() {
    c
}

Execute complete-with-snippet	4	6.
It crashes:
PREFIX	51	51
thread 'searcher' has overflowed its stack

Maybe dupe of #354

Yes, it is.