Feat/label selector

WORK IN PROGRESS
fixes #

it's working when the definition.cmd is curl
it's not working when opening the plugin on a fallback resource and the cmd is kubectl even though I add -l app=my-app to the definition.args
any idea why not? @Ramilito

Also when the cached_resources are loaded, and the fallback is now curl, the same filter that's working for other resources doesn't work on fallback

it's because we define definition.cmd and definition.url every time View() is called. working on it.

I had a bunch of stuff to do but now I'm back so let me know if you need me, was going to try to finish #354 otherwise!

Ready for review @Ramilito
it's working.
I'd like to add highlight in the future so key=value - key would be highlighted green. do you think this is easy to highlight when a user exits insert mode?

also I'd like to show the user that he is seeing resources with labels somewhere, maybe in the context bar?

I'm testing it out right now and It's looking really awesome!

I'd like to add highlight in the future so key=value - key would be highlighted green. do you think this is easy to highlight when a user exits insert mode?

The super easy way is to set a filetype that you feel is correct, that might not work here if you can't stick to yaml or json.
Otherwise, I would need to look into it but not sure what you mean with exits insert mode?

also I'd like to show the user that he is seeing resources with labels somewhere, maybe in the context bar?

Some are saving space by hiding the context and hints bar and it's too much information to put it in the divider like we use the filter for

ok we can do it in a different PR
can we merge?

ok we can do it in a different PR can we merge?

Left a few comments that I was curious about, would love it if  you could resolve those so we can merge it!

This feature might be useful later  together with kubectl tree feature


feat: implement EthereumTransaction

Signed-off-by: Daniel Akhterov<EMAIL_ADDRESS>Description:

Related issue(s):
Fixes #
Notes for reviewer:

Checklist

[X] Documented (Code comments, README, etc.)
[X] Tested (unit, integration, etc.)

Merged via cli because GitHub is being rude.


Implementing Better API

Our API for check whether someone was in the same region with a corona-virus patient is very network -consuming. In order to check that, we send the whole table of patients (thousands of people!) to the client each hour! And we want millions of client! Even if Israel is a small country with few citizens, re-using the app for USA, for instance, will mean an unreliable app.
I know there are privacy-paranoids who afraid, for reason I don't (and probably never will) understand, that the government will know where they were. Wow. I agree that's very horrible. But after the jokes, I'm proposing a different approach:
Instead of sending the whole database to the client, the client will send its location, and the server will return the overlaps, if there are. Of course, the paranoids mentioned above will protest again this approach, and so I suggest the following thing:
Yeah, (assuming the API keeps track of our movement and save the information, which I don't believe for, but anyway they're believe, so...) the API can track our movement. But only if it has access to our location in 100% sure every time. What if it can guess, but can't be sure?
Let's simplify the things. If we're requesting from someone to notify us whether in Jerusalem, st. Some-Street, the road near house numbered 33, there was a corona-virus patient on Thursday, 15:00 o'clock - this person can, somehow (I guess), to know where we was on Thursday, 15:00 o'clock. Don't you agree?
But what if we're requesting him to notify us whether there were corona-virus patients on both Jerusalem, Some-Street, the road near house 33 and Tel Aviv, Some-Another-Street, house 24? Now the person can guess where we live, but cannot be more than 50% sure.
Let's go one step further. If we ask the person about 5 locations, can it even guess where the real location is?
I think you can understand the direction. If, instead of just sending one location, we send multiple, the API can't know where we are.
Yet this is not true. because, let me illustrate the following scenario:
The app was installed on 10:00. Four hours after, the API knows that:

On 10:00, we were at either Jerusalem, Haifa or Tel Aviv.
On 11:00, we were at either Jerusalem, Tel Aviv or Rosh Hanikra.
On 12:00, we were at either Jerusalem, Ashdod, or Ramat Gan.
On 13:00, we were at either Jerusalem, Rehovot or Raanana.
On 14:00, we were at either Petah Tikva, Modiin, or Bnei Brak.

Do you see the problem? With this data, the API can easily guess that we're living at Jerusalem.
So, in order to prevent the API from tracking us, we need a way so even if it places crosswise the data across hours, still it can determine the real location.
Luckily, I've found a solution. Instead of just randomizing locations (apart from the real one), we'll do the following:

When the app is installed:

Save the user location as the previous location.
Randomize other four locations. Save them (I haven't said it yet, but obviously the number five is, ah, randomized).
Send the request.

Every time we want to check for overlap:

Calculate the distance and angle from the previous location.
Replace the "previous location" variable with the current one.
Add the distance to the four fictitious locations, and replace the variables of them.
Send the request.

This way, the server can't track us, as we have consistent five locations that can the only thing differs them from being real, is the unfortunate fact that they're not.
I still have a problem because we can exceed the country borders in long travels. I don't have a solution yet, I hope one of the people here will have.
If this proposal is accepted, the problem above is solved, and the folks at the Ministry of Health changes the API so it accepts list of locations and returns their overlaps, I'm ready to work on that and send a PR.

An anonymity set in the size of 5 (or even within tens, I would say) is too small to begin with.

Naive offsetting of geographic locations from randomized locations can very soon end-up in places that make zero-sense and would be easily ruled out by analysis of the request logs. Think crossing walls, walking on water, wandering around a kindergarten at night or a cemetery in the early morning.
A non-naive implementation, i.e. fitting locations into the randomized geographies so that they would make sense, will probably be an overkill.

There are other (IMHO more realistic) solutions that do not require sending all the patients data every period of time.
Mostly: incremental updates (as in https://github.com/MohGovIL/hamagen-react-native/issues/58) and Bluetooth proximity (as in https://github.com/MohGovIL/hamagen-react-native/issues/126).


Integrate with fsharp/fsharp

Hi @rojepp - I think something has happened to the commit history....there should be more than one commit, something like this : https://github.com/fsharp/fsharp/pull/498/commits

@dsyme Seems I messed up. Closing this.


FAQ Changes

Overview
The PM's will be working with Bonnie to edit some of the responses to the FAQ questions as well as potentially remove/edit questions that are deemed repetitive or can be combined into one.
Action Items

[ ] Create a google doc with newly edited question responses for Bonnie to look over before updating them.
[ ] Look into finding the FAQ folder so that PM's can make live update so front-end can focus on other issues.

Resources/Instructions
FAQ url

Link to google doc
Link is currently in view mode, only Levi and myself have access to make edits at this moment.


Provide a way to have a test complete when a future completes

I'm doing a lot of async tests and it'd be real handy if there was an easy way to have a test run until the future completes.
Basically given the test function:
Future testSomething() {
}
I've been doing:
futureTest('something', testSomething);
Where futureTest looks like:
void futureTest(spec, Future body()) {
  test(spec, () {
    expect(body(), completes);
  });
}
Would be nifty if this were built into the standard test function though.

This issue has been moved to dart-lang/test#187.


Split the screen using percent?

I tried to follow the Tailwind Flexbox Grids doc to split the screen. It works but I'd like more flexibility that the fixed set of fractions. Is it possible to split the screen by percent?
  wp = jp.WebPage()
  d = jp.Div(classes="flex mb-4", a=wp)
  jp.Div(text="Left", classes="w-1/6 bg-gray-400 h-12", a=d)
  jp.Div(text="Right", classes="w-5/6 bg-gray-500 h-12", a=d)

Sure, instead of the width class add the keyword argument style='width: 32%' if you want the width to be 32% for example.
You can see here: https://tailwindcss.com/docs/width/
what style the width classes translate to.
In the style you can insert and CSS you want.

Okay. So Tailwinds is just an alternative / abbreviated way to specify CSS. I can combine the two like this.
jp.Div(text="left css", style='width: 50%', classes="bg-gray-400 h-24", a=wp)
I notice that there's no runtime exception if I misspell a keyword argument. Why is that?

Yes, you can combine classes with style. If you are interested in learning how to style web pages there are many good CSS introductions. Classes are an important part of CSS.
For any keyword argument, JustPy sets the corresponding attribute of the instance created and therefore there is no error. When the component is rendered, JustPy knows how to handle special attributes like style, text and classes.


contextlib2 can't be installed (IDFGH-6210)

Run ./install.sh got following error message:
Collecting contextlib2>=0.5.5
  Downloading https://dl.espressif.com/pypi/contextlib2/contextlib2-21.6.0-py2.py3-none-any.whl (13 kB)
ERROR: Package 'contextlib2' requires a different Python: 2.7.17 not in '>=3.6'

My PC env is: Ubuntu 18.04.4 LTS

Hi @wushifu32.
What is the version of your ESP-IDF?
Python 2.7 is no longer supported by the Python community. Therefore, packages are dropping support for it.
If you use a recently patched version of ESP-IDF and install the required package dependencies - python3 and python3-pip in particular, then install.sh will detect and use Python 3 instead.

My ESP-IDF has been updated to the commit  caa9e323cc9556855e122cabe289d61b49aaa479
The ./install.sh running message:
Detecting the Python interpreter
Checking "python" ...
Python 3.6.9
"python" has been detected
Installing ESP-IDF tools
WARNING: File /home/colin/.espressif/idf-env.json can not be created.
Selected targets are: esp32s3, esp32s2, esp32c3, esp32
Installing tools: xtensa-esp32-elf, xtensa-esp32s2-elf, xtensa-esp32s3-elf, riscv32-esp-elf, esp32ulp-elf, esp32s2ulp-elf, openocd-esp32
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Installing Python environment and packages
===== here detected python2 =====
Python 2.7.17
pip 20.3.4 from /home/colin/.espressif/python_env/idf5.0_py3.6_env/local/lib/python2.7/site-packages/pip (python 2.7)
Installing Python packages from /home/colin/code/esp-idf/requirements.txt

But the default python & pip on My PC are allready version3+:
colin@T440:~/code/esp-idf$ pip --version
pip 21.3.1 from /usr/local/lib/python3.6/dist-packages/pip (python 3.6)
colin@T440:~/code/esp-idf$ python --version
Python 3.6.9

Please try to remove /home/colin/.espressif/python_env/idf5.0_py3.6_env/ and re-run the intall script.


feat: add support for $inspect and $effect.root

related to #423

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.009%) to 91.454%

Totals

Change from base Build<PHONE_NUMBER>:
0.009%

Covered Lines:
2490

Relevant Lines:
2633

💛  - Coveralls


Fetch slang-llvm.so from correct release

Closes https://github.com/shader-slang/slang/issues/4648
Should close https://github.com/shader-slang/slang/issues/4812

When I don't snooze the verbose warning messages, I got more usefull error message on Windows.
$ cmake.exe --preset default
Preset CMake variables:

  CMAKE_MSVC_RUNTIME_LIBRARY="MultiThreaded$<$<CONFIG:Debug>:Debug>"

-- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.46.0.windows.1")
-- The C compiler identification is Clang 18.1.8 with GNU-like command-line
-- The CXX compiler identification is Clang 18.1.8 with GNU-like command-line
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/LLVM/bin/clang.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/LLVM/bin/clang++.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found CUDAToolkit: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v12.3/include (found version "12.3.107")
-- Could NOT find OptiX (missing: OptiX_INCLUDE_DIRS)
-- Could NOT find NVAPI (missing: NVAPI_INCLUDE_DIRS NVAPI_LIBRARIES)
-- Could NOT find Aftermath (missing: Aftermath_INCLUDE_DIRS Aftermath_LIBRARIES)
CMake Warning at cmake/GitHubRelease.cmake:78 (message):
  Unsupported architecture for slang binary releases: AMD64
Call Stack (most recent call first):
  CMakeLists.txt:139 (get_best_slang_binary_release_url)

CMake Error at CMakeLists.txt:141 (message):
  Unable to find binary release for slang-llvm, please set a different
  SLANG_SLANG_LLVM_FLAVOR or set SLANG_SLANG_LLVM_BINARY_URL manually

fixed, feel free to merge please

@jkwak-work I see this PR has been previously approved but there are more comments.
Are there any changes needed in this PR before we can merge?

I think it is good to merge.
I misread a few lines.


DllReferencePlugin with multiple dll requires loading all

What is the current behavior?
I have 2 named items in my config to create dll bundles. The first one is intended as the base references for the whole site and I am including that on my main layout.html page. The 2nd one is only meant for a separate page and should be dynamically loaded by webpack. The issue is that I get an error when loading layout.html stating ....Uncaught ReferenceError: [the 2nd dll name] is not defined
I believe this is what issue https://github.com/webpack/webpack/issues/6656 was trying to say as well.
If the current behavior is a bug, please provide the steps to reproduce.
Here is an example entry for the dll config
entry: {            base: [             'bootstrap',                     ],                 jqueryui: ['jquery-ui/ui/widgets/draggable'] },
and loaded into the main configuration like so...
new webpack.DllReferencePlugin({
context: __dirname,
manifest: require('./dist/dll/base.json')
}),
    new webpack.DllReferencePlugin({
        context: process.cwd(),
        manifest: require('./dist/dll/jqueryui.json')
    }),

layout.html includes...

What is the expected behavior?
loading layout.html does not require jqueryui.dll to be loaded as well. This is wasteful as it is not needed on this page. If I do load jqueryui.dll in layout.html it does not throw the error.

Dynamically load the dll into the page that it requires only. Do not throw an error if all dlls are not included.
Other relevant information:
webpack version:  4.18.1
Node.js version: 8.12.0
Operating System: Win 10
Additional tools:

Why do you reference the DLL when it's not needed?

Something in the module graph seems to depend on the DLL. If nothing depends on the DLL it would not ask for it at runtime.
You need a separate entrypoint where nothing references the DLL.

Let me see if I understand what you mean.
Ok so let's say jquery is defined in dll1 and jqueryui is defined in dll2. Jqueryui depends on jquery so I need to also include jquery in dll2 as well?

That's not what I wanted to say, but for this scenario you might need a DllReferencePlugin pointing to dll1 in the build of dll2.

Is the dll plugin meant to be used with multiple entries? I haven't found any examples of it being used this way.

Is this problem fixed?


Add arresteddevops.com to Showcase

 You should sign our Contributor License Agreement in order to get your pull request merged.

Merged as 923e45573156fe4343b2bc6b33f7b1a6924536f8


toc is not generated: 'selectors': 'h2,h3,h4,h5', post only have ‘h3’

My article only have h3 tag, and I set  'selectors': 'h2,h3,h4,h5', toc is not generated in this situation.
Do the article must have the h2 tag ?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

'selectors' start with 'h3'

'selectors' start with 'h3'

Ok. Thanks.


Pagination widget not working in a column

Hi, When I tried to use Pagination widget inside a column, then its throwing error. Can anyone provide me some pointer to fix this issue.

I fixed it by putting my Pagination widget in ConstrainedBox. So its like -
SingleChildScrollView ( Column ( Widget1(), ConstraintBox (Pagination())),)
It has temporarily fixed the problem.
For now, I have I have placed maxHeight: MediaQuery.of(context).size.height - 236, for ConstraintBox.
Is there any specific method to find remaining height of screen


PR for #2813

Fixes #2813
Added compile-time and run-time dependencies for Marathon.  Also added instructions for compiling Marathon against mesos source.

@asridharan: thanks a lot for contribution to Marathon. There are some typos that should be fixed before we can merge this.
Happy New Year!

@asridharan merged, thanks!


When building a custom model using keras.Model, a warning was triggered

My environment:
window10
CUDA10.0
tensorflow-gpu 1.14
When I built a more complex model today, I triggered the following warning:

W1128 15: 22: 59.781456 32404 ag_logging.py:145] Entity <bound method DiMP.call of <__ main __. DiMP object at 0x0000024606A21208 >> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, export AUTOGRAPH_VERBOSITY = 10) and attach the full output. Cause: (unicode error) 'utf-8' codec can't decode byte 0xca in position 250: invalid continuation byte (tmp56zh3z7b.py, line 15)

