No controls/global hotkeys with WHDLoad Amiga ROMs that default to mouse in Amiberry

Amiga ROMs that default to mouse as their primary input method in Amiberry due to the configuration settings in the WHDLoad database result in a complete lack of controller compatibly -- as well as the inability to use global hotkeys to exit back out of the game. The only option is to reset the system.
I’ve determined that the mouse default is the problem since you can solve the hotkey issue by altering the individual game configurations in whdload_db.config (located under opt/amiberry/whdboot/game-data/) (You need to switch PRIMARY_CONTROL from MOUSE to JOYSTICK and PORT0 from MOUSE to JOY.) This does not solve the controller issue - you still can't play the games that require a mouse -- but it does allow you to use the hotkeys to escape the emulator. Presumably, the mouse setting blocks your ability to use the start + select hotkeys to exit since it causes the system to look for input from a non-existent mouse.
As far as I am aware, this means there is no way to play Amiga games whose primary input method is mouse based. So I would please regard this submission as a combined bug report/feature request.
Bug - Mouse-based games deactivate joypad controls and require a hard reset to exit the game when using WHDLoad games in Amiberry.
Feature request - Map an emulated mouse to the left joystick in Amiberry and default to this setting rather than a real mouse, which obviously doesn't exist on a handheld device.
This report is for ArkOS version 1.5 on the RG351P.

What are some example Amiga games that I can use to recreate this issue?

What are some example Amiga games that I can use to recreate this issue?

Barbarian I and II are a good example. Barbarian I defaults to mouse as the primary control, and you encounter the problem with no controls or hotkeys, while Barbarian II defaults to joystick as the primary control, and plays fine.
I also encounter the mouse problem with Black Crypt and Might & Magic II: Gates to Another World. I can test some more later if you need additional examples.
The game files preconfigured with WHDLoad are findable at http://www.whdownload.com/.
Thanks for looking into this!

Barbarian I and II are a good example. Barbarian I defaults to mouse as the primary control, and you encounter the problem with no controls or hotkeys, while Barbarian II defaults to joystick as the primary control, and plays fine.
I also encounter the mouse problem with Black Crypt and Might & Magic II: Gates to Another World. I can test some more later if you need additional examples.
The game files preconfigured with WHDLoad are findable at http://www.whdownload.com/.
Thanks for looking into this!

I haven't been able to find a good global solution for supporting both mouse and joystick.  The best solution I've found so far is to make these port changes on a per game basis and save the configuration for that game so it can load the configuration for that game.  I've added that information to the FAQ under the global events section for Amiberry.  https://github.com/christianhaitian/arkos/wiki/Frequently-Asked-Questions---RG351P#q-what-are-the-global-event-keys-and-emulator-event-keys-in-ArkOS

Thanks for looking into this. However, I think I'm missing something? The new documentation says to hit start + X to enter the Amiberry menu and switch to mouse controls on a per game basis. However, when a game defaults to mouse on launch - due to the instructions in default WHDLoad database file - it bypasses the jot as buttons. That is, you can't use any of the joypad keys - at all. So (as far as I am aware) you can't enter this menu to change the settings as the documentation recommends.

When I tested the games you suggested (Barbarian 1 and Barbarian II), I did not experience this issue.  I was able to get to the Amiberry Menu using the Select+X feature without issue.  So I have not been able to replicate this lack of access to the Amiberry menu that you state.  Were there any changes you made to Amiberry that may have possibly caused this?  If not, can you try imaging another SD card with ArkOS, update it only, and try the games you mention on that and see if the problem persist there are report back your findings?


PyFlow fails to launch

Replace all clock() with time (). This is outdated and doesn't work for me any other way (ImportError: cannot import name 'clock' from 'time' (unknown location)).
After a very compressed window with the interface. You can't do anything, and the console is constantly spamming

Traceback (most recent call last):
  File "C:\Users\Александр\AppData\Local\Programs\Python\Python39\lib\site-packages\PyFlow\App.py", line 425, in mainLoop
    deltaTime = time() - self._lastClock
TypeError: 'module' object is not callable

@AlexRMU check #79. Fixed it already

I have the latest version of the app and Python :/

And I have this error. Where is it fixed?

And I have this error. Where is it fixed?

Dear sir, do you solve this issue？@AlexRMU

Bit late but since the error still is happening : from what I gathered the time.clock() error is still happening when installing the "latest release" from the release branch. I guess the fix has been done only on the "latest development" from the master branch.
Install pyflow from the latest dev version (from pyflow doc) to fix the problem (but others exist for me...)
pip install git+https://github.com/wonderworks-software/PyFlow.git@master

Latest development version
Traceback (most recent call last):
  File "C:\Python310\Scripts\pyflow-script.py", line 33, in <module>
    sys.exit(load_entry_point('PyFlow==2.0.1', 'console_scripts', 'pyflow')())
  File "C:\Python310\Scripts\pyflow-script.py", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "C:\Python310\lib\importlib\metadata\__init__.py", line 171, in load
    module = import_module(match.group('module'))
  File "C:\Python310\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "C:\Python310\lib\site-packages\PyFlow\Scripts\__init__.py", line 23, in <module>
    from PyFlow.App import PyFlow
  File "C:\Python310\lib\site-packages\PyFlow\App.py", line 23, in <module>
    from time import clock
ImportError: cannot import name 'clock' from 'time' (unknown location)

Latest development version
Traceback (most recent call last):
  File "C:\Python310\Scripts\pyflow-script.py", line 33, in <module>
    sys.exit(load_entry_point('PyFlow==2.0.1', 'console_scripts', 'pyflow')())
  File "C:\Python310\Scripts\pyflow-script.py", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "C:\Python310\lib\importlib\metadata\__init__.py", line 171, in load
    module = import_module(match.group('module'))
  File "C:\Python310\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "C:\Python310\lib\site-packages\PyFlow\Scripts\__init__.py", line 23, in <module>
    from PyFlow.App import PyFlow
  File "C:\Python310\lib\site-packages\PyFlow\App.py", line 23, in <module>
    from time import clock
ImportError: cannot import name 'clock' from 'time' (unknown location)

I still have this error in 2022 in both version,
pip install passlib==1.7.3
i try to install passlib 1.7.3 but nothing happen!

This should be fixed in master branch with python 3 and pyside6


Integrate CLI and Winternitz Commit Logic to Client based on #131

I updated pull request #131 to the main branch's changes to the Wintenitz library.

@lucidLuckylee , you can close this and merge https://github.com/BitVM/BitVM/pull/138/files instead.


Explore: Consolidate CFApp and CFProcess Custom Resources

Context / Background
Some folks have expressed concerns about the large number of custom resources involved in this spike, so we've been thinking of ways in which we can consolidate/remove them without too much impact to the design/functionality of the CF API Shim.
One opportunity might be to cut scope and eliminate support for multi-process Apps so that we can have a single CR that represents both the App and the Process.
💡 NOTE💡
There is precedence for this in CF. Historically there was no distinction between Apps and Processes. The web Process was the App. When Apps and Processes were split apart, the web Process and App shared the same identifier (GUID) to maintain backwards compatibility. This allowed the granular v3 endpoints to care about Processes without having to teach the v2 endpoints that Processes and Apps were discrete resources. In other words, curling the /v2/apps/:guid and /v3/processes/:guid actually fetched the same object from the database!
Desired outcomes
Explore how feasible it would be to consolidate the CFApp and CFProcess custom resources into a single resource. Implement it as a branch of this spike repo and write a Proposal document to explain your findings and propose a course of action.
Questions to consider:

How do we implement the granular Process v3 endpoints if there is no dedicated Process resource?

We never implemented the GET endpoints for Processes on the spike. We may need to implement it for this exploration.

Is our assumption that users are not using multi-process Apps valid?

Most likely, but we should write down why we think this is the case.

What are the benefits of consolidating these resources?
What are the downsides?

How difficult would it be for us to support multi-process Apps in the future?

Acceptance Criteria / Scenarios
By the end of this explore we should have:

Example CR representing both Apps/Processes
Workable spike code demonstrating what this looks like.
A Proposal document recommending a next course of action.

Notes
Add any additional notes
[Timeboxed to 3 days, check in after 2 days with the current status]

After spiking this out, combining these two CRs is very feasible as long as we commit to only supporting single-process Apps.
@gnovv and I wrote up a proposal doc that goes into more detail:
https://docs.google.com/document/d/1O6bBAAT4bx_0h5DzNrkxe4sctPVx_JsIjBeRvwT83nk/edit#


Rename clients.getAll()

…since it has filtering options that filter by default.
@annevk suggested .get(), but does that suggest a singular return?
Could be .matchAll() like the caches.

.get() sounds more like getting a singular result.
.getAll(options) still LGTM as it suggests "get all the clients which meet the options which are happen to be controlled window for convenience."
But in case people still think it's not natural, .matchAll() seems fine to me too.

Proactively filed crbug.com/451334 for Blink, pending a decision.

@annevk still unhappy with getAll? Other suggestions are matchAll, queryAll.

I don't see how All makes sense given that it doesn't return all of them by default. Also, none of those names signifies that you are getting back copies rather than references.

How about just filter or match?

@mvano: would we need to pun filter with Array.prototype.filter?
I'll go with whatever this group likes, but @mvano's match and .matchAll() as previously suggested sound good to me. They're at least internally consistent with the identity semantics that @annevk is worried about.

would we need to pun filter with Array.prototype.filter?

Not sure what pun means in this context, but I recognize the potential confusion of having a method with the same name but different functionality on different classes. The same issue exists with String.prototype.match. I don't find this a major issue though. In an object oriented design you have natural namespacing and no real conflict.

Since we're bikeshedding... how about getClients() ?

Lets go with matchAll. Matches caches.matchAll which has a similar arg with filtering rules.

Tracked in gecko here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1130685

Commit a CL here:
https://codereview.chromium.org/892053003/


Encrypt secrets in DB

A good practice is to encrypt or hash secret keys in DB. I would suggest to implement this. (Enhancement)
While for one-off keys one way hash functions such as scrypt/bcrypt are available, that's not the option for TOTP where the actual key value is needed. Simple encryption where the encryption key is not stored in DB suffice.
Encryption of secret keys is recommended by RFC 6238.

The relevant part in the specification is the following:

We also RECOMMEND storing the keys securely in the validation system,
and, more specifically, encrypting them using tamper-resistant
hardware encryption and exposing them only when required: for
example, the key is decrypted when needed to verify an OTP value, and
re-encrypted immediately to limit exposure in the RAM to a short
period of time.

The key store MUST be in a secure area, to avoid, as much as
possible, direct attack on the validation system and secrets
database.  Particularly, access to the key material should be limited
to programs and processes required by the validation system only.

Hardware encryption cannot be enforced by this package, but the encryption could be implemented.

A possible package to perform the encryption would be: https://github.com/pyca/cryptography.

Another possible package: https://github.com/defrex/django-encrypted-fields

I've looked into this and the issue is that this package only stores the PhoneDevice, but not the other Devices, most notably the TOTPDevice. So while we could encrypt some of the fields, we still wouldn't cover all situations.

Perhaps a more thorough solution would involve django_otp  adopting database encryption in a way that this package could inherit?

Incidentally, I should probably take back my recommendation of django-encrypted-fields: it's not Python 3 compatible: defrex/django-encrypted-keys#27


Add version: ransome1.sleek version 1.0.8

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.1 schema?

Microsoft Reviewers: Open in CodeFlow

@wingetbot run


Update for Xcode 10

This is a minimal update for Xcode10.
Background
[[Int]!] will be treated as [[Int]?], so the codes in QRCodeModel.swift will not pass the building for WatchOS.
Solution
The easiest way to do this is to add ! to everywhere that needed.
But I think there is no need to use [[Int]?] here because of the logic of implementation.
So I chose to rewrite those codes to solve this issue instead of adding !.
Just for your reference
The new codes are not easy since I don't save any intermediate value.
The reason I did this is that I don't know how to name those value.
And This is the first time I open a pull request.
So if there is any inappropriate behavior, please tell me.
我用英语知识是为了练习英语，如果因此引起什么不便，请见谅。

Thanks for your work!


Build failed on Xcode 15 Beta 1

May be just a bug, the follow-up will continue to pay attention to.
Build failed:
Command SwiftCompile failed with a nonzero exit code.

Env:

Xcode 15 Beta 1
macOS 14.0 Beta 1 or macOS 13.3.1

Appreciate the feedback here, its good for me to have this on my radar (my attention is not in any Apple beta this year sadly).
This kinda looks like a bunch of buggy Xcode garbage to me.....but I certainly will be watching closely through the summer to ensure this isn't anything I need to take action in.
SwiftSlash needs some work to support Swift 6, but I believe that is next years development....

Fix in Xcode 15 beta 3 (15A5195k).


Hide non-defined functions

Hide for production

Withdraw project
Deny project
Custom query

Features in development or down the roadmap should not be displayed in production for release.
Previous issue: https://github.com/pulibrary/aux/issues/8
Acceptance Critieria:

[ ] Remove Withdraw project button
[ ] Remove Deny project button
[ ] Remove Custom query button

Hey team! Please add your planning poker estimate with Zenhub @bess @hectorcorrea @JaymeeH @kelynch @leefaisonr @jrgriffiniii


vue2.6 node8.15.0 get wrong when build

Before you start, please make sure to:

[X] Read the document
[X] Have tried the latest version
[X] Search to see if your issue already exists
[X] Make reasonable efforts to troubleshoot and rule out issues with your own code or any 3rd party library
[X] Look for / ask questions through appropriate channels like Stack Overflow

Link to minimal (but complete) reproduction
None
Steps to reproduce

node 8.15.0
npm run build
What is expected?
build success
What is actually happening?

System Info
node 8.15.0
"dependencies": {
    "@v-charts2/histogram": "^1.0.1",
    "@v-charts2/line": "^1.0.1",
    "@vue/composition-api": "^1.7.2",
    "axios": "0.17.1",
    "core-js": "^3.6.5",
    "dayjs": "1.8.17",
    "element-ui": "git+ssh://git@gitlab.mobvista.com:frontend/element-ui.git#v2.15.4-1.4.30",
    "js-cookie": "2.2.0",
    "json-editor-vue": "^0.12.0",
    "lodash": "^4.17.15",
    "normalize.css": "7.0.0",
    "nprogress": "0.2.0",
    "qs": "6.9.0",
    "v-code-diff": "^0.3.12",
    "vue": "^2.6.11",
    "vue-i18n": "^8.26.8",
    "vue-json-editor": "^1.4.3",
    "vue-router": "^3.2.0",
    "vuex": "^3.4.0"
  }

Package Manager
npm
Any additional comments?
No response

Actually, I'm very clear about where the issue lies in your code. But why did you enter "None" in a required field? Also, all the code you posted is in screenshots instead of using markdown, making it very inconvenient for me to copy your code.

Unsupported programming syntax ?? ，config your webpack to compile it successfully，if vue/cli is used，see project markdown file


Is there a compressed js file?

Hello @javisantana ,
I am the member of the cdnjs project.
We want to host this library.
But there is a problem I want to ask.
Is there a "cartodb.compressed.js" or a "cartodb.js" in npm package?
Because I just saw a "cartodb.uncompressed.js".
Thanks for your help.
https://github.com/cdnjs/cdnjs/issues/6746
https://github.com/cdnjs/cdnjs/pull/7812

+1

Hello, any info?

+1

It's available through NPM and through Carto's CDN:

<EMAIL_ADDRESS>https://cartodb-libs.global.ssl.fastly.net/carto.js/v4.0.9/carto.min.js


webpack plugin architecture does not guarantee a plugin will be able to require components from the same version of webpack

What is the current behavior?
If a project and one of its npm dependencies, let's call it nifty-cms, each depend on two different versions of webpack, i.e. 5 (project level) and 4 (nifty-cms), then npm and yarn will both do the reasonable thing and install webpack twice, with node_modules/nifty-cms/node_nodules containing webpack 4 and node_modules/webpack containing webpack 5. So far so good.
However, if nifty-cms also depends on a plugin — let's say it's vue-loader — and the project does not, then vue-loader will be installed as node_modules/vue-loader. Again, so far so good. Hoisting is normal.
But here's where we get in trouble: unfortunately, when webpack 4 in nifty-cms loads vue-loader, vue-loader then tries to require various files back from webpack itself, for instance:
const BasicEffectRulePlugin = require('webpack/lib/rules/BasicEffectRulePlugin')

At this point, npm (or yarn) sees that vue-loader was loaded from node_modules/vue-loader and loads node_modules/webpack.
But, this is not the version of webpack that instantiated the loader. So the user gets the following error indicating the discrepancy:
The 'compilation' argument must be an instance of Compilation

After puzzling over this for a while I can see two possible resolutions:

All webpack plugin releases could have a peerDependency specifying only one major webpack version, even if they are actually compatible with more than one with no code changes. (vue-loader is compatible with webpack 3, 4, and 5 all at the same time.) This might help, depending on whether npm/yarn actually pay attention to peer dependencies with regard to hosting. And it doesn't require an API change in webpack. But, it requires a lot of redundant publication of modules. And the need for it would be easy to miss.

webpack could provide a webpackRequire function on the compiler object passed to plugins which invokes require from webpack. I think this is the better solution. Unfortunately for this solution to really solve the problem it would need to be universally used. It would be difficult to stomp out the practice of requiring webpack/something when it works any time a project has only one version of webpack in it.

If the current behavior is a bug, please provide the steps to reproduce.
Please see the scenario above.
What is the expected behavior?
Projects and their dependent modules should be able to depend on and use different major versions of webpack independently without encountering the following error or its underlying cause:
The 'compilation' argument must be an instance of Compilation

Specifically, webpack plugins should be able to reliably require additional resources from the same webpack version that instantiated them.
Workaround:
A module in the position of nifty-cms can set webpack as a peer dependency instead, and support more than one version of webpack. However work must still immediately be done every time a new version of webpack comes out, and this could become untenable if other webpack plugin dependencies of nifty-cms only work with a single version of webpack in a given release. A further workaround, then, is for nifty-cms to publish nifty-cms-webpack-4-something-loader, nifty-cms-webpack-5-something-loader, etc. which each just require and export a specific version of something-loader. That's a lot of npm packages.
Other relevant information:
webpack version:  4 and 5
Node.js version: any
Operating System: N/A
This issue has been seen in the wild in various projects.

Yes I'm aware of this problem. Since webpack 5 the Compiler object has a webpack property, which contains the webpack exports of the current version running. So plugins no longer need to require("webpack") or have a webpack dependency at all (a peerDependency might be still a good idea to communicate which webpack version is supported).
Webpack 4 doesn't support it, but you can do const webpack = compiler.webpack || require("webpack") for that case.
class MyPlugin {
  apply(compiler) {
    const webpack = compiler.webpack || require("webpack");
    compiler.hooks.compilation.tap("MyPlugin", compilation => {
      // The following like will fail with a wrong webpack version.
      webpack.javascript.JavascriptModulesPlugin.getCompilationHooks(compilation);
    });
  }
}