I don't know if this warning will affect the model operation, and the content of the warning says that it needs to be reported. So I came here.
Because there are a lot of engineering components, I can't determine which part triggered this warning. I won't upload all the code for the time being. If I need to upload code, I will not refuse.
Here is the entire print:

C:\software\Anaconda3\envs\CV_env\python.exe C:/Users/stars_ocean/Desktop/DiMP_TF/models/DiMP.py
WARNING: Logging before flag parsing goes to stderr.
W1128 15:22:57.572051 32404 deprecation_wrapper.py:119] From C:\Users\stars_ocean\Desktop\DiMP_TF\models\backbone\MobileNet_V3_By_Model.py:4: The name tf.enable_eager_execution is deprecated. Please use tf.compat.v1.enable_eager_execution instead.

used backbone layers: [5, 12]
W1128 15:22:57.689736 32404 deprecation_wrapper.py:119] From C:\Users\stars_ocean\Desktop\DiMP_TF\models\classifiter\Initializer.py:24: The name tf.keras.initializers.RandomNormal is deprecated. Please use tf.compat.v1.keras.initializers.RandomNormal instead.
W1128 15:22:57.691731 32404 deprecation_wrapper.py:119] From C:\Users\stars_ocean\Desktop\DiMP_TF\models\classifiter\Optimizer.py:36: The name tf.get_variable is deprecated. Please use tf.compat.v1.get_variable instead.
2019-11-28 15:22:57.692470: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library nvcuda.dll
2019-11-28 15:22:58.922915: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 0 with properties:
name: GeForce GTX 1050 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:01:00.0
2019-11-28 15:22:58.923123: I tensorflow/stream_executor/platform/default/dlopen_checker_stub.cc:25] GPU libraries are statically linked, skip dlopen check.
2019-11-28 15:22:58.926473: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1763] Adding visible gpu devices: 0
2019-11-28 15:22:58.926787: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2019-11-28 15:22:58.930528: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 0 with properties:
name: GeForce GTX 1050 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:01:00.0
2019-11-28 15:22:58.930820: I tensorflow/stream_executor/platform/default/dlopen_checker_stub.cc:25] GPU libraries are statically linked, skip dlopen check.
2019-11-28 15:22:58.934215: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1763] Adding visible gpu devices: 0
2019-11-28 15:22:59.447520: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1181] Device interconnect StreamExecutor with strength 1 edge matrix:
2019-11-28 15:22:59.447669: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1187]      0
2019-11-28 15:22:59.447755: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 0:   N
2019-11-28 15:22:59.453515: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 2995 MB memory) -> physical GPU (device: 0, name: GeForce GTX 1050 Ti, pci bus id: 0000:01:00.0, compute capability: 6.1)
W1128 15:22:59.781456 32404 ag_logging.py:145] Entity <bound method DiMP.call of <main.DiMP object at 0x0000024606A21208>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, export AUTOGRAPH_VERBOSITY=10) and attach the full output. Cause: (unicode error) 'utf-8' codec can't decode byte 0xca in position 250: invalid continuation byte (tmp56zh3z7b.py, line 15)
W1128 15:23:05.219440 32404 deprecation.py:323] From C:\software\Anaconda3\envs\CV_env\lib\site-packages\tensorflow\python\autograph\impl\api.py:255: add_dispatch_support..wrapper (from tensorflow.python.ops.array_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.where in 2.0, which has the same broadcast rule as np.where
2019-11-28 15:23:06.199208: W tensorflow/core/common_runtime/eager/context.cc:371] Added two functions with the same name: __inference_conv_and_transpose_10931
Process finished with exit code 0

I know why that warning is triggered. Because i am in function
def call (self, inputs, training = None, mask = None):
This is caused by a long paragraph with """(omitted)""".
I deleted those comments and they didn't trigger the warning.
I think this warning is very unreasonable. I think adding a function description will not cause errors in the code, so it should not trigger any warning.


fix(sdk): Stops including binding in assertion hashes

Is there any back story on why this needs to be removed from the assertion?

@jentfoo

Is there any back story on why this needs to be removed from the assertion?

Because the way the assertion is defined in the spec is that it includes the signature. So there is a "chicken and egg" problem with the binding object.
https://github.com/opentdf/spec/pull/37/files#diff-9889d13f2cc03fa0cb9708ff10a6399fdc54b3800591c65daf4fe288bdd788b1R189-R197


Allow setting of Unity canvas element id

Is your feature request related to a problem? Please describe.
In API >= 8 the canvas element no longer has an id and there is no way to set it.
Describe the solution you'd like
Add an id= prop to the Unity component:
<Unity id="..." unityContext={...} />

Describe alternatives you've considered
You can already set the class name of the Unity canvas element, i.e. you can use event.target.classList.contains(...) to identify it. But IMHO event.target.id === '...' is much more concise.
Test automation may also benefit from this feature.
Additional context
An alternative would be to add a canvasProps= prop which would allow the user to set other properties on the canvas element, i.e.
<Unity
  canvasProps={{
    id: '...',
  }}
  unityContext={...}
/>

Hi, any update here?

Hi. This literal feature is not implemented. However, it is still possible to get a reference to the canvas and thus its id.
See the documentation for further details
https://react-unity-webgl.dev/docs/api/canvas-ref


Topic names are not auto-named in aws - this causes conflicts when two projects have the same topic name.

Attaching a snippet of code which explains why topics are not auto-named.
This might require an additional issue to resolve -
for k := range a.proj.Topics {
	a.topics[k], err = sns.NewTopic(ctx, k, &sns.TopicArgs{
		// FIXME: Autonaming of topics disabled until improvements to
		// nitric topic name discovery is made for SNS topics.
		Name: pulumi.StringPtr(k),
		Tags: common.Tags(ctx, k),
	})
	if err != nil {
		return errors.WithMessage(err, "sns topic "+k)
	}
}

https://github.com/nitrictech/cli/blob/develop/pkg/provider/pulumi/aws/aws.go#L194-L204


VisitsByDayOfWeek Component

It would be great to have a component that reports on the average number of visits by the day of the week.
The method signature would likely include:

visits: the ahoy visit data
time_window: the time window to average the visits over (i.e. 4 weeks would then report on the average visits by day of week for the past 4 weeks)
exclude_days: a list of days that are to be excluded for the report / calculation (i.e. skip Sat / Sun)

Reporting the data as a table would suffice.

Here is the pull request for this issue: https://github.com/harled/matey/pull/69
Display number of visits occurred on each day of the week for a given time
Method signature includes:

visits: the ahoy visit data
time_window: the time window to count the visits over (i.e. 4 weeks would then report on the total visits by day of week for the past 4 weeks)
exclude_days: a list of days that are to be excluded for the report / calculation (i.e. skip ["Saturday","Sunday"])

Notes:

I tried to group the visits within the query by the day of the week they occur on, with something like this:
@visits = visits.where(started_at: time_window.ago..).group(:started_at.strftime("%A")).count.first(limit)
but .strftime method can't apply to the :started_at symbol within the query.
Using the Groupdate gem is what is examplified on the official ahoy documentation,
(specifically group_by_day_of_week) but I didn't know if it is kosher to add a gem dependency to matey. Hence why there is a hashmap and ternary operator in the component.

Currently the component is showing the total number of visits that occurs on each day of the week within the time_window.
I would like to know a bit more about what "average the visits over" means: e.g. if 8 visits occur on the past 4 Mondays then the component displays an average of 2 for Monday (8 divided by 4)?

Thank you!

Alex and I were speaking and we were also wondering if it would be better to apply exclude_days in the component or the front end. Right now it is being applied in the component.

Alex and I were speaking and we were also wondering if it would be better to apply exclude_days in the component or the front end. Right now it is being applied in the component.

Definitely good to throw it in the component. We want to keep the UI fairly simple and focused on display for now. Great question!


@vitejs/plugin-legacy wrong work in nuxt

Environment

Operating System: Linux
Node Version:     v16.17.1
Nuxt Version:     3.0.0-rc.13
Nitro Version:    0.6.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      runtimeConfig, css, vite
Build Modules:    -

Reproduction
Nuxt
Describe the bug
Problem is polyfills load after entry file and System variable is undefined!
i install legacy plugin in pure vite project and don't see this problem. i think nuxt problem!
Additional context
No response
Logs
Uncaught ReferenceError: System is not defined `entry-legacy.4e3349cb.js:1:12341`

Hi. Are there any updates or a known workaround for this?

As a workaround, we ended up configuring config.vite.build.target for legacy JS support, and are using a self-hosed https://polyfill.io/ for the polyfills. We're self-hosting it because the online version is stuck in v3 for now, see https://github.com/Financial-Times/polyfill-service/issues/2734.
To make configuring config.vite.build.target easier, we're using browserslist along with esbuild-plugin-browserslist:
import browserslist from 'browserslist'
import { resolveToEsbuildTarget } from 'esbuild-plugin-browserslist'
import { defineNuxtConfig } from 'nuxt/config'

export default defineNuxtConfig({
  …
  vite: {
    build: {
      target: getBuildTarget([
        '>0.1% and supports es6-module and not ios < 12 and not opera > 0',
        'node >= 18.13.0'
      ])
    }
  }
})

function getBuildTarget(browsers) {
  return resolveToEsbuildTarget(browserslist(browsers), {
    printUnknownTargets: false
  })
}

As a workaround, we ended up configuring config.vite.build.target for legacy JS support, and are using a self-hosed https://polyfill.io/ for the polyfills. We're self-hosting it because the online version is stuck in v3 for now, see Financial-Times/polyfill-service#2734.
To make configuring config.vite.build.target easier, we're using browserslist along with esbuild-plugin-browserslist:
import browserslist from 'browserslist'
import { resolveToEsbuildTarget } from 'esbuild-plugin-browserslist'
import { defineNuxtConfig } from 'nuxt/config'

export default defineNuxtConfig({
  …
  vite: {
    build: {
      target: getBuildTarget([
        '>0.1% and supports es6-module and not ios < 12 and not opera > 0',
        'node >= 18.13.0'
      ])
    }
  }
})

function getBuildTarget(browsers) {
  return resolveToEsbuildTarget(browserslist(browsers), {
    printUnknownTargets: false
  })
}

Thanks for the quick response and for sharing your workaround, @lehni.
That might worth a try, but I want to make sure one thing. How do you integrate polyfill.io (or you self-hosted version of it), into your config above?

You just need to add a script tag to your app that loads the polyfill with the desired options. We have something like this in our default layout:
  setup() {
    const script = []
    const { polyfill } = useConfig()
    if (polyfill) {
      const version = polyfill.version || 1
      const features = polyfill.features?.join(',') || ''
      const flags = polyfill.flags?.join(',') || ''
      script.push({
        src: `/polyfill?v=${version}&features=${features}&flags=${flags}`
      })
    }
    …
    useHead({ script })
  },

And the config:
    polyfill: {
      version: 2, // Only used for cache busting.
      features: [
        'default',
        'globalThis',
        'es2015',
        'es2016',
        'es2017',
        'es2018',
        'es2019',
        'es2020',
        'es2021',
        'es2022',
        'es2023'
      ],
      flags: ['gated']
    }

wanna help for this issue @danielroe

@zhancheng help very welcome 😊

The temporary solution for this problem is to transfer the entry-legacy file to the end of the manifest file. You can solve the problem using a Nuxt hook in a module file:
// modules/fixViteLegacyPlugin.ts
import {defineNuxtModule} from '@nuxt/kit';

export default defineNuxtModule({
  setup() {
    nuxt.hook('build:manifest', manifest => {
      const keys = Object.keys(manifest);

      if (!keys.some(key => key.includes('polyfills-legacy'))) {
        return;
      }

      const entryKey = keys.find(key => key.includes('entry-legacy')) as string;
      const entryValue = manifest[entryKey];

      delete manifest[entryKey];
      manifest[entryKey] = entryValue;
    });
  }
});

Just in case if anyone lands here trying to make Nuxt work in Chrome 49 (Windows XP), I managed to achieve that by removing defer from the script tags:
diff --git a/dist/runtime.mjs b/dist/runtime.mjs
index 29154e86eed636881eabc2c7fd01e9883e9e0404..736cbd0cd5dab57e71fd5dea427afc99717c4909 100644
--- a/dist/runtime.mjs
+++ b/dist/runtime.mjs
@@ -162,8 +162,7 @@ function renderScripts(ssrContext, rendererContext) {
   return Object.values(scripts).map((resource) => renderScriptToString({
     type: resource.module ? "module" : null,
     src: rendererContext.buildAssetsURL(resource.file),
-    defer: resource.module ? null : "",
-    crossorigin: ""
+    crossorigin: resource.module ? "" : null
   })).join("");
 }
 function createRenderer(createApp, renderOptions) {

and then to fix this: [nuxt] error caught during app initialization Error: Context conflict the workaround is to remove modern chunks completely:
// modules/vite-legacy-patch.ts
import { defineNuxtModule } from '@nuxt/kit'
import { pick } from 'lodash'

export default defineNuxtModule({
  setup(_option, nuxt) {
    nuxt.hook('build:manifest', manifest => {
      // copy of manifest where polyfill is moved to 1st position
      const manifest_copy: typeof manifest = {
        ...pick(manifest, 'vite/legacy-polyfills-legacy'),
        ...manifest,
      }
      // clear manifest
      for (const key of Object.keys(manifest)) {
        delete manifest[key]
      }
      // fill manifest again from the copy
      Object.assign(manifest, manifest_copy)

      // remove module attributes from legacy chunks
      for (const key of Object.keys(manifest)) {
        if (key.match(/-legacy(\.|$)/)) {
          manifest[key].module = false
        } else if (manifest[key].module) {
          // remove modern chunks completely, otherwise it conflicts in modern Chrome:
          // [nuxt] error caught during app initialization Error: Context conflict
          //
          // that could be related to defer being removed from legacy chunks
          // see<EMAIL_ADDRESS>          // but with that patch Chrome 49 wouldn't run any scripts at all
          delete manifest[key]
        }
      }
    })
  },
})

and then some polyfills:
export default defineNuxtConfig({
  vite: {
    plugins: [
      // for Windows XP
      // see also modules/vite-legacy-patch.ts
      legacy({
        targets: ['chrome 49'],
        additionalLegacyPolyfills: [
          'intersection-observer',
          'mdn-polyfills/Element.prototype.getAttributeNames',
        ],
      }),
    ],
  }
})

This makes it work in Windows XP.
This is all (without a doubt) very dirty and unpleasant, so if there are better workarounds please weigh in!

The problem is that the polyfill bundle is loaded after the entry bundle, cause polyfills should always come first. I was inspired by Ilya's comment to create a solution like this:

That's the only change I needed to make, no need to adjust any build artifacts or anything.

Just a heads up, I managed to deliver isomorphic build which runs both legacy and non-legacy code:
1. Put the polyfills chunk to 1st position and remove module attribute from legacy chunks
modules/vite-legacy.ts:
import { defineNuxtModule } from '@nuxt/kit'
import { pick } from 'lodash'

// Fix vite-legacy build, see https://github.com/nuxt/nuxt/issues/15464
export default defineNuxtModule({
  setup(_option, nuxt) {
    nuxt.hook('build:manifest', manifest => {
      if (!manifest['vite/legacy-polyfills-legacy']) {
        return
      }

      // Copy of manifest where polyfill is moved to 1st position.
      const manifest_copy: typeof manifest = {
        ...pick(manifest, 'vite/legacy-polyfills-legacy'),
        ...manifest,
      }
      // Clear manifest.
      for (const key of Object.keys(manifest)) {
        delete manifest[key]
      }
      // Fill manifest again from the copy.
      Object.assign(manifest, manifest_copy)

      // Remove module attribute from legacy chunks.
      for (const key of Object.keys(manifest)) {
        if (key.match(/-legacy(\.|$)/)) {
          manifest[key].module = false
        }
      }
    })
  },
})

2. Mark legacy chunks as nomodule and remove defer from them
server/plugins/vite-legacy.ts:
import { defineNitroPlugin } from 'nitropack/dist/runtime/plugin'

// Make vite-legacy build operational, see https://github.com/nuxt/nuxt/issues/15464
export default defineNitroPlugin(nitroApp => {
  nitroApp.hooks.hook('render:response', response => {
    // Mark legacy chunks as nomodule (prevents modern browsers from loading them)
    // At the same time, unmark them as defer (otherwise System.register() in the legacy entry doesn't actually execute the code)
    response.body = response.body.replace(
      /(<script src="[^"]+\-legacy\.[^>]+") defer/g,
      '$1 nomodule',
    )

    // Remove legacy chunks preload (fixes warnings in modern browsers)
    response.body = response.body.replace(
      /<link rel="preload" as="script" href="[^"]+\-legacy\..*?>/g,
      '',
    )

    // The other option would be NOT to remove defer from legacy chunks,
    // but start them from a nomodule HTML script:
    //
    // response.body += `<script nomodule>document.querySelector("script[src*='/entry-legacy.']").onload=function(){System.import(this.src)}</script>`
    //
    // This is similar to what vite-legacy-plugin does in vanilla vite.
  })
})