But accessing private modules like require('webpack/lib/rules/BasicEffectRulePlugin') is not possible this way, but accessing private modules isn't supported anyway.

Hmm, so this almost sounds like a perfect resolution, until that last line
(:
Is vue-loader doing something wrong — should it gain access to
BasicEffectRulePlugin and its numerous friends some other way?
On Fri, Feb 5, 2021 at 3:55 PM Tobias Koppers<EMAIL_ADDRESS>wrote:

Yes I'm aware of this problem. Since webpack 5 the Compiler object has a
webpack property, which contains the webpack exports of the current
version running. So plugins no longer need to require("webpack") or have
a webpack dependency at all (a peerDependency might be still a good idea to
communicate which webpack version is supported).
Webpack 4 doesn't support it, but you can do const webpack =
compiler.webpack || require("webpack") for that case.
class MyPlugin {
apply(compiler) {
const webpack = compiler.webpack || require("webpack");
compiler.hooks.compilation.tap("MyPlugin", compilation => {
// The following like will fail with a wrong webpack version.
webpack.javascript.JavascriptModulesPlugin.getCompilationHooks(compilation);
});
}}
But accessing private modules like
require('webpack/lib/rules/BasicEffectRulePlugin') is not possible this
way, but accessing private modules isn't supported anyway.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/webpack/webpack/issues/12606#issuecomment-774283510,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27NLBA4ZE3UFANTWD6TS5RLKRANCNFSM4XFMOS2Q
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

Actually it should not use that at all. Afaik it tries to copy the rules for CSS, JS, etc for their blocks, but webpack has a better mechnism to run a file as if it is a .css, .js, .ts file: !=!
Example: for a my-file.vue file with
<style>
...
</style>

<script>
...
</script>

the vue-loader can generate code like that:
import "./my-file.vue.css!=!vue-loader/get-block?range=1-3!./my-file.vue";
import "./my-file.vue.js!=!vue-loader/get-block?range=4-6!./my-file.vue";

Where vue-loader/get-block is a loader that extract the content of a block from a range.
The inline syntax ./my-file.vue.css!=! will treat the result of vue-loader/get-block?range=1-3!./my-file.vue as if it was written in ./my-file.vue.css and apply the .css rules to it.

Interesting. So I guess the next question is how common it is for loaders
and plugins in heavy use to follow these antipatterns.
On Fri, Feb 5, 2021 at 4:46 PM Tobias Koppers<EMAIL_ADDRESS>wrote:

Actually it should not use that at all. Afaik it tries to copy the rules
for CSS, JS, etc for their blocks, but webpack has a better mechnism to run
a file as if it is a .css, .js, .ts file: !=!
Example: for a my-file.vue file with

the vue-loader can generate code like that:
import "./my-file.vue.css!=!vue-loader/get-block?range=1-3!./my-file.vue";import "./my-file.vue.js!=!vue-loader/get-block?range=4-6!./my-file.vue";
Where vue-loader/get-block is a loader that extract the content of a
block from a range.
The inline syntax ./my-file.vue.css!=! will treat the result of
vue-loader/get-block?range=1-3!./my-file.vue as if it was written in
./my-file.vue.css and apply the .css rules to it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/webpack/webpack/issues/12606#issuecomment-774305660,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27NTND4BD2ESCUH7IZDS5RRLBANCNFSM4XFMOS2Q
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

So I guess the next question is how common it is for loaders and plugins in heavy use to follow these antipatterns.

When you need it :smile: Why do you think it is antipatterns?

When I used the term "antipatterns," I was referring to the importing of
private modules, which Tobias indicated is not appropriate. If that is
common in loaders, then it could be a long road to realistically make this
work in most applications, but if it's just vue-loader that's a
different story.
On Sat, Feb 6, 2021 at 6:44 AM Alexander Akait<EMAIL_ADDRESS>wrote:

So I guess the next question is how common it is for loaders and plugins
in heavy use to follow these antipatterns.
When you need it 😄 Why do you think it is antipatterns?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/webpack/webpack/issues/12606#issuecomment-774459865,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27PYXNSTF6HBINGA7TLS5UTS3ANCNFSM4XFMOS2Q
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

I surveyed the following loaders and plugins with a pretty basic grep
search:
case-sensitive-paths-webpack-plugin
corejs-upgrade-webpack-plugin
fork-ts-checker-webpack-plugin
html-webpack-plugin
mini-css-extract-plugin
pnp-webpack-plugin
stylelint-webpack-plugin
terser-webpack-plugin
babel-loader
css-loader
eslint-loader
file-loader
postcss-loader
raw-loader
sass-loader
sass-resources-loader
style-loader
url-loader
vue-loader
vue-style-loader
Of these, the only offenders that required private modules from webpack
were vue-loader and html-webpack-plugin. html-webpack-plugin seems pretty
official. I don't know webpack internals enough to know if it needs to be
doing what it's doing.
On Sun, Feb 7, 2021 at 4:22 PM Tom Boutell<EMAIL_ADDRESS>wrote:

When I used the term "antipatterns," I was referring to the importing of
private modules, which Tobias indicated is not appropriate. If that is
common in loaders, then it could be a long road to realistically make this
work in most applications, but if it's just vue-loader that's a
different story.
On Sat, Feb 6, 2021 at 6:44 AM Alexander Akait<EMAIL_ADDRESS>wrote:

So I guess the next question is how common it is for loaders and plugins
in heavy use to follow these antipatterns.
When you need it 😄 Why do you think it is antipatterns?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/webpack/webpack/issues/12606#issuecomment-774459865,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27PYXNSTF6HBINGA7TLS5UTS3ANCNFSM4XFMOS2Q
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

@boutell You need open issues in them repos, we can't fix it here, our recommend solution - using compiler.webpack (compiler.webpack can be used in loaders and plugins without problems), feel free to feedback

OK thanks. I'll take it to vue-loader. I think html-webpack-plugin does not
really have this problem because their peer dependency only matches one
major release of webpack.
On Mon, Feb 8, 2021 at 5:02 AM Alexander Akait<EMAIL_ADDRESS>wrote:

Closed #12606 https://github.com/webpack/webpack/issues/12606.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/webpack/webpack/issues/12606#event-4302470042, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27LHGYJE724BIANNLRTS56ZDBANCNFSM4XFMOS2Q
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his


ccls: use llvmPackages_latest

Motivation for this change
ccls should use llvmPackages_latest to always support the latest C/C++ language features.
Also, ccls doesn't require clang to build, so we should use the default stdenv.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@mic92 @tobim

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

1 package built:

ccls

@SuperSandro2000 can we get a macOS build here?

Result of nixpkgs-review pr 113154 run on x86_64-darwin 1

1 package built:

ccls


support high-precision timestamps

Direct access to the second + nanosecond parts of the time stamps are going to available from pyepics
https://github.com/pyepics/pyepics/pull/71
We should think about how we want to propagate this up through ophyd / bluesky.
A plausible way to cope with this is to add a 'timestamp_format' do the descriptors and let objects return their times as either a float (which drops precision) or as a (int[s], int[ns]) tuple which has more precision than we know what to do with.
Adding a 'hiprec_timestamp' (optional ?!) dictionary to event documents is also an option.

I think I prefer a new optional key in the events to a flexible data structure inside timestamps. Adding a specific optional key to events isn't too scary, so long as we don't make the schema dynamic.


build repo and explore the code

once you've taken a look at the docs, build the project locally and start looking over the code

Built using docker - made comments on the instructions, improved the readme.


Overlays: Avoid using IEyeManager whenever possible

About the PR
See also: #5705

Conflicts

how the hell


[feature-request] Add node-postgres support

It would be great to have support for some more traditional DBMS ...  maybe on a separate branch for each DBMS?
In this ticket I'd like to have postgres supported, using this great npm module:
https://node-postgres.com/
Typings dbd.
Great work by the way.

I don't think that adding multiple DBMS systems in various branches is a very maintainable strategy. You would probably need to maintain that on your own, or fork it.

How about a new branch where Loopback is used, so you could use whatever DBMS you felt like using?

Would probably be a bit more OSS friendly to add something like knex.js/bookshelf.

(not the LB isn't, I just don't think you want to tie users to a platform for a starter repo).

I like the fact that this is just a starter repo, agnostic with respect to what people want to create from it. Myself, I've used it to start a few projects. Some used PostgreSQL with TypeORM and one used MongoDB (without Mongoose). But I wouldn't want that added in, because that wouldn't be fair to other people who might want to go in a different direction.
The starter repo being agnostic helps people see a clearer path to what they want to create instead of having to think about what surgery to perform on it to remove what they don't want. (at least that's my opinion, I'd love to hear others too)


Added dtype to images.map

fixes #284
Only adds the functionality for images object not for series.

Added dtype to series as well.
Something to consider in series.map()
There is currently no way to pass a shape of the resulting index without passing an index. It is an edge case, and I don't know if you want this to be implimented.
@freeman-lab What do you think?

@boazmohar this is looking great. Any chance you could add the same functionality to Blocks.map + a corresponding test? If we can get that in, then I'd be happy to merge this in.

Sure I will do it later today.
Thanks,
Boaz On Mon, May 09, 2016 at 1:09 PM, Jason Wittenbach <<EMAIL_ADDRESS><EMAIL_ADDRESS>> wrote:
@boazmohar [https://github.com/boazmohar] this is looking great. Any chance you could add the same functionality to Blocks.map + a corresponding test? If we can get that in, then I'd be happy to merge this in.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub [https://github.com/thunder-project/thunder/pull/285#issuecomment-217926240]

@jwittenbach looking over the blocks.py code, there is a dtype passed there:
blocks.py@map()
I haven't seen a test for it, do you want me to add one?

@boazmohar ah, I should have looked more closely. Yeah, if you want to add a test, that would be perfect!

@jwittenbach Done, could you please have a look, I want Aaron to use this fix as well.
Thanks!

@boazmohar awesome. Looks like there are some merge conflicts. This is probably because some other changes have been made in the meantime. If you do a git pull upstream from this branch on your local machine, then you it will try to grab those changes. Any files where those changes clash with yours will show up when you do git status. Inside those files it will show you the conflict, and you just need to manually resolve it. Then do another comit and push.

@jwittenbach sorry about the mess, should work now.

Looks good to me. Thanks @boazmohar!


Minor issue on switch

I have a group of 3 devices that stopped working. I can turn them on with the "Alexa All Bar Lights On" command, but with "Alexa All Bar Lights Off" she says "All Bar Lights doesn't support that." Strange. I can individually turn them all off.
Tried deleting the devices both from Node-Red and within your registration page, then asking Alexa to discover devices. Then reinstalled everything and Alexa discovered the command. But same problem... can never turn them off, just on. Ideas?

Not really.
My only question would be have you marked the devices as "SWITCH" or "LIGHT" at the bottom of the device editing dialog? Given that the name is "All Bar Lights" I wonder if the Amazon matching is getting confused

Duh! I didn't tick the "Off" option during registration with your site. As a side note... it doesn't seem to make any difference whether I select Switch or Light in the device editing dialog. It works even when nothing is ticked. That total section seems to be undocumented.


Level detection incorrect for named function expressions

function foo() {
	var y = 3;
	var w = function baz(){
		var p = 2;
	};
}

In that code, the identifier baz should be in the same scope as var p (aka, level 2), since identifiers of named function expressions are always in their own function's scope (and read-only), not in the containing scope.
However, I tried this on the demo page (http://mazurov.github.io/eslevels-demo/) and it's incorrectly identifying it in the outer scope (level 1), the same as var y.

The names of NFEs are in an intermediate scope, not the scope of their bodies.
top-level -> foo body/params -> special scope for just the baz name -> baz body/params

@michaelficarra OK, that is technically true by spec.
But while you can construct obscure scenarios where the differences in those scopes matter, in the vast majority of cases, I believe baz would be interpreted by readers/authors of code as "in the scope of itself (its own function)". I can't really imagine practical scenarios where es-levels would need to represent an intermediate scope, especially since there's literally only one identifier in that scope.

Importantly, it's most definitely not in the outer scope, and suggesting that it is -- as es-levels does right now -- is very much misleading/incorrect.

it's implementation specific. In the latest Firefox the last example x(1) returns "undefined":

By specification, the eslevels displays it right.
Eslevels is a client of escope library which determines variables scopes.

@getify It is important to understand this distinction when analysing your second example (copied/simplified below)
var a = function baz() { var baz; return baz; };
a();

If these variables were both declared in the same scope, the function would return itself. But instead, the variable declared in the body shadows the one in the function name scope. The distinction is important to average users.

@michaelficarra I don't run across people doing that kind of shadowing very often, but that's also because most people rarely use named function expressions (even though I'm always preaching that they should!).
I'm not saying the information/distinction is unimportant, just that most of the time that extra level (and different color) would probably be irrelevant.
Maybe a compromise would be that es-levels would identify (and colorize) it as belonging to the inner scope UNLESS it's shadowed, in which case it gets a different color to make it clear in those cases?

@getify Telling a partial story about the scope might be confusing, as users might be surprised that changing variable names makes scopes appear/disappear.

I would like to re-emphasize a point I made earlier in this thread:

Importantly, it's most definitely not in the outer scope, and suggesting that it is -- as es-levels does right now -- is very much misleading/incorrect.

That may be lost in the weeds here with the esoteric discussion of whether there needs to be a color for the intermediate scope. I still disagree with @michaelficarra on that, but there should be no question that the current behavior -- implying it's part of the enclosing scope -- is most definitely wrong, and should be fixed.
I don't want the intermediate color, and I think that will confuse more users, but it would still be better than what it does now, which is flatly inaccurate.


[MCOMPILER-395] Allow dependency exclusions for 'annotationProcessorPaths'

this should be quite straightforward to review, since the plugin only needs to "push" the exclusions down to the maven-resolver and all the "magic" happens there

Following this checklist to help us incorporate your
contribution quickly and easily:

[x] Make sure there is a JIRA issue filed
for the change (usually before you start working on it).  Trivial changes like typos do not
require a JIRA issue.  Your pull request should address just this issue, without
pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [MCOMPILER-XXX] - Fixes bug in ApproximateQuantiles,
where you replace MCOMPILER-XXX with the appropriate JIRA issue. Best practice
is to use the JIRA issue title in the pull request title and in the first line of the
commit message.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean verify to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
[x] You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

[x] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

[x] In any other case, please file an Apache Individual Contributor License Agreement.

@slawekjaranowski @cstamas hello again! Would you guys have some time to review this PR?

@slawekjaranowski thansk, Javadoc updated (I hope this is what you meant by documentation). The rendered page now looks like this:

The failed test is MCOMPILER-481-requires-static-included, which seems to a known issue. The same test fails also on master with Maven 3.9.0. It is possibly related to surefire version 3.0.0.M8 (which is the default in Maven 3.9.0 I believe). Temporary workaround could be to pin down the surefire plugin version to some older one for that specific test case (2.22.2 seems to be working).


postinstall failing

Whenever I try to npm i react-native-interactable it fails with:
><EMAIL_ADDRESS>postinstall C:\Users\x1\Documents\GitHub\trustedplatform_android\node_modules\react-native-interactable
> ln -sf lib/{ios,android} .

'ln' is not recognized as an internal or external command,
operable program or batch file.

May you please help me?

I was on Widows so needed C:\Program Files\Git\usr\bin in PATH.


Correct a typo in the message for Spacing.yml

This PR corrects a typo in the Spacing.yml
This is my first itsy-bitsy PR for VaRH repo. Please let me know if I missed something. Thanks!

LGTM


Add PIN/Fingerprint Check to Device Info

@7ynk3r opened https://github.com/rebeccahughes/react-native-device-info/issues/153 a few days ago.  This is the pull request to go along with that.
@passabilities @rebeccahughes @GantMan

very nice!  @kacynMedallia - do you have a second to answer a few questions regarding this?
Can you tweet me?  @gantlaborde ?

@GantMan Done!

@GantMan Fixed the iOS code and README

LGTM! 👍

@GantMan we found that isPinOrFingerprintSet value might change while the app is running. If that it's the case, beacuse the values are exported as constants, the only way to reload the values is to re-open the application.
Any advice on how to deal with this problem? Maybe export the function with a differnt method name so it doesn't overlap with the contants? Remove it from the contant list?
Thanks!
JM

So the best thing we can do is emit events.   So if it changes and our native code can fire, we can emit an event, and so apps that really care about catching this information when it's fresh, can then subscribe for those events and update accordingly in their own state.
I'd be willing to have something like that in here if you're interested.  But I'm unfamiliar with the specific event you're looking for.  Examples of emitting events are easy to come by.

@GantMan Thanks for getting back to us.  I think it's a simpler solution to use callbacks in this case, so apps using this don't have to set up listeners.  I tested this method and it seems to work well.
Please see my PR here for the fix using callback functions: https://github.com/rebeccahughes/react-native-device-info/pull/157
Let us know what you think!
cc @7ynk3r


Error connecting to server when verifying CNAME

Describe the bug
CNAME Record on self-hosted OneUptime cannot be verified. Connection to server not possible.
To Reproduce
Steps to reproduce the behavior:
Go to Project Setting add Custom Domain and TXT Record on DNS Server to verify the domain
Go to Status Page >> Custom Domain  --> create status page domain and verify CNAME
Expected behavior
CNAME should be verified.
Screenshots

Deployment Type
self hosted (7.0.3018)
Additional context
DNS settings seem to be correct. Resolution within the docker container is possible.
Which server is ment in the error message?

In the Container logs I get the following error:
BadDataException [Error]: Cname is not valid for domain status1.teccle.cloud
at fn (/usr/src/Common/Server/Utils/Greenlock/Greenlock.ts:215:19)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Function.orderCert (/usr/src/Common/Server/Utils/Greenlock/Greenlock.ts:171:12)
at async fn (/usr/src/Common/Server/Services/StatusPageDomainService.ts:132:11)
at async fn (/usr/src/Common/Server/Services/StatusPageDomainService.ts:437:15)
at async fn (/usr/src/app/FeatureSet/Workers/Jobs/StatusPageCerts/StatusPageCerts.ts:55:11)
at async /usr/src/app/FeatureSet/Workers/Jobs/StatusPageCerts/StatusPageCerts.ts:42:12
at async Function.runJobWithTimeout (/usr/src/Common/Server/Infrastructure/QueueWorker.ts:49:12)
at async Worker.QueueWorker_1.default.getWorker.concurrency [as processFn] (/usr/src/app/FeatureSet/Workers/Index.ts:107:13)
at async Worker.processJob (/usr/src/Common/node_modules/bullmq/src/classes/worker.ts:792:22)
at async Worker.retryIfFailed (/usr/src/Common/node_modules/bullmq/src/classes/worker.ts:998:16) {
_code: 400
}


CORE-17437: State Manager Configuration Section

Promote State Manager configuration to its own section and remove it
from under the Messaging configuration.

Related api change: https://github.com/corda/corda-api/pull/1277


Update notify-github to not send imdsv1 calls

What does this PR do?
This updates how we use pr-commenter to avoid making IMDSv1 calls, the invoke function doesn't produce any call (this job has no metrics within this).
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


lsp.log file gets filled up with line feed characters

Actual behaviour
The log file generated by nvim's built-in LSP implementation gets filled up with line feed characters and no other contents in it.
$ wc -l ~/.cache/nvim/lsp.log
      21 /Users/gian/.cache/nvim/lsp.log

$ hexdump -C ~/.cache/nvim/lsp.log
00000000  0a 0a 0a 0a 0a 0a 0a 0a  0a 0a 0a 0a 0a 0a 0a 0a  |................|
00000010  0a 0a 0a 0a 0a                                    |.....|
00000015

I also pasted the log file as-is below to show that it's effectively empty.
Expected behaviour
I expect the log file to just stay empty, with no spurious line feed characters if nothing is to be logged.
I don't know if one of the language servers I use is at fault here but I mainly use Go with gopls and Rust with rust-analyzer, in Neovim.
Health check

Checkhealth result
health#lspconfig#check
========================================================================
## Checking language server protocol configuration
  - INFO: rust_analyzer: configuration checked.
  - INFO: gopls: configuration checked.

LSP log (located at ~/.cache/nvim/lsp.log)

Log file

Nvim version

version
NVIM v0.5.0-dev+nightly-16-gb96db38af
Build type: Release
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/clang -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNDEBUG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/tmp/neovim-20210204-13668-10drhzx/build/config -I/tmp/neovim-20210204-13668-10drhzx/src -I/opt/homebrew/include -I/tmp/neovim-20210204-13668-10drhzx/deps-build/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include -I/opt/homebrew/opt/gettext/include -I/tmp/neovim-20210204-13668-10drhzx/build/src/nvim/auto -I/tmp/neovim-20210204-13668-10drhzx/build/include
Compiled by<EMAIL_ADDRESS>
Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/opt/homebrew/Cellar/neovim/HEAD-b96db38/share/nvim"

Run :checkhealth for more info

nvim-lspconfig version: 2eb8567

I have never seen nor noticed this before, but no logging functionality is implemented in this repo, so this bug belongs in core. (I can't transfer your issue, so I'm closing).

Thanks! Reopening it there.


Symlink succeeds when should fail

import pyfakefs.fake_filesystem
import os
fs = pyfakefs.fake_filesystem.FakeFilesystem()
fs.CreateDirectory('/Volumes')
fs.CreateDirectory('/Volumes/ramdisk')
fs.CreateDirectory('/Users/alex/tstl/examples/pyfakefs/testingdir')
os0 = pyfakefs.fake_filesystem.FakeOsModule(fs)
component0 = "gamma"
path0 = "/Volumes/ramdisk/test"
path1 = path0 + "/" + component0
os0.symlink(path0,path1)
os fails the symlink with OSError Errno 17 File exists, while pyfakefs allows it

Uh, I already hate symlink... will check it another day, too tired today.

Sounds good.  Looks like just a missing guard leading to error, at least.
You're running clean on 1 file descriptor + rename with no restrictions other than avoiding apple's bug.

(symlink is off until this is fixed)

Problems with this test case, hold on, fixing it

Ok, just tested the behavior - under Windows it is completely broken (in the given case, it behaves like pyfakefs, in other cases, followlinks makes no difference, or returns incorrect results).
So I will ignore Windows completely here (anyway, symlinks are not used here in reality).
Under Linux, followlinks is ignored for the top directory (which is not obvious from the documentation, at least for me), I will change the implementation accordingly.


Merkle multiproofs

@ralexstokes please what's blocking this PR, I'll like to help finish it up.

I have gone though it and I think what's left is adequate testing, which I will be happy yo work on.

merged into #88


how to change control plane floating IP

Describe the bug
we have a floating IP of a 3 node cluster, we installed Kubernetes (kubeadm)
created/etc/kubernetes/manifests/kube-vip.yaml with vip_address value as floating-ip
kubeadm init --control-plane-endpoint=Floating-IP .........
kubeadm join
kube-vip.yaml manifest same in all nodes.
Cluster working fine, kubectl cluster-info --> shows floating IP.
Now we are in a situation to change Floating-IP to some other value.
How do we achieve this?  could you please guide with Steps?
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS/Distro: [e.g. Ubuntu 1804]
Kubernetes Version: [e.g. v.1.18]
Kube-vip Version: [e.g. 0.2.3]

Kube-vip.yaml:
If Possible add in your kube-vip manifest (please remove anything that is confidential)
Additional context
Add any other context about the problem here.

Edit /etc/kubernetes/manifests/kube-vip.yaml to use the new IP
stop kubelet
kill kubevip pods
start kubelet

kubevip pod should be re-created which should result in kube-vip editing the relevant linux config files setting the new IP.

This is stale, so closing for now.


UTC times for BB ? or just CC ?

Hi thanks for creating this.
I'm not clear after reading the readme, if I have to enter UTC times if I'm running BB, or only if I'm running CC.
Thanks

BB understands  local time; CC does not, it needs UTC.

ok so it needs UTC, even if you are running BB :)

Wrong.
BB needs  local time, NOT UTC.
Please, see README.


Support for the Swift Package Manager

Is support for Xcode 12's "Swift Package Manager" coming?
Thanks

My open PR #71 should fix all existing SPM issues.


Add link to the tutorial modalities

Please, add the link to this new post:
https://acl2020.org/blog/detailed-modalities-of-tutorials/
from two tutorial pages:
https://acl2020.org/program/tutorials/
https://virtual.acl2020.org/tutorials.html
Thanks!

Hi Agata,
We have added it here https://acl2020.org/program/tutorials/
We couldn't add it in time for our yesterday's release of the virtual website. So as a workaround, I added a link to the new blog post in the old blog post that is linked on https://virtual.acl2020.org/tutorials.html

Sure, thanks!


Document "Paths_haskell_ide_engine" module

I only found 4 occurences:
Searching 57 files for "Paths_haskell_ide_engine"

/Users/rvion/dev/haskell-ide-engine/haskell-ide-engine.cabal:
   25                         Haskell.Ide.Engine.Transport.JsonStdio
   26                         Haskell.Ide.Engine.Types
   27:   other-modules:       Paths_haskell_ide_engine
   28    build-depends:       Cabal >= 1.22
   29                       , aeson
   ..
   64    hs-source-dirs:      app
   65    main-is:             MainHie.hs
   66:   other-modules:       Paths_haskell_ide_engine
   67    build-depends:       base
   68                       , Cabal >= 1.22

/Users/rvion/dev/haskell-ide-engine/app/MainHie.hs:
   27  import           Haskell.Ide.Engine.Types
   28  import           Options.Applicative.Simple
   29: import qualified Paths_haskell_ide_engine as Meta
   30  import           System.Directory
   31  import           System.Environment

/Users/rvion/dev/haskell-ide-engine/src/Haskell/Ide/Engine/BasePlugin.hs:
   18  import           Haskell.Ide.Engine.PluginUtils
   19  import           Options.Applicative.Simple (simpleVersion)
   20: import qualified Paths_haskell_ide_engine as Meta
   21  import           Prelude hiding (log)
   22

4 matches across 3 files

This is generated as part of the compile process, and lives in .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/autogen
On my machine it ends up having
module Paths_haskell_ide_engine (
    version,
    getBinDir, getLibDir, getDataDir, getLibexecDir,
    getDataFileName, getSysconfDir
  ) where

import qualified Control.Exception as Exception
import Data.Version (Version(..))
import System.Environment (getEnv)
import Prelude

catchIO :: IO a -> (Exception.IOException -> IO a) -> IO a
catchIO = Exception.catch

version :: Version
version = Version [0,1,0,0] []
bindir, libdir, datadir, libexecdir, sysconfdir :: FilePath

bindir     = "/home/alanz/mysrc/github/alanz/haskell-ide-engine/.stack-work/install/x86_64-linux/nightly-2015-10-27/7.10.2/bin"
libdir     = "/home/alanz/mysrc/github/alanz/haskell-ide-engine/.stack-work/install/x86_64-linux/nightly-2015-10-27/7.10.2/lib/x86_64-linux-ghc-7.10.2/haskell-ide-engine-<IP_ADDRESS>-31m1iz1kJsh3j19t7gGZiH"
datadir    = "/home/alanz/mysrc/github/alanz/haskell-ide-engine/.stack-work/install/x86_64-linux/nightly-2015-10-27/7.10.2/share/x86_64-linux-ghc-7.10.2/haskell-ide-engine-<IP_ADDRESS>"
libexecdir = "/home/alanz/mysrc/github/alanz/haskell-ide-engine/.stack-work/install/x86_64-linux/nightly-2015-10-27/7.10.2/libexec"
sysconfdir = "/home/alanz/mysrc/github/alanz/haskell-ide-engine/.stack-work/install/x86_64-linux/nightly-2015-10-27/7.10.2/etc"

getBinDir, getLibDir, getDataDir, getLibexecDir, getSysconfDir :: IO FilePath
getBinDir = catchIO (getEnv "haskell_ide_engine_bindir") (\_ -> return bindir)
getLibDir = catchIO (getEnv "haskell_ide_engine_libdir") (\_ -> return libdir)
getDataDir = catchIO (getEnv "haskell_ide_engine_datadir") (\_ -> return datadir)
getLibexecDir = catchIO (getEnv "haskell_ide_engine_libexecdir") (\_ -> return libexecdir)
getSysconfDir = catchIO (getEnv "haskell_ide_engine_sysconfdir") (\_ -> return sysconfdir)

getDataFileName :: FilePath -> IO FilePath
getDataFileName name = do
  dir <- getDataDir
  return (dir ++ "/" ++ name)

thanks !
I'll add that to the documentation :)

Can we close this?

FYI I asked myself this same question in a different setting, and eventually found a canonical source documenting the Paths_* file:
https://www.haskell.org/cabal/users-guide/developing-packages.html#accessing-data-files-from-package-code

@alanz can we let it open until I document it ?

@rvion Can I close this?

Sure :+1: didn't do it, and I'm not writing Haskell anymore lately


Editor window - inserting and scrolling

When inserting pages and scrolling to see the page types in a category, hovering and other events seem to stop working on the menu.
By Julian

Fixed with new insert page menu


Question about Result Reproduction

Hi~, great work.
I run the Validation code using LISA-7B-v1, and get the gIoU and cIoU scores of the ReasonSeg_val giou: 0.0610, ciou: 0.0567, which are abnormal and far behind the results in paper. Could you tell me what the problem might be? Thank~

I think you may not successfully load the model. The validation results seem to be that of random model weights.
Besides, the v1 model is trained with both train+val sets, so please use the v0 model if you want to reproduce the validation results.

Yes, I find the output mask is random. I download the provided model and valite by:
deepspeed --master_port=24999 train_ds.py \   --version="model/llava/pretrain_model/LLaVA-7B-Lightening-v1-1"  \   --dataset_dir='./dataset' \   --vision_pretrained="model/segment_anything/pretrained_model/sam_vit_h_4b8939.pth" \   --exp_name="test" \   --dataset="reason_seg" \   --weight='model/lisa/LISA-7B-v1' \   --eval_only
But I run the demo by:
python chat.py --version='model/lisa/LISA-7B-v1' --precision='fp16' --load_in_4bit
the output mask looks fine. Is my validation cmd wrong?

In fact, what confuses me is that the validation code sets the --weight hyperparameter but I can't found the place where it is uesed.

Hi, thanks for the great project!
I am having the same issue trying to reproduce the results on reason_seg. I get values like giou: 0.0843, ciou: 0.0662. I have tried with the following commands. Can you let me know what I am doing wrong?
I understand from the previous comment that v1 is trained on train+val, but that makes my results still very unexpected. I should be getting results much higher than this with either v0 or v1.

 I have tried the latest version and 0e26916, while both of the results are abnormal. (latest: giou: 0.0317, ciou: 0.0200) (0e26916: giou: 0.0487, ciou: 0.0309). Have you successfully reproduce the validation performances? How do you solve the issue? Thanks a lot!

@SxJyJay what command do you use?

Hi @X-Lai, I just found I can get meaningful accuracy after comment out this initialization. This initialization will make SAM and projection layer from pretrained coefficient to random initialization one.
BEFORE
giou: 0.0723, ciou: 0.0686
AFTER
giou: 0.9526, ciou: 0.9721
Please confirm if my understanding is correct.

I think you may not successfully load the model. The validation results seem to be that of random model weights.
Besides, the v1 model is trained with both train+val sets, so please use the v0 model if you want to reproduce the validation results.

One thing to confirm. As default setting in training code shows, it looks like it  use train sets only. Is my understanding correct? If so, may I know why did v1 use train+val sets?

Hi @X-Lai,
In 4b17762 version, I just found I can get meaningful accuracy for xinlai/LISA-13B-llama2-v1-explanatory after comment out this initialization. This initialization will make SAM and projection layer from pretrained coefficient to random initialization one. BEFORE giou: 0.0723, ciou: 0.0686 AFTER giou: 0.9526, ciou: 0.9721 Please confirm if my understanding is correct.
Should we add a flag for this initialization? if not args.eval_only:   model.get_model().initialize_lisa_modules(model.get_model().config)
Best, Ryusaeba

Hi, thanks for the solution! I also gained a great increase after commenting. However, my result is giou: 0.8833, ciou: 0.9409, and before mine was also lower than yours. What do you think could be the problem? Thanks!

Hi @X-Lai,
In 4b17762 version, I just found I can get meaningful accuracy for xinlai/LISA-13B-llama2-v1-explanatory after comment out this initialization. This initialization will make SAM and projection layer from pretrained coefficient to random initialization one. BEFORE giou: 0.0723, ciou: 0.0686 AFTER giou: 0.9526, ciou: 0.9721 Please confirm if my understanding is correct.
Should we add a flag for this initialization? if not args.eval_only:   model.get_model().initialize_lisa_modules(model.get_model().config)
Best, Ryusaeba

Hi, thanks for the solution! I also gained a great increase after commenting. However, my result is giou: 0.8833, ciou: 0.9409, and before mine was also lower than yours. What do you think could be the problem? Thanks!

Apologies. I used the 7B model hence obtaining lower results. By the way, I've tried to evaluate the 13B model with 8*NVIDIA 3090 GPUs, while met the 'cuda out of memory' error. May I know how many GPUs did you use to evaluate the 13B model @ryusaeba ? Thanks in advance.

@Jeff001128 Yes, you are right. I'm using 13B.

same here. when i use LISA-13B-llama2-v0 with 0e26916 on reason_seg. the tensorboard logs 0.06295.
using LISA-13B-llama2-v1 on  main will result around 0.9 . how to reproduce the result on paper ?


Tracing of tf function is stuck when the function contains custom CRF layer that wraps tfa crf functions inside

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

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Mac OS Big Sur
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): from pypi
TensorFlow version (use command below): 2.4
Python version: 3.7
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
When wrapping crf functions from tensorflow_addons into a custom Keras layer and then creating a training function with it that will be converted into tf.function with dynamic first dimension of the input shape, the process is stuck during tracing when trying to create gradient tensors. if I create tf.function with static shapes, it works.
If I use tfa.text.crf.crf_decode and tfa.text.crf.crf_log_likelihood directly without custom Keras layer wrapper, tracing tf.function seems to be working.
The problem appeared in version 2.4, it is working in 2.3
Describe the expected behavior
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
import tensorflow as tf
import tensorflow_addons as tfa

potentials = tf.random.uniform((3,4,5))
sequence_lengths = tf.ones((3,))
tag_indices = tf.ones((3,4), dtype=tf.int32)

class CRF(tf.keras.layers.Layer):
    def build(self, input_shape: tf.TensorShape) -> None:
        self.transition_params = self.add_weight(
            shape=(5, 5),
            regularizer=tf.keras.regularizers.l2(0.1),
            name="transitions",
        )
        self.built = True

    def call(self, potentials, sequence_lengths):
        x = tfa.text.crf.crf_decode(
            potentials, self.transition_params, sequence_lengths
        )
        y = tfa.text.crf.crf_log_likelihood(
            potentials, tag_indices, sequence_lengths, self.transition_params
        )
        return x, y

crf = CRF()

def foo(potentials, sequence_lengths):
    with tf.GradientTape(persistent=True) as tape:
        x, y = crf(potentials, sequence_lengths)

    return x, y

tf_foo_static =  tf.function(foo)
tf_foo_static(potentials, sequence_lengths)  # works fine

tf_foo_dynamic = tf.function(foo, input_signature=[tf.TensorSpec((None, None, 5)), tf.TensorSpec((None,))])
tf_foo_dynamic(potentials, sequence_lengths)  # the execution is stuck without raising any error

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
When the process is terminated for tfa.text.crf.crf_log_likelihood, it looks like the gradient calculation through tf.scan in crf_forward is stuck, if we add back_prop=False, it manage to do the tracing, but it is a part of the loss function, so we need to backdrop the gradient.
When the process is terminated for tfa.text.crf.crf_decode, it looks like the gradient calculation through tf.keras.layers.RNN in crf_decode_forward is stuck.

@Ghostvv
I ran the code shared on tf 2.4 and nightly,please find the gist here and let us know.

@Ghostvv
I ran the code shared on tf 2.4 and nightly,please find the gist here and let us know.

@Saduf2019 thank you very much for creating colab. Indeed tf2.4 is stuck, while tf2.5-nightly seems to be working

@Saduf2019 thank you very much for creating colab. Indeed tf2.4 is stuck, while tf2.5-nightly seems to be working

@Ghostvv
Can you please upgrade and use nightly as the issue does not occur in nightly.

@Ghostvv
Can you please upgrade and use nightly as the issue does not occur in nightly.

I'm sorry we cannot use nightly releases. Unfortunately, as we ship rasa library, we have to use stable releases. Do you have a timeline when 2.5 might be released?

I'm sorry we cannot use nightly releases. Unfortunately, as we ship rasa library, we have to use stable releases. Do you have a timeline when 2.5 might be released?

Thanks for your issue. We are tracking this as to-do for upcoming TF 2.5 release. Will keep you posted as we know more.

The original code snippet is fixed with latest release TF 2.5.
See gist


Help me make the subview beyond borders of parent view in android

apologize for my english
i have two view:
<View style={{position: 'absolute', top: 0, left: 0, height: 100, width: 300}}>      <View style={{position: 'absolute', top: 50, left: 0, height: 100, width: 100}}>      </View> </View>
but subview can not exceed the borders of parent view when run in android
please help me fix

Overflow is not supported on Android. You will have to make the parent view larger.


Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
Rate-Limited
These updates are currently rate-limited. Click on a checkbox below to force their creation now.

[x] Update actions/checkout action to v4
[ ] Update crazy-max/ghaction-import-gpg action to v6
[ ] Update goreleaser/goreleaser-action action to v5
[ ] 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked
These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

[ ] Update module github.com/stackitcloud/stackit-sdk-go/services/argus to v0.2.0

Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

[ ] Update module github.com/hashicorp/terraform-plugin-framework to v1.4.0
[ ] Update module github.com/hashicorp/terraform-plugin-go to v0.19.0
[ ] Update module github.com/stackitcloud/stackit-sdk-go/services/logme to v0.3.0
[ ] Update module github.com/stackitcloud/stackit-sdk-go/services/mariadb to v0.3.0
[ ] Update module github.com/stackitcloud/stackit-sdk-go/services/postgresflex to v0.2.0
[ ] Update module github.com/stackitcloud/stackit-sdk-go/services/rabbitmq to v0.3.0
[ ] Update module github.com/stackitcloud/stackit-sdk-go/services/redis to v0.3.0
[ ] Update module github.com/stackitcloud/stackit-sdk-go/services/resourcemanager to v0.2.0
[ ] Update module github.com/stackitcloud/stackit-sdk-go/services/ske to v0.2.0
[ ] Click on this checkbox to rebase all open PRs at once

Detected dependencies
github-actions

.github/actions/build/action.yaml

actions/setup-go v4

.github/workflows/ci.yaml

actions/checkout v3

.github/workflows/release.yaml

actions/checkout v3
actions/setup-go v4
crazy-max/ghaction-import-gpg v5
goreleaser/goreleaser-action v4

.github/workflows/renovate.yaml

actions/checkout v3
renovatebot/github-action v39.0.5

.github/workflows/tf-acc-test.yaml

actions/checkout v3

gomod

go.mod

go 1.20
github.com/google/go-cmp v0.5.9
github.com/google/uuid v1.3.1
github.com/hashicorp/terraform-plugin-framework v1.3.5
github.com/hashicorp/terraform-plugin-framework-validators v0.12.0
github.com/hashicorp/terraform-plugin-go v0.18.0
github.com/hashicorp/terraform-plugin-log v0.9.0
github.com/hashicorp/terraform-plugin-testing v1.5.1
github.com/stackitcloud/stackit-sdk-go/core v0.2.0
github.com/stackitcloud/stackit-sdk-go/services/argus v0.1.0
github.com/stackitcloud/stackit-sdk-go/services/dns v0.2.0
github.com/stackitcloud/stackit-sdk-go/services/logme v0.2.0
github.com/stackitcloud/stackit-sdk-go/services/mariadb v0.2.0
github.com/stackitcloud/stackit-sdk-go/services/opensearch v0.3.0
github.com/stackitcloud/stackit-sdk-go/services/postgresflex v0.1.0
github.com/stackitcloud/stackit-sdk-go/services/postgresql v0.3.0
github.com/stackitcloud/stackit-sdk-go/services/rabbitmq v0.2.0
github.com/stackitcloud/stackit-sdk-go/services/redis v0.2.0
github.com/stackitcloud/stackit-sdk-go/services/resourcemanager v0.1.0
github.com/stackitcloud/stackit-sdk-go/services/ske v0.1.1
golang.org/x/mod v0.12.0

Moved to https://github.com/stackitcloud/terraform-provider-stackit/issues/50


Infinite load in server Again

In version <IP_ADDRESS> and <IP_ADDRESS> I don't,no one else can go again this picture is loading as it should and was deleting the folder Level or Players doesn't help =_=

I am right there with you, might be an unturned bug though

I have all the latest updates to worked! It's something you have my problem you haven't solved!


refactor(app): use traditional function syntax

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

18 of 18 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
528

Relevant Lines:
528

💛  - Coveralls


generate-graph fails

I can't seem to generate the graph on win 10:
C:\git\vpc-flow-log-analysis-master>npm run generate-graph

><EMAIL_ADDRESS>generate-graph C:\git\vpc-flow-log-analysis-master
> ts-node ./graph-generator/index.ts

download log data from AWS s3: 1:34.392 (m:ss.mmm)
unzip log data: 1:59.968 (m:ss.mmm)
(node:22272) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'logs/log_2020-12-09T09:26:34.500Z.txt'
    at Object.openSync (fs.js:476:3)
    at mergeFiles (C:\git\vpc-flow-log-analysis-master\node_modules\merge-files\index.js:17:17)
    at C:\git\vpc-flow-log-analysis-master\graph-generator\s3-download.ts:70:38
    at step (C:\git\vpc-flow-log-analysis-master\graph-generator\s3-download.ts:33:23)
    at Object.next (C:\git\vpc-flow-log-analysis-master\graph-generator\s3-download.ts:14:53)
    at fulfilled (C:\git\vpc-flow-log-analysis-master\graph-generator\s3-download.ts:5:58)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:22272) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:22272) [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.

i was thinking it may have to do with how url is in win vs linux so I changed:
in s3-download.ts:
const mergedFileName = `logs/log_${new Date().toISOString()}.txt`;

to
const mergedFileName = `logs\log_${new Date().toISOString()}.txt`;

and
const fullPath = `data/${object.Key}`;

to
const fullPath = `data\${object.Key}`;

in utils.ts:
    const folders = path.split('/');
    folders.pop();  // last element is file path
    const folderPath = folders.join('/');

to
    const folders = path.split('\\');
    folders.pop();  // last element is file path
    const folderPath = folders.join('\\');

and then I got:
C:\git\vpc-flow-log-analysis-master>npm run generate-graph

><EMAIL_ADDRESS>generate-graph C:\git\vpc-flow-log-analysis-master
> ts-node ./graph-generator/index.ts

(node:21376) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, mkdir ''
(Use `node --trace-warnings ...` to show where the warning was created)
(node:21376) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:21376) [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.

Would love some guidance.

Has the logs directory been created by this call?

The logs directory exists. not sure if by that call or other.

tried to remove it - the directory is recreated with nothing inside (same error)

Hm, have you tried removing the logs folder prefix completely?
I.e., changing this line to
const mergedFileName = `log_${new Date().toISOString()}.txt`;

same
 grant delete on fandalism.tblDistroBankWithdrawls  TO 'dkingestor_u'@'%';

Seems like you have kept your backslash Windows adjustments, can you reset them and then try again?

I haven't.
This is what I have:
utils.ts:
    const folders = path.split('/');
    folders.pop();  // last element is file path
    const folderPath = folders.join('/');

s3-download.ts:
    const mergedFileName = `log_${new Date().toISOString()}.txt`;

and
        const fullPath = `data/${object.Key}`;

Hmm interesting, but it's the same error. I think we might need to skip this step if we don't use a folder. Can you try that, please?

download log data from AWS s3: 1:33.082 (m:ss.mmm)
unzip log data: 2:09.409 (m:ss.mmm)
(node:13616) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'log_2020-12-13T12:08:36.438Z.txt'
    at Object.openSync (fs.js:476:3)
    at mergeFiles (C:\git\vpc-flow-log-analysis-master\node_modules\merge-files\index.js:17:17)
    at C:\git\vpc-flow-log-analysis-master\graph-generator\s3-download.ts:68:38
    at step (C:\git\vpc-flow-log-analysis-master\graph-generator\s3-download.ts:33:23)
    at Object.next (C:\git\vpc-flow-log-analysis-master\graph-generator\s3-download.ts:14:53)
    at fulfilled (C:\git\vpc-flow-log-analysis-master\graph-generator\s3-download.ts:5:58)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:13616) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:13616) [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.

Sorry, I can't reproduce it here. Might be a problem with the merge-files library on Windows / in your environment. I use Node version v15.3.0, maybe that's something to investigate.


centos host image site is not available

we are not able to get chef/centos 6.6 hots site

I think they have been moved to: https://atlas.hashicorp.com/bento/

Fixed by PR #4

I merged PR #5 which should fix your issue.
Sorry for the massive delay.

Thank you so much
On Thu, May 26, 2016 at 12:55 AM, Craig S<EMAIL_ADDRESS>wrote:

Closed #2 https://github.com/craig5/salt-essentials-utils/issues/2.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/craig5/salt-essentials-utils/issues/2#event-672255835


sail error

./vendor/bin/sail artisan key:generate
UnexpectedValueException
The stream or file "/var/www/html/storage/logs/laravel-2024-08-23.log" could not be opened in append mode: Failed to open stream: Permission denied
The exception occurred while attempting to log: file_put_contents(/var/www/html/.env): Failed to open stream: Permission denied
Context: {"exception":{}}
at vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php:140
136▕             }
137▕             if (!\is_resource($stream)) {
138▕                 $this->stream = null;
139▕
➜ 140▕                 throw new \UnexpectedValueException(sprintf('The stream or file "%s" could not be opened in append mode: '.$this->errorMessage, $url) . Utils::getRecordMessageForException($record));
141▕             }
142▕             stream_set_chunk_size($stream, $this->streamChunkSize);
143▕             $this->stream = $stream;
144▕         }
  +13 vendor frames