We've discussed as a team and I think we shouldn't adopt within Nuxt itself as the incompatibility window is small and decreasing with time.
However, a module implementation would very much be welcome. Feel free to ping me if there's anything you need or Nuxt does not provide as part of doing this.

the incompatibility window is small and decreasing with time.

@danielroe Can you elaborate on this? It seems like this is always going to be a problem, cause the polyfill bundle is always going to be loaded after the nuxt bundle.
The resolution is quite hacky as well (having to re-order the build manifest in a nuxt hook).
Would be nice if there would just be a nuxt config API that would allow you to control the load order of bundles.

@fabis94 Would you open a new issue to track the enhancement you're talking about, perhaps?

FWIW, I published my recipe above as a Nuxt module:
https://www.npmjs.com/package/nuxt-vite-legacy
This collection of hacks is not something I'm exactly proud of, but it works. :)

This is something that I feel should be documented somewhere. I have prior experience with Vite and polyfills from another project and expected to be able to add the legacy plugin to the the vite.plugins property in the nuxt.config.ts file without issue. I went so far as writing the documentation for using this property in Nuxt before finding this issue.
Quite shocked that we need to update the response on every request using the render:response, feels icky IMHO.
Honestly this is something I'd like to see first class support however I understand there's very little sense in re-inventing the wheel.

The problem is that the polyfill bundle is loaded after the entry bundle, cause polyfills should always come first. I was inspired by Ilya's comment to create a solution like this:
// nuxt.config.ts
  hooks: {
    'build:manifest': (manifest) => {
      // kinda hacky, vite polyfills are incorrectly being loaded last so we have to move them to appear first in the object.
      // we can't replace `manifest` entirely, cause then we're only mutating a local variable, not the actual manifest
      // which is why we have to mutate the reference.
      // since ES2015 object string property order is more or less guaranteed - the order is chronological
      const polyfillKey = 'vite/legacy-polyfills'
      const polyfillEntry = manifest[polyfillKey]
      if (!polyfillEntry) return

      const oldManifest = { ...manifest }
      delete oldManifest[polyfillKey]

      for (const key in manifest) {
        delete manifest[key]
      }

      manifest[polyfillKey] = polyfillEntry
      for (const key in oldManifest) {
        manifest[key] = oldManifest[key]
      }
    }
  }

That's the only change I needed to make, no need to adjust any build artifacts or anything.
Note: The polyfill bundle key might be different depending on the settings of the legacy plugin. I'm only using it to generate polyfills for modern bundles (renderLegacyChunks: false & modernPolyfills: true)

It works for me,thx~

FWIW, I published https://github.com/nuxt/nuxt/issues/15464#issuecomment-1539790246 as a Nuxt module:
https://www.npmjs.com/package/nuxt-vite-legacy
This collection of hacks is not something I'm exactly proud of, but it works. :)

@IlyaSemenov thanks for your module.
It worked for me.  However, I want to add to that.  My target browser was chrome 69.0.3497.106 I also tested chrome 79.0.3906.0.
I used:
"nuxt-vite-legacy": "1.2.0"
"nuxt": "3.10.3",

If used only this and I got error Uncaught ReferenceError: globalThis is not defined
legacy: {
   targets: ["chrome 69"],
}

I fixed the error when I added a polyfill for globalThis.
legacy: {
    targets: ["chrome 69"],
    modernPolyfills: ['es.global-this'],
}

After that, I added all the necessary polyfills
legacy: {
    targets: ["chrome 69"],
    modernPolyfills: ['es.global-this', 'es.object.from-entries', 'es.array.flat-map', 'es.array.flat']
}

All variants polifills from core-js has here

@IlyaSemenov Thanks for this module.  I was having a lot of trouble with Nuxt and the vite legacy plugin.


TAJO-1783: Query result is not returned by invalid output path

I just reviewed the patch. The change and its clean up look great to me.
I tried to find non-forwarded tests on partitioned tables. I haven't found them. If they exist, could you let me know where they are?
Actually, it's not your problem. But, I'd like to ensure that your change guarantees that non-forwarded scans work well on partitioned tables.

You can find it like testColumnPartitionedTableByThreeColumns in TestTablePartitions.
https://github.com/apache/tajo/pull/431 does not allow the managed table. so it does not test the non-forwarded query.
Anyway,  I’m going to add TestSimpleQuery

+1
The patch looks great  to me. The patch seems to include unit tests to verify the things you changed.


variadic higher order functions

Description
This is an issue for making variadic forms of the other higher order functions (similar to #1642)

[ ] integrate_1d
[ ] algebra_solver
[ ] algebra_solver_newton
[ ] map_rect

Current Version:
v3.3.0

Examining the code, it looks like algebra_solver and algebra_solver_newton have variadic arguments (@jgaeb implemented this a bit ago).
That said I can't find the issue nor the PR where these changes were made. And it doesn't look like these changes made it all the way to the Stan language.

Algebra solvers were made variadic as a side effect of #2421 but that has not been exposed to the Stan language.


tech-story: [M3-9017] - Add MSW crud domains

Description 📝
Straight forward PR to add domains to CRUD mode (including seeds)

Changes  🔄

Add domains CRUD mode
Add domains seed
Fix small eventing display bug with "Import a zone" events

How to test 🧪
Prerequisites
Verification steps

Reset all MSW
Play with domains crud mode (including seeding)

 Author Checklists
As an Author, to speed up the review process, I considered 🤔
👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿  Providing accessibility support

[ ] I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

[x] All unit tests are passing
[x] TypeScript compilation succeeded without errors
[x] Code passes all linting rules

Re-converting to draft in order to revisit the bugs mentioned in code review

@jaalah-akamai had a bad update to the loader. all fixed now. changes are limited to just domains without further optimization to the MSW tooling


How to display app version?

My package.json has a version number, let's say I want to show that in the footer of my application.
How would I do so?
All I could find is this, but that's not relevant to current angular-cli right? http://stackoverflow.com/questions/34907682/how-to-display-app-version-in-angular2

I'm not on the very latest version but as of beta 30 importing package.json did work. I'd give it a try.

I couldn't import it, and requireing it didn't work with ng build -prod.

Something to consider is that importing or requiring your package.json has the potential to expose development information into your production build.
Two other possible options include:

Hard-code the value in the source -- the environment file would probably be the best place
Create a pre-build script that injects the version into the source before each build

I concur with @clydin that the value should be set in your environment files and should be put there via a process outside of the CLI itself. I'm closing this issue as the suggested approach is manual and outside of the CLI.

If you're doing semver, git describe is a cool thing!
// @ts-check
const chalk = require('chalk');
const git = require('git-describe');
const path = require('path');
const fs = require('fs-extra');

const info = git.gitDescribeSync({ longSemver: true });
const file = path.resolve(__dirname, '..', 'src', 'environments', 'version.ts');

fs.writeFileSync(
    file,
    `export const VERSION = ${JSON.stringify(info)};` ,
    { encoding: 'utf-8' });

console.log(chalk.green(`Wrote version info ${info.raw} to ${path.relative(path.resolve(__dirname, '..'), file)}`));

  "scripts: {
    "postinstall": "node scripts/version.js"
  }

I couldn't import it, and requireing it didn't work with ng build -prod.

const { version: appVersion } = require('../../package.json')