14  artisan:13
Illuminate\Foundation\Application::handleCommand()

What did you do exactly to trigger this error?

This error only occures in a Docker environment.
I removed the Docker configuration files because they were provided by another user and not used nor maintained by me.
If you want to use this application in a Docker enveronment, please fork the project and set it up yourself.

it was run in a ubuntu lcx container, not the docker installation, so how do i actually install this?


Adding animation to AnimatedSprite doesn't update inspector immediately

Godot version:
3.1 beta8
Issue description:
When you add a new animation in AnimatedSprite

the inspector isn't updated

and you need to reselect the sprite to have it refreshed. Surprisingly, renaming animation updates correctly.
Steps to reproduce:

Create AnimatedSprite node
Add SpriteFrames
Add a new animation
Check animation list in inspector

Hi
I am able to reproduce this issue on Ubuntu.
I would like to work on it.

I would like to give it a shot too, see if I can fix this :)
I haven't looked at this part of the code base, but I'm curious to see it!

It appears that removing a Animation also doesn't update, but renaming animations does seem to do the trick... Interesting... I'll look into this more today, I got some classes now :)

This issue is weird. I investigated it and nowhere in code the animation list is updated explicitly. I noticed that it's refreshed upon calling _validate_property, but it's only called magically when doing rename ("magically" ie. not anywhere near AnimatedSprite). Trying to force any validation sadly fails.
I also noticed that it happens with other nodes too. E.g. when changing a Polygon2D from the editor, inspector's vertex list doesn't update. I noticed that AnimationPlayer does this correctly, but ugh .-. I failed to determine how. It seems to require some deep digging. Or someone who knows how it works.

Yeah, that's what I originally thought. Maybe a function that someone forgot to call to update the inspector, but it seems it's deeper than that.
I'll keep looking into it today!

https://github.com/godotengine/godot/blob/a53645e726097e9020d12df886b62431cb1740b9/editor/plugins/sprite_frames_editor_plugin.cpp#L385-L386
Removing these two lines give the expected behaviour, but it also changes selected animation in inspector as the new animation.

I am also trying!

Yeah, I was looking at that file too, nice catch tho! We might be getting closer :)

@veryprofessionaldodo What's the behaviour required? Just removing these lines seems to fix this particular issue and it does not seems to break anything(or does it?).

Oh, actually it seems like the problem is fixed!
KoBeWo did mention that it also appears in Polygon2D. Is that problem affected, or is it another problem entirely?

Which part in Polygon2D? It works fine for me..

I don't know, I never actually noticed it.
But that seems like another issue, maybe this looks like it's ready for a pull request

The array isn't updated if it's expanded in the inspector. You either need to re-select node or shrink/expand the array.

It still does not work properly on removing animation(deleting). I was conforming whether maybe issue is something else, but can not yet figure it out.


SOS flash a bit quicker

This PR is purely a matter of taste.  My view is that SOS looks a bit better if a little faster.
Strangely, I built a version which allowed the original sleeps to be multiplied by a fiddle factor for experimentation.
Liking 0.75, I hard-coded it in.
Not sure why I played with this, but here it is for what it's worth.