this soultion ( from http://stackoverflow.com/questions/34907682/how-to-display-app-version-in-angular2 )
works well for me in Angular 5.
Just make sure to add "node" type inside "types" property in tsconfig.app.ts as mentioned in comments there.

I know this is an older issue, but when trying to solve the same problem i combined the above solution with a line in your packages.json, this makes sure it keeps your version.ts up to date, when using npm version:
"version": "node set-version.js && git add -A .",
Whenever you run npm version x.x.x it will update your version.ts and include it in the commit and tag.

Thanks @thijsvanbuuren for your suggestion. I was able to simplify it a bit with a script to run from the package.json scripts:
version.sh
version_file=src/app/app.version.ts
> $version_file
echo "// This file was generated on $(date)
export const appVersion = '$1';" >> $version_file
git add $version_file

package.json
...
"version": "0.0.0",
"scripts": {
  "version": "./version.sh $npm_package_version",
  ...

Then from a component:
import { appVersion } from 'path/to/app.version';

Note that calling git add from the version script will cause the file to be staged while npm is updating the version (but just after the version is updated, so you have access to the newest version number). See the npm docs

@menehune23 any way you could convert the shell script to a batch file for Windows usage?

@JaxonWright I don't have a Windows machine and haven't run batch scripts in a long time, though the logic is pretty simple: we're just writing some literal text to a file called src/app/app.version.ts.  The only variable parts are the date (optional, honestly, but I like to have it), and the first argument.
In Windows, I believe echo works, and the argument can be referenced by %1. Not tested, but should be a good start.
If anyone else with Windows experience wants to chime in, feel free 😉.

The shell script works fine as-is for me on Windows 10.


Visual Studio 2017 - An incompatible SQL Server version was detected

When I try to add the Linux based SQL server 2017 from Microsoft to the list of SQL Servers in the SQL Server Object Explorer then Visual Studio returns the error  An incompatible SQL Server version was detected.
Steps to reproduce:

In the SQL Server Objet Explorer : enter the connection parameters of the database.
The list of possible databases is found !

Select a database and press the Connect button.

Now the error is thrown.
But I can connect to the database via Tools > Connect to database...
And I can also connect to the database with SQL Server Management Studio v17.1.
I have already tried installing the latest version of:

SQL Server Data Tools 17.1
Data-tier Application Framework 17.1

Executing the statement SELECT @@VERSION on the database returns me:
Microsoft SQL Server 2017 (CTP2.1) - 14.0.600.250 (X64)   May 10 2017 12:21:23   Copyright (C) 2017 Microsoft Corporation. All rights reserved.  Developer Edition (64-bit) on Linux (Ubuntu 16.04.2 LTS)
I am running Visual Studio 2017 on a Windows 10 64-bit.

I checked and VS2017 does not yet support SQL 2017 CTP or RC builds.  The support is being worked on and should roll out in a VS preview release later this month and an update within a couple months.

Where can I read more information on this issue?

The only information from Microsoft that I found on this is confirming that it does not yet support SQL 2017 : https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt#use-ssdt-in-visual-studio-2017. I guess we will have to wait a couple of months. I will close the issue here as it is not a Docker issue.


Cleanup

I have decided against writing tests for main,  cause it is difficult and doesn't have much value.  Its simply a set of function calls which are tested elsewhere,  or part of third party code which shouldn't be tested


Adding i18n server-side JS function

Fixes #160.
Even though PR #180 added the server-side JS function for i18n, it wasn't added to the Nashorn bindings context. Hence webapp developers wasn't able to use that function. This PR carries necessary changes to add the i18n function to the Nashorn bindings.

Note: merge this PR after merging #219


chore: Added setup to the project

In this milestone we worked on the following 💪🏼  :

Created the main.rb file introducing the Main class.
Added Linters for the project
Created Item class in a separate .rb file.

Build with :

Ruby 💎 💎 💎

THANKS FOR YOUR FEEDBACK 💟

Implement all the methods in item.rb to start the project.
I also  added the UI for main.rb we just need to edit parts to make it works


multipleOf logic produces incorrect results

The logic for multipleOf compares the remainder of a division with the f64 EPSILON constant to decide if a number is a multiple or not. This approach doesn't make sense. EPSILON is simply the difference between 1.0 and the next larger representable number. With regards to the multipleOf calculation this is just an arbitrary constant and comparing remainders to it gives us no guarantees.
EG:
1e-15 is a multiple of 1e-16. But (1e-15 / 1e-16) % 1.0 = 1.7763568394002505e-15 which is greater than epsilon so it is incorrectly said to not be a multiple.
1.3e-16 is not a multiple of 1.3. But (1.3e-16 / 1.3) % 1.0 = 9.999999999999999e-17 which is less than epsilon so it is incorrectly said to be a multiple.

The people over at Monaco have implemented a better way to implement this calculation without introducing incorrect results - https://github.com/microsoft/vscode-json-languageservice/blob/7a478cd29a387cf8813b0a32499e2347102d7a6c/src/parser/jsonParser.ts#L596


Asset precompile fails with undefined method `column_attributes'

I didn't see anything locally, but this is what happens when pushing to Heroku:
remote: -----> Preparing app for Rails asset pipeline
remote:        Running: rake assets:precompile
remote:        rake aborted!
remote:        NoMethodError: undefined method `column_attributes' for #<struct PermittedParams params=nil>
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/surveyor_gui-0.1.2/lib/surveyor_gui/models/column_methods.rb:13:in `block in <module:ColumnMethods>'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/concern.rb:120:in `class_eval'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/concern.rb:120:in `append_features'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/surveyor_gui-0.1.2/app/models/column.rb:2:in `include'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/surveyor_gui-0.1.2/app/models/column.rb:2:in `<class:Column>'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/surveyor_gui-0.1.2/app/models/column.rb:1:in `<top (required)>'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:274:in `require'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:274:in `block in require'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:240:in `load_dependency'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:274:in `require'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:360:in `require_or_load'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:317:in `depend_on'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:233:in `require_dependency'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/surveyor_gui-0.1.2/lib/surveyor_gui/engine.rb:24:in `block (2 levels) in <class:Engine>'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/surveyor_gui-0.1.2/lib/surveyor_gui/engine.rb:23:in `each'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/surveyor_gui-0.1.2/lib/surveyor_gui/engine.rb:23:in `block in <class:Engine>'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/callbacks.rb:441:in `instance_exec'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/callbacks.rb:441:in `block in make_lambda'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/callbacks.rb:189:in `call'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/callbacks.rb:189:in `block in simple'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/callbacks.rb:190:in `call'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/callbacks.rb:190:in `block in simple'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/callbacks.rb:190:in `call'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/callbacks.rb:190:in `block in simple'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/callbacks.rb:92:in `call'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/callbacks.rb:92:in `_run_callbacks'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/callbacks.rb:734:in `_run_prepare_callbacks'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/callbacks.rb:81:in `run_callbacks'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.0/lib/action_dispatch/middleware/reloader.rb:83:in `prepare!'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.0/lib/action_dispatch/middleware/reloader.rb:55:in `prepare!'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/application/finisher.rb:50:in `block in <module:Finisher>'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/initializable.rb:30:in `instance_exec'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/initializable.rb:30:in `run'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/initializable.rb:55:in `block in run_initializers'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/initializable.rb:54:in `run_initializers'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/application.rb:352:in `initialize!'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/config/environment.rb:5:in `<top (required)>'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:274:in `require'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:274:in `block in require'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:240:in `load_dependency'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:274:in `require'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/application.rb:328:in `require_environment!'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/application.rb:443:in `block in run_tasks_blocks'
remote:        /tmp/build_7025e2961ac33212e9d88b2cedf49b95/vendor/bundle/ruby/2.0.0/gems/sprockets-rails-2.2.2/lib/sprockets/rails/task.rb:64:in `block (2 levels) in define'
remote:        Tasks: TOP => environment
remote:        (See full trace by running task with --trace)
remote:  !
remote:  !     Precompiling assets failed.

I'm using 0.1.2

Will take a look this week.

Having trouble reproducing.  Was able to build a barebones app (see https://github.com/kjayma/survtest) and successfully deployed to heroku here: https://nameless-citadel-2500.herokuapp.com/surveyor_gui/surveyforms
Please try changing your gemfile to take the latest version of surveyor from github and see if that works:
gem 'surveyor_gui', :git => 'git://github.com/kjayma/surveyor_gui.git'

If that does not solve the problem, we'll need to dig a little deeper into your app.

I believe it was heroku run rake db:migrate that got me around this.
Thanks for the help and sorry I didn't reply sooner!
On Sun, Jan 25, 2015 at 10:41 AM, Kevin Jay<EMAIL_ADDRESS>wrote:

One other thought - have you run heroku run rake db:migrate recently?
—
Reply to this email directly or view it on GitHub
https://github.com/kjayma/surveyor_gui/issues/40#issuecomment-71385344.

No problem!  Sorry I didn't respond sooner.  Day job keeping me pretty busy :)

This is a load order issue in: https://github.com/kjayma/surveyor_gui/blob/master/lib/surveyor_gui/engine.rb#L13
The permitted params decorator (which defines PermittedParams.new.column_attributes) needs to be loaded before the models that reference it.


Remove unused vif drivers

Two drivers that are unused in Cosmic.

IvsVifDriver was part of BigSwitch
DirectVifDriver was part of LXC
Both are now gone and since this also includes some duplicate code I propose to ditch this too.

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 07:52 min (Wall Clock)
[INFO] Finished at: 2016-05-13T21:19:02+02:00
[INFO] Final Memory: 73M/738M
[INFO] ------------------------------------------------------------------------

Ping @bheuvel @borisroman @wilderrodrigues

Integration tests: https://beta-jenkins.mcc.schubergphilis.com/job/cosmic/job/0002-tracking-repo-branch-build/78

The Jenkins build seems to hang. Any idea how to trigger rebuild? Tries force-push and close/open but didn't work.

go build

go build

Integration test results: https://beta-jenkins.mcc.schubergphilis.com/job/cosmic/job/0002-tracking-repo-branch-build/78/
Three tests failed, seem unrelated but weird that tests keep failing. What do you think @borisroman? Can't be related to PR I'd say.


Fix tag finding

Close #153.

The replacing of the function body by an empty string is good way for splitting.


rename LIBSPDM_ENABLE_CAPABILITY_SET_CERTIFICATE_CAP to LIBSPDM_ENABLE_CAPABILITY_SET_CERT_CAP

This is to align all CAP definition in SPDM specification.

1/23/2034 - agree.


Download audio-only as Webm / Keep Webm file "effectively" (without using -k)

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2019.02.18. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2019.02.18

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[x] Feature request (request for a new functionality)
[x] Question
[ ] Other

Description of your issue, suggested solution and other information
Currently, to download the best quality audio from youtube video, we simply use
youtube-dl -x ULR
The application download the webm file, then quickly "get out" the opus file from webm container and immediately delete original webm file.
However, the opus file isn't widely supported, I want to keep the webm file.
Of course, the application suggest using "-k" to keep that file. But when we use -k, the whole video file (which is 8-10x bigger) would be downloaded.
Please add one more option for this purpose (download audio-only as Webm), or simply add webm to --audio-format

Thank you

Don't use -x in the first place if you don't need any conversion.

@dstftw Could you please read my issue for one minute instead of close it immediately? Please.
We use -x to download the audio only instead of the big whole audio file.
The webm file is downloaded actually, but it was deleted.
Add "webm" to AUDIO-FORMAT is reasonable.

Anyway, I've changed the title of issues


Wrong highlight for {…} in comments.

lean.nvim version (commit): ddcc998

Should be fixed, thanks.


Load Operator Extensions

I have some code in progress that would allow orca to load extensions to the library.
Motivation:
Orca has a very limited set of operators. This is a good thing®. It focuses the user on basic use out of the box. Also most user keyboards only have access to so many letters, and orca is running out of available characters.
But,
There are times that a user wants to extend the set of operators. It would allow for some really unique customizations or shorthands that don't need to be added to the orca.
I propose an way in orca that a user can load a set of operators that are custom, and dont have to be compiled in. It would be commander command, 'extend', which would load a js file at runtime and add the operators to the library.
Here is an example of what it might look like: custom.orcas
export const load = (Operator) => {
  const extensions = {}

  extensions['Φ'] = function Operator_ (orca, x, y, passive) {
    Operator.call(this, orca, x, y, '_', passive)

    this.name = 'niff'
    this.info = 'Reads offset, bangs if equal to char'

    this.ports.x = { x: -2, y: 0 }
    this.ports.y = { x: -1, y: 0 }
    this.ports.comparison = { x: 1, y: 0 }
    this.ports.output = { x: 0, y: 1, bang: true }

    this.operation = function (force = false) {
      const x = 0 - this.listen(this.ports.x, true)
      const y = 0 - (this.listen(this.ports.y, true) + 1)
      this.ports.val = {x, y }
      const a = this.listen(this.ports.comparison)
      const b = this.listen(this.ports.val)
      return a !== b
    }
  }
  return extensions
}

This style of exports works better for a dynamic load in a browser and node environment.
Risks
Orca is already running out of space for operators. Its hard to find available chars to extend. I propose that extensions are in the unicode space, so that there is no interference between extensions and normal orca operators. Currently its not easy to enter unicode in Orca, (I have to use something like  https://unicode-table.com/en/#03A6 and copy and paste) but I've proven it works fine. In some future it might be nice to have a way to help users put unicode chars in, (like a selector) but I will leave that to the futue.
I would like to pursue this as a merge request, I just want to make sure that @neauoire you'd be open to this as I don't want to have a lot of time invested and not have it available to the community. I think it would open up Orca to some amazing things.

I'm not particularly a fan of this idea, especially the parsing javascript code on the fly. I'm sure that if someone want to make their own operators, they can modify their library directly, it's simpler, safer and a lot more reliable.
If someone has no programming knowledge and would like to use someone else's special operators, I think it would be a good opportunity to show this person how orca works underneath the hood and where to paste the operator code. I've had to do that in the paste and it was fun.

Ok sounds like solid logic. I will keep my own library of operators, and
try to share them via gists if others would be interested.
On Sun, Dec 1, 2019, 7:35 PM Лu Лinveгa<EMAIL_ADDRESS>wrote:

I'm not particularly a fan of this idea, especially the parsing javascript
code on the fly. I'm sure that if someone want to make their own operators,
they can modify their library directly, it's simpler, safer and a lot more
reliable.
If someone has no programming knowledge and would like to use someone
else's special operators, I think it would be a good opportunity to show
this person how orca works underneath the hood and where to paste the
operator code. I've had to do that in the paste and it was fun.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hundredrabbits/Orca/issues/194?email_source=notifications&email_token=AAGCJOTKRHXEQPD6HOJT3I3QWRX65A5CNFSM4JTHVNR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFSAD2I#issuecomment-560202217,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGCJOUVBLCUPTQE5YBHYB3QWRX65ANCNFSM4JTHVNRQ
.


Crash at ZIP GASH store in Mall

I had been having crashes at the mall every time I go into the ZIP store. I had tested GTAVC with and without the limit adjuster and I found that the Limit Adjuster does in fact cause the crash. Even mod loader wasn't installed, only asi loader which was required is installed. I'm also using VC.exe 1.0 which is what everyone uses anyway.

Having a similar issue but made a new thread because my circumstances feel a little different. I have some mods installed and even when I uninstall them, my game freezes and crashes within a certain radius of the Gash store (honestly it's a super far radius for me, I can barely enter the mall or pass it without it crashing). For you, you may want to try editing the LimitAdjuster.ini in text editor, scroll to[VCLIMITS] and changed EntryInfoNode = 3200 to EntryInfoNode = 30000. Those were the instructions I found here on GTAForums. Unfortunately it hasn't worked for me, but maybe it'll work for you? Good luck!

YAMUVAH, I appreciate you replying. I have set the EntryInfoNode to 30000 and I'm not experiencing anymore crashes at the mall, I wish I could had found the instructions you linked sooner. Thank you. I hope you'll find a cause of the crash on your side. I would suggest make a clean install of the game and Install only one mod each time when you load the game to narrow down which mod is causing the crash for you. I wish you luck.


Rename the algorithm and type names (IPartition, knn join, distance join) to be consistent with paper's naming

rename PackedPartitionWithIndex to IPartition, and add type alias for IndexRDD
refactor the distance join and knn join. e.g., RTreeKNNJoin -> RKJSpark.
fix the error of length more than 100 characters in SparkConf.scala.
update the example for knn join.

Please fix the parser problem for drop index.
It is defined here.
replace DEINDEX and CLEAR INDEX syntax to
DROP INDEX idx_name ON tbl_name -> drop specific index on a table
DROP INDEX ON tbl_name -> drop all indexes on a table
CLEAR INDEX -> clear all indexes in the system


Create Bottom Tab View

Close the issue because the component already exists, and only the preview does not exist.


CLAIM does not seem to be a body part anymore

Not mentioned in the docs, and it'll error out if used with the following message:
SyntaxError: The requested module '/game/constants' does not provide an export named 'CLAIM'
    at (<isolated-vm boundary>)

Hi @NiciusB I assume your issue was resolved since you closed this?

@thmsndk  I guessed the part exists but not in my arena of choice after seeing people reporting missing variables for that reason in the discord


add UI host as env variable

I want to template out and have lots of hosts without managing a bunch of config secrets everywhere.
With this, we can specify the ENV var through our helm templates.
Signed-off-by: nobletrout<EMAIL_ADDRESS>

closing going to add again cleanly


how to delete mails storage?

Hi,
I have a created a mail server but it was taking too much space of my server.
Please take a look in the screen shots.

And i want to delete this storage.
Thanks in Advance

You'll have to adjust the settings in this mail server to retain less data.

How?

Settings -> Advanced settings -> RAW MESSAGE RETENTION SIZE

It was already set as 2 GB by default


add comments and mod some para name

Codecov Report
Attention: Patch coverage is 71.42857% with 2 lines in your changes missing coverage. Please review.

Project coverage is 70.96%. Comparing base (684d043) to head (c7ad2b8).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

taos-ws-sys/src/tmq.rs
66.66%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #366      +/-   ##
==========================================
- Coverage   70.96%   70.96%   -0.01%
==========================================
  Files          97       97
  Lines       33952    33951       -1
==========================================
- Hits        24093    24092       -1
  Misses       9859     9859

Flag
Coverage Δ

70.96% <71.42%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Upgrade peerDep range to include React 17

Let's make the library usable with React 17 by updating the peerDeps range. Ideally we can allow either ^16.8 and ^17.
Another project at GitHub using PRC is running into issues with the event delegation in older versions and is reliant on PRC upgrading to version 17 to move forward with shipping bug fixes.

Update: I think we should limit usage to just v17 and up. Because v17 includes changes to how event delegation works, it seems risky to allow either React 16 or React 17.

This has been merged into the major release branch

This has been merged into the major release branch


Negative numbers in types are not parsed as unary expressions

Describe the bug
Given the following code:
type test = -1;
const t = -1;

It parses like so:
Node kind: Module
Text: "type test = -1;\nconst t = -1;"
Node kind: TsTypeAliasDecl
Text: "type test = -1;"
Node kind: Ident
Text: "test"
Node kind: TsLitType
Text: "-1"
Node kind: Number
Text: "1"
Node kind: VarDecl
Text: "const t = -1;"
Node kind: VarDeclarator
Text: "t = -1"
Node kind: Ident
Text: "t"
Node kind: UnaryExpr
Text: "-1"
Node kind: Number
Text: "1"

Expected behavior
I would expect both numbers to parse within unary expressions. So:
Node kind: TsLitType
Text: "-1"
Node kind: UnaryExpr
Text: "-1"
Node kind: Number
Text: "1"

Version
0.19.2 of parser

@dsherret Currently TsLitType cannot store UnaryExpr or its siblings like BinExpr and I'm not sure if allowing usage of arbitrary expression in a TsLit is a good idea.
Anyway, I verified (and added a test) that type test = -1; is parsed as TsList with -1 as a value.

Hmmm... yeah I wasn't thinking too much when I opened this 😅 -- I was only thinking about what TypeScript does...

...but Babel does the following:

Yup, arbitrary expressions in a TsLit is not a good idea.
Ah, ok I didn't realize the value of the number was negative in this case. I've only been looking at the text because I need to get the text as-is. Anyway, for me it is not a big deal as when I encounter a TsLit that's a Number I will just look at the whole text of the TsLitType.
Thanks and thank you for adding the test! I'm going to close this because I think what swc is doing here is sufficient. 🙂


mesa: 24.1.1 -> 24.1.2

Description of changes
https://docs.mesa3d.org/relnotes/24.1.2.html
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Darwin currently doesn't build for unrelated reasons.

I also added .3 directly, after building on x86_64-linux:
5a56b5dfb19b1b2db9360a3bc1dd98c7cc42b331


[DO NOT MERGE] Testing AccessLint

Expect comments from AccessLint

Closing this, re-open if you still need to test.

It was more a demo than anything :)
On Thu., 14 Jun. 2018, 21:19 Code Hugger (Matthew Jones), <
<EMAIL_ADDRESS>wrote:

Closed #5680 https://github.com/sakaiproject/sakai/pull/5680.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sakaiproject/sakai/pull/5680#event-1680901876, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAH4aUM4zM6zKSWvDRD6Aft31xb8F08Zks5t8kbegaJpZM4Ujltm
.


[Question] Error trying to deploy to heroku

I have followed the instructions for deploying to heroku, however, every time I attempt to deploy I receive the following error:
 error An unexpected error occurred: "https://registry.yarnpkg.com/aws4/-/aws4-1.5.0.tgz: Request failed "502 Bad Gateway"".
Any help?

I have gotten past the above error. I basically reset my package.json to what was the latest in the repo. However, when I go through the section describing deploying to heroku I see the following:
"start:prod": {     "command": "node bin/server",     "env": {       "NODE_ENV": "production"     }   }
however there is no file names 'server' inside the bin folder.

I had the same problem and struggled with this for hours: I looked through old versions of the library and found that there used to be a file called server.js, which turns out to be pretty much exactly like the file which should be in bin/dev-server.js. I reproduced the file in bin/server.js as:
const config = require('../config/project.config')
const server = require('../server/main')
const debug = require('debug')('app:bin:server')
const port = config.server_port
const host = config.server_host

server.listen(port)
debug(`Server is now running at http://${host}:${port}.`)
debug(`Server accessible via localhost:${port} if you are using the project defaults.`)

All of the documentation on the package.json setup however did not work for me at all, and what I got working in the end was this:
"build": "npm run deploy:prod"
"start": "better-npm-run start:prod"
  "betterScripts": {
    "start:prod": {
      "command": "node bin/server",
      "env": {
        "DEBUG": "app:*",
        "NODE_ENV": "production"
      }
    },
    "deploy": {
      "command": "npm rebuild node-sass; npm run compile",
      "env": {
        "DEBUG": "app:*"
      }
    },
    "deploy:dev": {
      "command": "npm run deploy",
      "env": {
        "NODE_ENV": "development",
        "DEBUG": "app:*"
      }
    },
    "deploy:prod": {
      "command": "npm run deploy",
      "env": {
        "NODE_ENV": "production",
        "DEBUG": "app:*"
      }
    }
  }

Heroku with the create-react-app buildpack will run npm install followed by the build script and finally start.
If this works for you, you may also find issues with routing once the app is up: I fixed this by adding
app.get('*', function (request, response){
    response.sendFile(path.resolve(project.paths.dist(), 'index.html'))
  })

in main.js under the line app.use(express.static(project.paths.dist()))


Cannot read property 'parent' of undefined

🐛 Bug Report
I have seen other people mention some similar issue with 'push' recently. I am having this happen using the Trail component with data that is being fed as a list. The list is a state and gets updated via componentDidUpdate()
If i pull this out of the trail component and just render the Animated box by mapping groupIdsByDayData[i], everything works fine but of course I lose all the fancy animations.
<Trail
                                native
                                config={config.gentle}
                                // items={this.groupsDataArrayForDay(i)}
                                items={groupIdsByDayData[i]}
                                keys={item => item.id}
                                from={{ opacity: 0, x: 40 }}
                                to={{ opacity: 1, x: 0 }}>
                                {item => ({ x, opacity }) => {
                                    let editState = editing
                                    if (item.program_id !== program.id){
                                        editState = false
                                    }
                                    return(

                                        <AnimatedGroupBox style={{
                                            opacity,
                                        }
                                        }
                                                          color = {this.props.allPrograms[item.program_id].color}
                                                          key={item.id}
                                                          group={item} edit = {editState} />
                                    )}}
                            </Trail>

debugger links to this part of the app.js code, some part of Spring?

To Reproduce
Hard to reproduce, happens randomly after I try a few updates.
Expected behavior
that it magically works :)
Link to repro (highly encouraged)
(Please provide either a CodeSandbox demo or an example GitHub repo.)
Environment
"react-spring": "^8.0.19",
"react": "^16.8.6",
"react-dom": "^16.8.6",

If I use just a SPRING component and map the list manually, it also seems to work.

{groupIdsByDayData[i] && groupIdsByDayData[i].map(item =>
                                <Spring
                                    native
                                    key={"new"+item.id}
                                    config={config.wobbly}
                                    from={{ willChange: 'opacity,transform', opacity: 0, transform: 'translate3d(0,-40px,0)' }}
                                    to={{ opacity: 1, transform: 'translate3d(0,0px,0)' }}>
                                    {styles =>
                                                <AnimatedGroupBox style={styles}
                                                color = {this.props.allPrograms[item.program_id].color}
                                                key={item.id}
                                                group={item}/>}
                                </Spring>

                                                )}

Can you try it with the v9 beta?
npm install react-spring@next

Make sure to change the import path:
// You can import the <Trail> component from the main module now.
import { Trail } from 'react-spring'

Hello @bytewoopy. Please try with react-spring@next and I'll reopen if the issue persists.

I'm experiencing the same issue with useTrail in 8.0.27, however upgrading to react-spring@next isn't viable for me at the moment due to other issues with trails that I've noted in the v9 issue. For me, this error occurs when the animated component is unmounted.
Here's the error's call stack, I can provide more information if needed!


Division updates(additions of new divisions) using FOI FLOW Admin , need to Sync FOIDocumentreviewer DB as well

Title of ticket:
Description
As part of Regression testing for the release of Gathering records, its being found that Updates/ additions to Divisions on FOI FLOW DB using Admin Modules will also need to update FOI Document Reviewer DB, else Computing Services functionalities will get affected!
Dependencies
Are there any dependencies?
DOD

[ ] List the items that need to be complete for this ticket to be considered done
[ ]
[ ]
[ ]
[ ]

Per comments on teams - I updated one of the WLRS Divisions - I didn't add or remove, just made an edit to update the name. Division was updated to 'Coastal Marine Stewardship'
cc @nkan-aot

No estimate yet because Emerald is still under discussion.

Note for this ticket - I've updated divisions for EMCR (Ministry of Emergency Management and Climate Readiness)

Added divisions for MOE/ENV (Ministry of Environment and Climate Change Strategy).
CARD – ADMO
CARD – Conservation Officer Service
CARD – PSB – Exec Director
CARD – PSB – Capital Investment
CARD – PSB – Recreation Services
CARD – PSB – Visitor Services
CARD – PSB – Engagement, Education & Enhance
CARD – PSB – Conservation
CARD – PSB – Planning & Land Administration
CARD – PSB – Indigenous Relations
CARD – Recreation Sites & Trails
CARD – ROB – Exec Director
CARD – ROB – Interior Region – Kootenay/Okanagan
CARD – ROB – Interior Region – Thompson/Cariboo
CARD – ROB – Northern Region – Skeena
CARD – ROB – Northern Region – Omineca – Peace
CARD – ROB – South Coast Region – Coastal Mainland
CARD – ROB – West Coast Region – Vancouver Island
CAS – ADMO
CAS – CGB – Exec Director
CAS – CGB – Clean Investment
CAS – CGB – Industrial Reporting & Control
CAS – CGB – industrial Climate Policy
CAS – AEAB – Exec Director
CAS – AEAB – Economics & Analysis
CAS – AEAB – Climate Strategy Development
CAS – CPEB – Exec Director
CAS – CPEB – Policy Integration & Engagement
CAS – CPEB – Partnerships
CAS – CPEB – Clean Government
CAS – RIRB – Exec Director
CAS – RIRB – Climate Risk Management
DMO – Correspondence Unit
DMO – Deputy Minister’s Office
EPD – ADMO
EPD – CEEB – Exec Director
EPD – CEEB – Compliance & Enviro Enforcement
EPD – ESB – Exec Director
EPD – ESB – Clean Air, Integrated Pest Mgmt & Bonding
EPD – ESB – Clean Communities
EPD – ESB – Clean Technologies
EPD – ESB – Extended Producer Responsibility
EPD – EMAB – Exec Director
EPD – EMAB – Analysis & Reporting
EPD – EMAB – Environmental & Climate Monitoring
EPD – ROB – Exec Director
EPD – ROB – Authorizations – North
EPD – ROB – Authorizations – South
EPD – ROB – Monitoring, Assessment & Stewardship
EPD – ROB – Mining Operations
EPD – ROB – Digital Services
EPD – ROB – South East Coal Mining
EPD – Regulatory Effectiveness & Sector Integration
SSD – Indigenous Partnerships & Engagement
SSD – SPB – Exec Director
SSD – SPB – Legislation
SSD – SPB – Intergovernmental Relations
SSD – SPB – Planning, Evaluation & Performance Mgmt
SSD – STB – Service Transformation
MO – Minister’s Office

Added divisions for CFD (Ministry of Children and Family Development)
Minister’s Office
Deputy Minister’s Office
Client Relations Branch (DMO)
Finance and Corporate Services
Analytics (FCS)
Provincial Director of Child Welfare
Partnership and Indigenous Engagement
Service Delivery Division
Strategic Integration, Policy and Legislation
Litigation (SIPLD)
Strategic Services Branch

Note - I've tagged this as release 9.0 - changes to the DB for divisional updates will cause doc reviewer errors, this should be done prior to release, or very soon after

Code:
EMLI
Added:
Energy Resources Division
Electricity and Utility Regulation Division
Energy Decarbonization Division
Corporate Service for the Natural Resources Sector (CSNR)
Updated:
Mines, Competitiveness and Authorizations Division changed to Responsible Mining and Competitiveness Division
Strategic and Indigenous Affairs Division changed to Strategic and Indigenous Partnerships Division
To be deleted when appropriate (there are records associated with these three divisions):
Oil and Gas Division
LNG Canada Implementation Secretariat
Woodfibre Implementation Group

Added:
'Corporate Management Services Branch'
Org Code:
HSG

@abin-aot, is this still high priority for the 9.0 release?
Cc @KyEggleston @liseandtea

Associated to #4183?

Yes! #4183, this ticket is related and can be concluded as duplicate . Also to indicate #4184 can be done along with this ticket @KyEggleston

@abin-aot - are we good to link these tickets (#3838, #4183 and #4184) together, and I can close this ticket? Just want to make sure the information in this ticket isn't forgotten, especially if needed for the other tickets. Thanks!

@Aman-Hundal @milosdes - review as part of #4183


Project tagline is confusing

"A Handlebars view engine for Express which doesn't suck."
Why does the other handlebars view engine suck? Why should I use this one over that one? The Readme does not give enough details on this.

Agreed, it could be something better like
A better Handlebars view engine for Express
or maybe the other Handlebars view engines suck, I dont know, I didnt try them :sweat_smile:

I am just a maintainer of this repo so can't change the tag line, and I haven't seen Eric active much anymore. I am going to close this issue.


Hex generation from RGB without colormap

Hex generation can be done without colormap. Hence saves us to import a module.

I'll check that if it works. Until then remove Colormap and Easydev from requirements.txt and test again with venv.
Thanks for the improvement, I'll merge once tested.


Missing S3FileSystemInfoTest.java

Hello, I noticed that the test class in the subject is not anymore there. Is it wanted?

Hmm, it may have gone missing during the refactoring. Will need to pull it back in from a prior commit.

Just checked back through the last five releases and I'm not sure we ever had a test for this. Unless I am looking in the wrong place. I can see one for S3XFileSystemInfoTest.java


Extension: only show Toolbar when XF project is open

When I start my VS2017 I'm often confused why there is an empty toolbar icon

until I notice this is Hotreload Connect Icon. Display it only when a project is loaded that targets Xamarin.Forms

Yes, I think it makes sense

@stanbav what do you think?

Yes, that's something that should be fixed.)

Fixed in https://github.com/AndreiMisiukevich/HotReload/commit/d24ea31dc0c3751a2c13ff3dcdba82794893cd60. Will be included in next release (1.2.0).


Supabase integration and misc features

Saving all data for the API in the supabase db
Support for multiple apps with their own API keys
Authentication for apps
Support for multiple agent accounts per user (apps can have many users)
Tracking for submitted batches of transactions

Code that tracks dev mode and switching between cli and API versions is a bit wonky and could be refactored in the future

/workflows/benchmarks agents/token/send 3


Add support for kafka 3.0.0

Sonic fast: https://github.com/apache/kafka/releases/tag/3.0.0

Aside: should we have constants for V2_7_0_1 and V2_8_0_1 ?

Great question: do we want to add constants for all minor versions? This is the hack I'm doing in Burrow to get around this, for instance: https://github.com/linkedin/Burrow/blob/master/core/internal/helpers/sarama.go#L26-L70

If/when we move to using ApiVersionsResponse results to gate protocol, I guess we wouldn't necessarily have these constants anymore


Pipe npm script to a function

is it possible to pipe the output of a npm script to a javascript file that using notifier to display the text.
This doesn't work but its what I'm trying to do
"flow": "flow | node config/notification.js"
I would like to pick up the flow output and use it as the message for this script.
var notifier = require('node-notifier');
notifier
.notify({ message: 'Script complete', wait: false }, function(err, data) {
});

that looks like what i need


Add DeliveryOrder status condition or annotation for Trigger

Problem
In https://github.com/knative-sandbox/eventing-kafka-broker/pull/701 we introduced a new annotation to configure the delivery order and during the discussion there, we come up to the conclusion that would like to have a status condition to give users feedback on it since we don't have a way to signal that the annotation has been read correctly.
Persona:
Which persona is this feature for?

Event consumer

Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
Time Estimate (optional):
How many developer-days do you think this may take to resolve?
1
Additional context (optional)

Discussion in https://github.com/knative-sandbox/eventing-kafka-broker/pull/701

Added to #589

/assign


Couldn't import crnn module using project root as a namespace

Hi,
I use crnn-pytorch as a submodule with name pytorch_crnn. The project has no package namespace so I've done a quickfix with a relative import to fix import problem.
The proper way to do this is to introduce single root package (+ setup.py) and move all code except the scripts under this package. Then code can be imported as from root_package_name.foo import bar.

:+1:
Thanks for PR


Configure Widoco to execute files with accents properly

For example, here: https://raw.githubusercontent.com/opencitydata/vocabularios-datos-abiertos/master/turismo/alojamiento/0.1/alojamiento.owl the encoding is not properly shown.
This could be solved with the -Dfile.encoding=utf-8 option when executing the JAR.

@dgarijo I'm getting the below error with Widoco running this command
java -jar /home/ubuntu/Widoco/JAR/widoco-0.0.1-jar-with-dependencies.jar -Dfile.encoding=utf-8 -rewriteAll  -ontFile<EMAIL_ADDRESS>-outFolder<EMAIL_ADDRESS>-confFile<EMAIL_ADDRESS>Command-Dfile.encoding=utf-8 not recognized.

@idafensp ar2dtool is also giving an error for this owl file

I have just tried and it works. Maybe it's a java special feature of the distribution you are running. I have also tried it in a Unix environment and it works too.

It seems to be working for me also. Could you upload your conf file?

@idafensp I'm sorry idafensp, the problem was related to a change I made on the ontology file. Thank you


Add custom field

[x] commit messages are commitizen-friendly
[x] code is unit tested
[x] code is integration tested
[x] public code is documented
[ ] code is reviewed by at least one person
[x] code satisfies linter rules

Same support for category sync is also planned?

@Siilwyn Tests are failing though, so maybe you check that.

@Siilwyn custom fields are not supported for category-sync. Should this be part of this PR too?

@butenkor no I'd like to limit the scope of this PR, sorry about the confusing branch naming. The inventory has priority for now, in the future all (category, order, product) should support custom fields.

Changes Unknown when pulling 390210083be44a06e7629c784acbb67a916a567e on add-custom-field into ** on master**.

Changes Unknown when pulling 390210083be44a06e7629c784acbb67a916a567e on add-custom-field into ** on master**.

Changes Unknown when pulling 390210083be44a06e7629c784acbb67a916a567e on add-custom-field into ** on master**.

Changes Unknown when pulling 390210083be44a06e7629c784acbb67a916a567e on add-custom-field into ** on master**.

Changes Unknown when pulling 390210083be44a06e7629c784acbb67a916a567e on add-custom-field into ** on master**.

PR ready, @PhilippSpo or @emmenko merge please. :)


Build SwiftUI version of tvOS app

Scroll to item in SwiftUI 2 - https://stackoverflow.com/questions/60855852/how-to-scroll-list-programmatically-in-swiftui
Needs tvOS 14 though - should we wait?

SwiftUI example for TVOS: https://www.alfianlosari.com/posts/building-expense-tracker-apple-tv-app-with-core-data-swiftui/

App lifecycle details: https://peterfriese.dev/ultimate-guide-to-swiftui2-application-lifecycle/


Implement iterative NTT algorithms

Implement iterative NTT algorithms
Description
This aims to close #125 by expanding the current FFT library with iterative algorithms, which can be more easily optimized and will be ported to Metal/CUDA in a future PR. Also gives the user more power to use convenient algorithms in particular situations.
Update: The iterative algorithms implemented are at least ~4x faster and have ~6x times the throughput than the current recursive one (accounting with the calculation of twiddle factors and a bit-reverse permutation, input size of 2^20). This means that a new objective for another PR would be to replace the recursive one with these. Also the NR algorithm seems to be faster than the RN (I'm not sure why).
Type of change

[x] New feature

Checklist

[x] Linked to Github Issue
[x] Implemented all relevant algorithms
[x] Unit tests added
[x] Benchmarks added/run
[x] Documentation has been added/updated.

Codecov Report

Merging #127 (68a9692) into main (3c681a3) will increase coverage by 0.20%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #127      +/-   ##
==========================================
+ Coverage   95.71%   95.92%   +0.20%
==========================================
  Files          49       51       +2
  Lines        5251     5372     +121
==========================================
+ Hits         5026     5153     +127
+ Misses        225      219       -6

Impacted Files
Coverage Δ

math/src/fft/bit_reversing.rs
100.00% <100.00%> (ø)

math/src/fft/fft_iterative.rs
100.00% <100.00%> (ø)

math/src/field/element.rs
94.73% <0.00%> (+2.63%)
:arrow_up:

math/src/field/test_fields/u64_test_field.rs
73.68% <0.00%> (+7.89%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix runtime permission of entrypoint.sh

Commit MSG
In commit 1792f52 the entrypoint.sh is changed to run by autoware user.
This is done because the gosu command used to drop from root user to
autoware user does not work on Arm CI. However, this caused the side
effect that usermod is prevented from changing the UID of the autoware
user.
In this commit we revert back to running entrypoint.sh as root but drop
to autoware user using the chroot command.
Change-Id: I338c6135edcaeab5a53f35f98478d1f5ed30dafc
Issue-ID: SCM-1053
Signed-off-by: Liyou Zhou<EMAIL_ADDRESS>Bug fix
Fixed bug
https://github.com/Autoware-AI/docker/issues/2
Fix applied
Run entrypoint script as root and drop to user autoware using the chroot command instead of gosu to avoid any problems with the go runtime.

@JWhitleyWork We need your opinion here.
I reverted back to running the entrypoint.sh as root user in order to fix the problem stated in #2. However, this violates a linting rule. Would you accept a lint disable on that line? something like # hadolint disable=DL3002

Would you accept a lint disable on that line? something like # hadolint ignore=DL3002

Yes, this is fine. Also, you'll need to sign your commits. Please see the DCO check for more information.


Let make-manifests target work locally and within workflow

This time I tested it with nektos/act to make sure it'll run both locally and within the workflow.

Can you demo nektos/act for us next week?

Sure.


stuck on "Cross-Origin Request Blocked" warning

I'm trying to use this module in a Nuxt JS app and am facing this error while developing locally:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://www.youtube.com/playlist?list=PLWKjhJtqVAbnZtkAI3BqcYxKnfWn_C704. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).

Hi @phivk
Please refer to this answer on Stack Overflow
The one who answered it has mentioned -

I guess the API provider has not foreseen or planned for this API to be used from a frontend (e.g. JavaScript in the browser), so you would have to work around this.

That's true. This module wasn't primarily built to work in the browser.


Added support for new iTC check box

Fixes https://github.com/fastlane/fastlane/issues/4241

Look good to me :)

@KrauseFx  India is good for fastlane :)

Hi Everyone, I am trying to update fastlane but it says there aren't any updates. I was running into this issue and wanted to pull these changes.