Looks good!


You can use the REST API without validation

Bug
You can fake requests to the REST API and obtain other user's credentials
Contact
discord: the_goldgamerrr (Khunakorn on ISP discord)

Y'know, It would be really bad if someone (who is getting quite annoyed by the lack of response) were to leak all of your user's credentials in a public space. I really think you should start addressing theses issues.

how do you this exactly? since our project doesn't really use REST API, I don't really know how to check if it's true.

First off, thank you for finally responding to my emails.
I don't know why or how you sent the response to my personal email.
I guess you got it from github.
Anyways, clearly your backend uses some kind of API to send data,
and from what I've seen it's structured like a REST API
As for how I did it, it's actually shocking how easy it is.
Just go to:
https://workflow-automation-backend-d8aee053fe82.herokuapp.com/workflows/
and you can literally see all users who created a workflow as well as their
unhashed passwords.
Best Regards,
Khunakorn
On Sun, Dec 1, 2024 at 1:11 PM Chamarak @.***> wrote:

how do you this exactly? since our project doesn't really use REST API, I
don't really know how to check if it's true.
—
Reply to this email directly, view it on GitHub
https://github.com/TAGCH/Workflow-Automation/issues/66#issuecomment-2509591868,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDA2PY4RTJ4LN6MWFXLP7DD2DKSCVAVCNFSM6AAAAABSLOI3DKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBZGU4TCOBWHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

wow so that's a thing, I didn't know you could respond in Github via email.
Anyways, now that I leaked all your accounts accidentally. You probably should fix it.

wait, how did you get that link tho.


GitHub repo does not match NPM package

I've noticed that the README, tests and index.js file in this repo are outdated and do not match the latest code in the NPM package. Oddly enough, the NPM package.json is outdated (despite having the correct version number) and the GitHub repo has the correct deps/devDeps...

I think @kevva forgot to publish a new version, or he never had the time to finish the release.

Closing in favor of https://github.com/kevva/bin-build/issues/9.


Start refactoring a common UI pattern: recalculate some value only when

a key changes.
It's quite verbose right now for some widgetry States to determine if
the mouse is over a particular type of object, check if that object has
changed since the last time, and calculate something based on it. This
introduces a new helper for expressing the pattern a little more
clearly.
It might be worth removing the dependncy on SimpleApp, if some use cases
in game show up.
@michaelkirk Does this help? Is the Cacheable type overkill? Originally I had fn key as part of the trait too, but couldn't plumb all of the side parameters needed in while expressing the lifetimes correctly.

Actually, I think #406 is better. Can you tell I wrote Java for many years? >_<


Event Strategy & Messaging: cdCON

[ ] https://docs.google.com/document/d/1ROIQsfPwMKuxkuu0BE2cG92TDOfj8Yh8PShevrF0Q4g/edit?usp=sharing
[ ] cdCON Vision
[ ] cdCON Mision
[ ] cdCON Verticals


cannot run on gpu with configs and data in the example and docs (but work well on cpu backend)

my main.py:
import argparse
from easy_tpp.config_factory import Config
from easy_tpp.runner import Runner
def main():
parser = argparse.ArgumentParser()
parser.add_argument('--config_dir', type=str, required=False, default='configs/experiment_config.yaml',
                    help='Dir of configuration yaml to train and evaluate the model.')

parser.add_argument('--experiment_id', type=str, required=False, default='NHP_train',
                    help='Experiment id in the config file.')

args = parser.parse_args()

config = Config.build_from_yaml_file(args.config_dir, experiment_id=args.experiment_id)

model_runner = Runner.build_from_config(config)

model_runner.run()

if name == 'main':
main()
Error messege:
2023-09-05 22:06:34,176 - config.py[pid:552;line:33:build_from_yaml_file] - CRITICAL: Load pipeline config class RunnerConfig
2023-09-05 22:06:34,197 - runner_config.py[pid:552;line:163:update_config] - CRITICAL: train model NHP using GPU with torch backend
2023-09-05 22:06:34,200 - runner_config.py[pid:552;line:36:init] - INFO: Save the config to ./checkpoints/552_19516_230905-220634\NHP_train_output.yaml
2023-09-05 22:06:34,201 - base_runner.py[pid:552;line:170:save_log] - INFO: Save the log to ./checkpoints/552_19516_230905-220634\log
2023-09-05 22:06:34,483 - tpp_runner.py[pid:552;line:60:_init_model] - INFO: Num of model parameters 60672
2023-09-05 22:06:35,077 - base_runner.py[pid:552;line:92:train] - INFO: Data 'taxi' loaded...
2023-09-05 22:06:35,078 - base_runner.py[pid:552;line:97:train] - INFO: Start NHP training...
Traceback (most recent call last):
File "E:\isomorphism\ntpp\main.py", line 25, in
main()
File "E:\isomorphism\ntpp\main.py", line 21, in main
model_runner.run()
File "C:\ProgramData\anaconda3\envs\graphL\lib\site-packages\easy_tpp\runner\base_runner.py", line 191, in run
return self.train(**kwargs)
File "C:\ProgramData\anaconda3\envs\graphL\lib\site-packages\easy_tpp\runner\base_runner.py", line 98, in train
model = self._train_model(
File "C:\ProgramData\anaconda3\envs\graphL\lib\site-packages\easy_tpp\runner\tpp_runner.py", line 93, in _train_model
train_metrics = self.run_one_epoch(train_loader, RunnerPhase.TRAIN)
File "C:\ProgramData\anaconda3\envs\graphL\lib\site-packages\easy_tpp\runner\tpp_runner.py", line 188, in run_one_epoch
self.model_wrapper.run_batch(batch, phase=phase)
File "C:\ProgramData\anaconda3\envs\graphL\lib\site-packages\easy_tpp\torch_wrapper.py", line 116, in run_batch
loss, num_event = self.model.loglike_loss(batch)
File "C:\ProgramData\anaconda3\envs\graphL\lib\site-packages\easy_tpp\model\torch_model\torch_nhp.py", line 237, in loglike_loss
hiddens_ti, decay_states = self.forward(batch)
File "C:\ProgramData\anaconda3\envs\graphL\lib\site-packages\easy_tpp\model\torch_model\torch_nhp.py", line 192, in forward
self.rnn_cell(x_t, h_t, c_t, c_bar_i)
File "C:\ProgramData\anaconda3\envs\graphL\lib\site-packages\torch\nn\modules\module.py", line 1501, in call_impl
return forward_call(*args, **kwargs)
File "C:\ProgramData\anaconda3\envs\graphL\lib\site-packages\easy_tpp\model\torch_model\torch_nhp.py", line 54, in forward
x_i = torch.cat((x_i, hidden_i_minus), dim=1)
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu! (when checking argument for argument tensors in method wrapper_CUDA_cat)

let me have a look

Hi,
NHP model is fixed for running on cuda. Please use the most updated master branch.
There are still some problems with other models. When i fix everything, i will publish a new version of package.

I have checked other models and they seem work fine.

Thank you very much,Hope everything goes smoothly 🙏Many thanks for your workMou---Original---From: @.>Date: Thu, Sep 21, 2023 11:21 AMTo: @.>;Cc: "Altina @.>@.>;Subject: Re: [ant-research/EasyTemporalPointProcess] cannot run on gpu withconfigs and data in the example and docs (but work well on cpu backend) (Issue#5)
I have checked other models and they seem work fine.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

You are welcome.  Let us know if there are any other problems. We will continue to improve the code.